SR-A12087 · Issue 224463
Accessibility focus improved for DashboardTree
Resolved in Pega Version 7.2
Accessibility tree grid handlers were not allowing focus on the Expand/Collapse icon in a portal tab that used a pyDashboardTree section with the PegaWAI ruleset. The element focus methods have been updated to correct this.
SR-A12087 · Issue 227542
Accessibility focus improved for DashboardTree
Resolved in Pega Version 7.2
Accessibility tree grid handlers were not allowing focus on the Expand/Collapse icon in a portal tab that used a pyDashboardTree section with the PegaWAI ruleset. The element focus methods have been updated to correct this.
SR-A12450 · Issue 224438
Trailing line removed from breadcrumb
Resolved in Pega Version 7.2
When creating a work item, the breadcrumb showed a trailing line when it displayed "Review and Confirm". This was an issue with a page change class in middle of a screenflow, and has been fixed.
SR-A5367 · Issue 226749
Enhanced accessibility for sorted columns in Repeating Grids
Resolved in Pega Version 7.2
Enhancements have been added to enable JAWS to consistently read the header labels and sort status of columns in a Repeating Grid. The sort and filter status of the columns can be now read using TAB / SHIFT + TAB.
SR-A5367 · Issue 217918
Enhanced accessibility for sorted columns in Repeating Grids
Resolved in Pega Version 7.2
Enhancements have been added to enable JAWS to consistently read the header labels and sort status of columns in a Repeating Grid. The sort and filter status of the columns can be now read using TAB / SHIFT + TAB.
SR-A9731 · Issue 224437
Pick a Value window resized for proper display
Resolved in Pega Version 7.2
On clicking on the criteria field of any report (listview / SummaryView), the 'Pick Values' modal window opens up for user to select values. This window is sized smaller by a percentage than the ClientHeight to ensure the popup can display the content within the height of the current window. After upgrade, the modals appeared with a default height of 96% and caused the Apply / Cancel / Submit buttons to either be partially visible or not visible at all, which did not allow user to select values. This has been resolved by updating the "launchpickavalue" method defined in "Rule-Obj-HTML.Wizard_Parameters" rule to set the iframe height to 93%.
SR-125113 · Issue 203182
Localized labels displaying in Safari
Resolved in Pega Version 7.2
Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.
SR-A7487 · Issue 221276
Better Japanese font handling in CreatePDF smart shape
Resolved in Pega Version 7.2
The CreatePDF smart shape was not able to properly parse Japanese font characters in section data. This has been corrected by changing the default font to 'MS PGothic' which better supports Japanese.
SR-A8298 · Issue 218280
Resolved connection reset error on nested grid harness refresh
Resolved in Pega Version 7.2
When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.
SR-A8430 · Issue 218096
Resolved connection reset error on nested grid harness refresh
Resolved in Pega Version 7.2
When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.