INC-223222 · Issue 723634
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.7.3
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
INC-223222 · Issue 723635
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.8
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
SR-133715 · Issue 204978
RTE <br> handling resolved when using pega:when = false
Resolved in Pega Version 7.2
Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.
SR-133715 · Issue 209655
RTE <br> handling resolved when using pega:when = false
Resolved in Pega Version 7.2
Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.
SR-A3803 · Issue 212217
Better handling for menus when using JAWS
Resolved in Pega Version 7.2
When accessibility was invoked, the Navigation menu did not indicate arrow up/down options in links with showmenu role='link' generated on them, and JAWS was not reading out that it was a link with a menu. This was an unintended side-effect of updates to avoid reading out a URL in a label/text, and corrections have been made to support accessibility so that navigational menus are read out more intuitively with JAWS.
SR-A9773 · Issue 221357
Fixed repeating row focus when using Accessibility
Resolved in Pega Version 7.2
When Accessibility was enabled and the add icon was clicked to add a section to a row repeat, it was not possible to access the first item in first row with the keyboard. Additional added rows had the correct focus. This was traced to an issue where getFocusOnNewRow was not being called correctly, and as been resolved.
SR-A12357 · Issue 230904
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A12357 · Issue 231872
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A101069 · Issue 270616
Fixed dropdown issues when using Google Chrome
Resolved in Pega Version 7.2.2
The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.
SR-A101069 · Issue 269981
Fixed dropdown issues when using Google Chrome
Resolved in Pega Version 7.2.2
The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.