what is the difference between UI policy and data policy?

[SNnewbie2]

I know UI policies can hide or show diplays, or you can make any field mandatory as well. But I dont know what is a data policy? Can I have screenshot of examples of data policy?

[Javed1]

They are applied on the same fields as UI policies would do. Think of it as a superset of UI policy. It can apply to data entered from different sources not, only on the form. 

[nikhilc_45]

need some screenshot of this, how it different to UI policies.

[Deepak Ingale1]

Hi Claudia,

UI policies helps to control behavior of the fields on the UI form like mandatory etc.

Data Policy acts at database level ( server ) and controls the behavior of the field.

For example, suppose that you are configuring a web service that allows users from outside the platform to update problems on the ServiceNow instance. Since these problems are not updated through the instance UI, they are not subject to the UI policies on the problem form. To ensure that the Close notes field is completed before a problem is marked Closed/Resolved, you can create a data policy that applies to server-side imports. Data that does not comply with this data policy produces an error. You can also apply the policy on the browser by selecting the Use as UI Policy on client check box in the data policy record.

http://wiki.servicenow.com/index.php?title=Data_Policy#gsc.tab=0

[adilrathore]

In addition to what UI policies can do i.e., apply to data in the form data policies can apply rules to all data entered into the system - from import sets, web services and so on. So they are applied on the form as well as the imports/web services/data from mobile UI.

[Vishal Ingle4]

• Data policies are similar to UI policies, but UI policies only apply to data entered on a form through the standard browser.
• Data policies can apply rules to all data entered into the system, including data brought in through import sets or web services and data entered through the mobile UI.
• Data Policies, unlike UI Policies, execute on the server.
• You cannot make a field visible or hidden using data policies, because there is no server-side equivalent of a contextually hidden field.
• There is also no Advanced view, no scripted conditions, and no UI or server-side scripting possible through a data policy (except to the extent that scripting is possible inside of any condition builder to make a determination about whether the data policy should run).