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-D76927 · Issue 541424

VirusCheck added to all Pulse uploads

Resolved in Pega Version 8.4.1

The upload file activity has been updated to invoke VirusCheckActivity for all Pulse uploads.

SR-D77268 · Issue 542339

Updated URL opening for iOS 12 & 13

Resolved in Pega Version 8.4.1

Attempting to open a URL did not work on iPad/iPhone with iOS 12 and 13 and PIMC version 8.3.500. This has been resolved by updating previewPIMCAttachmentOnline function to handle URL opening by using the application.openurl function.

SR-D81859 · Issue 543766

Maps and signatures inside layout groups scroll correctly

Resolved in Pega Version 8.4.1

A map configured in the screen was getting grayed out while scrolling horizontally. Analysis showed that when an address map is inside a layout group, the layout group swipe was triggered instead of scrolling. To resolve this, the target parent now has the data attribute "data-nogestures" = true so the layout group swipe will not be triggered. This will also prevent swipe on signature while scrolling horizontally.

SR-D85551 · Issue 548077

Resolved touch events issue with updated Google Chrome

Resolved in Pega Version 8.4.1

After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.

SR-D85780 · Issue 547815

Corrected iosVersion handling for getDirections

Resolved in Pega Version 8.4.1

When opening the map function in the iPhone app, it first navigated to Google maps but clicking on 'get directions' opened Apple maps. This was traced to pzpega_control_actions_getDirections. When using the getMapURL function the value being assigned for iosVersion dictates the behavior: If the iosVersion is greater than 8 it opens Google maps, else Apple maps. However, an error caused the value to be sent as string instead of integer, causing the iosVersion check to fail. This has been corrected.

INC-182423 · Issue 691799

Pull to refresh disabled during case submission

Resolved in Pega Version 8.7.1

Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.

INC-183485 · Issue 692518

ClientCache performance optimization

Resolved in Pega Version 8.7.1

In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.

INC-195519 · Issue 698497

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.7.1

Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.

INC-199354 · Issue 696718

Corrected pulse comments rendering in mobile

Resolved in Pega Version 8.7.1

When using mobile, clicking the number on the Pulse comments section was not responding and conversations inside a comment were not visible. This has been resolved by updating pypega.social.js and pypega.social.css so the section renders correctly.

INC-199891 · Issue 695892

Updated handling for parametrized data pages on offline mobile app

Resolved in Pega Version 8.7.1

After update, the UI in the offline mobile app was showing .pyStandardValue and not the LookUpValue. This was caused by parametrized data pages not getting populated when used on UI components so the custom populator was not getting called, and has been corrected.

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