Using the No Data Result PathLast Updated: 08/12/2016 Introduced in Verision: 2.0
If a flow step requires input but the input is not provided, the flow will stop running. For example, if a step requires input data from a user-completed form and the user submits the form with no data in the required fields, the flow will not continue. Adding a No Data Result path solves this problem by allowing a flow to proceed, even when a flow step requiring input does not receive it.
Add a No Data Result path in the Flow Designer by selecting the Show No Data as Path checkbox in the Properties panel, under the Outcomes section.
Our example flow will capitalize text which we will supply via a form.
If the form is submitted without text, we will be presented with another form advising us to add text for capitalization. Behind the scenes, our example flow has continued to the End Step.
Begin our example with the bulk of our flow already in place. Our first step is the form into which we’ll enter text for capitalization. It has one path Capitalized that flows to our capitalization component Capitalize 1. This step also has one path Done which leads to the End Step. Another form End Form 1 has also been previously created for this example.
In the event that our form is submitted without text, we want Capitalize 1 to detect this and show us the second form. Select Capitalize 1 and, in the Properties panel, under the Outcomes section, select the Show No Data as Path checkbox. This creates a No Data Result anchor which we can use in the next part of our example.
Save the flow and run it in the Debugger.
Note that in Decisions version 3.5 and above, you’ll need to click on Test Flow to access the Debugger.
When we run our flow in the debugger, we’re presented with our initial form. If we choose to submit it without entering any information
We’re directed to our second form, telling us that we need to provide text to capitalize.
Click the Diagram tab to see the flow’s progress. Even though we entered nothing in the field on the form, the flow has continued to run, reaching the End Step, directed in part by the No Data Result path.
- Checking if an Object is Null
- Using the Mapping Editor
- Creating Your First Form Flow
- Building a Converter Flow
- Using Placeholder Components to Sketch Out Flow Structure
- Creating a Form Validation Rule
- Creating Your First Form
- Catching All Unhandled Exceptions
- Using Custom Data as Flow Input
- Using the Flow Debugger