Expanded Sub-Process

Intro

In BPMN, an expanded sub‑process is a sub‑process that shows its internal flow within the parent process. It matters because it provides detail without switching context to a separate diagram.

Key points:

• Displays contained events, activities, and gateways inside a larger rounded rectangle.
• Improves transparency for reviewers and implementers.
• Common use cases: detailed approvals (BPM), orchestration segments (Apps/Tech), data handling stages.
• Pitfall: overcrowding the expanded area, reducing readability.

Examples:

• Showing all steps of “Verify customer” within the main onboarding flow.
• Exposing exception handlers inside “Process payment.”
• Detailing “Fulfillment” with pick/pack/ship activities.

In practice:

Expand only when detail aids decision‑making; keep a clean overview and provide a collapsed version for high‑level views.

Related terms: sub-process; activity; bpmn

FAQs:

Q: How is an expanded sub‑process shown?
A: As an enlarged rounded rectangle containing its flow objects.

Q: When should I expand versus collapse?
A: Expand for analysis and review; collapse for overview diagrams.

‍