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-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-A16012 · Issue 231256
Localization added for locking messages
Resolved in Pega Version 7.2.1
Localization has been added for locking-related messages in LockInfoAdvanced to facilitate translating messages such as "This case is locked by your operator in another PRPC session. Choosing the End other session to release lock option will log out your other PRPC session in order to release the lock. This option may not be effective immediately."
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.