►
From YouTube: Magento MSI Open Demo. February 17, 2018
Description
Today’s agenda:
- @aleron75 Alessandro Ronchi - Interfaces renaming (DDD concepts), InventoryReservations module introduce
- @vz - Configurable product wizard (final state)
- @Yaroslav Rogoza - Low Stock Notification (final state)
A
So
hello
guys
today
is
Friday
and
this
usually
we
we
start
weekly,
msid
MO
and
according
to
our
agenda,
which
we
shared
recently,
we
will
show
you
the
really
really
fancy
stuff
which
we've
done
in
scope
of
the
DDD
changes,
which
was
asked
to
be
brought
to
the
MSA
by
Anton.
Creel
and
Alessandra
will
describe
the
status
of
these
changes
and
what
actually
had
been
done
by
him
so
Alessandra
feel
free
to
share
your
screen
and
make
presentations.
B
C
B
So
we
introduce
these
new
two
models:
inventory
reservations,
API
that
as
usual
as
usual,
has
the
definition
of
our
public
API
and
specifically
the
append
reservations,
interface
and
reservation
interface.
So
the
interface
describing
the
reservation
entity
and
some
concrete
implementation
of
all
concepts.
B
Probably,
first
of
all
the
and
reservation
command
implementation
and
all
the
accessories
that
we
have
in
the
scope
of
reservation,
so
clean
up
command
the
internal
API
to
get
reservation
quantity.
The
reservation
builder
and
NATO
cannot
case
converted,
which
is
used
in
scope
of
reservation,
so
I
moved
it
in
this
module
as
well.
B
D
B
Will
have
to
maintain
consistency
of
data
from
the
application
point
of
view,
so
I
already
created
an
issue
and
assign
it
to
me
to
guarantee
that
data
will
be
consistent.
Consistent
at
the
application
level
was
getting
reading.
Getting
rid
of
these
foreign
key
from
the
reservation
table
doesn't
guarantee
anymore
that
if
I,
for
example,
remove
a
stock
I
can
have
reservation
pointing
to
that
stock.
So
this
can
lead
to
errors,
and
we
have
to
avoid
this
kind
of
problems.
B
C
E
A
C
B
A
Wanted
to
add
a
couple
of
words
for
the
presentation
of
Alessandra.
As
he
mentioned,
we
introduced
not
just
inventory
reservation
into
a
dedicated
module,
but
also
introduced
inventory
reservation
API,
so
that
will
provide
the
same
ability,
for
example,
to
substitute
undo
iron
adapter.
So
the
transport
layer
for
the
reservation,
because
out
of
the
box,
will
provide
the
my
sequel,
but
potentially
we
can
replace
it
with
rabbit
in
queue
or
maybe
Redis.
So
it
would
be
little
bit
faster
than
my
sickle
table.
So
we
segregated
API
out
of
the
implementation.
E
A
Okay,
thank
you.
Thank
you.
Thank
you
very
much.
Alessandra
stop
sharing,
so
the
next
one
would
be
volodymyr
sighs
who
helped
us
to
prepare,
Zach
and
prepare
and
adopt
the
configurable
product
wizard,
because
we
have
quite
quite
a
big
UI
wizard
for
the
configurable
product
and
it's
manageable,
depending
on
how
the
configurable
product
is
being
created.
So
while
the
dimmer
feel
free
to
to
share
your
screen
and
show
how
the
configurable
product
will
look
like
when
the
msi
would
be
merged
to
the
magenta.
F
F
F
F
G
Can
you
confirm
that
what
is
expected
is
when
you
see
this
light
out
panel,
only
the
ones
that
can
be
added
will
show.
So,
if
you
have
in
this
case
there
was
11
sources,
you
showed
all
of
them
and
removed
one.
When
you
open
the
slide
out,
you
would
expect
to
see
only
the
one
available
to
be
edit
yeah.
F
G
H
G
G
So
the
question
was
two
things
so
on
this
tooltip:
that's
showing
on
your
screen
right
now,
that's
great,
but
it's
not
clear
to
me
that
I
would
know.
I
can
click
on
it
because
it
just
seems
to
be
regular
text,
so
we'll
probably
need
to
check
with
Eugene
on
that,
whether
there's
an
icon
or
something
that
allows
the
user
to
know
they
can
it's
clickable
I.
G
F
G
F
F
E
E
F
A
I
I
So
at
the
moment
we
have
four
products
in
catalog
and
let
me
show
so
some
of
them
are
low
stock
and
some
of
them
are
not.
For
example,
if
we
check
some
product
we
have
a
possibility
to
in
this
grid
where
we
assign
sources
to
the
product.
We
have
a
possibility
to
to
put
the
quantity
to
current
counted
here
of
this
product
and
put
the
35.
I
I
B
Just
an
idea
suggestion
to
to
to
everyone
in
the
low
stock
report
we
have
the
column
named
stock
quantity,
and
there
is
this
problem
related
to
the
fact
that
stock
is
an
entity
in
multi-source
inventory,
which
is
a
precise
meaning,
so
maybe
I
would
suggest
to
to
name
it
quantity,
not
stop.
Quantity,
I
got
a
girl.
We
discussed
a
lot
about
this
ambiguity,
so
I
think
that
we
should
avoid
using
words
stock
when
it
doesn't
refer
to
what
stock
is
in
multi-source
inventory,
which
is
the
application
of
multiple
sources
and.
A
E
B
E
G
Yeah,
it's
interesting
because
this
is
a
traditional
name
of
the
report.
The
merchants
know
to
look
for
yeah
in
stock
is
a
general
way
that
they
speak
of
the
inventory
that
they
have,
but
yeah
I
don't
want
confusion.
I
think
low
quantity
report
would
be
fine.
It
would
eliminate
any
chance
for
confusion
in
the
written.
The
report
names.
G
K
A
J
J
I
do
have
sources
for
the
content
and
I've
gone
with
the
talk
with
the
other
riders
about
the
architecture
of
the
content
worth
what
what
document
units
is
going
to
go
into
I've
started,
creating
a
document
plan,
that's
mainly
for
use
internally
with
the
riot,
the
other
riders
and
I've
created
a
couple
of
tickets.
So
that's
about
when
I,
where
I'm
at
now.
C
Okay
cool
so
last
week,
I
didn't
know
the
test
they
actually
got
created
this
week.
I
will
turn
distracted
for
MF
t
fo
I
don't
have
much
draw
today.
We've
ends
and
hub.
If
you're
interested
in
the
official
list
of
the
actual
eight
tests
that
have
been
created
so
far
put
inside,
you
can
check
out
sorry
five
one
two.
They
have
links
the
actual
repo
in
which
these
guys
are
committed
to.
C
Currently
they
have
not
been
pushed
to
the
inner
thigh
Rico
because
they
are
dependent
on
a
pending
code
review
that
is
open
for
the
Magento
to
see
a
penguin
test,
repos
that
will
eventually
emerge
and
then
sync
over
images.
For
so
once
this
is
done,
then
I
can't
officially
open
up
PR
for
a
messiah
zone
and
the
actual
tests
themselves
are
in
the
branch.
I
have
a
782
and
I
am
a
PS
test
hitches.
So
there
are
a
test
checked
in
here
once
the
other
changes
are
synced
up.
Let's
show
these
off
officially.
D
C
Done
for
this
week,
actually
working
on
story,
5,
4
2,
which
was
the
documentation
for
tension
developers
I'm
going
to
create
a
github
with
the
entry
in
the
MSI
repo
under
our
lovely
wiki.
Here
it
will
eventually
be
under
number
six
here,
so
it
should
be
number
seven
and
show
you
what
it
looks
like
locally.
C
So
here
will
be
the
new
section.
We
have
enough
Tia
test
tensions
of
getting
started.
Information
will
have
where
you
can
find
I
test
a
food.
What
to
do
with
this
is
have
instructions
where
to
action
story
test
how
to
reference
them
in
inept
yeah.
How
to
keep
them
and
I
will
have
several
tips
and
tricks.
That
is
all
a
giant
work
in
progress.
As
you
can
see
here,
I'll
have
I,
have
a
link.
J
C
The
top
of
this
talk,
which
will
lead
to
our
standard
MF
Jia
Devdas
team,
has
worked
very
hard
on,
and
this
wiki
entry
will
basically
a
synopsis
of
all
of
our
Devdas
and
has
edited
specifically
to
finish
my
project
they're.
All
the
unified
tested
information
located
in
there
so
to
be
very,
very
much
successful.
I
to
us
once
this
is
all
created
and
done.
C
J
E
C
J
C
A
Us,
if
no,
please
raise
any
question
in
the
Mathias
like
channel,
which
already
quite
a
big
team
here.
So
you
see
there
are
like
MF
Kiev
guy.
We
have
a
technical
writer
on
board,
we
have
a
product
owner,
we
have
a
few
developers
and
an
architect,
so
we
have
a
pretty
big
team
now,
so
you
can
ask
any
question
in
a
slag
chat
and
we
will
try
to
facilitate
the
question
and
the
difference,
if
add
an
answer.
So
since
you
everybody
for
your
time,
thank
you
for
your
presentations
and
see
you
soon
guys
and.