Red Hat Bugzilla – Bug 1264746
jboss-bpmsuite-example: GDT editor reporting impossible matches in "Mortgage Calculation"
Last modified: 2015-11-04 01:34:26 EST
Created attachment 1075390 [details]
Screenshot illustrating the issue.
Description of problem:
Guided Decision Tables editor reports that "Mortgage Calculation.gdst" artifact from bpm-example-app has impossible matches. Many errors of the following form are reported in the editor UI:
The impossible match is on row 2 for field creditScore of pattern Applicant.
Conflicting conditions are creditScore >= 660 and creditScore < 680.
The GDT seems valid to me. Perhaps those are false positives? Clicking 'Validate' button for the table shows "Item successfully validated".
Version-Release number of selected component (if applicable):
BPM Suite 6.2.0 ER2
Steps to Reproduce:
1. Install bpm-example-app (download http://dev138.mw.lab.eng.bos.redhat.com/candidate/brms-6.2.0.ER2/jboss-brms-bpmsuite-6.2.0.ER2-quickstarts.zip , unzip and follow instructions in jboss-bpmsuite-example/README)
2. Open guided decision table 'Mortgage Calculation.gstd' in editor
The Analysis panel in the editor displays error "Impossible match" for almost every row of the decision table (see screenshot)
All assets in the demo should be valid with no warnings/ errors reported
This was fixed in the a previous BZ for master. Cherry-picked to 6.3.x.
Ok, no more false positives, the 'Mortgage calculation' GDT is valid again. Verified with BPM Suite 6.2.0 ER5