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:

It is recommended to use one ARTE Component in a Page/Interface.
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

Santhosh Kumar over 3 years ago in reply to singaravelus0001

Hi singaravelus0001,

We can't reproduce the issue. Could you provide steps to reproduce the issues?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
singaravelus0001 over 3 years ago

Hi,

The plugins installed successfully but the value in the parameter "RichTextValue" is not displaying.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Santhosh Kumar over 3 years ago in reply to Gregor Gisler-Merz

Hi Gregor,

Due to security reasons, Appian documents are not shared publically over the internet. For your requirement, you can use the URL of the publically hosted image in the Component's insert image section. We will also be looking forward to Appian providing API to access its document without any security.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Gregor Gisler-Merz over 3 years ago

Hi,

Editor works fine. When creating a body for an email with images and send it externally to a client not having access to Appian these documents cannot be rendered in an email client due to the fact that the client has no access to Appian. Currently the easiest way to achieve this would be to fetch the inline residing images in Appian and attach those to the resulting email. Is there anything from your side available?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Santhosh Kumar over 3 years ago in reply to sivakumard0001

Hi sivakumard0001,

I understand your scenario. You need to wait until the load bar at the top to complete which executes the 'saveInto' to update the Local or Rule Input variable.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
sivakumard0001 over 3 years ago in reply to Santhosh Kumar

Yes we have tried that. Let me explain the testcase where we are facing issue upon submission :

Scenario 1 : Enter some data and hit submit. Validation works fine.

Scenario 2 : Enter some data, then clear the data and submit the form before form is loaded. Since richtexteditor loads little slowly the validation for richtexteditor and even sectionLayout fails.

Hope the scenario is clear here.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Appian AppMarket over 3 years ago
v1.1.1 Release Notes
- Added two new parameters “showUsageBar” and “enableFullpageOutput”
- Now users can copy the content in the ReadOnly mode.
- Placeholder option will be hidden when no value is provided for the placeholder.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Santhosh Kumar over 3 years ago in reply to sivakumard0001

The Required parameter only shows or hides the asterisk indicating but does not enforce requiredness. To enforce this behavior, use the parameter “validations”. To enforce requiredness only upon submission, use section, or form-level validations.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
sivakumard0001 over 3 years ago

Does the required parameter work in the component ? If I set it to required I am still able to submit the form even with the component left empty. Can you please advise on the same ?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
shwetad155 over 3 years ago

Hi,

We have deployed latest version of this plugin (1.1.0) in Appian cloud and we came across below issue.
It did not replace the existing(1.0.3) plugin version with the new version(1.1.0), however it got added as a new plugin.

Is it happening because of name difference ? (see below screen shot)

Thanks
- Cancel
- Up 0 Down
- Reply
- More
- Cancel