Hi @ceefour and @aravindhrs,
Being the product manager for both Cawemo and the Modeler, it was a pleasure to read this thread and how you helped each other. I couldn’t have described this better.
What I would add on top: what we have seen our customers doing is that they have the technical models as part of their source code repositories like git. This way, all technical people can collaborate and keep the models in sync with other source code that implements the individual tasks. Since many teams work with feature branches in such a setup, a live sync of process diagrams among several developers would not work in these scenarios. Therefore, we will always see the Camunda Modeler as the main tool for adding the technical execution details.
That said, we want to enable all stakeholders to at least be able to see how the process models evolve during the technical phase. This can be done using the already mentioned integrations between Cawemo and the Modeler or Camunda Engine. What we have added in the recent months are further details (basically all technical properties, like the external task topic, that you can edit in the Modeler) in the visual diffing mode that were not yet available in the demo video from the past CamundaCon:
Regarding our roadmap: while we do not have bigger topics like editing the execution details directly within Cawemo on our near-term roadmap, we still have these topics in the back of our mind and are regularly considering to invest in such topics.
If you have any further questions, please don’t hesitate to let us know.
Best,
Volker