Business Flows
The chains that cross module boundaries — procure to pay, quote to cash, hire to retire — counted rather than drawn.
12 steps · 10 questions · 8 screens on this shelf
The screens on this shelf
Workspace
Flow Map
Every step of a business flow with the records currently sitting in it, and every handover with how many of them got across.
Open
Records
Flow Definitions
The chains themselves. A template ships with the platform; a copy belongs to whoever made it.
Open
Records
Flow Steps
What each step is backed by, and what "still in this step" means in the words the table itself uses.
Open
Records
Flow Handovers
The column that carries each link. Without one an edge can be drawn but not counted, and the map says so.
Open
View
Flow Snapshots
The shape of a flow on a given day, so a slide from 8% stalled to 21% is a record rather than a memory.
Open
Records
Test Scenarios
Augmented data for a flow, made by calling the same routes the screens call rather than by inserting rows behind the application’s back.
Open
Records
Scenario Steps
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.
Open
View
Scenario Runs
What each run created, and whether the flow’s handovers moved as a result.
Open
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.