INC-184099 · Issue 664855
Localization added to DelegateDescription
Resolved in Pega Version 8.4.6
Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription.
INC-185045 · Issue 672419
Performance improvements for action check-in
Resolved in Pega Version 8.4.6
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-186437 · Issue 669187
Updated entity attachment extraction tokenizers
Resolved in Pega Version 8.4.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 674016
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.4.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-187070 · Issue 672107
Strategy execution queries tuned
Resolved in Pega Version 8.4.6
During Next Best Action 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-189136 · Issue 679518
Dataflow with report definition source repaired
Resolved in Pega Version 8.4.6
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-192102 · Issue 676362
Performance improvements for stale thread warnings
Resolved in Pega Version 8.4.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.
INC-167254 · Issue 651529
Reports database configuration documentation updated
Resolved in Pega Version 8.4.6
Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database.
INC-177323 · Issue 672423
Search string wildcard use documentation updated
Resolved in Pega Version 8.4.6
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-190130 · Issue 678543
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.4.6
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity.https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index