UI / Data Policy

A User Interface {UI) Policy is a rule that is applied to a form to dynamically change form information or the form itself

Once a UI Policy is saved, UI Policy Actions determine what happens on the form, including:

• Setting a field as mandatory - requiring a value in order to save the record
• Setting a field as hidden - no longer displaying a field on the form
• Setting a field as read-only- preventing a user from updating its value

UI Policies execute on the client side

A Data Policy is a rule that enforces data consistency by setting fields as mandatory and/or read-only

Data Policy controls are similar to UI Policies but UI Policies are only enforced on data entered into a form (passing through the UI)

Data Policies are applied to all data entered into the platform; form {UI), Import Sets, or Web Services

A Data Policy execute on the server side but can also run as a UI Policy on the client side

To immediately implement updates and changes to forms and lists, you can use UI Policies which allow you to add sophisticated controls without having to write scripts and define custom process flows for tasks.

Use a UI Policy to set fields on a form to

• Mandatory or Optional
• Hidden or Visible
• Read-only or Editable

NOTE: To apply a UI Policy to all views, set the Global setting to true.

A Data Policy enforces requirements on field and record data when the data is imported into ServiceNow or when the data in an Import Set is submitted through an external system. Data Policies can be opted out for Web Services and Import Sets. A Data Policy is used to set mandatory and read-only states on form fields. Data Policies can be used on lists to make a field read-only; the field will appear to be editable, but the update will fail.

The purpose of a Data Policy is to standardize the same data across ServiceNow applications.

NOTE: UI and Data Policies are not about security, they are about managing the user experience.