Choose the model
Predictable flow or adaptive case?
Use BPMN when work follows a designed sequence. Use CMMN when the path depends on evidence, events, and human judgment. Both can call decisions, collect Forms, and retain exact deployment provenance.
| Purpose | BPMN | CMMN |
|---|---|---|
| Running unit | Process instance | Case instance |
| Human work | User or Manual Task | Human Task |
| Business rules | Business Rule Task | Decision Task |
| Progression | Sequence Flows and gateways | Sentries and criteria |
| Nested work | Sub-process or Call Activity | Stage, Case Task, or Process Task |
| Outcome marker | End Event | Milestone and case completion |
BPMN Process User Manual
From Start Event to auditable completion.
Create the process inside its Application, keep field keys and DMN inputs aligned, define a fallback route for unmatched conditions, and launch only the exact activated entry point.
- 1Create an Application with a stable key
- 2Create Forms and DMN decisions inside Application Design
- 3Connect a Start Event, executable activities, gateways, and an End Event
- 4Bind Forms, assignments, decisions, timers, and route conditions
- 5Mark the process as an entry point, validate, version, and deploy
- 6Launch from Work, claim tasks, and verify the completed instance
Start
Optional pinned Start Form and payload-bound idempotency.
Route
Typed FEEL conditions, defaults, joins, timers, and event waits.
Finish
Human work, decision output, completion state, and full history.
CMMN Case User Manual
Let facts and events shape the work.
A case plan has no fixed sequence. Plan items become available or active when sentries and rules are satisfied. Required, blocking, manual-activation, repetition, and auto-complete choices determine how the case settles.
- 1Create the Application and its case data contract
- 2Add Human Tasks, Decision Tasks, Stages, milestones, and listeners
- 3Configure sentries, on-parts, conditions, required rules, and repetition
- 4Set deliberate manual activation and auto-complete behavior
- 5Mark the case as an entry point, validate, version, and deploy
- 6Start from Work and inspect plan items, timers, history, and completion
Sentries
Entry and exit criteria combine events with FEEL if-parts.
Milestones
Record business achievement without creating human work.
Case roles
Map organization groups to performers and authorized events.
Troubleshooting
Start with the exact boundary.
A resource is missing+
Confirm ownership, lifecycle status, permission, and the current Application scope.
A task is not active+
Inspect upstream execution state, sentries or route conditions, manual activation, assignment, and suspension.
A case remains active+
Look for blocking or required plan items, active Stages, pending timers, or deliberate auto-complete settings.
Deployment is blocked+
Follow the element-specific diagnostic, repair the draft, validate again, and create a new immutable version.