►
From YouTube: Magento MSI Open Demo. March 9, 2018
Description
Today’s agenda:
- Configurable Product (backend part in admin panel) @roman.kis
- Source Deduction as a result of Source Selection Algorithm (UI part) (@seruymt/@iminiailo) with an ability to change manually selection provided by the algorithm
- A few words about bug fixing, merged PRs, another tracks status (@vnayda @roman.kis)
https://magento.zoom.us/j/355586473
A
B
C
B
B
C
B
B
B
C
B
C
B
B
B
Sources
top
disappear
because
we
don't
need
to
assign
for
this
product
any
sources.
Now,
if
I
delay
it,
I
remove
one
product.
It
is
absent
still
and
if
I
remove
one
not
product,
we
can
see
this
sources
top
appear
again,
because
now
it
is
simple
product
and
we
need
to
assign
some
sources.
Yeah
seems
like
that's
all
update
from
my
site,
thanks
for
attention,
I
just.
A
We
just
saw
the
source
item
status,
but
potentially
like
not
really
good
from
the
utility
point
of
view
and
Merchants
see
grief
on
a
product,
editing
page,
but
actually
he
and
he
he
could,
for
example,
make
an
assumption
that
all
the
hints
book
items
would
be
counted
in
the
aggregation,
for
example,
but
because
this
source
is
disabled,
some
particular
source
items
would
not
be
too
late.
If
I
actually
decided
to
use
it
column,
we
can
present
the
patches
of
the
food
source.
D
B
C
Yeah
I'd
like
to
see
that
it
looks
like
in
the
example,
though
they
didn't
have
anything
with
longer
than
five
configured,
so
it
wouldn't
they
wouldn't
trigger.
So
that
may
take
some
time
to
create
all
the
sources
to
demonstrate
it.
My
question
is:
does
it
have
an
icon
that
appears,
if
there's
more
than
five,
so
the
user
knows
that
there's
like
a
mouse
over
available.
A
A
C
Okay,
maybe
I
should
check
what
you're
doing
I
just
have
some
concern.
In
my
they
thing,
consistent
with
how
we
do
that
in
other
parts
of
the
admin,
the
only
difference
being
whether
there's
an
icon
or
something
it's
either.
That's
why
I
say
I
have
to
check
on
the
standard,
either
an
icon
or
a
link
or
something
that
lets
the
user
know
that
it's
possible
for
them
to
trigger
them.
A
C
A
C
A
Okay,
so
let's
go
to
another
item
in
our
agenda
and
each
supposed
to
be
the
source
deduction
algorithm
as
a
result
of
the
source
selection
algorithm
so
and
it
will
actually
demonstrate
you,
the
the
cool
use
case
and
the
cool
business
case,
how
that
actually
the
porter
place
have
we
around
the
selection
ombudsman,
how
the
source
deductions
happen
implemented
by
from
eleven
cents,
forgave
from
that
he
did
try
guy
and
he
doesn't
want
to
make
it
demonstrated.
So
I
will
do
it
for
him.
A
We
already
throw
a
part
of
this
scenario
previous
previous
week,
but
we
didn't
have.
Actually
we
just
make
deductions
based
on
the
result
of
the
default
source,
selection,
algorithm
and
actually
we,
the
next
step,
was
introduced
into
usable
to
be
able
to
poor
merchant
to
modify
the
result
of
the
source
selection
algorithm
and
and
introduce
some
changes
to
this
results.
So,
let's,
let's
go
to
customers.
So,
first
of
all,
I
need
to
show
you
the
initial
initial
environment
we
have
so
we
we
have
a
stock.
A
This
talk
is
Europe
and
in
this
talk
we
have.
There
are
three
sources
in
this
talk.
This
talk
is
assigned
the
main
website
and
there
are
three
sources
and
because
we
were
evolving
our
priority
based
algorithm
the
priority,
the
warder
of
the
sources
actually
matters
here,
because
italy
has
the
highest
priority.
Poland
has
a
little
less
priority
and
ukraine
has
the
lowest
priority
and
now,
let's
go
to
the
products
and
let's
find
the
simple
products.
A
Here
we
need
to
pay
attention
that
test
simple
product
assigned
to
Italy,
Italian
and
Ukrainian
sources
and
has
a
quantity
100
on
both
of
these
sources
and
the
test
simple
product
assigned
to
Poland
and
Ukraine
and
also
has
a
has
a
quantity
100
per
each
of
the
sources.
So
now,
let's
create
an
order.
A
So
to
do
this,
let's
find
the
customer.
So
you
know:
ok,
that's
John
Doe
from
from
Texas,
let's
go
to
the
page
of
John
and
create
an
order,
and
let's
find
these
simple
products
and,
for
example,
for
example,
we
would
like
to
buy
20
items
of
test,
simple
product
and
10
items
of
test,
simple
product,
so
again
selected
products
to
the
shopping,
cart.
A
Currently
we
still
have
this
tab
in
which
we
can
make
an
estimation
which
would
be
result
of
the
default
for
selection
algorithm,
where
we,
how
we
have
the
default
algorri.
The
resources
will
be
selected
for
this
particular
order
fulfillment.
So
we
can
come
here
and
see
that
based
based
on
our
configuration,
we
don't
make
any
delivery
from
Ukraine,
because
the
first
product
was
in
Italy
and
in
Ukraine.
The
second
one
was
in
Poland
and
in
Ukraine,
taken
into
account
at
our
default
source.
Selection
algorithm
is
priority
based
in
both
of
in
both
cases.
A
A
We
generate
here
items
to
be
seen,
and
here
you
see
that
here
you
see
that
italian
italian
source
is
more
prioritized
comparing
to
ukrainian,
and
here
is
the
poland
no
prioritized
comparing
with
ukrainian.
But
here
we
can
change
this
source
selection.
For
example,
let's
decide
that
we
will
send
5
items
from
italian
store
and
5
from
Ukrainian,
and
here
we
decide
that
will
send
18
items
from
poland
store
and
2
items
from
ukrainian.
So
actually
before
this
demo,
we
never
demonstrated
that
we
made
the
source
deduction
on
more
than
one
one
sources.
C
A
C
A
A
C
Well,
what
we
Rex
were
actually
not
seeing
the
full
story
there
right,
because
it
would
have
made
a
reservation
and
then
updated
it.
It's
not
a
problem.
I'll
shoot!
You
I
mean
it's
showing
yeah,
it's
showing
the
correct
information
for
the
for
the
merchants,
but
I'm
just
trying
to
say
even
more
interesting.
Things
were
happening
than
you
are
able
to
demonstrate
only
in
the
admin
well,.
A
A
Apply
the
shipment
so
now
we
supposed
to
see
first
of
all,
it
see
the
generation
being
created
and
we
see
that
additional
compensation
or
reservation
created
and
now
we're
supposed
to
have
the
correct
quantity
like
minus
20,
plus
19
plus
1.
It's
all
together,
give
us
0
and
now,
let's
see,
is
that
actually
the
first
item
quantity
has
been
updated
either,
and
this
is
the
one
product
letter
first,
the
page
and
we
supposed
to
see
81
here.
A
A
Here
could
be
here:
we
thought
what
we
need
to
do
with
the
source
selection,
because
currently
we
don't-
we
don't
show
from
where
we
made
made
this
shipment.
So
should
we
leave
this
source
selection
table
in
our
order
view,
or
should
we
totally
remove
it
and
provide
all
the
data
in
a
shipment
top
well.
A
Before
before
that,
before
we
had
to
actually
work
in
source
selection,
algorithm
and
source
deduction,
we
use
it
just
to
see
the
results
of
the
source
selection
algorithm
work
to
make
it
sure
that
it
works
and
to
provide
the
possibility
to
make
something
demonstratable,
but
currently,
for
example,
the
only
possible
reason
why
merchants
can
need
it
if
to
see
their
the
default
results
of
the
how
how
default
for
selection
algorithm
will
work
and
what
sources
it
you
choose.
But
actually
we
can
do
the
same
on
this
shipment.
That
shipments
yeah.
C
No
I
understand
completely
why
it
was
that
and
for
demonstration
purposes.
I
think
that
makes
sense,
but
I
don't
know
that
we
need
to
keep
it
as
a
tab,
because
I
want
to
make
it
as
simple
as
possible
for
the
merchants.
So
if
they
can
have
everything
on
shipments
tab,
that
is
that's
preferable
so
having
to
add
another
one.
Ok.
D
A
A
So
we
actually
most
of
our
most
technical
update,
but
taken
into
account
I
will
show
you
I
even
treated
that
some
time
ago
mentioned
roadmap.
So
we
we
prepared
the
source
selection,
algorithm
technical
design,
which
recharge
in
Twitter-
and
you
know
it's
locked
channel
and
before
zest.
One.
Our
previous
design
was
really
coupled
to
that
order,
and
we
have
like
the
interface
of
the
signal
algorithm,
be
accepted,
order
order,
interface
as
a
parameter
and
provided
shoot.
A
Machine
algorithm
result
based
on
the
order
provided,
but
taking
into
account
that
some
of
agencies,
or
maybe
even
we
but
in
future,
decide
to
run
the
selection
algorithm
at
the
time
of
port
replacement.
We
decided
that
we
need
to
introduce
some
some
addition
abstraction
layer
which
will
provide
us
an
ability
to
not
depend
on
a
porter
interface.
A
You
know
certain
shooting
algorithm,
that's
why
actually
we
introduced
the
inventory
request,
interface,
which
consists
of
the
shipping
address
and
all
the
items,
and
this
request
interface
is
prepared
by
particular
factory
and
that
factory,
except
except
in
our
case
order
interface.
But
if
extension,
third-party
developer
or
guy,
who
may
make
some
kind
of
customization
will
decide
to
make
the
same
for
would
he
will
easily
introduce
his
own
factory
and
just
will
create
this
request?
Object
based
on
the
cart
interface,
so
based
on
what
this
is.
A
This
is
what
we
will
done
and
when
we
will
done
that,
we
decided
to
put
all
the
API
is
related
to
the
source
selection
algorithm
into
the
dedicated
module,
and
we
call
it
inventory
source
selection
API.
So
this
is
actually
by
which
providers
and
possibility
to
to
make
a
source
selection
based
on
this,
pretty
abstract
request
interfaces.
So
it's
not
really
highly
coupled
to
our
order.
Neither
to
the.
A
Cart
so
the
particular
implementation
is
is
made
in
inventory
shipping
module.
So
this
is
update
from
the
modularity
point
of
view,
and
we
consider
that
the
such
architecture
provides
an
ability
to
easily
integrate
algorithm
if
needed
at
the
time
of
order
placement.
So
this
is
this
was
the
main
idea
behind
these
changes.
A
D
Oh
guys
again
a
few
words
from
my
side.
During
this
week
we
also
murdered
a
few
pull
requests
related
to
some
technical
things.
I
chose
this
page,
for
example,
it
was
pull
requests
from
Bartok.
He
fix
it,
synchronization
between
legacy
stock
system
and
MSI
system
and
looks
likes.
It
was
to
last
stories
in
power,
adapter
catalog
inventory,
a
biased,
epics
and
looks
like
we
can
host
and
close
5.
Epic
points
looks
like
all
tasks
accosted.
D
Also,
he
noted
some
bug
fixing
like
Roman,
demonstrated
some
some
improvements
to
I
about
source
status.
We
remove
redundant
configuration
options,
fortifying
quantity,
we
introduced
it
all
for
inside,
but
it
was
redundant
because
we
already
have
these
options
in
currency
instant,
so
we
reuse
these
options.
Also,
it
was
a
few
progressed
about
some
technical
improvements,
like
organizations
fixing
of
our
Travis
bills
and
skip
best
and
fixes.
So
and
now
we
have
a
big
track,
which
is
in
progress
it
tracks
about
an
introduced
in
his
product
sale
before
progress
on
teach
interface.
D
Now
we
already
have
poor
request
from
Alessandro
understand
reward
some
implementations
of
this
pull
request
and
we
can
take
this
wait
for
another
trip
for
another
task
and
Bartek
starts
work
on
shopping,
cart,
now,
shopping
cart
is
working
only
with
one
single
stock
system
and
we
need
to
improve
and
replaces
the
power
with
our
cover
and
should
be
cut
short
work,
his
multi
stock
system.
This
part
take
Bartek
and
also
we
have
vitaly
format.
It's
this
guy
pick
it
up
tasks
related
to
integrations
this
service,
this
interface,
the
stories
in
Dutch
code.
A
Yes,
shortly
same
before
this
week,
we
had
the
situation
that
we
have
like
three
stories
and
in
each
of
the
stories
we
have
the
only
ticket
which
need
which
we
need
to
finish
to
call
that
story,
and
during
this
week,
as
whatever
already
mentioned
and
demonstrated,
we
finish
all
that
leftovers
in
each
of
the
story.
So
probably
we
can
close
these
stories
and
the
pursuit
his
father
father
work
on
a
shopping,
cart
and
veg
count.
A
C
The
demo
is
really
excellent.
It's
a
huge,
huge
step
forward
to
be
able
to
see
everything
with
shipping
and
the
configurable
product,
so
it's
very
great
to
see
that
I
still
want
to
make
sure
that
we
sign
all
this
off
with
Eugene
on
UX
to
make
sure
everything's
good
there
there's
one
for
a
saw.
For
example,
we
have
the
ability
to
set
the
notify
quantity
for
each
source
from
the
page
they're
from
the
product
page,
which
is
great
and
the
column.
C
Titles
I
believe
were
notify
quantity
and
then
it
said,
notify
quantity
use
default,
which
is
not
this.
Our
normal
practice
is
just
to
have
use
default
and
not
the
title
repeated.
You
know
we
just
made.
It
may
need
to
make
a
slight
adjustment
to
the
title
there,
like
I,
said:
I
need
to
check
with
Eugene.
That's
his
call,
but
it's
a
very
minor
point.
You
know
the
demo
is
excellent.
A
Thank
you
very
much
actually
like
right
before
the
demo.
We
discuss
it
with
a
woman,
a
name
in
in
in
this
greet,
and
also
we
decided
that
probably
it
would
be
better
to
rename
for
like
ID,
which
represent
source
code
and
probably
just
to
substitute
ID
with
code,
because
currently
the
column
name
says
ID,
but
the
data
which
we
show
there.
The
source
code
is.
C
A
You
very
much
for
your
update
and
then
say
thank
you
for
your
time
and
for
participation
in
the
demo
and
thank
you
guys
for
all
those
who
of
you
who
decided
to
spend
their
time
and
spend
their
time
with
us
on
magenta,
messiah,
Dima
and
see
you
next
week
all
right.
Thank
you.
Everyone!
Thank
you.
Bye,
bye,.