topic Re: Inclusive gateway forking fails? in Alfresco Archive

Inclusive gateway forking fails?

ollih — Mon, 16 Apr 2012 12:25:30 GMT

Hi!I'm new here and also quite new with BPMN. I noticed behaviour with OR GW, which I think is strange. The inclusive gateway in this process fails to fork, when a user completes the Engineering task one the second time:[img]http://i1156.photobucket.com/albums/p567/ollih1/OR-GWsimpletestFAILING.jpg[

Re: Inclusive gateway forking fails?

trademak — Tue, 17 Apr 2012 13:28:52 GMT

Hi,

Interesting. The problem is that the inclusive gateway checks if there is any execution active that can lead to the inclusive gateway as input.
If this is the case then it waits until this is execution is either completed or entered the inclusive gateway.
In your example the "Sales task two" task can lead to the inclusive gateway via the "Sales task three" task and therefore it waits for that execution.
So when you remove the sequence flow from "Sales task three" to "Engineering task one" this doesn't occur anymore.

Best regards,

Re: Inclusive gateway forking fails?

ollih — Wed, 18 Apr 2012 07:36:17 GMT

Thanks, Tijs!

You provided a very reasonable explanation for the behaviour!

But I wonder if that behaviour is acceptable.

According to the documentation http://www.activiti.org/userguide/index.html#bpmnInclusiveGateway

all concurrent executions arriving at the inclusive gateway wait in the gateway until an execution has arrived for each of the incoming sequence flows that have a process token.

In my diagram there is only one concurrent execution arriving for the only one incoming sequence flow for the OR GW. Shouldn't the GW fire immediately when the flow contains a token? Now the GW seems to freeze waiting for also possibly in the future materializing tokens (which actually can never occur).

Do you think that the OR GW works according to the Activiti documentation and BPMN 2.0 specification? Or is there a bug in the gateway?