This feature will allow user's to archive documents that were incorrectly uploaded, which removes it from the available documents. Or allow the user to unarchive documents at a later stage to make available again. Documents can be archived from the Entity Profile Page, outside of a journey context. Documents that are already linked to mandatory requirements will not be archived until they are unlinked.

User Guide Reference: Document Management V2 User Guide->Document Archiving

When adding related parties to a product the user will now have the ability to select existing related parties that are sourced from the main client's related party list. This removes the need for users to re-search and re-add Related Parties at the Product level even when those Related parties already exist on the client.

This release introduces support for migrating Entity Groups through the ETL process in Fenergo. This enables the transfer of Entity Groups, including their hierarchical Parent–Child relationships and verified data, ensuring accurate reconstruction in the target tenant.

Increased the ability to transform 12 different date formats in datasources to dates in ISO 8601 so they can be loaded correctly to Fenergo.

Three additional formats are now supported:

• yyyy/MM/dd (e.g., 2024/03/15)
• yyyy.MM.dd (e.g., 2024.03.15)
• yyyy-MM-dd (e.g., 2024-03-15)

ETL Product Documents enables the bulk migration of regulatory and KYC documents into Fenergo, allowing documents to be securely uploaded, validated, virus-scanned, and linked to the correct product with the appropriate metadata and access controls.

We’ve introduced a new optional Stage Datakey property on Journey stages to provide a stable identifier that does not change during Journey versioning or configuration promotion via Configuration Exchange.

When the Default Investment Account Name toggle is enabled, the Investment Account name is now automatically generated to include the linked Fund Product type, in addition to the Entity name and Fund name.

The updated naming formats are:

• No Fund linked: EntityName_Account
• Fund linked, no Product: EntityName_FundName_Account
• Fund and Product linked: EntityName_FundName_ProductType_Account

The name updates dynamically as Fund Product linkages are added or changed. If the generated name exceeds the configured character limit, it is truncated from the end. No new toggles or permissions are required - this behaviour is governed entirely by the existing Default Investment Account Name toggle. The tooltip text for this toggle has also been updated to reflect the new logic.

The recently released Document Metadata Policy Trigger Condition feature has been removed from the platform. Following release, we identified an issue that affects environments with high volumes of documents, and in order to protect the platform stability for all clients we have made the decision to remove this feature at this time while we work on a more robust solution. If you have already begun configuring this feature, please reach out to your Fenergo representitive who will be happy to advise on alternative approaches in the interim. We apologise for any disruption this may cause.

We've made some minor adjustments to the way that data is saved and validated within the Manage Products task. These changes are expected to improve performance by reducing the volume of changes that are saved at one time.

Screening resolutions can now be re-used when a screening process is reopened or when the same entity is screened again in a subsequent screening process (including in a different journey).

Where applicable, the most recently saved resolution for the same match is automatically populated to reduce repeat analyst dispositioning.