SR-D2229 · Issue 437546
Repository Delete API updated for better use with cloud storage
Resolved in Pega Version 8.2.2
Previously, the Repository Delete API immediately checked if a file existed after attempting to delete it. When deleting files in S3, the file may not be immediately removed: due to S3's eventual consistency policy, the file could still exist at the time Pega was attempting to verify the deletion but be "deleted" according to Amazon. This caused a false alert that the file deletion was unsuccessful, leading to alert emails being sent and the Manifest file not being created, and in some cases generating an exception. To resolve this issue, the logic in Repository Delete that checked if file existed after attempting to delete it has been removed.
SR-C96035 · Issue 434731
Write and Delete restrictions added to the RoboticAdministrator role
Resolved in Pega Version 8.2.2
The security configuration for the PegaRULES:RoboticAdministrator role has been updated with the 'when' rule condition pzModifyAllowed for Write and Delete access.
SR-D3036 · Issue 438138
Password change error message clarified for invalid characters
Resolved in Pega Version 8.2.2
When an operator updated their password and and included special characters other than those specified in the security policies, an error appeared that was not easy to understand. This message has been updated to clearly indicate that the password attempt includes invalid characters and needs correction.
SR-C95532 · Issue 435980
Improved handling for deleting dedicated index instances
Resolved in Pega Version 8.2.2
If the dedicated index instance was deleted from the ‘Custom search properties’ tab rather than from the dedicated tab of the search tab, then that instance was unexpectedly deleted from the instances of custom search properties and resulted in a blank row with the re-index button disabled and delete button enabled. This was a missed usecase related to handling the deletion of a dedicated index created from D-CP-S on a class whose immediate parent class is an abstract class or class that doesn't have a dedicated index, and has been resolved by setting the pySaveFromUI Flag when delete is invoked from the Data-CustomProperties-Search instance.
SR-C81185 · Issue 427993
Accessibility enabled Layout group tabs browsing corrected
Resolved in Pega Version 8.2.2
When using Layout group (Tab) or a Tabbed Layout for viewing client information in Tabs with Accessibility enabled, the system was reading each tab and its content but then focus was returning to the browser and tracing through all elements before moving on to the next tab. This was traced to an incorrect tabindex setting in the pzpega_ui_template_layout_header file, and has been fixed.
SR-C89504 · Issue 435566
Multi-Select values visible in read-only
Resolved in Pega Version 8.2.2
The Selected Multi-Select values were not seen on the read-only review screen. This has been corrected.
SR-C95187 · Issue 433824
IO exception logging enhanced
Resolved in Pega Version 8.2.2
In order to improve diagnosing problems such as DDS nodes not joining a cluster despite Cassandra nodes being run successfully, logging enhancements have been added that include details about IO exceptions.
SR-C95253 · Issue 435787
Custom datetime controls correctly appended to Excel export
Resolved in Pega Version 8.2.2
The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.
SR-C90418 · Issue 436017
Exception handling improved for pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions
Resolved in Pega Version 8.2.2
If the SLA Deadline days were updated from 0 to 1, the SLA agent did not trigger the deadline escalation activity and the error "com.pega.pegarules.pub.context.PRQueueException: Instance of class Queue not found: SYSTEM-QUEUE-SERVICELEVEL.SYSTEM-QUEUE-SERVICELEVEL" was generated. This has been resolved with the addition of better failure handling to the pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions for cases where an exception is generated.
SR-D3767 · Issue 438200
Enhancement added to track list based report definitions for statistics
Resolved in Pega Version 8.2.2
In order to expand the use of pyDefaultReport for Log-ReportStatistics, an enhancement has been added to pzPopulateListReport to call the pzPopulateStatisticsInfo activity with the required parameters to enable tracking of list based report definitions so they can be included in the report statistics table.