{"id":575,"date":"2026-02-25T10:20:36","date_gmt":"2026-02-25T10:20:36","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/"},"modified":"2026-02-25T10:20:36","modified_gmt":"2026-02-25T10:20:36","slug":"bpmn-task-vs-subprocess-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/","title":{"rendered":"Tasks, Sub-Processes, and Call Activities Misapplied"},"content":{"rendered":"

Every time I review a BPMN diagram that spans multiple screens, I see the same red flag: a flat, unstructured chain of tasks. This is not a model\u2014it\u2019s a flowchart with baggage. The root of the problem? Misapplying tasks, sub-processes, and call activities. It\u2019s not that these elements are misunderstood\u2014they\u2019re just overused, misused, or ignored.<\/p>\n

Let me be clear: a BPMN task<\/strong> should represent a single, atomic unit of work. A sub-process<\/strong> groups multiple tasks into a single activity with a clear boundary. A call activity<\/strong> references a reusable process defined elsewhere. Confusing these leads to diagrams that are hard to read, debug, and maintain.<\/p>\n

Over the last 20 years, I\u2019ve watched teams spend weeks cleaning up models that should have been structured properly from day one. The good news? These are correctable. This chapter explains exactly when to use each, how to refactor messy models, and what to avoid. You\u2019ll walk away with a method to build layered, readable processes that stand the test of time.<\/p>\n

Understanding the Core Misconceptions<\/h2>\n

Many modelers assume that everything must be a task. This stems from a misunderstanding of BPMN\u2019s purpose: to represent business processes, not just system steps.<\/p>\n

When every activity is a task, you lose all hierarchy. The process becomes a long, monolithic line of work with no natural grouping. This is known as flattened BPMN process issues<\/strong>.<\/p>\n

I\u2019ve seen a customer onboarding process with 47 tasks in a single lane. No grouping. No structure. No way to summarize or validate. The modeler said, \u201cIt\u2019s all one workflow.\u201d But that\u2019s not how business works. Work is broken into logical chunks\u2014approval steps, document collection, verification checks.<\/p>\n

Sub-processes are not just \u201ca bunch of tasks.\u201d They are containers for logic that share a common purpose. Use them to group related activities under a single header, whether that\u2019s Verify Identity<\/code>, Process Payment<\/code>, or Review Application<\/code>.<\/p>\n

Why Flat Modeling Fails<\/h3>\n

Flattened BPMN process issues are not just inconvenient\u2014they\u2019re dangerous. They hide complexity, make validation difficult, and increase the risk of oversight.<\/p>\n

    \n
  • Missing logic becomes invisible in a long chain.<\/li>\n
  • Reusing common steps across multiple processes becomes impossible.<\/li>\n
  • Stakeholders can\u2019t grasp the process structure.<\/li>\n
  • Automation tools struggle to map a 50-task process without clear boundaries.<\/li>\n<\/ul>\n

    Think of it like trying to read a book where every chapter is merged into one 500-page block. You lose the sense of progress, and you can\u2019t refer back easily.<\/p>\n

    When to Use Each Element: A Practical Guide<\/h2>\n

    Let\u2019s clarify what each element is for\u2014and when not to use it.<\/p>\n

    Use a Simple Task When\u2026<\/h3>\n

    It\u2019s a single, atomic action with no internal logic. The work doesn\u2019t break down further.<\/p>\n

      \n
    • Enter customer name<\/li>\n
    • Send confirmation email<\/li>\n
    • Update database record<\/li>\n
    • Print approval letter<\/li>\n<\/ul>\n

      These are perfect for simple tasks. Never group them under a sub-process unless you\u2019re about to add more logic.<\/p>\n

      Use a Sub-Process When\u2026<\/h3>\n

      You\u2019re grouping multiple related tasks under a single logical block. The sub-process has a clear purpose and can be collapsed for readability.<\/p>\n

        \n
      • Verify customer identity<\/li>\n
      • Check credit score<\/li>\n
      • Review past transactions<\/li>\n<\/ul>\n

        This is a classic using BPMN subprocess correctly<\/strong> scenario. The sub-process can be collapsed into Review Application<\/em>\u2014a single node that hides the complexity.<\/p>\n

        When you use sub-processes, you\u2019re not just organizing\u2014it\u2019s a signal to readers: \u201cThis is a self-contained unit. Don\u2019t ask about the steps unless you need to.\u201d<\/p>\n

        Use a Call Activity When\u2026<\/h3>\n

        The same process logic is reused across multiple areas. It\u2019s a reference to a separate, defined process.<\/p>\n

        For example, a Verify Identity<\/em> sub-process might be used in Onboard Customer<\/em>, Open Account<\/em>, and Reopen Case<\/em>. Instead of duplicating it, use a call activity<\/strong> to reference a Verify Identity<\/em> process.<\/p>\n

        Call activities are not just for reuse\u2014they\u2019re for clarity. They make it obvious when a process is being reused and where to go to see the full details.<\/p>\n

        Refactoring a Flattened Process<\/h2>\n

        Let\u2019s walk through a real example.<\/p>\n

        Imagine a customer onboarding process with 47 flat tasks. One of them is: Check credit bureau report for fraud indicators<\/em>. It takes five steps: retrieve report, analyze data, flag anomalies, cross-check with internal rules, and report findings.<\/p>\n

        Instead of leaving this as five separate tasks, group them into a Verify Credit Risk<\/em> sub-process. Collapse it. Now the main flow reads:<\/p>\n

          \n
        1. Collect customer documents<\/li>\n
        2. Verify identity<\/li>\n
        3. Verify credit risk<\/li>\n
        4. Approve or reject application<\/li>\n<\/ol>\n

          The model is now readable. Stakeholders can focus on intent. Developers can drill down when needed.<\/p>\n

          Before: Flattened BPMN Process Issues<\/h3>\n

          Here\u2019s a simplified version of the original model:<\/p>\n

          \n[Start] \n\u2192 Collect documents \n\u2192 Verify identity \n\u2192 Retrieve credit report \n\u2192 Analyze data \n\u2192 Flag anomalies \n\u2192 Cross-check rules \n\u2192 Report findings \n\u2192 Approve or reject\n\u2192 [End]\n<\/code><\/pre>\n
          This is a textbook example of flattened BPMN process issues<\/strong>. Each step is a task, and the logic is buried in sequence.<\/p>\n
          After: Using Sub-Processes and Call Activities<\/h3>\n
          Now restructured:<\/p>\n
          \n[Start] \n\u2192 Collect documents \n\u2192 Verify identity \n\u2192 [Call Activity: Verify Credit Risk] \n\u2192 Approve or reject\n\u2192 [End]\n<\/code><\/pre>\n
          The Verify Credit Risk<\/code> call activity links to a separate, named process. It\u2019s reusable, auditable, and scalable.<\/p>\n
          And inside that model, we can use sub-processes to group logic for analysis and flagging.<\/p>\n
          Common Pitfalls and How to Avoid Them<\/h2>\n
          BPMN Call Activity Misuse<\/h3>\n
          I\u2019ve seen modelers use call activities for processes that are only used once. That\u2019s a red flag. If a process isn\u2019t reused, don\u2019t make it a call activity. It adds overhead without benefit.<\/p>\n
          Also, never use a call activity to reference a process that\u2019s already in the same diagram. It breaks transparency. If you need to reuse logic, keep the process separate.<\/p>\n
          Misusing Sub-Processes<\/h3>\n
          Sub-processes should not be used for every small group of tasks. If you have only two or three steps, ask: Is there a clear business purpose here?<\/p>\n
          For example: Send email<\/em> \u2192 Log email<\/em> \u2192 Mark as complete<\/em>. This is not a logical unit. It\u2019s just a sequence. Keep it flat.<\/p>\n
          But: Review application<\/em> \u2192 Check documents<\/em> \u2192 Verify identity<\/em> \u2192 Check credit history<\/em> \u2192 Make decision<\/em>. This is a sub-process.<\/p>\n
          Sub-processes are for grouping work that has a shared intent.<\/p>\n
          Decision Tree: Choosing the Right Element<\/h2>\n
          Here\u2019s a simple checklist to guide your decisions:<\/p>\n
            \n
          1. Is the work single and atomic?<\/strong> \u2192 Use a task<\/strong>.<\/li>\n
          2. Is the work a group of related steps with a clear goal?<\/strong> \u2192 Use a sub-process<\/strong>.<\/li>\n
          3. Is the same logic used in more than one process?<\/strong> \u2192 Use a call activity<\/strong>.<\/li>\n
          4. Does the sub-process contain more than 5\u20137 steps?<\/strong> \u2192 Break it into sub-sub-processes or use a call activity.<\/li>\n<\/ol>\n
            Follow this, and you\u2019ll avoid most BPMN task vs subprocess mistakes<\/strong>.<\/p>\n
            Frequently Asked Questions<\/h2>\n
            Can I use a sub-process inside a call activity?<\/h3>\n
            Yes\u2014but only if the called process is defined elsewhere. The sub-process is part of the called diagram, not the calling one. Don’t nest sub-processes inside a call activity in the main flow unless the called process is structured that way.<\/p>\n
            What if my process is too big to fit on one page?<\/h3>\n
            That\u2019s a sign it\u2019s not a single process. Split it. Use a call activity<\/strong> to reference a subprocess that belongs to a different scope. Or, use a collaboration diagram<\/strong> with pools and message flows.<\/p>\n
            Is it okay to have a sub-process with only one task?<\/h3>\n
            Technically yes, but it\u2019s a red flag. If a sub-process has only one task, why not just use a task? Use sub-processes to group meaningful logic, not to pad structure.<\/p>\n
            Should I always use call activities for reusable logic?<\/h3>\n
            Yes. If the same sequence of steps appears in multiple processes, make it a call activity. It improves consistency, reduces duplication, and makes changes easier.<\/p>\n
            How do I know when to collapse a sub-process?<\/h3>\n
            When a sub-process has more than 5\u20137 steps, or when it\u2019s too complex to describe in one sentence. If stakeholders can\u2019t understand the purpose at a glance, it should be broken down.<\/p>\n
            Can a sub-process be used for parallel processing?<\/h3>\n
            Yes\u2014use a parallel gateway<\/strong> inside a sub-process to manage concurrent flows. But avoid using sub-processes just to group parallel tasks. Use them when the group has a shared business goal.<\/p>\n","protected":false},"excerpt":{"rendered":"
            Every time I review  […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":571,"menu_order":3,"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-575","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nBPMN Task vs Subprocess Mistakes: Fix These Common Errors<\/title>\n<meta name=\"description\" content=\"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.\" \/>\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\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Task vs Subprocess Mistakes: Fix These Common Errors\" \/>\n<meta property=\"og:description\" content=\"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/\",\"name\":\"BPMN Task vs Subprocess Mistakes: Fix These Common Errors\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:20:36+00:00\",\"description\":\"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Notation Misuse and Semantic Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Tasks, Sub-Processes, and Call Activities Misapplied\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Task vs Subprocess Mistakes: Fix These Common Errors","description":"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.","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\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/","og_locale":"zh_TW","og_type":"article","og_title":"BPMN Task vs Subprocess Mistakes: Fix These Common Errors","og_description":"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"7 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/","name":"BPMN Task vs Subprocess Mistakes: Fix These Common Errors","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:20:36+00:00","description":"Fix common BPMN task vs subprocess mistakes. Learn when to use simple tasks, sub-processes, and call activities to avoid flattened BPMN process issues and improve model clarity and maintainability.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-task-vs-subprocess-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Notation Misuse and Semantic Errors","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Tasks, Sub-Processes, and Call Activities Misapplied"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/575","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/575\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/571"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=575"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=575"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}