Flow nodes and elements
Overview
Teneo Studio allows to add a variety of Flow nodes and elements in a Flow to design the desired dialogue; this page provides an overview of the various elements which the user might encounter in the Flow window and offers links to more information when relevant.
| Flow node / element | VisualizationTeneo Studio Desktop | Comment | Learn more |
|---|---|---|---|
| User Intent trigger/transition | The User Intent contains the examples of intent which should trigger the current Flow/transition, it is also here that Match(es) and After Matches are defined | User Intent | |
| Prompt trigger | Prompts allow to add Groovy expressions which should be matched in order for the Flow to be triggered | Prompt trigger | |
| Match Class | Allows to define a Machine Learning Class which must be matched in order to trigger the Flow or Transition. | Matches | |
| Match TLML Syntax | Allows to define a syntax based on the Teneo Linguistic Modeling Language (TLML). | Matches | |
| Match Entity | Match an Entity in order to trigger the Flow. | Matches | |
| Match Language Object | Match a Language Object in order to trigger the Flow. | Matches | |
| Match Script | Enter the Flow by writing a script which must evaluate to true to enter the Flow. | Matches | |
| Match Scripted Context | Context Match requirement of type Scripted Context; select a Scripted Context and the wanted context state(s) which should be fulfilled for the Match requirement to match. | Matches | |
| Match Flow Variable | Context Match requirement of type Flow Variable; select a Flow Variable and write an evaluation script which must evaluate to true for the Match requirement to match. | Matches | |
| Match Global Variable | Context Match requirement of type Global Variable; select a Global Variable and write an evaluation script which must evaluate to true for the Match requirement to match. | Matches | |
| Integration node | Allows to call an integration from within a Flow when the Integration has previously been configured in the Integration manager | Integration node | |
| Flow Link | Allows to create links from one Flow to another (and back again in the case of Sub-flows) | Flow Link | |
| Script | Allows to add programmatic functionalities (Groovy) to a Flow; the code piece has access to Global Variables and Flow Variables of the current Flow | Script node | |
| Give Response | The "Give Response" label indicates that the Bot will give all pending Outputs as a response (up till that point in the Flow) and wait for a new user input | Transitions | |
| Junction | Junctions allows to split the flow of the dialogue and facilitates the modeling of the Flow logic as multiple transitions can point to/from the same Junction node | ||
| After Match Entity | Allows to extract the value of an Entity variable. After Matches are defined in the Intent Trigger/transition | After Matches | |
| After Match Language Object | Allows to extract the value of a Language Object variable. After Matches are defined in the Intent Trigger/transition | After Matches | |
| After Match Script | Allows to, for example, store matched words as a variable or execute a script. After Matches are defined in the Intent Trigger/transition | After Matches | |
| After Match Listener | Allows to execute a script for each input which matches a syntax rule. After Matches are defined in the Intent Trigger/transition | After Matches | |
| Output | Output nodes contain the answer(s) of the conversational AI application | Bot Output | |
| Raise | The "raise" label indicates when a Flow raise event happens in the Flow dialogue | ||
| Drop | The "drop" label indicates when a Flow drop event happens in the Flow dialogue | ||
| TODO | The "TODO" labels are shown in the Flow editor and on Flow nodes when an implementation of the node is still pending | TODO label | |
| Plus icon | Plus icons are displayed throughout the Flow editor indication where more nodes and elements can be added; when clicked, the available options are displayed in a menu for the user to choose from | Edit Flow |
