An outcome lets your user running the app move from one map element in the flow to another, or from one map element into another flow. Outcomes can be combined with business rules to determine the path of execution based on pre-determined logic.
You can customize the outcome through the configuration panel, which opens on the right when you create an outcome, or when you double-click an existing outcome.
The value you enter in the Name column is used by the Flow API; the Label is what your end-user sees.
Some elements (like Load or Save, that handle backend database actions and are not visible in the front-end), do not have any buttons that are visible in the app, but must still be connected using outcomes. You do not see a Label field in the configuration panel, for these instances.
Outcomes can be combined with business rules/comparison to determine the path of execution based on pre-determined logic. All map elements support outcomes. Decisions, messages, and pages support outcomes with rules/comparison.
Every flow begins with the Start element, which is fixed on the canvas. The first outcome in the flow is the outcome from the Start element, which connects an arrow from Start to the first element you place on the canvas. The first outcome is typically called ‘Go’, but you can call it anything you like.
All your flows will have at least one outcome, connecting the Start element to another element in the canvas.
You can not have an outcome connecting any element back to the Start element.
This is how the outcomes are rendered in the app:
Not all elements in the canvas need to be connected with outcomes. For example, you can have a flow like this, and add a navigation:
Looking for reference documentation on outcomes? We have you covered. Click here!