INC-174020 · Issue 650888
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.6.1
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
INC-174921 · Issue 652321
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.6.1
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field.This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-175322 · Issue 658651
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.6.1
In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-175990 · Issue 652088
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.6.1
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-176403 · Issue 653576
Security updated for buttons
Resolved in Pega Version 8.6.1
Cross-site scripting protections have been updated for Button controls.
INC-176734 · Issue 655178
Invalid manual time value stops progress and displays error
Resolved in Pega Version 8.6.1
When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.
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.