Junctions help you to model the layout and logic of your flow. Multiple transitions can point to the same junction, or a junction can be the starting point of multiple transitions.
Junctions themselves don't do anything. They don't execute scripts, nor do they display an output. They just offer an easy way to model your flow. By following the rules below you will learn how to get the most out of junctions.
Here we will describe some common cases where junctions are used in flows.
If you want to branch immediately after a flow trigger you can do this using a junction. This might be necessary if you have different responses for the channels your bot uses, or for different customer types, or for specialized cases of the user input. In this exercise we show you how to branch at the beginning of a flow.
When you add a branch at the beginning of a flow it looks something like this:
In this example the transitions following the junction represent special cases of the main case that leads to the junction.
Keep in mind that you can branch directly from an output node without using a junction. Adding junctions in such cases can make your flow harder to manage and also introduce unwanted errors. When adding a simple branch, don't use a junction.
Have a look at the transitions page for another example of correct branching from an output node.
You can add logical branches to your flows using junction nodes. These branches (transitions) can be assigned a language or script condition, and can also be set to unconditional. Here we describe some basic guidelines to help you use junctions in the best way possible.
Transitions connecting an output to a junction should include a Match. If a transition has a Match it could use a TLML Syntax condition.
When multiple transitions leave a junction, use the last transition as a fallback, and make sure it does not have a 'User Intent' in place. In this example, the first three transitions have a Match, and the fourth one, which serves as the fallback transition, does not.