INC-216490 · Issue 713633
pxIdentifier dynamically set for DecisionData while using GOS
Resolved in Pega Version 8.7.2
When using a Decision Data component in a strategy which was wrapped with Globally Optimized Strategy (GOS), no results were generated from the DataJoin shape under optimized execution. Investigation showed this was caused by a missing .pxIdentifier for the DecisionData shape during GOS execution. There was a workaround of unselecting the checkbox on the Advanced tab in the Decision Data component, but this has been resolved by updating the strategy kernel service so it will dynamically construct the pxIdentifier based on the skills assignment module (SSA).
INC-217728 · Issue 712731
Made CommitLog messages more resilient to class change
Resolved in Pega Version 8.7.2
Persistent class mismatch exceptions were seen while refreshing the ADM models after updating from Pega 8.5. This was caused by changes to the Cassandra adm_commitlog message schema which caused the commit log messages generated to be incompatible with the deserialisation logic present in higher versions of Pega, but as the commit log messages had a time to live of 24 hours the issue self-resolved. However, this has been resolved by setting serialVersionUID for the ModelParameters class so CommitLog messages are now compatible with future minor and patch releases.
INC-218757 · Issue 714551
AESRemote updated to be asynchronous
Resolved in Pega Version 8.7.2
The Autonomic Event Services (AES) agent PushCDHMetrics became stuck and was not pushing metrics to the console. This has been resolved by updating AESRemote to be asynchronous.
INC-220642 · Issue 717033
Updated context handling for executing data transforms in dataflows
Resolved in Pega Version 8.7.2
When performing a sort operation in a data transform on a page list and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.
INC-202111 · Issue 710105
Logging extended for PRPCPropertyInfoProvider
Resolved in Pega Version 8.6.5
In order to assist with diagnosing issues with Kafka and JSON, additional logging has been added for PRPCPropertyInfoProvider.
INC-208976 · Issue 719166
Enhanced SSA metrics made available
Resolved in Pega Version 8.6.5
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 which will generate detailed metrics to cover some of the strategy execution key performance intensive areas. 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'. A comprehensive set of enhanced metrics will be available in Pega 8.8.
INC-213217 · Issue 714194
Updated context handling for executing data transforms in dataflows
Resolved in Pega Version 8.6.5
When performing a sort operation in a data transform on a page list and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.
INC-215601 · Issue 721524
Explicit Kerberos renewal added for HDFS
Resolved in Pega Version 8.6.5
When using WebSphere/IBM with Hadoop connectivity, the Kerberos credentials were expiring after 7 days and causing connectivity failures. Investigation showed the Apache Hadoop HDFS Client was not renewing the ticket even when there were operation calls every few hours. To resolve this, an enhancement has been added to the Pega HDFS client which will explicitly tell Hadoop authentication layer to check for Kerberos ticket renewal instead of relying on Hadoop built-in logic.
INC-217290 · Issue 721376
Added support for creating predictive models in Production
Resolved in Pega Version 8.6.5
While creating a new predictive model rule in Prediction studio, the case was going into broken process after selecting the template with the error message "Error loading D_ProjectList , Reason : No databases defined in properties file:/databases.properties". This was an unexpected use case for creating models in Production level, and has been resolved by updating the flows to turn off the draft mode in this scenario.
INC-217728 · Issue 712733
Made CommitLog messages more resilient to class change
Resolved in Pega Version 8.6.5
Persistent class mismatch exceptions were seen while refreshing the ADM models after updating from Pega 8.5. This was caused by changes to the Cassandra adm_commitlog message schema which caused the commit log messages generated to be incompatible with the deserialisation logic present in higher versions of Pega, but as the commit log messages had a time to live of 24 hours the issue self-resolved. However, this has been resolved by setting serialVersionUID for the ModelParameters class so CommitLog messages are now compatible with future minor and patch releases.