INC-186437 · Issue 685014
Updated entity attachment extraction tokenizers
Resolved in Pega Version 8.5.6
After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.
INC-186889 · Issue 674013
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.5.6
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-187520 · Issue 677872
Actuals sync clears data from cache and persistence
Resolved in Pega Version 8.5.6
When sync attempted to clear the existing data from Actuals before copying data from the interaction history, the partition was cleared from the cache but not from persistence. IH data that was then copied to the same partition time ranges had new field descriptors created that did not match the format of the old data in persistence. As a result, when a query triggered the loading of such a partition, the mix of data with the old and new formats caused the load to fail. This has been resolved by updating the system to ensure the data is deleted properly from both the cache and persistence.
INC-188309 · Issue 684701
Proposition filter populated for test business Issue
Resolved in Pega Version 8.5.6
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 been resolved.
INC-188419 · Issue 671499
DSS added to configure usage of Topup
Resolved in Pega Version 8.5.6
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 NONESet DSS "cep/aggregates_dataset/partition_proc_cache_time" to -1
INC-188882 · Issue 679143
DSS added for configurable asynchronous writes into DDS
Resolved in Pega Version 8.5.6
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-191350 · Issue 679705
Corrected single case metrics being combined
Resolved in Pega Version 8.5.6
In Single Case dataflow runs, even though the data is processed on nodes, after some point of time the metrics were moving to 'Combined metrics of unavailable node'. This occurred when the corresponding service (realtime) was not available on the node when running the single case run, and has been resolved by updating the system to prevent single case metrics being combined while running on a node without realtime service enabled.
INC-191356 · Issue 679162
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.5.6
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-191789 · Issue 679605
Updated SimpleDateFormat to remove lenient parsing mode
Resolved in Pega Version 8.5.6
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-192102 · Issue 676359
Performance improvements for stale thread warnings
Resolved in Pega Version 8.5.6
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.