►
Description
During this 42-minute developer-focused demo, Shiladitya Saha and Karan Thapar thoroughly explain the new Action.Execute action type that synchronizes activity (payload) in the back-end while rendering cards natively in Teams and Outlook front-ends. Also shown - Contextual views in Teams bots/adaptive cards - individualized cards by role and Sequential Workflows support on Teams - progress through a multi-step process in a single adaptive card using auto invoke and synchronized refresh capabilities. Look for Action.Execute in Schema 1.4 and capability support by Teams and Outlook in mid-April. This demo is taken from the Adaptive Cards community call - March 2021, recorded on March 11, 2021.
Demo Presenters:
• Shiladitya Saha (Microsoft - Teams)
• Karan Thapar (Microsoft - Outlook)
Supporting materials:
• https://github.com/Microsoft/AdaptiveCards/issues/2268
Learn more:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog
A
Thanks
all
for
joining,
it's
wonderful
to
have
you
all
on
the
call
with
us
today
we'll
talk
about
how
universal
actions
our
newest
feature
in
adaptive
cards
help
you
elevate
your
end
user
experiences
on
both
teams
and
outlook.
I
am
current.
I
am
a
product
manager
in
outlook
and
I
am
joined
by
srila
dithya,
who
is
my
peer
from
teams.
A
C
A
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.
A
A
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.
A
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.
A
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,
dot,
http
or
action
dot
submit.
A
A
So
if
you
were
to
acknowledge
content
from
teams
that
acknowledgement
wouldn't
really
get
reflected
on
outlook,
or
vice
versa,
because
these
were
two
completely
separate
and
independent
apps
and
for
an
I.t
admin.
This
implied
complexity
in
deploying
and
managing
disparate
applications
across
an
enterprise
because
they
had
to
manage
multiple
layers
of
applications
due
to
the
inconsistent
action
model,
and
we
thought
why
not
give
it
a
shot
to
unify
these
experiences
across
teams
and
outlook
and
come
up
with
a
universal
action
model.
A
A
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.
A
A
A
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.
A
A
A
A
A
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.
E
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.
C
Yeah
not
to
overuse
my
soonish
joke,
so
the
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.
C
E
C
A
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.
A
Now
we
have
another
sought
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
cat
to
provide
him
the
requisite
approvals
again.
Cat
thanks
to
adaptive
cards
receives
an
actionable
email
in
outlook.
A
A
A
F
G
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
running
this.
This
instant
update,
you
know,
activity
that
you're
talking
about
is.
Is
this
a
new
behavior
that
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.
D
Yeah
we
have
a
question
in
in
chat
and
I
was
discussing
that
was
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?
C
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.
C
D
B
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,
the
channel,
for
example,
group
chat.
B
B
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?
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
can
now
get
differentiated
information
and
actions.
B
B
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
view
details.
B
H
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
have
logged
into
three
different
user
accounts
of
megans
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
B
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
talk
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.
B
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
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?
B
B
B
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
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.
B
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.
B
B
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.
B
B
Now.
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
there.
So
that
is
essentially
how
this
works.
G
B
Yeah,
so
that
is
the
limitation
today
and
we
are
actually
increasing
that
and
when
we
sometime
next
month
when
we
go
ga
you'd
be
able
to
see
like
that
number
going
up
earlier
when
we
talked
last,
we
have
like
currently
in
f3u
we're
keeping
that
number
down
as
five
where
you
can
test
out
your
scenarios
and
we're
planning
to
increase
that
number.
When
you're,
when
we'll
be
going.
B
A
So
I
can
get
some
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
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.
B
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
leg
work
there
so
because
of
this
different
model.
That
is
why
you
were
having
to
define
and
handle
two
endpoints
separately
for
teams
and
outlook.
B
B
B
B
B
C
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.
C
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.
So
we
really
hope
to
see
you
there
send
it
to
your
friends
and
and
we'll
keep
keep
doing
these
and
with
that
yeah.
Let's
talk
about
what
people,
if
you
have
any
feedback
for
for
the
team,
sure.
A
C
I
C
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.
D
C
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.
C
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.
F
C
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
I'm
not
sure,
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.
D
C
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.