AnsweredAssumed Answered

creating dependant drop-down lists with Policy Xpress

Question asked by FBruno on Aug 17, 2012
Latest reply on Dec 21, 2012 by Razvan_Dumitriu
Books online says:

"On-Screen Attribute Validation
In addition to the defined triggers (policy types), Policy Xpress can also listen to validation on attributes. This allows you to create policies that can run when an on-screen attribute that has been flagged as “validate on change” is updated.

This functionality can be used for creating dependant drop-down lists. For example, if there are two drop-down lists on the screen, Policy Xpress runs when the first drop-down option is selected, then sets the values for the second drop-down list based on the option selected in the first. An unlimited number of drop-down lists and other screen refreshes can be done. This differs from Select Box Data 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, when an administrator selects a department, Policy Xpress can automatically populate other attributes, such as department manager, department number, and HR Dept Code. This replaces the need to write logical attribute handler custom code.

To configure validation with a Policy Xpress policy
In the User Console, modify a task's profile screen and select the field you want to listen for.
Access the field's properties and select Yes in the drop-down list for Validate on Change.
In Policy Xpress, create a policy of type 'UI' .
Under the Run at Events tab, select the State 'Validate on Change' and the task you modified in Step 1."

Has anyone succefully configure a policy xpress to use "dependant drop-down lists"?

is There any DOC on how to configure it?.

THX

Outcomes