Joget DX 8 Beta Released
The beta release for Joget DX 8 is now available, with a focus on UX and Governance.
Text Area is one of the generic HTML Form input elements. Unlike Text Field, Text Area has multi-row like interface for a user to type in more information
The easiest way to see how the Text Area button works is to use the existing built-in App Expenses Claims. Here are the steps:
Element ID (By declaring as "justification", a corresponding database table column "c_justification" will be created)
Please see Form Element for more information about defining the ID and list of reserved IDs.
Element Label to be displayed to the end-user.
Default Value when there's no existing value found.
A hash variable is accepted here. For example, you may key the following
to pre-populate the field with currently logged in user's name.
Attach a Validator plugin to validate the input value.
When will validation takes place?
Validation will take place whenever a form is submitted, except when it is submitted as "Save as Draft".
The placeholder attribute specifies a short hint that describes the expected value of an input field (e.g. a sample value or a short description of the expected format). The short hint is displayed in the input field before the user enters a value.
Determines if the element is editable.
|Display field as Label when readonly?|
Displays the value of the element as plain text when an element is set to "Readonly".
If the form is part of a workflow process, upon saving of the form (by clicking on "Save as Draft" or "Complete" button). The value in this input field will be saved into the corresponding workflow variable named here.
Using a non-existent Workflow Variable name
You will get the following warning with the name printed out (e.g. status) in the server log if you attempt to map to a non-existent Workflow Variable.
context attribute status does not exist in process context - adding new attributes to the process context is not allowed