AWRA Help Center

Workflow Automation Module

Workflow Automation lets teams define repeatable operational processes that react to business events, check conditions, run actions, request approvals, create tasks, notify users, call connectors, and preserve a full execution trail.

Navigation Map

The left Automation menu exposes the most important operational pages:

• Workflows: Create, edit, clone, import, export, publish, deprecate, and review workflow definitions.
• Workflow Logs: Review workflow runs, timelines, failures, retries, health metrics, and operational alerts.
• Workflow Tasks: Manage workflow-created operational tasks, assignments, priorities, SLA status, comments, and attachments.
• Exceptions: Triage failed, stuck, risky, noisy, disabled, or misconfigured workflows.
• Scheduler Health: Confirm that background scheduling and recurring automation are running.

Core Model

• Trigger: The event that starts the workflow, such as low stock, overdue invoice, delayed purchase order, expiring quote, manual trigger, webhook trigger, scheduled trigger, or bulk event.
• Condition: A rule that decides whether the workflow is allowed to continue. Example: stock <= 5.
• Action: The step that runs after conditions pass. Examples include create task, send notification, send email, call webhook, create approval, wait, branch, loop, or fallback.
• Version: A saved workflow state used for drafts, publishing, approvals, rollback, export, import, and deprecation.
• Run: One execution attempt, including trigger payload, condition results, actions, retries, failures, duration, and logs.

Condition Builder

Conditions answer: When should this workflow run? The builder is designed around business fields, so users can choose practical rules without needing technical setup details.

• Join: Connects this condition to the previous condition. Use AND when both must pass. Use OR when either can pass.
• Type: Chooses the condition style: field check, related-record check, aggregate rule, risk score, condition group, reusable condition block, business calendar, or decision table.
• Field: The business field being checked, such as stock, status, due date, category, amount, or priority.
• Operator: The comparison, such as equals, not equals, less than, contains, changed, changed from, changed to, is empty, is business day, or is not business day.
• Value: The target value. Example: in stock <= 5, the value is 5.
• Value Type: Tells the system how to read the value: text, number, date/date math, or boolean.

Advanced Condition Logic

Advanced Logic is optional. Use it only when a simple field/operator/value rule is not enough.

• Group: Names a group of related conditions, such as stock_control.
• Parent Group: Nests this group under another group for more complex AND/OR structures.
• Group Operator: Controls whether all conditions in the group must pass or any condition may pass.
• Aggregate: Runs a count, sum, average, min, or max across related records.
• Aggregate Field: The field used by the aggregate, such as quantity, total, amount, or score.
• Metadata JSON: Advanced configuration for reusable condition blocks, business calendars, decision tables, examples, or extra context.
• Negate: Reverses the condition. For example, “is empty” becomes “is not empty.”

Action Builder

Actions answer: What should happen after conditions pass? Common inputs use dropdowns where possible to reduce typing.

• Create Task: Creates an operational task with title, description, task type, queue, priority, assignee, and due date.
• Create Notification: Creates an in-app alert with notification type, message, recipient rules, and duplicate suppression.
• Send Email / SMS / Push: Sends a message using a template key, recipient, message body, recipient rules, and suppression rules.
• Webhook: Sends a payload to an external system using endpoint URL, connector ID, auth headers, retry policy, idempotency key, and payload mapping.
• Update Record: Updates fields on the current or related record. High-risk updates may require publish approval.
• Create Procurement Request / Transfer / RFQ: Starts downstream inventory or procurement workflows from the automation.
• Create Approval: Starts an approval flow with sequential, parallel, first-responder, or consensus behavior.
• Add Comment: Adds an audit/comment note to the target record or workflow context.
• Wait: Delays the next step for a configured number of minutes.
• Branch: Chooses different action paths depending on condition results.
• Loop: Repeats nested actions over a collection or batch of records.
• Fallback: Runs backup steps if earlier actions fail or become unsafe.

Testing Order

1. Navigation: Open Automation menu links: Workflows, Workflow Logs, Workflow Tasks, Exceptions, and Scheduler Health. Confirm active states.
2. Workflow List: Open workflow index, create modal/actions, AI draft modal, import modal, packs, templates, logs, and tasks links.
3. Create Workflow: Select a module and event, add conditions and actions, review the preview, and save.
4. Edit Workflow: Confirm conditions display correctly, add/remove rules, open Advanced Logic, add/remove actions, save, reopen, and verify persistence.
5. Workflow Details: Review rules, actions, versions, test runs, run history, and available action buttons.
6. Dry Run: Run with blank payload and sample JSON. Confirm no real action executes and test history appears.
7. Manual Trigger: Trigger with sample payload. Confirm logs/runs are created and actions execute or fail visibly.
8. Actions: Test create notification, create task, email, push, webhook, update record, procurement request, transfer, RFQ, approval, comment, wait, branch, loop, and fallback.
9. Conditions: Test basic field rules, AND/OR, nested groups, related records, aggregate rules, date math, risk score, condition blocks, business calendar, and decision table behavior.
10. Approval Engine: Test sequential, parallel, first-responder, consensus, delegation/escalation, and audit pack behavior.
11. Tasks and SLA: Confirm tasks appear in Workflow Tasks, priorities and assignees display, comments/attachments work, and overdue/SLA escalation appears.
12. Notifications: Test templates, recipient rules, duplicate suppression, delivery preferences, quiet hours where configured, and message audit trails.
13. Webhooks and Connectors: Test auth headers, retries, payload mapping, idempotency, failure handling, and dead-letter/exception records.
14. Logs and Observability: Check timelines, branches, waits, retries, failures, duration, stuck detection, health dashboard, and retry failed logs.
15. Exceptions: Assign, comment, snooze, escalate, resolve, and track connector exceptions.
16. Versioning: Publish, force approval, approve publish, rollback, export, import, deprecate, and clone.
17. Scheduler Health: Verify heartbeat status, stale/healthy state, readable alert toast, refresh, and scheduler command guidance.
18. Permissions: Test view, create, edit, publish, test, retry, connector-management, and denied-access scenarios.