topic Re: CallActivity : Modeler does not add omgdc:Bounds in Alfresco Archive

CallActivity : Modeler does not add omgdc:Bounds

anuppc72 — Mon, 25 Jul 2011 13:50:59 GMT

Hi,The Call Activity does not add omgdc:Bounds tag in the bpmn20.xmlWhat is generated is : <bpmndi:BPMNShape bpmnElement="callactivity1" id="BPMNShape_callactivity1"> </bpmndi:BPMNShape>and what is expected is : <bpmndi:BPMNShape bpmnElement="callactivity1" id="BPMNShape_cal

Re: CallActivity : Modeler does not add omgdc:Bounds

trademak — Mon, 25 Jul 2011 14:00:39 GMT

Hi,

Could be a bug. I tried to reproduce it, but it generates the DI information fine here.
Is it possible to share your diagram?

Best regards,

Re: CallActivity : Modeler does not add omgdc:Bounds

anuppc72 — Mon, 25 Jul 2011 14:16:11 GMT

Hi,

The main process is ChangeRequest and the other 2 are used in the callactivity. Hope this helps.

Thanks
Anup

Re: CallActivity : Modeler does not add omgdc:Bounds

trademak — Mon, 25 Jul 2011 15:29:45 GMT

Hi Anup,

The problems was that there were two call activities that didn't appear in the diagram, but where still part of the object tree.
I've committed a fix to trunk that prevents the BPMN XML export of elements that don't have any sequence flow attached to them.
That also solves your problem.

Best regards,

Re: CallActivity : Modeler does not add omgdc:Bounds

anuppc72 — Tue, 26 Jul 2011 05:48:11 GMT

Thanks. However i think there is some other related issue in terms of delete (My guess). These 2 dangling callactivity definitions were leftover by some incomplete deletes?? Bcoz i haven't modified the XML directly i have used the palette to drag and drop shapes. I had these callactivities within my main process then possibly i deleted them to recreate them within a in-line subprocess. So perhaps there is a delete related bug perhaps?

-Anup

Re: CallActivity : Modeler does not add omgdc:Bounds

trademak — Tue, 26 Jul 2011 07:42:19 GMT

Yes you're right. It's however not easy to reproduce this.
I didn't encounter it yet. So if you see a pattern in how this delete bug can be reproduced, please let me know.

Best regards,