Table of Contents

Decision rule forms validate values of properties


A developer asks:

Are there ways to validate or edit that values entered in decision rule forms "make business sense"?  For example, if using a decision table with a column of .State (where .State uses the field's values for states), we want to make sure that any values typed in that column are in fact states. 

On the Decision Table form, a SmartPrompt lists the state codes, but this doesn't prevent someone from adding a letter to the end of the state code, or just typing in an invalid value, introducing a typo and an incorrect rule.


Beginning with V4.2SP1, decision table, decision map, and decision tree rules valid property values when you save the rule form. 

Where a property and a value for that property are specified in those rules, design-time rule validation checks that the value entered is valid according to the property rule and its related edit rule. 

Note that such validation is applied only to syntactically obvious property/value pairings, when it is clear from the rule field entry that you are specifying a literal value for a specific property. 

This validation cannot be applied to expressions, because expressions are not parsed to determine intent regarding the property and value. 

But when your decision table, map value, or decision tree rule specifies property = value, that is syntactically plain and the value is edited when you save the rule form against values defined as valid for the property.

Suggest Edit

66% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.