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-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-165256 · Issue 657036
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.5.5
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.
INC-175797 · Issue 662049
Date/time filter works in source column
Resolved in Pega Version 8.5.5
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".
INC-173392 · Issue 650243
Metadata space out of memory Healthcheck failure propagates correctly
Resolved in Pega Version 8.5.5
When an "OutOfMemoryError:MetaSpace" was generated from PRClassLoaderDB.loadClass, the exception was not propagated from its caller method. This has been resolved by adding the hook to call HealthMonitorService().processCriticalError in PRClassLoaderDB.loadClass(). HealthCheck will be set to 'UNHEALTHY' based on errors configured in GenericErrorAnalyzer, which includes an out of memory condition.
INC-178923 · Issue 660887
Resolved startup error related to business calendar object
Resolved in Pega Version 8.5.5
An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.
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-178990 · Issue 663786
Added handling for reloading portal while ChatBot is active
Resolved in Pega Version 8.5.5
An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat.
INC-179722 · Issue 659283
Added handling for legacy HTML formatting in Email Manager Bot
Resolved in Pega Version 8.5.5
When implementing Email Manager Bot features, pyBody fields were removing the additional spaces and causing the NLP model to not extract the correct data. Investigation showed HTML formatting from older version of Microsoft Outlook created nbsp; instead of space. This has been resolved by ensuring nbsp is replaced with spaces before calling JSoup clean.
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.