Setting local variables in execution which is going to be created next

piyush_kaizen — Sun, 30 Apr 2017 13:59:48 GMT

Consider that there is a " Service task A " which is attached to a parallel gateway then there are two tasks "Service Task B " and "Service task C".I have marked " Service Task B " , "Service task C" and parallel gateway as Asynchronous.Therefore a new execution will be created to execute "Service

Re: Setting local variables in execution which is going to be created next

gdharley — Mon, 01 May 2017 20:40:06 GMT

Not sure I completely understand your scenario, but if you have marked both Service Task B and Service Task C as asynchronous, then the original execution from Service Task A is released as soon as you hit the gateway.

You can prove this by logging the execution ID from each of the service tasks.

As for collecting local variables from each of the branch executions, you can set variables on the process instance which will be child execution agnostic.
I typically use map with the execution id as the key so there is no overlap between the different branches.

Another option for somethign ilke this is to use a multi instance loop.

Perhaps I am missing what you are trying to do, perhaps a more specific example.

Greg

‌

topic Re: Setting local variables in execution which is going to be created next in Alfresco Forum

Setting local variables in execution which is going to be created next

Re: Setting local variables in execution which is going to be created next