Pagero Integration

Pagero Itinerary Step

Async step that calls the pagero API. This call returns a FIleId that needs to be stored as a correlation ID on the async framework. This functionality must be implemented as the framework currently does not support this.

Prerequisites: Incoming document must be in PUF format

Pagero Scheduler Component

This step must call GetFileParts and GetDocuments (showFetchedOnly=false) and use the correlation/fileId to handle errors or resuming the flow. Finally call the fetched method to mark the documents as handled.

Pagero Authentication

Option 1 (HTTPHandler)

Component used for handling the authentication against the Pagero API. The HTTPHandler must provide a simple UI with credentials and a button that initates the auth process. The returned Auth-code must be used to fetch a refresh token to be stored in the Link settings so it can be used by the itinerary and scheduler step.

This reqired the client id and secret to be part of each link tenant. This however is not recomendable but the solution is intuitive and user friendly.

Option 2 (Central Identity host)

Create a new application where signin flow is exposed and store the client id and secret as part of this application. The user is redirected back to this application and can copy/paste the refresh token into Link settings

Option 3 (HTTPHandler and central identity host)

Same as option 2 but instead of showing the refresh token the user is redirected to a HTTPHandler in Link which stored the refresh token.