{"id":359,"date":"2026-02-25T10:16:43","date_gmt":"2026-02-25T10:16:43","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/"},"modified":"2026-02-25T10:16:43","modified_gmt":"2026-02-25T10:16:43","slug":"executable-vs-non-executable-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/","title":{"rendered":"Executable vs. Non-Executable Process Models"},"content":{"rendered":"<p>When you\u2019re modeling a business process, the question isn\u2019t just \u201cwhat happens next?\u201d \u2014 it\u2019s \u201cwho will act on this, and how?\u201d<\/p>\n<p>That\u2019s where the distinction between executable and non-executable BPMN models becomes critical.<\/p>\n<p>One model can guide conversation. Another can run software. Confusing them leads to wasted time, misaligned teams, and failed automation efforts.<\/p>\n<p>After two decades of working with organizations from startups to global enterprises, I\u2019ve seen this confusion repeat \u2014 not because people don\u2019t understand BPMN, but because they don\u2019t know how to *use* it for its intended purpose.<\/p>\n<p>This chapter cuts through the noise. You\u2019ll learn how to choose between a descriptive BPMN process for documentation and an executable BPMN process model for automation \u2014 and how to transition from one to the other with confidence.<\/p>\n<p>By the end, you\u2019ll know which elements matter for execution, which are safe to leave out, and how to avoid the trap of over-engineering a model that\u2019s meant to be a conversation starter.<\/p>\n<h2>Understanding the Core Difference<\/h2>\n<p>At its heart, the difference between executable and non-executable BPMN models comes down to intent.<\/p>\n<p>A descriptive BPMN process exists to communicate. It shows what a process *is*, not how it *runs*.<\/p>\n<p>An executable BPMN process model, by contrast, is a machine-readable specification. It defines the exact behavior a process engine must follow.<\/p>\n<p>Think of it like this: a descriptive model is a blueprint for a building. An executable model is the set of instructions a construction robot follows \u2014 precise, unambiguous, and ready to execute.<\/p>\n<p>They\u2019re both valuable. But using the wrong one in the wrong context creates friction.<\/p>\n<h3>When You Need a Descriptive BPMN Process<\/h3>\n<p>Use a descriptive BPMN process when your goal is clarity, alignment, or documentation.<\/p>\n<p>Examples include:<\/p>\n<ul>\n<li>Onboarding new team members to a business process<\/li>\n<li>Presenting a high-level workflow to stakeholders<\/li>\n<li>Mapping a process for compliance or audit purposes<\/li>\n<li>Facilitating a workshop to identify pain points<\/li>\n<\/ul>\n<p>These models don\u2019t need to be executable. In fact, forcing execution-ready syntax into them often adds noise.<\/p>\n<p>For instance, I once worked with a finance team that had a 12-step approval process. They modeled it in BPMN with every gate, every condition, and every data object \u2014 all for a presentation to executives. The result? A dense diagram that obscured the real issue: too many approvals.<\/p>\n<p>They didn\u2019t need an executable model. They needed a simple, visual story.<\/p>\n<h3>When You Need an Executable BPMN Process Model<\/h3>\n<p>Use an executable BPMN process model when you\u2019re preparing to deploy a process to a workflow engine \u2014 such as Camunda, Activiti, or Microsoft Power Automate.<\/p>\n<p>Here, every element must be precise, unambiguous, and technically valid.<\/p>\n<p>Key constructs that matter for execution:<\/p>\n<ul>\n<li><strong>Service tasks<\/strong> with defined operation references<\/li>\n<li><strong>Data objects<\/strong> and <strong>data associations<\/strong> that map to variables<\/li>\n<li><strong>Message events<\/strong> with correct correlation keys<\/li>\n<li><strong>Timer events<\/strong> with valid expressions (e.g., ISO 8601)<\/li>\n<li><strong>Boundary events<\/strong> with correct error codes or cancellation behavior<\/li>\n<li><strong>Sequence flows<\/strong> that are not just logical, but executable<\/li>\n<\/ul>\n<p>These aren\u2019t optional. They\u2019re required for the engine to interpret and run the process.<\/p>\n<p>For example, a \u201cSend Email\u201d task must reference a specific email service \u2014 not just say \u201csend an email.\u201d Otherwise, the engine doesn\u2019t know what to do.<\/p>\n<h2>What\u2019s in a Model? A Practical Breakdown<\/h2>\n<p>Let\u2019s compare a descriptive BPMN process and an executable one side by side \u2014 using a real-world example: a customer onboarding workflow.<\/p>\n<h3>Descriptive BPMN Process (Documentation-First)<\/h3>\n<p>This version focuses on clarity and stakeholder understanding. It shows the flow, responsibilities, and key decisions \u2014 but not execution details.<\/p>\n<p>Example elements:<\/p>\n<ul>\n<li>Start event: \u201cCustomer submits application\u201d<\/li>\n<li>Task: \u201cVerify identity\u201d (no service reference)<\/li>\n<li>Exclusive gateway: \u201cIs identity valid?\u201d<\/li>\n<li>Task: \u201cSend welcome email\u201d (textual description only)<\/li>\n<li>End event: \u201cOnboarding complete\u201d<\/li>\n<\/ul>\n<p>It\u2019s clean. It\u2019s readable. It answers: \u201cWhat happens in this process?\u201d<\/p>\n<p>But it\u2019s not ready to run.<\/p>\n<h3>Executable BPMN Process Model (Automation-Ready)<\/h3>\n<p>This version includes all the technical details needed for execution.<\/p>\n<p>Same process, but now:<\/p>\n<ul>\n<li>Task: \u201cVerify identity\u201d \u2192 <code>serviceTask<\/code> with <code>camunda:operation=\"verifyIdentity\"<\/code><\/li>\n<li>Gateway: \u201cIs identity valid?\u201d \u2192 <code>conditionExpression<\/code> with <code>${identityVerified == true}<\/code><\/li>\n<li>Task: \u201cSend welcome email\u201d \u2192 <code>serviceTask<\/code> with <code>camunda:operation=\"sendWelcomeEmail\"<\/code> and <code>dataInput<\/code> mapping to <code>customer.email<\/code><\/li>\n<li>Timer event: \u201cFollow-up reminder\u201d \u2192 <code>timeDuration=\"P7D\"<\/code><\/li>\n<\/ul>\n<p>Now the process engine knows exactly what to do, when, and with what data.<\/p>\n<p>It\u2019s not just a diagram. It\u2019s a program.<\/p>\n<h2>How to Evolve from Descriptive to Executable<\/h2>\n<p>Many teams start with a descriptive model \u2014 and that\u2019s perfectly valid. But the real power comes when you evolve it into an executable one.<\/p>\n<p>Here\u2019s a practical path:<\/p>\n<ol>\n<li><strong>Start with a descriptive model<\/strong> to align stakeholders and capture the process logic.<\/li>\n<li><strong>Validate the flow<\/strong> with business users \u2014 make sure no steps are missing, and decisions are clear.<\/li>\n<li><strong>Identify automation candidates<\/strong> \u2014 which tasks can be automated? Which decisions are rule-based?<\/li>\n<li><strong>Map data<\/strong> \u2014 define what data is needed at each step, and how it flows.<\/li>\n<li><strong>Add executable constructs<\/strong> \u2014 service tasks, data mappings, expressions, events.<\/li>\n<li><strong>Validate with a process engine<\/strong> \u2014 test the model in a simulation or deployment environment.<\/li>\n<\/ol>\n<p>It\u2019s not a one-way transformation. You\u2019ll often go back and refine the descriptive model based on execution feedback.<\/p>\n<p>For example, during a simulation, you might discover that a \u201cmanual review\u201d step is causing bottlenecks. You can then rework the descriptive model to reflect a new, automated review path \u2014 and update the executable model accordingly.<\/p>\n<h3>Key Trade-Offs to Consider<\/h3>\n<p>Not every process should be executable. Here\u2019s when to pause and ask: \u201cDo I really need this?\u201d<\/p>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Recommended Approach<\/th>\n<\/tr>\n<tr>\n<td>Process documentation for training<\/td>\n<td>Descriptive BPMN process<\/td>\n<\/tr>\n<tr>\n<td>Internal audit or compliance review<\/td>\n<td>Descriptive BPMN process<\/td>\n<\/tr>\n<tr>\n<td>Deploying a workflow to a digital platform<\/td>\n<td>Executable BPMN process model<\/td>\n<\/tr>\n<tr>\n<td>Integrating with an external system (e.g., CRM, ERP)<\/td>\n<td>Executable BPMN process model<\/td>\n<\/tr>\n<tr>\n<td>Facilitating a cross-functional workshop<\/td>\n<td>Descriptive BPMN process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Remember: a descriptive model is a conversation tool. An executable model is a contract with a machine.<\/p>\n<h2>Tools and Best Practices<\/h2>\n<p>Modern BPMN tools \u2014 like Visual Paradigm\u2014 support both modeling styles. But they don\u2019t always make the distinction clear.<\/p>\n<p>Here\u2019s how to stay sharp:<\/p>\n<ul>\n<li><strong>Use different diagram types<\/strong> for different purposes. A process diagram for internal flow, a collaboration diagram for partner interactions.<\/li>\n<li><strong>Tag models<\/strong> with labels like \u201cDraft \u2013 Descriptive\u201d or \u201cFinal \u2013 Executable\u201d to avoid confusion.<\/li>\n<li><strong>Use a consistent naming convention<\/strong> for tasks, data, and events \u2014 especially when transitioning between models.<\/li>\n<li><strong>Validate with simulation<\/strong> early and often. Don\u2019t wait until deployment to find issues.<\/li>\n<li><strong>Document assumptions<\/strong> \u2014 especially when omitting execution details in a descriptive model.<\/li>\n<\/ul>\n<p>One team I worked with used a simple color code: green for executable elements, yellow for descriptive ones. It took 10 minutes to set up \u2014 but saved hours of debate.<\/p>\n<p>Don\u2019t over-model. Don\u2019t under-model. Model with purpose.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can a single BPMN diagram be both descriptive and executable?<\/h3>\n<p>Technically, yes \u2014 but it\u2019s not recommended. A model that tries to serve both purposes often becomes bloated and confusing. It\u2019s better to use separate diagrams: one for discussion, one for execution.<\/p>\n<h3>What happens if I try to deploy a descriptive BPMN process to a process engine?<\/h3>\n<p>The engine will likely reject it. Missing service task references, invalid expressions, or undefined data objects will cause parsing errors. Always validate the model before deployment.<\/p>\n<h3>Do I need to model every step as executable?<\/h3>\n<p>No. Only the steps that need to be automated. Manual tasks, approvals, or human interventions can remain non-executable \u2014 as long as they\u2019re clearly marked and understood.<\/p>\n<h3>How do I know if a process is ready to become executable?<\/h3>\n<p>Ask: \u201cCan a machine follow this process without ambiguity?\u201d If the answer is \u201cnot really,\u201d then you\u2019re not ready. Add data mappings, conditions, and service references until it\u2019s unambiguous.<\/p>\n<h3>What\u2019s the biggest mistake teams make with executable BPMN models?<\/h3>\n<p>Over-specifying. They add technical details too early \u2014 before the process logic is agreed upon. This leads to rework, frustration, and models that don\u2019t reflect reality.<\/p>\n<h3>Is it possible to automate a process that started as a descriptive model?<\/h3>\n<p>Absolutely. That\u2019s one of the main benefits of starting with a descriptive model. It gives you a shared understanding. Then, layer in execution details incrementally \u2014 based on business need, not technical whim.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you\u2019re modeling a business process, the question isn\u2019t just \u201cwhat happens next?\u201d \u2014 it\u2019s \u201cwho will act on this, and how?\u201d That\u2019s where the distinction between executable and non-executable BPMN models becomes critical. One model can guide conversation. Another can run software. Confusing them leads to wasted time, misaligned teams, and failed automation efforts. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":356,"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-359","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>Executable vs Non-Executable BPMN: Clear Modeling for Automation &amp; Documentation<\/title>\n<meta name=\"description\" content=\"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready 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\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Executable vs Non-Executable BPMN: Clear Modeling for Automation &amp; Documentation\" \/>\n<meta property=\"og:description\" content=\"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/\",\"name\":\"Executable vs Non-Executable BPMN: Clear Modeling for Automation & Documentation\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:16:43+00:00\",\"description\":\"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Diagram Types Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Process Diagrams \u2014 Modeling Internal Workflows\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Executable vs. Non-Executable Process Models\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Executable vs Non-Executable BPMN: Clear Modeling for Automation & Documentation","description":"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready 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\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/","og_locale":"id_ID","og_type":"article","og_title":"Executable vs Non-Executable BPMN: Clear Modeling for Automation & Documentation","og_description":"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready design.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/","name":"Executable vs Non-Executable BPMN: Clear Modeling for Automation & Documentation","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:16:43+00:00","description":"Learn the key differences between executable BPMN process models and descriptive BPMN processes. Understand when to use each, and how to evolve a documentation model into an automation-ready design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/executable-vs-non-executable-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"BPMN Diagram Types Explained","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/"},{"@type":"ListItem","position":3,"name":"Process Diagrams \u2014 Modeling Internal Workflows","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/"},{"@type":"ListItem","position":4,"name":"Executable vs. Non-Executable Process Models"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/359","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/359\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/356"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=359"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}