Skip to end of metadata
Go to start of metadata

Project Variables

Overview

Project variables are set before runtime of the operation and become available to use across your project, for example within sources/targets, scripts, and transformations.

Project variables are first created via Design Studio. Once a project variable is created, you may set values for them either through Design Studio, the Management Console, or Citizen Integrator, providing the flexibility to set and change parameters and credentials without redeploying the project.

Common uses of project variables include for endpoint credentials, filenames, or variables that can change from environment to environment. Or, any variable that you want to be able to edit through the Management Console or Citizen Integrator.

Frequently Asked Questions

Q: What are the different types of variables in Jitterbit and how are they used?

A: Jitterbit has four main categories of variables:

  • Global Variables
    Global variables are set at runtime of the operation and become available to use downstream of the operation (i.e. in an operation chain). See Using Global Variables for more information.
  • Project Variables
    Project variables are set before runtime of the operation and become available to use globally within your project. See Using Project Variables for more information.
  • Local Variables
    Local variables are set within a script and can only be accessed within that script. See Using Local Variables for more information.

Q: Is there a performance difference between different types of variables?

A: Local variables are preferred since they are not persisted for other operations. Global and project variables must be cached for other operations. See Global Variable versus Temporary Storage for recommendations on when it is appropriate to use these two types.

Pages in This Topic
Search in This Topic

Last updated:  Nov 12, 2018