Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The easiest way to see how the Text Field works is to use the existing built-in App Expenses Claims. Here are the steps:

StepsScreen (Click to view)
  1. Start the Joget Server and open the App Center.

  2. Log in as admin and click on the pencil icon on the Expenses Claim to open the Design App. (see Figure 1)

  3. Click on  Expense Claim New and you will be directed to the Form Builder. 

  4. Hover the mouse over the Title (Example: China Travel, July Claims, etc.) field and click on Edit to open up the Edit Text Field properties. 


  5. Click on
Preview
  1. Preview and try entering values into the Text Field.

Image Modified

Figure 1


Image Modified

Figure 2


Text Field Properties

Edit Text Field Properties

...

NameDescriptionScreen (Click to view)
Value

Default Value when there's no existing value found.

A hash variable is accepted here. For example, you may key the following

Code Block
#currentUser.firstName# #currentUser.lastName#

to pre-populate the field with currently logged in user's name.

Max Length

Maximum character length allowed.

Validator

Attach a Validator plugin to validate the input value.

Info
titleWhen will validation takes place?

Validation will take place whenever a form is submitted, except when it is submitted as "Save as Draft".

Encryption

Determines if the value should be encrypted upon saving into the database. Read more in Protect Sensitive Data.

Workflow Variable

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.

Info
titleUsing 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.

Code Block
context attribute status does not exist in process context - adding new attributes to the process context is not allowed


UI

NameDescriptionScreen (Click to view)
Placeholder

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.

Image Modified




Size

Width of the element.

Readonly

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".

Workflow

NameDescriptionScreen (Click to view)
Workflow Variable

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.

Info
titleUsing 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.

Code Block
context attribute status does not exist in process context - adding new attributes to the process context is not allowed

Image Modified

Number Formatting

NameDescriptionScreen (Click to view)
Formatting Style
  • US Style Formatting (1,000.00)
  • European Formatting (1.000,00)

When you have selected this option, you can further define the following attributes:-

  • Number of Decimal
  • Prefix
  • Postfix
  • Use Thousand Separator?

Image Modified

Store as Numeric Value?

When formatting is applied, value is stored as it is. You may check this option to strip off formatting and store it as numerical value only.