Information Technology Reference
In-Depth Information
<bpmn2:boundaryEvent id="_A" name="" attachedToRef="_4">
<bpmn2:outgoing>_A_C</bpmn2:outgoing>
<bpmn2:errorEventDefinition id="_A1"
errorRef="java.lang.RuntimeException"/>
</bpmn2:boundaryEvent>
As you can see, this event is attached to another component (in this case, the compile
task) to receive events from it. It holds a reference to the error type that will be handled
through this particular connection.
Adding simple process data
In this section, we will add more information to our process diagram so that we are able to
execute it. We will need to specify the information that will be required by the process to
start, the information that will be required and generated by the human interactions, and
the information that will be sent to the external services that will be used by the process.
We will use the first and simplest version of the process to easily understand how we can
technically define the information exchange that will be required to accomplish the pro-
cess' business goal.
This information will be provided to the start event and will represent the information sent
by the product managers to the system. Because this information needs to be stored inside
our process, we will define what we call process variables. These process variables (or
process properties) are defined within the <bpmn2:process> tag, but outside any other
task, as it is shown in the following code:
<bpmn2:property id="project"
itemSubjectRef="_projectItem"/>
<bpmn2:property id="reqDescription"
itemSubjectRef="_reqDescriptionItem"/>
<bpmn2:property id="storyPoints"
itemSubjectRef="_storyPointsItem"/>
<bpmn2:property id="developerId"
itemSubjectRef="_developerIdItem"/>
<bpmn2:property id="compiled"
itemSubjectRef="_compiledItem"/>
<bpmn2:property id="deployed"
itemSubjectRef="_deployedItem"/>
Search WWH ::




Custom Search