Metadata

<manual-activity id="1" category="AC1">
      ...    
    <join type="none"/>
    <split type="and">
      <transition-id idref="1"/>
      <transition-id idref="2"/>
      <transition-id idref="3"/>
      <transition-id idref="4"/>
    </split>
    <task>
      ...       
    </task>
    <allocation-strategy type="target" 
                         identifier="HEARINGSCHEDULE"/>
    <event-wait>
      ...
    </event-wait>
  </manual-activity>

The metadata for the split type of and is similar to the split type of xor (see Choice XOR Split). The difference is that the type of split is specified as and. This ensures that when the workflow engine is determining the list of transitions to follow from a specified activity, the order of the transitions in this list is not important as all eligible transitions in an and split will be followed. The ordered list of transitions is maintained in this instance for this split type to facilitate the changing of the split type from and to an xor, in which case the order of the transitions becomes important again.