Versions Compared

Key

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

Image Removed

 

Image Removed

 

Figure 1: Screenshot highlighting a Hidden Field in sample Expenses Claim App

Screenshots in this article obtained from http://localhost:8080/jw/web/console/app/hr_expense/1/form/builder/hr_expense_new

Image Added

Figure 2: Hidden Field Properties

NameDescription
IDElement ID (By declaring as "status", a corresponding database table column "c_status" will be created)
Default Value

Default Value when there's no existing value found.

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

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

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

 

Image Added

Figure 3: Hidden Field Properties

NameDescription
Data PriorityDetermines on which value to be taken into consideration. There are 3 options with their own data precedence to cater to different use cases.
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