Joget DX Available for Download

Check out Joget DX, the next generation successor to Joget Workflow for faster, simpler digital transformation.

Skip to end of metadata
Go to start of metadata




Introduction

The Hidden Field is a standard HTML input element. Unlike Text Field, Hidden Field does not show up on the page, hidden away from the user. It is typically used to pass/set temporary or session-based information.


Get Started

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

StepsScreens (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. Under FORMS column, click on Expense Claim New (see Figure 2)

  4. Hover the mouse over the Hidden Field element on the canvas entitled status and click on Edit to open up the Edit Hidden Field properties. (see Figure 3)

  5. Click on Preview to open up the Preview tab, and you will not be able to see the Hidden Field.

Figure 1


Figure 2


Figure 3

Hidden Field Properties

Edit Hidden Field

NameDescriptionScreen (Click to view)
ID

Element ID (By declaring as "status", a corresponding database table column "c_status" will be created)

Please see Form Element for more information about defining the ID and list of reserved IDs.


Default Value

Default Value when there's no existing value found.

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

#currentUser.firstName# #currentUser.lastName#

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

Advanced Options

NameDescriptionScreen (Click to view)
Data Priority

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

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




  • No labels