►
Description
Leverage your existing bot investments (code) and expose functionality in Viva. In this 7-minute developer focused demo, Luca Bandinelli enables you to teach your bot how to speak Viva! Learn about Bot powered ACEs, implementation details, packaging and distribution. No Coding, self-contained bot deployed to SharePoint via a package. Step through code, manifest, create package, upload to app catalog, go to dashboard, add card. Talk about authentication and updating, Capability goes to Public Preview this week.
This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on June 6, 2023.
Demo Presenter
• Luca Bandinelli (Microsoft)
Supporting materials
• Article - Announcing SharePoint Framework 1.17 with updates for Microsoft Teams, Microsoft Viva and SharePoint
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms/community/home
A
A
Aces,
basically,
what
we
did
here,
we
wanted
to
be
able
to
create
an
opportunity
for
people
that
already
invested
in
Bots
for
Microsoft
teams.
Let's
say
that
heavily
invested
in
about
framework
to
be
able
to
reuse
existing
Investments
and
without
having
to
switch
and
learn
new
technologies,
because
maybe
they
built
their
Bots
using
c-sharp
or
other
kind
of
a
non-web-based
texts.
How
do
they
basically
use
the
same
kind
of
investment
and
participate
to
deliver
connections?
A
So
today,
if
you
have
something
like
that,
what
you
have
to
do,
you
have
to
build
your
AC
using
SharePoint
framework
and
then
create
some
sort
of
deep
linking
to
your
existing
bot
about
power.
Aces,
give
you
the
ability
to
avoid
that,
and
simply
for
lack
of
better
words,
teach
your
Bot
how
to
speak
Viva.
So
what
we
did
was
we
worked
with
about
framework
team
and
we
created
new
kind
of
actions
that
are
part
of
the
bot
framework
that
are
specifically
for
Viva.
So
now
your
Bot
can
basically
listen
to
these
actions.
A
The
dashboard
and
the
card
will
send
these
actions
to
the
bot
and
the
bot
can
respond
back
using
a
declarative
Applause
for
the
card
view
or
by
setting
the
properties
that
you
want
to
show
in
the
card
view
the
card
size,
the
template,
etc,
etc,
and
for
the
quick
view,
sending
the
whole
Json
adaptive
card
Json
for
showing
the
quick
view.
That
also
means
that,
from
the
SharePoint
framework
standpoint,
there
is
no
client
code
needed
actually,
as
a
matter
of
fact,
there
is
no
client
code
at
all.
A
It's
not
that
you
don't
need,
but
you
you
may
want
to
add
it
now.
You
can't
everything
is
in
the
bot
itself.
The
only
thing
that
you
have
to
deploy
in
SharePoint
is
a
package
that
is
basically
telling
SharePoint
that
there
is
a
new
type
of
card
that
to
see
the
surface
in
the
car
picker.
So
with
that
said,
let
me
reduce
this.
A
Let
me
open
My,
Demo
Box,
so
here
I
have
a
bot
that
has
been
built
using
node.js
I'm
using
ngrok
to
expose
my
bot
in
the
in
the
internet
and,
as
you
can
see,
everything
here
is
in
the
in
the
bot
itself
to
register
my
bot.
I
have
an
app
package
and
inside
the
app
package,
I
have
a
similar
to
the
team's
schema
manifest
that
has
some
kind
of
a
additional
information
for
the
bot
itself,
but
other
than
that
we
are
going
to.
A
A
Let
me
close
this
and
refresh
and
I
go
to
my
app
catalog
I
deploy
the
app
the
the
the
package
in
the
app
catalog.
This
is
my
both
basically
they
are
deployed.
It
looks
a
little
bit
different
because
it
looks
it
understands
that
it's
not
an
stfx
kind
of
component
and
then,
when
I
go
to
my
dashboard
I,
basically
refresh
I
can
edit
I
can
add
my
card,
and
basically
this
is
the
card
itself.
A
Here
is,
and
this
is
Macbeth.
This
is
my
card.
I
can
see
in
the
in
the
debugger
that
I
got
a
call
and
then,
for
example,
if
we
want
to
take
a
look
a
little
bit
on
how
it
works
and
I'll
be
Zoom
it
before
Wes
is
asking
so
basically
there's
a
there
is
a.
There
is
a
bunch
of
properties
that
we
have
in
order
to
be
able
to
intercept
the
messages
that
we
get
from
the
from
the
dashboard
itself.
A
We
have
something
called
just
like
get
quickview
sync:
we
have
get
Curve
Your
sync,
we
have
get
property
pane,
we
have
set
property
paying
and
when
you
get
these
messages,
you
can
basically
react
to
this
information.
So,
for
example,
with
the
get
quick
video
Sync
here,
I'm
able
to
set
up
and
create
multiple
views,
because
as
it
we
are
supporting
exactly
the
same
functionality
that
you
will
support
in
an
ace,
so
one
of
those
being
having
the
ability
to
have
multiple
views,
for
example.
A
So
if
I
could
create
quick
views
here,
so
right
now,
I
have
this
quick
view
in
the
basic
card
view
that
when
I
click
that
it
gives
me
this
title,
so
I
can
go
back
here
and
I
can
go
to
the
basic
view.
I
can
click
on
the
quick
view.
This
is
my
quick
view.
Then
I
can
simply
go
to
my
bot.
I
can
go
back
here
and
I
can
say
hello.
Community
I
can
save,
I
can
stop
and
restart.
A
It
is
and
then
I
click
on
the
basic
View,
and
here
it
is.
If
everything
changes
now
I
have
to
do.
I
add
I
have
to
do
no
changes,
because
there
is
no
publishing
in
the
package.
There
is
no
client-side
code.
Everything
is
server
side.
One
of
the
cool
features
that
we
have
enabled
for
the
bot
Drive
driven
Asus
is
the
ability
to
support
third-party
LEDs.
A
So,
for
example,
if
you
want
to
log
in
by
using
a
different
IDP
that
is
not
Azure
thing
directory
Google
OCTA,
You,
Name,
It,
We
Are,
we
have
hooked
to
the
same
flow
that
you
have
for
kingsbots
to
be
able
to
have
kind
of
a
magic
code
or
token
based
out
that
you
will
be
able
to
provide
in
order
to
be
able
to
authenticate
and
use
the
bot,
and
it's
completely
inside
the
framework
you
don't
have
to
create.
Any
dialogues
in
the
framework
takes
care
of
that.
A
For
you,
we
are
currently
private
preview,
but
we
are
launching
a
public
preview
this
week
so
expect
a
message
from
beza
or
anyone
else
from
us
to
the
community
and
to
the
internet.
When
public
preview
will
be
available,
we
know
that
there
are
some
features
that
are
not
still
yet
so
one
of
the
and
one
of
the
reasons
why
we're
doing
public
preview
is
because
we
want
to
get
as
much
feedback
as
possible.
A
One
example,
one
of
the
things
that
we
are
still
coding
is
the
ability
to
send
back
and
forward
to
all
of
this
code
the
information
that
you
may
have
set
in
the
property
bag,
so
that
you
can
at
any
given
time.
You
can
understand
that
for
that
specific
card
instance,
if
you
had
some
custom
properties,
which
kind
of
custom
properties
the
operator
set
and
reading
those
kind
of
information
on
any
basically
call,
that's
all
everything
that
I
have
excellent.
Thank
you.
Lokan
foreign.