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-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-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-A16401 · Issue 232956

Design-time email account accepts Data Page for port number

Resolved in Pega Version 7.2.1

When creating an Email Account rule (Integration-Resources), at design-time, the developer was prevented from using a Data Page reference as the Port number for the Sender or Receiver even though the run-time behavior of using a Data Page reference as a port worked. This has been resolved by removing the UI validation when the input starts with 'equal to', allowing Email Account save and connectivity testing to work with non-parameterized Data Page references for the port number in both Sender and Receiver configurations.

SR-A16406 · Issue 237367

Validation handling added for complex criteria values

Resolved in Pega Version 7.2.1

Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.

SR-A16432 · Issue 232172

Repaired Parse-Byte-Pos in File Listener

Resolved in Pega Version 7.2.1

Due to missing encoding for the type, files in byte format caused a NPE in file listener. This has been fixed.

SR-A16449 · Issue 234627

Java Mail API updated

Resolved in Pega Version 7.2.1

A bug in the Java Mail API 1.5.2 jar caused intermittent failures in receiving email. The API has been updated to the 1.5.3 jar.

SR-A16535 · Issue 231740

Null Boolean and datetime properties passed in command line extraction

Resolved in Pega Version 7.2.1

If a Boolean or a datetime Embedded valuelist /valuegroup /pagelist/page group property was in the WO blob but has no value when extracted from the command line using the -B and -J options, the value in the extract was not valid. This was traced to the handling for empty Boolean and datetime properties, and these properties will now be passed without modification when using the command line options -B and -J in XML output format or when running the extract from the UI.

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