Boundary message event isn't exported

[milioliluca]

Goodmorning

I have a problem wih boundary message event and its exportation to a file.
More precisely, If I drag and drop the boundary message event into a receive task directly from the palette, and I try to export the diagram, the boundary event is not exported. Please note that the boundary message is dropped when the receive task boundaries become green and after that I set a message reference to the boundary event (message is defined using "Message definition" filed of the process in the gui).
Insted, if I drag and drop the boundary message event in the diagram area,  then I set the message reference, and after that I drag and drop the boundary event into the receive task, then the diagram is exported correctly.
The diagram is also exported correctly If I drag and drop the boundary message event into receive task, and after I move the boundary message event mantaining it into the receive task.
I try to do this with 5.18 and 5.19 versions.

Is it a bug or a my error to use the explorer ?

Thanks

[jbarrez]

It seems to be a bug, I could also reproduce it … but no idea what is causing that … must be something low-level in the Oryx code.

[milioliluca]

I try to debug code when I drag and drop a boundary message event into a receive task.
The crux methods are in stencil-controller.js (dropCallback, overCallback, outCallback, startDragCallback and so on)… In this methods there are some calls to KISBPM and oryx-debug and when the execution in stencil-controller.js finishes, the flow returns to angular-dragdrop.
I don't know why if I drag and drop for the first time a boundary event in the draw canvas this methods are called, but if I move later that boundary event those methods won't call (the dropCallback method is called when I release the boundary event in a task).
The result is that described by me in the first post: when the boundary event is drag and dropped for the first time, it isn't exported, but If I interact again with it, the exportation is correctly performed.
I try to analyze the HTTP responses to get JSON about the process, see the attachements.
The correct json file contains the response of the model which successfully exported. There are some differences, but , in my opinion the most important is the presence of the outgoing resource id of the boundary event in the childshapes of the receive task

Thanks

[erikwinlof]

Hi, yes the problem is basically what you said. The logic in the initial drop (from angular to oryx) isn't handling the drop correctly and adds the boundary event as a child shape to the activity instead of as a sibling which is the correct way. The code that handles further drag n drops of the boundary event handles this correctly though.

A PR has been been created for this currently waiting to be merged https://github.com/Activiti/Activiti/pull/757

[milioliluca]

Hi, I tried to merge the changes reported to the link https://github.com/erikwinlof/Activiti/commit/b6d71b4f8c8d28727530e99181a84ada4bfe57ea
It works very well now.
Thank you for the support.

[erikwinlof]

Great! Glad I could help.

Cheers, Erik

[jbarrez]

Merged to master