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-A15903 · Issue 240872
Enhancement added to support non-standard HTML in Ruleforms
Resolved in Pega Version 7.2.1
After manually writing non-standard HTML code in Source mode, switching back to Design mode showed corrupted code. This was caused by the RTE used in the Ruleforms auto-correcting the HTML. A "source only mode" check box option has now been added to the on paragraph, correspondence, and corr fragment Ruleforms that will provide a text area in place of RTE when selected.
SR-A15922 · Issue 231258
Support added for cleartext passwords in Snapstart
Resolved in Pega Version 7.2.1
When posting credentials from an external source, the code makes the assumption that the Password value is encoded and therefore it is decoded prior to being handed to the authentication activity in Pega. This is not always the case. If the Password value is passed as clear text the result in the activity is garbled. This creates problems when subsequent authentication is attempted to an external source. To support this handling, a new DASS 'authentication/Snapstart/pwddecode' has been added. When the setting is false, the password is not decoded in Snapstart cases and will necessitate a cleartext password.
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-A15999 · Issue 232081
Modal window retains size after row delete
Resolved in Pega Version 7.2.1
If a repeat grid inside a modal window was using Expand-pane edit mode, adding a row and deleting it then pressing next caused the modal window to be completely squeezed and unable to be re-expanded. This was caused by a null pointer exception in the flow actions for the modal window, 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-A16012 · Issue 233486
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-A16026 · Issue 233285
Resolved validation error for saving section rule
Resolved in Pega Version 7.2.1
A Participant.FullName validation error occurred when trying to save a section rule when the Dynamic Layout with the .Participant.FullName property was above a repeat grid that has the Finish Assignment action specified for the Enter event. This was caused by a null clipboard page being passed in this configuration, and has been resolved.
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.