You got it this time ... I'm trying to inspect the field name. As you mention
there's a risk that a user could pick a mismatched RHS consequence, so I was hoping to
work some DRL magic to avoid that.
So I think I'll get around it by extending my facts and populating them each with the
value they should use. It means a lot more up-front calculations, but its probably the
Michael Anstis <michael.anstis(a)gmail.com> wrote:
rules-users mailing list