►
Description
Recording of the SIG from August 9th. Latest SharePoint Development news from engineering. SharePoint Developer news and cool community demos.
Modern page approvals with Microsoft Flow. SharePoint 2019 development platform and how to get started with it.
Detailed agenda and covered topics are available via the Microsoft Tech Community (http://aka.ms/spdev-community).
Download recurrent invite from http://aka.ms/spdev-sig-call.
A
Welcome
everybody,
this
achievement
patterns
and
practices
genoace
upon
development
special
interest
group.
So
this
is
the
community
core
where
we
talk
about
all
the
non
SharePoint
framework
and
non
JavaScript
development
stuff.
Well,
we
partly
actually
go
to
that
topic
today,
as
well,
so
more
on
the
solution,
design
architectures
see
some
new
get
packages,
and
all
of
that
today
we'll
talk
about
actually
SharePoint
framework,
because
shipment
framework
is
big
part
of
the
ship
on
2019
release
and
that's
part
of
the
agenda
as
well,
but
before
we
go
there,
let's
quickly
do
a
few
interests
or
slides.
A
If
there
are
new
people
joining
the
call-
and
you
haven't
been
actually
on
these
calls
before
so
we
started
originally
SharePoint
a
dozen
practices,
monthly
community
calls
or
SharePoint
developer
monthly
community
calls
absolutely
already
back
in
2014
and
then
gradually
it's
been
growing
and
growing
and
quite
fast.
At
some
point
we
realized
that
well
we're
running
out
of
time.
There
was
cool
demos.
There
was
a
lot
of
stuff
to
cover,
so
we
actually
introduced
first
an
office
hours,
and
then
we
introduced
two
different
special
interest
group
calls.
A
One
is
the
SharePoint
framework
special
interest
group,
where
we
talk
about
more
the
shipment
framework,
specific
topics
and
hopefully,
there's
always
a
active
discussion
in
the
window,
and
and
we
can
talk
about
those
questions
which
you
can
have
and
the
second
one
is
the
general
dev
special
interest
group.
This
was
originally
I.
Think
BMP,
you
see
some
core
sick
or
PNP
office
hours
this
one,
but
then
we
re
kind
of
a
formula
that
to
be
part
of
the
general
ratio,
point
AF,
so
anything
on
Prem
flow,
provisioning,
automation.
A
All
of
that
falls
on
this
anything
on
a
SharePoint
trained
work
force
on
the
other
one,
and
then
we
also
have
the
monthly
community
calls
so
the
next
one.
For
that
one
is
coming
actually
on
next
Tuesday,
where
we
talk
about
engineering
use
of
oil
status.
We
talked
about
more
what
has
happened
within
the
past
month
and
I'm
kind
of
an
intern
picture,
what's
happening
in
the
SharePoint
engineering
and
community
side.
By
the
way,
next
Tuesday
will
actually
have
two
cool
demos.
I
will
announce
the
agenda
later
today.
A
There's
the
shown
squares
is
gonna,
join
us
again
to
do
the
latest
on
site,
designs
and
side
scripts
in
next
Tuesday
and
then
I'm
gonna
do
a
live
demo
on
SharePoint
framework
1.6.
We
scheduled
to
go
live
later
this
month,
but
I'm
gonna
actually
demonstrate
some
of
the
capabilities
in
1.6
know
already
on
next
Tuesday.
A
So,
but
that's
on
next
Tuesday
today,
I
think
we
still
have
ship
1
has
such
a
humongous
amount
of
stuff
happening
also
on
the
left
side
and
that's
work
actually
why
we
have
quite
a
few
calls,
so
you
can
always
have
a
pinpoint
and
see
our
recordings
in
YouTube.
You
can
jump
to
the
specific
theme
of
what
you're
looking
before
we
actually
go
to
that
end
of
today.
There
are
opportunities
to
participate
in
a
community,
obviously
being
part
of
this
course
having
a
discussion
in
I
window.
That's
absolutely
one
way
of
participating.
A
We
understand
that
people
are
busy;
actually
they
have
their
own
life
and
you
can
always
just
participate
on
every
single
call,
but
you
can
demo
a
solution
or
technical
patterns.
So
if
you
wanna
have
more
visibility
for
your
role,
if
you
wanna
CRO
to
be
an
MVP
or
if
you
are
an
MVP
as
an
example,
and
you
want
to
gain
visibility
points
and
these
scores
are
actually
create
opportunity
for
you,
let's
face
it
back,
I
think
I
hear
Vince.
Is
my
man
I'm,
be
here
I'm
here
this
unbelievable?
It
is
what
it
is.
Ok,.
A
That's
good,
that's
good
now
so
on
today's
agenda,
so
there's
only
few
slides
of
general
announcement,
we're
not
gonna,
have
a
discussion
or
a
road
map,
or
anything
like
that
today.
So
we'll
talk
about
that
one
on
next
Tuesday's.
There
are
some
adjustments
on
the
1.6
released
as
an
example,
not
not
major
delays
or
anything
like
that,
but
some
adjustments.
But
we
want
to
make
sure
that
we
have
plenty
of
time
for
demos
because
we
promised
to
go
through
the
modern
baits
approvals
flow
with
checks,
checks.
A
A
What's
not
supported
we're
going
to
talk
about
shippment
framework
development
in
Chevron
2019,
let's
crossing
fingers
that
the
the
describe
issue,
which
we
had
already
here
still
only
one
today
but
and
then
Q&A,
hopefully
in
the
end
and
all
the
time,
you
can
actually
ask
questions
we'll
try
to
figure
out.
Follow
up
on
the
ion
window,
few
reminders
obviously
documentation
a
game.
Ssp
dev
Docs
is
to
SharePoint
documentation.
Checks
has
been
working
on
moving
some
of
the
flow
and
power-ups
documentation
here
as
well.
We
will
shrink
with
checks
on
latest
on
that
one.
A
Sounds
good
sounds
good,
so
the
whole
point
being
on
the
fact
that
anything
wants
is
related
on
SharePoint
development
or
makers,
meaning
the
configuration
like
photo
and
power-ups
will
be
found
from
a
one
single
location,
we're
hitting
like
one
nine
hundred
thousand
views
in
a
month
already
in
here.
So
that's
good
achievement.
A
The
second
thing:
what
I
wanted
to
still
promote
and
now
I
do
apologize,
we're
falling
behind
on
this
one,
because
I
was
on
vacation,
apparently
not
that
many
of
my
colleagues
were
actually
following
up
on
what's
happening
here,
and
so
the
issue
list
is
super
important
way
for
us
to
get
reports
from
you.
If
you
run
into
any
API
issues,
if
you
run
into
issues
in
SharePoint
Online,
this
is
mainly
because
our
general,
our
support,
does
not
actually
support
development
topic.
A
So
if
you
call
the
SharePoint
support
online
support,
saying
hey
this
API
doesn't
seem
to
work.
They're
not
gonna,
actually
help
you,
because
it's
a
customization
thing
or
development
thing,
and
that's
why
we
have
open
up
this
issue
list
and
we're
trying
to
keep
up
with
incoming
input
in
here
we
are
struggling.
So
we
do
apologize
on
on
the
delays
of
getting
up
to
date
on
everything,
but
we'll
get
will
actually
have
a
again
a
triage
later
today,
on
the
submitted
things
now.
A
You're
missing
a
ribbon
in
your
365
tenant
whoa.
That's
interesting!
No
idea
what
it
is,
but
missing
a
ribbon
in
a
tenant
is
not
a
dev
topic.
So
that's
because
that's
not
a
dev
topic,
please
open
up
as
a
support
issue
using
the
admin
portal
in
your
talent
and
explain
them
what's
the
issue
and
they
will
help
you
now.
A
Okay,
chef
start
again
just
a
reminder
on
this:
one:
okay,
miss
asbestos,
dev
starter
kit
that
there
has
been
some
advantages
or
additional
improvements
on
the
docks
during
the
summer
time.
We're
now
currently
working
on
end-to-end
automation
of
this
one.
So
pretty
soon
you
can
go
well,
at
least,
and
by
the
Ignite
timeframe.
Intention
is
that
you
can
go
to
our
website.
You
can
sign
in
as
a
tenant
administrator
and
you
can
select
what
kind
of
content
acts
you
actually
want.
A
A
provision
to
your
tenant,
one
of
them
being
the
the
portal
which
are
saying
here
there
will
be
other
ones
as
well
and
all
of
the
content
packs
will
be
open
sourced.
So
people
are
able
to
contribute
on
this
as
well.
The
main
intention
on
that
that's
self
service
portal
or
application
is
that
you
can
actually
use
that
as,
for
example,
as
a
pre
sells
a
tool.
A
If
our
consultant,
you
have
a
customer
pre-sales
engagement
tomorrow,
you
can
actually
easily
use
that
tool
to
provision
a
site
with
the
colors
and
theme
files
and
everything
else
matching
the
customer.
So
you
can
easily
actually
have
an
example
demo
available
now
this
good
question
from
a
lead
rope
around
will
this
one
of
these
will
be
available
in
a
SharePoint
2019
we're
looking
into
that
option
for
SharePoint,
starter
kit
and
the
communication
side
to
prop.
A
There
are
certain
challenges
of
introducing
the
starter
kit
as
such
in
on-premises
or
Chevonne
2019,
because
it
actually
contains
capabilities
and
Microsoft
craft
dependencies,
and
all
of
that,
so
we
will
have
to
refactor
the
starter
kit
at
some
point,
to
have
a
separate
solutions
for
SharePoint,
Online
and
shipment
on
Prem
to
make
that
happen,
and
that
will
still
make
sense.
Take
some
time.
A
B
You
so
first
things,
first
you're
doing
this
regularly
in
the
development
by
weekly
calls
talking
about
flow
and
power
apps
and
all
the
awesome
solutions
that
you
all
do
with
the
platform.
So,
if
you
are
interested
to,
you
know
talk
about
the
solutions
that
we
are
building,
make
sure
you
reach
out
to
me
or-
and
we
can
have
you
demo
in
these
calls
today,
I'm
gonna
be
looking
the
page
approvals
which
we
just
released
to
targeted
release.
Tenants
I
think
that
just
completed
a
hundred
percent
this
week.
B
B
So
now
we
know
that
that's
one
of
the
biggest
features
that
customer
requests
that
we
got
when
we
introduced
communication
sites,
especially
because
communication
sites
are
mostly
used
for
you
know
letting
organizations
and
others
know
about
all
the
things
that
are
happening
in
the
in
the
company
and
sometimes
you
need
to
kind
of
have
some
approvals.
So
you
have
someone
with
verifying
and
reviewing
the
content
that
was
being
published,
so
the
modern
pages
library
exactly
facilitates
that
modern
of
rules.
Sorry,
but
with
the
help
of
a
very
powerful
platform
called
Microsoft
flow.
B
So
in
the
pages
library,
if
you
go
to
the
flow
menu,
you
will
see
configure
page
approval
and
that
basically
is
going
to
set
you
up
with
a
flow
and
other
things
that
are
required
for
this
library
to
function.
So,
if
I
hit
create
flow,
now
I'm
going
to
get
the
create
flow
action
here.
The
panel
where
I
would
be
able
to
create
the
page
approval
flow
in
SharePoint
without
needing
to
go
to
the
full
site.
So
here
I
get
a
throw
name.
B
I
can
add
my
approvers,
so
I'm
gonna,
add
myself,
and
here
you
know
one
of
the
things
to
basically
look
for
is.
This
is
not
filtering.
Who
are
the
owners
or
poor
the
site,
visitors
or
members?
Right
now
you
know
the
site
owner.
Who
is
configuring
this?
Who
has
to
give
the
approvers
and
make
sure
that
they
have
access
to
the
page
when
they
do
come
to
review
and
approve
the
page?
So
let's
go
through
the
flow
and
then
probably
we
can
go
through
more
some
of
the
details.
B
So
now,
if
I
click
create
that's
going
to
create
the
approval
flow
change,
all
the
settings
in
my
library
and
in
a
moment
you
will
see
that
it
will
create
the
flow,
give
your
message
and
you
will
see
some
extra
columns
coming
up
in
the
library
which
is
the
approval
status.
So
this
will
now
got
whether
a
page
is
in
draft
pending
or
approved
State.
So
now
what
happens
is
on
this
left
side
of
the
edge
Microsoft
edge
browser
I?
Have
another
user
signed
into
the
site,
and
I
am
just
going
to
create
a
page.
B
B
And
now
I
can
submit
this
page.
So
now
what
happens
is
a
page
submitted
for
approval
and
in
a
second
you
should
see
this
page
now
status
into
the
view
approvals
there
you
go
so
it's
pending
approval
now.
So
this
what
happens
so
far
is
the
admin
on
the
site
enabled
approvals
for
pages.
We
created
a
flow
and
in
the
flow
I
also
said
myself
as
an
approver,
so
that
all
the
pages
that
do
come
from
approval
get
routed
to
me
and
then
a
user
who
went
to
the
site
added
a
page.
B
He
basically
submitted
the
page
for
approval
instead
of
directly
publishing
the
page,
and
now
he
basically
has
spending
approval.
Now,
if
I
go
to
my
email,
I
have
an
email
from
Flo
saying
that
there
is
an
approval
waiting
for
me
requested
by
John
Doe,
who
is
this
user
on
the
left
and
then
missus
sent
with
the
request.
Missus.
Also,
please
approve
this
page
well,
I
could
approve
here
directly
and
say.
Yes,
everything
looks
good,
but
I
can
also
click
to
review
the
page,
and
this
is
suffering
what
we
call
actionable
message.
B
Actionable
messages
are
supported
in
the
latest
outlook
clients.
So
if
we
have
office
365
outlook
and
using
the
latest
outlook
client
as
well,
whether
it's
Web
Access
or
your
Windows
outlook
client,
you
get
actionable
messages.
If
you
are
using
Mac
outlook,
client
or
you
know,
Windows
output
or
any
other
client
that
doesn't
just
not
Outlook,
you
don't
get
the
actionable
message
support.
So
at
those
times
you
know
you
will
see
this
message
at
the
bottom.
B
Now,
if
I,
when
you
click
review
approvals,
it'll
know
that
I
have
an
approval
waiting
for
me
for
this
particular
page
and
I
mean
get
the
approval
panel
here
from
flow,
so
it
has
all
the
details
and
then
I
can
basically
do
at
once.
They
can
even
crius
ein
through
the
and
person.
If
I
am
you
know,
invocation
or
have
some
other
work
and
then
I
can
now
click
approve.
B
I
can
basically
add
some
comments
and
then
confirm
so
now
that
basically
approves
the
page
and
soon
you
should
get,
and
so
soon
John
should
get
an
email,
basically
saying
that
the
page
is
approved.
Now
there
are
some
quotes
here.
You
see
that
this
is
not
changing,
but
if
I
actually
refresh
the
page,
it
will
change.
This
is
some
other
regression
that
we
just
thought
after
releasing.
So
we
just
knew
that
there
was
some
bug
that
was
stopping
that
auto
refresh
here.
B
So
let's
wait
and
see
if
we
if
John
gets
an
email
all
the
air
goes
to
here
this.
So
now,
John
gets
an
email
saying
your
SharePoint
page
was
approved,
and
you
can
basically
see
that
you
know
how
approved
by
check
relieved
with
the
following,
come
and
look
good
and
then
new
page.
You
can
basically
click
the
page
view
the
page
for
John.
So
this
is
what
the
end
to
end
flow
is
for
page
approvals
and
what
happens
behind
the
scenes
is
when
the
admin
created
the
flow.
B
If
you
actually
go
to
from
the
library
for
folks
that
know
what
you
know,
how
to
quickly
go
to
see
your
flows,
if
you
click
flow,
see
your
flows,
you
will
go
to
the
flow
side,
and
here
you
will
see
your
flow.
The
submit
SharePoint
pay
for
approval.
Now
this
name
depends
on
the
name
that
you
gave
when
creating
the
flow.
So
now,
if
you
edit
or
if
you
just
click
that
flow
you
can
see,
the
run
is
free.
It
was
succeeded
three
minutes
ago
right.
B
If
you
click
Edit
flow,
you
can
actually
see
what
we're
doing,
and
you
have
full
control
over
this
flow
now
to
add
or
modify,
or
do
anything
that
you
want
based
off
of
your
organization
policies
right.
This
is
the
basic
template
that
we
believe
works,
and
then
you
can
now
continue
doing
the
things
that
you
wanna
do
with
this
template.
For
example,
you
know
start
an
approval
right
now:
users,
anyone
from
a
sign-in
list.
You
can
change
that
to
everyone
from
the
assigned
list.
B
If
you
have
three
or
four
approvers
that
needs
to
go
through
and
finish
all
review
for
everybody
one
by
one.
You
can
so
the
basic
flow.
If
you
go
through
this,
the
design
of
this
flow
is
basically
it
once
for
the
pages
library,
and
then
it
has
a
message.
That's
what
you
saw
the
people
entering
a
message
you
can
remove
that.
Then
you
want
to
get
the
ability
for
people
to
summon
a
message.
B
Then
we
get
the
file
properties,
which
basically
gives
me
some
data
about
what
the
page
is
and
then
I
get
the
metadata
to
get
all
of
the
other
required
metadata.
I
have
on
that.
I
set
the
content
approval
status
for
the
library
to
be
pending
so
that
way
now
SharePoint
knows
that
the
page
is
now
from
move
from
draft
to
pending
and
of
course
the
e-tag
is
a
very
important
thing.
A
diagram
first
choose
the
particular
version
of
the
page
that
is
being
requested
to
review.
So
then
I
started
approvals.
B
Everything
is
said,
an
approval
in
the
condition
I
check
if
the
response
of
the
approval
is
approved,
if
it
is
I
use
the
same
content,
approval
action
and
I
said
it
to
approved,
with
the
comments
that
the
approver
supplied
during
the
during
when
they're
in
the
afterword
hit
approve
button.
Similarly,
if
it
was
rejected,
I
do
the
same
thing.
Instead
of
action
being
the
approve
here,
I
just
make
a
project
and
then
I
send
an
email
notification.
B
The
basically
saying
that
your
page
was
approved
or
your
page
was
rejected
and
that's
basically
the
floors
really
simple,
straightforward
and
you
see
the
ability
to
keep
using
what
you
get
from
SharePoint
or
you
have
the
ability
to
just
go
and
edit
the
page.
So
it
is
the
flow
and
add
your
own
governance
in
the
flow.
So
one
other
thing
that
happened
was:
if
you
go
to
your
library
settings
and
then
versioning
settings,
you
see,
you
have
now
content
approval
enabled.
So
that's
what
the
panel
did
as
well.
B
When
you
create
at
the
flow
now,
you
could
go
and
say:
no,
then
that
basically
means
you
don't
have
any
approvals
now.
The
other
thing
with
the
flow
is
that
you
have
the
option
running
multiple
flows
on
this
spacious
library
right,
it's
just
the
flow
in
its
library.
It
clear
how
much
ever
you
want
so
I
can
create
a
new
flow
again.
I
can
basically
name
the
approval
flow
to
be
different,
I
get
that
option
in
the
panel
once
it
comes
up
so
I
can
you
know
maybe
call
it
a
news.
B
A
B
B
A
B
Sail
it
home
and
he's
gonna
create
a
news
post,
because
news
post
is
something
different
from
a
normal
page
right.
So
now,
when
he
wants
to
submit
the
content,
he
will
now
get
two
options.
One
is
page
approval
and
when
his
News
approval,
so
these
are
the
two
flows
that
he
has
the
option
to
submit.
So
this
is
a
neat
way
instead
of
complicating
the
existing
flow
to
check
for
whether
it's
a
news
or
it's
a
page
or
its
type
of
page
or
whatever,
you
could
create
multiple
flows
and
just
manage
them
individually.
B
So
now
we
can.
You
know
John
know
that
this
is
a
news
post
I'm
supposed
to
get
music
and
you
click
news
approval
and
you
go
through
the
same
flow
of
basically
going
through
the
approval
process.
So
you're
not
limited
with
how
many
approval
flows
that
you
can
have.
It
basically
supports
all
of
those
scenarios
today.
So
this
is
page
approvals.
We
have
few
issues
as
well.
We
released
it
for
TRS.
If
you
go
to
aka
Don
MS
find
slash,
sorry,
SharePoint,
Paige
of
rules,
checks.
A
A
B
No,
these
are,
unfortunately,
are
issues
that
they
are
issues
and
known
issues,
though
they
they.
We
know
we
fixed
them,
but
something
cost
some
regression
and
it
didn't
ship.
So,
but
good
news
is
that
we
all
fixed
it.
It
might
be
there
next
week
or
so
so
those
won't
happen.
So
one
of
the
things
that
won't
work
is,
if
you
go
if
you
set
up
your
pages
library,
so,
for
example,
if
I
go
into
library
settings.
B
Versioning
settings
and
I
have
this
option
of
setting
document
version
history.
The
default
just
create
major
and
minor
versions
which
creates
drafts,
and
then
it
kind
of
1.1
1.2,
and
then
you,
when
you
publish
it,
becomes
true,
then
you
have
major
versions:
it
only
sticks
with
one
or
two
or
three
daro.
So
if
you
select
create
major
versions
right
now,
the
flow
the
system
will
fail.
We
know
we
fixed
it
before
it
caused
a
regression,
so
it
will
probably
be
fixed
next
week
or
so
in
the
service.
B
B
B
A
B
B
B
Thanks
for
reporting
this
issue
Ben,
if
you're
not
in
the
call-
and
basically
there
is
some
issues
with
creating
a
common
database
service,
which
is
what
the
floor
and
power-ups
use
behind
the
scenes
to
power
up
their
platform.
So
right
now
they
have
the
investigating
this
and
flow
team
will
publish
some
documentation
and
workers
on
how
to
rectify
this
problem.
But
until
then
page
approvals
won't
work
in
UK
if
we
create
a
new
tenant.
So
this
is
going
to
be
locked
as
a
known
issue
and
basically
will
be
resolved
by
the
flow
team
very
soon.
B
So
that's
something
to
keep
in
mind
if
you
already
have
a
tenant
in
UK
and
you're
already
working
there,
no
problem
at
all:
it's
just
the
nutrients
that
are
being
created,
I.
Think
since
March
are
something
you
can
see
the
thread
where
he
has
more
information
around
that.
So
bad
news
is,
it
doesn't
work
in
UK,
but
good
news
is,
if
you
do,
keep
us
giving
feedback.
We
are
listening
to
the
feedback
we
are
going
through
this
community
post.
B
A
That's
page
of
rules
now
checks,
two
questions
which
which
partly
we're
answered
actually
already
in
the
community
in
the
window,
but
I
wanted
to
make
sure
that
we
actually
get
it
recorded
as
well.
So,
first
of
all
approvals
for
me
is
that
is
there
a
view
where
you
can
actually
see
the
pending
approvals?
So
if
you
are
the
manager
who
needs
to
approve
plenty
of
submissions,
so.
B
B
A
B
B
We
have
plans,
similarly,
how
you
saw
you
are
able
to
create
a
flow,
some
webpage
for
approval
in
the
context
of
SharePoint
and
in
the
context
of
the
page,
we
will
work
on
bringing
this
approval,
setting
and
approval
history
in
SharePoint.
In
the
context
of
the
page,
you
can
see
all
of
the
history
and
everything
basically
in
SharePoint
without
needing
to
go
to
flow,
so
that's
in
the
backlog,
but
it's
a
good
question.
If
you
want
to
see
all
of
your
approvals
today,
you
have
to
go
to
flow
and
then
click
on
approvals,
cool.
A
The
second
question
is
that
do
this
approve
our
first
count
against
the
standard
flow
run,
count
for
license
and
perspectives,
and
it
was
answered
already
and
I
am
window
that
that
is
because
there's
a
typical
flow.
That's
this
or
no
it's
it's
a
flow
service.
We
just
in
SharePoint.
We
associate
flow
directly
to
the
page
approvals,
so
that's
understandable
now
and
then
the
obvious
one
quickly
is
how
about
documents.
So
can
we
get
similar
kind
of
things
for
document
approval
so.
B
Documentation
so
the
document
approvals,
the
only
difference
is
you,
don't
have
a
surface
to
submit
the
document
or
approve
or
reject
the
document
in
SharePoint.
We
never
have
that,
but
you
can
have
a
flow
and
basically,
you
know,
use
the
content,
approval
action
and
when
somebody
uploads
a
library,
somebody
approach
the
document
to
a
library
or
you
can
have
a
manual
flow
that
ones
that
you
can
go,
select
the
document
and
say
submit
for
approval
in
pages.
B
Since
we
have
actions
like
publish
or
some
and
a
surface
where
people
in
it
and
do
things
we
have
done
integration
in
Word
and
PowerPoint,
we
don't
have
the
option
to
publish
there's
no
concept
so
basically
I'll
do
it
in
in
the
library
and
then
make
it
work
with
your
content
approval
sitting.
But
it's
the
same
content
approvals.
It's
not
something
new,
so
I
actually
have
a
flow
here
called
document
approval.
Hopefully
the
screen
refreshes
right
through
the
designer.
A
B
B
A
B
I
mean
you
still
have
since
it's
using.
So
if
I
go
to
that
particular
library,
you
still
use
content
approval.
This
is
a
base,
basic
thing
that
we
use
for
managing
the
approval
status
in
SharePoint
right.
The
content
approvals
have
the
approval
status
column
that
gets
automatically
added.
It's
spending
its
draft.
It's
approved,
you
get
all
of
those
stuff.
So
that's
why
we're
not
doing
anything
new,
reusing
the
approval
status
column,
which
is
tied
with
the
content
of
rule
and
then
use
the
content?
B
Approval
status
flow
action
to
perform
those
now
one
thing:
if
this
is
this
is
a
you
know:
heavy
approval
system
right.
You
can't
do
anything
once
it
goes
to
pending
site
owners
only
can
change
the
status.
If
you
want
a
lightweight
action,
then
you
basically
select
the
document.
Imagine
you
don't
have
content
approval.
Stair
settings
here
is
turned
off
and
then,
if
you
click
flow,
you
will
get
you
option
you
want
when
we
have
the
need
to
go
to
another
library.
Yes,
I
thought
we
didn't
fix
that
bug.
B
A
B
B
A
I
I
think
what
you
said:
one
one
thing
to
really
kind
of
understand
that
if
you
are
at
let's
say
experience,
SharePoint
guy
you've
been
working
with
SharePoint
for
since
2007
or
2010
or
whatever
the
flow
is
just
piggybacking
on
the
out-of-the-box
approval
and
if
the
fields
and
functionality
is
everything
else.
So
technically,
it's
just
automating
those
updates
to
the
fields
and
and
approvals
of
the
item.
A
The
actual
approval
of
the
item
is
exactly
the
same,
which
has
been
there
since
2010,
or
something
like
that
or
pretty
much
teasing,
so
yeah
cool,
I'm
gonna,
actually
flip
back
on
the
slides,
because
I
do
have
some
content
and
slide
content
and
demos
which
I
want
to
go
through
as
well,
and
thank
you
checks
on
that.
There
was
good
discussion
on
the
entire
window
as
well,
and,
let's
see
how
many
Skype
crisis
I
will
have
on
the
later
part
of
their
called
the.
B
A
Yeah,
it
might
have
been
the
TCP
choke
which
actually
had
caused
disguise
the
crash.
So
who
knows
anyway?
So
the
second
thing?
What
we
wanted
to
talk
about?
That's
that's
super
cool
to
have
the
flow
functionality
for
SharePoint
Online
and
all
of
that,
but
the
one
thing
which
which
was
also
cool
but
because
there's
a
lot
of
people
still
in
on-premises
and
there's
a
lot
of
customers
we're
doing
high
print
deployments,
which
is
absolutely
one
of
the
key
value
propositions
in
Microsoft
platform.
A
A
Didn't
that
much
concentrate
on
what's
available
from
the
developer
platform,
and
and
now
that
I
came
back
from
vacation
I've
been
trying
to
address
those
gaps
from
a
perspective
because
absolutely
we
need
to
address
the
developer
platform,
documentation
side
of
the
story
as
well,
because
there's
a
lot
of
people
still
doing
even
farm
solutions
and
and
which
are
absolutely
100%
supported
in
the
future
as
well.
So
for
wrist.
Part
of
the
call
we're
gonna
concentrate
on
the
2019
developer
platform.
I'm
gonna
do
a
live
demo
on
this
as
well,
but
few
slides.
A
So
how
do
we
actually
get
started
on
SharePoint,
2019
preview?
So,
first
of
all,
if
you're
interested
on
testing
this,
you
need
to
download
to
2019
preview.
I
created
a
kms
link
for
that
one
earlier
today.
So
a
chemist's
SP,
dev
preview
that
will
point
to
the
plug
post,
where
this
announcement
was
actually
done.
A
So
the
2019
announcement
that
it's
available
in
the
blog
post
you'll
find
links
to
the
DVD
or
ISO
files,
and
also
on
the
guidance
files
which,
among
other
things,
they
actually
contain
the
license
to
install
the
2019
preview,
because
the
Installer
section
asking
the
license
ID
when
you're
running
through
that.
So
you
need
to
actually
access
those
files.
This
is
why
the
actually
get
started
with
this
one
is
really
to
use
a
sure
or
whatever
is
your
virtual
machine
platform.
A
So
now
what
I
did
for
2019
is
the
data
started
a
new
2019
server
and
associated
that
the
same
idea
ad
and
the
same
sequel
server
so
now
I'm?
Actually,
then,
in
the
same
environment
and
I
didn't
need
to
spin
up
the
whole
setup
again
and
it's
asking
link
to
SharePoint
2019
a
kms
SP
2019
preview
underneath
the
first
bullet
point.
That's
where
you
can
find
links,
and
there
yes
enable.
A
So
whenever
you
have
then
run
the
in-store
enabled
or
installed
shipment
when
in
nineteen
run
to
prereq
run
the
installer
run
the
setup
and
configure
thing
not
going
to
deep
dive
on
what's
actually
happening
there.
You
need
to
enable
the
adding
models
so
SharePoint
framework,
if
you're
planning
to
use
the
SharePoint
framework
in
SharePoint
2019,
you
need
to
enable
add-ins
in
the
environment,
and
that
means
that
you
need
to
make
sure
that
you
have
observers,
application,
enable
and
subscription
settings
service
application.
A
It
doesn't
really
understand
that
hey
who
you're
actually
using
SP
pkt
file,
not
an
app
file,
so
there's
no
exceptions
on
that
and
that's
why
the
add-in
model
has
to
be
enabled
at
least
for
now.
Now,
then
you
want
to
install
obviously
no
chest
and
bmu
and
called
the
basic
setters
for
SharePoint
framework
development
and
you
wanna
install
SharePoint
framework.
One
point
four
or
one
point
four
point:
one:
there
are
some
there
might
be
some
changes
on
this
one
we're
still
debating
on
the
unofficial
final
document
guidance
on
this
one.
A
We
were
still
in
preview,
how
it's
gonna
add
and
in
the
preview
timeframe,
at
least
for
me.
The
one
point
four
point:
one
actually
works
perfectly
well
now
and
when
you're
actually
creating
a
shipment
framework
solution,
you
need
to
choose
a
sharepoint
online
only
as
the
baseline
option
and
that
might
seem
slightly
confusing.
But
that's
because
in
the
sharepoint
framework,
when
you're
creating
a
solution,
there's
two
options:
are
you
targeting
sharepoint
2016
or
are
you
targeting?
A
I
went
online
and
we
don't
have
yet
option
for
sharepoint
26
upon
2019,
so
that's
gonna
be
part
of
the
sharepoint
framework
1.6,
which
is
scheduled
to
be
out
later
this
month.
I'm
gonna
explain
that
in
practice
in
a
live
demo
as
well,
but
after
this
one
we
basically
then
have
a
sharepoint
framework
running
in
your
farm,
and
you
can
actually
do
extensions.
You
can
do
other
stuff
as
well.
Now,
if
your
are
a
chiffon
developer,
probably
quite
interested
what
is
actually
supported
in
sharepoint
2019-
and
this
is
now
the
status
for
preview.
A
There
might
be
some
exceptions
for
this
for
RTM,
but
they
will
be
really
really
small,
so
this
is
pretty
much
the
status
for
go
live
as
well,
so
there
will
be
obviously
morning
pages
modern
lists,
big
thing
and
modern
pages.
Modern
experiences,
modern
sites,
so
modern
team
site
without
association
to
the
group
and
communication
status
included.
Modern
sub-site
will
be
there
in
GA
right
now
in
the
preview
version
of
SharePoint
2019,
the
modern
sub-site
isn't
not
actually
exposed
in
the
UI
we
are
debating
on
giving
you
the
workaround
on
that
one.
A
You
can
actually
because
it
works
in
the
preview
as
well,
but
we'll
give
you
the
workaround
in
our
documentation
most
likely
later
SharePoint
framework,
apps
extensions
and
webparts
absolutely
supported
web
hooks
supported
as
well
as
it
packaging
is
supported,
and
that
means
that
if
you
create
a
SharePoint
framework
solution,
you
can
just
include
javascript
files
and
images
inside
of
the
SP
PKG
file
and
will
host
that
for
you
from
that
catalog.
So
you
don't
have
to
worry
about
to
see
the
end
column,
formatting
and
list
column
formatting.
Is
there
ten
on
scope?
A
Deployment
is
available,
so
you're
able
to
push
webparts
directly
across
your
form
by
adding
them
to
their
catalog
big
thing
as
well
and
alm
api's
is
available
as
well.
Now,
what's
not
available
well
before
we
actually
own.
The
yes
part
still
just
do
not
avoid
confuse
anybody.
Obviously,
classic
experience
is
still
there
form
solutions
is
still
there.
Sandbox
solutions
still
there
feature
framework
still
there,
so
all
of
the
under
stuff
classic
stuff.
Absolutely
there
everything
what
you
had
in
SharePoint
when
a
16
pretty
much
is
available
in
2019
as
well.
Just
to
avoid
any
confusion.
A
A
Now
is
there
a
plan
to
allow
modern
sub
sites
in
a
long
term
shipment?
The
you
call
yesterday
implied
it
was
no
no
I,
don't
know
what
is
a
SharePoint
EU
call,
but
that's
wrong.
Actually,
we
are
looking
into
allowing
modern
subsides
in
a
long
term
for
shipment
online
and
for
on-premises
as
well
so
sure
we
recommend
people
to
have
potentially
individual
sites
in
individual
site
collection
that
is
more
performant
design
and
using
hub
sites
in
SharePoint
Online
now
in
on-premises,
hub
sites
are
not
supported,
so
they
didn't
actually
make
that
they.
A
They
were
released
and
SharePoint
Online
slightly
too
late
for
getting
them
included
in
SharePoint
2019,
and
that's
why
hub
sites
are
not
available
in
2019
and
will
not
be
there
in
GA
site
designs.
Unfortunately,
not
there,
then
on
properties,
not
their
modern
themes
are
not
there.
This
is
actually
slightly
even
slightly
painful,
to
be
honest
and
because
the
the
out-of-the-box
modern
themes
for
modern
sites
and
communication
sites
is
there,
but
the
capability
for
you
to
introduce
a
modern
theme
as
an
option
is
unfortunately
not
available.
You
can,
however,
use
the
classic.
A
What
is
it
look
and
feel?
Look,
but
is
it
the
classic
theme
capability,
whatever
it's
called
I
can't
remember:
site
collection,
app,
catalog
might
be
actually
there.
It's
pretty
close.
Thank
you.
Composite
looks
mentioned
under
a
window
and
the
site
collection
app
catalog
right
now
it
doesn't
work
in
preview.
It
might
be
there
in
GA
we're
looking
into
potentially
making
that
happen
as
a
hotfix
in
general,
shape
and
framework
third-party
version
will
be
one
point
four
or
one
point
four
one.
This
is
still
slightly
debatable.
A
There
is
a
pretty
big
difference,
however,
between
one
point,
four
and
one
point:
four:
one,
because
there's
a
difference
between
the
node
supported,
node
versions
and
ambient
version,
so
we're
trying
to
push
it
to
the
1.41,
but
we
haven't
yet
really
looked
the
whole
thing
good
and
are
we
looking
at
few
years
without
hub
sites
for
own
premises?
Unfortunately,
that
seems
to
be
in
our
studies.
We
can't
promise
and
put
anywhere
when
there
will
be
additional
capabilities,
form
premises.
Potentially
they
might
at
some
point.
Potentially
they
might
not.
A
So
don't
quote
me
on
saying
that
some
of
these
capabilities
will
be
released
later
they
basically
the
hop
sites
went
GA
in
SharePoint
Online
too
late,
comparing
to
the
timelines
of
getting
stuff
included
in
SharePoint
2019,
because
we
need
to
remember
that
SharePoint
2019
is
based
on
SharePoint
Online.
The
latest
version
is
already
in
SharePoint
Online.
The
the
ship
on
2019
is
a
fork
from
earlier
this
year
from
SharePoint
Online,
and
then
we
clean
up
the
cloud
dependent
capabilities,
the
way
cool,
focusing
isn't
for
that.
Don't
use
that
I
think
it's
actually
supported.
A
Next
steps
for
ship
and
2019
development,
so
some
things
before
I
do
the
live
demo
as
well,
so
the
season,
lookit
and
so
client-side
object
model
new
kit
for
SharePoint
2019
I
was
planning
to
get
it
out
before
this
call.
Unfortunately,
there
was
a
unexpected
certification
thing:
it
would
still
need
to
figure
out
with
new
get
people.
A
Eta
right
now
is
tomorrow,
so
you
can
actually
then
start
doing
development
against
you
up
on
2019,
what's
actually
kind
of
interesting,
technically
SharePoint
2016
season
look
at
dust
work
which
you
have
on
2019,
what
that's
been
missing,
some
of
the
capabilities
which
are
available
in
2019
I'm
not
going
to
deep
dive
on
the
version
in
differences
here.
I
might
actually
do
that
later
in
some
of
these
calls
and
why
that
is,
but
let's
actually
concentrate
on
that
one
in
this
one
now
Shipman
2019
needed
support
in
SharePoint.
A
When
is
SharePoint
framework
1.6,
so
in
SharePoint
framework
1.6,
which
is
ETA
by
the
end
of
August,
there
will
be
an
option
where
you
can
actually
target
the
code
to
be
targeted
on
a
ship
and
2019
onwards,
including
SharePoint
Online.
So,
basically,
you
will
have
then
three
different
options.
When
you
run
the
Yeomen
template
and
one
of
them
will
be
then
four
twenty
twenty
nineteen
api
documentation
updates
ETA
in
September,
so
API
season,
maybe
a
server-side
API
updates.
We
unfortunately
somehow
matically
didn't
do
this
for
SharePoint
2016
I.
A
A
And
loading
three
dots
I
can
see
that
somebody
should
be
saying
my
screen.
Somebody
needs
to
confirm
America,
1,
2
3,
yes,
exciting
cool.
So
let's
have
a
look
on
things.
So,
first
of
all
the
how
to
get
started
on
the
preview
is
that
if
you
write
a
kms
in
a
kms,
I'm,
gonna,
actually
zoom
in
here
a
kms
SB
2019
preview,
that's
gonna,
actually
land
you
on
announcing
availability
on
SharePoint,
Server,
2019
preview,
page
from
build
beer
which
concentrates
on
the
enthusiatic
bilities.
A
And
if
you
scroll
down
here,
you
can
actually
find
the
relevant
download
links
and
also
what
you
need
to
have
and
also
have
a
look
on.
Is
this
reviewer
guide
and
QuickStart
guide,
because
this
contains
the
licensing
information
or
the
license
information
for
2019?
There
was
a
question
around
guidance
on
upgrading
from
2090
2016
to
2019,
honest
to
be
honest.
A
I
haven't
checked
on
that
at
all,
so
I
can't
confirm
or
deny
do
we
have
guidance
on
that
or
not
so
simply
haven't
had
a
time
to
check
that,
but
this
basically
gives
you
the
preview
version
and
you're
able
to
then
install
that.
So,
in
my
case,
what
I've
done
like
explained
I
actually
have
a
2013
environment
with
an
azure
ad
sorry,
AD,
sequel,
server,
provisioned
at
some
point
and
then
what
I
did
was
that
I
had
just
added
my
2019
preview
machine
right
next
to
that
setup.
A
So
this
way
I'm
just
expanding
my
own
premises.
Environments
on
that
set
up
well
in
this
particular
subscription,
so
I
do
have
quite
a
few
subscriptions,
but
this
is
my
MSDN
subscription,
but
technically
that's
how
I
added
my
2019
pretty
easily
available
in
usher
for
my
VM
environment.
So
basically
every
one
of
you
probably
have
your
own
way
of
doing
this,
and
that's
absolutely
fine
will
anyway
at
guidance
and
article
which
is
explaining
how
to
get
started
sooner
or
later
in
our
developer
documentation
as
well.
A
Now,
let's
see
here's
my
actually
SharePoint
2019
environment,
so
few
things
here.
So
what
did
I
actually
want
to
pinpoint
so
a
few
things
from
a
service
application
site?
So
we
get
this
one
covered
so
in
here,
if
you
run
the
configuration
this
hurts.
So
if,
when
you
run
the
SharePoint
2019
installation,
it
actually
asks
you
the
configuration
wizard
to
run
as
an
one
of
the
options
when
you
start
up
now,
some
of
you
might
say,
and
all
of
the
advanced
people
are
saying
that.
A
Well,
you
should
never
ever
use
to
this
art,
but
if
you're
using
this
for
development
usage
well,
do
these
artists
are
in
pretty
decent
job.
So
you
don't
actually
have
to
wait
hour
on
the
Power
Cells
and
all
of
that
to
configure
everything
it
configures
your
environment
pretty
nicely
only,
and
it
actually
creates
also
that
management
service,
so
after
management
service
application,
but
it
does
not
create
subscription
service
applications
and
that's
something
what
you
need
to
manually
create
using
PowerShell,
and
this
is
something
what
we
will
absolutely
include
in
our
documentation.
A
But
you
need
to
create
this
to
your
tenant
as
well
to
be
able
to
a
SharePoint
framework
in
your
SharePoint
2019
environment.
The
second
thing:
what
you
need
to
do
in
the
form
is
configure,
create
def,
catalog
and
also
configure
to
app
URLs,
even
though
she
upon
framework
doesn't
use
the
app
domain.
But
these
are
pre
requirements
in
the
process
and
potentially
will
look
into
skipping
this
wide
GA
so
we'll
see
if
we
can
actually
get
it
fixed.
But
you
need
to
do
this
for
preview,
at
least
after
that's
actually
done.
A
You
are
and
then
a
basically
ready
for
SharePoint
framework
development
in
general
in
SharePoint
2019.
It
is
almost
like
SharePoint
Online
well
in
certain
ways,
so
it
looks
like
a
shipment,
here's
the
SharePoint
home,
if
I
could,
if
you,
if
I,
go
to
the
app
launcher,
we
can
actually
say
that
this
newsfeed
still
there's
a
onedrive
link
that
SharePoint.
So
it
looks
like
a
SharePoint
to
mine
and
women.
Now
in
here,
I
can
absolutely
then
create
sites.
A
A
Sharepoint,
so
this
one
will
start
to
SharePoint
framework
generator
and
there
is
I
just
can't
do
this
properly.
So
let
me
actually
do
this
yo.
This
is
always
good.
Yes,
I'm
always
doing
that
mistake.
Thank
you
David,
but
you
can
always
start
here
if
needed,
because
if
you're
lazy,
you
can
just
select
the
Microsoft
SharePoint
from
here
and
then
it's
that's.
Gonna
actually
start
this
thing
now,
in
my
case,
I've
installed
shipment
framework.
A
One
point
for
point:
one
to
this
environment:
I'll
show
that
one
in
in
a
second,
which
means
that
when
I
actually
create
the
solution,
I
wanna
target
the
shipment
online,
even
though
that's
slightly
confusing,
but
the
SharePoint
2016
onwards
is
for
SharePoint
2016.
That
will
actually
create
your
SharePoint
framework,
1.1
version
of
the
environment,
this
one
because
I'm
actually
installed.
One
point
four
point:
one
will
create
me.
One
point
four
point:
one
solution:
so
that's
actually
the
right
one.
A
A
Let's
see
actually
find
the
right
keys
from
my
keyboard.
I'm
still
learning
this
keyboard
no
come
on
there
we
go
so
in
my
case.
I
do
have
a
SharePoint
framework,
a
shipment
framework
in
stock,
but
it's
one
point
four
point
one
and
how
did
I
get
that
installed?
It's
actually
getting
installed.
So
if
you
do
installation-
and
all
of
this
is
absolutely
getting
documented-
so
if
I
do
MPM,
install
Microsoft,
SharePoint,
generator
and
I
add
explicitly
the
right
version
in
the
end
of
this
comment.
That
will
then
install
the
one
point.
A
Four
point:
one
version
for
me.
So
that's
how
you
actually
target
the
specific
version
to
be
installed
on
this
machine
cool
in
my
case,
I've
actually
created
a
call
extension
just
to
show
this
one
in
practice
and
I.
Do
apologize.
We'll
go
fight
Lea
slightly
long
today,
because
I
want
to
get
this
one
documented
as
a
video.
A
You
need
to
be
aware
that
or
don't
get,
let's
say
fault.
So,
when
I'm
instantly
the
solution,
it
is
using
asset
packaging.
The
packaging
means
that
my
JavaScript
files
and
my
images
are
automatically
hosted
by
the
farm.
So
you
don't
actually
need
to
host
these
JavaScript
files
anywhere,
which
is
pretty
cool.
So
it's
inside
of
the
solution
package
almost
like
a
almost
like
a
sample
solution,
but
not
quite
now
what
it
means.
Then
it
is
that
when
I'm
installing
this,
it's
actually
saying
ooh.
A
So
it's
actually
saying
that
the
client-side
solution
will
get
content
from
following
domains.
And
it's
saying
shipment
online,
which
is
highly
confusing
and
that's
a
mistake
because
we
just
haven't
actually
considered
on-premises
in
this
dialog,
so
it
should
say
SharePoint
form.
So
it's
not
actually
copying
anything
on
a
sharepoint
online.
You
don't
have
to
have
a
sharepoint
online.
A
Everything
is
from
the
on-premise
environment
now
clicking
that
is
gonna,
add
an
install
the
solution
and
that's
now
available
and
now,
if
I
go
back
to
that
site,
which
we
just
created,
community
called
demo,
site
content
and
I've
installed
or
or
I
have
all
of
the
capabilities
available.
I'm
adding
an
app
I
can
actually
see
my
C
called
demo
client-side
solution
available.
That's
now
getting
installed
on
the
page
and
in
any
second,
we
can
actually
then
see
the
extensions
available
and
getting
loaded
on
the
side.
A
So,
let's
see
one
two,
three
one,
two
three
still
installing
there's
a
timer
job
running
behind
off
the
scenes
in
the
server
and
whenever
the
time
a
job
has
executed
properly,
we
were
able
to
see
that
the
extension
has
been
installed
properly.
The
design
now,
what's
also
just
a
pin
point,
is
that
this
one
we
do
support
tenon
scope
deployment,
so
you're
able
to
use
that
one
to
go
shred
points
by
the
way,
Pavel's
comments,
app
deployment
has
been
taking
some
time
lately.
This
is
my
own
premises
form.
A
So
whatever
has
taken
time,
for
you
doesn't
mean
that
it's
taking
time
for
me
in
my
own
premises
form
so
that's
a
different
setting.
Now
there
we
go
there's
my
extension
extension
is
getting
rendered.
It's
a
super
cool
header
component
and
now
seriously
and
a
super
cool
and
awesome
footer,
oh
my
god,
but
you
can
actually
see
that
my
extensions
are
getting
rendered
properly
in
on
premises,
form
it's
Chevron,
2019
and
things
are
working,
but
the
tenant
scope
deployment
like
mentioned,
supported
you're
able
to
push
webparts
available
to
all
of
the
sides.
A
You're
able
to
use
that
actually
also
together
with
extensions.
But
then
you
need
to
enable
the
extension
in
a
side-by-side
level.
One
point
still
on
the
demo
side
of
the
story.
If
I
go
to
the
sharepoint
and
really
pinpoint
this
one
he
disappeared
and
that
we
don't
have
a
site
designs
available,
which
means
that
you
can
actually
modify
this
selection
and
it
can't
actually
modify
what's
happening
with
the
communication
sites
or
the
team
site
creation,
and
that
is
a
nasty
limitation
technically
and
if
you
need
to
run
code
whenever
the
communication
side
is
created.
A
That
means
that,
well,
I
shouldn't
probably
say
this
out
loud,
but
there's
always
an
option
of
implementing
a
form
solution
and
using
feature
stapling,
so
not
necessarily
the
optimal
solution.
But
then
again,
it's
on-premises
form
solutions,
absolutely
support
it.
If
you
want,
you
can
still
use
classic
experiences,
you
don't
have
to
use
the
modern.
You
can
gradually
introduce
the
modern,
so
there's
multiple
different
options
for
you
to
take
advantage.
So
we
do
not
force
only
modern
in
shape.
One
2019,
but
yes,
I,
mean
I
said
it
is
different.
A
Everyone
told
me
yesterday
that
you
can't
say
that,
but
it
is,
if
you
have
a
business
scenario,
that
you
need
to
enable
running
code
whenever
a
modern
air
communication
site
is
getting
created,
probably
feature
stapling
is
the
only
way
to
do
that.
Now.
Let
me
actually
come
back
on
the
slides
and
we
can
close
up
the
call.
I
probably
missed
some
of
the
questions
and
the
PMP
packet
yeah,
there's
a
few
other
things
in
the
in
the
2019
preview,
where
the
community
good
able
to
help.
A
But
it's
it's
one
of
those
things
that
do
we
actually
want
to
do
that
and
do
we
actually
want
to
and
do
that
in
practice
or
drive
the
farm
solution,
scenarios
and
still
phone
Prem,
let's
see
if
I
can
actually
get
the
slides
available
on
the
PMP?
Yes,
oh
there's
a
nice
virtus
or
sharepoint
variation,
so
loading
of
the
slides
there
we
go.
We
went
a
few
minutes
long
I
do
apologize
on
that.
We
had
a
to
2
months
of
discussions
with
Jax,
but
that's
fine.
A
Let
me
actually
close
that
one
next
time
we
don't
have,
if
there's
any
urgent,
Q&A
questions
which
I
missed,
you
can
still
put
them
in
the
I
window.
I
can
answer
in
the
I
window
also
after
we
close
to
call,
but
next
dev
cig
meeting
is
on
August
23rd.
The
next
SharePoint
framework
meeting
is
on
next
Tuesday
and
we
do
have
the
monthly
community
call
coming
on
next.
Sorry,
the
community
open
framework
special
interest
group
on
Thursday,
the
monthly
community
call
on
Tuesday.
So
there's
quite
a
few
calls.
A
You
can
absolutely
also
join
watch
the
course
or
the
demos
using
the
recorded
YouTube
videos
as
well,
so
that's
an
absolutely
an
option
as
well,
but
for
now
I
think
it's
time
to
move
on.
So
thank
you
for
those
who
joined.
Hopefully
that
was
interesting,
and
hopefully
that
was
beneficial
for
your
work
as
well.
The
call
has
been
recorded.
The
video
will
be
available
in
SharePoint
dev
YouTube
channel
within
24
hours.
So
thank
you,
everybody
and
thank
you
for
your
feedback.