Skip to main content

Environment Variables

Environment Variables allow you to manage environment-specific settings (e.g. tokens) without overwriting them when copying configurations between test and live environments. Use variables as auto-fill fields across actions and manage them centrally.

Arne Bracke avatar
Written by Arne Bracke
Updated over a month ago

When you need this

When preparing a config update on a test environment, you often want to deploy the updated configuration to your live environment. Many configurations contain environment-specific details, such as:

  • Link and credentials to connect to a TMS environment

  • Link and credentials to connect to an ERP system

  • Other connection details or tokens.

When copying your configuration from test to live, you usually do not want these environment-specific values to be overwritten.

Main idea

Environment Variables let you store environment-specific parameters separately from your configuration. These values are defined per environment and remain untouched when copying configurations between environments.

All variables are maintained in a central list and can be used throughout your configuration via auto-fill fields.

How does it work

Create a variable

  • Navigate to ⚙️ Configuration > Environment Variables

  • Click "New Variable"

  • Choose variable name, type and value

Variable types:

  • Default: For non-sensitive values that can be displayed openly.

  • Secret: For confidential tokens or passwords.

    • Note: Secret values are never visible once created. You can update them, but you cannot view the existing value.

Use variables as auto-fill fields

  • Open any action that supports auto-fill fields

  • Search for your variable—environment variables are always prefixed with Variable.

  • Select the variable to replace a hardcoded value

More information

Deletion Rules

Environment variables can always be deleted, even if they are currently referenced.

If a deleted variable is still in use:

  • It will appear highlighted in red in the UI where it was referenced

  • At execution time, the system will resolve it as undefined

Won't do / limitations

At the moment, environment variables cannot be used in configuration screens for:

  • I/O modules

  • Cameras

  • Scanners

  • Other device configuration sections

Did this answer your question?