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-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
SR-A17654 · Issue 234844
Stack trace will not display in REST errors
Resolved in Pega Version 7.2.1
To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.
SR-A17654 · Issue 246367
Stack trace will not display in REST errors
Resolved in Pega Version 7.2.1
To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.
SR-A17748 · Issue 233597
TrimLog performance improved
Resolved in Pega Version 7.2.1
Activity log.trimlog is called several times from the systemCleaner agent to clean up old entries of generally unused Log- classes. In order to improve performance on large logs, the previous partial load and delete method has been updated to a bulk cleanup using the purgeTableContainingClass() API in the Pega Database.
SR-A17976 · Issue 239119
Updated SendEmailMessage to handle images with spaces in the filename
Resolved in Pega Version 7.2.1
When an image was inserted into a draft email and sent, the image was visible in PRPC but not at the receiving end. This was a problem with the regex available in the SendEmailMessage activity not being able to handle file names containing spaces: handling for this has now been added.