Processes, interactions and lifecycle
BPMN collaboration / message flow between pools
Two pools with their internal flows and the message flow between them: the classic BPMN collaboration picture.
bpmn.basic@1New DDN source
Why use it?
Make cross-organisation communication explicit without pretending one party controls the other.
When it helps
Whenever a process crosses an organisational boundary and responsibilities must stay visibly separate.
How to read it
- Each pool owns its sequence flow; message flow only connects across pools.
- A message flow inside one pool is a modeling error, not a style choice.
What you need
- The participants
- The messages exchanged, in order
- What each side does independently
Things to check
- Do not draw sequence flow between pools.
- Do not hide a participant whose messages drive your process.
Scope of this diagram
Notation coverage only: no execution, simulation or choreography conformance is claimed by this render.
Work with the converted example
- Open the viewer and select
collaboration. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.