UI Policy

• UI Policy:

UI policy is an alternative to client scripts for dynamically changing information on a form. Administrators and users with the Personalize Rules [personalize_rules] or the UI policy administrator [ui_policy_admin] role can use UI policies to define custom process flows for tasks. UI policy is the client script.

• UI Policy Fields:–There are 4 Important Options.

1. Global: Option for specifying whether the UI policy applies to all form views. If this check box is cleared, the UI policy isview-specific i.e. UI policy applies to the particular form view.
2. Reverse if False: Option for specifying that the UI policy action should be reversed when the conditions evaluate tofalse. In other words, when the conditions aretrue, actions are taken and when they change back to false, the actions are reversed (undone).
3. Inherit: Option for specifying whether extended tables will inherit this UI policy.
4. OnLoad: Option for specifying that the UI policy behavior should be performed On Load as well as when the form changes.

When possible, consider using a UI policy instead of a client script for these reasons:

• UI policies have an Order field to allow full control over the order in which client-side operations take place.
• UI policies do not require scripting to make a field mandatory, read-only, or visible.

* UI policies execute after client scripts*