Transitions are the connectors that link flow nodes together. They tell Teneo where to go next when processing a flow.


New input or not?

Transitions can be set to wait for a new input from a user. The flow processing then halts and the output is presented to the user. These transitions are displayed as solid lines in the flow graph. Transitions that don't wait for a new input are displayed as dotted lines. You specify whether a transition should wait for a new input or not with a toggle in the 'Examples' panel.


Transitions can be conditional or unconditional. If a transition is conditional, Teneo will evaluate if a condition is met before it traverses the transition. You specify conditionality with a toggle in the 'Examples' panel. Keep in mind that when writing a transition condition any Groovy code needs to be embraced by curly brackets, e.g. { userAge > 18 }.


If multiple transitions have the same node as their starting point, you specify the order in which they (or rather: their conditions) should be tested. The order is displayed in the flow graph, as a number on the transition. You change the order in the 'Examples' panel.

Transition ordering


You can specify whether a transition should be considered just once per session, or always. This is useful when you want the behaviour of a flow (or a point of flow) to be different depending on how many times the user visits it.

Was this page helpful?