Process contracts (governance)¶
Process contracts are the same process definitions you maintain in Processes; this surface is the governance registry — lifecycle, owner, category, version, linked products — not the canvas editor.
When to choose this¶
Use Process contracts when you need to:
- Review published vs draft definitions across the organisation
- Check ownership (team) and category before an audit
- See latest version and last modification at a glance
- Jump to the builder only when the graph must change
Create or import processes from Processes under Automation — there is no Create here.
Setup¶
Same as Processes: categories, domains/departments/teams as needed, roles bpm.viewer / bpm.editor.
What users see¶
| Surface | Path | Content |
|---|---|---|
| List | /contracts/process |
KPIs, filters, governance-oriented columns (owner, lifecycle, category, version, last modified, linked product) |
| Detail | /contracts/process/{id} |
Read-only lifecycle and history panels, version list with link to builder, Edit in Processes |
How it works¶
- Lists reuse the same BPM definitions API as the builder.
- Actions open
/processes/{id}for the visual editor.
Limitations¶
- No canvas editing here; active versions remain read-only until a new version is created in the builder (see Processes).
Audit & compliance¶
| Question | Where |
|---|---|
| Who changed the definition? | Detail metadata; audit log filtered by bpm |
| Which version was live? | Versions tab on detail |
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Empty table | No definitions | Create under Processes |
| Need to edit graph | Governance is read-only | Edit in Processes |
See also¶
- Processes — builder
- Data Products — wrapping a process for contract linkage
- Flows — executable automation