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-118918 · Issue 562155
Table Pagination elipses display properly for more than 10 pages
Resolved in Pega Version 8.4.2
When a table layout was configured with a report definition as the Data Source, the Pagination format in the grid header properly showed 'Page 1,2,3 ...' if there were fewer than 10 pages, but if there were more than 10 pages the '...' (elipses) were not appearing. This has been corrected.
INC-119669 · Issue 562589
Special character handling added to filters for table sourced with parameterized Report Definition
Resolved in Pega Version 8.4.2
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-125641 · Issue 573386
Column Filter working with class join
Resolved in Pega Version 8.4.2
When a class join was configured in the report definition and the report was edited to include new columns from the joined class, a "Filter condition invalid" error appeared in the tracer after adding a filter condition to a new column. This was only observed when the property added was a decimal property, and did not happen for a text property. The filter worked as expected after re-saving the property in the report definition in Designer Studio. This was traced to the data type being passed as "DECIMAL" for decimal fields, which did not match the logic used to set the filter value, and has been resolved.
INC-125752 · Issue 566171
Tab Titles show the correct title on hover of tab name
Resolved in Pega Version 8.4.2
When clicking on the case stages information from the Dashboard Case Manager to open the stage information in a new tab, hovering on the tab name displays the title of the case stage name. If there are two stages, clicking on the first stage opened it in a new tab and the title of the tabname on hover was correct. However, clicking on the second stage name to open the other stage in the same tab did not display the correct title when hovering on the tab name. This has been corrected by updating the code for the JSON configuration object.