SR-A17004 · Issue 239165
Silverlight updated for URL encryption
Resolved in Pega Version 7.2.1
If URL encryption is turned on in an environment where the Silverlight version of the WordMerge feature in use doesn't support encrypted URLs the error "Silverlight Control ERROR in 'GetAbsUriAllCookies': Cannot find absolute server URI when trying to launch word from within their application" was generated. The system has now been updated to detect the use of URL encryption in Silverlight via out-of-the-box JavaScript APIs and the URLs will be accordingly encrypted. The Silverlight Prerequisites installer has also been modified to include the latest certificate.
SR-A17016 · Issue 234926
Repaired multiple-value filters for RD data transform
Resolved in Pega Version 7.2.1
When using a report definition in which the filter values were supplied through the data transform rule, a single given value was correctly passed but multiple values were not. This was traced to the encoding of double quotes which were then not replaced in the correct step, and has been fixed.
SR-A17217 · Issue 234378
Security enhanced for RelayState
Resolved in Pega Version 7.2.1
Transport layer security (enabling SSL/TLS for all the communications) has been added to RelayState handling.
SR-A17278 · Issue 232804
Corrected file output override of Manifest path
Resolved in Pega Version 7.2.1
If a path was indicated by selecting the 'Include Manifest' check and the rule was saved, the manifest output directory path was overridden by the value of File Output directory the next time the rule was opened. This has been fixed with changes to pzCopyContentstoManifest DataTransform that will auto-populate the Manifest file directory and Manifest file name with the output file directory, and then output the file name of the extract only if the Manifest file directory and Manifest file name are empty.
SR-A17288 · Issue 237095
Email listener leaves empty text body untouched
Resolved in Pega Version 7.2.1
When Email Listener received a new email of Content-Type: text/plain with a subject line but an empty message body, it copied the email's subject to the email's body. This was traced to code explicitly performing this copying, which has been removed.
SR-A17313 · Issue 246970
Function added to XML manifest that includes empty pagelists for count
Resolved in Pega Version 7.2.1
If a PageList with empty properties is extracted to XML, it still appears in the XML file with empty tags but the entry is not counted for the pxTotalClassInstanceCount pagelist nodes count in the manifest file. This is as intended. As an enhancement to help with validation of the extract, an additional function pxTotalInstanceCount has been added to summarize all of the entries that are included in the XML regardless of whether or not they are populated with data. This will equal the pxTotalClassInstanceCount plus the number of empty tag entries.
SR-A17399 · Issue 104807
Cleared authentication requirement check box for PZINVOKECASETYPE
Resolved in Pega Version 7.2.1
SOAP clients were not able to execute authenticated activities (DATA-PARTY-PERSON VALIDATE , WORK-COVER- PZINVOKECASETYPE) due to the out-of-the-box final activity pzInvokeCaseType having 'Require authentication to run' default to checked. This default interfered with the ability to remove a covered case from a cover case, and has been changed.
SR-A17488 · Issue 234010
Corrected truncation of localized text in Report Viewer filters
Resolved in Pega Version 7.2.1
The localized test "Select Values" text was being truncated in the Report Viewer filters were enabled. This setting has been updated to take the additional width without truncating.
SR-A17497 · Issue 234925
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.
SR-A17649 · Issue 233752
SQL generation modified for "Optimize for Reporting"
Resolved in Pega Version 7.2.1
After using the wizard to update Properties via "Optimize for Reporting", Report Definition will create SQL that is unique if the optimized property name is too long. This can result in the unique property name exceeding the 30 character field length, which then triggers the generation of a unique id with P +timestamp as the column alias name. Unfortunately, this means even if the same report is executed multiple times, the query would be different each time because of the column aliases and therefore the DB engine won't take the benefit of prepared statement caching and performance could be effected. To create the most effective performance, the column alias generation has been modified as below to make the column alias the same across multiple runs of RD: - using 25characters in propertyname and suffix it with index of the field location in RD select, L for list report - using 25characters in propertyname and suffix it with index of the field location in RD select, G for group fields in summary report