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-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-A15491 · Issue 231066

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

SR-A15491 · Issue 231387

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

SR-A15495 · Issue 230541

Audit screen supports localization

Resolved in Pega Version 7.2.1

AddCoveredWork has been updated to localize the audit text.

SR-A15496 · Issue 230542

Audit screen supports localization

Resolved in Pega Version 7.2.1

AddCoveredWork has been updated to localize the audit text.

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-A15593 · Issue 231998

Better date selection retention in Calendar view switching

Resolved in Pega Version 7.2.1

Switching to weekly view and then back to daily view in the calendar caused it to reset to the first day of the week and ignore a selected date. selected date is ignored. The container handling has been updated to better handle retaining the selection on different views.

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.

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