Bryan Van Hook

Using parameters instead of literal values in decision table conditions

Discussion created by Bryan Van Hook on Mar 13, 2013
Latest reply on Mar 14, 2013 by Bryan Van Hook

The standard options for selecting the "cell format" for decision table conditions allow you to input a literal value, such as >5 or <10. What's the best way to write a condition when that value is not known at design time?


As an example, suppose we have a customer attempt to charge a purchase on their credit card that exceeds the available credit limit. Both the purchase amount and available credit are only known at runtime. We need a rule that has a condition purchaseAmount < availableCredit, in combination with several other conditions that determine which action to take. The decision tables in Blaze 7.1 do not appear to support this. Any suggestions?