►
From YouTube: Adaptive Cards community call-March 2020
Description
This month’s call, hosted by Matt Hidinger, included a conversation about the new concept we are calling the Adaptive Cards Management System (ACMS). Our team working on this showed a preview of the ACMS admin portal, how to render an adaptive card on Microsoft Teams using Power Automate and what’s next to turn this preview into a live offering.
Read details in our blog https://aka.ms/AA7ww6n
Resources
Adaptive Cards roadmap https://aka.ms/ACRoadmap
Get started with Adaptive Cards https://aka.ms/AA7wo56
Connect with us!
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
Hi,
everyone
welcome
to
the
adaptive
cards.
Developer,
community
call
the
March
2020
edition
and
I
appreciate,
despite
all
the
things
going
on
in
the
world
right
now
that
you
decided
to
spend
some
time
with
us,
we're
excited
to
have
you.
We've
got
some
stuff
to
share
I'm
Matt
Heidegger
I'll,
be
your
your
host
today
and
we
mean
every
month.
Hopefully
you
know
we're
actually
kind
of
curious
I
keep
forgetting
to
add
to
the
survey.
Where
did
people
find
this
call
so
we're
excited?
A
You
found
us
at
some
point:
I'm
gonna
find
out
where
everyone's
coming
from,
and
if
this
is
your
first
or
last
time,
we'll
have
a
survey
at
the
end,
but
I'll
get
to
that.
So
the
agenda
today
is
gonna,
be
a
quick
look,
quick,
look
and
an
update
of
our
roadmap.
We've
made
some
changes.
We've
got
some
positive.
Some
things
that
were
kind
of
wishy-washy
have
been
moved
around
a
little
bit
so
I'll
do
a
quick
update
on
that
and
the
bulk
of
the
call
will
be
a
kind
of
interactive
demo.
A
A
They've
still
got
some
some
time
left
before
the
project
is
officially
at
the
end
of
the
allotted
time
when
we
had
so
it
would
be
great
if
we
can
learn
from
you
ask
questions
figure
out
if
that
makes
sense
or
where
we
should
spend
the
rest
of
our
time
and
just
peek
below
the
hood
and
see
how
it
works,
and
if
you
have
any
curious
curiosity
around
it,
that'd
be
the
time
to
do
that,
so
it'll
be
slightly
interactive
after
they
give
a
quick
demo.
So
with
that,
let's
get
into
the
start
of
it.
A
So
we've
had
this
feature
portal
around
I
talk
about
it
every
month,
if
you're
here
every
month,
you're,
possibly
sick
of
me
talking
about
it,
but
you
can
go
to
a
kms
or
on
the
previous
one.
We
have
AC
roadmap,
but
that
is
gonna.
Kick
up.
Kick
you
off
to
a
portal
that
we
have,
which
is
kind
of
a
user
friendly
view
of
a
high-level
view
of
what's
on
top
of
our
mind
and
when
what
we're
hoping
to
release
in
a
given
in
a
given
quarter.
A
So
a
couple
quick
updates
along
the
way
so
templating
has
been
rolled
out
in
more
places.
We
released
a
public
preview
of
the
adaptive
card,
template
service
and
then
the
last
month
we
will
not
we,
but
the
power
automate
team
released
action,
support
in
their
power
automate
connector.
So
you
can
now
use
a
connector
that
sends
a
card
into
teams
collects
input
from
the
user.
Then
you
can
click
the
button
in
teams
and
it
it
basically
kicks
off
the
flow
to
continue
on
based
on
what
the
user
had
typed
in.
A
So
you
can
really
create
these
really
powerful
and
end
experiences,
creating
a
card
collecting
data
from
someone
in
teams
and
then
doing
something
with
that
data
all
from
power
automate
without
having
to
write
any
code
and
I,
know
a
lot
of
jargon
and
a
lot
of
what
I
just
said.
If
you're
not
familiar
with
power,
automate
I
definitely
encourage
you
to
check
it
out.
It
used
to
be
called
Microsoft
flow.
A
I,
don't
have
any
demos
planned
today,
but
if
you
look
at
any
previous
community
calls,
in
fact,
at
the
end
Thomas,
who
is
our
familiar
friend
on
this
call
kind
of
walked
us
through
some
of
the
cool
power
automate
edition.
So
if
you
are
at
least
curious
with
that
product
or
using
it
every
day,
there's
been
two
cool
editions
specifically
for
adaptive
cards
that
you
can
learn
all
about
from
last
month's
call.
So
that's
what's
happened
as
far
as
what's
launched,
we've
got
some
updates
around
templating
we've
been
talking
about
templating
for
a
long
time.
A
A
That's
currently
what
we're
calling
adaptive
card
template
and
what
changes
when
I
turn
this
toggle
on
is
instead
of
one
giant
text
box
or
JSON
box,
we
get
to.
We
basically
separate
the
two
concepts.
So
what's
changed
here
is
the
the
data
from
the
card,
and
it's
any
data
you
want.
You
could
have
described
the
state
of
yourself.
You
could
have
gotten
it
from
another
service,
but
here's,
basically
the
dynamically
replaceable
part
of
this
card.
A
So,
in
this
case,
I'm
saying,
there's
a
title:
there's
a
description,
there's
a
creator
and
the
creator's
name
and
their
profile
image,
and
then
it
gets
used
in
the
card
via
these
binding
expressions
where
you
can
see
these
these
curly
braces
so
I'll.
Actually,
let
me
zoom
in
just
a
little
bit.
So
it's
a
separation
of
the
static
part
of
the
card
and
the
dynamically
replaceable
card.
What
this
means
is
now
that
you
have
a
so-called
template.
You
can
now
bind
this
with
data
later
on
at
runtime
and
reuse.
A
It
and
reuse
this
same
card
without
having
to
rebuild
the
whole
thing.
All
you
have
to
do
is
send
the
updated
data.
So
that's
templating.
It's
existed
for
a
little
while
now
it
has
been
in
preview
as
we
call
out
everywhere.
We
finally
have
a
pretty
good
plan
on
how
we
can
take
it
out
of
preview.
The
main
thing
that
we
were
waiting
on,
for
example,
if
I
go
to
this
stock
card,
this
data
came
from
another
service.
Iex
trading
offers
financial
data
I
don't
have
any
ability
to
control
this
data.
A
So
when
there's
something
like
open
time
well,
this
is
a
millisecond
offset
number
clearly
I
need
to
format.
This
number
in
a
human
readable
way,
I
need
some
ability
to
take
this
number
parse
it
into
a
date
and
then
display
it
as
you
expect
here.
Well,
this
is
Friday
May
3rd
2019.
There's
a
lot
of
other
examples
like
this,
for
example
the
latest
price.
This
is
a
number
one,
28.9,
that's
a
valid
number,
but
when
you
present
currency
to
humans,
you
typically
use
two
decimal
places.
A
So
what
you
would
expect
to
see
here
is
128
dot
90,
so
you
realize
you
need
some
ability,
usually
to
format
or
shape
or
somehow
coerce
the
data
in
certain
ways,
and
so
we've
had
limited
support
for
that.
You
can
call
functions,
it's
very
similar
to
what
you
might
do
in
Excel,
why
we
wrote
a
function
called
parse
date
for
me
POC,
and
then
we
have
some
kind
of
cascading
ways
of
coalescing
these
functions.
To
do
certain
things.
In
some
cases
you
can
see
some
of
these
expressions.
A
For
example,
if
the
stock
is
trading
up,
then
I
want
the
color
to
be
the
color
good
in
adaptive
cards.
Otherwise,
I
want
to
be
color
attention
and
if
the
text
is
up
or
the
stuff
change,
the
stock
is
up.
I
want
the
up
arrow
to
be
placed
here
versus
the
down
arrow,
and
here
you
can
see.
There's
some
format
calls
here.
So
there's
some
expressions,
part
of
it.
That's
the
term
we're
using,
and
that
string
is
an
expression
and
that's
been
the
last
piece
we
knew.
A
We
didn't
want
to
really
invent
a
new
expression
language.
We
we
did.
Some
research
and
I
just
want
to
give
a
quick
update,
because
in
subsequent
calls
we'll
really
dive
into
this.
But
the
high-level
news
is:
we
found
another
team
in
Microsoft
who
is
doing
very
similar
things.
We
have
a
product
in
the
works
that
is
going
to
basically
join
the
adaptive
family
that
will
solve
and
be
this
reusable
expression
layer.
That's
going
to
solve
a
lot
of
things.
We'll
have
all
these.
A
If
conditions
you
see
we'll
have
some
couple
hundred
of
built-in
functions
that
you
might
expect
like.
Two
upper
to
lower
string
manipulation
all
the
things
you
would
kind
of
expect
so
that
you
can
write
these
reusable
reusable
templates.
Put
enough
power
in
them.
Bind
them
to
data,
and
the
template
itself
is
is,
is
definitely
increasing
in
its
in
its
potency.
So
the
good
news
they're
taking
it
back
to
the
the
portal,
is
that
we
have
a
good
roadmap.
A
There
I'll
share
more
details
in
the
coming
months,
but
we're
pretty
good
that
we
can
land
this
in
in
q2,
so
templating
will
have
built-in
function
and
expression
support
the
power
automate
connector
for
the
service.
I
did
a
preview
that
a
couple
years
ago
or
a
couple
months
ago,
and
it's
still
in
it
still
has
been
released,
there's
some
compliance
stuff.
That
has
to
be
done,
but
this
is
basically
we
have
connecting
to
the
template
service,
the
designer,
with
version
selector
support.
We
had
a
lot
of
comments
on
this
in
random
places.
A
We're
just
doing
kind
of
final
bug,
bashing
and
testing
on
that.
So
that
should
be
should
be
out
pretty
quickly
a
couple
other
templating
things
about
accessing
host
properties
from
within
the
template.
The
template
service
automatically
generating
a
card
from
JSON
scheme
I'm
going
a
little
quickly.
Just
to
summarize
some
quick
updates.
If
you
are
curious
on
all
these
we've,
we've
done
deep
dives
on
most
of
these
things
in
previous
community
calls.
A
So
if
you
should
just
do
a
quick
search
for
our
for
our
blog
post
along
the
months,
if
you're
curious
about
any
of
these,
the
blog
post
will
cover
the
gist
and
then,
if
you
really
want
to
dive
in
click
on
the
call
all
these
community
calls
are
on
YouTube
as
well.
The
only
update
I
said
there
was
a
little
bit
of
possibly
down
news.
The
xamarin
and
xamarin
forms
SDKs.
We
did
a
lot
of
prototyping
trying
to
find
a
realistic
way
that
we
can
release
support
for
these
without
overburdening
our
our
test
matrix.
A
We
had
a
plan,
we
we
did
the
right
thing
and
reevaluate
the
plan
before
we
got
too
far
and
we're
we're
still
making
progress
on
it.
But
I
wanted
to
call
out
that
if
you
were
depending
on
this,
where
we
might
be
a
little
bit
later
than
than
we
thought.
So
if
you
have
thoughts
on
xamarin,
there
will
be
a
survey
at
the
end
of
this
call
with
just
an
open-ended
box,
and
you
can
give
us
feedback
there.
A
If
that
you
know
how,
if
that's
really
like
impacting
your
plans,
the
final
piece
I'll
say
on
this
is
this
tool
is
really
cool,
especially
if
you're
not
a
developer
or
full-time,
and
you
don't
have
github
any
one
of
these
you
can.
Click
on
all
you
have
to
give
us
is
all
you
have
to
add
some
of
the
background
stuff,
because
I'm
logged
in
if
you're
anonymous.
Looking
at
this
all
these
numbers
are
people
basically
telling
us
that
they
needed
this.
This
is
your
opportunity
to
tell
us
what
we
should
be
focusing
on.
A
All
you
need
is
an
email
address.
You
don't
have
a
create
account,
it's
incredibly
low
friction,
and
just
tell
us,
is
this
nice
to
have
critical?
You
can
see.
Our
highest
requested
item
is
input,
validation
and
just
evolving
the
story
of
inputs
and
data
collection.
It
is
something
we're
actively
working
on
a
couple
months
ago.
We
reviewed
the
plan
with
that.
A
A
Let's
take
three
more
minutes
and
then
hand
it
over
to
the
folks
working
on
the
meat
of
the
management
portal.
So
I'll
summarize
with
this
fundamentally
the
lifecycle
of
an
adaptive
card
today
is
we
have
a
set
of
tools
it
centers
around
the
adaptive
card.
Json.
We
have
a
set
of
tools
from
the
card
designer
the
template
service.
What
you're
about
to
see
which
is
basically
a
private
version
of
the
template
service?
A
We've
got
some
power,
automate
options,
but
all
of
these
tools,
including
the
new
integrated
designer
in
power,
automate
they're,
all
helping
you
build
the
adaptive
card,
JSON
that
then
lands
on
an
app
like
teams
or
Outlook
or
your
own
apps
and
then
lands
on
a
platform
and
gets
rendered
natively
to
look
like
that
app.
That's
basically
the
life
cycle,
so
the
interns
which
we're
gonna
see
who've
been
building.
A
This
project
have
been
really
focusing
on
this
left:
half
of
the
story,
finding
new
ways
to
help
teams
of
developers
and
designers,
collaborate
on
building
that
JSON
sharing
the
JSON,
just
basically
a
better
story
which
we've
effectively
left
kind
of
to
each
developer,
to
figure
out
what
works
best
for
them.
So
this
is
a.
This
is
an
attempt
at
really
thinking
about
this
problem
space
with
the
goal
of
helping
organizations
become
more
efficient,
designing
and
then
collaborating
on
adaptive
cards.
A
It
was,
it
is
an
intern
project
here
at
Microsoft
got
eight
fantastic
interns
up
in
Vancouver
BC
working
on
it.
We've
got
a
PM
six
devs
and
a
designer,
and
with
all
that
I'm
gonna
hand
it
over
to
them
to
give
us
a
quick
update
dive
into
some
of
the
code
and
we'll
tell
it
leave
it
up
to
them
to
tee
up
when
if
they
have,
if
you
folks
have
questions,
if
they
want
questions
from
you
and
we'll
make
this
part
a
little
more
interactive.
So
with
that
who
do
I?
Whoever
wants
to
share?
B
Okay,
thanks
Matt
for
introducing
us
hi
everybody.
My
name
is
Sarah
and
I'm,
one
of
the
interns
here
in
Vancouver
who
is
working
on
this
project
and
we
are
working
on
the
management
system
for
adaptive
cards
where
you
can
create
edit
and
share
the
template.
It
comes
in
two
pieces.
It
comes
with
the
other
portal,
as
you
can
see
on
my
screen
right
now,
and
it
also
comes
with
the
API.
So
you
can
fetch
the
templates
in
your
applications
that
you
or
your
friends
or
your
co-workers
have
created
and
published
on
the
website.
B
So
you
don't
need
to
copy/paste
the
JSON
anymore.
You
just
call
the
API
and
it
will
give
you
the
template.
Let's
have
a
look
at
the
website
we
have
made
so
far.
So
when
you
log
into
the
website,
that's
what
you're
going
to
see.
This
is
the
portal.
So,
on
the
left
hand,
side
we
can
see
a
little
navigation
bar
has
some
pages
you
can
browse
around.
This
is
the
dashboard
we
see
you
can
also
create
a
new
template,
see
all
the
templates
that
are
published
on
the
website
right
now.
B
You
can
see
the
drafts
just
set.
The
templates
that
you're
currently
working
on,
but
you
here
haven't,
decided
to
publish
it
yet
so
it's
still
work-in-progress
publish
would
be
the
templates
that
are
already
published
by
you
and
by
the
organization.
So
you
can
see
all
the
published
templates
and
the
work
that
people
share
and
we
also
have
implemented
some
method
to
search
and
navigate
through
the
templates
using
tags.
I
will
dive
into
it
a
little
bit
later
in
the
middle
of
the
screen.
We
can
see
two
portions,
it's
recently
edited
and
recently
template.
B
So
here
we
can
see
the
templates
that
you've
recently
added.
They
might
be
yours,
so
they
might
be
some
other
published
templates
that
you
have
permissions
to
edit,
and
this
is
the
recently
viewed
table.
It's
just
navigation
bar
to
help
you
to
see
which
template
you
have
you
recently
named
and
the
owner
is
not
implemented
yet
so
just
just
heads-up.
That's
why
it's
on
title
and
a
username:
let's
go
through
the
workflow.
How
would
create
and
publish
and
share
the
template?
So
I
would
click
new
template.
B
A
B
B
And,
as
you
can
see,
it
appeared
and
recently
edited
on
the
dashboard,
so
you
can
click
on
it
and
it
will
open
the
preview
page
of
the
template
in
the
middle
of
the
screen.
You
can
see
the
preview
of
the
template
being
really
rendered
all
screens
and
on
the
right-hand
side
you
can
see
a
little
bit
of
information
about
the
template,
so
every
template
can
have
multiple
versions.
Currently
this
is
version
number
1.0,
because
we've
just
created
it.
B
We've
decided
to
implement
some
versioning
to
allow
people
to
make
changes
to
the
templates
if
they
want
to
and
not
break
somebody's
else
code
who
is
already
using
previous
version.
So
let's
say
you've
created
version
number
1.0
and
some
of
the
developers
or
your
co-workers
or
friends
are
using
this
version
of
this
template
to
display
you
are
in
their
application.
But
then
you
suddenly
decide
that
oh
I
want
to
change
the
design
a
little
bit.
B
B
A
Just
to
make
sure
everyone
is
is
aware
of
the
flow
that
he
just
mentioned
is
the
working
thought
here
is
that
this
is
an
organization
that
has
two
different
groups:
one
creating
the
card.
Maybe
it's
a
designer,
that's
their
role,
they're,
creating
the
card
and
saving
it
here
in
this
in
this
user
friendly
experience,
but
later
on,
someone
else
is
going
to
consume
that
template
and
then
fill
it
with
the
with
the
data.
A
That's
what
we
talked
about
the
templating
in
this
case
you're
seeing
static
data
into
it
if
you're
gonna
demo
that
later
I
apologize,
I
just
cut
cut
that
off.
But
the
theory
here
is
that
you
would
create
a
template
without
the
static
data.
So
this
issue
where
it
says,
spelling,
error
and
readme
that
would
be
provided
later
at
runtime.
They
would
there's
a
REST
API
powering
this,
so
they
someone
else
some
developers
somewhere
would
fetch
this
template
version.
1.0
version
1.1
pass
in
the
data
and
then
send
it
to
to
the
app.
B
B
So
when
you
publish
the
version
of
the
template,
it's
gonna
be
live
well,
CL
works
later.
This
is
a
little
date.
One
the
template
was
created,
and
here
we
have
four
for
let's
say
buttons:
you
can
edit
that
template
in
the
designer
you
can
delete
it.
You
can
share
it.
It
will
give
a
shareable
link,
will
I'll
demonstrate
it
later
and
you
can
publish
it
here.
We
can
see
the
owner
of
the
template.
B
This
can
be
a
little
picture
in
the
name
and
the
usage,
so
usage
will
display
some
statistics
about
a
template
and
how
many
people
have
used
it
and
requested
it
using
the
API.
So
if
you're
wondering,
if
someone
is
using
your
template
or
how
many
people
are
doing
this,
you
can
see
it
here.
You
also
have
a
little
feature.
It's
called
the
tags
I
have
mentioned
here.
You
can
add
a
tag.
So
it's
tag
github
to
this
template.
B
C
B
So
this
project
is
open
source
as
well
as
adaptive
cards.
We
are
trying
to
build
it
as
an
NPM
package,
so
you
can
install
our
entire
service
and
host
it
on
your
local
machine
or
your
tenant,
and
you
will
get
all
the
UI
in
all
the
backend
as
well,
and
the
beauty
of
it
that
all
the
components
that
you
require
for
authentication
and
the
storage,
meaning
the
database,
our
pluggable.
So,
for
example,
currently
we're
using
Azure
Active
Directory
to
authenticate
when
we
login
into
the
portal
and
for
storage
we're
using
MongoDB.
B
But
when
you,
when
you
will
download
our
package,
you
won't
have
to
do
that.
We
made
the
interfaces
pluggable,
so
you
can
plug
your
own
identification
provider
as
well
as
your
storage,
so
you
will
be
able
to
use
it
with
SQL
or
with
no
SQL
or
with
any
popular
database.
We
don't
know
what
we're
gonna
implement
exactly
yet,
but
the
idea
is
that
database
and
taunted
the
kitchen
is
gonna,
be
pluggable,
as
you
want
yeah.
A
B
So
here
we
got
attack,
you
can
attach
a
tag
to
the
template.
So
when
you
search
or
categorize
your
templates,
you
can
group
it
by
tags
a
little
lower.
We
see
a
little
table.
That's
called
recent
releases.
It's
little
table
that
displays
the
versions
of
this
template.
That's
already
made
so
currently
we
only
have
version
1.0
and
it's
in
the
draft.
So
what
I
would
like
to
do
right
now?
B
I
would
like
to
publish
the
template
and
then
I
will
share
it
with
Jessica
rpm
and
she
will
try
to
send
this
template
using
our
API
to
the
Microsoft
teams.
So
click
publish
now
it's
published
and
the
version
1
is
live
and
now
I
can
click
share.
So
here
you're
provided
the
link
like
in
Google
Docs,
for
example.
When
you
want
to
share
your
document,
you
copy
the
link
and
you
click
Share.
B
Now
the
template
is
shirt.
So,
if
I
follow
the
link
as
little
little
back
in
here,
this
is
what
it
would
look
like,
and
this
is
the
preview
page.
When
you
follow
the
shared
link,
you
can
see
the
template
and
the
JSON
that
it
comes
with.
You
cannot
edit
anything
or
brush
it,
and
it's
gonna
be
available
to
everyone,
whether
you
are
dedicated
owner.
So
right
now,
I'm
gonna
hand
this
link
to
Jess,
so
she
will
send
it
to
the
Microsoft
teams
through
the
flow.
So
the.
D
D
What
I'm
thinking
is
I
wanted
to
make
this
github
issue
bot
that
renders
this
github
issue
card
on
team's
channel,
so
I'm
going
to
use
power
automate
to
make
a
flow
and
use
a
CMS
API
to
get
the
card
we
pre
made
the
flow
yesterday.
So
if
I
go
too
slow,
basically,
what
it
does
is
using
a
CMS
API
to
get
the
card
and
render
it
on
the
team's
channel,
so
I'm
going
to
manually
trigger
it
for
now,.
D
D
There
you
go,
you
can
see.
The
github
card
is
rendered
by
flow
from
this
demo.
I
wanted
to
point
it
out
couple
benefits
of
using
a
CMS.
In
this
scenario,
let's
say:
seven
wants
to
update
his
design
of
cart
with
a
CMS.
The
updating
process
is
really
easy
and
simple
I'm
said
well.
Do
you
want
to
edit
it
so.
B
Here,
I'm
back
to
the
template
preview
page-
and
here
we
have
a
little
button
edit
in
the
designer.
So
if
I
click
it,
it's
gonna,
take
me
to
the
designer
with
the
template.
So
let
me
change
the
name:
I'll
change
it
to
bad
man.
Here,
I
got
something
else:
I
can
delete
this
line,
okay,
okay,
so
and
then
I
will
save
the
template
finish.
B
B
B
Then
it
creates
a
new
shared
link
for
that
version,
and
here
we
can
see
all
the
versions
that
have
been
added
to
this
template.
So
every
time
you
click
Edit
in
the
designer
and
you
save
it
again,
it
will
create
a
new
version
and
it's
gonna
be
in
the
draft
by
default,
but
you
can
publish
it
and
then
share
with
other
people,
so
they
can
use
okay,
I
think!
That's
all
for
me.
For
today.
D
C
D
There
is
a
way
to
take
the
latest
version
so
now
that
sort
of
updated
it
if
I
wanted
to
use
the
updated
version,
there's
a
two
way
to
do
it
so
first
way
as
to
when
I'm
making
the
flow
I
can
specify
subversion.
Here,
like
let's
say,
if
I
sat
1.2,
it
will
always
get
to
1.2,
but
if
you
want
to
get
the
latest
version,
always
just
live
with
the
version
parameter
ante,
then
it
will
always
get
the
latest
version.
C
D
A
Just
to
make
sure
I
understand
what
you're
showing
here.
So
this
is
basically
just
connecting
the
front
end
that
seven
was
showing
when
he
click
Save.
That's
taking
the
template
as
he
designed
it,
saving
it
in
a
database
and
it's
also
exposing
it
via
that
REST
API
right
and
then
you're
just
connecting
to
that
REST
API
from
here,
okay,
yeah
you're,
just
basically
building
up
the
the
query
string
right
there,
so
you're
just
showing
how
we
would
consume
it
from
power
automate.
A
D
E
Just
to
add
on
to
the
managing
multiple
versions,
we're
working
on
a
feature
right
now,
where
you'll
be
able
to
do
like
batch
operations
on
multiple
versions.
So
if
you
go
back
to
like
that,
template
info
page
on
the
right
hand,
side
there's
like
a
little
list
of
the
versions
and
there's
a
little
manage
button.
If
you
click
that,
then
there
will
basically
be
like
a
list
of
checkboxes
and
then
yeah.
So
if
you
go
down
to
the
recent
releases,
part
there's
like
a
little
manage
button.
E
E
This
is
our
architecture
for
our
project:
I'm
gonna
start
at
the
very
bottom
with
the
database,
so
this
actually
stores
the
templates
that
we
make
and
the
metadata
about
the
templates,
so
the
owner,
the
state
that
the
template
is
in
whether
it's
in
draft
it's
live
or
it's
implicated
and
some
additional
information
like
a
version,
as
seven
mentioned
before
this
is
pluggable.
So
right
now,
we've
implemented
this
as
using
MongoDB,
but
in
the
future
you
might
be
able
to
use
something
like
a
sequel
server.
E
So
about
that
we
have
our
back-end
library,
the
adaptive
cards
templating
service.
This
is
an
NPM
package
and
this
includes
a
storage
provider
layer
and
an
auth
provider
layer
so
focusing
on
the
storage
provider
provider
layer.
First,
it's
basically
a
database
adapter.
So
it's
what
connects
the
back-end
libraries
idea
of
the
template
models
and
how
they're
structured
to
how
it's
actually
stored
in
the
database
right
now
we
have
this
implemented
for
MongoDB.
We
have
a
MongoDB
adapter
and,
in
the
future,
we'll
be
able
to
add
other
adapters
that
support
different
databases.
E
Next
we
have
the
authentication
provider
layer
so
similar
to
the
storage
provider
adapter.
We
have
an
auth
provider
adapter
right
now.
We
have
this
implemented
for
Azure
Active
Directory,
but
in
the
future,
we'll
be
able
to
add
more
adapters
to
support
other
a
provider's
such
as
Google
authentication,
so
that
you'll
be
able
to
select
which
stores,
Rider
and
which
provider
you
want
to
use.
When
you
instantiate
the
package
in
this
back-end
library,
it's
also
basically
the
data
layer,
it's
where
all
of
the
heavy
lifting
is
done.
E
So
getting
all
your
templates
keeping
track
of
the
recently
viewed
recently
edited
templates
and
keeping
hit
usage
on
the
templates
that
are
published
and
keeping
track
of
who
has
permissions
to
view
which
templates.
So
this
back-end
library
also
has
routers
that
redirect
to
specific
functions
that
do
this
heavy
lifting
because
of
this
JavaScript
developers
or
typescript
developers,
can
also
directly
install
this
NPM
package
to
get
all
this
back-end
functionality
as
well,
and
they
be
able
to
add
in
their
own
storage,
Rider
and
off
provider.
Here,
above
that
we
have
our
no
GIS
web
server.
E
This
is
basically
what
where
we
specify
our
end
points,
and
then
we
hand
it
off
to
the
NPM
package
to
do
the
actual
routing
and
to
do
the
heavy
lifting
and
to
connect
to
the
database
and
do
authentication
and
so
another
layer,
above
that
we
have
our
client
SDKs.
These
are
basically
the
SDKs
that
make
it
easier
to
do.
Http
requests
to
our
web
server,
so
they're
auto-generated
by
swagger,
and
currently
we
have
a
JavaScript
client
SDK
for
our
own
front-end,
app
that
salmon
demoed
earlier
and
a
c-sharp
one.
E
If
you
were
trying
to
develop
an
app
to
access
this
template
service,
but
you
weren't
using
JavaScript
typescript
and
you
couldn't
directly
install
the
NPM
package.
You
would
be
able
to
install
the
client
SDK
instead
and
then
serve
up
your
own
or
run
your
own
web
server
and
then
use
a
client
SDK
to
easily
access
the
service
through
your
web
server
or
through
the
client
SDK
to
the
web
server.
And
then,
above
that,
we
are
using
our
JavaScript
client
SDK
right
now
to
serve
up
our
back-end
functionalities.
To
our
react.
E
A
A
This
is
effectively
we're
entering
the
Q&A
portion
of
the
evening,
so
feel
free
we'll
go
through
these
and
then,
as
we
get
into
it,
we'll
people
can
feel
free
to
unmute
and
ask
some
questions,
but
we'll
start
by
just
just
going
down
so
I'll
start
and
tee
them
off
and
kick
it
over
to
you
find
folks
when
they're
what
the
questions
are
about
the
Improv
the
project.
So
all
right
going
back
some
some
waves,
good,
very
nice
power,
automating
adaptive
car
is
good,
you're,
good,
the
expression
layer.
People
seem
excited
about
roadmap
page.
A
C
A
It's
come
up
a
couple
times:
I
need
to
find
the
right
people
to
reach
out
to
I.
Don't
have
an
update
there.
If
you
want
to
send
me
an
e-mail,
though
that's
the
thing.
Let
me
share
this
really
quickly:
I'll
reshare
my
screen
and
my
email,
I'll
put
it
in
the
chat
or
Dana,
because
my
computer
is
acting
slow
if
you
want
to
just
put
it
in
there,
but
it's
Matt
Heidegger
at
microsoft.com,
and
you
can.
C
C
Community
call
that
comes
up,
so
we
can
maybe
it's
usually
the
third
Wednesday
of
the
month,
but
this
month
it
happens
to
be
the
fourth
Wednesday.
So
it's
on
the
25th
this
month.
I
can
send
you
guys
a
link
to
that,
but
then
Matt
and
the
power-ups
team
can
work
on
this
and
we
can
bring
some
information
back
back
to
this
call
in
particular
as
well.
Yeah.
C
A
So
is
there
an
option?
This
is
for
just
and
you
folks,
is
there
an
option
to
save
a
comment
in
relation
with
the
version
change.
I
think
this
is
when
you
click
Save
I
saw
when
you're
sharing
I
think
when
you
click
publish
there
is
a
way
to
put
optional
notes.
Is
that
the
same
with
savers
that
only
at
publish
time.
D
A
D
A
Okay,
okay,
so
I'm
going
to
consider
while
you're
here
in
in
the
design.
The
next
question
is:
is
there
an
icon
or
an
ability
to
indicate
the
host
app?
In
this
view
and
I?
Think
one
of
our
screens
you've
got
shows
the
host
app
drop-down,
so
you
will
be
able
to
preview
the
template
in
different
host
apps
yeah.
A
A
What,
and
by
the
way,
if
I'm,
not
answering
the
questions
properly,
please
just
follow
up
I'll,
just
kind
of
go
through
them
really
quickly,
but
we're
here
to
make
sure
you
get
your
question
answered.
So
Tim
asks
what
happens
when
you
delete
a
template
with
frequent
usage.
Will
there
be
a
warning
or
delete
disabled
for
live
templates,
yeah.
D
Currently,
if
you
delete
delete
the
live
pump
it
there
there,
the
warning
sign
should
pop
up
on
the
admin
portal,
but
right
now
for
our
MLP,
there's
no
warning
sign
to
the
people
who
are
using
the
API
they'll
get
the
4/4
era
when
they
find
the
API
and
then
on
the
on
their
website.
They'll
go
look
at
the
poor
for
error
and.
A
To
provide
context
between
MLP,
so
I
sort
of
glossed
over
this
but
Jessica
said
grace
all
the
folks
that
you
saw
today
again
they
are
their
interns
here
for
16
weeks
and
they've,
basically
teased
this
project
into
MVP,
so
a
Minimum
Viable
Product,
which
is
effectively
what
you're,
seeing
now
and
they've
just
started
working
on
their
MLP,
which
is
the
minimum
lovable
product,
and
so
some
of
these
things
are
coming
in
we're
trying
to
prioritize
the
the
highest
status
things
because
I
think
they're
here
through,
like
mid-april
we've
got
another
for
some
yaks.
We.
A
A
So
the
next
question
I
might
need
some
more
context.
The
so
SharePoint
list
JSON
in
SharePoint
web
parts,
was
the
full
question.
I
share
points
come
up.
I.
Think
Thomas
asked
one
on
one
of
the
very
first
calls
that
I
met
him
about
a
sharepoint
web
part
and
we
don't
currently
have
any
turnkey
and
end
solution
for
rendering
cards
in
sharepoint
web
parts.
We
do
provide
SDKs
that
would
make
it
doable
if
you
do
have
some
development
expertise
and
knew
how
to
install
the
SDK
and
could
make
that
integration.
A
You
could
absolutely
render
an
adaptive
card
in
SharePoint,
but
as
of
now,
we
we
don't
have
any
out-of-the-box
way
of
doing
it.
Unfortunately,
if
that
didn't
answer
your
question,
please
feel
free,
add
more,
and
there
is
definitely
a
SharePoint
community
call
as
well.
That
I
think
we
link
to
at
the
end.
We
have
a
link
of
all
the
other
calls,
so
it
might
be
something
worth
bringing
up
to
them.
Maybe
someone
has
worked
on
this.
Maybe
someones
developed
it
I'm,
not
a
SharePoint
expert
I.
A
A
Some
love
for
for
Jessica's,
Harry,
Potter
icons,
that's
fantastic
and
cool
some
comments
that
they
liked
it.
So
could
there
be
a
card
designed
and
support
the
load
of
HTML
and
and
support
in
teams?
I,
think
this
question
is
Paula
of
correct
me
if
I'm
wrong,
but
I
think
this
question
is:
is
there
any
ability
to
put
HTML
chunk
or
chunks
of
HTML
within
the
card,
the
either
loaded
up
via
URL
or
not?
And
the
current
answer
is
no
I.
It's
not
on
a
road
map.
As
of
now
it
it
it's.
A
It
it'd
be
really
tricky
to
support
that.
If
I'm
understanding
your
question
properly,
mainly
because
two
of
the
guarantees
that
we
offer
with
adaptive
cards
is
that
they
always
render
natively
and
that
they're
always
styled
as
the
host
app.
So
these
host
apps,
like
teams,
they
get
the
performance
benefit,
and
they
also
know
that
they
can
basically
open
up
their
product
to
the
world.
A
It's
just
take
content
from
the
world,
but
it's
somewhat
constrained
in
sandbox
so
that
they
know
that
they're
not
really
risking
a
poor
user
experience
or
potential
security
flaws
or
anything
so
the
concept
of
injecting
custom
HTML
when
the
card
is
a
little
bit
tricky
to
solve
and
we're
just
not
there.
It's
not
currently
part
of
our
priorities,
specifically
for
actual
messages,
any
chances
where
the
am
debugger
on
outlook,
mobile,
I'm,
not
familiar
with
this
but
I,
think
David
Koh
was
on
the
call.
I,
don't
know
if
he
still
is.
A
C
A
Cool
yeah
that'd
be
great
and
that
one
got
a
heart
reaction
as
well.
So
at
least
two
people
on
our
call
would
be
interested
in
that
so
Thomas
adds
is
the
same
with
poverty
leaders
I
assumed
this
was
a
comment
regarding
something
they
were
demoing
integration.
What
they
see
is
on
the
roadmap
and
should
be
somewhere
in
May
Thomas.
Let
me
know
if
that
was
just
helping
along
with
what
was
on
the
screen
at
the
time,
then
Dana
add
a
link
to
our
survey,
which
gets
me
to
yeah.
Please
do
complete
this
survey.
A
It
means
the
world
to
us
to
understand.
If
these
things
are
useful
to
you,
this
particular
survey
is
less
about
the
community
calls
and
more
about
the
adaptive
card
management
service
Jessica
on
the
team
over
there
put
it
together,
we
mentioned,
we've
got
them
for
about
another
month,
let's
make
it
a
fantastic
month
and
make
sure
they're
delivering
the
value
that
that
you
need.
So
please
let
us
know
if
we're
on
the
right
direction
with
this,
if
we
should
keep
investing
in
it
after
the
internship
ends,
I
do
want
to
reiterate.
A
A
I
don't
want
to
speak
for
the
team,
but
I,
don't
if
it's
quite
at
a
state
where,
where
it's
easy
to
get
started
and
cell
phones,
but
as
you
can
see
from
the
demo,
it's
come
a
long
way
since
last
month,
so
hopefully
by
next
month's
community
call
it'll
be
at
a
state
where
you
could
install
it
and
start
using
it
and
really
start
getting
a
feel
for
some
of
the
offering
and
then
our
hope
is
that
long
term.
We
can
keep
this
project
going
after
the
internship
ends
and
deliver
ultimate
value
for
you.
A
A
If
there's
any
way,
you
could
share
that
with
me
or
the
team
I
we
get
this
question
every
so
often
I,
don't
know
if
it's
in
a
state
like
that,
if
you
share
source
code
again,
I,
don't
really
know
how
SharePoint
works
and
what
the
package
model
is,
but
if
that's
in
any
kind
of
state
that
we
can
share
it
with
our
community
I
think
that
would
be
a
huge
benefit.
I
had
absolutely
you'd
get
a
hundred
percent
credit
where
that
credit
is
due,
but
I
think
it'd
be
great
to
still
that
around.
A
Any
other
questions,
please
add
them.
You
are
free
to
unmute.
I
will
quickly
say.
Please
finish
this.
Please
do
some
colita
survey,
it's
incredibly
short
I
think
it
was
like
five
questions:
resources
to
catch
up
on
things
we
get
in
a
night
ignite
session
about
six
months
ago.
Definitely
go
to
that
AC
features
URL
to
let
us
know
what
features
you
need.
That
was
that
portal
from
the
beginning
get
started
with
adaptive
card.
Templating
we've
got
somewhat
updated
roadmap
through
2020.
A
There
are
plenty
of
Microsoft
365
developer
community
calls
that,
while
we're
super
happy,
you
joined
an
adaptive
cards.
One
there's
plenty
going
on
in
this
ecosystem
and
there's
plenty
of
opportunity
for
all
of
us,
with
the
help
of
Dana
to
really
make
sure
we're
cross
connecting
all
these
things
and
really
really
delivering
some
great
and
end
experiences.
A
The
recording
of
this
will
be
available
on
YouTube
by
the
Microsoft
365
developer.
Youtube
channel
you
can
see
there
please
subscribe
I
hear
that
all
the
time
when
I'm
watching
YouTube
you
can
follow
the
account
on
Twitter
at
Microsoft,
365
dev,
you
can
find
me.
I
should
probably
put
this
on
there
I'm
at
Matt
hiding
her.
You
can
find
me
on
Twitter.
The
next
call
will
be
April
9th
at
9:00
a.m.
A
A
Sweet
so
Stacy
and
Dana
are
hopefully
gonna
connect
awesome
any
last
questions:
David
I
I
didn't
get
the
1/3.
If
I
could
guess,
unless
you
add
more
context,
they're
adaptive
cards
1.3
as
our
current
upcoming
release.
1.2
is
our
most
recent
release.
It
was
just
rolled
out
two
teams.
If
you're
asking
about
teams
mobile
they're
now
on
the
latest
release,
Outlook
is
not
on
1.2
and
again
I'm,
just
kind
of
guessing.
A
C
A
Okay,
well,
I,
think
I,
don't
see
anything
else
coming
through
the
chat,
I
appreciate
again
everyone
coming
out
to
make
time
with
us.
Thank
you
for
coming,
we'll
see
you
again
in
a
month
expect
a
call
up
in
a
little
bit,
and
thank
you
very
much
for
joining.
Everyone
have
a
good
rest
of
your
day
or
evening.