OverviewStarting 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
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
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
Please send us details, including your SAIL code, a screencast/screenshot, and browser version, to richtext-componentpluginsupport@appian.com so we can better help you.
We are working on on-prime server which is 20.4, configured dynamic content URL and installed the plug-in. The component is not working though the dynamic content url is working without having any issues. I can able to retrieve the test page. So can you please let us know if any step is missing?
Hi everybody, does anyone have experience using the Rich Text editor to paste a table from Excel into the editor?
Dear All,
We are trying to capture user inputs using rich text editor which contains multiple fonts, bullets etc.. and then this information is used to generate a word document (DOCX). Can you help to suggest how we can generate this word document while retaining the rich text features ?
Currently we are on Appian 20.3 and we are using smart services available to generate the word document.
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..