INC-153249 · Issue 614899
Check box group links and buttons made clickable
Resolved in Pega Version 8.6
After upgrading from v8.4 to v8.5, click actions did not have the same behavior when using the standard template pyCheckboxGroupTemplate section. In v8.4, clicking anywhere in the card body triggered the checkbox, but in v8.5 only clicking on the checkbox itself triggered it. This was due to the CSS for checkbox templates (in the py-design-template-styles CSS rule) being updated, and has been resolved by making the links and buttons clickable.
INC-153266 · Issue 630851
Error message after submit persists appropriately
Resolved in Pega Version 8.6
When a template grid was in a section of flow action that performed validation and then populated an error message on a primary page post-processing, the messages were unexpectedly cleared after a very brief period. Investigation showed the network request made by the template grid created a state page on server which was being cleared, and this has been resolved by adding an update that will pass pzKeepPageMessages as true in the network request so the error message will persist as expected.
INC-153281 · Issue 612784
Selectors updated for segmented radio buttons in Cosmos
Resolved in Pega Version 8.6
When using a Segmented format radio button in an application built on Cosmos, clicking the control caused the screen to flicker and the focus moved to the top of the screen. This behavior did not occur when performing the same action in a classic application built on UI Kit. This was due to a difference in positioning: in UI Kit, the input for the segmented radio button is positioned using an absolute position and the parent radioTable div uses a relative position, while in Cosmos the radioTable div is given a static position. This has been resolved.
INC-153318 · Issue 621365
Check added to match time zone for Time Picker
Resolved in Pega Version 8.6
Time picker popup was showing minus 5 hours from the actual value in the time input field, though the value was updated correctly in the clipboard. The console error "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist." was seen. This only happened when using the non-template mode of the Datetime control and configuring it with TimeOfDay property with the combination of Allow text entry as "No" and onchange event as Refresh-Section. The issue was not seen if Allow text entry was "Yes" from the presentation tab or if the event action "Refresh-section" was removed. This was caused by the markup process using the operator time zone to format the value but the default time zone (GMT) for the data-value. This has been resolved by adding a check in non-template mode so the value markup will be generated using defaultTimeZone.
INC-153415 · Issue 616710
On click outside grid record will be saved
Resolved in Pega Version 8.6
When a record was added by copying a previous record, the new record was not saved if there was a click outside the grid. This has been resolved.
INC-153472 · Issue 629559
JAWS correctly reads headers of optimized tables
Resolved in Pega Version 8.6
Table column headers were not being read correctly with JAWS2020 and Google Chrome when using the "Tab" key to traverse the headers of an accessibility enabled application (PegaWAI ruleset included) that had an optimized table. This has been resolved by adding enhancements to enable keyboard navigation as per the WCAG standards of grid navigation for optimized tables.
INC-153555 · Issue 612227
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.6
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153602 · Issue 613567
Corrected visible margin in segmented button format
Resolved in Pega Version 8.6
After a new Segmented Button Format was created from the skin, an unexpected margin was applied between the elements. This has been resolved by updating the selectors for segmented radio buttons.
INC-153643 · Issue 621715
Dynamic layout group text area correctly rendered as editable for page list type
Resolved in Pega Version 8.6
A text area configured in one section with Edit Options set to 'Auto' had the text area field appear as Read Only at runtime. The section included an embedded sub-section where a Dynamic Layout Group (Tab) was configured with Source set to "Property", and the text area correctly appeared as editable in the wrapper section if the Dynamic Layout Group (Tab) was removed from the sub-section. This was caused by the section content for the dynamic layout group not being handled for page list type, and has been resolved.
INC-153721 · Issue 613662
Visual natural labels exposed to JAWS in REST wizard
Resolved in Pega Version 8.6
Get/Post/Put/Patch/Delete checkboxes were not properly read by the REST Integration Wizard when when tabbing through the checkboxes with JAWS enabled. When tabbing to each, “Tab – Select this method if it is supported at the endpoint” was read for each checkbox, and no information was given regarding what method each checkbox was for. When any helper text is configured, an aria-label attribute with helpertext message is generated. This aria-label will override any other native labeling mechanism (label - id mechanism), which is this case caused the control label to not be announced. To resolve this, the system will remove the aria-label attribute when helper text is configured and will add the helpertext div ID in aria-describedby for accessibility.