Implementing Journeys

Key points the exam tests

• Contextual Journeys trigger automatically based on business events (hire, transfer, promotion) — no manual assignment required.
• Learning task type links to an Oracle Learning course within a Journey, prompting the worker to complete it as part of their journey.
• AI Assist generates journey template content (tasks, descriptions, sequences) from a prompt. Set VB Studio 'Show AI Assist VB' constant to True to enable it.
• Guided Journeys appear as embedded side panels on specific HCM transaction pages, providing in-context guidance. Built in VB Studio.
• The full sequence: Configure RAG Agents (create tool + upload docs) → Process Agent Documents → Create RAG Agent → Create Workflow Agent → Create Guided Journey → Test via Journeys Assistant.
• Contextual Journeys trigger automatically based on defined business events (like a new hire), removing the need for HR to manually assign them.
• The seven task types are Document, Learning, Manual, Questionnaire, Report, URL, and ORC (Recruiting) Task — 'Questionnaire' lets workers answer survey-style questions as part of a journey step.
• Guided Journeys are embedded as side panels within a specific transaction page, providing in-context guidance exactly where the user is working — built using VB Studio.
• A RAG Agent retrieves relevant content from uploaded documents and uses it to generate accurate, grounded answers to worker questions — reducing generic or hallucinated responses.
• AI Assist uses generative AI to draft journey content from a prompt — the implementer still reviews and refines it, but starts from a generated draft instead of a blank template.
• Survey Journeys are specifically designed around Questionnaire tasks to gather structured feedback, and can be scheduled relative to an event like a hire date.
• The setup sequence is: configure the RAG Agent, process/upload its source documents, create the agent, bind it to a tool, then expose it through the Journeys AI Assistant.
• The Learning task type links directly to an Oracle Learning course, tracking completion as part of the journey's progress.
• URL tasks direct the worker to an external or internal webpage as a journey step — appropriate when the action happens outside Oracle's own pages.
• Guided Journeys are built and customized using Visual Builder Studio, which provides the low-code environment for embedding contextual side-panel experiences.
• Document tasks are designed for uploading files/attachments — exactly the use case for collecting signed acknowledgment forms.
• Automatic triggering ensures consistency — every new hire gets the journey without depending on a person to remember to assign it, reducing onboarding gaps.
• This VB Studio configuration constant must be set to True for the AI Assist journey-authoring feature to appear and be usable.
• ORC Task refers to Oracle Recruiting Cloud tasks — allowing journeys to include steps tied to the recruiting process, such as candidate-related actions.
• Journey tasks are commonly configured with relative due dates tied to the trigger event, so a change in that event date (like a start date) shifts the task timeline accordingly.
• Journey audience definition supports flexible criteria — organizational attributes, person type, and event-based conditions — allowing precise targeting of who receives a given journey.
• A Journey Template must be explicitly activated — this makes it available to trigger (for Contextual Journeys) or be assigned/enrolled (for other types).
• Oracle Process Automation can be integrated with Journeys to automate backend tasks/logic as part of a journey's execution, beyond tasks requiring direct worker interaction.
• Journey dashboards give administrators visibility into completion rates, in-progress tasks, and bottlenecks across the assigned population — critical for ensuring onboarding/offboarding stays on track.
• Journey Analytics quantify how workers engage with and complete journeys, letting HR assess whether a journey (e.g., onboarding) is actually achieving its intended outcomes.
• Journey Analytics is specifically designed to report on participation and completion data across a journey's assigned population, exactly the kind of metric described here.
• Combining Journeys with Process Automation lets routine backend actions happen automatically as journey steps progress, rather than requiring someone to manually perform them.
• Learning and Questionnaire are two of the seven standard Journey task types (alongside Document, Manual, Report, URL, and ORC Task). The other options are unrelated HCM structures.