...

• Custom column name: Specifies the name of the data source column in which to store the value. Values are stored in an internal data source unless you specify otherwise (e.g., if you select Writable data source column or Variable). This is the name you will use to reference the value in other places. For example, if it is stored in a data source column named My Value, you would choose My Value as the parameterized value. You could also reference it as ${My Value} in literal or multiple response views.

  
  
  
  

• Writable data source column: Enables storing the value in a writable data source column (see Configuring a Writable Data Source for details). This allows you to store an array of values. Other tools can then iterate over the stored values.

• Write to all columns that match: Enables storing the value in all columns whose name contains the specified string. When extracting multiple values from a message, each value will be written across all the columns that match. In contrast, if you pick a single writable data source column (the above option), then the values will be written down the column across multiple rows.

• Variable: Enables saving the value in the specified variable so that it can be reused across the current Responder, Action, or test suite. The variable must already be added to the current suite as described in Defining Variables in SOAtest or Defining Variables in Virtualize. Any values set in this manner will override any local variable values specified in the Responder, Action, or test suite properties panel.

...

You can configure the Console view (Window> Show View> Console) to display the data bank variables used during test execution. For details, see Monitoring Variable Usage.

Parameterizing XPaths

You can parameterize XPaths to reference Responder suite or test variables, environment variables, and data source values. The syntax to reference variables  is ${myVariableName}. The syntax to reference XML Data Bank values and Data Source values is: ${myColumnName}.

...