Create a rule

Updated 19 October 2026 · For back office users

Rules are created in the Rules folder of the back office. You can group them in sub-folders, for example one folder per process.

Before you start

Create the Rule Type the rule will use, and make sure the datasets you want to test are set up.

Create the rule

Open the menu on the Rules folder (or a sub-folder) and create a Rule. Name it after what it checks, such as Under 19 at start.
Pick the Rule Type and Match

In Rule Type, pick the outcome this rule represents. In Match, choose All if every condition set must be true, or Any if one is enough.
Add a condition set

In Condition Sets, add a condition set and choose its Match: All or Any of its conditions.
4
Add conditions
In Conditions, add a condition for each test:
- Dataset: pick the process's own dataset to test the record's own data. Pick a different dataset to look extra information up for each record.
- Field: choose from the list, which is loaded from the dataset. If it says Select a Dataset for this condition before choosing a field., pick the dataset first.
- Operator: how to compare, such as equal or greater_than.
- Value 1: the value to compare with. For range, also fill in Value2.
Add messages

Optionally, fill in the message fields on the rule, condition set and conditions. These explain why a record matched and can be included in emails and messages.
Save, publish and test

Save and publish. Make sure the rule's folder is picked in a process's Rules field, then use the process's Test tab to see which records match.

For OData datasets, the Field list shows the system's own field names, not the friendly As names from the dataset's Select.
Fields you test on the process's own dataset are fetched automatically, so you don't need to add them to the dataset's Select.
For REST datasets, you can type a path that isn't listed, such as courses[*].code.
Value 1 and Value2 can contain $$FieldName$$ to compare against another field on the same record.