Environmental variables when exporting or importin

Unknown

Environmental variables when exporting or importin

Unknown

Hello Support,

Is there a recommended way to manage environment variables when using either the Export/Import feature or Repository Server, such that certain configurations can be dynamically handled as configuration is shifted from one environment to the next?

To illustrate this, the below is a basic example of what I am trying to work through, where there is a flow that references a REST API. The flow, when in the development environment, should reference the development instance of the API. However, when the configuration is pushed into the UAT environment, it needs to point to the UAT instance of the API, and the same behaviour again when pushed into Production.

Unknown

Hello,

This can be accomplished by using system constants. Here is a link to documentation that goes over how to set these up in Decisions:
[url=https://documentation.decisions.com/docs/establishing-constant-data-global-variables]https://documentation.decisions.com/docs/establishing-constant-data-global-variables[/url] You can parameterize the host of the REST service integration and this will give you an input to this REST step called "hostName". You can then create a system constant for hostname and use it as the input for this. Then you can set the value of this system constant to be distinct on each of the three servers and safely promote your flows between your different environments as Decisions does not over write system constants on import.