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 3 years ago in reply to Dan Tobias

Fast turnaround, the download here has already been updated to be the signed one! Please re-download.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 3 years ago in reply to Hishore Nallasivam

Can you please email richtext-componentpluginsupport@appian.com and we'll provide the signed one via email. Not sure why it's not on the Download itself, we will sync with someone on that.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Hishore Nallasivam over 3 years ago

We won't have the developer token. Can you please provide the signed package for the on-premise environment?

We are getting this below error.

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in 'com.appian.richtext' (com.appian.richtext) version 0.0: 'Component plug-in approval verification failed. Please contact Appian for approval process

Please let us know if you need any other details.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Appian AppMarket over 3 years ago
v1.8.1 Release Notes
- IE support
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
juergeng0002 over 3 years ago

This component is nice.
Does it also support super/subscript functionality?
- Cancel
- Up +1 Down
- Reply
- More
- Cancel
Dan Tobias over 3 years ago in reply to Amit Lathkar

Unfortunately Component Plugins aren't supported in either Grids or Side-by-Side Layouts.

I've logged a use case for you.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Amit Lathkar over 3 years ago

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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 3 years ago in reply to CharlieS
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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
CharlieS over 3 years ago in reply to Appian AppMarket

Since the latest version, the field does not trigger validation if required.

Validations through the validations parameter still work as expected.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Jed Fonner over 3 years ago in reply to Appian AppMarket

The aria labels should help with screen reader support for fn!richTextField
- Cancel
- Up 0 Down
- Reply
- More
- Cancel