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-147873 · Issue 610865
Custom header character encoding for Subject added
Resolved in Pega Version 8.5.5
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-161645 · Issue 634639
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.5.5
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
INC-163292 · Issue 635839
Portlet service deprecated
Resolved in Pega Version 8.5.5
Portlet authentication services have been removed from the standard installation package. The IAC service has been restored.
INC-158018 · Issue 633374
Archiving updated to include pxobjclass in CTE column list
Resolved in Pega Version 8.5.5
After enabling the case archival feature on a casetype, cases were getting stuck in the Archive-Ready state while being archived, and a 'column not found' error was seen. Investigation showed that the generated SQL statement used to retrieve the resolved case instances used a common table expression (CTE) whose columns were inskey, insclass, and parentinskey, and the query that referenced the CTE was attempting to compare the column pxobjclass when pxobjclass did not exist in the CTE's column list. To resolve this, the CTE column list has been updated to pzinskey, pxobjclass, and parentinskey to prevent the 'column not found error' from occurring, and the query that referenced the CTE was also updated to use the correct column names and aliases.