The editor is able to distinguish Zeebe and Camunda diagrams

What should we do?

In order to have a unified modeler, we must find a robust way to tell apart Zeebe and Camunda diagrams. That mechanism SHALL be independent of whether an implementation property/namespace exists on the document.

• Resources (BPMN, DMN, CMMN, Form) contain meta-data about the execution platform and version targeted (i.e. Camunda BPM, v7.15, Camunda Cloud, xxx, Zeebe, v0.21.0)
• The meta-data is read from by the modeler to determine which editing controls to show
• Old diagrams without profile meta-data continue to open and are categorized on a best effort basis (i.e. by examining the used implementation namespaces; we could assume that diagrams with the camunda namespace are likely targeting a current (or previous) version of Camunda BPM. 3️⃣
• The profile meta-data is shown in the UI for a diagram
• Users are able to set the profile explicitly via the Modeler UI. This helps in situations where 3️⃣ does not work and allows users to start modeling without choosing any profile in the first place.

Why should we do it?

This is a core capability needed for a unified Camunda / Zeebe modeler

Things to investigate

• Is there any generic BPMN elements that we can use for storing version information? Or do we have to invent a new XML namespace + extension to do it?

Context child of https://github.com/bpmn-io/internal-docs/issues/216

[pinussilvestrus]

please keep in mind that detection via the namespace may not be enough

Yeah absolutely. I am just playing around with namespace detection due to the fallback scenario

Old diagrams without profile meta-data continue to open and are categorized on a best effort basis (i.e. by examining the used implementation namespaces; we could assume that diagrams with the camunda namespace are likely targeting a current (or previous) version of Camunda BPM. 3️⃣

[pinussilvestrus]

Summary of my work on top of https://github.com/camunda/camunda-modeler/issues/2029#issuecomment-778059880

Pull Request https://github.com/camunda/camunda-modeler/pull/2099

• Make sure we don’t load Camunda specific Deploy & Run on other tabs

https://github.com/camunda/camunda-modeler/compare/2029-distinguish-camunda-and-zeebe-diagrams...2029-cloud-bpmn-tab

• add CloudBpmnTab, incoorporates camunda-bpmn-js CloudModeler
• use camunda-bpmn-js PlatformModeler on existing BpmnTab
• display Zeebe specific Deploy & Run on cloud-bpmn tabs
• start on distinguishing mechanism for Zeebe diagrams (namespace fallback)
  • missing: check for executionPlatform

https://github.com/camunda/camunda-modeler/tree/2029-distinguish-camunda-and-zeebe-diagrams

• Some small fixups to make the CloudBpmnTab running

Let’s sync with @barmac and do the handover once he’s back 👍