►
From YouTube: Microsoft 365 PnP – General Microsoft 365 Developer SIG community call – 14th of October, 2021
Description
Microsoft 365 PnP Community - General SIG call on October 14th. Demos: Introduction to the new PnP Transformation Framework, Teams Meeting App – Record and playback attendee names, and Feedback bot using the new Adaptive Card capabilities. An updated Viva Connections public developer preview is now out. Project releases this week include PnP Core SDK v1.4.0 GA, PnP PowerShell v1.8.0GA, and Yo teams - generator-teams - v3.3.1 GA. As well, there were 17 script samples, 2 Teams samples and 3 Power Platform Samples this week. The host of this call was David Warner II (Catapult Systems) | @DavidWarnerII.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly General M365 Dev SIG call: http://aka.ms/spdev-sig-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos
A
All
right,
we'd
like
to
warmly
welcome
everyone
to
this
microsoft,
365
development,
bi-weekly
community
call.
My
name
is
david
warner,
pnp
team,
member
from
catapult
systems.
We
are
having
an
epic
collection
of
presenters
today,
we're
going
to
begin
with
an
overview
of
the
latest
on
the
pnp
initiatives,
pnp
framework
and
core
sdk
powershell,
yo
teams,
microsoft,
graph,
microsoft,
team
samples
and
power
platform
samples
and
then
the
ever
popular
together
mode
picture
time
for
the
entire
community.
A
Then
the
rock
stars
of
the
day,
bert
jensen
and
paulo
plrc,
introduction
to
the
new
pnp
transformation
framework.
Then
we're
going
to
move
with
marcus
muller
on
teams,
meeting
apps
on
how
you
can
record
and
play
back
attendee
names
to
ensure
that
everything
is
accurate
and
then
ravio
williams
is
going
to
cover
a
feedback
bot
using
the
new
adaptive
card
capabilities.
A
Let's
begin
with
a
review
of
how
you
can
get
involved
and
start
beginning
to
participate
in
the
community,
if
you
would
like
to
demo
a
technical
or
solution
pattern,
that
is
an
opportunity
for
you.
This
is
a
community
initiative,
and
so
you
have
that
opportunity.
You
can
request
a
demo
spot
at
the
url
ak
dot,
ms4
365
pnp
forward,
slash
request
for
slash
demo
or
you
can
contribute
on
github.
We'll
talk
a
little
bit
more
about
this
in
a
moment.
That's
an
opportunity.
A
A
That
is
going
to
provide
you
opportunity
to
look
at
these
videos
developer
and
community
you're,
going
to
be
able
to
see
all
of
the
open
source
repositories
available
to
you
all
of
the
sample
galleries
that
cover
team
samples,
web
parts,
power
platform,
spfx
list
formatting
and
the
new
aces,
as
well
as
the
opportunity
to
utilize
and
contribute
back
so
again,
ak
dot.
Ms
four
slash,
m365
tnp
is
your
number
one
landing
spot,
take
a
look
and
get
involved.
B
Hey
everybody,
so
the
script
samples
is
a
site
for
sharing
scripts
with
everybody
in
the
community
for
automating
tasking
365..
So
this
is
examples
of
the
microsoft
graph
scripts
cli
for
365,
pmp,
powershell,
spa
management,
shell
and
etc.
I'd
like
to
thank
everybody,
who's
contributed
so
far,
it's
been
been
great
and
but
we've
had
a
bumper
pack
of
of
new
contributions
in
the
last
couple
of
weeks.
So
I'd
like
to
thank
all
the
contributors
for
that,
so
we've
had
over
11
new
samples
and
six
updates
to
existing
samples.
B
So
it's
been
a
massive
massive
effort
from
the
sorry.
I
can't
see
the
slide
actually
so
from
the
presenters
who
sort
of
the
contributors
on
the
slide
deck
showed
there
and
I'd
like
to.
Thank
you
personally.
That's
been
amazing
that
you've
produced
so
much
in
such
a
short
amount
of
time.
So
I'm
really
really
happy.
But
if
you
want
to
go
and
check
out
the
samples
go
to
aka
dot.
A
A
That's
going
to
give
you
walk-throughs,
together
with
other
members
of
the
community
and
pnp
on
how
to
take
advantage
of
contributing
back
or
using
those
resources.
We've
got
our
upcoming
first
time
contributor
for
power
platform
samples.
The
first
time
ever
at
the
end
of
this
month
and
the
ever
popular
ask
me
anything
sessions
coming
up,
pnp,
powershell
and
cli
with
pmphs
scheduled
soon
again
safe
space
opportunities
join.
We
will
collaborate
together
and
walk
you
through
hands
on
aka
dot.
Ms
forward
slash
sharing
is
caring,
of
course,
within
all
of
our
initiatives.
A
We
want
to
recognize
and
celebrate
you.
The
pnp
recognition
program
is
here
powered
by
credly
the
same
credly
that
powers,
the
badges
for
certification
exams.
Your
contributions
to
the
community
are
going
to
be
officially
recognized
by
us
with
more
badges
coming
up.
We
do
need
you
to
opt
in.
It
is
a
very
cool
program
and
we
cannot
wait.
A
It
is
no
cost
to
you
by
the
way
and
we
are
going
to
continue
to
crank
out
new
campaigns
and
new
initiatives
to
recognize
you
for
all
the
work
you're
doing
working
with
a
number
of
the
pnp
maintainers
things
like
cli
and
the
independent
publisher,
connectors
all
kinds
of
stuff
coming
out
soon.
So
please
opt
in
aka.ms
forward,
slash
m365,
pnp,
dash
recognition.
A
We
also
have
the
tuesday
platform
call
coming
up
on
the
19th
of
october
at
8
a.m.
These
are
very
exciting
because
they
are
the
latest
news
from
microsoft,
engineering,
so
you're
going
to
get
it
directly
from
the
mothership.
These
sessions
are
going
to
always
be
covering
latest
from
the
microsoft
engineering
and
presented
by
microsoft
employees.
So
we
have
coming
up
on
next
tuesday,
introduction
to
universal
print
and
the
latest
on
the
microsoft
graph
data
connect.
You
can
get
that
recurrent
invite
from
aka
dot.
Ms
forward
slash,
m365
dash
dev
dash
call.
C
Yes,
thank
you
david.
So
for
being.net
we
have
a
new
release,
so
we
have
been
picker
sdk
version
1.4
really
excited
about
this
new
release
because
it
brings
two
main
new
components.
There
is
a
transformation
framework
which
will
be
a
topic
of
the
first
demo
in
today's
call.
So
I'm
not
going
to
talk
too
much
about
that
and
there's
also
an
admin
library
so
bringing
admin
features
site,
touching
creation
enumeration.
All
these
things
will
be
part
of
pnpro
sdk.
C
Furthermore,
there
is
additional
things
like
support
for
collapsible,
page
sections
and
a
ton
of
performance
improvements,
so
all
checkout
1.4,
I
would
say
all
right.
So
what
else
happened
to
bp
framework,
the
usual
kind
of
flow
of
updates
and
small
improvements
that
we
keep
getting
from
community
and
we
keep
processing.
So
I
think
what
on
track
there?
It's
also
work
planned
for
the
the
new
schema,
though,
and
on
the
course
gay
site.
As
already
mentioned,
we
ship
those
new
components
and
our
main
focus
going
forward
is
now
to
finalize
those
components.
C
A
D
D
Yep
yep,
so
we
released
1.8
finally
took
a
while,
but
it's
finally
out
a
lot
of
changes
in
there.
It
actually
goes
beyond
this.
The
size
of
this
slide
actually
to
put
them
in
there.
So
if
you
want
to
check
out
what
has
changed,
please
refer
to
the
github
repo.
We
will
find
a
change
log
there
and
you
will
find
tons
of
changes
in
1.8
really
happy
that
this
one
is
out.
Finally,
so
what's
happening
there,
we're
still
working
on
the
the
v2
proof
contract.
D
D
One
a
bit
of
our
goals
is
that
we
want
to
simplify
things
we
want
to.
Instead
of
having
these
swiss
pocket
knife
commandlets
with
with
5
000
switches
and
options
and
properties
and
everything
you
can
set,
we
want
to
have
single
focus,
commandlet
a
command
that
does
a
thing,
and
that
is
it
and
we
want
to
get
rid
of
the
season.
D
Thinking
you'll
know
that
most
of
you
know
that
realized
that
powershell
bmp
powershell
is
effectively
a
layer
around
the
season
library
for
microsoft
and
that
still
exposes
itself
quite
heavily
in
the
objects
that
we
returned
from
the
command
list
and
we're
changing
that
we're
getting
writ
still
using
season
behind
the
scenes
where
needed.
But
what
we'll
expose
to
you
will
be
power.
Shell
objects
owned
by
powershell,
pmp,
powershell
and
created
by
pnp
powershell.
D
A
Awesome
exciting
stuff,
thank
you,
irwin,
as
we
move
into
yo
teams.
Let's
take
a
look
at
the
latest
there
we
have
released
3.3.1,
which
has
support
for
teams,
js
sdk
1.11,
a
number
of
items
in
the
roadmap.
The
team
is
building
and
growing,
and
so
there's
a
lot
of
opportunity,
as
noticed
here
at
the
top
of
the
slide.
It
is
hacktoberfest,
so
there
are
good
first
issues
and
help
wanted
opportunities
for
you
to
get
involved
too.
Definitely
take
advantage
of
that
and
reach
out.
E
E
E
I
know
there
hasn't
been
a
lot
of
detailed
updates
on
this
page,
but
you
can
definitely
go
check
out
our
projects
board
because
the
graph
toolkit
is
open
source
to
see
our
roadmap
and
we
update
the
project
for
every
month
to
show
like
the
work
that
we
need
to
do
there
we're
also
part
of
the
hacktoberfest
tagging
system.
So
you
can,
you
know,
go
check
out
our
help,
wanted
issues
and
first
good
issues
in
order
to
help
us,
we've
only
been
managing
to
fix
small
bugs
because
we're
a
small
team.
E
A
A
G
Hello,
yes,
well,
I'm
excited
to
announce
two
new
team
samples
this
week.
The
first
is
from
marcus
mohler,
who
will
be
presenting
last
time
sample
this
time
and
maybe
this
time
sample
next
time.
I
don't
know
anyway,
it
makes
it
easy
because
I
don't
have
to
completely
redo
the
slide,
because
he's
always
seems
to
have
a
sample
which
is
just
great.
Thank
you
so
much
marcus.
G
This
one
is
an
elaboration
on
the
meeting
life
cycle,
bot
that
he
brought
us
last
time
and
now
he's
actually
taking
feedback
at
the
end
of
a
meeting
and
showing
universal
actions
with
smiling
and
frowning
faces,
and
we
also
have
a
new
sample.
It's
our
very
first
blazer
sample.
So
big
heartfelt
thanks
go
out
to
tomy
golis.
This
looks
like
really
great.
It
actually
goes
and
monitors
the
top
participants
in
your
team
so
that
you
can
kind
of
see
who
the
collaboration
champions
are
if
you're
not
familiar
with
blazer.
G
As
I
understand
it
is
a
technology
that
allows
you
to
write
in
c
sharp
and
compile
down
to
run
in
a
browser.
So
if
you
wish,
you
were
writing
in
c-sharp
and
not
javascript
or
typescript,
it's
something
that
has
been
on
my
list
to
check
out
for
some
time
and
I
just
never
seem
to
find
the
time
so
here's
a
great
opportunity
to
actually
try
it
out
in
teams.
A
H
H
We
have
a
great
sample
by
mikhail
mendez
about
hiding
the
sharepoint
page
title.
This
actually
uses
the
sharepoint
rest
api
inside
of
power
automate
to
dynamically
switch
with
sharepoint
list
formatting
the
page
template
that
you're
using
in
your
modern
sharepoint
site,
and
then
I
have
my
names
on
there.
I
just
thought
I
recreated
the
collect
feedback
workflow
that
we
had
in
classic
sharepoint
there
with
power
automate.
So
those
are
the
three
new
samples
we
have.
We
welcome
all
of
your
additional
samples,
we're
also
participating
in
oktoberfest.
H
A
I
And
let
me
unmute
myself
and
let
me
share
the
screen.
Let's
do
this
in
a
way
how
we
do
it.
Always
if
you
put
the
video
on
we
have
50
seats
on
the
screen.
Ralph
had
a
good
note.
Actually
there,
and
sooner
or
later
we
will
have
more
spots
in
the
in
the
screen.
I'm
already
recording
this.
Let's
fill
up
the
50
and
then
we'll
do
some
hand
waving.
Typically,
that
gets
filled
pretty
fast,
because
we
have
more
than
200
attendees
again
on
the
call.
I
Oh
and
a
sharepoint
monkey
is
in
the
house
as
well
awesome.
I
actually
found
the
sharepoint
monkey,
but
my
wife
found
sherbet
monkey
during
last
week
and
so
from
the
closet,
which
is
pretty
weird
anyway.
I
think
that's
filled
up.
So
let's
do
something:
saving
everybody
thanks
everybody
for
joining
awesome
to
have
you
as
part
of
this
community.
Thank
you.
Thank
you.
Keep
the
feedback
coming
and
let's
stay
kind
and
friendly
awesome.
Excellent.
Let's
move
into
the
demos,
excellent
thanks!
Everybody.
A
C
Yeah,
so
a
bit
of
background,
we
folks
might
be
aware
that
we
already
have
a
page
transformation
technology.
It
has
been
there
for
like
about
two
years
now,
which
enabled
people
to
transform
classic
pages
into
modern.
We
have
been
rewriting
this
and
will
kind
of
explain
why
we
did
that
work
and
what
will
be
the
added
value
of
the
rewrite,
but
I
want
to
kind
of
first
set
the
scene
about.
Why
is
page
transformation
important?
Why
should
you
care
about
page
transformation?
C
One
thing
to
remember
is
that
sharepoint
pages,
I'm
talking
about
sharepoint
modeling
pages-
are
key
in
sharepoint
and
they
will
be
getting
more
and
more
important
in
sharepoint.
If
you
receive
connections-
and
you
can,
for
example,
react
to
a
page-
it
has
to
be
modern,
modern
pages
work
in
teams,
so
there
is
inside
sharepoint
and
the
products
around
sharepoint
is
really
important.
C
C
And
it's
not
just
about
publishing
pages.
It's
also
sports
blog
pages,
wiki
pages
web
pages,
any
page
you
throw
at
it.
It
will
result
in
a
modern
page.
Today
it
is
sharepoint
it
used
to
be
sharepoint.
Only
input
towards
modern
going
forward
will
open
up
to
do
other
types
of
pages
as
well,
and
I
think
paulo
will
kind
of
cover
that
in
the
next
slides
and
then
so
polo,
I
think
you
can
take
it
away
now.
Sure.
J
So
let
me
try
to
explain
you
the
idea
that
we
used
to
start
thinking
about
the
new
transformation
framework.
We
have
nowadays
dpmp
modernization
framework
and
in
this
one
we
can
read
the
sharepoint
classic
pages
from
on-premises
or
sharepoint
online.
We
modernize
them
and
we
write
them
in
sharepoint
online
modern
pages,
but
we
do
all
of
that
in
a
unique
engine
which
is
an
engine
just
targeting
sharepoint
from
sharepoint
to
sharepoint
modernizations.
J
Now,
with
the
transformation
framework,
we
decided
to
review
the
architecture
and
the
solution
and
to
introduce
the
idea
of
a
data
source
which
can
still
be
and
still
is
sharepoint
classic
out
of
the
box,
because
that's
the
one
we
support
out
of
the
box
but,
as
I
said,
could
be
something
else,
and
you
can
simply
implement
your
own
data
source
by
implementing
a
set
of
interfaces
and
base
after
classes
to
create
your
own
data
source
provider.
Then
there
is
another
model
from
an
architecture
point
of
view,
which
is
the
transformation
engine
in
the
transformation
engine.
J
We
do
the
actual
processing
of
an
object,
which
is
an
abstraction
in
memory
of
a
page
which
will
become
a
modern
page.
In
sharepoint
online
thanks
to
a
generation
engine
well
inside
the
transformation
engine,
we
can
rely
on
a
set
of
mapping
providers.
For
example,
there
is
a
mapping
provider
for
web
parts.
There
is
another
one
for
page
layout.
There
is
one
for
urls
one
for
users
and
so
on
so
forth.
J
So
the
idea
is
that
the
transformation
engine
is
a
pluggable
engine
where
we
can
plug
in
our
mappers
and
right
now,
again
we
provide
out
of
the
box
mappers
that
target
the
main
target
of
the
transformation,
which
is
a
sharepoint
classic
to
sharepoint
model.
But
ideally
you
can
create
your
own
mappers
or
you
can
customize
and
register
your
own
mappers.
If
you
want
to
simply
change
the
default
behavior
of
the
transformation
framework,
how
can
you
do
that?
J
Well,
we
you
can
do
that,
because
the
new
solution
and
the
new
framework
with
the
new
architecture
is
targeting.net.
Core.Net
standard
is
based
on
dependency
injection
and,
as
such,
you
can
inject
your
own
implementations
of
the
services
that
we
rely
on,
so
that
it
is
fully
completely
customizable
as
like,
as
you
saw,
with
pmp
core
sdk,
also
in
the
pmp
transformation
framework.
J
For
that
reason,
because
we
want
to
reuse
what
we
learned
to
do
while
building
the
pmp
core
sdk,
and
so
we
are
using
the
pmp
core
sdk
engine
and
pages
api
under
the
cover,
and
we
have
built
a
new
framework
on
top
of
it,
reusing
the
reading
part,
including
from
sharepoint
classic
and
still
using
season
in
there.
So
we
still
rely
on
season
when
we
read
the
classic
content.
J
C
But
imagine
the
scenario
where
you
have
like
your
company
uses
like
let's
say
some
kind
of
a
wiki
product
that
that
maybe
it's
good.
But
maybe
you
want
to
move
that
to
sharepoint.
Well
now
you
can
think
about
reading
the
content
from
your
wiki
product
and
populating
the
model
and
then
say
generate
page
and
then
you
get
a
modern
page
from
your
classic
from
your
old
other
type
of
content.
J
J
Another
sig
call
demo
where
we
will
explain
you
how
you
can
use
this
new
framework
in
a
architecture
based,
for
example,
on
a
cloud-based
solution
like
an
azure
function
or
stuff
like
that,
because
using
dependency
injection,
you
can
easily
do
that,
so
one
more
slide,
and
then
we
will
see
a
demo.
The
data
sources
right
now
are
sharepoint
2014
16
19.,
so
we
did
predicated
2010
just
for
your
information
and,
of
course,
online
sharepoint
online
classic.
J
We
support
transforming
pages,
wiki,
webpart,
publishing
and
blogs,
and
images
and
assets
related
to
the
pages
that
we
are
transforming.
We
have
mapping
logic
for
all
of
the
main
content
like
web
parts
and
layouts
when
we
think
about
sharepoint
as
data
source
and
just
to
be
completely
clear.
We
do
not
migrate
content,
so
we
do
not
take
care
of
files.
Documents
list
items
and
stuff
like
that,
because
this
is
not
a
tool
for
migrating.
This
is
a
tool
for
transforming
content
pages
from
one
to
source
to
sharepoint
online
modern.
J
J
Yeah,
this
is
a
a
classic
wiki
page
in
a
classic
team
site.
We
want
to
transform
this
page
as
well,
eventually
this
one
as
well,
which
is
yet
another
wiki
page
with
a
table
and
with
an
embedded
video
from
youtube
and
stuff
like
that,
we
want
to
transform
those
pages
into
modern
pages
in
a
modern
team
site,
and
here
in
the
set
pages
we
don't
have
any
of
those
pages
right
now,
so
we
can
easily
use
pmp
powershell.
We
simply
need
to
connect
first
of
all
to
the
target
environment.
J
So
remember
that
first,
you
have
to
connect
to
the
target
and
then
you
have
to
connect
to
the
source
at
least
right
now,
based
on
the
out
of
the
box
behavior
nowadays
of
pmp
powershell.
So
now
that
I'm
connected
with
the
target
connection
and
with
the
default
connection,
I
can
simply
and
easily
say,
invoke
pnp
transformation.
J
I
provide
the
page
that
I
want
to
transform
and
I
provide
the
target
connection
and,
as
you
will
see
in
few
seconds,
we
will
see
the
new
page
transformed
and
available
in
the
target
site
with
modern,
ui
and
modern
functionalities,
and
here
we
are
so.
If
I
go
back
to
my
browser,
we
can
refresh
this
page
to
speed
up
the
demo,
and
we
can
see
that
I
have
my
page.
J
I
preserve
the
information
about
who
created
the
page,
for
example,
and
if
I
click
on
this
page,
I
can
see
the
new
transform
page
with
the
modern
ui
in
sharepoint
online
motor.
The
same
can
be
done
with
any
other
page
that
you
have
and
you
can
also
define,
for
example,
using
parameter
splatting
in
powershell.
J
You
can
reuse
parameters,
so
you
can
do,
for
example,
the
transformation
of
multiple
pages
at
once,
still
in
powershell
sharing
the
same
set
of
options
and
as
you
can
see,
we
have
plenty
of
options
available
when
we
want
to
transform
a
page,
and
once
all
of
the
pages
will
be
correctly
transformed
into
modern
pages.
We
can
go
back
one
more
time
and
see
that
in
our
oops
this
is
the
modern
site.
J
We
have
the
migrated
pages
and,
for
example,
we
have
the
zero
20
2018
geo
italia
and
we
can
see
the
embedded
youtube,
video
and
the
table
and
all
the
stuff.
The
same
can
be
done
for
publishing
pages,
so
we
can
connect
to
a
publishing
site
like,
for
example,
this
one
in
which
I
have
an
article
page
with
the
page
layout
of
type
left
article.
Sorry,
article
left
with
the
left
image,
and
we
want
to
convert
it
into
a
publishing
page
here
in
a
communication
site.
J
So
again
we
can
connect
to
the
target
and
to
the
source
site,
and
once
we've
done
that
we
can
invoke
pnp
transformation.
This
time
it
will
be
a
publishing
page.
So
I
can
run
it
one
more
time
and
I
will
see
my
sample
article
transformed
into
a
modern
page
in
a
communication
site
and
again,
let
me
refresh-
and
we
can
see
the
transform
page
with
the
picture
with
the
image
on
the
left.
If
you
want
to
do
that,
and
I'm
going
to
close,
if
you
want
to
do
that
in
code,
you
can
use
dependency
injection.
J
J
This
is
just
for
the
sake
of
giving
you
an
idea,
but
you
can
provide
plenty
of
options
to
customize
the
behavior
of
the
transformation,
and
then
you
will
need
an
old-school
client
context
for
the
data
source
and
the
new
pnp
context
for
the
target,
and
you
can
simply
say,
transform
sharepoint
async
using
a
page
transformator
service
to
execute
the
transformation
so
quickly
back
to
the
slides
roadmap.
Now
we
are
in
public
preview.
J
A
Awesome,
thank
you
bert
and
paulo.
This
is
exciting
stuff.
You
could
have
called
it
the
transformation
easy
button,
that's
how
incredible
this
is
really
really
cool
stuff.
Thank
you.
So
much.
Let's
move
into
the
next
demo
by
marcus
mohler
teams,
meeting
app
record
and
playback
attendee
names
marcus.
Take
it
away.
K
Yes,
today,
I
want
to
talk
about
microsoft
teams,
meeting
apps
and
I
want
to
give
you
a
sample
on
the
pre-meeting
and
the
in-meeting
experience,
and
the
sample
is
an
idea
given
to
me
by
microsoft,
by
bob
german
and
by
aji
also
today,
in
the
call
and
thanks
for
your
support
by
the
way,
because
they
were
not
only
giving
the
idea
well
supporting
me
about
the
background
stuff,
because
this
is
relatively
new
short
about
me.
My
name
is
marco
smeller.
K
K
K
K
There
can
one
use
one
of
my
demo
users
and
send
this
out
once
we
have
this
meeting,
we
can
open
or
edit
it
again
and
then
we
can
add
the
teams
app
in
my
case,
I
already
installed
it,
but
I
could
also
sideload
it
here
from
there,
but
I
have
already
installed
it
and
running
it.
So,
in
my
case
this
is
a
tab
and,
as
you
might
know
how
to
install
it
regularly,
this
is
quite
the
same.
You
install
your
tab
with
the
configuration
in
my
case.
K
I
don't
need
it
and
what
we
have
here
now
already
and
what
you
see
here
already
now-
is
the
so-called
pre-meeting
experience,
meaning
we
have
a
tap
in
our
meeting,
which
is
not
running
yet,
but
this
is
in
my
case.
This
is
the
purpose
that
all
the
attendees
can
record
their
name
to
help
others
later
on
in
if
they
are
in
doubt
about
their
pronunciation
and
therefore
I
have
a
record
area
here,
and
this
works
simply
like
a
speech
message
in
whatsapp.
You
would
like
so
push
the
button.
K
K
What
happened
now
is
the
audio
get
recorded
and
will
be
stored
in
the
background
in
a
configured,
sharepoint
library
and
there
we
have
it
back.
We
also
have
some
user
information
like
a
photo
or
so,
and
what
I
additionally
did.
I
created
a
custom,
audio
control
and
was
not
using
the
the
standard
one,
and
I
will
later
show
you
why
and
once
marcus
demonstrating
live.
We
hear
what
we
recorded.
K
So
that's
it!
This
is
how
it
works
in
the
in
meeting
experience
and
as
you
know,
from
the
chat,
this
emitting
experience
is
only
valid
for
the
user,
who
picks
it.
So,
in
my
case
I
see
it
now.
The
others
might
not
see
it,
but
then
the
others
see
it
when
they
open
it
themselves.
So
it's
like
you
might
one
of
you
might
help,
have
opened
the
chat
here
and
the
running
call
the
others
might
have
not.
K
As
I
already
said,
there
are
some
prerequisites.
What
you
need.
You
need
a
meeting
with
at
least
one
participant
to
install
an
app
for
the
in
meeting
experience.
You
need
a
physical
team's,
desktop
client
and
not
a
web
client
or
also
a
retro
client
like
windows,
365,
and
so
this
is
currently
not
supported.
K
K
One
may
be
for
the
browser,
as
I
was
recording
the
pre-meeting
experience
from
a
browser
client,
but
also
the
team's
client,
now
requests
device
permissions,
and
this
will
be
handled
via
the
team's
manifest
first
and
then
by
via
user
acceptance.
I
can
show
you
the
team's
manifest
in
a
minute
and
the
user
acceptance.
You
can
also
see
some
screenshots
in
my
blog
and,
of
course
you
need
this
team's
tab
application
and
the
specific
teams
manifest
and
there
we
will
come
to
in
the
over
next
slide.
K
We
also
have
some
additional
options.
I
already
touched
this
somehow
so
I
called
this
pre
or
post
meeting
experience,
which
is
quite
the
same
area.
This
can
be
in
parallel
to
the
team's
chat
or
to
the
meeting
chat
as
well
as
the
meeting
itself.
This
is
currently
quite
the
same,
and
you
also
have
the
shown
in
meeting
experience
as
a
side
panel,
but
this
can
also
show
up
as
a
dialog
box,
which
is
more
centered
or
as
in
meeting
stage
and
in
the
opposite
to
the
side
panel.
K
K
On
the
one
hand,
we
have
a
scope
which
at
least
needs
to
be
group
check,
and
then
we
have
the
context
and
the
meeting
surface
which
work
somehow
in
parallel
right
now.
This
is
where
we
really
say:
hey.
This
app
shall
show
up
shall
be
available
in
the
meeting
details,
tab
on
the
chat
tab,
which
is
the
pre-meeting
experience,
but
it
should
be
also
available
in
the
meeting
side
panel,
for
instance,
and
last
not
least,
we
have
the
device
permissions,
and
here
we
are
asking
for
media,
which
is
not
only
audio.
K
It's
also
a
video
in
that
case,
but
we
only
need
the
audio
permissions.
The
next
thing,
which
is
quite
specific
in
terms
of
in
the
opposite
to
a
normal
team
step,
is
we
have
some
specific
parameters
for
the
meeting
which
I
also
used
in
this
sample.
On
the
one
hand,
I
used
the
meeting
id,
and
this
comes
from
the
context-
this
meeting
id
is
a
specific.
Do
it,
it's
not
the
same
like
the
id
when
you
have
it
in
your
event
or
invent
of
the
participants
and
also
not
an
online
meeting
id.
K
K
Am
I
in
the
frame
context,
content
which
is,
in
that
case
the
pre-meeting
one
or
this
could
be
also,
I
don't
know
by
heart
hours,
right,
side,
panel
or
meeting
side
panel
or
so
then
I
know
hey
now,
I'm
in
a
side
panel
running
and
then
I
can
show
up
different
things.
If
I
would
like
to
do
next,
some
things
about
the
recording.
K
What
you
see
on
the
left
hand
side
is
simply
the
ui
stuff.
So
here
I
have
a
button
with
a
microphone
on.
I
can
yeah
and
once
I
on
mouse
down,
I
record
some
data
and
on
mouse
up,
I
stopped
the
recording.
This
is
what
you've
seen
and
the
recording
takes
place
on
the
right
side,
and
what
I'm
using
here
still
is
the
navigator
sdk
so
from
the
browser
stuff.
K
So
the
first
thing
what
we
are
doing
here
is
we
try
to
get
the
user
media,
so
the
microphone
access,
and
once
we
have
it
here,
then
we
instantiate
a
media
recorder,
and
this
media
recorder
gets
the
mime
type.
We
try
to
get
the
the
first
track
for
it
and
then
on
start.
I
shorten
this
up
a
bit
that
you
it
fits
on.
One
slide,
then
I
can
make
it
visible
here.
K
Set
recording
is
nothing
else
than
something
putting
to
the
state
hey
the
recording
is
running
now,
because
then
I
need
to
display
a
different
microphone,
a
filled
out
microphone
instead
of
an
empty
one
and
so
on.
It's
not
that
important,
but
once
we
have
the
data,
we
push
it
to
our
current
chunk
and
once
the
recording
stops,
of
course,
once
again
putting
it
to
the
state,
and
then
we
try
to
get
the
track
and
we
try
to
push
back
the
audio
stream
to
an
from
an
upper
component
coming
to
a
callback
method.
K
That's
it
so
far
how
this
works.
You
might
have
also
seen
this
in
the
browser.
This
is
as
I'm
using.
The
the
navigator
thing
is
that
the
browser
of
course
pays
attention,
hey,
there's
a
recording
running
and
this
will
get
off
once
the
recording
is
stopped
and
yeah.
This
is
how
it
looks
like
in
the
how
it
looked
like
simply
that
we
had
this
two
microphone
icons
empty
and
filled
out.
K
K
Also,
no,
here's
mute,
sorry
that,
for
those
of
you
who
might
not
know
what
I'm
talking
about
in
terms
of
the
custom
audio
control,
that
the
standard
audio
control
looks
a
bit
like
this
and
my
custom,
one
you
have
seen,
looks
like
this
or
this,
and
this
is
also
the
reason,
because
this
custom
control,
I'm
using
the
fluent
ui
react.
North
star
components
can
easily
adjust
it
based
on
the
team's
seam
yeah,
and
this,
I
think,
looks
much
better
than
the
other
one.
K
A
A
F
Thank
you
so
much
david,
I'm
not
sure
if
I
can
top
that
demo
great
job,
marcus
and
everyone
else
who
did
the
demos,
I'm
so
excited
to
be
here,
because
it's
been
a
while,
since
I've
been
on
a
pnp
call,
so
I've
got
a
I've
got
15
minutes
for
this.
I've
got
this
sample
that
I
did,
I
think,
mid
of
this
year
after
build,
so
we
announced
universal
actions
for
adaptive
cards
which
had
a
lot
of
cool
features
in
it.
So
we
already
have
a
pnp
video
on
universal
action.
F
What
the
capabilities
are
what
we
can
achieve
with
these
new
features,
so
I'm
not
gonna
go
in
and
open
up
the
powerpoint,
because
I
know
you've.
Probably
there
is
a
video
there
and
I
will
also
link
that
in
a
deck
that
I've
shared
with
david,
so
we
have
like
around
four
features
we
discussed
during
the
time
for
build.
We
for
this
adaptive
cards
like
from
one
point
four
upwards.
F
You
have
features
like
contextual
views,
so
you
can
have
adaptive
cards
that
would
show
up
different
views
for
different
people
with
this
was
a
game
changer.
When
I
announced
it,
it
was
one
of
the
coolest
thing
that
I
could
think
of,
because
you
know
previously
adaptive
cards
would
just
show
up.
You
know
the
same
view
for
every
single
person
that
would
be.
You
know
you
could
change
the
messaging.
You
can
update
it
stuff,
but
everything
is
just
like
in
that
same
conversation,
you
would
see
the
changes
happening.
F
If
one
person
went
ahead
in
that
conversation
and
updated
or
did
some
action
on
the
adaptive
card,
it
wouldn't
change
it
for
other
users
who
haven't
started
the
workflow
yet,
and
that
was
another
big
improvement
in
that
area
as
well,
and
then
the
other
one
was
introducing
the
refresh
capability
for
the
adaptive
cards.
So
you
could
go
ahead
and
update
the
card
and
you
know
you
could
see
the
status
updated
and
stuff
like
that.
F
So
these
are
the
three
things
I'm
going
to
be
demonstrating
in
the
sample
that
is
currently
in
the
pnp
gallery
as
well.
For
teams
it's
called
a
feedback
bot,
I'm
not
sure
if
it's
actually
a
feedback,
because
I
created
it
as
for
a
demonstration
purpose,
because
there
were
some,
I
think,
right
after
build,
we
had
some
samples
from
the
community
as
well.
I
remember
nandeep
had
a
sample
on
incident
management
and
there
was
one
from
waterdemon
on
another
approval
process
and
they
were
in
c-sharp.
F
So
I
took
that
opportunity
to
create
something
in
the
node.js
javascript
typescript
space
as
well
for
folks
who
are
into
that
framework,
so
have
this
bot,
so
I'm
just
gonna
share
my
screen
and
jump
right
into
the
demo,
so
I
already
have
the
project
up
and
running
and
I'll
go
to
the
source
code.
Once
I've
got
this
working
and
once
I've
showed
you
the
demo,
but
I
have
like
two
users:
three
users
actually
logged
in
and
side
by
side.
What
I'm
gonna
do
is
I'm
gonna
invoke
this
this
feedback
part.
F
So
what
I'm
doing
here
is
I'm
gonna.
Ask
some
questions
to
my
colleagues
or
my
you
know
teammates
here
in
a
channel
called
pmpdemo
and
then
I
want
to
see
their
responses.
So
most
of
the
time
what
happens
is
we
ask
a
question?
It
might
be
something
really
important
like
you
know.
What
are
you
watching
these
days?
F
What
series
are
you
watching
and
stuff
like
that,
and
then
you
know
that
there
might
be
people
who
replied
to
it,
but
then
you
lose
the
conversation
because
there's
something
else
coming
in
between
and
then
you
don't
know
what
the
others
said
about
this.
It's
some
somewhat.
Like
a
conversation,
you
know
just
keeping
everything
in
one
place,
so
I'm
just
gonna
go
ahead
and
invoke
my
bot,
so
it's
called
cardbots.
F
F
Only
I
can
spell
things
okay,
so
I'm
gonna
ask
this
question
as
a
person,
so
this
is
my
initiator
who
is
initiating
this
bot
and
it
will
throw
me
a
base
card,
so
this
is
what's
happening
under
the
hood
as
well.
It
will
throw
a
card
to
everyone.
I
hope
it's
working,
yep
cool,
so
you
can
see
for
a
tiny
moment
there.
You
can
see
that
everybody
in
that
in
that
whole
team
in
that
whole
channel,
can
see
the
base
card
being
sent
out,
but
immediately
for
the
initiator.
F
It
changes
it
updates.
This
is
the
contextual
view
that
I
was
talking
to
you
about,
like
based
on
what
your
role
is
in
that
particular
workflow.
You
will
see
the
cards
so
in
my
case
here
he
do
admin.
He
or
she
is
the
initiator
so
immediately
the
base
card
updated
and
it
showed
me
like
a
summary
of
you
know
if
my
teammates
responded
or
not
in
the
meantime,
I'm
logged
in
as
a
deal
here
who
gets
a
card
where
she
could
respond.
F
So
I'm
just
going
to
go
ahead
and
respond
to
that
and
she
she
wasn't
a
big
fan.
She
said
it's
overrated
cool,
so
she
has
sent
her
response
now.
On
this
particular
question,
you
can
see
that
the
message
updates
itself
at
the
same
time
it
refreshes
for
every
person
involved
here.
So
you
can
see
here
the
the
information
is
already
captured
and
she
got
a
card
that
says.
F
Thank
you
for
your
response,
so
you
don't
need
to
do
any
more
response
on
that
and
you
have
the
admin
I
mean
she
or
he
can
see
that
a
deal
responded
to
it
with
a
reply.
It's
it's
a
super
simple
demo,
like
I
said
it,
it
wants.
I
wanted
to
demonstrate
the
capabilities
of
adaptive
card,
but
you
can
think
of
other
scenarios
where
this
could
be
used
as
well.
So
we
have
seen
now
contextual
views
feature
and
we
also
see
the
refresh
capability
of
adaptive
cards.
F
F
But
if
I'm
logged
in
as
another
person
who
did
not
respond
in
our
case,
it
is
now
alex.
I'm
logged
in
as
alex
alex
can
see
this
card
again
because
he
hasn't
started
his
process.
Yet
so
he
can
see
the
question
and
he
can
reply
then
and
there.
So
this
is
the
feature
that
they're
talking
about
the
sequential
workflow,
so
alex
can
go
ahead
and
reply
saying
it.
F
It
is
great:
okay,
there's
someone
who
actually
likes
it
and
respond
back
immediately.
What
happens?
Is
it
updates
the
card
for
every
single
person
in
that
channel
and
shows
you
know
the
summary
for
the
admin
or
the
initiator?
Whoever
initiated
this
bot-
and
you
know
nothing-
changes
for
a
deal
because
she
she
responded,
so
that's
fine
and
for
alex
it
should
be
again
similar
to
a
deal.
F
So
this
is
basically
the
demo
demo
part
of
it
how
it
all
works
together
and
how
you
can
all
get
all
these
features
now
with
just
few
changes,
because
they,
the
game
changer,
was
that
they
introduced
some
refreshed
properties
and
also
the
response
sending
the
adaptive
card
response
back
into
the
bot.
So
that
was
the
game
changer
for
all
this
to
work
together.
Apart
from
this,
they
also
had
the
feature
of
it.
You
know
being
universal.
F
That
was
the
whole
concept
right,
so
you
have
universal
actions,
means
it
works
in
teams
and
it
works
in
outlook
as
well,
because
the
back
end
is
now
the
same
bot
registered.
So
you
just
have
to
open
up
the
channel
to
outlook.
I
unfortunately
cannot
demonstrate
that
in
in
this
sample,
because
it's
the
code's
not
there,
but
so
I
will
jump
and
jump
into
the
code
aspect.
F
B
F
Jump
into
the
vs
code,
so
this
is
basically
my
project
and
it
is
probably
I
started
off
at
a
very
good
base
project
and
thanks
to
bob
german
who
was
my
colleague
and
friend,
who
suggested
the
yeoman
generator
for
bot
builder.
It
was
a
game
changer
for
me,
because
I
was
looking
for
something
really
simple
to
start
with,
and
I
wanted
a
structure
or
a
project
that
does
not
have
a
lot
of
things
going
on,
because
obviously
I
wanted
to
learn
these
concepts
first,
so
I
used
the
generator
for
that
and
it
was
perfect.
F
I
used
an
ecobot
template
for
it
and
it
just
created
this
bot,
dot,
ts
and
my
entry
file,
and
that
was
it.
That
was
the
only
thing
I
need
to
worry
about.
So
here
are
a
few
things
that
I've
done
extra
is
I
have
a
memory,
so
I
have
some
conversation
data
that
I
needed
to
store
in
order
to
make
sure
that
I
know
who
the
who
the
initiator
is.
You
know
the
user
id
of
that
person.
F
I
wanted
to
know
who
responded
so
that
I
can
show
them
a
different
view
or
a
different
card.
So,
for
that
reason
I
needed
some
sort
of
a
memory
so
use
this
memory.
Storage
here,
which
is
what
you
see
in
this
file.
Other
changes
is
basically
the
main
changes
are
all
happening
in
the
bot,
so
I
have
the
activity
handler
here
and
for
what
it's
worth.
F
I
have
included
comments
in
most
of
the
lines,
because
again
this
is
a
demonstrating
samples,
so
I
I
find
it
really
helpful
when
people
will
see
some
comments,
so
go
ahead
and
check
this
out
in
our
pnp
gallery,
and
you
can
probably
understand
what
I'm
trying
to
do
here.
But
you
know
it's
it's
just
basic
stuff
and,
like
I
said
getting
the
user
information
and
things
like
that,
and
what
I'm
really
interested
to
show
you
today
is
this
invoke
activity
function.
F
That
is
what
I
override,
and
then
I
put
my
logic
in
for
all
that
refresh
activity,
that's
happening,
and
here
what's
happening,
is
based
on
the
action
on
the
card
like.
If
I'm
going
ahead
and
submitting
the
card,
then
I'm
checking
I'm
storing
this
information
of
this
user
into
the
payload
into
the
memory
and
then
using
it
in
the
payload
to
refresh
that
card,
so
that
you
know.
First,
I
send
out
the
base
card
and
then
I
would
check
if
that's
an
initiator
boom.
F
I
show
the
initiators
card,
which
is
like
a
summary
card
and
if
someone
else
goes
ahead
and
put
the
form
information
in
and
click
the
boom
button,
and
then
I
will
go
ahead.
So
that's
a
switch
case
here.
Okay
and
then
I
go
ahead
and
add
that
person
into
the
list
of
user
id
and
based
on
who
they
are
they're,
not
the
initiator,
okay,
show
them
the
other
card.
That
says
thank
you,
and
this
is
how
it
works.
F
So
this
is
that
extra
piece
of
stuff
they
added
so
this
user
id
is
where
you
can
add
these
users,
who
are
active
participants
of
this
workflow
like
if,
in
in
a
in
a
business
scenario,
it
would
be
a
person
who's,
approving
a
person
who
you
know
created
an
incident
form
or
something
like
that
that
those
user
ids
can
go
into
the
payload
and
they
could
kick
off
a
refresh
of
that
adaptive
card
and
show
something
new.
So
I
think
we
have
just
one
moment
for
this
meeting
so
yeah.
F
I
really
wanted
to
just
show
you
that
and
finally,
I
will
share
this
links.
Basically,
I
think
I
have
shared
this
deck
with
david
as
well,
so
I've
got
the
blog.
I've
got
the
source
code
in
pnp
gallery.
I've
got.
If
you
want
to
read
more
about
universal
actions,
you
can
go
to
aka
dot.
Ms
slash
pnp
hyphen.
I
also
linked
in
the
generator
that
I
used
to
build
this
one
out.
So
yeah,
that's
basically
the
demo.
A
Fantastic
ravi.
This
is
really
awesome,
stuff
very
exciting.
Thank
you
for
sharing
it.
Today.
Links
are
in
the
chat.
They
will
also
be
in
the
blog
if
you're
watching
the
video,
let's
go
to
back
to
the
slides,
to
wrap
up
again
like
to
thank
all
of
our
presenters,
bert,
paolo,
marcus
and
rabia
awesome
stuff.
Today,
this
community
is
the
best
by
far
thank
you
all
again
for
taking
the
time
to
share
with
the
rest
of
the
community.
A
The
recording
will
be
available
in
24
hours
or
less
in
the
microsoft
365
pnp
youtube
channel,
aka.mssportslash,
m365,
pnp,
slash
videos.
You
can
follow
us
on
twitter,
at
microsoft,
365
dev
or
at
microsoft.
M365
pnp,
the
next
general
development
call
will
be
two
weeks
from
today
october
28th
at
7
a.m.
Pacific
time,
sharepoint
framework
call
will
be
next
thursday
october
21st
at
7.
Am
you
can
get
the
invites
from
all
of
our
calls?
Aka
dot,
ms
forward
m365pnp?
A
Of
course
there
is
the
weekly
platform
call
as
we
mentioned,
on
tuesdays
aka
dot.
Ms
forward
slash,
m365
dev
dash
call
get
the
invite,
do
not
miss
that
one.
It
is
awesome.
We
have
a
number
of
other
developer
community
calls,
adaptive
cards,
identity,
platform,
office,
evidence,
power,
apps,
microsoft,
665,
community
and
sharepoint
framework.
You
can
get
them
all
at
aka,
dot
m
s
forward,
slash,
m365,
pnp!
Thank
you
again.
Everyone
enjoy
the
weekend.