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.
fn!richTextField() features include:
Supported Browsers: Chrome, Firefox, Edge, IE11, Safari, and Mobile
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 Rich Text Editor Component, please see the troubleshooting guide: https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide.
Share:
Hey Alberto, if you open up your browser's developer tools interface (ctrl+shift+I if using Chrome), and check the console tab, do you see any errors?
hi Philip,
This plugin requires dynamic content domain. I tried but failed.
Could you share us the detail configuration for dynamic content domain?
Thanks in advance.
Thank you for creating this component. But I have run into a problem with this component in one of my applications that you might be able to help me resolve. When opening a form that has several of these components some times I can't type into one or more of the fields. It is like it does not have focus. To solve this issue I have asked the users to click in another field and then come back to the rich text field and you can type. Any thoughts or ideas?
Hello,
Many thanks for this plugin, it works great!
We have found some issues with IE11 though, related to the use of flexbox when the component is used in readonly mode. We believe this issue is due to the readonly mode using display:flex on its #parent-container. If we manually remove that style using our browser tools in IE11, the readonly view displays correctly in IE11.
Apparently there are many known issues with flexbox and IE11:
Would it be possible for you to have a look at this issue to make sure that this component works correctly for IE11 when in readonly mode?
Many thanks,
Philip.
Hi!
I'm trying to use this plugin in my interface but it doesn't show nothing:{ a!sectionLayout( label: "Section", contents: { richTextField( label: "Rich Text", richTextValue: ri!rich, richTextSaveInto: ri!rich, enableProgressBar: true ) } )}
What is wrong with my code??
The Appian version is 19.3.
Thanks!
Just place the .zip file you downloaded. The package is extracted and the component is available to use.
The file available to download is a zip file, why not a jar file? where do i get the jar for installing on on-permise.
The file available to download is a zip file, why not a jar file?
Hello I am attempting to install this plugin in an On-Premises 19.3 installation. I am receiving the following error:
'No plugin factories found for plugin file Unit: C:\appian\_admin\plugins\ComponentPlugin_Rich_Text_v1.0.15_signed.jar (1568818065954). Does it contain an appian-plugin.xml file?'
Please advise.
hi all, when testing this plugin, it says "This component requires the dynamic content domain to be properly configured. Contact your system administrator." could please share the configuration, thanks.
Currently, we require the value to be saved upon keypress. Anyway that we can allow that?
Component Plug-ins were introduced in 19.1. Therefore, this requires at least 19.1 to be used.
The file available to download is a zip file, why not a jar file? I am getting Errors when deploying it in 18.4. Even after renaming the component from zip to jar
Does this plugin work in Appian 18.4?
pavansastrya please email richtext-componentpluginsupport@appian.com for support.