►
From YouTube: Magento MSI Open Demo. September 28, 2018
Description
Regression status
and
Source Selection Algorithm based on the distance between Sources and Shipping address
A
Issues
is
found
and
the
how
many
issues
will
be
fixed
and
the
whole
recorder
will
share
some
ideas
and
he
is
currently
working
on
inland
to
the
configuration
story,
the
big
one
and
the
one
he
will
share.
He
started
from
also
the
idea
of
for
introducing
the
usual
selection
algorithm,
based
on
the
remoteness
and
geocoding
and
remoteness
of
destination
address
from
from
sources.
B
B
Well,
what
is
not
implemented
yet
it
gonna
be
fix,
it
sort
of
say
in
Muslim
faith
and,
as
already
said,
that
we
have
sought
in
Staten
area
failed
and
I
will
now
go
to
github,
and
here
we
have
tickets
dedicated
to
box
what
we
discovered
during
this
regression
I
have
labeled
regression
melt
onto
its
box.
First
of
all,
we
started
with
all
stock
report
and,
as
I
know,
ready
Alessandra
is
working
on
these
issues.
Is
we
have
several
back?
What
is
the
concern?
B
B
A
So,
regarding
yeah,
so
I
saw
I
mentioned.
We
started
our
aggression
on
in
local
environment
because
we
had
the
blocker
on
cloud
and
actually
we
had
two
blockers
encounter.
The
first
one
was
regarding
the
hermitian
database
permission,
which
we
fix
pretty
quickly,
and
after
that
we
had
a
had
another
blocker,
because
on
our
cloud
we'd,
we
actually
test
magenta
to
the
tree.
A
That
old
package,
which
includes
enterprise,
b2b
plus
different,
bugs
extensions,
including
dot,
plant
mail
there,
for
example-
and
there
was
an
actually
issue
between
between
MSI
and
dot
mailer-
that
both
extension
actually
conflict
in
each
other,
and
we
managed
to
fix
this
issue
two
days
before
and
now
that
gave
us
an
opportunity
to
to
bond
on
you
new
composer
package,
and
there
is
a
pretty
good
update
for
today.
That
actually
is
this
Friday.
A
A
So,
actually,
you
can
see
here
all
the
issues
and
tickets
which
were
fixed
during
this
milestone
and
all
the
bugs.
Actually,
you
can
see
here
in
the
bottom
of
this
list.
You
can
see
all
the
bugs
created
at
the
scope
of
regression,
along
with
bugs
which
we
had
before.
Currently
all
the
bugs
we
have
a
marked
with
the
top
ten
bugs
and
all
the
bugs
found
in
the
regression
mark,
additionally,
with
regression
milestone
to
label
and
as
soon
as
regression
gonna
finish.
So
currently,
we
have
just
155
scenarios,
so
it's
about
33.
A
A
But
not
nothing
prevents
guys
from
community
to
help
us
already
now
because
they
already
created.
So
if
you,
if
you
are
watching
this
demo,
you
can
use
this
filter
by
progression,
milestone
to
and
choose
any
bug
which
is
not
assigned
to
all
the
unassigned
bug.
You
can
take
any
assign
it
to
yourself
and
start
working
on
it
and
yeah
so
currently.
Currently,
this
is
our
burn
down.
Some
of
the
tasks
would
be
read
prioritize
because
currently,
these
are
all
issues
we
have
in
our
backlog.
Some
of
this
issue
would
be
postponed,
so
we
will.
A
We
will
after
the
first
cycle
of
regression,
we
will
make
trash,
and
some
not
some
bugs
with
a
highest
priority
would
be
would
be
left
for
fixing
this.
This
milestone
and
others
would
be
postponed
to
the
milestone
3.
So
this
is
actually
all
our
regression
status
for
for
this
week
and
now,
I'm
I'm
stop
sharing
my
screen
and,
given
a
word
to
record
it,
we
will
hit
update.
C
Okay,
thank
you
so,
as
you
said
before,
I'm
working
on
the
inventor
configuration
and
we
well
actually
yesterday
we
got
a
lot
of
red
tests
and
today
I
think
we
just
got
maybe
three
for
failing
tests
that
I'm
fixing
so
hopefully
for
the
end
of
the
day.
I
will
push
again
and
check.
We
all
green
I
think
we
just
have
to
fix
some
additional
statics
tests.
I,
don't
know
what
is
your
policy
about
all
the
new
rules
that
became
active
with
two
point
three
regarding
did
don't
I
transfer
on
actually
because.
A
B
A
C
Okay,
so
we'll
just
focus
on
integration
tests
and,
as
I
said
before,
hopefully,
for
the
end
of
the
day,
we'll
have
something
working
I
mean,
at
least
from
the
test
point
of
view.
Then,
as
you
said
before,
I've
been
start,
I
started
working
on
an
idea
actually
because
I
had
a
customer
asking
for
base
the
msi
and
he
had
a
requirement
that
was
a
distance
based
algorithm
for
su
selection.
C
That,
I
think
is
it
could
be
a
very
common
requirement,
so
I
decided
to
start
testing
something,
and
we
show
you
what
is
my
D,
of
course,
is
just
it's
just
an
idea,
and
it
is
not
still
working
because
I
just
started
yesterday
and
I
I
didn't
finish
it.
But
the
idea,
of
course,
is
to
is
to
add
a
new
new
class
handling.
C
But
yesterday
we
have
been
talking
with
Igor
about
this,
and
the
idea
is
to
provide
different
ways,
so
you
can,
for
example,
provide
one
offline,
distance
computation
and
maybe
one
aligned
based
on
Google,
my
upon
whatever
you,
like
so
I,
decided
to
introduce
something
like
a
distance
provider
that
you
can
select
from
your
back-end
configuration,
so
you
can
choose
between
Google
and
offline
distance,
lector
and
whatever.
So.
C
Basically,
the
distance
provider
is
something
very,
very
simple
that
basically
it
takes
as
text
to
arguments
that
are
the
sort
of
item
I'm,
sorry,
the
source
interface.
So
where
is
your
warehouse
and
what
is
the
address?
And
then
it
provides
a
distance
in
kilometer
between
them
and
depending
on
these?
Basically,
we
are
sorting
all
the
sources,
and
then
we
we
have
the
feature
almost
working.
The
only
problem
was
that
currently,
the
inventory
selection
is
only
based
on
the
SQ
and
the
quantity
requested.
C
So,
basically,
in
the
metarie
request,
I
added
an
address,
request,
interface,
that
it
is
not
exactly
connected
to
the
address
because
I
don't
want
to
add
a
new
dependency
is
just
a
DTO
containing
all
the
basic
information,
so
the
country
postcode
them
whatever
and
depending
on
this
information
that,
of
course,
I
have
to
provide
while
creating
the
Metro
request.
I
can
apply
this
algorithm,
so
I
had
to
modify
or
easy
yeah.
This
should
be
the
controller,
for
example.
This
is
the
controller
when
you,
when
you
run
the
selection
page.
C
So,
for
example,
you
had
to
modify
something
here
are
doing
the
address
then
I
found
then
I
find
all
the
occurrences
of
the
Metro
request.
Creation
and
I
modified
to
to
accept
the
new
address
and
it
should
be
working
I
think
I
I
can
have
something.
I
mean
something
very
minimal
for
the
next
week
and
currently
I'm
working
with
Google
map.
In
fact,
as
you
can
see,
is
the
only
one
I
start
where
I
started
working
well,
as
far
as
now
is
very
it's
just
a
mark.
C
So
I
need
to
to
implement
all
the
calls,
but
I
will
start
from
this
one.
Then
I
will
add
the
offline
mechanism
that
will
be
probably
based
on
some
kind
of
public
database.
We
may
found
me
we
may
find
in
the
lot
or
maybe
from
some
kind
of
input
that
the
user
can
provide.
So
this
is
the
idea
behind
and
I'm
done.
Oh.
A
Thank
you,
so
I'm
I
was
sure
my
you
know,
so
actually
it's
pretty
pretty
interesting,
but
actually
I
believe
that
we
need
to
extend
our
inventory
request
interface
yeah
this.
This
is
what
I
did
actually
yeah
all
data
interfaces
with
extension
attributes
and
so
that
we
can,
we
can
specify
like
shipment
address
here.
C
A
A
In
any
case,
even
for
adding
extension
attribute,
we
we
have
to
add
the
after.
So
in
any
case,
we
need
to
modify
the
interface
and
as
soon
as
while
we
did
not
release
it
yet
is
acceptable
and
probably
actually
that
that
was
another
task
which
I
had
told
you
that
we
need
to
do
before
the
release.
So
we
need
to
review
all
the
all
the
interfaces
and
my.
C
A
Any
particular
organ
algorithm
can
require
additional
data
to
be
transferred
to
be
transferred
via
the
extension,
for
example,
because
already
now
we
have
the
priority
based
algorithm,
which
actually
no
need
any
any
shipping
data
so
that
it's
not
it's
not
properly.
To
get
this
as
a
mandatory
part
of
the
of
the
interface.
B
C
Example,
I
had
I
had
a
very
similar
issue
with,
for
example,
products
we
discount
that
cannot
leave
from
one
source
and
not
from
another,
because
it
was
a
scenario
I
had
with
one
customer
with
much
Antoine
and
I
think
we.
We
can
have
something
like
this
very
strange
scenario.
So
maybe
yes,
adding
an
accession
attribute
is
the
best
option,
because
you
do
whatever
you
like
yeah.
A
And
actually,
because
from
the
from
the
interface
design
perspective,
is
not
good
to
have
method
methods
under
the
scope
of
an
interface
which
applicable
in
one
business
scenarios
and
not
applicable
in
another
one.
So
actually,
this
heaven,
heaven
different
method
in
the
scope
of
one
and
to
face
actually
violate
the
idea
of
the
connection
between
the
between
the
interface
methods.
So
this
is
usually
could
be
considered
kind
of
bad
smell
of
the
interface
design,
and
this
usually
says
that
message
should
be
distributed
in
different
interfaces
or
classes.
A
A
Yes,
yes,
whether
all
our
data
interfaces
have
have
to
get
extension
and
said
extension
to
Butte
method,
because
because
this
is
actually
a
gap
in
this
particular
interface,
because
because
I
expected
that
we
have
this
extension
part.
So
as
a
absence
of
the
gate
extension
attribute
methods
is
a
gap
in
our
extensibility.