UI, Navigation and Forms →hardMultiple ChoiceObjective-mapped

SNOW-CSA UI, Navigation and Forms Practice Question

Exhibit

Refer to the exhibit.

UI Policy Record:
Table: incident
Condition: current.state == 2
Actions:
  - Set 'assigned_to' mandatory: true
  - Set 'assignment_group' visible: false
Conditions: On load, On update

Client Script (on change of state):
function onChange(control, oldValue, newValue, isLoading, isTemplate) {
   if (newValue == 2) {
      g_form.setMandatory('assigned_to', true);
   }
}

An incident has state set to 'In Progress' (value 2). When the user loads the form or updates the state, what is the resulting form behavior?

⚠ Common exam trap

ServiceNow often tests the misconception that Client Scripts can override UI Policies, but in reality, UI Policies are applied after Client Scripts on form load and have higher precedence for mandatory and visibility settings.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden

The UI Policy is configured to run when the state is 'In Progress' (value 2). It sets the 'assigned_to' field as mandatory and hides the 'assignment_group' field. Since UI Policies run on the client side when the form loads or the state changes, the resulting behavior is that 'assigned_to' becomes mandatory and 'assignment_group' is hidden. The Client Script does not override the UI Policy because UI Policies have higher priority in enforcing field behavior on the form.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden
Why this is correct
UI Policy sets both actions; Client Script reinforces mandatory.
✗
The 'assigned_to' field is mandatory but the 'assignment_group' field remains visible
Why it's wrong here
UI Policy hides assignment_group, so it is not visible.
✗
The 'assigned_to' field is not mandatory because the Client Script overrides the UI Policy
Why it's wrong here
Both set mandatory to true, so it remains mandatory.
✗
The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden, but the Client Script causes an error
Why it's wrong here
No error, the script runs fine.

Go deeper

SNOW-CSA UI, Navigation and Forms Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question