Global Variables

When you create or see a global variable in the flow, it is actually a global variable condition, not a global variable object. That is, it is part of the dependency string (for example, v(GVAR1) = 42), and processing will proceed when the variable is set with that value. These global variables do not necessarily exist on the server before being set to satisfy the condition. Creating one in the flow automatically meets its requirement and triggers its dependent jobs.

Notes:

Global variables you add to the flow do not have to be defined in the CA Workload Automation AE database to be used in the flow.
You cannot assign a value to a global variable that you add to the flow; however, you can define the properties of the dependency link that connects the global variable to another object. The dependency link defines the value that the global variable must be equal to, not equal to, less than, or greater than for the dependency condition to be met.
The global variable you add to the flow is included in the dependency statement of the job that depends on it.
You can set a global variable value in a sendevent command. CA Workload Automation AE keeps it in memory so it can be used.

More information:

Add a Global Variable