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.

Product Scoping Rules can now be imported via Configuration Exchange, both as direct selections and as automatic dependencies of journey schemas that reference them in a Manage Products task. Once imported, the Manage Products task in the target tenant uses the version of the Product Scoping Rule that was selected during the import.

A new Legal Hold mechanism has been introduced to block the deletion of an entity while legal or regulatory proceedings are active. Legal Holds can be applied to any entity type from the Entity Profile Page and suppress both the automated Data Deletion Scheduler and the Delete Entity Data API for as long as the Legal Hold is active. When the Legal Hold expires or is removed, the entity returns to the standard deletion lifecycle.

For user clarification, the entity data validation error that appears when field validation fails, has been updated to reference the fields label name as it appears in the task, rather than the underlying datakey identifier.

The Conflict Resolution task has been updated so that users only see the products and product fields they are entitled to see. Configurators also have the option to nominate Product Categories whose conflicted fields should default to "Current Verified Data" instead of "This Journey".

This feature introduces the ability to have the Manage Products Task be completed by the Autocompletion agent. This can be configured within the journey builder.