INC-193775 · Issue 686646
Action Sets in Sections working as expected
Resolved in Pega Version 8.6.3
When adding actions to a table, the action sets were not always saved correctly. Sometimes actions from one actions set were moved to a new action set without any event, which seemed to occur when there were multiple actions defined for each action set. This was traced to the open of the table property panel in the activity Embed-Harness-SectionBody-Grid.pzGridActionSets activity. This activity sets data for the action set display, including setting a “pyKeyCode” property. The “pyKeyCode” property is not set correctly in certain scenarios, causing the selected action/behavior to not be saved correctly. This has been resolved by changing the local param-pzGridActionSets: TempKeyCode to string.
INC-193947 · Issue 684138
Focus corrected for dynamic layout in mobile
Resolved in Pega Version 8.6.3
When any new item was added to a repeating dynamic layout in mobile or if the grid one of the items was expanded, the entire UI refreshed and the focus moved to the top. This has been resolved by adding a check for isMobileFullScreen.
INC-194239 · Issue 685736
JAWS reads characters limits in grid text area
Resolved in Pega Version 8.6.3
A text area in a grid with a character limit was not reading the maximum characters and remaining characters when using JAWS. This has been resolved by adding the necessary aria attributes to the non-template text area control.
INC-194446 · Issue 691354
Mobile app validates collapsed layouts
Resolved in Pega Version 8.6.3
Validation did not fire in the offline app when the fields were in collapsed layouts. This has been resolved by removing the validateHiddenFieldsInOffline flag for Offline.
INC-195321 · Issue 684972
Check added for readonly header control
Resolved in Pega Version 8.6.3
After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.
INC-195363 · Issue 690044
Accessibility improvements for Cosmos
Resolved in Pega Version 8.6.3
After update, some UI changes were seen in Cosmos that could impact accessibility. These included the left panel for the portal can be folded, but the arrow/Icon to fold this pane shows only when you hover over with it with the mouse; on the same portal, Submit and Cancel buttons are displayed at the bottom of the screen as a sticky menu over the long form instead of the previous behavior of being at the bottom of the form; and that the sticky menu partially covered the bottom of the form's functionality. These have been resolved by updating the selectors to make the collapsible icon accessible using keyboard and by removing the sticky behavior for the case action area buttons in the perform harness.
INC-195581 · Issue 691843
Control menu code minified
Resolved in Pega Version 8.6.3
Minification has been turned on for control menus.
INC-195583 · Issue 684841
Flow action modal pop-up closes after submit
Resolved in Pega Version 8.6.3
On clicking Submit button on the modal window, the post action was successfully completed but the buttons froze and the modal window did not close. This was traced to a missing condition in the if loop to handle the needed flow action logic, and has been corrected.
INC-196002 · Issue 684940
Handling added for undefined GadgetOffsetState in Mashup modal windows
Resolved in Pega Version 8.6.3
Following an update, the system was hanging after launching Mashup and submitting from modal window. Investigation showed that in this mashup scenario, when the modal dialog was rendered on click of a button the globally-defined pega.Mashup.GadgetOffsetState object was passed as undefined to the pega.u.d.registerModalListener API due to pega.Mashup getting reset elsewhere in the process. To resolve this, handling has been added for a modal dialog in mashup scenarios when pega.Mashup.GadgetOffsetState is undefined.
INC-197243 · Issue 687413
Locking updated for EmailLink
Resolved in Pega Version 8.6.3
After clicking a work link from email and opening the work object in a new window, opening the work object in the perform harness and performing a browser refresh by way of Actions -> Refresh resulted in a locking error when trying to submit the case. This was traced to the handling in the Ajax container: when an assignment is opened from the todo list, it will open it in primary Ajax container. If the complete web page was refreshed, the contents in the Ajax container were cleared and loaded back to previous state. While doing this process the lock of the Work Object was released and not added back. In order to achieve the lock after the refresh, the doUIAction activity has been updated to lock the case when the case is opened and reloaded.