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-A17560 · Issue 234697
Added dynamic check to HarnessPurpose parameter
Resolved in Pega Version 7.2.1
If a main flow referenced a subflow with a parameter "HarnessPurpose" and value "Perform", accessing the subflow generated the error "Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness." This was an issue where the HarnessPurpose parameter caused a reset of the pxFormName property in the newassignPage, and this has been fixed by checking if the harnesspurpose is dynamic before setting the pxFormName.
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-A17670 · Issue 236156
New display control for attachment category delete privilege
Resolved in Pega Version 7.2.1
If an attachment category delete privilege was set to 'never' but there was no access group referenced for it, it was possible for the user to delete the attachment. This was a scenario where even though the delete-all option was enabled for the attachment category, the display of the delete icon was not controlled by this access specifier. A new when condition "HaveAttachmentDeletePrivileges" has now been added on the delete icon to control whether or not the icon appears.
SR-A17738 · Issue 234851
Authentication requirement removed from OnProcessEnd
Resolved in Pega Version 7.2.1
pzChangeStageWrapper calls pzOnProcessEnd, which requires Authentication and is a Final rule. This created an issue using the ChangeStageWrapper without authentication, and the authentication requirement has been removed from OnProcessEnd.
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-A17852 · Issue 234570
Edit Validate passes parameters to message rule
Resolved in Pega Version 7.2.1
When using an Edit Validate rule in the condition, functions could not be passed as a parameter into a message rule. This has been fixed.
SR-A17938 · Issue 236489
Custom header section of Calendar retained after Smartinfo popup displayed
Resolved in Pega Version 7.2.1
Due to the way the date/time parameters were handed, the Smartinfo popup was overriding a currency icon and logo set into a custom header of Calendar events to show currency market closings (holiday, etc.). A check for custom values has now been added.