Hi,
this is definitely something in scope for the type of Defeasible rules i'm
working on right now.
I have just one last question:
do you need the second rule to override the activation of the first, or do
you need the VALUE set
by the second rule to override the value set by the first?
In your
Hi Davide,
For my case, whats proposed in Example #1 would suffice with the activations
being overridden i.e. the Rule High should completely override Rule Low
which should not be activated, and the outcome should be only one log (A)
and the policy should be set to A.
Example#2 for my case would
Davide,
Thanks for the suggestions. I was considering using the MetaData as well,
since it allows both evaluation on the LHS (just like the example you have)
as well as on the RHS where I can get the MetaData through code and use it
in the application.
And like you have suggested I can use
is a myth.
The business users wants rule-driven systems, yet they dont want to learn
drools. And drools DSL just doesnt cut it.
From: Davide Sottara dso...@gmail.com
To: rules-users@lists.jboss.org,
Date: 09/13/2012 01:57 AM
Subject:Re: [rules-users] Cutom Attributes in Drools
Sent
alternative ?
- Mail original -
De: gpa...@tsys.com
À: Rules Users List rules-users@lists.jboss.org
Envoyé: Jeudi 13 Septembre 2012 18:47:52
Objet: Re: [rules-users] Cutom Attributes in Drools
I would not store the result of the (missed) activation of a rule in a rule
attribute, anyway
Thank you for reporting this user experience... and I think this is of
interest for other users too.
I would address your problem at different levels..
You basically are asking for a more declarative approach to writing business
rules, and that is perfectly
understandable. The DRL rules are
Thanks for the suggestions. However I have rules where the Control Fact is
not mandatory, as well as there is a choice between multiple elements (LHS
and RHS) so I have to come up with a Dummy which says something like does
not apply to this rule, a bit cumbersome but an approach that can be
Hi,
Is there support for Custom Attributes in Drools? What I want to do is add
attributes which determines when rules should be fired as well as attributes
that the rule updates which I can query at a later time.
E.g. Fire rule only for specific regions. So when new rules are
created/added BAs
