Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Data policy fields

These fields appear on the Data Policy form and related forms.

FieldDescription
Table

The table to which this policy applies.

Note: The list shows only tables and database views that are in the same scope as the data policy.

ApplicationApplication that contains this data policy.
InheritIf selected, applies this data policy to tables that extend the specified table. For example, incident, problem, and change tables all extend the task table, therefore selecting Inherit on a data policy defined for task would apply the data policy to them as well.
Reverse if falseIf selected, the data policy action is reversed when the conditions evaluate to false. For example, when the conditions are true, then actions are taken and when they change to false, the actions are reversed.
ActiveIf selected, the data policy is used.
Short descriptionA short description that identifies the policy.
DescriptionA detailed description of the policy.
Apply to import setsIf selected, the data policy applies to data brought into the system from import sets. This option also applies to web service import sets.
Apply to SOAPIf selected, the data policy applies to data brought into the system from a SOAP web service. Scripted SOAP web services are not affected. This field does not affect data policy interaction with REST web services.
Use as UI Policy on clientIf selected, enforces the data policy on the UI using the UI policy engine.
FieldDescription
TableThe table on which the data policy action applies.
Field nameThe field from the specified table to which the data policy will apply.
Read OnlyHow the data policy affects the read only state of the field. Choices are:- Leave alone - True - False
Mandatory

How the data policy affects the mandatory state of the field. Choices are:

  • Leave alone
  • True
  • False

Note: For tables that are in a different scope than the data policy record, you cannot make a field mandatory.