INC-175394 · Issue 661457
Date Time format corrected for Chinese locale
Resolved in Pega Version 8.5.5
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-175814 · Issue 657821
Runtime edit saves section to correct class
Resolved in Pega Version 8.5.5
When the active thread had an Ajax container embedded in it and a runtime edit was made of a section in the Ajax container thread, the section was saved into the parent thread's work object class. This was an unsupported use case, and has been resolved by adding support for runtime editing of sections from an embedded Ajax container.
INC-175990 · Issue 652086
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.5.5
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-176342 · Issue 654507
Summary Tabs correctly sync after case refresh or submit
Resolved in Pega Version 8.5.5
The right side display showed the corresponding section as expected after selecting any last tab, but after a case refresh the right side of the summary tab highlighted the first summary tab's section while the focus remained on the previous selected tab. This was traced to the setActiveTab API triggering pega.ui.templatenav.toggleLayoutGroupTab with incorrect parameters, and has been resolved.
INC-176403 · Issue 653574
Security updated for buttons
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for Button controls.
INC-176429 · Issue 654752
Values updated in Local action correctly reflected in the UI
Resolved in Pega Version 8.5.5
After update, values were not updated in the UI after being modified in a local action which targeted a modal dialog and had some text fields on overlay with validation messages placed using Property-Set-Messages. Analysis revealed that the ReloadSection was not getting called correctly in this scenario, and has been resolved by changing the nullify method to pega.u.d.cleanUpHarnessElements(null, [containerBody]); .
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.