Hide Forgot
Created attachment 537458 [details] decision table source Description of problem: DT Wizard allows you to add a Fact pattern with a binding and update that Fact in an action column. If you don't add a constraint to the Fact (some condition column), then the finished DT source points to an undefined Fact in the "when" section. Validation fails. Version-Release number of selected component (if applicable): BRMS 5.3.0 dev5 Steps to Reproduce: 1. Create a new rule - guided decision table - using the wizard. 2. Add a Fact pattern with binding "factBinding". Don't add any constraints to the Fact. 3. Add action to update a Fact - update some field of the Fact with binding "factBinding". 4. Click Finish. 5. Add a row and fill in some values into the cells. 6. Click View source from the Source menu. Actual results: The source shows empty "when" section and "factBinding.setField(value);", using the undefined "factBinding" variable/binding. Expected results: Either the source contains something like "when factBinding:Fact()" or the wizard doesn't allow to update a Fact without any constraints.
Created attachment 537459 [details] validation result
Fixed and back-ported to 5.3.x branch.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The decision table wizard allowed users to add a fact pattern with a binding and update that fact in an action column. If the user didn't add a constraint to the Fact (some condition column), then the finished decision table source points to an undefined Fact in the "when" section, and validation failed.
Hi Mike, Sorry another one :) For the release notes, if you could let me know how this was resolved, I can add it to the release notes to warn customers about changes that might affect them. Thanks Lee
No problem: You can no longer define actions to update a Fact Pattern where the Fact Pattern had zero constraints defined. This behavior is consistent with that of defining a decision table without using the Wizard.
Thanks Mike.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -The decision table wizard allowed users to add a fact pattern with a binding and update that fact in an action column. If the user didn't add a constraint to the Fact (some condition column), then the finished decision table source points to an undefined Fact in the "when" section, and validation failed.+The decision table wizard allowed users to add a fact pattern with a binding and update that fact in an action column. If the user didn't add a constraint to the Fact (some condition column), then the finished decision table source points to an undefined Fact in the "when" section, and validation failed. It is no longer possible to define actions to update a fact pattern which has zero constraints defined.