Variables

Avariable is an integration element that holds and transports data between the tasks, triggers, and edges of an integration.

• Variables can be statically defined at design time or dynamically passed to the integration at runtime.
• Variables can reference other variables in an integration.
• Variables can be globally accessible to all tasks, or locally accessible to a specific task.

Variables

In Application Integration, variables are set or initialized in various places:

• Config variables: Set at design time to store the configuration data of the integration. For example, you can use this to set a target email address for notification, rather than hard-coding that email address in the integration.
• System variables: Automatically generated by the system to store the configuration data of the integration. For example, theExecutionId variable stores the execution ID of the integration.
• Integration variables: Set explicitly in your integration to keep track of data throughout the course of an entire integration execution. For example, you can set a variable to store the result of a task and use it in a subsequent task.
• Task variables: Set implicitly by executing specific tasks to store the output of the task. For example, theCall REST Endpoint task sets theresponseBody variable to store the response body of the REST endpoint. Task variables are also known asauto-generated variables. Auto-generated variables have a special naming convention of using backticks around the variable name.

Integration variables

Integration variables, which include input and output variables, are similar to variables used in a programming language. Data in the variables can be read and written throughout the execution of the integration.

Integration variables can be used in the following ways:

• Taken in as inputs to the integration, also known asinput variables.
• Returned as outputs of the integration, also known asoutput variables.
• Used to hold temporary state during the execution of an integration.

Task variables are pre-defined auto-generated variables of atask. If a task has an output, all such outputs are available in a task variable. You cannot delete or edit a task variable. Task variables are also known asauto-generated variables.

The unique name of a task variable follows a special naming convention: it uses backticks around the variable name and includes the Task ID. The format is`<Task ID>_<Variable Name>`.

For example, theCall REST Endpoint task has an output for the response body. If this task has an ID ofTask_5, the unique task variable name for the response body is`Task_5_responseBody`.

In theVariables pane, task variables might be listed by a common output name, for example,responseBody, without the Task ID or backticks. To see the full, unique variable name required for reference, click on the variable in the pane and view its details in the right-hand panel.

Config variables

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

Config variables enable you to externalize configuration for integration. With config variables, you can configure aspects of your integration such as connector details, authentication details, or URL endpoints that are based on the development environment, such as QA, staging, or production. You don't need to update your integration manually before you upload the integration to a new environment. Application Integration lets you enter values for the config variables when you publish the integration.

Toview and edit the config variables defined in your integration, click the variable_addIntegration config variable in theVariables pane. To learn how to create config variables and use them, see the tutorialBuild CICD for your integration.

System variables

System variables are automatically generated when you create an integration. You can use these variables in your integration tasks and tohandle errors. The integration contains the following system generated variables:

• ErrorInfo: When your execution fails, you can access the error details with theErrorInfo variable:

  {  "ErrorInfo": {  "message": String,  "code": Number  }}

  You can access the error messages by creating anintegration variable namedErrorMessage. However, we recommend you to use the system-generatedErrorInfo.message variable to access error messages.

• ExecutionMode: Themode of execution based on the trigger. Valid values areSYNC andASYNC.
• ExecutionId: The execution ID of the integration.
• IntegrationName: The name of the integration.
• Region: The region of the integration.
• ProjectId: The project ID that contains the integration.

View variables

You can use theVariables pane to create, edit, view, duplicate, and delete variables in your integration. TheVariables pane also displays a count of the total variable references within the integration.

To view theVariables pane, click thelast_page, the Toggle panel, in the designer navigation bar.

The following image shows a sample layout of theVariables pane:

View and edit config variables

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

To view the config variables defined in your integration, click the variable_addIntegration config variable in theVariables pane. This brings up theConfig variables pane displaying all the config variables defined in your integration. You can simply click theValue field to edit the value of the config variable.

The following image shows a sample layout of theConfig variables pane:

Create a variable

