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-instance), the rule-flow-group is activated again (actually, it was already active), but since anything has changed since the last execution, no rules will be fired.
One possible solution could be to add a "guard" restriction to your rules. So, inside the subprocess you can insert an instance of this "guard" object before the rule node. You can also even have a rule with low salience to retract this "guard" when you are done.
Best Regards,
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Esteban Aliverti
- Developer @
http://www.plugtree.com - Blog @
http://ilesteban.wordpress.com
On Wed, Jun 1, 2011 at 6:31 AM, HMandic
<trbuhom@net.hr> wrote:
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-process in question should run three times, and it does.
The script node executes three times, as it should, BUT the rule executes
only for the first sub-process, not for the other two!
Just to clarify things - there's no condition in that rule, just a
System.out.print in RHS.
--
View this message in context: http://drools.46999.n3.nabble.com/Problem-with-sub-process-rules-inside-multiple-instances-tp3009981p3009981.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users