topic Re: Inklusive Gateway after JavaScript Task in Alfresco Archive

Inklusive Gateway after JavaScript Task

tc1 — Mon, 08 Dec 2014 13:23:58 GMT

Hello everybody,I'm new in BPMN and I try to build a model with a JavaScript Task and a gateway behind. The ScriptTask should only declare a variable like "var MeaningOfLife = "42";But how can I write a flow condition to evaluate that? I tried something like "${MeaningOfLife="42"}" or "${MeaningOfLi

Re: Inklusive Gateway after JavaScript Task

martin_grofcik — Tue, 09 Dec 2014 07:33:22 GMT

Hi Thomas,

did you check whether variable is set after scriptTask execution?


activiti:autoStoreVariables="false"

Regards
Martin

Re: Inklusive Gateway after JavaScript Task

tc1 — Tue, 09 Dec 2014 09:34:45 GMT

Hi Martin,

thanks for your fast answer!
First of all, I wrote accidentally "inklusive". It's an "exklusive" gateway.

Yout hint about the autoStoreVariables brought me to this page:
http://www.jorambarrez.be/blog/2013/03/25/bug-on-jdk-1-7-0_17-when-using-scripttask-in-activiti/

I edited my javascript code to:
<code>
var MeaningOfLife = "42";
execution.setVariable("MeaningOfLife", MeaningOfLife );
</code>

The JUnit test is now running without any errors, but the flow condition ${MeaningOfLife=="42"} is never true. Why?

<code>
<process id="testScriptTask" name="Testprocess with Script Task" isExecutable="true" activiti:candidateStarterUsers="Sales">
    <startEvent id="startevent1" name="Start"></startEvent>
    <sequenceFlow id="flow1" sourceRef="startevent1" targetRef="scripttask1"></sequenceFlow>
    <scriptTask id="scripttask1" name="Execute JavaScript" scriptFormat="javascript" activiti:resultVariable="MeaningOfLife" activiti:autoStoreVariables="false">
      <script>var MeaningOfLife = "42";
execution.setVariable("MeaningOfLife ", MeaningOfLife );</script>
    </scriptTask>
    <exclusiveGateway id="exclusivegateway1" name="Exclusive Gateway"></exclusiveGateway>
    <sequenceFlow id="flow2" sourceRef="scripttask1" targetRef="exclusivegateway1"></sequenceFlow>
    <exclusiveGateway id="exclusivegateway2" name="Exclusive Gateway"></exclusiveGateway>
    <endEvent id="endevent1" name="End"></endEvent>
    <sequenceFlow id="flow6" sourceRef="exclusivegateway2" targetRef="endevent1"></sequenceFlow>
    <sequenceFlow id="flow7" name="MeaningOfLife=="42"" sourceRef="exclusivegateway1" targetRef="scripttask4">
      <conditionExpression xsi:type="tFormalExpression"><![CDATA[${MeaningOfLife=="42"}]]></conditionExpression>
    </sequenceFlow>
    <scriptTask id="scripttask4" name="Way 1" scriptFormat="groovy" activiti:autoStoreVariables="false">
      <script>outrintln "Right, the meaning of life is 42";</script>
    </scriptTask>
    <sequenceFlow id="flow8" name="Default Flow" sourceRef="exclusivegateway1" targetRef="scripttask5"></sequenceFlow>
    <scriptTask id="scripttask5" name="Way 2" scriptFormat="groovy" activiti:autoStoreVariables="false">
      <script>outrintln "Wrong, meaning of life should be 42";</script>
    </scriptTask>
    <sequenceFlow id="flow9" sourceRef="scripttask4" targetRef="exclusivegateway2"></sequenceFlow>
    <sequenceFlow id="flow10" sourceRef="scripttask5" targetRef="exclusivegateway2"></sequenceFlow>
</process>
</code>

Regards,
Thomas

Here is a screenshot of the conditions:
http://i.imgur.com/goa8bbb.png

Re: Inklusive Gateway after JavaScript Task

martin_grofcik — Wed, 10 Dec 2014 07:25:41 GMT

Hi Thomas

there are 2 issues

there is additional space in execution.setVariable("MeaningOfLife ", MeaningOfLife );
scriptTask stores the result in MeaningOfLife variable. This viariable is initialized twice (in script and as a result of the script execution (which is void - unrecognized variable type)

Solution:
use following code in your scriptTask:


  <scriptTask id="scripttask1" name="Execute JavaScript" scriptFormat="javascript"
        activiti:resultVariable="MeaningOfLife" activiti:autoStoreVariables="false">
   <script>"42"</script>
  </scriptTask>

Regards
Martin

Re: Inklusive Gateway after JavaScript Task

tc1 — Wed, 10 Dec 2014 07:37:12 GMT

Hi Martin!

Thanks! Works great!

Regards,
Thomas