Skip to main content

5 posts tagged with "Journey"

View All Tags

Journey Launch Controls Per Team

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.

Journey Cancellation Comment Configuration

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

Enabling Parallel Risk tasks Within Journey Builder

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.

Connected Journeys View enhancement

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.

Policy Tasks Autocompletion

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.