In Progress

Non-persistent Message flow connector

A messageflow connector connects two lanes.

When opening the BPM file, the message flow connector is not connected anymore. (see attached Situation 1,2 and 3). After re-connecting, the validation says everything is fine. See Situation 4.

The BPM is saved.

After reopening the BPM the non-connection starts again (Situation 1). This issue can be repeated.

I attach the Situation pictures and the BPM to test.

What to do ....?

The version we work with is 3.1.0.011, 64bits.

Comments (3)

photo
1

Dear Carel,

We were able to reproduce it. We have escalated it to our product team. As soon we receive news, we will write back.

Regards

photo
1

Dear Juan, it is now three weeks ago ... still no solution? In the earlier days response with a fix was more quick .... ;-) I hope this issue can still be solved. It bothers us very much, since each time we use the file, the disconnections are there and need to be solved first, before getting an errorless validated model. Thanks!

photo
1

Dear Carel,

We are sorry to mention that this issue will be resolved in a future release. At this moment, our team is working in some features.

Thank you to help us to be better.

Regards