INC-128880 · Issue 592817
Handling added for angle brackets in legacy Chart control
Resolved in Pega Version 8.3.5
When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.
INC-141322 · Issue 594513
Resolved drill up doubling the filter box
Resolved in Pega Version 8.3.5
When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.
INC-137317 · Issue 585404
Security improved for searches
Resolved in Pega Version 8.3.5
Authentication requirements have been added to activities associated with searching.
INC-139700 · Issue 591563
Shortcut works for copying reports into private rulesets
Resolved in Pega Version 8.3.5
Copying out of the box shortcuts to other categories in the Report Browser was failing with the error ".pyShortcutName: The rule name pyTimePerStage is a reserved name (starts with px, py, or pz) and is not created in a Pega- ruleset." This was caused by the system trying to create a new rule with a py prefix in a non pega- ruleset, which was a missed use case in the refactoring work of report actions to use the Record API. This has been corrected by moving the report ID generation logic from the activity pzValidateSaveAsInput to a new Rule-Utility-Function in the ReportingUtils library called pzGenerateUniqueRecordName so that it can also be used by pzCopyShortcutPostActivity7 when the shortcut's ID is prefixed with px, py, or pz.
INC-140701 · Issue 602862
The Report Resource Limit is applied on Job Scheduler
Resolved in Pega Version 8.3.5
The Job Scheduler was ignoring the application-wide limit for maximum number of rows to retrieve that was set on the Report > Settings landing page. If the limit was set on the Data Access tab of the report, it was honored. If it was set on the Application settings rule Pega-RulesEngine.pyMaxRecords it was not honored. This behavior was due to pzUpdateSystemSettings being called by pxRetrieveReportData. In pzUpdateSystemSettings, .pyContent.pyMaxRecords was updated to match the value in px.Requestor.pyReportSettings.pyMaxRecords. In some cases, that was not available and the max amount of records was not limited in that case. This has been resolved by updating pzUpdateSystemSettings to pull pyMaxRecords using @getRuleSystemSetting().
SR-D18879 · Issue 500642
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.1.7
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D27528 · Issue 501372
Return from drilldown in frameless portal corrected
Resolved in Pega Version 8.1.7
Drill up after drilling down on a dashboard chart in a frameless portal (such as Case Worker or Case Default) was throwing an exception. This was caused by the top-level page generated during drilldown not having pyRetainPage set to true, causing it to be removed from the clipboard by doUIAction. This has been resolved by updating runReport to set pyRetainPage if it needs to create the top-level page.
SR-D32222 · Issue 500901
Auto-generated controls with images supported in export to Excel
Resolved in Pega Version 8.1.7
When attempting to display a column as an image, changing the column format to "pxCheckbox" showed an image while running the report if the value was true, but blank values were displayed when the report was exported to Excel. Investigation showed that the value was being returned as null when a boolean value was set on a column and the option for the auto control was set to show as an image due to the formatted value being returned as an HTML element instead of a boolean value. To correct this, AutoGenReportUIField has been modified so that auto-generated controls that are shown as images are converted to text upon export to Excel.
SR-D37943 · Issue 505737
Corrected Export to Excel after adding custom DateTime field
Resolved in Pega Version 8.1.7
An issue with exporting report definition results to Excel after adding a custom date field column through the edit report option of the report in report viewer was traced to the processing of the controls backing a cell in a report when exporting to Excel. For controls like "Date Only" DateTime (non-autogenerated) control, the code was not returning a string the way it should. To resolve this, NonAutoReportUIField has been updated to always treat all Non-auto Controls as strings.
SR-D43179 · Issue 509888
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.1.7
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.