Search Crosser Knowledge Base

Environment Variables

With the release of our Control Center on Feb 6th we introduced a new way of configuring modules. The Interactive Wizard for Data Selection and Mapping lets you configure modules in a more intuitive way by interacting with the source or destination systems. The feature is available for everyone as a preview and is currently implemented on the following modules:

If you add this information to your payload and store it in your database as an example, you have the possibility to backtrace which flow version generated the specific dataset on which Node.

Environment variables can be picked using the following template syntax:

{$ENV.< variable name>}

The following environment variables are supported:

  • NODE_NAME
  • NODE_ID
  • NODE_VERSION
  • NODE_PLATFORM
  • FLOW_NAME
  • FLOW_VERSION
  • FLOW_ID
  • FLOW_DEPLOYMENT_ID (only available if flow is deployed)

Example using the Message Template module, Target Property set to “meta”:

{
  "node.name": {$ENV.NODE_NAME},
  "node.id": {$ENV.NODE_ID},
  "node.version": {$ENV.NODE_VERSION},
  "node.platform": {$ENV.NODE_PLATFORM},
  "flow.name": {$ENV.FLOW_NAME},
  "flow.version": {$ENV.FLOW_VERSION},
  "flow.id": {$ENV.FLOW_ID}
}

Crosser-Evironment Variables
Environment variables can be used in modules that support template syntax, such as Property Mapper and Message Template.

About the author

David Nienhaus | Senior Solution Engineer

David is a Senior Solution Engineer at Crosser. He has over 10 years experience working with software integration and digitization projects for critical infrastructure.
His engineering background gives him the understanding and focus needed to solve customer use cases in the most efficient and successful way.