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.

SR-A100292 · Issue 270065

Select Values from join properly displayed on chart

Resolved in Pega Version 7.3

In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.

SR-A103079 · Issue 273545

Check added for RD date time values

Resolved in Pega Version 7.3

An exception was generated when running RD by choosing the relationship for a datetime property as "Is not null" in filter conditions before displaying the data. This has been fixed with the addition of a check for the date time value.

SR-B10828 · Issue 282620

Surrounding spaces trimmed from property labels to ensure localization

Resolved in Pega Version 7.3

Property labels in the add reports screen were not localized because the value was given as "Contact Channel " with a trailing space. To resolve this, the pzReportExplorerNode control has been updated to trim leading and trailing spaces before performing localization.

SR-B11379 · Issue 281867

Backwards compatibility added for imported RDs to ensure Export to PDF option given

Resolved in Pega Version 7.3

After upgrade, the Export to PDF option was not visible under actions. This occurred when the Report Definition exported from an earlier version did not contain the property "pyUI.pyUserInteractions.pyShowDataOnly" in the rule XML, causing the 'when' rule pzShowExportToPDFLink to be evaluated to false. To correct this, the pzUpgradeOnOpen Data-transform has been modified to create the pyShowDataOnly property and assign it to false if it was not present or if the value is empty/null so the Export option will appear as expected.

SR-B11675 · Issue 284417

Cursor correctly changes to hand in Report Wizard popup

Resolved in Pega Version 7.3

The hand icon was not displaying as expected when the cursor was placed on the Search icon in the "Report Wizard" pop up window. This has been fixed.

SR-B11776 · Issue 289458

Report results populating as expected for tree grid

Resolved in Pega Version 7.3

Report definition results were not populated in the tree grid structure but were populated in the spread sheet structure. This was caused by a difference in handling for formatting a column with empty values, and has been changed.

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-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-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.

SR-B13775 · Issue 293697

Resolved error in adding Association's Page Property in report browser

Resolved in Pega Version 7.3

Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us