►
From YouTube: Adaptive Cards community call – April 2021
Description
Agenda for this month’s community call: 1) Take a lap around the Company Communicator app and 2) Learn about Microsoft Teams rollout updates – capabilities and delivery estimates. Capability updates include: Full width Adaptive Cards, Static Autocomplete, Search with Adaptive Cards, Information Masking, Person Component, Input validation and labels, ActionSet Flyout (Overflow), People Picker, and New Universal Action Model v1.4 including contextual views = Universal Adaptive Cards. A lively 10-minute Q&A at the end of call. The call was hosted by Matt Hidinger (Microsoft). Presenters include Mykhailo Sydorchuk (Microsoft) and Ojasvi Choudhary (Microsoft). Recorded on April 8, 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 - May 13th at 09:00am PDT
B
A
2021
we're
almost
two
and
a
half
years
into
these,
so
I
appreciate
you
all
taking
time
out
of
your
day
to
join
us.
We
I'm
matt
heidinger
I'll,
be
your
your
host,
but
really
I'll
be
in
the
background
today,
because
we've
got
two
guest
speakers:
we've
got
mikailo
kylo,
hopefully
I'll,
try
and
say
it
better.
A
As
I
get
to
know
him
better,
he's
gonna
show
us
the
company
communicator
app
that
his
that
his
team
has
built
heavily,
takes
advantage
of
adaptive
cards,
so
that'll
be
a
kind
of
cool
case
study,
we'll
dive
into
and
he'll
show
a
demo
of
that
and
then
odyssey
you've
seen
a
bunch
of
times
on
here.
Talking
about
teams
updates,
we've
got
some
cool
stuff
to
share.
Regarding
teams.
Some
stuff
went
from
dev
preview
to
ga
and
I
think
we'll
see
some
live
demos
from
that
today.
A
C
Perfect,
thank
you.
Matt
hi
everyone.
My
name
is
muharrasuk.
I
am
senior
program
manager
in
microsoft,
digital
employee
experiences,
team
productivity,
gosh,
that's
a
mouthful
and,
as
matt
mentioned,
the
company
communicator
app,
which
I'm
going
to
walk
through
today
and
do
the
demo
it's
all
about
the
adaptive
parts.
So
actually
this
solution,
it
was
built
by
the
product
group
and
it's
provided
to
all
of
you
through
the
github.
So
there
is
a
set
of
teamstab
templates
and
company.
Communicator
is
just
one
of
those
templates.
C
So
what
does
the
solution
do
so?
The
main
goal
of
the
company
communicator
is
to
enable
communicators
to
create
and
send
messages
intended
for
multiple
teams
for
large
audiences
inside
of
their
organizations
and
to
send
those
messages
in
teams
through
chat
or
channels
and
to
reach
employees
right
where
they
collaborate,
meaning
in
teams.
C
The
original
template
was
had
to
be
a
little
bit
adjusted
to
be
used
inside
of
microsoft
and
the
main
changes
that
we
made
were
including
supports
of
multiple
apps
and
bots,
so
the
original
template
only
could
handle
a
single
austrian
dashboard
and
a
single
communicator
bot
and
inside
of
microsoft.
Obviously
we
have
multiple
communication
teams
and
also
multiple
divisions
which
have
a
need
to
have
their
own
way
to
communicate
with
their
users,
and
because
of
that,
we
have
extended
the
solution
to
or
utilize
multiple
multiple
communication
channels.
C
Also,
our
communications
team.
They
not
always
have
a
need
to
send
to
adl
or
a
list
of
team
members
so
because
of
that
they
sometimes
are
sending
to
some
custom
list
of
recipients.
So
because
of
that,
we've
also
extended
the
solution
to
take
a
custom
csv
file
as
an
input
and
then
process
all
those
users
as
recipients.
C
Another
change
was
full
support
for
custom
adaptive
cards,
so
the
initial
template
it
just
had
a
couple
of
fields
which
the
communicators
fill
in
and
based
on
that
data.
The
adaptive
card
is
created,
but
that
was
not
sufficient
because
I'll
show
you
during
the
demo
later,
but
we
had
a
need
to
send
more
customized
messages
and
full
support
of
adaptive
cards
could
cover
that
because,
as
you
know,
adaptive
cards
can
be
whatever
you
want
them
to
be.
C
Another
change
is
direct
image
embedding
so
by
default
of
the
solution
supported
image
embedding
using
the
url.
However,
sometimes
communication
teams
have
a
need
to
secure
the
image,
so
the
image
is
not
exposed
publicly
and
we
have
figured
a
way
to
directly
embed
the
card,
the
image
into
the
card
and
then
send
it
to
all
recipients.
C
So
the
image
is
not
available
by
publicly
successful
url
and
the
last
but
not
least,
change
is
programmatic
message
sending
via
api.
So
right
now
we've
been.
We
are
thinking
about
company
communicator
as
truly
as
a
platform
and
right
now
the
solution
can
be
extended
and
how
other
apps
or
services
tapping
into
it
and
sending
messages
through
the
centralized
platforms
that
we
control,
that
we
have
ordered
for
and
utilizes
technology
to
send
messages
in
teams
to
target
recipients.
C
Is
the
internal
microsoft
dog
footing
program
where
users
are
testing
new
features,
and
we
did
an
original
round
and
majority
of
users
have
shown
an
interest
to
receiving
communication
in
teams
versus
just
email.
So
we
went
ahead.
We've
started
the
project,
implemented
the
changes
and
then
we've
started
like
the
full-blown
pilot
program
with
elite,
and
we
had
600
members
enrolled
in
the
program.
C
We
send
them
multiple
messages
and
you
can
see
the
example
of
those
messages
on
the
screenshot,
so
the
messages
were
around
teams,
best
practices,
just
elite
program,
overview
company,
communicator
details
and
so
on.
So,
overall,
the
performance
of
the
solution
was
that
we've
been
able
to
send
600
messages
under
one
minute
and
100
success
rate
for
all
of
the
users
who
had
the
bot
enabled
or
like
pushed
them.
So
what
did
we
learn
from
from
the
elite
program?
C
97
of
respondents
were
satisfied
with
receiving
communications
via
chat,
and
also
I've
been
really
curious
to
hear
if
the
communication
through
teams
is
disruptive
or
not
disruptive
for
the
users
and
the
majority
of
responders,
like
67
percent,
would
want
to
receive
communication
in
chat
at
least
two
to
three
times
a
week,
so
the
users.
So
what?
But
so
the
conclusion
that
you
made
the
users
are
very
open
to
receive
communication
in
teams
and
adopt
these
like
new
ways
of
working
and
shifting
their
workloads
fully
into
teams.
C
The
second
part
of
the
app
is
the
authoring
dashboard
and
it
is
used
by
communication
managers
to
craft
and
send
messages
to
their
target
audiences,
so
I'm
environment
right
now
and
I'll
just
create
a
new
message
and
show
you
how
that
initial
screen
looks.
So
we
have
a
couple
of
fields
and
the
fields
are
pretty
intuitive.
So
we
have
title.
We
can
upload
an
embed
image,
summary
author
and
we
can
also
add
the
button
to
the
card
and
on
the
right
side
we
can
see
the
card
previous
of
the
communication
teams.
C
C
We
have
employee
town
hall
today,
so
it's
a
really
good
use
case
for
hr
team
to
remind
all
users
that
there
is
an
important
event
in
the
company
and
the
event
is
coming
today
note
about
the
image.
So
we
can
embed
the
image
using
the
direct
url
to
the
image
and
also
we
can
upload
the
image
and
by
image
upload.
Actually
what
we
are
doing.
We
are
a
base64
encoding,
the
image
and
then
storing
the
image
in
in
the
bot
database.
C
So
then
we
can
use
this
encoded
string
and
embed
it
directly
into
the
card,
and
by
doing
so
the
image
does
not
go
outside
of
the
one
environment
and
all
the
users
have
would
receive
the
image
directly
in
their
card.
In
terms
of
the
button.
We
cannot
specify
the
url
and
then
button
title
and
this
button
will
be
displayed
to
all
recipients.
C
Then,
second,
after
we
have
composed
the
message
we
need
to
define,
we
will
be
receiving
the
message
and
we
have
multiple
options
here.
So
we
can
send
the
message
to
the
general
channel
of
the
specific
teams
we
can
send
in
chat
to
specific
people,
meaning
members
of
the
team,
so
over
here,
I'm
just
going
to
send
it
to
all
members
of
hr
users.
Mass
team,
other
options
are
sending
to
m65
group
distribution
group
security
group,
and
then
we
can
also
upload
the
custom
cc
file
and
process
all
recipients.
C
Last
option
is
sending
in
chat
to
everyone
who
are
in
scope
of
the
spot.
So
I'm
just
going
to
go
ahead
and
send
it
to
you.
My
hr
users
team,
save
it
as
draft
after
it
save
this
draft.
We
can
also
preview
the
card
in
the
general
channel
of
the
team
just
go
here,
and
this
is
my
card,
so
looks
good,
yup.
C
Once
the
message
is
sent
on
the
back
end,
editor
data
function,
processes,
the
message
and
just
triggers
the
bot
message
to
all
target
recipients
in
scope,
and
I
just
got
a
message
from
a
company
communicator
app-
and
here
is
my
message.
So
the
app
is
very
straightforward
and
like
the
target
audience
is
a
communication
manager.
So
it's
very
intuitive
and
easy
to
use.
C
C
Thanks
for
providing
that
matt,
this
loves
this
designer
we've
been
using
it
a
lot,
and
I
can
tell
you
how
many
times
have
you
been
using
this
specific
card?
So
I'm
just
copying
the
card
payload
going
back
to
to
the
bot
facing
it
here
and
boom,
exactly
as
it
was
in
the
designer.
So
it's
the
beauty
of
adaptive
card
that
we
can
reuse
them
in
this
solution
as
well.
C
Sending
again
one
additional
verification:
parent
descent,
oh
and
by
the
way
after
the
message
was
processed,
we
can
also
download
the
report
and
see
like
how
much
time
it
would
take
to
send
the
message,
failure
and
success
rates,
and
we
can
also
expert
detailed
results
which
would
include
all
users
who
had
been
processed
and
their
respective
status
of
the
communication
and
going
back
to
the
general
channel
of
our
hr
authors
team.
So
this
is
the
card
which
was
sent
to
the
bottom,
just
a
quick
touch
on
the
technology
behind
the
scenes.
C
So
it's
available
again
in
the
in
the
github
template.
But
in
order
to
compose
this,
like
default
adaptive
card,
we're
just
using
adaptive
cards
library
and
based
on
the
information
that
the
users
had
input
like
title
image,
link,
summary
author
and
so
on,
we
are
just
creating
adaptive
card
and
adaptive
card
creator.
It's
again
like
we
are
utilizing
the
that
card
library
and
we
are
just
taking
the
values
provided
by
by
the
communications
team
and
composing
the
card
from
them.
C
A
A
A
So
if
anyone
did
not
get
a
question
answered,
why
don't
you
feel
free
to
go
ahead
and
put
your
hand
up
right
now,
and
then
we
can
talk
it
over
on
on
the
audio
and
if
we
missed
your
chat
or
someone
hasn't
helped,
you
just
go
ahead
and
ping
it
and
and
we'll
we'll
get
through
I'll.
Try
I'm
trying
to
scroll
through
it
live,
but
it's
also
a
little
tricky
with
all
the
stuff
going
on
so
yeah
mikailo.
Do
you
want
to
explain
a
little
bit
about
the
base64
encoding.
C
Yeah
absolutely
so,
the
image
is
just
encoded
into
basics,
the
first
string
and
stored
in
the
database
and
then
embedded
into
the
card.
But
obviously
we
are
subject
to
the
adaptive
card,
size
limitations.
So
we
every
time
we
need
to
make
sure
that
the
encoded
image
is
still
up
to
that
size
limit
and
because
of
that
we
have
noticed
a
somewhat
drop
in
the
image
quality.
But
unfortunately
we
have
to
just
leave
with
that.
C
A
D
So
I
think
nikita
replied
in
the
chat,
so
28
is
the
max
kilobyte
for
the
message
size
within
teams
and
I
think
the
adaptive
card
payload
is
limited
to
16.
So
we
are
definitely
working
on
expanding
that
in
the
future,
yeah.
So
we're
taking
that
up
as
a
work
item
in
kyoto.
So
hopefully
we
can
address
it
by
q3.
A
C
A
Really
often,
I
saw
someone
suggesting
a
potential
warning
in
the
designer
itself
that
if
we
do
exceed
the
payload
limit,
I
think
that's
a
really
good
suggestion.
It's
come
up
a
handful
of
times,
but
I
I
think
it
is
one
of
those
ones
that
I
would
start
to
argue
for.
We
do
have
a
pretty
large
backlog
with
our
limited
team,
but
that
one
I
I
do
agree
that
it
does
generate
a
lot
of
questions
and
and
stuff
and
and
just
confusion
which
is
the
worst
part,
because
you
don't
really
know
why
it
failed.
A
The
quick
question
I
had
too
on
that
for
for
really
the
room
and
feel
free
to
add
in
the
chat
and
also
mikailo,
we've
talked
about
adding
authenticated
image,
support
to
say,
sharepoint
urls,
basically,
things
that
are
within
your
same
tenant
so
that
we
could
technically
use
the
same
auth
that
you're
logged
into
with
teams.
Would
that
meet
a
lot
of
the
needs?
Would
it
meet
half
of
the
image
needs?
I
mean
a
lot
of
these
images.
Are
they
coming
from
an
internal
sharepoint?
A
That's
within
your
same
tenant,
or
are
they
sometimes
out
of
completely
different
places
at
which
point
you
know
base
64
might
be
the
way
to
go.
I'm
curious
how
much
we
should
prioritize
how
easily
we
can
reference
technically
secured
images,
but
they're
at
least
still
within
the
same
tenant.
So
if
people
want
to
just
kind
of
comment
on
chat,
that
would
be
nice
for
us
to
have
some
context
on.
E
And
matt,
just
one
point
I
want
to
make
for
for
the
designer
aspect:
is
we?
The
designer
is
also
open
source.
So
if,
if
folks
do
feel
like
hey,
I
feel
like.
I
have
some
expertise
here
and
I
could
jump
in
and
help.
We
do
welcome
pull
requests
and
people
jumping
in
to
help
out
because
it
is
an
open
source
project.
So,
if
you
do
want
to
help
out
and
get
some
contributions
in
there,
please
feel
free
to
reach
out
to
us
and
we
can
start
helping.
A
Absolutely
that'd
be
a
nice
one
to
to
get
your
feet
wet
in
the
adaptive
cards.
Library,
cool!
Well,
thank
you!
So
much
mikailo
I
I
know
you
said
you
had
a
kind
of
hard
stop
at
9
30.
So
people
get
your
questions
in
like
right
now,
if
you
can
but
also
reach
out
to
us
afterwards
or
if
you
have
any
other
thoughts
or
feedback
and
we
can
route
them
appropriately,
but.
C
Another
note
so
like,
as
I
was
just
doing
this
demo,
I've
got
a
new
message
from
the
our
internal
company,
communicator
pilot,
so
I'll
just
share
on
my
screen
really
quickly
and
show
you
how
of
that
looks
internally.
So
the
other
difference
that
this
is
no
reply
bot
and
we
cannot
respond
to
the
bot.
But
this
is
the
message.
I've
just
got
about
a
new
feature
in
in
teams,
so
there
are,
like
other
other
messages.
I've
been
getting.
So
this
is
how
it
looks
in
in
the
production,
environment.
A
D
A
A
D
Sounds
good,
okay
yeah,
so
this
is
filled
with
adaptive
cards.
We
had,
I
think,
spoken
about
this
last
time.
In
terms
of
where
you
know.
Definitely
a
very
neat
feature,
just
a
very
simple
feature
in
terms
of
like
making
your
cards
look
good
and
using
all
that
extra
real
estate.
It
is
now
generally
available,
so
we've
been
talking
about
it
for
some
time,
but
you
can
go
ahead
and
use
it
if
you'd
like
to-
and
it's
it's
it's
it's
very
simple.
D
It's
just
there's
just
one
property.
It's
ms
teams
with
equals
full,
and
that's
really
all
you
need
to
do,
and
I
I
think
in
a
certain
sense,
that's
like
the
beauty
of
adaptive
cards
that
you
know.
All
of
these
features
are
just
to
leverage
this
in
your
existing
cards.
You
really
don't
have
to
do
much.
D
You
know-
and
I
hope
that
continues
to
scale
as
we
add
more
and
more
features
awesome.
The
next
one
is
static
autocomplete.
So
you
know
this.
One
again
comes
very
handy.
If
you've
got
like
a
bunch
of
information
going
through,
you
know,
let's
say:
you've
got
like
50
hundred
or
different
elements
within
your
choice
set.
You
can't
meaningfully
expect
the
user
to
start
scrolling
through
all
of
them
right,
so
you
can
take
an
existing
choice
set
and
without
having
to
do
anything.
D
You
can
basically
just
go
ahead
and
add
this
property
first,
like
style,
equals
filtered,
and
you
have
static
audio
complete
again.
Very
simple.
You
just
need
to
make
sure
is
multi
select
is
false
for
this
particular
case,
but
other
than
that
right,
like
you,
can
use
static
autocomplete
within
your
cards
for
teams
today,
because
now
this
is
also
generally
available.
B
D
D
So
it
says
loading
results
from
bots
from
bot,
which
is
essentially
what
it's
doing,
and
I
mean,
like
you-
have
a
feature
like
static
autocomplete
today,
but
tomorrow
this
I
think,
is
going
to
be
super
super
powerful
because
any
like
you
have
basically
over
here,
like
a
full
search
based
front
end
inside
an
adaptive
card
for
your
application
and
teams.
I
think
this
is
going
to
go
a
long
way
for
people,
and
this
is
right
now
in
in
our
zero,
which
means
it's
in
our
one
of
our
lower
rings.
A
A
Teams
is
rolling
ahead
and
basically
getting
early
access
into
what
will
become
version,
1.5
features
of
adaptive
cards
so
1.3
we
had
a
bunch
of
input,
validation,
1.4.
We
added
the
universal
action
model
which
we
shared
last
month,
and
I
think
that
just
some
stuff
went
to
ga
and
teams.
I
don't
know
just
see
if
you're
going
to
cover
some
of
that
later.
D
So
this
one
is
information
masking,
and
this
is
basically
a
you
know,
style
equals
password,
and
what
this
allows
to
do
is
that
if
you
have
a
user
who
wants
to
send
some
sensitive
information,
like
you
know,
some
probably
like
some
sort
of
a
password
update
scenario,
they
can
go
ahead
and
use
this
field
for
updating
it.
In
fact,
and
now
this
is
also
in
depth
preview
and
I
think
matt.
This
is
one
of
those
where
I
have
a
demo
as
well,
so
I'm
trying
to
bring.
D
Yeah
awesome,
okay,
so
I'm
gonna
go
ahead
and
take
the
screenshot
away
from
you.
Okay,
so
here
it
is
it's
a
simple
card:
I'm
using
it
inside
a
message.
Extension
this
one.
Actually,
this
full
flow-
I
mean,
I
guess,
yeah
it.
It
would
probably
work
within
a
message.
Extension
too,
but
you'd.
I
idly
wanted
from
a
bot
right.
You
don't
want
to
sending
your
passwords
to
a
user
over
here.
You
have
a
feel
for
password
and
then
you
can
see
as
I
toggle
through
and
then
it
goes
away.
D
Oh
and
it's
covered
and
it's
secretive
and
then
when
I
can
toggle
back
it's
visible
so
right
now
you
can
go
ahead
and
try
this,
and
this
is
available
in
depth
preview.
Today
and
it's
you
know
it's
working
and
we
expect
to
roll
this
out
to
ji.
Definitely
before
build
so
within
the
next
within
the
next
month
or
so
yeah
awesome.
D
A
D
So
next
we
have
the
person
component
this
coming
soon.
I
think
this
one
we've
spoken
about
in
the
past.
The
intention
over
here
is
and
I'll
I'll.
Let
matt
do
his
his
this
pitch
for
adaptive
competence
all
up,
but
this
is
like
the
first
adaptive
component,
where
basically
we're
taking
certain
graph
entities.
D
If
there
are
more
people
than
what
is
supported
inside,
let's
say
if
there
are
seven
or
eight
people,
and
you
don't
have
as
much
space,
then
we'll
sort
of
like
remove
the
name,
but
if
there
are,
but
if
there
is
enough
space,
then
you
know
if
that
is
just
a
single
person
that
may
well
show
the
name.
So
like
properties
like
these,
which
you
know,
if
you
were
to
implement
them
within
javascript,
it
would
take
you
yeah.
D
It
would
take
some
amount
of
effort
and
you'd
probably
have
to
figure
out
how
to
like
talk
to
graph
and
like
fetch
out
all
this
data,
and
you
know
fetch
the
image
of
the
person
and
all
of
that-
and
I
think
this
is
gonna-
go
a
long
way
in
terms
of
like
simplifying
a
powerful
scenario
like
this.
So
this
is
what
is
called
the
person
component
editor
matt.
Do
you
want
to
add.
A
A
What
is
the
name
of
the
component
you
want?
I
want
to
put
a
user,
I
want
to
put
a
file
in
there
and
then
all
you
have
to
provide
is
the
properties
of
that
that
thing,
so
a
file
will
have
different
properties,
and
what
these
match
is
the
shape
of,
in
this
case,
in
the
graph
components
it
just
maps
the
shape
of
the
api
calls
that
you
would
make
to
graph.
A
This
is
going
to
be
our
solution
for
that,
so
the
first
one's
going
to
light
up
in
teams,
it's
just
a
user
component
or
a
person
component.
It's
not
going
to
be
the
full
adaptive
component
model
that'll
come
in
version
1.6,
but
feel
free
to
take
a
look
at
that
and
give
us
feedback
as
as
we're
going
cool
all
right.
Let's
go
to
the
next
one,
and
this
one
is
the
validation
stuff.
So
take
it
away.
D
Yeah,
so
input
validation,
so
this
is
adaptive,
god's
1.3,
so
I
have
I
you
know.
Quite
frankly,
we
were
hoping
to
be
in
generally
available
with
this
one
today
by
the
time
I
spoke
this
one
so
matt
and
I
had
a
chat
and
we
had
planned
it
to
be
generally
available
in
in
april,
like,
unfortunately,
we're
not
gonna
be
able
to
make
it.
This
has
been
pushed
out
to
may.
A
Build
we
should
be
able
to
to
quickly
add
on
that.
So
in
again,
in
1.3,
we
we
did
that
input,
validation,
it's
very
straightforward,
there's
just
there's
is
required
properties
on
every
input.
There's
a
custom
error
message
that
you
can
provide
and
the
input
validation
will
just
work
as
you
expect
for
choice
sets
for
for
text
input.
We
have
additional
things
on
text,
for
example
like
regular
expressions,
so
just
getting
that
experience
right
on
all
the
platforms,
ios,
android
and
making
sure
they
work
in
all
the
teams.
A
Canvases
is
is
part
of
why
that's
delayed
a
little
bit,
but
you
can
get
a
feel
for
how
it
works.
I
guess
I
should
have
made
this
a
short
link,
but
so
apologies
for
that,
but
you
can
certainly
read
up
on
all
these
properties
and
you
can
technically
start
adding
them
today.
So
if
you
want
to
start
adding
required
validation,
you
can
drop
these
on
your
card.
These
properties
are
fully
backwards
compatible
except
for
label.
A
I
guess
I
should
say
that
as
well.
We
call
this
feature.
Input
validation,
but
it
really
was
a
big
input.
Update,
so
inputs
can
now
have.
Labels
makes
your
cards
significantly
more
verbose.
We
were
just
talking
about
the
payload
size
increase
with
base64
images,
and
labels
are
much
more
straightforward.
They
just
write
on
the
input
itself
so
rather
than
having
a
separate
text
block-
or
you
know
it
basically
does
reduce
your
json
size
and
it
just
makes
it
a
little
cleaner.
A
It
also
is
much
more
accessible
by
having
this
label
with
the
input,
this
new
property.
We
can
do
much
better
screen
reader
and
assistive
device
stuff
so
that
people
know
that
these
radio
buttons
are
associated
to
this
label,
whereas
you
don't
have
that
before.
So
it's
really
a
major
update
in
a
bunch
of
different
vectors,
not
only
for
user
experience
but
for
assistive
devices
as
well.
A
A
D
Action
set
fly
out,
so
this
is
one
that
you
know
many
times
over
here,
you'll
see
in
this
msdn
magazine
right.
You
have
a
core
set
of
asks
in
this
particular
bot,
where
you
probably
either
want
to
like
read
it
online.
So
it's
going
to
take
you
to
a
website
or
you
want
to
like
download
the
issue,
but
you,
your
application
or
your
card,
might
have
other
sets
of
actions
that
are
not
primarily
associated
with
the
card
right
over
here
like
we
have
the
example
for
copy
edit
or
delete.
D
Well,
I
mean
this
is
just
informational,
but
you
could
think
of
it
as
access.
My
account
right
or
access
a
previous
issue
or,
for
example,
for
the
for
the
magazine
over
here,
which
aren't
directly
related
to
the
use
cases.
You
definitely
wouldn't
want
to
like
give
them
prime
time
real
estate,
and
what
would
you
rather
do
with
them
and,
and
I
think,
an
action-
the
action
overflow
menu-
the
triple
load
menu
over
here
makes
perfect
sense
that
it's
a
industry-wide
construct.
You
know
a
lot
of
websites
supported.
D
Just
bringing
this
like
natural
interface
within
adaptive
cards
and
allowing
you
to
like
stack
your
actions
between
certain
primary
actions
that
you
want.
The
user
to
focus
on
versus,
like
certain
secondary
actions
are
important
or
you
would
like
to
be
there,
but
you
don't
necessarily
want
to
compromise
on
real
estate
because
with
gods,
it's
all
about
being.
You
know,
concise
and
to
the
point.
A
B
D
A
D
We
expected
to
be
at
least
in
developer
preview
by
build
this
year.
The
other
good
thing
is,
I
showed
you,
the
search
basically
search
and
adaptive
cards,
so
search
and
adaptive
cards
and
people
will
picker.
You
can
think
of
it
as
like
a
little
bit
of
complimentary
features
where
within
people
picker,
you
are
you're
using
the
native
people,
picker
option
that
is
provided
via
graph,
but
with
search
you
can
think
of
it
as
it's
basically
advanced
type
ahead,
but
like
the
back
end
could
be
your
crop
could
be
your
application.
D
D
It's
got
a
little
bit
of
image
because
you
know
we
can
pull
the
images
from
graph
and
we
can
share
some
extra
text
over
here.
The
full
search
that
we
that
I
showed
earlier.
The
intent
is
definitely
to
go
this
way
like
to
see.
If
we
can,
you
know
in
the
future,
maybe
add
images
or
like
a
secondary
line
or
stuff,
but
but
I
think
that
there's
like
a
ways
in
the
future,
but
you
know
two
methods
of
achieving
the
same
thing,
but
people
pick
her
in
general.
D
A
Yeah
absolutely-
and
there
was
a
quick
question
that
I
think
is
no,
but
then
I'm
going
to
ask:
does
the
people
pickers
support
groups?
No
yeah?
Okay,
I
didn't
think
so.
Oh
yeah,
and
this
just
shows
how
you
do
it
so
similar
to
the
the
component
model.
This
is
basically
how
you
opt
into
people
picker.
We
have
a
new
property
called
choices.data.
A
This
is
where
you
tell
us
where
the
data
comes
from
for
these
choices,
and
so,
if
you
just
want
a
query
from
your
bot
like
like,
we
showed
on
the
xbox
card
that
you're
just
basically
filtering
a
set
of
products
or
games
or
whatever
this
is
just
the
data
set,
is
whatever
you
want.
But
if
you
specify
the
data
set
of
graph.microsoft.com
users,
that's
teams
queue
and
other
apps
is
queue
to
pull
from
the
the
directory.
A
I
don't
think
we
show
it,
but
you
can
filter
it
to
say
the
current
context,
which,
if
you're
in
say
a
group
chat,
it'll,
be
able
to
filter
list
users
for
that
group
chat
or,
if
you're
in
a
channel.
So
we
do
have
the
ability
to
show
the
whole
directory
or
just
a
subset,
but
not
currently
a
group,
in
that
case
cool,
and
then
we
have
this
slide
in
here.
D
Where
you're
going
yeah,
yeah,
yeah
yeah,
so
switching
gears
a
little
bit
right
like
you,
this
is
the
adaptive
cards
community
call,
and
you
are
familiar
with
with
the
fact
that
adaptive
cards
are
available
on
outlook
teams.
Web
chart
cortana
your
own
applications
like
windows,
timeline
and
across
the
board
like
layout
and
rendering
is
consistent.
D
Action
handling
is
not,
and
you
have
probably
seen
this
slide
before
so
you
know
what's
coming
next,
so
so
we
have
the
current
and
consistent
action
model.
If
you
want
to
create
the
same
card
within
teams,
one
uses
action.submit
the
other
uses,
action.deep
http,
while
in
principle
and
in
spirit
you're
effectively
creating
basically
the
same
card.
You
have
to
do
something
slightly
different.
Now
the
new
universal
action
model
we
just
wanted
to
share
with
you.
It's
generally
available
right
now,
so
you
can
go
ahead
and
use
action.execute
and
it's
just
teams
right
in
just
teams.
D
A
And
so
the
the
big
update
here
is
that
it's,
it
went
ga
into
teams,
like
I
think
this
morning,
within
a
couple
days.
The
reason
I
I
I
went
through
it
kind
of
quickly
is
because
I
didn't
want
to
leave
some
time
for
q
a,
but
this
was
covered
in
detail
last
month.
So
I
I
totally
get
that
the
blog
is
behind.
That's
that's
my
fault.
That's
on
me,
but
the
m365
dev
channel
on
youtube
does
have
all
the
community
calls.
A
The
the
expectation
is
that
by
the
build
conference,
which
is
the
end
of
may
that
both
teams
and
outlook
will
be
on
1.4
and
you'll
be
able
to
start
using
all
this
stuff
in
ga.
So
if
you're
curious
on
more
of
the
universal
action
model
definitely
take,
I
think
we
answered
a
ton
of
questions.
It
also
adds
a
bunch
of
really
cool
features
like
role-based
views.
You
can
do
much
better
like
sequential
flows
and
actually,
oh
just
be
sorry.
Do
we
have
like
some
demos
here,
yeah.
A
D
If
you
have
a
manager
or
an
account
executive
versus,
they
probably
want
to
have
access
to
the
same
case,
but
one
probably
has
a
workflow
where
they
can
approve
or
deny
a
particular
workflow
and
the
other
one
cannot.
They
can
probably
just
request
it
and
view
it
right.
So
over
here
like
if
you
have
like
a
requester
versus
someone
who
has
the
power
like
marie,
who
is
danielle's
boss?
D
Who
has
the
power
to
like
you,
know,
approve,
reject
or
ask
for
more
details
with
regards
to
a
particular
request
like
she
can
do
it,
and
the
only
way
you
can
sort
of
support
this
within
the
same
adaptive
card
is
through
universal
actions
and
contextual
views.
So
contextual
views
are
in
developer
preview
today.
We
definitely
aim
for
this
to
be
in
generally
available
by
bill
the
sale
but
yeah
if
you
can
totally
go
and
check
this
out
today,
if
you'd
like
to.
A
A
D
A
Yeah,
I
think,
just
in
the
name
of
time
just
to
leave
time
for
q
a
we
will
share
all
this.
This
will
be
available,
but
this
is
really
just
showing
the
power
of
the
role-based
views
working,
not
only
in
teams.
So
if
you
have
a
certain
permission
over
the
card,
but
also
in
an
outlook,
so
a
lot
of
really
cool
stuff
there.
Let
me
really
briefly
say
so:
we
talked
a
little
bit
about
features.
I
saw
in
the
chat
a
lot
of
good
feature:
requests,
aka
dot.
A
Ms
slash
ac
roadmap
is
the
place
to
go
to
see
what
we're
working
on
what's
under
consideration
and
also
easily
vote
on
things.
All
we
need
is
an
email
address.
You
don't
create
an
account,
a
bunch
of
different
links,
check
out
the
adaptive
card
source
code.
If
you
want
to
help
us
with
some
of
those
designer
enhancements,
we
would
absolutely
welcome
those
prs
and
certainly
help
you
get
started
too.
A
There's
a
bunch
of
other
m365
developer
community
calls
I'll
show.
Those
here
definitely
check
those
out.
We
will
see
you
again
on
may
13th
at
9.
00
am
pst
second
thursday
of
every
month.
We'll
see
you
here
and
with
that,
I'm
going
to
switch
over
to
q
a
huge
thanks
to
odyssey
mikailo
for
sharing
this
stuff.
The
chat
was
super
active
today
we're
going
to
take
some
time
and
have
to
go
through
some
of
that.
A
But
if
you
didn't
get
an
answer
to
your
question
and
it
is
pressing,
please
feel
free
to
raise
your
hand
and
we'll
start
to
go
through
those
and
john.
I
know
you
are
following
along
some
of
the
other
folks
on
the
call
nikita
there's
some
adaptive
cards,
dev
team.
So
if
you
guys
want
to
also
tackle
some
of
these,
please
feel
free.
E
Thing
I
wanted
to
quickly
call
out.
I
tried
I
was
trying
to
be
follow
all
the
issues
people
having
on
chat.
If
I
wasn't
able
to
answer
your
question,
please
reach
out
into
our
github
repo
that
I
just
linked
and
file
some
issues
and
we
can
start
tracking
down
and
looking
at
some
of
the
issues
you're
having
with
cards
there.
So
once
again,
just
any
issues
you're
having
follow
them
in
github
and
we
can
start
communicating
there
and
start
tracking
them
down
and
try
and
solve
your
issues.
A
G
So
the
the
role-based
view
that
was
shown
earlier,
that
we
can
post
it
in
a
team's
channel
and
it
will
dynamically
show
the
end
user,
depending
on
their
role
the
actions
that
they
can
take
correct.
That's
the
kind
of
capability
we'll
be
getting
yes
awesome
great
and
has
anyone
looked
into
if
they're
waiting
for
an
adaptive
cad
response?
Is
there
a
scenario
that
that
somebody
might
have
already
come
to
again?
G
This
is
not
specifically
for
the
technical
team,
but
from
a
process
standpoint
I
have
been
like
I
I've
gotten
this
request
from
multiple
people
where
they
want
to
cancel
an
approval
in
between
the
flow,
because
the
user
who
you
sent
to
the
card
has
left
the
organization
is
on
a
long
week
or
an
emergency
leave.
So
has
anyone
looked
into
these
scenarios
where
we
can
in
the
middle
switch
the
flow
or
do
something
from
the
back
end
to
reassign
it
and
take
over
stand
over
adaptive
card
or
have
an
expiry
set
to
it?
G
G
D
A
Yeah
within
certainly
it
is,
and
and
tamash
on,
this
call
has
been
a
friend
of
ours
to
make
sure
we're
doing
what's
best
for
power
power,
users,
power,
automate
users,
I'm
not
actually
sure
what
the
latest
like
how
this
is
going
to
roll
out,
how
it's
going
to
expose
itself
through
a
flow.
So
we'll
probably
have
to
get
back
to
you
on
that.
I
know
there
are
threads
going
on,
though,
and
we've
been
talking
with
some
of
the
tomasz
as
a
power
platform
mvp
and
some
other
folks,
maybe
as
well.
A
H
So
I
think
you
probably
answered
what
you're
probably
going
to
just
repeat
yourself,
but
mine
was
just
making
sure,
with
everything
that's
being
showed,
with
teams
eventually
getting
to
the
1.4
with
that
post
to
adaptive
card
is
peoplepicker
the
action.execute
and
the
with
going
to
be
available,
and
also
with
that
action.execute.
When
that
updates.
Is
that
going
to
break
like
previous
power
automates
that
I
have
with
an
action.
H
H
C
A
A
A
D
H
A
Yeah
yeah
we'll
it's.
It's
definitely
we'll
be
keeping
that
in
mind
and
really
seeing
how
we
can
nail
these
these
experiences
once
we
get
them
in
teams
and
then
the
adaptive
cards
sdks
and
ideally
we'll
keep
the
power
automate
editions
as
close
to
the
raw
sdks
that
the
thing
is
they
will
require
kind
of
these
raw
sdks
that
were
that
we
are
still
baking
is,
is
the
kind
of
the
timeline
of
this
stuff.
H
Right
matt-
and
I
appreciate
you
know-
I
see
where
microsoft's
going
they're-
definitely
trying
to
make
it
where
hey
us
power
users.
We
can
pretty
much
like
do
it
without
having
to
tap
high
t
all
the
time,
because
they
don't
got
time
to
deal
with
what
the
business
needs
and
I'm
that
in
between
the
between
the
business
and
I.t.
A
F
A
Yeah,
absolutely
these
will
all
be
into
the
ssdks.
Well,
some
of
them
are
further
along.
Some
of
them
are
being
coded
up
as
we
speak
in
the
github
repo,
some
of
them.
We
haven't
fully
starred
on
yet,
but
we
don't
look
exact
timelines.
I
remember
last
month
it
was
definitely
like
soonish,
we're
still
figuring
out
the
etas
on
that,
but
yeah
aside
from
anything
that
starts
with,
like
ms
teams
like
this
they'll
be
coming
into
the
sdks
throughout
the
year.
A
Yes,
peoplepicker
will
the
only
thing
I'll
caveat
there
is.
We
are
hoping
to
come
up
with
a
plan
to
be
able
to
reuse
the
fluent
ui
controls.
We
don't
want
to
build
in
a
custom
people,
bigger
control
for
every
platform,
there's
some
logistics.
We
have
to
figure
out
with
that.
We're
not
sure
how
possible
that's
going
to
be
so
we
might
have
a
degraded
people
picker
experience
out
of
the
bare
bones
sdk.
A
It
might
not
be
as
full
feature
as
the
one
you
see
in
teams,
but
that's
the
general
adaptive
cards
thing
anyway.
You
know
we
use
what
the
platform
provides
for
ui
and
we
make
it
as
good
as
we
can
so
we're
still
going
to
figure
that
out,
but
I
expect
that
plan
to
start
to.
We
can
start
socializing
that
more
over
the
coming
months.
Thank
you.
Cool
saw
one
other
hand,
go
up
it's
hard
to
toggle
back
and
forth
between
the
chat
and
the
people
so
feel
free
to
unmute.
I
A
I
A
question
regarding:
do
you
guys
have
any
usage
data
so
a
lot
of
these
meetings?
We
tend
to
discuss
when
things
are
available
in
teams,
but
these
cards
can
be
used
on
other
platforms.
Do
you
have
any
idea
how
they're
actually
being
used
in
the
real
world?
Is
it
like
99
teams,
one
percent
everything
else.
A
I
don't,
I
definitely
don't
think
it's
that
we
have
access
to
microsoft,
platform
data,
so
t
we
know
how
many
cards
go
through
teams.
We
know
how
many
cards
get
delivered
through
outlook,
there's
quite
a
few
through
both
and
outlook.
We
also
track
how
many
actions
get
invoked
and
those
numbers
are
fantastic.
Like
the
the
the
people
getting
actionable
emails
who
haven't
moved,
you
know
completely
the
teams
or
a
lot
of
their
workflows
as
email
like
those
actionable
emails
have
been
significant
productivity
enhancers
for
users.
A
That
said,
we
do
not
have
telemetry
in
the
sdks
themselves.
So
if
someone
out
there
some
big
name
company,
some
small
startup,
is
using
our
libraries
to
render
adaptive
cards
on
ios
or
android.
We
will
have
no
idea
unless
they
reach
out
to
us,
which
is
a
bummer,
but
also
we
didn't
want
to
just
drop
random
telemetry
that
calls
into
microsoft
for
using
an
open
source
library.
So
we
we
made
what
I
believe
is
the
right
call
for
an
open
source
project,
but
it
does
mean
we're
limited.
A
As
far
as
you
know,
who,
who
in
the
greater
world
is,
is
using
adaptive
cards.
We
do
know
some
of
our
bigger
partners
on
the
call
that
join
us,
so
cisco
webex
uses
adaptive
cards
for
for
their
platform
as
well,
so
they
have
some
data
we've
announced
so
sap
uses
adaptive
cards.
We
don't
have
telemetry
for
either
of
those,
but
there
has
been
some
good,
broader
industry
adoption,
but
unless
they
tell
us
we
we
don't
really
know.
Thank
you
cool.
I
appreciate
such
a
lively
conversation.
A
Thank
you
all
for
joining
this
month,
we'll
we'll
scrub
the
chat.
Thank
you
for
everyone
who
helped
out
in
the
chat.
Thank
you,
jaspy
nikita
for
for
starting
to
share
some
of
the
more
teams
stuff,
and
I
appreciate
everything
you
guys
are
doing
with
adaptive
cards.
We
will
see
you
next
month.
Thank
you.
So.