Information
  • Author: Vuram
  • Type: Plug-in (Component)
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 22.3
  • First Released:
  • Last Updated:
  • Cost: Free
Resources
Share
Home » AppMarket » Advanced Rich Text Editor (Vuram)

Advanced Rich Text Editor (Vuram)

Overview

The Rich Text Editor Component can be used on Appian interfaces where you want to show the rich text information in readable format to the end user. We can use the component to show it as an email subject typing interface.

With this component you can add images, customize tables etc. This also has a functionality called placeholders using which you can use the same information in multiple items in the editor without retyping.
Additionally it allows uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plug-in).

Note:

  1. It is recommended to use one ARTE Component in a Page/Interface.
  2. We do not encourage to use Short as height in the component.

Key Features & Functionality

Parameters:

  • Label : Text to display as the field label.
  • Label Position: Determines where the label appears. Valid values: “ABOVE” (default), “ADJACENT”, “JUSTIFIED”, “COLLAPSED”.
  • Height: Determines the layout height. Valid values: “SHORT”, “MEDIUM”, “TALL”, “AUTO” (default).
  • MaxSize: Maximum size of the rich text data. Default:10000
  • Placeholder : Placeholder text to display in the component wherever you want.
  • richTextValue: Rich text to display in the field.
  • richTextSaveInto: One or more variables that are updated with the richText value when the user changes it. Use a!save() to save a modified or alternative value to a variable
  • IsReadOnly: Determines if the field should display as editable or not. Valid Values : True or False
  • allowImageUpload : Determines if image upload are allowed. Default: false.
  • imageStorageConnectedSystem: The instance of the connected system used to store images from the rich text editor. This is required if allowImageUpload is set to TRUE. You can download the Connected System from the Appian App Market.
  • Show Usage Bar: Provide false to hide the usage bar at the bottom of editor. Default true
  • Enable Fullpage Output: Enabling fullpage exposes <head>, <body> and various meta tags in richText output. Default true.
  • Enable Spell Checker: Provide true to enable the spell checker. Default false.
  • Uploaded Images Doc Ids SaveInto- Document Ids of all uploaded images will be saved into this rule variable.
  • Exported PDF Id - Returns the document ID of the exported PDF.
  • Enable Export Pdf- Provide false to disable the 'Export as PDF' button. Default: True
Anonymous
Parents

  • Hello Vuram Team,

    We are facing below issues while using richTextEditorField for our Application-

    1. Users are able to upload/ copy paste images, even though allowImageUpload  is set to false.
    2. We have set maxsize to 65000. When user is adding a image that is breaching the limit of 65K , validation is not getting triggered properly and user is able to create the record with more chars than the defined limit.
      When user tries to update the same record later, he is unable to do so due to validation coming.

      Ideally validation should have come in the first place itself when user is creating the record.

    Hoping for a quick resolution.

    Thank You.

Comment

  • Hello Vuram Team,

    We are facing below issues while using richTextEditorField for our Application-

    1. Users are able to upload/ copy paste images, even though allowImageUpload  is set to false.
    2. We have set maxsize to 65000. When user is adding a image that is breaching the limit of 65K , validation is not getting triggered properly and user is able to create the record with more chars than the defined limit.
      When user tries to update the same record later, he is unable to do so due to validation coming.

      Ideally validation should have come in the first place itself when user is creating the record.

    Hoping for a quick resolution.

    Thank You.

Children
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.