Rich Text Editor Component

Overview

Starting 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

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.
Allows uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plugin from https://community.appian.com/b/appmarket/posts/rich-text-editor-image-upload-connected-system).

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

Component: fn!richTextField()
Allows for size validation
Allows for adjustable height
Allows for read-only / editable view
Supported font formats: "header", "size", "bold", "italic", "underline", "strike", "color", "background", "link", "align", "indent", "list"
Designer control over the allowed formats

Supported Browsers: Chrome, Firefox, Edge, Safari
Supported on Mobile

Dan Tobias over 2 years ago in reply to Anyan Hu

I believe that's an issue with the component plugin framework rather than this particular plugin. Can you please open a support case about it?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Anyan Hu over 2 years ago

Hi Team, these days our platform move upgrade to 22.3, and for this plugin, sometimes it will load fail, and find some api response 403 code, do you know the cause?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Yulia over 2 years ago in reply to Jed Fonner

Thank you!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 2 years ago in reply to Yulia

No component plug-ins are compatible with Portals... yet. Hopefully that will come soon.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Yulia over 2 years ago

Is the Rich Text Editor Component compatible with portals?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Appian AppMarket over 2 years ago
v1.8.3 Release Notes
- Accessibility: allow tabbing through buttons
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 2 years ago in reply to rashida0001

Yes, it will always be backwards compatible
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
rashida0001 over 2 years ago

Hi Team,
Can anyone confirm if Rich text editor Plugin will be backward compatible in higher versions after Appian version upgrades.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 2 years ago in reply to Venkatesh Suram

1. The plugin uses deprecated functionality however there are no plans to address it since there is no workaround. There is no actual risk as that functionality will not be removed. We will see if we can suppress it from the health check so it's no longer incorrectly flagged as a risk.

2. There is a separate plugin function that supports tables in that plugin, see here for more details: community.appian.com/.../end-user-rich-text-editor-component
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Venkatesh Suram over 2 years ago

Hi Team,

Can you please help me out on below queries.

1. In the Appian Health check it is flagged as medium risk item. Please find more details. Are we going to update plugin code OR IF we use the plugin now, Is there any risk involved?.

Example: "Appian Connected System - Rich Text Editor (com.appian.richtext.csp) references deprecated Appian APIs [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getContentService(com.appiancorp.services.ServiceContext)" .

2. Is there any plans for support the tabular format in future releases?.

Thanks!!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel