Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Old bpmn files cannot be opened in newer Modelers

See original GitHub issue

Describe the Bug

We have a bpmn file that was created with Modeler version 2.2.4 and then uploaded to Cawemo. In Cawemo the diagram cannot be opened. When opening the file in Modeler versions 3.2.0 and newer, the file cannot be rendered and the following log is shown:

[/Users/XXXX/Downloads/XXXX.bpmn] no diagram to display
    at Object.handleDefinitions (webpack:///node_modules/bpmn-js/lib/import/BpmnTreeWalker.js:173:0)
    at file:///Volumes/Camunda%20Modeler%203.2.0/Camunda%20Modeler.app/Contents/Resources/app.asar/public/6.6.js:1:392700
    at file:///Volumes/Camunda%20Modeler%203.2.0/Camunda%20Modeler.app/Contents/Resources/app.asar/public/6.6.js:1:392723
    at this (webpack:///node_modules/bpmn-js/lib/Viewer.js:311:26)
    at open (webpack:///node_modules/bpmn-js/lib/Viewer.js:256:0)
    at file:///Volumes/Camunda%20Modeler%203.2.0/Camunda%20Modeler.app/Contents/Resources/app.asar/public/6.6.js:1:391731
    at file:///Volumes/Camunda%20Modeler%203.2.0/Camunda%20Modeler.app/Contents/Resources/app.asar/public/0.0.js:1:373393 [ error ]
This error may be the result of a plug-in compatibility issue. [ info ]
Disable plug-ins (restarts the app) [ info ]

Expected Behavior

We show the illegal id warning (hidden right now)
We show the error (diagram cannot be found)

Current workaround

Change the ‘id’ attribute of the bpmn:definitions tag such that it does not start with a number and the diagram is rendered properly.

Environment

OS: MacOS (but not relevant, same issue in Cawemo)
Camunda Modeler Version: 3.2.0 and newer

sample-broken-file.bpmn.txt

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

nikkucommented, Oct 7, 2019

My few cents from the 🛋️:

Why does it not throw the original error (“'illegal ID …”)?

This is a bug we should fix.

Do we want to permit this for old diagrams that worked in older versions? Why wanted to have this validation in the first place?

We want people to migrate their diagrams. These diagrams are broken, as they contain invalid IDs in the XML. Note that such IDs have been created in very rare cases, only. We do not want old diagrams to be magically opened.

0reactions

nikkucommented, Dec 12, 2019

We’ve decided that we will improve the situation in the following way: