UI, Navigation and Forms →mediumMultiple ChoiceObjective-mapped

SNOW-CSA UI, Navigation and Forms Practice Question

Exhibit

UI Policy: "Make Category Mandatory"
Condition:
  (function() {
    var gr = new GlideRecord('sys_properties');
    gr.addQuery('name', 'myapp.high_priority');
    gr.query();
    if (gr.next()) {
      return gr.getValue('value') == 'true' && g_form.getValue('priority') == '3';
    }
    return false;
  })();
Actions:
  - Set mandatory: category = true

Refer to the exhibit. A user reports that the category field is not becoming mandatory on the incident form even when priority is set to '3' and the system property 'myapp.high_priority' is set to 'true'. What is the most likely cause?

⚠ Common exam trap

Candidates often assume UI Policies automatically re-evaluate on any field change, but ServiceNow tests the distinction between 'Run on load' and 'Run on change' settings, which is a key nuance in UI Policy behavior.

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 UI Policy is set to run on load only, and the priority field change does not trigger re-evaluation.

UI Policies have a 'Run on load' and 'Run on change' setting. By default, UI Policies run only when the form loads. If the policy is set to run on load only, changing the priority field after the form has loaded will not trigger re-evaluation, so the category field will not become mandatory even when the condition is met.

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 system property 'myapp.high_priority' is set to 'false'.
Why it's wrong here
The user confirmed the property is set to 'true'.
✗
The condition script uses 'g_form.getValue' which is not available in a UI Policy condition.
Why it's wrong here
'g_form' is available in client-side UI Policy conditions.
✓
The UI Policy is set to run on load only, and the priority field change does not trigger re-evaluation.
Why this is correct
Correct: Without the priority field in the UI Policy's 'Fields' list, changing priority does not re-trigger the condition.
✗
The user must refresh the page after changing priority for the UI Policy to take effect.
Why it's wrong here
UI Policies can run on change events; refresh is not needed if properly configured.

Go deeper

SNOW-CSA UI, Navigation and Forms Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question