{"id":358,"date":"2026-02-25T10:16:43","date_gmt":"2026-02-25T10:16:43","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/"},"modified":"2026-02-25T10:16:43","modified_gmt":"2026-02-25T10:16:43","slug":"bpmn-private-process-internal-workflow","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/","title":{"rendered":"Private (Internal) Process Modeling Explained"},"content":{"rendered":"<p>Over 80% of the BPMN models I\u2019ve reviewed in the past five years were private processes\u2014internal workflows modeled within a single pool, with no external message flows. This isn\u2019t a coincidence. Teams use this format because it aligns with how work actually happens inside an organization: a sequence of actions, decisions, and handoffs, all contained within one unit of responsibility.<\/p>\n<p>What makes a BPMN private process unique is its focus on internal logic. It shows the full flow of work from start to finish, without exposing interactions with other teams or systems. This is ideal when you\u2019re documenting a process for internal training, designing automation in a workflow engine, or analyzing bottlenecks in a department\u2019s daily operations.<\/p>\n<p>As a mentor, I\u2019ve seen teams struggle when they try to use collaboration diagrams for internal tasks\u2014adding pools and message flows where none exist. It creates confusion. The private process avoids that. It\u2019s not about who sends what to whom. It\u2019s about what happens next in the sequence.<\/p>\n<p>By the end of this chapter, you\u2019ll know how to model a private process with clarity, decide the right level of detail, and handle internal handoffs without overcomplicating the diagram. You\u2019ll also learn how to distinguish this from collaboration or choreography views\u2014so you pick the right tool for the job.<\/p>\n<h2>What Is a BPMN Private Process?<\/h2>\n<p>A BPMN private process is a process diagram that represents the internal workflow of a single participant\u2014typically a department, role, or system\u2014within a single pool.<\/p>\n<p>It does not show message flows to external participants. There are no inter-pool connections. All sequence flows are internal.<\/p>\n<p>This is the most common type of BPMN diagram used in organizations. It\u2019s the go-to choice when you\u2019re documenting how a team performs a task, from initiation to completion.<\/p>\n<p>Think of it as a \u201chow it really works\u201d map\u2014inside the organization, not across it.<\/p>\n<h3>Why Use a Private Process?<\/h3>\n<p>There are three main reasons teams choose private process modeling:<\/p>\n<ul>\n<li><strong>Clarity of internal logic<\/strong> \u2013 When the focus is on the sequence of steps, decisions, and handoffs within a single unit, a private process removes external noise.<\/li>\n<li><strong>Automation readiness<\/strong> \u2013 Most workflow engines (like Camunda, Activiti, or Flowable) execute private processes. If you\u2019re modeling for automation, this is the format to use.<\/li>\n<li><strong>Stakeholder alignment<\/strong> \u2013 Internal teams, such as HR, finance, or IT, benefit from seeing their own process in full detail without needing to understand external dependencies.<\/li>\n<\/ul>\n<p>When I worked with a mid-sized insurance company, they modeled their claims processing as a private process. The result? A 30% reduction in onboarding time for new claims analysts. Why? Because the diagram showed exactly what each step involved\u2014no assumptions, no guesswork.<\/p>\n<h2>Modeling a BPMN Private Process: Key Principles<\/h2>\n<p>Modeling a private process isn\u2019t just about drawing a flowchart. It\u2019s about making choices that reflect the reality of how work is done.<\/p>\n<h3>Start with a Single Pool<\/h3>\n<p>Every private process begins with a single pool. This pool represents the participant\u2014e.g., \u201cClaims Department\u201d or \u201cCustomer Service Agent.\u201d<\/p>\n<p>Do not split it into lanes unless you\u2019re modeling distinct roles within the same team. Even then, use lanes sparingly. The goal is to keep the focus on the process, not the people.<\/p>\n<p>When I see a private process with five lanes, I ask: \u201cIs this really a process, or is it a collaboration?\u201d If the handoffs are between different teams, it\u2019s likely a collaboration diagram in disguise.<\/p>\n<h3>Use Sequence Flows, Not Message Flows<\/h3>\n<p>Only use sequence flows inside a private process. Message flows should never connect to external pools.<\/p>\n<p>Message flows are for collaboration diagrams. They show what is sent or received between participants. In a private process, all flows are internal\u2014what happens next in the sequence.<\/p>\n<p>Example: If a customer service agent approves a refund, the next step is \u201cProcess payment.\u201d That\u2019s a sequence flow. If the agent sends a message to the finance team, that\u2019s a message flow\u2014and it belongs in a collaboration diagram, not here.<\/p>\n<h3>Handle Internal Handoffs with Clarity<\/h3>\n<p>Internal handoffs\u2014when one role passes work to another within the same team\u2014are common. But they can blur the lines of ownership.<\/p>\n<p>Use lanes to represent different roles. But avoid over-lane-izing. One lane per role is usually enough.<\/p>\n<p>For example, in a loan approval process, you might have:\n    <\/p>\n<ul>\n<li>Loan Officer (enters application)<\/li>\n<li>Underwriter (assesses risk)<\/li>\n<li>Manager (approves or rejects)<\/li>\n<\/ul>\n<p>Each lane contains the activities they perform. The sequence flows move from one lane to the next, showing the handoff.<\/p>\n<p>Don\u2019t use message flows between lanes. That\u2019s a red flag. It suggests you\u2019re modeling a collaboration, not an internal process.<\/p>\n<h2>Choosing the Right Level of Detail<\/h2>\n<p>One of the biggest challenges in private process modeling is knowing how much detail to include.<\/p>\n<p>Too little detail? The diagram is useless for training or automation.<\/p>\n<p>Too much? It becomes a wall of text and icons, unreadable by anyone.<\/p>\n<p>Here\u2019s my rule of thumb: <strong>model at the level of execution<\/strong>.<\/p>\n<p>If the process will be automated, include all tasks, decisions, and data inputs\/outputs. If it\u2019s for documentation, focus on key decision points and major handoffs.<\/p>\n<h3>Decision Tree: How Much Detail?<\/h3>\n<p>Use this checklist to decide:<\/p>\n<ol>\n<li><strong>Is this process going to be automated?<\/strong> \u2192 Include all tasks, data objects, and conditions.<\/li>\n<li><strong>Is it for training or onboarding?<\/strong> \u2192 Focus on major steps and decision points. Use swimlanes to show role responsibilities.<\/li>\n<li><strong>Is it for executive review?<\/strong> \u2192 Simplify. Use a conversation diagram instead.<\/li>\n<li><strong>Is it part of a larger system?<\/strong> \u2192 Keep it modular. Break it into sub-processes if needed.<\/li>\n<\/ol>\n<p>When I worked with a logistics team, we modeled their invoice reconciliation process. Initially, we included every field and validation rule. It was too dense. After a review, we simplified it to show only the key decision points: \u201cIs the invoice valid?\u201d and \u201cIs the amount correct?\u201d The rest was moved to a separate data model.<\/p>\n<p>Result? The team understood it faster. And the automation team could still map the logic precisely.<\/p>\n<h2>BPMN Private Process Example: Employee Onboarding<\/h2>\n<p>Let\u2019s walk through a real-world BPMN private process example: employee onboarding in a mid-sized tech company.<\/p>\n<p>Pool: HR Department<\/p>\n<p>Lanes: HR Coordinator, IT Admin, Manager<\/p>\n<p>Key Steps:<\/p>\n<ul>\n<li>Receive new hire paperwork (Start Event)<\/li>\n<li>Verify documents (Task)<\/li>\n<li>Is documentation complete? (Exclusive Gateway)<\/li>\n<li>Yes \u2192 Create user account (Task, IT Admin lane)<\/li>\n<li>No \u2192 Notify hiring manager (Task)<\/li>\n<li>After account creation \u2192 Send welcome email (Task, HR lane)<\/li>\n<li>Send onboarding schedule to manager (Task, HR lane)<\/li>\n<li>End (End Event)<\/li>\n<\/ul>\n<p>Notice: All flows are sequence flows. No message flows to external pools. The handoffs are between roles within HR and IT\u2014internal.<\/p>\n<p>This is a <strong>BPMN single pool process<\/strong> that clearly shows the internal workflow. It\u2019s ideal for training, automation, or auditing.<\/p>\n<h2>Common Mistakes in Internal Process Modeling<\/h2>\n<p>Even experienced modelers make these errors. Watch out for them:<\/p>\n<ul>\n<li><strong>Mixing sequence and message flows<\/strong> \u2013 If you\u2019re using a message flow inside a single pool, you\u2019re likely modeling a collaboration by mistake.<\/li>\n<li><strong>Over-lane-izing<\/strong> \u2013 Too many lanes make it hard to follow the flow. Use lanes only to show distinct roles, not every individual.<\/li>\n<li><strong>Ignoring data<\/strong> \u2013 Tasks often depend on data. Include data objects or input\/output parameters where relevant.<\/li>\n<li><strong>Starting with a collaboration diagram<\/strong> \u2013 If you begin with multiple pools, you\u2019re already in collaboration territory. Switch to private process only when you\u2019re modeling a single unit.<\/li>\n<\/ul>\n<p>When I reviewed a model from a financial services firm, they had a private process with three pools. The diagram was labeled \u201cInternal Process,\u201d but it showed message flows between HR, Finance, and IT. I asked: \u201cWho\u2019s sending what?\u201d The answer was \u201cWe don\u2019t know.\u201d That\u2019s a red flag. It\u2019s not a private process. It\u2019s a collaboration.<\/p>\n<h2>When Not to Use a Private Process<\/h2>\n<p>Just as important as knowing when to use it is knowing when not to.<\/p>\n<p>Use a private process only when:<\/p>\n<ul>\n<li>You\u2019re modeling a single participant\u2019s workflow.<\/li>\n<li>There are no external handoffs or message exchanges.<\/li>\n<li>The goal is documentation, training, or automation.<\/li>\n<\/ul>\n<p>Don\u2019t use it when:<\/p>\n<ul>\n<li>You need to show interactions between departments.<\/li>\n<li>Work is passed between teams or systems.<\/li>\n<li>You\u2019re defining a contract or agreement with a partner.<\/li>\n<\/ul>\n<p>In those cases, use a collaboration or choreography diagram instead.<\/p>\n<h2>Summary: Key Takeaways<\/h2>\n<p>A BPMN private process is the right choice when you\u2019re modeling internal workflows within a single team or system.<\/p>\n<p>Use a single pool. Avoid message flows. Focus on sequence flows and internal handoffs.<\/p>\n<p>Decide the level of detail based on your goal\u2014automation, training, or audit.<\/p>\n<p>Remember: <strong>internal process modeling BPMN<\/strong> is about clarity, not complexity. If your diagram feels cluttered, simplify it. If it\u2019s too vague, add the missing logic.<\/p>\n<p>And always ask: \u201cIs this really a private process, or am I modeling a collaboration in disguise?\u201d<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between a BPMN private process and a collaboration diagram?<\/h3>\n<p>A private process shows the internal flow of a single participant, using only sequence flows. A collaboration diagram shows interactions between multiple participants, using message flows. If there\u2019s no external exchange, use a private process.<\/p>\n<h3>Can a BPMN private process include multiple lanes?<\/h3>\n<p>Yes, but only to represent distinct roles within the same team. For example, HR Coordinator and IT Admin in the same department. Avoid using lanes to represent separate departments or external teams.<\/p>\n<h3>Is a BPMN private process executable?<\/h3>\n<p>Yes, if it includes all necessary elements for automation: tasks, gateways, data objects, and valid sequence flows. Most workflow engines expect private processes for execution.<\/p>\n<h3>When should I use a BPMN single pool process instead of a collaboration diagram?<\/h3>\n<p>Use a single pool process when the workflow is entirely internal. Use collaboration when work is passed between teams, departments, or systems. If there are no external message flows, it\u2019s a private process.<\/p>\n<h3>How do I decide how much detail to include in a private process?<\/h3>\n<p>Ask: \u201cWho will use this diagram?\u201d If it\u2019s for automation, include all tasks and data. If it\u2019s for training, focus on key steps and decisions. Avoid unnecessary detail that obscures the flow.<\/p>\n<h3>Can a private process be part of a larger model?<\/h3>\n<p>Yes. A private process can be a sub-process within a collaboration or choreography diagram. It\u2019s a common pattern to break down complex workflows into smaller, internal processes for clarity and reuse.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Over 80% of the BPMN models I\u2019ve reviewed in the past five years were private processes\u2014internal workflows modeled within a single pool, with no external message flows. This isn\u2019t a coincidence. Teams use this format because it aligns with how work actually happens inside an organization: a sequence of actions, decisions, and handoffs, all contained [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":356,"menu_order":1,"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-358","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>BPMN Private Process: Internal Workflow Modeling<\/title>\n<meta name=\"description\" content=\"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.\" \/>\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\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Private Process: Internal Workflow Modeling\" \/>\n<meta property=\"og:description\" content=\"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/\" \/>\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=\"9 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\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/\",\"name\":\"BPMN Private Process: Internal Workflow Modeling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:16:43+00:00\",\"description\":\"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Diagram Types Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Process Diagrams \u2014 Modeling Internal Workflows\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Private (Internal) Process Modeling Explained\"}]},{\"@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":"BPMN Private Process: Internal Workflow Modeling","description":"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.","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\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/","og_locale":"id_ID","og_type":"article","og_title":"BPMN Private Process: Internal Workflow Modeling","og_description":"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"9 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/","name":"BPMN Private Process: Internal Workflow Modeling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:16:43+00:00","description":"Learn how to model a BPMN private process for internal workflow clarity. Understand when to use a single pool, avoid external flows, and choose the right detail level for your team. Real-world examples included.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/bpmn-private-process-internal-workflow\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"BPMN Diagram Types Explained","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/"},{"@type":"ListItem","position":3,"name":"Process Diagrams \u2014 Modeling Internal Workflows","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-diagram-types-explained\/bpmn-process-diagram\/"},{"@type":"ListItem","position":4,"name":"Private (Internal) Process Modeling Explained"}]},{"@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\/358","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\/358\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/356"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=358"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}