INC-136518 · Issue 582571
Elapsed time available for an AJAX event duration
Resolved in Pega Version 8.5.1
An enhancement has been added which will capture a start of queue event for an AJAX event. This can be added to the existing end of queue event information and be used to calculate the event duration via Pega Web Analytics.
INC-130790 · Issue 580590
Special character handling added to App Studio column headers
Resolved in Pega Version 8.5.1
Changing the order of columns in App Studio was destroying the section, causing it to not be able to render unless it was restored. Investigation showed this was caused by an exception in the getIfPresent function due to the presence of special characters after a period (.) that were not considered valid identifiers. To resolve this, the GenerateCellContent Rule-Utility-Function has been updated to better parse the property identifier of the column header value.
INC-127658 · Issue 568625
Corrected 1 day discrepancy for non-template DateTime
Resolved in Pega Version 8.5.1
Date values in DateTime controls in a custom filter section of a report definition were reduced by one day after drilling down into drilldown report and navigating back to the main report. Investigation showed that when the non-template version of datepicker was configured with a date property, it displayed the value using read-only formatting with allow text entry set to 'No'. This caused the operator time zone to be used to format the value while data-value used the default timezone(GMT). To resolve this, and update has been made so that while generating markup in non-template for the date property the default timezone will be used whereas the datetime property will use the server timezone.
INC-134920 · Issue 582562
Spanish localization fixed for available appointment date
Resolved in Pega Version 8.5.1
For the Spanish locale, one of the values was not formatted correctly for one particular date format in the new appointment screen. For example, "lunes 6 de julio de 2020" was displayed correctly in the control but at runtime appeared as "lunes 6 61 julio 61 2020". This has been corrected by creating a placeholder for the text 'de' for the Spanish locale, and once the date is formatted the system will replace the placeholder with the original text.
INC-134018 · Issue 583011
Cross-site scripting protections updated for Dynamic Tab group
Resolved in Pega Version 8.5.1
Handling has been added to the Dynamic Tab group to protect against Cross-site scripting.
INC-128890 · Issue 565240
Highlighting fixed for rich-text editor with spellcheck
Resolved in Pega Version 8.5.1
In a Rich Text Editor, after turning on spell check and performing some text highlight on certain words and then clicking save, the formatting of the styling format was being applied to the words after the highlighted word. This has been resolved by modifying the regex reSpellChk1 to remove the last span tag instead of the first.
INC-133924 · Issue 581345
Table captions added for accessibility per HTML5
Resolved in Pega Version 8.5.1
In order to add Table captions for accessibility per HTML5 specifications, a new grid caption field has been introduced to add the caption to the table. When caption is specified, the summary attribute won't be generated.
INC-136620 · Issue 583782
Log off timer localization corrected
Resolved in Pega Version 8.5.1
Localization was not working correctly for the log off timer text “Timeout will occur in”. This has been corrected.
INC-140289 · Issue 589003
Check added to preserve clipboard pages for pop-up
Resolved in Pega Version 8.5.1
Many properties were missing in the clipboard after launching an ImageViewer. This was traced to the clipboard pages being deleted in the pop-up mode, and has been resolved by adding a check to not delete pages in case of pop-up opened from top navigation case.
INC-134893 · Issue 587169
Added check for localeDb properties in dateTimeUtils
Resolved in Pega Version 8.5.1
On click of the Approval/Finish assignment submit button, a blank screen appeared and no further progress could be made. This was traced to an issue with the operator locale not being properly set by the html fragments that initialize the locale for use in dateTimeUtils. This has been resolved by adding a check for properties in the localeDb object.