INC-142589 · Issue 595490
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.6
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 596555
Recent Cases from different applications available to open
Resolved in Pega Version 8.6
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 596955
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.6
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-143260 · Issue 599302
Overlapping columns fixed in ReportViewer
Resolved in Pega Version 8.6
When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.
INC-143363 · Issue 604364
Added handling for maintaining on-change event descriptor
Resolved in Pega Version 8.6
The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.
INC-143599 · Issue 598770
Non-template RDL time value handling updated
Resolved in Pega Version 8.6
The Time value displayed on clipboard and data designer differed from the value shown on user work form when using a categorized repeating dynamic layer rendered in non-template mode with the Datetime control configured inside the RDL. This was traced to the Time string being considered as a date when using this configuration and calling the engine API, and has been resolved by ensuring this configuration will call the correct Time API instead so that the timeofday property value will be formatted correctly.
INC-144301 · Issue 604407
Revised character escaping for Tooltip
Resolved in Pega Version 8.6
Hover text/Tooltip on the Collapsible layout was showing the content in ASCII format if the input string contained special characters like "&" (which was getting printed as "&"). This has been resolved by unescaping the title string and letting handlebars do the work of escaping it.
INC-144320 · Issue 600536
Dirty Flag reset updated
Resolved in Pega Version 8.6
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
INC-144500 · Issue 600031
Cosmos layout switch works with language packs
Resolved in Pega Version 8.6
When using localization, operators were unable to switch between Details & Pulse layouts: no action was performed on click of the tabs. This was traced to the generated java code in the pzTemplateNav control which fills out the navigation data page with values for "section name" and "label" used for targeting corresponding section in DOM. Because both values were not working in all possible cases, this has been resolved by swapping section targeting from label-based to index-based.
INC-144515 · Issue 608599
Corrected multiple harness error messages being displayed
Resolved in Pega Version 8.6
Same validation error messages are being displayed multiple times for the harness. This was traced to the way the system checks for an existing error table based on the data-harness-id attribute in the current harness context; sometimes existing errors tables are missed and new ones were created which stacked up on screen. This has been corrected by adding a condition to check for existing errors.