Journey Notifications for Pending and Terminated Workers

All email notifications from Cloud HCM are sent to the user account email address. The user account email address is populated from the email address specified as Work in the person record.

Typically, pending workers don't have a corporate email address. Preboarding email notifications are sent only to the email address specified in the user account. So, for pending workers to receive email notifications on their Home email, you can enable either one or both of these profile options:

• ORA_PER_CHECKLIST_NOTIFY_HOME_EMAIL
• ORA_PER_USER_ACCOUNT_NOTIFY_HOME_EMAIL

This table shows the differences between the journey and user account notifications based on different criteria.

Criteria	Journey Notifications	User Account Notifications
What's the profile option code?	ORA_PER_CHECKLIST_NOTIFY_HOME_EMAIL	ORA_PER_USER_ACCOUNT_NOTIFY_HOME_EMAIL
What's the default value of the profile option?	N	N
Which notifications are impacted?	Journey and task notifications	Notifications that are a part of the password lifecycle process. The notifications are related to these events: Forgot username New user created Password expired Password expiry warning Password generated Password reset confirmation Password reset
Which home email is used?	The one marked as H1 in the application. If there's more than one H1 email specified, the application uses the first H1 email returned in the search. It's better to use only one H1 email address for pending workers so that journey notifications are consistently sent to the same home email.	The one marked as H1 in the application. If there's more than one H1 email specified, the application uses the H1 email that is valid as of the system date and was created last in the application.
How is the notification sent?	If you set this site-level profile option to Y, journey email notifications are sent to the home email address of the journey assignee. Additionally, the email notification is sent to their user account email, if it exists. If there is no email of type H1 and no user account email, then no email notification is sent.	If you set this site-level profile option to Y, user account email notifications are sent to the home email address of the user. If there is no email of type H1, then the email notification is sent to the user account email. If there is no user account email as well, then no email notification is sent.
Are there any dependencies?	Yes. The journey and task email notifications are sent to the home email. The notifications are sent if the user meets these conditions on the date the journey and tasks are assigned: Has only an active pending worker work relationship. Has only terminated work relationships. That is, no active work relationships of type employee or contingent worker. In all other cases, the email notification is sent to the user account email. If there is no user account email, then no email notification is sent. A worker can't take any action (mark complete or not applicable) from the notification they receive on the home email. This is because such emails aren't actionable and won't have actionable links.	Yes. The user account email notifications are sent to the home email. The notifications are sent if the user meets these conditions on the system date: Has only an active pending worker work relationship. Has only terminated work relationships. That is, no active work relationships of type employee, contingent worker, or nonworker. In all other cases, the email notification is sent to the user account email. If there is no user account email, then no email notification is sent.