| Summary: | Decision Table Wizard: row numbers missing in source, Test Scenarios cannot run. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Zuzana Krejčová <zkrejcov> |
| Component: | BRM (Guvnor) | Assignee: | manstis |
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | BRMS 5.3.0.GA | CC: | lpetrovi, manstis |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.3.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
After creating a decision table via the decision table wizard, running a test scenario against the decision table resulted in a "400 Sorry, a technical error occurred. Please contact a system administrator." error, this occurred because the data was not stored in the repository correctly. This issue has been resolved and the data created in decision table wizard is now stored correctly in the repository.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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:
After creating a decision table via the decision table wizard, running a test scenario against the decision table resulted in a "400 Sorry, a technical error occurred. Please contact a system administrator." error, this occurred because the data was not stored in the repository correctly. This issue has been resolved and the data created in decision table wizard is now stored correctly in the repository.
|
Description of problem: After finishing a Decision Table via the wizard, the first version of the table is created. To the user, it looks OK. But trying to run a Test Scenario will result in an error "400 Sorry, a technical error occurred. Please contact a system administrator." and the TS won't run. Clicking View source from the Source menu doesn't reveal anything interesting. The cause seems to be missing row number elements in the DT table content part of the repository. The corrupted repository (Administration->Import Export->Export) shows in the content of the table rows like these: <data><list> <value> <dataType>STRING</dataType> <isOtherwise>false</isOtherwise> </value> <value> <dataType>STRING</dataType> <isOtherwise>false</isOtherwise> </value> <value> <valueString>1</valueString> <dataType>STRING</dataType> <isOtherwise>false</isOtherwise> </value> <value> <valueString>2</valueString> <dataType>STRING</dataType> <isOtherwise>false</isOtherwise> </value> </list><!--other rows--></data> The first <value> element is missing the actual content of the cell - the row number. There needs to be <valueNumeric>[row_number]</valueNumeric> otherwise, the Test Scenario won't work, as mentioned above. The <dataType> element value can remain String, that doesn't seem to matter. Once you manually add the row number, you can import it and it works just fine - if you avoided other Wizard related bugs. Further work with the Decision Table fixes this problem - saving it, archiving and unarchiving, adding columns, rows... 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 and field restriction, make sure to fill in the value list. (Choose to expand all the columns.) 3. Finish the table. 4. Without saving the table - the first commit has already been done by the Wizard - open or create a Test Scenario and try to run it. Actual results: Error shown - "400 Sorry, a technical error occurred. Please contact a system administrator." Expected results: Test Scenario runs as expected.