Skip to main content
Version: ACE 4

Workspace variables

It is possible to define workspace variables from ACE in order to reuse common variables (e.g. API_URL API_KEY)

Creating Workspace variable​

  1. open Settings section in ACE
  2. click on plus icon
  3. enter key and value for Workspace variable (if multiple variables need to be added click on plus icon until desired inputs have been created)
  4. click on save icon to store the Workspace variables in ACE

Using Workspace variable in flows​

Workspace variables can be accessed from ACE flow using $env.ENV_VARIABLE_KEY e.g. if the Workspace variable was set with key API_TOKEN then in flow it can be accessed using $env.API_TOKEN

The usage of variables in steps varies (please refer to each individual step documentation), but the most common usage pattern for consuming the workspace variable is with double curly brackets

e.g. for setting the url for REST step it would be {{$env.API_BASE_URL}}/get/policy.

Overriding workspace variable​

System environment variables override variables defined in workspace, so it's possible to override environment specific variables via environment variables defined in Docker or other way.

info

ACE reads variables defined in flow-runner service

For instance if there is a workspace variable API_BASE_URL=https://my.service.url and environment variable API_BASE_URL=https://prod.service.url (defined in flow-runner service), expression {{$env.API_BASE_URL}} will return https://prod.service.url