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.

INC-133301 · Issue 580677

Resolved authorization request errors on mobile

Resolved in Pega Version 8.2.8

After upgrading and rebuilding the APK with the HC Client Version – 7.41.8-SNAPSHOT, numerous "PYREDIRECTAUTHORIZATIONREQUEST" alerts during mobile interactions caused system performance issues. This was traced to a change in the handling for OAuth2 tokens and related to missing pyClientID column in the database table which forced the system to read all records from the table, and has been resolved.

INC-135159 · Issue 580673

Logic updated for deepMergeObj API

Resolved in Pega Version 8.2.8

Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.

INC-144948 · Issue 602275

Resolved JBoss memory leak

Resolved in Pega Version 8.2.8

JBoss logs indicated connection leaks. This has been resolved by limiting the scope of instance of ActionProvider, DataSyncRequestParser to a try-with-resources block which ensures that all resources are released.

SR-D95638 · Issue 556964

Added handling for mobile SharePoint attachments

Resolved in Pega Version 8.2.8

When an application was using SharePoint to store the attachments, adding an attachment in an offline-enabled mobile app and then synching resulted in the mobile app crashing if the user re-logged in and launched the same work object. This was due to the attachment handling. Attachments are downloaded during synchronization and they are base64 encoded: when a mobile phone processes the synchronization response, it decodes the base64 encoded attachment and saves the data in internal storage. In this scenario, attachments retrieved from SharePoint (REST Service) use a base64 conditional encoding that is different than in case Repositories or Pega Database storage. To resolve this, a check has been added to determine whether the base64 text contains newline characters, and if so the text is merged into one line.

SR-D37275 · Issue 519028

Enabled PDF attachment for iPad Safari

Resolved in Pega Version 8.2.6

It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.

SR-D42243 · Issue 524579

Added handling for offline mobile attachments using PRFiles and Repositories

Resolved in Pega Version 8.2.6

Attaching a file on mobile and then immediately clicking on it to open it either did not open the attachment or the attachment opened and then the app stopped working with a "Sync Failed" error. Attachments were not synchronized on the server, and when synchronization was re-tried the attachment was duplicated on attachment list. This was traced to the system being configured to use PRFile API for synchronizing attachments along with Repositories to store attachments; when the processing "commitAttachment" action was processed, it called the Work-.AttachFile activity to finalize attachment upload, but the activity was called without the mandatory attachment InputStream required when using PRFile + Repositories. This has been resolved by ensuring there is a call to Work-.AttachFile with InputStream in cases where PRFiles and Repositories are enabled.

SR-D50584 · Issue 518442

Security added to retrieving operator list by URL extension

Resolved in Pega Version 8.2.6

It was possible to append information to the application URL which allowed an unauthenticated user to find a list of operators. This has been corrected, and will now result in the message "There has been an issue; please consult your system administrator."

SR-D56148 · Issue 537404

Corrected map zoom issue with iOS13

Resolved in Pega Version 8.2.6

After including a map control with markers in an application for iOS13, viewing via a mobile app and zooming introduces a gray bar across the map. This has been resolved by setting transform translateZ to the div of address map.

SR-D68810 · Issue 532133

Google street view enabled

Resolved in Pega Version 8.2.6

The Google Maps street view control has been enabled by setting streetViewControl to true in pzpega_ui_addressmap .

SR-D70674 · Issue 535483

Handling added for mobile upload of filename containing dots

Resolved in Pega Version 8.2.6

An issue with uploading a file name containing dots (such as 2019.12.12) while using the mobile browser has been resolved by updating the AttachFile activity in the propertyExist function.

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