Might it be a better idea in that case to create 1 object for the first person, then show the form and let the user fill in some details. After he is done and clicks on save, you get the next person from the list and create an object and show the new form and so on?
What if you create a page that shows a list of people, and then you setup a dataview to listen to this grid. Then when a user selects a record in the list, the form that you need to have them fill out will appear on the right side of the screen. The user can fill in the details and then click the next record in the list.
Here is an example:
The list can be any list, I just used a datagrid for this example.
Hope this helps!
You could also try adding a process record (could even be non-persistant)
So indeed (as suggested by others) you do not loop through the list, but based on your first record you create the process record, link the people record and create the record that you want the user to fill in. In the form (sample below) you fill in the fields that you want.
The Save button can trigger a microflow that
You could do without the process record, Step 3 would close the form and opens the form with the first record that is not 'done'. However Close/Open form might disturb the user more than refreshing the process record. And on the process record you could add a counter (record 10 of 20) that keeps the user informed about the progress.