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:
The Required parameter only shows or hides the asterisk indicating but does not enforce requiredness. To enforce this behavior, use the parameter “validations”. To enforce requiredness only upon submission, use section, or form-level validations.
Does the required parameter work in the component ? If I set it to required I am still able to submit the form even with the component left empty. Can you please advise on the same ?
Hi,
We have deployed latest version of this plugin (1.1.0) in Appian cloud and we came across below issue.It did not replace the existing(1.0.3) plugin version with the new version(1.1.0), however it got added as a new plugin.
Is it happening because of name difference ? (see below screen shot)
Thanks
Gregor Gisler-Merzchitras0003 The updated version will be available approximately by end of next week.
Hi chitras0003
Is there any timeline till when the update will be available? Other than that the plugin is great. Handles all sorts of html email gracefully.
Hi chitras0003,
Thanks for your feedback. We assume it is because of the new update in Appian. We will soon update the component.
Hi jeanalainb0001,
Thanks for your feedback. We will update it soon.
Hi Simon Spencer,
Thanks for your feedback. We will analyze the issue that exists and fix it.
In recent version of Appian, the uploaded images does not render correctly.
The image source in HTML uses the doc id in rich text field. But as doc id is no more supported and document has to be accessed by opaque URL.
Would this be implemented in new version of component?
Thanks!