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-A94871 · Issue 263314

Handling added for summary report paging mode changes

Resolved in Pega Version 7.2.2

After switching a summary report previously configured to use the "Next Previous" paging mode to a list report using the "List" action in the "Actions" menu, changing to a new page caused an error to be shown and no records displayed. This has been corrected by adding a step to the activity pzPostReportSummarizeConfig to reset the paging of a report when converting from a summary report to a list report.

SR-A99642 · Issue 266586

Fixed special character encoding for Report Definition

Resolved in Pega Version 7.2.2

Double encoding of the Axis label caused issues with special characters such as apostrophes in Report Definition. This has been corrected.

SR-A92190 · Issue 261317

Added support for '&' in report parameter

Resolved in Pega Version 7.2.2

If the value of a parameter to report was set to be passed as 'A & B', the parameter value was being truncated to 'A' by the time it is received by the report. This truncation has been fixed by encoding the parameters while generating the Data-click attributes.

SR-A76586 · Issue 256002

Guardrail updated for Report Definitions using Data Page for filter

Resolved in Pega Version 7.2.2

It is possible to configure a report definition to use a Data Page in the Filter/Criteria field (such as pxObjClass Contains D_ABC.PropValue) and not be prompted to list the Data Page on the Pages & Classes Tab, but when it is not listed on this Tab the query uses a literal value as opposed to a dynamic reference. In order to ensure expected results, a check has been added to fully identify invalid page prefixes and an Informational guardrail for Functionality will appear.

SR-A87322 · Issue 260290

Enhancement to display custom properties during editing based on when

Resolved in Pega Version 7.2.2

It was assumed that if pyShowCustomProperties returns false, only the custom properties are shown while editing a report in the data explorer. This was not always true based on checkout privileges, and was therefore inconsistent with the name of the when rule. In order to meet expectations for filtering, pzPrepareReportExplorerFieldNames and runReport have been updated to reference a new 'when' rule called pyReport_ShowCustomProperties. This function will filter the properties as expected based on the available when rule and will reference pyShowCustomProperties for backwards compatibility reasons.

SR-A98617 · Issue 265782

Enhancement allows suppression of date/time on Export to Excel filename

Resolved in Pega Version 7.2.2

The ExportToExcel process creates an Excel file with a filename that has Date and Time appended to the report name by default. An enhancement has been added to optionally suppress the date/time portion of the filename based on the When rule pyShowDatetime.

SR-A91248 · Issue 264400

Enhancement allows suppression of date/time on Export to PDF filename

Resolved in Pega Version 7.2.2

The ExportToPDF process creates an PDF file with a filename that has Date and Time appended to the report name by default. An enhancement has been added to optionally suppress the date/time portion of the filename based on the When rule pyShowDatetime.

SR-B960 · Issue 271764

PDF "Display Report Filter" check honored

Resolved in Pega Version 7.2.2

The filter layout was visible in a generated PDF despite "Display Report Filter" being unchecked. This was the fault of a missed visibility condition in pzDisplayReportSectionForPDF, which has now been added.

SR-A89677 · Issue 257766

Removed erroneous warning from auto-created DataType reports

Resolved in Pega Version 7.2.2

When creating a data type and local source, a report definition is automatically generated for the data type. That report definition contains the warning "Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls." This was confusing, creating the unintended assumption that something was wrong with the automatically generated report. To clarify this, the warning will not be displayed when the rule is created automatically.

SR-A96539 · Issue 264614

Report Definition parameter passing improved for grids

Resolved in Pega Version 7.2.2

When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.

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