Collapsed Sub-Process

Intro

In BPMN, a collapsed sub‑process is a sub‑process that hides its internal flow. It matters because it keeps diagrams readable while signaling that detailed logic exists.

Key points:

• Represents grouped activities without exposing steps.
• Uses a marker (small square with a plus sign) to distinguish it from a task.
• Common use cases: encapsulating complex approvals (BPM), modular service orchestration (Apps/Tech), staged data handling.
• Pitfall: overusing collapsed nodes can obscure critical paths and exceptions.

Examples:

• “Customer onboarding” shown as a single collapsed sub‑process in the main flow.
• “Calculate premium” encapsulating validation and rating steps.
• “Fulfillment” wrapping pick, pack, and ship activities.

In practice:

Collapse only when detail would clutter the view; keep an expanded version available for analysis and maintenance.

Related terms: sub-process; task; bpmn

FAQs:

Q: How do I indicate a collapsed sub‑process in BPMN?
A: Use the sub‑process shape with a small square plus marker.

Q: When should I collapse versus expand?
A: Collapse to simplify overviews; expand for detailed design and exception handling.

‍