SR-A18009 · Issue 236493
Default values set for row properties missing after upgrade
Resolved in Pega Version 7.2.1
After upgrade, the default values for .pyUI.pySource.pyRowKeyInfo.pyGetRowKey and .pyUI.pyBody.pyUIFilters.pyGetDistinctRows properties were not set in Rule-Obj-Report-Definition!pzUpgradeOnOpen DataTransform. This caused old reports to not have click action on the grid in report viewer. The system will now set default values for these properties to help the old reports to run as expected post-upgrade.
SR-A18899 · Issue 236697
Operator ID screen messages localized
Resolved in Pega Version 7.2.1
Localization has been added for error messages generated in the Operator ID Screen.
SR-A18928 · Issue 241932
AddDays calendar logic updated
Resolved in Pega Version 7.2.1
The AddDays function in a Business Calendar was not working correctly because it did not have a default timezone. The Days RUF with 4 parameters ADDDAYS--(STRING,INT,BOOLEAN,STRING) has been set to use the GMT timezone in cases where the use business calendar parameter is sent as false.
SR-A19159 · Issue 237816
Enabled custom parameter input for PushBodyCountVar
Resolved in Pega Version 7.2.1
After importing custom markup language based on JSP 2.0 tlds and mustache templates and writing a custom HTML rule to generate JSP, the error s were generated relating to the default value of aTagPushBodyCountVar parameter. To enable the custom input, the generateCustomStart() method has been modified to use a passed-in parameter by way of aTagPushBodyCountVar instead aVisitor.getPushBodyCountVar().
SR-A19219 · Issue 237911
RACache performance improved
Resolved in Pega Version 7.2.1
Pega0005 alerts were appearing during system startup, and queries were taking an excessive amount of time. Bind variables are now used in the RACache loading query at server start up to improve performance.
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.