Journeys

Journeys

A journey extends the checklist functionality and enables all stakeholders to act on tasks in a
single application. Tasks guide workers when they experience a change be it work related such
as transfer or personal such as an update to their marital status.

Organization can create a journey by building on an existing checklist template or create a

brand-new journey in the Journeys app. A journey can be allocated manually or automatically.

Oracle introduced two type of Journeys as of now.

1. Guided Journeys
2. Contextual Journeys

Guided Journeys
 This feature can provide guidance such as tutorials, company policies, and best practices
in the context of an HCM flow using guided journey tasks. For example, tasks to help a
line manager transfer an employee.

 Based on the way developer setup the guided journey, when employees, line managers,
or HR specialists initiate an action they see a Guide Me button

 Guided Journey category can be used in Checklist Templates to setup and add tasks that
are relevant for the guided journey.
 Developer can only use tasks of the type Analytics, Document, Embedded Learning,
External URL, Manual Task, Questionnaire, Report, and Video in a guided journey.
 Journeys
 Below screenshot shows sample guided journey with Video and Manual Task, this can
add number of tasks by using below task types.
 Analytics
 Document
 Embedded Learning
 External URL
 Manual Task
 Questionnaire
 Report
 Video
Example Sample Video

Example Manual Task Type

 After Manager/HR completes going through the tasks, they can see completed symbol
beside tasks like below.
 Journeys

Contextual Journeys

Using Contextual Journeys, developer can configure tasks that need to be performed by
different task performers before a HCM transaction. For example, tasks that a manager needs to
do before a transfer action.

To configure a contextual journey, use the Contextual Journey category in Checklist Templates.
Unlike other journey templates, the attributes to configure contextual journey are different. In
addition to basic details, developer need to select a context such as Me, My Team, or My Client
Groups and then associate this context to a quick action.

Additionally, developer can choose attributes that are available for the action and configure
criteria that will determine who will see the contextual journey. For example, if business want the
contextual journey and tasks to be specific to worker locations, developer can configure the
location specific attributes at the template level. When the user initiates the quick action, they
will see the contextual journey that has been configured for that worker’s location.

 Below Is the sample contextual Sample journey for transfer which Manager/HR should
complete given tasks before perform transfer of an employee.
 Journeys

 Manager/HR should click on start Journey to finish the given tasks and if developer
configure task for any other users based on AOR. i.e., they will get notification to
complete the assigned journey task.
 Journeys

 If tasks are not manadatory, performer can click Contiue Without Journey and do the
transfer as usual.
 Journeys

Then Click on Continue

Journeys