Using Global Variables
This section explains the usage of global variables to pass data across components.
In a simple test flow, add a new person in Oracle Utilities Customer Care and Billing and add a customer contact for that person. The C1-CustomerContactAdd component is a dependent component and during runtime needs the ID of the person, created using C1-PersonAdd component within the same flow.
To add component references to a dependent component (C1-CustomerContactAdd):
- In the Edit Test Data GUI of the C1-CustomerContactAdd component, find the component line that requires the personId as input.
- Against the personId row, click the downward arrow to open the Test Data drop-down list. All variables exposed by the preceding components are diaplayed in the Global Variables section.
In this case, personId exposed by the C1- PersonAdd component.
- Select the personId variable from the drop down list and set it as test data against this element.
Figure 8-23 Selecting a global variable for test data

Each of the base components expose one or more global variables that hold the output of the component during execution. These global variables can be used to set the output of one component as the input of another component.
Additionally, global variables are also created to hold output of functions used in pre-validations or post-validations sections. These global variables are defined in the Output Variable field and are to be set against only functions that return an output value. These function based global variables are automatically pre-fixed with “fVar_” and these can be used as input in the test data of subsequent steps in the flow.
All the global variables are automatically suffixed with their occurrence number. If the C1-PersonAdd component is used twice in the flow, there will be two variables (gVarPersonId1, gVarPersonId2) one for each occurrence of the component, suffixed with it's occurrence number. Custom global variables can be defined and exposed by the components through the Pre-Validations and Post Validations sections. These variables are automatically prefixed with “fvar_”, to differentiate them from the component's base global variables. These variables are also suffixed with their occurrence number in the flow, similar to the global variables specified in the component definition.