{"id":549,"date":"2026-02-25T10:19:56","date_gmt":"2026-02-25T10:19:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/cmmn-vs-bpmn-when-to-use-which\/cmmn-bpmn-comparison\/hybrid-cmmn-bpmn-patterns\/"},"modified":"2026-02-25T10:19:56","modified_gmt":"2026-02-25T10:19:56","slug":"hybrid-cmmn-bpmn-patterns","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/cmmn-vs-bpmn-when-to-use-which\/cmmn-bpmn-comparison\/hybrid-cmmn-bpmn-patterns\/","title":{"rendered":"Hybrid Modeling Patterns"},"content":{"rendered":"

Most modelers assume they must choose between BPMN and CMMN. But in practice, real-world work doesn\u2019t fit neatly into one box. Complex processes often start with structured logic\u2014BPMN’s domain\u2014but require adaptive handling when exceptions arise, where CMMN shines. This is where hybrid CMMN BPMN patterns come into play.<\/p>\n

My experience over two decades has shown that rigid adherence to either notation leads to models that either over-control or under-manage. The real power lies in orchestrating both. Think of it as using BPMN as the backbone and CMMN as the adaptive nervous system.<\/p>\n

You\u2019ll learn how to embed CMMN cases inside BPMN flows, use BPMN to trigger CMMN case plans, and manage exceptions through coordinated decision logic. The goal isn\u2019t just to combine tools\u2014it\u2019s to build models that reflect reality, not just rules.<\/p>\n

Core Principles of Hybrid Modeling<\/h2>\n

Hybrid CMMN BPMN patterns aren\u2019t about mixing two standards at random. They\u2019re grounded in a simple insight: structured processes often break down at the edges. That\u2019s where adaptive case handling becomes essential.<\/p>\n

When you model a loan approval process, BPMN handles the predictable steps: application receipt, credit check, income verification. But when an anomaly appears\u2014say, a disputed credit history\u2014the system should pause the process and shift to a CMMN case for investigation.<\/p>\n

This shift isn\u2019t a workaround. It\u2019s a design choice. Hybrid modeling allows you to keep the flow of control clear while empowering knowledge workers to respond dynamically to uncertainty.<\/p>\n

Why Not Just Use CMMN for Everything?<\/h3>\n

Because CMMN excels in flexibility, but that flexibility comes at a cost: complexity and reduced automation potential. Not every process needs a case plan.<\/p>\n

BPMN, on the other hand, thrives in predictable, repeatable scenarios. But when exceptions emerge, modeling them in BPMN often leads to bloated, hard-to-maintain diagrams with endless gateways and alternate paths.<\/p>\n

Hybrid modeling keeps the strengths of both. Use BPMN for the predictable core. Use CMMN for the exceptional path.<\/p>\n

Key Hybrid Integration Patterns<\/h2>\n

1. BPMN Initiates a CMMN Case<\/h3>\n

One of the most reliable patterns: let BPMN detect a deviation and trigger a CMMN case.<\/p>\n

Example: A customer service ticket flows through BPMN stages\u2014receipt, triage, assignment. If the issue is complex or unresolved after three attempts, a gateway checks: \u201cIs this an edge case?\u201d If yes, the BPMN process triggers a CMMN case named \u201cInvestigation Workflow.\u201d<\/p>\n

The BPMN diagram remains clean. The CMMN case handles the investigation with stages, tasks, and sentries. When resolved, the case signals back to BPMN to resume.<\/p>\n

This pattern is ideal for customer complaints, insurance claims, or incident management.<\/p>\n

2. CMMN Subcase within a BPMN Process<\/h3>\n

Use this when part of a larger workflow is inherently unpredictable.<\/p>\n

Consider a loan underwriting process. After initial data validation (BPMN), you reach a point where the decision depends on a deep risk assessment. That assessment isn\u2019t linear\u2014it involves reviewing documents, consulting experts, and adjusting thresholds.<\/p>\n

Here, embed a CMMN case as a subprocess. The BPMN flow calls the CMMN subcase. The subcase manages its own tasks, milestones, and entry conditions. When complete, it returns control to BPMN to proceed with approval or rejection.<\/p>\n

This keeps the high-level BPMN flow readable while preserving adaptability in the complex region.<\/p>\n

3. Exception Handling via CMMN in BPMN<\/h3>\n

Most BPMN diagrams fail to model exceptions well. They either ignore them or hardcode them into parallel paths.<\/p>\n

Instead, use CMMN as the exception handler. When a BPMN process hits a failure point\u2014say, a required document is missing\u2014instead of adding another branch, create a CMMN case named \u201cDocument Reconciliation.\u201d<\/p>\n

The CMMN case defines: what documents are needed, who can request them, and what conditions allow resumption. Once the case is complete, the BPMN process continues.<\/p>\n

This approach avoids flow explosion. It also aligns with how real teams operate: they don\u2019t follow a fixed path when something goes wrong\u2014they create a new plan.<\/p>\n

Design Patterns in Practice<\/h2>\n

Here\u2019s how these patterns look in a real-world scenario: insurance claim processing.<\/p>\n

Step 1: A claim is submitted. BPMN handles data capture, initial validation, and fraud screening.<\/p>\n

Step 2: If fraud risk is low and the claim is straightforward, BPMN continues to settlement.<\/p>\n

Step 3: If fraud risk is medium or high, the BPMN process triggers a CMMN case: \u201cFraud Investigation.\u201d<\/p>\n

Inside the CMMN case, tasks like \u201cReview transaction history,\u201d \u201cInterview claimant,\u201d and \u201cConsult forensic analyst\u201d are defined. Entry conditions ensure the case only starts when fraud risk exceeds threshold.<\/p>\n

When the case is complete, a \u201ccase complete\u201d event triggers the BPMN flow to resume. The claim proceeds to settlement or denial.<\/p>\n

This design is not just elegant. It reflects how real claims teams operate. It\u2019s not a flowchart\u2014it\u2019s a decision framework.<\/p>\n

Implementation Checklist<\/h2>\n