Information Technology Reference
In-Depth Information
usually a modification or addition in the model that will be easily checked by a gateway
later on. In our case, the elements we check in each of the gateways' outgoing connections
is the requirement's priority value, and determine two paths based on the values of the pri-
ority.
Ad hoc process instance evaluations
Ad hoc processes are processes whose sequence of actions cannot be predefined. When
we define an ad hoc process, we do know what tasks will be needed to be performed, but
the order and sequence of said tasks is either too complex to be defined in a flow or too
variable to be considered fixed. As a diagram, they just seem as a bag of tasks with no
connection between them. The following diagram shows a representation of the
ad-
hocProcess.bpmn2
file:
In jBPM6, ad hoc processes are supported in a way that makes it similar to a Business
Rule task: the name of the ad hoc process will be a ruleflow group that will be activated
when you reach the start the process. Using rules, you can determine which task needs to
be created and you can start one of those tasks manually using a class called
Dynam-
icUtils
. You can also determine the conditions to exit the ad hoc process using rules.
In the
process-rules-examples
project, you can find a test called
AdHocPro-
cessTest
, which uses this functionality to run an ad hoc subprocess called
adHocProcess
and uses the rules defined in the
ad-hoc-sub
ruleflow group to de-
termine the next task. The rules are defined in a file called
adhocRules.drl
, and on
finding specific conditions, fires a new work item to execute a specific task within the ad
hoc process as the following rule shows:
rule "init rule"
salience 100
