SR-A89260 · Issue 263428
Performance improvements for Proposition rule editing in Google Chrome
Resolved in Pega Version 7.2.2
Proposition' rule editing in Google Chrome was substantially slower than in other browsers due to the display handling for a text area present inside a Table structure with a heavy DOM. Performance has been improved by updating the code to avoid span generation for a minimum height setting in pixels and by optimizing the heightUpdate API.
SR-A97603 · Issue 264562
JAWS reads "Showing all reports"
Resolved in Pega Version 7.2.2
The Accessibility related property for dynamic layout of section pzRBShortcutsTitle7 has been updated to allow JAWS to read out the "Showing all reports" title.
SR-B426 · Issue 271503
Error label highlighting corrected for inside grid
Resolved in Pega Version 7.2.2
The correct label associated with the UI element in which the client side error was thrown was not highlighted when inside a grid. To fix this, the function findLabelFor has been updated to handle the case specific to the grid, as the error elements ID and the label's 'for' attribute were never equal due to the 'for' attribute changing value when used on repeating elements within a grid.
SR-A75957 · Issue 250773
D_pyUserWorklist Code performance improvement
Resolved in Pega Version 7.2.2
The D_pyUserWorklist Code was not checking whether a worklist was empty or not and was doing a compare to get data. A check has been added to improve performance.
SR-A94113 · Issue 261063
D_pyUserWorklist Code performance improvement
Resolved in Pega Version 7.2.2
The D_pyUserWorklist Code was not checking whether a worklist was empty or not and was doing a compare to get data. A check has been added to improve performance.
SR-A77536 · Issue 256600
Error section in tab groups receives correct focus
Resolved in Pega Version 7.2.2
The displayFormErrors function of the Perform harness was not properly holding focus in sections having tab groups if accessibility was enabled; the focus would jump from error table to the first tab. This has been fixed.
SR-A20694 · Issue 256036
Added overlay modal dialog check in service intent
Resolved in Pega Version 7.2.2
The enter key press was not working as expected when searching for a new service intent. While another service intent was currently open, 'enter' jumped back to the open service intent. This has been corrected by adding a target check for an overlay modal dialog.
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.
SR-A101069 · Issue 270595
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.