INC-165992 · Issue 657692
Table Filter save uses correct harness
Resolved in Pega Version 8.4.6
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
INC-170918 · Issue 653218
DateTime property handling revised for future date with daylight savings time
Resolved in Pega Version 8.4.6
A DateTime property was changing each time the local action refreshed. Investigation showed this was a missed use case related to recent work to correct an issue with a 1 day discrepancy for non-template DateTime. The previous update to use the default time zone when generating markup in non-template for the date property while the datetime property uses the server time zone has been further refined to handle formatting the date time when the year is greater than 2037 and combined with daylight savings time. This will be resolved by setting the correct date before returning the moment object if the year is greater than 2037 for the date time control using display mode as date.
INC-173944 · Issue 660179
Cancel button on embedded GridRow cancels single action
Resolved in Pega Version 8.4.6
When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.
INC-175394 · Issue 661454
Date Time format corrected for Chinese locale
Resolved in Pega Version 8.4.6
The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone.
INC-177019 · Issue 662706
Corrected styling for layout group section navigation
Resolved in Pega Version 8.4.6
When a layout group was added to a section after updating, the group was shifted when the left arrow key was pressed. This was traced to the use of arrow keys for navigation calling the focus() method and causing the scrolling. Although it is recommended to use a Tab Group control in this configuration, the shift issue has been resolved by updating the styling in the layout group.
INC-178024 · Issue 666418
Timeline correctly shows events in local time zone
Resolved in Pega Version 8.4.6
The DateTime value shown in the DateTime control and Timeline control were different from each other when using a locale setting. For example, a DateTime value which was within British Summer Time (BST) displayed as BST in the DateTime control correctly but displayed as GMT (one hour earlier) in the Timeline control. A site configured with the fr_FR locale in Europe/Paris time zone showed an incoming call interaction at 09:30 AM local Paris time while it appeared as 07:30 (GMT time) on the screen. Investigation traced this to the Pega date time formatter not being used when calculating event times, causing events to display in GMT and not in the local time zone. This has been resolved by ensuring the Pega date time formatter is added to the timeline component to display events in the local time zone.
INC-179683 · Issue 664453
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.4.6
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-180712 · Issue 664785
Improved accessibility for utility pane
Resolved in Pega Version 8.4.6
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 663517
Information added for ckeditor plugin availability
Resolved in Pega Version 8.4.6
Documentation for adding external plugins to the rich text editor has been updated with additional information regarding available plugins for ckeditor.
INC-184109 · Issue 671194
Handling updated for customDateTime formatting
Resolved in Pega Version 8.4.6
When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.