Rich Text Editor Component

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

muhammadh669742 over 1 year ago

Which kind of formats does not supports by this editor?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Appian AppMarket over 1 year ago
V1.11.3 Release Notes
1. Updated to improve accessibility.
2. Set aria-expanded="false" as the default for buttons that expand to a menu.
3. Set aria-label="formatting options" on the toolbar to announce the purpose of the toolbar for screen readers.
4. Removed aria-hidden="true" from the close button on the link dialog to comply with the Fourth Rule of ARIA Use (www.w3.org/.../
5. Updated the keyboard focus indicator on the color palette menu to increase the color contrast.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Rob Turverey over 1 year ago

Our 508 team found that JAWS does not announce the label for this component correctly. Our label was "Message" and the 508 team expected JAWS to announce it as "Message edit contain text type in text". Instead, JAWS announced it as "Edit contain text type in text"

It seems like the label itself is missing from what JAWS reads
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 1 year ago in reply to gauravp9819

There's no limit, you can set it as high as you want. Just be careful to not set it too high if you're saving the data to process variables or the database.

The plugin just renders HTML and strips out non-supported formatting. You will have to write rules to convert stuff or remove blank boxes before sending it to the plugin.

There might be other plugins that meet your needs, you can search around, I'm not sure.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
gauravp9819 over 1 year ago in reply to Dan Tobias

Whenever we ingest emails which have text embedded on the top of say a coloured background and a few images within the template ,viewing it in the this plugin is very very difficult , Images won't render and I will see blank boxes , and just Texts , also I will always see Content Exceeded Error , which wont' go away ,even say number of characters are just 100.Any solutions? or should we use some other plugins?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
varunbawa over 1 year ago

Would appreciate any possible solution for the question asked in below thread for Rich Text Editor:

https://community.appian.com/discussions/f/user-interface/29359/hidden-html-tags-showing-in-rich-text-editor
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Appian AppMarket over 1 year ago
v1.11.1 Release Notes
- Upgraded the bootstrap version.
- Images uploaded will now use the Opaque URL for documents, introduced in 20.3 - https://docs.appian.com/suite/help/22.4/Opaque_URL_Guidance.html.
- This change requires the usage of a version of the companion Connected System plugin that also relies on Opaque URLs.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Venkatesh Suram over 1 year ago in reply to Dan Tobias

Thanks for the response Dan Tobias. What is the maximum size of the richtext data allowed.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 1 year ago in reply to justinc7991

These will be fixed in the next release of the component plugin, hopefully this week.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 1 year ago in reply to Venkatesh Suram

There is a parameter on the component called maxSize which is configurable and lets you increase the allowable size. It defaults to 10,000. You can increase this to support more content.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel