UI Policies
Client-side form behaviour rules. UI Policies let you dynamically show, hide, make mandatory, or make read-only form fields based on the values of other fields.
How UI Policies work
Policies evaluate in the browser when a form loads and whenever field values change. They run in two groups:
- General policies — fire on every form load and save attempt
- Field policies — fire when a specific
trigger_fieldchanges
Policy configuration
| Property | Description |
|---|---|
| Trigger kind | general (always) or field (when trigger_field changes) |
| Trigger field | The field that triggers re-evaluation (field policies only) |
| EQL filter | When the policy applies. Evaluated against current form values |
| Affected fields | Map of {field_name: {read_only?, hidden?, mandatory?}} |
| Sort order | Policies evaluate in ascending order |
Example: show resolution field only for closed tickets
- Trigger kind:
field, Trigger field:status - Filter:
status:closed - Affected fields:
resolution→{hidden: false}
Example: make contract URL mandatory for enterprise accounts
- Trigger kind:
general - Filter:
account_type:enterprise - Affected fields:
contract_url→{mandatory: true}
UI Policies only affect the form display. They do NOT validate
data server-side. Use Business Rules for mandatory data enforcement.
data server-side. Use Business Rules for mandatory data enforcement.