►
From YouTube: Magento MSI Open Demo. April 6, 2019
Description
Agenda of fancy stuff will be presented:
• Integration of GraphQL and MSI @Bartłomiej Szymański
• Performance improvement via reducing the usage of legacy stock view @Bartłomiej Szymański
• Store Pickup UI for Source grid and form @Aleksandr
• Ready for Pickup controls on Orders placed with Store Pickup @Maxim Novik
• Updates form the Contribution Day event happening right now in Perugia @TheRick
A
So
welcome
to
another
MSI
demo,
which
which
is
intended
to
present
some
really
interesting
items
happened
during
the
last
week
and
some
interesting
contributions
submitted
to
Messiah.
So
today
we
are
hosting
the
meeting
from
the
image
special
its
headquarters
here
in
Perugia
Italy,
where
we
are
having
a
blast
at
the
event
organised
here
by
the
guys
and
doing
a
lot
of
MSI
stuff.
So
Ricardo
will
will
provide
more
information
on
that,
but
currently
II
team
is
working
simultaneously
on
bundle.
A
Product
supports
on
b2b
on
various
improvements,
bug
fixes
and
even
CLI
for
reservations
management
just
just
made
it
up
today
now
working
on
it.
So
quite
a
productive
event.
Today,
on
the
schedule,
we
have
two
items
by
Bartek,
but
unfortunately
he
was
unable
to
join
due
to
some
family
related
reasons.
So
we'll
try
like
me
and
eager
to
to
present
his
work
done,
which.
A
Yeah,
which
was
not
during
the
event
last
week
in
Krakow
I,
think
the
first
item
was
the
integration
of
graph
key
on
my
site.
Yes-
and
this
was
quite
a
big
item,
as
we
already
have
graph
key
role
in
supporting
Magento,
which
is
in
active
development,
it
was
first
released
with
two
point
three,
the
same
time
as
MSI,
but
unfortunately,
Rafael
didn't
know
much
about
other
sources
are
the
stocks
and
well,
it's
only
was
capable
of
working
with
the
default
stock.
A
So
Bartek
addressed
this
issue
in
his
pull
request
to
do
that,
he
had
to
introduce
another
module
which
is
inventory
graph
kilo
and
basically
implements
to
resolvers,
which,
which
are
now
used
in
place
of
the
ones
coming
in
the
bundle
with
gravel.
So
the
solutions
pretty
forwards
and
one
of
the
one
of
the
resolvers
provides
only
X,
left
and
sock
feature
which
is
used
on
the
front
ends
and
can
be
configured
by
a
by
an
admin.
Basically
just
shows
the
amount
of
products
left
and
stock
after
a
certain
threshold
is
reached.
A
A
B
A
A
B
B
Based
on
the
my
sequel
view,
while
some
of
the
performance
patches
we
already
did
but
not
released
yet,
and
with
this
approach
based
on
the
triggers
and
like
making
that
comparison,
we
realize
that
we
still
have
a
gap
and
we
don't
have
we're
still
using
view
on
a
pretty
crucial
scenario,
which
is
run
on
a
front-end.
And
actually
this
scenario
implies
so
implies.
B
B
We
don't
have
the
my
secret
view,
digital
and
instead
of
the
instead
of
the
my
sequel
view,
we
are
using
the
direct
drawing
on
the
cattle
inventory
stock
item
table
the
leads
fixin
to
use
that,
for
four
months,
performance
boost
or
both
category
page
and
the
product
save
page
scenarios
to
subject
applying
these
Peaks
we're
going
to
rerun
most
of
our
performance.
Acceptance
builds
to
compare
to
compare
that,
like
our
productivity,
which
exists
in
magenta
plasma
side.
This
actually
pretty
much
all
I
believe
both
of
these
requests
would
be
accepted,
maybe
today
or
tomorrow.
C
Do
you
see
my
screen?
Yes,
we
do
so
I
will
talk
a
little
bit
about
my
request.
Actually,
this
pull
request
is
mostly
a
refactoring
of
implementation,
which
has
started
from
some
Australian
guy
in
on
contribution
Day
in
Australia.
This
is
related
to
refactoring
of
implementation,
new
attributes
for
inventory
ORS,
which
can
tell
us
that
the
source
is
available
to
use
as
pickup
location.
C
C
B
D
D
D
E
D
A
A
Maybe
anyone
has
any
questions
to
specifically
to
store
pickup
of
implementation,
which
is
currently
going
on.
If
not,
please
feel
free
to
drop
those
questions
to
MSI
chat
on
the
slack.
If
any
of
those
horizon
you
point
to
the
next
on
the
agenda,
I
think
I
think
we
had
Greek
but
also
I
I
know
that
I
know
the
Slava
would
like
to
share
some
progress.
That
he's
been
has
been
happening
on
the
test
scenarios
from
the
manual
test
scenarios
for
the
MSI.
So
though
I
suppose
I
suppose
Lawler
can
can
talk
about
it.
Now.
F
Let
me
share
my
screen,
so
you
know
our
detonators
are
located
on
he
test
and
during
this
week,
where
I
was
fitting
some
gap
for
testing
areas
and
added
23
more,
it's
even
I
would
say
it's
like
variation
of
scenarios,
so
it
was
the
dedicated
to
first
of
all,
a
synchronous
way
for
mass
action
transfer
a
venturi
to
source
onto
the
grid.
I
had
several
scenarios
here.
F
Also
it
was
fitting
the
gap
of
work,
of
making
order
from
custom
website
and
custom
stocks
for
simple
products,
for
virtual
progress
as
well
and
for
downloadable,
and
also
we
had
issue
with
backorder
work
when
product
was
not
visible
on
a
front
end
when
they
have
the
recorder
on
with
zero
quantity.
So
this
gap
also
was
filled
with
that
scenario,
and
that's
all
from
me.
Thank
you.
A
A
A
G
Wouldn't
say
beautiful
office,
but
thank
you
anyway,
but
so
yes
today,
maybe
can
you
thank
you
or,
if
or
the
feedback,
so
today
we
we
had
a
contribution
day
here
in
Perugia
and
it
would
be
the
same
for
tomorrow
and
we
started
working
on
some
working,
some
issues
for
MSI.
So
this
is
basically
an
MSI
oriented
contribution
day
and
I.
G
Don't
want
to
share
everything
because
we
are
working
on
several
aspects,
but
I
just
want
to
share,
maybe
the
most
interesting,
oh
yeah,
you
should
see
my
screen
and
so
I
have
a
couple
of
guys
working
on
the
bundles
products.
Support
for
MSI
sourcing
so
basically
seems
like
we
managed
to
have
the
friend
accession
working
for
bundled
product.
G
You
cannot
see
anything
now
a
mean
there
is
not
any
open
pool
request
because
they
probably
are
going
to
finish
their
job
tomorrow
or
maybe
even
the
day
after,
but
this
is
quite
interesting
and
they
managed
to
do
arrange.
Something
so
seems
like
that.
The
bundled
products
would
be
reality
for
a
messiah
quite
soon.
G
Another
cool
issue
we
are
working
on
is
reservation
CLI.
So
basically,
this
is
a
common
line
tool.
Although
we
need
to
find
any
potential
inconsistency
in
reservation
mechanisms,
because
when
you
migrate,
for
example
from
2.2
to
cook,
to
2.3,
you
may
have
some
orders
that
are
not
in
a
complete
status.
So
basically,
you
can
have
an
inconsistent
reservations,
reservation
table,
so
this
common
basically
finds
every
single
potential
inconsistency
you
have,
and
we
are
also
thinking
to
add-
maybe
some
automatic
l
automatic
fixing
tool
for
for
these
kind
of
situations.
G
I
think
you
would
see
probably
one
poor
request
by
the
end
of
the
day.
For
this,
then
we
are
even
working
to
adding
some
b2b
functionalities
for
MSI,
specifically
this
issue
from
Lars
that
basically
ms:I
support
for
b2b
and
I'm.
Also
personally
working
on
one
old
pool
request:
I
still
have
under
working
progress.
G
Maybe
you
have
a
greater
idea
than
me,
so
I
found
that
basically
trying
to
improve
the
performance
I
had
a
performance
degradation
that
usually
is
not
exactly
the
best
thing
you
can
find
when
you
want
to
work
on
performance,
but
fortunately
I
found.
That
was
not
my
fault,
because
when
I
basically
ran
some,
some
of
the
operations
are
synchronously
because
we
use,
basically,
you
don't
need
to
run,
for
example,
rained
accession
or
the
legacy
synchronization
in
a
in
a
synchronous
way.
G
You
can
run
either
synchronously
I
found
that
basically,
the
pushing
the
messages
to
the
queue
apparently
was
taking
more
time.
Then
depression
itself,
so
I
found
these
digging
into
the
implementation
of
schedule
bulk,
but
basically
when
saving
in
the
entitymanager,
because
you
know
every
time
you
push
something
as
bulk
operation
you're,
creating
the
one
one
entry
in
one
summary
in
the
bulk
summary
I
found
this
in
the
entity
manager
that
was
lowering
down
implementation.
G
B
B
E
E
Yeah
we
just
looked
at
your
last
past
this
code.
Snippet,
you
showed
me
just
as
a
note.
We
have
on
a
scenic
import
track.
We
have
several
stories.
We
want
to
eliminate
the
using
the
database
on
the
step
of
saving
the
bulk
operations
and
yeah.
Nobody
had
pick
up
this
story,
so
it's
somebody
interesting
making
improvements
here.
You
are
welcome.
I,.
E
B
Potentially
because
we
can
still
preserve
the
precision
position
of
the
records
in
the
database,
but
like
the
main
part
which
affects
a
performer
in
this
case,
is
that
we
are
saving
each
operation
one
by
one
here
so
like
Tavian
saving
a
hundred
operation
will
lead
to
100
independent
object
to
be
saved
because
we
we
are
working
with.
We
are
the
entity
managers
there.
So
potentially
we
can
just
substitute
it
with
the
bulk
insert
call.
For
example,
that's
true,
so
the
SEC
should
be
the
question.
E
In
short
code
discuss
the
Balkans
article,
that's
quite
a
good
point:
this
elimination
of
database
that's
kind
of
feature
which
want
to
be
developed,
but
it
will
not
be
like
the
default
one.
The
database
will
still
stays
the
default
one
because
so
this
mean
when
we
have
a
way
to
improve
the
current
default
state,
let's
say
to
using
the
bulk
saving.
That's
definitely
a
good
idea,
but
we
didn't
had
any
details.
The
discussion
on
this
topic,
yet,
okay,
so.
B
H
Next
week
this
is
Laurie
I'm
gonna
be
working
on
a
bunch
of
documentation
updates,
but
I'm
also
going
to
try
and
do
my
first
good
PR
against
UX
text.
So
I
may
be
pinging
a
couple.
People
for
help.
Just
okay
I'll,
also
look
at
the
in-store
pickup
for
to
make
sure
that
we're
we're
using
the
same
terminology
of
active
versus
enabled
across
everything.
So
we
don't
confuse
users.
I
One
more
really
quick,
maybe
as
a
question
for
Rick,
so
I
saw
the
one
that
you
showed
on
the
b2b
items,
which
is
great,
that
was
number
eighteen
and
a
one
eight
to
eight.
There
is
a
separate
issue
as
well
one
eight
to
three,
which
is
also
related
to
b2b,
for
making
msi
compatible
with
requisition
lists.
I,
don't
know
if
that
has
something
was
something
that
you
had
seen,
but
you
know
we'll
need
to
pick
it
up
at
at
some
point.