INC-184311 · Issue 667270
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-184443 · Issue 668437
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-162426 · Issue 638771
Regex handling updated for Rich Text Editor spellcheck
Resolved in Pega Version 8.7
When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.
INC-182724 · Issue 677844
Added empty space handling for tab labels
Resolved in Pega Version 8.7
After upgrade from Pega 6 to Pega 8, tab names were not displaying when rules were opened in Designer Studio. This was traced to empty space in the label which caused the Tab name to show as empty, and has been resolved by updating pzpega_ui_dynamiccontainer to use the trim method to check whether the label is empty or not .
INC-183163 · Issue 676252
Optimized table search updated
Resolved in Pega Version 8.7
Search functionality that can be enabled from tables after selecting the "Optimize" checkbox was not working correctly. This was traced to a potential issue getting the search parameter passed into the activity the section uses, and has been resolved by updating the system to get the element from pega.ctx.dom when pyFlowActionHTML div does not exist.
INC-170258 · Issue 645043
Removed unneeded query parameter in UI
Resolved in Pega Version 8.7
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-180275 · Issue 666456
Collaboration control hidden if data type is delegated
Resolved in Pega Version 8.7
When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.
INC-186466 · Issue 670292
Style selector workaround added for Internet Explorer 11
Resolved in Pega Version 8.7
When using UI-Kit 15.0.1 with Microsoft Internet Explorer 11, the responsive behavior of the left navigator was not working as expected, it was not possible to Customize/Style the File Path control completely, and the AutoComplete control and Date Time Controls had a blue border on hover/focus. This was traced to the styles not being correctly selected because they contained the selector "focus-within" which is not supported in this browser. This has been resolved by adding focus-within separately so Internet Explorer will ignore the selector.
INC-183995 · Issue 673789
Corrected accessibility for action menu button
Resolved in Pega Version 8.7
When using JAWS with Google Chrome or NVDA with Microsoft Edge, the action menu button label was announced twice, as 'Case Action Menu button' and 'Action Menu button', and it required two tab key presses to set focus on the Action menu button from the Follow button. This has been resolved by removing the role type as component/widget and keeping the label as "case wide actions" so that after the focus from the icons, the focus is correctly set on the action buttons.
INC-169203 · Issue 646097
Robotics Desktop Automation correctly runs on subsequent tabs
Resolved in Pega Version 8.7
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.