A splitting XOR starts with a function that represents a decision and is followed by an XOR rule. The rule must be followed by an event for each branch of the process. This event may also be an end event. Each branch must end with an event.
You can define conditions that have their own business semantics and specify which branch of the process is to be taken after the XOR. The conditions can be specified as follows:
The Condition expression attribute is specified at the connection leading from the XOR rule to the subsequent event.
The Connection role attribute is specified at the connection leading from the XOR rule to the subsequent event.
The Name attribute is specified for the event that follows the XOR rule.
The splitting XOR rule is transformed into a task at which a decision must be made. This task is followed by a data-based XOR gateway. The condition specified in the EPC is written to the Condition expression attribute of the connection that starts at the XOR gateway. The graphic displays the exact mapping of this type of pattern. In addition, Expression is specified as the value of the Condition attribute.
The individual branches end with a BPMN end event. The Name attribute in the BPMN diagram is set to the name of the end event in the EPC.
The graphic displays an example with two branches, but any number of branches can be modeled.