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

Anonymous
  • Hi,

    I am noticing a couple of issues with this plugin:

    1. The following HTML tagged text rendered using the Rich Text Editor plugin renders with a line break between the <strong> tags, as seen in Image 1, whereas the same tagged text renders on a modern website or renderer (for example: https://htmledit.squarefree.com/) without this line break as seen in Image 2. 

    "Heating Evenness: This model performed fair in our heat evenness test consisting of reheating a bowl of mashed potatoes. blabbbla bla bla.<br/><strong>Auto Defrost: This model performed</strong><strong>3.6613622820666666</strong><strong>in our defrosting test consisting of thawing a pound of frozen ground beef.</strong>"

    1. The following HTML tagged text rendered using the Rich Text Editor plugin mentioned above renders with a whole line separating text if there is a space between tags (example: "</strong> <strong>"), as seen in Image 3, whereas the same tagged text renders on a modern website or renderer (for example: https://htmledit.squarefree.com/) without this new paragraph behavior as seen in Image 4. 

    "Heating Evenness: This model performed very good in our heat evenness test consisting of reheating a bowl of mashed potatoes. blabbbla bla bla.<br/><strong>Auto Defrost: This model performed</strong> <strong>5.1690371066666666</strong> <strong>in our defrosting test consisting of thawing a pound of frozen ground beef.</strong>"

    Would the author be able to adjust the behavior of its plugin to match the standards of other tools that render HTML tags?

    Thank you,
    Walker

  • Hi, I have form where I am using this component along with some OOB appian component like radio box,textField and all. when open the form OOB component loads immediately how ever this component takes 3 to 4 second to load after the normal component 

    Is there any workaround for this 

  • Hi,

    Can you please help us out with below issues for the plugin:

    It is observed that the plugin adds <p> tags for every statement for every new line text.

    Eg: <p>Hi Sonakshi</p><p>How are you?</p> which returns extra line breaks when viewed in html.

    Result:

    Expected Result:

    Thanks in advance.

  • Hi there

    Did you ever manage to resolve this issue

  • Hi there

    Did you ever manage to resolve this issue?

  • 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 Disappointed

    Hope it is easy enough to fix!

  • Waiting for this component to be updated with some fixes for issues being faced

  • Could you please suggest the solution and tell why this error.

  • Hi Joe, I am facing similar issue, plugin installed on Premise, but not working, opened Developer's tool in chrome, got the error: