INC-182137 · Issue 662487
Multistage Prediction Logic improved
Resolved in Pega Version 8.6.2
When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.
INC-183431 · Issue 665161
Strategy execution queries tuned
Resolved in Pega Version 8.6.2
During NBA strategy execution, interaction history summaries were queried multiple times for a single strategy execution. To improve this function, the isChanged query will now be executed once after system startup if there are no changes instead of being executed every time the Aggregates DataSet BBK is executed. If the same Aggregates query is made multiple times as part of a Strategy in a REST request (i.e. likely multiple ADM models in a MakeDecision call), only one Aggregates BBK call will be made.
INC-185045 · Issue 672418
Performance improvements for action check-in
Resolved in Pega Version 8.6.2
The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.
INC-186889 · Issue 674015
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.6.2
After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.
INC-188389 · Issue 672761
ComponentName fallback added for toggling page context
Resolved in Pega Version 8.6.2
Whenever the External Strategy configuration was changed from "Another Page" to "Current Page", pyComponentName property was not being created. This was a missed use case for toggling page context for external substrategies in the user interface of the strategy designer, and has been resolved by setting pyComponentName to its default if reset when switching context.
INC-188419 · Issue 671500
DSS added to configure usage of Topup
Resolved in Pega Version 8.6.2
During NBAD-generated strategy execution, each interaction history summary is queried twice to check data relevancy. This update adds configuration options to disable topup in aggregate datasets. Topup can be disabled with the following configuration items:- Set prconfig "ih/aggregates/last_customer_update_method" to NONE - Set DSS "cep/aggregates_dataset/partition_proc_cache_time" to -1
INC-159836 · Issue 638267
Upgraded Apache UIMA Ruta libraries to resolve memory leak
Resolved in Pega Version 8.7
A memory leak issue that resulted in a reboot being needed every few days was traced to the class org.apache.uima.ruta.rule.RuleMatch. This has been resolved by upgrading the Apache UIMA Ruta libraries to v2.8.1.
INC-164243 · Issue 658270
DateTime validation works correctly after importing invalid data
Resolved in Pega Version 8.7
After creating DecisionData (Dev studio) and adding a DateTime property to the form, importing records with invalid DateTime values failed with a validation error on the screen and the message "Error while converting format for data type DateTime property name Test_date_format with value scvf" was logged. Attempting to proceed by correcting the DateTime property and uploading worked, but any subsequent imports in the same session silently allowed invalid inputs to be passed without any validation errors and then showed blank date fields. This has been corrected.
INC-165704 · Issue 639506
VBD data flow timeout increased and made configurable
Resolved in Pega Version 8.7
Intermittent VBD timeouts were seen when writing records to MSK even though no errors were reported on the MSK side. Analysis showed that while batch data flows retry when a timeout occurs, real time data flows do not retry and the configuration to wait up to 10 seconds for an acknowledgement may not be sufficient depending on the system conditions. This has been resolved by increasing the default timeout to 20 seconds and adding a configurable timeout "vbd/streamPublishTimeoutMillis" to allow a customized setting.
INC-166561 · Issue 645648
ADM Models correctly updated
Resolved in Pega Version 8.7
The ADM models were not being updated when responses were processed either via the CaptureResponse API or when the time elapsed that should result in an update reflecting a non-response. This was traced to incomplete handling for a response coming for some other model which was converted to EMPTY, and has been resolved by modifying the logic so that the default responses and other responses are processed properly.