Hero - Build your bot

Variables are important when building bots. Not least, your bot's memory will rely on what is stored in variables. Global variables in Teneo are accessible from all flows, script nodes in flows, listeners and most [script events](/article/build/scripting/concepts/scripts) in your solution. In that way, they differ from [flow variables](/article/build/flows/concepts/variables#flow-variable), which only exist during the processing of a flow, and will be forgotten as soon as a flow is dropped from the [flow stack](/studio/conversations/concepts/flow-stack).

## Global variable

### Create a global variable

You can create global variables in the main solution window. Open the 'Solution' tab and select 'Globals'. Then select 'Variables' at the top, and click 'Add' in the upper right corner. Give the variable a name, and assign it with a default value.

![1-global vars](//images.ctfassets.net/2vbtnveccz5s/NmW2UMgbu7ioD6cWxipSh/1b748b2394faecf6568037a0bc2b5248/1-global_vars.PNG)

### Lifespan

By default, the value of a global variable lives for the entire session, or until it's reset. You can, however, make a global variable forget its value after a specified number of turns. The variable will then be cleared and get back its default value. In Teneo this is called *'setting the lifespan'* of a variable. A [common use case](/studio/conversations/how-to/share-information-between-flows) is to remember something the user says in one flow, so that it can be used in another flow.

If you have a global variable called __topic__, you would set its lifespan like so:

    `_.setSessVarLifespan('topic', 2)` 

You would typically set the value of the variable at the end of a flow and at the same time set its lifespan. In this example, the lifespan is set to two turns, but you are free to choose whatever value you see fit. Note, however, that the lifespan includes the request/input that is currently being processed. Each subsequent request (or input or turn) will consume one of the lifespans and when the lifespan reaches 0, __topic__ will be reset to the value that was used when it was initialized. However, any flow can overwrite the value of the global variable at any time and give it a new lifespan.

## Flow Variable

Flow variables allow your bot to remember details during the processing of a flow. Anything you store in a flow variable will be forgotten once the flow has finished processing. If you want to [share information between flows](/studio/conversations/how-to/share-information-between-flows), you have to use [global variables](/article/build/flows/concepts/variables#global-variable) instead.

### Create a Flow Variable

To create a flow variable, open a flow in 'Edit' mode, go to the 'FLOW' tab and select 'Variables'. Click on 'Add' in the upper right corner, and provide a name and a default value. In the example below, we have two variables, __flavor__ and __size__, which both have an empty string __""__ as the default value.

![flow variable](//images.ctfassets.net/2vbtnveccz5s/poo9ta8hju3rGrKvYIUsl/67d39edfcb42d4533d994a62bb9bae26/flow_variable.PNG)

!!! In Teneo, variables may be of any type that Groovy (and Java) supports, including strings, booleans, maps, lists, and custom objects. It's possible to populate and edit a variable in your flow, you can populate a flow variable using a script, or you can store the results of an integration or a Sub-Flow in a variable.

## Local variables
Local variables are only available in the script node (or script event) in which you created them. You must define or specify the type of the local variable like so:  `def name = "Guillaume"`. You can see an example of a script with local variables here: [How to add a script to your flow](/studio/flows/how-to/add-a-script-to-your-flow).

Build - Variables

Variables are important when building bots. Not least, your bot's memory will rely on what is stored in variables. Global variables in Teneo are accessible from all flows, script nodes in flows, listeners and most [script events](/article/build/scripting/concepts/scripts) in your solution. In that way, they differ from [flow variables](/article/build/flows/concepts/variables#flow-variable), which only exist during the processing of a flow, and will be forgotten as soon as a flow is dropped from the [flow stack](/studio/conversations/concepts/flow-stack).

## Flow Variable

Flow variables allow you to remember details during the processing of a flow. Anything you store in a flow variable will be forgotten once the flow has finished processing. If you want to [share information between flows](/studio/conversations/how-to/share-information-between-flows), you have to use [global variables](/article/build/flows/concepts/variables#global-variable) instead.

### Create a Flow Variable
To create a flow variable you open a flow in 'Edit' mode, select the Variable icon under the minimap. Click on 'Add' and provide a name and a default value. In the example below, we have two variables, __orderedCoffeeType__ and __userNameForOrder__, which both have an empty string __""__ as the default value.

![1-variable](//images.ctfassets.net/2vbtnveccz5s/31dZnQDdmR1owywtdijN8Z/88901d36fb5837ff4c328dab6b100fed/2-variable.png)

!!! In Teneo, variables may be of any type that Groovy (and Java) supports, for example strings, booleans, maps, lists and custom objects. Its possible to populate and edit a variable In your flow, you can populate a flow variable using a script or you can store the results of an integration or a sub-flow in a variable.

## Local variables
Local variables are only available in the script node (or script event) in which you created them. You must define or specify the type of the local variable like so:  `def name = "Guillaume"`. You can see an example of a script with local variables here: [How to add a script to your flow](/studio/flows/how-to/add-a-script-to-your-flow).

Studio Web - Build - Variables

Variables

Analyze your bot

Analyze Log Data

Analyzing sessions

Augmenters

Concepts

Extract values with Augmenters

How To

Metadata

Running custom queries

Counting coffees with Metadata

Reference

Teneo Query Language Cookbook

Teneo Query Language Reference Guide

Teneo Query Language Syntax Overview

Teneo Query Language

Data hierarchy

Event

Property

Session

Transaction

How to

Explore session statistics

Find stuck flows

Generate session logs

Locate and view a session

Make use of skip constraints

Make use of sub queries

Query variables

Troubleshoot the Safetynet

Use relative dates in queries

Query Syntax

Command

Constraint

Meta-parameter

Selection

Transformer

Build your bot

Bot design

Best practices

Data footprint

Encrypting user data in sessions

Flow checklist

Plan your bot

Starting a new Teneo project

Writing good answers

Writing good examples

Conversations

Context restrictions

Flow stack

Greeting message

Listeners

Ordering

Safetynet

Create a custom order group

Handle ambiguous inputs

Make your bot pro-active

Share information between flows

Use listeners

Flows

Bulk Import

Entities

Junctions

Outputs

Sub-Flows

Transitions

Intent triggers

Add a script to your flow

Branch at the beginning of a flow

Use TLML Syntax Match

Use a Sub-Flow

Use Bulk Import

Language Understanding

Annotations

Attached scripts

Language conditions

Language objects

Languages

Lexical resources

Libraries

Localization

Match requirements

Used words

Combine Match requirements

Create a solution in your language

Create your own language objects

Find language objects and entities

Localize a bot

Normalize the user's spelling

Optimize language conditions

Recognize plural and singular

Store what the user said

Advanced Condition Coding

Annotations Reference

Condition Syntax Reference

DateTime Handler Reference

DateTime Handler

Engine Scripting API Reference

Input Processing Path

Language Object Reference

Prebuilt Entities

Scripting

Engine scripting API

Groovy basics

Integration manager

Resource file manager

Scripts

Add a Groovy class

Add an integration

Add files to your solution

Annotate user inputs

Anonymize user data

Define a scripted context

Populate output parameters

Store input parameters

Test your bot

Run automated tests

Test your bot with Botium

Dialog Tester

Deploy your bot

Engine API

Versioning and Publishing

Publish your bot

Version Flags

Work with Version Flags

SDK's

Android

JavaScript

Node.js

Getting started

After Match

Extract Entities

Class Manager

Introduction to transitions

Introduction to entities

Deal with Follow-ups

Dialogue and Context Model

Getting started with Teneo

Handle interruptions

Skip conditions

Teneo in 10 minutes

Flows and match requirements

Entities and After Match

Your First Flow

Your First Solution

Optimize your bot

Optimize classes

Improve the balance

Review Inputs

Refine your bot

Debug your bot in Tryout

Use data to improve your bot

Use Teneo's improvement tips

Troubleshooting

My flow doesn't trigger

My flow behaves unexpectedly

I see warnings in Tryout

Suggestions

root

Table of Contents