SR-C83615 · Issue 424946
Support added for hiding unwanted category reports
Resolved in Pega Version 8.2.1
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-C84609 · Issue 424884
CustomFilter clipboard page now retained after section submit
Resolved in Pega Version 8.2.1
When a Report Definition was configured to display filters using a custom section, selecting the filter property value and submitting the section resulted in the CustomFilter clipboard page being deleted automatically. In order to prevent the clipboard page from being immediately cleaned up by the doUIAction activity, a step has been added to the pzCreateCustomFilterPage activity that will set the pyRetainPage property to "true".
SR-C80948 · Issue 421765
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.2.1
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C84167 · Issue 422477
Corrected issue with Field Level Auditing re-adding deleted page list items
Resolved in Pega Version 8.2.1
Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.
SR-C82254 · Issue 421056
Support added for saving draft survey flows in production level 5
Resolved in Pega Version 8.2.1
With production level set to 5, creation of a survey was generating two errors: in UI, "Default survey flow creation failed", and in trace, "Update record failed: .pyDraftModeON". Because in most cases Survey authoring would be done in a system with a lower production level where users would not see any issues, the code did not include support for saving draft mode flows when the system was set to production level 5. This ability has now been added to support this use.
SR-C83899 · Issue 421068
Alternate RD added for sub class union that will skip blob open
Resolved in Pega Version 8.2.1
The screen load was taking 4 seconds or more to load when a parent case had 500+ child cases, leading to timeouts and issues with case processing. This was caused by the system performing a database open of all the child work items for building the tree: because different child items are mapped to different work tables, a single RD would not suffice for fetching all child items. This meant a work record was opened and child inskeys grouped into different groups based on table mappings, then the RD was called multiple times to fetch the details. To resolve this and avoid blob open, a report definition that performs a union on all sub classes has now been put in place. Execution is based on a parameter to avoid any backward compatibility issues. This is used by overriding the 'pyPopulateCaseContentsWrapperExtension' data transform and setting param.useOptimizedQuery to 'true' to override the database open.
SR-C82530 · Issue 420608
Atmosphere XSS Vulnerability fixed
Resolved in Pega Version 8.2.1
Atmosphere has been updated to close a potential XSS vunerability.
SR-C84788 · Issue 422937
Handling added to maintain custom modal template name after errors
Resolved in Pega Version 8.2.1
When using a grid where each grid row had an Edit button which launched a modal dialog with a custom modal template, the post action activity of the flow action introduced error messages on a top level page (not on primary or pyWorkPage). Clicking the submit button again caused the modal dialog size to shrink and not work after that. This was traced to the second submit using the system's pyGridModalTemplate instead of the custom modal template due to the modal submit button being replaced with new markup. To resolve this, the modal launch will now use the "pega.u.d.submitModalDlgParam.modalSection" variable which will have the modal template name. In addition, a check has been added to ensure this is not passed as null.
SR-C75205 · Issue 424476
Invalid text entry in Date control field now returns current timestamp
Resolved in Pega Version 8.2.1
Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect.
SR-C85096 · Issue 423236
XSS check logic updated for pyPosition
Resolved in Pega Version 8.2.1
Additional logic has been added to prevent the injection of javascript into script tags while rendering Smart Tips.