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-182726 · Issue 677531

CORS DSS settings corrected for Constellation

Resolved in Pega Version 8.6.3

After moving to the new HIPPA edition, the developer work area in Constellation appeared as blank under Channel-Portal-Landing Pages. This was traced to a DSS setting issue when using cross-origin resource sharing (CORS), and has been resolved.

INC-182803 · Issue 679725

SearchKeyword assed to HandleInput allow list

Resolved in Pega Version 8.6.3

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 675312

Update Language Pack for correct direct web access link localization

Resolved in Pega Version 8.6.3

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-183163 · Issue 676253

Optimized table search updated

Resolved in Pega Version 8.6.3

Search functionality that can be enabled from tables after selecting the "Optimize" checkbox was not working correctly. This was traced to a potential issue getting the search parameter passed into the activity the section uses, and has been resolved by updating the system to get the element from pega.ctx.dom when pyFlowActionHTML div does not exist.

INC-183485 · Issue 680134

Performance improvements for mobile app refresh

Resolved in Pega Version 8.6.3

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-183530 · Issue 669265

Corrected logging of jars added during node startup

Resolved in Pega Version 8.6.3

Logging regarding jar additions was being skipped when user-configured class path elements were added to the compile time classpath during node startup. This was an inadvertent side effect of previous work and has been resolved by adding the log statement "Skipping to add jar '%s' to compile time classpath as it was already present".

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.

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