{"id":518,"date":"2026-02-25T10:19:27","date_gmt":"2026-02-25T10:19:27","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/"},"modified":"2026-02-25T10:19:27","modified_gmt":"2026-02-25T10:19:27","slug":"nested-cmmn-subcase-strategies","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/","title":{"rendered":"Nested Case Models and Sub-Case Strategies"},"content":{"rendered":"<p>When a case isn\u2019t just a single flow\u2014it\u2019s a system of interconnected decisions, roles, and data, the real power of CMMN emerges through nesting. I\u2019ve worked with dozens of enterprise-grade models where a single case plan wasn\u2019t enough. It wasn\u2019t just about flexibility; it was about structure within chaos.<\/p>\n<p>Think of a medical disability review. The main case exists for the individual, but it branches into subcases: one for diagnostics, another for legal compliance, and a third for employer coordination. Each subcase has its own tasks, data, and lifecycle\u2014but they\u2019re all tied together under the parent case. That\u2019s where nested CMMN becomes essential.<\/p>\n<p>This chapter focuses on how to build and manage these hierarchical models effectively. You\u2019ll learn how to define CMMN subcase relationships, link data across levels, and trigger activation based on real-world dependencies. The goal isn\u2019t to automate every step\u2014but to design models that adapt intelligently and reflect the true complexity of expert work.<\/p>\n<h2>Understanding the Need for Nested Case Models<\/h2>\n<p>Not every case is a simple linear journey. Some require parallel decision paths, independent workflows, or shared data resources. That\u2019s where nested CMMN steps in.<\/p>\n<p>Consider a legal case involving multiple parties. The lead case might include subcases for discovery, motion filing, and settlement negotiation. Each operates semi-independently but shares common data\u2014like case files, evidence logs, and court dates.<\/p>\n<p>Without nesting, you\u2019d either over-bundle tasks into one monolithic case plan or duplicate logic across multiple models. That leads to inconsistency and maintenance nightmares.<\/p>\n<p>Nested CMMN solves this by allowing a case to contain child cases\u2014each with its own structure, case file, and activation rules. These are not parallel processes. They are <strong>subcases<\/strong>, deeply tied to the parent through data and control dependencies.<\/p>\n<h3>When to Use Nested CMMN<\/h3>\n<p>Not every case needs nesting. But when any of these apply, consider it:<\/p>\n<ul>\n<li>Multiple stakeholders manage different parts of the same case.<\/li>\n<li>Tasks in one area depend on outcomes from another, but execution isn\u2019t sequential.<\/li>\n<li>Sub-activities involve distinct roles, documentation, and approval chains.<\/li>\n<li>Some parts of the case need to be created and managed only after specific events occur.<\/li>\n<\/ul>\n<h2>Structuring CMMN Sub-Case Relationships<\/h2>\n<p>Creating a subcase in CMMN means defining it as a child of the parent case. In visual modeling tools like Visual Paradigm, this is done through a dedicated <code>Sub-Case<\/code> element, attached to the parent case plan.<\/p>\n<p>Here\u2019s how it works in practice:<\/p>\n<ol>\n<li>Define the parent case\u2014e.g., \u201cInsurance Claim Review.\u201d<\/li>\n<li>Identify distinct subcases\u2014e.g., \u201cMedical Evidence Evaluation,\u201d \u201cFraud Detection Review,\u201d and \u201cSettlement Negotiation.\u201d<\/li>\n<li>Link each subcase using the <code>Child Case<\/code> dependency in the case plan model.<\/li>\n<li>Set activation conditions using sentries (e.g., \u201cWhen medical report is submitted\u201d).<\/li>\n<li>Define data sharing through shared case file items.<\/li>\n<\/ol>\n<p>Each subcase can have its own stages, tasks, and milestones. But they are all governed by the parent case\u2019s lifecycle and rules.<\/p>\n<h3>Key Data Flow Patterns in Nested CMMN<\/h3>\n<p>Data must flow between parent and child cases. The most effective way? Use <strong>case file items<\/strong> that are accessible across levels.<\/p>\n<p>For example:<\/p>\n<ul>\n<li>Parent case stores: <code>Claim ID<\/code>, <code>Claimant Name<\/code>, <code>Claim Date<\/code>.<\/li>\n<li>Subcase \u201cFraud Detection\u201d needs <code>Claim Amount<\/code>, <code>Claim Date<\/code>, and <code>History of Past Claims<\/code>.<\/li>\n<li>These items are shared via case file references\u2014no duplication, no drift.<\/li>\n<\/ul>\n<p>Use the <code>Shared Data<\/code> attribute in the case file to mark items that should be available to child cases. This avoids redundant data entry and ensures consistency.<\/p>\n<h2>Managing CMMN Dependencies and Activation<\/h2>\n<p>One of the most common challenges in nested models is controlling <strong>CMMN dependencies<\/strong>. A child case shouldn\u2019t activate prematurely. It shouldn\u2019t block the parent either.<\/p>\n<p>Activation is governed by sentries\u2014either event-based or condition-based. Here\u2019s how to manage it:<\/p>\n<h3>Activation Strategies for CMMN Subcases<\/h3>\n<p>Choose one of these to control when a subcase becomes active:<\/p>\n<ol>\n<li><strong>Event-Driven Activation<\/strong>: The subcase starts when a specific event occurs\u2014e.g., \u201cWhen the medical report is uploaded.\u201d<\/li>\n<li><strong>Condition-Based Activation<\/strong>: The subcase activates when a business rule evaluates to true\u2014e.g., \u201cIf claim amount &gt; $50,000, then activate fraud review.\u201d<\/li>\n<li><strong>Manual Activation<\/strong>: A user explicitly triggers the subcase via a button or action. Useful for discretionary workflows.<\/li>\n<\/ol>\n<p>Use <code>Entry Criteria<\/code> on the subcase to define when it\u2019s eligible. But remember: eligibility \u2260 activation. The user (or system) must still explicitly start it\u2014unless you use a <code>Direct Activation<\/code> rule.<\/p>\n<p>Here\u2019s a practical example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Subcase<\/th>\n<th>Activation Trigger<\/th>\n<th>Dependency Type<\/th>\n<\/tr>\n<tr>\n<td>Fraud Detection<\/td>\n<td>Claim amount &gt; $100,000<\/td>\n<td>Conditional<\/td>\n<\/tr>\n<tr>\n<td>Medical Review<\/td>\n<td>Medical report received<\/td>\n<td>Event-driven<\/td>\n<\/tr>\n<tr>\n<td>Settlement Negotiation<\/td>\n<td>Approved by legal team<\/td>\n<td>Dependency on parent task<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Each of these defines a different kind of <strong>CMMN dependencies<\/strong>. The key is to choose the right one based on business needs, not just technical convenience.<\/p>\n<h2>Best Practices for Nested CMMN Modeling<\/h2>\n<p>Modeling nested cases is powerful\u2014but easy to overcomplicate. Here are the rules I\u2019ve learned from years of working with teams:<\/p>\n<ul>\n<li><strong>Keep subcases focused<\/strong>: Each should handle one core business function. Avoid merging unrelated workflows into one subcase.<\/li>\n<li><strong>Use clear naming conventions<\/strong>: e.g., \u201cClaim_Review_Fraud_Detection\u201d helps distinguish roles and purpose.<\/li>\n<li><strong>Minimize cross-case data duplication<\/strong>: Share only what\u2019s necessary. Use references, not copies.<\/li>\n<li><strong>Document activation logic<\/strong>: Don\u2019t assume users know why a subcase appears. Add comments or annotations.<\/li>\n<li><strong>Validate with real users<\/strong>: Run simulations with case managers. See where the model breaks\u2014especially in dependency logic.<\/li>\n<\/ul>\n<p>One team I worked with once created seven subcases under a single parent. It looked impressive\u2014but the model failed in testing. Why? Because activation rules were too complex, and no one could track which subcase was responsible for what. I simplified it to three core subcases with clear triggers. The performance improved, and user satisfaction rose.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced modelers fall into traps with nested CMMN. Here are the top three:<\/p>\n<ol>\n<li><strong>Over-reliance on automatic activation<\/strong>: Just because a condition is met doesn\u2019t mean the subcase should start. Always ask: \u201cWho makes this decision?\u201d<\/li>\n<li><strong>Ignoring data ownership<\/strong>: If the parent case owns a data item, don\u2019t let a subcase modify it without authorization. Add a <code>Read\/Write Rule<\/code> in the case file.<\/li>\n<li><strong>Missing lifecycle coordination<\/strong>: A subcase might finish, but the parent stays open. Define exit criteria or auto-closure rules.<\/li>\n<\/ol>\n<p>Always ask: \u201cCan this subcase be managed independently?\u201d If yes, it might be better as a standalone case. If no\u2014it belongs nested.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between a CMMN subcase and a BPMN subprocess?<\/h3>\n<p>A CMMN subcase is a full case in its own right\u2014complete with stages, tasks, and data. A BPMN subprocess is a sub-flow within a process. Subcases are autonomous by design; subprocesses are part of a larger flow.<\/p>\n<h3>Can CMMN dependencies exist across multiple levels?<\/h3>\n<p>Yes. Subcases can depend on other subcases, or on tasks within the parent. Use sentries and case file items to model cross-level dependencies. Just keep the logic transparent.<\/p>\n<h3>How do I prevent a subcase from triggering prematurely?<\/h3>\n<p>Set a clear entry criterion using a condition or event. Don\u2019t rely on default activation. Use a manual trigger unless the business rule is unambiguous and safe.<\/p>\n<h3>Are nested CMMN models harder to test?<\/h3>\n<p>They are more complex, yes. But with proper activation rules and data sharing, they are no harder to simulate than flat models. Use visual simulation tools to walk through scenarios.<\/p>\n<h3>Can I reuse the same subcase in multiple parent cases?<\/h3>\n<p>Yes\u2014by making it a <code>Reusable Subcase<\/code> element. Just ensure the data model and rules are generic enough to apply across contexts. Be cautious with task-specific dependencies.<\/p>\n<h3>What\u2019s the impact of nesting on performance in a case management system?<\/h3>\n<p>Nesting adds overhead in terms of data coordination and state tracking. But it\u2019s usually negligible in modern systems. The real cost is in model complexity and maintenance. Balance depth with clarity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a case isn\u2019t just a single flow\u2014it\u2019s a system of interconnected decisions, roles, and data, the real power of CMMN emerges through nesting. I\u2019ve worked with dozens of enterprise-grade models where a single case plan wasn\u2019t enough. It wasn\u2019t just about flexibility; it was about structure within chaos. Think of a medical disability review. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":517,"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-518","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>Nested CMMN: Mastering Sub-Case Design<\/title>\n<meta name=\"description\" content=\"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.\" \/>\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\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Nested CMMN: Mastering Sub-Case Design\" \/>\n<meta property=\"og:description\" content=\"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/\",\"name\":\"Nested CMMN: Mastering Sub-Case Design\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:19:27+00:00\",\"description\":\"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CMMN Explained: A Practical Guide for Modelers\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Advanced Modeling and Integration Practices\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Nested Case Models and Sub-Case Strategies\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Nested CMMN: Mastering Sub-Case Design","description":"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.","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\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/","og_locale":"de_DE","og_type":"article","og_title":"Nested CMMN: Mastering Sub-Case Design","og_description":"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/","name":"Nested CMMN: Mastering Sub-Case Design","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:19:27+00:00","description":"Learn how to design nested CMMN models and manage CMMN subcase relationships with precision. Master data dependencies, activation logic, and hierarchical workflows for complex case management.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/nested-cmmn-subcase-strategies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"CMMN Explained: A Practical Guide for Modelers","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/"},{"@type":"ListItem","position":3,"name":"Advanced Modeling and Integration Practices","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/cmmn-explained-practical-guide-for-modelers\/advanced-cmmn\/"},{"@type":"ListItem","position":4,"name":"Nested Case Models and Sub-Case Strategies"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/518\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/517"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=518"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}