INC-198021 · Issue 686631
Corrected blank areas on maximized view
Resolved in Pega Version 8.5.6
A blank section was displayed when maximizing the reply screen. Investigation showed that when the editor was inside a positioned container with overflow hidden and the editor had a scrollbar with its body height greater than the document, the scrollIntoView would scroll to grey spaces which were originally hidden by overflow. This has been resolved by commenting out scrollintoview, since it is not necessary and scroll position/cursor will be retained without it.
INC-198033 · Issue 688688
Updated ctx.recordId as variable handling
Resolved in Pega Version 8.5.6
Attempting to create a case using the Microsoft Internet Explorer 11 browser failed and the browser console log recorded the error "Caught exception: TypeError: Unable to get property 'split' of undefined or null reference". This has been resolved by updating the handling for passing the ctx.recordId as variable.
INC-198316 · Issue 699313
Resolved error in PortalNavigation save
Resolved in Pega Version 8.5.6
An error indicating Rule-UI-Components were either missing or could not be found appeared while using revalidate and save for a PortalNavigation section, though the update completed and worked as expected. This has been resolved by adding validation handling for a section when given a property as the class for the icon source.
INC-198326 · Issue 690316
Tab key menu navigation updated
Resolved in Pega Version 8.5.6
Using the tab key to navigate links in the left menu would intermittently skip links or not appear to advance. This was an unintended side effect of work done to use the tab key to move out of the portal menu and to the next focusable element, and has been resolved by modifying the re-setting tabindex for left navigation so it will anchor on the first element in the menu list for tab traversal.
INC-198951 · Issue 688271
Desktop browser java render error corrected
Resolved in Pega Version 8.5.6
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-198958 · Issue 691540
Scroll Bar displayed for lengthy sub menu
Resolved in Pega Version 8.5.6
The scroll bar on the main CaseManager/Case Worker portals menu was not displayed on the second mouse hover. This was traced to an intermittent issue where max-height was not being calculated correctly if there was a lengthy sub-menu, and has been resolved by ensuring the correct positioning of the menu.
INC-199043 · Issue 697067
Preview link aligned under item
Resolved in Pega Version 8.5.6
The preview option was not showing below the link control configured to open the case, but instead was displayed elsewhere on the page. This was traced to changes made in Google Chrome v.93+, and has been corrected by changing the perspective to none instead of 0 so the link is displayed in the expected location.
INC-199558 · Issue 693301
Updated calling activities from refresh to use invokeActivity
Resolved in Pega Version 8.5.6
The Refresh DX API was inconsistently throwing an index out of bound exception when using a checkbox which invokeed an activity on check to save and commit the case. This has been addressed by updating calling activities from refresh to use invokeActivity, and a try/catch has been added to capture exceptions and add a page message if the activity is not found or has an error.
INC-199625 · Issue 690721
Handling added for dropdown with duplicate option values
Resolved in Pega Version 8.5.6
When load behavior used "After screen renders" and dropdown options had duplicate values, a console error was observed and the UI became frozen. This has been resolved by adding handling for scenarios where the dropdown has duplicate option values.
INC-201739 · Issue 694504
Switch from Pega base64 utility to java.util.Base64.getEncoder
Resolved in Pega Version 8.5.6
An on-premises Web Application Firewall (WAF) was interpreting the characters "%0a" in the Pega auto-generated URL as an "HTTP Response Splitting" attack. As a result communications were intercepted and a 403-error screen was shown. In addition, the characters %250A were interpreted as LF (line feed) or \n in the refreshFor hash generation. To resolve this, an update has been made to use java.util.Base64.getEncoder().encodeToString instead of the Pega base64 utility.