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