►
From YouTube: Magento MSI Open Demo. May 24, 2019
Description
Agenda:
• 1.1.2 Release Update
• Further improvement of Source Assignment UI on Product page
• Mass actions for enabling and disabling Inventory Sources
• Resolve possible Race condition of Store Pickup orders and Shipping orders
• Extend Source entity with Pickup Location information
• MSI Test Cases organization
A
Welcome
to
another
MSI
demo
meeting
today,
we
don't
have
too
much
of
the
new
information.
Has
we've
been
busy
with
packaging
and
completing
the
release
for
MSI
1
1
2,
which
would
be
included
with
Magento
the
next
patch
watch
movies
of
Magento?
So
the
main
update
for
the
release
is
that
we
have
one
small
packaged
the
MSI.
A
A
A
Though
we
had
already
had
some
cycles,
one
was
with
the
enterprise
Magento
one
with
was
with
just
a
community
edition
and
some
of
the
latest
fixes
which
we
delivered
after
the
first
cycle.
So
we
see
some
decrease
in
number
of
failures.
This
is
caused
by
the
fact
that
some
of
the
tests
are
only
failing
on
Enterprise
Edition
and
some
of
the
tests
were
fixed,
I
mean
bugs
were
fixed
during
yeah
during
the
past
week.
So
this
is
pretty
much
it.
Regarding
the
release.
B
A
One
of
the
pool
requests
was
done
by
Sergei,
who
I
assume
is
not
on
the
call
today.
Some
reason
he
was
unable
to
connect,
but
I'll,
try
to
demo
and
present
what's
been
done
in
the
scope
of
this
quest.
So
the
idea
was
to
improve
the
UI
for
the
assigned
sources
on
the
product
page,
we'll
already
had
some
work
going
in
in
that
direction,
but
Sergei
decided
to
completely
rethink
it
and
implement
it
in,
like
he
claims
in
Magento
style,
with
the
grid
and
and
familiar
controls
so
to
the
demo.
A
A
Burn
in
their
own
places,
but
now
buttons
are
pretty
much
a
lot
in
the
same
as
all
other
controls
and
the
the
source
of
surveillance
is
not
presented.
Nice
grid,
which
has
pretty
much
common,
look
and
feel
for
all
of
the
magenta.
All
of
the
functionality
remains
the
same,
so
we
still
have
the
assign
on
the
sign
and
we
can
change
all
the
values
and
Oh
still
still
functional
as
it
was
before.
A
Additionally,
the
advanced
inventory
was
moved,
but
it's
opening
the
same
old
slide-out,
but
now
in
a
new
place,
though,
this
is
pretty
much
cover.
Steeple
request
from
Sergei,
we'll
still
be
working
with
mark,
who
is
the
product
owner
for
MSI
to
make
sure
that
doesn't
have
any
questions?
This
is
and
will
be
emerging
that
right
after
updating
all
of
the
functional
sets,
which
also
relates,
which
also
rely
on
this
functionality.
A
The
was
the
first
update
and
one
more
nice
fishable
request,
which
was
implemented
by
William
during
the
imagine
on
the
contribution,
D
and,
unfortunately,
I
think
William
is
living
in
Australia
and
it's
well.
It's
Mike
in
there
now
so
I'll
also
present
this
one,
and
this
cool
request.
Pretty
much
adds
a
new
feature
and
I've
heard
some
people
were
waiting
for
that
feature,
and
this
is
mass
enabling
and
disabling
of
sources.
So
again
pretty
small,
but
someone
may
be
really
useful.
A
Tell
with
this
pull
request
covered
I'm,
going
to
stop
sharing
my
screen
and
we'll
pass
the
word
to
Maxine,
who
has
been
working
hard
on
the
store,
pickup
truck
and
has
at
least
two
updates.
Today
we
have
merged
quite
a
lot
of
pull
requests
from
him
lately
to
stop
the
carcass
in
well
max.
Please
feel
free
to
continue.
B
B
B
There
there
could
be
a
case
when,
as
you
can
see
now
so
selection
algorithms
instead.
Well,
if
we
need
to
fib
beta
items,
we
could
use
this
pickup
source
just
to
avoid
internal
turtle
teleportation
and
it's
cool,
but
by
the
fact
we
should
reserves
is
quantity,
so
we
should
take
all
all
the
orders
placed
use
its
or
pickup
and
reserve
their
quantity
for
the
selection
algorithm.
So
what
do
I
mean
at
the
moment?
B
As
you
can
see,
there
is
eight
available
for
pickup
source
or
four
and
four
for
two
buzzers.
Who
is
my
pull
request?
It
looks
like
their
quantity
available
for
pickup
source
is
zero,
because
two
is
because
we
already
have
and
order
place
units
or
pickup
for
the
source.
So
no
selection
algorithm
should
not
see
it.
A
A
B
Well
that
simple:
we
just
need
to
create
two
different
attributes
for
source
which
are
not
used
in
the
sauce
itself,
but
are
used
for
the
complications.
So
technically
they
are
extension
entities.
How
does
it
look
now?
So
previously
we
had
M
users,
pickup
location,
checkbox,
and
now,
if
we
do,
each
a
magic
happens.
B
B
B
Well,
however,
that's
not
all
if
you
remember,
we
have
a
motto
which
converts
source
entity
to
the
immutable,
pickup
location
entity
and
what
the
problem
you
should
help
for
that
name
for
typical
application
to
display
the
quartet,
even
if
it's
not
state
in
the
package,
so
we
created
Alexander
culture
created.
Another
extension
point
was
a
mapper,
it's
pre-processors.
A
Thank
you
very
much
max
I.
Don't
think
your
English
is
better
managed
to
understand
everything.
So
thank
you
very
much
for
your
effort.
Okay,
so
I
think
we
don't
have
too
many
more
updates.
The
the
last
one
would
be
just
a
short
update
on
the
test
cases.
Usually
we
have
the
quality
report
by
Tom,
but
due
to
the
fact
that
we
were
working
hard
to
reorganize
all
of
the
MSI
hipsters
and
all
scenarios
Tom,
some
Tom's
automations
did
not
make
it
and
this
week
we'll
just
present.
A
What's
what's
changing
so
for
those
of
you
who
possibly
use
these
test
cases
for
some
fun
purposes,
which
we
have
600
650
now
what
we
have
come
up
with
and
as
is
that
we
change
directory
structure.
Now
it
looks
more
like
single
stock
and
multi
talk.
Directories
are
rule
directories
inside
the
femicide.
A
This
means
that
we
have
some
test
cases
which
not
directly
relate
to
MSI,
for
example,
all
of
the
MSI
scenarios,
but,
like
all
the
inventory
scenarios
but
executed
in
these
singles
talk
mode
when
when
we
did
not
create
any
sources
or
stocks
and
the
other
one
covers
all
of
these
scenarios,
which
relates
to
the
multi
stock,
where
user
renamed
both
a
few
sources,
stocks
and
stuff
like
that,
though
this
is
done
dude.
This
is
done
to
allow
self-contained
MSI
regression
testing
cycles.
A
So
we
keep
like
magenta
related
stuff
here
as
well
to
another
major
update
like
what
we've
been
working
on
during
the
past
weeks,
as
is
labeling
all
of
these
cases
and
linking
them
to
the
found
artifacts
so
like,
for
example,
we
have
some
random
tests.
We
have
some
steps
something
happening
here,
but
now
we
have
huge
scope,
huge
amount
of
labels
which
identify
the
automation
status
of
the
test
case
type
of
the
automation
applied,
so
it
may
be
MF
TF
or
in
some
cases
Web
API
and
integration
tests.
A
It's
again
indicates
mode
the
severity
of
this
scenario
and
the
MSI
release
where
this
specific
test
case
was
introduced.
So
doing
this
kind
of
updates
would
allow
us
to
improve
qualities
in
the
future
as
we'll
be
able
to
generate
better
reports
and
metrics
and
figure
out.
Where
do
we
miss
on
the
verge
of
a
Miss
on
the
automation?
This
is
something
we'll
be
working
throughout
the
next
next
month.
A
We'll
see
more
automation
items
popping
up,
so
this
is
pretty
much
it
on
the
test.
Reorganization
and
yes,
I
think
this
is
even
it
for
today.
So
thank
you
very
much
for
joining.
Thank
you
for
your
time
and
thanks
a
lot
max
for
sure
and
they
store
pickup
dates.
It's
really
exciting
that
I
hope
who
will
see
some
entrance
scenarios
working
with
in-store
pickup,
probably
a
great
weekend.