How Journeys are Assigned

An assigned journey is a specific instance of a journey template.

This table lists the different methods a journey and task can be assigned.

Type	Method	What's assigned?
Automated	Employment actions that includes actions such as, Add Pending Worker, Hire an Employee, Add a Contingent Worker, Create Work Relationship, and Local and Global Transfer.	Journey and tasks
	HCM Events that includes events such as, person data change, add absence, update marital status, and upload document record.	Journey and tasks
	Background processes that includes processes such as, Move to HR, and Convert Pending Workers.	Journey and tasks
	Workers REST is used to add new workers, update existing workers, and so on. The journey is then assigned to the workers created by REST API.	Journey and tasks
	Creating a nudge to trigger journeys.	Journey and tasks based on nudges
Manual	Assigning from the Journeys page by selecting single and multiple assignees.	Journey and tasks
	Creating a recurring survey journey.	Survey journey and task
	Creating a recurring journey.	Recurring journey and tasks
	Creating a contextual journey that can be started through a quick action (for example, Promote, Transfer, and so on).	Contextual journey and tasks
	Reassign task	Task
	Add task	Task
	Journey REST APIs (assignJourney, workerJourneys, workerJourneyTasks, and so on).	Journey and tasks
	Journey Allocation HDL (AllocateChecklist.dat)	Journey and tasks

Points to Consider

• Notifications aren't triggered when a journey is assigned using HCM Data Loader. You can explore a custom report to send out a generic notification or email for journey task assignees to review their tasks.
• When you enter a person name to assign the journey in the Person list of values (LoV), the search results display the person number and assignment status attributes in addition to the person name and business title. However, to see the assignment status attribute, you need to enable Oracle Search. For more information about setting up Oracle Search, see the topic in the Related Topics section.
• When a journey is manually assigned from the Journeys UI for a single person, the journey eligibility profile isn't evaluated. However, eligibility profiles are evaluated for the tasks in the journey.
• When a journey is assigned from the Journeys UI to multiple people at the same time, these things happen:
  • An ESS job is activated that evaluates eligibility for the journey and it's tasks.
  • The Mass Assign Journeys ESS process is internally run to process the multiple journey assignments.
• When you assign a journey to multiple people from the Assign Journey UI and you have selected a nonprimary assignment for one of the workers, the journey doesn't get assigned to any worker. However, when you assign the journey to only one worker, it's assigned to the primary assignment of the worker.
• When a journey is assigned using HDL auto-allocation, the eligibility is evaluated using the AllowAutoAllocation attribute flag. If the attribute flag is set as Y (default value), then eligibility is evaluated at journey and task level.
• Journeys can only be assigned to persons of the type employee, contingent worker, and pending worker. They can't be assigned to candidates who are in the offer stage and non-workers. However, you can't assign a journey to a pending worker from the Assign Journey UI.
• When there are no tasks for the journey assignee, the journey won't be visible to the journey assignee in the My Journeys tab.
• If the user name is changed after the journey is assigned, the journey or task awaiting assignment (deferred) is still associated to the previous user name as of the task activation date.
• If the user tries to access the task notification after the user name is changed, the task details will be blank in the notification. Hence, the assigned task will have to be removed and added again to the assigned journey.
• The journey task doesn't get assigned to the future line manager or AoR for internal candidates. This is because the application checks for the line manager or AoR details only if the person type is that of employee, contingent worker, and pending worker. It doesn't check for nonworkers or candidates who are in the offer stage.
• For onboarding journeys, if you modify the start date of a new hire, the journey and task assignment dates won't change automatically. You will have to delete the assigned journey and manually reassign the journey.
• Self-assigned journeys are visible only for the person who assigned it to themselves. Additionally, these journeys aren’t available on the Assigned Journeys tab. However, the journey tasks for other performers are displayed on the My Tasks tab.