Exclusive gateway after parallel gateway problem

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

rkroll

We have a process similar to the following:
[img]http://i51.tinypic.com/2qjm3if.png[/img]


When the exclusive gateway is passed (either path), the join never occurs to reach the "Never Reached" user task.  Is there something we're missing in this type of logic flow?  We have also tried using an additional Parallel gateway to after the exclusive gateway to no avail.

Here is the test BPMN we are using -

<startEvent id="startevent1" name="Start"></startEvent>
    <userTask id="usertask1" name="Initial Task" activiti:assignee="pbutler"></userTask>
    <parallelGateway id="parallelgateway1" name="Parallel Gateway"></parallelGateway>
    <userTask id="usertask2" name="Task1" activiti:assignee="pbutler"></userTask>
    <userTask id="usertask3" name="Task 2" activiti:assignee="pbutler"></userTask>
    <exclusiveGateway id="exclusivegateway1" name="Exclusive Gateway" default="flow9"></exclusiveGateway>
    <userTask id="usertask5" name="Test No" activiti:assignee="pbutler"></userTask>
    <parallelGateway id="parallelgateway2" name="Parallel Gateway"></parallelGateway>
    <userTask id="usertask4" name="Never Reached" activiti:assignee="pbutler"></userTask>
    <endEvent id="endevent1" name="End"></endEvent>
    <sequenceFlow id="flow1" name="" sourceRef="usertask1" targetRef="parallelgateway1"></sequenceFlow>
    <sequenceFlow id="flow2" name="" sourceRef="parallelgateway2" targetRef="usertask4"></sequenceFlow>
    <sequenceFlow id="flow3" name="" sourceRef="usertask4" targetRef="endevent1"></sequenceFlow>
    <sequenceFlow id="flow4" name="" sourceRef="parallelgateway1" targetRef="usertask3"></sequenceFlow>
    <sequenceFlow id="flow5" name="" sourceRef="usertask3" targetRef="parallelgateway2"></sequenceFlow>
    <sequenceFlow id="flow6" name="" sourceRef="parallelgateway1" targetRef="usertask2"></sequenceFlow>
    <sequenceFlow id="flow7" name="" sourceRef="usertask2" targetRef="exclusivegateway1"></sequenceFlow>
    <sequenceFlow id="flow9" name="" sourceRef="exclusivegateway1" targetRef="usertask5">
      <conditionExpression xsi:type="tFormalExpression"><![CDATA[${false}]]></conditionExpression>
    </sequenceFlow>
    <sequenceFlow id="flow11" name="" sourceRef="startevent1" targetRef="usertask1"></sequenceFlow>
    <sequenceFlow id="flow12" name="" sourceRef="exclusivegateway1" targetRef="parallelgateway2"></sequenceFlow>
    <sequenceFlow id="flow13" name="" sourceRef="usertask5" targetRef="parallelgateway2"></sequenceFlow>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Thanks!

ronald_van_kuij

Learn the semantics of a parallel gateway.

http://www.activiti.org/userguide/index.html#bpmnParallelGateway


And from the Activiti in action book (worth buying)

join—All concurrent executions arriving at the parallel gateway wait in the gateway until an execution has arrived for each incoming sequence flow. Then the process continues past the joining gateway.