Hierarchy of restrictions

The conditional restrictions that you define are applied hierarchically. For example, if you make an attribute read-only by using a data restriction, you cannot use the Application Designer application to make a field that is bound to the attribute editable.

The restrictions are applied as follows:
  1. Database configurations
  2. Data restrictions
  3. Application configurations

Database configurations take priority over data restrictions and data restrictions take priority over application configurations.

If you define an object as read-only in the database, you cannot use data restrictions or the Application Designer application to make the object editable.

Data restrictions take priority over application configurations made in the Application Designer application. For example, if an attribute is made read-only using a data restriction, you cannot use the Application Designer application to make the attribute editable.

Configurations that are made with data™ restrictions apply everywhere an attribute is used. Application configurations made in Application Designer apply to that application only. For example, if you want to restrict access to a field that is in the header section of multiple tabs, you can put a data restriction on the field every instance of the field has the access restriction. If you configure the restriction in Application Designer, you must apply the restriction to each instance of the field on each tab.