Administration

Workflow automation

Event-driven rules: triggers, conditions, actions, dry-run testing, the execution log, and safe rollout.

Rules

Settings → Automations hosts the workflow rule engine: when this happens, if these conditions hold, do that. A rule pairs one trigger with optional conditions (field comparisons on the event) and one or more actions.

Triggers span the operation: stock below threshold / out of stock / expiring / confidence low; movement created / large adjustment; PO sent, closed, or overdue; transfer overdue; count completed / variance exceeded; tool checkout overdue; and scheduled for time-driven rules.

Actions: notify people, create a task, create a count task, create a PO suggestion, require approval, auto-quarantine, or call a webhook.

Test before trusting

Every rule has a dry-run test: feed it a sample event and see whether conditions match and which actions would fire — without side effects. The execution log then records every real and test firing with its outcome, so "did the rule run?" is a lookup, not a debate.

Rules vs alerts

Alerts notify humans about conditions; workflow rules act. When a notification is all you need, prefer an alert — fewer moving parts. Reach for a rule when something should happen: a count opened, a quarantine imposed, a webhook fired. Roll out deliberately: dry-run, then enable with a notify action, then add the consequential actions once the log shows the rule firing exactly when expected. Automation is a plan capability, and the automation-settings permission gates editing.