Rich Text Editor Component

Arial

Courier New

Georgia

Tahoma

Trebuchet MS

Calibri

EB Garamond

Lucida Sans Unicode

Times New Roman

Verdana

Label Text                                                                        

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case.

Disable User Input                                                                                        

When set to (ON), end-users cannot interact with or edit the Express View's input field or element. When end-users hover over the field, their cursor changes to alert them to the status change.

By default, Disable User Input is set to (OFF).

Hide Field                                                                                        

Displays or hides the component from view. Setting Hide Field to (ON) hides the component in Express View. Setting it to (OFF) displays the component. The component is always visible in the Module Builder.

By default, Hide Field is set to (OFF).

Hide Toolbar in Express                                                                                        

When set to (ON), the Editor's toolbar is hidden from the end-user in Express View. This setting is useful when you want to display read-only content to the end-user.

By default, this setting is set to (OFF).

Read Only Content View                                                                                        

When set to (ON), the Default Content field displays in the component's configuration window. Content entered in this field displays as read-only to the end-user. When set to (ON), the Reference Content feature available.

By default, this setting is set to (OFF).

Default Content                                                                                            

This field offers a semi-WYSIWYG (What You See is What You Get) content editor.  Built to look like a word processor, this editor lets you create, edit, and format your content.

Entering content into the editor and setting the component as read-only makes the content user-facing. If you don't set the component as read-only, the end-user has a blank content field to edit in Express View.

This setting is available when you set Read Only Content View to (ON).

Reference Content                                                                                            

This field lets you reference content from other components. To reference content, choose the Property ID of the referenced component and give it an alias. Then, reference that alias in the Editor. To work, you must surround your alias in curly braces. For example, {{Name}}.

Where you entered the alias, the end-user will see the referenced content.

This setting is available when you set Read Only Content View to (ON).

Store Data in Database

The Store Data in Database setting affects how data persists through your application. When set to (ON), Unqork stores values entered into the field to the database (server-side submission). This occurs in three scenarios:

• Navigating between Panels in a Navigation component. On navigation between pages (Panels), the component’s value saves to the database.

• Triggering a module save event using a Button component with an Action Type of Save.

• Navigating between screens of a workflow. On navigation between screens, the component’s value saves to the database.

  By default, workflows persist data from all fields in the client-side submission when navigating between screens. However, only values from fields with Store Data in Database enabled store in the server-side submission.

Set the toggle to (OFF) when you don’t want to store the values from this field in the database.

When using a Plug-In to remote execute a module, ensure data moving between modules is persistent. You can optionally enable Store Data in Database for components in the source module. But any components in the API module whose values are included in an API response must have Store Data in Database enabled. When a component’s data is not persistent, the data isn't included in an API call's response. So, Plug-Ins or external services requesting data from the API module can't receive non-persistent data in the response.

Store Data in Database also affects what data is tracked using Unqork’s built-in tracker. When the Enable Tracker and Track Value toggles are set to (ON) in Module Settings, only values from fields with Store Data in Database enabled are tracked.

By default, the Store Data in Database toggle is set to (ON).

Required                                                                    

When set to (ON), the end-user must enter a value in the component's visible fields. When set to (OFF), the input is optional.

By default, Required is set to (OFF).

Error Message                                                                    

A custom error message that displays below a required field. The error message displays when the end-user tries to save or submit the module without completing the required field.