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-D77095 · Issue 559842

Improved backwards compatibility for imported WSDL and ParseXML rules

Resolved in Pega Version 8.2.7

After update, a Connect-SOAP integration created using the "Connector and Metadata" wizard in Pega 6 was unable to use newly generated WSDL that contained updated elements due to the wizard not updating the Parse XML rules with the updated properties, and two parse XML rules were created in draft mode when the old WSDL was imported and then followed by the new WSDL. If the "Create SOAP Integration wizard" was used instead, the properties and Parse XML rules were generated as expected but a new class was created due to the system removing special characters such as underscore. For example, the imported Connect-SOAP rules used the "XXX-APC_QUOTESERVICE-" class, but the Create SOAP Integration wizard changed this to "XXX-APCQUOTESERVICE-". Upper and lower case differences were also seen between the old and new XML Stream and Parse XML rule names. As a result, it was not possible to either skip or generate new properties into a higher ruleset version in the Connector and Metadata Accelerator. To resolve this, updates have been made which now properly skip the identical properties when generating on top of the existing run. The system now also handles unqualified schemas as it did in previous versions.

SR-D81651 · Issue 545237

Added check for signed-data in encrypted email

Resolved in Pega Version 8.2.7

Numerous java.lang.UnsupportedOperationException messages were seen in the logs. Investigation showed that signed email which arrived as encapsulated within another email with header content-type = "application/pkcs7-mime, smime-type=signed-data name="smime.p7m" caused the exception. This was due to a missed check for 'signed-data' while parsing the email and checking for encryption, and has been resolved.

SR-D81659 · Issue 548900

Handling added for encrypted messages using IMAP

Resolved in Pega Version 8.2.7

Log errors were seen related to Email Listeners while processing encrypted emails from specific mail IDs, including "Unable to determine DSN, EmailClientRuntimeException: Unable to load BODYSTRUCTURE" and "isMimeType(JavaMailMIMEMessage - Unable to determine partIsEncryptedMessage". This issue is related to how certain servers work with the IMAP protocol to parse messages, and has been handled by creating a new instance of MimeMessage from the original MimeMessage and working on it.

SR-D83329 · Issue 546658

AWS S3 client SDK upgraded

Resolved in Pega Version 8.2.7

The com.amazonaws group has been updated to version 1.11.740 .

SR-D83424 · Issue 552721

Class Loader cache values wrapped with WeakReference for improved cleanup

Resolved in Pega Version 8.2.7

Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.

SR-D84122 · Issue 547966

Added min INT comparison for BrowseByKeys

Resolved in Pega Version 8.2.7

Running the dataset with the Browse option worked as expected, but running it using BrowseByKeys operation and giving a negative value caused results to not be populated. To resolve this, a minimum INT value comparison has been added.

SR-D84725 · Issue 547962

Search behavior change after update corrected

Resolved in Pega Version 8.2.7

After update, changes were seen in the search behavior that included the toggle button at the top left corner of the landing page becoming disabled when re-indexing was in process, the Re-index buttons becoming disabled and a cancel button appearing in place of the re-index button for the specific index category being indexed, indexing done through batch indexers not presenting progress in the document size column every 10 seconds but instead presented the whole row for the index category as blank, and progress being indicated by the changing figures under the Queue Information section on the Search Landing Page. This was due to a conflict in which ruleset was highest after rulesets were imported during update, and has been resolved by updating pzLPSearchManagerReIndexSection to use the correct version of the ruleset.

SR-D84876 · Issue 547688

Performance improvement for Oracle 12c queries

Resolved in Pega Version 8.2.7

In order to compensate for a known issue with Oracle 12c that can cause repeated queries at certain times to cause database contention, Oracle pre/post processing steps have been added to improve performance in this environment.

SR-D84880 · Issue 546889

Null check added to resolve addmapcasetomap error

Resolved in Pega Version 8.2.7

Using a createcase flow shape to create child cases by looping on a page list on the parent case resulted in pzaddmapcasetomap throwing an exception related to the activity pzLoadCaseHierarchyWrapper in step 5. This was traced to a page being removed after the list of pages was received in findPageByHandle, and has been resolved by adding a null check.

SR-D87605 · Issue 547296

Indexes and tables updated to improve purge query performance

Resolved in Pega Version 8.2.7

Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.

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