Journey tasks based on days before or after the effective date

Why I picked it

It fixes one of the most common Journeys frustrations: tasks timed from when the journey was assigned, not from the hire or leaving date.

Where it helps

A new starter's laptop request goes out 15 days before their start date, and the welcome email three days before, however early HR set up the journey.

Watch out: A task still can't start before the journey itself is assigned.

From Oracle's note

Journey tasks in Oracle HCM have always been scheduled relative to the date the journey was assigned. That's been a limitation for preboarding and offboarding, where the tasks need to align with the hire, transfer or termination effective date, not the date an HR admin ran a process. Now lets administrators schedule journey tasks relative to the action effective date, so tasks can be triggered a set number of days before or after the actual business event.

• Activate IT devices 15 days before a pending worker's start date
• Send a welcome email 3 days before the hire effective date
• Assign offboarding tasks a fixed number of days before the termination effective date
• Schedule a confidentiality agreement signing 3 days before the job start date
• Request onboarding feedback one week after the hire date

Two new fields on the journey task setup page: Select criteria for task due and Criteria for starting task. Both support a Duration option (number of days before or after the reference date) and an On specific date option. One important constraint: a task can't be assigned before the journey itself is assigned. Existing journey configurations are unaffected. The default remains the journey assignment date unless administrators choose the new fields.

Last reviewed November 2026