SR-B51449 · Issue 308503
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 308504
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313658
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313738
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B43400 · Issue 307258
Localization added for field value used in 'Enter a Short Description' validation message
Resolved in Pega Version 7.3.1
Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.
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.