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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B12714 · Issue 294429

String comparison logic updated for complex property references

Resolved in Pega Version 7.3

Running a report that has a single page property (.Address.pyCountry) generated an error and the report shows no results. It worked correctly if the column is removed or a filter was added on instances that have .Address.pyCountry not null. This was an issue related to string comparisons, and has been resolved by updating the logic for parsing of complex references in UDFs.

SR-B12737 · Issue 283588

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B12737 · Issue 282869

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B12770 · Issue 285068

Text areas display OOB error message as expected

Resolved in Pega Version 7.3

In the Text area control, the Pega OOB error message was not generated when there was no value in the required text area. This was an issue with minimum characters validation not considering an empty string to be a valid one, and has been corrected.

SR-B13016 · Issue 284134

Report title shows for exported Excel; display report label name reverted

Resolved in Pega Version 7.3

Exported Excel reports were not showing the report title if the "display report filters" checkbox was unchecked in the RD rule. If the box was checked, the report title turned up in the Excel sheet, but the report UI showed an unnecessary blue bar if none of the filter criteria were set to be displayed as per business needs. The missing report title was traced to an error in the "display report filters" checkbox, and has been fixed. Additionally, the 'display report header' label in the pzReportViewerUserActions section had been recently modified to read 'display report filters', which was misleading - that change has been reverted.

SR-B13315 · Issue 284499

Accessibility updated for flow action label

Resolved in Pega Version 7.3

Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.

SR-B13315 · Issue 284499

Accessibility updated for flow action label

Resolved in Pega Version 7.3

Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.

SR-B13450 · Issue 284622

Null check added to joins of UserWorkList columns

Resolved in Pega Version 7.3

When attempting to join a pyUserWorkList Report definition with work class properties, blank values in the pyUserWorkList columns caused a Null Pointer exception on click of the filter icon for joined class properties/columns. This has been resolved by adding a null check.

SR-B13517 · Issue 293343

Icon alignment fixed in grids with skin inheritance

Resolved in Pega Version 7.3

The Header Title and the Collapsible Icon of a grid were misaligned due to an error in skin inheritance. The pzTemplateNewSkin1 legacy standard format has been changed to correct this.

SR-B13606 · Issue 287616

Angle brackets escaped for RD drill down

Resolved in Pega Version 7.3

In a report definition with drill down, if the column parameter had a value that used the wrong parameter was getting passed in Query. This was due to the characters getting converted into their HTML equivalent < and >., and the character escaping has been corrected to resolve this.

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