Hi,
occasionally, we have quite large bpmn diagrams, that use nested subprocesses.
Currently, we are using signavio for modeling those diagrams, where each collapsed subprocess is an own process definition, modeled in a separate file.
Now, we are evaluating camunda Modeler, for modeling those larger diagrams and export them to signavio afterwards.
We need to use collapsed subprocesses, call activites are no option.
In order to evaluate camunda Modeler, I re-modeled the original diagram in camunda Modeler (see attached file).
When I open the file in camunda Modeler Version 1.12.0, I’m facing the following issues:
when I change the type of a collapsed subprocess to expanded (“Change type” and then select “Sub Process (expanded)”), change the content of the subprocess and change the type of the sub process back to collapsed (“Change type” and then select “Sub Process (collapsed)”), the layout of the main model, containing the sub process, is somehow changed.
on uncollapsing a subprocess, the elements of the main process are greyed out, which is good, but some elements are not, which is confusing.
Can you reproduce my issues?
Do you have any idea, how to work around them?
Thanks a lot,
Georg
One problem with Signavio is that it doesn’t regard subprocesses being part of the main process. So you can export a nested process and import it to camunda which works fine (except for the layout problems reported above). But when you alter the model in camunda modeler and save it, you can only re-import it to Signavio as a completely new model. It won’t update the old Signavio models (for Signavio there are multiple models) to a new revision. I assume, this cannot be solved by the camunda folks but needs to be done a few blocks away.
Are there plans to develop any option to display nested subprocesses in a more transparent way?
For instance: When expanding a collapsed sp, the main process becomes invisible, and is visible again, when the sp is collapsed.
I appreciate that you guys don’t want to save the sp in a different entity, because it would be in conflict with the bpmn specs. Just a solution in terms of displaying it in the modeler would solve the challenge within camunda and there would be no need for working with two systems.
Hi philippfromme,
I checked camunda modeler V 2.2.3 and it looks much better, then initially.
I did 2 checks with the new modeler:
Check 1:
I navigated through various subrocesses of pvcm.bpmn ans occasionally chenged the content of the subprocesses.
Finding:
The position of the tasks stays the same, but still the lines between the tasks (edges) are different from the initial diagram. Furthermore, if I navigate through the sub processes, un-/collapsing them, I never get the initial state. So, I have to save.
Check 2:
I exported the original executable process from signavio, that pvcm.bpmn is copied from. I opened this process with modeler.
Findings:
1.: When I open it, the log shows entries like
Imported BPMN diagram with 10 warnings [warning]
unparsable content detected
line: 28327
column: 12
nested error: duplicate ID [warning]
I checked the originally exported xml-file from siganvio, but it doesn’t have the id’s as duplicates.
Only the modeler has them duplicate, when I open the xml-view of the model.
2.: When I edit the (signavio exported) model (for example in the 3rd hierarchy of submodels), I get an error in the log view:
TypeError: Cannot read property ‘children’ of undefined
at MoveConnectionHandler.execute (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:95197:63)
at file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:84925:31
at CommandStack._atomicDo (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:84888:5)
at CommandStack._internalExecute (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:84919:8)
at CommandStack.execute (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:84675:8)
at Modeling.moveConnection (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:94145:22)
at file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:96444:16
at forEach (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:149378:20)
at MoveHelper.moveClosure (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:96438:24)
at MoveElementsHandler.postExecute (file:///home/groever/temp/camunda-modeler-2.2.3-linux-x64/resources/app.asar/public/index.js:95287:16) [error]
After that error, I can not edit the model anymore. Means, the roundtrip between signavio and camunda is somehow interrupted.
Could you please help with those issues?
Thanks a lot,
Georg
I created a Diagram in signavio, containing a sub process
exported the diagram (name : “Neuer Prozess (Kopie).bpmn”)
opened the diagram in modeler
Edited the subprocess (added a task before task 1) in modeler
Saved as “Neuer Prozess.bpmn”
imported the modified process to signavio
When I open the modified process in signavio
the preview popup of the subprocess is OK
when I open the subprocess, I can not scroll to the upper part of the canvas. Thus the newly added task is not visible.
With more complex hierarchies of subprocesses, I face the same problem, but more severe: The modified subprocess as shown in signavio sometimes collapses to a single point.
The warnings and errors I mentioned in my last post only occured in process descriptions, that are outdated. So this seems to be not relevant.
another example of a process, creaded in signavio, updated in modeler.
If you load it in siganvio again, the model looks somehow strange. Neuer Prozess(1).bpmn (160.5 KB)
On MacOS with Camunda Modeler 2.2.4, the diagrams provided by you open without warnings or errors. Please explain what “looks somehow strange” means for you. A screenshot could be useful.
Hi barmac,
in the meantime, I filed a bug with signavio and signavio version 12.12.2 together with the current camunda modeler (version 2.2.4) are looking much more promising, regardng the “camunda-signavio roundtrip”.
But, there are still 2 issues on the camunda side, that I would like to address:
When opening a process with a collapsed sub process (for example pvcm.bpm), the collapsed subprocess is initially shown like
, but when navigating into the sub process and closing it again, the edges are moved and the bpmn-file needs to be saved ( see finalSubProc in my next post).
when importing the modified process to signavio, the layout in signavio is somehow messed. I opened a bug in signavio (SCS-9483), but they say, the reason is a “different interpretation of the starting point of the drawing area” on camunda side. Could you please get into contact with signavio on the bug
Hi barmac,
I’ve attached a Hauptprozess(2).bpmn (34.0 KB)
with a sub process, where the above mentioned Problem can be reproduced.
The bug is still in camunda modeler 3.0.1 existing.
It should be easily reproducable with this process.
Thanks a lot,
Georg
