INC-182959 · Issue 668738
SQL queries modified to use qualified table references
Resolved in Pega Version 8.4.6
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
INC-182984 · Issue 665940
Accessibility label added to delete column header of delegated data table
Resolved in Pega Version 8.4.6
After delegating a data table, the header row of the delete column added to the grid was empty and JAWS was reading "HEADER". This has been resolved by adding a label for the delete column which will also be displayed in the delegated rules in the case manager portal.
INC-184031 · Issue 667219
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.4.6
After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.
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.