Skip to main content

2 posts tagged with "Journeys"

View All Tags

Product Journey Checkpoint task

This release introduces a new Product Journey Checkpoint task type for onboarding journeys that launch multiple product-specific connected journeys in parallel. The checkpoint acts as a synchronisation point in the parent journey, ensuring product-level work is finalised before the parent journey proceeds to subsequent steps (for example, client-level verification and activation).

This release enables you to:

  • Add a Product Journey Checkpoint task to a Journey Schema in Journey Builder.
  • Pause a parent journey until all connected product journeys launched from the same parent are finalised.
  • View the set of launched connected journeys directly within the checkpoint task and navigate to them (subject to existing access permissions).

Configuration rules and validation​

  • A Journey Schema can contain only one Product Journey Launchpad task.
  • A Product Journey Checkpoint task can be added only to a Journey Schema that contains a Product Journey Launchpad task.
  • The checkpoint must be placed in a sequential stage and process that occurs after the stage containing the Launchpad task.
  • If a user attempts to save a Journey Schema that violates these placement rules, the save fails and an error toast is displayed:
    • Product Journey Checkpoint must be placed in a sequential stage and process that comes after the Product Journey Launchpad task
    • The invalid journey elements are highlighted in red.

Runtime behaviour​

When the Product Journey Checkpoint task becomes active, it identifies all connected journeys launched by the Product Journey Launchpad task from the same parent journey and displays them in a table with the following columns:

  • Journey (the Product Scoping Rule name that triggered the connected journey)
  • Name (the connected journey instance name; hyperlink to open, subject to permissions)
  • Journey Status
  • Application Status
  • Started

Completion logic​

  • The Complete button is disabled by default.
  • The Complete button is enabled only when all listed connected journeys have a Journey Status of Complete or Cancelled.