Integration with Other Knowledge Definitions - jBPM6 Developer Guide - page 284

The preceding process diagram has a Business Rule task called prioritize requirement .
The task has an input mapping of a Requirement object, such as the one we saw in the
model of Chapter 6 , Human Interactions , and Chapter 7 , Defining Your Environment with
the Runtime Manager . It also defines establish-reqs-priority as the
RuleFlow Group attribute value. This attribute will define that when the process in-
stance reaches the prioritize requirement task, only rules that define the same
RuleFlow group variable will be activated. You can see examples of such rules in the
reqRules.drl file. The following code snippet is a small skeleton of a rule that
defines such group:
rule "prioritize requirements"
lock-on-active
ruleflow-group "establish-reqs-priority"
when
r: Requirement(priority == -1)
then
r.setPriority(5);
end
As you can see in the examples, you can have multiple rules that evaluate the model and
change values to different objects in it. The output of the rules in a Business Rule task is