topic ex-gateway incorrect behaviour in Alfresco Archive

ex-gateway incorrect behaviour

jrcamenzuli — Tue, 28 May 2013 06:20:10 GMT

Unfortunately I can't upload a diagram picture here so I'll have to explain my problem.A start event is connected to a timer and a user-task. Both the timer and the user-task are connected to an exclusive gateway. The exclusive gateway is connected to an end event too.My understanding is that the ex

Re: ex-gateway incorrect behaviour

jbarrez — Wed, 29 May 2013 08:14:19 GMT

If you have two outgoing sequential flows to the timer and the user task, you've effectively creating TWO parallel executions in the process instance. The exclusive gateway does not merge any parallel paths, that's what other gateways are for.

When the execution arrives in the exclusive gateway, it will just make that execution pass through the right outgoing flow.

Re: ex-gateway incorrect behaviour

cbs-johnny — Thu, 30 May 2013 00:53:32 GMT

Hi jbarrez,
I'm the same guy as the OP.

Thank you, that answers my question. Anyway I don't think I explained the diagram properly so for the record here is the diagram picture:
http://i27.photobucket.com/albums/c153/wasssup1990/model.png

My boss thought that only one 'done' user task would be created. In fact there are two that are created. We wanted the timer task to stop if the 'user task' completed before the timer expired. Clearly this doesn't happen - it just keeps running and creates another 'done' task after it expires.

Thanks again,
Johnny

Re: ex-gateway incorrect behaviour

jbarrez — Fri, 31 May 2013 12:06:01 GMT

What you actually want is a usertask + a timer on the boundary to get the behaviour you want.

Note that you can group stuff together in a subprocess and put a timer on that subprocess in a similar fashion.

PS: love your avatar. For some reason, I never though anybody would ever choose a chicken as avatar on a BPM forum 😉

Re: ex-gateway incorrect behaviour

cbs-johnny — Mon, 03 Jun 2013 23:55:05 GMT

Yep, we were figured out that we needed a timer boundary event on the user-task. The ability to put a timer boundary event on a sub-process is something that I haven't tried until now. Thanks for mentioning it.

P.S. I thought a chicken avatar would be funny. *lol*