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

SR-A185 · Issue 203599

All join values now showing in 'Pick value' pop-up

Resolved in Pega Version 7.1.9

PromptFieldValue and Table Type field values with a join were not being displayed in Valid Values. This was caused by the wrong Property name being passed to the query, and has been corrected.

SR-A2199 · Issue 210092

12 hour format (AM/PM format) support added in Report Definition chart

Resolved in Pega Version 7.1.9

The out-of-the-box Pega Report Definition chart only offered a 24-hour time format. An enhancement has been added to support new formats for the date time property, including datePatterns.add("MM/dd/yy hh:mm:ss a") and datePatterns.add("hh:mm:ss a"); to in step 2 of pzGetDateTimeAxisPatterns activity.

SR-A2268 · Issue 206068

Summary drilldown now uses entire screen

Resolved in Pega Version 7.1.9

While running summary view, the drilldown data only appeared on half of the screen and the other half was blank. This was caused by the window height logic for the drilldown using offsethright for the window size. This has been changed in RULE-OBJ-HTML RULE-OBJ-SUMMARYVieW DRILLDOWN to use view port height to make the results occupy all the window.

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