diff --git a/docs/components/modeler/web-modeler/create-a-process-application.md b/docs/components/modeler/web-modeler/create-a-process-application.md new file mode 100644 index 0000000000..88e7eb1f55 --- /dev/null +++ b/docs/components/modeler/web-modeler/create-a-process-application.md @@ -0,0 +1,63 @@ +--- +id: create-a-process-application +title: Create a process application +description: Create a process application and select a development cluster to deploy to. +--- + +import EmptyProjectImg from './img/process-applications/empty-project.png' +import ReassignMainProcessImg from './img/process-applications/reassign-main-process.png' +import FileListImg from './img/process-applications/file-list.png' + +Create a process application in your project to work on and deploy a set of related files. + +## Create a process application + +To create a process application, either: + +- Select **Create process application** in an empty project. +- Select **New project > Create process application** if you have not yet created a project. +

Create a process application from an empty project

+ +### Select a default cluster + +Camunda 8 SaaS only + +When you create a process application, you must select a development cluster to deploy to. + +- If you have already created a cluster, turn on the toggle next to the cluster name in **Select a development cluster**. +- If you have not yet [created a cluster](/guides/create-cluster.md), or if **No Cluster has been created yet** is shown, select **Create new dev cluster**. The Console **Clusters** tab opens so you can create a new cluster. + +:::note + +- If your modeling plan does not allow you to create more clusters, a `Cluster creation is not available on this modeling plan` warning is shown. Contact the administrator or owner of your organization to upgrade your plan. + +- If you do not have the proper permissions to create a cluster, a `Missing permissions` warning is shown. Contact the administrator or owner of your organization to create a cluster. + +::: + +### Main process + +After you have created a process application, a new BPMN diagram is created and labeled as the main process. + +- The main process diagram is named using the process application name. You can rename the main process diagram any time. +- A process application must have a main process. You cannot delete or move the main process diagram out of the process application. +- You can assign another BPMN diagram as the main process using the **Reassign main process** option in the action menu. +

+ Reassign the main process +

+ +### Add files to a process application + +To add more files to the process application, either: + +- Select the **Create new** dropdown on the process application page to create and add a new file. +- Drag and drop files from your local computer. +- Move an existing file into the process application from a different location in Web Modeler. + +The main process is always displayed at the top of the file list, regardless of the sort order. + +

Process application file list

+ +:::note +Process IDs, decision IDs, and form IDs must be unique across all files within a process application. This avoids ambiguity and conflicts when you link resources and deploy the process application. +::: diff --git a/docs/components/modeler/web-modeler/deploy-process-application.md b/docs/components/modeler/web-modeler/deploy-process-application.md new file mode 100644 index 0000000000..addecf2539 --- /dev/null +++ b/docs/components/modeler/web-modeler/deploy-process-application.md @@ -0,0 +1,66 @@ +--- +id: deploy-process-application +title: Deploy and run your process application +description: You can deploy your process application to a cluster, and run your process application to test, debug, and observe how it performs in a live environment. +--- + +import DeployImg from './img/process-applications/define-stages-deploy.png' +import RunProcessApplicationImg from './img/process-applications/run-process-application.png' +import DeployErrorImg from './img/process-applications/deploy-error.png' + +You can deploy your process application to a cluster, and run your process application to test, debug, and observe how it performs in a live environment. + +## Deploy your process application + +To deploy your process application: + +1. Open the [main process](create-a-process-application.md#main-process). +1. Select **Deploy** to open the **Deploy process application** modal. +

Deploy a process application

