Hide Forgot
Description of problem: In Web Guided Decision Table it is possible to merge adjacent cells in a collumn that have the same value. Rows with such cells can that be collapsed (or grouped) together into one row. In such a state, if you remove a collumn the table becomes unoperable, save for changing the values in cells. It is impossible to expand the rows back, add a row, delete a row, add or delete a collumn.. till refresh. Version-Release number of selected component (if applicable): BRMS 5.2.0 ER5 Steps to Reproduce: 1. Create a Web DT with at least 2 rows, same values in one collumn. 2. Click the picture in upper left corner of the table to merge the cells 3. Click the "-" sign in the merged cell to collapse the rows 4. Remove a collumn 5. Try clicking the "+" sign in the merged cell, adding a row.. 6. Save the table or refresh in some way. -> Table is operable again.
Change 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: When merging cells in a guided decision table, the decision table could become inoperable.
Hi Mike, Please let me know how this was resolved so I can add the information to the release notes. Thanks Lee
Hi Lee, When deleting a column that contained a row of grouped data the underlying ungrouped row data was not correctly processed leading to the corruption. Cheers, 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 @@ -When merging cells in a guided decision table, the decision table could become inoperable.+When merging cells in a guided decision table, the decision table could become inoperable. This was because deleting a column that contained a row of grouped data the underlying ungrouped row data was not correctly processed leading to the corruption. This has been resolved and the error no longer occurs.