A customer has asked for the following updates to a form: * Make Resolution code mandatory, admin state is changed to Resolved. * Hide major incident…

✔ UI Policies are the best way to implement dynamic form behavior such as making fields

mandatory, hiding/showing fields, and setting values based on conditions.

Breaking Down the Requirements:

Making "Resolution Code" mandatory when "State" is changed to "Resolved"

This requires a UI Policy that:

Condition: State = Resolved

Action: Set "Resolution Code" field to Mandatory = True

Hiding the "Major Incident" checkbox unless the logged-in user has the "Major Incident Manager"

role

This requires another UI Policy that:

Condition: User does NOT have the role major_incident_manager

Action: Hide the field

Why the Other Options Are Incorrect:

Option A (Dictionary Design) ❌

The dictionary defines the structure of fields but does not control dynamic form behavior like field

visibility or conditions.

Option B (Field Limiter) ❌

There is no such feature called "Field Limiter" in ServiceNow.

Option D (UI Design) ❌

"UI Design" is not a recognized concept in ServiceNow. UI Policies are used for form behavior

changes.

Option E (Form Constraint) ❌

There is no "Form Constraint" feature in ServiceNow; ACLs and UI Policies control field behavior

instead.

Reference: ServiceNow UI Policy Documentation (Platform Configuration)