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

nikhileshk over 4 years ago

Hi,

I was automating the regression test part of our application using Appian selenium API framework, Can some onw guide me on how to automate filling the sample data in to a rich text field.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 4 years ago in reply to chitras0003

Hello - we do have on our backlog to add support for the new opaque URLs. In the meantime, please see https://community.appian.com/w/the-appian-playbook/1378/end-user-rich-text-editor-component#imageuploads for instructions on how to enable non-opaque URLs to documents.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
chitras0003 over 4 years ago

Hi,

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. 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!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
walkers0001 over 4 years ago in reply to walkers0001

The same html renders correctly on any online html editor:
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
walkers0001 over 4 years ago

Hello,

I am seeing an issue where fn!richTextField() does not correctly render text if it starts and ends with paragraph tags: <p> and </p>.

Here is an example of with the <p> tags. See the raw input on the top, and the input rendered by the fn!richTextField() field on the bottom:

Here is an example without the <p> tags:

Does the fn!richTextField() not recognize paragraph tags? Could this be added in the next version?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Vincenzo Reggina over 4 years ago

Hi,
the plugin need some specific configuration after installation? because a message appear "System configuration missed" instead of plugin interface.

Thanks.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
evans0001 over 4 years ago in reply to evans0001
Note that when clicking the "Post Comment" link it
1. starts a process model with a!startProcess
2. nulls the value we are passing into richTextValue
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
evans0001 over 4 years ago in reply to Dan Tobias

Dan, we were actually able to reproduce similar a similar issue even with the latest plugin version. We caught a video. It looks like it's clearing the value while the component is still loading, so definitely a more uncommon case. Hope this helps!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
evans0001 over 4 years ago in reply to Dan Tobias

Der, upgraded the component and can no longer reproduce the issue. Thanks for the help!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 4 years ago in reply to evans0001

I'm not able to reproduce this on the latest version of the rich text editor (1.4.0). Do you have a screen record you could share, preferably from the /design interface?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel