Lifecycle rule filters and schedules

Because the filter is based on attributes, only the attributes associated with the schema of the entity or entity type are accepted.

There might also be the need to include environment data or external data into the filter. For example, you might need to include the current time or a value obtained from a customer database. The inclusion of this data is achieved by allowing macros to be placed in the filter. For example, a filter checking if a password changed within the last 30 days might read as follows: (erPswdLastChanged>=${system.date - 30}).
Note: Leaving the filter blank returns all entities. Entity relationship macros can be used in lifecycle rule filters.

The interval defined for an event can be constructed from the following options:

Daily
Triggers the lifecycle event every day. After you select this option, click the clock icon to specify a time in the At this time field.
Weekly
Triggers the lifecycle event once a week. After you select this option, select a day from the On this day of the week list, and then click the clock icon to specify a time in the At this time field.
Monthly
Triggers the lifecycle event once a month. After you select this option, select a date from the On this day of the month list, and then click the clock icon to specify a time in the At this time field.
Hourly
Triggers the lifecycle event once an hour. After you select this option, select a time from the At this minute list.
Annually
Triggers the lifecycle event on a specific date and time of the year. After you select this option, select a month from the Month list. Then select a date from the On this day of the month list, and then click the clock icon to specify a time in the At this time field.
During a specific month
Triggers the lifecycle event on a specific month, day, and time. After you select this option, select a month from the Month list. Then select a day from the On this day of the week list, and then click the clock icon to specify a time in the At this time field.
Quarterly
Triggers the lifecycle event four times per year on a specific day and time of the quarter. The reconciliation will occur on the specified day past January 1, April 1, July 1, and October 1. After you select this option, select a day from the On this day list, and then click the clock icon to specify a time in the At this time field.
Semi-Annually
Triggers the lifecycle event two times per year on a specific day and time of the half-year. The reconciliation will occur on the specified day past January 1 and July 1. After you select this option, select a day from the On this day list, and then click the clock icon to specify a time in the At this time field.
Note: More than one schedule can be specified.

A lifecycle rule evaluation schedule contains only a reference to a corresponding rule definition. If a lifecycle rule definition changes before the scheduled evaluation starts, the evaluation uses the updated version of the definition. It does not use the rule definition that was originally scheduled.

In this example, a lifecycle rule is created. It checks once a day for accounts with no password changes in 90 days. An email notification is sent to owners of accounts that meet the lifecycle rule search criteria, informing them that they must change their passwords.

First, a lifecycle operation named remindToChangePassword is constructed for the Account entity type. It is defined as an instance-based (not static) operation, and so it has the account object itself as an input parameter. The business logic of the operation is defined with one work order activity that sends the reminder message to the owner of the account. It includes the user ID of the account in the message.

A lifecycle rule is then constructed for the Account Entity Type named passwordExpiration that references the remindToChangePassword operation. It has an event with an evaluation interval of daily at 12:00 A.M.. It also has the following filter: (&(erAccountStatus=0)(erPswdLastChanged<=${system.date - 90})).