INC-147590 · Issue 608130
Handling added for new doc.write with Google Chrome 85
Resolved in Pega Version 8.6
Document.write was not working as expected on Google Chrome 85 due to the DOM elements not being updated. This has been resolved by updating the code to do doc.write by checking the if the document body has no child nodes in a time out.
INC-147665 · Issue 605058
Corrected Excel table picture being included with Rich Text Editor paste
Resolved in Pega Version 8.6
As an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using Rich Text Editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
INC-147683 · Issue 605292
Parameter added for skipping thread cleanup in RedirectAndRun
Resolved in Pega Version 8.6
Attempting to close an interaction after completing a phone call was resulting in a blue screen with the error "PRRuntimeError Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: 'RULE-OBJ-FLOWACTION' 'AGENTAVAILABILITYFLOW'." This was traced to the page context not being found for a rule from the Pega Call ruleset, and has been resolved by adding the boolean parameter bSkipCleanUpAllThreads to the RedirectAndRun Activity that can be set to true to prevent thread cleanup.
INC-147757 · Issue 620012
RecordFieldValuesList page cleared
Resolved in Pega Version 8.6
Investigation of web node crashes traced the issue to a condition where the RecordFieldValuesList page was not cleared. This has been resolved.
INC-148115 · Issue 605422
Autocomplete results list position scrolls inside a table
Resolved in Pega Version 8.6
Given a row editable table with a fixed height and freeze grid header, when autocomplete was included in a row of a table and the down-arrow was pressed to get the list of options in dropdown, this drop-down popup was not moving along with the row during scrolling. This was due to scroll handler not being triggered for popover when inside a hierarchical table, and has been resolved.
INC-148237 · Issue 605847
Autocomplete markup handles control format style names with spaces
Resolved in Pega Version 8.6
After creating the format 'Standard Gray Background' in the skin rule to change the back-ground color for an auto_complete field and using it in a presentation tab for Control-format input, the field was not updated with the background color as expected. This was due to the Autocomplete control only replacing the first space in the control format name with underscore ( _ ), causing the formatting to not be accepted. While there was a workaround of providing a name without spaces or using a name with only a single space, this has now been resolved by modifying the autocomplete markup generation so all the spaces in a control format style name are replaced instead of only the first space.
INC-148272 · Issue 608999
Increased specificity for collapsed DL
Resolved in Pega Version 8.6
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-148303 · Issue 606796
doRDLAction activity registered for BAC validity
Resolved in Pega Version 8.6
Users were unable to see more than the 10 most recent pulse posts because of a security alert (SECU0019) being thrown when the 'Show More' link was clicked. Investigation showed the error was coming from the PegaGadget-Feed.pyRDLPaginator section: "pzdoRDLAction" is part of non-template rendering, and pagination will use "pzdoRDLAction" activity whenever paginator is used in a non-template section. Because of this, it must be registered for BAC security to accept it and pass through, and this has now been done to resolve this issue.
INC-148375 · Issue 607797
"Today" will set date-time in the respective operator time zone
Resolved in Pega Version 8.6
When a Date was entered using the "Today" option in Datetime control, the Date set used the system date and Time was taken from time zone specified for the operator. This created issues for a scenario such as operator being set to America/New_York/ EST while the application was accessed in another country such as India or Japan. This was a missed use case and has been resolved by adding code to get the date-time in the respective operator time zone and setting it on click of date-time controls.
INC-148552 · Issue 607368
Added ability to disable dirty form browser alerts
Resolved in Pega Version 8.6
In order to add support for those who do not want to see a browser alert pop-up when cancelling a work item after making changes but do want the out-of-the-box Dirty popup to be displayed, an update has been made to add a configurable flag. If pega.u.d.bUseNativeDirtyConfirm is set to false, only Pega dirty dialogs will be shown. Setting it to true will show the Pega dirty dialog or else the browser dirty dialog for an event object.