{"id":851,"date":"2026-02-25T10:25:41","date_gmt":"2026-02-25T10:25:41","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/"},"modified":"2026-02-25T10:25:41","modified_gmt":"2026-02-25T10:25:41","slug":"decision-table-design-patterns","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/","title":{"rendered":"Reusable Patterns and Design Strategies"},"content":{"rendered":"<p>Every time you design a decision table, ask: can this logic be reused across multiple business domains? That\u2019s the core principle I\u2019ve learned over two decades of working with financial, healthcare, and insurance systems. Reusability isn\u2019t a feature\u2014it\u2019s a necessity when business rules evolve rapidly. The most effective decision table design patterns are those built around abstraction, modularity, and consistency.<\/p>\n<p>What makes a pattern truly reusable? It must survive changes in context, scale, and stakeholders without needing full reconstruction. This chapter shows how to build decision tables that don\u2019t just solve today\u2019s problem\u2014but become assets for future rule sets.<\/p>\n<p>You\u2019ll learn how to extract reusable decision logic patterns from complex processes, apply them across departments, and maintain them with minimal effort. These aren\u2019t theoretical constructs\u2014they\u2019re battle-tested strategies from real-world implementations where a single table saved months of rework.<\/p>\n<h2>Core Principles of Reusable Decision Logic<\/h2>\n<h3>Abstraction Over Specificity<\/h3>\n<p>Never tie a rule to a single business entity or process. Instead, define conditions and actions using general terms that reflect business intent.<\/p>\n<p>For example, instead of:<\/p>\n<ul>\n<li><code>IF claim_type = \"auto\" AND damage_value &gt; 5000 THEN assign to senior_assessor<\/code><\/li>\n<\/ul>\n<p>Use:<\/p>\n<ul>\n<li><code>IF severity_level = \"high\" THEN route to senior_assessor<\/code><\/li>\n<\/ul>\n<p>Now the rule applies whether the case is an auto claim, medical treatment, or credit dispute.<\/p>\n<p>Abstraction doesn\u2019t remove detail\u2014it shifts it into metadata. You can then map &#8222;severity_level&#8221; to specific thresholds per business unit.<\/p>\n<h3>Modularization Through Rule Families<\/h3>\n<p>Group related decision tables into families based on decision type, not business process. A \u201crisk evaluation\u201d family can serve credit, insurance, and lending workflows.<\/p>\n<p>Each family should have:<\/p>\n<ul>\n<li>A shared input schema (e.g., applicant_status, income_level, credit_score)<\/li>\n<li>Reused action types (e.g., approve, escalate, reject, request_additional_info)<\/li>\n<li>Common validation rules (e.g., no overlapping conditions)<\/li>\n<\/ul>\n<p>When a new business line needs a similar decision, you don\u2019t start from scratch\u2014you select the right rule family, customize the thresholds, and deploy.<\/p>\n<h2>Top 5 Reusable Decision Logic Patterns<\/h2>\n<h3>Pattern 1: The Tiered Decision Chain<\/h3>\n<p>Use this when decisions depend on multiple layers of evaluation\u2014like risk assessment, eligibility checks, or claim validation.<\/p>\n<p>Structure:<\/p>\n<ul>\n<li>Table 1: High-level risk tier (low, medium, high)<\/li>\n<li>Table 2: Action based on tier (e.g., auto-approve, manual review, escalate)<\/li>\n<li>Table 3: Escalation rules (if escalated, which team handles it?)<\/li>\n<\/ul>\n<p>Each table is independent but shares the same input variables. This makes it easy to update one layer without touching the others.<\/p>\n<h3>Pattern 2: The Parameterized Rule Template<\/h3>\n<p>When the same decision logic applies across different contexts but with variable thresholds, use templates.<\/p>\n<p>Example: Eligibility for a benefit program<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Condition<\/th>\n<th>Action<\/th>\n<\/tr>\n<tr>\n<td>age \u2265 {threshold_age}<\/td>\n<td>eligible = true<\/td>\n<\/tr>\n<tr>\n<td>income \u2264 {threshold_income}<\/td>\n<td>eligible = true<\/td>\n<\/tr>\n<tr>\n<td>employment_status = &#8222;employed&#8221;<\/td>\n<td>eligible = true<\/td>\n<\/tr>\n<tr>\n<td>age &lt; {threshold_age} AND income &gt; {threshold_income}<\/td>\n<td>eligible = false<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Replace {threshold_age} and {threshold_income} per business unit. This avoids duplicating the entire rule set.<\/p>\n<h3>Pattern 3: The Guarded Decision Gateway<\/h3>\n<p>Use this when a decision depends on a precondition being met\u2014like whether a user has completed prior steps.<\/p>\n<p>Structure:<\/p>\n<ul>\n<li>First column: \u201cIs prerequisite completed?\u201d (Yes\/No)<\/li>\n<li>Second column: Decision logic only if Yes<\/li>\n<\/ul>\n<p>This pattern prevents invalid rule execution and reduces cognitive load in validation.<\/p>\n<h3>Pattern 4: The Exception-First Rule Set<\/h3>\n<p>Most business logic is built around common cases. But exceptions are where complexity lives.<\/p>\n<p>Structure:<\/p>\n<ul>\n<li>First, define rules for the rarest case (e.g., \u201cIF claim_type = 'fraudulent&#8217; THEN escalate_to_compliance\u201d)<\/li>\n<li>Then, define rules for common scenarios (e.g., \u201cIF claim_status = 'approved&#8217; THEN process_payment\u201d)<\/li>\n<\/ul>\n<p>By placing exceptions first, you avoid ambiguity and make edge cases impossible to overlook.<\/p>\n<h3>Pattern 5: The Context-Aware Decision Matrix<\/h3>\n<p>Use this when the same condition leads to different actions based on context.<\/p>\n<p>Example:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Context<\/th>\n<th>Condition<\/th>\n<th>Action<\/th>\n<\/tr>\n<tr>\n<td>Claim Processing<\/td>\n<td>damage_value &gt; 1000<\/td>\n<td>escalate_to_senior_assessor<\/td>\n<\/tr>\n<tr>\n<td>Loan Approval<\/td>\n<td>credit_score &lt; 600<\/td>\n<td>require_additional_documentation<\/td>\n<\/tr>\n<tr>\n<td>Customer Support<\/td>\n<td>complaint_level = &#8222;urgent&#8221;<\/td>\n<td>assign_to_specialist<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These rules share the same condition structure but act differently based on context. You can reuse this matrix across services with minimal changes.<\/p>\n<h2>Decision Table Modeling Best Practices<\/h2>\n<p>Reusability isn\u2019t just about patterns\u2014it\u2019s about consistency in how you build and manage decision tables.<\/p>\n<h3>Standardize Naming and Structure<\/h3>\n<p>Use consistent naming across all tables:<\/p>\n<ul>\n<li><strong>Prefix<\/strong>: <code>RT_<\/code> for Risk Tier, <code>EL_<\/code> for Eligibility, <code>EX_<\/code> for Exception rules<\/li>\n<li><strong>Context<\/strong>: Include the domain in the name (e.g., <code>EL_Credit_Approval<\/code>)<\/li>\n<li><strong>Versioning<\/strong>: Add version numbers (e.g., <code>EL_Credit_Approval_v2<\/code>)<\/li>\n<\/ul>\n<p>Standardization makes it easy to find, compare, and reuse rules.<\/p>\n<h3>Document Conditions and Actions Clearly<\/h3>\n<p>Never assume. Even simple conditions like <code>status = \"active\"<\/code> should be documented:<\/p>\n<ul>\n<li><strong>Condition<\/strong>: status = &#8222;active&#8221;<\/li>\n<li><strong>Definition<\/strong>: User has completed onboarding and is not suspended or expired<\/li>\n<li><strong>Source<\/strong>: User Profile Module v3.1<\/li>\n<\/ul>\n<p>Clear documentation enables reuse and prevents misinterpretation.<\/p>\n<h3>Validate Before Reusing<\/h3>\n<p>Just because a rule is reusable doesn\u2019t mean it\u2019s correct. Always:<\/p>\n<ul>\n<li>Check for overlapping conditions<\/li>\n<li>Verify no missing combinations<\/li>\n<li>Test edge cases in the target context<\/li>\n<\/ul>\n<p>Reusing flawed logic multiplies errors, not efficiency.<\/p>\n<h2>When Not to Reuse: The Limits of Abstraction<\/h2>\n<p>Abstraction has limits. If a rule depends on highly specific business policies\u2014like \u201cIF policy_type = 'premium&#8217; AND under_65 AND has_medical_history THEN increase_premium_by_15%\u201d\u2014then reuse may introduce errors.<\/p>\n<p>Ask:<\/p>\n<ul>\n<li>Will the same thresholds apply in the new context?<\/li>\n<li>Are the business implications the same?<\/li>\n<li>Can I explain the rule to a new stakeholder without confusion?<\/li>\n<\/ul>\n<p>If any answer is \u201cno,\u201d then the rule is likely not reusable\u2014and shouldn\u2019t be forced into a pattern.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if a decision table is reusable?<\/h3>\n<p>If the same decision logic applies across multiple departments or processes, and the inputs and outputs can be mapped consistently, it\u2019s a candidate for reuse. Test it with a new business unit before implementation.<\/p>\n<h3>Can I reuse decision logic across different rule engines?<\/h3>\n<p>Yes\u2014but only if the engine supports the same condition syntax and action formats. Always map the decision table to the target engine\u2019s rule language. Some engines require minor adjustments to support parameterized templates.<\/p>\n<h3>What\u2019s the best way to manage versioning for reusable decision tables?<\/h3>\n<p>Use semantic versioning (v1.0, v1.1, v2.0). Each change should be documented with a log: \u201cAdded new condition for expat applicants.\u201d Link the version to the change request ID for traceability.<\/p>\n<h3>How do I avoid over-abstraction in decision tables?<\/h3>\n<p>Abstraction works best when it reduces complexity. If adding a parameter or context layer increases cognitive load or requires more documentation than the original rule, you\u2019ve oversimplified. Aim for clarity over elegance.<\/p>\n<h3>Should I store reusable decision tables in a central repository?<\/h3>\n<p>Absolutely. A shared, version-controlled repository (like Git with metadata) allows teams to find, audit, and integrate rules safely. Integrate with your CI\/CD pipeline to validate changes automatically.<\/p>\n<h3>How often should I review reusable decision logic patterns?<\/h3>\n<p>Review annually\u2014or whenever a business policy changes. Reusable logic that isn\u2019t maintained becomes legacy, and legacy rules often break when reused.<\/p>\n<p>Reusability is not a one-time setup. It\u2019s a discipline. The best decision table design patterns are those that grow with the business\u2014not shrink from it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every time you design a decision table, ask: can this logic be reused across multiple business domains? That\u2019s the core principle I\u2019ve learned over two decades of working with financial, healthcare, and insurance systems. Reusability isn\u2019t a feature\u2014it\u2019s a necessity when business rules evolve rapidly. The most effective decision table design patterns are those built [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":850,"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-851","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>Decision Table Design Patterns: Best Practices &amp; Reusable Logic<\/title>\n<meta name=\"description\" content=\"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.\" \/>\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\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Decision Table Design Patterns: Best Practices &amp; Reusable Logic\" \/>\n<meta property=\"og:description\" content=\"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/\",\"name\":\"Decision Table Design Patterns: Best Practices & Reusable Logic\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:25:41+00:00\",\"description\":\"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Decision Tables Explained: From Concept to Implementation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Advanced Decision Table Design\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Reusable Patterns and Design Strategies\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Decision Table Design Patterns: Best Practices & Reusable Logic","description":"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.","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\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/","og_locale":"pl_PL","og_type":"article","og_title":"Decision Table Design Patterns: Best Practices & Reusable Logic","og_description":"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/","name":"Decision Table Design Patterns: Best Practices & Reusable Logic","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:25:41+00:00","description":"Master reusable decision logic patterns and decision table modeling best practices to build scalable, maintainable business rules with confidence.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/decision-table-design-patterns\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Decision Tables Explained: From Concept to Implementation","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/"},{"@type":"ListItem","position":3,"name":"Advanced Decision Table Design","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/advanced-decision-table-design\/"},{"@type":"ListItem","position":4,"name":"Reusable Patterns and Design Strategies"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/851\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/850"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=851"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}