Doubt

[PoojithaVap]

A customer requests the following data quality measures be added:
• Incident numbers should be read only, on all lists and forms, for all users.
• Short Description field should be mandatory, on all records, across all applications, on Insert.
Which type of policy would you use to meet this requirement?
A. Data Quality Policy
B. Dictionary Design Policy
C. UI Data Policy
D. UI Policy
E. Field Criteria Policy
F. Data Policy

[YaswanthKurre]

Hi @PoojithaVap ,

UI Policy (D) is designed to enforce UI-level constraints like making fields read-only or mandatory based on conditions.

If this resolves your question, please mark it as Helpful and Correct. 😊

Thanks,

Yaswanth

[Dr Atul G- LNG · Accepted solution]

Hi @PoojithaVap 

D  - UI Policy

[Hristo Ivanov]

The answer is B, by configuring the dictionary, not sure why they called it "Dictionary Design Policy" though

[Peeyush Thakur]

Correct Policy Type: Data Policy
To meet the customer’s requirements, you would use a Data Policy in ServiceNow.

Why a Data Policy?
1. “Incident numbers should be read‑only, on all lists and forms, for all users.”
Data Policy can enforce read‑only behavior:

• Across all interfaces (UI, mobile, integrations, imports)
• For all users
• On both forms and lists
• 
  This is broader than a UI Policy, which only affects the UI and not data coming through APIs or imports.

2. “Short Description should be mandatory, on all records, across all applications, on Insert.”
A Data Policy is designed exactly for this:

• Enforces mandatory fields at the server level
• Applies to all applications and all record creation methods
• Ensures compliance even if data is inserted via integrations, imports, or scripts
•  

Why not a UI Policy?
UI Policies:

• Only apply to the UI (forms)
• Do not enforce rules on data coming from APIs, imports, or background scripts
• 
  So they wouldn’t satisfy the “all records, across all applications, on Insert” requirement.