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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C3300 · Issue 347485

Fixed circumstanced section render fail

Resolved in Pega Version 7.4

A circumstanced section was failing during FUA and could not be rendered. This was traced to the FUA encountering duplicate variable declaration in the generated java, and has been fixed by adding scope parentheses to avoid the same variable declaration in the same scope.

SR-C4390 · Issue 351249

Clipboard page fixed for evaluating Rule-Access-When condition

Resolved in Pega Version 7.4

After logging into the application and accessing the work objects from the worklist, a sporadic error would appear when evaluating Rule-Access-When conditions even though the required page being evaluated against has the data populated. Evaluation showed the execution of the Rule-Access-When condition was failing because the incoming primary page was null, and this was traced to an incorrect clipboard page name in AccessEvaluatior.java. This has been fixed.

SR-C445 · Issue 338352

cluster rule watch lock expires on crash

Resolved in Pega Version 7.4

If the cluster rule watch was in progress and the browser / system crashed, the rule watch became locked until the system (cluster) was restarted. In this case, the disconnect command from Req1 has an encrypted requestor ID because it is an unauthenticated requestor, leading to all String-matches failing. A hook to delete all entries in the distributed rule watch map for a given requestor during its clean up has now been added to resolve this.

SR-C4531 · Issue 347039

JSON key sort performance improvements

Resolved in Pega Version 7.4

Sorting the keys in the JSON output was causing a synchronization bottleneck. The acquisition of the Collator object was synchronized in JDK code when it did not need to be, and the call to Collator.getInstance() has now been replaced with a call to Collator.getInstance(Locale.getDefault()) in order to improve performance.

SR-C4723 · Issue 347122

Added null check for clipboard error after HF

Resolved in Pega Version 7.4

No values were displayed when clicking on a page of the clipboard after installing an update. A null check has been added to correct this.

SR-C4752 · Issue 346874

Autopopulate disabled for clearPageMessages API

Resolved in Pega Version 7.4

A concurrent modification issue was seen in the logs while adding Location, and was traced to an exception in the clearPageMessages API caused by autopopulation. In order to ensure consistent behavior throughout the system, a decision was made to disable Autopopulate in all of the messages-related parent APIs that are NOT expected to change the data on the object.

SR-C5653 · Issue 348605

IOException communication improvements for BIX extractions

Resolved in Pega Version 7.4

An enhancement has been added to improve communications regarding IOExceptions for ExtractImpl. When the exception occurs while trying to close the file, the previous INFO message in the PegaRULES log file has been modified to be a warning message that will include the actual IOEX.getMessage(). This will also be in the PegaBIX log.

SR-C6035 · Issue 349019

Set urandom for Unix/Linux to resolve connection reset

Resolved in Pega Version 7.4

On a Unix system where securerandom.source is not set to /dev/random, running an installation on Oracle using a new version of the JDBC driver caused connection reset. To fix this, Djava.security.egd=file:///dev/urandom has been added to prpcUtils.xml and migrateSystem.xml for use when the database is Oracle and environment is Linux/Unix.

SR-C6280 · Issue 348100

Performance improvements for pyNavigation page cleanup

Resolved in Pega Version 7.4

In order to improve performance, the cleanup of pyNavigation pages has been tuned to reduce memory footprint.

SR-C631 · Issue 345886

DB query performance improvement

Resolved in Pega Version 7.4

Performance improvements have been made by removing unnecessary steps that performed DB queries when packaging cases with no offline attachment support.

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