Evaluate Journey Task Performers and Owners During Task Initiation

We have enhanced the journey task configuration by giving you the ability to evaluate task performers and owners during task initiation instead of task allocation. You can select the Evaluate task performer and owner when task is initiated option when you configure a task.

This feature is applicable in these scenarios:

When a task is dependent on another task.
When a task is deferred based on a delay duration.
When a journey is deferred based on days for initiation.

Use Case	Evaluate task performer and owner when task is initiated - Disabled	Evaluate task performer and owner when task is initiated - Enabled
When a task is dependent on another task. For example: Task 2 is dependent on Task 1. Task 2 performer is the line manager. Line manager is changed before task 1 is completed.	Task performer and owner for the dependent task are evaluated as soon as the task is assigned. Task 2 is assigned to the current line manager. Even when the line manager changes, the task 2 performer continues to be the original line manager. Notification is sent only when the task is initiated. In this case, it is sent to original line manager.	Task performer and owner for the dependent task are evaluated only when the preceding task is completed, and the dependent task is initiated or activated. When the journey is assigned, task 2 appears as a disabled task since it’s a dependent task. Task 2 is shown as assigned to the current line manager. When task 2 is initiated, the task performer is re-evaluated as the changed line manager. Task 2 is removed from the original line manager’s list and is available in the changed line manager’s list. Notification is sent only when the task is initiated. In this case, it is sent to the changed line manager.
When a task is deferred based on a delay duration. For example: Task A has a delay duration of 10 days. Task A performer is the line manager. Line manager is changed before the delay duration is reached.	Task performer and owner for the task are evaluated as soon as the task is assigned. Task A is assigned to the line manager. Even when the line manager changes, the task A performer continues to be the original line manager. Notification is sent only when the task is initiated. In this case, it is sent to the original line manager.	Task performer and owner for the task are evaluated only when the task is initiated or activated. When the journey is assigned, task A appears as a disabled task since it’s a deferred task. Task A is shown as assigned to the current line manager. When task A is initiated, the task performer is evaluated as the changed line manager. Notification is sent only when the task is initiated. In this case, it is sent to the changed line manager.
When a journey is deferred based on days for initiation. For example: Onboarding journey has the days for initiation configured as 5 days. Tasks B and D in this journey have the line manager as the performer. Line manager is changed before the journey is initiated.	Task performer and owner for all journey tasks are evaluated as soon as the journey is assigned. Task B and D are assigned to the line manager. Even when the line manager changes, task B and D performers continue to be the original line manager.	Task performer and owner for all journey tasks are evaluated only when the journey is initiated or activated. When the onboarding journey is assigned, the performers for tasks B and D are evaluated as the current line manager. Tasks are displayed as disabled (tasks waiting to be assigned). When the onboarding journey is initiated, the performers for tasks B and D are evaluated as the changed line manager.

Use Case

Evaluate task performer and owner when task is initiated - Disabled

Evaluate task performer and owner when task is initiated - Enabled

When a task is dependent on another task.

For example:

Task 2 is dependent on Task 1.
Task 2 performer is the line manager.
Line manager is changed before task 1 is completed.

Task performer and owner for the dependent task are evaluated as soon as the task is assigned.

Task 2 is assigned to the current line manager.
Even when the line manager changes, the task 2 performer continues to be the original line manager.
Notification is sent only when the task is initiated. In this case, it is sent to original line manager.

Task performer and owner for the dependent task are evaluated only when the preceding task is completed, and the dependent task is initiated or activated.

When the journey is assigned, task 2 appears as a disabled task since it’s a dependent task. Task 2 is shown as assigned to the current line manager.
When task 2 is initiated, the task performer is re-evaluated as the changed line manager.
Task 2 is removed from the original line manager’s list and is available in the changed line manager’s list.
Notification is sent only when the task is initiated. In this case, it is sent to the changed line manager.

When a task is deferred based on a delay duration.

For example:

Task A has a delay duration of 10 days.
Task A performer is the line manager.
Line manager is changed before the delay duration is reached.

Task performer and owner for the task are evaluated as soon as the task is assigned.

Task A is assigned to the line manager.
Even when the line manager changes, the task A performer continues to be the original line manager.
Notification is sent only when the task is initiated. In this case, it is sent to the original line manager.

Task performer and owner for the task are evaluated only when the task is initiated or activated.

When the journey is assigned, task A appears as a disabled task since it’s a deferred task. Task A is shown as assigned to the current line manager.
When task A is initiated, the task performer is evaluated as the changed line manager.
Notification is sent only when the task is initiated. In this case, it is sent to the changed line manager.

When a journey is deferred based on days for initiation.

For example:

Onboarding journey has the days for initiation configured as 5 days.
Tasks B and D in this journey have the line manager as the performer.
Line manager is changed before the journey is initiated.

Task performer and owner for all journey tasks are evaluated as soon as the journey is assigned.

Task B and D are assigned to the line manager.
Even when the line manager changes, task B and D performers continue to be the original line manager.

Task performer and owner for all journey tasks are evaluated only when the journey is initiated or activated.

When the onboarding journey is assigned, the performers for tasks B and D are evaluated as the current line manager. Tasks are displayed as disabled (tasks waiting to be assigned).
When the onboarding journey is initiated, the performers for tasks B and D are evaluated as the changed line manager.

Option to Evaluate Task Performer and Owner When Task is Initiated

Line Manager Owner and Performer Before Assigning

Line Manager Owner and Performer After Assigning

Ensures that the journey task is assigned to the appropriate performer when the task is activated.

Steps to Enable

To evaluate the journey task performer and owner when the task is initiated, instead of assigned, refer to this topic: Can the journey task performer and owner be evaluated when the task is initiated?

Key Resources

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

Access Requirements

You must be granted the Manage Journey (ORA_PER_MANAGE_JOURNEY_TEMPLATE) aggregate privilege to work on journey templates.