Connection conditions for Tables object

Connection conditions let you define server-side rules that control the data available to an app. You can use conditions to restrict the records returned or deleted by a Tables object, or enforce field values when records are created or updated.

Note: Connection conditions work together with object and field permissions. Permissions determine which operations a user can perform on a Tables object. Conditions provide additional rules that determine which records are returned or affected by those operations, or which field values are enforced.

Jump to:

Access the Conditions page

You can access the Conditions page from:

  1. Go to Tables.

  2. Open the table for which you want to configure connection conditions. You can use one of the following options:

    • Select the table from the tables list.

    • Click next to the table and select Open.

  3. On the toolbar, click Permissions, and select App conditions.

    The Conditions page opens.

  1. Go to Apps.

  2. Select an app.

    The App Designer opens.

    Note: If you do not already have an app, create one. For more information, see Create and customize apps.

  3. In the Elements panel, select Permissions.

  4. Open the permission set for which you want to configure connection conditions. You can use one of the following options:

    • Select the permission set from the permissions list.

    • Click next to the permission set and select Configure.

  5. Under Connection access, turn on the toggle for Tables, and click Edit.

  6. In the Objects panel on the left, select an object.

  7. Under Condition permissions, click Configure conditions.

    The Conditions page opens.

Create a condition

  1. On the Conditions page, click Create a condition.

  2. Type a Condition name that describes the purpose of the condition.

  3. Select the Field that the condition applies to.

  4. Select the Value source that determines the value used by the condition. The following options are available:

    • Single specified value: The field value must match the specified value. When you select this option, the Value field appears. Type the value that the condition must match.

    • Nintex Apps user attribute: The field value must match an attribute of the Nintex Apps user accessing the app. When you select this option, the User attribute field appears. Select the user attribute to use as the condition value.

    • Session variable: The field value must match the value of a session variable. When you select this option, the Session variable field appears. Select the session variable to use as the condition value. For more information, see User management.

    • None - blank value: The field value must be blank.

  5. Under Enforce on, select when to apply the condition. The following options are available:

    • Query: When the app queries the connection, Nintex Apps returns only data that matches the condition. Use this option to filter records.

    • Insert: When the app creates a new record, Nintex Apps sets the specified field to the condition value. This option is particularly useful for Created By <User> fields.

    • Update: When an end user updates an existing record, Nintex Apps enforces the condition value. If the user changes or removes the field value, Nintex Apps replaces the user's value with the condition value.

    • Delete: When an end user attempts to delete an existing record, Nintex Apps allows the deletion only when the record meets the condition. Use this option to restrict which records users can delete.

  6. Click Save.

Manage connection conditions

  1. On the Conditions page, click Add condition.

  2. Configure the condition as required. For more information about the condition settings, see Create a condition.

  3. Click Save.

  1. On the Conditions page, next to the condition you want to delete, click Delete.

  2. To confirm deletion, click Delete.

  1. On the Conditions page, next to the condition you want to edit, click Edit.

  2. Edit the condition as required. For more information about the condition settings, see Create a condition.

  3. Click Save.

Use conditions with app permissions

Connection conditions and object permissions serve different purposes and work together. For more information, see Configure app-level Create, Read, Update, and Delete (CRUD) permissions for objects.

Object permissions determine which operations a user can perform on a Tables object. Connection conditions add rules to those operations. For example, a user can have Read permission for a Tables object while a Query condition limits the records returned to that user.