Information Technology Reference
In-Depth Information
Property
Description
Just like the
DataOutput
property explained for start nodes, this property is used to specify the output
variables in this node. In jBPM6, the only output variable you can define is
event
. This variable will contain
the event object.
DataOutput
DataOutputAssociations
Just like Start events, we have this property to map the output variable of this event to a process variable.
This is the key name of the event type that the node is waiting for. It is just a string that must be used when
you want to signal the event.
SignalRef
In our scenario, the event we are going to be waiting for is the manual cancellation of the
requirement, which is why we need to change the
SignalRef
property to
reqCan-
celled
. To do so, we select the event and then click on the
Properties
panel, where we
will see the properties of the event selected. In this case, we don't want to know anything
else from the event, so we are not going to define any
DataOutput
or
DataOut-
putAssociations
property in this node. The only other change we are going to make
to this node is to add a meaningful name to it so that users reviewing this process can eas-
ily understand what event the node is waiting for. The value we are going to set for the
Name
property is:
Req. Cancelled
.
The Error Boundary events that we defined for two of our tasks show that we want to
handle exceptions being thrown inside the execution of said tasks as part of the sequence
of steps in this process. Just like the Signal events, they have
DataOutput
and
DataOutputAssociations
to capture the event being sent. In them, you define a
single variable with any name that you can map to a process variable to keep the excep-
tion as a variable in subsequent nodes. For our case, we are not going to configure those
properties.
The one property we are going to configure is the
ErrorRef
property. In it, you must
write the fully qualified name of the exception you expect to capture. In jBPM6, it must
be a single specific type (not a generic super class of the exception, but the actual excep-
tion), and it must have a fully qualified name even if you added the exception type to the
Imports
property in the process properties. For our case, we will type
java.lang.RuntimeException
in said property.
The last event nodes that we will configure in our process are the
End Event
nodes,
which represent the end of the execution path on the process. We can configure them for
many different purposes, but in our case, we will use only a type that will terminate the
