►
From YouTube: Magento MSI Open Demo. June 14, 2019
Description
Agenda:
• General Updates. Finalized strategy for B2B and Commerce Edition support
• Simplified Pickup Location mapping and Store Pickup interfaces updates
• Inventory Transfer extension demo by Magestore
• MSI Quality Report and Automation status
A
Great
welcome
guys
to
this
week's
MSI
demo.
Today
we
don't
have
too
much
items
on
the
agenda,
but
they
are
all
interesting
and
let
me
jump
in
into
the
first
one
straight
away,
though
this
week
was
really
focused
on
the
quality
and
by
the
quality
I
mean
we
haven't,
really
increased
our
automated
test
coverage.
As
you
can
see,
we
have
a
lot
of
functional
testers,
which
some
of
them
cover
multiple
scenarios.
Some
of
them
follow
just
one,
but
still
a
good
increase,
and
we
also
have
the
lots
of
tests
pull
request
pending.
A
Need
additional
modules
to
work
as
an
aside
correctly,
so
the
question
was:
where
should
we
build
those
modules
and
are
we
able
to
create
dependencies
from
B
to
B
and
from
Enterprise
Edition
onto
the
MSI?
The
the
decision
ended
up
being
that
we
are
indeed
able
to
put
those
connector
modules
into
enterprise
and
b2b,
and
that's
pretty
much
mean
reasoning,
is
that
b2b
and
II
still
depend
on
Community
Edition,
which
is
already
packaged
together
with
MSI
the
we
pretty
much
had
that
dependency
all
the
time,
but
it
was
not
not
so
explicitly.
A
C
A
A
Luckily,
we
already
have
some
cool
requests
going
on,
one
of
which
is
support
of
a
Messiaen
which
be
an
adventure.
Coach
Ricardo
was
so
fine
to
provide
us
with
this
code,
and
we
already
previously
have
done
preparation
work
on
this
in
the
enterprise,
so
the
Willetts
left
is
just
to
get
it
merged
test
and
we'll
be
done.
A
So
this
is
something
coming
really
soon
and
at
this
point,
I
think
it's
it's
all
of
the
really
major
updates
for
this
week,
though
now
I'll
be
passing
the
words
over
to
Alexander,
who
has
been
really
working
hard
on
the
topical
this
time.
We'll
have
some
updates
on
the
api's
on
how
those
eight
guys
were
simplified
and
how
we
are
going
to
develop
them
in
future.
So
Thunder,
please.
D
D
Okay,
so
this
week
we
processed
with
poor
request,
which
was
related
to
a
refactoring
of
API
implementation
in
store
pickup
directly.
It
was
related
to
and
pour
into
each
dedicated
to
provide
lists
of
a
nearest
pickup
location.
To
do
the
requested
address
the
idea
that
this
point
this
end
point
become
his
to
complex
and
requires
too
many
arguments
to
be
passed,
and
we
decided
to
switch
it
to
the
search
criteria
which
will
provide
possibility
to
compact
our
required.
D
It's
not
required
arguments
in
one,
a
simple
object
and
in
the
result,
this
poor
request
was
merged,
and
now
we
have
possibility
not
only
specify
address,
and
we
have
also
a
possibility
to
add
pagination
for
the
search
of
new
respect
application.
Probably
we
have
a
possibility
to
change
sort
order
of
a
result
which
will
be
returned
and
add
some
filters
and
afters
it.
D
After
that,
we
decided
that
this
is
something
which
which
we
don't
want
to
have
in
this
endpoint,
and
it
leads
to
the
new
issue
where
we
will
decrease
the
number
of
functionality
which
can
be
done
with
this
endpoint.
So
the
only
it
will
be
available
is
to
search
near
a
spec
application
and
pagination
for
this
endpoint.
D
This
is
what
we
going
to
finish
next
week
and
also
there
are
two
pull
requests
which
were
done
during
this
week's
last
week's.
This
one
is
related
to
shipping.
Pricing
was
currently
we
implemented
functionality
that
provides
a
fixed
price
for
for
in-store
pickup
delivery.
This
price
is
manageable
from
the
admin
panel,
as
for
fair
trade,
for
example,
and
this
per
request,
when
it
will
be
finished,
will
provide
possibility
for
third
party
developers
and
guys
who
build
extensions
to
extend
this
functionality
and
add
their
custom
rules.
D
Also,
it
will
provide
ability
to
specify
in-store,
pickup
delivery
in
sales
rules,
because
for
now
this
price
is
fixed
and
cannot
be
changed,
except
that
from
admin
settings
and
the
last
one.
The
big
pull
request,
which
is
still
in
progress,
is
continuous
implementation
of
in-store
pickup.
It's
for
coverage,
checkout,
magenta
checkout,
and
provide
possibility
to
place
a
full
order
cycle
with
using
and
store
pickup
delivery
method,
but
for
now
only
with
Magento
API.
D
A
This
is
really
interesting
and
usually
on
a
side
note
having
web
api's
is
really
important
parts
of
the
don't
pick
up
for
us,
because
we'll
know
that
checkout
is
built
on
top
of
the
image
enters
REST
API
sand,
maybe
will
be
migrated
into
a
graphical
future.
But
that's
a
separate
topic
and
well
actually
enablement
of
that
way
by
API
is
already
major
step
which
would
just
leave
the
UI
work
to
to
complete
before
before.
We
can
actually
show
the
each
and
every
scenario.
A
Yeah,
thank
you
very
much
yeah
and
now
we
have
one
more
unexpected
change
in
the
agenda
and
I'm
happy
to
introduce
Alex,
who
can
demonstrate
some
of
maesters
extension
and
how
it
integrates
with
msi,
because
we
always
welcome
additional
use
cases,
information
how
people
with
Optimus
are
in
their
projects.
So
Alex,
please
take
the
stage
the
world
is
yours.
C
C
C
C
In
the
case,
you
just
want
to
send
some
a
few
up
for
us
to
another
sauce.
You
can
use
the
feature
and
you
can
also
upload
seed
v5
in
case
you
want
to
send
many
items
to
another
sauce
and
we
also
provide.
Is
it
hamlet
of
Silvia
file?
You
can
download
and
just
added
more
SKU,
and,
as
is
the
quantity
you
want
to
chain
for.
C
B
B
B
C
C
B
C
C
C
C
C
C
A
C
C
C
D
A
C
And
we
can
share
some
insight
on
this,
because
many
of
our
customer
requests
this
feature
too.
You
know
MSI
I,
think
MSI
provide
very
bad
architecture
for
eventually
mixed
in,
but
I
think
it's
like
some
feature
for
the
merchants
too
many.
They
eventually
like
stop
a
lot
and
Chandler
stop
was
stop
taking
and
many
of
customer
requests.
This
feature
is
a
reason
why
we
provide
a
feature
to
our
customer
and
I
hope.
That's
an
area
we
can
go
and
contribute
this
feature
to
MSI
we're
very
happy
to
do
this.
A
C
C
C
A
E
Okay,
all
right,
so
our
regularly
scheduled
quality
report,
a
couple
of
things
to
highlight
this
week,
I'm
sorry
almost
last
week
change
a
metric.
So
every
done
this
a
little
so
so
what
we're
looking
at
here
is
the
focus
point.
Is
this
gray
line
for
automation?
We
have
tracked
up
for
those
of
you
who
missed
a
couple
of
weeks
back
the
numbers
in
blue
and
orange,
which
is
total
and
manual
not
yet
automated
tests
have
tracked
down
just
because
we're
doing
better
reporting
and
recording.
E
So
that's
a
reflection
that
we're
consolidating
test
tracking
things,
property
is
FFT,
F
or
manual
only
or
Web,
API
or
integration,
and
we'll
see
the
use
of
that
as
we
start
tracking,
where
the
API
specific
stuff
later
in
the
presentation.
But
right
now
we
have
a
155
165
increase
between
reports
in
the
gray
line.
The
automation,
as
you
can
see,
with
our
slowly
climbing
line
over
the
last
month,
and
that
is
our
biggest
single
increase.
E
Okay,
severity,
unless
you're
very
familiar
with
you
wouldn't
see,
we
have
changed
severity
very
little,
but
in
component
we've
actually
the
catalog
number
has
come
up
slightly
faster
than
the
seals
number
that
reflects
that
there's
been
good
catalog
coverage.
Seals
pretty
well
covers
days,
but
not
animation.
Catalog
is
getting
better
coverage.
E
That's
let's
come
up
and
with
that
additional
automation
coverage
in
the
last
week
or
two
weeks
in
terms
of
our
manual
testing
that
so
our
component
again
basically
reflects
our
split
there's
a
higher
focus
on
seals
with
a
manual
testing
right
now,
but
what
we
have
been
doing
is
where
they
pay
regression
testing.
Since
we
reported
a
full
pass
in
our
smaller
regression
cycle
about
three
weeks
ago,
there's
also
been
a
way
of
APA
regression
cycle.
That
is
a
full
pass.
So
bed
green
circle
love
to
see
it,
but
what's
happening.
E
On
top
of
that
is
now
that
we've
split
up
tests
and
more
clearly
identified
what
is
functional
front
dance
of
MFT
f
specific.
What
is
very,
much
a
kiss
from
manual
things
with
you
know:
user
input
set
up,
cron
jobs,
anything
like
that
needs
to
run
that
we
want
to
keep
manual.
We
track
that,
but
we're
also
heavily
tracking.
E
What's
a
good
use
case
for
not
only
Web
API
testing,
so
there's
manual
number
this
coverage
that
we've
done
manually,
but
also
what
we
can
put
into
Web
API
testing
and
get
that
automated
and
kicked
in
our
builds
and
PRS
and
everything
and
there
are
PRS
for
that
out
right
now.
So
all
we
haven't,
you
know
driven
that
number
up
this
week,
that
is
in
the
pipeline.
We're
going
to
see
that
coming
and
that's
going
to
give
us
great
an
API
as
well
as
functional
test
coverage
going
forward
and
I.
E
Don't
know
Eugene
the
next
week,
we'll
be
communicating
with
those
PRS
and
making
sure
they
get
in
and
that
we
can
drive
that
number
up
next
week
as
you'll
see
on
the
graph
that
isn't
specifically
tracked
as
that
becomes
a
focus.
We
might
stick
a
line
on
there
to
splode
ID
MFT
F
automation,
where
the
API
automation,
so
we
can
see
higher.