INC-170304 · Issue 645810
PDF generation corrected
Resolved in Pega Version 8.5.4
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-171121 · Issue 648131
Filter popup persists correctly
Resolved in Pega Version 8.5.4
When the Apply filter option was selected for a table configured with page list property as source, the filter popup appeared on the screen but disappeared after 3 to 4 seconds. This has been resolved by enabling the stretch for tabs option in the layout group.
INC-172521 · Issue 651551
Email template content visible in user application
Resolved in Pega Version 8.5.4
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
INC-174699 · Issue 652070
Work objects can open in multiple tabs with Layout group
Resolved in Pega Version 8.5.4
After implementing the Worker portal with Layout Group(Tab) to open work objects and other options (Pulse, Spaces, My Cases etc.) in multiple tabs, the tabs opened as expected the first time but after all of the tabs were closed any newly opened cases appeared in popup windows instead of tabs. Investigation showed that when the last tab was closed, the display was set to the main div container of the ajaxcontainer so opening the work object again used a new window. Tab Group has been deprecated in the current Pega version, but the site has a requirement to open the cases in same way as they appeared with Tab Group; to resolve this, support has been added by making the width 0 for the active header highlighter instead of using display none for the main container for this configuration.
INC-174921 · Issue 652320
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.5.4
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field.This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-155878 · Issue 645364
Class list updated when using ActivateDocument in portal navigation
Resolved in Pega Version 8.5.4
Global search worked the first time it was used, but failed after another case was opened from the dashboard or there was a click on any landing page home, dashboard, or space. Investigation showed this was caused by the pySearchText being blank in the clipboard, which was traced to a harness context issue related to pega.desktop.activateDocument being used in pzPortalNavigation on DynamicLayout with Application Logo and Application label. To resolve this, an update has been made that will update the class list with the proper one when the data-harness-id is set.
INC-159836 · Issue 631206
Upgraded Apache UIMA Ruta libraries to resolve memory leak
Resolved in Pega Version 8.6.2
A memory leak issue that resulted in a reboot being needed every few days was traced to the class org.apache.uima.ruta.rule.RuleMatch. This has been resolved by upgrading the Apache UIMA Ruta libraries to v2.8.1.
INC-167606 · Issue 665869
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.6.2
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651079
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.6.2
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-171842 · Issue 664387
Visible element populated for field value controls
Resolved in Pega Version 8.6.2
When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element.