|
|
|
Important! Use caution when changing process flows. Using these actions may result in an infinite loop.
By default, policies are sorted by priority and then executed one by one. While this flow is almost always the flow necessary, you can change the flow of the system.
This flow-changing functionality is represented by an action that can be attached to any action rule.
The following four flow-changing subtypes can be used:
Causes all policies after the current policy to be ignored, and Policy Xpress will exit.
Note: Only Policy Xpress exits. If you want to force Identity Manager to stop too, you can use the Exception type action plug-in.
Stops processing the rest of the policies and goes back to the start of the list. This option is useful in cases where the action of one policy causes another policy, which ran before it and did not execute, to now met the entry criteria. That policy is now reevaluated.
Causes a policy to run again. This option is useful for iteration. For example, creating a unique username requires a policy to run over and over again until it finds a unique name.
Should be used rarely and with caution. This action requires selecting an existing policy. If that policy is running at the same time as the current policy (can be before or after) then Policy Xpress jumps to the selected policy. If the new policy is of lower priority, all policies between the current policy and the selected policy are ignored. If the new policy priority is higher, the process goes back.