Executive summary
Due to our deprecation policy, certain custom implementations may have been removed in this release (see Removal notice). Identify configuration issues using the configuration validation before upgrading.
Removal notice​
The following features will be removed in the next major release:
- TBC
The following features have been removed in this release:
- Dynamic Web Twain integration (
DocumentLibraryType.DYNAMIC_WEB_TWAIN). Remove the document library from the module settings (DOSSIER_DOCUMENTS,PARTY_DOCUMENTS,IDENTITYandFINANCIAL_SP_DOCUMENTS) and flow step settings (DOSSIER_DOCUMENTS,PARTY_DOCUMENTS,PARTY_IDENTITY_DOCUMENTSandUBO_IDENTITY). - The flow option
DIRECT_INVESTOR_SMS. Existing config will be removed automatically upon releasing.
Deprecation notice​
The following features have been deprecated in this major release:
CreditsafeV7PartyProvider, superseded byCreditsafeV8PartyProviderCreditsafeV8PartyProvider, superseded byCreditsafeV9PartyProvider- The
identityStatuses,identityExpirationDateFromandidentityExpirationDateTocriteria on a party filter, replaced by the same criteria underindividualFilter. Existing configurations keep working and are reported by the configuration validation so they can be moved.
Configuration​
Dashboard tile totalling a numeric field​
A new DOSSIER_AGGREGATION dashboard metric shows the total or the average of a numeric dossier metadata field over the dossiers matching a filter — one bar per field, optionally reported as a percentage of one of the other bars — where the other metrics count dossiers.
See the built-in dashboard and the FINANCIAL_SP_DASHBOARD module for more information.
Choose which FSP field an SSO reference names​
SSO providers can now be told whether the FSP references they receive — the ones in the token and the fspExtRef entries of SSO_ROLE_MAPPING — name an FSP's external reference or its identifier: the external reference when the FSP naming is managed externally, the identifier when it is self-managed and has to stay stable. Existing providers are unaffected, since without the setting a reference is still matched against the external reference.
See SSO providers and the Keycloak SSO provider, where the organization alias is the reference in question.
Individual criteria grouped on the party filter​
Wherever a party filter is configured, the criteria that only apply to individuals — nationality, identity status and identity expiry dates — now sit together under individualFilter, next to the existing companyFilter. Configurations using the old top-level identity criteria keep working and are reported by the configuration validation, so they can be moved when convenient.
See the Data removal scheduled provider for a provider that uses a party filter.
Configurable report parameters​
Reports now define their own filter parameters instead of always offering a fixed "from" and "to" date. For each report you configure which parameters the FSP user fills in when running it, and how each one behaves — a date, a number, free text, a fixed list of values shown as a dropdown, or a configured list whose translated labels the user picks from. Each parameter's label and info text are translated like any other field label, so they follow the user's language and can be overridden per white label. A report can only be run with the parameters its query actually uses, and only value types the report engine can bind are accepted, so mismatched configuration is caught when you save the module instead of when a user runs the report. Existing report configurations are migrated automatically: each report keeps its date-range inputs where its query used them.
See the Reports library and the FINANCIAL_SP_REPORTING module for more information.
Configurable report filenames​
A report's filename can now carry the FSP's stable identifier or its external reference, a timestamp in any format you choose, and the values the user supplied when running the report, on top of the report identifier, run date and FSP name already available. A single report can override the FSP-wide filename pattern with its own when it needs a different name.
A report uploaded to a file server can also reuse the stored document's name in its destination filename, and format the upload timestamp. That is a new action, UploadReportToFileServerV2: UploadReportToFileServer is deprecated and keeps behaving exactly as before, so moving an FSP over is a change of action class and nothing else — the same filename settings produce the same names.
See the Reports library, the FINANCIAL_SP_REPORTING module and Upload a report to a file server for more information.
Editable default language on form definitions​
A form definition's default language can now be changed from the admin UI after creation, instead of being fixed at creation time. Because the default language's translation can never be deleted, moving the default to another language now lets you remove the language that was previously the default — no more JSON export/import workaround.
See the Form definitions library for more information.
Choose the documents step layout​
The dossier documents flow step can now be rendered as an assessment view — one card per document showing its assessment badge and message — instead of the default one-card-per-type view. Set the visualization setting on the documents flow step to ASSESSMENT_CARDS to enable it; it stays on the default view otherwise.
See Document Management in the flow for the setting.
Protect related parties against deletion in the flow​
The related parties flow steps now accept a deletableWhen condition that is evaluated per related party: only the ones matching it can be deleted in the flow, which is typically used to protect related parties delivered by an integration. Deletion outside the flow is unaffected, and without the condition every related party stays deletable.
See Protecting related parties against deletion in the flow for the configuration and an example.
Restrict status transitions by role and dossier​
A status transition's forRoles now also accepts custom role identifiers. By giving such a role a filtered permission, a transition can be limited to the dossiers that match the filter (for example a specific RBA rating or dossier service): users whose role does not match no longer see the transition offered, and it is rejected if attempted anyway.
See Restricting a transition to specific dossiers for the configuration and an example.
Restrict bulk actions by role and dossier​
A bulk action's forRoles now restricts which dossiers it acts on: each selected dossier is checked against what those roles grant, and dossiers outside their scope are skipped and reported as failed. The identifiers must point to roles that exist and hold the bulk-action permission, which is now validated when the settings are saved or imported; TRIGGER_EVENT actions no longer accept forRoles.
See Bulk actions for the configuration.
Linked parties​
Linked parties (for a given party) can now be seen in a table on a party details page.
The feature can be enabled in the module settings of the FINANCIAL_SP_PARTIES module.
Additionally, it is supported to limit the association types through configuration.
See the FSP Parties Module settings for more information.
Linked dossiers​
Linked dossiers (for a given party) can now be limited by the association types through configuration.
See the FSP Parties Module settings for more information.
Multiple configurable dashboards per FSP​
You can now configure more than one dashboard per FSP — built-in (metric) and iframe dashboards — each shown as its own tab in the configured order, with its own metrics and role-based visibility (an optional roles list per dashboard; a built-in tab is also only shown to users who may see at least one of its metrics).
Each dashboard has a stable identifier: its /dashboard/:identifier route key and the leaf of its tab-title translation key BACK_END.VALUES.DASHBOARDS.<identifier>.label (white-label overridable, the same way field and bulk-action labels work). Existing FSP definitions are migrated automatically.
See the Dashboard module for more information.
Ordering and percentages for custom dashboard metrics​
A custom (DOSSIER_FILTER) dashboard metric can now order its bars by dossier count instead of the declared order, and optionally show a percentage next to each bar's count relative to a configurable denominator filter. Both are optional settings, so existing dashboard configurations keep their current behaviour.
See the built-in dashboard configuration for more information.
Classify dossier documents in the flow​
A new DOSSIER_DOCUMENTS_CLASSIFICATION flow step lets front-office users go through a dossier's documents one by one and assign each a document type, either by clicking it or by pressing a configurable hotkey. You choose which documents are shown through a document filter and which document types can be assigned — each with an optional colour and keyboard shortcut — and the step is only complete once every selected document has been classified.
See the DocumentClassificationFlowStepSettings flow step for the configuration.
Creditsafe V9: search criteria per country​
A new Creditsafe V9 party provider is available. It takes the same settings as V8 and enriches the same data, but sends only the search criteria Creditsafe accepts for the party's country.
Creditsafe publishes a fixed set of mutually exclusive search criteria per country and rejects anything else — a criterion the country does not offer (most countries cannot be searched by VAT number, Taiwan only by name), a value that violates the country's length or format (a Dutch registration number must be 8 or 12 digits), a company name below the country's minimum length, or a country it cannot search at all (Gibraltar, the Isle of Man, Jersey, Guernsey, Israel, the Faroe Islands, Vatican City). Every one of those rejections used to reach the user as a provider error, or as a silent no-match when the search ran automatically.
V9 skips a criterion that cannot work so the next one is tried instead, refuses a search that cannot work at all with an error naming the field to correct, and narrows on an exact company name itself in the countries where Creditsafe does not offer exact matching. Parties are therefore resolved on their company number or name in cases where V8 silently found nothing.
Belgium is deliberately excluded: it already returned results before this change, so it keeps behaving exactly as it did, including its own message when a company name is too short.
Creditsafe V8 is deprecated in favour of V9.
See Creditsafe Party Provider for more information.
FinScan sanctions and PEP screening​
A new due-diligence provider screens individuals and companies against the FinScan ISI service. Each match FinScan returns is resolved into the CDD parameters the FSP has mapped to it, taking both the sanctions category and the PEP category of the matched watchlist record into account — so a sanctioned politically exposed person is recorded as both, rather than as only one of the two. A SCREENING_HIT parameter separately records whether anything matched at all, which distinguishes a party that was never screened from one that was screened and came back clean.
A branded PDF screening report is attached to the dossier when document fetching is enabled, with one page per match listing the category, dates of birth, nationalities and aliases an analyst needs to rule a false positive in or out.
See the FinScan provider for more information.
Convert uploaded documents to another format​
A new ConvertDocumentFormat automation converts a document right after it is uploaded, so the viewer, the document assessment provider and the client only ever see a format they can handle. Scans delivered as TIFF are converted to JPEG; the document itself is kept, and a file that cannot be converted stays as it was uploaded.
TIFF uploads also have to be allowed on the document's field definition, which now accepts tif and tiff.
See the ConvertDocumentFormat action for the configuration.
Screen a party's phone number and email for fraud risk​
A new Trustfull due diligence provider screens an individual's mobile phone number and email address for fraud signals, and reports each as its own due diligence parameter with its own PDF report on the party. You choose which of the two checks run and the fraud score above which a parameter is flagged.
This provider is experimental and is only available once ALLOW_EXPERIMENTAL_CUSTOM_CLASSES is enabled for the organization.
See the Trustfull provider for the configuration.
Serve a flow step to selected counterparties only​
Any flow step can now be limited to certain counterparty types, so one flow definition can serve counterparties with different jobs. Configure a generate step twice — once for the party that fills in the declaration and generates a PDF, once for the intermediary that only reviews the same data and generates none — or restrict a single step to the intermediary that keys data the party never declares itself.
Leaving applicableCounterpartyTypes empty keeps serving the step to everyone, so existing configurations are unaffected. Overlapping counterparty types are rejected at import for generate steps only; for every other step type the combination is not validated, because steps of one type are legitimately configured several times and told apart by their identifier. Make sure the restrictions you write there are disjoint.
See BaseFlowStepSettings for the configuration; every flow step inherits it.
Manage Keycloak organization users from Harmoney (beta)​
Where an organization's users live in Keycloak rather than in Harmoney, the FSP management area can now expose those Keycloak users instead of Harmoney's own partner list: set userManagement to KEYCLOAK on the FINANCIAL_SP_MANAGEMENT module and the Users tab is replaced by a Keycloak users tab, where a manager can add users, change their sub-groups, reset a password, update an email address and remove a user from the organization. The two tabs are mutually exclusive, and leaving the setting out keeps the built-in partner list, so existing FSP definitions are unaffected.
The screen authenticates against Keycloak with its own session, separate from the Harmoney one: Harmoney decides who may open the tab, Keycloak's manager group decides which organizations they may administer. It also requires the environment to be configured with the Keycloak realm and admin service, so it is enabled per environment rather than per FSP.
:::warning Beta This feature is in beta and still incomplete — it manages a subset of what Keycloak offers, has no audit trail on the actions performed from it, and its UI and configuration may change in a future release without a deprecation cycle. Agree the scope before enabling it for a production tenant. :::
See Keycloak user management for the configuration and prerequisites.
Grant roles per Keycloak organization​
A Keycloak SSO provider can now grant roles per Keycloak organization instead of a single flat role list: each organization the user belongs to maps to the FSP whose externalReference matches the organization's alias, and the groups the user holds within that organization decide which roles they get on it.
See the Keycloak SSO provider for the configuration.
Metadata fields on the dossier transaction​
The transaction of a dossier now supports metadata fields, the same way the dossier and party models already did. Once the fields are defined in the field-definition provider, they are shown on the transaction card of the dossier detail and can be filled in there. The fields are also available on the API Gateway and in the dossier CSV import through the dossier_transaction_metadata column.
The transaction card is only shown when the TRANSACTION module is activated, and without configured metadata fields nothing changes on it.
See the Field definition provider for the entities that support metadata fields, and the Modules for the TRANSACTION module.
UI/X-updates​
Source document preview in the flow (split view)​
Flows can now show a split view: the flow steps on the left and a preview of the dossier's source documents on the right, so users can transcribe data from e.g. a passport photo without switching context. The panel previews both image and PDF documents: images can be zoomed, rotated and panned, PDFs open in an embedded viewer with its own toolbar. It supports paging (buttons or arrow keys), documents can be pinned from the document tiles, and the divider position is remembered per user. The feature is opt-in per flow definition and can be restricted per counterparty type, per responsibility and per flow step.
See the Split view documentation for the configuration.
Party details drawer​
Party details can now be opened in a drawer, allowing users to review party information without leaving the current dossier context.
Number of dossiers on the clients and parties overview​
The clients and parties overviews can now show a "Dossiers" column: the number of dossiers the party is the client of. Dossiers in which the party only appears in another role (related party, UBO, signatory, ...) are not counted, and neither are archived dossiers or dossiers that are not visible to the front office. The overviews can be sorted on the column, ascending and descending; parties without any dossier take part in that ordering with a count of zero. Filtering on it is not available.
The column is not shown by default. Like other optional fields, the totalDossierCount field has to be made visible through the field definition provider before it appears on the overviews. As long as it is not visible, the counts are not computed at all, so the overviews of the organizations that don't use the column are unaffected.
The count is computed per request, so it is always up to date.
Working nationality filter on the parties list​
The nationality field in the parties list filter panel now actually filters. It was shown before but had no effect on the results.
Search the parties list on address​
The parties list filter panel now has a street and a country criterion, so a party can be looked up by where it lives instead of only by name, phone number, e-mail address, company number or external reference. The street is matched as a part of the street, so "Lilas" finds "Rue des Lilas 12"; the country is picked from the country list and several countries can be selected at once. Both criteria apply to individuals: selecting either of them narrows the list to individuals, and companies, indivisions and partnerships are left out. As long as neither is filled in, the list is unchanged.
Dossier lifecycle on the dossier list​
The dossier list can now show a "Lifecycle" column, next to the dossier status.
Like other optional fields it is not shown by default: the lifecycle field has to be made visible through the field definition provider.
Information Exchange​
[title]​
[description]
Complete an information exchange right after creating it​
Creating an information exchange now flows straight into completing it. After the form and counterparty have been chosen, the modal no longer closes silently: a final step confirms the information exchange was created and offers to complete it immediately, or to skip that for now. Completing opens the familiar completion dialog (choosing how to inform the counterparty), while skipping leaves the information exchange pending in the list where it can still be completed later via its "Complete" action. The step is only offered when the user is allowed to complete the information exchange, otherwise the modal simply closes as before.
Assignee for information exchanges on the intermediary side​
An intermediary FSP can now assign an ongoing information exchange to a specific user within its own organisation, so the work is clearly owned and distributed without exposing the assignment to the originating FSP. The assignee can be set, reassigned or cleared back to "Unassigned", and the information exchange overview can be filtered by assignee.
See the Modules for more information.
Completing information exchanges back to back on the intermediary side​
An intermediary FSP user can now complete information exchanges back to back through a "Start working" queue on the information exchange overview, instead of picking them one by one. The queue hands out the next available (pending, unassigned) information exchange, locks and assigns it to the user, and takes them straight into its flow; after finishing, the user is automatically taken to the next one until the queue is empty. Because each pick is atomic, multiple users can work the same queue in parallel without ever receiving the same information exchange, and an interrupted user simply resumes their own in-progress information exchange.
This feature can be enabled with the new informationExchangeQueue.enabled setting of the FINANCIAL_SP_INFORMATION_EXCHANGES module.
See the Modules for more information.
Role Based Access Control (RBAC)​
[title]​
[description]
Gateway​
Dossier created and last-edit timestamps​
The front-office dossier GET now returns two read-only timestamps: timeCreated (when the dossier was created) and timeUpdated (when it was last edited in the front office), both ISO-8601. They are ignored on create/update, so a client cannot overwrite them.
Transaction of a dossier​
A dossier now carries its transaction as a transaction object holding the amount, the currency and the metadata of the transaction. Existing integrations are unaffected: both the read and the write direction require the TRANSACTION module to be activated for the FSP.
See the Gateway release notes for the details.
Data Warehouse​
[title]​
[description]