Information Technology Reference
In-Depth Information
<bpmn2:outgoing>_7_3</bpmn2:outgoing>
</bpmn2:exclusiveGateway>
As you can see, two outgoing sequence flows are referenced from the diverging flow ob-
ject, and two incoming sequence flows are referenced from the converging flow object.
Version 3 of the process includes an intermediate signal catch event definition, which is
used to wait for an external notification. This notification will be generated if the require-
ment development is cancelled. It also has two error boundary event definitions that will
be used when compilation or deployment throws an error. All these components are
shown in the following diagram:
The intermediate signal catch event is represented by the following XML snippet:
<bpmn2:intermediateCatchEvent id="_D" name="Cancel Req.">
<bpmn2:outgoing>_D_E</bpmn2:outgoing>
<bpmn2:signalEventDefinition id="_D1"
signalRef="reqCancelled"/>
</bpmn2:intermediateCatchEvent>
As you can see, this event flow object doesn't have any information about the event type;
it just has a reference name for the signal name. It doesn't have the information that this
event will contain (and that needs to be propagated to the process context) either.
One of the error boundary events is represented by the following XML snippet:
