Navigate Loops and Callable Flows
The information here assumes you finished the flow authoring course in Trimble Learn and that you have access to the workspace.
The document is not a how-to guide, but more of a way of helping you continue your task if there are issues.
Navigate Loops and Callable Flows
Get to Your Callable Flow
You can get to your callable flow in two ways:
Know the name of your flow and find it in the standard list of flows.
Open the parent flow and view the flow in the Call a Flow step.
Callable flows are shown in the standard list of flows, so you will just need to know the name of your callable flow to find it here. Additionally, you can get to your callable flow from the parent flow that calls it. Open the Call a Flow step and choose the View Flow link under the name of your callable flow. This will open the callable flow in a new window.
Schema for a Callable Flow
Callable flows can define an input schema which will then be shown on the Call a Flow step in a parent flow. Define this schema by clicking on the trigger in the callable flow and selecting Custom Schema. The input schema will need to follow the JSON Schema v7.0 format.
Data Returned from a Stop Step in a Callable Flow
A callable flow has no output unless you define it using a Stop step. Include a Stop step for every exit scenario in your callable flow so the output to the parent flow is consistent. The Result Status, Result Message, and Result Details will all flow back to the parent flow.
A Stop step configured like this:
will look like this in the parent flow:
If a Stop step has the Result Status set to Failure, then the “__Status” property will be 400.
Data in a For Each Loop
A For Each in a List step expects a collection as the input. The steps nested under the For Each in a List step will be executed against each object in the collection. These iterations will run in parallel to each other.
Following is an example of a For Each in a List step that looks at a list of Vista Jobs and returns success if the job is open and failure if the job is closed.
This produces an output that looks like: