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.

SR-A1705 · Issue 205449

Fixed scrumboard intermittent failure

Resolved in Pega Version 7.1.9

After upgrading, it was seen that the scrumboard would intermittently fail to load, partially displaying and then hanging if the columns did not fit within the window boundaries due to the number of elements. This was traced to an error in the functionality that resizes parts of the scrumboard, and has been fixed.

SR-A11329 · Issue 222587

Fixed popup navigation menu scrolling

Resolved in Pega Version 7.2

When a button was configured to pop up the navigation menu on click, the menu was fixed on the screen even after scrolling the screen up and down. This was caused by a div inconsistency in the function split button constructor method(SplitButton), and has been fixed.

SR-A23012 · Issue 242327

pega.u.d.onViewUpdatecorrectly triggered from Master-Detail

Resolved in Pega Version 7.2.1

The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.

SR-A23012 · Issue 243963

pega.u.d.onViewUpdatecorrectly triggered from Master-Detail

Resolved in Pega Version 7.2.1

The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.

SR-A97999 · Issue 264513

Decision tree handles special characters in the property label

Resolved in Pega Version 7.2.2

Attempting to open a Decision Tree with special characters in the property label generated an exception. This was due to the property label code not properly handling characters such as $ and \ and has been fixed by using the Matcher.quoteReplacement function Instead of directly using the string in replaceAll.

SR-B10051 · Issue 279714

Agent management detail corrected to show all nodes

Resolved in Pega Version 7.3

Drilling down to the agent detail from the Agent management page was showing only the current node when agents from the other nodes should have been displayed as well. This was caused by an error in the DataAgentIndex function, and has been corrected.

SR-B74586 · Issue 325692

Fixed save-as for RD with sub-report and join

Resolved in Pega Version 7.3.1

A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.

SR-B85963 · Issue 339603

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

SR-B85963 · Issue 338180

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

SR-B85973 · Issue 338040

Cleaned up unneeded Connect-REST logging

Resolved in Pega Version 7.4

Each Connect-REST execution was writing a log entry in the Pega rules log file. Though there was no functional impact, these error messages were misleading and were filling the log. To resolve this, the PRServiceUtils has been modified to use startRecursiveTiming().

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