Rich Text Editor Component

IMPORTANT: Select component plug-ins are experiencing issues due to a recent browser update. If you encounter any problems with previously functional component plug-ins, please create a support case. If you notice other component plug-ins that are not functioning correctly, please create additional support cases for each instance.

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
  • When the keyboard is Arabic and a mixture of numbers and Arabic is typed in, the numbers are not updated as right to left.  The numbers are updated on the incorrect side.  for example --- when wanting to type "2024/09/10 arabic"  from the right side -- the arabic text is typed first and then number (RTL), the text appears as " 10/09/2024 arabic". The english numbers are typed from LTR while the arabic is typed RTL.  Depending on the keyboard setting, all the flow is expected to be from RTL.  This is a mixture of RTL and LTR.  

Comment
  • When the keyboard is Arabic and a mixture of numbers and Arabic is typed in, the numbers are not updated as right to left.  The numbers are updated on the incorrect side.  for example --- when wanting to type "2024/09/10 arabic"  from the right side -- the arabic text is typed first and then number (RTL), the text appears as " 10/09/2024 arabic". The english numbers are typed from LTR while the arabic is typed RTL.  Depending on the keyboard setting, all the flow is expected to be from RTL.  This is a mixture of RTL and LTR.  

Children
No Data