...
The XML List Processor allows you to select items from a payload to be processed individually, enabling you to build a dynamic list for use in a response. It It can be used by chaining it to another tool (for example, a responder or REST client) or as a stand-alone tool. By iterating over each item in the payload, the tool enables the aggregation of dynamic, item-specific data, such as data source lookups or calculations, within a single operation.
...
- Handle a dynamic list of items in a single incoming request.
- Process each item independently (for example, fetch additional data, perform validation).
- Aggregate individualized results in a single, structured response payload.
See Handling Lists with a Dynamic Number of Items for an example of using a list processor like this one in a common workflow.
Configuring the XML List Processor Tool
...
- 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 (for example, 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: Tells Virtualize to store the value in a writable data source column. 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 you to store values in all columns with names that contain 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 you to save the value in the specified variable so it can be reused across the current Responder or Action suite. The The variable must already be added to the current suite as described in Defining Variables in Virtualize. Any values set in this manner will override any local variable values specified in the suite properties panel.
...