BPMN 2.0 Call Activity link to child diagram lost when using XMI Import Merge

[PWarren]

We are using Call Activities (BPMN 2.0) within our business process diagrams, and then linking them to their relevant diagrams.

We also each have to work locally and then use XMI Export, the XMI Import Merge up to the client's master repository. (I use the Direct merge option as I am the only one currently on the team using ver 13.0 EA.)

After the Import completes the link from the Call Activity to the Child diagram for it, is dropped and has to be added back in manually on the repository copy.

The main reason to use XMI Export/Import is the lack of SVN being deployed and used by the client. The team and I are hoping that will change in the very near future, although I personally feel the client will need to make additional improvements regarding network and DB optimization too.

[Graham_Moir]

Is the global re-usable process (activity/child diagram) being called, stored outside of the project browser package/folder structure  that you are exporting?   If so that could be the reason it gets dropped. 

[PWarren]

No, it is part of the same package/folder structure.

[Graham_Moir]

OK, have you logged an official bug report/support issue?

[PWarren]

No, what is the procedure for completing that?

[qwerty]

Use the link bottom right of this very page.

q.

[PWarren]

Is the global re-usable process (activity/child diagram) being called, stored outside of the project browser package/folder structure  that you are exporting?   If so that could be the reason it gets dropped.

I was hoping you could elaborate on this a bit more, as you may have identified one cause of our broken link to Call Activity issues.

If we identify an activity or sub process as a candidate to become a Call Activity (global re-usable process), what is the correct usage if it is needed by another higher/lower level process branch?

For example, B.1.1.3.9 is the parent process and contains and uses Call Activity B.1.1.3.9.1. As modeling progresses into other branches, we discover the same Call Activity can be used by parent processes B.1.2.4 and B.1.3.1.1.4.

[PWarren]

Use the link bottom right of this very page.

q.

Thanks! Going to wait for reply on my last more detailed question, just to make sure this issue is not self-inflicted due to incorrect usage of Call Activities.