Skip to main content
Version: 4.6

Release Notes

This version is available as of platform version v18.0.

Executive summary​

Information exchanges​

Information exchanges can now be managed through the front-office API Gateway. A new set of endpoints under /external/v4/financial-sps/{frontOfficeIdentifier}/dossiers/{dossierIdentifier}/information-exchanges allows you to create an information exchange, initiate it, list all information exchanges of a dossier, retrieve a single one, cancel one, fetch its questionnaire answers, and post an externally completed information exchange. These endpoints are available when the DOSSIER_INFORMATION_EXCHANGE module is activated. See Information Exchanges for details.

Trigger dossier automation​

A new endpoint POST /external/v4/financial-sps/{frontOfficeIdentifier}/dossiers/{dossierIdentifier}/automations/{automationIdentifier} triggers a given automation for an existing dossier. The automation is executed asynchronously. This removes the previous workaround of issuing an additional create/update dossier call to start an automation. See Automations for details.

Set dossier owner and assignee​

A dossier's owner and assignee can now be set through the API Gateway when creating or updating a dossier. A user is resolved by their email address: when the email matches a single known user, that user is assigned as owner and/or assignee. When the user is unknown, or when multiple users share the same email address, the dossier is still created or updated and the owner/assignee is left unchanged: resolving the user never blocks the request.

Task completion timestamp​

Dossier tasks now have a read-only timeCompleted timestamp next to the existing completedBy. It records when the task was completed. Both are empty as long as the task is open.

Multiple flow completion results per dossier​

The flow completion endpoint now accepts several flow completion results on the same dossier. Previously only one was allowed, on a dossier without flow completions. Every completion that is posted creates a new profile and keeps the documents of the previous one, so a submission date can be set several times through the API. Submission groups that are created in the application itself are not affected. See POST Flow completion results for details.

Migration guide​

  • Not applicable. All changes are backward compatible.