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-153152 · Issue 613687

Privilege on table cells updated for non-template mode

Resolved in Pega Version 8.5.3

When using a table sourced from a report definition where certain cells were hidden or shown based on privilege, the configuration worked as expected in regular tables but did not work correctly for optimized tables. This was traced to an issue with image control rendering in non-template mode related to privileges for the image, and has been resolved by updating the pzgenerateicon Rule-Utility-Function.

SR-C30049 · Issue 373668

JAWS properly reads icon column in expand pane

Resolved in Pega Version 8.1

When a grid is configured with Expandable rows master detail, with an icon for the "expand / collapse" icon per row, a column is reserved for the icon. However, when using JAWS table shortcuts, the column header reserved for the icon was read out as blank. This was due to the expand pane header not having the required aria attributes, and these have been added in the GenerateGridHTML function.

SR-C97873 · Issue 437280

Added check to maintain key value when using collapseAllMenu in child navigation menu

Resolved in Pega Version 8.3

After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.

SR-D392 · Issue 438871

Behavior reset for using getLocalizedValue with an input string containing parentheses

Resolved in Pega Version 8.3

After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.

SR-C93572 · Issue 440078

Search initialization logic updated to ensure consistent node member information

Resolved in Pega Version 8.3

The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.

SR-D16762 · Issue 486032

Search initialization logic updated to ensure consistent node member information

Resolved in Pega Version 8.3

The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.

SR-D19944 · Issue 488359

Search initialization logic updated to ensure consistent node member information

Resolved in Pega Version 8.3

The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.

SR-D19945 · Issue 488360

Search initialization logic updated to ensure consistent node member information

Resolved in Pega Version 8.3

The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.

SR-D19944 · Issue 491156

Search initialization logic updated to ensure consistent node member information

Resolved in Pega Version 8.3

The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.

SR-D22885 · Issue 494166

Added check for empty class properties to report scheduler

Resolved in Pega Version 8.4

A report that was looking for events in the most recent X hours by using the "Difference In Hours" filter function ran in the foreground but failed with an exception when running under the scheduler. The same report ran as expected in background without the filter. This was traced to a classname property not being set on the clipboard, and has been resolved by adding a check for empty classes on the clipboard when scheduling a report.

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