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.
INC-180712 · Issue 664782
Improved accessibility for utility pane
Resolved in Pega Version 8.5.5
JAWS was not reading the items on the utility pane, and performing any action using the keyboard controls with JAWS running in the background did not open the actionable item. To resolve this, the Utilities panel has been configured with tablist role instead of combobox, and Header buttons titles have been changed to be more descriptive.
INC-181534 · Issue 663518
Information added for ckeditor plugin availability
Resolved in Pega Version 8.5.5
Documentation for adding external plugins to the rich text editor has been updated with additional information regarding available plugins for ckeditor.
INC-184311 · Issue 667268
Time value handling updated for IW locale
Resolved in Pega Version 8.5.5
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-184419 · Issue 668753
Checks added to prevent EditingMode null value
Resolved in Pega Version 8.5.5
When trying to open a section rule in developer portal in Pega Cloud, "Error" was displayed instead of the section details. Investigation showed the pyEditingMode property was present but did not have a value, and this has been resolved by adding checks to the UpgradeSequoiaGrid activity to ensure the pyEditingMode of "" does not invoke a data transform of that name.
INC-185847 · Issue 668984
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.5.5
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
INC-187057 · 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.