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-D71408 · Issue 534932

DIrty check flag triggered by adding columns and filters

Resolved in Pega Version 8.1.8

If a report was edited and closed without saving, the dirty check worked as expected. However, if new columns or filters were added and the report closed without saving, the dirty check did not appear. This has been resolved by updating the check logic.

SR-D53176 · Issue 541793

Error when adding function filter will persist

Resolved in Pega Version 8.1.8

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

SR-D76204 · Issue 543591

Index conflict resolution logic updated

Resolved in Pega Version 8.1.8

After configuring a dedicated index on delivered Class - PegaCA-Interface-Contact, trying to generate the index resulted in an error indicating a type conflict in delivered classes/properties. This has been resolved by updating the conflict resolution logic.

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.

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