From 3ac432b0ed071ba09fd5e5aefebd64c610262880 Mon Sep 17 00:00:00 2001 From: christinaausley <84338309+christinaausley@users.noreply.github.com> Date: Mon, 11 Sep 2023 13:08:46 -0400 Subject: [PATCH] Docs modeler renaming (#2564) * modeler renaming * rename modeler page * resolve comments --- docs/components/modeler/about-modeler.md | 6 +-- docs/components/modeler/bpmn/bpmn.md | 2 +- .../business-rule-tasks.md | 2 +- .../inclusive-gateways/inclusive-gateways.md | 2 +- .../modeler/bpmn/script-tasks/script-tasks.md | 2 +- .../modeler/bpmn/user-tasks/user-tasks.md | 4 +- docs/components/modeler/data-handling.md | 2 +- ...-platform-8.md => connect-to-camunda-8.md} | 8 ++-- .../c7-defining-templates.md | 12 +++--- .../element-templates/defining-templates.md | 2 +- .../modeler/desktop-modeler/flags/flags.md | 4 +- .../modeler/desktop-modeler/index.md | 8 ++-- .../model-your-first-diagram.md | 2 +- .../modeler/desktop-modeler/start-instance.md | 4 +- .../desktop-modeler/telemetry/telemetry.md | 4 +- .../desktop-modeler/troubleshooting.md | 2 +- .../dmn/decision-requirements-graph.md | 2 +- .../modeler/dmn/decision-table-input.md | 2 +- .../modeler/dmn/decision-table-output.md | 2 +- docs/components/modeler/dmn/decision-table.md | 2 +- docs/components/modeler/dmn/dmn-data-types.md | 2 +- .../modeler/forms/camunda-forms-reference.md | 4 +- .../modeling-guidance/rules/element-type.md | 2 +- .../publish-public-processes.md | 8 ++-- .../web-modeler/collaborate-with-modes.md | 2 +- .../modeler/web-modeler/collaboration.md | 8 ++-- .../web-modeler/design-your-process.md | 2 +- .../web-modeler/implement-your-process.md | 2 +- .../modeler/web-modeler/import-diagram.md | 2 +- .../web-modeler/launch-cloud-modeler.md | 6 +-- .../modeler/web-modeler/milestones.md | 2 +- .../web-modeler/model-your-first-diagram.md | 2 +- .../modeler/web-modeler/new-web-modeler.md | 2 +- .../modeler/web-modeler/play-your-process.md | 2 +- .../run-or-publish-your-process.md | 18 ++++---- .../modeler/web-modeler/save-and-deploy.md | 2 +- .../helm-kubernetes/upgrade.md | 2 +- optimize_sidebars.js | 2 +- .../version-3.10.0-sidebars.json | 2 +- .../version-3.9.0-sidebars.json | 2 +- sidebars.js | 2 +- static/.htaccess | 6 +++ .../components/modeler/about-modeler.md | 4 +- .../components/modeler/bpmn/bpmn-coverage.md | 2 +- .../components/modeler/bpmn/bpmn.md | 2 +- .../business-rule-tasks.md | 2 +- .../inclusive-gateways/inclusive-gateways.md | 2 +- .../modeler/bpmn/user-tasks/user-tasks.md | 4 +- ...-platform-8.md => connect-to-camunda-8.md} | 6 +-- .../element-templates/additional-resources.md | 4 +- .../configuring-templates.md | 4 +- .../element-templates/defining-templates.md | 42 +++++++++---------- .../element-templates/using-templates.md | 4 +- .../modeler/desktop-modeler/flags/flags.md | 4 +- .../model-your-first-diagram.md | 2 +- .../modeler/desktop-modeler/start-instance.md | 4 +- .../desktop-modeler/telemetry/telemetry.md | 4 +- .../dmn/decision-literal-expression.md | 2 +- .../dmn/decision-requirements-graph.md | 2 +- .../modeler/dmn/decision-table-input.md | 2 +- .../modeler/dmn/decision-table-output.md | 2 +- .../components/modeler/dmn/decision-table.md | 2 +- .../components/modeler/dmn/dmn-data-types.md | 2 +- .../modeler/forms/camunda-forms-reference.md | 4 +- .../web-modeler/collaborate-with-modes.md | 2 +- .../modeler/web-modeler/collaboration.md | 6 +-- .../web-modeler/design-your-process.md | 2 +- .../web-modeler/implement-your-process.md | 2 +- .../modeler/web-modeler/import-diagram.md | 2 +- .../web-modeler/launch-cloud-modeler.md | 6 +-- .../modeler/web-modeler/milestones.md | 2 +- .../web-modeler/model-your-first-diagram.md | 2 +- .../modeler/web-modeler/new-web-modeler.md | 2 +- .../modeler/web-modeler/save-and-deploy.md | 2 +- .../modeler/web-modeler/start-instance.md | 2 +- .../components/modeler/about-modeler.md | 6 +-- .../components/modeler/bpmn/bpmn.md | 2 +- .../business-rule-tasks.md | 2 +- .../inclusive-gateways/inclusive-gateways.md | 2 +- .../modeler/bpmn/script-tasks/script-tasks.md | 2 +- .../modeler/bpmn/user-tasks/user-tasks.md | 4 +- .../components/modeler/data-handling.md | 2 +- ...-platform-8.md => connect-to-camunda-8.md} | 8 ++-- .../c7-defining-templates.md | 12 +++--- .../element-templates/defining-templates.md | 2 +- .../modeler/desktop-modeler/flags/flags.md | 4 +- .../modeler/desktop-modeler/index.md | 8 ++-- .../model-your-first-diagram.md | 2 +- .../modeler/desktop-modeler/start-instance.md | 4 +- .../desktop-modeler/telemetry/telemetry.md | 4 +- .../desktop-modeler/troubleshooting.md | 2 +- .../dmn/decision-literal-expression.md | 2 +- .../dmn/decision-requirements-graph.md | 2 +- .../modeler/dmn/decision-table-input.md | 2 +- .../modeler/dmn/decision-table-output.md | 2 +- .../components/modeler/dmn/decision-table.md | 2 +- .../components/modeler/dmn/dmn-data-types.md | 2 +- .../modeler/forms/camunda-forms-reference.md | 4 +- .../web-modeler/collaborate-with-modes.md | 2 +- .../modeler/web-modeler/collaboration.md | 8 ++-- .../web-modeler/design-your-process.md | 2 +- .../web-modeler/implement-your-process.md | 2 +- .../modeler/web-modeler/import-diagram.md | 2 +- .../web-modeler/launch-cloud-modeler.md | 6 +-- .../modeler/web-modeler/milestones.md | 2 +- .../web-modeler/model-your-first-diagram.md | 2 +- .../modeler/web-modeler/new-web-modeler.md | 2 +- .../modeler/web-modeler/play-your-process.md | 2 +- .../run-or-publish-your-process.md | 12 +++--- .../modeler/web-modeler/save-and-deploy.md | 2 +- .../helm-kubernetes/upgrade.md | 2 +- versioned_sidebars/version-8.1-sidebars.json | 2 +- versioned_sidebars/version-8.2-sidebars.json | 2 +- 113 files changed, 215 insertions(+), 209 deletions(-) rename docs/components/modeler/desktop-modeler/{connect-to-camunda-platform-8.md => connect-to-camunda-8.md} (64%) rename versioned_docs/version-8.1/components/modeler/desktop-modeler/{connect-to-camunda-platform-8.md => connect-to-camunda-8.md} (81%) rename versioned_docs/version-8.2/components/modeler/desktop-modeler/{connect-to-camunda-platform-8.md => connect-to-camunda-8.md} (64%) diff --git a/docs/components/modeler/about-modeler.md b/docs/components/modeler/about-modeler.md index 71780a18de0..ded90336408 100644 --- a/docs/components/modeler/about-modeler.md +++ b/docs/components/modeler/about-modeler.md @@ -5,7 +5,7 @@ description: "Any executable process needs a BPMN diagram designed and configure keywords: ["process mapping tool"] --- -Camunda Platform 8 only +Camunda 8 only Any executable process needs a **[Business Process Model and Notation (BPMN)](./bpmn/bpmn.md) diagram** designed and configured beforehand. @@ -15,7 +15,7 @@ In tandem, different events and implementation details (such as the conditions w Camunda offers two tools to design and implement your diagrams: -- [Web Modeler](./web-modeler/launch-cloud-modeler.md): Integrate seamlessly with Camunda Platform 8 SaaS and Self-Managed installations alongside [Console](../console/introduction-to-console.md). +- [Web Modeler](./web-modeler/launch-cloud-modeler.md): Integrate seamlessly with Camunda 8 SaaS and Self-Managed installations alongside [Console](../console/introduction-to-console.md). - [Desktop Modeler](./desktop-modeler/index.md): Design, view, and edit models using this desktop application. Install and use Desktop Modeler locally, all while integrating your local development environment. :::note @@ -26,7 +26,7 @@ In this guide, we'll demonstrate modeling BPMN diagrams using both Web Modeler a ## Next steps -- [Modeling BPMN](/guides/automating-a-process-using-bpmn.md) - Learn how to model an automated process in this tutorial using Web Modeler with Camunda Platform 8 SaaS. +- [Modeling BPMN](/guides/automating-a-process-using-bpmn.md) - Learn how to model an automated process in this tutorial using Web Modeler with Camunda 8 SaaS. - [Camunda Forms](/guides/utilizing-forms.md) - Design and configure forms, and connect them to a user task or start event to implement a task form in your application. - [DMN](./dmn/dmn.md) - In DMN, model and execute decisions using the same language. As a business analyst, model the rules that lead to a decision in comprehensive tables, and execute these tables directly by a decision engine like Camunda. - [Out-of-the-box Connectors](/guides/configuring-out-of-the-box-connector.md) - Utilize pre-built connectivity with a number of outside systems. Connectors are modular by nature, reusable, and accelerate automation across those systems. diff --git a/docs/components/modeler/bpmn/bpmn.md b/docs/components/modeler/bpmn/bpmn.md index e866f60b75b..23cfe55faa2 100644 --- a/docs/components/modeler/bpmn/bpmn.md +++ b/docs/components/modeler/bpmn/bpmn.md @@ -5,7 +5,7 @@ description: Let's start modeling by creating a BPMN diagram. --- :::note -BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda Platform 7 in Camunda Platform 8, or vice versa, at this time. +BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda 7 in Camunda 8, or vice versa, at this time. ::: ## Start modeling diff --git a/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md b/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md index b65061ae0df..54d35d613ae 100644 --- a/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md +++ b/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md @@ -10,7 +10,7 @@ modeled in [Decision Model and Notation](https://www.omg.org/dmn/) (DMN). ![task](assets/business-rule-task.png) :::info -Camunda Platform 8 supports alternative task implementations for the business rule task. If you want +Camunda 8 supports alternative task implementations for the business rule task. If you want to use your own implementation for a business rule task, refer to the [job worker implementation](#job-worker-implementation) section below. The sections before this job worker implementation apply to the DMN decision implementation only. diff --git a/docs/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md b/docs/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md index b201349d91f..f882fbb42fd 100644 --- a/docs/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md +++ b/docs/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md @@ -6,7 +6,7 @@ description: "An inclusive gateway (or OR-gateway) allows you to make multiple d :::note -Currently, Camunda Platform 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. +Currently, Camunda 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. ::: diff --git a/docs/components/modeler/bpmn/script-tasks/script-tasks.md b/docs/components/modeler/bpmn/script-tasks/script-tasks.md index 5a58b43828e..f7f0b7e824e 100644 --- a/docs/components/modeler/bpmn/script-tasks/script-tasks.md +++ b/docs/components/modeler/bpmn/script-tasks/script-tasks.md @@ -11,7 +11,7 @@ JavaScript, or Python. ![task](assets/script-task.png) :::info -Camunda Platform 8 supports alternative task implementations for the script task. To use your own +Camunda 8 supports alternative task implementations for the script task. To use your own implementation for a script task, refer to the [job worker implementation](#job-worker-implementation) section below. The sections before this job worker implementation apply to the [FEEL expression](/components/modeler/feel/language-guide/feel-expressions-introduction.md) implementation only. diff --git a/docs/components/modeler/bpmn/user-tasks/user-tasks.md b/docs/components/modeler/bpmn/user-tasks/user-tasks.md index 958362e3381..8431ca01b96 100644 --- a/docs/components/modeler/bpmn/user-tasks/user-tasks.md +++ b/docs/components/modeler/bpmn/user-tasks/user-tasks.md @@ -47,12 +47,12 @@ For [Tasklist](/components/tasklist/introduction-to-tasklist.md) to claim the ta the value of the `assignee` must be the user's **unique identifier**. The unique identifier depends on the authentication method used to login to Tasklist: -- Camunda Platform 8 (login with email, Google, GitHub): `email` +- Camunda 8 (login with email, Google, GitHub): `email` - Default Basic Auth (elasticsearch): `username` - IAM: `username` :::note -For example, say you log into Tasklist using Camunda Platform 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. +For example, say you log into Tasklist using Camunda 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. ::: ## Scheduling diff --git a/docs/components/modeler/data-handling.md b/docs/components/modeler/data-handling.md index f5bc1fe5e6b..9b0f818dc21 100644 --- a/docs/components/modeler/data-handling.md +++ b/docs/components/modeler/data-handling.md @@ -4,7 +4,7 @@ title: Data handling description: "Get editor support for variables by defining the variables in the process model." --- -Camunda Platform 8 only +Camunda 8 only The FEEL editor will suggest variables in the current element's scope when defining input and output mappings in a process. The variables created by the mapping are automatically picked up and added to the suggestions. diff --git a/docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md b/docs/components/modeler/desktop-modeler/connect-to-camunda-8.md similarity index 64% rename from docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md rename to docs/components/modeler/desktop-modeler/connect-to-camunda-8.md index f832f940ea1..26616b27b24 100644 --- a/docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md +++ b/docs/components/modeler/desktop-modeler/connect-to-camunda-8.md @@ -1,10 +1,10 @@ --- -id: connect-to-camunda-platform-8 +id: connect-to-camunda-8 title: Deploy your first diagram -description: "Follow these steps to directly deploy diagrams and start process instances in Camunda Platform 8." +description: "Follow these steps to directly deploy diagrams and start process instances in Camunda 8." --- -Desktop Modeler can directly deploy diagrams and start process instances in Camunda Platform 8. Follow the steps below to deploy a diagram to **Camunda Platform 8 SaaS**. To deploy to a local installation, visit the [Camunda Platform 8 Self-Managed guide](../../../self-managed/modeler/desktop-modeler/deploy-to-self-managed.md). +Desktop Modeler can directly deploy diagrams and start process instances in Camunda 8. Follow the steps below to deploy a diagram to **Camunda 8 SaaS**. To deploy to a local installation, visit the [Camunda 8 Self-Managed guide](../../../self-managed/modeler/desktop-modeler/deploy-to-self-managed.md). 1. Click the deployment icon: @@ -16,7 +16,7 @@ Desktop Modeler can directly deploy diagrams and start process instances in Camu 3. Input the `Cluster URL` and the credentials (`Client ID`, `Client Secret`) of your [API client](../../console/manage-clusters/manage-api-clients.md): -![deployment via Camunda Platform 8](./img/deploy-diagram-camunda-cloud-remember.png) +![deployment via Camunda 8](./img/deploy-diagram-camunda-cloud-remember.png) 4. Toggle **Remember credentials** to locally store the connection information. diff --git a/docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md b/docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md index 0c2f4229e48..359d2997bca 100644 --- a/docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md +++ b/docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md @@ -1,10 +1,10 @@ --- id: c7-defining-templates -title: Defining templates in Camunda Platform 7 +title: Defining templates in Camunda 7 description: "Learn about JSON schema compatibility, supported BPMN types, defining template properties, and more." --- -Camunda Platform 7 only +Camunda 7 only Templates are defined in template descriptor files as a JSON array: @@ -64,7 +64,7 @@ For example, given the following `$schema` definition, the application takes `0. "$schema": "https://unpkg.com/@camunda/element-templates-json-schema@0.9.1/resources/schema.json" ``` -The JSON schema versioning is backward-compatible, meaning all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON schema version for Camunda Platform 7 element templates. +The JSON schema versioning is backward-compatible, meaning all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON schema version for Camunda 7 element templates. ## Supported BPMN types @@ -215,7 +215,7 @@ The resulting properties panel control looks like this: #### Omitted type :::note -Omitting the type is supported in Camunda Platform 7 element templates only. +Omitting the type is supported in Camunda 7 element templates only. ::: By omitting the `type` configuration, the default UI component is rendered for the respective binding. @@ -328,7 +328,7 @@ Notice that adherence to the following configuration options is enforced by desi ### Scoped bindings -Scoped bindings allow you to configure nested elements, such as [Camunda Platform 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). +Scoped bindings allow you to configure nested elements, such as [Camunda 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). ```json { @@ -366,7 +366,7 @@ exposed to the user in a separate custom fields section. #### Supported scopes -Camunda Platform 7 supports the following scope bindings: +Camunda 7 supports the following scope bindings: | Name | Target | | ------------------- | ------------------------------------------------------------------------------------------ | diff --git a/docs/components/modeler/desktop-modeler/element-templates/defining-templates.md b/docs/components/modeler/desktop-modeler/element-templates/defining-templates.md index ebddf8beb9d..f0c3b2edf86 100644 --- a/docs/components/modeler/desktop-modeler/element-templates/defining-templates.md +++ b/docs/components/modeler/desktop-modeler/element-templates/defining-templates.md @@ -37,7 +37,7 @@ As seen in the code snippet, a template consists of a number of important compon :::note -The `$schema` attribute is **required** for Camunda Platform 8 element templates. +The `$schema` attribute is **required** for Camunda 8 element templates. ::: Example: diff --git a/docs/components/modeler/desktop-modeler/flags/flags.md b/docs/components/modeler/desktop-modeler/flags/flags.md index 95db46b2c52..c770dacfa06 100644 --- a/docs/components/modeler/desktop-modeler/flags/flags.md +++ b/docs/components/modeler/desktop-modeler/flags/flags.md @@ -80,7 +80,7 @@ To display a custom version information in the status bar of the app, configure > :information_source: The Modeler will read trusted certificates from your operating system's trust store. -Provide additional certificates to validate secured connections to a Camunda Platform 8 installation. +Provide additional certificates to validate secured connections to a Camunda 8 installation. Configure your `flags.json` like this: @@ -92,7 +92,7 @@ Configure your `flags.json` like this: Additional information adapted from the [upstream documentation](https://nodejs.org/docs/latest/api/tls.html#tlscreatesecurecontextoptions): -> The peer (Camunda Platform 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. +> The peer (Camunda 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. ### Default execution platform version diff --git a/docs/components/modeler/desktop-modeler/index.md b/docs/components/modeler/desktop-modeler/index.md index 84139cbfa5b..e8d12678c05 100644 --- a/docs/components/modeler/desktop-modeler/index.md +++ b/docs/components/modeler/desktop-modeler/index.md @@ -2,10 +2,10 @@ id: index title: Desktop Modeler sidebar_label: About -description: "Camunda Desktop Modeler is a desktop app for modeling BPMN, DMN, and Forms, compatible with Camunda Platform 7 and Camunda Platform 8." +description: "Camunda Desktop Modeler is a desktop app for modeling BPMN, DMN, and Forms, compatible with Camunda 7 and Camunda 8." --- -Camunda Platform 7 and 8 +Camunda 7 and 8 Desktop Modeler is a desktop application for modeling BPMN, DMN, and Forms and supports you in building executable diagrams with Camunda. @@ -14,7 +14,7 @@ Desktop Modeler is a desktop application for modeling BPMN, DMN, and Forms and s ## Features - Design [BPMN](../bpmn/bpmn.md), [DMN](../dmn/dmn.md), and [Forms](../forms/camunda-forms-reference.md) -- Implement process applications for Camunda Platform 7 and 8 +- Implement process applications for Camunda 7 and 8 - Deploy and run processes directly from the application - Validate your diagrams using [configurable lint rules](https://github.com/camunda/camunda-modeler-custom-linter-rules-plugin) - [Customize](./flags/flags.md) and [extend](./plugins/plugins.md) the application @@ -25,7 +25,7 @@ Download the app for Windows, Linux, or MacOS from the [Camunda downloads page]( ## Get started -Learn how to [develop your first process](./model-your-first-diagram.md) and [deploy it](./connect-to-camunda-platform-8.md) to Camunda Platform 8. +Learn how to [develop your first process](./model-your-first-diagram.md) and [deploy it](./connect-to-camunda-8.md) to Camunda 8. ## Resources diff --git a/docs/components/modeler/desktop-modeler/model-your-first-diagram.md b/docs/components/modeler/desktop-modeler/model-your-first-diagram.md index 587cebfb3b7..a37ab52d7b3 100644 --- a/docs/components/modeler/desktop-modeler/model-your-first-diagram.md +++ b/docs/components/modeler/desktop-modeler/model-your-first-diagram.md @@ -25,4 +25,4 @@ Elements that support different types can be reconfigured by clicking on the cor ![properties panel](img/properties-panel.png) -5. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda Platform 8 cluster](./connect-to-camunda-platform-8.md). +1. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda 8 cluster](./connect-to-camunda-8.md). diff --git a/docs/components/modeler/desktop-modeler/start-instance.md b/docs/components/modeler/desktop-modeler/start-instance.md index 0dd7e5d10c5..99832ceb6d5 100644 --- a/docs/components/modeler/desktop-modeler/start-instance.md +++ b/docs/components/modeler/desktop-modeler/start-instance.md @@ -1,10 +1,10 @@ --- id: start-instance title: Start a new process instance -description: "After you have deployed your process to Camunda Platform 8, you can start a new instance of this process via the play icon." +description: "After you have deployed your process to Camunda 8, you can start a new instance of this process via the play icon." --- -After you have [deployed your process to Camunda Platform 8](./connect-to-camunda-platform-8.md), you can start a new instance of this process via the play icon: +After you have [deployed your process to Camunda 8](./connect-to-camunda-8.md), you can start a new instance of this process via the play icon: ![start instance icon](./img/start-instance-icon.png) diff --git a/docs/components/modeler/desktop-modeler/telemetry/telemetry.md b/docs/components/modeler/desktop-modeler/telemetry/telemetry.md index bb65745b55a..36a5446325b 100644 --- a/docs/components/modeler/desktop-modeler/telemetry/telemetry.md +++ b/docs/components/modeler/desktop-modeler/telemetry/telemetry.md @@ -61,8 +61,8 @@ These events include the following properties: The `Deployment Event` is sent in the following situations: -- User deploys a BPMN or DMN diagram to Camunda Platform 7 or Camunda Platform 8 -- User deploys a Form to Camunda Platform 7 +- User deploys a BPMN or DMN diagram to Camunda 7 or Camunda 8 +- User deploys a Form to Camunda 7 The `Deployment Event` and `Start Instance` have the following properties: diff --git a/docs/components/modeler/desktop-modeler/troubleshooting.md b/docs/components/modeler/desktop-modeler/troubleshooting.md index 23782d42d09..92436eb3665 100644 --- a/docs/components/modeler/desktop-modeler/troubleshooting.md +++ b/docs/components/modeler/desktop-modeler/troubleshooting.md @@ -76,7 +76,7 @@ You can connect to Zeebe via [`zbctl`](../../../apis-tools/cli-client/index.md) ### Secure connection to Zeebe fails -When connecting securely to Camunda Platform 8 SaaS, Camunda Platform 8 Self-Managed, or a standalone Zeebe instance (via `https` endpoint URL), Desktop Modeler tries to establish a secure connection. In the process, it strictly validates the server certificates presented against well-known certificate authorities. Failure to connect may have several reasons: +When connecting securely to Camunda 8 SaaS, Camunda 8 Self-Managed, or a standalone Zeebe instance (via `https` endpoint URL), Desktop Modeler tries to establish a secure connection. In the process, it strictly validates the server certificates presented against well-known certificate authorities. Failure to connect may have several reasons: #### The (remote) endpoint is not configured for secure connections diff --git a/docs/components/modeler/dmn/decision-requirements-graph.md b/docs/components/modeler/dmn/decision-requirements-graph.md index 93715c44f2d..04efa0946b6 100644 --- a/docs/components/modeler/dmn/decision-requirements-graph.md +++ b/docs/components/modeler/dmn/decision-requirements-graph.md @@ -49,7 +49,7 @@ The name describes the DRG. It is set as the `name` attribute on the `definition The id is the technical identifier of the DRG. It is set in the `id` attribute on the `definitions` element. -Each DRG should have an unique id when it is deployed to the Camunda Platform. +Each DRG should have an unique id when it is deployed to Camunda. ```xml diff --git a/docs/components/modeler/dmn/decision-table-input.md b/docs/components/modeler/dmn/decision-table-input.md index 043d78a6375..479d9f181ad 100644 --- a/docs/components/modeler/dmn/decision-table-input.md +++ b/docs/components/modeler/dmn/decision-table-input.md @@ -33,7 +33,7 @@ XML element. ## Input id -The input id is a unique identifier of the decision table input. It is used by the Camunda Platform to reference the +The input id is a unique identifier of the decision table input. It is used by Camunda to reference the input clause. Therefore, it is required. It is set as the `id` attribute of the `input` XML element. ```xml diff --git a/docs/components/modeler/dmn/decision-table-output.md b/docs/components/modeler/dmn/decision-table-output.md index cc0425dcf75..61c74f129d5 100644 --- a/docs/components/modeler/dmn/decision-table-output.md +++ b/docs/components/modeler/dmn/decision-table-output.md @@ -29,7 +29,7 @@ XML element. ## Output id -The output id is a unique identifier of the decision table output. It is used by the Camunda Platform to reference the +The output id is a unique identifier of the decision table output. It is used by Camunda to reference the output clause. Therefore, it is required. It is set as the `id` attribute of the `output` XML element. ```xml diff --git a/docs/components/modeler/dmn/decision-table.md b/docs/components/modeler/dmn/decision-table.md index 4b2cb1e90cb..b9d9f9a3c30 100644 --- a/docs/components/modeler/dmn/decision-table.md +++ b/docs/components/modeler/dmn/decision-table.md @@ -49,7 +49,7 @@ The id is the technical identifier of the decision. It is set in the `id` attribute on the `decision` element. Just as the `name`, the `id` can be changed via the Properties Panel after selecting the respective "Decision" in the Decision Requirements Diagram view. -Each decision should have an unique id when it is deployed to the Camunda Platform. +Each decision should have an unique id when it is deployed to Camunda. :::caution diff --git a/docs/components/modeler/dmn/dmn-data-types.md b/docs/components/modeler/dmn/dmn-data-types.md index b52ff6c39a4..fa44f27d1b0 100644 --- a/docs/components/modeler/dmn/dmn-data-types.md +++ b/docs/components/modeler/dmn/dmn-data-types.md @@ -4,7 +4,7 @@ title: Data types description: On overview of the available data types in DMN. --- -The Camunda Platform supports the following data types for DMN: +Camunda supports the following data types for DMN: | Type name | Associated FEEL type | | ----------------- | --------------------------------------------------------------------------------------------------------- | diff --git a/docs/components/modeler/forms/camunda-forms-reference.md b/docs/components/modeler/forms/camunda-forms-reference.md index 431b305f938..830a960114b 100644 --- a/docs/components/modeler/forms/camunda-forms-reference.md +++ b/docs/components/modeler/forms/camunda-forms-reference.md @@ -5,12 +5,12 @@ description: Streamline your human workflows with the help of Camunda Forms --- :::note Support for Camunda Forms -The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda Platform 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda Platform 7 version 7.15.0 or later. +The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda 7 version 7.15.0 or later. ::: The Camunda Forms feature allows you to design and configure forms. Once configured, they can be connected to a user task or start event to implement a task form in your application. -While you can incorporate Camunda Forms solely within Camunda Platform 8, you can also utilize Camunda Forms in Camunda Platform 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. +While you can incorporate Camunda Forms solely within Camunda 8, you can also utilize Camunda Forms in Camunda 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. To learn more about how Camunda Forms are created in Camunda Modeler and embedded in Camunda Tasklist, visit our guide on [user task forms](../../../guides/utilizing-forms.md). diff --git a/docs/components/modeler/reference/modeling-guidance/rules/element-type.md b/docs/components/modeler/reference/modeling-guidance/rules/element-type.md index 1fcfc93a676..8592ad65325 100644 --- a/docs/components/modeler/reference/modeling-guidance/rules/element-type.md +++ b/docs/components/modeler/reference/modeling-guidance/rules/element-type.md @@ -6,7 +6,7 @@ description: Reference for the `element-type` rule. import MarkerGuideline from "@site/src/mdx/MarkerGuideline"; -The element you modeled is not [supported for execution](../../../../bpmn/bpmn-coverage/) by the selected Camunda Platform version. It may be supported in a later version. +The element you modeled is not [supported for execution](../../../../bpmn/bpmn-coverage/) by the selected Camunda version. It may be supported in a later version. ## Element type not supported by selected version diff --git a/docs/components/modeler/web-modeler/advanced-modeling/publish-public-processes.md b/docs/components/modeler/web-modeler/advanced-modeling/publish-public-processes.md index 6dbaf02851f..a4744cad5b9 100644 --- a/docs/components/modeler/web-modeler/advanced-modeling/publish-public-processes.md +++ b/docs/components/modeler/web-modeler/advanced-modeling/publish-public-processes.md @@ -1,7 +1,7 @@ --- id: publish-public-processes title: Publish processes via a form -description: "Share executable processes publicly with anyone from Web Modeler on Camunda Platform 8 SaaS." +description: "Share executable processes publicly with anyone from Web Modeler on Camunda 8 SaaS." --- import CreateFormImg from '../img/create-form.png'; @@ -13,9 +13,9 @@ import ImplementModeImg from '../img/implement-mode-active.png'; import PublicLinkImg from '../img/public-link.png'; import PublicFormImg from '../img/public-form.png'; -Camunda Platform 8 SaaS only +Camunda 8 SaaS only -Camunda Platform 8 SaaS offers a convenient solution for process developers who want to make their processes accessible to users without requiring them to sign up to the platform or understand how tasks and processes work. +Camunda 8 SaaS offers a convenient solution for process developers who want to make their processes accessible to users without requiring them to sign up to the platform or understand how tasks and processes work. This feature is particularly useful when you want to gather data or initiate a process from users who are not part of your organization or do not have direct access to Camunda. It also allows you to rapidly test a process with your peers in a development environment. @@ -98,7 +98,7 @@ To update a public form, follow these steps: ### What are the benefits of publishing a process via a public form? -- **Easy access for external users:** External users can start process instances without the need for Camunda Platform access, making it convenient for them to participate in your business processes. +- **Easy access for external users:** External users can start process instances without the need for Camunda access, making it convenient for them to participate in your business processes. - **Efficient data collection:** The public form enables you to gather structured and validated data from external users, ensuring the accuracy and completeness of the information required for your process. - **Rapid testing and feedback:** By sharing the public form with your peers in a development environment, you can quickly test and gather feedback on the process before deploying it to a wider audience. - **Improved collaboration:** Involving external users through the public form fosters collaboration and engagement, allowing stakeholders, customers, or partners to participate in your business processes. diff --git a/docs/components/modeler/web-modeler/collaborate-with-modes.md b/docs/components/modeler/web-modeler/collaborate-with-modes.md index 6ce876d6d90..267a32211e0 100644 --- a/docs/components/modeler/web-modeler/collaborate-with-modes.md +++ b/docs/components/modeler/web-modeler/collaborate-with-modes.md @@ -4,7 +4,7 @@ title: Collaborate with modes description: "Dedicated modes are ways for business and IT professionals to collaborate effectively." --- -Camunda Platform 8 only +Camunda 8 only Collaboration between business and IT professionals can be challenging, which is why we introduced three modes in BPMN diagrams that help users with different technical backgrounds to collaborate effectively: **design**, **implement**, and **play**. diff --git a/docs/components/modeler/web-modeler/collaboration.md b/docs/components/modeler/web-modeler/collaboration.md index 5f80626be3a..e0b6abeab71 100644 --- a/docs/components/modeler/web-modeler/collaboration.md +++ b/docs/components/modeler/web-modeler/collaboration.md @@ -4,21 +4,21 @@ title: Collaborate with your team description: Collaboration features and access rights for Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only ## Projects Files and folders are stored in projects. The user access on files and folders is defined at the project level. -When you access Web Modeler via the Camunda Platform 8 dashboard, you can note the **Home** page with all the projects you can access: +When you access Web Modeler via the Camunda 8 dashboard, you can note the **Home** page with all the projects you can access: ![home page](img/collaboration/web-modeler-home.png) ### Access rights and permissions Users can have various levels of access to a project in Web Modeler, outlined in this section. -After creating a project, you can invite members of your Camunda Platform 8 organization to collaborate in Web Modeler. +After creating a project, you can invite members of your Camunda 8 organization to collaborate in Web Modeler. There are four roles with different levels of access rights that can be assigned to each user: - **Project Admin**: The user can edit the project itself, all folders and diagrams within the project, and invite more users to collaborate. @@ -51,7 +51,7 @@ On the right side of a project, view a list of your collaborators and invite mor 2. Choose a role for your new collaborator. ![invite choose role](img/collaboration/web-modeler-collaborator-invite-choose-role.png) -3. Begin typing the name of the individual and Web Modeler will suggest Camunda Platform 8 organization members that you can invite to the project. +3. Begin typing the name of the individual and Web Modeler will suggest Camunda 8 organization members that you can invite to the project. ![invite suggestions](img/collaboration/web-modeler-collaborator-invite-suggestions.png) 4. Write a message to your new collaborator about their invitation to the project. diff --git a/docs/components/modeler/web-modeler/design-your-process.md b/docs/components/modeler/web-modeler/design-your-process.md index 6621f627fab..33ebd4c8e34 100644 --- a/docs/components/modeler/web-modeler/design-your-process.md +++ b/docs/components/modeler/web-modeler/design-your-process.md @@ -4,7 +4,7 @@ title: Design mode for business users description: "Design mode is tailored to business users and allows strategic modeling" --- -Camunda Platform 8 only +Camunda 8 only In the **Design** mode view, business users have access to a different workspace of Web Modeler with a reduced properties panel. Only comments are shown, which provides a decluttered user interface. diff --git a/docs/components/modeler/web-modeler/implement-your-process.md b/docs/components/modeler/web-modeler/implement-your-process.md index 3e368bb5e95..8db9636d616 100644 --- a/docs/components/modeler/web-modeler/implement-your-process.md +++ b/docs/components/modeler/web-modeler/implement-your-process.md @@ -4,7 +4,7 @@ title: Implement mode for developers description: "Implement mode is tailored to developers and allows full access to an implementation-focused workspace." --- -Camunda Platform 8 only +Camunda 8 only In the **Implement** mode view, developers have access to a full, implementation-focused workspace of Web Modeler. diff --git a/docs/components/modeler/web-modeler/import-diagram.md b/docs/components/modeler/web-modeler/import-diagram.md index a5610e3df50..41201206215 100644 --- a/docs/components/modeler/web-modeler/import-diagram.md +++ b/docs/components/modeler/web-modeler/import-diagram.md @@ -4,7 +4,7 @@ title: Import diagram description: "You can import a BPMN or DMN diagram at any time with Web Modeler." --- -Camunda Platform 8 only +Camunda 8 only You can import a BPMN or DMN diagram at any time with Web Modeler, and there are several ways to accomplish this: diff --git a/docs/components/modeler/web-modeler/launch-cloud-modeler.md b/docs/components/modeler/web-modeler/launch-cloud-modeler.md index b70eef0c390..b99882efed9 100644 --- a/docs/components/modeler/web-modeler/launch-cloud-modeler.md +++ b/docs/components/modeler/web-modeler/launch-cloud-modeler.md @@ -1,12 +1,12 @@ --- id: launch-cloud-modeler title: Launch Web Modeler -description: "Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." +description: "Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." --- -Camunda Platform 8 only +Camunda 8 only -Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. +Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, follow the steps below: diff --git a/docs/components/modeler/web-modeler/milestones.md b/docs/components/modeler/web-modeler/milestones.md index d6bb2cf83f9..2c6a642a847 100644 --- a/docs/components/modeler/web-modeler/milestones.md +++ b/docs/components/modeler/web-modeler/milestones.md @@ -4,7 +4,7 @@ title: Milestones description: Working with milestones in Web Modeler --- -Camunda Platform 8 only +Camunda 8 only ## Milestones diff --git a/docs/components/modeler/web-modeler/model-your-first-diagram.md b/docs/components/modeler/web-modeler/model-your-first-diagram.md index 740a99b130e..b3ef8ba4100 100644 --- a/docs/components/modeler/web-modeler/model-your-first-diagram.md +++ b/docs/components/modeler/web-modeler/model-your-first-diagram.md @@ -4,7 +4,7 @@ title: Model your first diagram description: "After you've created a BPMN diagram, you can start modeling it." --- -Camunda Platform 8 only +Camunda 8 only After you've created a BPMN diagram, you can start modeling it. diff --git a/docs/components/modeler/web-modeler/new-web-modeler.md b/docs/components/modeler/web-modeler/new-web-modeler.md index ded045bb126..aa52409a650 100644 --- a/docs/components/modeler/web-modeler/new-web-modeler.md +++ b/docs/components/modeler/web-modeler/new-web-modeler.md @@ -4,7 +4,7 @@ title: New Web Modeler description: Your data was automatically migrated from the old Cloud Modeler to the new Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only If you used our old Cloud Modeler (before March 2022), all of your data has been migrated to the new Web Modeler. diff --git a/docs/components/modeler/web-modeler/play-your-process.md b/docs/components/modeler/web-modeler/play-your-process.md index aaf00878873..e39615d5106 100644 --- a/docs/components/modeler/web-modeler/play-your-process.md +++ b/docs/components/modeler/web-modeler/play-your-process.md @@ -4,7 +4,7 @@ title: Play mode for rapid validation description: "Play mode gives developers a playground environment to quickly iterate and manually test their processes." --- -Camunda Platform 8 only +Camunda 8 only In the **Play** mode, developers have access to a Zeebe-powered playground environment within Web Modeler. diff --git a/docs/components/modeler/web-modeler/run-or-publish-your-process.md b/docs/components/modeler/web-modeler/run-or-publish-your-process.md index 12835ae8fee..e2f359cec10 100644 --- a/docs/components/modeler/web-modeler/run-or-publish-your-process.md +++ b/docs/components/modeler/web-modeler/run-or-publish-your-process.md @@ -18,9 +18,9 @@ import WebhookPanelImg from './img/web-modeler-webhook-panel.png'; import ConvertToWebhookImg from './img/web-modeler-convert-to-webhook.png'; import TasklistProcessesImg from './img/tasklist-processes.png'; -Camunda Platform 8 only +Camunda 8 only -When you design a process in Camunda Modeler, you have multiple flexible options to either run or publish it on Camunda Platform 8. This page explains the differences between running and publishing a process, and outlines the various options to publish a process into any environment, and to any audience. +When you design a process in Camunda Modeler, you have multiple flexible options to either run or publish it on Camunda 8. This page explains the differences between running and publishing a process, and outlines the various options to publish a process into any environment, and to any audience. ## Deploy a process @@ -45,7 +45,7 @@ To perform any of these actions, make sure to be in **Implement** mode. ## Run a process -Running a process means that you execute the process as a process instance on Camunda Platform 8. It allows you to test and debug your process and observe how it performs in a live environment. +Running a process means that you execute the process as a process instance on Camunda 8. It allows you to test and debug your process and observe how it performs in a live environment. - [Test run using Play mode](#test-run-using-play-mode) - [Run programmatically](#deploy-to-run-programmatically) @@ -113,7 +113,7 @@ You can also define the success of your processes by setting key performance ind ## Publishing a process -Publishing a process means that you make it available to other users inside and outside of Camunda Platform 8. Once published, other users can access and start instances of the process. +Publishing a process means that you make it available to other users inside and outside of Camunda 8. Once published, other users can access and start instances of the process. You have the following options to publish a process: @@ -181,9 +181,9 @@ To learn more about publishing processes to Tasklist, refer to our [documentatio ### Publish via a public form -Camunda Platform 8 SaaS only +Camunda 8 SaaS only -Publishing a process via a public form allows you to share your process with external users who can start instances of the process without requiring access to Camunda Platform 8. This feature is particularly useful when you want to gather data or initiate a process from users who are not part of your organization or do not have direct access to Camunda. It also allows you to rapidly test a process with your peers in a development environment. +Publishing a process via a public form allows you to share your process with external users who can start instances of the process without requiring access to Camunda 8. This feature is particularly useful when you want to gather data or initiate a process from users who are not part of your organization or do not have direct access to Camunda. It also allows you to rapidly test a process with your peers in a development environment. A public form @@ -217,13 +217,13 @@ You can access the URL in the **Publication** tab of the **properties panel**, a Sharing a public link -When an external user accesses the public form URL, they can fill in the form fields and submit the data. Upon submission, a new process instance is automatically started in Camunda Platform 8, using the submitted data as input. +When an external user accesses the public form URL, they can fill in the form fields and submit the data. Upon submission, a new process instance is automatically started in Camunda 8, using the submitted data as input. For further configuration and how to unpublish a process again, refer to the [full documentation](./advanced-modeling/publish-public-processes.md). ### Listen to message or signal events -Camunda Platform 8 supports message and signal events, which can be used to trigger a process instance when a specific event occurs. Everyone on the platform that knows the message or signal correlation keys can call such a process. To listen to a message or signal event, you need to define a [message](../bpmn/message-events/message-events.md#message-start-events) or [signal start event](../bpmn/signal-events/signal-events.md#signal-start-events) in your process model and configure it to listen for the desired event. Follow these steps to configure a message or signal start event: +Camunda 8 supports message and signal events, which can be used to trigger a process instance when a specific event occurs. Everyone on the platform that knows the message or signal correlation keys can call such a process. To listen to a message or signal event, you need to define a [message](../bpmn/message-events/message-events.md#message-start-events) or [signal start event](../bpmn/signal-events/signal-events.md#signal-start-events) in your process model and configure it to listen for the desired event. Follow these steps to configure a message or signal start event: 1. Select the start event. 2. Change the start event type to a message or signal start event using the **wrench tool**. @@ -241,5 +241,5 @@ As soon as a matching event is received, a process instance will be started. To - Make sure that the process is accessible to the appropriate users only. :::note -When working on Camunda Platform 8 Self-Managed, you can define access permissions on a per-process level using [Identity Resource Authorizations](../../../self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). +When working on Camunda 8 Self-Managed, you can define access permissions on a per-process level using [Identity Resource Authorizations](../../../self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). ::: diff --git a/docs/components/modeler/web-modeler/save-and-deploy.md b/docs/components/modeler/web-modeler/save-and-deploy.md index d0d72c5f1d3..ae6f5497f55 100644 --- a/docs/components/modeler/web-modeler/save-and-deploy.md +++ b/docs/components/modeler/web-modeler/save-and-deploy.md @@ -4,7 +4,7 @@ title: Save and deploy your diagram description: "If a diagram is changed and autosaved, it has no effect on your cluster." --- -Camunda Platform 8 only +Camunda 8 only Web Modeler will autosave all your changes on a diagram. The changes will also be visible in real-time to any collaborators opening the same diagram. diff --git a/docs/self-managed/platform-deployment/helm-kubernetes/upgrade.md b/docs/self-managed/platform-deployment/helm-kubernetes/upgrade.md index db3a9cf54c2..4425d388d75 100644 --- a/docs/self-managed/platform-deployment/helm-kubernetes/upgrade.md +++ b/docs/self-managed/platform-deployment/helm-kubernetes/upgrade.md @@ -147,7 +147,7 @@ To authenticate: 2. [Assign permissions to the application](/docs/self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). 3. Connect with: -- [Desktop Modeler](/docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md). +- [Desktop Modeler](/docs/components/modeler/desktop-modeler/connect-to-camunda-8.md). - [Zeebe client (zbctl)](/docs/self-managed/zeebe-deployment/security/secure-client-communication/#zbctl). ### v8.2 diff --git a/optimize_sidebars.js b/optimize_sidebars.js index 03e4bcf3e5c..8e9dea6219d 100644 --- a/optimize_sidebars.js +++ b/optimize_sidebars.js @@ -233,7 +233,7 @@ module.exports = { ), docsLink( "Deploy your first diagram", - "components/modeler/desktop-modeler/connect-to-camunda-platform-8/" + "components/modeler/desktop-modeler/connect-to-camunda-8/" ), docsLink( "Start a new process instance", diff --git a/optimize_versioned_sidebars/version-3.10.0-sidebars.json b/optimize_versioned_sidebars/version-3.10.0-sidebars.json index b52c7bfdce5..c1c870f66e3 100644 --- a/optimize_versioned_sidebars/version-3.10.0-sidebars.json +++ b/optimize_versioned_sidebars/version-3.10.0-sidebars.json @@ -303,7 +303,7 @@ { "type": "link", "label": "Deploy your first diagram", - "href": "/docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8/" + "href": "/docs/components/modeler/desktop-modeler/connect-to-camunda-8/" }, { "type": "link", diff --git a/optimize_versioned_sidebars/version-3.9.0-sidebars.json b/optimize_versioned_sidebars/version-3.9.0-sidebars.json index b399d111c79..e08c9f72123 100644 --- a/optimize_versioned_sidebars/version-3.9.0-sidebars.json +++ b/optimize_versioned_sidebars/version-3.9.0-sidebars.json @@ -305,7 +305,7 @@ { "type": "link", "label": "Deploy your first diagram", - "href": "/docs/8.1/components/modeler/desktop-modeler/connect-to-camunda-platform-8/" + "href": "/docs/8.1/components/modeler/desktop-modeler/connect-to-camunda-8/" }, { "type": "link", diff --git a/sidebars.js b/sidebars.js index 2bfb2c610a9..d11edb35c31 100644 --- a/sidebars.js +++ b/sidebars.js @@ -190,7 +190,7 @@ module.exports = { items: [ "components/modeler/desktop-modeler/install-the-modeler", "components/modeler/desktop-modeler/model-your-first-diagram", - "components/modeler/desktop-modeler/connect-to-camunda-platform-8", + "components/modeler/desktop-modeler/connect-to-camunda-8", "components/modeler/desktop-modeler/start-instance", { type: "category", diff --git a/static/.htaccess b/static/.htaccess index c54d0961eee..0b0d207963c 100644 --- a/static/.htaccess +++ b/static/.htaccess @@ -6,6 +6,12 @@ RewriteRule (.*) https://%{SERVER_NAME}/$1 [R=301,L] # Disable directory listing and multi views Options -Indexes -MultiViews +# Rename Modeler Camunda 8 +RewriteRule ^docs/next/components/modeler/desktop-modeler/connect-to-camunda-platform-8/(.*)$ /docs/next/components/modeler/desktop-modeler/connect-to-camunda-8/$1 [R=301,L] +RewriteRule ^docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8/(.*)$ /docs/components/modeler/desktop-modeler/connect-to-camunda-8/$1 [R=301,L] +RewriteRule ^docs/8.2/components/modeler/desktop-modeler/connect-to-camunda-platform-8/(.*)$ /docs/8.2/components/modeler/desktop-modeler/connect-to-camunda-8/$1 [R=301,L] +RewriteRule ^docs/8.1/components/modeler/desktop-modeler/connect-to-camunda-platform-8/(.*)$ /docs/8.1/components/modeler/desktop-modeler/connect-to-camunda-8/$1 [R=301,L] + # Rename Concepts Camunda 8 RewriteRule ^docs/next/components/concepts/what-is-camunda-platform-8/(.*)$ /docs/next/components/concepts/what-is-camunda-8/$1 [R=301,L] RewriteRule ^docs/components/concepts/what-is-camunda-platform-8/(.*)$ /docs/components/concepts/what-is-camunda-8/$1 [R=301,L] diff --git a/versioned_docs/version-8.1/components/modeler/about-modeler.md b/versioned_docs/version-8.1/components/modeler/about-modeler.md index 6280300e281..5dcbabf7f9a 100644 --- a/versioned_docs/version-8.1/components/modeler/about-modeler.md +++ b/versioned_docs/version-8.1/components/modeler/about-modeler.md @@ -4,7 +4,7 @@ title: About Modeler description: "Any executable process needs a BPMN diagram designed and configured beforehand. Camunda offers Web Modeler and Desktop Modeler to design and implement these." --- -Camunda Platform 8 only +Camunda 8 only Any executable process needs a **BPMN diagram** designed and configured beforehand. @@ -17,7 +17,7 @@ Camunda offers a few tools to design your diagrams and implement them: - [Web Modeler](./web-modeler/launch-cloud-modeler.md) - [Desktop Modeler](./desktop-modeler/install-the-modeler.md) -Web Modeler and Desktop Modeler differ mainly in their environment. Web Modeler is part of Cloud Console and offers a seamless integration into Camunda Platform 8 to model BPMN. Desktop Modeler is a desktop application that can be installed and used locally, all while integrating your local development environment. +Web Modeler and Desktop Modeler differ mainly in their environment. Web Modeler is part of Cloud Console and offers a seamless integration into Camunda 8 to model BPMN. Desktop Modeler is a desktop application that can be installed and used locally, all while integrating your local development environment. :::note Interested in editing the underlying XML of BPMN and DMN diagrams directly? Be sure to utilize Desktop Modeler, as it features an XML editor tab. The XML editor comes with its own history (undo or redo), search and replace functionality, and XML syntax highlighting. diff --git a/versioned_docs/version-8.1/components/modeler/bpmn/bpmn-coverage.md b/versioned_docs/version-8.1/components/modeler/bpmn/bpmn-coverage.md index 9dd5a7f19a0..81157e59b10 100644 --- a/versioned_docs/version-8.1/components/modeler/bpmn/bpmn-coverage.md +++ b/versioned_docs/version-8.1/components/modeler/bpmn/bpmn-coverage.md @@ -10,7 +10,7 @@ export const Highlight = ({children, color}) => ( ); -The following BPMN elements are supported by our modeling tools. Elements highlighted in green are supported for execution by Camunda Platform 8. Click on an element to navigate to the documentation. +The following BPMN elements are supported by our modeling tools. Elements highlighted in green are supported for execution by Camunda 8. Click on an element to navigate to the documentation. ## Participants diff --git a/versioned_docs/version-8.1/components/modeler/bpmn/bpmn.md b/versioned_docs/version-8.1/components/modeler/bpmn/bpmn.md index 3e614d10dfd..d65d6cc3425 100644 --- a/versioned_docs/version-8.1/components/modeler/bpmn/bpmn.md +++ b/versioned_docs/version-8.1/components/modeler/bpmn/bpmn.md @@ -7,7 +7,7 @@ description: Let's start modeling by creating a BPMN diagram. # Model a BPMN 2.0 diagram :::note -BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda Platform 7 in Camunda Platform 8, or vice versa, at this time. +BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda 7 in Camunda 8, or vice versa, at this time. ::: ## Start modeling diff --git a/versioned_docs/version-8.1/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md b/versioned_docs/version-8.1/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md index 41f14dea4c5..415418ffebe 100644 --- a/versioned_docs/version-8.1/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md +++ b/versioned_docs/version-8.1/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md @@ -10,7 +10,7 @@ modeled in [Decision Model and Notation](https://www.omg.org/dmn/) (DMN). ![task](assets/business-rule-task.png) :::info -Camunda Platform 8 supports alternative task implementations for the business rule task. If you want +Camunda 8 supports alternative task implementations for the business rule task. If you want to use your own implementation for a business rule task, see the [job worker implementation](#job-worker-implementation) section below. The sections before this job worker implementation apply to the DMN decision implementation only. diff --git a/versioned_docs/version-8.1/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md b/versioned_docs/version-8.1/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md index b201349d91f..f882fbb42fd 100644 --- a/versioned_docs/version-8.1/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md +++ b/versioned_docs/version-8.1/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md @@ -6,7 +6,7 @@ description: "An inclusive gateway (or OR-gateway) allows you to make multiple d :::note -Currently, Camunda Platform 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. +Currently, Camunda 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. ::: diff --git a/versioned_docs/version-8.1/components/modeler/bpmn/user-tasks/user-tasks.md b/versioned_docs/version-8.1/components/modeler/bpmn/user-tasks/user-tasks.md index 07e33031039..86a4e22f873 100644 --- a/versioned_docs/version-8.1/components/modeler/bpmn/user-tasks/user-tasks.md +++ b/versioned_docs/version-8.1/components/modeler/bpmn/user-tasks/user-tasks.md @@ -46,12 +46,12 @@ For [Tasklist](/components/tasklist/introduction-to-tasklist.md) to claim the ta the value of the `assignee` must be the user's **unique identifier**. The unique identifier depends on the authentication method used to login to Tasklist: -- Camunda Platform 8 (login with email, Google, GitHub): `email` +- Camunda 8 (login with email, Google, GitHub): `email` - Default Basic Auth (elasticsearch): `username` - IAM: `username` :::note -For example, say you log into Tasklist using Camunda Platform 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. +For example, say you log into Tasklist using Camunda 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. ::: ## Variable mappings diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-8.md similarity index 81% rename from versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md rename to versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-8.md index db64e5a4e56..51191408485 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/connect-to-camunda-8.md @@ -1,9 +1,9 @@ --- -id: connect-to-camunda-platform-8 +id: connect-to-camunda-8 title: Deploy your first diagram --- -Desktop Modeler can directly deploy diagrams and start process instances in Camunda Platform 8. Follow the steps below to deploy a diagram: +Desktop Modeler can directly deploy diagrams and start process instances in Camunda 8. Follow the steps below to deploy a diagram: 1. Click the deployment icon: @@ -15,7 +15,7 @@ Desktop Modeler can directly deploy diagrams and start process instances in Camu 3. Input the `Cluster URL` and the credentials (`Client ID`, `Client Secret`) of your [API client](../../console/manage-clusters/manage-api-clients.md): -![deployment via Camunda Platform 8](./img/deploy-diagram-camunda-cloud-remember.png) +![deployment via Camunda 8](./img/deploy-diagram-camunda-cloud-remember.png) 4. Select the **Remember** checkbox if you want to locally store the connection information. diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/additional-resources.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/additional-resources.md index ebe924edc50..3798e44214b 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/additional-resources.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/additional-resources.md @@ -3,8 +3,8 @@ id: additional-resources title: Additional resources --- -Use the [Camunda Cloud Connect Plugin for Camunda Platform 7](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) to integrate Camunda Modeler with [Cawemo](https://cawemo.com/) and retrieve templates from a Cawemo catalog project. +Use the [Camunda Cloud Connect Plugin for Camunda 7](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) to integrate Camunda Modeler with [Cawemo](https://cawemo.com/) and retrieve templates from a Cawemo catalog project. -Try playing around with custom elements and our example templates for [Camunda Platform 7](https://github.com/camunda/camunda-modeler/tree/master/resources/element-templates/samples.json) or [Camunda Platform 8](https://github.com/camunda/camunda-modeler/tree/master/resources/element-templates/cloud-samples.json). +Try playing around with custom elements and our example templates for [Camunda 7](https://github.com/camunda/camunda-modeler/tree/master/resources/element-templates/samples.json) or [Camunda 8](https://github.com/camunda/camunda-modeler/tree/master/resources/element-templates/cloud-samples.json). If you get stuck, ask for help [in our forums](https://forum.camunda.org/c/modeler). diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/configuring-templates.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/configuring-templates.md index 4a5aeedbae9..7a0d8c96854 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/configuring-templates.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/configuring-templates.md @@ -5,8 +5,8 @@ title: Configuring templates Element templates are defined as [JSON files](../defining-templates). There are two ways to integrate them into Camunda Modeler: -1. **Local filesystem (Camunda Platform 8 or newer):** You can fetch the JSON templates from [here](/self-managed/connectors-deployment/install-and-start.md#connector-templates). Store element templates as `.json` file in the `resources/element-templates` folder, relative to the modelers executable _or_ relative to the modelers data directory ([see below](#example-setup)). Alternatively, they can be stored in a `.camunda/element-templates` directory that resides, relative to the currently opened diagram, anywhere in the diagrams path hierarchy. -2. **Retrieve from Cawemo (Camunda Platform 7 only):** use the [Camunda Cloud Connect Plugin for Camunda Platform 7](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) to integrate Camunda Modeler with [Cawemo](https://cawemo.com/). The Modeler can then retrieve templates from catalog projects setup in Cawemo. Note that the [Cloud Connect plugin](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) will keep Cawemo and your local Camunda Modeler installation in sync (e.g., deleting a template in Cawemo will delete it locally as well). Locally the synced templates will be stored in the `config.json` file in your [`{USER_DATA_DIRECTORY}`](../../search-paths#user-data-directory). You should not manually change the `config.json` unless you know what you're doing. +1. **Local filesystem (Camunda 8 or newer):** You can fetch the JSON templates from [here](/self-managed/connectors-deployment/install-and-start.md#connector-templates). Store element templates as `.json` file in the `resources/element-templates` folder, relative to the modelers executable _or_ relative to the modelers data directory ([see below](#example-setup)). Alternatively, they can be stored in a `.camunda/element-templates` directory that resides, relative to the currently opened diagram, anywhere in the diagrams path hierarchy. +2. **Retrieve from Cawemo (Camunda 7 only):** use the [Camunda Cloud Connect Plugin for Camunda 7](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) to integrate Camunda Modeler with [Cawemo](https://cawemo.com/). The Modeler can then retrieve templates from catalog projects setup in Cawemo. Note that the [Cloud Connect plugin](https://docs.camunda.org/cawemo/latest/technical-guide/integrations/modeler/) will keep Cawemo and your local Camunda Modeler installation in sync (e.g., deleting a template in Cawemo will delete it locally as well). Locally the synced templates will be stored in the `config.json` file in your [`{USER_DATA_DIRECTORY}`](../../search-paths#user-data-directory). You should not manually change the `config.json` unless you know what you're doing. New templates will be recognized when reconnecting to Cawemo or on Camunda Modeler reload/restart. diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/defining-templates.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/defining-templates.md index b560f605728..fc45c6c3063 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/defining-templates.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/defining-templates.md @@ -35,15 +35,15 @@ Templates are defined in template descriptor files as a JSON array: As seen in the code snippet a template consist of a number of important components: -- `$schema : String`: URI pointing towards the [JSON schema](https://json-schema.org/) which defines the structure of the element template `.json` file. Element template schemas are maintained in the [element templates JSON schema](https://github.com/camunda/element-templates-json-schema) repository. Following the [JSON schema](https://json-schema.org/) standard, you may use them for validation or to get assistance (e.g., auto-completion) when working with them in your favorite IDE. Note that the `$schema` attribute is **required** for Camunda Platform 8 element templates. +- `$schema : String`: URI pointing towards the [JSON schema](https://json-schema.org/) which defines the structure of the element template `.json` file. Element template schemas are maintained in the [element templates JSON schema](https://github.com/camunda/element-templates-json-schema) repository. Following the [JSON schema](https://json-schema.org/) standard, you may use them for validation or to get assistance (e.g., auto-completion) when working with them in your favorite IDE. Note that the `$schema` attribute is **required** for Camunda 8 element templates. - Camunda Platform 7 example: + Camunda 7 example: ```json "$schema": "https://unpkg.com/@camunda/element-templates-json-schema/resources/schema.json" ``` - Camunda Platform 8 example: + Camunda 8 example: ```json "$schema": "https://unpkg.com/@camunda/zeebe-element-templates-json-schema/resources/schema.json" @@ -62,8 +62,8 @@ As seen in the code snippet a template consist of a number of important componen The application uses the `$schema` property to ensure compatibility for a given element template. You find the latest supported versions here: -- [Camunda Platform 7](https://www.npmjs.com/package/@camunda/element-templates-json-schema) -- [Camunda Platform 8](https://www.npmjs.com/package/@camunda/zeebe-element-templates-json-schema) +- [Camunda 7](https://www.npmjs.com/package/@camunda/element-templates-json-schema) +- [Camunda 8](https://www.npmjs.com/package/@camunda/zeebe-element-templates-json-schema) The tooling will ignore element templates defining a higher `$schema` version and will log a warning message. @@ -73,7 +73,7 @@ For example, given the following `$schema` definition, the application takes `0. "$schema": "https://unpkg.com/@camunda/element-templates-json-schema@0.9.1/resources/schema.json" ``` -The JSON Schema versioning is backward-compatible, meaning that all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON Schema version for Camunda Platform 7 element templates. +The JSON Schema versioning is backward-compatible, meaning that all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON Schema version for Camunda 7 element templates. Learn more about specifing a `$schema` [here](../defining-templates). @@ -185,7 +185,7 @@ As seen in the example the important attributes in a property definition are: - `binding`: Specifying how the property is mapped to BPMN or Camunda extensions (cf. [bindings](#bindings)) - `constraints`: A list of editing constraints to apply to the template -In addition, Camunda Platform 8 supports these properties: +In addition, Camunda 8 supports these properties: - `id`: An identifier that can be used to reference the property in conditional properties - `condition`: A condition that determines when [the property is active](#defining-conditional-properties) @@ -231,7 +231,7 @@ The resulting properties panel control looks like this: ##### Omitted type :::note -Omitting the type is supported in Camunda Platform 7 element templates only. +Omitting the type is supported in Camunda 7 element templates only. ::: By omitting the `type` configuration the default UI component will be rendered for the respective binding. @@ -255,7 +255,7 @@ For the `camunda:executionListener` binding, an omitted `type` will lead to the ##### FEEL :::note -FEEL properties are only supported in Camunda Platform 8 element templates. +FEEL properties are only supported in Camunda 8 element templates. ::: We support the feel properties `optional` and `required`. @@ -278,7 +278,7 @@ When set, the input field offers visual indications that a feel expression is ex ###### Supported types -Camunda Platform 8 supports `feel` on the following input types: +Camunda 8 supports `feel` on the following input types: - `String` - `Text` @@ -291,9 +291,9 @@ Notice that adherence to the following configuration options is enforced by desi @@ -307,7 +307,7 @@ Notice that adherence to the following configuration options is enforced by desi | **Binding parameters** | `name`: the name of the property | | **Mapping result** | `<... [name]=[userInput] ... />` | -The `property` binding is supported both in Camunda Platform 7 and 8. +The `property` binding is supported both in Camunda 7 and 8. @@ -437,7 +437,7 @@ The `zeebe:property` binding allows you to set any arbitrary property for an out #### Optional bindings :::note -Optional bindings are only supported in Camunda Platform 8 element templates. +Optional bindings are only supported in Camunda 8 element templates. ::: We support optional bindings that do not persist empty values in the underlying BPMN 2.0 XML. @@ -477,7 +477,7 @@ If a user removes the value in the configured control, it will also remove the m ##### Supported Bindings -Camunda Platform 8 supports `optional` on the following binding types: +Camunda 8 supports `optional` on the following binding types: - `zeebe:input` - `zeebe:output` @@ -487,10 +487,10 @@ Camunda Platform 8 supports `optional` on the following binding types: #### Scoped bindings :::note -Scoped bindings are only supported in Camunda Platform 7 element templates. +Scoped bindings are only supported in Camunda 7 element templates. ::: -Scoped bindings allow you to configure nested elements, such as [Camunda Platform 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). +Scoped bindings allow you to configure nested elements, such as [Camunda 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). ```json { @@ -528,7 +528,7 @@ exposed to the user in a separate custom fields section. ##### Supported Scopes -Camunda Platform 7 supports the following scope bindings: +Camunda 7 supports the following scope bindings: | Name | Target | | ------------------- | ------------------------------------------------------------------------------------------ | @@ -624,7 +624,7 @@ Together with the `pattern` constraint, you may define your custom error message #### Icons :::note -Icons are currently supported in Camunda Platform 8 element templates only. +Icons are currently supported in Camunda 8 element templates only. ::: It is possible to define custom icons to update the visual appearance of elements after applying an element template. @@ -676,7 +676,7 @@ Per default, the element template defines the visible entries of the properties ### Defining conditional properties :::note -Conditional properties are currently supported in Camunda Platform 8 element templates only. +Conditional properties are currently supported in Camunda 8 element templates only. ::: Properties may have a condition which determines when they should be active, depending on the value of another property. When property is **active**, it is displayed in the properties panel, and its value is serialized in the XML. If a property is **not active**, it is not displayed, and its value is removed from the XML. diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/using-templates.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/using-templates.md index d569a075719..2adfb8fe847 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/using-templates.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/element-templates/using-templates.md @@ -18,7 +18,7 @@ selected element. Applying a template stores it via the `modelerTemplate` property and the optional `modelerTemplateVersion` property on the selected element: -Camunda Platform 7: +Camunda 7: ```xml @@ -27,7 +27,7 @@ Camunda Platform 7: camunda:modelerTemplateVesion="1"/> ``` -Camunda Platform 8: +Camunda 8: ```xml diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/flags/flags.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/flags/flags.md index 2130dde70bc..4e107a3258c 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/flags/flags.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/flags/flags.md @@ -78,7 +78,7 @@ To display a custom version information in the status bar of the app, configure > :information_source: The Modeler will read trusted certificates from your operating system's trust store. -Provide additional certificates to validate secured connections to a Camunda Platform 8 installation. +Provide additional certificates to validate secured connections to a Camunda 8 installation. Configure your `flags.json` like this: @@ -90,4 +90,4 @@ Configure your `flags.json` like this: Additional information adapted from the [upstream documentation](https://nodejs.org/docs/latest/api/tls.html#tlscreatesecurecontextoptions): -> The peer (Camunda Platform 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. +> The peer (Camunda 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/model-your-first-diagram.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/model-your-first-diagram.md index 79a81f555cb..cc6c8df39f6 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/model-your-first-diagram.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/model-your-first-diagram.md @@ -25,4 +25,4 @@ Elements that support different types can be reconfigured by clicking on the cor ![properties panel](img/properties-panel.png) -5. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda Platform 8 cluster](./connect-to-camunda-platform-8.md). +1. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda 8 cluster](./connect-to-camunda-8.md). diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/start-instance.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/start-instance.md index 0dd7e5d10c5..99832ceb6d5 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/start-instance.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/start-instance.md @@ -1,10 +1,10 @@ --- id: start-instance title: Start a new process instance -description: "After you have deployed your process to Camunda Platform 8, you can start a new instance of this process via the play icon." +description: "After you have deployed your process to Camunda 8, you can start a new instance of this process via the play icon." --- -After you have [deployed your process to Camunda Platform 8](./connect-to-camunda-platform-8.md), you can start a new instance of this process via the play icon: +After you have [deployed your process to Camunda 8](./connect-to-camunda-8.md), you can start a new instance of this process via the play icon: ![start instance icon](./img/start-instance-icon.png) diff --git a/versioned_docs/version-8.1/components/modeler/desktop-modeler/telemetry/telemetry.md b/versioned_docs/version-8.1/components/modeler/desktop-modeler/telemetry/telemetry.md index 1e2d9e6c7f6..751f01954ef 100644 --- a/versioned_docs/version-8.1/components/modeler/desktop-modeler/telemetry/telemetry.md +++ b/versioned_docs/version-8.1/components/modeler/desktop-modeler/telemetry/telemetry.md @@ -118,8 +118,8 @@ Also in the case of BPMN diagrams, the event payload may include further diagram The `Deployment Event` is sent in the following situations: -- User deploys a BPMN or DMN diagram to Camunda Platform 7 or Camunda Platform 8 -- User deploys a Form to Camunda Platform 7 +- User deploys a BPMN or DMN diagram to Camunda 7 or Camunda 8 +- User deploys a Form to Camunda 7 The `Deployment Event` and `Start Instance` have the following properties: diff --git a/versioned_docs/version-8.1/components/modeler/dmn/decision-literal-expression.md b/versioned_docs/version-8.1/components/modeler/dmn/decision-literal-expression.md index afe9e389682..90e8871ad87 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/decision-literal-expression.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/decision-literal-expression.md @@ -45,7 +45,7 @@ attribute on the `decision` element. The id is the technical identifier of the decision. It is set in the `id` attribute on the `decision` element. -Each decision should have an unique id when it is deployed to the Camunda Platform. +Each decision should have an unique id when it is deployed to Camunda. :::caution diff --git a/versioned_docs/version-8.1/components/modeler/dmn/decision-requirements-graph.md b/versioned_docs/version-8.1/components/modeler/dmn/decision-requirements-graph.md index 93715c44f2d..04efa0946b6 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/decision-requirements-graph.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/decision-requirements-graph.md @@ -49,7 +49,7 @@ The name describes the DRG. It is set as the `name` attribute on the `definition The id is the technical identifier of the DRG. It is set in the `id` attribute on the `definitions` element. -Each DRG should have an unique id when it is deployed to the Camunda Platform. +Each DRG should have an unique id when it is deployed to Camunda. ```xml diff --git a/versioned_docs/version-8.1/components/modeler/dmn/decision-table-input.md b/versioned_docs/version-8.1/components/modeler/dmn/decision-table-input.md index 043d78a6375..479d9f181ad 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/decision-table-input.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/decision-table-input.md @@ -33,7 +33,7 @@ XML element. ## Input id -The input id is a unique identifier of the decision table input. It is used by the Camunda Platform to reference the +The input id is a unique identifier of the decision table input. It is used by Camunda to reference the input clause. Therefore, it is required. It is set as the `id` attribute of the `input` XML element. ```xml diff --git a/versioned_docs/version-8.1/components/modeler/dmn/decision-table-output.md b/versioned_docs/version-8.1/components/modeler/dmn/decision-table-output.md index cc0425dcf75..61c74f129d5 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/decision-table-output.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/decision-table-output.md @@ -29,7 +29,7 @@ XML element. ## Output id -The output id is a unique identifier of the decision table output. It is used by the Camunda Platform to reference the +The output id is a unique identifier of the decision table output. It is used by Camunda to reference the output clause. Therefore, it is required. It is set as the `id` attribute of the `output` XML element. ```xml diff --git a/versioned_docs/version-8.1/components/modeler/dmn/decision-table.md b/versioned_docs/version-8.1/components/modeler/dmn/decision-table.md index 4b2cb1e90cb..b9d9f9a3c30 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/decision-table.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/decision-table.md @@ -49,7 +49,7 @@ The id is the technical identifier of the decision. It is set in the `id` attribute on the `decision` element. Just as the `name`, the `id` can be changed via the Properties Panel after selecting the respective "Decision" in the Decision Requirements Diagram view. -Each decision should have an unique id when it is deployed to the Camunda Platform. +Each decision should have an unique id when it is deployed to Camunda. :::caution diff --git a/versioned_docs/version-8.1/components/modeler/dmn/dmn-data-types.md b/versioned_docs/version-8.1/components/modeler/dmn/dmn-data-types.md index b52ff6c39a4..fa44f27d1b0 100644 --- a/versioned_docs/version-8.1/components/modeler/dmn/dmn-data-types.md +++ b/versioned_docs/version-8.1/components/modeler/dmn/dmn-data-types.md @@ -4,7 +4,7 @@ title: Data types description: On overview of the available data types in DMN. --- -The Camunda Platform supports the following data types for DMN: +Camunda supports the following data types for DMN: | Type name | Associated FEEL type | | ----------------- | --------------------------------------------------------------------------------------------------------- | diff --git a/versioned_docs/version-8.1/components/modeler/forms/camunda-forms-reference.md b/versioned_docs/version-8.1/components/modeler/forms/camunda-forms-reference.md index 431b305f938..830a960114b 100644 --- a/versioned_docs/version-8.1/components/modeler/forms/camunda-forms-reference.md +++ b/versioned_docs/version-8.1/components/modeler/forms/camunda-forms-reference.md @@ -5,12 +5,12 @@ description: Streamline your human workflows with the help of Camunda Forms --- :::note Support for Camunda Forms -The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda Platform 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda Platform 7 version 7.15.0 or later. +The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda 7 version 7.15.0 or later. ::: The Camunda Forms feature allows you to design and configure forms. Once configured, they can be connected to a user task or start event to implement a task form in your application. -While you can incorporate Camunda Forms solely within Camunda Platform 8, you can also utilize Camunda Forms in Camunda Platform 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. +While you can incorporate Camunda Forms solely within Camunda 8, you can also utilize Camunda Forms in Camunda 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. To learn more about how Camunda Forms are created in Camunda Modeler and embedded in Camunda Tasklist, visit our guide on [user task forms](../../../guides/utilizing-forms.md). diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/collaborate-with-modes.md b/versioned_docs/version-8.1/components/modeler/web-modeler/collaborate-with-modes.md index 736b8bc5bda..137507340d6 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/collaborate-with-modes.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/collaborate-with-modes.md @@ -4,7 +4,7 @@ title: Collaborate with modes description: "Dedicated modes are ways for business and IT professionals to collaborate effectively." --- -Camunda Platform 8 only +Camunda 8 only Collaboration between business and IT professionals can be challenging, which is why we introduced two modes in BPMN diagrams that help users with different technical backgrounds to collaborate effectively: **design** and **implement**. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/collaboration.md b/versioned_docs/version-8.1/components/modeler/web-modeler/collaboration.md index 634e410a137..5c000f37021 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/collaboration.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/collaboration.md @@ -4,7 +4,7 @@ title: Collaboration description: Collaboration features and access rights for Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only ## Projects @@ -18,7 +18,7 @@ When you access Web Modeler via the Cloud menu, you see the **Home** page with a Users can have various levels of access to a project in Web Modeler, outlined in this section. -After creating a project, you can invite members of your Camunda Platform 8 organization to collaborate in Web Modeler. +After creating a project, you can invite members of your Camunda 8 organization to collaborate in Web Modeler. There are four roles with different levels of access rights that can be assigned to each user: - **Project Admin**: The user can edit the project itself, all folders and diagrams within the project, and invite more users to collaborate. @@ -36,7 +36,7 @@ On the right side of a project, view a list of your collaborators and invite mor 2. Choose a role for your new collaborator. ![invite choose role](img/collaboration/web-modeler-collaborator-invite-choose-role.png) -3. Begin typing the name of the individual and Web Modeler will suggest Camunda Platform 8 organization members that you can invite to the project. +3. Begin typing the name of the individual and Web Modeler will suggest Camunda 8 organization members that you can invite to the project. ![invite suggestions](img/collaboration/web-modeler-collaborator-invite-suggestions.png) 4. Write a message to your new collaborator about their invitation to the project. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/design-your-process.md b/versioned_docs/version-8.1/components/modeler/web-modeler/design-your-process.md index 6621f627fab..33ebd4c8e34 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/design-your-process.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/design-your-process.md @@ -4,7 +4,7 @@ title: Design mode for business users description: "Design mode is tailored to business users and allows strategic modeling" --- -Camunda Platform 8 only +Camunda 8 only In the **Design** mode view, business users have access to a different workspace of Web Modeler with a reduced properties panel. Only comments are shown, which provides a decluttered user interface. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/implement-your-process.md b/versioned_docs/version-8.1/components/modeler/web-modeler/implement-your-process.md index 3e368bb5e95..8db9636d616 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/implement-your-process.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/implement-your-process.md @@ -4,7 +4,7 @@ title: Implement mode for developers description: "Implement mode is tailored to developers and allows full access to an implementation-focused workspace." --- -Camunda Platform 8 only +Camunda 8 only In the **Implement** mode view, developers have access to a full, implementation-focused workspace of Web Modeler. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/import-diagram.md b/versioned_docs/version-8.1/components/modeler/web-modeler/import-diagram.md index b0dad1e6a93..9ca91a00f02 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/import-diagram.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/import-diagram.md @@ -4,7 +4,7 @@ title: Import diagram description: "You can import a BPMN or DMN diagram at any time with Web Modeler." --- -Camunda Platform 8 only +Camunda 8 only You can import a BPMN or DMN diagram at any time with Web Modeler, and there are several ways to accomplish this: diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/launch-cloud-modeler.md b/versioned_docs/version-8.1/components/modeler/web-modeler/launch-cloud-modeler.md index b70eef0c390..b99882efed9 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/launch-cloud-modeler.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/launch-cloud-modeler.md @@ -1,12 +1,12 @@ --- id: launch-cloud-modeler title: Launch Web Modeler -description: "Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." +description: "Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." --- -Camunda Platform 8 only +Camunda 8 only -Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. +Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, follow the steps below: diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/milestones.md b/versioned_docs/version-8.1/components/modeler/web-modeler/milestones.md index d6bb2cf83f9..2c6a642a847 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/milestones.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/milestones.md @@ -4,7 +4,7 @@ title: Milestones description: Working with milestones in Web Modeler --- -Camunda Platform 8 only +Camunda 8 only ## Milestones diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/model-your-first-diagram.md b/versioned_docs/version-8.1/components/modeler/web-modeler/model-your-first-diagram.md index 740a99b130e..b3ef8ba4100 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/model-your-first-diagram.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/model-your-first-diagram.md @@ -4,7 +4,7 @@ title: Model your first diagram description: "After you've created a BPMN diagram, you can start modeling it." --- -Camunda Platform 8 only +Camunda 8 only After you've created a BPMN diagram, you can start modeling it. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/new-web-modeler.md b/versioned_docs/version-8.1/components/modeler/web-modeler/new-web-modeler.md index 4fced47f802..4c8139086e7 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/new-web-modeler.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/new-web-modeler.md @@ -4,7 +4,7 @@ title: New Web Modeler description: Your data was automatically migrated from the old Cloud Modeler to the new Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only If you used our old Cloud Modeler (before March 2022), all of your data has been migrated to the new Web Modeler. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/save-and-deploy.md b/versioned_docs/version-8.1/components/modeler/web-modeler/save-and-deploy.md index d0d72c5f1d3..ae6f5497f55 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/save-and-deploy.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/save-and-deploy.md @@ -4,7 +4,7 @@ title: Save and deploy your diagram description: "If a diagram is changed and autosaved, it has no effect on your cluster." --- -Camunda Platform 8 only +Camunda 8 only Web Modeler will autosave all your changes on a diagram. The changes will also be visible in real-time to any collaborators opening the same diagram. diff --git a/versioned_docs/version-8.1/components/modeler/web-modeler/start-instance.md b/versioned_docs/version-8.1/components/modeler/web-modeler/start-instance.md index 3b23710c4fe..8ab6a2386ae 100644 --- a/versioned_docs/version-8.1/components/modeler/web-modeler/start-instance.md +++ b/versioned_docs/version-8.1/components/modeler/web-modeler/start-instance.md @@ -4,7 +4,7 @@ title: Start a new process instance description: "If a BPMN diagram is deployed via Web Modeler, you can start a new instance of this diagram." --- -Camunda Platform 8 only +Camunda 8 only If a BPMN diagram is deployed via Web Modeler, you can start a new instance of this diagram. diff --git a/versioned_docs/version-8.2/components/modeler/about-modeler.md b/versioned_docs/version-8.2/components/modeler/about-modeler.md index 71780a18de0..ded90336408 100644 --- a/versioned_docs/version-8.2/components/modeler/about-modeler.md +++ b/versioned_docs/version-8.2/components/modeler/about-modeler.md @@ -5,7 +5,7 @@ description: "Any executable process needs a BPMN diagram designed and configure keywords: ["process mapping tool"] --- -Camunda Platform 8 only +Camunda 8 only Any executable process needs a **[Business Process Model and Notation (BPMN)](./bpmn/bpmn.md) diagram** designed and configured beforehand. @@ -15,7 +15,7 @@ In tandem, different events and implementation details (such as the conditions w Camunda offers two tools to design and implement your diagrams: -- [Web Modeler](./web-modeler/launch-cloud-modeler.md): Integrate seamlessly with Camunda Platform 8 SaaS and Self-Managed installations alongside [Console](../console/introduction-to-console.md). +- [Web Modeler](./web-modeler/launch-cloud-modeler.md): Integrate seamlessly with Camunda 8 SaaS and Self-Managed installations alongside [Console](../console/introduction-to-console.md). - [Desktop Modeler](./desktop-modeler/index.md): Design, view, and edit models using this desktop application. Install and use Desktop Modeler locally, all while integrating your local development environment. :::note @@ -26,7 +26,7 @@ In this guide, we'll demonstrate modeling BPMN diagrams using both Web Modeler a ## Next steps -- [Modeling BPMN](/guides/automating-a-process-using-bpmn.md) - Learn how to model an automated process in this tutorial using Web Modeler with Camunda Platform 8 SaaS. +- [Modeling BPMN](/guides/automating-a-process-using-bpmn.md) - Learn how to model an automated process in this tutorial using Web Modeler with Camunda 8 SaaS. - [Camunda Forms](/guides/utilizing-forms.md) - Design and configure forms, and connect them to a user task or start event to implement a task form in your application. - [DMN](./dmn/dmn.md) - In DMN, model and execute decisions using the same language. As a business analyst, model the rules that lead to a decision in comprehensive tables, and execute these tables directly by a decision engine like Camunda. - [Out-of-the-box Connectors](/guides/configuring-out-of-the-box-connector.md) - Utilize pre-built connectivity with a number of outside systems. Connectors are modular by nature, reusable, and accelerate automation across those systems. diff --git a/versioned_docs/version-8.2/components/modeler/bpmn/bpmn.md b/versioned_docs/version-8.2/components/modeler/bpmn/bpmn.md index e866f60b75b..23cfe55faa2 100644 --- a/versioned_docs/version-8.2/components/modeler/bpmn/bpmn.md +++ b/versioned_docs/version-8.2/components/modeler/bpmn/bpmn.md @@ -5,7 +5,7 @@ description: Let's start modeling by creating a BPMN diagram. --- :::note -BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda Platform 7 in Camunda Platform 8, or vice versa, at this time. +BPMN diagrams must be created for the process engine they intend to be deployed on. You cannot run a BPMN diagram modeled for Camunda 7 in Camunda 8, or vice versa, at this time. ::: ## Start modeling diff --git a/versioned_docs/version-8.2/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md b/versioned_docs/version-8.2/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md index a076e900e66..eea15c5572f 100644 --- a/versioned_docs/version-8.2/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md +++ b/versioned_docs/version-8.2/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md @@ -10,7 +10,7 @@ modeled in [Decision Model and Notation](https://www.omg.org/dmn/) (DMN). ![task](assets/business-rule-task.png) :::info -Camunda Platform 8 supports alternative task implementations for the business rule task. If you want +Camunda 8 supports alternative task implementations for the business rule task. If you want to use your own implementation for a business rule task, see the [job worker implementation](#job-worker-implementation) section below. The sections before this job worker implementation apply to the DMN decision implementation only. diff --git a/versioned_docs/version-8.2/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md b/versioned_docs/version-8.2/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md index b201349d91f..f882fbb42fd 100644 --- a/versioned_docs/version-8.2/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md +++ b/versioned_docs/version-8.2/components/modeler/bpmn/inclusive-gateways/inclusive-gateways.md @@ -6,7 +6,7 @@ description: "An inclusive gateway (or OR-gateway) allows you to make multiple d :::note -Currently, Camunda Platform 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. +Currently, Camunda 8 only supports the diverging (i.e. splitting, forking) inclusive gateway. It does not yet support the converging (i.e. merging, joining) inclusive gateway. A combination of parallel and exclusive gateways can be used as an alternative way to merge the flows. ::: diff --git a/versioned_docs/version-8.2/components/modeler/bpmn/script-tasks/script-tasks.md b/versioned_docs/version-8.2/components/modeler/bpmn/script-tasks/script-tasks.md index 668547f1508..1af1b9e1cec 100644 --- a/versioned_docs/version-8.2/components/modeler/bpmn/script-tasks/script-tasks.md +++ b/versioned_docs/version-8.2/components/modeler/bpmn/script-tasks/script-tasks.md @@ -11,7 +11,7 @@ JavaScript, or Python. ![task](assets/script-task.png) :::info -Camunda Platform 8 supports alternative task implementations for the script task. To use your own +Camunda 8 supports alternative task implementations for the script task. To use your own implementation for a script task, see the [job worker implementation](#job-worker-implementation) section below. The sections before this job worker implementation apply to the [FEEL expression](/components/modeler/feel/language-guide/feel-expressions-introduction.md) implementation only. diff --git a/versioned_docs/version-8.2/components/modeler/bpmn/user-tasks/user-tasks.md b/versioned_docs/version-8.2/components/modeler/bpmn/user-tasks/user-tasks.md index 958362e3381..8431ca01b96 100644 --- a/versioned_docs/version-8.2/components/modeler/bpmn/user-tasks/user-tasks.md +++ b/versioned_docs/version-8.2/components/modeler/bpmn/user-tasks/user-tasks.md @@ -47,12 +47,12 @@ For [Tasklist](/components/tasklist/introduction-to-tasklist.md) to claim the ta the value of the `assignee` must be the user's **unique identifier**. The unique identifier depends on the authentication method used to login to Tasklist: -- Camunda Platform 8 (login with email, Google, GitHub): `email` +- Camunda 8 (login with email, Google, GitHub): `email` - Default Basic Auth (elasticsearch): `username` - IAM: `username` :::note -For example, say you log into Tasklist using Camunda Platform 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. +For example, say you log into Tasklist using Camunda 8 login with email using your email address `foo@bar.com`. Every time a user task activates with `assignee` set to value `foo@bar.com`, Tasklist automatically assigns it to you. You'll be able to find your new task under the task dropdown option `Claimed by me`. ::: ## Scheduling diff --git a/versioned_docs/version-8.2/components/modeler/data-handling.md b/versioned_docs/version-8.2/components/modeler/data-handling.md index f5bc1fe5e6b..9b0f818dc21 100644 --- a/versioned_docs/version-8.2/components/modeler/data-handling.md +++ b/versioned_docs/version-8.2/components/modeler/data-handling.md @@ -4,7 +4,7 @@ title: Data handling description: "Get editor support for variables by defining the variables in the process model." --- -Camunda Platform 8 only +Camunda 8 only The FEEL editor will suggest variables in the current element's scope when defining input and output mappings in a process. The variables created by the mapping are automatically picked up and added to the suggestions. diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-8.md similarity index 64% rename from versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md rename to versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-8.md index f832f940ea1..f5ab2abe3ee 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/connect-to-camunda-8.md @@ -1,10 +1,10 @@ --- -id: connect-to-camunda-platform-8 +id: connect-to-camunda-8 title: Deploy your first diagram -description: "Follow these steps to directly deploy diagrams and start process instances in Camunda Platform 8." +description: "Follow these steps to directly deploy diagrams and start process instances in Camunda 8." --- -Desktop Modeler can directly deploy diagrams and start process instances in Camunda Platform 8. Follow the steps below to deploy a diagram to **Camunda Platform 8 SaaS**. To deploy to a local installation, visit the [Camunda Platform 8 Self-Managed guide](../../../self-managed/modeler/desktop-modeler/deploy-to-self-managed.md). +Desktop Modeler can directly deploy diagrams and start process instances in Camunda 8. Follow the steps below to deploy a diagram to **Camunda 8 SaaS**. To deploy to a local installation, visit the [Camunda Platform 8 Self-Managed guide](../../../self-managed/modeler/desktop-modeler/deploy-to-self-managed.md). 1. Click the deployment icon: @@ -16,7 +16,7 @@ Desktop Modeler can directly deploy diagrams and start process instances in Camu 3. Input the `Cluster URL` and the credentials (`Client ID`, `Client Secret`) of your [API client](../../console/manage-clusters/manage-api-clients.md): -![deployment via Camunda Platform 8](./img/deploy-diagram-camunda-cloud-remember.png) +![deployment via Camunda 8](./img/deploy-diagram-camunda-cloud-remember.png) 4. Toggle **Remember credentials** to locally store the connection information. diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md index d010f8315a7..4eefb2e401f 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md @@ -1,10 +1,10 @@ --- id: c7-defining-templates -title: Defining templates in Camunda Platform 7 +title: Defining templates in Camunda 7 description: "Learn about JSON schema compatibility, supported BPMN types, defining template properties, and more." --- -Camunda Platform 7 only +Camunda 7 only Templates are defined in template descriptor files as a JSON array: @@ -64,7 +64,7 @@ For example, given the following `$schema` definition, the application takes `0. "$schema": "https://unpkg.com/@camunda/element-templates-json-schema@0.9.1/resources/schema.json" ``` -The JSON schema versioning is backward-compatible, meaning all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON schema version for Camunda Platform 7 element templates. +The JSON schema versioning is backward-compatible, meaning all versions including or below the current one are supported. In case no `$schema` is defined, Camunda Modeler assumes the latest JSON schema version for Camunda 7 element templates. ## Supported BPMN types @@ -215,7 +215,7 @@ The resulting properties panel control looks like this: #### Omitted type :::note -Omitting the type is supported in Camunda Platform 7 element templates only. +Omitting the type is supported in Camunda 7 element templates only. ::: By omitting the `type` configuration, the default UI component is rendered for the respective binding. @@ -328,7 +328,7 @@ Notice that adherence to the following configuration options is enforced by desi ### Scoped bindings -Scoped bindings allow you to configure nested elements, such as [Camunda Platform 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). +Scoped bindings allow you to configure nested elements, such as [Camunda 7 Connectors](https://docs.camunda.org/manual/latest/user-guide/process-engine/connectors/#use-connectors). ```json { @@ -366,7 +366,7 @@ exposed to the user in a separate custom fields section. #### Supported scopes -Camunda Platform 7 supports the following scope bindings: +Camunda 7 supports the following scope bindings: | Name | Target | | ------------------- | ------------------------------------------------------------------------------------------ | diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/defining-templates.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/defining-templates.md index 6f3f7243564..9605e1c4ae7 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/defining-templates.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/element-templates/defining-templates.md @@ -37,7 +37,7 @@ As seen in the code snippet, a template consists of a number of important compon :::note -The `$schema` attribute is **required** for Camunda Platform 8 element templates. +The `$schema` attribute is **required** for Camunda 8 element templates. ::: Example: diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/flags/flags.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/flags/flags.md index 2130dde70bc..4e107a3258c 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/flags/flags.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/flags/flags.md @@ -78,7 +78,7 @@ To display a custom version information in the status bar of the app, configure > :information_source: The Modeler will read trusted certificates from your operating system's trust store. -Provide additional certificates to validate secured connections to a Camunda Platform 8 installation. +Provide additional certificates to validate secured connections to a Camunda 8 installation. Configure your `flags.json` like this: @@ -90,4 +90,4 @@ Configure your `flags.json` like this: Additional information adapted from the [upstream documentation](https://nodejs.org/docs/latest/api/tls.html#tlscreatesecurecontextoptions): -> The peer (Camunda Platform 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. +> The peer (Camunda 8) certificate must be chainable to a CA trusted by the app for the connection to be authenticated. When using certificates that are not chainable to a well-known CA, the certificate's CA must be explicitly specified as trusted or the connection will fail to authenticate. If the peer uses a certificate that doesn't match or chain to one of the default CAs, provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA, and must be provided. diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/index.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/index.md index 84139cbfa5b..e8d12678c05 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/index.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/index.md @@ -2,10 +2,10 @@ id: index title: Desktop Modeler sidebar_label: About -description: "Camunda Desktop Modeler is a desktop app for modeling BPMN, DMN, and Forms, compatible with Camunda Platform 7 and Camunda Platform 8." +description: "Camunda Desktop Modeler is a desktop app for modeling BPMN, DMN, and Forms, compatible with Camunda 7 and Camunda 8." --- -Camunda Platform 7 and 8 +Camunda 7 and 8 Desktop Modeler is a desktop application for modeling BPMN, DMN, and Forms and supports you in building executable diagrams with Camunda. @@ -14,7 +14,7 @@ Desktop Modeler is a desktop application for modeling BPMN, DMN, and Forms and s ## Features - Design [BPMN](../bpmn/bpmn.md), [DMN](../dmn/dmn.md), and [Forms](../forms/camunda-forms-reference.md) -- Implement process applications for Camunda Platform 7 and 8 +- Implement process applications for Camunda 7 and 8 - Deploy and run processes directly from the application - Validate your diagrams using [configurable lint rules](https://github.com/camunda/camunda-modeler-custom-linter-rules-plugin) - [Customize](./flags/flags.md) and [extend](./plugins/plugins.md) the application @@ -25,7 +25,7 @@ Download the app for Windows, Linux, or MacOS from the [Camunda downloads page]( ## Get started -Learn how to [develop your first process](./model-your-first-diagram.md) and [deploy it](./connect-to-camunda-platform-8.md) to Camunda Platform 8. +Learn how to [develop your first process](./model-your-first-diagram.md) and [deploy it](./connect-to-camunda-8.md) to Camunda 8. ## Resources diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/model-your-first-diagram.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/model-your-first-diagram.md index 587cebfb3b7..a37ab52d7b3 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/model-your-first-diagram.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/model-your-first-diagram.md @@ -25,4 +25,4 @@ Elements that support different types can be reconfigured by clicking on the cor ![properties panel](img/properties-panel.png) -5. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda Platform 8 cluster](./connect-to-camunda-platform-8.md). +1. Once you finish modeling and configuring your diagram, you can deploy it to a [Camunda 8 cluster](./connect-to-camunda-8.md). diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/start-instance.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/start-instance.md index 0dd7e5d10c5..99832ceb6d5 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/start-instance.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/start-instance.md @@ -1,10 +1,10 @@ --- id: start-instance title: Start a new process instance -description: "After you have deployed your process to Camunda Platform 8, you can start a new instance of this process via the play icon." +description: "After you have deployed your process to Camunda 8, you can start a new instance of this process via the play icon." --- -After you have [deployed your process to Camunda Platform 8](./connect-to-camunda-platform-8.md), you can start a new instance of this process via the play icon: +After you have [deployed your process to Camunda 8](./connect-to-camunda-8.md), you can start a new instance of this process via the play icon: ![start instance icon](./img/start-instance-icon.png) diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/telemetry/telemetry.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/telemetry/telemetry.md index 5edbfd04de4..ec7f9ba2bec 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/telemetry/telemetry.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/telemetry/telemetry.md @@ -61,8 +61,8 @@ These events include the following properties: The `Deployment Event` is sent in the following situations: -- User deploys a BPMN or DMN diagram to Camunda Platform 7 or Camunda Platform 8 -- User deploys a Form to Camunda Platform 7 +- User deploys a BPMN or DMN diagram to Camunda 7 or Camunda 8 +- User deploys a Form to Camunda 7 The `Deployment Event` and `Start Instance` have the following properties: diff --git a/versioned_docs/version-8.2/components/modeler/desktop-modeler/troubleshooting.md b/versioned_docs/version-8.2/components/modeler/desktop-modeler/troubleshooting.md index 23782d42d09..92436eb3665 100644 --- a/versioned_docs/version-8.2/components/modeler/desktop-modeler/troubleshooting.md +++ b/versioned_docs/version-8.2/components/modeler/desktop-modeler/troubleshooting.md @@ -76,7 +76,7 @@ You can connect to Zeebe via [`zbctl`](../../../apis-tools/cli-client/index.md) ### Secure connection to Zeebe fails -When connecting securely to Camunda Platform 8 SaaS, Camunda Platform 8 Self-Managed, or a standalone Zeebe instance (via `https` endpoint URL), Desktop Modeler tries to establish a secure connection. In the process, it strictly validates the server certificates presented against well-known certificate authorities. Failure to connect may have several reasons: +When connecting securely to Camunda 8 SaaS, Camunda 8 Self-Managed, or a standalone Zeebe instance (via `https` endpoint URL), Desktop Modeler tries to establish a secure connection. In the process, it strictly validates the server certificates presented against well-known certificate authorities. Failure to connect may have several reasons: #### The (remote) endpoint is not configured for secure connections diff --git a/versioned_docs/version-8.2/components/modeler/dmn/decision-literal-expression.md b/versioned_docs/version-8.2/components/modeler/dmn/decision-literal-expression.md index afe9e389682..90e8871ad87 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/decision-literal-expression.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/decision-literal-expression.md @@ -45,7 +45,7 @@ attribute on the `decision` element. The id is the technical identifier of the decision. It is set in the `id` attribute on the `decision` element. -Each decision should have an unique id when it is deployed to the Camunda Platform. +Each decision should have an unique id when it is deployed to Camunda. :::caution diff --git a/versioned_docs/version-8.2/components/modeler/dmn/decision-requirements-graph.md b/versioned_docs/version-8.2/components/modeler/dmn/decision-requirements-graph.md index 93715c44f2d..04efa0946b6 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/decision-requirements-graph.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/decision-requirements-graph.md @@ -49,7 +49,7 @@ The name describes the DRG. It is set as the `name` attribute on the `definition The id is the technical identifier of the DRG. It is set in the `id` attribute on the `definitions` element. -Each DRG should have an unique id when it is deployed to the Camunda Platform. +Each DRG should have an unique id when it is deployed to Camunda. ```xml diff --git a/versioned_docs/version-8.2/components/modeler/dmn/decision-table-input.md b/versioned_docs/version-8.2/components/modeler/dmn/decision-table-input.md index 043d78a6375..479d9f181ad 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/decision-table-input.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/decision-table-input.md @@ -33,7 +33,7 @@ XML element. ## Input id -The input id is a unique identifier of the decision table input. It is used by the Camunda Platform to reference the +The input id is a unique identifier of the decision table input. It is used by Camunda to reference the input clause. Therefore, it is required. It is set as the `id` attribute of the `input` XML element. ```xml diff --git a/versioned_docs/version-8.2/components/modeler/dmn/decision-table-output.md b/versioned_docs/version-8.2/components/modeler/dmn/decision-table-output.md index cc0425dcf75..61c74f129d5 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/decision-table-output.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/decision-table-output.md @@ -29,7 +29,7 @@ XML element. ## Output id -The output id is a unique identifier of the decision table output. It is used by the Camunda Platform to reference the +The output id is a unique identifier of the decision table output. It is used by Camunda to reference the output clause. Therefore, it is required. It is set as the `id` attribute of the `output` XML element. ```xml diff --git a/versioned_docs/version-8.2/components/modeler/dmn/decision-table.md b/versioned_docs/version-8.2/components/modeler/dmn/decision-table.md index 4b2cb1e90cb..b9d9f9a3c30 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/decision-table.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/decision-table.md @@ -49,7 +49,7 @@ The id is the technical identifier of the decision. It is set in the `id` attribute on the `decision` element. Just as the `name`, the `id` can be changed via the Properties Panel after selecting the respective "Decision" in the Decision Requirements Diagram view. -Each decision should have an unique id when it is deployed to the Camunda Platform. +Each decision should have an unique id when it is deployed to Camunda. :::caution diff --git a/versioned_docs/version-8.2/components/modeler/dmn/dmn-data-types.md b/versioned_docs/version-8.2/components/modeler/dmn/dmn-data-types.md index b52ff6c39a4..fa44f27d1b0 100644 --- a/versioned_docs/version-8.2/components/modeler/dmn/dmn-data-types.md +++ b/versioned_docs/version-8.2/components/modeler/dmn/dmn-data-types.md @@ -4,7 +4,7 @@ title: Data types description: On overview of the available data types in DMN. --- -The Camunda Platform supports the following data types for DMN: +Camunda supports the following data types for DMN: | Type name | Associated FEEL type | | ----------------- | --------------------------------------------------------------------------------------------------------- | diff --git a/versioned_docs/version-8.2/components/modeler/forms/camunda-forms-reference.md b/versioned_docs/version-8.2/components/modeler/forms/camunda-forms-reference.md index 431b305f938..830a960114b 100644 --- a/versioned_docs/version-8.2/components/modeler/forms/camunda-forms-reference.md +++ b/versioned_docs/version-8.2/components/modeler/forms/camunda-forms-reference.md @@ -5,12 +5,12 @@ description: Streamline your human workflows with the help of Camunda Forms --- :::note Support for Camunda Forms -The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda Platform 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda Platform 7 version 7.15.0 or later. +The initial release of Camunda Forms includes a debut minimal feature set, which will be expanded with upcoming versions. The Camunda Forms feature was added with the 7.15.0 release of Camunda 7 and the 4.7.0 release of [Camunda Modeler](../about-modeler.md). Therefore, they can be used within BPMN diagrams running on Camunda 7 version 7.15.0 or later. ::: The Camunda Forms feature allows you to design and configure forms. Once configured, they can be connected to a user task or start event to implement a task form in your application. -While you can incorporate Camunda Forms solely within Camunda Platform 8, you can also utilize Camunda Forms in Camunda Platform 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. +While you can incorporate Camunda Forms solely within Camunda 8, you can also utilize Camunda Forms in Camunda 7. After deploying a diagram with an embedded form, Tasklist imports this form schema and uses it to render the form on every task assigned to it. To learn more about how Camunda Forms are created in Camunda Modeler and embedded in Camunda Tasklist, visit our guide on [user task forms](../../../guides/utilizing-forms.md). diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/collaborate-with-modes.md b/versioned_docs/version-8.2/components/modeler/web-modeler/collaborate-with-modes.md index 81719ed8baf..7c702460dd3 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/collaborate-with-modes.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/collaborate-with-modes.md @@ -4,7 +4,7 @@ title: Collaborate with modes description: "Dedicated modes are ways for business and IT professionals to collaborate effectively." --- -Camunda Platform 8 only +Camunda 8 only Collaboration between business and IT professionals can be challenging, which is why we introduced three modes in BPMN diagrams that help users with different technical backgrounds to collaborate effectively: **design**, **implement**, and **play**. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/collaboration.md b/versioned_docs/version-8.2/components/modeler/web-modeler/collaboration.md index 7186571d19e..e61378903a1 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/collaboration.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/collaboration.md @@ -4,21 +4,21 @@ title: Collaborate with your team description: Collaboration features and access rights for Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only ## Projects Files and folders are stored in projects. The user access on files and folders is defined at the project level. -When you access Web Modeler via the Camunda Platform 8 dashboard, you see the **Home** page with all the projects you can access: +When you access Web Modeler via the Camunda 8 dashboard, you see the **Home** page with all the projects you can access: ![home page](img/collaboration/web-modeler-home.png) ### Access rights and permissions Users can have various levels of access to a project in Web Modeler, outlined in this section. -After creating a project, you can invite members of your Camunda Platform 8 organization to collaborate in Web Modeler. +After creating a project, you can invite members of your Camunda 8 organization to collaborate in Web Modeler. There are four roles with different levels of access rights that can be assigned to each user: - **Project Admin**: The user can edit the project itself, all folders and diagrams within the project, and invite more users to collaborate. @@ -40,7 +40,7 @@ On the right side of a project, view a list of your collaborators and invite mor 2. Choose a role for your new collaborator. ![invite choose role](img/collaboration/web-modeler-collaborator-invite-choose-role.png) -3. Begin typing the name of the individual and Web Modeler will suggest Camunda Platform 8 organization members that you can invite to the project. +3. Begin typing the name of the individual and Web Modeler will suggest Camunda 8 organization members that you can invite to the project. ![invite suggestions](img/collaboration/web-modeler-collaborator-invite-suggestions.png) 4. Write a message to your new collaborator about their invitation to the project. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/design-your-process.md b/versioned_docs/version-8.2/components/modeler/web-modeler/design-your-process.md index 6621f627fab..33ebd4c8e34 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/design-your-process.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/design-your-process.md @@ -4,7 +4,7 @@ title: Design mode for business users description: "Design mode is tailored to business users and allows strategic modeling" --- -Camunda Platform 8 only +Camunda 8 only In the **Design** mode view, business users have access to a different workspace of Web Modeler with a reduced properties panel. Only comments are shown, which provides a decluttered user interface. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/implement-your-process.md b/versioned_docs/version-8.2/components/modeler/web-modeler/implement-your-process.md index 3e368bb5e95..8db9636d616 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/implement-your-process.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/implement-your-process.md @@ -4,7 +4,7 @@ title: Implement mode for developers description: "Implement mode is tailored to developers and allows full access to an implementation-focused workspace." --- -Camunda Platform 8 only +Camunda 8 only In the **Implement** mode view, developers have access to a full, implementation-focused workspace of Web Modeler. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/import-diagram.md b/versioned_docs/version-8.2/components/modeler/web-modeler/import-diagram.md index a5610e3df50..41201206215 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/import-diagram.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/import-diagram.md @@ -4,7 +4,7 @@ title: Import diagram description: "You can import a BPMN or DMN diagram at any time with Web Modeler." --- -Camunda Platform 8 only +Camunda 8 only You can import a BPMN or DMN diagram at any time with Web Modeler, and there are several ways to accomplish this: diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/launch-cloud-modeler.md b/versioned_docs/version-8.2/components/modeler/web-modeler/launch-cloud-modeler.md index b70eef0c390..b99882efed9 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/launch-cloud-modeler.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/launch-cloud-modeler.md @@ -1,12 +1,12 @@ --- id: launch-cloud-modeler title: Launch Web Modeler -description: "Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." +description: "Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, take these steps." --- -Camunda Platform 8 only +Camunda 8 only -Since Web Modeler is embedded in the Camunda Platform 8 Console, it does not need to be started separately. +Since Web Modeler is embedded in the Camunda 8 Console, it does not need to be started separately. To launch Web Modeler, follow the steps below: diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/milestones.md b/versioned_docs/version-8.2/components/modeler/web-modeler/milestones.md index d6bb2cf83f9..2c6a642a847 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/milestones.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/milestones.md @@ -4,7 +4,7 @@ title: Milestones description: Working with milestones in Web Modeler --- -Camunda Platform 8 only +Camunda 8 only ## Milestones diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/model-your-first-diagram.md b/versioned_docs/version-8.2/components/modeler/web-modeler/model-your-first-diagram.md index 740a99b130e..b3ef8ba4100 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/model-your-first-diagram.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/model-your-first-diagram.md @@ -4,7 +4,7 @@ title: Model your first diagram description: "After you've created a BPMN diagram, you can start modeling it." --- -Camunda Platform 8 only +Camunda 8 only After you've created a BPMN diagram, you can start modeling it. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/new-web-modeler.md b/versioned_docs/version-8.2/components/modeler/web-modeler/new-web-modeler.md index ded045bb126..aa52409a650 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/new-web-modeler.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/new-web-modeler.md @@ -4,7 +4,7 @@ title: New Web Modeler description: Your data was automatically migrated from the old Cloud Modeler to the new Web Modeler. --- -Camunda Platform 8 only +Camunda 8 only If you used our old Cloud Modeler (before March 2022), all of your data has been migrated to the new Web Modeler. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/play-your-process.md b/versioned_docs/version-8.2/components/modeler/web-modeler/play-your-process.md index 1c5a7dedb87..6cce84aa288 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/play-your-process.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/play-your-process.md @@ -4,7 +4,7 @@ title: Play mode for rapid validation description: "Play mode gives developers a playground environment to quickly iterate and manually test their processes." --- -Camunda Platform 8 only +Camunda 8 only In the **Play** mode, developers have access to a Zeebe-powered playground environment within Web Modeler. diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/run-or-publish-your-process.md b/versioned_docs/version-8.2/components/modeler/web-modeler/run-or-publish-your-process.md index 34bc5f785a1..176238b111c 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/run-or-publish-your-process.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/run-or-publish-your-process.md @@ -7,9 +7,9 @@ description: "Flexible options to run or publish a process in any environment an import Tabs from "@theme/Tabs"; import TabItem from "@theme/TabItem"; -Camunda Platform 8 only +Camunda 8 only -When you design a process in Camunda Modeler, you have multiple flexible options to either run or publish it on Camunda Platform 8. This page explains the differences between running and publishing a process, and outlines the various options to publish a process into any environment, and to any audience. +When you design a process in Camunda Modeler, you have multiple flexible options to either run or publish it on Camunda 8. This page explains the differences between running and publishing a process, and outlines the various options to publish a process into any environment, and to any audience. ## Deploy a process @@ -29,7 +29,7 @@ To deploy, click **Deploy** in the upper right corner of the modeling screen: ## Run a process -Running a process means that you execute the process as a process instance on Camunda Platform 8. It allows you to test and debug your process and see how it performs in a live environment. +Running a process means that you execute the process as a process instance on Camunda 8. It allows you to test and debug your process and see how it performs in a live environment. - [Test run using Play mode](#test-run-using-play-mode) - [Run programmatically](#deploy-to-run-programmatically) @@ -97,7 +97,7 @@ You can also define the success of your processes by setting key performance ind ## Publishing a process -Publishing a process means that you make it available to other users inside and outside of Camunda Platform 8. Once published, other users can access and start instances of the process. +Publishing a process means that you make it available to other users inside and outside of Camunda 8. Once published, other users can access and start instances of the process. You have the following options to publish a process: @@ -161,7 +161,7 @@ To learn more about publishing processes to Tasklist, refer to our [documentatio ### Listen to message or signal events -Camunda Platform 8 supports message and signal events, which can be used to trigger a process instance when a specific event occurs. Everyone on the platform that knows the message or signal correlation keys can call such a process. To listen to a message or signal event, you need to define a [message](../bpmn/message-events/message-events.md#message-start-events) or [signal start event](../bpmn/signal-events/signal-events.md#signal-start-events) in your process model and configure it to listen for the desired event. Follow these steps to configure a message or signal start event: +Camunda 8 supports message and signal events, which can be used to trigger a process instance when a specific event occurs. Everyone on the platform that knows the message or signal correlation keys can call such a process. To listen to a message or signal event, you need to define a [message](../bpmn/message-events/message-events.md#message-start-events) or [signal start event](../bpmn/signal-events/signal-events.md#signal-start-events) in your process model and configure it to listen for the desired event. Follow these steps to configure a message or signal start event: 1. Select the start event. 2. Change the start event type to a message or signal start event using the **wrench tool**. @@ -179,5 +179,5 @@ As soon as a matching event is received, a process instance will be started. To - Make sure that the process is accessible to the appropriate users only. :::note -When working on Camunda Platform 8 Self-Managed, you can define access permissions on a per-process level using [Identity Resource Authorizations](../../../self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). +When working on Camunda 8 Self-Managed, you can define access permissions on a per-process level using [Identity Resource Authorizations](../../../self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). ::: diff --git a/versioned_docs/version-8.2/components/modeler/web-modeler/save-and-deploy.md b/versioned_docs/version-8.2/components/modeler/web-modeler/save-and-deploy.md index d0d72c5f1d3..ae6f5497f55 100644 --- a/versioned_docs/version-8.2/components/modeler/web-modeler/save-and-deploy.md +++ b/versioned_docs/version-8.2/components/modeler/web-modeler/save-and-deploy.md @@ -4,7 +4,7 @@ title: Save and deploy your diagram description: "If a diagram is changed and autosaved, it has no effect on your cluster." --- -Camunda Platform 8 only +Camunda 8 only Web Modeler will autosave all your changes on a diagram. The changes will also be visible in real-time to any collaborators opening the same diagram. diff --git a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/upgrade.md b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/upgrade.md index 427541c2a85..a768d1b7f3c 100644 --- a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/upgrade.md +++ b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/upgrade.md @@ -109,7 +109,7 @@ To authenticate: 2. [Assign permissions to the application](/docs/self-managed/identity/user-guide/authorizations/managing-resource-authorizations.md). 3. Connect with: -- [Desktop Modeler](/docs/components/modeler/desktop-modeler/connect-to-camunda-platform-8.md). +- [Desktop Modeler](/docs/components/modeler/desktop-modeler/connect-to-camunda-8.md). - [Zeebe client (zbctl)](/docs/self-managed/zeebe-deployment/security/secure-client-communication/#zbctl). ### v8.2 diff --git a/versioned_sidebars/version-8.1-sidebars.json b/versioned_sidebars/version-8.1-sidebars.json index e565aedc5a9..30b1ba0f236 100644 --- a/versioned_sidebars/version-8.1-sidebars.json +++ b/versioned_sidebars/version-8.1-sidebars.json @@ -149,7 +149,7 @@ "Desktop Modeler": [ "components/modeler/desktop-modeler/install-the-modeler", "components/modeler/desktop-modeler/model-your-first-diagram", - "components/modeler/desktop-modeler/connect-to-camunda-platform-8", + "components/modeler/desktop-modeler/connect-to-camunda-8", "components/modeler/desktop-modeler/start-instance", { "Element templates": [ diff --git a/versioned_sidebars/version-8.2-sidebars.json b/versioned_sidebars/version-8.2-sidebars.json index d148b354609..7724319c631 100644 --- a/versioned_sidebars/version-8.2-sidebars.json +++ b/versioned_sidebars/version-8.2-sidebars.json @@ -166,7 +166,7 @@ "components/modeler/desktop-modeler/index", "components/modeler/desktop-modeler/install-the-modeler", "components/modeler/desktop-modeler/model-your-first-diagram", - "components/modeler/desktop-modeler/connect-to-camunda-platform-8", + "components/modeler/desktop-modeler/connect-to-camunda-8", "components/modeler/desktop-modeler/start-instance", { "Element templates": [