Navigating BizOps Engine
This page is a tour of the BizOps Engine web client. Read it before Building Workflows if you are new to the product.
Route Map
| Path | Screen |
|---|---|
/ | Projects list |
/projects/:projectId | Processes for that project |
/projects/:projectId/processes/:processId | Jobs for that process |
/projects/:projectId/processes/:processId/jobs/:jobId | Job details and workflow editor |
/projects/:projectId/processes/:processId/jobs/:jobId/cycles/:cycleId | Cycle / run history detail |
/projects/:projectId/processes/:processId/builder | Process Builder entry point |
The canonical place to edit a job workflow is Job details, which loads the visual workflow editor.
Projects list
The home screen lists every project you can access. Each project card typically shows:
- Name and description
- Criticality and domain
- Process count and status
- Last updated time
From here you create a project or open an existing one to manage its processes.
Processes list
Inside a project you see processes owned by that portfolio. Common fields include:
| Field | Meaning |
|---|---|
| Name / description | What the automation stream does |
| Owner | Responsible operator or team |
| Trigger type | How jobs under the process are expected to start (for example event-based) |
| Health status | High-level process health |
| Job count | How many jobs exist under the process |
| Enabled | Whether the process is active |
Open a process to work with its jobs.
Jobs list
Jobs are the runnable units. The list highlights:
- Job name
- Version and environment
- Runtime status
- Last run result and last execution time
Create a job when you need a new runnable configuration, or open an existing job to edit its workflow.
Job details and workflow editor
Job details is the primary authoring surface. It combines:
| Area | Purpose |
|---|---|
| Job metadata | Version, environment, status, and identity |
| Workflow canvas | Visual graph of steps and edges |
| Step palette | Catalog-driven actions grouped for drag-and-drop |
| Configuration panel | Action parameters, tables, and version selection for the selected step |
| Execution views | Logs and history for recent or selected runs |
Use the palette to add steps, connect edges on the canvas, then configure each step in the side panel before saving.
Cycle history
From a job you can open cycle (run) history to inspect:
- Trigger source
- Start and end times / duration
- Overall result
- Per-step trace with status and optional output payloads
This is the first place to look when a run succeeded, failed, or produced unexpected step output.
Process Builder
Some deployments also expose a Process Builder route or an external process-builder microfrontend. Treat that as a product-specific entry point. Job-level editing inside Job details remains the core workflow authoring path documented here.
Tips for first-time users
- Start with one Project that matches a real business domain.
- Create a Process for a single automation stream (for example incident triage).
- Create a Job for the environment you want to exercise (often a non-production environment first).
- Build a short three-step workflow before adding branching complexity.
- Run once and open cycle history so you learn how traces appear before scaling the graph.