Diagram information in technical model
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2011 04:29 PM
When generating technical BPMN model from Signavio Json, class called RemedyTemporarySignavioIncompatibility (nice name btw ) is removing all DI information - line 41.
Is it still needed? I think it would be good to have DI information in developer friendly version - especially now, as one can import it to Designer, or display in Modeler.
Is it still needed? I think it would be good to have DI information in developer friendly version - especially now, as one can import it to Designer, or display in Modeler.
Labels:
- Labels:
-
Archive
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2011 09:37 AM
Hi mproch.
True, and we already have an issue for it 🙂 It should be in 5.2.
The problem is, if we keep it, we have to adjust the ID's according to the changed ID's in the XML. But since we now can open the BPMN XML correctly in the Eclipse Designer, maybe we remove the RemedyTemporarySignavioIncompatibility completely, since developer friendliness is less an issue then.
But we have a con call tomorrow where we discuss this bigger picture and I am confident, some solution will make it in 5.2…
Cheers
Bernd
True, and we already have an issue for it 🙂 It should be in 5.2.
The problem is, if we keep it, we have to adjust the ID's according to the changed ID's in the XML. But since we now can open the BPMN XML correctly in the Eclipse Designer, maybe we remove the RemedyTemporarySignavioIncompatibility completely, since developer friendliness is less an issue then.
But we have a con call tomorrow where we discuss this bigger picture and I am confident, some solution will make it in 5.2…
Cheers
Bernd
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2011 10:05 AM
Well, removing temporary hacks is alway a Good Thing
But DI generation works ok now - I mean, when you remove this line from RemedyTemporarySignavioIncompatibility. The point is that ids are replaced already on JSON level, so generated bpmn already has adjusted ids - and it just works
maciek
But DI generation works ok now - I mean, when you remove this line from RemedyTemporarySignavioIncompatibility. The point is that ids are replaced already on JSON level, so generated bpmn already has adjusted ids - and it just works
maciek
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2011 10:10 AM
Really? I thought I tested it and it didn't… But it was just in between to other tasks 😉 So then this is a sure shot to be in the 5.2, but removing it completely is still under discussion 🙂
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2011 04:27 AM
Okay, I fixed the last small issues today, now the DI is kept in the Developer Friendly BPMN correctly.