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-A16148 · Issue 231915
Support for value list and value group editing/deletion added
Resolved in Pega Version 7.2.1
Trying to update a valuelist using the clipboard generated an error during the processing after clicking on save due to the processing of finding the page value coupled to the valuelist within the activity UpdatePageFromCLipboardInMultiThreadedContext (step1). Support has been added for value list and value group editing/deletion to correct this.
SR-A16256 · Issue 231874
Exception recovery added to PegaAESRemote
Resolved in Pega Version 7.2.1
The presence of a bad or missing data-admin-db-table was causing an exception and exit when the PegaAESRemote agent sent data to PDC or AES to support analysis. The code has now been updated to handle the exception and continue to build the XML and send it across to PDC/AES.
SR-A16333 · Issue 232083
Added missing quotes for changetrack_updatefield values
Resolved in Pega Version 7.2.1
The From and To entries coupled to the field value changetrack_update were missing the necessary quotes for the Change events. This omission has been fixed.
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.
SR-A16398 · Issue 232765
UI-Kit updated to use Open Work by Handle in pyFavorites
Resolved in Pega Version 7.2.1
In the Manager portal, clicking on a parent case in the "Following" section opened the subcase instead of the parent case that was being followed. The issue occurred when utilizing the pyFavorites section in a UI-Kit that was configured with the Open Work Item action. To correct this, the UI-Kit for this release has been changed to use the Open Work by Handle option.
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-A16406 · Issue 231876
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.