bmpn20.xml does not sync with .acitiviti files properly

[ruedesilva]

Hi,

In the latest 5.7.1 designer when you open an .xml file the .activiti file that gets generated automatically is not synced properly. Form parameters, documentation elements etc are missing in the Activiti diagram. Then when you save the Activiti diagram the .xml file is overwritten and all the Form params, documentation etc are gone. This was not the case previously as there used to be a 'design' and 'src' tabs instead of having to open the diagram and .xml files separately. Also if you modify the .xml file the changes are not reflected in the Acitiviti diagram - which was not the behaviour before. So now it has become very difficult to maintain complex WFs.

Is this the normal behaviour now? Seems like some bug? It should work as prior to 5.7.1 no matter where you make a change both should be synched.

thanks,
Rue

[lisama]

Thank you for the prompt answer Tiese. Is there already a release date set for the new designer version with the included bugfixes?

[tiesebarrell]

LisaMa,

sorry, but I don't understand your question. Which bugfixes are you referring to? The workaround I suggested is something you would implement yourself and isn't planned for Designer itself. Could you clarify?

[lisama]

I was refering to the bugfixes mentioned my Tijs at the start of the topic. Sorry for that making that clearer

[trademak]

Hi,

I took a new look at the XML syncing issue and came to the conclusion that we should support this.
I've committed some code changes to make this work again.
It now syncs the basic stuff for the most tasks including multi instance, activiti listeners and field extensions.
Can you let me know what kind of functionality you would like in the XML sync in addition, if any?

Best regards,

[ronald_van_kuij]

so there is a dual editor again? Certainly have to check the source out then.

[lisama]

Wow you guys are awesome for adding more sync features, can't wait for the new Designer.

Not really part of the sync mechanism, but if I could wish for something it would be some kind of dummy element for the palette. So that if you import something from Modeler or edit the xml file by hand, for example adding an element which is not yet supported by the Designer, it will be replaced with the dummy element. The diagram would still exist and could be worked with and there would be one less error message to get headaches about 

[trademak]

Hi Ronald,

Yes it's a dual editor, but not a multipage editor.
So you can edit the model file which is synced to the XML file and vice versa in separate editor pages.

Best regards,

[trademak]

Hi,

Could you explain in which cases you had a need for the dummy element?

Best regards,

[lisama]

For example the send and receive tasks from Modeler.

[trademak]

Hi,

Okay right. We can easily solve this by using dummy manual tasks for these elements.
Let me know if you can think of more items.

Best regards,