Problem with multi instance activiti time event in a subprocess

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.

avc

I have a problem with the boundary time event. After x minutes the Subprocess must exit but at the moment the Instance still exist and the escalation instance exist. In the manual stands “Since a multi-instance is a regular activity, it is possible to define a boundary event on its boundary. In case of an interrupting boundary event, when the event is caught, all instances that are still active will be destroyed.”
I don’t find the Problem

    <subProcess id="subprocess1" name="Sub Process">
      <multiInstanceLoopCharacteristics isSequential="false">
                         <loopDataInputRef>antrag.vorgesertzteKuerzel</loopDataInputRef>
            <inputDataItem name="assignee"/>
      <completionCondition>${nrOfCompletedInstances &gt;= 1 }</completionCondition>
      </multiInstanceLoopCharacteristics>
      <userTask id="dringlichkeitpruefen" name="Dringlichkeit Prüfen" activiti:assignee=${assignee}>
        <extensionElements>
          <activiti:formProperty id="dringend" name="Dringend" type="boolean" variable="${antrag.dringend}" required="true"></activiti:formProperty>
          <activiti:formProperty id="startdat" name="Start Datum" type="date" expression="${antrag.startDat}" readable="false" writable="false"></activiti:formProperty>
          <activiti:formProperty id="endDat" name="End Datum" type="date" expression="${antrag.endDat}" readable="false" writable="false"></activiti:formProperty>
          <activiti:formProperty id="abgesprochen" name="Abgesprochen mit Projektleitern" type="boolean" expression="${antrag.abgesprochen}" readable="false" writable="false"></activiti:formProperty>
          <activiti:formProperty id="besondereSachen" name="Beondere Umstände" type="string" expression="${antrag.besondereSachen}" readable="false" writable="false"></activiti:formProperty>
          <activiti:formProperty id="art" name="Art" type="string" expression="${antrag.art}" readable="false" writable="false"></activiti:formProperty>
          <activiti:formProperty id="stunden" name="Genügend Studen vorhanden" type="boolean" expression="${antrag.stunden}" writable="false"></activiti:formProperty>
          <activiti:formProperty id="bereitschaft" name="Ist der Mitarbeiter in Bereischaft" type="boolean" expression="${antrag.breitschaft}" writable="false"></activiti:formProperty>
          <activiti:formProperty id="urlaub" name="Besitzt der Mitarbeiter genügend Urlaubstage" type="boolean" expression="${antrag.urlaub}" writable="false"></activiti:formProperty>
        </extensionElements>
      </userTask>
      <startEvent id="startevent3" name="Start"></startEvent>
      <endEvent id="endevent2" name="End"></endEvent>
      <sequenceFlow id="flow7" sourceRef="startevent3" targetRef="dringlichkeitpruefen"></sequenceFlow>
      <sequenceFlow id="flow8" sourceRef="dringlichkeitpruefen" targetRef="endevent2"></sequenceFlow>
    
       <boundaryEvent id="boundarytimer1" name="Timer" attachedToRef="subprocess1" cancelActivity="true">
      <timerEventDefinition>
        <timeDuration>PT1M</timeDuration>
      </timerEventDefinition>
    </boundaryEvent>
   </subProcess>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

here a the Diagramm

https://www.dropbox.com/s/a17hy2gtvr3cxom/fehlerassyncrone.JPG

frederikherema1

On first sight, looks like the boundary-event is only closing a single instance of the multi-instance sub-process. Is it possible to create a simple unit-test for this, highlighting the failure. If it's indeed an issue, as a workaround, you can add an additional subprocess-scope around the MI-subprocess and put the bondary-event on the outer sub-process.