►
From YouTube: Adaptive Cards community call – June 2021
Description
After a quick wrap up on Microsoft Build ’21 from an Adaptive Cards perspective, this call’s primary focus is on Microsoft Viva Connections Extensibility with Adaptive Cards. Starting at the top with a Viva Extensibility Overview - Dashboard demo and Dashboard and card composition. There is a review of Adaptive Card Extensions (ACEs) – SPFx component/tool to build cards, available templates and a live Q & A covering distribution, analytics, and more. This call was hosted by Matt Hidinger (Microsoft). Microsoft presenters are Luca Bandinelli, John Nguyen and Pat Miller. Recorded on June 10, 2021.
Stay connected:
• Twitter - https://twitter.com/microsoft365dev
• YouTube - https://aka.ms/M365DevYouTube
• Blogs - https://aka.ms/m365pnp/community/blog
• Recurrent Invite - https://aka.ms/adaptivecardscommunitycall
• Next call – July 8th at 09:00am PDT
A
Hi
everyone
thank
you
for
joining
the
adaptive
cards
community
call
of
june
2021,
I'm
matt
heidinger
I'll,
be
your
host,
but
just
for
a
few
minutes,
because
we've
got
a
really
exciting
guest
set
of
speakers,
luca
pat
and
john
work
on
the
microsoft
viva
product
and
they're,
going
to
dive
deep
into
the
extensibility
model,
the
product
itself
and
how
adaptive
cards
empowers
different
people
to
basically
build
up
dashboards.
What
I've
skimmed
through
it.
I'm
personally
really
excited
about
this
topic
and
so
without
further
ado
I'll
hand.
B
Matt,
thank
you
very
much.
Hi
everybody.
Thank
you
for
having
us.
My
name
is
luca
bandinelli.
I
am
a
program
manager
in
the
microsoft
onedrive
and
sharepoint
team
and
as
part
of
our
org,
we
are
also
responsible
of
one
branch
of
the
viva
brand,
which
is
the
viva
connections
and
specifically
the
viva
connection
dashboard,
where
we
are
leveraging
the
power
of
adaptive
card
to
be
able
to
have
beautiful,
rich
experience
in
the
web,
as
well
as
in
the
rich
clients,
specifically
teams,
rich
clients
and
teams.
B
B
A
I
I
did
want
to
do
one
quick
call
out
to
the
build
21
conference
that
was
a
few
weeks
ago,
so
it
was
a
slightly
wordy.
It
probably
won
some
award
on
one
of
the
wordiest
build
titles,
but
for
building
great
discovery
and
collaboration
apps
for
m365,
with
new
microsoft,
graph,
connector
and
adaptive
card
capabilities.
So
jeremy,
thake
and
rabia
presented
some
really
exciting
adaptive
card
stuff,
primarily
around
universal
actions,
which
makes
it
possible
to
build
a
single
card
back
end
that
works
with
teams
and
outlook.
A
B
Perfect,
thank
you
very
much.
So
no
further
notice,
let's
talk
about
viva
connection
and
how
the
adaptive
card
framework
plays
a
big
role
in
the
extensibility
world
for
viva
connections,
not
only
for
first
party
components,
but
also
for
third-party
components
and
how
the
developers
can
use
that
to
extend
with
a
connections
experience
in
the
dashboard.
So,
if
you
think
about
the
web
connections,
vivo
connection
has
three
main
pillars.
B
It
has
the
dashboard
where
the
company
author
can
basically
compose
cards
and
applications
that
the
different
type
of
users,
frontline
workers,
as
well
as
different
either
audiences,
can
use
to
basically
have
access
to
the
applications
and
can
perform
quick
task
actions
that
are
crucial
for
the
for
their
day-by-day
work.
Together
with
the
dashboard,
we
also
have
the
feed
that
gives
the
ability
to
have
accurate
aggregation
of
information
across
your
organization
and
the
resources
which
gives
you
the
ability
to
access
some
of
the
key
and
sometimes
mandatory
links
that
are
available
in
your
company.
B
From
the
dashboard
standpoint,
we
surface
the
dashboard
in
the
mobile,
as
well
as
in
the
rich
client,
by
using
the
power
of
sharepoint
to
modern
pages
and
publishing,
and
we
also
provide
an
authoring
experience
in
the
sharepoint
as
well.
That
gives
the
ability
to
content
creators
to
build
the
dashboard
for
the
entire
organization,
and
we
will
go
about
that
later
in
the
demo.
B
B
The
connectors
is
one
of
the
functionalities
that
we
have
in
microsoft
to
book
shuttles
that
can
help
us
moving
across
different
buildings
within
the
private,
sound
area
and
you
set
the
connector
and
when
the
connector
is
ready
to
pick
you
up
the
card
automatically
changes
without
any
end
user
intervention
to
basically
notify
the
end
user
that
the
connector
is
available
for
him
or
her
in
terms
of
the
components
of
the
dashboard
you
have
the
company
name
and
navigation
bar
the
company
logo.
We
have
different
type
of
cards
right
now.
B
We
support
two
different
layouts,
but
we
are
planning
to
expand
that
in
the
future-
and
this
is
the
card
itself-
company
name
and
company
logo.
It's
something
that
the
author
and
the
admin
can
change.
We
rely
on
the
team's
admin
experience
and
the
team's
tenant
admin
capabilities
to
be
able
to
change
this
kind
of
information
or
this
kind
of
content,
because
viva
connection
is
a
teams
app.
So
just
like
any
other
teams
app,
the
team's
administrator
is
able
to
change
the
branding
and
change
the
company
name.
B
So,
let's
talk
about
the
assembling
the
dashboard,
so,
as
I
was
saying,
dashboard
is
a
component
that
the
author
can
create,
but
there
are
other
kind
of
roles
within
the
organizations
that
are
operating
together
in
order
to
make
the
viva
connections
dashboard
available.
So
the
sharepoint
themes,
administrator
and
themes,
administrators
are
basically
the
one
that
decide
where
the
dashboard
live,
because
the
dashboard
right
now
will
live
in
this
home
site
of
your
company
in
sharepoint.
B
The
business
unit
representative
is
basically
the
one
that
says
which
one
of
application
I
want,
which
kind
of
inform,
which
kind
of
information
my
users
needs
to
access,
and
then
the
business
unit
representative
then
interact
with
the
isv
and
or
the
system
integrator
in
order
to
be
sure
that
the
right
third-party
applications
are
available.
Because,
again,
one
of
the
trains
of
viva
connections
is
to
be
able
to
aggregate
functionalities
not
only
from
perspective
solutions,
but
also
from
third-party
solution
either
by
connecting
existing
third-party
application.
B
I'll
show
you,
I
mean
what
I
mean
by
that
or
by
having
solutions
that
were
built
directly
for
viva
connections,
using
sharepoint
framework
and
adaptive
card
framework
to
be
able
to
surface
in
microsoft,
viva
connections
and
specifically
in
the
dashboard
and
then
at
the
end.
The
corporate
communication
is
basically
the
content
creator
or
the
dashboard
author,
which
is
the
person
which
is
more
connected
to
the
business,
and
that
person
is
the
one
that
is
able
to
build
the
dashboard.
B
So
the
authoring
experience,
as
I
was
saying
before,
is
very
familiar
authoring
experience
for
people
that
know
how
to
or
that
already
deal
with
the
modern
page
authoring
experience
in
sharepoint.
You
start
with
a
default
layout.
You
have
a
card
speaker
experience
and
you
can
start
adding
the
cards
inside
your
dashboard.
B
So
very
quick
recap.
As
I
said
at
the
beginning,
we
are
supporting
two
different
kind
of
layouts.
We
can
sweet
sport
button
that
can
have
direct
action
or
then
connect
the
card,
the
user
directly
to
the
external
application.
Again,
an
external
link,
sharepoint
page
or
a
teams
application
or
a
quick
view,
experience
which
is
a
more
inside
app
experience
completely
and
100
powered
by
adaptive
card.
B
Some
of
the
information
can
be
customized
by
the
but
the
author,
and
also
we
support
some
kind
of
dynamics,
capabilities
and
functionalities,
and
we
will
support
some
kind
of
provide
some
kind
of
out-of-the-box
card.
So
let's
talk
about
the
authoring
experience
and
let
me
go
here
so
you
can
see
my
screen.
I
am
in
a
communication
site
in
my
communication
site.
I
can
go
here
and
select
the
dashboard.
B
So
here
you
can
see
that
I
have
my
cards
in
my
dashboard.
There's
already
some
cards
over
here
we'll
go
through
them
a
little
bit
as
an
author.
I
can
go
and
edit
and
now
I
am
in
an
edited
canvas
and
I
can
have
multiple
kind
of
cards
here.
I
can
see
that
I
have
different
cards.
If
I
click
on
the
card,
I
can
select
the
pencil
and
then
now
I
can
see
that
I
have
my
property
page
here.
B
But
a
couple
of
interesting
card
that
I
have
one
one
is
called
the
teams
app
and
if
I
select
the
teams
up.
Basically
this
is
the
first
party
card
that
we
provide
out
of
the
box
that
gives
the
author
the
ability
to
connect
existing
teams,
personal
app
and
both
to
viva
connection.
So,
for
example,
here,
as
I
said
before,
as
I
did
already
before,
I
can
connect
to
tiny
pools
and
when
I
do
that,
basically
I
have
a
minimal
kind
of
pulse
kind
of
customizations
that
I
can
do.
B
But
then,
when
I
preview
what
it
does,
it
basically
gives
me
the
ability
to
go
here
and
open
themes
directly,
and
you
can
see
that
as
a
way
and
that
points
directly
to
my
application.
So
this
is
basically
a
way
for.
Let
me
go
back
over
here,
a
way
for
authors
to
be
able
to
reuse
existing
applications
that
were
built
on
microsoft,
teams
and
reuse.
The
investments
that
isvs
or
the
company
themselves
and
companies
themselves
did
on
top
of
microsoft
teams
and
have
these
kind
of
functionalities
available
from
the
get-go
inside
of
viva
connections.
B
Dashboard.
Another
interesting
card
that
we
built
as
a
first
party
card
is
the
what
we
call
the
car
designer
and
the
car
designer
is
an
interesting
card
that
we
are
building
for
citizen
developers
and
developers
that
unleash
the
power
of
adaptive
card
to
be
able
to
create
the
beautiful
cards
in
the
vivoconnection
dashboard.
Without
you
needing
to
engage
with
a
developer
or
without
you
being
a
developer,
so
you
can
see.
B
Basically
the
card
designer
gives
you
the
ability
to
specify
the
template
json
from
adaptive
card
and
the
other
json,
so
that
you
basically
can
provide
the
same
kind
of
functionalities
and
capabilities
that
you
can
build
in
adaptive
card
using
deductive
card
designer
from
the
beginning.
So
if
you
click
on
the
button
this
goes.
This
brings
me
over
here
on
a
different
page,
because
that
what
is
what
I
configured
in
the
button.
B
So,
as
an
author,
you
can
go
to
adaptive
card
design
or
you
can
select
your
favorite
adaptive
card
copy
paste
that
information
here
in
the
card
itself
and
voila
your
card
is
available
to
everybody
without
you
needing
to
be
able
to
or
having
their
requirements
to
engage
with
the
developers.
Now
that's
kind
of
a
different
kind
of
opportunity
and
options.
As
you
can
see,
there
is
no
way
for
you
to
provide
any
kind
of
external
data
or
dynamic
data.
B
Everything
is
static
and
is
configured
within
the
card
itself,
but
with
the
developer
option,
which
is
the
one
we're
going
to
talk
about
a
little
bit
later,
you
will
be
able
also
to
provide
this
kind
of
functionalities
and
capabilities
with
a
more
dynamic
kind
of
interaction.
So,
for
example,
you
should
be.
You
will
be
able,
as
a
developer,
to
use
adaptive
card
but
then
feed
the
adaptive
card,
json
with
external
data
coming
from
microsoft,
graph
or
any
other
api
that
has
been
registered
in
azure
active
directory.
D
A
This
is
cool,
I
gotta
say
like
I.
It
reminds
me
like
the
first
time
I
saw
the
adaptive
card
stuff
in
power
automate
and
just
you
know,
making
this
stuff
available
to
an
entire
group
of
people
that
that
you
know
that's,
not
a
traditional
developer.
That's
trying
to
just
achieve
a
simple
scenario,
so
I
really
like
the
power
here,
but
for
my
own
understanding
and
potentially
for
other
folks.
So
this
communication
site,
like
this
is
a
feature
in
sharepoint.
B
And
actually,
just
just
like
I
was
I
was
showing
if
you
can
see
that
this
is
the
the
dashboard
that
I
have
the
same
dashboard,
because
it
goes
through
adaptive
card.
It's
also
available
in
the
mobile.
So
here
is
a
video
that
I
created.
We
created
this
morning
where
the
viva
connection
application
is
showing
the
same
dashboard
that
I
just
used
in
a
mobile
reach
experience
you
can
access
the
themes
application.
This
is
the
food
card
that
we
show.
B
This
is
exactly
the
same
adaptive
card,
json
that
I
selected
before,
and
I
use
it
from
the
browser,
but
now
I'm
using
that
from
the
teams.
Application,
rich
client
and
one
of
the
important
thing
that
I
want
to
highlight
here
is
that,
because
of
the
power
of
the
adaptive
card,
we
are
able
to
render
all
this
experience
in
react
native.
So
what
you
are
seeing
right
now,
all
the
cars
that
they
are
seeing,
especially
the
one
that
was
built
using
the
json
from
adaptive
car
designer,
is
not
a
web
view.
B
So,
basically,
you
are
able
to
use
sharepoint
framework
and
the
power
of
adaptive
card
to
build
the
solution,
deploy
that
solution
to
your
organization,
by
using
the
microsoft
store
or
by
site
loading,
your
application
in
your
enterprise
and
now
that
application
will
run
in
the
web
in
a
web
view
or
natively
in
a
device
or
in
a
channel
that
is
supporting
native
design
or
native
rendering,
just
like
the
team's
mobile
application
by
building
the
code
once
and
basically
have
that
code
being
rendering
differently.
Thanks
to
the
power
of
adaptive
card.
A
B
A
A
E
B
The
dashboard
will
be
this
new
entry
point
from
the
authoring
standpoint
that
be
able
to
create
a
viva
connection
dashboard
for
the
viva
connections.
Then
in
themes,
you
will
have
a
new
app
called
viva
connection
that
will
be
available
either
in
both
in
mobile
and
in
the
desktop
from
where
you
will
be
able
to
surface
the
dashboard
itself
in
either
web
or
native,
depending
on
the
kind
of
experience
that
you
are
surfacing
to
teams
mobile
as
an
example,
just
like
I'm
showing
right
now
will
be
native
rendering
cool
so.
C
B
B
So,
let's
move
forward.
Let's
talk
about
custom
cards
so,
like
I
said
we're
talking
about
out
of
the
box
card,
we
will
have
some
kind
of
out
of
the
box
card
themes
up
designer
and
other
cars
that
connect
to
first
party
microsoft.
Applications
just
like
tasks
as
an
example
will
be
available
for
for
microsoft,
265
customers.
B
If
that's
something
needed
from
their
business
requirements
and
using
code,
they
will
also
be
able
to
do
tipling
connection
to
external
application,
external
web
applications,
external
sharepoint
pages
or
external
themes,
applications
very
similar
to
the
one
that
we
did
with
the
themes
card,
but
because
it's
custom
code
and
now
the
card
can
go
a
little
bit
more
detail
integration
just
like,
for
example,
if
your
themes
application
has
multiple
tabs,
you
will
be
able
to
say
I
want
if
you
click
this
button.
I
want
to
go
to
this
tab.
B
If
I
click
this
other
button,
I
want
to
have
a
different
kind
of
experience
inside
of
the
team's
application
itself.
So
let's
talk
about
kind
of
the
infrastructure
and
the
architecture,
the
taxonomy
of
the
vivo
connections
cards.
So
the
card
is
the
first
experience
that
you
have
in
the
dashboard.
It's
something
that
it's
required.
It's
something
that
you!
B
If
you
want
to
build
a
custom
experience
on
top
of
viva
connections,
dashboard
you
will
have
to
provide,
and
the
purpose
of
the
card
is
to
be
able
to
provide
to
the
end
user,
weak,
actionable
information
that
are
supposed
to
be
consumed
directly
within
the
card.
So,
for
example,
your
connector
is
arrived
or
your
flight
has
been
changed
or
you
have
to
go
to
the
gate
or
you
need
to
check
in
for
kind
kind
of
frontline
worker
scenario.
B
This
is
an
optional
component
if
you're
going
to
build
an
it's,
a
new
experience
on
top
of
a
connection
dashboard
card
is
the
only
one
that
you
have
to
create.
The
quick
view
is
something
that
you
can
provide
that
you
can't
provide
it's,
not
it's
not
required
for
that,
and
then
you
can
also,
I
said,
extend
and
connect
your
experience
to
an
app
which
can
be
triggered
directly
from
the
quick
view
and
the
card.
The
cell
are
actually
another
important
information
to
think
about.
There
is
no
sequence
here.
B
The
flow
is
not
sequential
is
not
that
in
order
for
you
to
trigger
an
app,
you
have
to
create
a
quick
view.
The
car
is
the
only
one
that
is
required
again,
but
from
the
card
you
can
go
to
the
quick
view
and
that's
it
from
the
card.
You
can
do
nothing
else.
Everything
is
surprising.
In
the
card
from
the
card,
you
can
go
directly
in
the
app
from
the
quick
view.
We
can
go
directly
in
the
app.
B
B
Second
conversation
is
that
sharepoint
framework
is
a
development
model
that
is
built
on
top
of
modern
javascript
technologies
that
developers
use
in
order
to
build
extensibility
components
on
top
of
sharepoint
web
parts,
full
pages
on
top
of
teams,
personal
apps,
dot,
app
chat,
apps
messaging
extension
meeting
extensions,
etc,
and
now
on
viva
connections,
it's
a
full
javascript
based
developer
model.
You
don't
need
to
be
a
sharepoint
expert
to
be
able
to
create
sharepoint
framework
components.
B
As
a
matter
of
fact,
you
have,
if
you
have
no
knowledge
of
sharepoint
sharepoint
is
just
another
component.
You
interact
with
to
be
able
to
build
your
kind
of
extensions
or
your
kind
of
components.
On
top
of
this,
and,
of
course,
if
you're
building
something
for
teams,
you
don't
even
have
to
understand
sharepoint
at
all,
but
it
also
provides
a
lot
of
interesting
functionalities
that
developers
can
use.
For
example,
it
gives
you
the
ability
to
consume
the
entire
microsoft
365
or
the
majority
of
max
365
contexts,
so
that
you
can
understand
where
you
are.
B
B
So,
for
example,
if
you
have
to
consume
microsoft
graph
data
by
using
sharepoint
framework,
you
are
able
to
make
that
kind
of
interaction
seamlessly,
and
we
basically
take
care
of
all
the
authorization
and
authentication
steps
for
you
by
embedding
msal.js
v1
working
for
v2
and
being
able
to
interact
to
do
all
the
interaction
in
terms
of
potentially
conditional
access
policy
getting
getting
the
token
caching,
the
token
et
cetera,
et
cetera.
So
all
these
functionalities
are
there
and
again
because
we
are
using
adaptica
framework.
B
Your
card
will
render
in
a
web
view
in
the
browser,
but
will
also
render
natively
in
teams
mobile
in
this
case,
because
that's
what
we
are
using
for
rendering
cars
in
the
dashboard
in
the
team's
mobile
vivo
connection
experience
so
couple
of
custom
car
supports
as
an
example.
These
are
some
examples
that
you
can
see
that
you
can
build
by
using
a
graphic
card
and
the
sharepoint
framework
and
adaptive
card
extensions.
Some
of
those
are
mock-ups.
B
We
know
that,
and
you
guys
know
better
than
we-
that
adaptive
cards
and
some
some
constraints,
but
we
are
working
together
with
adaptive
car
theme
to
be
able
to
provide
new
functionalities
and
capabilities
in
the
adaptive
card
itself,
so
you
have
dynamic
title
and
icon
dynamic
description,
multiple
buttons
and
the
adaptive
card
json
itself.
So
again,
the
dynamicity
of
this
information
is
the
ability
to
provide
dynamic
information
in
all
of
these
experiences
is
important
here,
as
we
saw
before.
B
So
let's
talk
about
a
little
bit
more
of
the
anatomy
of
the
custom
card
in
adaptive
card
extensions.
You
have
the
view
and
the
view
basically
are
the
content
of
the
card
or
the
quick
view.
There
are
predefined
templates.
The
developer
can
choose
you
can.
In
this
example,
you
have
a
three
template
for
the
car
view
and
one
template
for
the
quick
view,
and
basically
the
developer
can
focus
more
on
the
data
model
instead
of
the
user
interface
and
what
I
mean
by
that
is
that,
especially
for
the
card.
B
Although
the
card
itself
is
using
adaptive
card
behind
the
scenes
to
render
the
card
for
the
card,
we
are
not
providing
the
full
adaptive
card,
the
ability
we
are
not
providing
the
ability,
the
ability
to
the
developer
to
build
the
full
adaptive
card
json.
So
specifically,
what
I
mean
by
that?
Each
of
these
templates
expose
different
parts
that
the
developer
can
use
in
order
to
interact
with
the
card
in
order
to
surface
information
to
the
end
user
to
the
card
itself.
B
So,
for
example,
you
will
have
an
account
property
that
by
code
you
can
change,
the
title
can
be
changed.
The
primary
text
can
be
changed
and
then
there
are
other
things
that
are
only
specific
to
specific
templates
or
views.
So,
for
example,
image
url
is
only
available
on
the
basic
image
card.
The
description
is
only
available
on
the
primary
text
card
and
then
on
the
quick
view
instead
is
where
we
give
the
ability
for
the
developer
to
provide
the
full
adaptive
card
json.
B
So
again,
I
want
to
clarify
that
here
a
little
bit
one
more
time
when
you,
while
you're
building
the
card,
you
will
only
be
able
to
interact
for
specific
constraints,
properties
that
we
provide
to
you
in
the
code
and
the
framework
will
build
the
adaptive
card
json.
Based
on
the
information
that
you
provide.
B
However,
in
building
the
quick
view
you
as
a
developer
will
be
able
to
provide
the
entire
adaptive
cards
json
and
you
will
be
able
to
build
these
adaptive
caches
or
in
json
in
the
way
you
want
interact
with
third-party
apis,
interact
with
microsoft,
graph
and
augment
that
kind
of
json
in
the
way
that
your
business
needs
and
and
before
anyone
asked.
Why
did
you
guys
do
that?
What
the
hell
did
you
guys
do?
The
reason
why
we
did?
B
That
is
because,
as
you
remember
from
the
demo-
and
I
can
show
here
now
here-
you
are
partying
with
a
lot
of
other
people,
so
we
need
to
be
able
to
do
things
just
like
reflowing
and
being
able
to
hide
and
surface
cars.
So,
for
example,
one
of
the
things
that
we
didn't
talk
about
as
a
functionality
that
we
have
is
basically
we
have
the
ability
to
do
something
which
is
called
audience
targeting.
So,
for
example,
I
can
discard
charge
here.
Okay,
I
can
edit
so
what
I
can
do.
B
If
I
go
to
a
card,
I
can
select
and
say
that
I
want
to
be
able
this
card
to
be
only
available
to
a
specific
audience
inside
inside
of
my
organizations
when
I
do
that,
as
you
can
see
as
an
end
user
will
see
different
kind
of
cards
depending
on.
Actually
let
me
do
that
on
a
card
that
can
be
showed.
Let
me
show
a
little
bit
better.
Let
me
go
here.
B
B
This
is
here.
This
is
here
interesting,
interesting
bug,
okay,
I
I
have
a
bug
here.
I
think
so.
Yes,
okay,
so
basically
here
I
can
do
this
kind
of
targeting.
So
if
I
am
this,
if
I
am
this
user,
I
cannot
see
the
card,
but
if
I
am
this
user,
I
will
see
the
card,
so
you
can
see
that
we
need
to
support
things
just
like
reflowing
on
different
kind
of
formats,
so
we
can
think
we
need
to
do
to
support
hiding
and
surfacing
cards
depending
on
who
you
are
so.
B
For
that
reason,
we
need
to
be
able
to
constrain
the
kind
of
information.
The
other
thing
that
we
need
to
be
able
to
support
is
on
the
fly,
different
kind
of
templates
right
so
our
size,
so
I
can
change
it
between
size
and
medium
kind
of
card.
I
can
go
here
and
do
the
same,
so
I
need
to
be
able
to
give
this
kind
of
flexibility
to
the
author
and
give
kind
of
flexibility
in
terms
of
content,
consumption
consumption
to
the
end
user.
B
For
that
reason,
we
have
provided
some
kind
of
a
constraint
environment
for
the
developer
when
the
developer
needs
to
create
the
card.
Again,
that's
not
true
for
the
quick
view.
So
when
I
am
the
quick
view
now,
you
are
in
the
full
adaptive
card
json
and
especially
as
we
saw
in
the
video
on
the
mobile,
it's
a
full
page
experience.
So
now
you
can
do
whatever
you
want.
A
Luca
totally,
I
love
the
justification.
I
don't
know
if
you
have
to
worry
about
it,
because
you
got
a
bunch
of
thumbs
up
and
applause
as
you
as
you
mentioned
it.
I
know
you
kind
of
were
like
worried
a
little
worried
about
it.
I
just
wrote
you
a
mail
separately,
but
I
think
the
one
thing
that
there's
a
lot
of
potential
with
this
to
to
continue
to
meet
your
goals
around
a
little
more
rigid
and
fixed
modeling
in
the
in
the
at
the
top
level
is
a
concept
we've
talked
about
on
the
community.
A
Calls
in
the
past
called
adaptive
components
and
it
lets
you
do
exactly
that.
You
can
kind
of
define
these.
One
of
them
is
basically
it's
just
it's
a
thing
and
a
thing
has
a
title
and
image.
You
know
it's
so
I
we
have
an
opportunity
to
potentially
integrate
that
in
the
future,
where
we
can
maybe
use
that
model
here
and
the
nice
thing
about
the
component
model
is
those
set
of
properties.
A
A
It's
in
version
it's
planned
for
version
1.6,
so
we're
currently
building
1.5
and
then
1.6
will
follow
that.
So
it's
really
just
a
spec
at
this
point,
so
you
guys
are
free
to
drive
requirements
into
it,
but
I
I
just
t
it
up.
I
see
a
lot
of
potential
synergy
there
with
what
we've
talked
about
in
the
past.
B
F
B
As
I
was
saying
at
the
beginning
of
the
call,
this
is
very
news
for
us.
You
guys
are
seeing
something
that
has
been
announced
but
has
not
been
released
yet,
but
we
also
expect
that
the
more
we
get
feedbacks
the
more
new
layouts
and
new
views
will
come,
but
this
is
basically
what
will
surface
by
the
time
that
we
launch
with.
That
said,
I
am
pretty
much
done
so.
I
would
like
to
open
mike
for
questions,
and
I
know
that
there
are
other
slides
that
you
matt
will
go
through
eventually.
A
Yeah,
so
the
the
final
thing
is
so
just
awesome.
I
think
this
is
a
really
great
great
application
of
the
technology
and
why
we
set
out
to
build
it.
I
think
it's
it's
just
perfectly
fit
with
the
pain
points
that
we
were
trying
to
solve,
definitely
want
to
give
a
shout
out.
I
don't
know
if
anyone
from
imagineer
is
on
the
call.
A
So
I
want
to
give
a
shout
out
to
them
for
all
the
support
they
gave
to
you
folks
and-
and
you
know
they
do
it
out-
of
the
goodness
of
their
open
source
heart,
so
huge,
huge,
shout
out
and
definitely
check
out
the
react
native
package
if
you're
also
exploring
react
native
style,
apps
and
then
the
last
slide
I
really
had.
Is
a
q
a
so
what
I'll
say.
Real
quick
is
thanks.
A
B
One
important
things
I
want
to
to
specify
here
is
that
we
have
a
private
preview
for
viva
connections,
two
things
here.
So
first
one
we
have
a
connection
private
preview.
If
you
guys
want
to
join,
there
is
a
link
that
will
send
you.
What
gives
you
access
is
some
early
access
to
the
beats,
but
if
you
can
wait
a
little
bit,
what
we
are
planning
to
do
is
that
we
are
planning
to
release
the
new
version
of
sharepoint
framework
in
beta
1.13
beta
end
of
the
month,
beginning
of
july.
B
When
that
will
happen,
we
will
be
able
to
provide
public
access
to
these
adaptive
card
extension
frameworks
and
we
will
be
able
to
enable
the
ability
for
developers
to
create
cards
and
test
their
cards
in
their
developer
tenants.
So
as
part
of
the
developer
experience
in
sharepoint,
we
have
what
we
call
the
workbench,
which
is
a
special
page
in
your
tenancy.
That
gives
you
the
ability
to
connect
to
your
gulp
and
when
you're
building
code,
you
are
able
to
surface
that
code
immediately.
B
There
and
the
workbench
will
start
supporting
adaptive
card
extensions
and
microsoft
viva
connections
cards.
So
if
you
want
to
start
clicking
the
tires,
because
you
have
a
really
business
requirement
for
that-
and
we
should
talk
if
you
do-
you
can
do
that
right
now.
But
if
you
wait
until
the
end
of
the
month
early
beginning
of
july,
we
will
go
public
with
the
1.13
beta
version
of
the
sharepoint
did
framework
decent
job
path,
or
did
they
say
something
wrong
he's
my
engineer
manager.
So
I
have
to
be
careful.
B
A
G
Yeah
hi,
I'm
osama,
just
a
quick
question
with
viva
connections
adapter
card,
so
we
are
planning
to
use
viva
connections,
but
we're
leveraging
a
sharepoint
page,
which
has
news
and
everything
else.
Is
there
a
scenario
where
we
could
use
some
components
of
the
sharepoint
page
and
then
it
throw
on
the
other
cards?
Because
I
love
the
interactivity
of
the
cards
and
how
they're
they're
dynamic?
Can
we
do
sharepoint
page
and
cards
on
top
100.
B
G
B
But
as
a
developer,
you
can
also
create
a
more
complex
version
of
this
card
that
will
provide
more
information
that
that
can
be
tolerated
to
the
end
user.
So,
for
example,
the
card
could
recognize
that
you
are
the
author
of
the
page
or
you
are
a
person
that
can
only
see
the
page
and
provide
different
information
in
the
card
itself
and
then
by
clicking
on
the
card
or
clicking
on
the
button
that
can
surface
in
the
card
connect
directly
to
the
page
itself.
F
B
F
So,
thank
you.
So
my
question
is:
are
we
capturing
type
of
analytics
on
the
back
end
as
cards
are
published
and
through?
Because
I
know
I
get
a
lot
of
that
from
corporate
communications
teams
and
developers
going
well
how
popular
is
my
card?
Are
we
capturing
any
of
the
analytics
on
the
click-throughs
on
the
card.
B
E
Awesome
and
man
bear
man,
yes
hi,
so
my
question
is
related
to
the
development
side.
Is
that
as
a
teams
app
developer,
do
I
have
to
now
create?
If
I
want
to
publish
a
card
on
the
dashboard,
I
create
a
separate
package
for
sharepoint
and
that
is
distributed
as
a
sharepoint,
app
or
single
package
or
and
then
also
related
to
the
analytics
part
that
how
do
I
know
how
much
of
user
traffic
coming
to
my
app
through
my
card
or
through
my
app
and
and
how
do
I
get
that
info.
B
C
App
today
in
teams,
there
are
sorry
look,
there's
even
a
first
thing,
which
is:
if
you
have
a
teams
app,
you
don't
need
to
build
a
card
to
have
that
surface
on
the
dashboard.
Unless
you
want
that
card
to
have
like
surface
dynamic
information
from
your
teams
app,
you
can
automatically
drop
any
team's
app
onto
the
dashboard
with
a
card.
You
click
on
it
and
it'll.
It
will
launch
your
team's
app
yeah.
So.
E
B
So
yes,
so
we
deep
link
only
on
the
first
app
right
now.
So
if
you
want
to
have
a
more
tylered
deep
link
experience,
you
can
do
that
by
creating
a
custom
card.
Yes,
okay,
so
and
again,
to
to
etherate
more
on
the
excellent
point,
excellent
point
that
pat
made
we,
if
you
already
invested
heavily
in
teams,
we
give
the
ability
for
you
to
have
a
first
stage
experience
in
viva
connections
by
simply
allowing
the
end
user
to
consume
your
app
through
viva
connection
by
using
the
first
party
card.
B
B
So
if
you
develop,
if
you
distribute
to
your
application
as
an
enterprise
application
on
site
loading
teams
today,
meaning
that
you
offload
the
team's
package
to
the
teams
administrators
today,
then
yes,
the
answer
is
that
you
will
have
to
do
the
same
for
the
admin
for
the
sharepoint
admin
and
in
the
manifest
of
the
sharepoint
admin
of
the
sharepoint
framework
application.
Sorry,
you
will
be
able
to
reference
the
team's
application
so
that
the
system
itself
will
do
the
integration
and
interaction
between
the
two
components
itself.
B
So
that's
that's
one
conversation
if
you're
using
partner
center
in
appsource-
and
if
you
don't
know
what
partner
center
is,
then
the
answer
is
no.
But
let's
say
that
you
use
that,
then
we
are
working
in
order
to
be
able
for
you
in
the
future
to
submit
just
a
new
version
of
the
same
team's
application
through
partner
center
and
to
support
to
publish
that
as
a
teams
application
and
that
package
will
contain
more
items
that
we
will
then
automatically
use
both
in
sharepoint
and
teams
to
provide
that
kind
of
functionalities.
E
E
B
So
again,
so
what
part
partners
they
do
that
for
for
specific
customers?
Let's
talk
about
system
integrators,
they
will
create
two
different
packages
that
will
create
a
teams,
file,
a
teams
package,
sorry
and
a
sharepoint
package,
and
they
will
upload
the
themes
package
in
the
teams,
lob
catalog
and
they
will
upload
the
sharepoint
package
in
the
sharepoint
app
catalog.
That
would
be
the
distribution
model
for
llb
for
store.
It
will
be
one
package
only
through
partner
center.
B
F
B
From
lob,
in
that
case,
this
analytics
information
will
be
provided
to
the
tenant
owner
or
administrator.
And
that's
back
to
the
previous
conversation
that
I
was
answering
to
steve.
But
if
you're
coming
from
store,
we
are
doing
work
in
order
to
be
able
to
provide
at
least
similar
kind
of
analytics.
That
store
provides
today
to
partners
that
publish
information,
publish
application
to
partner
center
in
appsource.
A
We've
got
a
couple
more
questions.
I
have
a
hard
stop
at
10,
I'm
not
sure
about
y'all.
So
what
I'm
gonna
do
is
sign
off,
stop
the
recording
and
then
let
let
people
keep
asking
questions
if
you're
able
to
so
either
pat
or
luca.
I
don't
know
if
you're
able
to
drive
it,
I'm
going
to
at
least
give
you
the
option
there,
but
I'm
going
to
stop
recording.