Two new configuration types are now available for import via Configuration Exchange, extending the platform's ability to promote consistent configuration across tenant environments.

This release introduces Hierarchy Comparison Insights within the Related Party step of the External Data – Entity Enrichment task. This summary highlights missing entities, missing associations and other differences and supports the user in making informed decisions on whether to retain, update or remove associations.

KYRA:Screen's hit adjudication logic has been updated to improve consistency and accuracy across entity types.

Journey administrators can now configure a setting in Journey Builder that makes the 'Reason for Cancellation' dropdown mandatory when cancelling a journey. When enabled, users must select a reason for cancellation before a journey can be cancelled.

To allow for STP scenarios, the Related Party Data & Documents task has been enhanced to support task autocompletion configuration.

User Guide Reference: Working with Journeys->Working with the Autocompletion Agent

Journey administrators can now configure a setting in Journey Builder that makes the comment field mandatory when reassigning a task. When enabled, users must provide a comment before a single or bulk reassignment can be submitted, ensuring the receiving user or team always has context for why a task was redirected to them.

Advanced Dashboards now remembers your last-selected saved filter between login sessions. When you log back into Fen-X, the saved filter you had active on the Tasks or Journeys dashboard is automatically restored, saving you from having to re-select your filter preference at the start of each working day.

Clear API failure notifications are introduced to keep users informed when connectivity issues arise during the ISDA Data Sourcing task.

Users can manage their notification preferences from their profile page under the Technical heading, including opting in or out of in-app notifications and email alerts for these messages.

The ISDA Data Sourcing task in maintenance journeys will now automatically display the results grid from the last completed search, showing all previously linked and unlinked datasets.

To add or remove datasets under the same Match ID or to look for a new Match, the user can click the entity name to open the search with the previous criteria pre-populated and ready to return the latest data.

Dynamic Access Layer rules for Products can now use Lifecycle Status as a condition, and Product Access Layers are re-evaluated when the Verify Products V2 task is completed using the expected post-verification status. Together this allows access to a product to vary across its lifecycle — for example a pending merger or private deal can be restricted while in draft and opened up once it becomes Onboarded.