This enhancement introduces a configuration option to prevent the persistence of expired documents within document-related tasks. Once enabled, out-of-date documents will be flagged with an 'Expired' chip, giving greater visibility to document status and helping users easily identify expired documentation.

Gives users the ability to remove multiple associated entities from the Related Party hierarchy in a single action, with permission-based access, confirmation and progress modals, and changes finalised after the Verify Related Party Associations V2 task.

New approach to rate limiting Ingress Events by complexity.

ISDA Initial Data Sourcing task enhancements including individual linking of datasets, support for extra data sets (include EMIR Legacy, EMIR Refit (UK and EU), and SBS) and MR Support

This enhancement introduces the ability to configure and display custom metadata fields as additional columns within the Linked Documents and Matching Documents grids. This provides greater visibility of document-level data directly in the UI, reducing the need for users to open individual document records. Users can configure up to two text-based metadata fields (excluding rich text) via the Document Metadata Configuration screen. Once enabled, the selected fields will appear in the relevant document grids, with values truncated for readability and full text available via tooltip on hover. This enhancement applies to document requirements using the Document V2 framework.

A new secondary identifier field is now available for LexisNexis and any custom screening provider: Passport Number. This must be enabled in the screening provider's Secondary Identifier Configuration in order to use. For LexisNexis Ongoing Screening (OGS), the Batch Formats configured in Bridger must be updated to include Passport Number for it to be sent and used in OGS. The updated Batch Format files can be downloaded from the User Guide.

A new configuration setting has been added to allow administrators to require users to enter a comment when waiving a document. This setting can be enabled from the Document Requirement Metadata configuration screen. When turned on, users will not be able to complete a waiver without providing a comment. The configuration applies to all waiver tasks going forward and supports improved compliance tracking.

User Guide Reference: Document Management -> Mandatory Comments on Document Waiving

A new configuration option has been added to allow tenant-level control over whether users are required to provide comments when cancelling a journey. A user with the journey edit permissions can now enable or disable the "Require comments when cancelling a journey" setting from the journey configuration panel. When enabled, users must enter a comment before cancelling a journey. The setting is applied automatically across all in-flight journeys, with no need for manual saving.

User Guide Reference: Configuring Journeys -> Mandatory Comment on Journey Cancellation

This feature removes the validation that prevented users from adding a Risk Assessment task (of any type) to a process within a stage that was configured with process completion order set to 'In any order'. This allows you to complete jurisdictional KYC requirements within the same stage, improving overall onboarding times by better supporting parallel work effort.

An update has been applied so the Related Party Scoping Rules can now be located under the Journey management menu option.

User Guide Reference: Related Party Management->Related Party Adapted Experience