---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Use the SetEnvironmentVariable component

# Use the SetEnvironmentVariable component {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create or update an environment variable as part of an automation Workflow by using the SetEnvironmentVariable component in RPA Desktop Design Studio. These variables persist across activities and can be retrieved later using GetEnvironmentVariable.

## Before you begin

Role required: none

## About this task

You can configure the properties for the SetEnvironmentVariable component. For more
information about these properties, see [Properties of the Environment components](https://www.servicenow.com/docs/M52C7kQV1A9HMXruB0fK_Q "Learn about the properties of the Environment components in RPA Desktop Design Studio.").

## Procedure

1. In the Toolbox pane, navigate to UtilitiesEnvironment.
2. Drag the SetEnvironmentVariable component to the Design surface.
3. To configure the input fields, see [Configure port properties](https://www.servicenow.com/docs/o6fErdzBCUqYUWlLG1ZZzQ "Configure how data is passed to the input fields of a component or method in RPA Desktop Design Studio.").
4. Connect the data and control ports of the SetEnvironmentVariable component to the corresponding ports of the other components as described in the following table.  
   {#use-environment-setenvvariable__table_jnw_jn1_krb__entry__3}

   | Port type | Purpose of connection | Mandatory? |
   |-|-|-|
   | Data In (variable) | Takes the environment variable name from a previously executed component. | Yes |
   | Data In (value) | Takes the environment variable value from a previously executed component. | Yes |
   | Control In | Connects to the Control Out port of one or more components. | Yes |
   | Control Out | Connects to the Control In port of another component or the default end component. | No. Connecting the port is optional. |
   [ ]

   {#use-environment-setenvvariable__table_jnw_jn1_krb}
5. **Optional:** To test the component, under the DESIGN tab, click Run.

## GetEnvironmentVariable component {#use-environment-setenvvariable__example_ucn_zxd_ggc}

You want your robot to process files and save logs to different folders depending on whether it's running in Development or Production mode.

1. At the start of the automation, use SetEnvironmentVariable to define the following variables:
   * `ENV_MODE = Development`
   * `LOG_PATH = C:\RPA\Dev\Logs`

   {#use-environment-setenvvariable__ul_of4_g12_ggc}

   This variable defines if robot is running in the development mode, where to store the log files.
2. Later in the workflow, when saving log files, use GetEnvironmentVariable to retrieve the value of `LOG_PATH`.

   The robot dynamically stores the log files as per the value in the
   `LOG_PATH` variable.
3. In production, simply update the environment variable setup to:
   * `ENV_MODE = Production`
   * `LOG_PATH = C:\RPA\Prod\Logs`

   {#use-environment-setenvvariable__ul_xnm_r32_ggc}

   The robot now logs to the production folder automatically, because it reads the `LOG_PATH` value from the environment variable.
{#use-environment-setenvvariable__ol_l3b_f12_ggc}

*[\>]: and then