# 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. 



#### __Teneo Studio Desktop__

| Flow node / element            | Visualization<br/>Teneo Studio Desktop                       | Comment                                                      | Learn more                                               |
| ------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | -------------------------------------------------------- |
| User Intent trigger/transition | ![Intent Trigger](media/flow-nodes-and-elements/desktop-intent-trigger.jpg) | _The User Intent contains the intents or examples of intents which should trigger the current Flow/transition, it is also here that Match(es) and After Matches are defined_ | [User Intent](user-guide/flow/user-intent)               |
| Prompt trigger                 | ![Prompt Trigger](media/flow-nodes-and-elements/desktop-prompt-trigger.jpg) | _Prompts allow to add Groovy expressions which should be matched in order for the Flow to be triggered_ | [Prompt trigger](user-guide/flow/prompt-trigger)         |
| Match Class                    | ![Class Match](media/flow-nodes-and-elements/desktop-class-mr.jpg) | _Allows to define a Machine Learning Class which must be matched in order to trigger the Flow or Transition._ | [Match requirements](user-guide/flow/match-requirements) |
| Match TLML Syntax              | ![Syntax Match](media/flow-nodes-and-elements/desktop-syntax-mr.jpg) | _Allows to define a syntax condition based on the Teneo Linguistic Modeling Language (TLML)._ | [Match requirements](user-guide/flow/match-requirements) |
| Match Entity                   | ![Entity Match](media/flow-nodes-and-elements/desktop-entity-mr.jpg) | _Match an Entity in order to trigger the Flow._              | [Match requirements](user-guide/flow/match-requirements) |
| Match Language Object          | ![Language Object Match](media/flow-nodes-and-elements/desktop-lob-mr.jpg) | _Match a Language Object in order to trigger the Flow._      | [Match requirements](user-guide/flow/match-requirements) |
| Match Script                   | ![Script Match](media/flow-nodes-and-elements/desktop-script-mr.jpg) | _Enter the Flow by writing a script which must evaluate to true to enter the Flow._ | [Match requirements](user-guide/flow/match-requirements) |
| Match Scripted Context         | ![Scripted Context Match](media/flow-nodes-and-elements/desktop-context-mr.jpg) | _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._ | [Match requirements](user-guide/flow/match-requirements) |
| Match Flow Variable            | ![Flow Variable Context Match](media/flow-nodes-and-elements/desktop-context-fv-mr.jpg) | _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._ | [Match requirements](user-guide/flow/match-requirements) |
| Match Global Variable          | ![Global Variable Context Match](media/flow-nodes-and-elements/desktop-gv-context-mr.jpg) | _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._ | [Match requirements](user-guide/flow/match-requirements) |
| Integration node               | ![](media/flow-nodes-and-elements/desktop-integration.jpg)   | _Allows to call an integration from within a Flow when the Integration has previously been configured in the Integration manager_ | [Integration node](user-guide/flow/integration-node)     |
| Flow Link                      | ![Flow Link](media/flow-nodes-and-elements/desktop-flow-link.jpg) | _Allows to create links from one Flow to another (and back again in the case of Sub-flows)_ | [Flow Link](user-guide/flow/flow-link)                   |
| Script                         | ![Script node](media/flow-nodes-and-elements/desktop-script-node.jpg) | _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](user-guide/flow/script-node)               |
| Give Response                  | ![Give Response](media/flow-nodes-and-elements/desktop-give-response.jpg) | _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](user-guide/flow/transition)                |
| Junction                       | ![Junction node](media/flow-nodes-and-elements/desktop-junction.jpg) | _Junctions allows to split the flow of the dialogue and facilitates the modelling of the Flow logic as multiple transitions can point to/from the same Junction node_ |                                                          |
| After Match Entity             | ![Entity After Match](media/flow-nodes-and-elements/desktop-entity-da.jpg) | _Allows to extract the value of an Entity variable. After Matchs are defined in the Intent Trigger/transition_ | [After Match actions](user-guide/flow/data-actions)      |
| After Match Language Object    | ![Language Object After Match](media/flow-nodes-and-elements/desktop-lob-da.jpg) | _Allows to extract the value of a Language Object variable. After Match actionss are defined in the Intent Trigger/transition_ | [After Match actionss](user-guide/flow/data-actions)     |
| After Match Script             | ![Script After Match](media/flow-nodes-and-elements/desktop-script-da.jpg) | _Allows to, for example, store matched words as a variable or execute a script. After Match actions are defined in the Intent Trigger/transition_ | [After Match actions](user-guide/flow/data-actions)      |
| After Match Listener           | ![Listener After Match](media/flow-nodes-and-elements/desktop-listener-da.jpg) | _Allows to execute a script for each input which matches a syntax rule. After Match actions are defined in the Intent Trigger/transition_ | [After Match actions](user-guide/flow/data-actions)      |
| Output                         | ![Output node](media/flow-nodes-and-elements/desktop-output.jpg) | _Output nodes contain the answer(s) of the conversational AI application_ | [Bot Output](user-guide/flow/bot-output)                 |
| Raise                          | ![Raise label](media/flow-nodes-and-elements/desktop-raise.jpg) | _The "raise" label indicates when a Flow raise event happens in the Flow dialogue_ |                                                          |
| Drop                           | ![Drop label](media/flow-nodes-and-elements/desktop-drop.jpg) | _The "drop" label indicates when a Flow drop event happens in the Flow dialogue_ |                                                          |
| TODO                           | ![TODO label](media/flow-nodes-and-elements/desktop-todo.jpg) | _The "TODO" labels are shown in the Flow editor and on Flow nodes when an implementation of the node is still pending_ | [TODO label](user-guide/flow/flow-basics?id=todo-label)  |
| Plus icon                      | ![Plus icon](media/flow-nodes-and-elements/desktop-plus-icon.jpg) | _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](user-guide/flow/flow-basics?id=edit)         |

