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-A15105 · Issue 230713

Performance improvements for "Check out to Branch"

Resolved in Pega Version 7.2.1

The "Check out to Branch" operation was very slow in installations with very large ruleset lists. Performance has been improved by removing unnecessary calls to the GetAppRulesets activity.

SR-A15325 · Issue 231926

NPE resolved for WorkLock

Resolved in Pega Version 7.2.1

After upgrade, errors occurred in the WorkLock activity when attempting to create new Work Objects in a pre-production environment. This has been fixed.

SR-A15388 · Issue 231184

Reordered email encryption logic

Resolved in Pega Version 7.2.1

Encrypted email sent using the out-of-the-box Activity "@baseclass.SendEmailNotification.Pega-EventProcessing:07-10-09" to send out encrypted (s/mime) emails generated emails that could not be decrypted on the receiving end. This was an error caused by the getCertificate activity not being able to read the certificate from keystore, and the logic of pyGetEmailCertificates had been reordered such that the encryption and signing params/logic in SendEmailMessage do not conflict with one another.

SR-A15499 · Issue 242094

WordTextArea control updated for Microsoft Internet Explorer 11

Resolved in Pega Version 7.2.1

The WordTextArea control was not working on IE11, causing the inability to use the WordEmbedMergeTest functionality. WordInclude and WordMerge non-auto generated sections have now been completely revamped with ActiveX technology on all types of IE, particularly IE11 and Edge supported. Note: the WordInclude section contains three text areas by word embed merge function. Currently this fix has only added support for the First Text area.

SR-A15710 · Issue 232090

Additional logging added to diagnose stale thread errors

Resolved in Pega Version 7.2.1

In order to better diagnose issues with stale threads, loggers have been added to the ThreadData class to capture and print any stack trace which is causing the thread to be cleared or destroyed. These loggers will only be printed whenever a stale thread error is thrown in order to maximize log space.

SR-A15866 · Issue 242715

Corrected email decryption and handling

Resolved in Pega Version 7.2.1

When handling encrypted email, the system was decrypting the email body but then attaching it to the work object with file type .p7m and the subject line was copied to the pyInboundEmail.pyBody property. This was cause by a logic flaw, and has been fixed.

SR-A15923 · Issue 230798

Performance improvements for delete ruleform

Resolved in Pega Version 7.2.1

Slow performance was seen after clicking the delete button on a ruleform in installations with very large ruleset lists. Performance has been improved by removing unnecessary calls to the GetAppRulesets activity.

SR-A15924 · Issue 233877

Fixed Dashboard template error in portal

Resolved in Pega Version 7.2.1

A dashboard template null was appearing after performing certain actions on customized case manger tree grid sections, and the Portal became non-workable with the error message "The Dashboard Template" has not been specified. This was found to be a handling issue with the threads and the clipboard that resulted in inconsistent AutoPopulate State across TabThreads, and has been fixed.

SR-A16058 · Issue 241525

Cookie handling updated for Silverlight Merged Word doc creation

Resolved in Pega Version 7.2.1

When trying to create a Merged Word Document using Silverlight based implementation, the Word session started but then generated the error "Failure to reattach server session" and the merge process did not occur. This was an issue where the HTTP requests sent from Silverlight WordMerge control did not contain all of the expected cookies if the cookies contained the equal (=) sign in them. The cookie parsing logic has been fixed to support cookies whose value contains equals (=) sign, and additional diagnostics have been added in the form of Cookies.xml. This file contains the list of cookies parsed from the cookie string retrieved from InternetGetCookieEx. SL adds these cookies to the HttpWebRequest object while making calls to Pega. This file gets created in the session folder (SLWord_*) in the temp directory.

SR-A16144 · Issue 238899

WAS XML parsing performance improved

Resolved in Pega Version 7.2.1

Thread contention in WAS was causing performance issues with the Parse XML execution when configured with substitutions. The hashmap has been updated to handle null substitutions.

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