Build Once, Execute Multiple Times with Loops in Kiosk Studio in Zoho CRM

Build Once, Execute Multiple Times with Loops in Kiosk Studio in Zoho CRM

Hello Everyone,

Introducing Loop Functionality in Kiosk Studio.

If you've ever built a Kiosk that needed to perform the same action multiple times like updating a list of contacts, scheduling calls for a batch of leads, or processing multiple products in a deal, you've probably hit a point where reconfiguring the same steps over and over becomes the bottleneck. Until now, Kiosk actions could only execute one record at a time, forcing you to restructure flows or repeat configurations to achieve the same outcome.

Loop functionality changes this. You configure the logic once, define when the loop should end, and Kiosk Studio handles the repetition automatically.

Let's take a look at how loop functionality enhances Kiosk Studio's capabilities.

What You Can Do With Loops

  1. Process multiple records automatically in a single flow
  2. Execute the same actions like updates, approvals, emails, across records
  3. Repeat the same set of steps multiple times without rebuilding the flow
  4. Loops can be configured using records, fixed iteration counts, or values from previous steps.
  5. Give users manual control over when a loop should stop.
Overall, this helps you build kiosks that are simpler, faster, and easier to maintain.

Configuring Loop Execution

Loops are created by establishing a loop connection between two Kiosk elements where you define the conditions under which the loop should stop.


Once the connection is created, you can define when the loop should end. Loop functionality gives you control over when a screen, action, or set of steps should repeat and when the loop should stop.

You can control loop execution in the following ways:
  1. Based on GetRecords - The loop runs once for each selected record from a GetRecords element. When all selected records are processed, the loop stops automatically.
  2. Based on a maximum iteration - Admins can define how many times a loop should run. The iteration count can be determined in two ways:
    1. Static value - Set a fixed number of iterations up to 100.
    2. Based on fields - Use values from previous screens or actions to decide the number of iterations.
  3. Ending a Loop Manually - Admins can add an End Manually button to a kiosk screen. When users click this button, the loop stops and the kiosk proceeds to the next step.
Notes
Note: This option is available only when screens are configured within the loop.

Here's how a configured loop looks in the Kiosk builder:


Use Case : Scheduling calls across multiple leads

A sales manager fetches a list of leads using GetRecords. Each lead needs a follow-up call scheduled. With a loop, the configured action is executed for every lead automatically and the manager doesn't have to re-trigger the flow for each one.


Nested Loops

Kiosk Studio also supports loops within loops, up to two levels of nesting. This is useful when each record in your outer loop contains its own set of records to process.

Use Case : Processing orders and their items

Imagine a kiosk used to process customer orders. Each order has multiple items. The first loop goes through each order. The second loop goes through each item inside that order.

How it works:
  1. The outer loop retrieves each customer order one by one.
  2. For each order, the inner loop runs through every item in that order, updating details and marking each item as processed.
  3. Once all items in the order are done, the inner loop ends and the outer loop moves to the next order.
  4. When all orders are processed, the outer loop ends and the Kiosk continues to the next step.


Things to Know

  1. Fields configured inside a loop are only accessible within that loop; they cannot be used in steps outside it.
  2. Records fetched by a GetRecords element before the loop can be used inside the loop.
  3. Records retrieved within the loop stay scoped to that loop only.
  4. Loop executions are capped at 100 iterations, including nested loops.
  5. A loop cannot be deleted until all components configured inside it have been removed first.
Info
Availability & Release Plan :
  1. This feature is available on the Standard edition and above.
  2. It is currently live for users of all DCS. 

If you have questions about specific use cases or run into anything unexpected, drop a comment below. We'd love to hear how you're using loops in your flows.

Thanks & Regards,
Serena Woolridge