INC-174321 · Issue 664240
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.4.6
After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.
INC-184756 · Issue 667323
Static assembler correctly creates temp directory
Resolved in Pega Version 8.4.6
Static Assembly CLI was failing while creating a temp directory. This was traced to an issue with staticAssembler.xml, and has been resolved. In addition, security improvements have been added to the XML transformer.
INC-190722 · Issue 676403
Ruleset Restoration Utility repaired
Resolved in Pega Version 8.4.6
Attempting to use the standard Ruleset Restoration utility after update was resulting in a "Status:fail Operator:Unauthenticated or not available Node:No ID available" error message. This was a missed use case for the refactoring done around importing rules, and was caused by the utility calling the deprecated Importable.isValidImport() method. This has been resolved by updating the import activity to restore its functionality.
INC-164775 · Issue 681241
Web page generation security updated
Resolved in Pega Version 8.4.6
Cross-site scripting protections have been enhanced around web page generation.
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.