Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

SR-A24517 · Issue 246951

JMX Javadoc available for download

Resolved in Pega Version 7.2.1

The document MBeanJMXJavadoc.zip was last shipped in Pega 7.1.7 and was not present in the on-line documentation. The Mbean Javadoc package is now available for download at the following link: https://pdn.pega.com/release-note/mbean-javadocs-download-file

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-A24787 · Issue 247535

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

SR-A24787 · Issue 245849

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

SR-A24797 · Issue 247605

Localization added to reassign statement in Audit -> History

Resolved in Pega Version 7.2.1

The Audit->History reassign statement "This assignment has been reassigned to Operator ?, as ? is unavailable" was not localized due to the string being hardcoded without using field values. Localization has been added through the newly created field value ROUTINGREASSIGNEDTOSUBSTITUE to be used in the checkForSubstitute function.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us