Create a Data Partition Constraint

Administration › Security and Role Management › Data Partitions › Create a Data Partition Constraint

Create a Data Partition Constraint

Data partition constraints restrict the database record access for users that are assigned to the data partition.

Follow these steps:

Select Security and Role Management, Data Partitions, Data Partition Constraints on the Administration tab.
The Data Partition Constraints List page opens.
Click Create New.
The Create New Data Partition Constraint page opens.
Complete the data partition constraint fields, as appropriate.
Complete the information in the tabs, as appropriate:

Constraint

Specifies the criteria that controls the records in the table and can be viewed, created, updated, or deleted by a user that is assigned to the data partition. For example, you can specify that users can only update issues that are assigned to them. When a user in the data partition requests a record that does not match the condition then the record is read-only.

Limit: 4000 bytes

SQL Translation

Displays the constraint definition in SQL format. The condition that you entered on the Constraint tab is validated, and the underlying SQL WHERE clause is built. This translation is displayed on the SQL Translation tab for the verification.
Click Save.
The constraint is saved and added to the data partition.

Example: Create a Data Partition Constraint for CAB Assignments

You can create a data partition constraint that lets users update only change orders that are assigned to a CAB to which the logged in user belongs.

To create a data partition constraint for CAB change order user assignments, assign the following constraint values for a Change_Request controlled table in a data partition:

Constraint type: Pre-Update
Constraint specification: cab.[group]group_list.member IN (@root.id)

The logged in user can only update change orders that are assigned to a CAB to which the user belongs.