Hi folks, According to the user guide, lock-on-active “inhibits additional activations of all rules with this flag set within the same rule flow or agenda group”.
I was doing a little testing of some rules earlier today, and noticed that lock-on-active seems to change behaviour when applied to rules which don’t have an agenda-group or rules flow-group defined. It also seemed to have a slightly inconsistent effect, although that may just be me not realising what it’s supposed to do. There doesn’t appear to be any documentation of what the attribute means when a rule is not part of a rule flow or agenda group. So I was wondering whether perhaps there is an expected/official behaviour, which is just not documented. Or is lock-on-active without a rule flow or agenda group an error? In which case is there a reason why it doesn’t cause a compilation error when the knowledge base is built? Yours curiously... Steve _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
