INC-140821 · Issue 600748
Resolved Intermittent Access Group Issue for GetBundleEventDecisionDetails
Resolved in Pega Version 8.6
When using a REST service that calls the GetBundleEventDecisionDetails activity and dataflow to send the treatment in multiple channels, intermittent access issue related errors appeared while running the activity in logs for multiple customers. This was traced to a missed use case for authentication, and has been resolved.
INC-141579 · Issue 591851
Enhancement added for node heartbeat recovery process
Resolved in Pega Version 8.6
Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.
INC-142084 · Issue 599874
Support added for expression in strategy scorecards
Resolved in Pega Version 8.6
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
INC-142118 · Issue 597313
Data Migration Import/Export made more resilient
Resolved in Pega Version 8.6
The entire data migration operation (export or import) was marked as "FAILED" even if the operation failed for just one type of data. While managing the failure, the operation deleted any completed data flow runs as part of the clean-up and only retained the failed data flow runs for use in further analysis. Because the queued runs could not be deleted, the data migration case became a broken process. At the root of the issue, the data export work item was failing due to one or more DSM service nodes being non-functional based on a validation failure in the case type that runs a check for the presence of functional DSM nodes before starting the data migration operation. This validation can return false negatives, especially on Cloud where the nodes are usually swapped seamlessly without the function realizing it. In such cases, the validation function returned false despite the DSM service nodes being up and running. This has been resolved by adding handling for the failed data migration case by stopping and deleting the open data flows and by disabling the validation which checks for functional nodes.
INC-142216 · Issue 596667
VBD performance improvements
Resolved in Pega Version 8.6
Performance issues were seen when running a decision funnel simulation. As part of the simulation, a VBD collection was created on the fly to store the metrics and linked to the simulation. Before each insert, which happened in batches of 500 records, there was a check if such collection exists. This check was required in earlier versions as the process relied on the VBD service being running, and the run would fail otherwise. Recently, VBD handling became more resilient and was updated to allow inserts even if the VBD server is down. If the VBD service is stopped before the simulation is completed, the simulation will continue writing records. When the VBD service starts again, it reads the backlog, and the simulation displays the final results. To adapt to this resiliency and improve performance, the system has been updated so that the VBD collection is not created and checked before the insert call, but only when the simulation is run or scheduled.
INC-142669 · Issue 599061
JMX exception logging corrected
Resolved in Pega Version 8.6
Although the process of decommissioning a Cassandra node worked correctly, JMX errors were visible in the logs during the operation. This has been corrected.
INC-142674 · Issue 594495
Enhancement added for node heartbeat recovery process
Resolved in Pega Version 8.6
Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.
INC-143121 · Issue 610733
Timeout for loading predictors made configurable
Resolved in Pega Version 8.6
When using an extremely large number of predictors, the Report definition pzADMPredictorsFilter was suffering timeouts due to the time for loading predictors from the database exceeding the time threshold allowed. This has been resolved by marking the rule as editable to allow custom setting of the threshold according to need.
INC-143441 · Issue 608897
Strategy Simulation Runs made more resilient
Resolved in Pega Version 8.6
Intermittently, a decision funnel simulation would fail with particular strategy logic or a particular StrategyTracker would not contain the results for all components so the system would not be able to calculate input SRs. Handling has now been added to make the simulations more resilient so they will not fail with a null pointer error due to incomplete strategy inputs.
INC-147692 · Issue 605279
Date properties on DSMClipboardPages formatted by determined type
Resolved in Pega Version 8.6
When data flow data was sourced from a File type dataset, the destination data showed 2020101+ for a valid date like 20201016. This has been resolved by modifying the way Date properties are read for DSMClipboardPages: properties which are instances of Date will be formatted considering the type, which will be deduced with usage of "getType" method. Invocation of this method can decrease performance of DSMClipboardPages, so it will be executed only when property will be of date type.