INC-176734 · Issue 655176
Invalid manual time value stops progress and displays error
Resolved in Pega Version 8.5.5
When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.
INC-177263 · Issue 659175
isFutureDate edit validation fires correctly
Resolved in Pega Version 8.5.5
The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.
INC-177852 · Issue 658652
Added UI handling for error message on Delegated data table
Resolved in Pega Version 8.5.5
It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll.
INC-178116 · Issue 660567
Article on configuring display options for a harness updated
Resolved in Pega Version 8.5.5
The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.
INC-178365 · Issue 659041
Corrected tab thread handling for modal close
Resolved in Pega Version 8.5.5
Clicking Grid item in My Opportunities tab did not open the section in that tab but rather opened another tab and showed the section of that tab. This was traced to pxReqURI not getting reset by the modal close, and has been resolved.
INC-178639 · Issue 658053
Improved accessibility for Autocomplete Role
Resolved in Pega Version 8.5.5
Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.
INC-179478 · Issue 662928
Handling updated for progressive load on scroll in repeating dynamic layers
Resolved in Pega Version 8.5.5
When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate.
INC-179664 · Issue 661111
Child Case comments pop-up opens as expected
Resolved in Pega Version 8.5.5
Comments on the header level were opening correctly, but the comments pop-up for the child case tab was not. This has been resolved by adding a safe check for the eventTarget.closest method.
INC-179683 · Issue 664450
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.5.5
Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.
INC-179883 · Issue 661617
Pega reference tags persist
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated to allow Pega reference tags.