- The issue mentioned in the title could be seen with the use case of enumeration with Guided Rules, Guided Decision Tables and as per some users Guided Decision Template too (although my attached test case might not be able to replicate this one). The issue occurs when we use Enumeration for a field of a fact in Guided rules and we could see that the resultant rule does not contain the selected value from the enumeration drop down as within quotes ("") , thus resulting validation errors. Following are my findings from the research and it can be validated it from the attached project archive "repository1_TestProject.zip" as well.
- Although the use case of an enumeration used for a 'List' type of fact ('SimpleFact.factOne') might not look as a best way to use the enumeration feature in guided rules, but in some use cases it can be a valid use case. For an example take the following use case.
If a rule developer has a 'List' and they want to find out if the list contains a specific value and he would like to use a dropdown to identify the specific value, in an effort to prevent the user of the rules to enter an invalid value/entry. e.g. to validate a list of 'loan' types (e.g. "housing", "automobile" , "personal" , "industrial") and developer needs to be able to check whether the 'loan' is of a predefined type. Instead of typing in the type of 'loan' , developer would restrict the options to what is visible in a drop down, based of an enumerator just like in above example project.
- is cloned by
-
RHBRMS-2578 [GSS] (6.3.z) Use of "contains" operator does not add values from enumeration with quotes in Guided Rules etc.
- Closed
- is related to
-
RHBRMS-2754 [GSS] (6.4.z) Unexpected results in GDST when using enumerations with commas
- Verified