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-B77604 · Issue 328533

Hazelcast subscriber dependency removed to ensure Social Connector consistency

Resolved in Pega Version 7.4

Social Connectors that had stopped could not be restarted manually using the Social Configuration Landing Page, and no meaningful error was displayed to screen. After restarting the whole cluster the connector was able to start. The inability to manually restart is a syncing issue: when the social connector has stopped automatically, the node on which it was running stops and the node exits the cluster of nodes of which it was a part. When trying to restart the connector manually using the Social Configuration Landing Page, the node tries to rejoin the cluster but fails because the Hazelcast instance running on the isolated node is not able to sync with the Hazelcast running on the cluster. However, the root of this issue was that Hazelcast was kicking out nodes due to a dependency on the number of subscribers. To resolve this, that dependency has been removed so nodes will not be expelled.

SR-B77908 · Issue 330904

Hazelcast subscriber dependency removed to ensure Social Connector consistency

Resolved in Pega Version 7.4

Social Connectors that had stopped could not be restarted manually using the Social Configuration Landing Page, and no meaningful error was displayed to screen. After restarting the whole cluster the connector was able to start. The inability to manually restart is a syncing issue: when the social connector has stopped automatically, the node on which it was running stops and the node exits the cluster of nodes of which it was a part. When trying to restart the connector manually using the Social Configuration Landing Page, the node tries to rejoin the cluster but fails because the Hazelcast instance running on the isolated node is not able to sync with the Hazelcast running on the cluster. However, the root of this issue was that Hazelcast was kicking out nodes due to a dependency on the number of subscribers. To resolve this, that dependency has been removed so nodes will not be expelled.

SR-B79002 · Issue 329139

Workaround added for Excel export of very large decision tables

Resolved in Pega Version 7.4

When attempting to export a very large decision table, the exception "IllegalStateException: The maximum number of Cell Styles was exceeded" appeared. An .xlsx Workbook allows defining up to 64000 styles, and in this case the number of cell styles created exceeded 64000. In order to support very large decision tables, the cell style creation has been optimized to work within this limit and reuse the styles created.

SR-B81000 · Issue 335702

Resolved exception in Event Strategy with Abstract component

Resolved in Pega Version 7.4

When trying to run the DataFlow-Execute and operation Browse, Browse by keys or Save with a Data Flow which contained Event Strategy, the step was not working because some of the required parameters were not populated. This has been fixed.

SR-B81000 · Issue 332881

Resolved exception in Event Strategy with Abstract component

Resolved in Pega Version 7.4

When trying to run the DataFlow-Execute and operation Browse, Browse by keys or Save with a Data Flow which contained Event Strategy, the step was not working because some of the required parameters were not populated. This has been fixed.

SR-B82340 · Issue 337461

Enhancement added for backwards compatibility of multilevel strategies

Resolved in Pega Version 7.4

A multilevel strategy called from the dataflow was unexpectedly appending the keys from the sub strategy to the main strategy key. For example, if the CustomerID(Key) was 121 and the AccountID(Key) was ABC, after the strategy execution in Dataflow pySubjectID was modified to 121ABC. This was the unintended result of recent behavior changes (as of v7.2.2) for multilevel strategies that were not backwards-compatible. A configuration checkbox has been added to allow changing the default: any new sub-strategy that is added, be it in a new strategy or in a migrated one from recent versions, will have the Multilevel checkbox checked so the new behavior will be enabled and the sub-strategy will set the SubjectID of the parent strategy. Multilevel strategies developed before 7.2.2 and migrated to a 7.4 platform will keep the old behavior and all sub-strategies will have the Multilevel checkbox unchecked.

SR-B84184 · Issue 334535

Removed unnecessary save button for delegated data types

Resolved in Pega Version 7.4

A blank ActivityStatusError message appeared and an error was logged when attempting to edit and save a delegated Data Type. This was traced to an unnecessary Save button: this Save button is used in Data designer to save the Data class and its settings, but records added or updated in the Delegation screen are auto saved. This led to the save generating an exception when it was unable to find the properties which it would use in Data Designer. This has been corrected by changing the display conditions for the Save button so it will not appear for delegated Data types.

SR-B87046 · Issue 340616

Cassandra set as default DF KeyValueStoreFactory

Resolved in Pega Version 7.4

When running Data Flow with ES, the default value (CASSANDRA) is now set for the "KeyValueStoreFactory" parameter on the DF parameter page so the correct state provider will be created for the Event Strategy.

SR-B88244 · Issue 336225

Repaired Facebook comment harvesting

Resolved in Pega Version 7.4

An issue was found with fetching Facebook comments even when the option was enabled in the Facebook connector rule UI. This was traced to the system not using the Boolean variable holding the value for whether comments should be fetched or not, leading the condition to always be False. This has been fixed.

SR-B88244 · Issue 336175

Repaired Facebook comment harvesting

Resolved in Pega Version 7.4

An issue was found with fetching Facebook comments even when the option was enabled in the Facebook connector rule UI. This was traced to the system not using the Boolean variable holding the value for whether comments should be fetched or not, leading the condition to always be False. This has been fixed.

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