Metadata

<manual-activity id="1" category="AC1">
    ...
    <join type="and"/>      
    <split type="xor">
        <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>

split

This is present for each activity and it contains the details of the split from the activity. This includes a list of the transitions from the specified activity that will be resolved by the workflow engine when the associated activity is completed to examine if they can be followed or not.

The order of the transitions in this list is important for a split type of XOR as it is the first transition that is eligible in the ordered list of transitions that will be followed by the workflow engine. In the metadata example above, if the transition conditions for transition identifiers 2, 3 and 4 are satisfied, it is the transition with the identifier of 2 that will be followed as this is the first eligible transition in the list of ordered transitions.

type: This represents the type of the split. As described above, there are three possible split types. A split type of none indicates that there is only one outgoing transition from the specified activity. A split type of xor indicates a choice and this means that the first eligible transition from the list of ordered transitions will be followed. A split type of and indicates a parallel path of execution which ensures that all of the eligible transitions listed in the ordered list of transitions will be followed in parallel.

transition-id

This contains a reference to the specified transition. There will be multiple entries of this metadata tag when the split type is xor or and.

idref: This contains a reference to a transition in the workflow process definition.