INC-180184 · Issue 665092
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.4.6
After update, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
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-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-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-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-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-165722 · Issue 636327
Stack trace logging enhanced for engine startup issues
Resolved in Pega Version 8.4.6
Enhanced stack trace logging has been added to capture additional information when the application is unable to start and no PegaRULES logs are generated.
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-179166 · Issue 676526
Correspondence rule finds updated content
Resolved in Pega Version 8.4.6
Activity Method Property-Set-Stream retrieved the older content of Correspondence when triggered via Queue processor. Restarting the queue processor resolved the issue until the next correspondence update, and then the cycle repeated. This has been resolved by adding an explicit thread cleanup to remove cached rules.