Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

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

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

Children