It would be "polite" to have it:
Rule "Cleanup Rule"
salience -999
rule-flow-group "your group"
when
$g: Guard()
then
retract($g);
end
The low salience will make activations of this rule to be executed at the
end of the execution cycle.
Best Regards,
XXX
Thanks, it worked.
Is cleaning up the session necessary?
How would that rule look like?
--
View this message in context:
http://drools.46999.n3.nabble.com/Problem-with-sub-process-rules-inside-multiple-instances-tp3009981p3014310.html
Sent from the Drools: User forum mailing list archive at Nabb
Yes, I was talking about a dummy object that must be inserted before the
Rule Node.
Your rules then should use this object at its first restriction, but there
is no need to modify it. Ej:
when
Guard()
then
end
The low-salience rule I was talking about is meant to clean up the s
Hmmm, that could be it!
I'm not sure I understand what you mean by that "guard" object. Would that
mean that I should insert some dummy object in a script node (action node)
before my rule node and change its value inside this rule, so the rule could
be triggered when the second and third instance
I'm not sure, but it could be that your rules (which is really just one
rule) belongs to the same rule-flow-group. So, when the first rule node is
executed, the rule-flow-group is activated and the rule get fired. When the
second rule node is executed (in the second iteration of your
multiple-insta
Does anyone have a working example of a sub-process with rules, inside a
multiple instances node?
I can't get it to work properly.
This sub-process of mine has one script node (that just prints something)
and one rule. Multiple instances node gets a Collection of three elements,
so the sub-proce
