Share:
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
Note: uploading images is currently only supported for on-premise customers. We're working on a solution that will be cloud-approved.
Sorry, no. We're working with Engineering to see what, if anything, can be done to speed up the loading of the component.
For the curious, Appian loads pretty much all of its static files (JS, CSS, etc) when you first log-in, so no additional downloads need to happen as you load new pages and SAIL UIs. However, component plug-ins are different and their content gets loaded only when they are rendered. Unfortunately since they are sandboxed, if you have multiple on the page then their content each has to get loaded again, once for each instance of the component. We're looking into ways to streamline the number of separate static files in the component and also add more caching to the product to reduce the time to load the component..
Does this release update to slowness of rendering rich text editor compare to oob sail component
Right now the playbook recommends using the“validations” parameter or using section or form-level validations.
Is there any further update for making the component to be required?
Thanks - sent over!
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.
Please send us details, including a screencast/screenshot and browser version, to richtext-componentpluginsupport@appian.com so we can better help you.
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.
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
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.
This plugin makes use of the Quill.js library for handling rich text. That library does not support tables.
Which version of the plugin are you using? The newest version should use <div> instead of <p>
You refer to image 1-4. Are you able to attach those images to a comment?