{"id":600,"date":"2026-02-25T10:20:48","date_gmt":"2026-02-25T10:20:48","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/"},"modified":"2026-02-25T10:20:48","modified_gmt":"2026-02-25T10:20:48","slug":"internal-vs-external-bpmn-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/","title":{"rendered":"Confusing Internal Processes with External Partner Flows"},"content":{"rendered":"<p>One decision separates good BPMN modeling from confusion: whether to treat a customer or partner as an extension of your own process or as a distinct participant. Most modelers who struggle with collaboration diagrams make the same early misstep\u2014placing partner actions inside the same pool as internal steps. This blurs responsibilities, hides contractual boundaries, and makes it impossible to audit or automate correctly.<\/p>\n<p>Over 20 years of auditing BPMN models has taught me that a diagram is only as useful as its ability to reflect real-world responsibility. When you mix internal tasks and external partner actions in one pool, you\u2019re not just modeling a process\u2014you\u2019re misrepresenting who does what. This chapter will show you how to fix that.<\/p>\n<p>You\u2019ll learn when and how to use separate pools, how to model external participants as black-box processes, and when to expose internal steps without breaking the contract. You\u2019ll also see real-world examples where this mistake caused automation failures and audit issues.<\/p>\n<h2>Why Mixing Internal and External Flows Breaks the Model<\/h2>\n<p>Every BPMN pool should represent a distinct participant with clear ownership. When you place a customer\u2019s payment confirmation step inside your organization\u2019s pool, you\u2019re implying your team performs the action\u2014when in reality, it\u2019s initiated by an external system.<\/p>\n<p>This mistake is especially common in invoicing, onboarding, or order processing flows. A typical example: a modeler writes \u201cCustomer approves invoice\u201d as a task inside the company\u2019s pool. But the approval happens via a third-party portal. The act of approval is external, and the responsibility lies with the customer\u2014not your team.<\/p>\n<p>What happens when you do this? The model claims ownership where none exists. Automation systems expect to control every task in the process. When a task is actually external, the workflow fails or skips steps because the system doesn\u2019t know it\u2019s waiting for a signal from outside.<\/p>\n<p>Here\u2019s the rule: if a task is triggered by an external agent or system, do not place it in your internal pool unless you\u2019re representing it as an event. The moment you do, you\u2019ve broken the contract.<\/p>\n<h3>Real-World Impact: When the Flow Lies<\/h3>\n<p>At a financial services firm, a BPMN model showed \u201cCustomer uploads documents\u201d as a task in the internal processing pool. The system was designed to wait for this step to complete before sending the application to underwriting. But the customer uploads happened via a secure portal\u2014outside the process. The model claimed the process was stuck when it was actually waiting for a user action.<\/p>\n<p>After the fix, the model used a message flow from a separate \u201cCustomer\u201d pool. The internal process now correctly waited for a \u201cDocument Received\u201d message event. The automation worked. The audit passed. The root cause? A single misplacement of a task in the wrong pool.<\/p>\n<p>This is why <strong>modeling partners in BPMN<\/strong> requires more than just a new lane. It demands a shift in mindset: from \u201cwhat happens\u201d to \u201cwho is responsible.\u201d<\/p>\n<h2>The Correct Way: Modeling Customers and Partners as Separate Pools<\/h2>\n<p>When you represent a customer, vendor, or external system as a distinct participant, you create a clear boundary. This is the foundation of a correct collaboration model.<\/p>\n<p>Start by asking: \u201cCan this step be performed without my team\u2019s involvement?\u201d If yes, it belongs in a separate pool. This applies to any action initiated by an external agent, system, or approval.<\/p>\n<p>Use the following pattern:<\/p>\n<ol>\n<li>Create a new pool for the external participant (e.g., \u201cCustomer,\u201d \u201cBank,\u201d \u201cSupplier\u201d).<\/li>\n<li>Add a message flow from your pool to theirs to represent a request.<\/li>\n<li>Add a message flow back to represent a response.<\/li>\n<li>Use a message event in your process to receive the external signal.<\/li>\n<\/ol>\n<p>This approach makes responsibilities explicit and aligns with how real processes work.<\/p>\n<h3>When to Use Black-Box vs White-Box Pools<\/h3>\n<p>Not every external process needs detailed modeling. Use a black-box pool when you only care about the interaction, not the internal steps.<\/p>\n<p>For example, in a loan application process, you may only need to know when the credit check is complete. You don\u2019t need to model every step the bank takes. Represent the bank as a black-box pool with a single message event: \u201cCredit Check Complete.\u201d<\/p>\n<p>Use a white-box pool when you need to show the sequence of steps the partner performs. This is common in integrations where the external process is reusable or must be audited.<\/p>\n<p>Never model both internal and external details in the same pool. That\u2019s the essence of <strong>BPMN customer pool errors<\/strong>: confusing the actor with the actor\u2019s responsibility.<\/p>\n<h2>Step-by-Step: Fixing an Incorrect Collaboration Model<\/h2>\n<p>Here\u2019s how to correct a flow that mixes internal and external actions.<\/p>\n<ol>\n<li><strong>Identify external actions<\/strong>: Look for any task or event triggered by a customer, partner, or system outside the current process.<\/li>\n<li><strong>Create a new pool<\/strong>: Add a pool for the external participant (e.g., \u201cOnline Portal,\u201d \u201cPayment Gateway\u201d).<\/li>\n<li><strong>Replace internal tasks<\/strong>: Remove the task from your pool and replace it with a message event that receives a signal from the external pool.<\/li>\n<li><strong>Add message flows<\/strong>: Draw a message flow from your process to the external pool (e.g., \u201cSend payment request\u201d) and back (e.g., \u201cReceive payment confirmation\u201d).<\/li>\n<li><strong>Verify contracts<\/strong>: Ensure the message names reflect real, auditable events (e.g., \u201cPayment Approved by Gateway\u201d).<\/li>\n<\/ol>\n<p>This approach is not about complexity. It\u2019s about accuracy.<\/p>\n<h3>Example: Correcting a Flawed Onboarding Flow<\/h3>\n<p>Before:<\/p>\n<ul>\n<li>\u201cCustomer fills out form\u201d \u2013 in company pool<\/li>\n<li>\u201cCustomer submits form\u201d \u2013 in company pool<\/li>\n<li>\u201cCustomer verifies identity\u201d \u2013 in company pool<\/li>\n<\/ul>\n<p>After:<\/p>\n<ul>\n<li>\u201cCustomer fills out form\u201d \u2013 in \u201cCustomer\u201d pool<\/li>\n<li>\u201cCustomer submits form\u201d \u2013 in \u201cCustomer\u201d pool<\/li>\n<li>\u201cReceive identity verification result\u201d \u2013 in company pool, as a message event<\/li>\n<\/ul>\n<p>The company now waits for a message from the customer\u2019s process. Responsibility is clear. The model is correct.<\/p>\n<h2>When to Expose Internal Logic: Collaboration Diagrams<\/h2>\n<p>There are times when you need to show the internal steps of an external system. Use a collaboration diagram to do so.<\/p>\n<p>For example, if your process interacts with a vendor\u2019s API, and that API has multiple steps\u2014authentication, validation, processing\u2014you might want to show its internal flow.<\/p>\n<p>Do this by:<\/p>\n<ol>\n<li>Creating a collaboration diagram (a sub-diagram within the main process).<\/li>\n<li>Showing the external system as a pool with internal lanes.<\/li>\n<li>Linking the main process to the collaboration diagram using message flows.<\/li>\n<\/ol>\n<p>This is called a <strong>white-box collaboration<\/strong>. It\u2019s appropriate when the internal steps affect your process behavior.<\/p>\n<p>But never do this in a way that blurs the external boundary. The external system remains a separate pool. Its internal logic is part of a separate model.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even after understanding the principles, modelers often revert to old habits. Here are the top mistakes to watch for:<\/p>\n<ul>\n<li><strong>Using sequence flows between pools<\/strong>: This implies your process controls the partner\u2019s steps. Always use message flows for cross-pool communication.<\/li>\n<li><strong>Labeling external actions as \u201cdone by us\u201d<\/strong>: Even if your team handles the input, the action is external. Use \u201cCustomer approves\u201d or \u201cPayment gateway confirms,\u201d not \u201cWe confirm.\u201d<\/li>\n<li><strong>Over-detailing external flows<\/strong>: Show only what affects your process. If a partner\u2019s internal steps don\u2019t impact you, keep them in a black box.<\/li>\n<li><strong>Forgetting to model handoffs explicitly<\/strong>: A message flow must start and end at a clear event or task. No ambiguity.<\/li>\n<\/ul>\n<p>Each of these reflects a failure to separate internal and external flows. They\u2019re symptoms of a deeper issue: mistaking control for ownership.<\/p>\n<h3>Checklist: Are You Separating Internal and External Flows?<\/h3>\n<ul>\n<li>\u2705 Is every external action placed in its own pool?<\/li>\n<li>\u2705 Are message flows used for cross-pool communication?<\/li>\n<li>\u2705 Is the external participant\u2019s role clear in the process?<\/li>\n<li>\u2705 Have you avoided placing customer actions in your own pool?<\/li>\n<li>\u2705 Do message events reflect real, auditable signals?<\/li>\n<\/ul>\n<p>Use this checklist before finalizing any collaboration diagram.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I model a partner\u2019s process in detail inside my BPMN diagram?<\/h3>\n<p>Yes, but only through a collaboration diagram. Never embed a partner\u2019s internal steps in your main process pool. Use a separate pool with lanes to show the partner\u2019s internal flow. Keep the main model focused on your responsibilities.<\/p>\n<h3>When should I use a black-box pool instead of a white-box one?<\/h3>\n<p>Use a black-box pool when the internal steps of the external process are irrelevant to your model. This is typical for third-party systems like payment gateways or credit bureaus. You only care about the result, not how it\u2019s produced.<\/p>\n<h3>What if the partner\u2019s process is not well-documented?<\/h3>\n<p>Model it as a black box. Use a message event to represent the expected output (e.g., \u201cPayment confirmed\u201d). Work with the partner to agree on signal names and timing. This keeps the model correct and collaborative.<\/p>\n<h3>How do I handle a situation where my process depends on multiple partner actions?<\/h3>\n<p>Use multiple pools, each with its own message events. For example, one pool for the vendor, another for the shipping provider. Link each with a message flow to your process. Use gateways to wait for all or any signals, depending on the flow.<\/p>\n<h3>Can I use the same pool for both internal and external actions if I add a label?<\/h3>\n<p>No. A pool is a boundary of responsibility. Adding labels doesn\u2019t change the semantics. If an action is performed externally, it must be in a separate pool. Labeling a task \u201cCustomer\u201d doesn\u2019t make it internal.<\/p>\n<h3>Is it bad to have multiple message flows to the same external pool?<\/h3>\n<p>No, it\u2019s common and acceptable. For example, your process might send a \u201cRequest for Quote\u201d and later receive a \u201cQuote Received\u201d message. Each is a distinct interaction. Just make sure the message names are clear and unambiguous.<\/p>\n<p>When you stop mixing internal and external flows, you stop hiding complexity. You\u2019re not hiding it\u2014you\u2019re revealing who does what. That\u2019s the real value of BPMN: clarity, accountability, and automation readiness.<\/p>\n<p>Remember: a diagram that hides responsibility is worse than no diagram at all. Fix your pools. Fix your flows. Fix your mind.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One decision separates good BPMN modeling from confusio [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":597,"menu_order":2,"template":"","meta":{"_acf_changed":false,"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":""}},"footnotes":""},"doc_tag":[],"class_list":["post-600","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Internal vs External BPMN Mistakes: Fixing Partner Flow Errors<\/title>\n<meta name=\"description\" content=\"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Internal vs External BPMN Mistakes: Fixing Partner Flow Errors\" \/>\n<meta property=\"og:description\" content=\"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/\",\"name\":\"Internal vs External BPMN Mistakes: Fixing Partner Flow Errors\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:20:48+00:00\",\"description\":\"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Collaboration and Interaction Mistakes\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Confusing Internal Processes with External Partner Flows\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Internal vs External BPMN Mistakes: Fixing Partner Flow Errors","description":"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/","og_locale":"zh_CN","og_type":"article","og_title":"Internal vs External BPMN Mistakes: Fixing Partner Flow Errors","og_description":"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"8 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/","name":"Internal vs External BPMN Mistakes: Fixing Partner Flow Errors","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:20:48+00:00","description":"Fix common BPMN modeling errors by separating internal processes from external partner flows. Learn how to model partners correctly and avoid confusion in collaboration diagrams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/internal-vs-external-bpmn-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Collaboration and Interaction Mistakes","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/"},{"@type":"ListItem","position":4,"name":"Confusing Internal Processes with External Partner Flows"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/600\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/597"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=600"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}