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.
SR-A2313 · Issue 207691
"int" added to pzCheckCompatibilityOfColumnTypes
Resolved in Pega Version 7.1.9
If a report definition was created with a sub-report that is joined on a column of type integer, it was not possible to save the report definition rule if one of the columns mapped to a MS SQLServer column of type int. This was a problem with the int case not being handled in pzCheckCompatibilityOfColumnTypes, and has now been fixed.
SR-A3897 · Issue 209254
Resolved authentication requirements in activity pzSetQueryDefaults for SSO setup
Resolved in Pega Version 7.1.9
Code-Security.InitialProfileSetup does not need authentication to run, but during the SSO login it calls Code-Pega-Requestor.pzSetQueryDefaults which was hard-coded to require authentication. This was an error, and the SetQueryDefaults activity no longer requires authentication.
SR-A4972 · Issue 211383
Report Viewer remains active after launching tab Is closed
Resolved in Pega Version 7.1.9
If Report Viewer was opened from Dashboard, it shared the Dashboard's thread and would not be operational if it remained open after the Dashboard tab was closed. This was expected behavior, but the need has been established for allowing the Report Viewer to continue working independently of the Dashboard after launch, so an enhancement has been added that will now launch the report within a dynamic container so it will continue to be available after the Dashboard is closed.
SR-A4972 · Issue 211536
Report Viewer remains active after launching tab Is closed
Resolved in Pega Version 7.1.9
If Report Viewer was opened from Dashboard, it shared the Dashboard's thread and would not be operational if it remained open after the Dashboard tab was closed. This was expected behavior, but the need has been established for allowing the Report Viewer to continue working independently of the Dashboard after launch, so an enhancement has been added that will now launch the report within a dynamic container so it will continue to be available after the Dashboard is closed.