SR-A24114 · Issue 246936
Removed hardcoding from pyWorkPage
Resolved in Pega Version 7.2.1
The function pzIsAFollower contains "pyWorkPage", which is hard-coded to get the handle of the Primary Page. However, if the primary page was a different named page and not pyWorkPage, an exception was generated. This has been resolved by removing the hardcoding in pzIsAFollower().An overloaded function has been created for pzIsAFollower() which takes reference page name as parameter, and the when rule which calls this utility function to pass the parameter has been updated.
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-A24421 · Issue 247092
Case Audit section localized
Resolved in Pega Version 7.2.1
The ChangeStageAutomatic field value was not showing the localized value in audit due to the ChangeStageAutomatic field value not being properly picked when encountering a blank field. To fix this, Embed-ListParams.getHistoryList will set the localized pyMemo instead of the direct pyMemo in pyMessageKey when it is blank.
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-A24444 · Issue 247096
Page name in pxCreateTopCase dynamically generated
Resolved in Pega Version 7.2.1
The page name of the Top case being created was hard-coded in pxCreateTopCase, causing corrupted data in FW. This has been fixed by dynamically generating the page name and removing it as well at the end of pxCreateTopCase.
SR-A24478 · Issue 247983
Diagnostic logging added to upgrade Java Syntax task
Resolved in Pega Version 7.2.1
While running the upgrade.sh script to upgrade an in-place single-schema upgrade, the script halted while performing "Scanning Class" operations and remained there for over 8 hours. Attempting to resume appeared to proceed for a few minutes before halting again and remaining at the same point. The problem was traced to list views getting the PMD going into an infinite loop during the upgrade java syntax task. Diagnostic logging has been added to the PreUpgradeRuleAnalyzer/JavaParser code to add a log statement to print any keys which are getting processed when errors occur.
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-A24508 · Issue 246983
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-A24516 · Issue 247668
Reports correctly deleted
Resolved in Pega Version 7.2.1
Reports are not deleted after deleting a shortcut, causing errors when trying to create reports using the same name. The logic for UpdateCheckIn has been corrected so that it will not jump to block the rule and will instead delete the rule.