INC-206109 · Issue 706236
Delayed Learning works correctly with Volume Constraints
Resolved in Pega Version 8.8
When running an outbound campaign using NBA Designers predictions and delayed learning in conjunction with volume constraints, the adaptive models ended up with incorrect feedback if the prediction had an Alternative label configured with a defined waiting window. This has been resolved with the addition of a new flag 'isVolumeConstraintEnabled' during dataflow creation which will check for volume constraint, and a filter in HandleResponses for that flag.
INC-208709 · Issue 710810
Added handling for new requestor in previously authenticated Voice AI group
Resolved in Pega Version 8.8
When attempting to pilot the new Voice AI feature set provided recently in the Customer Service framework, the error "You lack access required to execute RULE-OBJ-ACTIVITY WORK-CHANNEL-INTERACTION-VOICEAI TRANSCRIPTDISPATCHER" was logged. The same was seen for the ConnectToAudioProcessor activity. Investigation showed this could happen when a new requestor that's not authenticated yet gets created with currentAccessGroup already equal to the desired access group, causing the authentication step to be skipped. This has been resolved with an update to address the dataflow thread authentication edge case where the default requestor access group is equal to the dataflow run's access group.
INC-208976 · Issue 719164
Enhanced SSA metrics made available
Resolved in Pega Version 8.8
In order to better diagnose delays related to the time when a Campaign is scheduled to start and the time when the Dataflow actually starts to run, an update has been made to introduce detailed metrics to cover some of the strategy execution key performance intensive areas including invocation of other non-strategy modules like adaptive model scoring and interaction history summaries. These Level 1 diagnostics are enabled by default. Additional lower level internal metrics related to SSA engine execution have also been made available by way of a DSS to collect more runtime insight for diagnosis. To enable the collection of these Level 2 SSA internal metrics, set the dataflow/shape/strategy/detailed_metrics/level2 DSS in the Pega-DecisionEngine rule set to 'true'.
INC-210126 · Issue 708784
Timeout added for Cassandra writes
Resolved in Pega Version 8.8
When using Customer Decision Hub with external C* deployment, attempting to stop a data flow run which was reporting stale threads for some partitions resulted in some of the partitions continuing to run while threads were waiting on the Cassandra save operation. This has been resolved by adding configuration for a timeout when waiting for the results of the save operation, with a default of 300 seconds.
INC-210639 · Issue 705345
Query limit removed from Scenario Planner
Resolved in Pega Version 8.8
Scenario Planner was not correctly finding or opening some Audience Simulations. Investigation showed that when there are 500+ completed data flows, the system was failing to load next 500 records from pegadata.pr_data_decision_ddf_runtime. This has been resolved by removing the query limits, and additional debug logging has been added.
INC-210892 · Issue 706288
Handling corrected for CSV formatted output from CDH
Resolved in Pega Version 8.8
After upgrade, the Output Templates with File output (.csv file extension, comma delimiter) for Customer Decision Hub did not work as expected. Creating an Output Template for use in an action flow with defined fields containing commas for output previously resulted in the individual fields containing commas being enclosed in double quotes, but the output after upgrade instead was enclosing each of the comma-delimited fields in quotes, causing an issue with the original format of the data. This has been corrected.
INC-211251 · Issue 706540
Handling added for Model level Data type empty values
Resolved in Pega Version 8.8
After update, the Email Intelligent Virtual Assistant™ (IVA) was not able find the proper response for the real-time incoming emails but was able to find the topic and response when running it from Dev Studio and Prediction Studio. This was due to an edge case where the model datatype page list property was present on the text analyzer rule and a page was present in it, but the property pyName which actually holds the data type (body, attachment, all) was not present in the page. This has been resolved by updating the system to add 'all' as the datatype if the pyName is blank (null or empty).
INC-211349 · Issue 709607
Service API called directly in CDH simulation
Resolved in Pega Version 8.8
Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.
INC-212169 · Issue 710515
Log4j file security vulnerability issue addressed
Resolved in Pega Version 8.8
A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability
INC-212354 · Issue 711210
Scenario Planner performance improvements
Resolved in Pega Version 8.8
Scenario planner runs were causing out of memory errors on the dataflow nodes. To resolve this, updates have been made to improve performance. Only relevant information will be kept for decision funnel simulations out of SR pages, the memory footprint of data structures used to aggregate and rollup counts has been reduced, and temporary objects will be released as soon as they are not needed anymore.