I wanted to see the interoperability of Camunda Modeler and Flowable Modeler.
I created a process in Camunda and set an email id for Assignee.
After importing in Flowable Modeler, I dont see the Assignee.
Can someone confirm if both Camunda and Flowable actually use the interoperable BPMN specs?
I had created a defect in github on some sets of bpmn diagram failing in import.
Does that mean only flowable exported processes can be imported back?
Same problem. Assignee or candidate users applied on Flowable Modeller are lost when Flowable’s exported xml is opened in Camunda.
Is this following BPMN specs in the right spirit? Or am I missing something altogether.
Yes the BPMN spec is followed. However, the BPMN spec does not have the concept for assignee, candidate users etc. The BPMN spec also allows for products to provide custom extension elements. The assignee, candidate users are one of those custom extension elements. When you export the XML from the Flowable Modeler you will see those elements under the flowable namespace. When you export them from the Camunda modeler I presume that they are under the camunda namespace (which Flowable does not understand). The opposite will also be valid, when you import a process from Flowable Modeler into Camunda it will lose the custom Flowable data.
Thanks Filip. I m going through the BPMN spec in detail to see if there are implementation differences even for say Script tasks, boundary events, etc.
In my product under development, we are planning to only use the runtime, but wanted to give my customers the ability to model. The short term is to include modeler app. But it needs the IDM app too.
This setup is becoming little heavy and complicated to manage at this moment.
How can i migrate my Camunda model to Flowable model, Is there any tool for the same.
We plan to migrate a Project from Camunda to Flowable. Do we have any reference links for the same
Please suggest.
That would depend on your BPMN xml. Most (if not all) should be importable as it’s all BPMN 2.0 XML (but there are vendor extensions of course). If you can share some samples, we can say more.