►
From YouTube: Adaptive Cards community call-August 2020
Description
On this month's call, we reviewed the Adaptive Cards v1.3 release which includes the most-requested feature of the past 2 years: Input Validation and Input Labels! We also discussed the "Consistent Cards" project and walked through some amazing real-world business processes that can be streamlined and improved using Power Automate.
Speakers: Matt Hidinger, Hammad Hassan, Tomasz Poszytek
Resources
Adaptive Cards v1.3 https://aka.ms/AA9dtlt
Consistent Cards https://aka.ms/AA9ddxp
Adaptive Cards in Power Automate https://aka.ms/AA9d69w
Stay connected
Twitter https://twitter.com/microsoft365dev
Blogs https://aka.ms/M365DevBlog
A
Hi,
everyone
welcome
to
the
august
2020
edition
of
the
adaptive
cards.
Community
call
I'm
matt
heidenger
and
I'm
joined
this
month
with
we've
got
an
action-packed
day
for
you,
our
session
here
with
hamad.
We've
got
a
microsoft
intern
who's
going
to
walk
through
a
peek
inside
of
a
project.
He
started
called
consistent
cards
and
then
tamasha
posha
tech
is
a
power
platform.
Mvp
who's,
gonna
wow
us
with
how
citizen
developers
and
power
users
can
really
take
advantage
of
adaptive
cards
in
some
pretty
compelling
ways.
A
Let's
jump
in
we've
got
three
major
topics:
we
shipped
version
1.3,
it's
a
huge
update,
I'm
going
to
walk
through
how
that
benefits,
cart,
authors
and
hosts
alike
and
we'll
do
a
quick
lap
around
what's
coming
next
and
then
I'll
hand
it
off
to
haman
to
talk
about
the
consistent
cards
project
and
then
to
tomash
to
wrap
it
up.
So
the
1.3
release
was
focused
almost
entirely
on
input,
evolution
and
input
validation,
so
adaptive
cards
can
collect
data.
A
They
have
a
rich
set
of
inputs
and
one
missing
piece
was
labeling
those
inputs
and
validating
those
inputs
directly
on
the
client.
So
I'll
do
a
quick
demo
of
that
and
you
can
follow
along
on
your
own
at
adaptivecards.io.
That's
where
everything
adaptive
cards
lives.
So
what
I'm
going
to
do
is
quickly
change
over
to
my
other
browser.
A
So
again,
everything
adaptive
cards
is
at
adaptivecards.io
and
let
me
kind
of
do
one
of
those
before
you
know
old
and
busted
and
the
new
hotness,
so
the
old
and
busted
way
which
you
still
have
to
use
today,
because
it
hasn't
rolled
out
everywhere,
is
this
way
of
doing
inputs.
So
we
had
inputs.
This
is
one
of
our
sample
cards.
It's
just
a
handful
of
examples
where
it
shows
that
you
can
collect
data
like
okay,
the
name.
You
know.
A
What's
my
home
page,
you
know
matt,
heidenger.com,
etc
and
there's
a
couple
bummers
here,
one
these
placeholders,
they
just
disappear.
You
know
so
I
have
to
I
lose
kind
of
context
of
what
what
that
field
was,
so
the
label
sort
of
goes
away,
which
is
fine,
but
also
you
know,
depending
on
how
advanced
your
form
is,
you
know,
could
be
improved
and
of
course
I
can
submit
this,
and
the
dialog
here
is
showing
what
that
submitted.
Data
includes
and
there's
a
whole
bunch
of
empty
values.
A
So
if
you
wanted
to
make
sure
that
someone
put
a
quantity
in
here
that
wasn't
possible
so
down
towards
the
bottom,
is
the
new
inputs
with
validation
and
another
quick
example.
Well
I'll
just
show
that
kind
of
same
card,
so
this
inputs
with
validation.
So
again,
the
requirement
here
and
why
it's
a
separate
sample
down
at
the
bottom
is
because
this
does
rely
on
version
1.3
of
the
schema
which
is
released
in
the
sdk
form.
So
now
what
that
means
is
all
of
our
host
apps,
such
as
teams,
outlook,
cisco,
webex
teams,
cortana
skills.
A
They
now
have
the
sdks,
and
now
they
do.
They
just
have
to
basically
ingest
those
sdks
and
then
roll
it
out
to
all
of
you.
So
you
can't
actually
take
advantage
of
these
features,
yet
in
teams
or
outlook,
but
we're
keeping
on
them
and
making
sure
that
we
reduce
that
window
between
when
we
finish
the
sdk
and
when
our
hosts
get
to
them
so
stay
tuned
on
when
you
can
start
taking
advantage
of
these
things.
A
If
you
are
rendering
cards
in
your
own
apps
you're
using
our
sdks
directly,
you
can
start
using
this
today
and
what
you're
seeing
on
the
website
is
doing
exactly
that,
and
so
the
change
here
is.
We
change
those
placeholders
to
use
a
new
property
called
label,
and
so
you
can
see
here
there's
this
input
text
and
it's
got
a
label
property
there,
and
it
also
has
these
validation
properties
saying
whether
it's
required
and
what
the
error
message
is.
So
now
I
get
some
nice
ux
improvements.
A
A
And
of
course,
if
I
leave
that
blank-
and
I
try
to
do
this-
you
know
blah
blah
and
I
try
to
submit
this
card
you'll
see
what
it
did.
It
scrolled
up
the
page
focused
that
input
and
showed
that
name
is
required,
so
great
user
experience
much
improved
over.
You
can
see
another
one
here,
accepting
the
terms
and
conditions
is
required.
So
I
have
to
check
this
box
so
there's
validation
on
every
type
of
input,
from
choice
set
to
number
date.
A
The
number
inputs
we
have
always
had
these
min
and
max
values,
and
now
what's
really
cool,
so
they
they
would
restrict
you
in
the
ui
where
supported.
So
you
can't,
actually,
you
know,
click
the
up
beyond
five,
because
I've
specified
that's
the
max,
but
I
can
also
always
type
in
here
right.
So
a
user
can
type-
or
maybe
this
is
like
a
headless
thing
where
I
can.
You
know,
talk
a
number
or
even
put
invalid
letters.
So
now,
if
I
hit
submit
here,
you'll
see
a
few
things
too.
A
The
quantity
must
be
between
negative
five
and
five,
so
min
max
validation
that
works
on
date
times
lots
of
improvements
again
with
these
inputs.
I
will
add
one
thing
slightly
disingenuous:
just
the
way
this
card
was
created
on
the
placeholder
stuff,
so
you
could
always
have
a
text
block
that
serves
as
a
label
and
that's
you
know
what
we've
done
on
this
example,
where
it
says
your
name.
First
last
your
email
but
you'll
notice,
and
that's
just
because
you
have
we
have
a
text
block
here
and
then
the
input
under
it.
Where
are
those
inputs?
A
Let
me
turn
off
the
templating
example,
just
a
simple
one.
So
as
a
typical
pattern,
you
would
see
today
a
text
block
that
says
your
name
and
then
the
input
and
then
a
text
block
and
then
the
input
which
is
pretty
verbose.
It's
not
accessible,
meaning
that
to
screen
readers
or
people
using
assistive
devices.
A
They
have
no
idea
that
this
text
block
is
associated
with
this
input.
So
it's
a
a
very
poor
accessibility
story.
It
also
makes
your
payloads
just
bigger,
they're,
more
reverse
and
the
user
experience
is
worse
because
I
can't
like
click
on
this
label
and
and
have
the
input
focused.
So
a
label
property
goes
a
long
way
towards
taking
stuff
that
you're
already
doing
today
and
just
making
it
much
more
compact,
much
more
powerful.
A
It's
really
nice
that
you
know
the
label
is
just
a
property
right
in
the
input,
so
it
just
these
cards
get
a
lot
smaller.
So
that's
a
look
at
the
1.3
release,
I'll
switch
over
to
one
other
thing.
Before
I
hand
it
off
to
everybody
else
towards
the
end
of
this
call,
there
will
be
a
survey
link.
It's
five
minutes,
we'd
really
appreciate.
If
you
can
give
us
some
feedback.
One
of
the
questions,
though,
is
going
to
be.
A
A
This
is
important
to
them
and
that's
what
made
us
you
know,
focus
and
and
deliver
that
we've
got
a
handful
of
things
coming
up
in
q3
and
into
q4
throughout
the
rest
of
the
year,
a
big
one
templating
on
mobile
sdks,
we're
trying
to
figure
out
how
we
can
build
the
power
automate
connector
for
the
template
service.
So
this
is
all
coming
together
and
a
look
into
the
early
next
year.
A
A
A
These
are
all
the
things
that
get
a
lot
of
feedback,
and
so
this
is
a
tentative
list,
but
just
to
give
you
an
idea,
what's
on
our
radar
for
coming
up
as
well
as
long
term
into
the
future,
things
like
live
data,
binding,
responsive,
ui,
client,
side
updates,
so
you
can
do
like
dynamic
drop
downs.
This
is
your
opportunity
to
really
influence
where
this
product
goes,
and
so
I'll
have
a
link
to
this
we'd
love
to
know.
A
B
B
So
this
summer
I
focused
on
the
problem
of
inconsistency.
So
to
start
off,
I
will
talk
a
bit
about
what
inconsistency
is
so
put.
It
simply
inconsistencies
when
a
card
payload
behaves
differently
across
the
different
platforms,
so
it
might
render
differently
on
different
platforms
or
it
might
render
on
some
of
them
or
fail
to
render
on
some
of
them.
So
we
want
the
behavior
to
be
consistent
across
all
the
platforms.
We
want
it
to
render
consistently
or
fail
consistently
on
all
of
them
and
so
to
test.
B
If
your
a
card
payload
is
consistent,
you
have
to
basically
manually
render
the
card
on
each
of
our
supported
platforms,
and
to
do
that,
you
have
to
basically
use
some
of
the
tools
that
we
ship
so
for
net
and
uwp.
These
are
the
visualizer
tools
for
javascript.
This
is
the
designer
and
for
android
and
ios.
These
are
the
apps
that
we
ship,
but
the
inconvenience
from
these
tools
is
that
some
of
them
built
against
our
source
code,
not
our
publicly
shipped
rendering,
sdks
and
also
they're
not
easily
available
to
everyone.
B
B
So
the
user
b
is
basically
inputting
a
json
payload
that
corresponds
to
an
adaptive
card
and
the
user
clicked
submit
and
then
they're
able
to
see
pictures
of
their
card
rendered
across
some
of
the
platforms
that
we
support
and
at
the
back
end
it
is
using
the
rendering
sdks
that
we
should
publicly
to
take
that
card.
Payload
parse
it
and
render
it
on
each
of
the
supported
platforms.
B
B
And
then
this
backend
is
connected
to
a
bunch
of
cloud
hosted.
Rest
api
is
written
in
python
fast,
so
the
rest
endpoint
basically
sends
the
users
inputted
json
payload
to
each
of
these
rest
api
via
http,
post
and
then
each
rest.
Api
is
connected
to
a
driver
program
corresponding
to
each
platform
that
that
my
project
supports
and
so
the
rest
api.
Since
the
users
inputted
json
payload
to
this
driver
program
for
javascript
and
dot
net,
it
starts
the
dart
program
as
a
child
process
and
communicates
over
certain
and
standard
for
uwp
and
android.
B
Here
are
some
of
the
details
of
how
the
request
handling
works.
So,
as
I
explained
earlier,
the
user
inputs,
a
json
data
for
the
card
and
the
web
interface
sends
this
json
to
the
flask
app
by
http
post.
The
flask
app
sends
it
to
the
driver
program
via
standard
and
and
then
the
driver
program
parses.
The
json
renders
the
adaptive
card
takes
the
screenshot
converts
it
to
basic
super
encoded
string
and
sends
it
along
with
warnings
and
errors,
and
then
the
flask
app
sends
this
back
to
the
web
interface
and
the
web
interface.
B
B
So
once
I
paste
this
payload
here
and
I
click
submit,
so
I
should
hopefully
be
able
to
see
this
card
across
the
platforms
that
we
support.
As
you
can
see,
this
is
that
card
payload
rendered
using
the
javascript
printing
sdk.
They
did
the
pf
android
and
uwp.
So
this
is
the
card
payload
and
it
was
actually
rendered
on
each
of
these
platforms
and
the
screenshot
was
taken
if
there
were
any
warnings
or
areas
that
were
generated
during
the
process,
those
would
have
been
shown
directly
underneath
and
you
might
notice
some
differences
in
the
buttons
like.
B
So
these
are
per
platform,
and
that's
just
how
this
card
looks
like
on
android.
So
these
are
platform
details.
So
now
you
may
have
noticed
that
we
have
data
in
template
and
this
corresponds
to
templating
that
we
introduced
in
may.
So
my
project
currently
supports
both
templated
and
non-templated
cards
and
to
demonstrate
that
I'll
just
take
a
quick
look
at
this
card
and
see
how
that
renders
so
I'll
just
copy
the
data.
B
Yeah,
so,
as
you
can
see,
I've
just
been
shown
that
templated
card
on
across
all
of
our
platforms.
Now
you
might
be
thinking
my
android
looks
the
way
it
does,
and
that's
simply
that
we
haven't
yet
introduced
templating
on
android.
So
if
you
do
try
to
render
a
templated
card
on
android,
then
that
is
how
it
would
look
like.
But
in
the
future,
when
we
do
introduce
templating
on
android,
it
will
look
pretty
much
similar
to
the
rest
of
the
platforms.
B
But
you
know
it's
pretty
good
that
we
can
use
both
templated
on
non-templated
cards
and
in
a
way
you
can
actually
see
how
the
templated
card
would
look
like
on
android.
If
you
tried
and
so
a
bit
about
the
future
of
this
project,
I'm
currently
focusing
on
the
deployment
right
now.
Most
of
it
is
working
on
my
local
machine,
but
that's
what
I'm
focusing
on.
So
one
of
the
areas
that
I'm
working
on
is
docker
containers,
docker
containers
and
another
area
that
I'm
looking
into.
B
Is
these
hosting
services
like
expo
appetize,
test
cloud
where
I
can
host
my
android
or
android,
uwp,
apps,
and
so
another
area
that
we
do
need
to
focus
on
is
implementing
the
ios
part
of
this
project.
So
if
we
do
implement
it,
it
will
be
quite
similar
to
how
android
and
uwp
work
and
one
of
the
nice
features
about
the
architecture
of
this
project-
is
that
each
piece
that
I
showed
you
earlier
is
individual.
B
So
we
can
pick
and
choose
which
pieces
that
we
want,
and
so
in
terms
of
that
it
offers
us
the
flexibility
of
using
or
taking
the
other
pieces
of
this
project
and
using
them.
How
you
want
so
an
example
can
be
in
our
designer
right
now.
You
can
just
click
preview
and
render
the
card
using
the
javascript,
rendering
sdk
and
see
how
it
looks.
But
in
the
future
you
can
one
of
the
areas
can
be
that
we
can
add
drop
down
or
something
where
you
can
just
place.
B
A
Awesome
that
is,
super
cool
to
see
and
the
progress
keeps
getting
better.
A
quick
note
on
templating
too,
so
one
big
piece
of
our
roadmap
that
we're
really
hoping
to
land
is
to
get
templating
working
on
the
mobile
sdks
by
the
end
of
the
year,
so
that
android
demo
would
start
working
and
it
gets
us
towards
where
we
can
start
having
templating
directly
in
apps,
like
teams
etc.
A
C
There
is
this
new
functionality
that
allows
you
to
record
you
talking
your
name
and
last
name
so
that
anyone
viewing
your
profile
on
mobile
can
just
hit
this
small
microphone,
sorry,
speaker,
icon
and
then
listen
to
how
you
should
pronounce
that
person's
name
and
last
name.
So
that's
a
cool
feature,
but
anyway
I
know
yeah.
So
this
is
a
new
edition.
It's
just
like
brought
out
this
month.
So
I
know
it's
not
easy,
but
now
we
can
try.
C
Always
I'm
working
with
with
this
technology
for
years
and
for
like
four
years
already
with
office
65-
and
I
am
mmvp
business
applications
to
be
precise,
but
per
platform
is
the
area
that
I'm
really
working
on
very
hard
and
then
sharing
the
community
and
working
with
the
community.
So
you
can
find
me
on
twitter.
You
can
find
me
on
my
blog.
You
can
find
me
on
youtube
linkedin
like
wherever
you
want.
I
should
be
there
like.
C
There
should
be
this
shortcut,
aka
dot,
ms
slash
slash,
posh
attack,
but
I
think
it's
still
pointing
to
my
blog,
but
anyway,
that's
all
about
me.
So
speaking
about
the
power
automate
and
adaptive
cards,
what
the
big
picture!
The
message
that
I
wanted
to
tell
you
is
that
I
don't
actually
know
from
what
specific
area
you're
originating
if
you
are
power
users
or
if
you're
developers
like
I
know
there
is
team
with
us
tim
gardenbach,
who
is
able
to
build
almost
entire
websites
using
only
adaptive
cards.
I
am
not
I'm
just
a
power
user.
C
C
C
But
when
I
checked
it
yesterday,
the
roadmap
says
that
adaptive
cards
are
coming
to
pva
in
january
next
year,
so
due
to
all
those
difficulties
we
had
with
kovit,
this
functionality
is
also
postponed,
but
I
know
that
it's
not
only
much
responsibility,
but
microsoft
is
always
looking
internally
at
the
technology
and
that
adaptive
cards
as
the
sdk
is
implemented
in
in
services
like
cortana
like
skype.
I
think
as
well
in
about
framework
of
course.
C
So
if
you
are
doing
your
own,
if
you're
writing
your
own
bot,
then
you're
able
to
benefit
from
adaptive
cards
already
and
this
will
be
possibly
put
into
another
or
more
communication
focused
tools
that
microsoft
has
so
back
to
the
topic.
When
I
want
to
build
a
process
when
I
want
to
really
engage
users,
and
since
I'm
just
a
power
user,
not
a
developer.
I
said
I'm
trying
to
use
microsoft
teams
and
outlook
as
those
tools
that
I
primarily
choose
for
communication
around
the
process.
C
C
Any
way
you
choose
to
author
adaptive
card,
you
can
then
put
it
in
here
and
start
actually
using
it
in
microsoft
teams.
Of
course,
you
can
as
well
put
their
dynamic
values.
So
if
you
have
logic
in
power
automate
that
is
first
used
to
obtain
information,
then
inside
adaptive
cards
code
you
can
put
outcomes
of
the
previous
actions
and
they
they
are
rendered.
C
What
is
also
important
is
that
today,
unfortunately,
the
templating
in
microsoft
teams
is
not
fully
supported.
It
only
supports
actually
the
very
basic
definition
of
the
inline
placeholders,
like
once,
we
jump
to
adaptive
card
designer
what
we
can
actually
try
to
do
with
microsoft.
Teams
are
those
simple
expressions
like
this
one,
so
today
we
can
actually
just
use
those
simple
placeholders
that
refers
to
a
single
value.
C
We
can't
use
any
other
benefits
from
templating
that
I'll
try
to
show
you
as
well
a
little
bit
of
like
what
I
was
able
to
do
with
power
automate
from
the
box
and
what
I
would
be
able
to
do
with
power
automate
if
the
templating
was
working
and
was
fully
supported,
I
want
to
show
you
what
we
actually
can
do.
First,
starting
with
triggers
so,
for
example,
imagine
that
since
previous
month
we
have
in
power
automate
the
trigger
that
we
can
use
in
microsoft,
teams
that
we
can
use
to
help
us
govern
microsoft
teams.
C
Actually,
so
any
process
related
around
microsoft
teams,
governance
and
especially
messages
can
be
enhanced
or
enriched
with
this
new
trigger.
So
once
you
navigate
to
microsoft
teams,
and
then
you
can
here
find
a
trigger
that
is
called
for
a
circuit
message.
Now
this
trigger
lets
you
to
author
an
adaptive
card
and
then
define
its
width
and
height.
That
will
be
shown
once
a
user
hit,
the
ellipsis
icon
and
on
the
microsoft
teams
channel
and
a
message.
So
let
me
show
you
how
it
works
and
what
you
actually
can
do
with
that.
C
So
this
is
just
a
regular
microsoft
teams
channel
with
a
lot
of
posts.
Some
of
them
are
just
a
spam
and
well
let
me
just
switch
to
a
different
user.
So
that's
the
account
microsoft
teams
of
a
journal
researcher,
the
another
user
that
is
present
on
my
on
my
tenant
and
john
finds
this
beautiful
post
with
a
gif
as
an
offensive
or
oh
disturbing.
C
So
because
I
have
this
new
channel,
this
new
trigger
already
used
for
one
flow.
It's
that's
the
name
of
the
flow.
Actually,
then,
once
I
hit
it,
it
will
trigger
this
adaptive
card
that
I
have
altered
for
this
case,
and
so
with
that
john
is
able
now
to
say
what
is
actually
what
what
he
would
like
actually
to
do
with
this
specific
message.
C
C
That
is
already
mentioning
the
author
of
this
previous
message
with
information
that
hey
we,
we
are
send
a
report
and
this
message
is
under
investigation,
so
just
be
aware
that
something
is
wrong,
and
now,
since
I
am
the
microsoft
team's
admin
here
on
this
tenant,
so
now
that's
my
account
in
a
separate
channel.
I
have
received
this
message
request
with
information
that.
C
That
the
user
john
researcher,
has
actually
reported
this
following
message
from
test
user
as
an
offensive
because
well
he
don't
like
like
gifts
in
the
communication,
and
so
I
can
now
navigate
to
this
message.
So
you'll
notice
that
right
now
teams
opens
this
message
and
highlights
it
with
this
yellow
color.
So
I
can't
say
that
I
don't
know
what
message
we
are
talking
about
plus
well.
This
is
an
example
of
an
action
that
actually
posts
an
adaptive
card
to
a
team's
channel
and
is
waiting
for
the
response.
C
C
The
card
is
going
to
be
closed
with
this,
not
very
fancy
automatic
card
plus
me
as
a
general
researcher
for
the
reporter
in
my
chat
window,
I
don't
at
information
from
well
again
from
flow
that
this
message
I
have
reported
has
been
taken
care
of,
and
so
how
was
this
actually
done?
How
was
all
these
steps
done?
So?
First,
let
me
just
refresh
it
and
then
it
will
be
easier.
C
So
first
thing
is
the
trigger
that
I
mentioned
that
allows
us
to
create
a
workflow
that
is
then
being
displayed
under
those
ellipses
icon,
then
more
actions.
So
the
number
of
flows
you
create
with
this
trigger
will
be
shown.
Then,
under
those
ellipses
icon
for
other
users,
then
note
that
those
names
of
flows
have
to
be
quite
short
because
they're
really
enlarged
and
they
will
not
fit
into
the
width
of
this
sub
menu,
and
so
once
it
is
triggered.
C
C
C
Next
posting
adaptive
card
to
the
administrator
and
waiting
for
the
response
so
he's
waiting
until
the
administrator
is
actually
somehow
reacting
to
this
message
and,
lastly,
he's
posting
a
message
to
the
user,
who
reported
it
that
this
flow
has
been
completed
and
the
message
is
taken
care
of.
So
this
short
demo
is
actually
showing
all
nearly
all
those
actions
that
we
have
in
microsoft:
teams
stuck
in
power
automate
that
helps
us
to
enhance
those
business
processes
with
interactive
adaptive
cards
that
we
can
send
to
microsoft.
C
Teams
that
we
can
use
to
get
feedback
from
the
user
that
we
can
get
their
inputs,
and
so
the
process
is
really
moving
on.
Without
actually,
this
need
that
a
user
has
to
navigate
away
from
microsoft
teams
that
they
have
to,
for
example,
open
microsoft
teams,
tasks
or
they
have
to
go
to
exchange,
to
outlook,
to
check
their
email
or
to
even
go
to
sharepoint,
to
open
tasks
and
to
do
something
there,
like
everything,
actually
is
happening
inside
microsoft
teams.
C
What
makes
users
less
confused
and
less
frustrated
that
they
have
to
well
just
navigate
between
applications,
systems
and
waste,
their
time
on
on
searching
where
they
have
to
click
and
what
they
have
to
do
in
the
next
step.
Now
the
second
example,
maybe
more
business
oriented,
I
want
to
show
you
is
somehow
related
to
the
invoicing
processing.
So
here
I
have
this
small
application
that
is
being
used
to
scan
invoices,
and
there
is
an
air
builder
underneath
that
is
going
to
help,
and
so
once
I
upload
here
this
new
invoice.
C
C
C
So
again,
the
the
accountancy
don't
have
to
actually
go
from
their
team's
channel
where
they,
whether
collaborate
and
contribute
on
documents
to
sharepoint,
for
example,
or
some
other
file,
storage
or
well
any
other
place.
But
I
have
all
the
information
they
need
to
handle
to
process
this
new
invoice
in
place.
So
let
me
just
send
it
for
approval,
and
now
what
is
happening
underneath
is
actually
a
quite
a
complex,
workflow
being
triggered
that
process
the
information
from
that
invoice
and
is
trying
to
rebuild
this
invoice
as
a
very
fancy.
Looking
adaptive
card.
C
That
shows
all
the
information
that
is
info,
important
from
the
accountancy
perspective,
plus
information
to
or
the
possibility
to
approve
or
reject.
What
I
could
adhere
as
well
would
be
like
a
small
button,
maybe
somewhere
on
the
top
right
corner
to
click
and
to
open
the
actual
physical
document
stored
somewhere
on
sharepoint,
so
that
they
can
compare
the
values
if
they
are
correct
or
not.
C
C
C
C
C
There
was
a
little
bit
of
struggle
to
actually
accomplish
that.
Finally,
once
this
whole
adaptive
card,
json
code
is
built
merged,
concatenated,
whatever
it's
being
sent
to
a
channel,
as
you
saw
and
that
works
now,
if
you're
anyhow
familiar
with
ai
builder,
then
you
already
know
that
what
albeeter
is
actually
returning
to
power,
apps
or
into
power
automate
can
be
as
well
a
very
regular
json
format
of
a
data
with
the
templating.
C
This
is
a
json
that
stores
data,
and
here
we
have
just
the
reference
to
okay.
You
just
can't
see
that,
but
there
is,
there
is
somewhere
here,
yeah
the
profile
image
here
right.
So
this
is
just
the
reference
placeholder
that
that
active
card
now
might
correct
me,
but
the
personal
parser,
but
generator
from
the
on
the
on
the
host,
is
replacing
this
placeholder
with
the
actual
value
from
the
data.
C
C
C
So
here
is
the
adaptive
card
pieces
and
another
piece,
then
there's
another
piece
of
adaptive
card
that
I'm
just
concatenating
and
everywhere.
Here
you
can
find
that
they're
just
those
outcomes
from
previous
actions
replacing
just
the
pieces
of
that
object.
I
mean
not
not
replacing
but
are
being
put
and
then
actually
replaced
by
the
power
automate
to
finally
generate
an
active
card,
complete
code
now
with
the
templating.
What
I
could
do,
I
could
simply
provide
those
placeholders.
C
C
C
And
then,
once
I
okay,
well
I'm
just
just
one
thing.
What
is
also
important
here
is
that
the
items
from
the
from
the
invoice
are
presented
here
as
a
table
in
a
json,
and
that
means
I
mean
this.
This
is
read
by
the
by
the
templating
language
that
it
has
to
be
actually
generated
for
each
item
in
the
table,
so
that
the
scope
for
binding
of
this
table
should
be
multiplied
by
the
number
of
items.
C
So
now,
once
I
switch
from
the
designer
into
the
preview
mode,
you'll
notice
that
to
them
the
table
has
been
automatically
generated
just
based
on
the
data.
So
I,
if
the
templating
was
working
in
microsoft
teams,
I
wouldn't
be
able
really
to
I
shouldn't-
be
able
to
shouldn't,
be
forced
actually
to
build
this
on
on
my
own
and
then
display
it,
but
that
would
just
work
like
a
charm
magically.
So
this
is
an
actually
power
of
the
templating
plus
you
can
see
here.
C
C
C
C
C
C
We
can
actually
make
all
these
processes
a
lot
of
simpler
for
the
end
users
more
understandable
and
then,
if
we
also
decide
to
use
microsoft
teams
as
a
platform
to
host
the
processes
to
really
put
in
a
center
of
focus
of
the
everyday
collaboration
of
our
employees.
Therefore,
we
are
actually
able
to
build
a
very
powerful
machine
that
will
help
them
to
be
members
of
those
processes
without
those
additional.
C
You
know
frustration
orientation
that
they
have
to
just
switch
those
applications
in
between
and
the
adaptive
cards
that
I
showed
you
are
really
simple
to
be
built
and
well,
I'm
really
looking
forward
for
the
new
versions
of
the
sdk
to
be
fully
implemented
and-
and
I
just
lost
the
word
but
anyway
today,
in
microsoft,
teams
we
are
running
version
1.2,
but
not
in
full
compatibility
on.
I
mean
it's
not
covering
the
full
functionality,
the
version
1.3
matt.
Maybe
you
have
some.
C
Maybe
you
heard
some
rumors,
maybe
by
the
end
of
this
year,
maybe
maybe
sooner
but
anyway,
just
just
try
to
work
with
adaptive
cards
yourself.
I
really
saw
a
lot
of
cool
processes
both
around
the
onboarding,
for
example,
of
the
new
users,
building
the
champions
champions
team
of
the
users
who
began
alerting
others
and
be
the
power
users
in
the
organization.
C
As
I
showed
you,
the
financial
processes
as
well
the
travel
processes
so
around
again
the
hr
area
they
all
can
be
built
on
power
automate
with
the
usage
of
microsoft
with
the
usage
of
adaptive
cards,
as
this
mean
to
communicate,
to
interact
with
the
end
users
to
get
their
feedback
to
get
them
to
complete
the
tasks
and
therefore
usage
of
those,
let's
say
ordinary
power.
Automated
tasks
is
not
always
the
best
idea.
C
Let
me
just
check
one
last
time:
oh
here
we
go,
it
has
been
triggered.
So
where
is
that
just
a
short
short
reminder?
John
researcher
was
added
to
the
hr
team,
and
now,
if
you
would
like
to
be
allowed
to
that's
just
a
proof
concept,
if
you
would
like
to
be
allowed
to
this
confidential
information,
he
has
to
acknowledge
those
all
these
rules
and
express
and
express
his
compliance
all
right,
and
so
once
he
does,
it.
C
Once
he
does
it,
you
can
see
that
right
now
he
is
in
the
hr
team
and
there
is
confidential
and
so
yeah
graph
call
has
added
to
the
private
channel.
So
now,
general
researcher
is
also
led
into
this
private
confidential
channel,
where
some
information
on
the
nda
or
really
strictly
limited
to
a
group
of
hr
is
being
is
being
discussed.
A
A
So
go
and
shoot
me
an
email,
it's
in
the
chat
matt.heidinger
at
microsoft.com
and
we'll
talk
about
you,
know
the
tech,
the
tap
program
and
see,
if
you'd
be
a
candidate
for
that
or
just
you
know,
upcoming
focus
groups
just
go
ahead
and
shoot
me
an
email
and
we'll
we'll
work
with
you
to
see.
If
see,
if
we
can
put
anything
together,
no
promises
on
that
by
the
way
like
just
reach
out.
A
Let
me
know
we're
just
kind
of
trying
to
gauge
interest
to
see
what
are
what
are
better
ways
or
what
what
are
some
additional
ways
we
can
keep
engaging
with
our
community
outside
of
these
community
calls
a
bunch
of
resources,
one
external
one
I
always
like
to
draw
attention
to
is
made
with
cards
dot.
Io,
really
cool
user
contributed
samples.
A
We
had
a
build
2020
session
that
goes
into
a
lot
of
things
templating
we
released
a
couple
months
ago,
so
it
was
in
preview
for
a
long
time.
Tomas
showed
off
the
power
of
it.
We
are
looking
to
find
a
way
that
we
can
bring
the
power
of
templating
into
power
automate,
but
if
you
are
using
native.net
or
a
node.js
backend,
you
can
use
templating
today,
while
we
roll
it
out
to
the
mobile
sdks
and
and
different
apps
throughout
the
year.
There's
other
m365
developer
community
calls,
so
this
call
will
be
online.
A
A
There's
a
question
on
xamarin
and
xamarin
forms.
We
have
man,
it
comes
up.
We
we
totally
get
the
demand
for
it.
We
we
almost
had
it
done
last
quarter
and
hit
a
handful
of
complications
specifically
with
the
xamarin
forms
api
and
getting
the
projections
right.
We
had
the
rendering
done,
but
just
getting
it
done.
Oh
yeah,
thanks
thanks
ben
joining,
so
xamarin
forms
is
tricky.
It's
not
actively
in
development
right
now.
I
can
what
I'll
do
actually
after
this
is
get
you
a
list.
A
I
can
point
you
to
the
branch
where
development
was
taking
place,
but
at
this
point
it's
one
of
those
we
either
need
support
from
the
community
to
finish
it
or
it's
just.
It
ended
up
being
a
little
too
difficult
for
us
at
this
point
relative
to
other
things,
we're
trying
to
get
done
through
the
year
yeah
adaptive
card
studio.
So
tim,
you
wanna
quickly
mention
what's
going
on
with
adaptive
card
studio.
D
It's
constantly
maintained
it's
sort
of
released
since
last
month,
since
we
had
the
community
goal
last
month,
we
released
it
and
it's
basically
an
studio
code
extension
that
allows
you
to
author
adaptive
cards
pretty
similar
to
the
designer,
but
with
a
json
approach.
So
there's
no
no
fancy
drag
and
drop,
it's
just
purely
json
yeah,
but
you
can
edit
and
also
cards
directly
in
virtual
studio,
with
a
few
snippets
to
make
it
easier
and
it
automatically
finds
and
tracks
all
the
adaptive
cards
you
might
have
in
your
workspace.
A
And
tim
did
a
demo
of
this
on
last
month's
community
call
so
install
it
it's
now
out
at
last
month.
It
was
just
kind
of
in
code
form
so
yeah
I
could
install
it
check
it
out
and
if
you'd
like
a
quick
demo
of
it,
go
ahead
and
check
out
last
month's
call
and
tim
tim
walks
through
some
of
that
there
was
a
question
on
power.
C
A
C
I
I
can
answer
this
question.
Oh
please
do
right
so
so,
actually,
today
when
we
are
using
the
power,
visual
agents
and
we
bind
them
with
microsoft,
teams-
they're
just
postnozzula
messages
now
since
january
next
year,
because
in
january
it
is
meant
to
be
in
a
in
a
preview
version,
we'll
be
able
actually
to
post
regular
adaptive
cards.
C
Now
today
we
are
also
able
to
post
the
gift
cards
involved
agents,
but
to
do
that,
we
need
to
build
our
own
bot
skill
using
bots
framework
in
azure
and
then
use
these
bots
yeah
bought
skill,
measurable
skill
inside
the
pva
as
an
action
and
and
then
if
this
advice
card
is
coming
from
the
bot
framework,
then
this
can
be
displayed
today
in
pva
as
well.
But
this
native
pva
support
for
adaptive
cards
is
going
to
be
next
year.
C
A
A
Thank
you
so
much
everyone
I'm
going
to
go
ahead
and
wrap
it
up.
We're
we'll
we'll
see
you
next
month,
I've
seen
a
handful
of
emails
coming
in
so
it
looks
like
there
is
some
interest
in
a
focus
group
really
targeted
at
the
power
platform.
Folks,
so
I
think
that's
cool
I'd
love
to
learn
more
about
what
their
expectations
are,
how
adaptive
cards
can
best
tell
so
it
looks
like
we'll
probably
set
something
up
with
that
and
yeah
thanks
everyone
for
joining.