This example shows you the high level steps necessary to create a marriage life event.

1. 1. Use the Life Event Reasons window to define the Marriage life event reason this person change triggers.

   See: Defining General Characteristics of Life Event Reasons

2. 2. Use the Person Changes window to define the person change that triggers this Marriage life event.

   See: Defining Person Changes

3. 3. Use the Person Change Causes Life Event window to associate the person change with the Marriage life event.

   See: Associating a Person Change with a Life Event

4. 4. A FastFormula programmer creates a Marriage rule that specifies how the system detects the Marriage life event when doing so is more complex that steps 2 and 3 can accommodate.

5. 5. Use the Life Event Reasons window to associate this Marriage rule to the Marriage life event.

6. 6. After you define these person changes, every time a database change occurs, a program reads the table you populate using the Person Change Causes Life Event window. If all conditions are met, this program updates the Person in Life Event Reason table.

   This step requires no human intervention.

7. 7. On a periodic basis, the benefits administrator runs the Participation batch process which reads the Person in Life Event Reason table and then determines the impact on the person's eligibility for enrollment, change in enrollment, and de-enrollment.

   See: Participation Batch Processes