Journey administrators can now configure a setting in Journey Builder that restricts task reopening to users who belong to the team assigned to that task. When enabled, users outside the assigned team cannot reopen a task, ensuring the responsible team retains control over their assigned work.

KYC Analysts will now see a warning message when the combined first-level ownership of Related Parties to a main client exceeds 100% in the hierarchy. The warning appears inline as a brief toast message when adding new related parties and as a banner at the top of the task. This applies to both the Related Parties and Hierarchy Capture task types. The warning is informational only and does not block data entry.

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.