►
From YouTube: Magento MSI Open Demo. April 13, 2018
Description
- MSI current after regression @iminiailo
- Modularity. Exclude UI part from Business logic, make it possible to work with inventory in a headless way @mikola.malevanec
- Store Order Information into the Reservation to provide possibility easily track Inventory deduction @aleron75
A
A
So
we
don't
the
for
today's
demo
and
the
main
reason
for
that
that,
at
the
end
of
previous
week,
we
merged
most
of
the
functionality
in
our
main
line
and
the
last
big
pull
request
was
devoted
for
the
source,
deduction
mechanism
and
shipment
creation
and
I
want
at
the
beginning
of
this
week.
We
around
the
progression
and
in
the
scope
of
this
regression,
we
created
some
issues.
All
those
issues
are
marked
with
regression
of
phase
one
label.
B
A
Of
that
issue
will
go
to
the
milestone.
Some
of
them
are
critical
for
for
first
release
and
would
be
would
be
fixed
right
after
the
regression
finish.
So
we
can
say
that
today,
regression
finished,
and
we
already
have
this
result
and
we'll
start
to
proceed,
fixing
the
bugs
so
there's
a
good
new
news
for
community,
because
we
have
quite
a
lot
of
pretty
independent
features.
A
So
we
have
quite
a
lot
of
guys
from
community
like
bug
hunters
who
have
quite
the
limited
time
and
they
can
participate
in
the
bug
fixing
for
after
after
our
regression
phase
one.
So
those
of
you
who
listened
in
the
demo
or
watching
or
we
will
watch
it
later-
you
can
just
make
a
filter
by
regression
phase
one
and
assign
ticket
to
yourself
and
proceed.
Miss
ticket
execution,
so
tomorrow
is
going
to
be
another
contribution
day
and
I
know
that
it
might
be
my
sidetrack
there.
A
This
is
probably
all
regarding
the
regarding
the
regression,
but
along
with
regression,
we
also
started
implementation
of
two
news
stories,
and
these
stories
are
not
finished
yet,
but
we
will
demonstrate
you
the
current
update
regarding
this
story.
So
I'm
stop
sharing
my
screen
and
the
nickel.
I
will
will
make
a
presentation
of
his
part.
C
Hi
guys
so,
as
Tigger
said
not
today,
we
have
started
our
work
on
separation
of
business
logic
from
present
presentation
layer
in
MSI
yeah.
Unfortunately,
there
is
nothing
to
show
you
from
the
user
perspective,
as
there
is
no
changes
at
least
yet,
and
everything
worked
the
same
way
as
it
did,
and
we
can
already
show
all
UI
Petros
on
previous
demos
yeah,
but
from
the
code
perspective
there
will
be
a
lot
of
changes
and
we
already
made
some
tangible
progress
and
more
to
come
so
yeah.
C
Why
are
we
doing
this
in
the
in
this
separation?
Of
course,
now,
first
of
all,
we
you
want
to
make
an
assignment
flexible
from
perspective
of
development,
at
ability
to
run
magenta
with
an
assign
in
headless
way,
make
MSI
models
as
much
independent
as
possible,
and
also
like
more
specific
that
every
module
does
only
its
specific
job
we
delegate
with
so
yeah.
At
this
moment,
we
we
have
to
pull
request
created,
which
separate
logic
for
inland
drink,
italic.
B
C
C
Yes,
multi
no
see
we
are
testing
all
your
features
be
introduced
in
MSI
on
your
rearranged
code
to
make
sure
that
continue
to
work
as
expected,
and
then
we
we
planning
to
write
web
app.
The
functional
tests,
which
will
be
able
to
buy
different
types
of
products
create
and
processing
orders
and
invoices.
C
Also,
they
should
be
able
to
use
our
source
selection
algorithm,
create
shipment
at
specific
warehouse
and
deaths
will
prove
that
we
can
use
all
MSI
features
without
using
UI
and
yeah
after
this
will
be
done,
we'll
be
able
to
confidently
say
that
MSI
can
work
in
headless
way
with
custom
UI
or
without
you,
I
atoll,
so
yeah.
There
is
plenty
of
work
to
be
done,
I
believe
that's
all
Thank.
A
D
D
Okay,
let
me
place
this
order
with
two
backs:
okay,
what
happens
now?
As
you
already
know,
every
order
places
some
reservations.
What
we
have
here
as
a
new
thing
is
the
metadata
column,
which
is
populated
with
some
information
about
the
event
that
we
call
the
sales
event
that
caused
the
reservation
to
be
placed.
So
in
particular,
we
have
order
placed
events,
and
we
also
want
to
track
the
object
and
the
idea
of
the
object
which
can
be
useful
in
in
this
particular
event.
D
D
We
have
to
do
some
some
refactoring
to
change
a
bit
of
things
to
do
this,
but
actually
it
seems
us
to
be
a
better
design
to
keep
the
data
about
the
order
that
caused
the
reservation
to
be
placed,
because
we
also
will
have
to
keep
track
of
the
deduction
the
reservation
about
the
duction
at
order
processing,
so
I
did
at
the
moment
we
will
have
the
ability
to
understand
that
the
same
order.
What
are
the
reservation
that
are
bound
to
the
same
up
from
front
end?
Point
of
view,
that's
all
as
useful.
D
D
Still
don't
know,
to
be
honest,
I
mean
this.
These
days
is
installed
because
we
realized
that
in
some
circumstances
it
was
very
difficult
also
for
developers
to
realize
what
was
going
on
with
the
data
that
is
stored,
I'm,
not
sure,
but
probably
this
data
will
be
used
in
some
way.
At
a
certain
point.
Okay,.
A
You're
correct
mark,
so
we
probably
can
make
maybe
in
the
future
our
clean
mechanism
which
clean
currently
cleans
the
reservation
little
bit
more
smarter
and
it
it
can
because
currently,
what
what
it
does
just
make
an
aggregation
by
by
stock
ID
and
s
cube.
And
if
the
total
quantity
is
zero.
Just
remove
all
the
reservation
form.
A
We
don't
clean
up
the
reservation
and
that
introduced
kind
of
manual
work
for
him
to
find
the
problem
and
taking
account
that
it
could
be
a
lot
of
reservation
and
the
reservation
before
this
did
not
have
any
reference
to
the
business
process
which
leads
to
this
reservation
and
gear.
So
it
would
not.
Even
it
would
not
even
possible
to
find
the
reason
why
the
quantities
grow.
So
now
heavens,
for
example,
now
we
at
the
time
of
the
reservation
placement.
B
A
The
time
of
the
product
is
assault.
We
place
a
reservation
with
reference
to
the
holder
and
when
the
product
is
shipped,
we
have
a
reservation
with
a
reference
to
the
same
order.
So
now
we
can
make
we
can
upgrade
our
cleaning
mechanism
to
clean
the
reservation
just
to
find
this
reservation,
which
much
each
other
based
on
the
on
the
same
port
authority,
and
that
makes
this
kind
of
clean
and
then
also
it
would
be
kind
of
developer
API.
D
Yeah
it
for
screw
it
some
more,
it's
more
developer,
side
implementation,
but
actually
we
don't
clear
as
a
vision
that
non-match
quantities.
So
if
something
goes
wrong,
we
don't
clear
reservation
and
in
the
reservation
we
have
at
least
something
in
the
metadata.
That
explains
what
originates
from
what
originates
that
reservation,
because
it
can
become
very
difficult
to
to
understand
once
we
have
a
lot
of
them
to
understand
what
originated
those
reservations.