topic Re: Element Variable not being assigned to subprocess for MultiInstanceLoop in Alfresco Archive

Element Variable not being assigned to subprocess for MultiInstanceLoop

jorell — Thu, 06 Feb 2014 22:37:38 GMT

I seem to be having a very basic problem. I have the following node in a parent process:<callActivity id="createSubs" name="CreatSubs" activiti:exclusive="false" calledElement="multiInstanceLoopSub"> <extensionElements> <activiti:in source="line_item_id" target="l_i_id"/&g

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jbarrez — Fri, 07 Feb 2014 08:47:52 GMT

A call activity is actually not one execution in the db, but at least two. The element variable is set on the topmost, so it can be found in all the children.

I'm assuming you have an error with this? What doesn't work in this setup?

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jorell — Fri, 07 Feb 2014 22:18:48 GMT

There isn't an error as such. I just cant access the "creative_id" variable in the subprocess delegates. I have this snippet in the first task of the multiInstanceLoopSub process:

<code>
<serviceTask id="taskId" name="Task Name" activiti:class="com.xyz.delegatename" >
      <extensionElements>
       <activiti:field name="variableNames">
          <activiti:string>
            creative_id,
            l_i_id,
            o_id
          </activiti:string>
        </activiti:field>
      </extensionElements>
    </serviceTask>
</code>
The creative_id in the delegate is not there. When I do execution.hasVariable("creative_id") I get back false.

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jbarrez — Mon, 10 Feb 2014 08:50:50 GMT

Okay, I would need your whole process (as simplified as much as possible, but still showing the error) so I can verify it and fix it in the engine if it is a bug. Would that be feasable.

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jorell — Mon, 10 Feb 2014 22:13:54 GMT

Here is the parent process:

<code>
<?xml version="1.0" encoding="UTF-8"?>
<definitions id="definitions"
             targetNamespace="testMultiInstanceLoop"
             xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xmlns:activiti="http://activiti.org/bpmn">

<process id="multiInstanceLoop" name="Test MultiInstance Loop Process" >

    <!– nodes –>
    <!– Start Node –>
    <startEvent id="start" name="Start" >
      <extensionElements>
        <activiti:formProperty id="creative_ids" name="creative_ids" type="list" required="true"/>
        <activiti:formProperty id="line_item_id" name="line_item_id" type="string" required="true"/>
      </extensionElements>
    </startEvent>

    <!– Sample Tasks –>
    <callActivity id="createSubs" name="createSubs" activiti:exclusive="false" calledElement="multiInstanceLoopSub">
      <extensionElements>
        <activiti:in source="line_item_id" target="l_i_id"/>
        <activitiut source="o_id" target="order_id"/>
      </extensionElements>
      <multiInstanceLoopCharacteristics isSequential="false" activiti:collection="c_ids" activiti:elementVariable="creative_id"/>
    </callActivity>

    <serviceTask id="verifyResult" name="Verify Result" activiti:class="com.xyz.somedelegatename" >
      <extensionElements>
       <activiti:field name="variableNames">
          <activiti:string>
            createSubs_order_id_map
          </activiti:string>
        </activiti:field>
      </extensionElements>
    </serviceTask>

    <!– End Node –>
    <endEvent id="end" name="End" />

    <!– connections –>
    <sequenceFlow id="flow1" sourceRef="start" targetRef="createSubs" />
    <sequenceFlow id="flow2" sourceRef="createSubs" targetRef="verifyResult" />
    <sequenceFlow id="flow3" sourceRef="verifyResult" targetRef="end" />
</process>
</definitions>
</code>

Here is the child:

<code>
<?xml version="1.0" encoding="UTF-8"?>
<definitions id="definitions"
             targetNamespace="testMultiInstanceLoop"
             xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xmlns:activiti="http://activiti.org/bpmn">

<process id="multiInstanceLoopSub" name="Test MultiInstance Loop Sub Process" >

    <!– nodes –>
    <!– Start Node –>
    <startEvent id="start" name="Start" >
      <extensionElements>
        <activiti:formProperty id="creative_id" name="creativeId" type="string" required="true"/>
        <activiti:formProperty id="l_i_id" name="lineItemId" type="string" required="true"/>
      </extensionElements>
    </startEvent>

    <!– Sample Tasks –>
    <serviceTask id="taskId" name="Task Name" activiti:class="com.xyz.delegatename" >
      <extensionElements>
       <activiti:field name="variableNames">
          <activiti:string>
            creative_id,
            l_i_id,
            o_id
          </activiti:string>
        </activiti:field>
      </extensionElements>
    </serviceTask>

    <!– End Node –>
    <endEvent id="end" name="End" />

    <!– connections –>
    <sequenceFlow id="flow1" sourceRef="start" targetRef="taskId" />
    <sequenceFlow id="flow3" sourceRef="taskId" targetRef="end" />
</process>
</definitions>
</code>

To summarize, I am unable to access 'creative_id' in com.xyz.delegatename using execution.hasVariable() method. Please let me know if I can provide more info.

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

trademak — Tue, 11 Feb 2014 15:12:58 GMT

That's because creative_id is not passed as a variable to the sub process. What you could do is define a multi-instance sub process and then have a call activity in there that also provides create_id as one of the input parameters (with an activiti:in element).

Best regards,

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jorell — Wed, 12 Feb 2014 01:46:14 GMT

I would be surprised if I need to explicitly pass in creative_id to the sub process. When I have a multiInstance Loop like below:

<code>
<multiInstanceLoopCharacteristics isSequential="false" activiti:collection="c_ids" activiti:elementVariable="creative_id"/>
</code>

The activiti:elementVariable is supposed to do exactly that, according to the documentation:

<code>
Suppose the variable assigneeList contains the values [kermit, gonzo, foziee]. In the snippet above, three user tasks will be created in parallel. Each of the executions will have a process variable named assignee containing one value of the collection, which is used to assign the user task in this example.

The downside of the loopDataInputRef and inputDataItem is that 1) the names are pretty hard to remember and 2) due to the BPMN 2.0 schema restrictions they can't contain expressions. Activiti solves this by offering the collection and elementVariable attributes on the multiInstanceCharacteristics:
</code>

Otherwise in my case where I have a multiInstance loop inside a call activity, I see no point in using activiti:elementVariable. Please let me know if I misunderstood.

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

trademak — Wed, 12 Feb 2014 18:04:11 GMT

No that's not correct. You have to pass every variable you want to set in the sub process context via input parameters of a call activity. Nothing is passed automatically, so also not the multi instance element variable. The element variable is only available in the parent process context.

Best regards,

Re: Element Variable not being assigned to subprocess for MultiInstanceLoop

jorell — Thu, 13 Feb 2014 18:53:02 GMT

Alright. I understand that that's how its coded right now. But what is the justification to keep it this way. When a user uses the elementVariable attribute in a multiInstance loop, it is clear the intent is to use this variable in the subprocess. Why not provide this to the subprocess implicitly without having them explicitly provide it?
Thanks for taking the time to look at this Tijs.