A customer has asked for the following updates to a form: * Make Resolution code mandatory, admin state is changed to Resolved. * Hide major incident check box, unless logged in user has Major incident Manager role What type of rules (s) would you use to implement this requirement?

UI Policies are client-side rules used to dynamically change the behavior and visibility of fields on a form without scripting, although scripting can be used for more complex logic. The first requirement—making "Resolution code" mandatory when the "State" is "Resolved"—is a standard condition-based UI Policy. The second requirement—hiding a field unless the user has a specific role—can be achieved using the "Run scripts" option within a UI Policy. The script would use guser.hasRole() to check the user's role and gform.setVisible() to control the field's visibility, making UI Policy the correct tool for both requirements.

A. Dictionary Design: This defines a field's attributes globally (e.g., always mandatory), not conditionally based on form values or user roles.
B. Field Limiter: This is not a standard, recognized term for a type of rule or configuration element within the ServiceNow platform.
D. UI Design: This refers to the general practice of designing a user interface, not a specific type of configurable rule in ServiceNow.
E. Form Constraint: This is not a standard, recognized term for a type of rule or configuration element within the ServiceNow platform. ---

1. ServiceNow Product Documentation: "UI policies". This document states, "UI policies dynamically change the behavior of information on a form... You can use UI policies to set fields on a form to mandatory, visible, or read-only." It also details the use of conditions and scripts for advanced logic. Platform Administration > User interface > UI policies.

2. ServiceNow Developer Site: "Client-Side Scripting" Learning Module, "UI Policies" section. This module explains, "UI Policies can have scripts that execute on the client. Use UI Policy scripts to create complex conditional checks or to take actions other than setting field attributes (mandatory, visible, read-only)." This directly supports using UI Policies for role-based visibility checks.

3. ServiceNow Now Learning: "ServiceNow Fundamentals" Courseware. In the module on "User Interface & Navigation," the section on "Form Configuration" introduces UI Policies as a primary method to control field visibility and mandatory status based on defined conditions.