INC-188124 · Issue 673106
Strategy updates
Resolved in Pega Version 8.7
Three issues with Strategies were addressed: * 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 * 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. * Summaries created with a list of filters for aggregation were intermittently truncating the generated Summary Dataset. This has been resolved by updating the Digest calculation strategy to not take into account Filter IDs which may change if a Dataset is generated from CPD.
INC-188309 · Issue 684702
Proposition filter populated for test business Issue
Resolved in Pega Version 8.7
When running the proposition filter rule, no drop down list appeared for a business issue. This was caused by the Issue list not being populated for the Action-Run test page, and has ben resolved.
INC-188389 · Issue 674671
ComponentName fallback added for toggling page context
Resolved in Pega Version 8.7
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 671501
DSS added to configure usage of Topup
Resolved in Pega Version 8.7
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-188882 · Issue 679144
DSS added for configurable asynchronous writes into DDS
Resolved in Pega Version 8.7
An enhancement has been added which will allow DDS writes happening within pxDelayedLearningFlow to happen asynchronously and be configurable per node in order to improve performance. name: dnode/save_dds_async_processing_enabled description: Enable asynchronous processing of records in DDS Dataset save operation. Failures to store individual records will not interrupt operation execution.
INC-191356 · Issue 679163
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.7
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
INC-191554 · Issue 681351
Mapping updated for Primary filter rule with globally optimized strategies
Resolved in Pega Version 8.7
A discrepancy was seen in the results when compared between running globally optimized strategies (GOS) and a normal strategy in the Customer Decision Hub. Investigation showed this was caused by a proposition filter rule containing When rules configured with the keyword "Primary", which caused page mappings to fail in GOS. This has been resolved by explicitly populating the primary context for callWhen.
INC-191789 · Issue 679606
Updated SimpleDateFormat to remove lenient parsing mode
Resolved in Pega Version 8.7
When using File Dataset to ingest CSV files with the required Date format set as yyyyMMdd, an error was thrown if the date value provided in a file was in the format '14/04/1971', but a date format such as 14-04-1971 did not produce an error but instead was mapped to a Date value of 00131204. . This has been resolved by disabling the lenient mode of parsing in SimpleDateFormat.
INC-192025 · Issue 680706
Scenario Planner performance improvements
Resolved in Pega Version 8.7
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.
INC-192102 · Issue 678532
Performance improvements for stale thread warnings
Resolved in Pega Version 8.7
Stale thread warnings were causing performance issues during dataflow run execution. Stale thread/slow component warnings are added as part of the dataflow execution when a processing thread takes more than 5 minutes to process a single dataflow record. The stacktrace of the dataflow thread is added as part of the warning for debugging purposes, but in some scenarios the stacktrace can become very large. This has been resolved by removing the stacktraces from the warning, improving the query logic, and adding the run ID to the exception method to assist if there is an error.