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.
SR-D71408 · Issue 534932
DIrty check flag triggered by adding columns and filters
Resolved in Pega Version 8.1.8
If a report was edited and closed without saving, the dirty check worked as expected. However, if new columns or filters were added and the report closed without saving, the dirty check did not appear. This has been resolved by updating the check logic.
SR-D53176 · Issue 541793
Error when adding function filter will persist
Resolved in Pega Version 8.1.8
When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.
SR-D76204 · Issue 543591
Index conflict resolution logic updated
Resolved in Pega Version 8.1.8
After configuring a dedicated index on delivered Class - PegaCA-Interface-Contact, trying to generate the index resulted in an error indicating a type conflict in delivered classes/properties. This has been resolved by updating the conflict resolution logic.
INC-145293 · Issue 674901
Additional diagnostic logging added for ElasticSearch startup issues
Resolved in Pega Version 8.7
The PyIndexerState was stuck in Starting status during node initialization. This issue could occur if the filesystem became hung due to network level issue while scanning entries from /etc/mtab, resulting in a lock which was not released correctly. In order to better determine which node entry in a cluster may be responsible for the hang, an update has been made which will use a temporary virtual environment to repeat the part of the initialization phase responsible and generate additional logs for debugging. To activate this, the PegaSearch.Diagnostics logger must be set in DEBUG mode. This duplicated virtual initialization will not interrupt the normal initialization.