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.

SR-D3405 · Issue 439259

URL construction logic updated for Tracer

Resolved in Pega Version 8.2.2

When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.

INC-180891 · Issue 663513

Zip compression added for tracer XML

Resolved in Pega Version 8.5.6

After upgrading from Pega 7 to Pega 8, attempting to save and download a trace session would run for a time before pausing and displaying the message "Operation failed. Network error". Investigation showed the tracer was generating a very large XML file which was consuming the heap and causing the issue. To resolve this, an update has been made that will reduce memory usage by using GZip compression on the file. The new behavior will be to always zip tracer XML by default.

SR-C18637 · Issue 360155

Logic repaired in toGMT RUF

Resolved in Pega Version 8.1

A logic error in the toGMT RUF has been fixed to correctly handle dates before the epoch date.

SR-D16678 · Issue 511271

FTPS server connections repaired

Resolved in Pega Version 8.4

When attempting to connect and transfer files to an FTPS server, errors were seen and the files did not transfer. This has been corrected by updating the system to send a PSBZ command before sending PROT in the FTPS implementation.

SR-D37757 · Issue 507968

Pulse delete icon repaired

Resolved in Pega Version 8.4

After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.

SR-D37757 · Issue 507967

Pulse delete icon repaired

Resolved in Pega Version 8.2.4

After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.

SR-D37757 · Issue 507966

Pulse delete icon repaired

Resolved in Pega Version 8.3.1

After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.

INC-193071 · Issue 686647

Find by ID functionality repaired

Resolved in Pega Version 8.5.6

After update, the Find by ID Functionality was not working as expected. This was an unintended side effect of work done around the inheritance of default values when the portal pyPortal.pyDesktopType was set to Composite, and has been resolved by modifying the previous work to move the check to verify if the pxCurrentWorkPool== "" to a later step.

INC-208729 · Issue 711401

Repaired Perform for 'Assignments with Errors'

Resolved in Pega Version 8.6.4

The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.

INC-208729 · Issue 711402

Repaired Perform for 'Assignments with Errors'

Resolved in Pega Version 8.7.2

The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.

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