INC-128279 · Issue 591378
Layout Group tab alignment correctly shown in Microsoft Internet Explorer
Resolved in Pega Version 8.5.2
Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.
INC-139023 · Issue 591163
Tab will exit portal side menu
Resolved in Pega Version 8.5.2
It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.
SR-D96909 · Issue 558139
Removed extra scroll bar in Multiselect
Resolved in Pega Version 8.2.8
An extra scroll bar was appearing when opening the multi-select control case manager portal using the "Results displayed Maximum 500 results to display" setting. This was a result of recent updates to the popover scroll and height that caused on overflow condition. To resolve this, the logic for Multiselect has been updated.
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-137510 · Issue 591293
CKEditor Source edit with formatting resumes process automatically
Resolved in Pega Version 8.5.2
Buttons on the harness were freezing after applying format using CKEditor when source mode was turned on in rich-text editor. Investigation showed that on clicking the source button, after applying styles, the events were being paused and were not resumed automatically. This has been resolved by adding changes to resume the event queue.
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-148303 · Issue 606795
doRDLAction activity registered for BAC validity
Resolved in Pega Version 8.5.2
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-121444 · Issue 561810
Added handling to force text area maxlength in Microsoft Edge
Resolved in Pega Version 8.1.9
When using the Microsoft Edge browser, it was possible to continue entering characters in excess of the value set for the 'max characters' property. Investigation showed that the Microsoft Edge browser does not honor the maxlength attribute on text area; to resolve this, logic has been added to restrict the user from entering extra characters above the max limit.
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.