UI Policies & Actions Questions

Dynamically change form behavior without scripting using UI Policies. Create custom buttons and menu items with UI Actions for streamlined workflows.

21 total questions2 free questions

Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made

About UI Policies & Actions

UI Policies provide a no-code/low-code approach to dynamically changing form behavior based on conditions. They can make fields mandatory, read-only, or visible/hidden without writing client scripts. UI Actions extend the interface with custom buttons, links, and context menu items that trigger server-side or client-side logic.

Why This Matters for Your Exam

Questions test your understanding of when to use UI Policies vs Client Scripts, how UI Policy conditions work, and how to create effective UI Actions for custom form buttons.

Key Concepts to Master

Understand UI Policy conditions (simple vs scripted), UI Policy actions (mandatory, visible, read-only), and execution order. Know how UI Actions create form buttons, list buttons, and context menu items. Learn when each approach is appropriate.

Exam Tips

UI Policies are preferred over client scripts for simple show/hide and mandatory behavior because they work across all interfaces (desktop, mobile, Service Portal). Remember that UI Policies execute in order and can override each other. Know the difference between client-side and server-side UI Actions.

Practice Questions

21 questions available
1
application

An administrator creating a UI policy on the Incident table wants to record a brief summary of what the policy does, such as "Make Close notes mandatory when Resolved". Which field holds this summary?

AShort description, on the UI policy form
BView, on the UI policy form
CName, on the UI policy form
DField name, in the UI Policy Actions list

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Short description, on the UI policy form

The UI policy form includes a Short description field, documented as a short summary of the UI policy, alongside fields such as Table, Active, Order, and Conditions. The documented form has no separate Name field, so Short description is where the summary goes.

  • Why B is wrong: View selects which form view the policy applies to when Global is cleared. It controls scope, not a description of what the policy does.
  • Why C is wrong: The documented UI policy fields include Table, Active, Short description, Order, and Conditions, with no Name field to hold a summary.
  • Why D is wrong: Field name is on each UI policy action and identifies the field on the table that the action affects, not a summary of the whole policy.
2
application

A child table has a UI policy with Order 500 that shows the Urgency field. Its parent table has a UI policy, inherited by the child table, with the same conditions and Order 100 that hides Urgency. When the conditions are met on the child table's form, what happens?

AUrgency is shown, because 500 is the higher Order value
BUrgency is hidden, because the parent policy runs last
CUrgency is shown, because the child policy overrides the parent
DUrgency is shown, because the parent policy runs first

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: B. Urgency is hidden, because the parent policy runs last

When a child table has a UI policy inherited from its parent table, the child table's UI policy always runs first, regardless of Order. The documentation uses this exact example: the child policy (Order 500) runs first and shows Urgency, then the parent policy (Order 100) runs and hides it, so Urgency ends up hidden.

  • Why A is wrong: Order sets the processing sequence within a table, but for inherited UI policies the child table's policies run first and the base table's policies run after them, regardless of Order. The parent policy runs last and hides Urgency.
  • Why C is wrong: The child policy does not override the parent. It runs first, and the inherited parent policy then runs and hides Urgency.
  • Why D is wrong: The parent policy does not run first. When a child table has an inherited UI policy from its parent table, the child table's UI policy always runs first; the parent policy runs after it and hides Urgency.