►
From YouTube: Adaptive Cards community call – April 2022
Description
The following topics are covered in this month’s community call. Overview on Universal Actions + Messaging Extensions (elevating user experiences with Universal Actions and Messaging Extensions on Teams and Outlook – walkthrough capabilities and value propositions) - Karan Thapar (Microsoft), Accessibility Updates (Accessibility work and SDK v1.6 release) – J.P. Roca (Microsoft), and 15 minute live Q&A primarily focused on Universal Actions + Messaging Extensions. This call was hosted by J.P. Roca (Microsoft) | @jpthepm. Recorded on April 14, 2022.
Stay connected
• Twitter - https://twitter.com/microsoft365dev
• Blog - https://aka.ms/m365pnp/community/blog
• Recurrent Invite - https://aka.ms/adaptivecardscommunitycall
• Next call – May 12th at 09:00am PT
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365pnp
A
Welcome
to
the
adaptive
cards
community
call
for
april
2022.
if
you're
new
here
we
host
these
community
calls
every
second
thursday
of
the
month.
If
you
come
here,
often
welcome
back
today,
we
have
a
very
exciting
presentation,
with
our
friends
over
in
outlook
quran
he'll
be
presenting
about
universal
actions,
plus
messaging
extensions.
A
B
Thank
you
so
much
for
having
me
jp,
it's
fantastic
being
here
for
the
third
time
and
speaking
with
this
lovely
community.
All
right,
my
name
is
karan.
I
am
a
product
manager
from
third
party
content
and
experiences
platform
team.
What
does
our
team
stand
for?
Our
team
aims
to
empower
our
developer
partners,
like
all
of
you
to
better
bring
in
their
content
within
m365
ecosystem
and
enhance
the
experiences
that
you
deliver
for
your
end
users,
and
today
we
will
talk
about
two
of
the
many
ways
in
which
we
make
this
happen.
B
B
B
B
B
B
B
All
in
all,
the
actors
for
search
requests
need
to
take
an
action
just
once
within
the
hub
of
their
choice
and
magically
see
the
same
approval
getting
reflected
everywhere,
including
your
app
and
what's
in
the
best
interest
for
the
initiator
of
the
request.
Part
in
this
case
is
that
they
get
to
benefit
from
timely
approvals.
C
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
observes
that
one
of
the
boilers
at
a
remote
site
had
broken
down
and
files.
A
new
incident
through
contoso
report,
incident's
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.
C
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.
C
B
Before
we
proceed
ahead,
let
me
just
recap:
what
happened
here?
There
was
an
incident
that
was
created
and
the
card
for
that
rendered
differently
bases
the
different
views
that
were
assigned
to
personas
and
someone
who
has
the
ability
to
resolve.
This
incident
actually
took
an
action
in
outlook,
not
in
teams
but
in
outlook
and
the
very
same
action
that
resolution
got
reflected
in
teams
as
well.
B
That's
the
part
that
summarizes
universal
actions,
so
an
action
that
happens
in
outlook
renders
beautifully
and
gets
updated
in
teams
as
well,
and
as
far
as
the
contextual
views
are
concerned,
we
could
see
the
cards
getting
rendered
differently
for
different
actors.
In
this
scenario,
the
last
key
universal
actions
capability
that
we
would
want
to
talk
about
is
sequential
workflows.
B
These
aren't
a
single
click
actions
and
rather
entail
complete
workflows
and
in
the
earlier
model
we
would
see
that,
upon
acting
on
a
single
card,
the
bot
that
we
are
interacting
with
would
send
another
card,
and
this
kind
of
conversation
model
would
end
up
consuming
the
entire
real
estate
on
our
viewport
and
to
enhance
the
experiences
for
our
end
users.
We
came
up
with
this
capability
of
sequential
workflows,
wherein
the
same
card
continues
to
get
updated
upon
different
actions
and
to
illustrate
this
visually.
B
B
B
B
B
B
So
imagine
you
dealing
with
a
work
item
that
you
would
want
to
socialize
and
publish
within
your
team.
You
can
click
on
the
control
source
icon
at
the
bottom
of
your
teams.
Chart
select
the
work
item
and
what
you
would
see
is
a
beautiful
and
delightful
card
getting
inserted
in
the
chat
window
and
again.
Needless
to
say,
this
is
a
welcome
change
from
the
earlier
paradigm,
where
we
would
typically
paste
links
to
these
work
items.
B
Now
you
can
make
these
experiences
a
lot
richer
by
being
able
to
share
cards
rather
than
just
plain
urls,
and
as
soon
as
you
send
chart
chart
message.
What
actually
gets
delivered
to
the
users
is
a
card
wherein
the
users
can
have
buttons
to
view
additional
details
or
to
complete
certain
other
actions,
and
when
we
talk
about
actionable
messaging
extensions,
we
take
this
a
step
further
and
enable
our
users
to
also
create
content
on
the
fly
and
the
recipients
of
these.
To
take
multiple
other
actions.
B
B
B
The
second
key
benefit
for
using
adaptive
cards
are
the
faster
approvals
that,
in
a
way,
lead
to
monetary
savings
as
well.
We
have
data
that
suggests
that
adaptive
cards
lead
to
close
to
an
8
million
dollar
saving
every
year
by
saving
late
credit
card
fee,
as
the
approvers
of
these
expense
requests
are
empowered
to
act
quickly.
B
This
is
a
very
high
level
call
to
action.
Our
request
would
be
to
start
envisioning
scenarios
think
how
adaptive
cards
can
help
you
and
your
users
to
better
their
day-to-day
lives,
then
go
ahead
and
design
and
build
these
adaptive
cards.
We
have
linked
our
developer,
documentation
that
details
the
process
of
creating
and
building
an
adaptive
card,
and
the
third
essential
element
here
would
be
to
have
an
azure
bot
setup
that
would
actually
communicate
with
the
emails
in
outlook
and
the
chat
messages
in
teams.
B
A
Really
appreciate
it,
for
those
that
don't
know
today
is
actually
a
holiday
in
in
idc,
so
quran
took
the
time
out
of
his
holiday
to
to
hop
on
this
call.
We
really
appreciate
that
quran.
This
is
this
is
great
and
the
chat
is
very
excited.
They
have
a
ton
of
questions.
So
let
me
just
go
ahead
and
briefly
talk
about
the
next
section,
so
we
can
jump
right
into
the
q
a
and
get
all
these
questions
answered.
A
So
one
of
the
things
that
I
wanted
to
talk
about
were
some
accessibility
updates
that
our
team
has
been
performing.
As
you
may
know,
our
recent
release
of
the
sdk
version
1.5
that
was
our
most
recent
release
and
that
happened
in
october
of
last
year.
So
it's
been
quite
a
bit
since
we've
released
a
new
sdk
for
adaptive
cards.
A
lot
of
this
has
been
due
to
delays
that
our
team
has
experienced,
with
working
with
accessibility,
we're
really
trying
to
make
adaptive
cards
accessible
everywhere
and
going
forward.
A
Our
team
is
working
on
closing
a
ton
of
bugs
whether
it
be
on
the
website
or
our
different
renders,
and
once
we
get
this
accessibility
story
ironed
out
and
and
have
a
better,
more
accessible
experience
for
adaptive
cards.
We
will
share
more
updates
regarding
our
version
1.6
release
right
now.
I
can't
mention
or
commit
to
to
a
date,
but
we're
really
hoping
to
get
it
out
within
the
next
couple
of
months,
and
that
was
it
for
me.
We
can
hop
straight
into
the
q,
a
and
I'll
go
back
to
the
teams
chat.
A
B
A
B
So
jp,
that's
a
great
question
now.
What
I
would
suggest
is
that,
if
your
scenario
is
one
that
deals
with
a
global
scope,
so
if
you
are
an
isv,
then
the
party
that
approves
your
registrations
is
microsoft,
so
feel
free
to
develop
these
solutions.
These
solutions
come
to
us
for
an
approval.
We
review
those
registrations
and
approve
them
and
you
may
not
be
required
to
go
and
visit
urit
admins
microsoft
would
serve
as
the
authority
that
reviews
and
approves
these
integrations.
A
Thank
you
there's
also
a
a
lot
of
discussion
about
a
connector
that
had
appeared
in
logic
apps
in
the
past,
one
that
stated
post
an
adaptive
card
to
separately,
listen
for
response
in
a
chat
or
channel.
It
appears
that
this
connector
was
available
for
a
short
time
and
it's
no
longer
available.
Today.
A
A
B
B
A
Perfect,
thank
you,
quran
and
rob.
I
believe
that
the
the
action.execute
is
available
in
viva
connections.
What
I
think
won't
be
available
is
what
quran
demonstrated
where
you
can
see
the
the
card
demonstrated
in
in
various
different
apps.
At
the
same
time,
rafae
is
asking:
can
this
be
controlled,
separate,
rendering
versus
in
one,
and
I'm
not
sure?
I
understand
that
question
completely
rafi.
A
Can
you
maybe
elaborate
a
little
more
in
the
chat
and
we
can
come
back
to
the
question
as
soon
as
we
get
some
more
details,
gao
is
asking
a
question:
can
the
action
be
a
call
to
a
to
an
azure
function
and
tomas?
Thank
you
so
much
for
responding
that
in
the
chat
for
the
people
that
don't
have
the
chat,
the
act,
the
answer
is
yes,
the
action
can
be
a
call
to
an
azure
function.
A
Next
question
is
from
ryan:
can
the
universal
action.execute
work
with
a
flow
or
power
virtual
agent?
I
use
a
lot
of
adaptive
cards
in
outlook
but
have
been
using
the
action.open
url
action
to
call
http
request
flow.
I
want
to
switch
to
the
you
new
universal
action,
but
need
a
low
code
way
to
handle
the
action.execute
logic.
B
I'm
thinking
what
the
right
answer
to
this
is.
I
know
there
were
attempts
to
have
a
low
code
experience
for
action.execute
in
place,
but
I
would
request
to
confirm
internally
before
I
respond
to
that.
So
maybe
jpu
and
I
can
speak
with
someone
at
microsoft
just
to
keep
a
track
on
the
progress
made.
Thus
far
on
this.
B
Right,
yes,
that's
true!
The
intent
is
to
have
all
obsolete
action
types
if
I
may
call
them
that
way,
have
them
switched
over
to
action
dot
execute
because
while
we
want
to
be
cognizant
of
backward
compatibility,
I
think
it
would
be
fair
to
say
that
almost
every
new
adaptive
card
feature
and
capability
is
going
to
be
built
on
top
of
action.execute
perfect.
Thank
you.
A
Gareth
is
asking:
are
adaptive
cards
playing
a
role
at
build
2022
as
of
now
I
don't
have
any
information
on
that
gareth,
but
if
anything
changes
you
can
expect
to
hear
either
through
an
announcement
on
twitter
or
or
in
one
of
the
the
next
community
costs
as
well.
I
think
we
have
one
right
before
build
coming.
B
A
Oh
perfect,
yeah
there
we
go.
You
guys
just
got
a
a
sneak
peek
into
to
build
from.
I'm
super
excited
to
see
that
content
demonstrated
and
build.
I
guess
you'll
have
to
to
tune
in
to
to
learn
more
about
that
great
session,
happy
to
learn
more
about
adaptive
cards.
Is
there
any
update
regarding
the
payload
issue
to
a
team's
connector,
currently
28
kb,
which
is
very
low
to
post
a
clear
image
via
adaptive
card?
Is
there
any
other
way
to
post
a
clear
image
to
teams,
slash
a
chat
channel.
B
Thanks
for
that
question,
we
are
aware
of
this
limit.
Now
there
are
two
ways
to
respond
to
this:
do
we
have
a
way
to
expand
the
limit
today,
while
we
do
the
guidance
from
the
team's
platform
team,
the
team
that
owns
these
chats
and
conversations
in
teams
is
to
still
have
that
restriction
in
place.
One
of
the
key
reasons
we
have
that
restriction
is
because
of
or
performance
considerations
as
the
message
or
the
payload
size
increases.
It
can
have
adverse
implications
on
the
overall
performance
and
rendering
speed
of
the
platform.
A
A
A
recording
of
our
previous
community
called
the
one
from
february
of
this
year,
where
one
of
our
our
partners
made
a
video
player
bot
for
teams.
It's
not
exactly
the
same,
but
I
know
that
they
talked
about
some
ways
to
show
a
video
in
the
the
proper
quality
with
taking
some.
Some
workarounds
that
are
are
not
shown.
A
Ryan
is
asking:
is
there
a
tap
community
for
adaptive
cards
ryan?
Could
you
maybe
expand
that
acronym?
I
don't
think
I'm
aware
of
what
tap
community
means
in
the
meantime,
we
can
hop
over
to
the
next
question.
What
is
the
progress
on
component
features
in
adaptive
cards,
so
alexander
adaptive
components?
That's
definitely
still
on
our
roadmap.
We
don't
have
a
a
fixed
date
on
that,
yet
we're
hoping
to
to
get
it
done
within.
I
think
our
latest
estimates
have
been
early
next
year.
A
B
A
Awesome
and
drew
is
asking
anyone
try
to
use
teams
connect
to
send
an
adaptive
card
into
a
shared
channel
looks
to
not
be
supported.
Yet
this
is
not
really
in
line
with
with
the
universal
action
models
we've
talked.
I
think
this
might
be
a
power
automate
question.
Is
there
anyone
in
in
the
call,
maybe
that
can
answer?
This
question
looks
like
we
might
be
getting
some
answers
in
the
chat
drew.
Unfortunately,
I
don't
know
the
answer
to
this
question.
A
Anyone
tried
to
use
teams
connect
to
send
adaptive
card
into
a
shared
channel
looks
to
not
be
supported,
yet
it
might
not
be
supported.
Yet
I
know
the
the
power
automaker
is
still
making
some
updates
and
looking
to
actually
update
us
as
well.
The
latest
version
of
adaptive
cards
that
they
utilize,
so
it
might
be
coming
soon
if
it's
not
already
supported
jim,
is
asking.
Can
we
use
other
components
like
the
microsoft
graph
toolkit
in
an
adaptive
card?
A
Jim?
I
think
we
we
do
have
support
for
for
microsoft.
Graph
valeris
is
asking
what
is
planned
in
roadmap
related
to
adaptive
cards
in
terms
of
provisioning
like
specific
adaptive
card
forms
or
setups
in
teams
approval
flow,
where
you
can
provision
approval
templates
automatically,
I'm
not
sure
what
is
meant
with
with
templating.
I
know
we
we
do
have
templating
with
adaptive
cards
today
where
actually,
I
think
that
might
be
the
question.
So
in
our
designer
veterans,
we
have
a
section
for
data
where
you
can
enable
things
like
adaptive
card
templates.
A
What
this
does
is
provide
data
binding
support
where
the
data
can
change.
Based
on
the
information
you
provided,
giving
users
different
sort
of
views.
There
might
be
some
workarounds
that
need
to
be
done,
for
example,
using
our
dollar
sign,
one
key,
which
basically
establishes
a
condition
based
on
some
inputs
that
need
to
be
met
to
show
a
different
card
based
on
the
information
you're
giving
it,
but
I
think
that
would
be
possible
today.
A
Ryan
acts,
technical
access,
preview,
ryan,
the
closest
thing
we
have
to
that
is
our
ci
build
of
the
website.
That's
where
we
post
all
of
our
pre-release
content
and
get
the
the
latest
updates
build
on
a
nightly
build
of
our
main
branch
on
github.
So,
for
example,
one
feature
that's
coming
in
version
1.6
that
you
can
actually
use
today
in
that
ci
version
of
the
website
is
the
carousel
component.
So
this
is
a
horizontal
carousel
that
lets.
You
have
multiple
views
of
an
adaptive
card
displayed
and
travel
to
next
and
previous
cards.
A
A
B
B
A
And
jim
is
asking:
is
there
a
recording
of
the
video
player
bought
for
teams
that
you
mentioned?
Yes,
jim?
It's
our
recording
for
our
february
2022
community
call
it's
available
on
youtube.
I
share
the
link
a
little
more
up
in
the
chat,
and
I
I
oh
I
see
that
vasa
also
shared
a
link
to
it.
Thank
you
so
much
for
that
trying
to
search
for
any
other
questions
that
we
have.
I
don't
think
we
have
any
more
pending
questions
in
the
chat,
I'll
go
ahead
and
move
forward.
A
Thank
you.
Everyone!
So
much
for
attending
the
april.
2022
community
call
thank
you
again
quran
for
for
joining
us
here.
I
know
it's
late
over
there
and
it's
also
a
holiday
so
really
appreciate
you
taking
the
time
to
join
us
and
talk
about
universal
actions
and
messaging
extensions.
It's
a
topic
that
the
community
is
super,
excited
about
and
really
hoping
to
to
get
some
more
work.
In,
as
mentioned,
I
will
take
an
action
item
to
follow
up
on
the
question
about
the
azure
logic.
Connector
that
has
gone
missing.
A
I
will
go
ahead
and
share
an
update
on
my
twitter
and
also
in
the
next
community
call
the
second
thursday
of
may.
If
you're
looking
for
more
resources
like
our
roadmap
and
our
code,
repo,
you
can
find
all
the
links
here.
We
also
have
samples
and
more
tools
in
madewithcards.io
to
access
any
of
the
other
microsoft
365
developer
community
calls
you
can
find
all
the
links
here,
as
well
as
their
cadence
and
that'll,
be
all
for
the
april
22
community
call
for
adaptive
cards.
Thank
you,
everyone
for
joining.