17 posts tagged with "Journey"

We’ve introduced a new optional Stage Datakey property on Journey stages to provide a stable identifier that does not change during Journey versioning or configuration promotion via Configuration Exchange.

When the Default Investment Account Name toggle is enabled, the Investment Account name is now automatically generated to include the linked Fund Product type, in addition to the Entity name and Fund name.

The updated naming formats are:

• No Fund linked: EntityName_Account
• Fund linked, no Product: EntityName_FundName_Account
• Fund and Product linked: EntityName_FundName_ProductType_Account

The name updates dynamically as Fund Product linkages are added or changed. If the generated name exceeds the configured character limit, it is truncated from the end. No new toggles or permissions are required - this behaviour is governed entirely by the existing Default Investment Account Name toggle. The tooltip text for this toggle has also been updated to reflect the new logic.

This enhancement introduces the ability to configure journey launch permissions at a team level, extending the existing Journey Launch Controls functionality. Configurators can now restrict which teams are permitted to initiate specific journey types.

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.

We've added 3 capabilities to the Connected Journeys View to improve usability and performance in journeys using Entity Grouping, Related Parties Launchpad and Agency Journey Launchad:

• Search Connected Journeys by Entity Name
• Filter by Journey Status (i.e. 'In Progress')
• Scroll bar will automatically appear when the number of Connected Journeys Requires it.

The Policy Tasks Autocompletion feature allows for the automatic completion of Tasks by the system. A Task that is configured as such will only autocomplete if all Policy validation is satisfied within the individual Task. If there is outstanding validation, the Task must be completed by a User. A dedicated User Guide has been created for this functionality, under the "Journey" section on the Document Portal.