You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Self Triggering Life Events Best Practices

edited Sep 5, 2020 12:10AM in Benefits 4 comments

Summary

Self Triggering Life Events Best Practices

Content

We are looking to roll out life events that are triggered due to an employee entered data change in Oracle HCM Cloud.

We currently have employees have the ability to enter their own marital status change, so it only makes sense to have the life event triggered based on this change.

What life events do you have triggered by the employee? Any best practices or lessons learned you can share?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!