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
fn!richTextField() features include:- size validation- adjustable height- read-only / editable view- many supported font formats, including: "header", "size", "bold", "italic", "underline", "strike", "color", "background", "link", "align", "indent", "list"- designer control over the allowed formats- uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plugin and requires Appian 19.3 or later)
- Supported: Chrome, Firefox, Edge, IE11, Safari and the Appian Mobile Apps
Thanks for the information but our Appian instance is created in 21.1 hence non-opaque URLs are not supported at all. Seems the solution is to only update the component.
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.
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.
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?
The same html renders correctly on any online html editor:
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?
Hi,the plugin need some specific configuration after installation? because a message appear "System configuration missed" instead of plugin interface.Thanks.
Note that when clicking the "Post Comment" link it
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!
Der, upgraded the component and can no longer reproduce the issue. Thanks for the help!
© 2021 Appian. All rights reserved.