UI Policy Execution

Trigger specifies when to execute

• UI Policy Actions and/or Scripts

  specifies what to **execute

  **

• Every field in the record can be

  evaluated even if it is not visible on

  the form (UI16 and UI15)

• UI Policies do not have a Name field

  • Use the Short description field as a

    pseudo name

• Not all UI Policies require scripting

The Advanced view of the UI Policy form is presented baseline.

There is a basic four step strategy to create a new UI Policy:

1. Configure the UI Policy trigger:

   1. Table — table to which the UI Policy applies.
   2. Application — identifies the scope of the UI Policy.
   3. Active — select the checkbox to make the UI Policy active.

   4. Short description — supply a short explanation of what the UI Policy is for. The value in this

      field appears in the debugging information.

   5. Order — the sequence in which UI policies are applied, from lowest to highest. Use when

      there are multiple UI Policies for the same table that may contain conflicting logic.

2. Configure the the When to Apply conditions (when the UI Policy will run).
3. Save (not Submit) the record.
4. Configure the UI Policy Actions (what the UI Policy will do):
   1. Field name - field for which the UI Policy applies an action.
   2. Mandatory - how the UI Policy affects the mandatory state of the field.
   3. Visible — how the UI Policy affects the visible state of the field.
   4. Read Only — how the UI Policy affects the read-only state of the field.

IMPORTANT

Although a UI Policy can evaluate any field in a record regardless if it is visible by the end user, the field specified in a UI Policy Action does need to be present on the form. For Ul11, ensure any field called by a UI Policy exists on the form.