Toolkit — live demo
Self Service Dynamic Flows
Self Service Dynamic Flows lets a business-unit administrator draw a working process — not a diagram of one — and publish it without a single deployment. Flows are data, never code: a versioned JSON graph that an in-app router executes against IBM Business Automation Workflow through a small, fixed set of generic set pieces.
The builder below is the real application, running live in your browser. Nothing is recorded and nothing is sent to a server — drag a step onto the canvas, connect it, open Validate, or step through execution with Debug.
Best viewed on a desktop screen. Open the demo in a new tab →
What you are looking at
Zero-deployment authoring
Creating or changing a flow never touches the BAW server. The graph, the task bindings and the per-step configuration are application data, interpreted at run time.
A registry, not one-off nodes
Every step an administrator can place is a registered task type with a JSON-schema’d configuration contract. New capability means a new entry in the registry — never a special case in the router.
A publish gate you cannot skip
A flow only publishes when the graph is well formed, every step’s configuration satisfies its schema, and every loop is guarded by a decision. Accepted warnings stay visible on the version.
Deterministic, auditable runs
Production runs execute frozen, immutable snapshots. Every run records the flow version, per-step inputs and outputs, timestamps, actor and routing decisions — enough to replay the audit trail without the live system.
Step debugger
Press Debug to advance a token one step at a time, edit the run payload, and inspect the run document before and after each step with written paths highlighted.
Claude as a design-time assistant
The AI Assistant panel drives the same named command surface the UI uses, so it can never do anything the tool surface cannot express. It authors flows at design time and is deliberately absent from the run path.
On the AI assistant: the demo runs its offline deterministic parser by default, so it works with no API key. To see the Claude-powered mode, open AI Assistant → settings and paste your own Anthropic API key — it is kept in your browser’s local storage and is sent only to Anthropic’s API, never to us.
Want this against your own BAW estate?
We adapt the task-type registry to your systems and connect the runtime to your Workflow environment. Tell us which processes are eating your delivery capacity and we will show you what they look like as self-service flows.