Skip to end of metadata
Go to start of metadata

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

NameDescriptionScreens (Click to view)
ID

Env variable id. Only letters (a-z and A-Z), numbers (0-9) and underscore (_) are allowed in the ID field. ID cannot have space. Mandatory field.

Figure 1: Add Env Variable

RemarksOptional, typically used as remarks to Joget developers.
Value

Environment Variable value. Can be a number or a static value or a piece of software code (HTML, CSS, Javascript, Java, etc.).


Hash Variables

You can use Hash Variable to reference a value in Environment Variable.


Related Links


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.



  • No labels