The ruleflow-group will control the rules to not fire until the
ruleTask is reached in your process, but all the evaluations will be
done as soon as the information goes inside the
workingmemory/ksession.
Cheers
On Thu, Dec 29, 2011 at 12:40 PM, Rob Fisher
<rob.fisher.l2gk(a)statefarm.com> wrote:
Was curious if this had been resolved through subsequent versions? I
too am
trying to incorporate a custom AgendaFilter (using rule metadata attributes
to control the firing of rules). I would also prefer to run my rules
through a ruleflow. However, with the AgendaFilter, my rules are not
firing. Without, they are. I'm currently working with 5.2 Final. If not,
any recommendations on other ways to control firing of rules, while keeping
the use of the ruleflow?
Thanks!
--
View this message in context:
http://drools.46999.n3.nabble.com/Flow-isn-t-behaving-as-I-d-expect-tp320...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
- CTO @
http://www.plugtree.com
- MyJourney @
http://salaboy.wordpress.com
- Co-Founder @
http://www.jugargentina.org
- Co-Founder @
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -