SR-A20018 · Issue 250155
Drill down fixed for use with "Do not display group headings"
Resolved in Pega Version 7.2.2
When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.
SR-A75959 · Issue 252005
Error messages correctly clear after copying report
Resolved in Pega Version 7.2.2
When trying to perform "Copy" of a report into the same category using the report shortcut menu from case manager portal, the error "This report shortcut already exists in this category. Please select a different category" appeared. The error persisted on the screen (harness) even after clicking on "Cancel" of Modal Dialog, and after cancelling the "Copy Report Shortcut" modal in the Report Browser with an error in the modal's form, the errors reappeared at the top and bottom of the Report Browser itself. This was due to validation messages being copied from the temporary shortcut page to the primary page so that submitting the form was prevented when there were errors, but these messages should have been cleared from the primary page when cancel was clicked. This has been fixed.
SR-A24855 · Issue 253637
Fixed Export to Excel with Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using Microsoft Internet Explorer 11, Export to Excel from report definition generated the sporadic error "Unable to read file." After consulting with Microsoft, the cause was traced to the browser attempting to open the file before it was downloaded, and code has been added to check for the browser and handle the download/open appropriately.
SR-A98702 · Issue 266129
Minor update to help doc for property optimization run time
Resolved in Pega Version 7.2.2
The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.
SR-A89212 · Issue 257059
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A89212 · Issue 257378
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A90165 · Issue 258244
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A80668 · Issue 256820
DateTime Accessibility improved for iOS
Resolved in Pega Version 7.2.2
Accessibility has been improved for the DateTime control in iOS, allowing Input, Calendar image, Show Previous Month, Show Previous Year, Show Next Month, and Show Next Year buttons to be read out correctly.
SR-A93531 · Issue 266554
Corrected mobile login issues after sync
Resolved in Pega Version 7.2.2
After forcing a full sync, users already logged into the app (i.e. packaged data is present in client) observed login issues thereafter while new users did not. This has been corrected by updating the logic in the pzpega_ui_doc_HCLoadManager getOfflineStorageCount API call.
SR-A91327 · Issue 259570
Modified cookie name handling to clear operator sync between logins
Resolved in Pega Version 7.2.2
Full sync was happening only at the very initial time the user tried to login and not at every login, creating a scenario where an operator was given a synchronization package for the last logged user. This was an error with part of a session cookie name being hardcoded and not being cleared when the previous user logged out, and the logic has been corrected.