Build a rule
1 · NAME
The convention is Area: Subject — the name appears in the
audit trail against every row this rule decides, so make it say something.
2 · MATCH — when does it fire?
Want OR? That's a second rule —
duplicate this one for another pattern after inserting.
3 · SET — what does it do?
4 · THE RULE
# fill in the steps aboveappends to the file and runs the whole file through the engine
Your rules file
Checked by the real engine via
/rules/validate — the Workbench
contains no parser of its own, so "valid here" and "valid in a run" are the same fact.
Drafts autosave in this browser. Rules run in file order and the last matching
rule sets the category — put specific rules after general ones.