INC-142792 · Issue 594501
Modified thread data page cleanup
Resolved in Pega Version 8.6
Some cases were becoming stuck at a particular stage and not proceeding further even though the task in the backend was complete. Investigation traced this to work done that removed declarative pages at the thread level to optimize performance while other clipboard pages were retained, and the issue has been resolved by deleting all thread data pages after every item processed by the agent.
INC-142831 · Issue 605474
Corrected Outlook web inline image handling
Resolved in Pega Version 8.6
Outlook web was not able to render inline images and instead added them as external attachments. Investigation showed inline images were not being rendered properly in Outlook web due to the disposition not being set. This has been corrected.
INC-143376 · Issue 604530
Adding handling for property without parent page
Resolved in Pega Version 8.6
Filtering was not working for a DateTime control in an optimized grid with embedded property which was a function alias defined in a report definition referenced by a Data Page. This was traced to the system assuming that every property has a parent page, which this use case did not. To resolve this, an update has been made that will return null for the parentGroupOrListProp if one does not exist.
INC-143461 · Issue 601840
Updated JSON DT nested page property handling
Resolved in Pega Version 8.6
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a page list property is given, the page list was populated with only one result but the single-page property was treated like a page list and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested Page Lists.
INC-143668 · Issue 617488
Performance improvements for Attachment Migration Utility
Resolved in Pega Version 8.6
The Attachment Migration Utility was showing a zero count for attachments in the Pega Database. This was traced to the underlying report definition that retrieves data for the Attachment Migration Utility timing out, and has been resolved by updating the activities to improve performance for applications having a large number of attachments without customization.
INC-143865 · Issue 602197
Handling added for empty back link in BLOB
Resolved in Pega Version 8.6
A DirectStreamContainerV7 Exception (BLOB Corruption) was seen when opening a work object that expanded a certain property. This was traced to an empty back link present in the BLOB: during deserialization, the exception was thrown while trying to parse that empty back link. To resolved this, an update has been made which will parse the empty back link information properly.
INC-143908 · Issue 606550
Data Page Save correct in batch mode
Resolved in Pega Version 8.6
After configuring a List type savable Data Page with save activity in Code-Pega-List, the save data page was triggered from utility of flow from the queue processor to handle queueing 10k data items and creating 10k work objects. When this was run, a field dpClassName was being changed by different threads in DataPageSaverImpl.java. This has been resolved by making the class DataPageSaverImpl.java stateless to ensure thread safety.
INC-143972 · Issue 600520
Added handling to avoid class cast exception
Resolved in Pega Version 8.6
The error "doMaintain errorjava.lang.ClassCastException: java.util.HashMap cannot be cast to com.pega.pegarules.priv.factory.SequencedEntry" appeared in production numerous times per day, leading to exceptions. Investigation showed this was being triggered from the activity Show-harness, and was traced to the ConcurrentMostRecentlyUsedMap eviction method casting entries to Sequenced entries. There is no such check while putting entries. To resolve this, a wrapper has been added over the ConcurrentMostRecentlyUsedMap object to avoid a class cast exception.
INC-144387 · Issue 605340
Support added for allow list for LaxRedirectStrategy
Resolved in Pega Version 8.6
When using Connect REST with POST to access a third-party service deployed on multiple nodes, the load balancer sometimes replied 302 with Location header. The ability to allow the REST connector to automatically follow these redirects even in the case of POST messages is supported by Apache http client via LaxRedirectStrategy, but REST Connectors need both rule and engine enhancements to allow for this. To support this use, an allow list has been implemted for hostnames. This will allow the connector to be configured to follow the LaxRedirectStrategy only when the hostname of the redirect location is in the allow list. The default will continue to block the redirect.
INC-144601 · Issue 602423
Empty addresses removed from email
Resolved in Pega Version 8.6
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.