Hero - Build your bot

Scripted contexts make it possible to add restrictions to triggers or transitions using scripts. You define [scripted contexts](/studio/conversations/concepts/context) once, globally in your solution, and then they can be applied to any trigger or transition in your solution. You can include scripts in language conditions too, but that might cause duplication of code. Storing them centrally in a scripted context makes your solution easier to maintain.

Let's assume our solution contains flows that should only be triggered at certain times of the day, for example only before noon, when breakfast is served. We can create a scripted context called 'Is it morning?' that will return 'yes' or 'no' depending on the time of day.

Once added, the scripted context 'Is it morning?' will look as follows:

![Context added to the global context manager](//images.ctfassets.net/2vbtnveccz5s/7Kfsf1R4oqsGhQpT71eXPl/b0252473328e65fb80ba0de26df03de6/finale_1.PNG)

## Create a scripted context
To create a new scripted context, proceed as follows:
1. From the main solution window, click on the 'Solution' tab.
2. Choose 'Globals' and select the 'Contexts' tab.
3. Click the 'Add' button to add a new context.
4. Name the context `Is it morning?`
5. Click on the back arrow in the top left of your window to go to the main scripted context window.

![1-create context](//videos.ctfassets.net/2vbtnveccz5s/3gc0QsSTVrLdSPmYrIKTdx/570244cba1b36b09f3f849e0e2cbddb7/1-create_context.mp4)

We can now add the script and specify the valid 'states' of our context.

## Add the script
While still in the main scripted context window, paste the following script into the scripting area to the left:
```groovy
// get the hour of the day
def hour = java.time.LocalDateTime.now().getHour()
// is it morning?
if (hour > 5 && hour < 12) {
    return true
} else {
    return false
}
```

The scripts gets the current time and if the current hour is between 5 and 12 in the morning, it will return __true__. On other hours, it will return __false__.

![Scripted context added](//images.ctfassets.net/2vbtnveccz5s/q6aSTleIAE9fym1QE1nAj/c962c2a960a8359ada6a8481fc7def6a/first_picture_1.PNG)

## Add Expected States
Since the script can return two values (true and false) we will need to add 'Expected states' for both them. These will be the values that can be selected when adding a context restriction to a trigger or a transition.

### Add the 'Yes' state
1. In the Expected States panel on the right, replace __Expected state 1__ with `Yes`.
2. In the field below, type `true`; this means this expected state 'Yes' will be returned when the script returns __true__.

### Add the 'No' state
1. Click on the Add button at the top of the panel to add a second state.
2. Replace __Expected state 1__ with `No`.
3. In the field below type `false`; this means this expected state 'No' will be returned when the script returns __false__.
4. Hit 'Save'. 

![Add Expected States](//videos.ctfassets.net/2vbtnveccz5s/50uVtgpUGiMPzp0z0neRnQ/afaee6e4ffc5d5f330d23f2af041a17a/inside-context-script.mp4)

## Usage in flows
That's it! We now have a global scripted context that can be used to restrict an trigger or transition based on the time of day. This is what the context might look like within a flow:     

![flow with context](//images.ctfassets.net/2vbtnveccz5s/zuo6TdFYCKE3PhO3orjp4/2f4fa8248d4600213c36ed54ef48a199/flow_with_context.png)

!!! You can add context restrictions in the 'Examples' panel of a trigger or transition, as illustrated [here](/getting-started/deal-with-follow-ups#make-the-trigger-context-dependent).

Define a scripted context

Scripted contexts make it possible to add restrictions to triggers or transitions using scripts. You define [scripted contexts](/studio/conversations/concepts/context) once, globally in your solution, and then they can be applied to any trigger or transition in your solution. You can include scripts in language conditions too, but that might cause duplication of code. Storing them centrally in a scripted context makes your solution easier to maintain.

Let's assume our solution contains flows that should only be triggered at certain times of the day, for example only before noon, when breakfast is served. We can create a scripted context called 'Is it morning?' that will return 'yes' or 'no' depending on the time of day.

Once added, the scripted context 'Is it morning?' will look as follows:

![i-finished context](//images.ctfassets.net/2vbtnveccz5s/l0oGx98GEZI248i25KJRG/cf9efa39550ef34968a0eba6c0cf8f0e/i-finished_context.png)

## Create a scripted context
To create a new scripted context, proceed as follows:
1. On the Solution dashboard, navigate to the Globals tile.
2. Click on the Add button next to Scripted Contexts.
3. Name the context `Is it morning?`
5. Click on Create.

![1-create new context](//videos.ctfassets.net/2vbtnveccz5s/56cuHGLOefoZuvt0Vleaod/5abac999c78b898f74434b414375ccfc/1-create_new_context.mp4)

We can now add the script and specify the valid 'states' of our context.

## Add the script
While still in the main scripted context window, paste the following script into the scripting area to the left:
```groovy
// get the hour of the day
def hour = java.time.LocalDateTime.now().getHour()
// is it morning?
if (hour > 5 && hour < 12) {
    return true
} else {
    return false
}
```

The scripts gets the current time and if the current hour is between 5 and 12 in the morning, it will return __true__. On other hours, it will return __false__.

![2-is it morning](//images.ctfassets.net/2vbtnveccz5s/5o1FmS4m7b6Alc3pdlmW27/980a2ca7c736bc9edda5109b9753aab8/2-is_it_morning.png)

## Add Expected States
Since the script can return two values (true and false) we will need to add 'Expected states' for both them. These will be the values that can be selected when adding a context restriction to a trigger or a transition.

### Add the 'Yes' state
1. In the Expected States panel on the right, you will see an expected state has been added already. Set the name of this state to `Yes`.
2. In the field below, type `true`; this means this expected state 'Yes' will be returned when the script returns __true__.

### Add the 'No' state
1. Click on the Add button at the top of the panel to add a second state.
2. Name this state `No`.
3. In the field below, type `false`; this means this expected state 'No' will be returned when the script returns __false__.
4. Hit 'Save'. 

![3-expected states](//videos.ctfassets.net/2vbtnveccz5s/3C21hmmuVABpbFkn4X494o/678d21c9d4da8217d5f09d7a85436ebc/3-expected_states.mp4)

## Usage in flows
That's it! We now have a global scripted context that can be used to restrict an trigger or transition based on the time of day. This is what the context might look like within a flow:     

![4-states in flow](//images.ctfassets.net/2vbtnveccz5s/252l4QyDAIuStkSayLlGZZ/bd2a8590b1f4639a514d372a90dc3810/4-states_in_flow.png)

!!! You can add context restrictions in the 'Examples' panel of a trigger or transition, as illustrated [here](/getting-started/deal-with-follow-ups#make-the-trigger-context-dependent).

Studio Web - Define a scripted context

Build - Define a scripted context

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

Safetynet

Trigger Ordering

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

Variables

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

Linguistic Modeling Language

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

Engine Scripting API Reference

Input Processing Path

Language Object Reference

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

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