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

pieterk over 5 years ago in reply to nupoorn0002

Hi there

Did you ever manage to resolve this issue?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Fabio Basile over 5 years ago

Am I the only one having troubles setting the richTextField component to be required?

If I set it to required I can submit the form even with the component left empty

Hope it is easy enough to fix!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
pavan.sastry over 5 years ago

Waiting for this component to be updated with some fixes for issues being faced
- Cancel
- Up -1 Down
- Reply
- More
- Cancel
Jacob Edelman over 5 years ago

Any plans to support html tables?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
nupoorn0002 over 5 years ago in reply to nupoorn0002

Could you please suggest the solution and tell why this error.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
nupoorn0002 over 5 years ago in reply to joec0010

Hi Joe, I am facing similar issue, plugin installed on Premise, but not working, opened Developer's tool in chrome, got the error:
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
joec0010 over 5 years ago in reply to Alberto Mata

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?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
eaglez over 5 years ago in reply to philips0001

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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
helmuta over 5 years ago

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?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
philips0001 over 5 years ago
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:
- IE 11 requires a unit to be added to the third argument, the flex-basis property see MSFT documentation
- In IE10 and IE11, containers with display: flex and flex-direction: column will not properly calculate their flexed childrens' sizes if the container has min-height but no explicit height property. See bug.
- IE 11 does not vertically align items correctly when min-height is used see bug
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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel