Rules are executed in the order in which they are listed in the rule set. Identity Management executes each rule in a rule set separately, and transparently continues to each subsequent rule in the rule set unless a rule fails.
Because validation rules are executed in a predictable order, you can implement rules whose actions are dependent upon the outcome of previous rules, as in the following examples:
Perform the following basic operations when defining custom validation rules:
|
|
Inline |
By Reference |
|---|---|---|
|
Regular Expression |
directory.xml or task screen |
— |
|
JavaScript |
directory.xml or task screen |
Source file referenced in directory.xml |
|
Java |
— |
Class file referenced in directory.xml or task screen |
Task-level validation has task-specific scope—that is, it can be used only in the context of the particular task screen where it is assigned.
Directory-level validation has global scope. This means that directory-level validation can be used on any field configured with the managed object attribute, regardless of the task screen that contains the field, and regardless of the Identity Management environment that includes the task screen.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|