Switching Pulse to display its message in a rich texteditor can break the whole portal
Config: pega 7.3 default start case listener configured to prefer HTML content and to ("Embed data for inline images into HTML") on the auto generated email listener for start case (see more about the config in this post: https://collaborate.pega.com/question/pulse-not-rendering-html). The incoming messages are posted by default to the Pega pulse.
Problem: Pega pulse does not display html, it displays the string which is not good user experience.
Tried to solve this by switching the control used to display .pyMessgae from DisplayPostText to RichTextEditor.
The problem is that pega truncates the messages when sending them to the client. If the messages contains an inline base64 image (the listener creates it). the image src tag will not be complete and causes the whole portal to break.
***Edited by Moderator Marissa to update SR Details***
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-53431 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,
Pegasystems Inc.
IN
Hi Grego,
On discussing this post internally, we believe that the SR you have currently open with the support team would be the best path for investigation. We will continue to track the progress through this post.
Thank you,
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-53431 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,