{"id":522,"date":"2026-02-25T10:19:28","date_gmt":"2026-02-25T10:19:28","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/"},"modified":"2026-03-02T09:06:33","modified_gmt":"2026-03-02T09:06:33","slug":"cmmn-support-case-dynamic-ticket-management","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/","title":{"rendered":"Customer Support Management Case"},"content":{"rendered":"<p>Most support cases don\u2019t follow a fixed path. They evolve based on user behavior, urgency, and expert judgment. This is where CMMN support case modeling shines\u2014not as a rigid sequence, but as a living structure that adapts to real-time triggers.<\/p>\n<p>When modeling a customer support case, I\u2019ve found that teams often misunderstand the role of tasks: they\u2019re not just steps to do, but dynamic elements that activate based on conditions. The real power lies in how tasks are triggered by events, not just time or sequence.<\/p>\n<p>By the end of this guide, you\u2019ll know how to model a full support request lifecycle using the CMMN Case Plan Model\u2014complete with dynamic entry conditions, escalation logic, and flexible task sequencing. You\u2019ll walk away with a working example that mirrors real-world ticket management CMMN practices.<\/p>\n<h2>Mapping the Customer Support Case Lifecycle<\/h2>\n<p>Let\u2019s start with a simple scenario: a customer reports a login failure. This isn\u2019t a one-size-fits-all fix. The path forward depends on the ticket\u2019s severity, user history, and response time.<\/p>\n<p>Begin by defining the case\u2019s core structure: stages, tasks, milestones, and case file items.<\/p>\n<h3>Define the Case Plan Structure<\/h3>\n<p>Start with the top-level case plan. In Visual Paradigm, this means creating a new CMMN Case Plan Model.<\/p>\n<p>Use three clear stages:<\/p>\n<ul>\n<li><strong>Initial Assessment<\/strong> \u2013 Verify ticket validity and gather initial data.<\/li>\n<li><strong>Resolution Attempts<\/strong> \u2013 Execute diagnostic and fix workflows.<\/li>\n<li><strong>Escalation and Closure<\/strong> \u2013 If unresolved, escalate; otherwise, close.<\/li>\n<\/ul>\n<p>Each stage is a container for tasks. But remember: stages are not just labels. They communicate progress and help the support team visualize where the case stands.<\/p>\n<h3>Modeling Dynamic Task Triggers<\/h3>\n<p>Tasks in CMMN aren\u2019t manually triggered. They\u2019re activated by sentries\u2014conditions that evaluate in real time.<\/p>\n<p>Here\u2019s how I model dynamic task triggers:<\/p>\n<ol>\n<li>Define a task called <em>Verify User Credentials<\/em>.<\/li>\n<li>Attach a sentry with the condition: <code>ticket.severity == \"High\" OR ticket.firstResponse &gt; 4 hours<\/code>.<\/li>\n<li>Set the sentry to <strong>wait for<\/strong> the condition to be true.<\/li>\n<\/ol>\n<p>This means the task won\u2019t appear in the task list unless the condition is met. It\u2019s not a rule\u2014it\u2019s a trigger.<\/p>\n<p>For example, if a high-severity ticket is flagged, the system automatically activates diagnostics tasks. But if it\u2019s low priority and no escalation is detected, the task stays hidden until needed.<\/p>\n<p>Do this consistently: use sentries to control visibility, not task lists.<\/p>\n<h2>Escalation Logic: From Support to Experts<\/h2>\n<p>Escalation is not a manual step. It\u2019s a dynamic state transition driven by time, status, and data.<\/p>\n<p>Model this with a two-part approach:<\/p>\n<h3>Set Up Escalation Criteria<\/h3>\n<p>Create a milestone named <em>Escalation Deadline<\/em> with a due date rule:<\/p>\n<ul>\n<li>Due in 8 hours for high-severity tickets.<\/li>\n<li>Due in 48 hours for medium-severity tickets.<\/li>\n<li>No deadline for low-severity.<\/li>\n<\/ul>\n<p>Use a case file item: <code>ticket.escalationDeadline<\/code>.<\/p>\n<p>Then, attach a sentry to the <em>Escalate to Senior Support<\/em> task:<\/p>\n<pre><code>caseFile.escalationDeadline &lt;= now() AND caseFile.status == \"In Progress\"<\/code><\/pre>\n<p>This condition ensures the task only activates when the deadline is near and the case hasn\u2019t been resolved.<\/p>\n<h3>Dynamic Task Reassignment<\/h3>\n<p>When escalation is triggered, the task gets reassigned. But in CMMN, reassignment isn\u2019t a task\u2014it\u2019s a property of the case.<\/p>\n<p>Set the <em>Assignee<\/em> field in the task to:<\/p>\n<ul>\n<li><code>escalationTeam<\/code> for high-severity cases.<\/li>\n<li><code>seniorSupport<\/code> for medium.<\/li>\n<\/ul>\n<p>Use a case file condition to dynamically assign team roles based on ticket severity.<\/p>\n<p>Why it works: it removes manual handover. The system knows who to assign the task to\u2014based on logic, not hierarchy.<\/p>\n<h2>Using Case File Items for Context<\/h2>\n<p>Support cases are data-rich. The case file is where you store and manage all information.<\/p>\n<p>Define key items:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Item<\/th>\n<th>Type<\/th>\n<th>Use Case<\/th>\n<\/tr>\n<tr>\n<td>ticket.severity<\/td>\n<td>String (High\/Medium\/Low)<\/td>\n<td>Drives task visibility and escalation<\/td>\n<\/tr>\n<tr>\n<td>ticket.resolutionTime<\/td>\n<td>DateTime<\/td>\n<td>Tracks performance metrics<\/td>\n<\/tr>\n<tr>\n<td>ticket.history<\/td>\n<td>List of Events<\/td>\n<td>Logs all actions and decisions<\/td>\n<\/tr>\n<tr>\n<td>ticket.escalationTeam<\/td>\n<td>Team<\/td>\n<td>Auto-assigns when needed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These items aren\u2019t static. They\u2019re updated as the case evolves.<\/p>\n<p>For example: when a technician logs a diagnostic step, the <code>ticket.history<\/code> list is updated automatically. This ensures full auditability without requiring extra workflow steps.<\/p>\n<h2>Best Practices for CMMN Service Desk Example<\/h2>\n<p>After modeling multiple support cases, I\u2019ve distilled five key principles for robust, maintainable CMMN service desk example models:<\/p>\n<ol>\n<li><strong>Use sentries, not time-based triggers<\/strong> \u2013 Let the system evaluate conditions in real time. Don\u2019t rely on \u201cafter 4 hours\u201d unless it\u2019s part of a milestone.<\/li>\n<li><strong>Keep tasks atomic<\/strong> \u2013 Each task should represent one logical action: <em>contact user<\/em>, <em>check logs<\/em>, <em>run test script<\/em>.<\/li>\n<li><strong>Model severity early<\/strong> \u2013 Define <code>ticket.severity<\/code> as a case file item at model start. It will be used across multiple sentries.<\/li>\n<li><strong>Use milestones only for time-bound checkpoints<\/strong> \u2013 These help track SLA compliance, not just document progress.<\/li>\n<li><strong>Log decisions in the case file<\/strong> \u2013 Every critical decision\u2014like escalating to engineering\u2014should be recorded for audit and analysis.<\/li>\n<\/ol>\n<p>These aren\u2019t rules. They\u2019re patterns I\u2019ve seen work across industries: from SaaS platforms to government helpdesks.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced modelers fall into traps. Here are three I\u2019ve seen most often:<\/p>\n<ul>\n<li><strong>Overusing tasks<\/strong> \u2013 Too many tasks create confusion. Use stages to group related tasks. A task should be a single action, not a process.<\/li>\n<li><strong>Hardcoding escalation paths<\/strong> \u2013 Avoid \u201cif severity = high, then escalate.\u201d Instead, use dynamic sentries and case file logic to reflect real-time rules.<\/li>\n<li><strong>Ignoring case file visibility<\/strong> \u2013 The case file is the source of truth. If a task needs data, it should come from the file\u2014never be assumed.<\/li>\n<\/ul>\n<p>When I first modeled a support case for a telecom client, I used 12 tasks. After refactoring with stages and sentries, it dropped to 7\u2014with better clarity and fewer exceptions.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How does CMMN support case differ from BPMN in support ticketing?<\/h3>\n<p>BPMN is ideal for structured, repeatable processes\u2014like a standard onboarding workflow. CMMN is built for uncertainty. In support, the path isn\u2019t known in advance. CMMN lets you model what <em>could<\/em> happen, based on real-time data. You\u2019re not designing a flow; you\u2019re designing a response system.<\/p>\n<h3>Can I use CMMN for both IT service desk and customer support?<\/h3>\n<p>Absolutely. The same modeling principles apply. Whether it\u2019s a login failure or a refund request, the case structure\u2014stages, tasks, sentries, case file\u2014remains consistent. You adapt the data and conditions to the domain.<\/p>\n<h3>How do I handle multiple support agents working on a single case?<\/h3>\n<p>Assign tasks dynamically using the case file. For example, set <code>task.assignee<\/code> to <code>currentAgent<\/code> or <code>escalationTeam<\/code> based on severity. CMMN doesn&rsquo;t require a dedicated agent role\u2014it works with organizational roles.<\/p>\n<h3>What if a sentry condition is never met?<\/h3>\n<p>That\u2019s fine. The task won\u2019t activate. CMMN is event-driven, not time-driven. If the condition never evaluates to true, the task remains inactive. This prevents unnecessary work and keeps the interface clean.<\/p>\n<h3>Is CMMN scalable for enterprise-level support teams?<\/h3>\n<p>Yes. Many large enterprises use nested CMMN models\u2014where one case spawns sub-cases for diagnostics, engineering, or compliance. The key is to keep the main model focused on control logic, while delegating detailed workflows to sub-cases. This way, the model stays manageable and maintainable.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most support cases don\u2019t follow a fixed path. They evolve based on user behavior, urgency, and expert judgment. This is where CMMN support case modeling shines\u2014not as a rigid sequence, but as a living structure that adapts to real-time triggers. When modeling a customer support case, I\u2019ve found that teams often misunderstand the role of [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":521,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-522","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>CMMN Support Case: Dynamic Ticket Management<\/title>\n<meta name=\"description\" content=\"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CMMN Support Case: Dynamic Ticket Management\" \/>\n<meta property=\"og:description\" content=\"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:06:33+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/\",\"name\":\"CMMN Support Case: Dynamic Ticket Management\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:19:28+00:00\",\"dateModified\":\"2026-03-02T09:06:33+00:00\",\"description\":\"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CMMN Explained: A Practical Guide for Modelers\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Case Studies and Exercises\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Customer Support Management Case\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CMMN Support Case: Dynamic Ticket Management","description":"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/","og_locale":"fr_FR","og_type":"article","og_title":"CMMN Support Case: Dynamic Ticket Management","og_description":"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","article_modified_time":"2026-03-02T09:06:33+00:00","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/","name":"CMMN Support Case: Dynamic Ticket Management","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:19:28+00:00","dateModified":"2026-03-02T09:06:33+00:00","description":"Model a real-world CMMN support case with dynamic task triggers, escalation logic, and event-driven control. Learn ticket management CMMN and CMMN service desk example best practices.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/cmmn-support-case-dynamic-ticket-management\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"CMMN Explained: A Practical Guide for Modelers","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/"},{"@type":"ListItem","position":3,"name":"Real-World Case Studies and Exercises","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/cmmn-explained-practical-guide-for-modelers\/cmmn-case-study\/"},{"@type":"ListItem","position":4,"name":"Customer Support Management Case"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/522","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/522\/revisions"}],"predecessor-version":[{"id":2389,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/522\/revisions\/2389"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/521"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=522"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}