serviceNow

[satishdbira]

 Difference Between ServiceNow Data policy and UI policy

[Ankith Sharma]

Hi @satishdbira  

To Understand the difference - UI Policy controls how fields behave on a form for end users. It runs on the client side and can make fields mandatory, read-only, or visible/hidden based on conditions.

A Data Policy enforces data validation at the platform level. It runs on the server side and helps maintain data integrity regardless of how the record is created or updated

Example: If an Incident is moved to Closed:

• A UI Policy can make Close Notes mandatory on the form.

• A Data Policy ensures Close Notes is required even when the record is updated through an import or integration.

In short:
UI Policy = Form behavior
Data Policy = Data validation and integrity across all data sources.

If you found this useful, feel free to mark it as Accept as Solution and Helpful. It makes my day (and helps others too 😉).

Regards,
- Ankit
LinkedIn: https://www.linkedin.com/in/sharmaankith/

[Tanushree Maiti]

Hi @satishdbira 

Feature	UI Policy	Data Policy
Execution Layer	Client-side (runs in the user's browser)	Server-side (runs at the database level)
Primary Purpose	Improve user experience by dynamically showing/hiding or enabling/disabling fields.	Ensure data consistency , data integrity across all entry points and mandate fields across the entire platform.
Applicability	Only works when users interact with the platform through the standard Form UI.	Works for all data sources: Forms, Web Services (APIs), Import Sets, and Background Scripts.
Field Visibility	Can show or hide fields on a form.	Cannot hide or show fields; can only make them mandatory or read-only.
Bypassable	Yes. Since it's client-side, users can sometimes bypass it using scripts, imports, or API integrations.	No. Data entering the database must adhere to the policy, making it highly secure and reliable.

Refer: Difference between Data policy and UI policy

https://www.servicenow.com/community/developer-forum/ui-policy-vs-data-policy/td-p/3453864

https://www.servicenow.com/community/itsm-forum/ui-policy-vs-data-policy-understanding-the-differenc...

https://www.servicenow.com/community/developer-forum/ui-policy-vs-data-policy/m-p/2948423

[Its_Azar]

Hi there @satishdbira 

May i now why this question? its pretty much available all over the internet with Realtime examples too.

[Aditya_hublikar]

Hello @satishdbira ,

I have outlined some differences between UI Policy and Data Policy below.

UI Policy

1. UI Policy is client-side and is used for configuration such as Read-only, Mandatory, and Visible fields.

2. We can write scripts in UI Policies for additional modifications.

3. UI Policies are applied only on UI forms.

4. UI Policies do not apply to onCellEdit actions (List view editing).

5. To convert a UI Policy to a Data Policy, the following conditions must be met:
   i) Global checkbox should be checked
   ii) There should be no visibility actions
   iii) Run scripts checkbox should be unchecked

Data Policy

1. In Data Policy, there are only options for Read-only and Mandatory.

2. Data Policies run on the server side, meaning they are enforced when data is inserted or updated in the database (table).

3. There is no option to write scripts in Data Policies.

4. Data Policies are applied even when data is inserted through Import Sets, Mobile UI, Web Services (API), or integrations.

5. For data policy to ui policy conversion there is no any pre-requisit.

(Note - to disble data policy during modifying/creating record using script like gliderecord we need set gr.setUseEngine(false))

If this helps you then mark it as helpful accept as solution.

Regards,

Aditya,