SR-A23694 · Issue 246996
Timeliness functions modified to return 0 in place of NULL
Resolved in Pega Version 7.2.1
The "Timeliness" function aliases returned NULL for all the CASE statements that returned false, but NULL value using the AVERAGE summarize function in a report definition returned an incorrect result. The following Function Aliases have been updated to return a 0 instead of NULL when the result is false: - pxSLAAgeByClassTimeliness - pxSLAAgeTimeliness - pxSLAHistoryTimeliness - pxSLAAssignTimeliness
SR-A23862 · Issue 246708
VPD Data Page passes custom properties
Resolved in Pega Version 7.2.1
When trying to set up Oracle VPD custom properties as instructed in a PDN article, an exception was generated due to missing handling for custom class/property definitions. The new pyCustomProperties if PageList has been added to Code-Pega-DBApplicationContext .
SR-A23862 · Issue 246796
VPD Data Page passes custom properties
Resolved in Pega Version 7.2.1
When trying to set up Oracle VPD custom properties as instructed in a PDN article, an exception was generated due to missing handling for custom class/property definitions. The new pyCustomProperties if PageList has been added to Code-Pega-DBApplicationContext .
SR-A23915 · Issue 247392
Apache Struts updated for security
Resolved in Pega Version 7.2.1
Apache Struts has been updated to version 2.3.28 to protect against potential security vulnerabilities exposed when Dynamic Method Invocation is enabled, removing the ability for remote attackers to execute arbitrary code via method: prefix, related to chained expressions.
SR-A24183 · Issue 247604
Added visibility for XML Stream Rule Form fields
Resolved in Pega Version 7.2.1
The configurable fields "Stream Name" and "XML Type" have been made visible when "Mapping Mode" is "Apply Rule" in the XML Stream Rule Form.
SR-A24402 · Issue 246696
Tuned scheduled reports start calculations
Resolved in Pega Version 7.2.1
In recurring schedule - daily pattern, if the start date was more than one day in the future, either the next scheduled run time was wrongly calculated as tomorrow with the right hour or if the start date was tomorrow, the next scheduled run time was wrongly calculated as today with the right hour. To fix this, the Next execution time calculation in DailyPattern.java now considers the mStartDateTime value.
SR-A24439 · Issue 247958
Operator ID always clickable link
Resolved in Pega Version 7.2.1
When the operator profile was opened from Operator menu drop down at the top right corner of Designer Studio or from the Case Manager portal, the ID link in the ?Operator Profile? popup was clickable in Microsoft Internet Explorer but not clickable in Google Chrome. The system will now present these as links regardless of browser.
SR-A24508 · Issue 247393
Apache Struts updated for security
Resolved in Pega Version 7.2.1
Apache Struts has been updated to version 2.3.28 to protect against potential security vulnerabilities exposed when Dynamic Method Invocation is enabled, removing the ability for remote attackers to execute arbitrary code via method: prefix, related to chained expressions.
SR-A24598 · Issue 247394
Apache Struts updated for security
Resolved in Pega Version 7.2.1
Apache Struts has been updated to version 2.3.28 to protect against potential security vulnerabilities exposed when Dynamic Method Invocation is enabled, removing the ability for remote attackers to execute arbitrary code via method: prefix, related to chained expressions.
SR-A4613 · Issue 227870
Updated logging for "Obfuscated URL tampering" errors
Resolved in Pega Version 7.2.1
The error "pegarules.util.URLObfuscation) ERROR - Obfuscated URL tampering - unable to derive cleartext data" was being logged when the "cookie/HttpOnly" parameter was set. This was traced to the unobfuscating of data failing at the server end, and the loggers have been updated to print requestor data for better diagnostics.