{"id":363,"date":"2026-02-25T10:16:45","date_gmt":"2026-02-25T10:16:45","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/"},"modified":"2026-02-25T10:16:45","modified_gmt":"2026-02-25T10:16:45","slug":"bpmn-message-flows-shared-responsibilities","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/","title":{"rendered":"Modeling Message Flows and Shared Responsibilities"},"content":{"rendered":"<p>When you&#8217;re modeling a process that spans multiple departments or organizations, the temptation is to connect everything with sequence flows. But that\u2019s where things go wrong\u2014fast.<\/p>\n<p>Message flows are the correct answer. They\u2019re not just a visual nicety; they\u2019re the foundation of accurate, stakeholder-aligned collaboration diagrams.<\/p>\n<p>I\u2019ve seen teams waste weeks trying to force internal sequence flows across pools. It creates confusion, hides ownership, and breaks the model\u2019s integrity. The moment you use a message flow instead, clarity emerges.<\/p>\n<p>This chapter walks you through the practical mechanics of modeling BPMN message flows, how they differ from sequence flows, and how to assign responsibilities clearly using pools and lanes. You\u2019ll learn how to avoid the most common modeling anti-patterns and build diagrams that stakeholders actually trust.<\/p>\n<p>By the end, you\u2019ll know how to model B2B interactions, departmental handoffs, and shared workflows with precision\u2014without overcomplicating the diagram.<\/p>\n<h2>Understanding Message Flows vs. Sequence Flows<\/h2>\n<p>It starts with a fundamental distinction: sequence flows are internal. Message flows are external.<\/p>\n<p>A sequence flow shows the order of activities within a single process. It\u2019s the thread that runs through one pool, from start to end.<\/p>\n<p>A message flow, by contrast, represents communication between participants. It crosses pool boundaries and signals that one participant is sending a message to another.<\/p>\n<p>You can\u2019t use a sequence flow to connect two separate pools. If you do, you\u2019re implying that one participant is orchestrating the other\u2014a false assumption in most real-world cases.<\/p>\n<p>Think of message flows as the postal system of your model. They carry information, not control. They don\u2019t dictate what happens next inside the receiving pool\u2014they simply notify it that something has occurred.<\/p>\n<h3>When to Use Each Flow Type<\/h3>\n<p>Use sequence flows when modeling:<\/p>\n<ul>\n<li>Internal steps within a single process<\/li>\n<li>Decision paths inside a participant\u2019s workflow<\/li>\n<li>Internal looping or error handling<\/li>\n<\/ul>\n<p>Use message flows when modeling:<\/p>\n<ul>\n<li>Handoffs between departments<\/li>\n<li>Customer notifications from a system<\/li>\n<li>Order confirmations from a supplier<\/li>\n<li>Approval requests between teams<\/li>\n<\/ul>\n<p>Never mix them. A message flow should never connect two activities in the same pool. That\u2019s a red flag. It means you\u2019re treating a cross-participant exchange as if it were internal\u2014misleading and inaccurate.<\/p>\n<h2>Modeling Responsibilities with Pools and Lanes<\/h2>\n<p>Pools represent participants. Lanes represent roles or departments within those participants.<\/p>\n<p>Each pool owns its internal sequence flows. Each lane owns the activities assigned to it. The responsibility boundary is clear: you don\u2019t model someone else\u2019s internal logic.<\/p>\n<p>For example, in a procurement process, you might have two pools: \u201cProcurement Department\u201d and \u201cSupplier.\u201d The Procurement Department has lanes for \u201cPurchase Request,\u201d \u201cApproval,\u201d and \u201cOrder Creation.\u201d The Supplier has lanes for \u201cOrder Receipt,\u201d \u201cFulfillment,\u201d and \u201cShipment Notification.\u201d<\/p>\n<p>When the Procurement Department sends an order to the Supplier, that\u2019s a message flow from the \u201cOrder Creation\u201d lane to the \u201cOrder Receipt\u201d lane in the Supplier pool.<\/p>\n<p>This structure prevents the common mistake of \u201cover-owning\u201d the process. You\u2019re not modeling the Supplier\u2019s internal fulfillment process in detail unless you\u2019re building a collaboration diagram that includes it. Even then, you only show what\u2019s relevant to the interaction.<\/p>\n<h3>Best Practices for Assigning Responsibilities<\/h3>\n<ol>\n<li><strong>One pool per participant.<\/strong> Don\u2019t split a participant across multiple pools. It creates confusion about who is responsible.<\/li>\n<li><strong>Use lanes to represent roles, not individuals.<\/strong> Lanes are about function, not names. This keeps models scalable and reusable.<\/li>\n<li><strong>Label message flows clearly.<\/strong> Use verbs like \u201cSend Order,\u201d \u201cConfirm Receipt,\u201d or \u201cRequest Approval\u201d to make the intent obvious.<\/li>\n<li><strong>Align message flow direction with the participant\u2019s role.<\/strong> If the Supplier sends a shipment update, the message flow should originate from the Supplier pool, not the Procurement pool.<\/li>\n<\/ol>\n<p>These rules aren\u2019t arbitrary. They\u2019re based on years of modeling real supply chains, customer service workflows, and financial reconciliation processes. When you follow them, stakeholders can instantly see who does what\u2014and when.<\/p>\n<h2>BPMN Collaboration Message Flow Example<\/h2>\n<p>Let\u2019s walk through a real-world BPMN collaboration message flow example: a customer order process between a retailer and a logistics provider.<\/p>\n<p>Pool 1: Retailer (with lanes: Order Entry, Payment Processing, Shipment Request)<\/p>\n<p>Pool 2: Logistics Provider (with lanes: Order Receipt, Dispatch, Delivery Confirmation)<\/p>\n<p>Here\u2019s how the message flows work:<\/p>\n<ol>\n<li>After payment is confirmed, the Retailer sends a \u201cShipment Request\u201d message to the Logistics Provider.<\/li>\n<li>The Logistics Provider receives the request and sends a \u201cShipment Confirmed\u201d message back.<\/li>\n<li>After dispatch, the Logistics Provider sends a \u201cDelivery Update\u201d message.<\/li>\n<li>Finally, the Retailer sends a \u201cPayment Finalized\u201d message upon delivery confirmation.<\/li>\n<\/ol>\n<p>Each message flow is a clear, one-way communication. No internal logic is shown in the other pool. That\u2019s the power of separation.<\/p>\n<p>Now, if you were to model this as a single process diagram, you\u2019d have to include all the internal steps of both parties. That\u2019s not just messy\u2014it\u2019s impossible to maintain. Collaboration diagrams exist to solve that exact problem.<\/p>\n<h3>Common Pitfalls to Avoid<\/h3>\n<p>Even experienced modelers fall into traps. Here are the most frequent ones:<\/p>\n<ul>\n<li><strong>Mixing sequence and message flows across pools.<\/strong> This implies control where none exists. It breaks the model\u2019s meaning.<\/li>\n<li><strong>Using message flows to represent internal decisions.<\/strong> A message flow should not be used to show a conditional branch. Use gateways and sequence flows inside the pool.<\/li>\n<li><strong>Overloading a single pool with too many lanes.<\/strong> If a pool has more than 5\u20136 lanes, consider splitting it into sub-pools or using conversation diagrams to summarize.<\/li>\n<li><strong>Using generic labels like \u201cMessage\u201d or \u201cSend Data.\u201d<\/strong> Be specific. \u201cSend Invoice\u201d is clearer than \u201cSend Message.\u201d<\/li>\n<\/ul>\n<p>These mistakes don\u2019t just confuse readers\u2014they undermine trust in the entire model. If stakeholders can\u2019t understand who\u2019s doing what, they won\u2019t use the model to drive decisions.<\/p>\n<h2>How Shared Responsibilities Are Communicated<\/h2>\n<p>Shared responsibilities don\u2019t mean shared ownership of every step. They mean shared accountability for outcomes.<\/p>\n<p>For example, in the retailer-logistics interaction, both parties are responsible for on-time delivery\u2014but the Retailer is responsible for accurate order data, and the Logistics Provider is responsible for dispatch timing.<\/p>\n<p>That\u2019s where message flows become powerful. They make the handoff points visible. Each message flow is a checkpoint: \u201cThis task is complete. Now it\u2019s your turn.\u201d<\/p>\n<p>When you see a message flow labeled \u201cOrder Confirmed,\u201d you know the Retailer has finished their part. The Logistics Provider can now begin theirs.<\/p>\n<p>This transparency is the first step toward optimization. You can now measure handoff times, identify bottlenecks, and assign SLAs.<\/p>\n<p>Without message flows, these handoffs are invisible. The process looks like one long chain, and no one knows where delays occur.<\/p>\n<h3>Using Message Flows to Define SLAs and KPIs<\/h3>\n<p>Message flows are not just for documentation. They\u2019re the foundation for performance measurement.<\/p>\n<p>For example, you can define a KPI: \u201cTime from \u2018Shipment Request\u2019 to \u2018Shipment Confirmed\u2019 must be under 2 hours.\u201d That\u2019s measurable because the message flow defines the start and end points.<\/p>\n<p>Similarly, \u201cDelivery Update\u201d must be sent within 15 minutes of dispatch. That\u2019s a clear, traceable target.<\/p>\n<p>These KPIs can\u2019t be derived from internal sequence flows alone. They require the external visibility that message flows provide.<\/p>\n<h2>Tooling Tips: Visual Paradigm and BPMN Message Flows<\/h2>\n<p>Visual Paradigm makes it easy to model message flows correctly. The tool enforces the separation between sequence and message flows, so you can\u2019t accidentally connect two pools with a sequence flow.<\/p>\n<p>When you drag a message flow, it automatically appears as a dashed line with an arrow. The tool also lets you define message types and interfaces\u2014critical for consistency.<\/p>\n<p>Use the \u201cLink to Process Diagram\u201d feature to connect a collaboration diagram to its underlying process diagrams. This way, you can drill down from a high-level message flow to the internal logic of each participant.<\/p>\n<p>Also, use the \u201cParticipant Reuse\u201d feature. If you\u2019re modeling multiple order processes, you can reuse the same Retailer and Logistics Provider pools across diagrams. This ensures naming consistency and reduces errors.<\/p>\n<h2>Conclusion<\/h2>\n<p>Mastering BPMN message flows is not about syntax\u2014it\u2019s about clarity of responsibility.<\/p>\n<p>When you model interactions between pools, always ask: \u201cWho owns this step? What is being communicated? And where does the responsibility shift?\u201d<\/p>\n<p>Use message flows to answer those questions. They\u2019re not just connectors\u2014they\u2019re accountability markers.<\/p>\n<p>With clear pools, lanes, and message flows, you\u2019re not just drawing a diagram. You\u2019re building a shared understanding of how work actually gets done across boundaries.<\/p>\n<p>That\u2019s the real power of BPMN collaboration modeling.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use message flows inside a single pool?<\/h3>\n<p>No. Message flows are strictly for inter-pool communication. If you need to show internal handoffs, use sequence flows within the pool. Using message flows inside a pool breaks the modeling convention and confuses readers.<\/p>\n<h3>What\u2019s the difference between a BPMN collaboration message flow example and a choreography diagram?<\/h3>\n<p>A collaboration diagram shows the overall interaction between participants, including both message flows and the internal logic of each. A choreography diagram focuses only on the message exchanges, without showing internal process steps. Use collaboration diagrams when you need to show both sides of the story. Use choreography when you want to define a contract or interface.<\/p>\n<h3>How do I handle bidirectional communication in BPMN message flows?<\/h3>\n<p>Use two message flows\u2014one in each direction. For example, \u201cSend Order\u201d from Pool A to Pool B, and \u201cConfirm Order\u201d from Pool B to Pool A. Never use a single bidirectional line. BPMN requires separate flows for each direction.<\/p>\n<h3>Why should I avoid mixing sequence and message flows between pools?<\/h3>\n<p>Mixing them implies that one participant controls the other\u2019s process, which is rarely true. It creates a false sense of ownership and makes the model inaccurate. Message flows are passive signals; sequence flows are active control. Keeping them separate preserves the integrity of the model.<\/p>\n<h3>How do I model shared responsibilities without overloading the diagram?<\/h3>\n<p>Use lanes to assign specific roles within each pool. Then, use message flows to show handoffs. Keep internal logic detailed only where necessary. For high-level views, use conversation diagrams to summarize interactions.<\/p>\n<h3>Can message flows be used in non-executable models?<\/h3>\n<p>Absolutely. Message flows are valid in descriptive models used for analysis, documentation, or stakeholder alignment. They\u2019re not dependent on execution. Their purpose is to clarify communication and responsibility\u2014regardless of whether the process is automated.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you&#8217;re modeling a process that spans multiple departments or organizations, the temptation is to connect everything with sequence flows. But that\u2019s where things go wrong\u2014fast. Message flows are the correct answer. They\u2019re not just a visual nicety; they\u2019re the foundation of accurate, stakeholder-aligned collaboration diagrams. I\u2019ve seen teams waste weeks trying to force internal [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":361,"menu_order":1,"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-363","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>BPMN Message Flows: Modeling Shared Responsibilities<\/title>\n<meta name=\"description\" content=\"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.\" \/>\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\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Message Flows: Modeling Shared Responsibilities\" \/>\n<meta property=\"og:description\" content=\"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/\",\"name\":\"BPMN Message Flows: Modeling Shared Responsibilities\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:16:45+00:00\",\"description\":\"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Diagram Types Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Collaboration Diagrams \u2014 Interactions Across Participants\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Modeling Message Flows and Shared Responsibilities\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Message Flows: Modeling Shared Responsibilities","description":"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.","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\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/","og_locale":"es_ES","og_type":"article","og_title":"BPMN Message Flows: Modeling Shared Responsibilities","og_description":"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"9 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/","name":"BPMN Message Flows: Modeling Shared Responsibilities","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:16:45+00:00","description":"Learn how to model BPMN message flows between pools and define shared responsibilities with clarity. Includes real-world examples, best practices, and common pitfalls to avoid in cross-organizational processes.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/bpmn-message-flows-shared-responsibilities\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"BPMN Diagram Types Explained","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/"},{"@type":"ListItem","position":3,"name":"Collaboration Diagrams \u2014 Interactions Across Participants","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/bpmn-diagram-types-explained\/bpmn-collaboration-diagram\/"},{"@type":"ListItem","position":4,"name":"Modeling Message Flows and Shared Responsibilities"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/363\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/361"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=363"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}