IMPORTANT: Select component plug-ins are experiencing issues due to a recent browser update. If you encounter any problems with previously functional component plug-ins, please create a support case. If you notice other component plug-ins that are not functioning correctly, please create additional support cases for each instance.
Overview
The Rich Text Editor Component can be used on Appian interfaces where you want to show the rich text information in readable format to the end user. We can use the component to show it as an email subject typing interface.
With this component you can add images, customize tables etc. This also has a functionality called placeholders using which you can use the same information in multiple items in the editor without retyping.Additionally it allows uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plug-in).
Note:
Key Features & Functionality
Parameters:
We have a business requirement to copy complete email content, including text, images, and signatures. For this editor, we used the following plugins:
Despite this, when copying and pasting email content directly into the rich text editor, the text is successfully transferred, but the images are not.
As a workaround, I first copied the email content into a file, then copied the images from the word file and pasted them into the editor. This method successfully included the images.
Could you please help me understand why the images are not being copied directly and advise on how to resolve this issue?
Hi guys, big update: the reason for this behavior is something related to Google changing the way handling cookies (see here). Make sure to open a ticket and request to apply the change to support the Rich Text Editor plugin.
Dear Team,
We have identified that ARTE and potentially other component plug-ins are encountering issues due to a recent update affecting all major browsers. If you are experiencing problems with any of the plug-ins, please submit a support case with Appian and they will assist you in resolving the issue.
We have successfully addressed this bug through a site property adjustment and an application restart.
Thank you for your cooperation.
For me placeholder is not working now. Here is my sample code.
richTextEditorField( label: "Compose Message", required: true, height: "MEDIUM", richTextValue: local!emailTemplates.template, richTextSaveInto: local!emailTemplates.template, includeHTMLlength :true, enableSpellChecker: true, allowImageUpload: false, enableExportPdf: false, placeholder: {{"Case #: {Case ID}"}, {"PO #: {PO Number}"}, {"PO Date: {PO Date}"}} )
Hi,
I just updated to the latest version because I was experiencing issues with images. However, even after the update, the plugin still isn’t working; I’m still having trouble, and the images aren’t loading.
Is there a new version that you are currently working on?
or something else that I need to configure?
Hi guys,
I'm also having the same issue of broken pictures. Even the upload is not working correctly anymore after upgrading to Appian 24.2.
Images are created in the expected folder, everything looks fine, but then the image is not read correctly by the plugin.
If i click on "Open image in new tab" the image is shown correctly.
Of course both parameters are set correctly:
1- allowImageUpload
2- imageStorageConnectedSystem
I've also tried to re-create the connected system, with no luck.
We were running version 1.1.1 of the Advanced Rich Text Editor plugin and version 1.0.0.0 of the Connected System plugin.
Apparently after moving to 24.2 it stopped working and upgrading the plugin to 1.6.1 and 1.2.0 (Connected system) did not solve the issue.
Let me know if I can give you any additional information.
Best regards,
Fabio
Hi Team
We've been using this component for quite some time, and it has been functioning well in terms of handling images. However, recently we've encountered an issue where images are not being added or displayed to the end user, regardless of their size.
We attempted to update the plugin to the latest version (1.6.1) to stay in line with recent updates, but the problem persists.
Please provide a resolution as a priority.
Thanks
Shweta
Hi Thomas Pulliam ,
Thanks for reaching out!
We found the issue and fixed it, this solution will be available in the next release.