The Decision Table parser only adds the Fact type to the generated rule if it has at least one constraint.

There is a workaround (although I've not tried it):-

CONDITION         | CONDITION         | CONDITION         | ACTION
--------------------------------------------------------------------------------------
Customer                              | Tariff            |
--------------------------------------------------------------------------------------
this != $param    | name              | value             | customer.setOffer($param)
--------------------------------------------------------------------------------------
null              | "pepe"            | 5                 | "lot of offers"
null              |                   | 100               | "lot of offers"

It basically adds an additional constraint that can never be false.

On 16 March 2012 13:00, Zeta <zoraidahidalgo@gmail.com> wrote:
Hi,

thanks for your responses. You right but, why is it? I mean, rules are
receiving two facts(one Customer instance and one Tariff instance) and I
need to set the customer offer value even when I am not checking any
condition on the customer. Is it not possible? Is there any workaround?

Thanks.-

--
View this message in context: http://drools.46999.n3.nabble.com/Doubt-when-modifying-facts-on-an-action-tp3831681p3831775.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users