The Validation feature allows you to validate provisioning objects on the local file system before you deploy. The validation runs Designer’s project checker and displays the results in the Project Checker view.
For directory abstraction layer objects, Designer:
Verifies that the XML is well-formed and complies with the schema that defines the elements needed for entities, attributes, lists, relationships, and so on.
Checks every entity to ensure that references to other entities and global lists are valid.
For example, when validating an entity and its attributes, the validator checks that all references to other entities via the Edit Entity, DNLookup, and Detail Entity references exist.
Ensures that every entity has at least one attribute defined.
Ensures that every local and global list contains at least one item.
For Provisioning Request Definitions, Designer:
Validates that every Provisioning Request Definition has at least one request form and one approval form.
Ensures that the Condition Activity has both an outbound true flow path and an outbound false flow path.
Ensures that the Entitlement Activity Data Item Mapping of DirXML-Entitlement-DN is valid.
Ensures that the Final Timeout Action property (for User Activities) has a matching flow path link leading from the activity. For example, if Final Timeout Action=denied, there must be a denied link.
For Branch and Merge activities, ensures that a workflow has an equal number of Branch and Merge activities. It also ensures that all paths descending from a Branch activity merge into one Merge activity, that all merge activities have a branch activity, and that all Merge activities have a branch-activity-id attribute.
Ensures that static list keys contain the correct data for the decimal data type.
For Provisioning Team objects, Designer:
Validates that managers and members have been defined for the team.
Validates that team requests are specified for the team.
If the request scope is Categories, it validates that the team request actually references a category.
For the User Application driver locales, Designer ensures that the locales contain descriptions and display names. You can turn off the validation of display names for each locale by setting a preference. For more information, see Section 2.3, Setting Provisioning View Preferences.
To validate objects from the:
Provisioning view, right-click a node and click.
Directory abstraction layer editor, clickfrom the editor’s toolbar, or select from Designer’s menu.
Provisioning request definition editor, selectfrom Designer’s menu.
Provisioning team editor, selectfrom Designer’s menu.
NOTE:Validation does not check the Identity Vault for the existence of any object.