Workflow automation: templates, assignments, approvals and monitoring
Design approval templates, attach them to record types and actions, work the approval inbox, delegate, automate follow-up actions and monitor bottlenecks.
On this page
Process at a glance
- Design a templateProcess ownerA template with steps, approvers and routing exists.
- Assign itAdministratorThe template is linked to a record type and scope.
- Bind module actionsAdministratorEach module action has a workflow or proceeds immediately.
- Decide approvalsApproverItems are approved, rejected, returned or delegated.
- Cover absencesApproverA substitute sees your approvals while away.
- Trigger automationAdministratorAn HTTP call, email or integration flow fires when a template resolves.
- MonitorProcess ownerBottlenecks and instance status are reviewed.
#Purpose and scope
Workflow automation is the shared approval engine used by other modules. This chapter explains how to build a template, connect it to the records that need approval, handle the approval inbox and watch running work. Document publishing and many voucher types use it, so a mistake in a template affects every record type that uses it.
#Before you start
- Create the user roles that will approve (see “Roles and access”); approver steps point at a role (approver group).
- Know which record type or module action needs approval. Record types and their codes come from Administration.
- Decide who may edit templates. Anyone who can edit templates, steps and rule sets changes approval routing for the whole company.
#1. Design a template
- Open Templates and create a template with a code, name, description, Active flag and a trigger.
- Choose the trigger: Automatic when a record is submitted, Manual (run on demand) or Scheduled (a condition sweep with an interval of at least 5 minutes, an entity to scan and a JSON condition).
- Choose Design to open the designer. Add steps, drag to reorder, and click a step to edit it. Switch between canvas and linear views.
- Use Copy to duplicate a template, or the play button to run an active template now regardless of its trigger; the new run appears under Instances.
| Setting | What it does |
|---|---|
| Type | Approval, Review, Notification or Condition. A Condition step is a decision node: it is evaluated automatically and has no approver. |
| Approver resolution | Fixed group, the requester’s manager, a role read from a payload field, or a user read from a payload field. It is resolved when the step is entered. |
| Required, Priority | Marks the step required; priority is Low, Medium, High or Critical. |
| Auto-approve (days) | Approves the step automatically after that many days. |
| SLA and escalation | SLA days, escalation days and an escalation group. |
| Notifications and delegation | Notify on entry, notify on overdue, allow delegation, and the entry and overdue email templates. |
| Step owner permissions | Modify record, add, edit or delete documents while the step is current. |
| On rejection | Restart (back to step 1), Go to a chosen step, or End the workflow. |
| Conditional branching | Branches are checked top-down after approval; the first match wins, otherwise the workflow goes to the next step. A branch can go to the next step, a specific step, approve and finish, or reject and finish. Use Match ALL or Match ANY with comparisons such as equals, greater than, contains, in list, between, is empty or matches regex. |
#2. Reuse rules with rule sets
- Open Rule sets and create a rule with a code, name and kind: Condition (boolean tree) or Decision table (rows to outcome).
- Enter the definition as JSON. A branch can then reference the rule set instead of an inline condition.
#3. Version a template
- In the designer choose Publish version and confirm. The current version is archived and new instances use the new version.
- Use Make active on the Versions list to switch back to an earlier version.
#4. Assign templates to records and actions
- In Assignments link a template to a record type (or All Record Types), choose the scope (System, a project group or a project), set Effective From and Active.
- In Action workflows each module action is listed by module with a drop-down of templates. Pick one to bind it, or choose No workflow so the action proceeds immediately. The counter shows how many actions are configured.
#5. Work the approval inbox
- Open My approvals. The tabs are Mine, My Team and, for superusers only, All.
- Add a comment, optionally attach files, then choose Approve, Reject or Return. Return sends the item to the previous step; it is refused on the first step.
- Choose Delegate to hand the current step to another user (the user is required, a comment is optional). Delegation is refused unless the step allows it.
- Delegations sets out-of-office cover: delegator, delegate, effective from and to, reason and Active. While active, the delegate also sees the delegator’s approvals.
| Status | Meaning |
|---|---|
| Pending | Created, not yet on a step |
| In progress | Waiting on the current step |
| Approved | Finished and approved |
| Rejected | Finished and rejected |
| Cancelled | Cancelled |
#6. Automatic follow-up actions
- In Automation actions choose a workflow template, when to fire (Approved, Rejected or Both) and the action type: HTTP call, Email notify or Integration flow.
- Enter the configuration as JSON, for example the URL, method and body template for an HTTP call. The list shows the last run status and time.
#7. Monitor and recover
| Screen | Use |
|---|---|
| Instances | All executions with template, record type, status, current step, who started it and when. |
| Analytics | Where in-progress work is piling up: pending count, average and maximum wait in hours per workflow step. |
| Saga monitor | Cross-module saga state and step history. Only failed or compensating sagas can be retried. |
| Deleted logs | Recover deleted workflow instances. Superusers only. |
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Process owners, administrators and approvers
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:article/guide/workflow-automation
Was this helpful?