►
From YouTube: Magento MSI Open Demo. July 20, 2018
Description
Agenda:
Today’s Agenda:
1. Finalization of Backlog for Milestone 2
2. Support Negative Threshold for Backorder functionality
3. Bug fixing
4. Mass Inventory action (re-assign Source Items from/to different sources) Proof of Concept
5. Backorder configuration on Source and Stock levels. Support drop shipping allowing create shipment with negative SourceItem Quantity
A
Hello,
let's
start
Friday,
and
you
probably
already
used
to
that
this
time
we
usually
have
magenta
magenta
emicida
mounatin,
and
today
we
have
quite
a
lot
of
quite
a
lot
of
topics
to
share
with
you.
Let
me
share
my
screen
and
I've
already
shared
agenda
in
the
Messiah
channel.
So
let's
start,
let's
let
let's
hold
the
agenda,
so
the
first
item
in
the
agenda
is
definitely
a
foundation
of
the
backlog
for
milestones.
A
So,
as
you
know,
we
had
grooming
meetings
during
general
last
two
weeks
and
we
were
discussing,
we
groomed
the
different
stories,
an
epic
which
we
currently
have
an
product
backlog,
so
the
product
backlog,
reachable
by
by
the
sink
MSI
roadmap,
we're
going
to
find
it
as
the
second.
The
second
link
from
the
in
the
right
panel
and.
A
A
We
will
start
our
our
sprint
officially
from
from
Mundi
from
next
Monday,
and
we
supposed
to
finish
it
with
the
visitor
at
the
first
of
September
this
actually,
the
finalized
backlog
also
I,
will
share
with
you
some
architectural
update
at
the
end
of
this
meeting,
but
that's
all
regarding
the
standardization.
Also.
There
is
pretty
good
news
that
we
finally
run
all
our
MFCs
tests
on
Jenkins
and
we
managed
to
make
them
green.
We
managed
to
get
green
build.
A
So
since
now
we
have
a
green
built
with
with
50
scenarios,
so0
scenarios
and
this
build
will
be
helping
us
for
management
for
management
managing
all-father.
Pork
has
created
for
MSI
project,
so
this
all
regarding
the
finalization
of
chromium
status
and
the
next
one
gonna
be
Alessandra.
Who
will
demonstrate
you
actually
already
implemented
story
for
negative
threshold
support
for
backorder
functionality?
B
B
B
B
B
A
D
C
E
E
A
E
E
F
E
F
E
E
A
D
We
had
problems
that
you
may
edit
source
code,
and
actually
you
not
edited,
but
you
when
you
edit
existing
source
code
to
you,
creating
new
source
called
new
source
with
new
code,
but
this
bug
fixing
is
disabling
it,
and
now
you
may
see
that
everything
is
working
after
you
say
it
once
your
new
source.
The
code
is
not
editable
anymore.
A
We
fix
this
issue
because
we
know
not
far
from
one
of
the
contributors
created
a
tickle,
so
I
just
share
this
ticket
in
the
chat
for
the
zoom
control,
and
there
is
some
kind
of
misunderstanding
because
on
an
aside
project,
we
usually
we
use
natural
identities
for
most
of
the
entities
and
one
of
them
is
a
source.
So
we
have
a
source
code
and
we
don't
have
the
database-generated
ID
for
this
entity
and
that's
why?
A
Actually,
it
is
not
possible
to
update
the
nature
of
identity,
because
in
the
emergent
we
don't
have
CrossFit
of
the
LSD
and
it
has
the
same
operation
actually
the
same
for
creation
and
update
entity.
That's
why
what
we
would
be
managed
to
have
managed
to
fix.
We
just
don't
provide
an
ability
to
edit
entity
on
on
UI
level.
A
H
Okay,
you
should
sit
my
screen,
okay,
so
basically,
in
the
one
of
our
last
meeting,
we
decided
to
slightly
change
the
behavior
of
the
mass
transfer
inventory
to
source
that
previously
was
basically
taking
multiple
sources
and
migrating
all
the
quantities
from
this
assist
to
another
source.
So
we
decided
to
slightly
change
by
letting
the
user
to
choose
the
origin
source
the
destination
source.
H
So
basically,
if
I
select
to
one
or
more
products
and
I
select
transfer
inventory
to
source
now,
I
am
I
have
to
choose
what
is
the
origin
source
so
it,
for
example,
if
I
want
to
transfer
from
the
test
source
to
the
default
source.
I
can
do
this
way
and
make
them
enter
it
faster
and,
of
course,
it's
a
pie
to
all
the
products.
I
selected
I
still
have
some
issue
on
the
default
stock
indexing,
but
I'm
working
on
that
and
plus.
We
also
decided
to
add
this
other
feature.
H
You
probably
noticed
before
that
is
transfer
and
then
unassigned
from
source.
So,
basically,
I
can,
for
example,
transfer
the
quantity
from
the
full
source
to
that
source
unassigned
of
the
products
from
the
origin
source,
and
we
can
do
this,
as
you
may
see,
the
full
source
is
basically
removed
from
the
assignment
and
not
the
point.
It
is
transferred
to
the
to
the
destination
source
plus.
H
We
also
decided
to
warn
the
user
while
using
the
unassign
from
event
resource
so
because,
when
we
unassign
one
product
to
one
source,
we
basically
remove
all
the
product
of
the
quantities
of
the
products
in
a
permanent
in
a
permanent
way,
and
we
decided
just
to
add
this
morning-
and
this
is
with
all
the
main
changes
I
applied.
This
to
this
feature.
C
Have
any
question
yeah?
Thank
you
just
one
question
on
the
transfer
itself.
So
if
we
have
an
item,
that's
in
multiple
sources
and
we
do
the
last
option
and
they
show
their
the
transfer
to
another
one
assume
it's
only
going
to
move
from
the
one
that
you
input
in
the
drop
down.
I
just
wanted
to
confirm,
meaning
if
the
product
is
on.
If
a
product
is
on
three
sources
and
you
click
on
transfer
and
you
select
one
of
those
sources,
then
the
other
two
will
not
be
affected.
A
H
H
C
H
A
C
I
A
E
E
Please
remind
me
what
was
what's
an
effect
so
when
you
have
seen
single
source,
you
are
in
single
source
mode,
and
so
we
have
single
source.
You
have
single
stock
on
single
website
and
then
you
add
additional
source.
What
what
happens
currently
in
Magento
so
I
understand
that
this
feature
is
to
migrate
products
from
between
sources
right.
What
happens
today,
if
you,
if
you
add
one
more
source,
if.
C
E
But
what
what
what
was
the
scenario
that
we
are
fixing
like?
So
if
you
add,
if
you
add
one
more
source
and
one
more
stock
right
and
start
adding
products
to
that
to
that
source,
what's
the
behavior
today,
why
do
I
think
the
behavior?
Is
that
you
cannot?
You
cannot
assign
that
yeah.
You
cannot
assign
that
new
source
to
default
stock
right
yeah.
E
Okay,
understood
so,
of
course,
this
fix.
It
makes
it
much
easier,
think,
adjust
we
have
to
emphasize
it
in
documentation
and
explain
why?
Because
the
scenario?
It's
not
very
intuitive
that
if
you
as
we
discussed
multiple
times
before,
if
you
add
a
source,
you
cannot
link
it
to
default
stock
and
stuff.
H
A
So
this
is
a
game
question,
a
question
about
the
pad
for
their
functionality
and
how
we
supposed
to
treat
the
corner
configuration
because
in
pink
magenta
to
the
two,
so
in
a
single
stop
magenta,
which
wish
we
have
right
now.
All
this
talk
all
the
source,
all
actually
all
the
stop
deduction.
We
don't
have
such
a
such
a
term
like
a
sort
deduction.
All
the
stock
deduction
happen
at
the
time
of
the
order
placement
so
that
we
don't
have.
A
We
don't
manipulate
with
the
stock
quantity
at
the
time
of
invoicing
and
the
shipment
creation,
and
actually
that's
why,
even
if
you
created
the,
if
you
have
product
with
a
backorder
configuration,
you
can
place
an
order
and
you
will
get
your
stock
item
with
a
negative
quantity
and
after
that
you
can
create
a
shipment
for
this
stock
item.
So
this
is
how
it
works
in
magenta
this
how
it
works
in
magenta
work
right
now,
but
let's
see
how
it
works.
Work
from
MSI
for
this
purposes:
let's,
let's
open
this
product
and
specify
some
quantity
tweet.
A
So
it
was
out
of
stock,
let's
specify
some
quantity.
Yes,
there
are
some
reservation
already
created,
so
I
just
updated
the
quantity
and
we'll
have
the
sellable
quantity
recalculation
and
let's
see
what
the
saleable
quantities
available.
Quantity
now
are
115
and
let's
specify
that
we
allow
Corder
Sobek
portal
is
enabled
and.
A
Just
to
make
sure
that
they
don't
have
done
hella
stressful
for
the
backorder,
because
I
am
one
yet,
let's
specify
the
out
and
stop
stressful
to
zero.
So
if
you
specify
how
to
stop
stressful
to
zero,
we
would
consider
that
before
recorder,
functionality
works
as
it
worked
before.
So
we
have
the
infinite.
If
you
continue
quantity
of
product,
because
that
functionality
is
a
little
bit
changed
with
with
feature
implemented
by
alessandra,
because
before
that,
we
always
considered
that
if
the
before
functionality
is
enabled,
we
have
the
infinite
number
of
products
to
fulfill
the
orders.
A
A
A
A
A
So,
as
you
can
see,
there
are
300
items
and
taking
into
account
that
in
MSI
we,
along
with
the
stock
deduction,
will
have
the
sort
deduction.
So
the
Soros
deduction
supposed
to
happen
at
the
time
of
the
shipment
creation.
So
as
soon
as
I
will
I
will
click
the
submit
shipment
and
the
new
shipment
gonna
be
created,
and
in
the
scope
of
this
shipment
creation
we
will
make.
We
will
determine
the
source
from
which
we
need
to
make
a
sort
deduction.
A
In
this
case,
this
is
default
source
and
we
will
try
to
make
a
source
deduction
from
the
default
source
and
taking
into
account
that
we
don't
have
enough
quantity
on
default
source
item.
We
will
get
an
error
that
we
don't
have
enough
enough
quantity
to
fulfill
the
order
to
fulfill
the
request,
quantity-
and
actually,
this
is
currently
the
main
difference
compared
to
what
we
have
with
the
magenta
work,
because
in
magenta
port
we
actually
applied
before
there
for
stock.
A
But
on
MSI
we
have
configuration
for
stock
level
and
for
source
level,
and
this
before
there,
which
exists
right
now
is
applicable
for
stock
levels.
So
we
apply
it
as
a
condition
to
check
whether
whether
we
can
place
an
order,
whether
we
can
add
the
product,
this
shopping
cart,
but
not,
but
not
the
configuration
option,
whether
we
can
make
a
source
deduction
or
not-
and
that
was
actually
discussion
about
this
during
this
week
and
actually
here
the
result
of
the
discussion.
A
So
we
decided
that
actually
it's
pretty
a
pretty
similar
to
what
we
already
have
four
quantities:
shonali,
because
for
quantity
functionality
we
have
two
two
types
of
quantity:
we
have
the
stock
availability,
so
the
number
of
products
we
have
will
have
a
located
on
a
source
items
and
we
have
product
sale
ability.
This
is
an
aggregated
quantity
among
all
of
the
source.
Items
was
additional
additional
business
logic,
for
example
like
like
Minnie
Mouse
result,
for
example,
because
negative
threshold
for
back
orders
also
add
added
value
to
the
saleability
quantity.
A
So
it's
pretty
similar
and
actually
would
be
decided
that
we
will
introduce
the
porter
configuration
option
on
a
level
of
source
and
we
will
calculate
the
backorder
configuration
option
on
a
level
of
stock
and
the
stock
configuration
option
would
be
used
as
a
check
for
order
placement
and
adding
product
to
the
shopping,
cart
and
the
source
configuration
option
would
be
used
to
make
a
decision
whether
weak,
allowed
or
not
allowed
to
to
proceed
with
the
shipment
with
a
negative
quantity.
Because
for
some
user
scenarios,
yes.
A
E
E
C
B
E
E
I
guess
because
of
this
data
duplication-
and
it's
not
related
to
this
topic-
only
there
are
lots
of
scenarios
wouldn't
when
the
beta
can
get
out
of
sync
right,
and
this
back
order.
Functionality
adds
more
to
those
scenarios
like
McWhorter,
disabled
and
the
core
distress
holds
changed.
It
would
have
all
the
scenarios
described.
E
A
This
is
perfectly
good
for
business,
like
which
guess
like
a
supplier,
and
they
need
to
get
to
get
this
amount
of
products
and,
after
that,
make
a
shipment
by
their
self.
But
if,
if
we
consider
the
use
case
with
the
drug
shipment,
a
drop
shipping
where
all
the
treatment
done
by
a
drop
shipper,
the
current
behavior
is
not
sufficient
because,
as
emergent,
you
can't
even
complete
the
order,
because
to
complete
the
order,
you
need
to
create
a
shipment.
A
And
probably
you
need
to
create
a
shipment,
at
least
for
heaven,
some
possibility
to
track
all
the
all
the
orders
which
are
completed
and
just
to
track
what
what
was
already
delivered
by
the
drop
shipper.
So
having
this
functionality.
With
the
book
order
on
the
levels
on
source
and
stock,
we
can
say
that
we
support
dropship
the
freaking
in
in
in
Mashhad.
A
A
Looks
like
no,
so
thank
you
guys
for
your
time.
It
was.
It
was
really
really
good
demo,
so
we
we
just
did
not
even
started
our
next
print,
but
we
already
demonstrated
to
all
the
stories
which
are
part
of
this
print,
so
really
good
velocity.
Thank
you
guys
and
thank
you
for
contribution.
See
you
next
week,
yeah.