To create a variable, perform the following steps:

1. In the integration editor navigation bar, click thelast_page, the Toggle panel, to bring up theVariables pane.
2. Click+Create.
3. Do the following in theCreate Variable pane:
   1. Name: Enter the name of the variable.
   2. Variable Type: Choose the type of the variable.

   Data type	Description
   None	A local variable in an integration.
   Config variable for Integration	Aconfig variable in an integration.
   Input to Integration	During execution the variable will be provided as an input to the executed trigger.
   Output from Integration	Variable's final value at the end of execution should be output to the integration's caller.
   Input and Output of Integration	At execution the variable will be provided as an input to the executed trigger and its final value will be output to the integration's caller.

   3. Data Type: Choose the data type of the variable. You can identify the data type of a variable by using the icon next to the variable name.

      Data type	Example
      String	Alex
      Integer	30
      Double	30.5
      Boolean	true
      JSON	{ "employee":{"name":"Alex", "age":30, "city":"Mountain View"} }
      String array	Alex, Kai, Raha
      Integer array	30, 25, 22
      Double array	30.5, 25.34, 22.134
      Boolean array	true, false, false

      For information about the supported data types, seeSupported data types.

   4. Default Value: Enter the default value for the variable. This is an optional field.
   5. Schema: Select the JSON schema for the variable.
      • Infer from a sample JSON payload: Generates a JSON schema from a sample JSON payload. The sample payload is discarded after the schema is generated. Only the generated schema will be saved.
      • Enter a JSON schema: Manually enter an entire JSON schema.
      • Infer from the default value: Generates a JSON schema using the provided default value.
      • None: No JSON schema.
      Note: This field is displayed only forJSON data type variables.
   6. Mask the variable in logs (preview): Select this option to enable masking for the variable in the integration execution logs. To enable masking for the variable, you must enable masking variables for your integration and region. For information about how to enable masking for the integration and the region, seeEdit an integration andEdit regions.

      For information about masking, seeMask sensitive data in logs.

4. ClickCreate.

How variables work in integrations

During the execution of an integration, run-time data is passed in as variables that are declared for the integration or task. Once execution begins, input data is converted into an in-memory object called anEvent.

After the Event object is created, an in-memory graph of tasks is built by using the integration definition. Incoming variable values are passed to tasks based on your configuration. As the integration executes, the tasks read and write data back into the Event object,to be used by subsequent tasks or to form the output data of the integration.

The following table summarizes the different types of variables and their behavior:

Variable references

The tasks, triggers, and edges in an integration read and write to variables by usingvariable references. A variable reference takes the form$paramKey$ whereparamKey is the name of the variable.

For example:

• An edge conditional could look like this:

  $isNameUnique$ = true AND $numAccounts$ >= 1

  In this example,isNameUnique is a variable of data typeboolean andnumAccounts is a parameter of data typeinteger.

• You can create an email notification for a new user registration within an Application Integration workflow. Suppose you have two variables:
  • $userName$: Holds the new user's name (e.g., "Alex").
  • $orderID$: Holds a unique order identifier (e.g., "ORD-12345").

  The template for the email body could be:

  Hello $userName$, thank you for your order! Your order ID is $orderID$.

  When this message is sent, the system replaces the variable references with their corresponding values. The final message will be:

  Hello Alex, thank you for your order! Your order ID is ORD-12345.

You can use variable references in the following places:

• Task parameters
• Trigger parameters
• Edge conditions

When you refer to an auto-generated or task variable, you must use its full, unique name, which includes backticks and the Task ID, within the dollar sign delimiters. For example, to refer to theresponseBody output of aCall REST Endpoint task with IDTask_5, you must use$`Task_5_responseBody`$.

Quotas and limits

For information about quotas and limits, seeQuotas and limits.

What's next

• Learn how tobuild CI/CD for your integration.
• Learn how tomask sensitive data in logs.
• Add and configure aData Mapping task