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:
Why it's suddenly stopped working with Appian version 26.3? Can you please look into it or let me know if any changes are required.
Hi Matthew Sutton we are experiencing the same issue , were you able to fix this or find the root cause of this issue
Is there a way we can add custom fonts to this plugin?
We recently migrated our environment from the legacy EC2-based infrastructure to Kubernetes. Following the migration this plugin has stooped working, component is not loading it is just showing blank UI. Has anyone faced the same issue?
Hi,
We are experiencing a issue while uploading images from mobile using this plugin. Some time it loading on upload or not rendering image entirely. For web, it is working fine. Any help or suggestions please?
We have implemented this component for a client.
They are experiencing an issue where the cursor keeps jumping back / repositioning itself while typing in the rich text field.
Could this be due to refreshing variables? I tried using locals to save the text instead and its still jumping around
Would you be able to provide some insight into the cause please?
Thanks!
-Matt
Emoticons and Date/Time options are disappearing when we change the Height from "Auto" to any other (Short,Medium,Tall). Could you please assist us with this?
We've detected the plugin is trying to use a file in /richTextEditorField/v1/skins/content/default/content.css which doesn't exist. It's not impacting usability at the moment but it is quite noisy in terms of gateway and console errors. Anything you can do to resolve this would be great.