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-178831 · Issue 697057

Ensured correct context for multi-select

Resolved in Pega Version 8.7.1

When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.

INC-182287 · Issue 670743

Decimal places showing correctly after update

Resolved in Pega Version 8.7.1

After selecting Decimal places in the Property Panel in the section for a particular property, the decimal places were not added on tab-out at runtime. Decimal places were correctly applied if no property was specified. Investigation showed that an explicit post value call was initiated to apply the read-only formatting, but that call was suppressed by other conditions related to updating the Pega version. To resolve this, an unneeded data-auto-formatting conditional check has been removed.

INC-182803 · Issue 679724

SearchKeyword assed to HandleInput allow list

Resolved in Pega Version 8.7.1

After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.

INC-182874 · Issue 675311

Update Language Pack for correct direct web access link localization

Resolved in Pega Version 8.7.1

When a direct web access (DWA) link was generated for an external user to perform an action on an external assignment, the shared link was corrupted when used with localization on the receiving system. This was due to the JSP fragment in the correspondence not being properly translated during localization. To resolve this, please access the most recent Language Pack available from https://community.pega.com/marketplace/language-packs/pega-platform

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.

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