►
From YouTube: Magento MSI Open Demo. July 13, 2018
Description
Agenda:
1. Bug fixes made during this week - by @Slava Moskalyuk
2. Update on MSI documentation and MSI FAQ page - by @Lori Krell
3. Update on Magento Functional/Acceptance Tests for MSI - by @jstennett
4. Bold agency is about to launch two new projects with MSI - by @Bartłomiej Szymański
5. Update on Grooming status (Stock and Source configuration) - by @iminiailo
A
A
A
Hi
guys
I
was
muted
and
did
not
did
not
notice
that
I
was
muted,
so
hello,
everyone.
Let
me
start
the
regular
weekly
MSI
demo
meeting
and
I
propose
to
follow
the
agenda
shares
erroneous
ago
in
in
MSI
side,
channel
and
first
present
are
going
to
be
flower,
which
show
you
several
bug
fixes
we
made
even
this
week
for
box
created
earlier,
so
I
feel
free
to
share
your
screen.
B
B
B
And
now
you
may
see
that
the
sources
get
up,
it's
still
present
on
product
page
and
we
may
seize
it.
Our
custom
source
and
the
source
assign
it
and
by
the
way
you
may
an
ensign
here
using
this
trash
can
but
it's
disabled.
So
you
cannot
change
any
value
for
quantity
and
let
my
quantity
and
so
I
go
back
to
advances
in
venturi
and
it
changed
manage
top
where
you
back
to
the
config
settings,
and
we
may
say
that
it's
this
fields
are
still
again.
Editable
and
I
also
show
that
it's
affected
also
in
consideration.
B
B
B
B
C
Sharing
the
screen
all
right,
so
this
week,
I
had
added
in
MSI
FAQ
page
as
we
collect
questions
from
issues
and
demos
conversations
grooming
sessions,
we'll
add
those
questions
to
this
page
with
links
into
the
documentation.
This
will
also
help
us
find
what
questions
there
are
to
enhance
the
documentation
so,
as
I've
been
adding
these
answers,
I'm
also
adding
it
back
into
the
Doc's
themselves,
which
thank
you
very
much.
Everyone
for
your
questions,
they're
extremely
helpful
for
everyone.
C
This
page
will
definitely
grow
so
I'll.
Add
some
links
at
the
top
to
make
it
easier
to
work
through
also
for
other
updates
on
the
documentation,
I'm
working
on
a
new
page
to
give
a
deeper
dive
into
the
source.
Algorithms,
so
be
watchful
for
that,
but
for
right
now
there
is
an
overview
of
this
through
this
MSI
features
and
processes.
This
is
a
great
introduction
area
to
kind
of
understand.
What's
going
on
with
the
sources
stocks
and
the
algorithm
itself
and
all
the
features
I'm,
also
adding
a
new
mass
action
tool,
page.
C
Yeah
I'm
also
working
on
a
mass
action
tool,
page
that
is
going
to
be
in
development.
This
content
will
be
updating
as
Ricardo
works
on
this
feature,
and
we
will
I'll
keep
it
up
to
date
with
all
the
changes
that
are
coming
through.
So
this
is
going
to
change
quite
a
bit,
but
it'll
give
you
a
good
start.
Introduction
and
I'll
be
adding
updates
for
all
the
changes
that
we're
seeing
in
the
demo.
So
the
documentation
will
now
start
including
work,
that's
being
completed
and
pushed
out
to
develop,
as
well
as
the
beta.
A
This
way,
I
take
into
account
that
we
don't
want
to
break
this
reference.
So
we
don't
want
potential
to
break
and
effect
already
existing
orders,
we're
keeping
all
these
references,
and
we
just
provide
an
ability
to
make
this
sort
disabled
and
by
the
way,
when
I
was
making
a
short
preparation
for
this
demo.
I
notice
that
currently
it
looks
like
we
have
a
bug
because
currently
it's
possible
to
make
to
edit
the
source
code.
A
So
this
is
actually
edit
source
page
and
the
source
code
is
editable,
but
this
field
is
supposed
to
be
disabled
because
in
msi
source
code
used
as
a
natural
identity.
So
after
the
creation
of
entity,
it's
not
possible
anymore
to
edit
it
because
we
under
the
hood
in
our
technical
implementation,
we
don't
have
database
generated
ad
and
in
our
case
the
source-code
plays
the
role
of
a
unique
identity.
So
updating
it.
You
will
actually
take
into
account
that
in
magenta
there
is
no.
There
is
no
crud,
but
we
use
LSD.
A
So
there
is
no,
so
we
use
the
LSD
like
a
lord
save
delete,
so
our
save
method
actually
doesn't
differentiate,
insert
or
update
query.
So
updating
the
unique
identity
user
will
just
create
another
source.
From
this
perspective,
the
source
code
supposed
to
be
supposed
to
be
disabled
on
the
level
of
UI
slower.
Could
you
please
create
this
bug
after
this
demonstration?
A
C
A
D
Ok,
for
the
past
few
weeks,
I
have
been
working
on
a
few
different
tasks,
one
of
them
being
stabilizing
our
existing
in
maasai
tests.
The
other
big
task
was
getting
our
Jenkins
instance
up
and
running.
So
with
the
help
of
an
and
our
lovely
DevOps
team
and
Alex
kolesnik
on
our
awesome
penguins
team,
we
finally
actually
got
as
soon
as
I
get
this
lovely
control
panel.
D
D
We
have
78
tests
in
the
MSI
repo
currently
and
there
are
nine
that
are
pending
PRS
right
now,
so
once
we
actually
get
the
builds,
Green
will
get
everything
merged
and
we
will
actually
be
able
to
run
this
with
everything
for
all
of
our
builds
going
forward,
which
is
really
exciting
and
it's
taken
a
while,
but
we're.
Finally,
here.
D
Yeah
I
think
that's
it
from
my
side.
Actually,
so
when
we
were
actually
doing
the
maintenance
on
our
test
repos,
we
found
that
there
were
changes
made
to
non
MSI
modules
that
we
had
to
move
to
a
separate
PR
for
the
Magento
pangolins
repository,
because
when
an
MSI
is
installed
to
a
Jenkins,
build
it
only
installs
it
only
copies
over
the
MSI
modules,
like
any
other
extension.
So
if
changes
are
not
included
in
a
my
side
modules,
then
they.
D
Won't
be
wrapped
principal,
so
we
have
to
have
them
sync
to
mainline
Magento
and
then
all
the
MSI
parts
have
to
be
contained
within
the
MSI
modules.
So
that's
just
something
we
discovered
when
we
were
doing
this
maintenance
and
I
moved
all
the
changes
over
I
split
them
apart
and
I
put
them
in
the
right
depots.
So
that's
how
we
got
this
unstuck
as
one
of
the
issues
that
we
ran
into,
but
that
is
it
for
my
side.
A
E
E
This
is
commerce
darshan,
so
yeah
on
the
horizon.
We
have
another
client
that
should
accept
our
our
our
predictions
about
MSI
and
enthuse
it,
and
at
least
not
for
last.
Of
course
we
have
a
very
sophisticated,
sophisticated
project
yeah,
it's
all
about
that.
This
will
be
something
like
the
marketplace
so.
E
Third-Party
sellers
could
up
their
products
to
to
this
marketplace.
Of
course,
this
is
it's
not
hard
part,
but
hard
part
is
start
start
with
with
numbers,
because
in
our
prediction
there
will
be
about
ten
to
twenty
thousand
of
stocks,
because
every
third-party
sellers
need
their
own
stock
in
Magento.
A
E
Yeah
exactly
one
source
with
multiple
stocks
yeah,
but
because
every
seller
needs
their
own
stock
and
we
have
two
for
the
customers
show
on,
for
example,
in
catalog,
page
and
search
page
aggregated
stocks,
but
in
recognition
recognitions.
There
is
one
neat
that
on
the
product,
page
client
can
choose.
A
So,
in
your
case,
the
roll-
let's
say
the
role
of
the
stock
resolver
I'm
gonna-
be
made
manually
by
afternoon.
Yet
by
the
way,
it's
very
similar
as
as
potentially
store
pickup
could
be
implemented
because
on
store
pickup,
you
also
supposed
to
show
all
different
locations
where
the
some
particular
product
could
be
picked
up
and
the
customer
money
early
choose.
E
A
So
work
is,
you
would
like
to
make
a
check
out
and
make
make
an
order,
and
in
this
order
gonna
be
several
stocks
be
used
in
the
scope
of
this
order,
but
maybe
it
makes
sense
to
do
it
like
we
implemented
the
multi
shipping,
because
actually
multi
shipping
create
several
orders
and
each
of
the
order
internally
represent
one
a
quarter.
It
will
be
the
same,
for
example,
and
you
will
create
several
workers
and
each
order
would
be
for
corresponding
stock.
You
will
actually
make
it
fall
back
to
to
existing
out-of-the-box
implementation
of
an
aside.
Yes,.
A
A
E
A
E
A
A
A
We
were
talking
about
technical
implementation
of
these
two
stories:
sauce
item
configuration
of
the
stock
item
configuration
and
the
main
idea
behind
these
stories.
It's
pretty
similar
to
how
we,
how
make
a
segregation
between
sources
and
stocks-
and
you
know
that,
currently
we
made
the
segregation-
and
this
is
actually
the
real
implementation
of
the
CQRS
on
a
project.
So
we
have
Commons
interfaces
and
the
four
common
common
interfaces
representative
sources.
So
these
are
interfaces
for
data
modification
and
we
have
a
query
interfaces
in
our
case.
A
Very
interfaces
are
stores,
so
these
are
interfaces
for
data
visualization
and
reading
data
and
the
on
a
front-end.
We
work
just
with
stocks
and
we
know
nothing,
nothing
about
sources,
that's
why.
Actually?
Our
system
is
agnostic
to
at
the
time
of
the
porter
placement
we
agnostic
to
how
many
sources
we
have
and
our
order
placement
process
is
identical
for
single
source
and
multi
source
systems.
That's
why
we
don't
add
additional
performance
degradation
if
it
helped
many
sources
on
board.
That
was
actually
the
main
design
solution
and
the
main
idea
technical
idea.
A
A
Summary
configuration
you
you'll
see
that
some
of
the
configuration
contrary,
contrary
to
the
stock
availability
and
the
source
quantity
we
have
the
configuration
and
which
is
applicable
for
on
the
source
level
and
on
the
stock
level.
For
example,
we
have
some
some
configuration
which,
which
is
applicable
just
for
the
stock,
for
example
only
X
left
threshold
or
manage
stock
or
minimum
quantity.
So
this
is
this:
is
configuration
option
applicable
just
for
just
on
a
stock
level
and
they
don't
don't,
have
they
actually
useless
on
a
source
level?
A
But
there
is
some
some
configuration
option.
For
example,
like
here
quantity
use,
decimals,
so
quantity
use
decimal
is
a
configuration
option
which
should
should
be
applied
just
on
a
level
of
source
and
on
a
level
of
stock.
It
should
be
computed
so
this
option.
There
is
no
sense
to
specify
it
manually
on
a
stock
level,
but
it
should
be.
A
A
Can
be
sell
as
a
as
a
decimal,
so
we
don't
have
a
by
kilograms
or
by
pounds.
So
there
is
no
integer
value
for
it,
so
we
can
just.
We
can
just
get
this
value
based
on
a
source
representation,
the
same
the
same
for
back
orders,
because
we
can
say
that
the
quarter
and
the
back
where
their
availability
is,
is
the
option
we
supposed
to
be
computed
based
on
on
a
configuration
setting
specify
on
a
source
level,
because,
for
example,
if
you
can
see
there
such
case
as
a
drop
shipper
support,
so
we
will.
A
Now,
before
the
negative
negative
stress
code
for
back
orders
implemented
and
merged
by
alessandra,
so
we
also
will
use
the
order
as
a
computed
option,
not
not
as
a
individually
individually
specify
option
on
the
level
of
stock.
This
is
actually
why
we
have
here
several
different
tricks
and
what
our
design,
what
our
final
vision
here,
that
we
would
like
to
make
stock
item
interface.
A
So
stock
item
interface
is
the
an
interface
which
would
be
which
will
represent
computed
and
calculated
index,
and
the
front-end
will
work
with
this
interface.
From
this
interface.
We
are
going
to
eliminate
all
this
setter
method,
so
the
interface
is
supposed
to
be
immutable
and
the
interface
will
represent
pre
computed
index
and
all
the
data
changes
would
be
done
through
the
admin
panel
and
through
the
admin
panel
each
particular
configuration
option
will
be
changed.
We
are
dedicated
service,
so
we'll
create
Commons
as
in
secure
s.
A
Architecture
and
this
command
will
affect
particular
particular
configuration
option,
whether
whether
this
configuration
option
supposed
to
be
changed
on
a
level
of
stock
like
mean
saleable
quantity
or
max
a
level
quantity
of
quantity
increments,
or
whether
this
configuration
options
supposed
to
be
effect,
data
on
a
level
of
store
on
a
level
of
source
like
the
quarter
and
at
the
time
of
the
rain,
invent
Tarricone
stock
configuration
or
indexation.
So
we
would
have
own
own
indexation
process
for
inventory
configuration.
A
We
would
create
dedicated
index
for
particular
stock
item
configuration
data.
It
would
be
a
little
bit
more
complicated
than
we
have
for
stocks
because
to
build
index
for
stock,
all
we
need
to
do
is
just
use
source
item
data,
but
here
we
will
health
data
for
the
source
configuration
and
for
the
stock
item
configuration
also,
we
will
apply
fallbacks,
which
will
also
introduce
on
complexity.
A
But
the
idea
is
it's
pretty
the
same,
so
we
want
to
build
the
world.
May
we
want
to
make
a
simulation
between
Commons,
which
update
the
updates,
the
data,
and
we
want
to
build
the
immutable,
read
interface,
which
would
be
used
as
a
query
on
a
front
end
and
the
front
end
supposed
to
work
with
the
interface
with
without
any
possibility
to
affect
and
update
the
configuration
valves.
So
this
is
sound,
probably
a
little
bit
tricky
and
during
the
weekend,
I
will
try
to
make
to
make
a
corresponding
document
and
describe
all
this
process.
A
We
describe
all
the
interfaces
because
they're
supposed
to
be
many
interfaces
here
and
after
that,
on
our
last
grooming
on
Tildy,
we
will
try
to
finalize
the
scope
of
work.
Will
we'll
discuss
and
clarify
all
the
final
question
with
marker
gardens?
It,
and
at
least
we
will
try
to
provide
the
at
least
rough
estimation,
whether
we
would
be
able
to
finish
this
pretty
big
story
in
the
scope
of
our
can't
better
release
of
MSI.
A
A
A
If
no
looks
like
we
we've
done,
thank
you
guys
for
your
time
feel
free
to
ping
us
in
msi
slack
channel.
We
are
always
available,
especially
on
weekend
and
at
night.
So
this
is
the
time
when
we
have
spare
time
for
for
chatting,
so
don't
hesitate
to
pinged
at
any
time
and
see
you
see
you
soon
on
an
father,
msi,
weekly
medians
thanks
ago.
Thank
you.