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-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.

SR-B88342 · Issue 352097

Memory leaks fixed for CPM portal with Microsoft Internet Explorer

Resolved in Pega Version 7.4

Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.

SR-B89105 · Issue 340037

Offer custom attributes honored

Resolved in Pega Version 7.4

When a property of type 'truefalse' was added under the decision data rule of the newly created Group, the default value set (example: false) did not get reflected in the Offer Flow details tab under the Custom Attributes. Instead, it defaulted to 'true'. This was a problem with the initial value not getting propagated to the marketing layer, and has been fixed.

SR-B89486 · Issue 337423

Added handling for VBD backup integrity

Resolved in Pega Version 7.4

VBD queries and inserts were failing after terminating a VBD node with kill -9. Investigation showed that VBD partition summary was not getting properly propagated to backup partitions after aggregation runs. If the node that owns the partition terminated ungracefully, then the backup partition ended up being promoted to primary with inaccurate state details and subsequent attempts to access the partition failed. This did not occur If the VBD node was shut down in an orderly fashion. To fix this, code has been added to ensure VBD sends proper partition summary data to the backup partitions after aggregation runs.

SR-B89486 · Issue 334029

Added handling for VBD backup integrity

Resolved in Pega Version 7.4

VBD queries and inserts were failing after terminating a VBD node with kill -9. Investigation showed that VBD partition summary was not getting properly propagated to backup partitions after aggregation runs. If the node that owns the partition terminated ungracefully, then the backup partition ended up being promoted to primary with inaccurate state details and subsequent attempts to access the partition failed. This did not occur If the VBD node was shut down in an orderly fashion. To fix this, code has been added to ensure VBD sends proper partition summary data to the backup partitions after aggregation runs.

SR-B90267 · Issue 338706

DataFlowGenerator class files preserved longer

Resolved in Pega Version 7.4

When creating a campaign, running the generated data flow manually resulted in an illegal argument exception indicating a null property name. This was traced to the use of an overwrite data flow API: class files were generated and removed immediately after the DataFlow object is constructed. In some cases, the java classloader may delay loading of the classes, causing the NoClassDefFoundException as files have been already removed. To resolve this, the DataFlowGenerator will now wait one day to remove the classes.

SR-B90756 · Issue 337902

Interaction history lookup fixed

Resolved in Pega Version 7.4

Interaction History load after updated was failing when there were multiple Interaction History shapes on a single strategy rule. This was due to the wrong API being used to parse pxOutcometime and has been fixed.

SR-B91617 · Issue 338996

Added handling for VBD backup integrity

Resolved in Pega Version 7.4

VBD queries and inserts were failing after terminating a VBD node with kill -9. Investigation showed that VBD partition summary was not getting properly propagated to backup partitions after aggregation runs. If the node that owns the partition terminated ungracefully, then the backup partition ended up being promoted to primary with inaccurate state details and subsequent attempts to access the partition failed. This did not occur If the VBD node was shut down in an orderly fashion. To fix this, code has been added to ensure VBD sends proper partition summary data to the backup partitions after aggregation runs.

SR-B91934 · Issue 339644

pzADMInputs made available for serialization

Resolved in Pega Version 7.4

There was an issue with saving the pzADMInputs.pzData (JavaObject) in the blob due to the serialize object option being unset in a final rule. This has been corrected by making pzADMInputs serializable.

SR-B92155 · Issue 343548

ADM and Batch Decision functions compile

Resolved in Pega Version 7.4

Trying to compile the functions of ADM or batch decision was failing with a compilation error. An issue was found in the library which was resulting in picking up and compiling the all the previous versions, and this has been corrected so the system will pick up the latest version of the Batch decisioning Library.

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