Temporal Event Detection Rules

When you create or edit a life event, you need to decide if you want these temporal life events to be detected in all circumstances, or only in some circumstances. These options help you select an appropriate detection rule.

Detection Rule	Purpose
Do not detect past temporal events	Prevents processing any events that happened in the past. For example, a person has 10 life events processed in the last decade. Depending on when a past temporal event triggers, it might actually back out eight events. That causes a lot of reprocessing work for the benefits administrator. You can select this rule so that only the events during the current period are detected.
Do not detect past or future temporal events	Prevents temporal event detection while the application processes this life event. Use this code with the delivered open and administrative events, or any other explicit events, when you do not want to detect any temporal events. For example, you don’t want to detect any temporal life events during open enrollment, as the Open enrollment process already calculates age and any other time-based criteria anyway.
Never detect this temporal life event	Prevents the automatic detection of a specific temporal event. Set this rule for any delivered temporal event, such as Age Change, or Length of Service Change, that you do not want to detect. For example, if you use this rule in the Age Changed life event, the application processes other life events, such as New Hire, Open, the Age Changed event won't be detected. The event won't be detected even if you run the temporal process. For example, assume that the current date is February 16, 2017. A temporal event occurs, such as length of service or age change, and it becomes an intervening event. A Gain Dependent life event was processed on January 15, 2017. Then, a temporal event triggered on January 14. The intervening events can back out the already-processed event, as events also need to process sequentially in time.

Detection Rule

Purpose

Do not detect past temporal events

Prevents processing any events that happened in the past. For example, a person has 10 life events processed in the last decade. Depending on when a past temporal event triggers, it might actually back out eight events. That causes a lot of reprocessing work for the benefits administrator. You can select this rule so that only the events during the current period are detected.

Do not detect past or future temporal events

Prevents temporal event detection while the application processes this life event. Use this code with the delivered open and administrative events, or any other explicit events, when you do not want to detect any temporal events. For example, you don’t want to detect any temporal life events during open enrollment, as the Open enrollment process already calculates age and any other time-based criteria anyway.

Never detect this temporal life event

Prevents the automatic detection of a specific temporal event. Set this rule for any delivered temporal event, such as Age Change, or Length of Service Change, that you do not want to detect.

For example, if you use this rule in the Age Changed life event, the application processes other life events, such as New Hire, Open, the Age Changed event won't be detected. The event won't be detected even if you run the temporal process.

For example, assume that the current date is February 16, 2017. A temporal event occurs, such as length of service or age change, and it becomes an intervening event. A Gain Dependent life event was processed on January 15, 2017. Then, a temporal event triggered on January 14. The intervening events can back out the already-processed event, as events also need to process sequentially in time.

The difference between the Do not detect past or future temporal events and Never detect this temporal life event rules is that the former can detect the temporal life event only if its recognized on the day the process is run.