Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C97610 · Issue 435223

Enhanced backwards compatibility for Attachment Gadget

Resolved in Pega Version 8.2.2

After upgrade, information was missing from Attachments. This included the case number being absent from between the parentheses on the Attachment name; the time stamp was missing on the attachment; and checking the 'Show Subcase Attachments' checkbox did not provide the expected information for the attachment. This was traced to a reworking of the attachment gadget in Pega 7.1.5, and logic modifications have now been added to enhance backwards compatibility with the 6.x versions of Pega.

SR-C98214 · Issue 435684

Decision Table keeps proper values when a column is deleted

Resolved in Pega Version 8.2.2

When the first column in a Decision Table was deleted and the rule saved, the value that was in the second column was replaced in the first row. This has been corrected.

SR-C97207 · Issue 435772

ModalCancelAction activity clipboard removal updated

Resolved in Pega Version 8.2.2

Clicking on the jump/when button on the activity step and then trying to expand any step in the Rule-Obj-Activity.pyModalCancelAction activity was resulting in the error "The property RH_1.pyTempModalPage was of mode String while adoptDictionaryDefinition(ImmutablePropertyInfo, boolean, boolean) was expecting Page mode. Details: the mode has been reset to match the property's definition." This has been corrected by modifying the code to use property-remove instead of property-set to remove the clipboard page.

SR-D2296 · Issue 436877

Enhancement added to support multiple security certificates

Resolved in Pega Version 8.2.2

When importing IDP metadata, the only the last verification certificate was imported if there were multiple certificates. This caused SAML SSO signing failures in some cases. Support has now been added for importing multiple certificates to enhance encryption security.

SR-C96703 · Issue 435742

CMIS Timestamp function updated to support more timezones

Resolved in Pega Version 8.2.2

When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.

SR-D1441 · Issue 438906

CMIS Timestamp function updated to support more timezones

Resolved in Pega Version 8.2.2

When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us