diff --git a/docs/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md b/docs/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md index 9f29b2dc237..c60e9d6527a 100644 --- a/docs/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md +++ b/docs/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md @@ -13,7 +13,7 @@ Task applications are the interface between humans and Camunda processes to orch ## What are task applications? -Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) (for [human task orchestration](/guides/getting-started-orchestrate-human-tasks.md)) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: +Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) (for [human task orchestration](/guides/getting-started-orchestrate-human-tasks.md)) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: - Listing available tasks and allowing users to select a task to work on. - Providing filter and search options for users so they can more easily find the right next task to work on. @@ -59,9 +59,9 @@ Task details are shown when a task is selected from the queue. A [form](/guides/ :::tip Typically, a task application utilizes forms to capture information from the user, to make a decision, to collect the results from a real-world task, or to provide task instructions to the user. -However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). +However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). -For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md/#custom-form-key). +For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md#custom-form-key). ::: On the top of the form, a header shows the title of the task to work on, and the current assignee. Depending on the status of the assignment, a button allows you to assign the task to yourself or release it to the queue. diff --git a/docs/components/concepts/execution-listeners.md b/docs/components/concepts/execution-listeners.md index 3ea3b4ce163..2f898a0c72f 100644 --- a/docs/components/concepts/execution-listeners.md +++ b/docs/components/concepts/execution-listeners.md @@ -53,7 +53,7 @@ Execution listeners are processed by [job workers](/components/concepts/job-work See [open a job worker](/apis-tools/java-client-examples/job-worker-open.md) for an example of how to create a job worker and handler that can also process execution listener jobs. :::note -[Throwing a BPMN error](/components/best-practices/development/dealing-with-problems-and-exceptions.md/#throwing-and-handling-bpmn-errors) for an execution listener's job is not supported. +[Throwing a BPMN error](/components/best-practices/development/dealing-with-problems-and-exceptions.md#throwing-and-handling-bpmn-errors) for an execution listener's job is not supported. ::: ## Variables in an execution listener diff --git a/docs/components/concepts/job-workers.md b/docs/components/concepts/job-workers.md index 70e0843c40a..eca348c56c5 100644 --- a/docs/components/concepts/job-workers.md +++ b/docs/components/concepts/job-workers.md @@ -92,8 +92,8 @@ Job workers can provide a **job result** for [user task listeners](components/co Job results are used to define: -1. **Corrections**: Updates to specific user task attributes, such as assignee, due date, follow-up date, candidate users, candidate groups, and priority, before the task transition is finalized. For more details, see [correcting user task data](components/concepts/user-task-listeners.md/#correcting-user-task-data). -2. **Denial**: Indicates that the lifecycle transition should be explicitly denied. Denying the task lifecycle transition rolls back the user task to the previous state, and discards any corrections made by previous listeners. For more details, see [denying the operation](components/concepts/user-task-listeners.md/#denying-the-operation). +1. **Corrections**: Updates to specific user task attributes, such as assignee, due date, follow-up date, candidate users, candidate groups, and priority, before the task transition is finalized. For more details, see [correcting user task data](components/concepts/user-task-listeners.md#correcting-user-task-data). +2. **Denial**: Indicates that the lifecycle transition should be explicitly denied. Denying the task lifecycle transition rolls back the user task to the previous state, and discards any corrections made by previous listeners. For more details, see [denying the operation](components/concepts/user-task-listeners.md#denying-the-operation). Below is an example of using job result: diff --git a/docs/components/console/manage-clusters/settings.md b/docs/components/console/manage-clusters/settings.md index 3dfedeceed3..c8a6628a3af 100644 --- a/docs/components/console/manage-clusters/settings.md +++ b/docs/components/console/manage-clusters/settings.md @@ -24,7 +24,7 @@ You can enable resource-based authorization on a per-cluster basis to control th - Disable this setting if you do not want to use resource-based authorization in the cluster. You can still configure resource authorizations, but they are only applied to cluster users when you enable this setting. :::tip -For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md/#resource-based-authorizations). +For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md#resource-based-authorizations). ::: ## Automatic cluster updates diff --git a/docs/components/modeler/web-modeler/collaborate-with-modes.md b/docs/components/modeler/web-modeler/collaborate-with-modes.md index 465b21d9010..497bbf6b574 100644 --- a/docs/components/modeler/web-modeler/collaborate-with-modes.md +++ b/docs/components/modeler/web-modeler/collaborate-with-modes.md @@ -31,4 +31,4 @@ When a process template is selected, the default mode is **Implement**. ![read only properties](img/read-only-properties.png) - **Viewers** can access only the **Design** mode with read-only permission, -Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md/#access-rights-and-permissions). +Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md#access-rights-and-permissions). diff --git a/docs/components/modeler/web-modeler/deploy-process-application.md b/docs/components/modeler/web-modeler/deploy-process-application.md index 91385f1ddd2..d6d94de3d77 100644 --- a/docs/components/modeler/web-modeler/deploy-process-application.md +++ b/docs/components/modeler/web-modeler/deploy-process-application.md @@ -39,7 +39,7 @@ Once validation is complete, deploy your process application to cluster stages i All BPMN, DMN, and form files contained in the process application folder are deployed as a single bundle. -In Self-Managed, you can deploy your diagram to the cluster defined in your Web Modeler [configuration](/self-managed/modeler/web-modeler/configuration/configuration.md#clusters). You should have the `Zeebe` [role](/self-managed/identity/user-guide/roles/add-assign-role.md/#add-a-role) assigned in Identity to be authorized to deploy. +In Self-Managed, you can deploy your diagram to the cluster defined in your Web Modeler [configuration](/self-managed/modeler/web-modeler/configuration/configuration.md#clusters). You should have the `Zeebe` [role](/self-managed/identity/user-guide/roles/add-assign-role.md#add-a-role) assigned in Identity to be authorized to deploy. :::note If any resource fails to deploy, the whole deployment [fails](#deployment-errors) and the cluster state remains unchanged. This safely ensures that a process application cannot be deployed incompletely or in an inconsistent state. diff --git a/docs/components/modeler/web-modeler/play-your-process.md b/docs/components/modeler/web-modeler/play-your-process.md index fcf731fe8dc..3d69f05065f 100644 --- a/docs/components/modeler/web-modeler/play-your-process.md +++ b/docs/components/modeler/web-modeler/play-your-process.md @@ -231,7 +231,7 @@ After selecting the **Play** tab in Self-Managed, you are prompted to select fro - The environment variables `CAMUNDA_CUSTOM_CERT_CHAIN_PATH`, `CAMUNDA_CUSTOM_PRIVATE_KEY_PATH`, `CAMUNDA_CUSTOM_ROOT_CERT_PATH`, and `CAMUNDA_CUSTOM_ROOT_CERT_STRING` can be set in Docker or Helm chart setups. However, these configurations have not been tested with Play's behavior, and therefore are not supported when used with Play. - Play cannot check the presence of Connector secrets in Self-Managed setups. If a secret is missing, Play will show an incident at runtime. - Learn more about [configuring Connector secrets](/self-managed/connectors-deployment/connectors-configuration.md/#secrets). + Learn more about [configuring Connector secrets](/self-managed/connectors-deployment/connectors-configuration.md#secrets). ## Play Usage and Billing Considerations 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 1c5441f1a99..9752abcee41 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 @@ -37,7 +37,7 @@ To deploy, click **Deploy** in the upper right corner of the modeling screen: ![The deploy dialog of a BPMN diagram](img/web-modeler-deploy.png) -In Self-Managed, you can deploy your diagram to the cluster defined in your Web Modeler [configuration](/self-managed/modeler/web-modeler/configuration/configuration.md#clusters). You should have the `Zeebe` [role](/self-managed/identity/user-guide/roles/add-assign-role.md/#add-a-role) assigned in Identity to be authorized to deploy. +In Self-Managed, you can deploy your diagram to the cluster defined in your Web Modeler [configuration](/self-managed/modeler/web-modeler/configuration/configuration.md#clusters). You should have the `Zeebe` [role](/self-managed/identity/user-guide/roles/add-assign-role.md#add-a-role) assigned in Identity to be authorized to deploy. ### Before deploying a process diff --git a/docs/reference/release-notes/850.md b/docs/reference/release-notes/850.md index 23e61dd0d92..bd51955d97f 100644 --- a/docs/reference/release-notes/850.md +++ b/docs/reference/release-notes/850.md @@ -272,7 +272,7 @@ The shared processes require Tasklist authorization to be started, in contrast t -Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md/#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. +Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. ### Hot backups: Azure Cloud Storage support Self-Managed diff --git a/docs/self-managed/concepts/access-control/user-task-access-restrictions.md b/docs/self-managed/concepts/access-control/user-task-access-restrictions.md index 8dcab6786ea..275ff04bcf4 100644 --- a/docs/self-managed/concepts/access-control/user-task-access-restrictions.md +++ b/docs/self-managed/concepts/access-control/user-task-access-restrictions.md @@ -15,7 +15,7 @@ User task access restrictions allow you to control the level of access a [user]( ### User task access restrictions -[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md/#user-restrictions) are used in Tasklist to control task access for a +[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md#user-restrictions) are used in Tasklist to control task access for a user or [group](/self-managed/identity/user-guide/groups/create-group.md). The restrictions are related to the candidate users or groups set up on user task definitions. diff --git a/docs/self-managed/setup/deploy/amazon/aws-ec2.md b/docs/self-managed/setup/deploy/amazon/aws-ec2.md index 8ffb1beba7c..137c1498c27 100644 --- a/docs/self-managed/setup/deploy/amazon/aws-ec2.md +++ b/docs/self-managed/setup/deploy/amazon/aws-ec2.md @@ -6,7 +6,7 @@ description: "Learn how to install Camunda 8 on AWS EC2 instances." This guide provides a detailed walkthrough for installing the Camunda 8 single JAR on AWS EC2 instances. It focuses on managed services by AWS and their cloud offering. Finally, you will verify that the connection to your Self-Managed Camunda 8 environment is working. -This guide focuses on setting up the [orchestration cluster](/self-managed/reference-architecture/reference-architecture.md#orchestration-cluster-vs-web-modeler-and-console) for Camunda 8. The Web Modeler and Console are not covered in this manual deployment approach. These components are supported on Kubernetes and should be [deployed using Kubernetes](/self-managed/setup/install.md/#install-web-modeler). +This guide focuses on setting up the [orchestration cluster](/self-managed/reference-architecture/reference-architecture.md#orchestration-cluster-vs-web-modeler-and-console) for Camunda 8. The Web Modeler and Console are not covered in this manual deployment approach. These components are supported on Kubernetes and should be [deployed using Kubernetes](/self-managed/setup/install.md#install-web-modeler). :::note Using other Cloud providers This guide is built around the available tools and services that AWS offers, but is not limited to AWS. The scripts and ideas included can be adjusted for any other cloud provider and use case. diff --git a/docs/self-managed/setup/deploy/local/c8run.md b/docs/self-managed/setup/deploy/local/c8run.md index 88b78bfbfd2..e5e35934726 100644 --- a/docs/self-managed/setup/deploy/local/c8run.md +++ b/docs/self-managed/setup/deploy/local/c8run.md @@ -87,7 +87,7 @@ A success notification displays when complete. [Start a new process instance](/c ### Use built-in and custom Connectors -Desktop Modeler [automatically fetches](/components/modeler/desktop-modeler/use-connectors.md/#automatic-connector-template-fetching) templates for pre-built Connectors. [Custom Connectors](/components/connectors/custom-built-connectors/connector-sdk.md) can also be added to your Camunda 8 Run distribution. +Desktop Modeler [automatically fetches](/components/modeler/desktop-modeler/use-connectors.md#automatic-connector-template-fetching) templates for pre-built Connectors. [Custom Connectors](/components/connectors/custom-built-connectors/connector-sdk.md) can also be added to your Camunda 8 Run distribution. To add a custom Connector: diff --git a/docs/self-managed/setup/deploy/local/manual.md b/docs/self-managed/setup/deploy/local/manual.md index d03b18b592c..b24d42b708f 100644 --- a/docs/self-managed/setup/deploy/local/manual.md +++ b/docs/self-managed/setup/deploy/local/manual.md @@ -233,7 +233,7 @@ A local setup of Identity in Camunda 8 is not yet supported out-of-the-box, use ## Run Optimize -The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md/#optimize) instead. +The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md#optimize) instead. ## Run Web Modeler diff --git a/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md b/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md index be82a783369..aeb15386c41 100644 --- a/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md +++ b/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md @@ -19,7 +19,7 @@ In this guide, we step through the configuration required to connect Camunda to - Client ID - Client secrets - Audience -- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md/#oidc-configuration) to use for initial access. +- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md#oidc-configuration) to use for initial access. :::note The steps below are a general approach for the Camunda components; it is important you reference the [component-specific diff --git a/docs/self-managed/zeebe-deployment/configuration/broker.md b/docs/self-managed/zeebe-deployment/configuration/broker.md index 076c5fd5cc0..dd0b3ebfad3 100644 --- a/docs/self-managed/zeebe-deployment/configuration/broker.md +++ b/docs/self-managed/zeebe-deployment/configuration/broker.md @@ -870,7 +870,7 @@ as well. ::: :::note -If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md/#zeebegatewaymultitenancy). +If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md#zeebegatewaymultitenancy). ::: | Field | Description | Example value | diff --git a/docs/self-managed/zeebe-deployment/configuration/gateway.md b/docs/self-managed/zeebe-deployment/configuration/gateway.md index 32958b815d4..ac1593b8043 100644 --- a/docs/self-managed/zeebe-deployment/configuration/gateway.md +++ b/docs/self-managed/zeebe-deployment/configuration/gateway.md @@ -497,7 +497,7 @@ as well. ::: :::note -If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md/#multitenancy-configuration). +If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md#multitenancy-configuration). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.3/components/console/manage-clusters/settings.md b/versioned_docs/version-8.3/components/console/manage-clusters/settings.md index fafbf265e66..eeb7070e83d 100644 --- a/versioned_docs/version-8.3/components/console/manage-clusters/settings.md +++ b/versioned_docs/version-8.3/components/console/manage-clusters/settings.md @@ -24,7 +24,7 @@ You can enable resource-based authorization on a per-cluster basis to control th - Disable this setting if you do not want to use resource-based authorization in the cluster. You can still configure resource authorizations, but they are only applied to cluster users when you enable this setting. :::tip -For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md/#resource-based-authorizations). +For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md#resource-based-authorizations). ::: ## Automatic cluster updates diff --git a/versioned_docs/version-8.3/self-managed/react-components/components.md b/versioned_docs/version-8.3/self-managed/react-components/components.md index aba76ce736d..ba18c2b7449 100644 --- a/versioned_docs/version-8.3/self-managed/react-components/components.md +++ b/versioned_docs/version-8.3/self-managed/react-components/components.md @@ -7,7 +7,7 @@ - Connectors - Optimize - Identity -- Web Modeler [Enterprise only](/reference/licenses.md/#web-modeler) +- Web Modeler [Enterprise only](/reference/licenses.md#web-modeler) All components except Web Modeler and Console are single Java applications. Depending on your needs, you might not need all of the above components to successfully use Camunda 8. diff --git a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/broker.md b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/broker.md index 59e7c1dcbd7..6cd3c093ca9 100644 --- a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/broker.md +++ b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/broker.md @@ -584,7 +584,7 @@ as well. ::: :::note -If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md/#zeebegatewaymultitenancy). +If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md#zeebegatewaymultitenancy). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/gateway.md b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/gateway.md index ba7bbe1097d..2c60d1f5af9 100644 --- a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/gateway.md +++ b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/gateway.md @@ -335,7 +335,7 @@ To use multi-tenancy, you must set [`authentication.mode`](#zeebegatewayclusters ::: :::note -If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md/#multitenancy-configuration). +If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md#multitenancy-configuration). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.4/apis-tools/frontend-development/introduction-to-task-applications.md b/versioned_docs/version-8.4/apis-tools/frontend-development/introduction-to-task-applications.md index 0058aa79196..362efedb849 100644 --- a/versioned_docs/version-8.4/apis-tools/frontend-development/introduction-to-task-applications.md +++ b/versioned_docs/version-8.4/apis-tools/frontend-development/introduction-to-task-applications.md @@ -18,7 +18,7 @@ If you are not familiar with the idea of human task management itself, read the ## What are task applications? -Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) (also referred to as a **human task**) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: +Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) (also referred to as a **human task**) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: - Listing available tasks and allowing users to select a task to work on. - Providing filter and search options for users so they can more easily find the right next task to work on. @@ -61,9 +61,9 @@ The **task details panel** shows the details of the selected task. A [form](/gui :::tip Typically, a task application utilizes forms to capture information from the user, to make a decision, to collect the results from a real-world task, or to provide task instructions to the user. -However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask`. +However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask`. -For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md/#custom-form-key). +For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md#custom-form-key). ::: On the top of the form, a header shows the title of the task to work on, and the current assignee. Depending on the status of the assignment, a button allows you to assign the task to yourself or release it to the queue. diff --git a/versioned_docs/version-8.4/components/console/manage-clusters/settings.md b/versioned_docs/version-8.4/components/console/manage-clusters/settings.md index fafbf265e66..eeb7070e83d 100644 --- a/versioned_docs/version-8.4/components/console/manage-clusters/settings.md +++ b/versioned_docs/version-8.4/components/console/manage-clusters/settings.md @@ -24,7 +24,7 @@ You can enable resource-based authorization on a per-cluster basis to control th - Disable this setting if you do not want to use resource-based authorization in the cluster. You can still configure resource authorizations, but they are only applied to cluster users when you enable this setting. :::tip -For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md/#resource-based-authorizations). +For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md#resource-based-authorizations). ::: ## Automatic cluster updates diff --git a/versioned_docs/version-8.4/self-managed/concepts/access-control/user-task-access-restrictions.md b/versioned_docs/version-8.4/self-managed/concepts/access-control/user-task-access-restrictions.md index 2d3acbf2863..afd9a0dda57 100644 --- a/versioned_docs/version-8.4/self-managed/concepts/access-control/user-task-access-restrictions.md +++ b/versioned_docs/version-8.4/self-managed/concepts/access-control/user-task-access-restrictions.md @@ -14,7 +14,7 @@ User task access restrictions allow you to control the level of access a [user]( ### User task access restrictions -[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md/#user-restrictions) are used in Tasklist to control task access for a +[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md#user-restrictions) are used in Tasklist to control task access for a user or [group](/self-managed/identity/user-guide/groups/create-group.md). The restrictions are related to the candidate users or groups set up on user task definitions. diff --git a/versioned_docs/version-8.4/self-managed/react-components/components.md b/versioned_docs/version-8.4/self-managed/react-components/components.md index fd5bcbced8b..fad798d0e9b 100644 --- a/versioned_docs/version-8.4/self-managed/react-components/components.md +++ b/versioned_docs/version-8.4/self-managed/react-components/components.md @@ -7,7 +7,7 @@ - Connectors - Optimize - Identity -- Web Modeler [Enterprise only](/reference/licenses.md/#web-modeler) +- Web Modeler [Enterprise only](/reference/licenses.md#web-modeler) :::note As of version 8.4, Console is only available in [Camunda 8 SaaS](/components/components-overview.md). diff --git a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/broker.md b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/broker.md index 109f6e805f4..4368ea48410 100644 --- a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/broker.md +++ b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/broker.md @@ -584,7 +584,7 @@ as well. ::: :::note -If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md/#zeebegatewaymultitenancy). +If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md#zeebegatewaymultitenancy). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/gateway.md b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/gateway.md index 2f861de6932..2b9743259ef 100644 --- a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/gateway.md +++ b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/gateway.md @@ -342,7 +342,7 @@ as well. ::: :::note -If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md/#multitenancy-configuration). +If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md#multitenancy-configuration). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.5/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md b/versioned_docs/version-8.5/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md index 4666037e70a..4cb9cb723ec 100644 --- a/versioned_docs/version-8.5/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md +++ b/versioned_docs/version-8.5/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md @@ -13,7 +13,7 @@ Task applications are the interface between humans and Camunda processes to orch ## What are task applications? -Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) (also referred to as a **human task**) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: +Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) (also referred to as a **human task**) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: - Listing available tasks and allowing users to select a task to work on. - Providing filter and search options for users so they can more easily find the right next task to work on. @@ -56,9 +56,9 @@ The **task details panel** shows the details of the selected task. A [form](/gui :::tip Typically, a task application utilizes forms to capture information from the user, to make a decision, to collect the results from a real-world task, or to provide task instructions to the user. -However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). +However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). -For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md/#custom-form-key). +For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md#custom-form-key). ::: On the top of the form, a header shows the title of the task to work on, and the current assignee. Depending on the status of the assignment, a button allows you to assign the task to yourself or release it to the queue. diff --git a/versioned_docs/version-8.5/components/console/manage-clusters/settings.md b/versioned_docs/version-8.5/components/console/manage-clusters/settings.md index 3dfedeceed3..c8a6628a3af 100644 --- a/versioned_docs/version-8.5/components/console/manage-clusters/settings.md +++ b/versioned_docs/version-8.5/components/console/manage-clusters/settings.md @@ -24,7 +24,7 @@ You can enable resource-based authorization on a per-cluster basis to control th - Disable this setting if you do not want to use resource-based authorization in the cluster. You can still configure resource authorizations, but they are only applied to cluster users when you enable this setting. :::tip -For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md/#resource-based-authorizations). +For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md#resource-based-authorizations). ::: ## Automatic cluster updates diff --git a/versioned_docs/version-8.5/components/modeler/web-modeler/collaborate-with-modes.md b/versioned_docs/version-8.5/components/modeler/web-modeler/collaborate-with-modes.md index 465b21d9010..497bbf6b574 100644 --- a/versioned_docs/version-8.5/components/modeler/web-modeler/collaborate-with-modes.md +++ b/versioned_docs/version-8.5/components/modeler/web-modeler/collaborate-with-modes.md @@ -31,4 +31,4 @@ When a process template is selected, the default mode is **Implement**. ![read only properties](img/read-only-properties.png) - **Viewers** can access only the **Design** mode with read-only permission, -Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md/#access-rights-and-permissions). +Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md#access-rights-and-permissions). diff --git a/versioned_docs/version-8.5/reference/release-notes/850.md b/versioned_docs/version-8.5/reference/release-notes/850.md index a8d636718f2..9f4df61ccaa 100644 --- a/versioned_docs/version-8.5/reference/release-notes/850.md +++ b/versioned_docs/version-8.5/reference/release-notes/850.md @@ -272,7 +272,7 @@ The shared processes require Tasklist authorization to be started, in contrast t -Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md/#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. +Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. ### Hot backups: Azure Cloud Storage support Self-Managed diff --git a/versioned_docs/version-8.5/self-managed/concepts/access-control/user-task-access-restrictions.md b/versioned_docs/version-8.5/self-managed/concepts/access-control/user-task-access-restrictions.md index 8dcab6786ea..275ff04bcf4 100644 --- a/versioned_docs/version-8.5/self-managed/concepts/access-control/user-task-access-restrictions.md +++ b/versioned_docs/version-8.5/self-managed/concepts/access-control/user-task-access-restrictions.md @@ -15,7 +15,7 @@ User task access restrictions allow you to control the level of access a [user]( ### User task access restrictions -[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md/#user-restrictions) are used in Tasklist to control task access for a +[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md#user-restrictions) are used in Tasklist to control task access for a user or [group](/self-managed/identity/user-guide/groups/create-group.md). The restrictions are related to the candidate users or groups set up on user task definitions. diff --git a/versioned_docs/version-8.5/self-managed/react-components/components.md b/versioned_docs/version-8.5/self-managed/react-components/components.md index 7659e1d03ab..21bf3049693 100644 --- a/versioned_docs/version-8.5/self-managed/react-components/components.md +++ b/versioned_docs/version-8.5/self-managed/react-components/components.md @@ -7,8 +7,8 @@ - Connectors - Optimize - Identity -- Web Modeler [Enterprise only](/reference/licenses.md/#web-modeler) -- Console [Enterprise only](/reference/licenses.md/#console) +- Web Modeler [Enterprise only](/reference/licenses.md#web-modeler) +- Console [Enterprise only](/reference/licenses.md#console) All components except Web Modeler and Console are single Java applications. Depending on your needs, you might not need all of the above components to successfully use Camunda 8. diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/local/manual.md b/versioned_docs/version-8.5/self-managed/setup/deploy/local/manual.md index 0305a1b323c..471ba3a6374 100644 --- a/versioned_docs/version-8.5/self-managed/setup/deploy/local/manual.md +++ b/versioned_docs/version-8.5/self-managed/setup/deploy/local/manual.md @@ -227,7 +227,7 @@ A local setup of Identity in Camunda 8 is not yet supported out-of-the-box, use ## Run Optimize -The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md/#optimize) instead. +The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md#optimize) instead. ## Run Web Modeler diff --git a/versioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md b/versioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md index e4c578c0379..bb7f4854c9e 100644 --- a/versioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md +++ b/versioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md @@ -19,7 +19,7 @@ In this guide, we step through the configuration required to connect Camunda to - Client ID - Client secrets - Audience -- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md/#oidc-configuration) to use for initial access. +- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md#oidc-configuration) to use for initial access. :::note The steps below are a general approach for the Camunda components; it is important you reference the [component-specific diff --git a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/broker.md b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/broker.md index 581aba36ee1..dd02043d243 100644 --- a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/broker.md +++ b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/broker.md @@ -688,7 +688,7 @@ as well. ::: :::note -If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md/#zeebegatewaymultitenancy). +If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md#zeebegatewaymultitenancy). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/gateway.md b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/gateway.md index b04075cba48..1a10beaa943 100644 --- a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/gateway.md +++ b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/gateway.md @@ -419,7 +419,7 @@ as well. ::: :::note -If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md/#multitenancy-configuration). +If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md#multitenancy-configuration). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.6/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md b/versioned_docs/version-8.6/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md index 3d343cdcc74..96ada8f88c6 100644 --- a/versioned_docs/version-8.6/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md +++ b/versioned_docs/version-8.6/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md @@ -13,7 +13,7 @@ Task applications are the interface between humans and Camunda processes to orch ## What are task applications? -Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) (for [human task orchestration](/guides/getting-started-orchestrate-human-tasks.md)) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: +Task applications are end-user applications that allow humans to perform work orchestrated with a process. A [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) (for [human task orchestration](/guides/getting-started-orchestrate-human-tasks.md)) represents a single **work item** to be performed by an individual or a group. The jobs of a task application include: - Listing available tasks and allowing users to select a task to work on. - Providing filter and search options for users so they can more easily find the right next task to work on. @@ -59,9 +59,9 @@ Task details are shown when a task is selected from the queue. A [form](/guides/ :::tip Typically, a task application utilizes forms to capture information from the user, to make a decision, to collect the results from a real-world task, or to provide task instructions to the user. -However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md/#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). However, note that job worker-based user tasks are deprecated with Camunda 8.6. While these are currently still supported, consider [migrating to Zeebe user tasks](/apis-tools/migration-manuals/migrate-to-zeebe-user-tasks.md). +However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only). However, note that job worker-based user tasks are deprecated with Camunda 8.6. While these are currently still supported, consider [migrating to Zeebe user tasks](/apis-tools/migration-manuals/migrate-to-zeebe-user-tasks.md). -For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md/#custom-form-key). +For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md#custom-form-key). ::: On the top of the form, a header shows the title of the task to work on, and the current assignee. Depending on the status of the assignment, a button allows you to assign the task to yourself or release it to the queue. diff --git a/versioned_docs/version-8.6/components/concepts/execution-listeners.md b/versioned_docs/version-8.6/components/concepts/execution-listeners.md index 3ea3b4ce163..2f898a0c72f 100644 --- a/versioned_docs/version-8.6/components/concepts/execution-listeners.md +++ b/versioned_docs/version-8.6/components/concepts/execution-listeners.md @@ -53,7 +53,7 @@ Execution listeners are processed by [job workers](/components/concepts/job-work See [open a job worker](/apis-tools/java-client-examples/job-worker-open.md) for an example of how to create a job worker and handler that can also process execution listener jobs. :::note -[Throwing a BPMN error](/components/best-practices/development/dealing-with-problems-and-exceptions.md/#throwing-and-handling-bpmn-errors) for an execution listener's job is not supported. +[Throwing a BPMN error](/components/best-practices/development/dealing-with-problems-and-exceptions.md#throwing-and-handling-bpmn-errors) for an execution listener's job is not supported. ::: ## Variables in an execution listener diff --git a/versioned_docs/version-8.6/components/console/manage-clusters/settings.md b/versioned_docs/version-8.6/components/console/manage-clusters/settings.md index 3dfedeceed3..c8a6628a3af 100644 --- a/versioned_docs/version-8.6/components/console/manage-clusters/settings.md +++ b/versioned_docs/version-8.6/components/console/manage-clusters/settings.md @@ -24,7 +24,7 @@ You can enable resource-based authorization on a per-cluster basis to control th - Disable this setting if you do not want to use resource-based authorization in the cluster. You can still configure resource authorizations, but they are only applied to cluster users when you enable this setting. :::tip -For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md/#resource-based-authorizations). +For more information on resource-based authorization, see [resource authorizations](/components/concepts/resource-authorizations.md) and [resource-based authorization](/components/console/manage-organization/manage-users.md#resource-based-authorizations). ::: ## Automatic cluster updates diff --git a/versioned_docs/version-8.6/components/modeler/web-modeler/collaborate-with-modes.md b/versioned_docs/version-8.6/components/modeler/web-modeler/collaborate-with-modes.md index 465b21d9010..497bbf6b574 100644 --- a/versioned_docs/version-8.6/components/modeler/web-modeler/collaborate-with-modes.md +++ b/versioned_docs/version-8.6/components/modeler/web-modeler/collaborate-with-modes.md @@ -31,4 +31,4 @@ When a process template is selected, the default mode is **Implement**. ![read only properties](img/read-only-properties.png) - **Viewers** can access only the **Design** mode with read-only permission, -Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md/#access-rights-and-permissions). +Read more about the [different roles and how to assign them](components/modeler/web-modeler/collaboration.md#access-rights-and-permissions). diff --git a/versioned_docs/version-8.6/components/modeler/web-modeler/play-your-process.md b/versioned_docs/version-8.6/components/modeler/web-modeler/play-your-process.md index 857207d6c67..8c473a813f3 100644 --- a/versioned_docs/version-8.6/components/modeler/web-modeler/play-your-process.md +++ b/versioned_docs/version-8.6/components/modeler/web-modeler/play-your-process.md @@ -202,7 +202,7 @@ If no cluster is configured, Web Modeler requests the following cluster details - The environment variables `CAMUNDA_CUSTOM_CERT_CHAIN_PATH`, `CAMUNDA_CUSTOM_PRIVATE_KEY_PATH`, `CAMUNDA_CUSTOM_ROOT_CERT_PATH`, and `CAMUNDA_CUSTOM_ROOT_CERT_STRING` can be set in Docker or Helm chart setups. However, these configurations have not been tested with Play's behavior, and therefore are not supported when used with Play. - Play cannot check the presence of Connector secrets in Self-Managed setups. If a secret is missing, Play will show an incident at runtime. - Learn more about [configuring Connector secrets](/self-managed/connectors-deployment/connectors-configuration.md/#secrets). + Learn more about [configuring Connector secrets](/self-managed/connectors-deployment/connectors-configuration.md#secrets). ## Play Usage and Billing Considerations diff --git a/versioned_docs/version-8.6/reference/release-notes/850.md b/versioned_docs/version-8.6/reference/release-notes/850.md index d514f55adca..7daa1ef9cf4 100644 --- a/versioned_docs/version-8.6/reference/release-notes/850.md +++ b/versioned_docs/version-8.6/reference/release-notes/850.md @@ -272,7 +272,7 @@ The shared processes require Tasklist authorization to be started, in contrast t -Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md/#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. +Users now have the option to [automatically select](/components/tasklist/userguide/using-tasklist.md#auto-select-first-available-task) the next available task in Tasklist to speed up task workflows. ### Hot backups: Azure Cloud Storage support Self-Managed diff --git a/versioned_docs/version-8.6/self-managed/concepts/access-control/user-task-access-restrictions.md b/versioned_docs/version-8.6/self-managed/concepts/access-control/user-task-access-restrictions.md index 8dcab6786ea..275ff04bcf4 100644 --- a/versioned_docs/version-8.6/self-managed/concepts/access-control/user-task-access-restrictions.md +++ b/versioned_docs/version-8.6/self-managed/concepts/access-control/user-task-access-restrictions.md @@ -15,7 +15,7 @@ User task access restrictions allow you to control the level of access a [user]( ### User task access restrictions -[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md/#user-restrictions) are used in Tasklist to control task access for a +[User task access restrictions](self-managed/tasklist-deployment/tasklist-authentication.md#user-restrictions) are used in Tasklist to control task access for a user or [group](/self-managed/identity/user-guide/groups/create-group.md). The restrictions are related to the candidate users or groups set up on user task definitions. diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/local/c8run.md b/versioned_docs/version-8.6/self-managed/setup/deploy/local/c8run.md index de44b096321..bd69cfcb254 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/local/c8run.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/local/c8run.md @@ -87,7 +87,7 @@ A success notification displays when complete. [Start a new process instance](/c ### Use built-in and custom Connectors -Desktop Modeler [automatically fetches](/components/modeler/desktop-modeler/use-connectors.md/#automatic-connector-template-fetching) templates for pre-built Connectors. [Custom Connectors](/components/connectors/custom-built-connectors/connector-sdk.md) can also be added to your Camunda 8 Run distribution. +Desktop Modeler [automatically fetches](/components/modeler/desktop-modeler/use-connectors.md#automatic-connector-template-fetching) templates for pre-built Connectors. [Custom Connectors](/components/connectors/custom-built-connectors/connector-sdk.md) can also be added to your Camunda 8 Run distribution. To add a custom Connector: diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/local/manual.md b/versioned_docs/version-8.6/self-managed/setup/deploy/local/manual.md index d03b18b592c..b24d42b708f 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/local/manual.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/local/manual.md @@ -233,7 +233,7 @@ A local setup of Identity in Camunda 8 is not yet supported out-of-the-box, use ## Run Optimize -The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md/#optimize) instead. +The installation of Optimize is described in [Optimize Setup]($optimize$/self-managed/optimize-deployment/install-and-start). A local setup in Camunda 8 is not yet supported out-of-the-box, use [Docker](/self-managed/setup/deploy/other/docker.md#optimize) instead. ## Run Web Modeler diff --git a/versioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md b/versioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md index 1e4598c42a6..0ef99068795 100644 --- a/versioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md +++ b/versioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md @@ -19,7 +19,7 @@ In this guide, we step through the configuration required to connect Camunda to - Client ID - Client secrets - Audience -- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md/#oidc-configuration) to use for initial access. +- A [claim name and value](/self-managed/identity/deployment/configuration-variables.md#oidc-configuration) to use for initial access. :::note The steps below are a general approach for the Camunda components; it is important you reference the [component-specific diff --git a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md index 121a90177ea..c47e249fcdf 100644 --- a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md +++ b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md @@ -842,7 +842,7 @@ as well. ::: :::note -If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md/#zeebegatewaymultitenancy). +If you are using a standalone gateway, refer to the [gateway configuration guide](./gateway.md#zeebegatewaymultitenancy). ::: | Field | Description | Example value | diff --git a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.md b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.md index b9b07fa78bc..da711b4b109 100644 --- a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.md +++ b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.md @@ -473,7 +473,7 @@ as well. ::: :::note -If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md/#multitenancy-configuration). +If you are using an embedded gateway, refer to the [broker configuration guide](./broker.md#multitenancy-configuration). ::: | Field | Description | Example value |