►
From YouTube: Magento MSI Open Demo. May 10, 2019
Description
Agenda:
• 1.1.2-beta Released. Documentation and installation. Quick recap of the release scope.
• Reservations CLI in 1.1.2 recap
• Stock Export in 1.1.2
• SSA Performance improvements
• How pair programming turned into quadruple programming
• Store Pickup updates
• Shipping method for Store Pickup
• SSA adaptation for Store Pickup
• Completing Store Pickup orders on non-default sources
• Quality Updates and 1.1.2 Regression Testing status updates
B
A
A
few
nice
features
included
anyway.
The
one
of
the
the
nice
one
is
partial
stock
transfer,
API,
which
is
which
is
designed
to
transfer
not
all
of
the
inventory
from
source
to
source,
but
just
selected
items.
So
then
we
have
reservation
CLI,
which
was
implemented
by
actually
two
teams,
because
mage
specialists
started
working
in
it,
but
then
what
him
took
over-
and
it's
done
quite
a
lot
of
work
on
that
front
as
well.
A
Performance
related
improvements
for
source
selection,
algorithms
and
the
next
big
one
is
a
graph
QL
support.
Tom
your
improvements
and
really
big
feature.
The
expert
stock
service
which
was
developed
by
Stefan,
and
it
allows
to
experts,
talks
to,
for
example,
to
third-party
sales
channels,
though
some
of
them
will
have
a
quick
recap
today,
just
just
to
make
sure
everybody
are
on
the
same
page.
A
It's
just
requiring
a
new
version
which
is
public
currently
published,
is
1
1
2
beta
2
for
those
who
are
using
2,
3
1
Magento.
Unfortunately,
it's
locked
to
the
1
1
1
version
of
MSI,
but
you
still
can
use
an
inline
alias
to
install
it
and
opened
as
we
see.
Currently
it's
pretty
much
compatible.
So
we
don't
expect
any
major
issues
with
both
2
3
0
and
2
3
1.
The
upcoming
2
3
2
release
would
include
the
new
MSI
version
and
would
be
fully
supported.
That
combination.
A
You
may
find
additional
documentation
on
the
MSI
slack
channel
and
I
think
it
was
also
to
eat
it
by
lorry,
but
we
have
quite
a
lot
of
dogs
regulated
to
be
release
specifically
and
to
and
to
the
api's,
which
already
exists
or
or
introduced
in
the
scope
of
the
release.
So
now
I'd
like
to
proceed
with
the
quick
recap
of
the
features
and
the
first
big
feature
will
be
recapping
would
be
the
reservation.
Cli
and
regime
will
share
some
some
insights
into
that
for
us.
C
C
The
previous
reservation
on
the
new
stock
he
assigned
to
the
size
channel
also
also,
if
we
migrated
form
a
magenta
to
a
budget
free
version,
for
example,
and
enable
MSI
for
orders,
which
we
migrated
from
the
previous
system,
which
are
still
not
complete.
There
are
still
missing
reservations,
so
we
need
to
detect
them
and
create
compensations.
C
So
so
these
are
just
a
few
cases.
How
how
this
can
happen,
probably
also
with
some
issues
if
there
are
some
who
knows
yeah
and
therefore
we
create
a
CLI
first
of
all,
I
think
Ricardo,
anti-electron
I,
don't
know
who
was
involved.
There
create
the
CLI
which
which
show
all
the
given
inconsistencies,
and
there
is
also
a
option
to
return
a
row.
C
Output
of
the
CLI
and
this
raw
output
can
also
be
used
to
to
provide
this
information
to
the
second
tool,
which
creates
the
compensations
and
by
pipelining
both
tools.
You
can.
You
can
use
the
whole
mechanism,
but
can
also
use
each
of
them
by
them
all.
So
that's
it
from
my
side,
I
think
any
questions
or.
A
Thank
you
very
much
regime,
since
nobody
has
a
questions.
I've
left
a
link
to
the
documentation
in
the
chat
for
this
call
actually
Laurie
already
prepared
quite
a
big
dog
regarding
the
both
CLI
commands,
which
are
doing
the
reservation
magic.
So
you
can
read
on
that
and
figure
out.
If
something
isn't
clear,
though,
thank
you
very
much,
Regina
I
hope
you
will
be
adding
some
more
nice
features
and
fix
in
one
small
buck,
I
think
which
we
had
in
the
reservation
CLI
in
the
scope
of
next
release.
A
D
Yep
Justin
for
me,
when
you,
when
you'll,
be
able
to
see
my
screen
guys
works.
Yeah,
looks
okay
good,
so
yeah
I,
created
I
created
inventory
stock
module
for
providing
ability
to
import
inventory
stock
so
in
during
implementation.
With
this
we
faced
with
with
some
problems
and
some
problems
related
to
performance.
D
So
if
we
use
usual
magenta
API
get
is
sellable
quality
yet
get
is
product
is
sellable
and
get
a
sellable
product
for
the
quantity
services
from
from
MSI.
So
it
turns
out
that
this
stock
is
really
slow.
So
right
now,
I
have,
as
you
can
see,
have
a
small
profile
here,
install
it
with
my
current
magenta
website
and,
as
you
can
see,
this.
D
D
D
D
This
is
only
differentiated
by
the
request
type
here,
because
in
this
request
we
are
able
to
inject
some
search
criteria
and
like
like
here
it
on
particular
products,
but
in
stock
index
data.
We
just
only
insert
here
website
code.
By
the
way
we
decided
to
change
this
website
called
to
sell,
sells
channel
code
to
be
able
replace,
if
you
will,
if
you
will
support
in
future
different
types
of
sales
channels,
not
only
websites
and
yeah
it's
in
the
future.
We
will
replace
it
and
cover
everything
by
the
test.
D
Yeah,
that's
it,
as
you
can
see.
Also
that
stock
dump
stock
index
data
endpoint
is
the
request
is
much
faster.
It
grunts
about,
let's
let
more
than
half
of.
Second,
it's
much
faster
than
another
one.
We
recall
the
this
one
is
turtle
and
it's
ready
yeah,
that's
it
from
my
side.
Maybe
someone
has
any
questions.
B
D
B
D
B
The
quantity
be
zero
or
can
I
set
like
pass
a
parameter
with
the
pre-configured
quantity
that
I
want
to
use
for
all
such
products
either
way
it
works.
For
me,
as
long
as
is
saleable
is
true
and
quantity
is
zero,
I
mean
I
just
need
to
be
able
to
identify
such
products
or
be
able
to
set
a
quantity
that
I
want
for
such
products.
D
They
do
that,
if
you,
if
you
don't
manage
stock,
you
shouldn't
care
about
the
quantity
I'm,
not
ready
to
answer
your
question
this
question
because
I
actually
don't
remember
what
exactly
will
be
here:
I'm
sure
that
if
manage
stock
fall,
then
here
will
be
through
by.
But
if,
if
you
have
I
believe,
if
you
will
have
some
quantity,
it
also
shows
you
a
quantity.
I
can
check
it
out
and
may
be
connected
directly.
B
A
A
B
A
A
E
Well,
honestly,
the
main
reason
for
coming
here
was
the
Texan
barbecue,
then
even
imagine,
but
yeah
anyway.
Yes,
I've
been
working
on
performance
from
different
point
of
view,
and
what
we
share
is
the
performance
improvement,
sure,
okay,
so
basically
it's
a
it's.
A
quite
simple,
pour
request
but
very
effective
from
the
performance
perspective.
E
Basically
the
main
problem
in
sauce
selection
auger.
It
was
in
this
class
that
basically
was
getting
all
the
sources
sorted
by
some
condition
that
was
doubled
for
each
nested
loop
with
my
sequel
queries,
so
it
was
quite
both
from
PHP
side
and
my
secret
side.
So
what
I
decided
to
do
is
to
first
write
a
couple
of
tests
make
sure
my
modification
was
not
breaking
anything.
I
know
that
substrate
that
I'm
writing
tests,
because
everyone
is
talking
about
me
I'm,
not
writing
writing
tasks.
E
But
here
you
have
the
evidence
that
I
did
it
and
once
I
wrote
the
test,
basically
ie
refactor,
that
class
by
simply
gathering
all
the
information
before
so
basically
modifying
an
approach
and
then
running
to
separate
for
each
loops.
So
it
is
no
more
message
and
seems
to
be
more
effective
and
that's
it.
Of
course
you
will
not
see
anything
from
the
UI
point
of
view.
It's
everything
under
the
hood,
and
this
is
my
request.
E
A
A
So
from
the
release
recap,
we
also
have
Maxime
Novick,
who
wanted
to
continue
his
story
from
one
of
the
previous
demo
calls
where
he
talked
about
the
pair
programming.
But
since
then
the
pair
programming
turned
into
I,
guess
quadruple,
programming,
or
even
more
as
more
and
more
people
got
involved
in
the
task.
So
what
seemed
please
feel
free
to
share
your
story.
F
F
F
F
We
have
the
first
pull
request.
Well,
were
all
I
destroyed
30
minutes
ago
had
been
done,
but
we
faced
a
problem
because
any
of
us
had
enough
a
lot
of
time
for
attribution
and
eager
goes
forth
to
find
someone
to
save
the
other
side,
so
our
hero
was
Vitaly
Boyko,
which
created
a
pull
request
to
succeed
in
puller
quest.
This
is
something
but
he
faced
the
same
problem
because
not
everything
was
exchanged.
It
is
not
about
the
last
time
and.
F
F
F
To
be
short,
there
was
a
problem.
The
top
status
was
not
used
to
check
if
product
available.
So
there
was
a
case
when
all
the
sources
are
disabled
by,
but
product
is
still
in
stock,
and
also
we
faced
a
problem
that
magenta
decoder
paralyzed
in
in
thus
I
expected
that
even
if
stores
give
disabled,
so
it's
out
of
stock,
it's
okay
to
use
the
cordis
with
this
item.
F
A
Thank
You
Maxime
I'm
really
happy
that
it's
now
ended
because
we
couldn't
continue
submitting
pool
requests
and
to
pull
requests.
I
had
a
lot
of
fun
merging
that
chain
of
pool
requests,
but
eventually
it
works
out.
It
hub
is
pretty
good
at
that
I
guess.
At
this
point
we
can
complete
our
one
one
to
release
recap
and
while
one
one
two
was
in
the
process
of
releasing,
we
were
also
working
on
the
next
release,
which
I
suppose
will
be
one
to.
A
We
expect
the
main
feature
to
be
the
store,
pickup
and
quite
a
lot
of
work
has
been
done
on
that
front.
In
the
mean
time
and
again,
currently,
the
top
contributors
are
Maxime
and
Alexander,
who
are
doing
really
lot
of
work
on
that
track,
specifically
introducing
the
back
ends
and
the
api's
and
a
lot
of
stuff,
and
yesterday
we
also
had
a
grooming
session
regarding
the
front
end
and
yeah.
A
No,
we
are
going
to
I,
guess
double
the
efforts
and
maybe
make
it
happen
even
much
more
quicker
than
we
initially
expected.
But
for
now
we
can
recap
what
has
happened
on
this
so
picked
up
in
the
last
two
weeks,
and
quite
a
lot
happened.
Quite
a
lot
of
stuff
happened,
so
first,
two
items
will
be
presented
by
Alexander.
A
He
has
implemented
quite
a
big
full
request,
which
is
devoted
to
introduction
of
top
pickup
shipping
method
for
Magento,
which
will
be
used
for
all
of
these
topic
of
orders
and
also
some
some
of
his
updates
for
the
sauce
selection.
Algorithm
I
see
the
ties
Andre
on
the
agenda
said
that
its
adaptation
and
Lausanne
is
currently
writing
me
a
personal
message
that
it's
not
yet
complete,
but
he
will
tell
us
more.
Do.
G
So
it
contains
the
same
changes
and
will
be
deliver
it
just
after
the
first
one
will
be
merge.
This
pull
request
is
provide
in-store,
pickup
shipping
method
of
delivery
method.
I
will
show
a
short
demo
about
this
request,
so
here's
panel
and
I'm
in
stores
configuration
I'm
in
sales
at
delivery
method,
and
here
you
can
see
there
is
in
store,
pickup
delivery
and
store.
Pickup
delivery
have
few
options
just
enable
disabled
price
of
delivery
hand
and
Kofi
and
hand
in
time
also
try
to
on
them,
and
it
is
it
also.
G
G
A
A
Okay,
okay,
thank
you
very
much.
This
is
decent
foundation
to
continue
building
the
store
pick
up,
and
given
that
we
have
some
people
wanting
to
join
the
front-end
track
as
well,
they
will
already
have
something
to
build
on
soon.
The
next
on
the
agenda
is
max
max
Novick
again,
who
I
guess
has
another
interesting
story
about
the
non-default
sources:
orders
pickup,
so
max
you
please
tell
us
about.
F
There
was
no
problem.
Nobody
noticed
if
the
shipment
was
always
magenta
was
virgin,
tried
to
create
a
him
and
positive
fault
source.
So
the
tourist
was
not
even
given
as
argument
at
all,
but
by
the
fact
by
by
the
fact,
we
should
use
each
application
if
time
kind
of
obvious.
So
the
problem
was,
is
the
product
theater
in
the
Sheep
is
not
assigned
to
default,
or
we
got
the
wrong
message.
F
A
A
Thank
you
very
much.
I
think
this
is
pretty
much
all
of
the
updates
on
features,
but
another
really
important
item
which,
by
the
way
marks
usually
missus,
is
the
test
and,
as
usual
as
every
demo
I'm
passing
the
world
to
Tom
who
share
the
updates
on
nemesis
quality
and
this
time
on
the
status
of
the
regression
testing
for
release,
one
one
two
as
it's
still
beta.
So
we
still
doing
some
additional
testing
and
bug
fixing.
H
For
this
week's
quality
report,
yeah
great
ok
call
these
snapshot
then.
So
this
is
just
an
idea
of
where
we
are
what's
going
on
without
getting
directly
in
the
figure.
So,
as
Eugene
said,
we
have
ongoing
manual
execution
of
that
one.
One,
two
we're
looking
at
six
failures,
discovered
five
of
those
can
be
directly
tied
back
to
already
known
bugs
so
they're
in
a
way
expect
failures
and
issue.
H
Two
two
two
nine
is
under
investigation
and
as
to
whether
it
was
previously
fixed
in
a
different
branch
or
that's
still
valid,
and
the
manual
scope
itself
has
been
altered,
especially
compared
to
previous
regression
cycles.
For
this
so
we'll
be
focusing
on
new
functionality,
critical
test
and
we've
also
made
the
effort
to
confine
the
manual
testing
to
just
manual
testing.
H
So
we've
been
adding
some
test
coverage
in
there
and
willing
for
further
test
coverage
next
week.
That's
a
sort
of
where
we
are
right
now
in
terms
of
the
automated
testing.
That's
been
run
just
to
track
where
we
are
so
you
can
see.
The
top
blue
line
is
the
total
number
of
tasks
that,
as
you'd,
expect
increasing
week
on
week.
Obviously
they're
not
automated
tests
come
up
with
that,
because
all
the
tests
defined
are
initially
not
automated
until
they
are
and
the
gray
line
you
can
see.
We've
had
a
small
bump
in
automated
test
numbers.
H
We
want
to
increase
the
velocity
on
that
and
but
that'll
be
a
process
of
community
contribution
and
to
help
bring
that
number
up,
especially
as
we
do
new
feature
development
after
this
one
on
to
release
we'll
look
at
where
we
can
actually
get
and
test
contribution
in
line
with
feature
contribution.
This
is
our
severity
and
component
matrix.
This
will
be
out
in
the
newsletter
if
you
want
to
review
where
we're
covering,
but
there's
not
a
lot
of
change.
The
focuses
in
catalog
and
seals
as
you'd
expect.
H
Then
the
manual
testing
that's
been
done
as
of
today.
This
is
sort
of
again
cataloging
seals
of
roughly
similar
proportions
to
our
automated
testing.
But
here
we
are
in
terms
of
our
ongoing
execution.
So,
right
now
I
say
we
have
the
scope
of
111
we're
at
76
total
completed
several
work
in
progress,
but
actually
run
with
a
result
is
76,
so
we're
70
percent
of
the
way
there.
So
we're,
maybe
looking
at
a
finish
for
this
by
next
Friday
I
would
hope,
but
we
will
come
back
on
there.