![\"Diagram](\"https:\/\/bpmn.visual-paradigm.com\/wp-content\/uploads\/sites\/8\/2026\/09\/img_6a96488c1e7aa.png\" "\\"Diagram")
<\/p>\n<\/p>\n
In the complex world of Business Process Model and Notation (BPMN), clarity is king. When processes grow too intricate to manage in a single flow, we need a way to organize complexity without losing sight of the big picture. This is where the Sub-Process<\/strong> comes into play. It is the primary mechanism for hierarchical process development, allowing us to encapsulate logic into reusable, manageable components.<\/p>\n This tutorial explores the mechanics of Sub-Processes, distinguishes between their visual states, and explains how to model them effectively using tools like Visual Paradigm.<\/p>\n At its core, a Sub-Process is a Compound Activity<\/strong>. It is not merely a simple task like “Send Email” or “Approve Document.” Instead, it acts as a container\u2014a boundary that holds an entire miniature process inside the main parent process.<\/p>\n Think of it as a black box that you can open when necessary. Inside this boundary, you can find:<\/p>\n These internal elements function independently of the main flow but ultimately contribute to the parent process’s overall goal. For instance, a “Credit Check” process might be a sub-process containing the detailed steps of receiving a report, approval, and transaction history checks.<\/p>\n One of the most powerful features of BPMN is the ability to toggle between different levels of detail. This is achieved through two distinct visual states:<\/p>\n The Collapsed Sub-Process<\/strong> is the default view. It appears as a simple rectangle with the name of the activity. Crucially, it features a small Plus (+) sign<\/strong> at the bottom center. This visual cue indicates “hidden lower-level detail.” It tells the reader, “There is more to this process, but for now, we are looking at the high level.”<\/p>\n When you need to understand the logic, you Expand<\/strong> the sub-process. This reveals the internal architecture. As shown in the diagram, the expanded view displays:<\/p>\n This transition allows for a seamless workflow: you can view the “Macro” view of the enterprise process, and drill down into the “Micro” view of specific operations as needed.<\/p>\n Beyond visual states, Sub-Processes differ in how they relate to the rest of the diagram. Understanding the distinction between Embedded<\/strong> and Independent<\/strong> (Reusable) sub-processes is critical for system architecture.<\/p>\n An Embedded Sub-Process is strictly local to the diagram it is drawn in. It cannot be called from other diagrams. It is a “One-Off” logic block that is tightly bound to its parent. In Visual Paradigm, this is often represented by the standard sub-process icon.<\/p>\n An Independent Sub-Process<\/strong> (often called a Reusable Sub-Process) is global. It is defined once and can be referenced (called) by multiple different parent processes. It acts like a function in programming.<\/p>\n Visually, these are often denoted by a specific icon (sometimes a gear or specific symbol depending on the tool) and are used when you have a standard procedure, such as “Standard Text” or “Credit Check,” that needs to be applied across multiple different workflows.<\/p>\n To see this in action, let us walk through the “Credit Check” example found in the source material. This workflow demonstrates how a sub-process manages logic:<\/p>\n By encapsulating this entire sequence into a single “Collapsed” box in the parent process, the main diagram remains clean, readable, and focused on the strategic flow rather than the tactical details.<\/p>\n","protected":false},"excerpt":{"rendered":" Master BPMN sub-processes to manage complex workflows hierarchically. Learn to distinguish collapsed versus expanded states and model reusable components effectively in Visual Paradigm.<\/p>\n","protected":false},"author":1,"featured_media":9033,"template":"","meta":{"_yoast_wpseo_title":"Mastering BPMN Sub-Processes: From Hierarchical Logic to Visual Modeling","_yoast_wpseo_metadesc":"Master BPMN sub-processes to manage complex workflows hierarchically. Learn to distinguish collapsed versus expanded states and model reusable components effectively in Visual Paradigm.","inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"source_url":"https:\/\/bpmn.visual-paradigm.com\/mastering-hierarchy-in-bpmn-a-guide-to-collapsed-and-expanded-sub-processes\/","source_h1_title":"Mastering Hierarchy in BPMN: A Guide to Collapsed and Expanded Sub-Processes","fifu_image_url":"","fifu_image_alt":"","_fifu_image_alt":"","fifu_alt":"","_fifu_alt":"","fifu_image_title":"","_fifu_image_title":"","fifu_input_alt":"","vp_image_hash":"0ab036ae0636841e1cfc5945fb4fc568829a76726b2d8e585dbccf1a2ecb2c09"},"asset-category":[20],"class_list":["post-9032","gallery","type-gallery","status-publish","has-post-thumbnail","hentry","asset-category-bpmn"],"source_url":"https:\/\/bpmn.visual-paradigm.com\/mastering-hierarchy-in-bpmn-a-guide-to-collapsed-and-expanded-sub-processes\/","source_h1_title":"Mastering Hierarchy in BPMN: A Guide to Collapsed and Expanded Sub-Processes","fifu_image_url":"","fifu_image_alt":"","vp_image_hash":"0ab036ae0636841e1cfc5945fb4fc568829a76726b2d8e585dbccf1a2ecb2c09","yoast_head":"\n1. The Compound Activity: A Process Within a Process<\/h2>\n
\n
2. Visual States: Collapsed vs. Expanded Views<\/h2>\n
The Collapsed View (The “Plus” Sign)<\/h3>\n
The Expanded View (The “Details Visible” State)<\/h3>\n
\n
3. Types of Sub-Processes: Embedded vs. Independent<\/h2>\n
Embedded Sub-Processes<\/h3>\n
Independent (Reusable) Sub-Processes<\/h3>\n
4. Practical Application: The Credit Check Workflow<\/h2>\n
\n