Designer 10.7 | webMethods Service Development Help | Mapping Data in Flow Services | About Assigning Values to Pipeline Variables | Assigning a Value to a Pipeline Variable
 
Assigning a Value to a Pipeline Variable
You can assign values to variables that are in Service In or Pipeline Out when the variable is not linked or when the variable is only implicitly linked to another value in the pipeline.
You cannot assign values to:
*Variables that are explicitly linked to another value in the pipeline
*Variables that have been dropped from the pipeline
*Object variables constrained as a byte [ ]
*Unconstrained Objects (Objects of unknown type)
*An XML document variable or an XML document list variable
*A variable that has a fixed null or default value assigned to it. Designer uses the symbol next to the variable icon to indicate that the variable has a fixed value that you cannot override by linking it to another variable.
*To assign a value to a pipeline variable
1. In the flow service editor, select the INVOKE or MAP step containing the variable you want to alter.
2. In Pipeline view, select the variable to which you want to assign a value. The variable must be in either Service In or Pipeline Out.
3. Click on the Pipeline view toolbar.
Designer displays the Enter Input for dialog box.
4. Assign values using the Enter Input for dialog box. For specific information for how to assign a value based on a variable’s data type, see one of the following:
For this type of variable...
See...
String
String List
String Table
Document
Document Reference
Document List
Document Reference List
Object
Object List
Notes:
*The Include empty values for String Type check box is disabled when assigning values to pipeline variables of type String, String List, String Table, Document, Object, and Object List. It is available only when assigning values to Document List variables. For more information, see Specifying Values for a Document List Variable.
*The check boxes next to each element in the tree are disabled when assigning values to pipeline variables of type String, String List, String Table, Document, Object, and Object List. The check box is only enabled for top-level Document variables within a Document List and is used along with the Include empty values for String Type check box. For more information, see Specifying Values for a Document List Variable.
*The Perform pipeline variable substitution check box indicates whether you want Integration Server to perform pipeline variable substitution at run time. To use a variable when assigning a String value, you type the name of the pipeline variable enclosed in % symbols (for example, %Phone%). If you specify a pipeline variable enclosed in % symbols for a String value, you must select the Perform pipeline variable substitution check box for the variable substitution to occur.
*The Perform global variable substitution check box indicates whether you want Integration Server to perform global variable substitution at run time. To use a global variable when assigning a String value, you type the name of the global variable enclosed in % symbols (for example, %myFTPUsername%). If you specify a global variable enclosed in % symbols for a String value, you must select the Perform global variable substitution check box for the variable substitution to occur.
*If a pipeline variable and global variable have the same name and you select both Perform global variable substitution and Perform pipeline variable substitution, Integration Server uses the value of the pipeline variable.
*The Overwrite pipeline value check box indicates whether you want Integration Server to use the value you specify even when the variable has a pipeline value at run time.
*Select the check box to have Integration Server always use the value you specify.
*Clear the check box if you want Integration Server to use the value you specify only if the variable does not contain a value at run time.