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-D91964 · Issue 551091

Negative values in optimized table filters show markup

Resolved in Pega Version 8.2.7

HTML markup was shown in the filter popup when Number control was used in a Table cell and there were negative values in the cells at runtime. This was traced to work done on template grid filtering, and has been corrected.

SR-D92571 · Issue 553114

Corrected ReportBrowser refresh section

Resolved in Pega Version 8.2.7

After bringing up the popup menu on a report shortcut in the report viewer and then dismissing it, the gear icon on the shortcuts in the upper section of the report browser stopped responding. This has been resolved by updating the system to refresh the pyReportBrowserInner section instead of pyReportBrowserAll.

SR-D95367 · Issue 560739

Expanded debug logging for exception blocks

Resolved in Pega Version 8.2.7

In order to enhance debugging, logging has been expanded to capture more detail on exception blocks.

SR-D95410 · Issue 556323

CSS added for currency display place holder when empty

Resolved in Pega Version 8.2.7

After update, currency cell properties displayed a blank space instead of the previous "--" if the value was empty. This was traced to templating and markup changes that resulted in styles related to adding hyphens not getting applied to the inner span, and has been resolved by adding the necessary CSS.

SR-D96224 · Issue 556780

Validation error messages correctly cleared

Resolved in Pega Version 8.2.7

The error message on a checkbox field, radio button, or text area with a on-change post value was persisting even after the correct input was provided. This occurred when the area had a caption, and was due to an additional wrapper span that caused the error div to be the span's sibling instead of the span itself. In the post value success, the system checked whether the error div was present in the area's parent, i.e. span, and when no div was returned the error msg was not removed. It was possible to add an action 'Refresh this section' on change as a workaround, but this has been corrected by updating the system so that Instead of checking the error div in src.parentNode, it will access the correct parentNode using 'closest' and check for the error div.

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