cancel
Showing results for 
Search instead for 
Did you mean: 

Visual Designer kills bpmn20.xml

frecklefoot
Champ in-the-making
Champ in-the-making
I found this thread: http://forums.activiti.org/en/viewtopic.php?f=8&t=2254, but it doesn't directly address my question. I have a process that I sketched out in the designer: the .activiti file. Then I went in and added some custom logic: the operation of a gateway, some formProperties, etc. Stuff I couldn't see an easy way of doing in the visual editor. Tested it out, it worked fine.

Then I went back to the .activiti file, made a small change, saved it and *BAM* all the logic in the bpm20.xml file was overwritten (it's okay, I had backups). Apart from adding all that custom code back in by hand, I don't any way around this. Is this a known/expected feature of Designer? That it blows away all modifications made by hand in the xml file? I haven't tried it, but I suspect the Modeler does the same thing. Our organization has workflows that are expected to change fairly frequently, and I don't see them relishing the task of merging back in logic after using the visual Designer or Modeler.
1 REPLY 1

tiesebarrell
Champ in-the-making
Champ in-the-making
Yes, this is a feature of Designer, that's documented here:

http://docs.codehaus.org/display/ACT/Designer+FAQ

If you want to re-apply additions, the most straightforward way is probably to create an XSLT that you can re-use to add your changes after updates.