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
This component is nice. Does it also support super/subscript functionality?
Unfortunately Component Plugins aren't supported in either Grids or Side-by-Side Layouts.
I've logged a use case for you.
This component is really useful and works well. I feel, it should be added to Product. However, I came across following scenarios/use cases where I find it difficult to use.
1. We have a requirement to display rich text created by users via this component in a!gridField() columns. I don't see any support for displaying the rich text as-is from this component.
2. richTextField() function is not supported in Side by Side layout. I received following error.
Could not display interface. Please check definition and inputs. Interface Definition: Expression evaluation error at function a!sideBySideLayout [line 6]: A side by side layout has an invalid item. The item at index 1 contains a component that is not supported in a side by side layout. Received: CertifiedSAILExtension.
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.
Since the latest version, the field does not trigger validation if required.
Validations through the validations parameter still work as expected.
The aria labels should help with screen reader support for fn!richTextField
Is this plugin updated with opaque URLs to documents? The image upload is not working on 21.3 appian cloud and fails with "Not able to obtain doc id from the connected system".
Hi Matthew - we've seen problems where the Rich Text Editor gets cut off when it has too much content. It seems to be a browser bug related to iFrames. Appian uses iFrames to display component plugins, and some browsers don't print the entire iFrame when the iFrame. For reference, see this 18 year old Firefox issue that explains the problem: https://bugzilla.mozilla.org/show_bug.cgi?id=113217.
If you are trying to generate a printable copy of an interface, I recommend looking into the various document generation capabilities in Appian and on the App Market.