The Screening Agent now supports AI-powered summarisation of articles linked within the Sources tab of a screening match. Analysts can generate structured per-source summaries and a consolidated overview to review key information more efficiently.

With the release of this feature, document requirements are now sorted by mandatory status by default, with mandatory documents displayed first.

This release introduces Automatic Client Re-onboarding, an enhancement that simplifies bringing previously offboarded jurisdictions back into scope.

When the Automatic Re-onboarding Toggle is disabled, re-onboarding continues to require users to explicitly select the jurisdictions they intend to re-onboard on the Journey Launchpad; only selected jurisdictions return to scope. To make this clearer, the Re-onboarding Journey Hub now displays messaging when scoping criteria are met for a jurisdiction that was not selected for re-onboarding.

When the Automatic Reonboarding Toggle is enabled, partially offboarded jurisdictions automatically return to scope once their trigger conditions are met again, while fully offboarded jurisdictions still require a Re-onboarding Journey to reapply the client chip and re-evaluate policy scoping. Data deletion schedules will be paused while an offboarded jurisdiction is being reonboarded.

An enhancement has been introduced for the loading of documents on the Entity Profile for scenarios where a large number of documents are associated with the entity in profile. A "Preview" chip will appear in the "Documents" component on the "Overview" tab of the Entity Profile with first 50 documents available. A user can navigate to the "Documents" tab to continue the load of remaining documents.

Alias Name Screening has been extended to the LexisNexis integration, allowing entities to be screened using multiple names, such as aliases (AKA), former names (FKA), and native-script name variants—within a single screening submission. This capability, which is already available for WCO and custom screening providers, has now been enhanced to deliver the same multi-name screening experience for LexisNexis.

Screening results for each alias are consolidated under a single legal entity, with clear traceability of which name triggered each match. This enhancement reduces manual overhead, improves screening coverage, and increases transparency by removing the need to submit and reconcile multiple screening requests for the same entity.

This feature enables users to query information related to data retention for offboarded and partially offboarded entities.

You can now cancel an envelope in the eSignature task by clicking the cancel button after sending. This eliminates the need to remove a document linked to a requirement and then re-upload it to void the envelope and create a new one.

This feature introduces a new task which gives the user the ability to search an external data source whilst building out their hierarchy. This task will work hand in hand with the previously released Related Party Data & Docs and will replace the existing Related Parties task.

This feature introduces the ability to configure the automatic attachment of a document that has been generated via the Automated Document Generation task to a corresponding eSignature document requirement.

This feature introduces the ability to auto-complete the eSignature task once all recipients have signed. This feature is configurable.