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-183485 · Issue 680133

Performance improvements for mobile app refresh

Resolved in Pega Version 8.7.1

After update, performance issues were seen on the mobile app with processes that required a refresh. This has been addressed by updating the process for selecting the DOM element to improve the performance.

INC-183672 · Issue 701869

Corrected vertical scroll bar for iPad Mashup page

Resolved in Pega Version 8.7.1

After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.

INC-186081 · Issue 675206

Report filter popup displays correctly

Resolved in Pega Version 8.7.1

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

INC-187617 · Issue 692543

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

INC-188029 · Issue 691097

Rich Text Editor will pause until instance is ready for interaction

Resolved in Pega Version 8.7.1

Outbound email was intermittently appearing blank creating replies using pyReply section. This was traced to the Rich Text Editor not loading completely before the interaction, and has been resolved by adding a brief pause that will temporarily disable the Rich Text Editor until the instance is ready.

INC-188212 · Issue 674104

Localization added for FilterUILabel

Resolved in Pega Version 8.7.1

Filter values were not rendered in French for French users for Case Status in all the grids. This has been resolved by updating the localization values in the pzFilterUiLabel control.

INC-189748 · Issue 694737

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

INC-189748 · Issue 701458

Websocket disconnect code logged

Resolved in Pega Version 8.7.1

An update has been added which will log the websocket disconnect code for additional diagnostic information.

INC-190609 · Issue 681324

Added null check for routeToParent in Mashup

Resolved in Pega Version 8.7.1

After update, mashup was loading in a different context. This has been resolved by adding a null check in routeToParent in webwb_pega_desktop_support.

INC-190708 · Issue 695488

Save works on Ajax container without Dynamic container

Resolved in Pega Version 8.7.1

After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.

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