INC-180246 · Issue 664948
Support for apostrophe added to keyword tokenization
Resolved in Pega Version 8.8
A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.
INC-180762 · Issue 666291
Calendar gadget correctly displays event of >31 days
Resolved in Pega Version 8.8
When using the pxCalendar gadget to display a hotel reservation of duration > 31 days, the entire bar was not displayed on the PEGA calendar. Investigation showed that eventslist was not considering the month value, and this has been resolved by updating the pzEventPreProcessing activity to check for month.
INC-194348 · Issue 682339
Resolved multiple copies of Pega0050 alerts
Resolved in Pega Version 8.8
The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.
INC-198914 · Issue 686938
PMML updated for nested 'if'
Resolved in Pega Version 8.8
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.
INC-200802 · Issue 699966
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.8
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.
INC-202111 · Issue 710107
Logging extended for PRPCPropertyInfoProvider
Resolved in Pega Version 8.8
In order to assist with diagnosing issues with Kafka and JSON, additional logging has been added for PRPCPropertyInfoProvider.
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.