Usually a set of rules fires all rules when you call fireAllRules. So,
what's keeping you from collecting the solutions derived from the
fired rules and presenting them in some order to the user?
If the sequental addition or update of properties is interleaved with
calls to fireAllRules I'd attach a marker object "Refused" with each
rule resulting in a solution, and set its property to true when necessary.
On 23/09/2013, Andrzej Grzelak <andrzej.grzelak(a)g.pl> wrote:
Im making some kind of expert system. And now i got new problem:
User is asked sequentially for propetieries of object, than I modify object
propetieries, then i call update() and fireAllRules() to check for any
It is repeated for every object property till we fire rule with answer.
Now problem comes : When user decline answer we need to find another one.
But first answer will fire every time now. That's not what i need....
Making somewhere in app list of "false answers" and then striping out them
on return wont work. My app flow is determined by drools rule fire - if one
of "answer rules" fires i return that answer, normally i would ask another
I would need to indicate drools somehow to delete/deactivate that rule.
Thanks for any help.