►
From YouTube: Adaptive Cards community call - March 2021
Description
In this month's community call, there is a quick roadmap update – 9 features in development to be delivered in Schema versions 1.4, 1.5, 1.6 over the next 3 months. Then there is a deep dive with demos and Q&A, focused on the Action.Execute feature and underlying Universal Actions Model for Microsoft Teams, Outlook and more, rolling out mid-April in Schema v1.4. The new Action.Execute action type synchronizes activity in the back-end while rendering natively in Teams and Outlook front-ends. The call was hosted by Matt Hidinger (Microsoft). Presenters include Shiladitya Saha (Microsoft Teams) and Karan Thapar (Microsoft Outlook). Recorded on March 11, 2021.
Stay connected:
•Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog
• Recurrent Invite https://aka.ms/adaptivecardscommunitycall
• Next call: April 8th at 09:00am PDT
A
So
hi
everyone
welcome
to
the
adaptive
cards
community
call
of
march
2021.,
I'm
matt
heidinger
I'll,
be
your
your
host
actually
just
for
the
start
of
this
call,
so
we
meet
every
month
on
the
second
thursday
of
the
month
at
9
a.m.
Pacific
time,
if
this
is
your
first
time
here,
welcome
you're
a
repeat
guest.
We
we
welcome
you
back
as
well.
A
A
That
is
your
best
place
to
go.
I've
got
a
version
of
it
right
over
here.
Actually
yeah
now,
it'll.
Take
you
to
this
page
and
I
share
this.
I
try
and
share
this
kind
of
every
call
just
to
make
sure
people
are
aware
of
it.
This
is
your
best
place
to
have
a
voice
into
what
we
build
next
and
what
you'll
see
is
three
tabs
along
the
top
things
that
are
under
consideration.
A
These
are
just
a
lot
of
the
ideas:
we've
explored
from
svg
support
to
a
rating
control,
responsive,
ui,
client-side,
updating
anything
in
this
first
tab,
we're
aware
of
it,
but
we're
not
quite
at
a
place
where,
where
we
know
when
we'll
work
on
it
or
even
that,
we
would
necessarily
get
to
it
in
the
in
the
some
future
planned,
on
the
other
hand,
is
stuff.
We
know
we're
going
to
do
we're
either
started
on
it
or
it'll,
be
started
on
soon,
and
I'm
just
going
to
break
this
down
into
a
few
things.
A
But
what
what
helps
us
the
most
is?
You
can
see
these
little
numbers
next
to
things,
and
it
is
very
easy
for
you
to
tell
us
what
you
need
and
give
us
a
little
bit
of
insight
into
why
you
need
it.
So
one
of
the
most
popular
requested
features
is
this
input
choice
set
autocomplete,
so
you
can
actually
search
from
a
drop
down
list.
Server
side
connect
to
a
server,
and
actually
you
know,
get
some
better
data
back
than
you
can
today,
with
this
a
static
list
of
things.
A
So
what
you
can
do
is
tell
us
how
important
this
is
to
you.
Is
it
nice
to
have
important
or
critical
give
us
a
little
bit
of
info
and
just
an
email,
you
don't
create
an
account,
don't
create
a
password
or
anything
very
low,
friction
way
for
you
to
kind
of
steer
the
direction
that
we
go
with
with
adaptive
cards.
A
If
you
don't
see
what
you
need
in
here,
then
you
can
go
and
kind
of
submit
an
idea
and
also
just
tell
us
in
general
what
it
is
and
we
go
through
that
feedback
when
we
start
to
plan
our
next
release
so
check
that
out.
Take
advantage
of
that
and
let
us
know
what
would
what
would
help
you
the
most.
That
said,
I've
got
some
details
and
and
quote-unquote
etas.
I
had
to
throw
an
eta
on
there
because
I
knew
it
would
be
the
first
question
so
so
I
did.
A
A
We
talked
a
lot
about
these
last
month,
so
if
you
weren't
with
us
last
month
and
want
to
know
what
all
these
features
are,
we
did
a
pretty
big,
deep
dive
into
all
of
them
and
and
when
you'll
start
to
see
them
in
teams.
So
some
of
them
are
small
like
password
masking
and
input
text,
but
then
the
dynamic
autocomplete
huge
feature
actions
being
able
to
kind
of
overflow
into
an
ellipsis
fly
out.
A
very
highly
requested
feature,
so
you'll
start
to
see
those
trickle
out
in
teams.
A
The
reason
I
kind
of
had
to
say
soonish
is
that,
if
you're
rendering
cards
today-
and
you
are
using,
say
our
ios
android
sdk-
maybe
the
react
native
sdk
supported
by
imagineer-
we
don't
have
timelines
on
when
those
will
be
in
the
sdks,
so
you're
going
to
see
them
in
teams
first
and
then
we're
going
to
take
that
code
out
of
teams
port
it
back
into
the
sdks,
the
general
purpose,
sdks,
so
that
anyone
else
can
start
to
take
advantage
of
them.
So
you'll,
it's
a
little
bit
staggered
and
that's
kind
of
why.
A
We
also
have
a
pretty
good
handle
on
at
least
two
of
the
features
we're
going
to
have
to
do
immediately
following
1.5,
and
one
of
them
is
a
an
actual
table
element.
So
a
lot
of
people
are
using
column
sets
to
create
table
like
structures
which
works.
It's
not
the
most
fun
and
in
certain,
and
if
you
have
any
kind
of
accessibility
needs,
it's
not
fun
at
all
the
column
set
structure.
A
They're,
it's
not
accessible
one
bit
so
so
the
table
element
will
be
much
more
user-friendly
if
you
are
showing
tabular
data
and
also
be
much
more
accessible
to
everyone
who
might
be
interacting
with
your
cards
after
that
is
one
of
the
bigger
advancements
we're
making
in
adaptive
cards.
It's
called
these
adaptive
components,
and
these
are
these
on-demand
declarative
components,
higher
level
components
like
files
or
people,
or
these
these
things
that
you
want
to
drop
in
and
not
necessarily
provide
the
layout.
A
So
we've
talked
a
lot
about
adaptive
components
in
the
past
on
some
previous
calls,
so
feel
free
to
take
a
look
through
the
archive
and
we'll
link
to
the
archive
later
on,
but
this
is
sort
of
a
gist
of
when
we
think
we're
getting
into
it.
I
don't
have
any
kind
of
timeline
on
adaptive
components
and
my
dev
team
is
on
this
call
and
would
be
upset
with
me.
If
I
put
anything
other
than
end
of
year,
question
mark,
we
are
trying
to
figure
out
when
we
can
get
through
a
lot
of
these
things.
A
So
if
you
have
any
questions
on
the
roadmap,
please
feel
free
to
send
them
in
chat
I'll,
be
monitoring
chat
and
we
do
have
a
dedicated
q
a
section,
but
for
the
rest
of
this
I'm
going
to
hand
it
over
to
karan
and
shiladitya
and
they're
going
to
dive
into
this
universal
action
stuff.
So
we'll
be
monitoring,
chat
and
helping
you
out
and
I'll.
Let
them
kind
of
handle
how
they
want
to
run
the
rest.
But
we
will
have
a
dedicated
q,
a
section
at
the
end
as
well.
B
C
A
B
Sure,
thanks
for
that
matt,
so
if
I
were
to
summarize
the
overall
value
prop
of
adaptive
cards
in
one
sentence,
it's
around
enabling
you
to
take
quick
actions
right
from
within
teams
and
outlook
at
its
core
adaptive
cards,
allow
you
to
safeguard
your
productivity
and
acknowledge
content
without
ever
having
to
leave
the
hub
of
your
choice,
which
could
very
well
be
either
teams
or
outlook
and
in
the
process
eliminate
context.
Switching
completely
here
are
a
few
of
our
most
popular
scenarios.
I'm
sure.
B
B
Here
are
a
few
snippets
of
adaptive
cards
that
show
that
these
work
cross
platform
cross
devices.
So
you
get
a
great
look
and
feel
across
mobile
and
desktop
devices,
and
then
they
also
run
cross
apps.
So
it
means
that
adaptive
cards
work
seamlessly
on
both
teams
and
outlook,
and
the
examples
that
you
see
here
are
from
poly,
asana,
etc.
B
I'm
sure
most
of
you
are
well
versed
with
outlook
and
teams,
and
in
addition
to
that,
we
have
the
likes
of
web
chat,
windows,
cortana,
etc,
and
the
challenge
that
such
a
broad
ecosystem
presents
is
that,
while
layout
and
rendering
for
adaptive
cards
are
universal,
the
action
handling
is
not,
and
this
is
also
a
question
that
I
just
saw
on
the
chat.
What
it
implies
is
that
today
there
is
an
inconsistent
action
model
between
teams
and
outlook.
B
Hence
you
see
that
the
action
model
is
inconsistent
and
there
previously
did
not
exist
anyway,
to
have
the
same
adaptive
card
payload
work
on
both
teams
and
outlook.
This
presented
a
disconnected
deployment
model
for
outlook
and
teams
and
thinking
in
terms
of
three
key
personas
for
a
developer
partner.
For
an
engineer,
there
was
lack
of
a
consistent
extensibility
model
and
due
to
the
disparate
action
types,
action.http
or
action.submit,
the
engineers
were
asked
to
build
two
separate
adaptive
card
based
applications,
one
each
for
outlook
and
teams.
B
B
You
can
simply
have
action.execute
in
your
adaptive
card
payload
and
that
payload
would
just
work
completely
fine
on
both
themes
and
outlook
and
wait
there's
more
to
it.
Now
we
have
also
introduced
a
refresh
card
mechanism
and
action.
Dot.
Execute
can
now
return
a
new
card
to
replace
the
existing
card
in
place.
B
B
B
Your
team
now
needs
to
build
only
one
application
that
uses
the
same
adaptive
card
payload
with
action.execute,
which
would
work
on
both
teams
and
outlook,
and,
to
be
honest,
the
greatest
value
prop
for
me
is
for
our
end
users.
Now
they
get
to
see
seamless
synchronization
between
their
emails
in
outlook
and
their
chart,
messages
and
teams.
B
C
B
B
B
B
She
decides
to
click
on
approve
and
that's
it
by
a
single
click.
Cat
was
able
to
approve
pat's
vacation
request
that
too,
within
fraction
of
a
second
and
thereby
safeguarding
her
productivity
as
well,
and
since
we
are
talking
about
action.execute,
the
best
part
is
that
this
acknowledgement
also
gets
reflected
in
teams
and
we'll
show
how
that
works
in
a
minute.
A
E
Thank
you
just
real,
quick
on
the
on
the
action.execute.
I
you
had
previously
mentioned.
The
react
native
sdk
would
sort
of
be
trailing
in
the
implementation
of
some
of
these
new
features.
That's
currently,
our
primary
delivery
channel
is
is
through
the
mobile.
Do
you
have
an
idea
of
sort
of
the
when
the
action.execute
would
be
implemented,
or
is
that
sort
of
in
the
soonish
or
you
know,
later-ish.
E
A
React
native
renderer
in
particular,
is
maintained
by
our
community.
I
was
scanning
the
list
to
see
if
anyone
is
on
that
call.
I
have
a
sync
with
them
meeting
with
them
next
week,
where
we're
gonna
talk
about
some
react
native
updates,
so
I
can
get
confirmation
then
they're,
usually
pretty
quick
after
things
you
know
get
announced.
So
I,
if
you're
following
along
on
the
to
get,
are
you
using
the
imagineer
one?
Do
you
know.
E
Yeah
I'm
using
the
imagineer
currently,
but
we've
actually
we've
actually
forked
it
and
done
our
own
implementations
to
get
it
to
where
we
need
it.
So
I'm
just
trying
to
figure
out
if
there
will
be
a
catch-up
on
that
or
if
there's
a
significant
lag
or
me,
maybe
maybe
I'll
end
up
being
the
one
that
does
it.
A
D
A
B
Right
sure,
thanks
matt
and
thanks
for
the
question,
all
right
moving
ahead.
This
is
how
the
view
appears
on
a
wider
outlook
desktop
screen.
You
again
see
that
cat
is
able
to
view
all
the
necessary
details
from
within
her
email,
click
on
approve
and
be
done
with
it,
and
let's
also
take
a
moment
to
appreciate
that
cat
benefits
from
seeing
an
acknowledgement
instantaneously,
and
she
knows
that
the
vacation
request
has
already
been
approved
and
it's
one
lesser
task
for
her
day
now.
B
Now
we
have
another
sort
after
scenario
around
adaptive
cards
that
talks
about
access
request,
approvals
cat
is
again
working
on
a
project
and
realizes
that
he
doesn't
really
have
access
to
a
necessary
document,
and
hence
he
requests
his
manager
cad
to
provide
him
the
requisite
approvals
again.
Cat
thanks
to
adaptive
cards
receives
an
actionable
email
in
outlook.
B
B
F
E
F
We
are
experiencing,
you
know
we
get
the
the
flash
update.
You
know
the
the
activity
showing
up,
but
the
the
card
itself
doesn't
show
up
in
the
tab
app,
so
we
have
to
do
some
kind
of
pulling.
I
was
just
wondering
this.
This
instant
update,
you
know,
activity
that
you're
talking
about
is.
Is
this
a
a
new
behavior
that
we're
we're
expecting
to
see,
or
are
we
expecting
to
do
some
polling
still
in
order
to
get
the
cards
to
update
in
a
tab,
app.
B
D
We
had
a
question
in
in
chat,
and
I
was
discussing
that
with
thomas
like
the
last
days.
So
as
far
as
I
know
to
do
that,
you
need
you
need
a
bot
in
the
background
right
now,
and
that
also
goes
in
line
with
a
question
we
have
in
chat.
If
there's
a
way
to
decide
where
you,
if
a
user
wants
it
in
both,
that's
something
I
can
decide
in
my
bot.
So
the
underlying
question
is:
can
I
only
do
that
with
a
bot
right
now
or
do
I?
A
Yeah,
I
think
the
answer
that
is
the
the
whatever
generated
the
card
is,
is
determining
what
user
experience
it
gets
delivered
to
so
they'll
be
generating
it
to
make
the
demo
they
just
showed.
You
would
be
generating
an
email
attaching
the
card
there
and
you
would
also
be
either
posting
a
card
to
a
channel
or
whatever
you
know,
you're
kind
of
in
charge
of
that
the
user.
I
don't
unless
they
built
it
in,
wouldn't
be
able
to
say
you
know.
I
no
longer
want
these
emails
like
the
the
back
end.
A
B
C
Sure,
thanks
karen
so
like
now
we'll
go
into
what
these
new
features,
what
the
universal
action
model
means
for
like
teams,
apart
from
the
university
context,
so
one
of
the
features
that
I'm
very
interested
to
talk
about
is
contextual
views
or
role-based
views.
So
all
users
in
a
team
today
see
the
exact
same
view
of
the
adaptive
card.
So
essentially,
everyone
is
seeing
the
same
chat
like
the
same
adaptive
card
in,
for
example,
a
channel
for
example.
Group
chat.
C
However,
there
is
need,
in
certain
scenarios
for
certain
people
to
see
different
actions
or
different
different
information
so
as
to
take
some
like
search
to
take
or
complete
an
action.
So
I'll
take
the
example
of
say
up
approvals.
You
would
want
someone
in
a
group
like
someone
sending
an
approval
in
a
group
chat.
Would
you
want
only
the
approval
to
get
the
accept
and
reject
buttons?
C
You
wouldn't
want
someone
else
in
the
chat
to
accidentally
approve
or
reject
your
card,
so
that
is
where
you
need
the
approval
to
get
maybe
some
more
information,
maybe
the
accept
and
reject
buttons
themselves.
So
that
is
what
contextual
views
now
allows
you
to
do.
So
certain
people
that
can
now
get
differentiated
information
and
actions
so
now
taking
you
through
the
approval
scenario,
the
requester
is
daniella,
who
wants
to
request
a
discount
for
her
long-term
customer
from
her
manager,
mary
and
mary
who's.
C
So
here
I'm
showcasing
two
screens.
The
left
one
is
daniella's
she's,
the
requester
there,
and
once
she
sends
the
approval
within
the
group
chat.
You'd,
see
that
on
the
left
is
daniela's
view
and
she
only
sees
the
option
to
cancel
the
request.
While
on
the
right,
you
see
mary's
view
and
she
has
the
option
to
approve,
reject
and
few
details.
So
she
also
has
the
option,
to
you
know,
add
more
comments
and
before
she
accepts
or
rejects
it.
C
H
Megan
is
a
50
inspector
at
contoso
who
routinely
inspects
the
sites
and
reports
incidents.
Let's
see
a
typical
day
at
megan's
work
and
how
the
new
capabilities
we
talked
earlier,
provide
rich
contextual
experiences
to
her,
and
the
team
megan
observes
that
one
of
the
boilers
at
a
remote
site
had
broken
down
and
files.
A
new
incident
through
contoso
report
incidents,
message,
extension
in
teams,
the
incident
card
gets
posted
in
the
group,
and
you
can
see
that
the
message,
although
posted
by
the
bot,
shows
it
being
sent
by
megan.
H
This
demonstrates
the
sender
attribution
feature.
We
talked
about
a
while
back
to
easily
demonstrate
role-based
views.
I've
logged
into
three
different
user
accounts
of
megan's
who
files
the
incident
of
alex
to
whom
the
incident
is
assigned
to
and
of
nestor
who
represents
rest
of
the
group
members
who
are
not
involved
in
the
process.
H
C
So
that
was
a
example
of
role-based
views
and
the
universal
actions
both
working
for
a
ticketing
application,
so
you
could
have
similar
scenarios
or
approval
scenarios
like
current
talked
you
through,
and
you
could
definitely
go
into
those
using
the
new
universal
actions
model.
So,
basically,
from
what
we've
talked
about
till
now,
there
are
some
core
capabilities.
One
is
the
fact
that
the
actions
are
universal.
C
Now
they
are
on
outlook
teams
and
more
platform
soon,
there's
a
refresh
property
that
is
coming
in,
so
that
is,
that
is
how
refresh
will
start
working
on
both
teams
and
outlook
on
outlook.
You
all
already
had
the
auto
invoke,
and
on
teams
you
now
have
the
refresh
that's
going
to
come
in
so
refresh
is
what
enables
what
you
currently
saw
so
refresh
is
like
david
already
mentioned
in
the
chat.
Refresh
is
what
powers
role
base
views?
C
C
C
So
today,
on
teams,
essentially
whatever
card
you
send
like
we
talked
about
it's
same
for
everyone
right.
So
you,
if
you
want
to
progress
through
a
set
of
workflows,
you
would
have
to
send
a
one
card
after
the
other
continuously
and
then
as
well
like
it
would
be
like
it
cannot
be
replaced
like
it's
clogging
the
chat,
essentially
so
with
action.execute
with
the
capability
to
actually
replace
the
card
in
place.
C
So
now,
essentially
I
progressed
through
that
catering
what
I
ordered
whatever
food
I
wanted
to,
and
during
this
entire
thing
I
just
had
it
within
one
card.
So
basically,
within
that
one
card,
I
was
able
to
update
the
like
update
the
entire
scenario
and
complete
it.
The
next
thing
that,
like
one
more
thing
that
we
can
do
using
this
like
using
sequential
workflows,
is
different
people
within
the
same
chat
can
be
on
different
stages
of
ordering
food.
C
C
So
that
is
another
interesting
capability
that
is
coming
in
so
in
terms
of
product
and
engineering
investments,
so,
like
first
step,
of
course,
is
envisioning
the
scenarios,
something
that
you
might
have
already
got
on
teams,
and
you
want
to
get
to
outlook
something
you
might
have
already
got
an
outlook.
You
want
to
get
that
to
teams,
you
need
to
envision
those
scenarios
for
the
full
cross
app,
and
then
you
need
to
design
those
adaptive
cards.
You
may
already
have
them.
C
C
If,
for
example,
you're
already
on
outlook
and
you're
looking
to
come
to
teams,
then
you
need
to
create
a
bot
and
register
for
outlook
and
teams
as
channels
if
you're
already
on
teams,
they
bought
you'd
already
have
a
bot,
and
that
is
what
you'd
be
able
you'd,
be
able
to
just
register
for
outlook
as
a
channel
and
then
send
out
adaptive
cards.
So
that
is
essentially
how
this
works.
C
B
Guidance
on
that,
at
least
for
outlook,
we
request
all
our
partner
developers
to
ensure
that
we
get
response
within
a
threshold
of
three
seconds
and
I'll
also
request,
shiladiti
and
syrup
to
chime
in
around
the
the
latency
requirements
to
be
on
teams.
However,
from
outlooks
perspective,
there
is
a
clear
directive
to
our
partners
to
ensure
that
at
p95
at
95th
percentile,
the
latency
shouldn't
exceed
three
seconds
for
the
partner
cards.
C
So
going
into
behind
the
scenes,
so
this
is
what
the
current
inconsistent
action
model
looks
like,
so
we'll
just
be
talking
about.
What's
changed
and
pretty
much
covering
what's
happening
behind
the
scenes
and
what's
changed
here
so
on
outlook,
you
would
have
your
web
service
on
the
backend,
while
on
teams,
when
you
were
using
action.submit,
you
would
have
had
your
bot,
which
was
doing
the
legwork
there
so
because
of
this
different
model.
C
That
is
why
you
were
having
to
define
and
handle
two
endpoints
separately
for
teams
and
outlook.
Now,
with
the
common
action
execute
model
coming
in,
you
have
the
bot
as
the
common
back
end.
That's
going
to
do
the
leg
work
for
you
and
with
that
you
could
send
both
to
outlook
and
teams
pure
cards
on
both
places
and
the
bot
would
be
able
to
maintain
both
of
them
in
sync.
C
C
C
C
A
Yeah
we're
doing
great,
I
will
go
ahead
and
take
over
sharing
give
people
some
quick
links
just
to
kind
of
wrap
up,
and
then
we
can
start
taking
any
questions.
Ideally
on
this,
since
we
have
some
folks
on
the
team,
but
don't
hesitate
to
ask
other
questions
so
again,
thanks
everyone,
a
ton
for
joining
here's,
a
handful
of
resources,
definitely
take
a
look
at
our
roadmap.
A
Definitely
look
at
templating.
We
haven't
talked
about
in
a
little
while,
but
if
you're
not
using
templates
to
build
your
cards
in
the
back
end,
you're,
probably
spending
a
lot
of
frustrating
time
our
code
base
on
github
with
our
most
recent
session-
I
guess,
was
build
of
last
year,
so
things
like
that
and
always
like
to
shout
out
madewithcards.io
where
people
are
constantly
kind
of
submitting.
A
These
really
helpful
cards
that
just
it's
a
great
community
inspired
and
community
run
website
that
lets
people
share
common
scenarios
and
and
neat
things
they've
built
with
adaptive
cards.
Bunch
of
other
m365
developer
community
calls
exist
so
check
those
out
if
you
haven't,
and
this
recording
will
be
up
on
youtube,
usually
within
a
couple
days,
and
we
try
and
write
a
blog
post
associated
with
it.
The
next
call
will
be
april.
8Th
at
9
am
so
the
same
exact
time.
A
B
B
A
I
A
Yeah
that
question
came
up
earlier
and
I
had
mentioned
that
we
have
a
chat
with
your
team.
I
think,
set
up
for
next
monday,
where
we
can
talk
about
that,
but
yeah.
That
would
be
great.
They
were
asking-
and
I
I
suggested
they
just
post
on
github
with
that
question
and
keep
an
eye
on
github
for
when
it
would
be
available
in
the
react
native
renderer
sure
that
will
be
really
great.
If
it's
a
technique
next
week
on
call.
D
A
That's
a
great
question
I'll
take
a
stab
at
it.
We
we
hope
so
our
goal
and
why
we're
calling
it
the
universal
action
model
teams
and
outlook
are
really
just
a
starting
point.
The
protocol
is
open-ended
enough
that
it
can
even
work
on
non-microsoft.
So
I
don't
know
if
anyone
from
cisco
is
on
the
call
today,
but
you
know
our
our
hope
is
that
we
design
it
in
such
a
way
and
we
will
make
it
as
easy
as
possible
for
other
channels
to
be
supported,
whether
they're
in
microsoft,
365
or
whether
they're
outside
of
it.
A
That
is
the
that
is
the
the
hope.
How
easy
it
is.
That's
an
open-ended
question.
The
sdk
support,
specifically
for
kind
of
implementing
your
own
channel
and
and
things
like
that.
That's
it
will
most
likely
especially
early
on
right
now,
it'll
be
a
lot
of
heavy
heavy
lifting,
not
a
ton
of
work,
but
you
would
be
kind
of
on
your
own.
A
So
yeah
you
should
be
able
to
I'm
gonna
speak
somewhat
outside
of
my
own
area
of
expertise,
but
any
bot
if
it's
a
microsoft,
bot,
there's
what's
known
as
a
direct
line
channel,
which
just
gives
you
raw
raw
access
to
to
the
activity
feed.
You
can
post
things.
So
that
is
typically,
I
think,
how
they
recommend
just
getting
access
to
it,
but
that
that
should
that
should
work.
D
But
well
in
past
the
the
bot
framework
was
all
only
sending
well,
it
was
only
communicating
between
one
one
instance,
so
with
you,
so
your
bot
was
communicating
with
teams,
and
now
they
change
that
so
the
bot
framework,
so
your
bot
can
effectively
talk
to
multiple
channels
at
once.
I'm
not
sure
if
that's
rolled
out
everywhere
and
if
that
works
for
any
channel,
basically.
F
D
A
Is
a
new
activity
type
that
david?
I
think
on
the
call.
I
don't
know
if
there's
anyone
else
from
the
bot
framework
team,
but
there
is
a
new
activity
type
that
flows
through,
but
it's
generally
the
same
protocol
like
it
would
flow
through
direct
line
and
with
just
a
new
activity
type,
which
is
an
action
execute
which
has
the
metadata
and
things
like
that.
E
A
J
A
Cool
yeah:
well,
thanks
everyone.
Let
me
just
kind
of
close
this
here,
I'll
at
least
stop
the
recording.
I
can
hang
out
for
a
little
bit
longer
if
there
are
additional
questions,
but
I
did
just
want
to
kind
of
wrap
up
the
recording.
I
really
appreciate
everyone
jumping
on
the
call,
especially
quran
and
chiliditia,
for
sharing
that
stuff
and
it's
cool
one
month
from
now,
one
month-ish
within
the
next
month,
or
so
you
should
start
to
be
able
to
use
all
this
stuff,
and
so
that's
an
exciting
moment.