Lifecycle rule modification

A modification to the filter or operation of a lifecycle rule will not take effect until the next time the lifecycle rule is evaluated.

The lifecycle rule might be actively evaluated by the system when the modification is made. The currently running evaluation continues to use the previous definition of the lifecycle rule until it completes. The workflow might change for the operation while the lifecycle rule is actively being evaluated by the system. The change affects the currently running evaluation at whatever point the change is made. For example, if the lifecycle rule filter identifies 50 Persons and the operation of the lifecycle rule operation is named Recertify. Changing the operation name to CheckPassword does not affect the current iteration of the rule. The change takes place the next time the rule is initiated. However, changing the workflow for the Recertify operation while it is active might result in 25 Persons being processed under the original workflow. The remaining 25 Persons are processed under the new workflow.

Lifecycle rule implementation has a key dependency on having the database contain the scheduling information. Removing, dumping, or otherwise purging the table that contains lifecycle rule scheduling information deactivates the associated lifecycle rules. If these changes occur, we must reconfigure all lifecycle rules and redefine their schedules.

If the operation associated with a lifecycle rule is deleted or renamed, the operation cannot be implemented within the lifecycle rule until the rule is reconfigured. When we add or modify a lifecycle rule for an entity, the updates you make take effect after the cache times out (10 minutes, by default).

Parent topic: Lifecycle rules management