Felipe Piccolini <felipe.piccolini <at> bluesoft.cl> writes: > > Subir, > > If you have 5 different numeric attrinutes then you will have just 4 > columns, in the same example. Columns are for different constrains, > but rows are for the use of those constrains (rules). So lets say you > have 3 different comparations (A>$param, A<$param, A==$param) if > $param is the attribute and you have 5 of them, then you will have 15 > rows, but only 3 columns. > > If you need more help you can send me an example with the table your > are working on, and I will be happy to attach some comments on it. > > Good luck!. > > Monday, November 28, 2005, 2:05:37 PM, you 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 > > -------------------------- > Felipe Piccolini > felipe.piccolini <at> bluesoft.cl > >
Hi Felipe, 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
