SR-A17773 · Issue 234118
Custom field value visible for maxloginattempts message
Resolved in Pega Version 7.2.1
In order to support a customized field value message once a user crosses the allowed invalid login attempts threshold, a new overloaded method of prepareStatusInfo() has been introduced in PRDiagnosticStream.java that will not mask the exception details with generic error message.
SR-A17916 · Issue 234503
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.
SR-A17916 · Issue 233771
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.
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.