Actions Supported in Journeys

Here's some recommended journey categories to use for common employment and recruiting actions.

Action Category to use Scenarios where this is applicable
Hire (HIRE)

Add Contingent Worker (ADD_CWK)

Onboarding Adding a new hire.
Add Pending Worker (ADD_PEN_WKR) Onboarding

Adding external candidates (through any source).

If you use Oracle Recruiting Cloud, when a new hire candidate is progressed to the HR phase, both the actions, Move to HR and Add Pending Worker, are triggered in case of a new hire. Hence, it's recommended that you don't configure a journey based on the Move to HR action for new hire candidates. Instead, configure journeys for new hire candidates based on the action of Add Pending Worker.

This configuration is also helpful in case the candidate gets delayed in the state Error During Processing after they're moved to the HR phase. The journey will be assigned only after the issue gets resolved when the Pending Worker or Work Relationship can be created.

Add Pending Work Relationship (ORA_ADD_PWK_WORK_RELATION) Onboarding

Rehires who already have a terminated work relationship in the application.

If you use Oracle Recruiting Cloud, when a rehire candidate is progressed to the HR phase, both the actions, Move to HR and Add Pending Work Relationship, are triggered in case of a rehire. Hence, it's recommended that you don't configure a journey based on the Move to HR action for rehire candidates. Instead configure journeys for rehire candidates based on the action of Add Pending Work Relationship.

This configuration is also helpful in case the candidate gets delayed in the state Error During Processing after they're moved to the HR phase. The journey will be assigned only after the issue gets resolved when the Pending Worker or Work Relationship can be created.

Global Transfer (GLB_TRANSFER), Global Temporary Assignment (GLB_TEMP_ASG) Onboarding

Movement of existing workers.

If you use Oracle Recruiting Cloud, when an internal candidate gets moved into the HR phase, they arrive in the status HR - Pending Manual Processing and they wait for an HR specialist to process them in the Manage Job Offers work area. The HR specialist will transform the offer's values into the action that was originally selected in the offer, such as global transfer and global temporary assignment. If any journey is configured with these actions, it will get assigned for the internal person only after the HR specialist has submitted this process based upon the offer. If you need your internal candidate to perform journey tasks before their actual internal change becomes effective, then you would need to configure the journey for the action of Move to HR.

Termination (TERMINATION), Resignation (RESIGNATION) Offboarding Exit of workers.
Move to HR (ORA_IRC_ACCEPT_JOB_OFFER) Any applicable category This action is applicable only if you use Oracle Recruiting Cloud.

Although the code for the action Move to HR is ORA_IRC_ACCEPT_JOB_OFFER, this action isn't triggered when the candidate accepts the job offer. After an offer is accepted and before the Move to HR UI action, time may elapse and any custom-configured phases can intervene. So despite it's code which mentions acceptance, this action named Move to HR is triggered when the candidate's job application changes to another state in the HR phase.

Create Offer (EMPL_OFFER_CREATE) Any applicable category

This action is applicable only if you use Oracle Recruiting Cloud. This isn't a recommended option, as there are many reasons that a newly-drafted offer may not result in a newly-hired or newly-transferred worker.

Assigning a journey too early in a candidate's lifecycle isn't effective. External candidates can't access any journeys assigned to them until after they become a pending worker. Internal mobility candidates may or may not end up accepting the offer as the recruiting process continues. So an appropriate time in the recruiting lifecycle to assign a journey is near the end, when the candidate's job application moves into the HR phase.

Journey tasks are assigned to a line manager or area of responsibility only if the journey is being assigned to an employee, contingent worker, and pending worker and not to a nonworker or candidate having an offer.

For more information about journey assignment during the recruitment phase, see the Implementing Recruiting guide on Oracle Help Center.

Change Offer (EMPL_OFFER_CHANGE) Not applicable This action isn't used by any product.