Plain English or the structured editor
Write ‘Hold ACME orders that have no purchase-order reference’ and check the proposed rule, or choose the decision, the outcome and the condition directly. Either way the rule is the same and goes through the same checks.
What a rule can choose
Each product declares the facts a rule may read and the outcomes it may choose, such as a destination, a priority or a hold. A rule picks from those approved outcomes; it cannot invent a new action.
Checks before saving
Automation checks each rule for unknown fields, mismatched types and units, overlapping or unreachable rules and missing defaults, and says plainly what it has and has not been able to check.
Examples instead of code
Instead of reading code, check examples: this order is held, that one is not; 1,200 mm needs no support, 1,201 mm does. The examples become the rule’s acceptance tests.
What SmartFACT Automation does not do
- Run scripts, SQL, regular expressions or free-text conditions in production rules.
Common questions
Do we need a developer?
No. The people who own the decision write and check the rules. SmartFACT sets up the first policy with you.
Can we write any rule we like?
Rules use the facts and outcomes each product declares. A requirement the products cannot carry out is shown as a gap rather than turned into a guess.
Related pages
Trials are by invitation and start with one agreed workflow. Scope and arrangements are agreed with you before access.
