Appearance
Workflow rule
Platform settingsAutomationWorkflow rulesWorkflow rulePermission:
settings.workflow.viewOpen in Roari ERP (new tab)Also known as
- new workflow rule
- trigger
- event
- condition
- action
- notify role
- send email
- set field
- require approval
- call webhook
A workflow rule has three parts: the Rule itself (name, on or off), When (the event and optional conditions) and Then (the actions, in order). The sentence at the bottom repeats it in plain words, for example When stock below reorder point and warehouse is “EAST”, notify the Purchasing role with “Reorder {item.code}”.
Create a workflow rule
- Go to SettingsWorkflow rules and select New rule.
- Enter the Name and leave Active on.
- Under When, pick the event in This happens.
- Optionally select Add condition to run the rule only in some cases.
- Under Then, set Action 1: pick what to do in Do this and fill in its fields.
- Select Add action for further actions; reorder them with the arrows, remove one with ×.
- Check the sentence and select Create rule. You see Rule “…” created.
| Field | Required | What to enter |
|---|---|---|
| Name | Yes | What the rule does, for example Tell the buyer when stock runs low. Empty: Name the rule. |
| Active | No (default on) | Off keeps the rule without running it. |
| This happens | Yes | The event that starts the rule (list below). Empty: Pick what starts the rule. |
| Conditions | No | Lines of field operator value, all of which must be true: Amount, Currency, Status, Warehouse, Customer, Days overdue, Department. Without conditions, the rule applies every time. |
| Actions | Yes, at least one | See the next table. Missing: Add at least one action.; an action without its main field: Fill this in. |
Events
| Area | Events |
|---|---|
| Sales | Sales order confirmed, Sales order cancelled, Delivery shipped, Customer created |
| Procurement | Purchase order submitted, Purchase order approved, Goods received |
| Finance | Invoice posted, Invoice overdue, Payment received, Period closed |
| Inventory | Stock moved, Stock below reorder point |
| People | Leave requested, Employee joined |
| Service | Service case created, Service SLA breached |
Type in the event field to search. Events of modules your organisation does not use never happen.
Actions
| Do this | Fields | What happens |
|---|---|---|
| Notify in the app | Who (a role, required), Message | Everyone with the role gets a notification. In the message, {number}, {amount} or {item.code} are replaced by the record's values. |
| Send an email | To (required): The customer, The vendor, The person who triggered it, The record owner or A specific address (then Email address); Template: Payment reminder, Order confirmation, Delivery notice, Internal alert | An email goes out with the chosen template. |
| Set a field | Field (required: a field or custom field key on the record, for example dunning_level), Value | The field is set to the value. |
| Require approval | Approver role (required) | Adds an approval step for that role before the record can move on. |
| Call a webhook | Webhook (required) | Sends the event to one of your webhooks. Add the webhook first. |
⚑ Approval
Require approval adds a step on top of what approval rules require. The approvers decide it in Approvals.
Change or delete a rule
- Open the rule from SettingsWorkflow rules. The tag shows Active or Inactive.
- Change it and select Save rule (or Discard).
To delete, select Delete rule and confirm. The rule stops running immediately; actions it already took are not undone.
Examples
| Goal | When | Then |
|---|---|---|
| Warn buyers about low stock | Stock below reorder point | Notify in the app: role Purchasing, Reorder {item.code} |
| Remind customers of overdue invoices | Invoice overdue, Days overdue is at least 15 | Send an email: The customer, Payment reminder |
| Feed the data warehouse | Sales order confirmed | Call a webhook: your BI endpoint |
