AnsweredAssumed Answered

Using getActiveActivityIds() with a parrallel gateway

Question asked by donovanmuller on Jul 4, 2012
Latest reply on Jul 5, 2012 by frederikheremans1
Hi,

I'm experiencing an issue using runtimeService.getActiveActivityIds() on a process that contains a parallel gateway.
The attached screenshot shows my test process.

Basically, I have a receiveTask before the gateway. After starting a process instance, I call getActiveActivityIds() with the process instance id, it returns this receiveTask as expected.
Once I signal (runtimeService.signal() with process instance id) the first receiveTask, it continues into the parallel gateway (where there is a receiveTask on one fork and a scriptTask on the other fork) the scriptTask is executed and the receiveTask waits as expected.
If I now call getActiveActivityIds() with the process instance id, I get a blank list back. I was expecting to get the second waiting receiveTask back.
If I now signal (using the process instance id) the second waiting receiveTask, the process continues as expected.

Why does getActiveActivityIds() not return the second waiting receiveTask when in the parallel gateway?

Thanks

Attachments

Outcomes