InServiceNow,UI Policiesallow administrators todynamically control form fieldsbased on conditions without using scripts. With UI Policies, you can change thebehaviorof a field by making it:
Read-only→ The user canviewthe field butcannot edit it.
Mandatory→ The field becomesrequired, and the usermustfill it out before submitting the form.
Hidden→ The field isremoved from visibilityon the form.
Explanation of Each Option:A. Read-only–Correct
A UI Policy can make a fieldread-only, meaning users canseethe field butcannot modifyits value.
Example: A field likeRequest Number (REQ0001)is typicallyread-onlyafter submission.
B. Write-only–Incorrect
ServiceNowdoes nothave a "write-only" field setting in UI Policies.
If a field iseditable, users canboth read and write; if it’s hidden or read-only, writing is not possible.
C. Necessary–Incorrect
There isno "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 fieldmandatory, requiring the user toenter a valuebefore submitting the form.
Example: AnIncident Descriptionfield might be mandatory before an incident is submitted.
E. Empty–Incorrect
UI Policiescannot directly enforce an "empty" state. However, adefault valuecould be cleared using aclient script, but this isnot a UI Policy feature.
F. Hidden–Correct
UI Policies canhide a field, making it invisible on the form.
Example: A"Manager Approval"field may be hiddenuntila certain condition (e.g., request cost > $1000) is met.
Final Answer:Read-only
Mandatory
Hidden
ServiceNow Docs – UI Policies and UI Policy Actionshttps://docs.servicenow.com
ServiceNow Learning – Form Configuration & UI Policies
ServiceNow Developer Portal – Controlling Form Behavior with UI Policies
References from Certified System Administrator (CSA) Documentation:
