AnsweredAssumed Answered

Possible bug - activiti:resultVariable vs activiti:resultVariableName

Question asked by jader on Jan 18, 2016
Latest reply on Feb 5, 2016 by trademak
Hello,

I'm experimenting with Activiti connected to java EE (on glassfish). I manage to sucessfully  execute bean by serviceTask and activiti:expression, but I had a problem with returning value. I created my bpmn with designer, and got this:

<serviceTask id="correction" name="to correction"
   activiti:expression="#{stepService.invoke('MARK_TO_CORRECTION')}"
   activiti:resultVariableName="stepResult">
</serviceTask>

Later I check variable stepResult in exclusive gateway and it is created but always is null. Funny thing is, that it starts working when I mannualy change resultVariableName to resultVariable:

<serviceTask id="correction" name="to correction"
   activiti:expression="#{stepService.invoke('MARK_TO_CORRECTION')}"
   activiti:resultVariable="stepResult">
</serviceTask>

Is it a bug, or should/can I configure something, somewhere?

Outcomes