{"id":367,"date":"2026-02-25T10:16:47","date_gmt":"2026-02-25T10:16:47","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/"},"modified":"2026-02-25T10:16:47","modified_gmt":"2026-02-25T10:16:47","slug":"bpmn-choreography-tasks","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/","title":{"rendered":"Choreography Tasks, Participants, and Sequence Flows"},"content":{"rendered":"<p>Imagine you\u2019re finalizing a contract with a vendor, and both parties need to agree on the exact sequence of messages\u2014acknowledgments, confirmations, data submissions\u2014without revealing internal workflows. That\u2019s where BPMN choreography tasks come in.<\/p>\n<p>This moment\u2014when clarity of interaction matters more than internal process details\u2014is where choreography diagrams deliver their highest value. They\u2019re not about what each participant does internally. They\u2019re about what they say to each other, and in what order.<\/p>\n<p>Many beginners start by modeling internal steps too early. They draw tasks, gateways, and lanes\u2014only to realize later that the real issue isn\u2019t internal logic, but misaligned expectations about who sends what, and when.<\/p>\n<p>After two decades of modeling complex integrations across finance, healthcare, and logistics, I\u2019ve seen this pattern repeat. The solution? Step back. Use choreography tasks to define the agreed-upon message flow. This is not a process diagram. It\u2019s a contract in visual form.<\/p>\n<p>By the end of this chapter, you\u2019ll know how to model choreography tasks, identify initiating and non-initiating participants, and use choreography sequence flow to express precise interaction order\u2014without a single internal activity.<\/p>\n<h2>What Are BPMN Choreography Tasks?<\/h2>\n<p>BPMN choreography tasks represent a message exchange between participants. They are not internal work. They are not actions performed by a single actor. They are events of communication.<\/p>\n<p>Unlike a regular BPMN task, which implies a unit of work (e.g., \u201cProcess Payment\u201d), a choreography task is purely communicative. It\u2019s a message sent or received\u2014like \u201cSend Invoice\u201d or \u201cReceive Confirmation.\u201d<\/p>\n<p>Think of it this way: a regular task says, \u201cI will do something.\u201d A choreography task says, \u201cWe will exchange this message.\u201d<\/p>\n<p>This shift in focus\u2014from internal work to shared communication\u2014is the core of choreography modeling.<\/p>\n<p>For example, in a B2B order flow, the choreography task \u201cSend Order Confirmation\u201d isn\u2019t owned by one party. It\u2019s a shared event: the buyer sends it, and the seller receives it. The choreography diagram captures that moment, not the internal steps that follow.<\/p>\n<h3>Choreography Tasks vs. Regular BPMN Tasks<\/h3>\n<p>Let\u2019s compare them directly:<\/p>\n<ul>\n<li><strong>Regular BPMN Task<\/strong>: Represents a unit of work performed by a participant. It has a name like \u201cValidate Customer Data\u201d and is located within a pool or lane.<\/li>\n<li><strong>BPMN Choreography Task<\/strong>: Represents a message exchange. It appears in the choreography diagram, not inside any pool. It has a name like \u201cSend Payment Notice\u201d and is connected via choreography sequence flow.<\/li>\n<\/ul>\n<p>Here\u2019s the key distinction: a choreography task has no internal process. It\u2019s a boundary event in the conversation, not an internal step.<\/p>\n<p>This is why choreography diagrams are often used to define service contracts, API interactions, or integration agreements. They\u2019re not about implementation\u2014they\u2019re about agreement.<\/p>\n<h2>Participants in BPMN Choreography<\/h2>\n<p>Participants in BPMN choreography are the actors involved in the message exchange. They\u2019re represented as pools in the diagram, just like in collaboration diagrams.<\/p>\n<p>But here\u2019s the difference: in choreography, each pool is a participant in a shared conversation. There\u2019s no internal structure. No lanes. No sequence flows inside the pool.<\/p>\n<p>Each participant is responsible for sending or receiving messages at the appropriate time. The choreography diagram defines the expected behavior of each participant, not their internal process.<\/p>\n<h3>Initiating vs. Non-Initiating Participants<\/h3>\n<p>One of the most practical distinctions in choreography is whether a participant initiates a message.<\/p>\n<p>An <strong>initiating participant<\/strong> is the one who sends the first message in the sequence. For example, in a customer onboarding flow, the customer might initiate by sending a \u201cRegistration Request.\u201d<\/p>\n<p>A <strong>non-initiating participant<\/strong> waits to receive the first message. In the same flow, the system might be non-initiating, waiting to receive the registration request before responding.<\/p>\n<p>This distinction is critical when modeling contracts or service-level agreements. It defines who starts the interaction\u2014and who is expected to respond.<\/p>\n<p>Use visual cues: initiating participants often have a message flow that starts from their pool. Non-initiating ones receive from others.<\/p>\n<h2>Choreography Sequence Flow: The Backbone of Message Order<\/h2>\n<p>The choreography sequence flow is the line that connects choreography tasks. It defines the order in which messages are exchanged.<\/p>\n<p>Unlike sequence flows in process diagrams, which represent internal logic, choreography sequence flows represent the agreed-upon order of communication.<\/p>\n<p>They are always directed from one choreography task to another. They never go inside a pool. They never connect to internal activities.<\/p>\n<p>Here\u2019s a simple pattern:<\/p>\n<ul>\n<li>Participant A sends Message 1<\/li>\n<li>Participant B receives Message 1<\/li>\n<li>Participant B sends Message 2<\/li>\n<li>Participant A receives Message 2<\/li>\n<\/ul>\n<p>This sequence is represented as a chain of choreography tasks linked by choreography sequence flows. The flow shows that the interaction must happen in this exact order.<\/p>\n<p>When you model choreography sequence flow, you\u2019re not modeling what happens inside. You\u2019re modeling what must happen between parties.<\/p>\n<h3>Common Choreography Patterns<\/h3>\n<p>Here are three recurring patterns you\u2019ll see in real-world choreography diagrams:<\/p>\n<ol>\n<li><strong>Request-Response<\/strong>: One participant sends a request, the other responds. This is the most common pattern in API and service contracts.<\/li>\n<li><strong>Two-Way Synchronization<\/strong>: Both participants send and receive messages in alternating order. Useful for real-time data exchange.<\/li>\n<li><strong>One-Way Notification<\/strong>: One participant sends a message, and the other receives it without a reply. Common in event-driven systems.<\/li>\n<\/ol>\n<p>Each pattern uses choreography sequence flow to enforce the correct order. No flow means no agreement.<\/p>\n<h2>Practical Modeling Steps: Building a Choreography Diagram<\/h2>\n<p>Here\u2019s how I approach choreography modeling in real projects:<\/p>\n<ol>\n<li><strong>Identify the participants<\/strong>: Who is involved in the interaction? List them clearly. Use consistent names across diagrams.<\/li>\n<li><strong>Define the message exchange sequence<\/strong>: Walk through the conversation step by step. What is sent first? What is expected in response?<\/li>\n<li><strong>Model each message as a choreography task<\/strong>: Use the format \u201cSend [Message Name]\u201d or \u201cReceive [Message Name]\u201d for clarity.<\/li>\n<li><strong>Connect tasks with choreography sequence flow<\/strong>: Ensure the flow reflects the required order. No loops unless explicitly agreed upon.<\/li>\n<li><strong>Label the flows<\/strong>: Add optional labels to indicate message types or conditions (e.g., \u201cif approval is granted\u201d).<\/li>\n<li><strong>Review with stakeholders<\/strong>: Show it to both technical and business teams. Ask: \u201cDoes this match your understanding of the interaction?\u201d<\/li>\n<\/ol>\n<p>When done right, the diagram becomes a shared contract. No more \u201cI thought you\u2019d send it earlier.\u201d<\/p>\n<h2>Visual Example: Order Confirmation Flow<\/h2>\n<p>Consider this real-world scenario: a retailer and a logistics provider must agree on the order confirmation sequence.<\/p>\n<pre><code>\n[Retailer] \u2192 Send Order Confirmation\n               \u2193\n[Logistics] \u2190 Receive Order Confirmation\n               \u2193\n[Logistics] \u2192 Send Shipment Acknowledgment\n               \u2193\n[Retailer] \u2190 Receive Shipment Acknowledgment\n    <\/code><\/pre>\n<p>This is a choreography diagram. The pools are \u201cRetailer\u201d and \u201cLogistics.\u201d The tasks are the message exchanges. The flows are choreography sequence flows.<\/p>\n<p>Notice: no internal steps. No gateways. No lanes. Just the agreed-upon message flow.<\/p>\n<p>This diagram can be shared with both teams. It\u2019s unambiguous. It\u2019s contract-ready.<\/p>\n<h2>Best Practices for BPMN Choreography Notation<\/h2>\n<p>Choreography diagrams are powerful\u2014but only if modeled clearly. Here\u2019s what I\u2019ve learned from years of audits and reviews:<\/p>\n<ul>\n<li><strong>Use consistent naming<\/strong>: \u201cSend Order Confirmation\u201d is better than \u201cSend Conf\u201d or \u201cOrder Sent.\u201d Be descriptive and unambiguous.<\/li>\n<li><strong>Never mix choreography and process flows<\/strong>: Choreography sequence flows must not connect to internal sequence flows. Keep them separate.<\/li>\n<li><strong>Use choreography tasks for all message exchanges<\/strong>: Even if a message is sent by a system, model it as a choreography task. The sender is still a participant.<\/li>\n<li><strong>Keep diagrams focused<\/strong>: A choreography diagram should show only the message sequence. Avoid adding conditions, loops, or data elements unless essential.<\/li>\n<li><strong>Link to other diagrams<\/strong>: Use choreography diagrams as a foundation. Then, build process diagrams for each participant\u2019s internal logic.<\/li>\n<\/ul>\n<p>These practices prevent confusion and ensure that choreography diagrams remain trustworthy as agreements.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the difference between a choreography task and a message flow in a collaboration diagram?<\/h3>\n<p>A choreography task is a message exchange represented as a task in a choreography diagram. A message flow in a collaboration diagram shows the direction of a message between pools, but it doesn\u2019t define the task. The choreography task is the event itself\u2014the message being sent or received.<\/p>\n<h3>Can a choreography task be part of a loop?<\/h3>\n<p>Yes, but only if the loop is explicitly agreed upon. For example, in a retry mechanism, a participant might send a message, receive a failure, and retry. This is allowed, but it must be clearly modeled with a loop construct in the choreography sequence flow.<\/p>\n<h3>How do I model a conditional message in a choreography diagram?<\/h3>\n<p>Use a conditional choreography sequence flow. Add a label like \u201cif payment approved\u201d or \u201cif data valid.\u201d The condition applies to the message exchange, not the internal logic of the participant.<\/p>\n<h3>Should I use choreography diagrams for internal process documentation?<\/h3>\n<p>No. Choreography diagrams are for inter-participant interactions. Use process diagrams for internal workflows. Mixing them creates confusion and undermines clarity.<\/p>\n<h3>What tools support BPMN choreography tasks and choreography sequence flow?<\/h3>\n<p>Most modern BPMN tools\u2014like Visual Paradigm\u2014support choreography diagrams. Ensure the tool allows you to draw choreography tasks and sequence flows outside of pools, and that it validates the flow structure.<\/p>\n<h3>How do choreography diagrams relate to process and collaboration diagrams?<\/h3>\n<p>They\u2019re complementary. A choreography diagram defines the agreed-upon message flow. A collaboration diagram shows how the message flows connect across pools. A process diagram shows what each participant does internally. Use all three to create a complete, consistent model.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Imagine you\u2019re finalizing a contract with a vendor, and both parties need to agree on the exact sequence of messages\u2014acknowledgments, confirmations, data submissions\u2014without revealing internal workflows. That\u2019s where BPMN choreography tasks come in. This moment\u2014when clarity of interaction matters more than internal process details\u2014is where choreography diagrams deliver their highest value. They\u2019re not about what [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":365,"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-367","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 Choreography Tasks: Modeling Message Exchanges<\/title>\n<meta name=\"description\" content=\"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.\" \/>\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\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Choreography Tasks: Modeling Message Exchanges\" \/>\n<meta property=\"og:description\" content=\"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/\",\"name\":\"BPMN Choreography Tasks: Modeling Message Exchanges\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:16:47+00:00\",\"description\":\"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Diagram Types Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Choreography Diagrams \u2014 Defining Participant Behavior\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Choreography Tasks, Participants, and Sequence Flows\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Choreography Tasks: Modeling Message Exchanges","description":"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.","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\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/","og_locale":"fr_FR","og_type":"article","og_title":"BPMN Choreography Tasks: Modeling Message Exchanges","og_description":"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/","name":"BPMN Choreography Tasks: Modeling Message Exchanges","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:16:47+00:00","description":"Learn how to model BPMN choreography tasks, participants, and choreography sequence flow with real-world examples. Master the notation and best practices for clear, collaborative process design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/bpmn-choreography-tasks\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"BPMN Diagram Types Explained","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/"},{"@type":"ListItem","position":3,"name":"Choreography Diagrams \u2014 Defining Participant Behavior","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-choreography-diagram\/"},{"@type":"ListItem","position":4,"name":"Choreography Tasks, Participants, and Sequence Flows"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/367\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/365"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=367"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}