# For Each {% hint style="info" %} See the changelog of this Action type [here](https://app.gitbook.com/s/IXj83By4f20oCrZZ0gyP/for-each). {% endhint %} ## Overview The **For Each** action divides a list field with different entries into different output events, along with the position they occupy in the list (being the first position `0`). For example, an input list containing `[a,b,c]` will generate three outputs, with these fields added to the event: * `elementValueOutField: a`; `elementIndexOutField: 0` * `elementValueOutField: b`; `elementIndexOutField: 1` * `elementValueOutField: c`; `elementIndexOutField: 2`

{% hint style="warning" %} In order to configure this action, you must first link it to a Listener. Go to [Building a Pipeline ](https://docs.onum.com/the-workspace/pipelines/building-a-pipeline)to learn how this works. {% endhint %} ## Ports These are the input and output ports of this Action:

Input ports

* **Default port** - All the events to be processed by this Action enter through this port.

Output ports

* **Default port** - Events are sent through this port if no error occurs while processing them. * **Error port** - Events are sent through this port if an error occurs while processing them.

## Configuration {% stepper %} {% step %} Find **For Each** in the **Actions** tab (under the **Advanced** group) and drag it onto the canvas. {% endstep %} {% step %} To open the configuration, click the Action in the canvas and select **Configuration**. {% endstep %} {% step %} Enter the required parameters:

Parameter	Description
Input*	Choose the field that contains the list you want to divide.
Output field*	Name of the new field where each iterated element will be stored. This will be the same type as the input field list.
Index field*	Name of the new field that will show the position of each element in the list.

{% endstep %} {% step %} Click **Save** to complete the process. {% endstep %} {% endstepper %} ## Example Imagine you receive a list-type field containing a string of five IPs: `127.0.0.1`,`127.0.0.2`,`127.0.0.3`,`127.0.0.4`,`192.168.0.1` {% stepper %} {% step %} Add the **For Each** Action to your Pipeline and link it to your required Data sink. {% endstep %} {% step %} Now, double-click the **For Each** Action to configure it. You need to set the following config:

Operation	Parameters
Input	In this case, we choose the field `ipsList` that contains our IP list.
Output field	We're naming the new field `ipValue`.
Index field	We're naming the new field `ipIndex`.

{% endstep %} {% step %} Click **Save** to apply the configuration. {% endstep %} {% step %} Now link the *Default* output port of the Action to the input port of your Data sink. {% endstep %} {% step %} Finally, click **Publish** and choose in which clusters you want to publish the Pipeline. {% endstep %} {% step %} Click **Test pipeline** at the top of the area and choose a specific number of events to test if your data is transformed properly. Click **Debug** to proceed. {% endstep %} {% endstepper %} The Action will create a separate event for each element of the string, each event containing two fields (value and index).