How to switch to Camunda Cloud after accidentally starting with Camunda Platform #2283
Labels
backlog
Queued in backlog
Camunda 8
Flags an issue as related to Camunda 8
enhancement
New feature or request
ux
Is your feature request related to a problem? Please describe.
During a customer demo, I already had some (Camunda Cloud) BPMN files open used the '+' button to quickly create another model for a fast sketch. As we continued the discussion, we needed technical attributes and noticed only after a while that the model was using Camunda Platform.
Describe the solution you'd like
I can easily switch the target platform. I don't need technical attributes to be converted. They should actually stay in the model to allow execution in both engines.
Alternative solutions:
Describe alternatives you've considered
I tried to quickly create a new Camunda Cloud model, but copy & paste between the models did not work. See #2124
I could have started editing the XML by hand, but that would have looked really unprofessional and potentially even scary to the prospect.
My sed script that I sometimes use to "convert" existing Zeebe Modeler files, is also far from presentable and requires completely closing and opening the model again as described in #2279
The above sed script even failed, because there where already Camunda Platform attributes in the header:
modeler:executionPlatform="Camunda Platform" modeler:executionPlatformVersion="7.15.0"
So back to XML editing... (yes, I could improve my sed script, but that's still difficult to sell to prospects)
Additional context
Execution Platform: Camunda Cloud
Tested in Camunda Modeler 4.9-nightly.20210520 on Kubuntu 20.04.2 LTS
The text was updated successfully, but these errors were encountered: