Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-118077 · Issue 170104

Excessive logging addressed in Pega Mobile 4.3

Resolved in Pega Version 7.1.7

In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.

SR-A76763 · Issue 252485

Ensured Dirty pop up appears for mobile log off

Resolved in Pega Version 7.2.2

While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return 'if dirty' to resolve this.

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.

SR-A91240 · Issue 259814

Corrected mobile app login load stream error

Resolved in Pega Version 7.2.2

In some circumstances, a "Failed to load stream" error was appearing when attempting to log in on the Mobile App. To fix this, the login process has been made more robust with the addition of the isSyncProcessingInProgress function to check sync progress, and a check has been added for the panel harness being set in the HCLoadManager js.

SR-A77474 · Issue 253967

Online-only Mobile harness always displays appropriate offline message

Resolved in Pega Version 7.2.2

In the Mobile app, clicking on an online-only harness (check box for online selected) from the navigation menu, then going offline and clicking it again resulted in an alert (0:Communication failure) with no other description. The issue was that in multithread context with possible switching between threads, the network status was not properly updated in desired pxRequestor page. The system will now loop through all the threads and update the pegaserveravailability status for the correct pxRequestor in the Client Cache and correctly display the message "Cannot perform this operation when offline".

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us