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-167747 · Issue 649658

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-167871 · Issue 666297

Desktop browser java render error corrected

Resolved in Pega Version 8.7

Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.

INC-168414 · Issue 641036

Web Mashup works from nested iframe

Resolved in Pega Version 8.7

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

INC-168695 · Issue 643017

String conversion logic updated for toFixed function

Resolved in Pega Version 8.7

The toFixed function of pzpega_ui_formatNumber.js was incorrectly converting a string while formatting the value. This potentially caused the UI to hang until manually refreshed. To resolve this, the logic has been updated to convert the string to a number before calling toFixed().

INC-169012 · Issue 651257

VMWare workspace One Mobile support added

Resolved in Pega Version 8.7

Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.

INC-169203 · Issue 646097

Robotics Desktop Automation correctly runs on subsequent tabs

Resolved in Pega Version 8.7

When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.

INC-169545 · Issue 649519

Localization updated for decimal slider

Resolved in Pega Version 8.7

When using the Indonesian locale, selecting the range on a slider which allowed selection of a decimal / double value that was then displayed in another textbox caused the value to increase incrementally and the slider always showed the end max. Investigation showed that this was caused by the handling of the comma decimal separator used in Indonesia, and has been resolved by updating the handling to ensure the slider value is converted to the respective locale.

INC-169796 · Issue 649263

Null check added for pyModes setting

Resolved in Pega Version 8.7

The column filtering function was not working after update from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.

INC-169866 · Issue 653548

View content type updated to FIELD

Resolved in Pega Version 8.7

After update table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after upgrade to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.

INC-170258 · Issue 645043

Removed unneeded query parameter in UI

Resolved in Pega Version 8.7

When using an Ajax container without a dynamic container, a refresh harness / section event call related to pyBlockUnregisteredRequests was not being properly registered, resulting in a 403 error and the message "Unregistered request encountered ..". This was traced to a "pyDataTransform=" query parameter that was present in the PZPEGA_UI_MICRODC file, and the parameter has been removed to resolve this issue.

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