How rules and conditions work
Rules decide what each record needs. A process checks every record it fetches against its rules, and each rule that matches tags the record with an outcome, called a Rule Type. Process steps can then act on that outcome.
The three levels
- Rule: has a Rule Type and one or more Condition Sets. Its Match setting decides how the condition sets combine.
- Condition Set: a group of one or more Conditions. Its own Match setting decides how the conditions combine.
- Condition: a single test, made of a Dataset, a Field, an Operator and Value 1 (plus a second value for
range).
Match All and Match Any
- All: everything in the group must be true (AND).
- Any: at least one must be true (OR).
For example, to express (Status is Active AND Amount over 1000) OR (Region is UK AND Priority is High), create a rule with Match set to Any, containing two condition sets each set to All.
How rules are attached to a process
- A process's Rules field picks up to five Rules folders, not individual rules.
- Every rule inside those folders is checked, including rules in sub-folders.
- Rules are checked independently, so one record can match several rules and get several outcomes.
- A rule with no condition sets never matches.
What a match produces
When a rule matches, AutomatedOn records its Rule Type and builds a summary from the messages on the rule, its matching condition sets and its matching conditions. You can include that summary in emails, messages and API requests.