INC-169012 · Issue 651256
VMWare workspace One Mobile support added
Resolved in Pega Version 8.6.1
Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.
INC-169203 · Issue 645694
Robotics Desktop Automation correctly runs on subsequent tabs
Resolved in Pega Version 8.6.1
When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.
INC-169796 · Issue 649261
Null check added for pyModes setting
Resolved in Pega Version 8.6.1
The column filtering function was not working after update from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.
INC-169866 · Issue 653549
View content type updated to FIELD
Resolved in Pega Version 8.6.1
After update table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after update to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.
INC-170258 · Issue 645041
Removed unneeded query parameter in UI
Resolved in Pega Version 8.6.1
When using an Ajax container without a dynamic container, a refresh harness / section event call related to pyBlockUnregisteredRequests was not being properly registered, resulting in a 403 error and the message "Unregistered request encountered ..". This was traced to a "pyDataTransform=" query parameter that was present in the PZPEGA_UI_MICRODC file, and the parameter has been removed to resolve this issue.
INC-171121 · Issue 648132
Filter popup persists correctly
Resolved in Pega Version 8.6.1
When the Apply filter option was selected for a table configured with a page list property as source, the filter popup appeared on the screen but disappeared after 3 to 4 seconds. This has been resolved by enabling the stretch for tabs option in the layout group.
INC-171352 · Issue 653692
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-172178 · Issue 655022
TransID updated to trim spaces
Resolved in Pega Version 8.6.1
While preparing newTransID from a response, special characters slipped into "newTransID" param value and generated an error. This has been resolved by updating the system to trim spaces from newTransID.
INC-172483 · Issue 651709
Filtering updated for UI markup
Resolved in Pega Version 8.6.1
Filtering has been added to the UI code to preserve the browser display appearance but remove inappropriate or potentially insecure markup.
INC-172521 · Issue 651552
Email template content visible in user application
Resolved in Pega Version 8.6.1
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.