not sure I understand the question. a decision table is like a state chart.
Say I have an object with 10 attributes. the number of attributes don't matter for rules. What matters is the number of unique conditions the rules will use to evaluate the data. Or put it another way. the number of columns is equal to the number of unique conditions. each row is a rule, which means each row has 1 or more columns checked. I haven't tried michael's decision table plugin, but that's generally how decision tables work in the tools I've seen. peter On 11/28/05, Subir Das <[EMAIL PROTECTED]> wrote: > > Hi Felipe, > > Thanks for your response. > So, if I have, say, 5 numeric attributes for setting up conditions, I need > to > have 15 columns in the decision table. As conditions will change with > course of > time and may be, at some point of time, those 15 columns will either be > extended or reduced. Hence I am just wondering if there is any better way > of > configuring the same. > > Cheers. > > Subir > >
