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-A24962 · Issue 250080

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

SR-A24962 · Issue 248678

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

SR-A80784 · Issue 254197

Enhancement for Facebook connector retrieval

Resolved in Pega Version 7.2.2

Whenever the Facebook connector was restarted, historical posts on the monitored page were being fetched and duplicate documents were getting harvested into the DB. To resolve this, a new search parameter has been added for the Facebook connector that will receive a date as parameter for how many period/days of historical data to fetch.

SR-B6425 · Issue 275629

Scrum Board chicklet error resolved

Resolved in Pega Version 7.2.2

After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.

SR-A75956 · Issue 250547

D_OfflineWorkIDs DP performance improvements

Resolved in Pega Version 7.2.2

The logic of D_OfflineWorkIDs DP has been updated to improve performance for the SA PROD App.

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.

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