AWRA Help Center

This adds to Workflow Builder and Runs & Troubleshooting.

Industry Packs

On the Workflows page, Industry packs offers five sets: Retail Store, Wholesale & Distribution, Manufacturing, NGO & Donor-Funded and Pharmacy & Healthcare.

• Preview lists what would be created and what would be skipped because you already have it, the thresholds it will use, and anything your plan would refuse.
• Installed workflows arrive as drafts. Nothing runs until you publish it.

Simulation Suites

Give a workflow test cases: a sample record and what you expect to happen — whether each rule passes, which actions run, and which branch is taken. Run the suite and each case passes or fails against what you expected. Branch coverage counts every branch and every default path, so a branch no test reaches is visible before a real record reaches it. Needs the test workflows permission.

Before A Workflow Can Be Published

• It needs an owner and a runbook link, so a failure reaches someone who knows what the workflow is for.
• A backup owner and an SLA in minutes are optional. The backup must be a different person, and the SLA is what breaches are measured against.
• A workflow with a high-risk action needs a policy acknowledgement, and your plan’s limit on actions per workflow applies.

The Workflows list shows each workflow’s owner, so one with nobody responsible is easy to spot.

Runs That Wait

A run paused on a wait step picks up again within about five minutes of its time coming, or as soon as its condition holds. It continues on the version it started under, so editing or republishing the workflow while it waits does not change its remaining steps. New runs use the new version.

Observability

Workflow Observability shows, for the last 14 days by default (up to 90): runs, successes, failures, runs stuck for over 30 minutes, SLA breaches, retries, open dead letters and connector failures. It is on the web, in the API and in the AWRA mobile app, and needs the view workflows permission.

Reviewing AI Suggestions

When AI suggests a change to a workflow, it waits in an AI Suggestions table on that workflow’s page. Accept or reject it, with an optional reason; the decision is kept with the suggestion. Needs the edit workflows permission.

Export And Import Between Workspaces

Exports use version 2 of the workflow file, and imports read versions 1 and 2. When importing into a different workspace, for example from a sandbox to production, supply an environment map that says which user, connector and URL in the file becomes which one here. Roles, warehouses, locations and departments are matched by name. Anything not mapped is matched by email or name, or cleared and listed in the import report. Imported workflows arrive as drafts.