#### __Teneo Studio Web__



| Flow node / element                    | Visualization<br/>Teneo Studio Web | Comment                                                      | Learn more |
| -------------------------------------- | ---------------------------------- | ------------------------------------------------------------ | ---------- |
| User Intent _(trigger/transition)_ | ![User Intent](media/flow-nodes-and-elements/web-user-intent.jpg) | _User Intent contains the intents or examples of intents which should trigger the current Flow or transition_ | [User Intent Trigger](user-guide/flow/user-intent) |
| Prompt _(trigger)_                    | ![Prompt Trigger](media/flow-nodes-and-elements/web-prompt.jpg) | _Prompts allow to add Groovy expressions which should be matched in order for the current Flow to be triggered_ | [Prompt Trigger](user-guide/flow/prompt-trigger) |
| Match Class            | ![Class Match](media/flow-nodes-and-elements/web-class-match.jpg) | _Allows to define a Machine Learning Class which must be matched in order to trigger the Flow or Transition_ | [Match requirements](user-guide/flow/match-requirements) |
| Match TLML Syntax | ![Syntax Match](media/flow-nodes-and-elements/web-syntax-match.jpg) | _Allows to define a syntax rule based on the Teneo Linguistic Modelling Language (TLML)_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Entity           | ![Entity Match](media/flow-nodes-and-elements/web-entity-match.jpg) | _Match an Entity in order to trigger the Flow_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Language Object  | ![Language Object Match](media/flow-nodes-and-elements/web-lob-match.jpg) | _Match a Language Object in order to trigger the Flow_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Script           | ![Script Match](media/flow-nodes-and-elements/web-script-match.jpg) | _Enter the Flow by writing a script which must evaluate to true to enter the Flow_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Scripted Context | ![Scripted Context Match](media/flow-nodes-and-elements/web-context-match.jpg) | _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_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Flow Variable    | ![Flow Variable Match](media/flow-nodes-and-elements/web-flow-var-match.jpg) | _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_ | [Match requirements](user-guide/flow/match-requirements) |
| Match Global Variable  | ![Global Variable Match](media/flow-nodes-and-elements/web-global-var-match.jpg) | _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_ | [Match requirements](user-guide/flow/match-requirements) |
| Call Integration                       | ![Call Integration](media/flow-nodes-and-elements/web-integration-node.jpg) | _Allows to call an integration from within a Flow when the Integration has previously been configured in the Integration manager_ | [Integration node](user-guide/flow/integration-node) |
| Call Flow Link                         | ![Call Flow Link](media/flow-nodes-and-elements/web-call-flow-link.jpg) | _Allows to create links from one Flow to another_ | [Flow Link](user-guide/flow/flow-link) |
| Call Script                            | ![Call Script](media/flow-nodes-and-elements/web-call-script.jpg) | _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](user-guide/flow/script-node) |
| Give Response                          | ![Give Response](media/flow-nodes-and-elements/web-give-response.jpg) | _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_ |            |
| Junction                               | ![Junction](media/flow-nodes-and-elements/web-junction.jpg) | _Junctions are displayed in the Flow editor with a simple_ Junction _label_ |            |
| After Match Entity       | ![Entity After Match](media/flow-nodes-and-elements/web-entity-data.jpg) | _Allows to extract the value of an Entity variable._ | [After Match actions](user-guide/flow/data-actions) |
| After Match Language Object | ![Language Object After Match](media/flow-nodes-and-elements/web-lob-data.jpg) | _Allows to extract the value of a Language Object variable._ | [After Match actions](user-guide/flow/data-actions) |
| After Match Script       | ![Script After Match](media/flow-nodes-and-elements/web-script-data.jpg) | _Allows to, for example, store matched words as a variable or execute a script_ | [After Match actions](user-guide/flow/data-actions) |
| After Match Listener     | ![Listener After Match](media/flow-nodes-and-elements/web-listener-data.jpg) | _Allows to execute a script for each input which matches a TLML syntax rule_ | [After Match actions](user-guide/flow/data-actions) |
| Bot Output                             | ![Bot Output](media/flow-nodes-and-elements/web-bot-output.jpg) | _Bot Output contains the answer(s) of the conversational AI application_ | [Bot Output](user-guide/flow/bot-output) |
| Raise                                  | ![Raise label](media/flow-nodes-and-elements/web-raise.jpg) | _The "raise" label indicates when a Flow raise event happens in the Flow dialogue_ |            |
| Drop                                   | ![Drop label](media/flow-nodes-and-elements/web-drop.jpg) | _The "drop" label indicates when a Flow drop event happens in the Flow dialogue_ |            |
| TODO                                   | ![TODO](media/flow-nodes-and-elements/web-todo.jpg) | _The "TODO" labels are shown in the Flow editor on the Plus icons or on Flow nodes when an implementation of the node is still pending_ | [TODO label](user-guide/flow/flow-basics?id=todo-label) |
| Plus icon                   | ![Plus icon](media/flow-nodes-and-elements/web-plus-icon.jpg) | _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](user-guide/flow/flow-basics?id=edit) |

