Back to AI Agents and AI Agent Studio

ORACLE HCM · AI IN JOURNEYS

Where AI fits in your Journeys

Oracle's AI features for Journeys, shown where they actually happen: inside the tasks, for the performers who see them.

For Oracle HCM teams running Journeys · Last reviewed October 2026

SHARE THIS PAGE

The AI in Journeys

HOW TO EXPLORE THE JOURNEYS

See where Oracle's AI features fit inside real journeys, and which to start with.

The journeys on this page are examples I've built to work like real Oracle journeys: an onboarding, a move to a new role and a leaver. They use made-up tasks and roles, not anyone's real data, so you can see where each AI feature would appear and how it helps. Oracle's own screens look different: this shows the flow, not Oracle's design.

The page has three parts:

  • The six feature cards: what each AI feature does and how much setup it needs.
  • Which ones first?: tick the situations that sound like yours for my suggested starting point.
  • The journey explorer: one example journey from start to finish, from building the template to the last task, with the AI marked wherever it can help.

To use it:

  1. 1

    Tick the situations that sound like your organisation to see which features to start with.

  2. 2

    Pick a journey and whose tasks to show. Turn on Show the AI to see where each feature appears.

  3. 3

    Select a card or any ✦ button to see what that feature does, how to set it up and what to watch for.

Which ones first?

You won't need all of them. Tick what sounds like your organisation.

JOURNEY
HIGHLIGHT TASKS FOR
Show the AI
Helps HR and managers build and track journeysHelps the performer inside a taskActs when a task is saved or completed

New starter onboarding

CATEGORY: Onboarding

2 of 10 tasks completed

Before anyone gets this journey

HR builds the journey template first. This is where the build features are used.

1

Describe the journey

Done by: HR specialist

AI Assist suggests a name, a description and at least 10 tasks. Each task arrives as a Manual Task with Worker as performer and Initiator as owner, so change each one.

2

Write the task instructions

Done by: HR specialist

Drafts in English, in an engaging or formal tone. Review each one before you activate the task.

3

Add translations

Done by: HR specialist

Enter translated names, descriptions and task names on the Redwood template page. Ask a fluent speaker to check anything about policy.

4

Assign it, then track it

Done by: HR specialist or line manager

Ask about progress and overdue tasks. It can read journey information but can't edit it.

Then the journey is assigned, and the tasks below begin.

BEFORE THE START DATE

Welcome from the team

Completed
Task type: VideoPerformer: WorkerDue: Before start date

Upload right to work documents

Completed
Task type: DocumentPerformer: WorkerDue: Before start date

Add your bank details

In progress
Task type: Application TaskPerformer: WorkerDue: Before start date

DAY ONE

Ask the onboarding advisor

Not applicable
Task type: AgentPerformer: WorkerDue: Day 1

Prepare for your new starter

Not applicable
Task type: AgentPerformer: Line managerDue: Day 1

Collect your equipment

Not started
Task type: Manual TaskPerformer: WorkerDue: Day 1

FIRST WEEKS

Complete mandatory learning

Not started
Task type: Learn EnrollmentPerformer: WorkerDue: Week 2

First-week check-in

Not started
Task type: Manual TaskPerformer: Line managerDue: Week 1

Confirm onboarding is complete

Not started
Task type: Manual TaskPerformer: HR specialistDue: Week 4

Tell us how it went

Not started
Task type: QuestionnairePerformer: WorkerDue: Week 4

An example journey with typical tasks, for illustration. Not a real configuration.

HELPS THE PERFORMER INSIDE A TASK

Agent task type in guided journeys

My rating: Lower risk

What it does
A task where the performer asks an AI agent questions, answered from the documents in the agent's tool, with sources shown. Two subtypes: RAG agent and workflow agent.
Who uses it
Any performer in a guided journey: workers, line managers and HR specialists.
Since
25A for guided journeys; section level on Redwood pages in 25D; agent as a task type in Journeys in 26C
Setup
Set the profile option ORA_PER_AGENT_TASK_TYPE_GUIDED_JOURNEYS_ENABLED to Y (the default is N). Build the agent and its document tool in AI Agent Studio, add a task with task type Agent to the guided journey, then enable the journey on a Redwood page. Users need the Intelligent Agent Chat privilege.
Good to know
Guided journeys on Redwood pages only. It can't use documents attached to the journey, conversations aren't stored, and it has no completion step, so it doesn't hold up the journey.

Good fit

Repeated questions with answers in current, owned documents.

Not a fit

Answers that live in people's heads, or tasks that must be tracked as done.

Start small

  • Pick one journey and one AI feature, not several at once.
  • Run it for one group first, such as one site or one month's new starters.
  • Measure before you switch it on, so you can show the difference.
  • Then widen it. The AI Agent Studio build path covers the how-to.

How you'll know it's working: Onboarding

  • Fewer "how do I…" emails and calls to HR from new starters.
  • Fewer overdue onboarding tasks.
  • New starters' questionnaire scores, before and after.

What Oracle's notes don't spell out

Things you only notice when you read the notes side by side, or run Journeys day to day.

An independent practitioner guide, not Oracle documentation. Features, names and availability change each release and depend on your licences and setup. Always check Oracle's release notes and your own environment. Last reviewed October 2026.