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
  • How can we remove extra spaces if added in rich text editor. We use a form layout and have this component. Even if no value is added by default it gets saved as "<div> </div>". If a user in UI just presses the space bar and enter and then space bars then also it is getting saved. We want to save the value only when there is a valid text value. We save it in rule input which is of type "text". Appian Version used in 21.1

  • You can use stripwith and striphtml to remove the HTML tags and spaces and check if there's any actual content.

    For example, this will return false to indicate the local!data does not contain any actual content: 

    a!localVariables(
    local!data: "<div> </div>",
    local!content: stripwith(
    striphtml(local!data), char(10)&char(32)),
    a!isNotNullOrEmpty(local!content)
    )

    But this will return true to indicate there is actual text there:

    a!localVariables(
    local!data: "<div>Some actual content </div>",
    local!content: stripwith(
    striphtml(local!data), char(10)&char(32)),
    a!isNotNullOrEmpty(local!content)
    )
Comment
  • You can use stripwith and striphtml to remove the HTML tags and spaces and check if there's any actual content.

    For example, this will return false to indicate the local!data does not contain any actual content: 

    a!localVariables(
    local!data: "<div> </div>",
    local!content: stripwith(
    striphtml(local!data), char(10)&char(32)),
    a!isNotNullOrEmpty(local!content)
    )

    But this will return true to indicate there is actual text there:

    a!localVariables(
    local!data: "<div>Some actual content </div>",
    local!content: stripwith(
    striphtml(local!data), char(10)&char(32)),
    a!isNotNullOrEmpty(local!content)
    )
Children
No Data