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
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.