Open lburja opened 5 years ago
I encountered the same issue, which is puzzling. Almost every CMMN diagram is likely to contain edges... so does it mean that nobody is using the export/import feature in the modeler?
I am wondering what people are doing:
As a workaround until this bug is fixed, you can apparently export the entire app from the modeler (as a zip) instead of only the diagram. That works, and preserves all the graphical representation (the zip contains inside the CMMN diagram, but also some other things, so that on import the layout is preserved)
On Wed, Dec 11, 2019 at 8:37 PM Olivier Liechti notifications@github.com wrote:
I encountered the same issue, which is puzzling. Almost every CMMN diagram is likely to contain edges... so does it mean that nobody is using the export/import feature in the modeler?
I am wondering what people are doing:
- deploying CMMN models directly from the modeler and never generating xml files?
- using the commercial version?
- not using CMMN at all?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/flowable/flowable-engine/issues/1857?email_source=notifications&email_token=AADQDT5YTERCRAAM7HFJQLTQYE6Q7A5CNFSM4IGNRW42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGUKD7Q#issuecomment-564699646, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQDT5DSJ4ZVWEWZIOAO4TQYE6Q7ANCNFSM4IGNRW4Q .
Cool, I will try that, thanks for the hint.
I have a very basic CMMN diagram, with one Task connected to one Milestone.
Exporting the diagram from the Modeler, and importing it again results in the edge losing its source.
Message in the console:
o.f.c.e.j.c.CmmnJsonConverter : Skipping edge CMMNEdge_sid-9BDC8203-B907-435D-9C12-F16962A0AB63 because source ref is null
I attach the exported diagram:
Test_Case.cmmn.xml.zip