►
From YouTube: MSI Open Demo. December 1, 2017
Description
1. Added configuration option for choosing between strong consistency and Eventual one. Presented by @Sinisa
2. Integration story. Deleting MSI source item when legacy CatalogInventory stock item has been deleted. Presented by @Sinisa
3. Product Import functionality. File format extended to support MSI data. Presented by @joshcarter
4. Inventory Configuration introduced. (used for Low Stock notification story). Presented by @Yaroslav Rogoza
A
C
B
B
Okay,
so
I
had
two
tickets,
one
of
the
tickets
were
was
well.
Both
tickets
were
related
to
synchronization
between
a
legacy
stock
and
MSI
inventory.
So
one
of
those
issues
was,
for
example,
when
we
have
to
when
we
delete
some
stock
item.
We
also
need
at
the
same
time,
to
trigger
deleting
in
the
MSI.
So.
B
B
A
A
D
D
D
D
D
A
Evidence
it
actually
it's
longer
now,
but
actually
in
each
initial
idea.
That,
like
currently
will
have
the
stock
item
in
the
Cadillac
inventory,
which
now
contains
too
many
information.
So
now
it
contains
the
stock
configuration
stock
item
configuration
and
the
stock
item
as
a
the
amount
of
some
particular
product
on
some
particular
stock.
A
So
actually
we
in
the
scope
of
the
MSI.
We
are
going
to
separate
the
data
to
different
entities
and
at
some
point
of
time
we
would
not
call
the
initial
stock
item
resource
model
at
all.
So
that's
actually
our
initial
case,
because
currently
we
we
are
starting
with
the
with
an
issue
which
sometimes
lead
to
circular
circular
dependency.
Circle
are
calling
because
we
need
to
support
both
umsi
tables,
update
and
the
old
msi
table
and
all
cattle
inventory
tables
data
and
keeps
the
data
in
a
consistent
way
for
the
for
the
inventory.
D
B
And
yet
there
is
one
other
ticket
which
was
related
to
vice
versa
operation.
So
if
you
delete
source
item,
we
need
to
do
that.
We
need
to
delete
a
prop
a
stock
I
can,
but
that
one
is
not
completed
for
this
for
this
meeting.
So
it
will
be
for
the
next
time
that
so
here,
let
let's
back
here
so
I
am,
after
that
we
just
delete
source
items
and
in
order
to
to
test
this
I
create
integration
test.
B
B
B
D
B
B
Sorry,
that's
what
this
ticket
and
the
another
one
was
small,
it's
just
about
writing,
possibility
to
enable
enable
or
disable
synchronization
logic.
So
what's
one
thing
when
you
place
an
order
on
checkout,
we
need
to
add
reservation
and
also
we
need
to
update
our
catalog
inventory
tables,
our
legacy
tables,
which
may
reduce
performance
bottlenecks
at
some
point,
maybe-
and
also
there
are
some
stores
which
doesn't
need
catalog
imagery
to
be
strong
consistent.
B
B
B
B
B
B
E
Yeah,
hey
guys,
so
I
would
like
to
start
throwing
a
short
description
of
them
in
my
entire
configuration
module.
So
what?
What
is
this
module
about?
So
actually
in
the
legacy
elementary
functionality?
We
have
all
items
configuration
inside
of
long
tables
of
the
help.
Quantity
would
have
quarters
like
option.
We
have
modifies
the
quantity
or
everything
inside
one
table
in
terms
of
multi-source
inventory.
We
decided
to
create
a
separate
entity
for
the
items
stock
configuration
so.
E
For
example,
we
don't
need
to
create
if
different
entry
for
every
product
necessities,
the
database
entry
will
be
created
only
if
we
have
some
specific
configuration
for
some
product,
but
if
we
don't
have
a
specific
configuration
to
the
pole
integration
to
be
used
from
the
database.
So
we
are
working
on
this
functionality
at
that
moment
and
it's
almost
finished
also.
So
this
this
module
consists
of
like
the
solution
consists
of
two
modules.
E
The
first
one
is
the
inventory:
configuration
provides
resource
model
and
the
database
structure,
and
we
have
the
inventory
configuration
API
and
that
this
separate
extension
provides
entry
points
for
working
with
underwriters
configuration.
So
for
that
moment
we
have
three
interfaces.
300
points
for
removing.
E
E
In
case,
if
we
use,
for
example,
source
item
ID,
we
need
to
form
an
additional
joy
in
what
we're
getting
the
information
about
source
item
configuration.
But
if
we
have
source
ID,
we
can
have
just
a
single
request
single
database,
this
database
in
order
to
get
because
we
have
like
on
request
on
the
entry
point,
we
already
have
source
idea
almost
on
request.
That's
why,
and
previously
we
have
only
source
ID
as
well.
E
E
D
Okay,
thank
you
and
what's
what's
the
behavior
of
system
without,
if,
if
I
disable
this
point,
but
so
I
will
not
have
configuration
for
source
item.
In
that
case,
all
the
behavior
that
depends
on
configuration
should
be
implemented
with
plugins
or
observers.
Right
then,
let's
implement
it
now.
Yeah,
that's
correct.
Their
functionality
is.
E
E
A
Believe
it
would
be
implemented
in
a
dedicated
module,
so
the
configuration
supposed
to
be
just
just
a
configuration
and
all
the
business
functionality
which
use
this
country
supposed
to
be
any
dedicated
modules
and
correct.
As
air
Slav
said,
we
mainly
reason
why
we
introduce
inventory
configuration
now
is
because
we
have
the
low
stock
a
lot
of
notification
functionality
as
a
part
of
the
M
VB
and
low
stock
notification
supposed
to
work
on
the
level
of
soil,
though
we
would
have
most
notification
on
the
level
of
sources
and
on
the
level
of
stock.
Okay,.
D
E
C
E
C
D
One
more
comment:
I
have
it's
not
related
to
this.
This
looks
good.
Thank
you.
There
is
a
graphical
API
being
developed
for
storefront
now
and
I.
Think
it's
at
some
point
in
that
development
will
become
more
public,
but
for
now
with,
we
should
not
forget
to
synchronize
with
them
and
build
the
plants
of
integration
of
multi
source
information.
A
Yes,
and
actually
like
configuration,
would
be,
would
be
pretty
interesting,
pretty
interesting
part
for
the
integration,
because,
like
SES
loud
mentioned,
the
configuration
is
pretty
Park
because
currently,
all
the
configuration
are
gathered
together
under
the
hood
of
the
stock
item.
But
what
we
are
going
to
do
in
MSI,
you
know
a
desirable
stage.
We
are
going
to
separate
the
soul,
configuration
out
of
source
item
configuration
and
probably
out
of
the
stock
item
configuration.
A
So
currently
we
see
that
we
have
three
different
kinds
of
configuration
and
all
of
that
configuration
supposed
to
be
managed
by
dedicated
entities,
and
it
could
be
gather
it
all
together,
for
example,
using
the
graph
kill.
For
example,
it
could
be
possible
to
wear
it
with
a
graph
kill
with
one
query.
So,
yes,
that's
good
control,
I.
C
A
A
C
A
To
demonstrate
what
he's
done,
but
actually
he's
working
on
product
import
functionality
and
now
he's
adapting
the
the
format
of
the
quantity
found
to
support
multi
source
inventor.
So
we
got
this
request
from
mark
and
we
started
to
work
on
the
functionality
and
actually
it's
pretty
interesting
things
that
George
proposed
us
to,
because
in
this
proposal
in
this
story,
which
was
described
by
mark,
we
have
the
like
source,
2
equal
to
300
items
from
some
some
some
warehouse
and
the
first
3
the
source.
A
For
so
all
of
that
is
the
references
to
to
some
sources,
but
currently
in
our
source
interface,
we
don't
have
the
field
the
source
code.
So
all
we
have
currently
is
the
source
ID
and
the
source
name,
and
probably
it's
it's
better
for
us
to
introduce
the
source
code,
especially
taking
into
account
that
probably
data
for
the
inventory
would
be
would
be
synchronized
from
the
gear
system.
A
So
it's
not
so
good
to
rely
on
internal
magenta
identity,
especially
like
surrogate
identity,
which
is
also
incremented,
and
the
source
name
is
not
not
used
initially,
for
that
one
so
supposed
to
be
show
somewhere
on
admin
back-end.
So
probably
we
requested
this
change
to
mark
Linton,
but
mark
did
not
respond
yet
about
that
so
currently.
A
Currently,
we
will
provide
the
support
like
source
ID,
because
our
current
source
item
import/export
uses
for
source
item
IDs,
probably
also
we
had
the
conversation
with
Vadim
from
from
tech
division,
who
has
experience
working
with
integration
of
ERP
system
with
magenta,
so
he
was.
He
agreed
that
it's
much
better
to
use
some
source
code
here,
but
not
so
said
you
so
I
believe.
As
soon
as
we
will
get
a
response
from
mark,
we
will
will
add
the
source
source
code
to
our
source
interface.
A
The
source
item
interface
so
initially
did
the
work
Josh
is
involved
into
and
he
was
about
to
finish
this
story.
I
believe
he
will
have
an
ability
to
to
make
a
presentation
on
the
next
meeting
and
he
asked
me
to
say
sorry
because
he
had
some
urgent
affairs
and
he
had
to
he
had
that
ability
to
join
today
and
also
another
contributor
whose
Bartek
his
also
can't
draw.
In
today's
meeting
he
finished
two
to
pull
requests
regarding
the
migrating.
A
A
Medium
like
like,
look
and
feel,
and
the
demo
presentation
how
we
make
the
check
out
and
how
the
chip,
how
it
affects
the
all
day
tell
you
late
and
how
we
synchronize
data
data
between
storages,
so
Bartok
can
manage
to
attend
today's
meeting,
so
I
didn't
have
time
to
prepare
the
environment
to
demonstrate
so
I
believe
all
of
that
would
be
presented
next
time
and
yeah.
So
just
probably
all
for
today,
if
you
have
any
question,
please
ask.
A
A
Okay,
so
thank
you
for
your
participation
feel
free
to
ping
us
in
the
MSI's
like
channel
and
ask
any
question
by
the
way
we
already
got
several
new
question
from
new
guys
who
who
involves
who
start
following
the
msi
track.
So
there
are
pretty
interesting
thread
now
in
an
emesis
like
channel,
so
just
fewer
just
follow
the
dragon.
You'll
get
a
lot
of
interesting
updates
on
our
side.
So
thank
you
for
participation
and
see
you
soon.
All.