SR-A3712 · Issue 222263
Removed collapse from advanced filter options to improve accessibility
Resolved in Pega Version 7.2
The advanced options in the report viewer's filter conditions were not accessible using the keyboard and would only expand with a mouse. To resolve this, the advance options collapse has been removed from PZFILTERADVANCEDOPTIONS and the information now fully displayed.
SR-A3712 · Issue 218750
Removed collapse from advanced filter options to improve accessibility
Resolved in Pega Version 7.2
The advanced options in the report viewer's filter conditions were not accessible using the keyboard and would only expand with a mouse. To resolve this, the advance options collapse has been removed from PZFILTERADVANCEDOPTIONS and the information now fully displayed.
SR-A8488 · Issue 219112
HTML line breaks honored in Excel export
Resolved in Pega Version 7.2
In Report Definition, Export to Excel was ignoring the new line of each cell due to pzDisplayPropValue not acting on the HTML tag
. To correct this, the call to the function "pzDisplayPropValue" has been modified to pass a flag which will be set based on option given on the RD rule form, i.e. "Ignore formatting when Exporting to Excel". In addition, the
tag is now supported so Excel will format it accordingly.
SR-A8488 · Issue 220333
HTML line breaks honored in Excel export
Resolved in Pega Version 7.2
In Report Definition, Export to Excel was ignoring the new line of each cell due to pzDisplayPropValue not acting on the HTML tag
. To correct this, the call to the function "pzDisplayPropValue" has been modified to pass a flag which will be set based on option given on the RD rule form, i.e. "Ignore formatting when Exporting to Excel". In addition, the
tag is now supported so Excel will format it accordingly.
SR-A9731 · Issue 222614
Pick a Value window resized for proper display
Resolved in Pega Version 7.2
On clicking on the criteria field of any report (listview / SummaryView), the 'Pick Values' modal window opens up for user to select values. This window is sized smaller by a percentage than the ClientHeight to ensure the popup can display the content within the height of the current window. After upgrade, the modals appeared with a default height of 96% and caused the Apply / Cancel / Submit buttons to either be partially visible or not visible at all, which did not allow user to select values. This has been resolved by updating the "launchpickavalue" method defined in "Rule-Obj-HTML.Wizard_Parameters" rule to set the iframe height to 93%.
SR-A12341 · Issue 224036
Corrected implementation for DataFlow key non-match
Resolved in Pega Version 7.2
If a DataFlow Dataset configured against a Report Definition had a property key name that was not identical to the column name in the database table, the Dataflow failed to execute with error " Incorrect implementation for Report Definition as a data flow source. Property-to-database table column mapping was not applied correctly". The implementation has been fixed to resolve this issue.
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.