Restrict Assigning Journey When it's in Progress

You can now configure a journey such that it’s not assigned again to the same person when the earlier assigned journey instance is still in progress with unfinished tasks.

Configure Option by Setting Value to Yes

Error Message Displayed When Option is Configured and Journey is Again Assigned When Earlier Instance is in Progress

This feature helps to avoid duplicate instances of the journey being assigned to the same person.

Steps to Enable

To enable this feature, refer to this topic: How do I restrict assigning a journey when it's in progress?

Tips And Considerations

• The Restrict assigning journey if it's in progress configuration option is available only on the Redwood Journey Templates page.

• The error message is displayed only when assigning the journey to a single person from the Assign Journeys page.

• For journeys assigned to Directs, Organization, or Filtered List, the following error message is displayed on the Activity tab for those persons who already have an in-progress journey: Journey already exists.

• When the option is set to Yes, the application will skip assigning the journey to those persons who already have an in-progress journey, when the journey is assigned either manually or automatically.

Key Resources

For more information about journeys, refer to the Implementing and Using Journeys guide on Oracle Help Center.