►
From YouTube: Magento MSI Open Demo. July 12, 2019
Description
Agenda:
• Placing Store Pickup order from the Admin panel
• Overview of current Store Pickup APIs state and module structure
• WebAPI for Store Pickup already capable of placing an order
• Upcoming performance improvements for default stock/source combination
• Weekly Quality report @Tom Erskine
A
Already
renamed
the
repository
in
starting
to
phase
out
the
name
which
supposes
that
it's
some
kind
of
a
different
component,
though
today's
main
focus
would
be
stopping
up
as
the
most
active
track
lately,
but
also
we'll
be
sharing.
Some
updates
on
performance
and
testing
and
those
are
all
so
exciting.
I
really
hope
that
we'll
be
able
to
release
those
soon
but
later
on
about
that.
So
I'd
like
to
start
with
inviting
Alexandra
to
talk
about
current
state
of
the
topic
of
AP
ice
and
the
current
state
of
module
relationships.
C
So
as
as
you
can
see
here,
we
have
some
general
models
which
already
implemented
like
about
core
functionality,
inventor
in
store,
pickup,
API
and
its
implementation,
and
also
we
decided
that,
according
to
the
bright
magenta
future
in
case
of
service
iterations,
that
it
will
be
nice
to
have
separated
components
for
a
separated
application,
application
areas
and
we
decided
to
move
all
operations
which
related
to
sales
adjustments
in
two
separated
modules.
It's
in
this
isn't
done
yet,
but
it's
plans
for
future,
and
in
generally
is
our
in-store
pickup.
C
C
Okay.
So,
let's
start
from
the
setup.
First
of
all,
I
have
Magento
with
two
websites
and
with
two
stories
to
write
it
to
his
two
websites:
I
have
of
sources.
There
are
different
sources
and
I
have
postman
with
predefined.
It
queries
which
I
will
just
going
to
send
to
the
magenta
and
first
I
will
start
from
the
showing
how
it
works
with
guest
card,
so
I'm
sending
requests
for
art
creation
and
I
receive
masked,
quote
ID
and
then
I
have
the
second
second
request.
C
This
request
is
serrated
to
add
a
simple
product
to
my
cart
and
I
just
place.
My
quote
ad
in
the
request.
I
found
it
here
we
go
now
I'm
going
to
set
shipping
information.
There
is
some
general
shipping
address
with
mentioned
pickup
location
code
and
selected
in-store,
pickup
and
delivery
method,
I
place
the
cart
ID
into
the
request
and
send
it
yeah.
So
shipping
information
was
set
and
I
receive
the
response
with
totals
and
available
payment
methods
to
continue
with
payment
information.
C
C
And
here
we
have
friends
in
province
and
city
city
street
street
postcode
postcode,
and
here
we
have
the
same
information.
Also
you
cannot
see
in
the
button
edit
as
a
kind
of
generality,
but
still
looks
like
working
order
form.
It
was
form
guest,
I,
have
created
customer
or
to
show
how
it
works
with
the
customer
not
only
focused
here,
you
have
some
customer
and
I
have
like
almost
the
same
address
which
I
used
for
guests,
but
little
bit
differ,
but
it's
this
address
is
already
saved
as
default.
Shipping
and
a
billing
address
for
the
customer.
C
It's
the
first
name,
last
name
telephone
number
country
used
for
validation
and
also
I
used
customer
address
ID,
so
magenta
will
see
in
this
field
and
will
try
to
cook
customer
address
to
place
it
to
the
order,
if
there's
something
wrong,
but
we
expect
that
our
gist
will
be
taken
from
the
pickup
location
which
mentioned
in
in
this
extension,
attribute
Oh,
40
sticks
and
then
send
request:
okay,
edit
and
now
I'm
sending
information
about
payment.
It's
just
check
money
order,
okay
and
now
I'm
placing
the
order.
C
Yeah
I,
don't
know
what
what
went
wrong,
but
it
probably
it
will
be
nice
case
to
recheck
it.
So
order
has
been
placed
and
it's
ad
31
I
will
just
change
it
in
the
address
in
the
yeah
URL,
and
here
we
can
see
the
almost
the
same
order.
It's
in
store,
pickup
shipping
method,
urges
and
remembers
the
same
as
previous
one
previous
one
order
and
yeah
probably
works,
but
as
they
can
see,
there's
some
back
buck
which
he
needs
to
be
investigated.
A
C
Yeah,
we
will
try
to
separate
the
sales
with
models
which
related
to
the
sales
in
case,
if
customer
or
just
merchant,
whatever
I
would
like
to
have,
for
example,
different
installations
for
Magento,
which
one
of
them
will
be
used
for
just
a
storefront
for
catalog
check
out
and
cart,
and
the
second
one.
If
will
it
will
be
used
for
admin
panel
and
all
how
to
call
it.
The
begins
operations
so
which
quite
security
and
the
sales
extension
will
be
required
for
their
back-end
installation
and
for
from
ghent,
magenta
I
think
it
will
be
instant
store.
C
A
Thank
you
very
much.
That's
pretty
much
covers
what
we
are
looking
to
do,
I'm,
pretty
sure
that
if
we
succeed
it
would
be
pretty
much.
The
first
implementation
like
Magento
is
implementation
with
the
services
relation
designed
in
mind
and
we're
looking
forward
to
it.
Maybe
anyone
has
some
questions
regarding
the
Web
API
or
the
placement
flow.
A
It
looks
like
looks
like
it
was
all
pretty
clear,
so
thank
you
very
much
of
a
Sondra
now
I'd
like
to
invite
Maxine,
who
is
one
of
my
favorite
speakers,
because
he
is
always
so
serious
and
Maxine
will
be
continuing
the
same
topic.
You
demonstrate
how
we
can
already
place
a
topic
of
order
with
the
admin
UI.
D
D
D
D
Is
great
and
a
my
feature
I
implemented
too,
is,
if
you
pay
attention
to
their
to
this
line,
you
can
see
that
the
first
part
is
the
shipping
method
name
and
the
second
one
is
the
name
of
the
application
which
was
used
so
I
believe
that
Ted
bean
will
be
able
to
understand
to
which
the
complication
was
used
for
the
order
just
me
be
able
to
step
back.
Okay
left,
oh
I,
believe,
probably
how
one
have
any
question
feel
free
to
I.
D
A
A
Okay,
so
I
guess
this
is
pretty
much
it
for
this
topic
of
updates
and
now
I
want
to
proceed
to
some
performance
improvement.
Work
done
specifically
specifically
step
on,
has
implemented
to
one
of
the
pull
requests
which
is
aimed
at
at
improving
performance.
In
the
scenario
when
magenta
drawn
in
a
single
sock
mode
with
the
default
source
and
default
sock.
Actually
we
had
the
series
of
to
pull
request.
One
was
implemented
based
upon
other
one
I
think
I
was
working
on
it
and
I'm,
not
sure
it's
upon
you.
A
E
E
E
E
A
B
A
You
said
so,
this
was
not
only
the
single
place,
the
price
injector,
which
were
identified
to
be
prone
of
doing
the
encoding
from
incorrect
tables
from
the
view.
So
there
is
one
more
request.
Actually
I
think
it
was
me
who
was
working
on
it
and
basically
what
happens
here.
It's
pretty
much
the
same
same.
What
Suppan
did.
B
A
A
We
get
a
really
significant
improvement,
so
catalog
product
scenario
that
decreased
dramatically
like
five
or
ten
times
and
what
even
sure
and
the
lot
of
scenarios
also
dropped
in
execution
time.
This
is
pretty
much
a
good
sign
of
the
performance
improvement.
We
are
getting
from
these
pull
requests
and
currently
we
are
working
with
the
performance
team
to
figure
out
the
methodology
and
to
make
sure
that
these
results
are
valid
and
may
be
really
maybe
included
in
the
release.
But
this
is
pretty
good
improvement
and
I
think
this
is.
A
A
A
A
B
B
Okay,
hopefully,
you've
got
my
screen
there,
so
this
is
weekly
quality
report,
which
I
think
it's
been
with
the
shutdown
everything
about
two
or
three
weeks
since
I've.
Had
this
so
headline
items
in
quality
then,
is
increasing
automation,
which
is
great
to
see
and
previous
two
weeks,
MF
TF
test
case
has
come
up
by
19.
You'll
see
this
in
the
graph.
That's
a
very
large
and
the
largest
two-week
increase
we've
had
this
year,
and
so
it's
really
good
to
see
those
numbers
come
up.
B
What
that
really
means
is
we're
looking
at
test
cases
for
one
one
to
release
being
all
automated
and
which
is
great
and
one
one
o
is
at
90%.
So
our
more
recent
releases
have
a
lot
of
great
covered
unit.
That's
work,
that's
being
done
to
bring
that
up,
which
is
good
to
see.
We
can
see
with
our
continuing
ability
to
refine
our
test
case
definitions.
B
So
we're
not
only
increasing
our
raw
number
of
automation,
but
also
having
a
much
clearer
picture
of
what
our
automation
scope
is
and
where
we
are
tracking
against
that.
So
that's
fantastic
to
see
and
that's
really
the
headlines
in
quality
we'll
go
down
through
our
normal
breakdown,
so
severity
we
are
pushing
as
zeros
that's
increased
by
a
couple
of
percentage
points
and
over
the
last
few
months,
so
focus
on
our
zeros
as
you'd
expect
component
again,
as
you'd
expect,
primarily
in
seagulls
and
cat
log.
B
Web
API
then,
should
be
stripped
out
of
this
it's
at
zero
and
and
will
be
fully
within
zone
Web,
API
testing
and
out
of
this
n
FTF
automation,
scope
entirely
and
mind.
You're
testing
no
update.
This
is
from
our
last
run.
We
haven't
done
a
manual
bun,
but
it's
good
that
we're
focusing
on
our
automation
right
now.
So
just
a
brief
one
there
for
now
take
questions.
Otherwise,
that's
alright.
Our
Fuji.