{"id":380,"date":"2026-02-25T10:16:53","date_gmt":"2026-02-25T10:16:53","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/"},"modified":"2026-02-25T10:16:53","modified_gmt":"2026-02-25T10:16:53","slug":"bpmn-diagram-selection-checklist","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/","title":{"rendered":"BPMN Diagram Selection Checklist"},"content":{"rendered":"<p>Most teams don\u2019t struggle with modeling\u2014they struggle with choosing the right view. The moment you realize that a single process can be shown in four different ways, the real challenge begins: which one to use, when, and for whom?<\/p>\n<p>After 20 years of modeling in regulated industries, fintech, and global supply chains, I\u2019ve seen the same mistake repeated: using a process diagram to explain a cross-organizational handoff, or a choreography diagram to train a frontline employee. The result? Confusion, misalignment, and wasted time.<\/p>\n<p>This checklist isn\u2019t a rigid rulebook. It\u2019s a decision-making compass\u2014practical, experience-tested, and built to help you pick the right BPMN diagram type based on real-world constraints: stakeholder needs, automation goals, and integration complexity.<\/p>\n<h2>Ask These 5 Questions Before Choosing a Diagram Type<\/h2>\n<p>Start with clarity on purpose. Every diagram should answer one primary question. If it doesn\u2019t, it\u2019s likely the wrong type.<\/p>\n<h3>1. Who is the primary audience?<\/h3>\n<p>Are you speaking to a developer, a compliance officer, a business analyst, or an executive?<\/p>\n<ul>\n<li><strong>Developers or technical teams<\/strong> need executable models. Use a <strong>process diagram<\/strong> with service tasks, data objects, and clear sequence flows.<\/li>\n<li><strong>Executives or business leaders<\/strong> care about ownership, timing, and outcomes. Use a <strong>conversation diagram<\/strong> to show who communicates with whom and about what.<\/li>\n<li><strong>Legal or compliance teams<\/strong> need precise message exchange rules. A <strong>choreography diagram<\/strong> is ideal\u2014no internal logic, just message order and obligations.<\/li>\n<li><strong>Operations or cross-functional teams<\/strong> need to see handoffs and responsibilities. A <strong>collaboration diagram<\/strong> with pools and message flows is most effective.<\/li>\n<\/ul>\n<h3>2. What level of detail is required?<\/h3>\n<p>Too much detail overwhelms. Too little leaves gaps. The right diagram type naturally limits scope.<\/p>\n<ul>\n<li><strong>Internal workflow with decision logic<\/strong>? Use a <strong>process diagram<\/strong>\u2014it\u2019s built for gateways, loops, and conditional paths.<\/li>\n<li><strong>Showing only message exchanges between systems<\/strong>? A <strong>choreography diagram<\/strong> keeps the focus on timing and order, not internal steps.<\/li>\n<li><strong>Summarizing multiple interactions into a single topic<\/strong>? A <strong>conversation diagram<\/strong> groups related messages under a common theme\u2014like \u201cOrder Confirmation\u201d or \u201cClaim Escalation.\u201d<\/li>\n<\/ul>\n<h3>3. Is automation or integration the goal?<\/h3>\n<p>If the model will be deployed, the diagram type must support execution.<\/p>\n<ul>\n<li><strong>Planning to execute the process in a BPM engine<\/strong>? Only a <strong>process diagram<\/strong> with executable elements (e.g., service tasks, timers, data inputs) can be deployed.<\/li>\n<li><strong>Designing a system interface contract<\/strong>? Use a <strong>choreography diagram<\/strong> to define the expected message sequence between systems\u2014this becomes the contract.<\/li>\n<li><strong>Mapping integration points across teams<\/strong>? A <strong>collaboration diagram<\/strong> clearly shows message flows and responsibilities between pools.<\/li>\n<\/ul>\n<h3>4. Are multiple organizations or systems involved?<\/h3>\n<p>When more than one entity is in the loop, the diagram type must reflect that reality.<\/p>\n<ul>\n<li><strong>Two departments within the same company<\/strong>? Use a <strong>collaboration diagram<\/strong> with lanes in a single pool or separate pools.<\/li>\n<li><strong>Partners, suppliers, or external vendors<\/strong>? A <strong>choreography diagram<\/strong> defines the agreed-upon behavior without exposing internal processes.<\/li>\n<li><strong>Multiple teams with overlapping responsibilities<\/strong>? A <strong>conversation diagram<\/strong> simplifies the view by grouping interactions into logical topics.<\/li>\n<\/ul>\n<h3>5. Is this a one-time documentation effort or part of an ongoing model?<\/h3>\n<p>Long-term models need consistency. The diagram type should support traceability and reuse.<\/p>\n<ul>\n<li><strong>Documenting a legacy process<\/strong>? A <strong>process diagram<\/strong> is easiest to create and understand.<\/li>\n<li><strong>Building a living model for continuous improvement<\/strong>? Use a <strong>collaboration or choreography diagram<\/strong> as the source of truth, then derive process diagrams from it.<\/li>\n<li><strong>Creating a model for governance or audit<\/strong>? A <strong>conversation diagram<\/strong> provides a high-level audit trail of communication flows.<\/li>\n<\/ul>\n<h2>Decision Matrix: Match Your Scenario to the Right Diagram<\/h2>\n<p>Use this table to quickly map common business scenarios to the most appropriate BPMN diagram type. It\u2019s based on real-world modeling projects across banking, healthcare, and logistics.<\/p>\n<table border=\"1\" cellpadding=\"6\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Business Scenario<\/th>\n<th>Recommended Diagram Type<\/th>\n<th>Why This Works<\/th>\n<\/tr>\n<tr>\n<td>Onboarding a new employee with HR, IT, and Finance involved<\/td>\n<td>Collaboration Diagram<\/td>\n<td>Clearly shows message flows between departments without detailing internal steps.<\/td>\n<\/tr>\n<tr>\n<td>Defining the message sequence between a bank and a payment gateway<\/td>\n<td>Choreography Diagram<\/td>\n<td>Establishes a contract for message exchange without revealing internal logic.<\/td>\n<\/tr>\n<tr>\n<td>Showing how customer service escalates claims across levels<\/td>\n<td>Process Diagram<\/td>\n<td>Best for modeling internal decision points, loops, and conditional routing.<\/td>\n<\/tr>\n<tr>\n<td>Presenting the high-level communication structure to a board of directors<\/td>\n<td>Conversation Diagram<\/td>\n<td>Summarizes key interactions into digestible topics like \u201cOrder Fulfillment\u201d or \u201cDispute Resolution.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Automating a loan approval workflow with system triggers<\/td>\n<td>Process Diagram (Executable)<\/td>\n<td>Supports deployment to a BPM engine with service tasks and data mapping.<\/td>\n<\/tr>\n<tr>\n<td>Documenting how a supplier and retailer exchange order and delivery confirmations<\/td>\n<td>Choreography Diagram<\/td>\n<td>Focuses on message order and obligations\u2014perfect for contractual clarity.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>When to Use Multiple Diagram Types Together<\/h2>\n<p>Don\u2019t treat diagram types as mutually exclusive. In mature modeling practices, they work in concert.<\/p>\n<p>For example, start with a <strong>choreography diagram<\/strong> to define the contract between two systems. Then, create a <strong>collaboration diagram<\/strong> to show how each party\u2019s internal process aligns with that contract. Finally, build a <strong>process diagram<\/strong> for each participant to model their internal logic.<\/p>\n<p>This layered approach ensures alignment. If the choreography says \u201cSystem A sends confirmation before System B processes,\u201d the process diagrams for both systems must reflect that sequence.<\/p>\n<p>Use a <strong>conversation diagram<\/strong> as a top-level map to show the entire communication landscape\u2014ideal for architecture reviews or stakeholder onboarding.<\/p>\n<h2>Common Pitfalls to Avoid<\/h2>\n<p>Even with the checklist, mistakes happen. Here\u2019s what to watch for:<\/p>\n<ul>\n<li><strong>Mixing sequence and message flows<\/strong>: Sequence flows belong inside a pool. Message flows cross pools. Confusing them breaks the model\u2019s integrity.<\/li>\n<li><strong>Overloading a single diagram<\/strong>: A process diagram with 20 lanes and 100 elements is unreadable. Break it into collaboration or conversation views.<\/li>\n<li><strong>Using choreography for internal process design<\/strong>: Choreography hides internal steps. If you need to model decisions or loops, use a process diagram instead.<\/li>\n<li><strong>Choosing the wrong diagram for the audience<\/strong>: Executives don\u2019t need gateways. Developers don\u2019t need conversation nodes. Match the diagram to the reader\u2019s role.<\/li>\n<\/ul>\n<h2>Final Advice: Make This Checklist Part of Your Practice<\/h2>\n<p>Every time you start a new modeling session, run through this checklist. It takes under two minutes, but it prevents hours of rework.<\/p>\n<p>Teams that adopt this approach report faster stakeholder alignment, fewer rework cycles, and stronger model governance. It\u2019s not about perfection\u2014it\u2019s about clarity.<\/p>\n<p>And remember: the goal isn\u2019t to use every diagram type. It\u2019s to use the right one, at the right time, for the right person.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Which BPMN diagram should I use for a customer onboarding process?<\/h3>\n<p>If you\u2019re modeling the internal steps\u2014like document verification, background checks, and account setup\u2014use a <strong>process diagram<\/strong>. If the process involves multiple departments or external partners, add a <strong>collaboration diagram<\/strong> to show message flows. For executives, a <strong>conversation diagram<\/strong> summarizing \u201cCustomer Onboarding\u201d as a single communication topic works best.<\/p>\n<h3>Can I use a process diagram to show interactions between two companies?<\/h3>\n<p>Not effectively. A process diagram is designed for internal workflows. If two companies are involved, use a <strong>collaboration diagram<\/strong> with separate pools. This clearly separates responsibilities and shows message flows between them. A process diagram would incorrectly imply a single owner.<\/p>\n<h3>When should I use a choreography diagram instead of a collaboration diagram?<\/h3>\n<p>Use a <strong>choreography diagram<\/strong> when you want to define a contract or agreement between participants without revealing internal logic. It\u2019s ideal for system-to-system integration, legal contracts, or when the internal processes are unknown or irrelevant. Use a <strong>collaboration diagram<\/strong> when you need to show both the internal process and the interactions between participants.<\/p>\n<h3>Is a conversation diagram just a simplified collaboration diagram?<\/h3>\n<p>Yes\u2014but with a purpose. A conversation diagram is a strategic summary. It groups related message exchanges into conversation nodes (e.g., \u201cOrder Confirmation,\u201d \u201cInvoice Dispute\u201d) and removes internal details. It\u2019s not a simplified version of collaboration\u2014it\u2019s a different level of abstraction, designed for high-level communication and governance.<\/p>\n<h3>What if I\u2019m not sure which diagram to use?<\/h3>\n<p>Start with the audience. Ask: \u201cWho will read this, and what do they need to understand?\u201d If it\u2019s a developer, go process. If it\u2019s a business stakeholder, start with conversation. Then refine based on detail and automation needs. The checklist is your guide\u2014not a gatekeeper.<\/p>\n<h3>How do I keep multiple diagrams consistent?<\/h3>\n<p>Use a single model repository (like Visual Paradigm) and link diagrams through shared participants, message interfaces, and choreography tasks. Name pools and message flows consistently across views. Use traceability features to link a conversation node to its underlying collaboration or choreography diagram. This ensures that changes in one view are reflected where needed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams don\u2019t struggle with modeling\u2014they struggle with choosing the right view. The moment you realize that a single process can be shown in four different ways, the real challenge begins: which one to use, when, and for whom? After 20 years of modeling in regulated industries, fintech, and global supply chains, I\u2019ve seen the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":379,"menu_order":0,"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-380","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 Diagram Selection Checklist<\/title>\n<meta name=\"description\" content=\"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.\" \/>\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-diagram-best-practices\/bpmn-diagram-selection-checklist\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Diagram Selection Checklist\" \/>\n<meta property=\"og:description\" content=\"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/\" \/>\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-diagram-best-practices\/bpmn-diagram-selection-checklist\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/\",\"name\":\"BPMN Diagram Selection Checklist\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:16:53+00:00\",\"description\":\"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/#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\":\"Best Practices and Professional Standards\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"BPMN Diagram Selection Checklist\"}]},{\"@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":"BPMN Diagram Selection Checklist","description":"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.","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-diagram-best-practices\/bpmn-diagram-selection-checklist\/","og_locale":"id_ID","og_type":"article","og_title":"BPMN Diagram Selection Checklist","og_description":"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/","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-diagram-best-practices\/bpmn-diagram-selection-checklist\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/","name":"BPMN Diagram Selection Checklist","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:16:53+00:00","description":"Use this BPMN diagram selection checklist to choose the right diagram type for your audience, detail level, and automation goals. A practical guide to avoid confusion and improve process clarity.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/bpmn-diagram-selection-checklist\/#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":"Best Practices and Professional Standards","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-best-practices\/"},{"@type":"ListItem","position":4,"name":"BPMN Diagram Selection Checklist"}]},{"@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\/380","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\/380\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/379"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=380"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}