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.

SR-B66844 · Issue 317078

RD modified to allow more than 1000 entries in a filter value

Resolved in Pega Version 7.3.1

A DB exception was thrown when a report definition was run with more than 1000 entries in a filter value. This was due to the DB limitation, and the system has been updated to pass the "pyReportParamPageName" parameter to RD to avoid the exception.

SR-B50800 · Issue 311591

Fixed sorting of nested repeat grid with one child-grid column

Resolved in Pega Version 7.3.1

A Null Pointer Exception was generated when performing a sort in a nested Repeat grid when the child-grid had one column and sort was enabled. The sort worked as expected when there was more than one row in the embedded/child grid. This was due to a loss of the content div after the first sort, and has been corrected.

SR-B41245 · Issue 315783

Query Generation layer Null Pointer Exception handling added to support Sybase and other DBs

Resolved in Pega Version 7.3.1

A Null Pointer Exception was generated while running a report that connected to a table on a Sybase database which had a nvarchar column. In order to handle Sybase requests or other unexpected DBs used with Pega, the DB_Type.GENERIC in mapDatabaseType in DatabaseUtils.java class has been updated to handle any Null Pointer Exceptions that might be encountered in the Query Generation layer.

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