Module guide
Workflow
Reports
Workflow Automation Guide
Use Workflow Automation to understand triggers, conditions, actions, approvals, tasks, SLAs, notifications, testing, versions, and exceptions.
Workflows help AWRA move work through repeatable steps. A workflow can start when a record is created or changed, check conditions, assign tasks, request approval, send notifications, enforce SLAs, and surface exceptions when work is stuck.
Workflow Building Blocks
| Block | Meaning | Example |
|---|---|---|
| Trigger | What starts the workflow. | Purchase request submitted or stock adjustment created. |
| Condition | A rule that decides the next path. | Amount is above a limit or warehouse is high-risk. |
| Action | Something the workflow does. | Assign task, send notification, create approval, or flag exception. |
| Approval | A decision step for an authorized user. | Manager approves request before PO is created. |
| SLA | Expected time for a task or response. | Approver should review within 24 hours. |
| Exception | A blocked, failed, overdue, or unusual workflow state. | Approval overdue or required field missing. |
Typical Workflow Lifecycle
- Define the business process and who owns each step.
- Choose the trigger and conditions.
- Add tasks, approvals, notifications, and escalation rules.
- Test with safe sample records before relying on it for live work.
- Publish or activate the workflow for the intended users or modules.
- Monitor runs, overdue tasks, failed actions, and exceptions.
- Update the workflow carefully when business rules change.
Testing And Versioning
- Test expected approval paths and rejection paths.
- Test missing information, overdue tasks, and escalation behavior.
- Check notifications go to the right people.
- Record what changed when updating an active workflow.
- Tell affected users before changing a workflow they use daily.
Common Workflow Issues
- Workflow is stuck because an approver is missing, inactive, or not assigned.
- Condition sends work down the wrong path because a field is blank or unexpected.
- Notifications are not received because recipient details or preferences are wrong.
- Users do not know whether to approve, reject, or return for correction.
- Workflow was changed without telling the team.
Support tip: Include workflow name, record number, current step, expected step, assigned user, and visible message when reporting a stuck workflow.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.