{"id":596,"date":"2026-02-25T10:20:46","date_gmt":"2026-02-25T10:20:46","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/"},"modified":"2026-02-25T10:20:46","modified_gmt":"2026-02-25T10:20:46","slug":"modeling-system-behavior-in-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/","title":{"rendered":"Modeling System Behavior Instead of Business Process"},"content":{"rendered":"<p>Too many BPMN diagrams begin as technical specifications disguised as process models. I\u2019ve seen teams spend hours mapping every API call, every screen transition, and every server-side validation \u2014 only to realize they\u2019ve built a workflow for developers, not a shared understanding for business stakeholders.<\/p>\n<p>Here\u2019s the truth: BPMN is not a system design diagram. It\u2019s a business process modeling language. When you model system behavior instead of business process, you\u2019re not simplifying complexity \u2014 you\u2019re obscuring intent.<\/p>\n<p>My experience shows that when a BPMN model includes technical events like \u201cAPI Response Received\u201d or \u201cUI Screen Loaded,\u201d it loses its power to communicate to business decision-makers. The diagram becomes a map of code, not a guide for people.<\/p>\n<p>What you\u2019ll learn here: how to distinguish between business-oriented and technical modeling, how to preserve clarity by separating concerns, and when to use alternative models like UML, technical workflows, or sequence diagrams instead.<\/p>\n<h2>Understanding the Core Mismatch: Business vs Technical BPMN<\/h2>\n<p>Many modelers confuse a workflow that describes \u201cwhat the system does\u201d with one that describes \u201cwhat the business needs.\u201d This is where problems begin.<\/p>\n<p>Consider this: a business process doesn\u2019t care if a data validation happens on the client or server. It only cares that the data is valid before proceeding. The mechanism is irrelevant \u2014 the outcome is what matters.<\/p>\n<p>When you model system behavior in BPMN, you\u2019re often conflating implementation with intention. That leads to models that are difficult to validate, hard to maintain, and impossible to use in business change management.<\/p>\n<p>Here\u2019s how to spot it: if your diagram contains terms like \u201cfetch user data via REST API,\u201d \u201crender screen X,\u201d or \u201csubmit form to backend,\u201d you\u2019re likely modeling system behavior.<\/p>\n<h3>What Should a Business Process Model Actually Capture?<\/h3>\n<p>A properly scoped BPMN model focuses on:<\/p>\n<ul>\n<li><strong>Who<\/strong> performs the activity (role or organization)<\/li>\n<li><strong>What<\/strong> they do (a business action, not a technical one)<\/li>\n<li><strong>When<\/strong> it starts and ends (based on business triggers)<\/li>\n<li><strong>Why<\/strong> it happens (aligned with business goals)<\/li>\n<\/ul>\n<p>Instead of \u201cAPI call to validate address,\u201d model it as \u201cValidate customer address.\u201d The technical method? Irrelevant at this level.<\/p>\n<p>Every activity should answer: \u201cWhat business value does this create?\u201d If it doesn\u2019t, it belongs in a different model.<\/p>\n<h2>Guidelines for Separating Business Process from Technical Implementation<\/h2>\n<p>Don\u2019t eliminate technical detail \u2014 just move it out of the BPMN model.<\/p>\n<p>Here\u2019s how to keep BPMN business-oriented while preserving technical accuracy:<\/p>\n<h3>1. Use a Two-Level Modeling Approach<\/h3>\n<p>Model your process at the business level first. Then, if needed, create a technical companion model for implementation.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>BPMN (Business level)<\/strong>: \u201cVerify customer identity\u201d<\/li>\n<li><strong>UML or Technical Workflow (Implementation)<\/strong>: \u201cCall KYC API with ID document, validate OCR results, compare with database\u201d<\/li>\n<\/ul>\n<p>Keep BPMN clean. Use annotations to reference the technical model when necessary.<\/p>\n<h3>2. Replace Technical Events with Business Triggers<\/h3>\n<p>Common mistake: using \u201cAPI Call Sent\u201d or \u201cError 404 Received\u201d as events.<\/p>\n<p>Correct approach: use business triggers.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Technical Event (Incorrect)<\/th>\n<th>Business Event (Correct)<\/th>\n<\/tr>\n<tr>\n<td>API Response Received<\/td>\n<td>Customer data verified<\/td>\n<\/tr>\n<tr>\n<td>Screen Loaded<\/td>\n<td>Customer reaches identity verification step<\/td>\n<\/tr>\n<tr>\n<td>Database Update Complete<\/td>\n<td>Application submitted for review<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These events are understandable by both business and IT \u2014 and they reflect what actually matters to the user.<\/p>\n<h3>3. Name Activities for Business Intent, Not System Actions<\/h3>\n<p>Bad: \u201cCall \/validate endpoint via POST\u201d<\/p>\n<p>Good: \u201cValidate customer\u2019s identity\u201d<\/p>\n<p>Even better: \u201cVerify name and address match\u201d \u2014 if that\u2019s the actual business rule.<\/p>\n<p>Use verbs that reflect the business outcome, not the technical method. The action is \u201cverify,\u201d not \u201csend a JSON payload.\u201d<\/p>\n<h3>4. Externalize Complex Logic<\/h3>\n<p>If a decision gateway contains a rule like \u201cIf (user.age &gt;= 18 AND isResident == true) AND (documentType == \u2018passport\u2019 OR \u2018driver\u2019s license\u2019)\u201d, you\u2019re overloading BPMN with system logic.<\/p>\n<p>Instead:<\/p>\n<ul>\n<li>Model the decision as \u201cIs customer eligible for application?\u201d<\/li>\n<li>Reference a <strong>DMN decision model<\/strong> that defines the eligibility rules.<\/li>\n<li>Keep BPMN focused on flow and ownership.<\/li>\n<\/ul>\n<p>This separates business rules from process flow \u2014 a key principle in model integrity.<\/p>\n<h2>When Not to Use BPMN for System Logic<\/h2>\n<p>There are times when BPMN is the wrong tool \u2014 specifically when you\u2019re modeling:<\/p>\n<ul>\n<li>Server-side workflows with complex logic<\/li>\n<li>API call sequences<\/li>\n<li>UI navigation flows<\/li>\n<li>Exception handling at the code level<\/li>\n<li>Message routing in microservices<\/li>\n<\/ul>\n<p>For these, use:<\/p>\n<ul>\n<li><strong>UML Activity Diagrams<\/strong> for detailed control flow<\/li>\n<li><strong>Sequence Diagrams<\/strong> to show message passing between components<\/li>\n<li><strong>State Machines<\/strong> for system states and transitions<\/li>\n<li><strong>Technical Workflow Models<\/strong> (e.g., in tools like Camunda, Aris, or Microsoft BizTalk)<\/li>\n<\/ul>\n<p>Don\u2019t force technical workflows into BPMN just because it\u2019s familiar. Doing so creates a false sense of clarity.<\/p>\n<p>Ask yourself: \u201cWould a business stakeholder understand this without technical training?\u201d If not, it\u2019s not a business process \u2014 it\u2019s a technical implementation.<\/p>\n<h2>Practical Checklist: Is My BPMN Too Technical?<\/h2>\n<p>Use this checklist before finalizing any BPMN model.<\/p>\n<ul>\n<li>Does every activity start with a verb that reflects a business outcome? (e.g., \u201cApprove,\u201d \u201cVerify,\u201d \u201cSubmit\u201d) \u2014 not \u201cSend,\u201d \u201cLoad,\u201d \u201cCall.\u201d<\/li>\n<li>Do the events reflect business triggers, not system events? (e.g., \u201cApplication received\u201d vs \u201cAPI call initiated\u201d)<\/li>\n<li>Are all decision conditions written in plain business language? (e.g., \u201cCustomer has valid ID?\u201d not \u201cIs documentType in [\u2018passport\u2019, \u2018driver\u2019s license\u2019]?\u201d)<\/li>\n<li>Have I externalized complex logic to a DMN or separate document?<\/li>\n<li>Could a non-technical stakeholder explain this process to a colleague?<\/li>\n<\/ul>\n<p>If more than one answer is \u201cno,\u201d you\u2019re modeling system behavior \u2014 and your BPMN is becoming a technical artifact, not a business one.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between business vs technical BPMN?<\/h3>\n<p>Business BPMN models focus on roles, outcomes, and business events. Technical BPMN (if it exists) tries to map system actions. The former is for stakeholders. The latter is for developers and should not be mixed into BPMN.<\/p>\n<h3>Can I still include API calls in BPMN?<\/h3>\n<p>Only if they\u2019re part of a business action. For example: \u201cSubmit application via API\u201d is acceptable if the verb \u201csubmit\u201d reflects business intent. But \u201cCall \/submit endpoint\u201d is not.<\/p>\n<h3>When should I use UML instead of BPMN?<\/h3>\n<p>Use UML for detailed technical workflows, message flows between systems, or complex decision logic. BPMN is for high-level business processes, team collaboration, and stakeholder alignment.<\/p>\n<h3>How do I convince my team to stop modeling system behavior in BPMN?<\/h3>\n<p>Start with a small, visible example. Show how a business-focused version is clearer, easier to review, and more useful for change management. Use before\/after comparisons to demonstrate value.<\/p>\n<h3>Can BPMN coexist with technical models?<\/h3>\n<p>Absolutely. Model the business process in BPMN. Then, link it to a technical workflow or sequence diagram for implementation. Use annotations or references to connect them.<\/p>\n<h3>Is it ever okay to model screen transitions in BPMN?<\/h3>\n<p>Only if they represent business steps. \u201cCustomer views confirmation screen\u201d is acceptable if that step is part of the business journey. But \u201cScreen loads after API call\u201d is not \u2014 that\u2019s system behavior.<\/p>\n<p>Remember: if you&#8217;re mapping user interface behavior instead of business behavior, you\u2019ve stepped outside the scope of BPMN.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many BPMN diagrams begin as technical specifications disguised as process models. I\u2019ve seen teams spend hours mapping every API call, every screen transition, and every server-side validation \u2014 only to realize they\u2019ve built a workflow for developers, not a shared understanding for business stakeholders. Here\u2019s the truth: BPMN is not a system design diagram. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":591,"menu_order":4,"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-596","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>Modeling System Behavior in BPMN: Avoiding Technical Overload<\/title>\n<meta name=\"description\" content=\"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.\" \/>\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\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Modeling System Behavior in BPMN: Avoiding Technical Overload\" \/>\n<meta property=\"og:description\" content=\"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/\" \/>\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\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/\",\"name\":\"Modeling System Behavior in BPMN: Avoiding Technical Overload\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:20:46+00:00\",\"description\":\"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scope, Levels, and Process Boundaries\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Modeling System Behavior Instead of Business Process\"}]},{\"@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":"Modeling System Behavior in BPMN: Avoiding Technical Overload","description":"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.","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\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/","og_locale":"pl_PL","og_type":"article","og_title":"Modeling System Behavior in BPMN: Avoiding Technical Overload","og_description":"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/","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\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/","name":"Modeling System Behavior in BPMN: Avoiding Technical Overload","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:20:46+00:00","description":"Learn how to avoid modeling system behavior in BPMN by focusing on business process instead of technical details. Discover best practices for separating business logic from system implementation and when to use other models.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/modeling-system-behavior-in-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Scope, Levels, and Process Boundaries","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/"},{"@type":"ListItem","position":4,"name":"Modeling System Behavior Instead of Business Process"}]},{"@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\/596","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\/596\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/591"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=596"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=596"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}