UI policy vs Data Policy

[Prathmeshdagade]

Can anyone tell me difference between UI policy and Data Policy?, and also Best Practices while defining them

[Harish Bainsla]

Hi @Prathmeshdagade  Check my notes over LinkedIn explain in detail 

https://www.linkedin.com/posts/harish-baisla-8895aa22a_data-policy-activity-7284418127453401090-ETVs...

if my answer helps you mark helpful and accept solution 

[TejasSN_LogicX]

Hi @Prathmeshdagade  ,

UI Policy
-UI Policy is running on Client Side
-It runs every time when the form is Loaded
-Hide Related Lists through Ul Policy
-When we convert UI policy to Data Policy then deactivate Ul Policy
-UI Policy apply for only browser window
-UI Policy Actions are used to fields Read Only, Mandatory, Visible, Clear the field value

Data Policy
-Data Policy is running on Server Side
-On Load is not available in Data Policy-Can't hide Related List
-When converting a Data Policy to a standard Policy, the associated UI Policy record should be deactivated. Note;An alternative is to enable the "Use as UI Policy on client" checkbox.
-Data Policies are applicable across various areas including Import Sets, REST/SOAP Web Services, List Views, and Script-Background.
-Data Policy Rules are used to enforce fields as Mandatory and Read-Only.

aslo refer this link:

https://www.servicenow.com/community/servicenow-ai-platform-articles/difference-between-data-policy-...

[TejasSN_LogicX]

hi @Prathmeshdagade  ,

If you found my solution helpful, please mark it as Helpful or Accepted Solution...!

thanks,

tejas

Email: adhalraotejas1018@gmail.com

LinkedIn: https://www.linkedin.com/in/tejas1018

[PrashantLearnIT]

Hi @Prathmeshdagade ,

Both Data Policies and UI Policies play important roles in enforcing data integrity and controlling field behavior, but they serve slightly different purposes and operate at different levels within the platform.

Data Policies:

• Data Policies primarily focus on enforcing data integrity rules at the database level. They are enforced regardless of how the data is entered or modified, whether it's through the user interface, API, import sets, etc.
• These policies define constraints such as mandatory fields, unique values, field lengths, data types, and other database-level validations.
• Data Policies are typically defined using table constraints, such as field attributes like "Mandatory" or "Unique", or through business rules that run before or after a record is inserted or updated.

UI Policies:

• UI Policies, on the other hand, are designed to control the behavior of form fields and related UI elements based on specified conditions.
• They provide a way to dynamically show or hide fields, make fields mandatory or read-only, set field values, or enable/disable related UI actions based on conditions evaluated on the client-side (browser).
• UI Policies are applied within the user interface (forms) and are evaluated as the form loads or as field values change.
• They are useful for guiding user interactions and ensuring that users enter data correctly or providing context-sensitive behavior within the user interface.

Difference between Data Policies and UI Policies:

• Data Policies take precedence over UI Policies when enforcing database-level constraints like mandatory fields and field-level validation.
• UI Policies can complement Data Policies by controlling other aspects of field behavior based on specified conditions. For example, while Data Policies enforce that a field is mandatory, UI Policies can control when that field becomes mandatory based on certain conditions.
• Together, Data Policies and UI Policies provide a comprehensive framework for enforcing data integrity and guiding user interactions within the ServiceNow platform.