INC-176960 · Issue 655522
PDF generation corrected
Resolved in Pega Version 8.6.1
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-176971 · Issue 655219
Web Mashup works from nested iframe
Resolved in Pega Version 8.6.1
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.
INC-177263 · Issue 655830
isFutureDate edit validation fires correctly
Resolved in Pega Version 8.6.1
The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.
INC-177852 · Issue 658654
Added UI handling for error message on Delegated data table
Resolved in Pega Version 8.6.1
It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll.
INC-178639 · Issue 658056
Improved accessibility for Autocomplete Role
Resolved in Pega Version 8.6.1
Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.
INC-179378 · Issue 661174
Repeating Layout renders correctly after update
Resolved in Pega Version 8.6.1
Repeating dynamic layout was not working properly after update. This was caused by a missing active class, and was traced to changes made in the pzpega_ui_layoutgroup function where reload happens on close of a modal dialog. To resolve this, a safe check has been added to setInActiveLayout in layoutgroup.js.
INC-179622 · Issue 659155
Flow action list available in navigation menu
Resolved in Pega Version 8.6.1
After update, only one flow action which had highest likelihood was visible when an assignment in a flow had multiple flow actions. Alternatives were not visible in the Action menu. This was an unintended side effect of work done to simplify the Actions menu which did not consider the usecase of an alternate flow action being configured, and has been resolved by restoring the flow action list to the navigation menu in pyWorkCommonActions.
INC-179883 · Issue 661615
Pega reference tags persist
Resolved in Pega Version 8.6.1
Cross-site scripting protections have been updated to allow Pega reference tags.