Environment variables are configured through the Frends UI and stored securely in the database.

Environment variables are optional static configuration information that is attached to a specific Environment. These variables are most commonly used to store integration process related information such as passwords and usernames of the systems that are being connected into.

You can create Environment variables in different categories to help organize similar variables together.

  • Key-Value pairs, for storing simple information such as connection strings.

  • Hierarchical Groups, for storing all the information relating to a specific object such as ERP password, username and server location.

  • Lists, for storing repetitive information such as the IP addresses of your client servers. For example, these lists can be used directly in Foreach loops, that can iterate over them. 

There are no limitations in what you can store in an Environment variable.

Storing Information

The main advantage in using Environment variables is that after configuring them you can simply refer back to an Environment variable in your Process to access the configured value and if you need to change that value you can update it on the fly in the Environment variables page.

Environment Specific Information

The other benefit of using Environment variables is that you can configure them to be Environment specific. This means that you can use a different password, or even a different server, for an integration process in the test Environment than you do in the Production environment. This allows for seamless development, testing and production life-cycle because the configuration of each Environment is tied to an appropriate Environment variable.

Environment Variables in a nutshell

  1. You only need to keep track of these variables in a single place

  2. If a variable changes you only need to update it once

  3. You can securely store sensitive information such as passwords as environment variables, using the secret variable type

  4. You can have different variables for different environments

Example

Following image show environment variable Foo, that has value bar in Development environment and foobar in Test environment. It is possible to these values in processes by using reference #env.Foo

Did this answer your question?