RELEASE NOTES

Platform Dependencies

Dependencies and Licenses

Prerequisites of Teneo Frontends

Teneo 7.0

Teneo 7.0.1

Teneo 7.0.2

Teneo 7.0.3

Technology and deployment

Teneo Studio

KNOWLEDGE BASE

Annotations

Annotations in Engine

Annotations in Studio

Bulk Import formats

Format Entities

Format Language Objects

Format Question and Answer pairs

General about format

Condition writing

Condition coding

TLML syntax summary

Limit unused words to

Draft TLML Syntax

Sentence test order and stop testing

General

FAQs

Input Processors

Custom configuration

Log data

Data model

Metadata

Machine learning

Class Manager

Class Performance

Publish

Solution publish

Resources

Lexical resources

Lexical resources for log data analysis

Teneo naming conventions

Scripts

Global Scripted Context

NLU Variables and Propagation scripts

Predicate scripts

Using scripts

Variables and Listeners

Solution

Localization setup

Multiple Flow Triggers

Skip Conditions

Predefining template solutions

Prompt Triggers

Relative ordering

Resume Prompts

Safetynet and default output

Sub-flows

What does a Flow consist of

Teneo Engine

Environment recognition

Output parameters

Processing path

Script and Listener events in the matching process

Stack of active flows

The answering process

REFERENCE

API reference doc

Teneo Inquire client

Interfacing with API JSPs

Web Socket API

NLP Capabilities

Chinese IP Chain

Japanese IP Chain

Korean IP Chain

Date and Time

Named Entity Recognizer

POS Tagger

Standard IP Chain

Turkish IP Chain

Conversational Modules

Date & Time

Deprecated objects

Pre-built Entities

Flow lists

Named Entity ANNOT objects

POS/Morphology ANNOT objects

Dialogue Resources

Lexical Resources

Offensive Language Detection

Sentiment & Intensity Analysis

Teneo Linguistic Modelling Language (TLML)

Teneo Query Language (TQL)

Auto-test

Auto-test results panel

Automated testing

Class management

Class manager window

Working with Classes and training data

Entity

Entity Basics

Entity Window

Entries Editor

Variables

Flow

Bot Output

Data Actions

Flow Basics

Flow Link

Flow Listener

Nodes and elements

Flow Variable

Flow window

Integration

Match Requirements

Prompt

Script

Sub-flow

Transition

User Intent

Globals

Emotions

Global Listeners

Global scripts

Global Variables

Metadata definitions

Global Context

Import Export

Bulk import

Export/Import of lexical resource

Importing and exporting

Merging solutions

Language Object

Language Object Basics

Language Object Window

Listeners and Variables

Creating a Listener

Creating Flow and Global Variables

Optimization

Class performance

Classifier

Improvement suggestions

Querying log data

Ordering

Ordering groups

Ordering suggestions

Trigger ordering window

Working with trigger relations

Publish environments

Publish a solution

Assign a lexical resource

Integrate external services

Resource Files

Document Basics

Version Control

Keyboard Shortcuts

Lexical Resource Information

Properties Lists

Localization Structure

Updates From Master

Recycle Bin

Search

Solution Properties

Solution Window

Syntax Editor

Referenced Documents

TLML Syntax

Teneo Log Data Manager

Augmenters

Teneo Manager

Get Started

Import/Export

Lexical

Solution Basics

Spellcheck

User Permissions

Login

Tryout

Advanced Tryout

Detailed information

TENEO 7.0.3

Table of Contents

Flow nodes and elements

Overview