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.

INC-212354 · Issue 711210

Scenario Planner performance improvements

Resolved in Pega Version 8.8

Scenario planner runs were causing out of memory errors on the dataflow nodes. To resolve this, updates have been made to improve performance. Only relevant information will be kept for decision funnel simulations out of SR pages, the memory footprint of data structures used to aggregate and rollup counts has been reduced, and temporary objects will be released as soon as they are not needed anymore.

INC-212704 · Issue 707114

Explicit lock release added for Cassandra threads

Resolved in Pega Version 8.8

Customer Decision Hub was not responding for realtime request REST service calls, and thread dumps during start up were showing all HTTP request threads were stuck in CassandraSessionCache.getSession. If an error is thrown while invalidating an old Cassandra session, the system may fail to unlock the write lock. This results in subsequent threads being blocked on the session cache's ReadWriteLock when they attempt to retrieve the session from the session cache. To resolve this, an update has been made to ensure that invalidate session is wrapped in a finally block that releases the write lock and log any thrown errors.

INC-212754 · Issue 708690

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.8

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability

INC-213176 · Issue 709976

Data flow stability improvements

Resolved in Pega Version 8.8

All nodes were showing as active and running in the cluster, including background, stream, web nodes, but the queue processor would not start. Log entries indicated "IllegalStateException: Invalid run transition found [PENDING_NODES->COMPLETED] on run [DF_OutboundPreProcessing_SMS] by [EventDescription{originator=CheckNodeAvailabilityTask, reason=Restoring previous state." Due to this, all dataflows were moved to queued state. As soon as the corrupted dataflow was deleted the other dataflows were resumed. To resolve this, data flow stability improvements have been added along with better handling of runs in Queued state.

INC-213189 · Issue 707343

Addressed performance issues for classless DSMClipboardPage

Resolved in Pega Version 8.8

The DSMClipboardPage implementation handles Page Group access as a classless page (i.e. pxObjClass = ""), creating potential performance issues in implementations where the page group is used with a very large number of distinct AccountIDs in a short period. This has been resolved by updating the system to not cache keys for page group classless page.

INC-213217 · Issue 714193

Updated context handling for executing data transforms in dataflows

Resolved in Pega Version 8.8

When performing a sort operation in a data transform on a pagelist and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.

INC-213945 · Issue 709367

Additional logging and executor work for Adaptive Decision Manager

Resolved in Pega Version 8.8

The Adaptive Decision Manager Pulse operation stopped running on some of the ADM nodes, causing an impact on the model update. To address this, some additional protections have been added for pulse operations running in a scheduled executor, and ERROR logging has been enabled.

INC-216490 · Issue 713634

pxIdentifier dynamically set for DecisionData while using GOS

Resolved in Pega Version 8.8

When using a Decision Data component in a strategy which was wrapped with Globally Optimized Strategy (GOS), no results were generated from the DataJoin shape under optimized execution. Investigation showed this was caused by a missing .pxIdentifier for the DecisionData shape during GOS execution. There was a workaround of unselecting the checkbox on the Advanced tab in the Decision Data component, but this has been resolved by updating the strategy kernel service so it will dynamically construct the pxIdentifier based on the skills assignment module (SSA).

INC-217290 · Issue 721374

Added support for creating predictive models in Production

Resolved in Pega Version 8.8

While creating a new predictive model rule in Prediction studio, the case was going into broken process after selecting the template with the error message "Error loading D_ProjectList , Reason : No databases defined in properties file:/databases.properties". This was an unexpected use case for creating models in Production level, and has been resolved by updating the flows to turn off the draft mode in this scenario.

INC-217728 · Issue 712732

Made CommitLog messages more resilient to class change

Resolved in Pega Version 8.8

Persistent class mismatch exceptions were seen while refreshing the ADM models after updating from Pega 8.5. This was caused by changes to the Cassandra adm_commitlog message schema which caused the commit log messages generated to be incompatible with the deserialisation logic present in higher versions of Pega, but as the commit log messages had a time to live of 24 hours the issue self-resolved. However, this has been resolved by setting serialVersionUID for the ModelParameters class so CommitLog messages are now compatible with future minor and patch releases.

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