+1. Turn on the toggle for the cluster stage you want to deploy to. +1. Perform any other actions as required, such as: + - Unpausing the chosen cluster if it has been auto-paused. Select **Resume**. + - Managing the cluster. Select **Manage**. + - [Defining the stages](process-application-pipeline.md#deployment-pipeline-stages) of your deployment pipeline. Select **Define stages**. +1. Select **Deploy** to deploy the process application to the selected cluster. + +All BPMN, DMN, and form files contained in the process application folder are deployed as a single bundle. + +:::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. +::: + +## Run a process application + +You can run your process application to test, debug, and observe how it performs in a live environment. + +To run your process application: + +1. Open the [main process](create-a-process-application.md#main-process). +1. Select **Run** to open the **Start instance** modal. +

Run a process application

+1. Select **Run** to start a new instance.

+ +:::info +Single-file deployment is not supported in a process application. If you select **Deploy** or **Run** in any diagram other than the main process, you are prompted to open the main process for deployment. +::: + +## Deployment errors + +If the deployment of a process application fails (for example, because one or more of the contained resources has invalid implementation properties), a modal is shown containing the error message thrown by the Zeebe engine. + +The message typically provides the name of the affected resource, the ID of the invalid diagram element, and the error details. + +

Process application deployment error

+ +### Deployment of external resources + +You can link BPMN processes, DMN decisions, or forms that are not part of the process application itself (external +resources) from any process inside a process application. + +Note that when you deploy the process application: + +- Linked external forms are deployed together with the process application. +- Linked external BPMN and DMN diagrams are _not_ deployed together. You must deploy these separately. diff --git a/docs/components/modeler/web-modeler/img/process-applications/define-stages-deploy.png b/docs/components/modeler/web-modeler/img/process-applications/define-stages-deploy.png new file mode 100644 index 0000000000..b3893db5f9 Binary files /dev/null and b/docs/components/modeler/web-modeler/img/process-applications/define-stages-deploy.png differ diff --git a/docs/components/modeler/web-modeler/img/process-applications/define-stages.png b/docs/components/modeler/web-modeler/img/process-applications/define-stages.png new file mode 100644 index 0000000000..16abcc8663 Binary files /dev/null and b/docs/components/modeler/web-modeler/img/process-applications/define-stages.png differ diff --git a/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-get-started.png b/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-get-started.png new file mode 100644 index 0000000000..d0b989a129 Binary files /dev/null and b/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-get-started.png differ diff --git a/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-pipeline.png b/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-pipeline.png new file mode 100644 index 0000000000..95ec13cbce Binary files /dev/null and b/docs/components/modeler/web-modeler/img/process-applications/diagram-process-application-pipeline.png differ diff --git a/docs/components/modeler/web-modeler/process-application-pipeline.md b/docs/components/modeler/web-modeler/process-application-pipeline.md new file mode 100644 index 0000000000..d73034131b --- /dev/null +++ b/docs/components/modeler/web-modeler/process-application-pipeline.md @@ -0,0 +1,90 @@ +--- +id: process-application-pipeline +title: Process application development lifecycle +description: You can use Web Modeler to quickly develop and progress low-risk process application releases through the stages of a typical development lifecycle. +--- + +import DeployProcessApplicationDiagramImg from './img/process-applications/diagram-process-application-pipeline.png' +import DeployStagesImg from './img/process-applications/define-stages.png' + +You can use Web Modeler to quickly develop and progress low-risk process application releases through the stages of a typical development lifecycle. + +

Process application file list

+ +:::caution +For business-critical and higher-risk processes that require strict governance and/or quality requirements, you can [integrate Web Modeler into your CI/CD pipelines](/docs/guides/devops-lifecycle/integrate-web-modeler-in-ci-cd.md). +::: + +## Model + +During the modeling stage, you will typically: + +- [Create a process application](create-a-process-application.md) and select a default development cluster to deploy to. +- Invite other users to collaborate on the process application. +- Define and set up the clusters and deployment stages you will use in your development pipeline. +- Model your diagrams and associated resources, and fix errors shown in the modeler. +- Use [token simulation](token-simulation.md) to correct and optimize your process flow. + +### Deployment pipeline stages + +You can use the provided Web Modeler deployment pipeline to manage your application process deployment. The deployment pipeline has four stages named **Development**, **Testing**, **Staging**, and **Production**. + +| Stage | Description | +| :---------- | :-------------------------------------------------------------------------------------------------------------- | +| Development | Use to create and test new software features and changes. | +| Testing | Use for quality checks, ensuring software meets defined standards before release. | +| Staging | Use for controlled testing where changes are validated before deployment to production. | +| Production | The live system with the latest software. Only administrators and organization owners can deploy to this stage. | + +To define your deployment pipeline stages: + +1. Open the [main process](create-a-process-application.md#main-process). +1. Select **Deploy** to open the **Deploy process application** modal. +1. Select **Define stages** to open the **Define stages** modal. +

Define stage for deployment modal

+1. Select and assign a cluster to each deployment stage that you want to use in your deployment pipeline. +1. Select **Save** to save your changes and close the modal. + +:::note + +- An administrator must define the cluster to deploy to for each stage. +- During deployment, the next stage is not automatically selected. You must select the stage you want to promote to. +- You must select a cluster for at least one stage to be able to deploy. An **Undefined stages** warning is shown if no cluster is selected for at least one stage. + +::: + +## Validate + +When your process application is ready for validation you can deploy it to your development cluster. + +- Use [Play mode](play-your-process.md) to quickly validate the process behavior and play different scenarios. +- Validate that all files and resources are correctly deployed. + +:::note +Play is being rebuilt and progressively rolled out to more users. See [Play limitations and availability](/docs/components/modeler/web-modeler/play-your-process.md#limitations-and-availability) for Play limitations and why you might not see the **Play** tab. +::: + +## Review + +After validation is complete, you can release a version of your process application for review and approval. + +- Use [process application versioning](process-application-versioning.md) to track and review changes across the files and assets in the process application. You can [compare milestones](/docs/components/modeler/web-modeler/milestones.md#compare-milestones) to visually review changes between two versions of a BPMN file, or view code changes for other files. +- Use comments to make review collaboration easier. +- Approvers can add a comment to the main process diagram to indicate that a review is complete and that the process application is ready to be promoted to the next stage. + +## Promote + +After the review is complete, you can promote the versioned process application to the next stage(s) of the deployment pipeline. For example, promote to your testing cluster/stage, then to staging, and finally to production. + +:::info +If you want to use your own deployment pipeline after the review is complete, you can use [Git Sync](git-sync.md) at this point to deploy and promote the process application through your own pipeline. +::: + +## Process governance + +The Web Modeler development lifecycle provides the following process governance: + +| Governance | Description | +| :----------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Change control | Users can announce a review is complete by adding a comment to the main process diagram. Governance is not enforceable, and comments can be deleted. | +| Deployment control |

| diff --git a/docs/components/modeler/web-modeler/process-application-versioning.md b/docs/components/modeler/web-modeler/process-application-versioning.md new file mode 100644 index 0000000000..c0e6d1432d --- /dev/null +++ b/docs/components/modeler/web-modeler/process-application-versioning.md @@ -0,0 +1,41 @@ +--- +id: process-application-versioning +title: Process application versioning +description: Process applications allow you to deploy multiple related files together in a single bundle. +--- + +Although you cannot version a process application itself, you can use [bulk milestone creation](milestones.md#bulk-milestone-creation) and version tags to save a single 'versioned' snapshot of all the process application files in one action, instead of having to create separate milestones for every file. + +- When you create a milestone in any process application file, a milestone is also created with the same name (version tag) for all files currently available in the process application. + +- This allows you to track a process application through the development lifecycle and ensure the correct version is called. + +## A worked example + +In this example, you have a process application that contains multiple files as well as the main process. + +- You create a new milestone for the main process and enter "1.2" as the version tag. +- When you create this new milestone, a milestone is also created for every other file and named with the same "1.2" version tag. +- All files in the process application now have a "version 1.2" milestone. + +![Diagram showing an example process application bulk milestone creation](img/process-applications/process-application-milestone-diagram.png) + +## Create a bulk milestone + +To create a bulk milestone for a process application: + +1. Open any file in a process application and [create a milestone](milestones.md#create-a-milestone). +1. Enter a **Version tag**. +1. Select **Create** to create the milestone and matching version milestones for every file in the process application. + +![Create a milestone screen](img/milestones/web-modeler-milestone-create-versioned-milestone-highlight.png) + +Now when you open the milestone history for any file in the process application, you can use the file navigation header buttons to switch between files, and view their individual milestone history. See [compare milestones](/docs/components/modeler/web-modeler/milestones.md#compare-milestones). + +![Milestone history with file navigation header buttons highlighted](img/milestones/web-modeler-milestone-compare-process-application-files-highlight.png) + +:::note + +When naming your milestone with a version tag, you cannot edit or delete the created versions. + +::: diff --git a/docs/components/modeler/web-modeler/process-applications.md b/docs/components/modeler/web-modeler/process-applications.md index 8bc80c5b6a..d72967608d 100644 --- a/docs/components/modeler/web-modeler/process-applications.md +++ b/docs/components/modeler/web-modeler/process-applications.md @@ -1,174 +1,66 @@ --- id: process-applications title: Process applications -description: Process applications allow you to deploy multiple related files together in a single bundle. +description: A process application is a type of folder that contains a set of related files you can work on and deploy as a single bundle. --- -import EmptyProjectImg from './img/process-applications/empty-project.png' -import ReassignMainProcessImg from './img/process-applications/reassign-main-process.png' +import ProcessApplicationImg from './img/process-applications/diagram-process-application-get-started.png' import FileListImg from './img/process-applications/file-list.png' -import DeployProcessApplicationImg from './img/process-applications/deploy-process-application.png' -import RunProcessApplicationImg from './img/process-applications/run-process-application.png' -import DeployErrorImg from './img/process-applications/deploy-error.png' -## Idea and purpose +A process application is a type of folder that contains a set of related files you can work on and [deploy](deploy-process-application.md) as a single bundle. This reduces the risk of a broken deployment at runtime, and makes it easier to deploy related files. -A process application is a special type of folder in Web Modeler that allows you to work on a set of related files and -[deploy](#deploy-and-run-a-process-application) them together in a single bundle with just one click. -This reduces the risk of having a broken deployment at runtime and makes it more convenient to deploy related files. +

Process application

-We advise using a process application for all non-trivial automation projects. -These projects tend to have one main BPMN process that represents your end-to-end use case and additional files the -main process depends on, such as called supporting processes, DMN decisions, or forms. - -## Create a process application - -Create a new process application by clicking the **Create process application** button in an empty project or via -**New project > Create process application** if you have not yet created a project. - -

Create a process application from an empty project

- -### Select a default cluster - -Camunda 8 SaaS only - -After selecting **Create process application**, you may select a cluster to use for deployment during development. - -If you have not yet [created a cluster](/guides/create-cluster.md), or see **No Cluster has been created yet** in the modal, select **Create new dev cluster**. This will automatically take you to the **Clusters** tab in Console to create a new cluster. - -If you have already created a cluster, select the toggle next to the cluster's name under **Select a development cluster**. - -:::note -A warning message reading `Cluster creation is not available on this modeling plan` means your modeling plan does not permit you to create more clusters. Contact the admin or owner of your organization to **upgrade your plan**. - -Alternatively, `Missing permissions` means you may not have the proper permissions to create a cluster. Contact your organization's admin to **create a cluster**. -::: - -### Main process - -The new process application will contain an empty BPMN diagram with the same name as the process application itself, labeled as the main process. You can rename the main process diagram any time. - -:::note -A process application must always have a main process. -That is why the main process diagram cannot be deleted or moved out of the process application. -However, you can assign another BPMN diagram as the new main process with the **Reassign main process** option in the -diagram's action menu: - -Reassign the main process -::: - -### Add files to a process application - -Add more files to the process application via the **Create new** dropdown on the process application page, drag and drop -from your local computer, or move from a different location in the Web Modeler. - -To make it easily discoverable, the main process will always be displayed at the top of the file list, regardless of the sort order. +For example, a process application for a consumer loan application might consist of a main process BPMN diagram and a number of additional supporting files, such as DMN diagrams and forms.

Process application file list

-:::note -Within the same process application, process IDs, decision IDs, and form IDs must be unique across all files. -This is to avoid ambiguity and conflicts when you link resources and deploy the process application later on. -::: - -## Deploy and run a process application - -### Deploy a process application - -Open the process application's [main process](#main-process) and use the **Deploy** button to deploy the process application to a Zeebe cluster. - -

Deploy a process application

- -All BPMN, DMN, and form files contained in the process application folder will be deployed in a single bundle. - -:::note -If any resource fails to deploy, the whole deployment will [fail](#deployment-errors) and the cluster state will remain unchanged. -This ensures that a process application cannot be deployed incompletely or in an inconsistent state, making it safer to use. +:::tip +We recommend you use a process application for all your non-trivial automation projects. These projects tend to have one main BPMN process that represents your end-to-end use case, and additional files that the main process depends on, such as called supporting processes, DMN decisions, or forms. ::: -### Run a process application - -Open the process application's [main process](#main-process) and use the **Run** button to start a new instance. -Before the actual process instance is started, all resources will be re-deployed if required so the new instance -will always use their latest state. +## Process application development lifecycle -

Run a process application

+You can use Web Modeler to quickly develop and progress low-risk process application releases through the stages of a typical development lifecycle. -After the process instance is started, you will receive a notification with a link to the process instance view in -[Operate](../../operate/operate-introduction.md). -Follow this link to monitor the process instance and interact with it as needed. +- [Process application development lifecycle](process-application-pipeline.md) -:::info -Single-file deployment is not supported in a process application. -If you click the **Deploy** or **Run** button for any diagram other than the main process, you will be asked to open the -main process instead to deploy the whole process application from there. -::: - -### Deployment errors - -If the deployment of a process application fails (for example, because one or more of the contained resources have invalid -implementation properties), a modal containing the error message thrown by the Zeebe engine will be displayed. -The message usually comprises the name of the affected resource, the ID of the invalid diagram element, and the actual error. +## Create a process application -

Process application deployment error

+Get started by creating a new process application. -### Deployment of external resources +- When you [create a process application](create-a-process-application.md), you must select a cluster to use for deployment during development. +- A process application must always have a [main process](/docs/components/modeler/web-modeler/create-a-process-application.md#main-process). You can rename and reassign the main process at any time. +- You can [add files](/docs/components/modeler/web-modeler/create-a-process-application.md#add-files-to-a-process-application) to the process application as required. -You can link BPMN processes, DMN decisions, or forms that are not part of the process application itself (external -resources) from any process inside a process application. +## Deploy and run a process application -Note that when you deploy the process application: +You can deploy your process application to a cluster, and run your process application to test, debug, and observe how it performs in a live environment. -- Linked external forms will be deployed together with the process application. -- Linked external BPMN and DMN diagrams are _not_ deployed together. They must be deployed separately. +- [Deploy and run a process application](deploy-process-application.md) -## Versioning +## Process application versioning Although you cannot version a process application itself, you can use [bulk milestone creation](milestones.md#bulk-milestone-creation) and version tags to save a single 'versioned' snapshot of all the process application files in one action, instead of having to create separate milestones for every file. -When you create a milestone in any process application file, a milestone is also created with the same name (version tag) for all files currently available in the process application. - -This allows you to track a process application through the development lifecycle and ensure the correct version is called. +- [Process application versioning](process-application-versioning.md) -### A worked example +## Known limitations -In this example, you have a process application that contains multiple files as well as the main process. +You should be aware of the following limitations when working with process applications. -- You create a new milestone for the main process and enter "1.2" as the version tag. -- When you create this new milestone, a milestone is also created for every other file and named with the same "1.2" version tag. -- All files in the process application now have a "version 1.2" milestone. - -![Diagram showing an example process application bulk milestone creation](img/process-applications/process-application-milestone-diagram.png) - -### Create a bulk milestone - -To create a bulk milestone for a process application: - -1. Open any file in a process application and [create a milestone](milestones.md#create-a-milestone). -1. Enter a **Version tag**. -1. Select **Create** to create the milestone and matching version milestones for every file in the process application. - -![Create a milestone screen](img/milestones/web-modeler-milestone-create-versioned-milestone-highlight.png) - -Now when you open the milestone history for any file in the process application, you can use the file navigation header buttons to switch between files, and view their individual milestone history. - -![Milestone history with file navigation header buttons highlighted](img/milestones/web-modeler-milestone-compare-process-application-files-highlight.png) - -:::note - -When naming your milestone with a version tag, you cannot edit or delete the created versions. - -::: +### General limitations -## Limitations +- You cannot create folders inside a process application folder. +- Once created, you cannot modify, delete, or roll back a process application version. +- Self-Managed does not support defining cluster stages, identifying clusters by tags, or cluster promotion. -Be aware of the following limitations when working with process applications: +### Deployment limitations -- You cannot create subfolders inside a process application. - Process applications can only be deployed to a Zeebe cluster in version 8.4.0 or higher. -- It is not possible to deploy individual files that are part of a process application; the application will always be deployed as a whole. -- When you deploy a process application, only the main process is checked for missing [Connector secrets](../../console/manage-clusters/manage-secrets.md). +- You cannot deploy individual files that are part of a process application; the application is always deployed as a whole. +- When you deploy a process application, only the main process is validated for missing [Connector secrets](../../console/manage-clusters/manage-secrets.md). - The overall size of the deployment bundle is limited due to a maximum [record](../../zeebe/technical-concepts/internal-processing.md) size of 4 MB in Zeebe. - Effectively, the limit is between 2 and 3 MB as Zeebe writes more data to the log stream than just the raw deployment. - - If you exceed the limit, you are shown the following [error message](#deployment-errors): - `Command 'CREATE' rejected with code 'EXCEEDED_BATCH_RECORD_SIZE'` + - The limit is effectively between 2 and 3 MB, as Zeebe writes more data to the log stream than just the raw deployment. + - If you exceed the limit, you are shown an [error message](deploy-process-application.md#deployment-errors):
+ `Command 'CREATE' rejected with code 'EXCEEDED_BATCH_RECORD_SIZE'`. diff --git a/docs/guides/devops-lifecycle/integrate-web-modeler-in-ci-cd.md b/docs/guides/devops-lifecycle/integrate-web-modeler-in-ci-cd.md index 6ececf915e..af37123b3c 100644 --- a/docs/guides/devops-lifecycle/integrate-web-modeler-in-ci-cd.md +++ b/docs/guides/devops-lifecycle/integrate-web-modeler-in-ci-cd.md @@ -16,6 +16,10 @@ import TabItem from "@theme/TabItem"; [Web Modeler](../../components/modeler/about-modeler.md) serves as a powerful tool for the development and deployment of processes and process applications. While Web Modeler simplifies one-click deployment for development, professional teams often rely on continuous integration and continuous deployment (CI/CD) pipelines for automated production deployments. The [Web Modeler API](/apis-tools/web-modeler-api/index.md) facilitates integration of Web Modeler into these pipelines, aligning with team practices and organizational process governance. +- For low-risk processes, you can use the Web Modeler [process application development pipeline](/docs/components/modeler/web-modeler/process-application-pipeline.md) to quickly develop and progress process application releases through the stages of a standard development lifecycle. [Milestone comparison](/docs/components/modeler/web-modeler/milestones.md#compare-milestones) (Visual and XML diffing) and [Git Sync](/docs/components/modeler/web-modeler/git-sync.md) provide a powerful combination for collaboration between team members using both Web and Desktop Modeler. + +- For business-critical and higher-risk processes that require strict governance and/or quality requirements, you can integrate Web Modeler into your CI/CD pipelines. + Continuous integration and deployment are pivotal for rapid and reliable software development, testing, and delivery. These practices automate the building, testing, and deployment processes, leading to shorter development cycles, enhanced collaboration, and higher-quality releases. Integrating Web Modeler into your CI/CD pipelines can significantly enhance process application development and deployment workflows. By automating process application deployment, changes can be promptly and accurately reflected in the production environment. This agility empowers teams to swiftly respond to evolving business needs, fostering a flexible and adaptable process orchestration approach. diff --git a/sidebars.js b/sidebars.js index aa57921929..09f435759b 100644 --- a/sidebars.js +++ b/sidebars.js @@ -153,8 +153,20 @@ module.exports = { "components/modeler/web-modeler/import-diagram", "components/modeler/web-modeler/fix-problems-in-your-diagram", "components/modeler/web-modeler/run-or-publish-your-process", - "components/modeler/web-modeler/process-applications", - "components/modeler/web-modeler/camunda-marketplace", + { + type: "category", + label: "Process applications", + link: { + type: "doc", + id: "components/modeler/web-modeler/process-applications", + }, + items: [ + "components/modeler/web-modeler/process-application-pipeline", + "components/modeler/web-modeler/create-a-process-application", + "components/modeler/web-modeler/deploy-process-application", + "components/modeler/web-modeler/process-application-versioning", + ], + }, { Collaboration: [ "components/modeler/web-modeler/collaboration", @@ -164,6 +176,7 @@ module.exports = { "components/modeler/web-modeler/play-your-process", ], }, + "components/modeler/web-modeler/camunda-marketplace", "components/modeler/web-modeler/milestones", "components/modeler/web-modeler/token-simulation", {