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-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.

INC-206049 · Issue 703470

Resolved activity registration error for Scan Barcode/QR Code

Resolved in Pega Version 8.5.6

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-163628 · Issue 660555

Corrected view generation logic for nested subsections

Resolved in Pega Version 8.5.6

Performing a save-as of the pyCaseMainInner work- section in the UIKit resulted in an infinite loop in the view generation logic. This was traced to the system recursively generating views from subsections, and has been resolved by updating the logic so a view is only generated for valid py prefixed sections on save of a section.

INC-164620 · Issue 640658

jQuery variable handling updated for mashup

Resolved in Pega Version 8.5.6

After upgrade, embedded mashup was not working. The browser console log showed the error "Uncaught TypeError: $ is not a function at pega.web.manager._initGadgets (PegaReg?pyActivity=pzIncludeMashupScripts:69)". The $ function belongs to the jQuery library, and investigation traced this to a difference in variable handling. This has been corrected by updating the referring jQuery to use the variable 'jQuery' instead of '$'.

INC-164775 · Issue 681238

Web page generation security updated

Resolved in Pega Version 8.5.6

Cross-site scripting protections have been enhanced around web page generation.

INC-165992 · Issue 657690

Table Filter save uses correct harness

Resolved in Pega Version 8.5.6

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

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