I’ve got a workflow that needs to act on every item in a list, and I want to handle that the right way rather than hacking around it. What’s the recommended approach to looping over items in 3B? I’m curious how each item gets processed and whether there’s anything to watch out for with larger lists. Examples would be appreciated.
Good news: there’s nothing to hack around, and no loop construct to place. A step in 3B is code, and code already knows how to iterate, so you describe what should happen to every item and 3B writes the loop for you.
Something like this is enough:
Pull every open ticket from the board, and for each one, look up the assignee in Okta and add their manager’s name to the ticket.
Where it pays to be specific is what happens when one item misbehaves. “If a lookup fails, skip that ticket and carry on, then tell me at the end which ones were skipped”, that sort of thing.
For bigger lists, mention the volume: “there’ll be a few thousand of these.” That tells 3B what a sensible build looks like, whether items get batched, whether results get written to storage as it goes rather than held in memory, and whether the work is better split across several runs.
Then run it and read the step’s output to confirm it did what you wanted it to.