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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-194932 · Issue 686277

Handling updated for offlineWorkIDs map

Resolved in Pega Version 8.8

Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.

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.

INC-206049 · Issue 703469

Resolved activity registration error for Scan Barcode/QR Code

Resolved in Pega Version 8.7.1

Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.

INC-182423 · Issue 691798

Pull to refresh disabled during case submission

Resolved in Pega Version 8.5.6

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-187230 · Issue 672472

Resolved exception during LDP processing

Resolved in Pega Version 8.5.6

A ConcurrentModificationException was appearing during the processing of Large Data Pages. This has been resolved with the addition of a lock on clear method in ConcurrentReplicatedPage.

INC-194932 · Issue 689290

Handling updated for offlineWorkIDs map

Resolved in Pega Version 8.5.6

Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.

INC-195519 · Issue 698496

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.5.6

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

INC-195601 · Issue 685769

Basereference context available for attach content control

Resolved in Pega Version 8.5.6

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

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