INC-169323 · Issue 646268
Deleting attachment with icon button works in Attachment section
Resolved in Pega Version 8.5.4
After upgrade, a delete icon in the attachment section was not working as expected. This was traced to BAC work done earlier, and has been resolved by updating the Delete Attachment function of the AttachmentListViewSelectorScript.
INC-170041 · Issue 649669
Check and error message added for filename containing "%00"
Resolved in Pega Version 8.5.4
At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.
INC-173953 · Issue 650851
Updated Pega DX API special character handling
Resolved in Pega Version 8.5.4
When the using Pega API v1 and invoking api/v1/cases/{ID}/actions/{actionID} for a few fields in section, special characters were being converted into HTML entities. For example,"You'll usually find this information in your terms and conditions." was being converted as "You& #39;ll usually find this information in your terms and conditions" in the API response. This has been resolved by updating the system to ensure the pyDXAPIEncodeValues application setting is honored.
INC-174355 · Issue 652051
Corrected file download in Cosmos
Resolved in Pega Version 8.5.4
An unauthorized request error was seen in tracer while downloading files in the Cosmos application. This was traced to the pyAttachmentFeedDescription control in the Theme Cosmos Rule Set not being correctly updated, and has been resolved.
INC-176091 · Issue 652121
Busy indicator correctly resolves with Microsoft Internet Explorer upload
Resolved in Pega Version 8.5.4
When using Microsoft Internet Explorer to upload documents, the busy indicator was not resolving after the file was attached. This was due to a missed use case in work done around the timing of the busy indicator when attaching multiple files, and has been resolved by modifying PzMultiFilePath to ensure the busy Indicator is removed when the file count is zero.
INC-147654 · Issue 642188
Updates to displaying embedded images in cases
Resolved in Pega Version 8.5.4
Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.
INC-157214 · Issue 631599
Mentioned user in Pulse appears correctly
Resolved in Pega Version 8.5.4
When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.
INC-160372 · Issue 629921
Resolved unneeded chat survey error logging
Resolved in Pega Version 8.5.4
After configuring a chat server to do a post chat survey, the post chat survey was correctly served but errors indicating "Cannot find PegaCA-Work-SurveyNPS.Thank you for your feedback. van type Rule-HTML-Paragraph" were logged. This was caused by the method used by the system to distinguish between text and paragraph questions in pyProcessNextStep, and has been resolved by adding additional checks for whether paragraph exists before opening it.
INC-160688 · Issue 632229
Skip topics from the attachments setting honored
Resolved in Pega Version 8.5.4
Topic detection was happening for attachments even when it was disabled in the UI. This issue was traced to pyTopics which were not properly configured by selecting checkboxes in iNLP configuration for Email Channel, and has been resolved.
INC-163368 · Issue 634469
Special character replacement added for Email Bot training data
Resolved in Pega Version 8.5.4
When training an Email bot in the email channel, the training data was incorrectly added to the model. Although the text was tagged as an entity in the channel and highlighted correctly, after building the model it was seen that the tagged text contained dislocated start and end tags. Investigation showed that this occurred If the training data text had \r's in it. To resolve this, updatetrainingrecord has been modified to replace \r 's with "". The text which is being replaced will not appear in the UI.