INC-184668 · Issue 665959
Check added for null mColumn values while estimating size
Resolved in Pega Version 8.4.6
A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.
INC-184669 · Issue 666183
Locking issue resolved for passivating requestor
Resolved in Pega Version 8.4.6
A null pointer error was seen when passivating a requestor related to AbstractPassivationStorage.deleteAssociatedRequestorContents. This was traced to the lock to being called on the app requestor and not properly released. This has been resolved by ensuring the lock will be cleared when the Requestor is destroyed/returned.
INC-187553 · Issue 675431
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.4.6
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-187628 · Issue 670753
Check added to ensure read locks are released
Resolved in Pega Version 8.4.6
Read locks were not being properly released if a thread was holding a read lock and the system encountered an issue such as an out of memory condition. To resolve this, an update has been made to DeclarativePageDefinitionCacheImpl which will check whether a thread holds any read lock before trying to acquire a write lock, and if so release all the read locks held by that thread.
INC-188143 · Issue 674974
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.4.6
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-189580 · Issue 672855
Cleanup added for disabled/deleted operator passivation data
Resolved in Pega Version 8.4.6
In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.
INC-193442 · Issue 679180
ServicePackage thread handling improvements
Resolved in Pega Version 8.4.6
Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler. This also resolves a 504 Gateway Time-out error intermittently seen while trying to open the URL of the Pega application.
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