|
|
|
In addition to the defined triggers (policy types), Policy Xpress can also listen to validation on attributes. To do this, use the Policy Xpress logical attribute handler. This allows you to create policies that can run when an on-screen attribute that has been flagged as "validate on change" is updated. However, task-level validation is not triggered when an attribute changes. The only way to use Policy Xpress in those instances is by setting up the Policy Xpress logical attribute handler.
Note: For more information about logical attribute handlers, see the CA Identity Manager Programming Guide for Java.
This functionality can be used for creating dependant drop-down boxes. For example, if there are two drop-down boxes on the screen, Policy Xpress runs when the first drop-down option is selected, then set the values for the second drop-down box based on the option selected in the first. An unlimited number of drop-down boxes and other screen refreshes can be done. This differs from Identity Manager's native functionality by allowing the drop-down options to be populated using any logic, rather than importing an XML file of static options.
Another use is populating other attributes based on the value of one attribute. For example, you can select department, and attributes such as department manager, department number, and HR Dept Code are automatically populated as suggested values. This replaces the need to write logical attribute handler custom code.
To use this functionality, at least one attribute on the screen must be created using the Policy Xpress attribute logical handler.
The handler is also an easy way for creating attributes that exist only during the current session and are not written to the user object (unless a policy copies the values to a physical attribute).