Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
The easiest way to see how the Hidden Field works are to use the existing built-in App Expenses Claims. Here are the steps:
Name | Description |
---|---|
ID | Element 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. 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. |
Name | Description |
---|---|
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. |
Validator | Attach a Validator plugin to validate the input value. Please see Form Validator. When will validation takes place? Validation will take place whenever a form is submitted except when it is submitted as "Save as Draft". Available Options:
|
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 |