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

SR-A96539 · Issue 265411

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.

SR-A91955 · Issue 260732

Filter icon made accessible

Resolved in Pega Version 7.2.2

When the Enable accessibility add-on was checked, the filter icon was not selectable. This has been corrected.

SR-A94690 · Issue 261686

Report Editor displays Associations

Resolved in Pega Version 7.2.2

When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.

SR-A77395 · Issue 255085

DB2 external mapping values used for filtering

Resolved in Pega Version 7.2.2

When using the "External Mapping" feature in a class to map column names to different property names in DB2, the filter conditions in a report definition rule either generated incorrect SQL in the report viewer for "Select Values" or the error "There was a problem getting a list" appeared. This error was caused by the SQL query using the property name instead of the column name, leading to external mapping for the properties not being considered. The pzGetAvailableValues activity has been modified to get the correct column name based on external mapping.

INC-151293 · Issue 630346

Out of memory condition resolved for BIX extraction

Resolved in Pega Version 8.5.4

A node was going down automatically during execution of a BIX Extract rule when working with old objects. Investigation showed this was related to an out of memory error: the work object had nested page lists, and when one of the page lists contained a propertylist which contained more records, the system was trying to add entries to the LinkedList if any properties were missing the reference during extraction. Because LinkedList allowed duplicates, it filled with enough errors to cause the out of memory condition. To resolve this, LinkedList has been replaced with LinkedHasSet, which does not allow duplicates.

INC-158473 · Issue 626278

BLOB decryption API updated for greater flexibility

Resolved in Pega Version 8.5.4

A BIX extraction issue occurred after the class had enabled BLOB Encryption. The errors indicated the BLOB had been persisted in an incorrect stage, causing the extraction of the single item to never complete even though some CSV file was created. This was traced to the API used to read the encrypted BLOB, DatabaseUtilsCommonImpl.getStreamBytes, which had the limitation of decrypting only when a Site-specific cipher existed. To resolve this, the system has been modified to use a different API which works for all encryption modes, PageDatabaseMapperImpl.getStreamBytes().

INC-159759 · Issue 629625

Report title displayed for empty widget charts

Resolved in Pega Version 8.5.4

Per design if there is no data to be rendered in the chart from a report added in a Widget in any portal, a static image is displayed saying "No Data to Display". However, if there were multiple reports in the Widget it caused confusion on which report was not being displayed because the image did not show the title of the report. To resolve this, an enhancement has been added to modify pzRRChartDiv to display the report Title even when there is no data in it.

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