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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D58201 · Issue 538979

Data page processing performance improvement

Resolved in Pega Version 8.2.7

After upgrade from Pega 7 to Pega 8, data page processing was noticeably slower. Based on analysis of the issue and results of testing, changes have been made to improve the performance of the query used by the expression parser by using an ClipboardPage API to read values from a Page (ClipboardPageAPI#getString(boolean, String)).

SR-D60830 · Issue 533029

Logic update for classloading synchronization

Resolved in Pega Version 8.2.7

The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.

SR-D67142 · Issue 548641

Enhanced CMIS connector logging

Resolved in Pega Version 8.2.7

Additional diagnostic logging has been added to enhance investigating CMIS connector health.

SR-D72389 · Issue 541946

Handling added for JSON with top level array

Resolved in Pega Version 8.2.7

When using serialize mode in a JSON data transform where the Top element structure was Array and the “For JSON only” relation was selected for relation mode, the result had an incorrect JSON structure. In order to support this configuration, generatePropertyAsJSON has been amended to set isTopLevelPageList to true in instances where automap is off, the top level is an array, and the JSON context is updated within the first step. In addition, generatePageAsJSON has been updated to check this flag when processing mappings in order to ensure these context changes are processed, and updates have been made to generatePropertyAsJSON to ensure that the context is popped when appropriate.

SR-D74376 · Issue 552258

Check added for string vs boolean for pzscan JSON

Resolved in Pega Version 8.2.7

When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.

SR-D74921 · Issue 551787

Error condition will close WebSocket connection

Resolved in Pega Version 8.2.7

An async listener has been added that will close the WebSocket connection when an error condition is encountered.

SR-D75636 · Issue 549347

Improved handling for attachments not using UTF-8 encoding

Resolved in Pega Version 8.2.7

When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.

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.

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