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-A6581 · Issue 216111

Encoding added to handle multi-byte characters in file names exported to Excel

Resolved in Pega Version 7.2

If a report title contained multi-byte characters such as Chinese fonts, exporting the report to Excel resulted in an incorrect file name is incorrect. To correct this, UTF-8 encoding has been added to pzViewExcelData to handle these characters.

SR-A2832 · Issue 211426

Expressions allowed in trend report config

Resolved in Pega Version 7.2

Configuring a trend report using an expression for the summary view caused the execution error "Failed to find a 'RULE-EDIT-INPUT' with the name; no rules with this name were found in the rulebase". This has been resolved by reworking the 'if' condition in the JS method editInput.

SR-A6872 · Issue 216420

Filtering modified to allow searches with two-step filtering

Resolved in Pega Version 7.2

If a List View was being filtered by two columns, entering the first filter value into the "Search" text box (as opposed to selecting values from the pick list) in the filter popup caused the second filter operation to not return any results. This was an issue with the crossScriptingFilter, which has been modified to allow two-step filtering.

SR-A5814 · Issue 216307

Resolved blank list page navigation

Resolved in Pega Version 7.2

If there was a backslash (escape characters) in the double quoted report parameters passed from the section, no data was shown when navigating to the next page in a ListView report. This was caused by multiple encodings of the escape characters while moving back and forth between the pages. The filtering has been updated to correct this issue.

SR-A6387 · Issue 216159

Resolved errors while saving in summary view

Resolved in Pega Version 7.2

While saving an existing summary view, the error message "Output type: ** Your Field Definition does not match with Chart Definition. Verify it" was generated if only the third column was selected at the time of the save. In addition, selecting any checkbox other than the first in the chart's data tab during save of the summary throws an error. These issues have been fixed.

SR-A7649 · Issue 219010

Fixed RD "Report on Descendant" access to application page

Resolved in Pega Version 7.2

A report definition using the "Report on Descendant" option worked when executed from a user session but did not work when executed by a File Listener Process. This was due to the report not being able to access the application page in the batch requestor context, and has been corrected.

SR-A12707 · Issue 229383

Subreport join/filter updated

Resolved in Pega Version 7.2

An invalid subreport join/filter condition error was thrown if a filter with an unoptimized property from a sub report on one side had an optimized or literal property on the other side, even if the prconfig setting "reporting/useStreamInJoinConditions" was set to true. This has been fixed.

SR-A9129 · Issue 220717

Report Definition error message localized

Resolved in Pega Version 7.2

Localization/customization has been added for the Report Definition error message : "Retrieving the report data exceeded the limit of * seconds. Please try making the report more specific by further limiting which rows to include".

SR-A12941 · Issue 224444

NCHAR column type added to RD supported column types

Resolved in Pega Version 7.2

After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java

SR-A12941 · Issue 230561

NCHAR column type added to RD supported column types

Resolved in Pega Version 7.2

After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java

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