Conditions: Defining When a Rule Passes or Fails

Each condition is made up of three parts: a Domain (the left-hand side), a condition operator (the test), and a value (the right-hand side). The value can be a literal string, number, or date - or it can reference another Domain or a Data Link column by typing @ to open the reference picker.

Multiple conditions within a single rule are combined by a logical operator set at the top of the Conditions section: And (all must be met), Or (at least one must be met), or All True (conditions are skipped and the rule always passes - useful for unconditional action rules). Sub-Conditions can be nested inside a condition to build more complex logic: for example, an And group that contains an Or sub-group.

Adding Conditions

1. In the Business Rule form, locate the Conditions section. Set the top-level logical operator to And, Or, or All True.
2. Click Add Condition. A new condition row appears
3. Select the Domain from the first dropdown. The available condition operators in the second dropdown update automatically based on the Domain's data type
4. Select the condition operator
5. Enter the comparison value in the third field. Type @ to open the reference picker and select another Domain or a Data Link column instead of a literal value, when applicable.
6. To add a Sub-Condition nested under an existing condition, click the Add Sub-Condition button on that condition row. Sub-conditions can have their own logical operator independent of the parent level
7. Repeat for each additional condition

Use Sub-Conditions when you need mixed And/Or logic within a single rule. For example: (Country is 'DE') And ((PostalCode starts with '1') Or (PostalCode starts with '2')). The outer level uses And; the inner sub-condition group uses Or.

Condition Operators by Data Type

The available operators depend on the data type of the Domain selected.

String Conditions

Number Conditions

Date Conditions

Boolean Conditions

Pattern Matching

The Matches pattern and Not Matches pattern operators use a simplified pattern syntax with two special characters:

• . (dot): Matches any single character except a newline.
• * (asterisk): Matches zero or more occurrences of any character.

Pattern matching is not the same as RegEx - the * in HEDDA.IO patterns matches any character (equivalent to .* in RegEx), not just the preceding character. Use Matches Regex for full regular expression control.

Regular Expression Matching

The Matches Regex and Not Matches Regex operators accept standard regular expressions. This is the most powerful condition operator for string validation - use it for structured formats like email addresses, phone numbers, postal codes, or document references.

Referencing Other Domains and Data Links

Any condition value field accepts a reference to another Domain or a Data Link column instead of a literal value. Type @ in the value field to open the reference picker, which lists all Domains in the Knowledge Base and all columns from configured Data Links.

Condition: InvoiceDate is lower than or equal to @DueDate. Both are Domains in the same Knowledge Base. This checks that every invoice was created before or on its due date - without any hardcoded literal value.

Condition: product_name is equal to @DataLink.old_product_name. The right-hand side is a column from a Data Link. When combined with a second condition on the client Domain, this matches rows where the product name matches an entry in the reference table.

If you have any further questions, please feel free to Contact Us.