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-205336 · Issue 698302

Logging level updated to resolve warning

Resolved in Pega Version 8.5.6

After applying a recent security update, an exception was logged indicating "WARN Error while converting string [USAGE] to type [class org.apache.logging.log4j.Level]". The logging level "USAGE" has been changed to "info" to resolve this issue.

INC-207309 · Issue 704300

Clipboard page handling updated for encrypted values

Resolved in Pega Version 8.5.6

When retrieving data that contained encrypted properties, the clipboard page either did not load, or if it did load the encrypted properties were not listed on the clipboard. This was traced to use of a read only data page, and has been resolved by updating pzRemovePWD with handling for read only pages.

INC-207818 · Issue 701749

Security updated for @baseclass

Resolved in Pega Version 8.5.6

After update, searching for a baseclass 'when' rule returned no results. Listing the rules under baseclass in App Explorer resulted in the error "Applies To: The Class with key value(s) %40baseclass does not exist". This was an unintended side effect of security updates, and has been resolved by creating an exception path for "@baseclass".

INC-209426 · Issue 706805

GetFunctionsForLibrary retrieves 10,000 rows

Resolved in Pega Version 8.5.6

Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.

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.

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