Decide on the shared clipboard

[barmac]

What should we do?

In Camunda Modeler, the clipboard is shared between BPMN diagrams. This means that you can copy an element from diagram_1.bpmn and paste it to diagram_2.bpmn.

However, you cannot easily copy an element with Camunda properties to a Zeebe diagram (and Zeebe properties to a Camunda diagram respectively) as this leads to errors. For example, zeebe:FormDefinition does not have any execution meaning within Camunda Workflow Engine. Because of that, we've decided to not include the shared clipboard in #2107.

I can see three different options how to solve this problem:

• disable shared clipboard (as in Distinguish camunda and zeebe diagrams #2107)
• allow to copy and paste elements but ignore process engine-specific properties (this requires additional work)
• try to convert the elements (rather infeasible)

Why should we do it?

Let's make an informed decision to replace the temporary solution or leave it as it is.

[nikku]

I personally favor option two. The other options look rather odd.

Could you elaborate how that causes errors / harm? Would love to get a better understanding.

[barmac]

The element is not pasted and en error is logged:

[diagram_1.bpmn] unknown type <zeebe:FormDefinition>
    at Registry.mapTypes (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:525:11)
    at Registry.getEffectiveDescriptor (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:550:8)
    at BpmnModdle.Moddle.getType (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:775:32)
    at BpmnModdle.Moddle.create (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:743:19)
    at BpmnFactory.create (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/modeling/BpmnFactory.js:68:29)
    at ModdleCopy.copyProperty (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/copy-paste/ModdleCopy.js:241:40)
    at eval (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/copy-paste/ModdleCopy.js:222:29)
    at eval (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:221:14)
    at forEach (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:181:16)
    at reduce (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:220:3) [ error ]
This error may be the result of a plug-in compatibility issue. [ info ]
Disable plug-ins (restarts the app) [ info ]
unknown type <zeebe:FormDefinition>
    at Registry.mapTypes (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:525:11)
    at Registry.getEffectiveDescriptor (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:550:8)
    at BpmnModdle.Moddle.getType (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:775:32)
    at BpmnModdle.Moddle.create (webpack-internal:///../../camunda-bpmn-js/node_modules/moddle/dist/index.esm.js:743:19)
    at BpmnFactory.create (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/modeling/BpmnFactory.js:68:29)
    at ModdleCopy.copyProperty (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/copy-paste/ModdleCopy.js:241:40)
    at eval (webpack-internal:///../../camunda-bpmn-js/node_modules/bpmn-js/lib/features/copy-paste/ModdleCopy.js:222:29)
    at eval (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:221:14)
    at forEach (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:181:16)
    at reduce (webpack-internal:///../../camunda-bpmn-js/node_modules/min-dash/dist/index.esm.js:220:3) [ error ]
This error may be the result of a plug-in compatibility issue. [ info ]
Disable plug-ins (restarts the app) [ info ]

[nikku]

Pretty cool. This means the only thing we need is to check whether we "know such elements" and ignore them during pasting all together?

[barmac]

That's what I would test first. So sth like:

if (!moddle.canCreate(propertyOrElement)) {
  return false;
}

[falko]

This could have been a workaround for #2283