SR-A19297 · Issue 237347
Added ability to set custom HTTP security headers
Resolved in Pega Version 7.2.1
XSS protections were interfering with the ability to set custom HTTP headers. To enable this, the system will use dynamic system settings from http/responseHeaders and add them to every HTTP response.
SR-A19406 · Issue 236911
Pega0031 debug tool stack trace updated
Resolved in Pega Version 7.2.1
When an activity was run which performed a show-html/show-stream twice, the first PEGA0031 alert was raised with no stack trace. The second instance of show-html/show-stream would log the PEGA0031 alert along with the stack trace of this interaction, and the first would not be seen. This was caused by the improper clearance of the pxHTMLStream property on the thread page at the end of the HTTP interaction and has been fixed.
SR-A19512 · Issue 238622
Standardized date time used for memo history compare
Resolved in Pega Version 7.2.1
History compare displayed unexpected results for the pxSaveDateTime for a Rule-Application record when a memo was added and then it was compared to another record in the history log. The comparison logic was not looking at the save time of the memo, but rather the save time of the rule itself, resulting in the mismatch. This has been resolved.
SR-A19652 · Issue 246778
BIX filter failure alert added
Resolved in Pega Version 7.2.1
A warning has been added to issue an alert when filters are not being added while generating a BIX query.
SR-A19704 · Issue 234771
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A19761 · Issue 237073
Fixed Require flag usage for Validate rule
Resolved in Pega Version 7.2.1
Saving a Validate rule that had a Required flag on one or more properties automatically reset the value, resulting in the inability to set the Required flag on any property of the rule. This was an error in the temporary activity handling, and has been fixed.
SR-A19803 · Issue 248102
Scheduled report generation errors skip sending email
Resolved in Pega Version 7.2.1
When a scheduled report encountered a database error, a blank email was sent to the recipients each time it retried instead of the expected behavior of stopping the process and not sending the correspondence. The code has been modified to ensure the process will properly skip the rest of the steps if there is StepStatusFail in the report generation.
SR-A19811 · Issue 241385
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-A19811 · Issue 239285
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-A19980 · Issue 242374
Added RunShortCut security for reporting
Resolved in Pega Version 7.2.1
Unauthorized users were able to run out-of-the-box reports through pxRunShortcut by updating the address URL and executing the final "pxRunShortcut" activity. pxRunShortcut now includes the function "pyCheckSecurity" for customers to write their own privilege conditions, and Page-Set-Messages will display a message created in the pyRuleSecurityErrorMsg HTML.