To provide an example use for Repeatable Groups we have a form for registering a team for the local pub quiz. We have a Team Name and Contact email, then a Repeatable Group to enter each member of the team with a First Name and a Last Name.

The form handler pipeline iterates through the groups to combine First Name and Last Name and build them into a comma separated list.

Feel free to submit the form as often as you want. The form is saved to your session, but the data is not saved or logged anywhere else. All it does is validate the inputs and return a success or error message. The session data facilitates persistence of some inputs, so you only need to enter your name and email once. You can also see your most recent form submission presented using Form Reform Display.

How this form works

The blocks used are the same as those used in any form with Form Reform. The difference is that a container is added to provide 3 columns with text inputs for first_name and last_name, then a Repeatable Group block is added to the third column. For the front end of the form, its a simple as that!

The Repeatable Group block automatically detects the row of the 3 column container which contains the form elements and provides Add, Delete and Sort controls to manage replication of the group.

Our pipeline handling the repeatable group

The pipeline shown below is a front-end non-editable version of the pipeline used to handle the above form. You can expand any stages to view the details. As usual, the submitted form is only saved to your session.

The new part of our pipeline is simply adding an extra {{place_holder}} to the Message to provide a cleaner format of our team member names.

The second Condition If section towards the end of our pipeline is to add a display of any UTM tags, as described in Example - Tracking UTM tags. If you are not using Form Reform UTM, you can ignore that part of the pipeline.

Specific handling for each item in a group

Our second submit pipeline - Submit 2 - illustrates iterating through each repetition of a group of inputs. The new part of our pipeline is between Iterate Repeatable Group and Iterate Repeatable Group End. This pair of handlers provides a way of acting on each repetition of a group in turn. All we are dosing here is aggregating names in a less elegant way than the pipeline above.

In a real world application, perhaps this could be providing handling specific to each group member such as a personalized email.

Once again the second Condition If section towards the end of our pipeline is to add a display of any UTM tags, as described in Example - Tracking UTM tags. If you are not using Form Reform UTM, you can ignore that part of the pipeline.

If you have already tried the Submit button above, refresh the page , make sure you have completed the form, and click the green Submit 2 button immediately below to the right and see the same form data used in Iterate Repeatable Group.