<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.adatis.co.uk/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>PEL Business Rule Re-use and Pre-defined What If Scenarios</title><link>http://blogs.adatis.co.uk/blogs/sachatomey/archive/2008/04/30/pel-business-rule-re-use-and-pre-defined-what-if-scenarios.aspx</link><description>You’ve built a rule set to satisfy an original set of business requirements for calculating budget, and all is good with the world. Then, a change order is raised and approved that requires, for want of a better description, a set of pre-defined what</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP2 (Build: 20611.960)</generator><item><title>re: PEL Business Rule Re-use and Pre-defined What If Scenarios</title><link>http://blogs.adatis.co.uk/blogs/sachatomey/archive/2008/04/30/pel-business-rule-re-use-and-pre-defined-what-if-scenarios.aspx#4818</link><pubDate>Thu, 01 May 2008 09:03:53 GMT</pubDate><guid isPermaLink="false">8d7d37f8-4a66-4c95-9fba-293fa87607dc:4818</guid><dc:creator>sachatomey</dc:creator><description>&lt;p&gt;Hi Peter,&lt;/p&gt;
&lt;p&gt;Yes, you are right, rule parameters are an option – However, one point I failed to mention in my post is that I’m using definition rules; for that ‘instant’ response. &amp;nbsp;If I were to employ rule parameters fed from the Excel Add-In, for example, I could not use a definition rule and this would result in an element of lag before the results are available. &amp;nbsp;Also, it would possibly make comparing the results of two pre-defined what-if’s more difficult.&lt;/p&gt;
&lt;p&gt;In my example I only use one member property to provide the factor/variance. &amp;nbsp;In reality this could be a bunch of properties to describe some more complex what-if’s. &amp;nbsp;Parameter entry could then become cumbersome when combined with a variety of different what-if’s. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I agree with your model variable point and relating the factor to the relevant scenario member and I guess that is the crux of the problem, and probably why I decided to go with a member property so I could use the natural relationship.&lt;/p&gt;
&lt;p&gt;Thanks for your comments, always most welcome !!&lt;/p&gt;
&lt;img src="http://blogs.adatis.co.uk/aggbug.aspx?PostID=4818" width="1" height="1"&gt;</description></item><item><title>re: PEL Business Rule Re-use and Pre-defined What If Scenarios</title><link>http://blogs.adatis.co.uk/blogs/sachatomey/archive/2008/04/30/pel-business-rule-re-use-and-pre-defined-what-if-scenarios.aspx#4799</link><pubDate>Wed, 30 Apr 2008 22:19:25 GMT</pubDate><guid isPermaLink="false">8d7d37f8-4a66-4c95-9fba-293fa87607dc:4799</guid><dc:creator>Peter Eb.</dc:creator><description>&lt;p&gt;I&amp;#39;m curious why you don&amp;#39;t mention parameters for this. I haven&amp;#39;t thought your example through entirely but does being able to reference model variables help create more reusable rules for this case? In any event you could simply change the scale factor, but off-hand I&amp;#39;m not sure what you can do for relating it to the valid scenario members except by naming convention.&lt;/p&gt;&lt;img src="http://blogs.adatis.co.uk/aggbug.aspx?PostID=4799" width="1" height="1"&gt;</description></item></channel></rss>