►
From YouTube: Magento MSI Open Demo. April 26, 2019
Description
Agenda:
* Reservations CLI updates: Improved compensations, Command piping @vadimjustus
* Store Pickup updates @Aleksandr
* Bugfixes for 1.1.2 @Vitalii Boiko
* Huge Documentation Update @Lori Krell
* MSI Quality status by @Tom Erskine
* 1.1.2 Release update @ishakhsuvarov
A
Today
we
have
some
really
interesting
updates,
specifically
the
ones
which
are
happening
in
the
scope
of
upcoming
MSI
one
one
to
release
two
we'll
be
talking
about
some
of
the
earth
which
will
be
delivered
in
the
release
and
the
documentation
and
the
processes
update
do
quite
a
lot
of
stuff.
To
start
with,
I
was
hoping
that
body
would
be
the
first
to
demonstrate
the
CLI
command
today,
but
she's,
not
answering
me
on
slack,
so
I
hope.
You've
all
answered
me
right
now.
Yes,
I
am
Indian.
B
B
What
I
did
the
last
a
couple
of
weeks
with
MSI
is
first
of
all
implement
this
command,
which
just
lists
all
the
inconsistencies
we
have
regarding
reservations
and
the
command
create
compensations,
which
should
which,
which
is
a
manual
opportunity
to
to
add
reservations
which
are
currently
missing,
and
so
in
order
to
compensate
the
saleable
quantities,
so
I
have
I
displayed
here.
The
current
help
of
above
commands,
probably
I,
should
also
say
this
one
was
there
before
I
started.
Also
we
changed
a
little
bit
and
refactored
it
since
we
needed
this
information
also
for
reservations.
B
So,
but
how
does
it
work?
First
of
all,
why
why
do
we
have
probably
inconsistencies
with
reservations?
There
are
a
couple
of
scenarios
when
this
could
happen.
One
of
I
think
typical
one
could
be
if
merchant
is
switching
from
Magento
to
two
to
Magento
two
point
three,
so
he's
start
using
MSI
and
probably
there
are
already
orders
there
which
are
not
completed
yet,
and
reservations
came
now
new
to
the
to
the
system.
B
So
this
was
a
way
this
disorders
will
be
compensated
when,
for
example,
shipments
will
be
done
or
order
will
be
canceled,
but
there
wasn't
an
initial
reservation
for
the
amount
amount
which
was
sailed.
So
therefore,
we
need
to
compensate
it
or
also
a
scenario
if
we
just
switching
from
defaults,
sewers
or
a
default
stock
to
a
MSI
stock,
or
also
if
we
switch
the
stock
for
income.
B
So
what
we
did
I
have
now
in
my
database.
Some
inconsistencies,
which
I
made
by
just
deleting
some
reservations
from
the
database
directly
and
the
list
command.
This
place
are
all
detected
inconsistencies
which
we
have.
We
have
also
a
roll
option
there
in
order
to
return
more
machine,
readable
information,
and
this
is
what
we
also
using
in
order
to
pipe
both
commands
with
each
other
in
order
to
compensate
directly
from
from
this
list
into
our
compensation
command.
B
B
C
C
B
C
B
D
B
C
C
B
C
B
B
D
B
D
B
B
B
B
C
Actually,
by
design
behavior
I,
don't
think
that
we're
gonna
gonna
change
it
any
anyhow,
because
we're
supposed
to
fulfill
the
order
based
on
the
current
assignment,
but
not
based
on
the
assignment
in
previous,
because
the
previous
assignment
may
not
be
actual
anymore,
and
maybe
the
previous
stock
wouldn't
be,
could
not
even
exist
at
the
time
when
the
warden
fulfilled.
So.
B
Yeah
and
yes
also
currently,
we
differ
between
completed
and
not
completed
orders,
but
the
the
reservations
might
be
already
compensated,
even
a
completely
compensated,
even
if
the
order
is
not
completed
yet,
but
it's
completely
shipped,
so
it's
also
difficult
to
to
to
match.
So
probably
we
need
to
defer
between
tripped
and
not
shipped
and
not
not
between
completed
and
not
completed,
but
I.
B
So
we
I
think
we
just
need
to
switch
complete
with
shipped
or
or
even
stick
to
the
to
the
order
item
quantities.
So
we
we
have
a
count
here.
How
many
was
ordered,
how
many
were
shipped,
how
many
was
canceled
and
so
on?
So
this
should
be
our
it.
This
is
the
source
of
true
for
the
for
the
compensation
and.
D
C
B
C
We
can't
determine
whether
we
have
some
inconsistency
in
the
scope
of
the
order
until
we
have
the
order
in
the
completed
canceled
or
closed
status,
that
we
can
do
it.
Let's
say
earlier
like
based
on
the
based
on
the
fact
whether
whether
like
one
day,
you
was
fully
compensated
in
the
scope
of
shipment
or,
if
found
yeah,.
B
I
think
we
don't
need
to
stick
on
on
the
order
status,
but
only
on
the
on
the
item
item
quantities.
So
we
can
still
see
how
many
items
are
not
fulfilled,
how
which
which
quantity
per
item
in
order
is
still
not
fulfilled
in
any
way
as
a
weather
concerned
cancelled
or
or
shipped
or
anything
else,
and
there
are
therefore
we
know
how
many
still
need
to
be
resurrected
in
our
database.
D
C
That,
in
even
now,
when
we
rely
on
the
light
of
the
complete
status
of
the
order,
I
believe
for
most
of
the
motion.
That
would
be
pretty
sufficient,
because
even
so
merchants
can,
even
so
that,
like
he,
for
example,
identify
the
inconsistency
earlier.
But
he
still
can
like
complete
the
order
and
then
over
to
will
find
that
inconsistent.
C
A
Thank
you
very
much
Vadim.
This
was
a
great
presentation
and
I
just
want
to
remind
that.
All
of
this
work
will
be
available
in
the
scope
of
one
one
to
release
so
everything,
but
iam
has
demonstrated
that
at
this
point
is
already
like
going
to
packaging,
so
merchants
will
be
able
to
use
it
really
soon.
So
next
on
the
agenda
is
I
believe
is
Alexander.
Who
is
going
to
provide
some
of
the
updates
regarding
the
store
pick
up
track?
What
we
can
expect
in
the
following
weeks.
E
Hello
guys
Oh
British
short
update
about
in-store
pickup
track
the
previous
week
the
current
week.
We
was
not
know,
as
so
many
our
time
to
this
topic,
but
I
want
to
share
what
we
are
going
to
do
in
the
closest
future,
and
so
there
was
at
least
three
issues
which
we
still
need
for
based
implementation
of
the
store,
pickup
right
and
we
are
going
to
do
it
in
psychosis
tweaks.
So
first
one
is
at
pickup
location
attributes
to
the
source
entity.
E
Second,
one
is
adjust
our
source
selection
algorithm
using
store,
pickup
orders
and
the
last
one
is
secret,
finally
create
and
point
for
a
pickup
location,
so
we
will
be
able
to
receive
them
and
also
news
that
we
have
the
video
found
person
who
is
ready
to
help
us
with
in-store
pickup
fermentation
on
front-end,
and
hopefully
he
will
start
help
us
from
the
next
week.
Oh
I
think
it
is
it.
Thank
you
for
attention.
E
F
A
Thank
You
Alexander,
ok,
so
the
next
on
the
agenda
is
vitally
vitally
he's
been
working
on
multiple
bug
fixes
during
the
last
few
weeks.
Actually
Vitalik
has
done
like
two
bug
fixes
in
contribution
day
in
kiev
and
then
joins
one
more
pretty
complicated
issue
and
helped
fixing
it
as
well.
So
the
stage
is
yours.
Please
show
us
what
you
have
done.
F
C
F
Thank
you,
so
both
bark
fixes
was
related
to
shipment
process
and
source
selection
algorithm
in
one
issue.
Guy
cannot
create
shipment
and
issue
caused
by
like
enable
at
source
source
selection,
algorithm
or
order
which
decide
disable
inventory,
which
is
you
know,
so
in
order
to
fix
it.
I've
disabled
source,
reflection
of
the
read
for
such
orders
I
create
kind
of
dedicated
service
which
takes
all
order,
items
and
check
them
for
stock,
manageable,
manageability,
let's
say
and
then
use
a
service
in
all
need.
Advice
applies
a
other
issue.
F
Was
related
to
configure
abroad
product
so
as
soon
as
you
know,
configure
product
I
believe
yeah
configurable
product
and
configure
risk
on
this
and
figure
custom
options,
so
customizations
for
such
products
has
like
generated
that's.
Why
is
this
SKU
and
not
start?
Let's
say
the
England
3
for
such
a
skill
not
be
in
town
but
on
the
source
or
selection.
Algorithm
is
speech.
F
With
a
Magento
tend
to
find
this
this
product
in
sources-
and
this
leads
to
the
issue-
so
the
implementation
was
quite
straightforward-
I
just
check
if
the
product
configurable
and
get
positive
for
this
product
actual
SKU.
So,
let's
jump
into
the
Magento
admin
I
have
here
prepared
orders
for
both
cases.
F
F
A
D
So
I
know
it's:
it's
been
probably
a
while,
since
we've
had
a
lot
of
documentation
updates,
but
we
have
a
bunch
or
two
three
two.
So,
as
we
kind
of
just
went
over
with
the
deem
the
CLI
new
references,
I've
gone
ahead
and
we've
created
a
CLI
reference
section.
We
also
moved
the
geo
code
information
for
that
CLI.
So,
as
we
continue
to
add
commands,
we
can
continue
building
this
reference
now.
D
At
the
same
time,
and
just
through
the
demo,
I
was
able
to
add
a
couple
of
nice
little
additions
like
the
event
type
being
a
manual
compensation,
and
each
of
these
has
descriptions
of
the
options,
shows
the
commands
and
also
provides
some
example
responses
based
on
what
what
how
those
work
out,
we
also
have,
as
you
will
notice,
a
ton
of
brand-new
diagrams
and
cons.
So
this
is
the
updated
content,
that's
in
the
user
guides.
D
That,
of
course,
will
not
be
going
out
till
two
threes
live
and
if
you
know
because
I
love
you
all
it's
also
over
in
all
of
over
in
here
you're
going
to
notice
all
the
diagrams
have
been
updated
with
new,
cleaner
diagrams
ones
that
deal
with
resources,
have
a
bit
more
information
and
are
far
more
clear.
I
also
updated
all
of
the
content
around
reservations
throughout
the
wiki
and
the
user
guides.
D
D
It's
also
in
the
other
user
guide
continent,
along
with
little
notes
and
updates
throughout
based
on
all
of
our
bug,
fixes
and
updates
43,
and
then
these
are
the
new
looking
release
notes
if
you
haven't
looked
at
them
recently
on
dev
Doc's,
we're
starting
to
kind
of
provide
icons
and
information
to
show
what's
coming
and
we're
also
going
to
have
like
a
new
icon
for
known
issues.
This
is
all
kind
of
provided
throughout
in
hidden
in
the
code.
Also,
we
keep
track
of
every
PR,
an
issue
that
are
related
with
each
of
these.
D
So
all
the
information
has
been
provided
for
1
1
2
from
acai,
including
all
of
the
information
for
updating
and
upgrading
in
here,
including
all
of
the
list
of
new
modules
that
have
been
created.
We
have
a
new
graph,
QL
module,
there's
also
the
CLI
modules
for
reservations
and
a
few
others
for
the
legacy
alignment
that
we
added,
which
are
also
in
rem
pinging
around
my
apologies.
D
In
the
wiki,
you
can
also
go
to
the
MSI
release,
notes
and
installation
and
find
all
of
the
updates
there
as
well
I'll
keep
both
of
our
internal
content,
which
will
be
ready
for
publish
23:2
publishes
as
well
as
the
wiki.
In
sync.
That
way,
you
get
a
preview
of
everything,
that's
going
to
come
out
and
you
don't
have
to
wait
so
it'll
always
be
there,
including
some
links
that
may
go
to
internal
content
to
the
wiki
and
those
will
get
updated
later
and
finally,
let's
see
we
also
documented
the
bulk
trend
transfer
API.
D
We
also
don't
have
it
to
preview,
but
we
documented
the
new
graph
QL
attributes
that
have
been
added
to
support
MSI
orders
as
well
and
I,
think
yeah,
where
all
of
that
and
then
the
next
item
that
will
be
tackled
today,
will
be
getting
@pr
ready
for
the
amazing
information.
I
were
provided
on
the
Magento
MSI
api's.
So
if
you
want
to
look
at
it
now
that
was
linked
in
slack
and
it
will
also
be
put
into
the
dev
Doc's
drafting
will
be
starting
today.
There's
a
ton
of
updates
to
make
it
simple.
C
As
usual,
and
probably
even
better
than
you
because,
like
this
is
exactly
like
very
cool
that
we
have
to
version
like
one
of
kind
of
official
on
a
deaf
dogs
and
one
on
a
Massiah
wiki,
because
probably
we
will
proceed
with
publish
some
better
package
before
even
before
the
official
magenta,
to
decided
to
release,
so
that
is
very
cool.
That
people
who
would
be
like
an
early
adopters
can
see
what
what
exactly
release
and
they
can
follow
the
documentation
not
on
the
official
place,
but
on
the
msi
wiki.
So
this
is
this
is
awesome.
C
A
G
D
G
April
26,
what
we're
looking
at
here
in
terms
of
our
snapshot,
then,
is
obviously
to
release.
So
we
talked
about
last
week
was
a
refocus
on
MFT,
F
coverage
and,
and
we've
done
that,
so
we
added
three
new
tests.
Last
week,
we've
also
added
three
new
turf
this
week,
and
this
is
all
net
new
testing
things
that
haven't
been
previously
covered
by
functional
automation
and
that's
finishing
off
credit
memo,
memo
scenarios
and
but
also
doing
some
really
foundational
work
in
order
products
things
we
had
not
covered
in
customer
flows.
G
G
That's
six
number
three
plus
three
up
to
something
more
like
it
or
tan,
but
during
the
week,
there's
also
being
it
existing
tasks
which
have
been
refactored
for
some
minor
fixes,
but
also
managed
to
improve
testability
and
those
making
them
more
repeatable,
less
flaky,
much
more
reliable
in
our
bills
as
well,
so
their
husband,
some
sort
of
maintenance
work
done
there
as
well,
but,
like
I,
said
last
week,
we
wonder,
focus
on
MF
TF,
a
little
we've
put
some
numbers
up
and
we're
gonna
try
and
continue
that
going
forward.
You'll
see
in
the
numbers.
G
We
also
increased
our
manual
task
coverage
by
twenty
five
soar
up
from
six
twenty
five
to
six
fifty
full
tests
and
to
find
in
head
test
for
our
coverage
position.
Otherwise,
looking
out
our
issues
and
bugs
created,
so
we
opened
within
the
last
seven
days.
We
opened
seven
issues
closed
three,
if
you
just
focusing
on
those
that
are
bugs
one
open
one
currently
open
still,
albeit
that
was
open
within
the
last
24
hours
by
Slava,
and
it's
table
inventory,
you
sealable
quantities,
not
quite
working
without
a
stock
22:04
very
recent.
G
G
That
can
be
automated,
otherwise,
no
further
change
in
terms
of
severity
and
component.
The
tests
are
in
conceals
manual,
testing
no
updates,
since
our
full
regression
cycle
will
have
more
amount
where
we
get
another
regression
side,
we
have
any
quality
questions.
Otherwise,
that
is
your
weeks.
Quality.
A
A
A
Yep
also,
we
are
looking
for
a
small
update
on
the
branching
strategy.
I
think
we'll
be
decoupling
from
the
Magento
slike
core
Magento
version
in
strategy
will
be
abandoning
branch
as
two
point
three
and
two
point
three
point:
zero,
because
well,
MSI
is
not
really
related
to
those
and
will
be
starting
to
use.
Something
like
like.
A
Maybe
one
develop
and
one
release
which
would
commence
Akali
correspond
to
the
MSI
version,
though
this
is
pretty
much
it
I
guess,
maybe
maybe
your
has
something
to
update
I'm,
not
sure
no
I,
don't
you
and
then
thank
you
very
much
guys.
Thank
you
for
joining.
It
was
pleasure
having
you
all
today
and
we've
had
lots
of
useful
information.