Rich Text Editor Component

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

Starting in 24.2, the Styled Text Editor Component is available directly in the product. Consider using this in place of the plug-in moving forward. For more information, review: https://docs.appian.com/suite/help/latest/Styled_Text_Editor_Component.html

Displays a field that allows for users to type text and format it with a variety of style options.
Output is saved as HTML. To get the raw character output, designers can use the Appian function fn!stripHtml() on the output.
HTML output can be passed into Send E-Mail node or document generation smart services. Note that not all formats supported by the Rich Text Editor component may be supported by e-mail or document generation.
Allows uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plugin from https://community.appian.com/b/appmarket/posts/rich-text-editor-image-upload-connected-system).

Visit https://community.appian.com/w/the-appian-playbook/1378/end-user-rich-text-editor-component for more information. If you have any problems installing or using the component, please see the https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide

Key Features & Functionality

Component: fn!richTextField()
Allows for size validation
Allows for adjustable height
Allows for read-only / editable view
Supported font formats: "header", "size", "bold", "italic", "underline", "strike", "color", "background", "link", "align", "indent", "list"
Designer control over the allowed formats

Supported Browsers: Chrome, Firefox, Edge, Safari
Supported on Mobile

PhilB over 4 years ago in reply to Jed Fonner

Thanks - sent over!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to PhilB

Please send screenshots of what you mean by "not to display as well" to richtext-componentpluginsupport@appian.com so we can better help you. Also include your browser version and SAIL code.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to helmuta

Please send us details, including a screencast/screenshot and browser version, to richtext-componentpluginsupport@appian.com so we can better help you.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
PhilB over 4 years ago

I think there's a potential issue with this component when trying to display HTML, in that using any level of nested <div> causes the top-level (ie containing) <div> not to display as well as all levels of <div> below.

Is this expected behaviour? Nesting <div> tags is fairly common on any number of websites.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to eaglez

Please check out the Rich Text Editor Troubleshooting guide which I believe will answer your question: https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to nupoorn0002

Please try the steps listed in the troubleshooting playbook page: https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide

It looks like your dynamic content URL might not be configured correctly. The above doc can you fix that.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to Jacob Edelman

This plugin makes use of the Quill.js library for handling rich text. That library does not support tables.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Michael Chirlin over 4 years ago in reply to sonakshid874

Which version of the plugin are you using? The newest version should use <div> instead of <p>
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Michael Chirlin over 4 years ago in reply to walkers0001

You refer to image 1-4. Are you able to attach those images to a comment?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
walkers0001 over 4 years ago
Hi,

I am noticing a couple of issues with this plugin:
1. The following HTML tagged text rendered using the Rich Text Editor plugin renders with a line break between the <strong> tags, as seen in Image 1, whereas the same tagged text renders on a modern website or renderer (for example: https://htmledit.squarefree.com/) without this line break as seen in Image 2.
"Heating Evenness: This model performed fair in our heat evenness test consisting of reheating a bowl of mashed potatoes. blabbbla bla bla.<br/><strong>Auto Defrost: This model performed</strong><strong>3.6613622820666666</strong><strong>in our defrosting test consisting of thawing a pound of frozen ground beef.</strong>"
1. The following HTML tagged text rendered using the Rich Text Editor plugin mentioned above renders with a whole line separating text if there is a space between tags (example: "</strong> <strong>"), as seen in Image 3, whereas the same tagged text renders on a modern website or renderer (for example: https://htmledit.squarefree.com/) without this new paragraph behavior as seen in Image 4.
"Heating Evenness: This model performed very good in our heat evenness test consisting of reheating a bowl of mashed potatoes. blabbbla bla bla.<br/><strong>Auto Defrost: This model performed</strong> <strong>5.1690371066666666</strong> <strong>in our defrosting test consisting of thawing a pound of frozen ground beef.</strong>"

Would the author be able to adjust the behavior of its plugin to match the standards of other tools that render HTML tags?

Thank you,
Walker
- Cancel
- Up +1 Down
- Reply
- More
- Cancel