►
From YouTube: Teams Development: Bot State
Description
This 10 minute video will show you how to use Bot State so the web service that implements your bot can be stateless. You'll learn about how bots using the Azure Bot Builder SDK manage information about the conversation and the users in it, how to choose and configure a Bot state provider (JavaScript), and how to use conversation and user state in a Bot (JavaScript)
Presenter: Bob German (Microsoft) | @Bob1German
Supporting materials:
• Teams Dev Center: https://developer.microsoft.com/en-us/microsoft-teams
• Microsoft Bot Framework: https://dev.botframework.com/
• Create a Bot for Microsoft Teams: https://docs.microsoft.com/en-us/microsoftteams/platform/bots/how-to/create-a-bot-for-teams
PnP videos for Teams developers: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWG3R399jMSrt1eFa5KErvc
PnP videos for Teams low-code developers: https://www.youtube.com/playlist?list=PLR9nK3mnD-OUEuwES5Zn66qUdUdD60PCZ
A
Hi
I'm
Bob
German
and
this
video
is
BOTS
tape.
Helping
your
BOTS
remember
what
it's
talking
about.
This
video
will
explain
how
BOTS
state
saves
data
between
turns
basically
between
web
server
requests.
I'll,
show
you
how
to
choose
and
configure
a
bot
state
provider
for
your
solution
and
how
to
use
conversation
and
user
state
in
your
bot.
A
So
let's
dive
in
recall
from
last
time
that
the
azure
bot
channel
service
is
what
connects
your
bot
to
teams
and
that
your
bot
communicates
with
the
channel
service
using
rest
calls
recall
also
that
there's
a
thing
called
a
turn
in
which
the
bot
sends
you
a
rest
call
and
you
can
send
back
multiple
activities
or
no
activities.
But
when
you
finally
respond
to
the
original
call
that
ends,
the
turn
turns
can
go
in
either
direction.
A
But
you
can
only
remember
something
really
for
the
duration
of
a
turn,
because
you're
running
in
most
likelihood
in
a
bank
of
stateless
web
servers
where
you
can't
just
keep
something
in
memory
and
have
it
stay
around
so
BOTS
state
is
going
to
help
get
around
that
problem
of
remembering
things
between
turns
so
just
to
clarify.
Where
we
are
your
bot
web
service,
the
green
box
is
using
the
bot
builder
SDK.
So
bot
state
is
a
feature
of
the
bot
builder
SDK.
It's
a
convenience
for
your
bot.
A
You
don't
need
to
use
it,
but
a
lot
of
the
other
bot
builder
concepts
build
on
it.
Bot
state,
there's,
really
three
different
kinds
of
bot:
State
user
data,
conversation,
data
and
private
conversation.
Data
user
data
is
available
in
any
turn
and
conversation
where
the
user
is
present.
So
if
users
come
and
go
from
different
conversations,
you
can
still
get
their
user
data.
It's
a
great
place
to
store
user
settings
and
preferences
conversation.
Data
is
available
in
any
turn
in
a
gun.
In
a
conversation
regardless
of
which
users
are
in
there,
the
application.
A
Microsoft
teams
in
our
case
gets
to
decide
when
conversations
begin
and
end,
and
they
do
tend
to
be
fairly
long
lived
in
Microsoft
teams.
These
are
really
useful
for
dialogue
state,
in
other
words,
keeping
track
of
where
you
are
in
a
back-and-forth
dialogue
and
any
other
details
about
what's
been
said.
There's
a
third
kind
of
state
that
I'm
not
going
to
demo
today
called
private
conversation
data,
which
is
basically
user
data
that
goes
away
at
the
end
of
the
conversation.
A
Now,
when
you're
setting
up
bot
state
inside
of
your
bot
code,
you
can
choose
between
different
storage
providers.
You
could
put
all
the
state
in
memory.
You
could
put
it
in
as
your
table,
storage,
cosmos,
DB
or
write
your
own
I'm,
going
to
show
in
memory
which
is
fine
for
development,
but
it
doesn't
work
with
more
than
one
web
server.
Nor
does
it
survive
restarts.
So
it's
not
really
good
for
staging
or
production.
A
A
Okay.
So
we're
going
to
start
here
in
index
J
s,
which
is
the
starting
class
for
our
node
project.
That
would
be
startup
dot
CS
if
I
was
in
c-sharp
and
you'll,
see
that
starting
on
line
10
I'm
going
to
bring
in
some
required
modules.
The
bot
framework
adapter
is
kind
of
the
main
main
one
for
the
SDK.
This
is
the
one
that
allows
your
bot
to
talk
to
the
channel
service
to
the
framework
on
line
13
we're
bringing
in
the
memory
storage
provider.
A
So
we
could
have
brought
in
one
of
the
others,
but
I'm
just
going
to
run
this
in
memory
and
then
line
12
and
14
have
the
conversation
and
user
state
management
classes.
So
then,
down
at
the
bottom
of
the
screen
on
line
25,
you
can
see
I'm
going
to
new
up
the
memory,
storage,
create
a
conversational,
State
manager
and
pass
in
the
memory
storage
and
then
do
the
same
for
the
user
state.
A
So
now,
let's
go
way
down
and
eventually
I'm
going
to
create
the
bot
here
on
line
53
and
pass
in
the
user
state
and
conversation
State.
So
here's
the
bot
class
and
as
you'll
see
as
you
would
expect,
passing
the
conversation
and
user
state
into
the
constructor
squirreling
those
away
and
then
creating
excess
errs,
starting
on
line
19
for
these
properties.
So
you
have
to
have
a
property
accessor,
which
is
basically
an
object
that
allows
you
to
read
and
write
the
state
property
so
new.
A
Those
up
and
I'm
gonna
call
one
conversation
data,
because
it's
just
things
up
tracking
about
the
conversation
and
the
other
user
profile,
because
it's
things
I
want
to
remember
about
the
user.
Now,
whenever
starting
on
line,
22
I'm
gonna
get
this
anonymous
function
is
going
to
get
called
every
time.
A
new
message
comes
in
from
the
bots
service,
so
the
first
thing
it
does
is
read
in
the
user
state
and
the
conversation
data.
A
Have
I
asked
for
the
user's
name
and
if
the
answer
is
no,
then
on
line
34
I'm
gonna
send
a
message
that
says
what
is
your
name
and
I'm
going
to
remember
in
the
conversation
data
I'm
going
to
also
remember
that
I've
prompted
the
user
and
I'm
just
going
to
make
the
assumption
the
very
next
thing,
the
user
types
is
their
name.
So
the
second
time
I
come
through
this
right.
We're
just
going
to
remember
that
name
in
the
user
profile
and
thank
them
for
their
name.
Now.
A
If
we
already
know
the
user's
name,
then
we're
just
going
to
echo
anything
that
they
say
so.
That's
my
silly
little
scenario
so
that
I
can
just
demo
how
user
in
conversation
state
work
and
make
it
a
little
bit
more
interesting
on
line
51
I'm
gonna,
actually
pull
out
the
a
property
called
turn
count,
which
is
just
my
own
property
I'm,
going
to
keep
track
of.
How
many
turns
I've
been
talking
to
this
user
and,
as
you
can
see,
I'll
I'll
bump
that
up
and
echo
it
out
and
then
what
notice
lines
59
and
60.
A
This
is
really
important.
You
always
have
to
save
your
changes
at
the
end,
so
here
we
are
at
the
at
the
bottom
of
the
function
that
got
called
for
the
message
and
we're
going
to
call
weight
next,
which
is
going
to
end
the
turn
the
bot
turn.
So
what
we
want
to
do
is
save
the
state,
it's
kind
of
like
the
SharePoint,
seesaw
or
server-side
API,
where
you
would
make
a
lot
of
changes
and
then
sort
of
persist
them
with,
with
a
with
one
method,
to
save
all
the
changes
that
you
had
made.
A
A
I'll
go
ahead
and
bring
up
the
local
terminal
and
type
NPM
start
and
notice
that
the
bots
running
on
port
39,
78,
so
I'll
go
to
the
bot
framework,
emulator
and
open
up
localhost
colon,
39,
78,
slash,
API,
slash
messages
and
the
bot
welcomes
us,
gets
the
conversation
update
and
sends
a
welcome
message
if
I
say
hello
as
expected,
it
asks
me
for
my
name
and
now
it
addresses
me
by
name
from
here
on
so
user
state
is
working.
You
can
see.
The
conversation
state
is
correctly
tracking.
A
A
Thanks
for
watching
this
Microsoft
365
patterns,
&
practices-
video-
if
you
like
this
video,
please
subscribe
to
the
patterns
and
practices
youtube
channel
at
AKA,
OMS,
slash,
SP,
P,
NP
of
videos,
I'm
Bob
Sherman.
You
can
follow
me
on
twitter
@
Bob,
one
German
and
please
check
out
my
blog
at
Bob,
one
German
comm!
That's
all
for
this
time,
and
thanks
for
watching.