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-189580 · Issue 672855

Cleanup added for disabled/deleted operator passivation data

Resolved in Pega Version 8.4.6

In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.

INC-193442 · Issue 679180

ServicePackage thread handling improvements

Resolved in Pega Version 8.4.6

Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler. This also resolves a 504 Gateway Time-out error intermittently seen while trying to open the URL of the Pega application.

INC-174781 · Issue 655123

Kerberos authentication added for external Cassandra

Resolved in Pega Version 8.4.6

Support has been added for Kerberos authentication with Cassandra.

INC-175207 · Issue 664362

Added handling for DSM Services stuck in leaving status after database outage

Resolved in Pega Version 8.4.6

During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update has been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage.

INC-176757 · Issue 657786

Interaction History properly saved when running strategy on a different data flow

Resolved in Pega Version 8.4.6

Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.

INC-177877 · Issue 661175

Write lock check added to avoid thread contention

Resolved in Pega Version 8.4.6

After updating the Pega platform and NBA Designer, a significant drop in performance for multilevel strategies was observed. Investigation showed that invoking a sub strategy containing external input intermittently caused a thread contention issue related to write lock. This was traced to overzealous write locking of a component where only a read lock for the thread was required, and has been resolved by adding a verification check to determine whether a write lock is necessary for a given operation before acquiring it.

INC-184099 · Issue 664855

Localization added to DelegateDescription

Resolved in Pega Version 8.4.6

Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription.

INC-185045 · Issue 672419

Performance improvements for action check-in

Resolved in Pega Version 8.4.6

The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.

INC-186437 · Issue 669187

Updated entity attachment extraction tokenizers

Resolved in Pega Version 8.4.6

After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.

INC-186889 · Issue 674016

Unused DSS compiledExpressions now defaults to false

Resolved in Pega Version 8.4.6

After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.

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