This could be an option. I will give a try.
Thank you.
Dr. Gernot Starke wrote:
>
> Georgy,
>
> one (simple) way to achieve this is to assert a "stop"-fact on the
> right-hand-side
> of the executing rule (e.g. by setting an appropriate attribute) AND
> querying that attribute on the LHS
activation-group behaves in a bit another manner: if first rule is activated,
the other rules are blocked for the whole working memory, not for this
particular entity. So it's not what I'm looking for.
Chris Woodrow wrote:
>
> Hi,
> The attribute 'activation-group' might be what you are lookiing
Hi,
I'm looking into the Drools engine for our application, and looks like it's
satisfies the reqirements. The only thing I haven't found still is a
following conflict management model:
If rule_1 (with highest salience) is applicable, STOP applying another
rules.
So the essence is that only 1