SR-D76150 · Issue 539454
Logging updated for EmailListener and Data-Agent queue items
Resolved in Pega Version 8.5
In order to avoid the pr_sys_queue_ftsindexer table being overwhelmed with Data-Admin-Connect-EmailListener and Data-Agent-Queue instances for queued items, the Data-Admin-Connect-EmailListener and Data-Agent-Queue class definitions have been modified to filter queue items to incremental indexing if updates are from system and instance type is data- .
SR-D66986 · Issue 539414
BIX command line support improved
Resolved in Pega Version 8.5
Post-upgrade, it was seen that changes to the engine which validate that Data-Admin-DB-Name is not defined multiple times caused the BIX command line extracts to no longer work the same way. In order to improve backwards compatibility, updates have been made to loosen the validation in JdbcConfigurationFactory to always prefer prconfig settings if there are multiple definitions.
SR-D70890 · Issue 542871
Enhanced diagnostic logging for automatic search re-index
Resolved in Pega Version 8.5
To better analyze an out of memory error, enhanced diagnostic logging has been enabled for the below classes to get more information regarding re-index triggered automatically after search index is complete. PegaSearch.SearchManager.SearchInitlizationUtils PegaSearch.SearchManager.BuildIndicesTask Rule_Obj_Activity.pzLPFTSManagerRunBuildIndex.Pega_Search_Manager.Action PegaSearch.Indexer.AbstractIndexer
SR-D61971 · Issue 529608
Search Landing Page handling added for email addresses containing hyphens
Resolved in Pega Version 8.5
When an e-mail addresse containing a hyphen was entered for the Automated Search Alert functionality, the validation error "Please Enter Valid Email Address(s)" appeared. For example, [email protected] was not accepted. To resolve this, the regexp function used for the email validator has been updated.
SR-D61199 · Issue 533479
Support expanded for postgres versions and logging improved
Resolved in Pega Version 8.5
While trying to import data into the Data Type Tables using a CSV file and selecting the 'Add or Update' option, an error appeared and the import failed. Using 'Add or Delete' worked as expected. This was traced to the import of data failing for postgres version 10.x because UseMerge for postgres did not use merge if the version of Postgres was not 9. Support has now been added for versions of Postgres higher than 9 in SQLGeneratorPostgres.useMerge(), and logging has been enhanced to improve triaging issues such as this.
SR-D85839 · Issue 550938
Support added for custom Kafka connection properties
Resolved in Pega Version 8.5
An enhancement has been added to allow specifying custom Kafka connection properties in the Data-Admin-Kafka data instance to allow connections to external Kafka through the common client configs, ssl configs, and sasl configs.
SR-D90505 · Issue 550990
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.5
After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.
INC-126091 · Issue 561825
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.5
After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.
SR-D94258 · Issue 560795
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
INC-126662 · Issue 561314
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.