INC-142589 · Issue 595489
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.4.3
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596554
Recent Cases from different applications available to open
Resolved in Pega Version 8.4.3
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596954
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.4.3
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
INC-142831 · Issue 605475
Corrected Outlook web inline image handling
Resolved in Pega Version 8.3.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-143668 · Issue 617486
Performance improvements for Attachment Migration Utility
Resolved in Pega Version 8.3.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-143908 · Issue 606548
Data Page Save correct in batch mode
Resolved in Pega Version 8.3.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-144387 · Issue 605341
Support added for allow list for LaxRedirectStrategy
Resolved in Pega Version 8.3.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-144913 · Issue 607993
Handling added for unknown ProducerID exception
Resolved in Pega Version 8.3.6
An "UnknownProducerIdException" was seen in the PegaRULES and Kafka broker logs for Stream services. This exception is raised by the broker if it can not locate the producer metadata associated with the producerId in question. This could happen if, for example, the producer's records were deleted because their retention time had elapsed. Once the last records of the producerId are removed, the producer's metadata is removed from the broker and future attempts to append additional metadata will return this exception. To resolve this, a new producer will be used if the old one is unknown.
INC-145756 · Issue 619292
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.3.6
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-146610 · Issue 614421
MimeTypeHandler added for cloud downloads on mobile
Resolved in Pega Version 8.3.6
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the Google Chrome browser on an android device, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so Chrome on mobile was not able to identify the file type. This was a missed use-case for returnFileForDownload(), and has been resolved by setting the system to use MimeTypeHandler for getting the content type.