►
From YouTube: Magento MSI Open Demo. September 7, 2018
Description
Agenda:
1. Regression plan presentation by @Slava Moskalyuk
https://github.com/magento-engcom/msi/wiki/MSI-Regression-test-cycle
2. Fix crucial issue with Price Indexation and Inventory indexation coupling by @Ivan Pletnyov
https://github.com/magento-engcom/msi/issues/1597
3. Source and Stock configuration by @mikola.malevanec
4. Documentation update by @Lori Krell
A
We
should
under
Corgan
for
everyone,
so
the
today's
demo
supposed
to
be
devoted
for
for
the
end
of
the
first
regression
week,
which
we
supposed
to
finish,
which
we
supposed
to
finish
today,
but
actually
because
because
of
the
blocker,
we
we
stuck
with
on
Monday
and
we
were
fixing
this
blocker
picture
later
in
the
cool
of
the
week.
We
did
not
have
an
ability
to
start
their
aggression,
but
we
will.
A
We
will
actually
demonstrate
you
today
the
regression
plan
which
was
composed
by
swallow,
our
key
engineer
and
after
that
we
will
actually
demonstrate
how
we
fix
that
pretty
big
issue.
We
stuck
with
our
Guardian
coupling
of
price
index
error
and
the
inventory
indexer
and
one
will
demonstrate
up
to
that,
the
working
functionality.
A
B
B
So
I
created
on
wiki,
page
small
page
dedicated
to
our
MSL
aggression,
testing
cycle
with
simple
plan
and
with
almost
a
link
to
hip
tests.
What
is
our
main
source
of
that
scenario
for
dating
and
also
they
have
linked
to
zerah,
because,
first
of
all,
we
will
do
manual
testing
for
a
massage
functionality
using
ship
test
scenarios.
B
C
B
We
will
do
we
have
such
a
month
old,
milestone
to
regression
cycle,
as
as
far
as
you
see
is
yet,
but
afterwards
to
have
will
say
all
statistics.
How
many
tests
will
pass,
how
many
tests
will
be
failed?
And,
oh
all,
people
who
from
community
who
want
to
join
us
here
and
we
say
I
wrote
that
you
may
contact
me
or
bigger
manila
or
whatever.
Neither
to
get
access
to
professed
and
to
participate
in
this
regression
and
for
final
station
for
regression
will
be
at
AT&T.
B
A
B
A
A
There
was
no
any
difference
whether
this
this
particular
child
with
a
minimal
price,
is
in
stock
or
out
of
stock.
So
it
was
an
escalation
which
came
from
one
of
our
merchants,
whom
it
was
pretty
critical
that
the
configurable
product
price
was
supposed
to
be
equal
to
the
lowest
lowest
price
of
the
variation
which
is
in
stock,
and
that
fix
was
deliberate
for
four
core
and
actually
in
core.
It
was
fixed
as
a
as
a
plugin
for
a
resource
model
on
a
stock
item,
and
actually
this
plugin
leads
to
additional
additional
query.
A
How
we
invalidate
index,
we
can
change
the
source
item
quantity,
for
example,
when
the
shipment
is
created
and
the
source
section
algorithm
is
wrong.
We
can
disable
source,
for
example,
if
some
some
problem
happen
with
particular
particulars,
of
course
we
can
enable
it
or
we
can
add
additional
force
to
stop
it.
Yes,
good.
D
Question
we
Christian
through
the
sound
the
the
issue
that
we
find
is
directly.
The
issue
that
came
from
from
from
mainline
is
that
they
started
to
only
choose
the
price
of
the
minimum
price
for
configure
of
product.
The
price
I
started
to
define
on
the
the
minimum
for
a
price
of
in
stock
product
it
yeah
and.
D
A
Yeah
we
adopted
it
and
actually
from
our
site,
we
like
we.
We
did
not
make
any
fixes
for
for
magenta
for,
but
we
provide
the
own
service
which
supposed
to
substitute
one
from
the
MSI
site,
because,
for
example,
we
just
disabled
the
initial
plugin
created
by
guys
from
sustainable
engineering,
because
they
are
currently
plugin
aizen's
resource
model
of
the
solar
stock
item,
which
actually
doesn't
make
a
lot
of
sense
from
MSI
perspective,
because
we
plugin
eyes
the
source
of
truth
and
legacy.
A
A
A
C
A
D
E
A
A
Good
good
point:
Sawa,
could
you
please
say
whether
we
have
this
scenario
covered
in
our
in
our
regression
plan?
If
not
probably
we
need
to
do
it.
So
they
say
if
their
idea
is
to
have
like
a
parent
product
is
not
reachable.
It's
not
accessible
because
some
of
the
children
are
out
of
stock
and
others
are
just
disabled.
A
So
now
what
we
will
do
now,
we
will
demonstrate
you
that
this
functionality,
when
configurable
product,
which
has
several
variation
and
the
variation
of,
is
the
lowest
price
which
is
out
of
stock,
is
accessible
on
a
console
on
a
custom
stock
is
accessible
and
it's
price
equals
not
not
the
price
of
the
variation
with
which
is
out
of
stock.
So
if
one
please
feel
free
to
share
your
screen
and
make
the
presentation.
G
F
F
F
A
So
what
we
need
to
do,
we
just
need
to
assign
all
these
all
these
products,
like
all
the
variations
to
the
newly
created
source
and
assign
that
force
to
the
custom
stock
and
after
that,
assign
the
custom
stuff
to
the
main
website
and
see
that
behavior
is
the
same.
So
the
quantity
is
20,
but
not
tanked.
A
B
A
So
I'm
told
we
have
probably
probably
another
question
regarding
this
regarding
this
functionality,
which
was
just
presented.
I
will
share
my
screen
now,
so
what
we
did
in
the
scope
of
the
implementation,
what
we
did
is
actually
we
introduced
the
dependency
of
the
catalog
product
price
to
inventory
index.
A
So
currently
we
we
have
this
possibility
because
initially
like
before
magenta
to
do,
we
considered
that
all
the
index,
all
the
indexes-
should
be
independent
from
each
other
and
it's
and
it's
forbidden
to
add
dependency
from
one
index
to
another
one
and
the
main
reason
and
the
main
business
reason
for
that
was
a
scalability
of
indexes.
So
we
wanted
to
have
an
ability
to
run
so
several
indexes
simultaneously.
A
But
since
magenta
to
the
I,
don't
know
precise
patch
version,
we
decided
to
introduce
the
dependency.
For
example,
it
was.
It
was
useful
for
full-text
search
index,
which
is
currently
dependent
on
several
other
indexes,
like
a
V
inventory
index,
etc,
but,
like
introducing
this
dependency
like
clear
dependency,
clear,
we
just
mentioned
in
the
index
or
XML
file
file,
what
we
currently
got
as
a
side
effect
of
that
heaven
or
indexation
on
a
level
of
source
item.
A
A
D
Will
discussed
dependency
between
it
exists?
I
think
one
of
the
arguments
was
that
for
for
dependency
for
indecisive
it
dependency
index
is
just
a
question
of
reusing
function,
market
indexes
right
and
it
should
not
change
the
behavior.
So,
for
example,
I
might
be
mistaken,
but
my
expectation
for
this
behavior
world
that,
if,
if
an
inventor
which
is
the
inventory
index
or
something
that
item
invented,
a
index
is
invalidated
or
product
is
saved,
then
partial
index
unsafe
rain.
This
happened
for
that
item
on
on
inventory,
in
first
indentity,
on
full
inventory
and
on
price.
D
A
D
After
a
partial,
but
after
partial
the
index,
women
prefer
their
fourth
fourth
item
right.
Exactly
so,
and
this
so
I
don't
think
we
have
time
to
discuss
it.
You
know
it
makes
sense
to
have
a
separate
meeting
discuss
it,
but
my
my
understanding
is
that
we
should
not
in
Mark
Price
Index,
as
involved
it
for
just
the
rate
index,
partial
remix,
for
right
exactly.
A
So
I
just
wanted
to
clarify
this
expected
behavior,
because
from
my
perspective,
we
need
to
make
the
price
index
turning
to
the
journey
to
the
invalid
state,
when
the
inventory
index
is
an
invalid
state,
for
example
like
when
we
decided
to
reassign
stock
from
one
website
to
another.
We
had
just
Marx
with
whose
inventory
indeed
says
you
know
as
wallet
and
this
supposed
to
churn
the
price
index
invalid.
A
D
H
A
So
we
will
discover
this,
and
probably
we
will
create
an
issue
for
for
guys
from
coral,
sustainable
engineering,
because
this
looks
like
the
scope
of
their
backlog.
So
that's
all
regarding
that.
This
feature
presentation.
Are
there
any
any
question
from
on
tone
or
from
mark
side,
I
see
that
Mark
Jones
a
meeting
I.
C
A
Actually,
actually,
we
check
whether
the
out
of
stock
products
are
available
like
if
out
of
stock
products
are
available
in
Qatar,
so
if
they,
whether
they
are
shown
in
catalog,
we
are
not
removing
these
products
from
the
price
index.
So
we
reconsider
that
if
the
products
in
the
out
of
stock
status
are
able
to
show
on
a
category
page
and
search
result,
page,
the
price
of
the
other
parent
product
still
would
be
the
lowest
one,
the
lowest
out
of
the
variation.
Okay,
good.
Okay.
So
that's
all
regarding
this
feature,
so
I'm
stop
sharing
my
screen.
A
H
H
So,
as
you
can
see,
it
has
vertically
increased
your
from
the
last
time
and
today,
I
will
show
you
how
it
will
look
like
from
the
admin
right
perspective
and
it's
still
a
work
in
progress
so
feature.
Maybe
change
and
different
UI
elements
maybe
behave
a
little
bit
different.
So
currently
we
have
a
lot
of
configuration
so
to
make
it
a
less
tedious
or
less
focused
on
just
to.
H
The
to
specific
configuration
values
which
actually
well
it
behave
is
a
full
chain
of
fallback,
so
it
will
be
sorry,
it's
not
you're
right
in
mentoring,
it
will
be
managed
stock,
which
is
now
exists
in
system
configuration
in
stock
configuration
and
stock
item
configuration
and,
for
instance,
and
decoders
which
exist
currently
on
three
layers
to
its
system.
Configuration
source
configuration
and
source
item
configuration.
So,
let's
put
it
know
by
default,
and
let's
put
it
a
lock
on
T
below
zero
key
saving
configuration
of
let's
create
some
source.
H
H
So
currently,
I
haven't
discussed.
This
part
I've
decided
to
initially
to
disable
inventory
advanced
inventory
button
because
we
have
no
stocks
assigned
to
this
product
or
this
product
not
assigned
to
any
stock.
So
there
is
no
configuration
for
it,
but
as
soon
as
we
add
from
this
product,
like
our
sources,
our
advanced
inventory
button
become
active,
and
here
we
have
a
drop-down
with
the
stocks.
So
in
current
implementation
we
can
save
just
one
stock
like
simultaneously.
H
So
in
order
to
save
all
configuration
for
different
stocks,
we
need
to
receive
product,
but
it
will
change
in
the
future.
So
yeah,
let's
take
a
look
at
our
configuration.
So
here
we
have
two
sources
and
we
can
see
that
the
product
it's
initially
it's
using.
This
is
a
gigantic
the
default
config
and
on
that
first
one
source.
We
can
see
that
fallback.
H
Well,
let's
do
another
way.
I
we
have
in
this.
Our
system
configuration
like
manage
stock
to
know
on
the
stock,
one
also
known,
but
for
instance,
we
want
for
this
particular
product
it
being
measured
it's
measurable
by
stock,
so
it
will
overwrite
all
the
oh.
Of
course
it
will
all
right
all
the
system
and
stock
configuration
and
for
this
product
the
stock
will
be
manageable.
C
A
You
can
please
open
the
advanced
twenty
one
more
time,
so
this
is
actually
pretty
pretty
interesting
stuff
and
we
do
not
have
an
ability
to
discuss
with
mark
that
and
we
had
to
to
apply
this
apply.
The
solution
like
as
soon
as
as
soon
as
we
can,
but
currently
we
can
discuss
whether
there's
a
implemented
solution
is
good
enough
for
at
least
first
release,
because
what
we
did
here
so
we
added
the
scope,
selector
and
the
scope
selector
in
our
case
is
a
stock
list
and
the
stock
lists.
A
H
The
best
correct,
so
it's
it's
actually
thought
and
dynamically.
So
currently
we
have
like
assigned
to
sources
and
what
we
actually
have
default
one.
So
as
soon
as
we
assign
the
default
one
source,
we
will
have
now
the
first
one
is
default
stock
in
in
our
and
drop-down
selection.
So,
yes,
it
has
all
the
science
talks.
Another
one
feature
is
we
are
currently
not
implement.
Is
confirmation
model
window
and
we
still
or
discussing
what
it
would
be
better
like
safe
all
the
stocks
configuration
simultaneously
or
just
showing
the
model
window
which
will
ask?
A
A
Potentially
we
can
introduce,
maybe
ajax.request,
which
will
save
the
data
but
for
dynamic
rules,
but
what
we
decided
that
currently
we
have
like
10
10
configuration
option
per
stock
and
if
you
will
add
the
dynamic
rows,
so
we
can
also
introduce
a
mess
because,
for
example,
user
would
be
like
10
stock
10
stocks,
they're
gonna
be
like
10,
x,
10.
So
too
many.
A
G
C
G
H
A
So,
actually,
maybe
it's
not
not
pretty
clear
from
from
the
presentation,
but
the
the
most
interesting
part
here,
the
actually
the
fallback
mechanism,
because
currently
we
are
like
we
are
making
a
fallback
based
on
the
configuration,
whether
it's
said
or
not.
We
have
the
next
level
like
stock
item
stock
and
the
global
configuration
and
similar
levels.
We
have
four
sources,
so
we
have
the
source
item,
source
and
global
and
depending
whether
we
have
configuration
set
on
the
lowest
level,
if
not,
we
making
the
fallback
to
the
upper
level
to
the
higher
level.
A
For
example,
if
the
source
item
configuration
not
set
for
particular
product
like
before
them
for
analogy
is
not
set,
we
make
him
fall
back
to
the
configuration
of
the
level
of
source.
So
actually
these
give
us
an
ability,
for
example,
to
introduce
a
source
which
going
to
be
used
as
a
drop
shipper
and
for
this
particular
source,
apply.
Configuration
like
also
like
before
their
functionality
is,
is
enabled,
and
actually
this.
E
G
Gonna
say
mentioning
documentation:
I'll
make
it
short
and
sweet
I
promise,
because
some
of
this
is
actually
going
to
change
with
the
demo
we
just
saw.
So
if
you
are
new,
because
there
were
some
questions
in
slack
about
where
to
find
documentation.
If
you
go
to
the
MSI
repo,
the
wiki
has
tons
of
great
technical
content,
as
well
as
the
user
guide
and
I
have
added
the
links
to
all
the
dev
Doc's
content,
which
has
some
great
tutorials
Kevin's
put
together.
G
This
will
give
you
an
a
quick
overview
into
the
product.
It
is
very
merchant
specific.
The
dev
Doc's
content
is
very
developer
centric,
but
it's
incredibly
helpful
to
you
to
understand
it
and,
as
was
just
mentioned
I,
you
have
some
content
drafted
regarding
this
configuration
fall
back,
but
I'm
going
to
be
reviewing
that
in
a
few
minutes
to
see
if
I
need
to
update
it
and
I
will
be
like
it
says
here,
adding
a
lot
of
examples
to
really
help
walk
through
it.
G
But
each
of
these
pages
has
been
updated
to
show
how
you
can
configure
the
different
options
at
each
of
these
levels,
including
the
create
sources
and
stock
pages,
now
have
new
screenshots
showing
a
lot
of
this
information.
For
example,
if
we
scroll
away
down
here,
you'll
start
to
see
these
configuration
areas
again.
This
is
very
much
in
progress.
G
It's
probably
going
to
change
dramatically
in
the
next
day,
in
fact,
to
make
sure
it's
up
to
date
with
all
information,
including
the
back
order
section
where
I'm
going
to
walk
through
some
better
examples
today
of
real-life
examples
of
when
you
want
to
do
it
globally
versus
at
the
source,
item
level,
stock
item
level,
product
etc.
But
this
will
give
everyone
it
like
a
really
good
walkthrough
of
what
to
expect
what
you
should
see
on
the
screens
as
well
as
how
to
configure
it
and
what
those
items
and
examples
are.
G
We've
also
added
some
information,
it's
a
kind
of
at
a
high
level,
but
we're
going
to
add
more
that's
deeper
of
what
what
merchants
should
expect
in
changes
to
inventory
management
overall,
when
MSI
is
going
to
be
installed
and
upgraded
with
2/3.
This
is
a
quick
list.
It's
it's
kind
of
high-level,
but
we'll
dig
deeper
and
all
of
this
content
will
be
available
as
beta
Doc's
when
we
do
have
another
beta,
but
this
is
all
available
right
now.
If
anyone
has
questions,
feel
free,
otherwise,
I
am
good.
Thank.
A
You
Laurie
the
conversation,
definitely
matter
for
us
and
taking
into
account
how
many,
how
many
requests
for
MSI
documentation
we
get
the,
and
this
is
really
good,
that
we
always
have
an
answer
like
to
have
the
mutation
here.
It
is,
and
so
thank
you
very
much
you're
doing
a
great
job
and
and
looks
like
that.
A
That's
all
for
today
and
thank
you
very
much
for
your
time.
It
was
a
little
bit
longer
than
being
than
we
expected,
but
I
believe
it.
It
was
really
really
interesting
features
to
be
like
presented
today,
because
that
was
really
really
really
sophisticated
functionality
and
the
sophisticated
bug,
so
that
was
for
us.
It
was
really
interesting
to
fix
and
to
work
with
that
and
I
hope
that
for
you,
it
was
also
interested
to
to
watch
this.
Thank
you
very
much
guys
and
see
you
see
you
next
week.