Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number 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-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.

SR-B42679 · Issue 303776

Report definition popup display overwrites single window

Resolved in Pega Version 7.3.1

Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.

SR-B42679 · Issue 305263

Report definition popup display overwrites single window

Resolved in Pega Version 7.3.1

Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.

SR-B42679 · Issue 307394

Report definition popup display overwrites single window

Resolved in Pega Version 7.3.1

Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.

SR-B57039 · Issue 312472

Removed space in data transform value

Resolved in Pega Version 7.3.1

After running a Summary View with Trend Reporting, the following error was logged: NumberFormatException For input string;" ". When trend reporting is enabled in list view with no value for pyCeilingField, the data transform initialized this value to " " instead of "", causing the issue. This has been fixed.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us