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.
INC-153783 · Issue 612992
Cross site scripting protection update
Resolved in Pega Version 8.6
Cross site scripting protections have been updated for labels.
INC-154205 · Issue 618737
Corrected wrap text for Cosmos radio buttons
Resolved in Pega Version 8.6
When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.
INC-154564 · Issue 617347
JAWS reads the table header and filter options separately
Resolved in Pega Version 8.6
When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Google Chrome from the way it reads them in Microsoft Internet Explorer, and has been resolved.
INC-154680 · Issue 619029
Moment time zone library update
Resolved in Pega Version 8.6
In order to reflect updates such as Brazil discontinuing DST time, the moment time zone libraries have been updated to the latest available version.
INC-154754 · Issue 629907
Check added for portal when performing local actions
Resolved in Pega Version 8.6
When using an Interaction case with a service case, performing any local action on this service case and then creating a new service case resulted in the I-related properties like CAParentID and CurrentInteractionID taking the pyID of the previous Service case where the local action was performed. This was caused by the parentKey value not being updated correctly in redux state whenever a local action was opened in a service case in a particular portal, and has been resolved by modifying the pzpega_ui_redux_reducers file to update 'parentKey' only in case of a DC SPA portal.
INC-154824 · Issue 620923
Check added for hidden field during validation
Resolved in Pega Version 8.6
When using custom validation for a future date, after certain steps the message "value cannot be blank" was displayed even though there was a value in the date control. This was traced to the validation also being performed on a hidden field, and has been resolved by adding a condition in pega_validators to check for hidden fields when running the validation.