INC-139624 · Issue 595987
Validation error messages persist appropriately
Resolved in Pega Version 8.6
Whenever there was a Validation check on a flow action Validation Tab and Post Processing Activity, the error message appeared on the screen momentarily and disappeared. Intermittently, the validation error would stay on the screen after appearing a second time. This was traced to the refresh action happening in the wrong context due to the refresh action of the Ajax container being called twice, once in postacrenderac and another time in the harness unload function.The case error DOM was present in the markup, but because of the refresh in the harness unload, the error message was removed from the DOM. This has been resolved by changing the refresh call from onHarnessUnload callback to postAcRender callback. Logic has also been added to prevent refresh when error messages are present.
INC-139645 · Issue 597499
Flowaction button responds for grid modal window
Resolved in Pega Version 8.6
The submit and cancel buttons were not working on first click for a modal window opened from a grid. Investigation found that this happened when the grid was shown on launching a harness but not if the grid was set to show otherwise in tabs, and was not seen when launching modal windows normally either from tabs or from harness (the pzModalTemplate or pyModalTemplate). This was traced to the system passing the target as a window to getTrackerChanges from triggerEvaluateClientConditions, which caused getTrackerChanges to be called on every window action. To resolve this, the event has been changed to 'focus' so that the method gets called only on focus.
INC-139739 · Issue 598901
Cross site scripting protection update
Resolved in Pega Version 8.6
Cross site scripting protections have been updated for labels.
INC-139849 · Issue 598126
Sorting icon visible for table in Cosmos on Chrome
Resolved in Pega Version 8.6
Tables were not showing any sort icon / indicator in the column header when using the Cosmos Theme in Chrome. This was only occurring in apps created with the Cosmos theme, and was caused by the sort icon for a non-optimized table using display flex, resulting in the position of the icon being displaced. This was a missed use case of having a non-optimized table in Cosmos, and has been resolved by removing the non-optimized-related CSS code.
INC-139966 · Issue 606842
JAWS announces popup error message
Resolved in Pega Version 8.6
When a form is submitted without giving value to required field, a browser pop up appears. The expected behavior is that the screen reader (JAWS) should move the focus to the field that has error and read the error message However, JAWS was not announcing the error "Value cannot be blank". This was traced to a scenario where if pega.u.d.fieldErrorType === "ERRORTEXT" is true, the class on the span within the error div will be set to "inputSpans", and this resulted in the return of an empty array for document.querySelectorAll("span.iconError.dynamic-icon-error"). To resolve this, support has been added for the "inputSpans" class.
INC-140140 · Issue 595669
Multi Select populates values for Page group
Resolved in Pega Version 8.6
Multi Select populates values for Page groupThe Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.
INC-140205 · Issue 595661
Safe check added for first element focus on inline table edit
Resolved in Pega Version 8.6
When moving the scrollbar when performing an inline edit of a hierarchical table, releasing the scrollbar caused it to move to the top of the table. This would continue until a refresh was performed. To resolve this, a safe check for focus first element method has been added.
INC-140289 · Issue 589004
Check added to preserve clipboard pages for pop-up
Resolved in Pega Version 8.6
Many properties were missing in the clipboard after launching an ImageViewer. This was traced to the clipboard pages being deleted in the pop-up mode, and has been resolved by adding a check to not delete pages in case of pop-up opened from top navigation case.
INC-140848 · Issue 596460
Button row correctly added for click on exception list
Resolved in Pega Version 8.6
After upgrade, clicking on an exception list button in the mobile app was not adding a row to an existing Page List as expected. Investigation showed that pega.u.d.refreshSection was not executing correctly from RunScript, which was traced to a missed use case for handling an empty repeating dynamic layer in this scenario. This has been corrected.
INC-141099 · Issue 598130
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.6
After routing an assignment to different operator, the current operator was still seeing the Go button in Cosmos for processing the assignment. Clicking on the button resulted in an error. To resolve this, the confirm notification section reload has been moved to a different context, and the visibility conditions have been updated to handle more use cases.