Routing creates a section with configurable buttons that support skip logic. For example, if you have a review and decision step, you might configure one routing button to move the process to the next step on Approve and stop the workflow on Decline.
Not sure how to configure a form? Learn more…
You can only add multiple routing sections to a step, however, if you add more than one set, you need to add conditions to each section to define when to show which routing options.
Imagine you’ve received personal information from a new supplier via a form you sent out. After reviewing the information, you can quickly decide what to do next:
By using looping, branching, and customizing workflows, you can tailor the process to fit your specific requirements. Plus, you can connect routing with conditions, ensuring the field is shown only when it meets the specified criteria.
Adding routing to your form creates a set of decision buttons. The buttons can trigger a selected action so that the selected decision-maker can do the following:
Routing buttons can be a part of a larger form or a stand-alone form field.
You can show the routing buttons based on specific conditions, for example, when particular data is missing, and you need to review and decide on the next action.
Yes! There is one caveat - you need to set conditions so that the sets show correctly and don’t break the workflow. If you set conditions on each set, one set will show at a time or to a specific group of users.
You can use the Routing form field as an alternative to the Decision step.
You can add extra information to help users provide the right input. The information will show when users hover over the info icon next to the field name.
You can update field data and complete a form using the API. To see examples of the JSON body you need for each form field, see Completing steps.
The step returns the following data :
Note that when an instance is stopped using routing, the complete step endpoint response will contain aborted_time
and not completed_time
.