►
Description
PnP Webcast around different activation options for SharePoint Framework extensions. Covers 3 different methods to activate an extension in the site with live demos.
Covered topics following
- Activation of extension using feature framework
- Tenant deployed extensions and how to activate them
- Globally deployed extensions (announced in Build 2018)
More documentation around SharePoint Framework extensions is available from http://aka.ms/spdev-docs.
A
Welcome
to
the
ship
and
partisan
practices
webcast
and
system
we're
going
to
talk
about
one
of
the
activation
options
of
viewership
on
fabric
extensions
to
the
SharePoint
site.
So
technically,
how
do
I
keep
my
shape
and
framework
extensions
available
within
my
sites?
What
are
my
options?
How
do
I
do
that
automatically,
potentially
in
tenant
wide
and
so
to
say
and
we'll
have
August
and
live
demos
for
all
of
these
options.
In
this
webcast
my
name
is
Esther.
A
Thank
You
Valda,
if
somebody
don't
know
who's,
wild
Exxon
is
good
donor.
Who
has
clarified
that
one
now?
So,
let's
actually
start
this
discussion
with
a
a
one
classic
slide,
which
we
actually
had
in
a
previously
recorded
webcast-
and
this
is
a
good
discussion-
is
not
good.
Let's
say
an
option
slide
to
come
in,
let's
say
start
discussing
these
options.
So,
first
of
all,
when
you
create
your
SharePoint
framework
solution
as
part
of
the
yeoman
flow
or
after
the
yeoman
flow,
you
can
configure
this
in
the
in
the
solution.
A
Packets,
a
JSON
file,
we're
asking
or
you
need
to
make
a
decision-
is
that
solution,
tenant,
scoped
or
not,
and
there
should.
This
is
a
really
important
question,
because
if
it
is
not
an
scoped
solution,
you
will
need
to
explicitly
install
that
solution
to
the
site
before
any
of
the
components
include.
The
extensions
of
web
parts
are
available
within
a
site
to
take
advantage
or
to
be
able
to
be
used
if
it
is
at
an
inscribed
option.
A
This
actually
gives
you
the
opportunity
of
having
your
VIP
parts
automatically
available
in
the
vapor
picker
in
the
site,
but
because
there
is
no
extension
picker
in
the
site
level
for
administrator
for
end-users,
which
makes
a
lot
of
sense.
The
extensions
are
technically
available,
but
they're
not
actually
activated
so
they're
not
visible
in
the
site.
So
that
means
that
there's
always
an
additional
step
which
you
need
to
perform
for
getting
the
extension
in
the
site
level.
Does
it
make.
B
A
Question
obvious:
a
us,
a
solution
architect
or
a
solution
designer
on
the
developer.
You
need
to
make
that
decision.
So
are
you
building,
for
example,
let's
say
an
specific
application
or
a
solution,
which
is
how
would
I
put
it?
It's
a
one
self-contained
solution
which
is
meant
to
be
installed
one
by
one
to
the
sides
where
it's
actually
being
used.
So
you
don't
want
to
have
your
webparts
available
across
the
channel.
A
That
would
be
a
design
decision,
so
then
make
sure
that
your
you're
packaging
everything
to
a
non
tenant
scoped
solution,
so
somebody
explicitly
is
not
add
the
package
to
their
site
and
then
they
get
additional
components
and
and
capabilities
available.
But
if
you,
if
you,
for
example,
creating
a
web
part
which
you
want
to
have
available
for
all
of
the
sites,
then
you
absolutely
do
students
code.
So
it's
a.
It
is
a
design
decision
which
you
as
a
developer,
need
to
do.
B
A
Because,
as
part
of
that
option,
you
can
do
a
feature
framework
based
configuration
for
the
site
in
the
elevated
mode
and
the
elevated
mode
means
is
kind
of
needed,
because
if
you
could
obviously
have
a
bit
part
which
creates
the
list
for
you
whenever
the
web
part
is
being
used.
But
what,
if
the
end
user
doesn't
have
permissions
to
create
a
list?
There
is
no
wave
to
elevate
because
we're
we're
basically
talking
about
JavaScript
here.
If
that
made
sense,
makes.
B
A
Activation
option,
so
let's
talk
about
slightly
this
option,
so
this
is
this
comes
down
on
the
the
it's
kind
of
a
well,
it's
highly
dependent
on
the
previous
slide
as
well.
So
how
do
we
actually
make
SharePoint
framework
extension
available
in
a
site
level,
so
we
have
a
three
different
options
and
the
third
option
was
introduced
in
the
build
2018,
so
basically
May
2018
forward.
It
was
announced
and
we're
going
to
talk
about
that
one
today.
A
But
if
you
watch
this
webcast
immediately,
when
this
record
closed
like
live
that
option,
it's
not
yet
available
for
you.
So
that's
coming
slightly
later,
I'll
come
back
on
that
one
in
a
second
now,
the
local
activation
is
the
first
option,
and
this
basically
means
that
the
solution
is
deploying
to
that
catalog
and
but
it's
not
tenon
scope
to
the
point.
So
you
basically
are.
The
solution
is
getting
activated
when
you
install
that
explicitly
to
the
very
site,
so
somebody
needs
to
go
and
install
the
solution
to
the
site
level.
A
You
can
technically
go
and
modify
the
parameterization
afterwards,
but
it's
not
really
typical
thing
to
happen.
The
second
option
is,
then,
the
own
demand
activation-
and
this
is
say
a
terminology
which
were
actually
by
the
way
introducing
in
this
webcast.
But
don't
demand.
Activation
basically
means
that
your
solution
is
deployed
to
Deb
catalog
and
activated
in
a
channel
scope.
So
inside
of
your
package
solution,
JSON
file,
you
have
configured
your
solution
via
tenon
scope
as
available
internal
scope.
So
that
means
that
there's
no
site
specific
installation.
A
So
if
a
person
goes
to
the
add
and
add
functionality
inside
your
solution
is
not
visible
to
be
installed
at
the
site
level.
So
all
of
the
webparts
like
in
the
previous
slide,
all
of
the
web
parts
are
automatically
available
in
in
all
of
the
sites
which
are
part
of
that
package
because
or
they
are
available
in
a
bit
per
speaker.
A
We
already
announced
this
that
if
this
is
coming,
but
it
hasn't
been
yet
available,
so
there
will
be
a
side
script
action
support
for
this
one
sooner
or
later.
And
what
it
means
is
that
if
you're
using
the
native
out-of-the-box,
I'd
provisioning,
site
collection,
provisioning
from
the
SharePoint
home
or
you
are
using
the
side
scripts
using
the
the
publish
on
you're
able
to
activate
the
extension
on-demand
in
the
site
collection
as
part
of
that
provisioning
process
or
when
you
are
applying
a
side
script
to
the
site.
B
So
don't
I
wanted
to
clarify.
Is
that
or
to
ask
if
that?
That's
indeed
the
case
right
so
here,
if
you
choose
tenant
wide
deployment
and
activation
of
your
extensions
and
webparts,
that
means
that
if
there
is
dependency
to
a
list
or
a
field,
colon
type
that
will
not
be
available
on
the
side.
So
if
that's
the
case,
you'll
always
need
to
use
it
in
combination
with
provisioning
peace.
That
will
make
these
lists
and
artifacts
fields.
Contacts
available
on
the
sides
where
you
want
to
use
the
web
person
extensions
right,
absolutely.
A
Absolutely
exactly
the
job,
that's
really
what
good
way
of
putting
that.
So,
if
there's
any
dependencies
on
the
web
part,
you
will
have
to
have
them.
For
example,
remote
provisioning
techniques
apply
it
to
the
site
or
a
site
script
action
which
will
then
create
a
list
with
the
dependent
schema
for
the
site
for
the
extension
of
a
part,
that's
really
good
way
of
putting
it.
A
A
The
third
option
which
we
announced
in
2018
are
built
is
a
global
activation.
This
is
in
well,
it's
in
quotes
because
it's
it's
it's
a
closed
activation,
no
doubt
and
you're
able
to
control
this
globally
in
that
in
the
in
the
tenant
level.
It's
in
quotes
because
we
don't
didn't
want
to
use
the
term
tenant
app
activation
because
that
all
the
lives
with
the
tenant
scoped
deployment.
A
So
you
have
this
global
control
and
you're
able
to
modify
that
anytime.
So
if
you
can
always
go
to
the
list
and
modify
which
are
the
extensions
and
they're
instantly
asian,
which
is
getting
rendered
as
part
of
these
and
modern
sites,
or
you
can
well
you
you
can
choose
which
are
the
extensions
for
which
site
types
and
like
no,
they
don't
really.
This
is
supported
only
for
obviously
for
modern
sites,
like
other
extensions
as
well,
because
to
modern
sites
or
the
modern
experiences.
A
I
would
be
more
specific
on
that
one,
so
you
can
actually
have
a
classic
theme
site,
which
has
the
modern
experiences
and
you're
able
to
use
the
global
activation
for
them
as
well.
This
you're
able
to
support
filtering
you're
able
to
do
filtering
of
the
extension
in
the
site,
template
or
in
a
list
template
level
so
you're
able
to,
for
example,
say:
hey
this
contextual
menu
button
or
toolbar
button.
In
the
list
view
command
set
is
visible
in
all
of
my
document.
A
Libraries
in
my
Tanna
or
it's
targeted
to
be
visible
only
in
a
custom
lists
in
my
tenon
or
you're,
able
to
say,
for
example,
that
this
application
place
for
extension
of
order
extension
would
be
available
in
all
the
communication
sites.
As
an
example,
questions
calling
me
randomly
trying
to
explain.
B
So
in
in
a
way,
if
I
think
about
the
to
the
on
demand,
activation
and
global
one
in
a
way
that
they
are
the
same
with
regards
to
the
day,
do
not
provision
any
artifacts
that
you
might
need
right.
So
from
that
regard,
you
still
need
to
ensure
that
they
are
there,
but
the
biggest
benefit
to
the
the
the
latest
all
option,
the
one
that
allows
you
to
globally
activate
or
enable
your
extensions.
It's
the
fact
that
it
works
on
both
new
and
existing
sites,
which
is
really
great
great.
B
If
you
want
to
build
some
songs
or
something
new
to
extend
your
your
parole
and
then
have
it
enabled
consistently
across
the
whole
internet,
all
sides
of
given
type
or
just
all
all
sites
experiences
yes,
and
you
want
to
do
it
consistently
across
the
board,
because
otherwise
you
would
need
PowerShell
script,
that
iterates
through
all
of
them
and
then
also
ensure
that
every
single
time
there
isn't
you
create
its
site.
You
would
either
need
to
extend
your
site
design
with
the
side-side-side
script
when
that's
available
or
provisioning
wise.
B
A
Absolutely
and
like
I
said
you
don't
have
to
as
an
example,
something
before
this
option.
You
were
forced
to
reassociate
or
reapply
or
add
a
new
user
customer
action
entry,
for
example,
for
food
around
hitter
for
all
of
your
sites,
and
what,
if
you
have
100,000
sites,
that's
going
to
take
a
while
to
actually
process
with
this
one?
You
have
a
global
control
on
what
extensions
will
be
visible
globe
from
a
one,
centralized
location
and
that's
brilliant.
That's
absolutely
I
really
really
like
this
functionality.
A
B
And
I
think
that
one
important
thing
to
keep
in
mind
is
that,
while
you
can
easy
so
when
you
create
the
entry
to
enable
the
extension
across
the
board,
you
can
specify
parameters
right.
So
in
that
way,
it's
probably
reasonable.
Yes,
you
can
parameterize
it,
but
the
same
parameters
will
be
used
on
all
sides
right
because
you
enable
it
for
all
experiences
for
all
lists
for
all
sites
right,
so
the
same
parameters
will
be
used
across
the
board
right.
So
it's
a
pro
and
a
con
absolutely
right,
because
in
a
way
it
limits
you
you're.
A
Absolutely
so,
and-
and
there
is
a
even
obviously
after
the
global
activations
report
being
available,
there's
absolutely
still
at
a
roll
and
a
demand
for
on-demand
activation
and
also
the
site,
scoped
or
local
activation
as
well.
So
having
these
three
options
will
then
cover
pretty
much
well.
I
can
come
up
with
a
scenario
which
which
would
not
be
covered,
but
we're
covering
all
of
the
different
scenarios.
How
would
I
get
my
shape?
One
framework
extension
available.
Do
I
want
to
have
it
available
in
off
the
side.
Check.
A
Do
I
want
it
available
only
for
a
certain
division
or
a
certain
set
of
sites,
for
example
using
a
site
design
which
is
targeted
for
a
HR
people,
and
then
HR
people
are
seeing
that
they
create
a
site,
and
then
they
will
have
an
extension.
That's
checking
on
the
on
demand
action.
So
you
and
there's
multiple
options
on
that
one
as
well
or
if
you
want
to
have
an
intuitive
and
I,
want
to
install
this
solution
from
the
app
catalog
to
my
site
and
then
will
activate
certain
things.
A
A
A
Okay,
so
let's
have
a
look
on
the
different
options
in
practice
and,
let's
start
with
a
local
activation
and
local
activation
meant
that
we
are
installing
a
application
to
the
site
explicitly
and
activating
that
to
be
available
from
an
extension
perspective.
So
in
this
scientist
to
say,
just
newly
created
site,
which
was
just
created
for
the
wakeup
cast
purposes,
brilliant
that
we're
going
to
actually
create
their
slides
so
as
sorry
sites
and
so
fast,
so
I'm
going
to
actually
go
here,
I'm
in
a
classic
experience.
A
Let's
go
actually
to
the
modern
experience
just
as
well
so
now
we're
in
the
modern
experience
and
we'll
go
new
and
add
an
web
app,
that's
web
and
app
and
in
my
case,
I
have
at
the
local
deploy
client-side
solution
available
from
the
App
Catalog.
So
I
already
installed
that
solution
to
be
available
and
I've
got
within
this
tunnel.
So
let
me
click
that
one
and
that's
gonna
then
start
installing
that
adding
or
app
in
this
case
well
technically
SharePoint
framework
solution
to
the
site.
A
Extension
and
food
are
saying
that's
located
by
extension,
so
this
extension
was
activated
to
the
site
because
we
explicitly
install
this
solution
to
the
side
and
obviously
it
doesn't
matter
where
you
are
within
the
site.
That
extension
is
getting
been
dirt,
and
in
this
case
it
is
also
following
up
on
the
on
the
theming
rendering
in
certain
level.
So
that's
why
the
coloring
changes
are
happening
now,
Oh
back
on
the
solution
and
let's
have
a
look
on
what
actually
happened.
A
So
this
is
a
relatively
simple
SharePoint
framework
extension,
following
up
pretty
closely
on
our
tutorials,
so
wanted
to
give
it
as
simple,
because
the
experience
isn't
really
the
key
point
it's
around.
How
do
we
get
it
deployed
to
the
site
level?
And
how
do
we
do
that
is
by
by
default
when
we
select
that
this
solution
not
to
be
a
tenon
scope
and
having
an
extension,
the
SharePoint
yeoman
template
actually
generated
this
element.
Xml
file
and
the
element
XML
file
was
generated
with
a
custom
action
entry
and
with
the
right
client-side
component
ID.
A
A
What
this
technically
means
in
practice
is
that
whenever
this
solution
is
getting
installed
to
the
site,
we
activate
a
feature
feature
Framework
feature
and,
as
part
of
that
feature
for
every
feature,
we
execute
this
custom
action
activation,
which
adds
a
cost
user
custom
action
to
the
SP
web,
use
a
custom
action
collection
with
a
specific
ID
and
the
definition
and
the
title
is
being
local
deployment.
So
we
can
actually
see
that
one
in
practice.
So
let
me
actually
go
to
a
power
shop
and,
let's
actually
connect.
Let
me
go
to
that
side.
A
I'm
gonna
take
the
URL
from
here.
I'm
gonna
use
slightly
pump
up
the
font,
so
you
can
more
easily
see
what
I'm
doing
here
so
in
my
case,
I'm
using
commander
also
as
my
PowerShell
tool.
If
you're
wondering
what
is
this,
what
I'm?
Actually
using
it's
just
a
matter
of
a
preference,
you
could
use
PowerShell
console
PowerShell
console
assets
as
well.
What
we
have
is
that
we're
using
the
PMA
power
shop,
so
I'm
gonna
do
connect
BMP.
A
Line
is
Triton
and
let's
actually
use
the
URL
and
paste
the
URL
on
there
in
my
case,
I've
configured
my
credential
manager
with
the
connection
data.
So
it's
not
actually
prompting
me
the
ID
and
password
just
taste,
something
what
can
be
done
with
the
BMV
coercion.
But
now,
if
I
do
a
get
gameplay
custom
action,
we
can
actually
see
the
bar
the
custom
actions
within
the
webcast
side,
and
this
is
the
custom
action
which
was
actually
added
to
the
side,
so
we're
in
the
webcast
side
we're
in
the
webcast
side.
A
Over
there
we
do
get
BMP
custom
action
and
we
can
see
that
there's
a
one
entry
available
within
a
side
so
and
that
entry
was
created
there
when
they
will
be
executed.
That
feature
XML,
which
is
part
of
this
solution.
What's
got
the
install
to
the
side
make
sense
water
right
absolutely.
So,
let's
have
a
look
on
the
second
option.
The
second
option
which
we
talked
about,
was
the
tenant
scope
deployed
extension
and
what
that
means
is
that
the
solution
itself
is
already
deployed
to
my
tenant.
A
So,
let's
have
a
look
on
quickly
the
solution
and
then
figure
out.
How
do
we
get
this
activated
to
the
side?
So
this
is
my
tenant
deploy
solution,
and
this
is
actually
looking
exactly
the
same
as
this
local
scope
solution,
except
that
it's
explicitly
saying
that
I'm
a
tenant
deployed
extension,
so
we
can
actually
see
it
in
the
UI
that
this
is
now
coming
from
the
tenant
deploy
solution.
A
So
this
solution
has
been
already
installed
to
the
tenant.
You
can
see
that
there's
no
feature
xml's
available
and
we
control
the
tenant
scope
deployment
option
in
the
package
solution
Jason.
So
this
one
here
is
saying
skipped
feature
deployment
equals
true,
which
basically
means
that
it's
a
tenant
scope
deployment.
Somebody
might
be
at
this
point
well
that
you
should
be
asking.
Why
did
we
name
that?
That's
reputed
like
that?
And
the
answer
is
well
fair
question.
We
it's
a
mistake
in
the
in
the
spec
planning.
A
It
should
have
been
more
like
a
10
on
scope,
deployment,
true
and
false,
but
it
is
now
skipped
feature
deployment
which
basically
means
the
tenant
scope,
true
or
false,
false
handling.
If
it's
down
scope,
you
do
skip
the
future
deployments,
it
kind
of
makes
sense,
but
anyway
slightly
yeah
confusing
good.
So
it's
skipped
featuring
deployment.
It
was
true,
so
it's
a
tan
scope
which
is
available
within
the
tenant
autumn.
The
solution
is
kind
of
available
or
the
components
in
the
solution
are
available
within
all
of
the
sites
automatically.
A
The
thing
is:
if
it's
a
bit
part
it
will,
it
has
a
webpart
picker.
The
web
part
picker
will
then
should
serve
also
the
web
parts
from
this
kind
of
solution.
Extensions
do
not,
however,
have
an
extension
picker,
because
there's
no
such
thing
as
an
extension
picker
in
the
site
level,
and
it
actually
doesn't
really
make
sense
to
introduce
that
kind
of
functionality.
So
we
need
to
explicitly
go
to
the
site
level
and
somehow
activate
the
extension
to
be
available.
The
easiest
way
to
do
that.
Well,
there's
multiple
ways
of
doing
that.
A
So
we
can
use
racism,
PM
people
at
the
powershell
orifice
racist
files,
they
lie
and
it's
matter
of
a
preference
again.
How
do
you
activate
this
or
pretty
soon,
when
we're
recording
this
video
after
we
record
this
video?
There
will
be
available
sites,
production
which
will
so
you're
able
to
activate
the
extension
in
the
site
level
as
part
of
the
site
design
which
is
getting
applied
to
the
site
or
site
script,
to
be
precise,
but
but
again,
but
how
do
we
get
in
this
case
this
to
be
available?
A
A
We
if
I
remember
correctly,
we
need
to
loop
that
we
need
to
also
provide
a
title,
so
one
can
actually
use
the
same
term.
Taylor
I,
remember
correctly.
The
BMP
PowerShell
just
requires
both
name
in
a
title,
the
dependency
that
this
can
be
used
for
numerous
different
other
purposes
as
well.
The
location
has
to
be
also
set,
so
let's
do
a
location
and
we
need
to
set
the
location
the
same
as
with
this
local
scope.
A
You
can
get
that
entry
from
our
documentation.
That's
one
way
of
doing
that
or
you
can
always
go
back
on
if
you
have
a
which
is
locally
deployed.
So
let
me
actually
activate
that's
one
there.
You
can
actually
see
the
location
in
here
regenerate
this
one
for
you
automatically
if
it's
locally
deployed
option
documentation
of
absolutely
support
as
well
or,
alternatively,
you
can
always
go
to
the
R,
for
example,
a
PowerShell
documentation,
I
think
we
do.
We
have
an
example
on
this
one.
A
We
have
name
title
location,
what's
missing
well
the
ideal
I
inside
component
ID
excellent,
so
the
client
side
component
ID-
and
this
is
basically
saying
they're
selling
telling
them
to
SharePoint
that
well
on
this
site.
When
somebody
is
using
this
site-
let's
also
under
this
client-side
component
ID
as
part
of
the
site
rendering-
and
in
this
case
it
is
a
application-
played
application
customizer
with
the
placeholders
in
use,
so
we
can
actually
send
see
some
changes
in
the
UI.
So
let
me
go
to
the
tenant
deployed
solution.
A
A
B
A
That's
a
fair
point,
so
I
could
have
also
used
first
of
all,
there's
a
client-side
component.
I
already
executed
this,
but
there's
a
client-side
component
properties
option.
So
you're
able
to
parameters
is
this
instance,
so
given
different
parameters,
parameters
and
that
could
change
the
behavior
of
the
extensions.
The
second
thing
is
also
that
there's
a
scope
option
which
basically
supports
a
web
/
site.
There
is
a
default
value
for
this
one,
so
we
don't
actually
explicitly
need
to
do
that
because
to
be
funded
as
well.
A
There
we
go
so
we
execute
a
top-line
added,
a
PMP
Castelo
executed
added
BMP
custom
action,
it
added
a
new
entry.
So
now,
if
we
go
to
the
get
BMP
custom
action,
we
can
actually
see
two
entries
in
here,
so
you
can
see
the
second
entry
which
was
just
at
it
and
the
local
scoped
entry
there
as
well.
Let
me
go
to
the
site:
let's
go
to
the
side,
let's
go
to
the,
for
example,.
A
Let's
go
refresh
and
we
can
actually
see
that
we
have
two
different
extension
whoo-hoo
awesome
of
UI
design.
Isn't
it
so
worth
the
bars?
Yes,
so
in
this
case
more
toolbars,
we
have
hitter
for
Tanaka
scope
extension
and
we
also
have
then
the
header
from
locally
deployed
destination.
So
we
have
two
of
these
headers
one
from
a
locally
activated,
one
with
sustenance,
a
scoped
activator
and
obviously,
if
I
uninstall,
the
local
scoped,
then
only
this
fellow
is
removed,
nothing
rendered
and
all
that,
so
they
are
completely
independent
configurations.
No
such
level
make
sense.
A
Get
the
third
one
well
we're
not
going
to
use
this
particular
tenant
and
have
for
the
first
one.
First
of
all,
the
site
could
start
looking
pretty
horrible
and
the
second
of
all.
Actually,
this
functionality
is
not
yet
rolled
out,
so
this
is
preview
functionality.
The
recording
is
happening
pretty
soon
after
the
build
announcement,
so
we're
gonna
use
the
same
tenant
as
we
used
within
the
bill,
so
this
is
still
in
test
environment
or
test
tenant
which
we're
gonna
use
for
showing
this
on
now.
A
How
we
do
this
is
that
in
the
ant
catalog
as
part
of
the
new
functionalities,
new
announcements
in
the
app
catalog
site
ad,
so
let
me
show
you
that
this
is
after
the
website.
This
is
an
app
catalog
site
where
we
have
certain
add-ins
already
installed
on
the
tenant
level.
So
in
this
site
we
actually
add
a
new
list.
In
this
case,
it's
not
yet
visible
in
the
site
contents.
It
will
be
visible
inside
condoms.
We
just
decided
actually
to
one
business
day
ago.
That
we'll
add
it
inside
contents.
A
So
you
can
easily
access
the
the
list
and
you,
as
an
administrator,
you
can
actually
configure
this
manual
as
well.
Now
we
will
support
adding
this
entry
here
automatically
as
well,
directly
from
the
SP
pkg,
1
and
potentially
at
some
point,
we
might
have
a
central
admin
UI
for
configuring.
These
options
in
a
more
let's
say,
ain't
user-friendly
way
as
well,
but
the
basic
functionality.
What
we're
saying
here
is
that
you
have
a
list
we're
able
to
configure
what
is
the
component
ID?
What
are
the
properties
for
that
instance?
A
Let
me
actually
had
to
click
the
new
item,
so
I
can
actually
show
this
one
in
practice
the
option.
So
we
basically
say
what
is
the
component
ID?
Basically,
what
is
the
manifest
ID,
which
is
getting
rendered
we're
able
to
parameter
size
that
the
instance
if
needed,
are
able
to
filter
this
extension
to
be
only
activated
in
certain
with
templates
and
what's
important
here?
A
Is
that
it's
not
just
the
the
modern
group
associated
team
side
and
a
communication
side,
it's
around
experience,
so
it
could
be
also
a
classic
team
side,
but
in
the
modern
experience
and
stuff
is
getting
rendered
properly
or
we
are
able
to
filter
based
on
a
list
template.
So
this
is
for
list
view
but
or
a
list
view
common
sets.
A
In
our
case
it
was
the
application
customizer,
a
location
which
we
added
on
the
on
the
previous
setups
as
well,
and
then
the
sequence
means
that
if
you
have
multiple
extensions,
what
is
the
order
of
those
extensions
getting
rendered,
so
the
sequence
could
be
1,
2,
3,
4,
5
or
it
could
be
100,
200,
300
and
and
so
on,
so
you're
able
to
define.
What's
the
order
of
the
extensions
in
my
case,
what
I
did
here?
I
actually
have
an
entry
already
available
here,
but
the
location
for
now
is
wrong.
A
So
the
location
is
something
which
we
don't
support,
so
let's
go
to
a
site
and
we
can
see
the
site
without
the
extension
I'm
gonna
go
to
a
normal
group
associated
team
site.
There's
no
extensions
in
this
team
site.
No,
nothing!
So
nothing
special
as
such!
So
nothing
fancy
getting
rendered
at
this
point.
So,
let's
actually
go
to
tenant
wide
extensions
and
I
want
to
modify
this
existing
entry.
A
I'm
gonna
make
sure
that
my
location
entry
is
correct,
so
it's
going
to
SATA
station
dot,
application
customizer
and
stop
editing
the
list
and
what
this
now
basically
meant
that
in
all
of
my
sites
in
the
modern
experience
is
in
my
tenant,
we
will
include
this
extension
to
be
rendered
with
the
component
ID
of
this
one.
So
I
need
to
have
a
SP
pkg
fellow
solution
in
my
app
catalog
matching
discoverable
with
a
component
mat
in
this
component
ID
and
with
these
particular
configurations.
A
So
these
are
solution,
specific
configurations,
in
our
case
we're
using
this
for
defining
what
is
the
term
store
and
browse
a
user
profile
property
which
this
extension
will
use
and
how's
the
user
interface?
So
let's
go
to
the
site,
lets
us
the
group
or
request
the
slide
again
we're
able
to
say
that
immediately
when
I
add
it
at
the
entry
to
the
site,
our
extension
is
getting
rendered
in
this
side
as
well.
So
in
this
case
the
site
there
we
go
and
let's
actually
do
a
control,
f5,
so
really
making
sure
it's.
A
B
A
I
did
settings
are
fine.
Everything
is
fine.
That's
fine!
That's
fine!
As
well!
Let's
get
in
here,
let's
actually
open
up
this
one
or
maybe
we
potentially
need
to
cut
a
section
from
the
webcast
recording.
Here
we
go
now
it
actually
renders
proble.
So
I
went
to
a
communication
site.
If
I
go
to
group
side,
it's
probably
it's
now
Ryan
properly.
That
was
a
small
delay.
Oh
it's!
It
is
actually
delay
on
carrying
the
javascript
file
served
there
we
go
so
the
extension
is
now
getting
rendered.
A
If
I
scroll
down,
you
are
able
to
see
this
extension
footer
here
with
the
saying
conducts
legal
policies
and
tools-
and
this
is
a
set
of
links
which
are
getting
controlled
by
the
the
tenant
administrator
or
the
tenant
person.
So
somebody
is
able
to
introduce,
let's
say,
static,
set
of
links
for
all
of
the
end.
Users
within
this
tunnel
make
sense
what
a
typical
actually
scenario
what
customers
want
to
have,
but
then
this
actually
has
this
edit.
My
links
focus
on
functionality
as
well.
A
A
Give
once
you
try
good
try,
doesn't
matter,
we
kind
of
use,
WWE
SharePoint
con,
it's
probably
registered
by
and
of
course,
how
am
I
s?
Game
am
SSB
PMP
shipment
community
pages.
How
did
I
miss
that
fun?
Okay,
three
are
links
which
are
configured
by
me
as
a
personalized
links
and
I'm
gonna
save
this
and
you
can
see
a
nice
screen
message
saying:
link
successful
is
saved
and
what's
I
have
a
new
selection
of
column
available
or
a
menu
available.
A
A
Right,
cool
and
really
maybe
a
one
thing
to
note
on
here
if
I
want
I,
can
absolutely
go
and
modify
and
add
multiple
instances
of
the
same
extension
or
remove
this
extension
and
the
changes
are
immediate.
So
this
is
not
like
something
is
then
scanning
through
all
of
the
sites,
one
by
one
and
activating
this
one
in
there?
No,
no,
it
is
a
runtime
activation.
A
A
Move
back
on
slides
and
do
a
quick
summary
and
close
up
the
webcast
excellent.
So
that's
it
so
quite
actually
big
demo
covering
all
of
those
three
options,
and
hopefully
we
were
able
to
follow
up
on
the
advantages
and
disadvantages
of
all
of
the
options,
but
basically,
now
that
we
have
to
build
2018,
we
introduced
the
COBOL
activation
option.
It
might
be
already
available
for
you
might
not
slightly
depending
on
when
the
when
you're
watching
the
video.
A
Now
it's
gonna
be
available
in
summer,
2018
timeframe,
roughly
so
no
exact
dates,
but
we
will
definitely
announce
that
properly.
But
having
these
three
options
available,
you
can
now
target
your
extension
to
be
easily
available
based
on
your
business
requirements
and
that's
really
the
key
here,
and
it
also
provides
flexibility
for
administrators.
So
we're
able
to
decide
how
and
when
these
extensions
are
available
well
or
developers
or
architects.
Whatever
is
the
role
within
your
company
making
that
decision
anything
I
want
to
add
here,
wallet.
B
I
would
actually
underline
what
you
say
is
that
it
gives
you
an
hour
option
and
it's
important
for
you
to
understand
that
these
options
are
there
when
to
use
which
one,
what
are
the,
what
will
be
the
consequence
of
using
each
option
and
to
incorporate
that
in
in
the
process
of
designing
your
intranet?
If
I,
just
just
the
fact
that
that
the
options
are
there
doesn't
mean
that
each
option
applies
to
each
case
right.
A
Absolutely
absolutely
and
typical:
quite
often,
people
come
and
ask
around
okay
so
but
which
of
these
options?
These
three
options
is
the
best
option
and
the
answer
is
well
all
of
them.
It
really
depends
on
your
business
scenario
for
all
of
them.
They
have
a
specific
use
case.
It
really
depends
on.
How
do
you
want
your
stuff
to
get
deployed
and
well?
How
are
you
planning
your
solution
to
get
the
point?
A
So
there's
no
there's
there's
no
black
and
white
statement,
which
of
them
is
the
best,
because
there's
no
such
thing
as
best
because
best
for
one
thing
isn't
the
best.
For
another
thing,
it's
makes
a
lot
of
sense.
Cool
I!
Think
that's
it
for
this
one.
So
thank
you
for
watching.
Thank
you,
Baldy
for
joining
and
asking
the
any
quotes
hard
question.
You
need
to
actually
pay
attention
on
asking
hard
questions.
What
like
ok,.