INC-187039 · Issue 678865
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.7
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-142066 · Issue 600045
Dirty confirmation alert added for standalone Ajax container
Resolved in Pega Version 8.5.2
In the Pega CS interaction portal, an interaction could be launched to create a service in the Ajax container. If the same service was opened from the search results or the worklist, however, it was not prompted with the dirty popup message to save or discard the changes. This was a missed use case for a standalone Ajax Container, and has been resolved by adding a check to evaluate whether the document has an Ajax Container so the proper dirty state handling will be called.
INC-174921 · Issue 652322
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.7
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field. This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-137966 · Issue 597740
Embed-ReportFilter supports pyDateproperties
Resolved in Pega Version 8.5.2
After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.
INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-139328 · Issue 588584
Corrected Excel table picture being included with the rich-text editor paste
Resolved in Pega Version 8.5.2
Corrected Excel table picture being included with the rich-text editor pasteAs an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using the rich-text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
INC-182803 · Issue 679724
SearchKeyword assed to HandleInput allow list
Resolved in Pega Version 8.7.1
After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.
INC-184419 · Issue 669619
Checks added to prevent EditingMode null value
Resolved in Pega Version 8.7
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-175394 · Issue 661455
Date Time format corrected for Chinese locale
Resolved in Pega Version 8.7
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-150407 · Issue 605840
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.5.2
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.