To define general characteristics of a life event reason:You use the Life Event Reasons window to date effectively define life events and their associated processing.
To define general characteristics of a life event reason:Set your effective date to the appropriate start date for this life event reason.
Enter a Name for this life event reason.
Note: Use a noun for the life event reason name since this life event may appear in communications that you send to participants.
Select a life event reason Type. Choose from a variety of types including:
Absence: Select this type if you want entry and ending of absences to trigger life events.
Checklist: Select this type to trigger HR Checklist events for HR administrators.
Compensation : Select this type if you are defining a life event for a Compensation Workbench plan.
Personal (Advanced Benefits only): Examples include Marriage, Divorce, and Birth.
Scheduled (Advanced Benefits only): Examples include age and length of service changes.
Work (Advanced Benefits only): Examples include Change in Job Assignment, New Hire, and Termination.
iRecruitment: Select this type if you are defining a life event for compensation plans for iRecruitment applicants.
If you selected Absence as the Type, select the Life Event Operation Code: Delete Event, Start Event, or End Event. For example, to set up the life event reason that detects entry of an absence end date, select End Event.
Select an Evaluation Rule to apply to this life event reason. You can use an evaluation rule to define:
How to combine multiple detected life events into one
How to fully detect a life event when its detection is complex
When to eliminate a previously detected life event.
Enter a description of the life event in the Description field.
Select a Life Event Treatment code if you want to limit the detection of seeded temporal life events. Choose from:
Do Not Detect Past Temporal Events: Prevents the detection of past temporal events while the application processes this life event.
Do Not Detect Past or Future Temporal Events: Prevents temporal event detection while the application processes this life event. Use this code with the seeded open and administrative events, or any other explicit events, when you do not want to detect temporal events.
Never Detect This Temporal Life Event: Prevents the automatic detection of a specific temporal event. Set this code for any seeded temporal event, such as Age Change or Length of Service Change, that you do not want to detect, such as for mid-year changes.
Select a Timeliness Evaluation code to indicate how the system processes potential life events that fall outside a time period that you define.
By default, the Timeliness Evaluation field is set to Process Potential Life Event Manually.
Do one of the following:
Enter the number of days after the life event occurred beyond which the system does not process this potential life event in the Timeliness Days field.
By default, Timeliness days is set to 90.
Note: By selecting timeliness evaluation and timeliness days values for user-defined events, you can avoid over writing processed life events during retroactive batch processing.
Select a Timeliness Period if the potential life event should be voided or processed manually because it occurred prior to the current calendar year.
Select a Rule that controls your timeliness definition.
Note: The Timeliness Days and Timeliness Period fields are mutually exclusive.
Select an Occurred Date Determination code that controls if the life event is processed according to the date the event occurred or the date the event was recorded in the system.
Note: By setting the profile option BEN: Comp Objects Display Name Basis in the System Profile Values window, you can choose whether compensation object names display in application windows (both in the professional and Self-Service user interfaces) based on the life event occurred on date or the user's session date. The default profile option value is Session.
If you want to link a life event reason to a self-service process, select a value in the Selectable for Self Service field to indicate in which processes this life event should be available.
All--the life event can be selected in all self-service processes
Add/Update/Delete Family Members--the life event can be selected in Self-Service Benefits when the user adds, updates, or end dates a family member contact
Add/Update Family Members--the life event can be selected in Self-Service Benefits when the user adds or updates a family member contact
Delete Family Members--the life event can be selected in Self-Service Benefits when the user end dates a family member contact
Basic Registration--the life event can be selected in the New Employee Registration process
COBRA Registration--the life event can be selected in the Non-employee Registration process
Basic and COBRA Registration--the life event can be selected in both the New Employee and the Non-Employee Registration processes
Note: In Self-Service Benefits, a user can select life event reasons with a Selectable for Self Service value of All, Add/Update/Delete Family Members, or Delete Family Members as valid reasons for ending a relationship between the primary participant and a dependent or beneficiary.
Note: Do not use the Life Events page in self-service registration if you are the employer of benefits recipients. This page is only for third party benefits providers.
See: Configuring the New Employee and Non-Employee Registration Processes
Select the appropriate value from the Show Primary Care Providers in Self Service to display or hide primary care providers in Self-Service for this life event. By default, the application displays all the primary care providers in Self-Service for this life event.
Select the Check Related Persons Eligibility field if the system generates a related person life event when the primary participant experiences this life event.
If you select the Check Related Persons Eligibility field, complete the Causes Related Person Life Events block as described in step 15
Select the Override field if this life event is the overriding life event in the case of the collision of two or more life events.
Note: When two or more overriding life events collide, no life event is selected as the winner. You use the Potential Life Events form to select the winning life event.
Select the COBRA Qualifying Life Event field if this life event impacts eligibility for US COBRA benefits.
Select the name of the related person life event this life event triggers in the Causes Related Person Life Event field.
Repeat this step for each related person life event that is triggered by this life event.
Save your work.
Next Step