All rule attributes are (more or less) just ad-hoc shortcuts for certain
scenarios which can, with little effort, be implemented using the
elementary techniques of inference, truth maintenance, fact manipulation
etc.
In fact, not letting rule attributes befuddle your mind will enable
you to design a clean logic. Finally, you proceed to implementation,
and then - only then - it is time to think about applying those
shortcuts.
-W
On 10/02/2014, jcarpene <jerome.carpene(a)sopragroup.com> wrote:
Hello,
I am trying to implement some rules that need more that a unique
Activation-group.
My case is related to some Voucher codes for online shopping. A simple case
works great, by defining an Activation-group to make sure 2 Voucher codes
cannot be used at the same time.
But now I need 2 Voucher codes (say Code 1, Code 2) to be compatible (no
activation-group) and a 3rd code (Code 3) to be disabled if Code 1 or Code
2
is used. If I use a XOR group name as an Activation-group, then Code 1 and
Code 2 will have a same Activation-group and will be exclusive (which I do
not want).
Do you know a way of setting multiple Activation-Groups for example, or any
workaround for that case ?
Regards,
Jerome
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Activation-group-how-to-set-many...
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