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.

INC-119669 · Issue 562588

Special character handling added to filters for table sourced with parameterized RD

Resolved in Pega Version 8.1.9

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

INC-145810 · Issue 599463

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.1.9

An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.

SR-D90400 · Issue 563187

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.1.9

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

SR-132352 · Issue 202264

Corrected Filter criteria Pick Value button behavior

Resolved in Pega Version 7.1.9

The Pick Value filter criteria pop-up was only working if the property was a direct class property and did not work with an embedded property. This has been corrected.

SR-132827 · Issue 202511

Adding handling for 'today' date field in RD filtering

Resolved in Pega Version 7.1.9

The 'today' link in calendar popup selects the current date when clicked and automatically closes the popup, but attempting to use the 'today' link in a Report definition with a date field as a filter did not select the current date and did not autoclose. This has been corrected.

SR-132946 · Issue 202933

RD with multiple joins now displays all properties in Data Explorer to end user

Resolved in Pega Version 7.1.9

Given a Report Definition with two joins defined on it, the end user was not able to view or select from all of the properties from the joined classes due to the myStepPage adding entries outside of the WHILE loop. This has been corrected by updating the pzGetPropsForTreeGrid activity to handle this scenario by iterating through all of the join classes and showing them in Data Explorer.

SR-A1139 · Issue 204433

Ensured threshold checkbox honored in Report Wizard

Resolved in Pega Version 7.1.9

Validation errors were being generated in the custom report wizard when 'threshold' was not selected. This was an issue where the validations were being added without checking the value of the checkbox, and has been corrected.

SR-A1220 · Issue 204961

Corrected SQL exception on Monitor Processes reports

Resolved in Pega Version 7.1.9

Some Pega out-of-the-box summary reports under 'Monitor Processes' like "Created in last 30 days by Operator", "Created in last 90 days by operator, etc., were throwing SQL exceptions on drill down if they had data. This was caused by the DrillDown activity getContentWeekly that was being used for some of the SVs not having the flags pyCanUseVirtualList and pyUseVirtualList set to true, unlike the default DrillDown activity getContent. This was causing the query generated for DrillDown to have the prefix "PC0" only for the drilldown filter condition. This has been resolved by modifying getContentWeekly to set the flags properly.

SR-A1267 · Issue 207657

Refined ScheduledTask-Reporting-pyExecuteTask to improve system performance

Resolved in Pega Version 7.1.9

An issue was found with performance degradation and excessive logging caused by the repeating of a scheduled report that had an exception and did not terminate after xx retries. Checks have been added to Pega-ScheduledTask-Reporting-pyExecuteTask in order to prevent this problem.

SR-A1733 · Issue 205403

Improved error handling for save-as of RD with invalid name

Resolved in Pega Version 7.1.9

Performing a SaveAs of a Report Definition with an invalid name was generating a stack trace Instead of showing a validation error for the name field of the save-as dialog. This has bene corrected.

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