Introduction
Environment Variables are used to store commonly used parameters or settings in the application. Storing commonly used values in one place eases the migration and maintenance of the application developed. Environment variables can be retrieved by using the Environment Variable Hash Variable.
One can make use of the Environment Variable to store commonly used values in places like Email Tool, Database Update Tool, and so on. Doing so makes it easier to manage setting/configuration changes.
Figure 1: Properties & Export
ID Generator Field Properties
Edit ID Generator Field
| Name | Description | |
|---|---|---|
| ID | Form field id. Only alpha-numeric and underscore characters allowed. Mandatory field. If you use "id", the form will save with the "id" primary key in running sequence. Joget will not create the "id" in UUID format. |
Figure 1: Add Env Variable |
| Remarks | Optional remarks to developers. | |
| Value | Environment Variable value. Can be a number or a static value or a piece of software code (HTML, CSS, Javascript, Java, etc.). |
Cautions And Warnings
When importing apps into a new Joget platform, for example from development to production server, do update all the environment values you may have defined; IP addresses, domain name, database connection strings values, etc.
However, if it is an existing app in a production server, do be careful not to change any environment variable counters that are link to your form's "ID Generator Fields". This may affect the running numbers in the form's new records.
If you are using the ID Generator Field as "id", meaning it is a primary key value, be careful not to override the environment variable value when inporting apps: do not click the "Show Advanced Options > Override environment variables" checkbox in Import App screen.