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-183712 · Issue 674133

IndexOf updated to remove extra bracket

Resolved in Pega Version 8.6.3

When trying to open a section rule, content was not loading if values were derived using a report with column containing a function. This occurred when the section rule included a table referencing the report where one of the section table cells had its Property value set to the function. To resolve this, indexof has been updated to not include closing > as the HTML returned from the server now includes an attribute on that tag.

INC-183963 · Issue 673444

Corrected Close button accessibility label

Resolved in Pega Version 8.6.3

The screen reader was reading the Close button as 'Add Content. This has been corrected.

INC-184104 · Issue 682357

Cosmos Report Browser list updates during current session

Resolved in Pega Version 8.6.3

The Cosmos Report Browser list section was using a cached list of reports that did not update to reflect created or deleted reports until after logout and new login. This has been resolved by adding the pzInvalidateRBDataPages activity for harness initialization to update the reports list during the current session.

INC-184109 · Issue 671193

Handling updated for customDateTime formatting

Resolved in Pega Version 8.6.3

When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.

INC-185563 · Issue 670846

"Manage content" dialog box tab index is consistent

Resolved in Pega Version 8.6.3

The tab ordering for the "Manage content" (document upload) dialog box was not consistent. This has been resolved by updating pzModalTemplate to list the submit, cancel, etc, buttons in a consistent order.

INC-185782 · Issue 675529

Tab Names correctly displayed in Ajax Container

Resolved in Pega Version 8.6.3

After configuring Action Set with an Ajax container to open a harness and then configuring the same harness name for multiple action items, the first open happened as expected but the following action items were not opening properly and were still pointing to the old tab instead of showing the new tab names. This was traced to actionMetadata.Name not having the correct value, and has been resolved by explicitly updating the tabName value in the "Display" action with the needed actionMetadata.Name.

INC-186072 · Issue 677410

Updated ClientDynamicData HTML Rule

Resolved in Pega Version 8.6.3

After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.

INC-186930 · Issue 679707

Mouse cursor remains consistent when expanding repeating grid column

Resolved in Pega Version 8.6.3

After update, expanding the last column of a repeating grid changed the mouse cursor. Refreshing the portal restored the original cursor. This has been resolved by adding the last column to the disableColumn array.

INC-187015 · Issue 678383

Listener implementation updated for closing modal dialog popup

Resolved in Pega Version 8.6.3

It was not possible to close the popup window in a local action when using a flow in a modal dialog action in Cosmos. This was traced to a missed use case for closing a modal dialog opened from a tertiary container, and has been resolved by updating the listener implementation in the ModalFlowTemplate.

INC-187617 · Issue 692544

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.6.3

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.

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