UI Policy Trigger — When to Apply

• UI Policies execute based on evaluation of the Conditions
  • Build conditions with the Condition Builder rather than scripting for better performance
  • If left blank the UI Policy logic always executes
• The Condition Builder is not unique to UI Policies, the feature is used across the platform.
• Global — the UI Policy applies to all form views if selected.

• View — name of the specific form view to which the UI Policies applies. Visible when the Global field

  is not selected. If the Global field is not selected and the View field is left blank, the script applies

  the default view.

• Reverse if false — UI Policy actions are reversed and the Execute if false script executed when its UI

  Policy conditions evaluate to false.

• On load — execute on form load and form change.

• Inherit — apply this script to any extended tables when selected.

Conditions are only re-evaluated if a user manually changes a field on the form; if the change is made by the system it will not be rechecked. Use Data Policies, which are not scriptable, to manage the mandatory and read-only state of fields for records not changed on a form.