OverviewDisplays 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).
Visit End-User Rich Text Editor Component for more information.
If you have any problems installing or using the component, please see the Rich Text Editor Component Plug-in Troubleshooting Guide
Key Features & Functionality
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
Since the latest version, the field does not trigger validation if required.
Validations through the validations parameter still work as expected.
Hi Charlie, sadly I think the requiredness has always worked this way. The notes section of the playbook mentions
The parameter required doesn’t actually validate that the richTextValue is not null. This is a limitation of the component plug-in framework. Use section-level or form-level validations to validate the requiredness of the richTextValue.