Question

2
Replies
104
Views
Gerg?T70 Member since 2016 22 posts
Saltech Consulting
Posted: February 23, 2018
Last activity: March 21, 2018
Closed
Solved

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://pdn.pega.com/community/product-support/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***

Low-Code App Development SR Parallel
Moderation Team has archived post
Share this page LinkedIn