By default, policies are sorted by priority and then evaluated one by one. While this flow almost always applies, you can change the flow, if necessary.
This flow-changing functionality is represented by an action that can be attached to any action rule. Flow-changing functions are located under the System category of the action.
Important! Use caution when changing process flows. Using these actions may result in an infinite loop. For example, if you set 'Redo the current policy' on an action rule with no conditions, the rule will always be true, and the policy will always restart and never exit.
The following four flow-changing functions can be used:
Causes all policies after the current policy to be ignored, and causes Policy Xpress to exit.
Note: Only Policy Xpress exits. If you want to force CA IdentityMinder to stop also, 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 meet 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.
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.
Note: Because the action may cause Policy Xpress to skip certain policies, use this action type with caution.
|
Copyright © 2013 CA.
All rights reserved.
|
|