A Split activity allows an instance to travel over several parallel paths at the same time.
The number of copies that the Split generates is the number of outgoing unconditional transitions plus any conditional transitions that evaluate to true for the Split activity.
Split activities must have a corresponding Join activity in order to complete the circuit and resume the process flow.
Activities within the Split / Join circuit cannot have any transitions to or from activities outside it. An exception to this rule is when you have a Grab activity to handle overrun conditions within the Split / Join circuit. However, in this case, grabbed instances can only be sent back to the activity from which they were grabbed or to the End activity and never to another activity outside the Split / Join circuit.
When an instance reaches a Split activity, the original instance immediately flows to the corresponding Join activity. Copies of the original instance travel through the activities inside the Split / Join circuit.