In ServiceNow, UI Policies allow administrators to dynamically control form fields based on conditions without using scripts. With UI Policies, you can change the behavior of a field by making it:
Read-only → The user can view the field but cannot edit it.
Mandatory → The field becomes required, and the user must fill it out before submitting the form.
Hidden → The field is removed from visibility on the form.
Explanation of Each Option:
✅ A. Read-only - Correct
A UI Policy can make a field read-only, meaning users can see the field but cannot modify its value.
Example: A field like Request Number (REQ0001) is typically read-only after submission.
❌ B. Write-only - Incorrect
ServiceNow does not have a "write-only" field setting in UI Policies.
If a field is editable, users can both read and write; if it's hidden or read-only, writing is not possible.
❌ C. Necessary - Incorrect
There is no "Necessary" field state in ServiceNow UI Policies.
If the intent is to make a field required, the correct term is "Mandatory".
✅ D. Mandatory - Correct
UI Policies can make a field mandatory, requiring the user to enter a value before submitting the form.
Example: An Incident Description field might be mandatory before an incident is submitted.
❌ E. Empty - Incorrect
UI Policies cannot directly enforce an "empty" state. However, a default value could be cleared using a client script, but this is not a UI Policy feature.
✅ F. Hidden - Correct
UI Policies can hide a field, making it invisible on the form.
Example: A "Manager Approval" field may be hidden until a certain condition (e.g., request cost > $1000) is met.
Final Answer:
✅ Read-only
✅ Mandatory
✅ Hidden
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs - UI Policies and UI Policy Actions
https://docs.servicenow.com
ServiceNow Learning - Form Configuration & UI Policies
ServiceNow Developer Portal - Controlling Form Behavior with UI Policies