I think you need to use "modify" for that to happen. Otherwise, it doesn't
get re-evaluated. Or maybe it did, but you're using the no-loop /
lock-on-active attributes.
_ miguel
On Thu, May 6, 2010 at 3:51 PM, Shai Bentin wrote:
> It seems that drools did not re evaluate the EnrichedApplicatio
Shai wrote:
>
> --snip--
> I then do some more things and insert the value of NetRepayment value to
> the EnrichedApplication, I re insert it to the workspace and then I run
> the rules.
> It seems that drools did not re evaluate the EnrichedApplication again
> and thus the value of NetRepaye
Thanks,
I did this and saw that 'amount' was 0, although netRepayment was
1.04, after looking at it a bit further I found the problem.
When I create the workspace I insert EnrichedApplicationVersion, I run
some rules from a different agenda and then I cleared the agenda
(however did not re
Could the rules be changing the values outside of a modify block?
Please try this (untested) rule as a test.
It binds the value on the left hand side.
rule "netRepaymentWithLiabilities1TEST"
agenda-group "autoUnderwriting"
when
ea: EnrichedApplicationVersionTO(amount :
Hi there,
er.. why don't you remove your "eval" and just evaluate in the object
binding?
$var = TypeOfObject( netRepaymentAmountAbilityIncludingLiabilities <= 0.65)
Other than that, i don't think a lotta people are still using drools4 and i
have no idea why that is happening. Apparently, it make
I'm running drools 4. It has been running for a long time with no issues.
I have this weird issue now and I'm wondering what can explain this.
I have the following rule defined.
rule "netRepaymentWithLiabilities1"
agenda-group "autoUnderwriting"
when
#conditions
enric
