Skip to main content

Process Explorer

Operations

For process-mining and operations-excellence tools

A process analyst opens an order-to-cash event log. The map shows how orders really flow; the insights beside it rank the slowest hand-overs and the throughput against the service level; variants, the dotted chart and the case table sit in the dock, all driven by one selection.

Open in StorybookSource

Make it yours

npx shadcn@latest add https://elabs-ai.com/r/process-explorer-page.json

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui template "Process Explorer" (process-explorer-page) to this project — a whole screen copied into the app, built from registry blocks and the @elabs-ai/components-* packages. A process analyst opens an order-to-cash event log. The map shows how orders really flow; the insights beside it rank the slowest hand-overs and the throughput against the service level; variants, the dotted chart and the case table sit in the dock, all driven by one selection.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Make sure the base is in place: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui`), then the packages the template imports: @elabs-ai/components-charts, @elabs-ai/components-data, @elabs-ai/components-flow, @elabs-ai/components-icons, @elabs-ai/components-process, @elabs-ai/components-tokens, @elabs-ai/components-ui. If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
3. Copy the template in with `npx shadcn@latest add https://elabs-ai.com/r/process-explorer-page.json` — it brings its blocks with it; if that url does not answer, copy the folders from https://github.com/mreimitz/elabs-components/tree/main/registry/blocks instead.
4. Mount the page at a route, keep its `WorkspaceShell` frame, and replace the seeded data with ours: [the route, the real data source, and what should change from the template]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

What each view shows

The screens the navigation names, one line each.

Order to cash
The process map, its KPIs and the statistical insights.

Try it on the screen above: Select an activity or a hand-over on the map: the insights, the variants and the case table re-read for it; replay animates every order as a token.

What it is made of

The blocks and packages the template composes — each has its own page. Copy the template and you copy the blocks with it.

7 packages

Use it for

  • Explore a discovered process: map, variants, filters, event log, conformance and case drill-down in one screen