SR-A11563 · Issue 224698
XSS security update for TabbedRepeatingListSection
Resolved in Pega Version 7.2
Security updates have been made to the TabbedRepeatingListSection function to close a potential XSS vulnerability.
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-161463 · Issue 638000
Case Dependency corrected for different access groups
Resolved in Pega Version 8.3.6
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
INC-163154 · Issue 638097
Code updated for bulk actions buttons
Resolved in Pega Version 8.3.6
After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.
INC-164413 · Issue 636125
Updated timestamp handling for duplicate key issue with PyCompleteAutomation
Resolved in Pega Version 8.3.6
Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.