OK, you could add the "Date Range" columns to the spreadsheet, but I see your point.

Your problem still seems more like a version control problem than rules: If your rule author has made 5 versions of the decision table how are you proposing to identify which version needs to be applied to a given Product? Products will still need to have an "effective date" and you are still going to need a mechanism to associate a given Product with a given version of the rules. How are you going to achieve this?

If you are to lookup the appropriate version of the DRL why not lookup the appropriate dtable instead? If you're saying your rule authors want to simply change a single "live" version of a single spreadsheet (ha, sounds like a training issue to me) then when were you going to extract and save the DRL you first asked about?

With kind regards,

Mike

On 18 April 2011 10:41, Riyaz Saiyed <Riyaz.saiyed@emirates.com> wrote:
The idea is to store these price rules as xls decision table.

The admin (non technical guy) will periodically update the xls just to
change the price.

For example for the same date range - 1-Jan-2011 to 31-Mar-2011, price can
be increased of decrease depending on the volume of requests. So creating
multiple version (more entries in xls) may be time consuming for him. He
will prefer to do "find and replace" to update the price.

--
View this message in context: http://drools.46999.n3.nabble.com/Drools-Decision-Table-tp2830218p2833685.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