Information Technology Reference
In-Depth Information
Configuring the event nodes
The Start Event node represents the beginning of the process. From all the different Start
Event types that we can use, we will use the None Start Event node, because in jBPM6,
you have to use this type of Start Event when your process is going to be explicitly started
using its ID, as the following line of code does:
Ksession.startProcess("id.of.the.process");
The properties present in this node relevant to the jBPM6 runtime are as follows:
Property
Description
This property defines all the output variables of the node. Each variable has a type (Java class) and a name.
Specifically, in the case of the None Start Event node, this property has no meaning. The property exists for
this node because it is used by other Start Event subtypes (that is, Signal Start Event, where it is used to hold
a reference to the Signal event and the information it contains).
DataOutput
This is the way we assign data from the different
DataOutput
variables to process variables. The type of
DataOutput
must be assignable to the process variable type. This property is present in each node that has
a
DataOutput
property.
DataOutputAssociations
The editor will have to create
DataOutput
. Associations require a dedicated section, as it is probably the
most complex property editor in the process designer. We are going to learn how to use it later in this chapter.
Given that this None Start Event node doesn't have any properties that affect its behavior
during execution, we are not going to modify any of them.
After the Start Event node is invoked, a process execution will be started. During the pro-
cess execution, we might capture two other types of events,
Signal Intermediate Catch
events (the circle with a triangle inside it at the bottom of the diagram) and
Error Bound-
ary
events (the two circles with the lightning-like icon, located at the border of two of the
tasks we defined).
Intermediate Signal Event nodes have to wait for an event to arrive in order to continue
their execution. Events can be broadcast from another process or from the Java application.
Using them allows us to create more maintainable and robust processes. The properties we
can configure a Signal Intermediate Catch event are as follows:
