Platform › Automation
Business Flows
The chains that cross module boundaries — procure to pay, quote to cash, hire to retire — counted rather than drawn.
In Platform → Automation · 8 screens
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Flow Map | Workspace | Every step of a business flow with the records currently sitting in it, and every handover with how many of them got across. | 0 | 0 | 0 |
| Flow Definitions | List | The chains themselves. A template ships with the platform; a copy belongs to whoever made it. | 7 | 8 | 0 |
| Flow Steps | List | What each step is backed by, and what "still in this step" means in the words the table itself uses. | 8 | 14 | 0 |
| Flow Handovers | List | The column that carries each link. Without one an edge can be drawn but not counted, and the map says so. | 6 | 9 | 0 |
| Flow Snapshots | Read-only list | The shape of a flow on a given day, so a slide from 8% stalled to 21% is a record rather than a memory. | 4 | 0 | 0 |
| Test Scenarios | List | Augmented data for a flow, made by calling the same routes the screens call rather than by inserting rows behind the application’s back. | 7 | 8 | 0 |
| Scenario Steps | List | The call each step makes, with tokens for the parts that vary. {{ref:module/resource}} picks an existing record; {{prev.x}} takes it from the step before. | 6 | 11 | 0 |
| Scenario Runs | Read-only list | What each run created, and whether the flow’s handovers moved as a result. | 9 | 0 | 0 |