Control connector
Control
Control connector supports two different actions called Condition and Iteration.
Actions for control connector
Action |
Description |
Condition |
Set up a condition in your workflow form based on data that will define the subsequent action based on whether the condition is true or false. |
Iteration |
Iterations can be used when you want to take an action for every row in a form table of a process or case system. |
Adding conditions
You may not always want a trigger to lead to an action. When you apply a YES or NO condition to step data, you can define specific actions in your workflow based on whether or not the data matches the condition. You can create multiple conditions and decide if they should match all or any one condition(s).
In the integration, add any actions, including additional conditions to specify what happens if the condition is true on the left side and what happens if the condition is false on the right side.
Adding iterations
Iterations can be used when you want to perform a unique action for every row in a process or case system's form table. For instance, you may want to update a dataset record based on inputs added to a process form.
Start by selecting the table in your process or case system's form. Then, select the action you want to take for each row.
Iteration action only works with the first 100 records of data. It ignores data after the 100th record.
Using the control connector
After you've finished configuring the integration, turn on the toggle button in the upper-right corner of the editor to activate it. When the trigger is initiated, the subsequent actions are carried out in the order specified by you.
To ensure your integrations are properly configured and tested, review our best practices guide for tips on building robust and maintainable solutions.