INC-151418 · Issue 610235
Authentication updated for legacy activities
Resolved in Pega Version 8.4.4
Authentication updates have been made for several legacy activities invoked via URL by custom HTML.
INC-152435 · Issue 612996
Hardcoded cluster password deprecated
Resolved in Pega Version 8.4.4
An unneeded hardcoded cluster group password has been removed in 3.8 version of Hazelcast as this use has been deprecated.
INC-152647 · Issue 609604
Email Listener auto-reply evaluation updated
Resolved in Pega Version 8.4.4
After upgrade, messages were being read but not getting processed for a specific Email listener (RCEmailListerner). The error "Email flagged as an autoreply email and will not be processed" appeared in the logs. Previously, an email was not considered to be an auto-reply only when the 'auto-submitted' header didn't exist or existed with value 'no'. This caused issues with auto-forward or auto-redirect emails where 'auto-submitted:auto-generated' could be in the header. Due to this, email was marked as auto-reply and email listener stopped processing it. To resolve this, the system has been modified to mark the message as auto-reply if it finds 'auto-submitted: auto-replied' in the header, but not 'auto-submitted:auto-generated'.
INC-153173 · Issue 612903
Assembly error self-healing enhancement added
Resolved in Pega Version 8.4.4
A StartOperation error was seen due to a declare trigger getting fired before the engine was fully up, indicating "UnresolvedAssemblyError: Error occurred trying to parse the expression and augmenting the code: java.lang.NullPointerException". This has been resolved by adding an enhancement that handles "self healing" for assembly errors.
INC-153877 · Issue 612370
Enhanced socket timeout logging
Resolved in Pega Version 8.4.4
In order to assist with diagnosing issues with socket timeouts such as a Data Flow Daily Run failing, logging to print the SocketTimeout value has been added when case info is enabled.
INC-154605 · Issue 615661
Date field correctly extracted for IMAP inbound email
Resolved in Pega Version 8.4.4
After upgrade, email-sourced cases were not being created correctly. Tracer showed the date field was blank, causing an error which was traced to the getReceivedDate being returned as null for the JavaMail AP even though the IMAP protocol was being used. This was an unintended side effect of work done to handle a throttling exception in the IMAP inbound email flow, and has been resolved by updating the system so that if the getReceivedDate is null, the date will be extracted from the mail header while processing dates in EmailMessageInfo class.
INC-158159 · Issue 622628
JobScheduler initialization timing adjusted
Resolved in Pega Version 8.4.4
DDS nodes were ending up in a deadlock condition on restart, preventing them from joining the cluster. This has been resolved by ensuring the JobScheduler initialization task waits for Search to start up.
SR-D96430 · Issue 561525
Updated visibility condition expression handling for decimal values
Resolved in Pega Version 8.4.4
After upgrade, any visibility condition expression failed to evaluate decimal values that used precision. When 0 (zero) was entered as a value in the input field, a button that was configured to show was visible as expected. When the value was entered as 0.0, the input failed and the button did not show. The problem did not happen "Run visibility condition on client" was enabled. Investigation showed this was an issue with how the When expression was evaluated and calculated within JspWhenEvaluate, and has been resolved.
INC-150689 · Issue 607157
Format specifier error resolved
Resolved in Pega Version 8.4.4
Errors were registered in PDC and stack for an Email Listener "Format specifier '%s" Exception. This was traced to a formatting error, and has been resolved.
INC-138501 · Issue 592286
Added VBD support for CSRF token setting
Resolved in Pega Version 8.4.4
Attempting to open any VBD reports in the marketing portal for a simulation test caused the user to be logged out. Investigation showed that this happened when CSRF token check was enabled in System > Settings > Cross-Site Request Forgery, and was caused by the planner not passing the CSRF tokens in its Ajax calls. To resolve this, handling for the CSRF tokens has been added to the necessary Ajax calls.