I understand that fact could store the values but my question more towards how to design this for dynamic number of facts. Let's say, if the business want to modify the rules with more fact values, I want to be able to happen this dynamically rather than changing the code for fact values and adding it there. I was thinking more toward having a property file(database??) and program reads those dynamic values and prepares fact model before running the rules Thoughts?? Thanks -- View this message in context: http://drools.46999.n3.nabble.com/drools-dynamic-LHS-tp2980536p2981145.html Sent from the Drools: User forum mailing list archive at Nabble.com.

Am 24.05.2011 21:17, schrieb marunam: Smells like YAGNI and a lot of accidental complexity. I'd code in DRL exactly what your business requires when it requires it, and design my software process in a way that allows to release/deploy the rules on the fly (which is actually quite easy thanks to support in Drools). Think "release/deploy to production three times a day". Exception to this rule of thumb might be if you want to re-use the same business rules for different customers but with different age limits, like maybe in a multi-tenant application. But that's a different story. In this case, you could define "configuration facts" which have to be defined for each tenant, and which are used in the actual rules like so: customer-a-configuration.drl: rule "Configure age threshold" when # fire always then insertLogical(new AgeThreshold(24)); end customer-b-configuration.drl: rule "Configure age threshold" when # fire always then insertLogical(new AgeThreshold(27)); end common-rules.drl: rule "Check age threshold" when AgeThreshold( $threshold: threshold ) Person( age > $threshold ) then // do something end Best regards Ansgar

Am 25.05.2011 00:34, schrieb marunam: Create pre-compiled rule packages: one for each state and one for the generic rules, and merge the latter with one of the "facts per state" when preparing the knowledge base. Works well for our use case (multiple customers), should do equally well for a number of states. Best regards Ansgar

You can load the "Configuration" fact from your calling program ( depending upon the state you are firing the rule for. ) This can be done using database/property file. Then insert this fact into working memory and then insert rest of the facts that you are already doing. This way you'll be able to re-use same ruleset and state-specific configuration fact object. -abhay -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of marunam Sent: Wednesday, May 25, 2011 4:05 AM To: rules-users(a)lists.jboss.org Subject: Re: [rules-users] drools dynamic LHS Thank you all for your response The reason why I need this is, the rules are for different states and the fact values could differ among states(insurance application). We probably don't want to duplicate rules for different states by writing separate drl file(just changing the fact value....age in our example) for each state What I was thinking was, creating fact object dynamically with its attributes being loaded from some properties file dynamically?? Any other solution/suggestions? Thanks -- View this message in context: http://drools.46999.n3.nabble.com/drools-dynamic-LHS-tp2980536p2982029.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users