Peter Lin <woolfel <at> gmail.com> writes: > > 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 <subir_k_das <at> hotmail.com> 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 > > > > > Sorry for replying late. I did't get any email when you responded. I have just seen it in the gmane site.
Let's say I need to set up a RuleSet based on 5 numeric attributes N1,N2,N3,N4 and N5. And I need to set up conditions as follows : N1 > $param1 N1 == $param2 N1 < $param3 N2 > $param4 N2 == $param5 N2 < $param6 N3 > $param7 N3 == $param8 N3 < $param9 N4 > $param10 N4 == $param11 N4 < $param12 N5 > $param13 N5 == $param14 N5 < $param15 Later the Business Analyst may like to add more conditions or take off some conditions which eventually will result in adding or deleting columns (conditions) in the decision table. I am just wondering if there is better way to configure the rules. Cheers, Subir
