Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
How to force self-reported life events into manual status
Summary:
For this year's Open Enrollment event (enrollment window from 11/1/24 - 11/15/25, closed on 11/16/24, elections take effect on 1/1/25), we need to prevent any self-reported life events (from 11/16/24 until 1/1/25) from backing out this year's closed Open Enrollment event.
Here is the list of self-reportable life events:
Desired Behavior (here is an example of what we want to happen, between 11/16/24 and 1/1/25):
- Employee accesses the Benefits page:
- Employee then clicks on Report a Life Event and accesses the Report a Life Event page:
- Employee selects a life event (Add Child due to Birth/Adoption/Legal Guardianship), enters a date (12/9/24 - keep in mind that the date used in this example is indeed within the timeframe (11/16/24 - 1/1/25) mentioned in the summary), and clicks Continue.
Tagged:
0