Overview of Contextual Journeys
Using Contextual Journeys you 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.
Even though you complete all tasks in a contextual journey, the HCM transaction won't start automatically. Therefore, it's recommended that you add an application task for the HCM transaction as the last task in the contextual journey template. Since contextual journeys aren't displayed on the My Journeys and Assigned Journeys tabs, only the initiator of the contextual journey will have an overview of the entire journey. Therefore, it's important to design or define your contextual journey accordingly.
You need to enable contextual journeys using the ORA_PER_CONTEXTUAL_JOURNEYS_ENABLED profile option. When this profile option is enabled and a configured contextual journey is available for a quick action, users see one or more eligible contextual journeys when they initiate a quick action from either Me, My Team, or My Client Groups.
To configure a contextual journey, you 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, you need to select a context such as Me, My Team, or My Client Groups. You then associate this context to a quick action.
Additionally, you can choose attributes that are available for the action and configure criteria that will determine who will see the contextual journey. For example, if you want the contextual journey and tasks to be specific to worker locations, you 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.
You can open a contextual journey by selecting a Redwood-enabled quick action when configuring the journey. For example if you use the Document Records quick action while configuring a contextual journey to add document records, you can open the document records Redwood page from the Journeys UI.
- The contextual journey is displayed only when you initiate the quick action directly from the Me, My Team, or My Client Groups tabs on the application home page. For example, the contextual journey isn’t displayed when you initiate the quick action from the list of actions for a worker in the My Team Overview page or from Deep Links.
- Consider this scenario. An Area of Responsibility (AoR) or line manager of a nonprimary assignment initiates a transaction which has a contextual journey. Additionally, the AoR or line manager starts the contextual journey. In this case, if the task performer or owner is a line manager or AoR, then the journey task is always assigned to the line manager or AoR of the primary assignment of the worker.
- You can't change the category of an existing journey to Contextual Journey. Instead, define a new contextual journey.
- The DocuSign and I-9 task types aren't supported in contextual journeys.
- All your contextual journeys configured for responsive quick actions will now open for supported equivalent Redwood quick actions.
- To know the list of quick actions supported for Contextual Journeys, you need to check the quick action list of values (LoV) on the journey setup page.
- The processing mode for contextual journeys is set to Alerts based notifications by default and BI Publisher notifications aren’t supported.
- You can't configure an eligibility profile at the journey or task level for contextual journeys.
- The Don’t copy, use source document check box is available when you configure a Document task type only in a contextual journey. If you enable this setting, a copy of the document isn’t created at the time of task assignment thereby improving performance.
- Contextual journeys don't support all the journey display properties. For example, you can't hide the Contact Us section for a contextual journey.