Administration Guide › Policy Xpress › How Policy Xpress Works

How Policy Xpress Works

When a trigger (tasks, events, business logic task handlers, and workflow) happens, Policy Xpress is activated and the following steps occur:

1. Policy Xpress checks activation times (Events) to see if there is a policy that should run at that particular time.
2. A list of policies is generated.
3. Policies are ordered based on priority, and Policy Xpress evaluates policies as follows:
   1. All required values (Data) are calculated.
   2. Entry rules are checked to see whether the policy should run.
   3. If the entry rules allow the policy to run, all action rules are checked for matches.
   4. For the matching action rule with the highest priority, the add actions for that rule are executed.
   5. For any action rule that previously matched but no longer matches, remove actions are executed.
4. Once the policy completes, information about the policy that ran is saved on the user object (even if the policy made no changes).
5. Appropriate events related to the action rules are generated. For example, if the policy modifies a user, the ModifyUserEvent is generated.
6. The next policy is loaded.

Note: The previous flow can be changed using action rules. For more information about changing the flow of Policy Xpress, see Flow Control.

More Information:

Flow Control