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-A14892 · Issue 234201

Consistent Indexing initialization

Resolved in Pega Version 7.2.1

The first node in the cluster that was started was getting stuck at "Initializing Search Infrastructure." Elastic search was causing WAS7 to fail on startup due to the instances of indexerAgents (FTSindexerAgent, SystemIndexeragent) only being initialized in distributed mode, and an NPE was generated in non-distributed mode. This has been resolved by setting the indexerAgent instances to always initialize irrespective of the DASS indexing/distributed.

SR-A15083 · Issue 237798

Cursor leak issue resolved

Resolved in Pega Version 7.2.1

Cursor leaks were observed in the LockManagerImpl code, resulting in the error "Maximum number of open cursors exceeded". This has been resolved.

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 236472

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-A15710 · Issue 236472

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

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-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.

SR-A16337 · Issue 232778

OCXinstaller install.bat script for Windows explicitly sets .cab file path

Resolved in Pega Version 7.2.1

The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.

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