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-A24052 · Issue 248427

Orphaned work objects purged by class

Resolved in Pega Version 7.2.1

Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.

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-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-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-A87552 · Issue 257706

Implicit privileges do not generate warnings

Resolved in Pega Version 7.2.2

RARO with implicit privileges was generating warnings that affected the compliance score. There is a particular format for declaring implicit privileges. i.e. Classname:ruleName, and the system has been updated with a check for this so implicit privileges will not be adding any guardrail warnings.

SR-A101006 · Issue 272734

JDBC password handling corrected

Resolved in Pega Version 7.2.2

After upgrade, a JDBC database connection on WebSphere 8.5/Oracle 11G indicated success on test connection, but a username/password "connection could not be obtained" error was thrown when attempting to save the connection. This was due to the handling of the encrypted password, and has been fixed.

SR-A101808 · Issue 269472

WebSphere deployment documentation updated to clarify JVM configuration advice

Resolved in Pega Version 7.2.2

The deployment guides for WebSphere have been updated to clearly distinguish between Oracle and IBM JVM when providing JVM configuration advice.

SR-A24989 · Issue 248910

WebSphere deployment guide updated to clarify scope settings

Resolved in Pega Version 7.2.2

The WebSphere Deployment Guide has been updated to indicate that the scope must be "server". If this is not set correctly in a split schema installation, the defaultSchema namespace bindings are defined at the cell level and will not be picked up at start, and the database user in the jdbc/PegaRULES datasource will not have the necessary privileges to run the system. Please see WAS deployment guides on the PDN for further information.

SR-B599 · Issue 270485

Flow Dependency queries performance improvements

Resolved in Pega Version 7.2.2

Case dependency queries executed by PEGA have been tuned to improve system performance when mid flow dependencies are getting fulfilled.

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