How are task performers and task owners determined in journeys?

The date when the action becomes effective for certain journey actions is predetermined.

Journey Action	Date When Action Becomes Effective
Add Pending Worker	Proposed start date of the pending worker
Add Assignment Add Temporary Assignment Add Global Temporary Assignment Change Location Change Manager Global Transfer Promote Transfer	First day of the new active assignment
End Assignment Termination End Temporary Assignment End Global Temporary Assignment Termination	Last day of the current active assignment

For example, in a journey for the termination action let's see how the eligibility profile is evaluated and when task performers such as line manager and HR representative are notified of their tasks.

Action and Evaluation	Date
Terminate worker	27-Sep-2023
Last day of active assignment	27-Sep-2023
Inactive assignment start date	28-Sep-2023
Journey eligibility evaluated, task owner and performer determined	27-Sep-2023

What Happens When Offset Days is Specified

You can specify offset days for a task to determine when the task should be evaluated and when task owners and performers should be determined. Say you create a journey for the transfer action which is effective 17-Sep-2023. You have 3 tasks one each for the current manager, new manager, and HR representative. Let's see how the task assignment date changes for each task performer based on the offset values you specify:

Task Details	Task 1	Task 2	Task 3
Name	Complete Performance Appraisal	Set Development Goals	Orientation Session with New Employee
Task Performer	Line Manager	Line Manager	AoR (HR representative)
Offset Days	-3 days	1 day	4 days
Task assigned and notification sent to task performers on	14-Sep-2023	18-Sep-2023	21-Sep-2023
Task performer determined based on offset days	Current Line Manager	New Line Manager	New HR representative

Evaluate Journey Task Performers and Owners During Task Initiation

You can evaluate task performers and owners during task initiation instead of task allocation by selecting the Evaluate task performer and owner when task is initiated option when you configure a task. For more information, refer to this topic: Can the journey task performer and owner be evaluated when the task is initiated?

The evaluation during task initiation 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.

This table shows the application behavior for each use case when the option is disabled or enabled:

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.