Sub-Process

Intro

A sub‑process is a process embedded within a parent process. In BPMN, it encapsulates detail for clarity, reuse, and modular design.

Key points:

• Improves readability by grouping related steps.
• Supports reuse across different parent processes.
• Common use cases across EA/BPM/Data/App/Tech include shared approval flows, provisioning tasks, and common validations.
• Pitfall: nesting too deeply, making models hard to navigate.

Examples:

• “Provision Access” sub‑process used in onboarding and role changes.
• “Validate Order” sub‑process reused across channels.
• “Run Compliance Checks” sub‑process in finance workflows.

In practice:

Use sub‑processes to encapsulate repeatable chunks; keep hierarchies shallow and well‑named.

Related terms: Parent Process; Process; Call Activity

FAQs:

Q: Are sub‑processes executable on their own?
A: They can be, depending on modeling and tooling.

Q: How do sub‑processes interact with the parent?
A: Via defined inputs/outputs and boundary events.

‍