{"id":1190,"date":"2026-02-25T10:37:23","date_gmt":"2026-02-25T10:37:23","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/"},"modified":"2026-02-25T10:37:23","modified_gmt":"2026-02-25T10:37:23","slug":"scoping-customer-journeys-in-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/","title":{"rendered":"Scoping a Journey: From Trigger to Outcome"},"content":{"rendered":"

Imagine a customer trying to resolve a billing discrepancy. They call support, get transferred between agents, receive conflicting information, and end up frustrated. The team tries to fix the issue, but no one knows the full sequence of steps or who\u2019s responsible. This isn’t just a support issue\u2014it\u2019s a design failure in process scope.<\/p>\n

Too often, teams start modeling customer journeys from a vague point like \u201cwhen the customer contacts us,\u201d without clarifying what triggers that interaction or where the journey truly ends. This leads to models that are either too broad\u2014covering every possible action across departments\u2014or too narrow, missing critical handoffs that impact experience.<\/p>\n

Scoping a journey in BPMN isn’t about capturing everything. It’s about choosing a clear, meaningful start and end that reflect a real customer goal. The goal is to create a model that reveals responsibility, identifies delays, and uncovers pain points\u2014without drowning in complexity.<\/p>\n

Defining the Right Start and End Events<\/h2>\n

Every journey begins with a trigger and ends with a clear outcome. The start event must be something that signals the customer\u2019s intent to act. A common mistake is starting at “Customer contacts support,” which is a channel, not a trigger.<\/p>\n

Instead, anchor the journey to a specific customer action: \u201cCustomer submits a dispute form for an incorrect charge\u201d<\/strong>. That\u2019s a valid start event\u2014actionable, observable, and linked to a clear goal.<\/p>\n

The end event should reflect a resolved state: \u201cDispute is resolved and customer confirms satisfaction\u201d<\/strong>. This avoids the trap of ending at “support ticket closed,” which may not reflect the customer\u2019s experience.<\/p>\n

Here\u2019s a simple rule: if the journey ends before the customer feels the outcome, it\u2019s incomplete.<\/p>\n

Start Event Types That Work<\/h3>\n
    \n
  • Message Start Event<\/strong> \u2013 for external triggers like \u201cCustomer sends a support request.\u201d<\/li>\n
  • Timer Start Event<\/strong> \u2013 for scheduled actions, such as \u201cRenewal reminder email sent.\u201d<\/li>\n
  • Conditional Start Event<\/strong> \u2013 when a specific condition is met, like \u201cCustomer exceeds 30 days of inactivity.\u201d<\/li>\n<\/ul>\n

    End Event Types That Deliver Value<\/h3>\n
      \n
    • End Event with Success Outcome<\/strong> \u2013 \u201cCustomer receives refund and confirms resolution.\u201d<\/li>\n
    • End Event with Exception Outcome<\/strong> \u2013 \u201cCustomer abandons the process due to unclear next steps.\u201d<\/li>\n
    • End Event with Feedback Loop<\/strong> \u2013 \u201cCustomer completes a satisfaction survey after issue resolution.\u201d<\/li>\n<\/ul>\n

      Each end state reveals insight. A journey ending in abandonment highlights a failure in communication. One ending in satisfaction shows where the process worked.<\/p>\n

      Choosing the Right Journey Scope and BPMN Boundaries<\/h2>\n

      Defining the journey scope in BPMN means agreeing on what\u2019s inside the model and what\u2019s not. I’ve seen teams include entire departments\u2014marketing, finance, legal\u2014just because they touch the customer. That\u2019s not a journey. It\u2019s a system.<\/p>\n

      Focus on one goal<\/strong>. For example, the journey from purchasing a product to receiving a delivery confirmation<\/em> is a valid scope. It includes shipping, tracking, delivery, and verification\u2014but not the customer\u2019s initial research or post-delivery feedback.<\/p>\n

      Common Pitfalls in Journey Scope and BPMN<\/h3>\n\n\n\n\n\n\n
      Problem<\/th>\nWhy It Fails<\/th>\nBetter Approach<\/th>\n<\/tr>\n
      Starting at \u201cCustomer visits website\u201d<\/td>\nCovers too many unrelated paths (research, purchase, support)<\/td>\nStart at \u201cCustomer adds item to cart\u201d<\/td>\n<\/tr>\n
      Ending at \u201cSupport ticket closed\u201d<\/td>\nCustomer may still be frustrated, even if the ticket is resolved<\/td>\nEnd at \u201cCustomer confirms resolution\u201d or \u201cSatisfaction survey submitted\u201d<\/td>\n<\/tr>\n
      Modeling all channels in one flow<\/td>\nCreates confusion and hidden assumptions<\/td>\nUse lanes to separate channels; model path variations separately<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      When modeling in BPMN, treat the journey as a single path<\/strong> focused on the customer\u2019s intent. Use lanes to represent different roles\u2014customer, agent, system\u2014but keep the flow centered on the customer\u2019s experience.<\/p>\n

      Step-by-Step Approach to Agreeing on Journey Scope with Stakeholders<\/h2>\n

      Aligning stakeholders on journey scope isn\u2019t about consensus\u2014it\u2019s about clarity. Here\u2019s how I guide teams:<\/p>\n

        \n
      1. Start with the customer\u2019s goal.<\/strong> Ask: \u201cWhat does the customer want to achieve?\u201d Use simple language. Example: \u201cI want to return this damaged item.\u201d<\/li>\n
      2. Define the trigger event.<\/strong> What action initiates the journey? Is it a form submission? A message? A timer? Be specific.<\/li>\n
      3. Identify the outcome.<\/strong> What does \u201csuccess\u201d look like? Not \u201cticket closed,\u201d but \u201crefund issued and customer notified.\u201d<\/li>\n
      4. Draw the first draft.<\/strong> Use a simple BPMN flow: Start \u2192 Activity \u2192 Decision \u2192 End. Keep it high-level.<\/li>\n
      5. Run the \u201cIs this the customer\u2019s focus?\u201d test.<\/strong> If you can\u2019t explain it in one sentence to a non-technical stakeholder, it\u2019s too broad.<\/li>\n
      6. Validate scope with stakeholders.<\/strong> Show the flow and ask: \u201cDoes this reflect the experience the customer has?\u201d If yes, you\u2019re on track.<\/li>\n<\/ol>\n

        When stakeholders can see a clear, focused journey, they stop arguing about what to include and start focusing on what to improve.<\/p>\n

        Why Journey Scope and BPMN Matter Together<\/h2>\n

        Defining the start and end of journeys isn\u2019t just a modeling detail\u2014it shapes how teams think. A well-scoped journey in BPMN forces clarity on responsibilities, handoffs, and timing. It turns vague ideas like \u201csupport is slow\u201d into measurable questions: \u201cWhy does the dispatch step take 48 hours? Who owns it?\u201d<\/p>\n

        When you model with clear boundaries, you create a shared language. The customer service agent understands the flow. The IT team sees automation opportunities. The CX leader sees where delays hurt satisfaction.<\/p>\n

        Remember: a BPMN model isn\u2019t a process map for systems. It\u2019s a blueprint for experience.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        What\u2019s the difference between a customer journey and a BPMN process?<\/h3>\n

        A customer journey describes the experience from the customer\u2019s perspective\u2014emotions, touchpoints, expectations. A BPMN process maps the actual steps, responsibilities, and flows behind the scenes. They\u2019re complementary: the journey defines the “why,” BPMN explains the “how.”<\/p>\n

        How do I decide whether to model a self-service or assisted journey?<\/h3>\n

        Start with the customer\u2019s choice. If they use help docs, chatbots, or forms, model the self-service path. If they call support or visit a branch, model the assisted path. Use gateways to show how the customer switches between paths. Keep both visible to show the full experience.<\/p>\n

        Can I model multiple journeys in one BPMN diagram?<\/h3>\n

        Yes, but only if they share a common goal or flow. For example, a purchase journey might include payment, shipping, and delivery. You can model them together. But avoid combining unrelated journeys\u2014like onboarding and refund processing\u2014into one diagram. Each should be a separate BPMN model.<\/p>\n

        How do I handle exceptions like abandonment or long waits in BPMN?<\/h3>\n

        Use Boundary Events<\/strong> attached to key activities. For example, attach a boundary event to \u201cWait for delivery confirmation\u201d with a timer: \u201cIf no confirmation after 7 days, escalate to support.\u201d This keeps the main flow clean while showing how the system responds to delays.<\/p>\n

        Should the customer be in their own pool in BPMN?<\/h3>\n

        Yes\u2014especially in complex journeys. A dedicated customer pool (or lane) makes their experience visible. It helps avoid confusion between customer actions and internal processes. Use message flows to show communication between the customer and service teams.<\/p>\n

        How do I ensure the journey scope stays aligned with business goals?<\/h3>\n

        Anchor every journey to a business metric\u2014like NPS, CSAT, or conversion rate. Ask: \u201cDoes this journey directly impact that metric?\u201d If not, reconsider the scope. Keep the model focused on what matters to both the customer and the business.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Imagine a customer trying to resolve a billing discrepancy. They call support, get transferred between agents, receive conflicting information, and end up frustrated. The team tries to fix the issue, but no one knows the full sequence of steps or who\u2019s responsible. This isn’t just a support issue\u2014it\u2019s a design failure in process scope. Too […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1186,"menu_order":3,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1190","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nScoping Customer Journeys in BPMN<\/title>\n<meta name=\"description\" content=\"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process 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\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scoping Customer Journeys in BPMN\" \/>\n<meta property=\"og:description\" content=\"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process models.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/\",\"name\":\"Scoping Customer Journeys in BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:37:23+00:00\",\"description\":\"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process models.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Foundations of Customer Journey Thinking\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Scoping a Journey: From Trigger to Outcome\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scoping Customer Journeys in BPMN","description":"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process 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\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/","og_locale":"id_ID","og_type":"article","og_title":"Scoping Customer Journeys in BPMN","og_description":"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process models.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/","name":"Scoping Customer Journeys in BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:37:23+00:00","description":"Learn how to define the scope of customer journeys in BPMN with clear triggers, paths, and outcomes. Master journey boundaries and stakeholder alignment for actionable, customer-centric process models.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/scoping-customer-journeys-in-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Foundations of Customer Journey Thinking","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/"},{"@type":"ListItem","position":4,"name":"Scoping a Journey: From Trigger to Outcome"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1190\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1186"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1190"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}