►
From YouTube: Magento MSI Open Demo. January 11, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Yeah,
okay,
emo,
hello,
everybody
well
welcome
and
we
glad
to
see
them
wait.
Welcome
you
on
a
weekly
MSI
demo
meeting
and
today
we
will
present
you
the
status
for
currently
and
during
the
current
weekly
they're,
mostly
making
all
the
preparation
for
that
coming
up
coming,
might
release
of
MSI.
Actually
it's
going
to
be
the
one
dot,
one
dot
older
version
of
MSI
package:
whites,
one
dot,
one
dot
all,
but
not
one
God.
All.
A
Indeed,
Mr
lorry
will
make
some
demonstration
of
the
draft
of
documents
and
a
frequently
asked
page
regarding
the
distance
based
algorithm
and
also
the
the
draft
of
the
release
notes,
so
that
this
is
actually
wise.
We
will,
we
will
bomb
the
minor
version
for
the
for
the
MSI
package
and
also
given
during
this
week.
A
We
had
quite
a
lot
of
different
communication,
and
this
is
a
more
and
more
people,
get
their
hands
dirty
in
the
MSI
code
and
start
to
make
some
MSI
customization
and
try
to
apply
an
aside
for
for
the
goodness
of
merchants
for
their
client.
That's
why
we
have
quite
a
lot
of
question,
and
probably
it
makes
sense
to
talk
a
little
bit
about
this
question
and
with
because
I
believe
that
questions
raised
in
some
discussions
in
the
in
a
small
circle.
Discussion
can
be
you
answer
to
this.
A
Patient
can
be
useful
to
other
people
who
try
to
accommodate
MSI
for
their
purposes,
so
I'm
I
will
share
my
screen
and
I
will
I
will
go
through
some
of
the
key
kids
created
some
of
the
quest
created
and
the
we
like.
We
can
get
discussed
by
some.
Particular
decisions
been
been
done
for
particular
situation.
So
let
me
show
you
the
screen
and
here
like
here
in
a
Massiah
channel
and
the
just
just
to
say
it
once
again,
that
the
main
communication
channel
for
MSI
is
a
select
channel
MSI.
A
What
do
you
used
to
begin
used
tools
came
to
us
even
this
week
and
the
race
race,
the
question
regarding
Z
configurable
product
and
the
because
initially
he
complained
that
we
still
have
a
problem,
one
when
configurable
product
could
to
be
be
added
to
the
shopping,
cart
and
the
sometime
ago,
like
a
half
of
a
year
ago.
We
really
had
this
this
problem,
but
in
reality,
what
being
had
a
little
different
problem,
not
even
problem,
because
finally,
we
agreed
that
this
is
this.
Behavior
is
expected
one,
but
would
like.
A
Would
the
behavior
when
in
stock
with,
is
that
he
created
the
configurable
and
initially
because
this
configurable
product
did
not
have
any
child?
It
was
created
as
out
of
stock,
and
then
he
added,
then
he
added
a
child
product
and
the
child
product
with
the
in
stock
as
stock
status,
so
that,
after
that
step,
he
added
the
child
product
to
the
parent
bomb
and
he
expected
that
the
configurable
product
will
get
their
status
as
a
in
stock.
A
So
in
this
case,
potentially
merchants
can
make
the
product
is
just
disabled,
but
disabling
the
product
will
just
eliminate
it
from
the
category
page
and
from
the
search
result
page
so
to
support
the
behavior
of
showing
the
out
of
stock
product.
If
merchants,
for
some
reason
decided
to
get
product
out
of
stock-
and
this
is
kind
of
conscious
decision,
even
though
that
product
is
available,
but
along
with
it,
to
provide
an
ability
for
customers
to
add
product
to
their
wish
lists.
A
We
agreed
that
we
will
have
the
stock
status
on
a
level
of
composite
products
like
configurable,
one
and
and
specifying
that
products
is
out
of
stock.
Is
one
of
the
our
first
step,
ballad
ation
for
such
services.
As
is
product
saleable
to
check
to
check
whether
product,
saleable
or
not?
So,
as
you
know,
you
know,
in
such
services,
like
its
product
sale
available,
we
have
the
validation
chain
which
consists
of
many
steps
and
which
checks
whether
product,
saleable
or
no,
because
we
have
quite
a
lot
of
condition.
A
Actually,
for
example,
we
have
the
inventory
configuration,
for
example,
as
like
is
managed
stock.
Also,
we
have
the
we
have
the
we
have
the
backorder
functionality
also,
we
have
actually
quantity
of
product
so
that
all
of
these
checks
implemented
as
independent
validation,
steps
and
for
existence
steps.
We
edit
one
more
step,
and
this
step
is
actually
they
check
whether
whether
product
is
a
composite
one,
and
if
the
product
is
composite
one.
A
We
check
whether
the
stock
status
out
of
stock
is
to
fight,
and
if
so,
we
just
keep
all
other
validation
checks,
and
we
just
returned
that
the
project
is
out
of
stock,
so,
along
with
that,
that
introduced
kind
of
actually
pretty
small,
but
the
performance
boost
for
for
composite
products.
So
after
this,
this
thread
of
discussion,
like
redeem,
accepted
our
our
arguments
and
he
agreed
that
this
is
that
like
by
default.
So
this
is
by
design,
and
this
is
expected.
Behavior.
A
So,
let's
proceed
further
to
entry
to
other
interesting
discussion,
another
interesting
discussion,
so
probably
we
we
already
already
demonstrated
it
several
times
before
before
Christmas,
that
on
our
upcoming
1.1
release
of
MSI.
So
this
release
will
contain
some
performance
boost,
especially
for
the
default
stock,
and
yesterday
I
had
a
conversation
with
with
our
partner
representative
from
vortex
with
Bruce
meet
and
actually
Bruce
mentioned
that
on
his
particular
Magento
installation.
He
achieved
the
performance
boost
a
little
bit,
fixing
our
my
sequel
query,
which
creates
a
which
creates
a
my
sequel
view.
A
Actually,
we
introduced
this
my
simple
view
with
a
join
and
in
our
view
we
have
the
distinct
query.
So
actually,
what
does
distinct
do
distinct,
make
some
kind
of
grouping
and
actually
distinct
prevent
that
more
than
more
than
one
entity
with
the
same
entity.
Id
now,
okay,
that's
product,
AG
gonna,
be
return
out
of
this.
A
Out
of
this
query
and
Bruce
mentioned
that
this
distinct
could
be
pretty
costly
for
us
if
we
have
quite
a
lot
of
products
and
if
we
have
quote
like
if
either
quite
a
lot
of
products
in
the
cattle
and
if
we
drop
in
and
if
we
have
quite
a
lot
of
herbs,
yep
and
if
we
have
quite
a
lot
of
stock
statuses,
but
in
fact
this
this
fix
definitely
could
be
applied
for
the
Community
Edition
so
that
it
could
be
like.
If
you
make
the
MSI
customization
you
can.
A
You
can
apply
this
view
like
you,
can
make
some
own
customization
and
remove
this
distinct
and
proceed
the
my
sequel
view
without
this
distinction.
That
will
definitely
work
for
you,
but
on
the
level
of
framework
like
we
can't
do
this,
because
this
is
actually
break.
The
removal
of
the
distinct
will
break
our
our
staging
behavior,
because,
even
so
that
we
don't
use
staging
for
the
inventory
data
we
still
use
station
for
them
for
the
catalog
product
entity
data.
A
That's
why
the
inner
join
between
the
cadillac
product
entity
and
the
and
the
stock
status
will
lead
to
more
than
one
entity
return
with
the
same
entity
ID,
and
these
will
potentially
not
potentially.
Actually,
this
will
break
our
category
page
and
this
will
break
our
search
result
page
because
we
will
have
more
than
one
product
with
the
same
ad
return,
so
we'll
just
render
several
identical
products.
A
A
Backwards
incompatible
changes
so
means
help
of
this.
You
we
like
we
make
all
our
contracts.
I
mean
programmatically
contracts
introduced
on
the
level
of
MSI
to
support
to
support,
like
all
the
cases,
even
for
default
stock.
Now,
let's
proceed
proceed
next,
because
there
were
several
other
pretty
interesting
questions.
A
For
example
like
even
today,
we
go
to
request
that
that
the
quantity
for
the
source
could
be
negative
and
the
contributor
item
I
I,
can
barely
barely
pronounce
his
name.
So
the
contributor
there
is
no
actually
name
so,
but
so
the
main
idea
of
contributor
was
to
prevent
a
possibility
to
specify
a
negative
negative
quantity
for
the
source
item
because
from
his
perspective,
and
actually
is
pretty
clear-
why?
Why
he's
thought
about
that?
A
That
that,
because,
like
we
all,
were
constantly
saying
that
MSI
is
much
closer
to
business
and
the
catwalk
inventory
than
previous
inventory
mechanism
we
had
before,
because
it
tries
to
be
as
much
close
to
real
business
cases
as
it
could
be,
and
that's
why
that's
why?
These
guys
probably
thought
that
there
could
be
negative
quantity
on
particular
source
and
he
tried
to
specify
the
negative
quantity.
He
seemed
that
the
system
allows
to
do
it
and
he
created
a
pull
request
which
introduced
additional
validation.
A
We,
which
forbid
to
specify
the
negative
quantity
on
the
level
of
the
source
item.
But
in
fact,
the
negative
source
item.
Quantity
is
a
desirable
state
for
us
and
the.
Moreover,
it
was
allowed
to
specify
negative
source
quantity
before,
like
in
magenta
in
magenta
Europe
before
the
MFI
was
introduced.
But
white
white
could
be
useful
for
us
on
magenta
with
msi.
So,
as
you
know,
magenta
with
msi
support
the
drop
shipping
and
the
drop
shipping
could
be
set
up
on
top
of
on
top
of
new
inventory
mechanism.
A
So
the
negative
quantity
for
this
particular
source
represent
actually
how
many
products
we
should
request
from
the
external
vendor
so
well,
because
that
drop
shipper
source
would
be
really
wouldn't
be
really
somehow
differ
from
other
sources.
But
merchants
can
can
differently,
treat
the
number
of
source
items
for
particular
Eskew
and,
for
example,
he
can.
He
can
specify
that
the
backwater
is
enabled
for
all
this,
all
the
s
queues
and
the.
So
that's
why
quantity
will
get
like
get.
You
will
get
below
zero
and
he
will
see,
for
example,
in
these
case,
like
minus
140.
A
A
Background
for
for
inventory
so
that
it
can
be
considered
just
just
a
bug
and
we
we
still
want
to
keep
the
possibility
to
specify
negative
negative
quantity,
and
maybe
if
it
makes
sense
to
introduce
some
kind
of
mod
or
like
think
that
this
is
this
is
real
warehouse
and
on
a
real
warehouse
and
it
can
be
just
a
negative
quantity.
So
in
this
case,
that's
true:
we
can
introduce
this
validation
of
for
real
warehouse
or
brick-and-mortar
stores,
but,
for
example,
for
virtual
virtual
sources
or
for
drop
shippers.
A
B
A
A
Actually,
we
are
not
in
progress,
but
we
little
bit
postpone
the
story,
which
was
started
by
Sergey
moot
of
and
Riccardi
attempt
estimate
previous
year.
We
wanted
to
apply
this
change.
This
configuration
set
setting
on
the
source
level
so
that
currently
we
use
it
on
the
stock
level,
but
even
so,
actually
this
value
declares
of
error,
whether
it's
possible
or
not,
to
specify
the
to
specify
the
decimal
value.
A
For
example,
if
you'll
specify
this
use
quantity
decimal
as
no
and
you
will
go
and
and
try
to
specify
the
quantity
as
a
decimal
you're
supposed
to
get
a
validation
error
as
soon
as
you
have,
this
inventory
configuration
option
assigned
to
yes.
So
we
allow
to
specify
in
there
that
decimal
value
so
that
we
have
a
dedicated
option
which,
which
is
responsible,
whether
we
allow
or
disallow
the
decimal.
A
A
Jonathan
Jonathan
approached
us
this
week
and
also
he
requested
functionality,
which
is
like
the
long
story
short
so
Jonathan
like
they
have
a.
They
have
a
system,
integration
of
Emma
file
with
external
European
system
for
Jonathan
keys,
and
this
system
makes
the
integration
on
a
timely
basis
and
they
could
be
like
several
orders
placed
in
a
in
a
same
Delta
of
time,
and
when
these
orders
will
come
to
two
can
come
to
the
source
selection
mechanism.
A
A
It
could
be
problem
because
what
we
trying
to
do,
they
try
to
launch
the
source
selection
source
selection
algorithm,
but
taking
into
account
that
the
source
selection,
making
algorithm
in
in
our
case
does
not
does
not
take
reservations
into
account,
and
is
it
like
either
going
to
be
two
orders
placed
like
order,
one
and
order
B
or
there
a
and
order
B?
And
if
there
are
just
three,
let's
say
three
items
on
a
on
a
on
particular
source
and
the
boss
of
this
order
like
order
it
items.
A
Actually
it
means
that
for
second
order,
we
can't
fulfill
the
order
from
from
from
the
same
from
the
same
warehouse,
because
we
like,
because
the
the
first
order
will
will
resolve
and
will
deduct
two
items
out
of
these
three
available
items
and
that's
why
Jonathan
proposed
us
to
actually
to
introduce
the
possibility
to
make
a
source
deduction
first
deduction
at
the
time
of
Chicago.
But
what
what
he
really
needs
is
this
source
level
reservation
and
III
describe
is
right
here,
and
this
is
this
really.
A
Paul
Paul
will
demonstrate
how
the
source
level
reservation
implemented
in
in
but
looks
like
this,
as
if
functionality
could
be
useful
for
quite
a
lot
of
people.
Quite
a
lot
of
business
cases
and
like
applying
this
source
source
level
reservation
people
can
actually
achieve
achieve
the
functionality
of
the
first
duction
at
the
checkout
time.
A
So
this
is
pretty
interesting
and
the
so
that,
for
example,
you
know
need
to
implement
the
functionality
of
working
with
the
quote
and
like,
instead
of
instead
of
order,
because
at
the
time
of
the
order
is
placed,
we
don't
have
the
order
object.
We
have
just
what
object,
but
what
we
can
do.
We
can
just
turn
the
solar
selection
algorithm
and
and
make
the
source
level
reservation.
A
So
this
is
this
quite
a
lot
of
different
different
questions
and
the
different
use
cases,
what
we're
dealing
with
on
a
day
to
day
basis,
and
actually
this
all
question
raised
during
during
this
week,
the
there
are
actually
some
more
question.
Probably
they
are
not
so
they're,
not
so
interesting
to
be
to
be
discussed
during
the
demo
meeting,
because,
on
all
other
question,
answers
could
be
found
on
on
a
MSI
day,
deaf
dogs,
on
a
on
a
depth
of
magenta,
deaf
dogs
and
the
owner
MSI
wiki
pages.
A
So,
but
this
is
a
pretty
interesting
cases
I
just
highlighted
which
our
guys,
who
make
MSI
customization
and
the
integration
start
with,
and
just
to
make
you
aware
so
that
I
I
will
I
will
stop
present
in
this
part
and
the
the
next
presenter
gonna
be
colleagues
who
will
who
presently
preach
interest
on
stuff
and
the
integration
of
the
about
API.
So
this
is
defense,
stuff
actually
implemented
by
Alex
on
his
Trek
other
other
community,
Fred
and
Alex.
Okay,
so
I'm
stop
talking
I'm
I'm,
quite
a
lot
already
so
Alex.
C
C
So
basically,
currently
magenta
has
queuing
system
like
RabbitMQ
can
be
used
or
database
connection,
and
basically
the
standard
have
to
be
that
the
database
connection
is
always
available
by
default,
and
if
you
want,
you
can
switch
to
say
to
Revit
mq,
but
but
but
currently,
a
synchronous.
Api
is
only
supported
by
the
queuing
system,
so
like
Revit
mq
and
the
idea
journey
and
in
our
track
he
also
has
an
idea
to
switch
Genesis.
C
The
database
connection
have
to
be
default
and
it's
actually
supported
out
of
box
by
Magento,
and
if
you
want
to
switch
to
queuing
system,
you
are
doing
it.
So
basically,
I'll
show
you
a
bit
of
code
this
one
this
one,
that's
a
inventory
kettle
had
mini
UI,
so
the
source
which
sign
in
the
ego
picks
me
around
a
sign
in
this
force
and
the
multiple
implementation
of
the
synchronous
API
in
the
MSI
module.
And
what
is
they
doing?
C
C
So
we
define
your
service
contract
and
then
each
topic
name
is
mapped
to
the
to
the
connection
tab
and
the
by
default
in
Magento.
Currently
implementing
that
the
connection
tied
is
mqp
and
the
simplest
way.
It
looks
like
just
to
change
this
name
to
database,
but
it's
not
working.
Unfortunately,
in
this
way,
because
I'll
go
back
to
the
implementation,
this
mass
publisher,
which
is
using
by
as
you
know,
separation,
module
of
magenta,
it's
designed
and
developed
for
MPP.
C
Only
so
if
we
want
to
have
the
database
connection
available,
we
have
to
create
the
own
publisher
and
also
then
later
we
have
to
create
the
own
consumers
that
will
execute
those
messages
in
consumer
somewhere
here
so
yeah.
Currently
in
a
separation
model,
mass
consumer
and
the
connections,
he
is
also
set
to
mqp.
So
this
consumer
will
not
work
with
databases
only
if
you
change
this
one,
this
names
here
and
this
connection
here-
and
we
have
this
issue
on
a
synchronous,
simple
track.
C
So
we
are
really
looking
for
the
people
for
interest
and
then
and
who
can
who
can
provide
a
solution,
for
that?
So
idea
is
to
switch
the
synchronous
input
by
default
to
the
database
usage
and
then
only
on-demand
to
use
the
AMQP
connection
basically
like
how
to
do
it
is
all
it.
So
it's
also
quite
clear
from
from
the
beginning,
so
one
limitations
is
coming
from
a
LuthorCorp.
C
Is
that
you
cannot
form
on
topic
name,
you
cannot
have
different
connection
type
enable
at
the
same
time
also
you
cannot
enable
or
disable
them
by
using
Magento
admin,
for
example.
So
if
you
are
not
developer-
and
you
don't
know
what
the
exam
is
you
are,
you
just
cannot
switch
between
the
different
connections
and
was
the
idea
behind
behind
the
possible
implementation
of
this
stuff.
Is
that
on
a
step
so
generally
those
connection
for
each
topic?
Those
topics
yeah
those
two
files,
they're
generated
on
fly,
and
then
there
is
a
cached.
C
So
the
idea
is
to
use
by
default
the
database
connection
here
to
generate
those
files
by
using
the
database
connection
and
also
make
those
files
also
generated
will
by
default.
So
because
here
is
also
using
the
connection
type
and
then,
if
you
let's
say
define
in
your
environment,
HP
file,
RabbitMQ
connection,
then,
when
you
flash
your
cash
most
file
will
be
generated
by
using
another
another
consumer
and
they
using
the
mqp
connection.
For
example,
it's
like
a
just
a
short
glance,
how
it
can
be
implemented
and
how
at
least
we
see
it
currently
yep.
C
A
I
believe
no
question
so
from
from
then
premise:
I'd
perspective,
we
like
we
agreed
with
Alex,
and
also
we
agreed
with
Marc
that
probably
at
the
quickest
solution,
what
we
will
do
from
Amazon
phone,
we
will
roll
back.
We
will
revert
our
changes.
We
introduced
four
default
mode
for
inventory
transfer,
and
actually
we
already
did
that.
A
We
already
recorded
that
and
our
default
way
of
source
item
transfer
gonna
be
synchronous,
and
actually
it's
not
really
bad,
because,
like
two
two
weeks
ago,
it
should
is
this
guy
Alex
Lu
Xun
make
synchronous
transfer
to
work
very
very
fast,
so
in
the
an
actually
route
called
why
we
wanted
to
make
the
asynchronous
transfer
from
source
to
source
was
that
our
performance
degradation
and
actually
taking
into
account
that
we
fix
the
performance
degradation?
We
are
not
so
critical
regarding
the
default
model,
I
think
on
us
transfer.
That's
why
I?
A
Currently
we,
where
reverse
that
feature
and
now
those
merchants
who
want
to
proceed
that
them,
the
separation,
you
know
I
think
way.
They
still
can
do
it,
but
currently
they
have
a
limitation
that
the
rabbitmq
should
be
installed.
So
the
separation
would
not
work
for
the
my
secure
doctor
until
contributors
will
deliver
this
functionality
to
this
to
the
track
led
by
alex
and
we
MSI
track.
We
would
be
able
to
use
the
fruits
of
the
goodness
brought
to
the
body
bag,
so
this
actually
house
happens
on
the
open
source,
so
somebody
consumption.
A
A
Top
document
and
the
in
the
scope
of
this
document,
quite
recently,
we
added
actually
new
ice
and
the
looking
fuse
of
the
store
picked
up,
gonna
be
gonna,
be
present,
that's
gonna
be
implemented,
and
what?
What
so?
What
Rodriguez
is
asking
for
he's
asking
for
whether
email
and
vloggin
will
be
added
at
the
payment
step,
so
the
payment
step
is
before
the
shipment,
one
the
same
as
will
already
have
for
virtual
product.
A
A
A
So
currently,
like
I
like
here,
we
need
to
to
provide
two
different
UIs
depending
on
the
dependent
on
guest
and
register
the
user,
because
I'm
not
sure
whether
it's
good
to
provide
an
email
address
for
the
store,
pickup
notification.
We
can
just
use
email
over
existing
existing
customer
and
just
send
the
store,
pickup
notification
to
this
email.
D
Yeah
it
we
need
to
expand
this
mock-up,
but
we
should
handle
it
in
the
same
way.
We
already
do
for
existing
orders
where
it's
it.
It
appears
the
same
as
that
the
top
mock-up
that
you're
showing
where
they're,
prompted
to
enter
an
email
address,
but
if
they
enter
an
email
address
that
is
already
associated
with
a
user
account,
then
they'll
be
prompted
to
log
into
that
account.
Mm-Hmm.
B
D
Then
assuming
they
they
do
that
either.
If
they
do
login,
then
on
the
pickup
and
store,
we
don't
need
to
ask
again
for
their
email
address
it's.
It
should
be
the
same,
though,
with
with
guests.
If
they
don't
have
an
account
with
the
internet.
Email
address,
that's
its
new,
unique
at
email
address.
We
don't
need
to
ask
them
second
time
on
the
next
screen,
but
we
can
just
make
it
to
guests
to
check
out.
D
E
D
A
B
D
It
may
be
based
on
the
payment
method.
I'm
not
asked
to
enter
it
again.
In
this
case,
it's
it's
just
a
sample
store,
so
I
only
have
checked
money
order,
enabled
there's
the
check
box
for
my
billing
and
shipping
address
or
the
same
and
then
place
order.
So
I've
only
been
asked
for
an
email
address
on
the
first
screen,
which
is
the
shipping
screen.
Okay,.
F
D
If
you
go
back
to
the
mock
up,
actually
then
we'd,
we
have
that
correctly.
I,
just
read
it
wrong.
Thinking
that
the
first
page
came
after
the
second
I'm
sorry,
they
went
in
order,
but
they
don't
the
way
that
it
works
is
that's
just
it's
a
tab
view.
So
the
first
thing
they're
asked
for
is
they'll
you
in
their
email
address
in
any
case,
and
then
they're
asked
for
their
address.
D
If
they
are
shipping
and
if
they
only
click
pick
up
in
store,
then
they
are
asked
for
just
their
email
address,
mm-hmm,
with
the
ability
to
log
into
account.
If
that
email
address
already
exists,
so
I
would
just
want
to
make
sure
that
the
way
this
forum
works
is,
if
you
type
in
your
email,
address
and
you're
on
the
shipping
tab
and
then
you're
like
oh,
no
wait,
I
want
in-store
pickup
and
you
click
pick
up
in
store.
What
you've
entered
in
that
field
should
persist.
A
A
G
I'll
show
you
I
think
it's
small
issue,
but
still
important,
and
it's
about
my
section
turn
short
from
source
to
source
well
consider
blood
products
which
was
assigned
to
default
source.
So,
as
you
may
see,
my
screen
I
have
configurable
products,
these
two
option:
red
and
blue.
It's
assigned
to
default
source
with
some
quantity,
I
mean
child
products,
and
originally
it's
in
stock,
however
status
in
stock.
G
F
A
So
we
could
say
that
in
the
scope
of
our
upcoming
but
MSI
Petrelli's,
we
fix
several
issues
on
in
inventory:
transfer
improve
the
performance,
fix
the
fix
the
inventory
configuration,
which
was
also
buggy,
and
now
we
will.
We
fix
the
issue
for
the
for
the
composite
product,
so
I
believe.
Actually
the
issue
would
be
reproducible
and
not
only
for
configurable,
but
for
grouped
product
as
well,
so
it
should
be.
It
should
be
for
all
complete
product
type
and
I
believe
that
this
fix
supposed
to
fix
this
for
group
product
as
well.
A
E
E
All
of
that
information
to
one
page
in
the
wiki
and
also
starting
to
track
all
of
the
release,
notes
so
you'll
see
all
the
info
that
used
to
be
on
that
overview
page,
but
it
was
kind
of
lost
and
hiddenness
got
its
own
page
here,
including
a
kind
of
a
quick
overview
of
what
we
released,
the
first
release
of
MSI
and
a
draft
of
what's
to
come
for
the
one
one.
Zero
I
need
to
remove
that
little
note.
E
E
You
know
a
short
snippet
inner
introductions
to
them,
as
well
as
how
to
configure
them
so
you'll
see
the
source
priority
algorithm,
which
doesn't
really
require
much
configuration
beyond
mapping
all
of
your
sources
to
a
stock
and
putting
em
in
order,
but
it
also
now
includes
the
new
distance
based
algorithm
that
Ricardo
has
been
we're
working
on
this
is
draft,
so
it
may
change
an
update
as
we
get
closer
to
packaging.
This
content
is
already
prepared
as
well,
for
the
published
online
guide,
so
we'll
be
ready
to
push
all
of
it
at
once.
E
But
this
gives
you
an
introduction
to
everything.
Now
it
includes
how
to
configure
your
Google,
Maps
I
went
through
and
kind
of
captured
all
that
information
on
setting
up
your
Google
API
key
any
key
screens
that
merchants
will
need
to
see.
This
is
the
merchant
side.
Kevin
is
actively
working
on
the
dev
Doc's
content
today,
he's
starting
that
work,
so
it'll
give
you
kind
of
a
quick
introduction,
as
well
as
seeing
these
new
screens.
That
will
be
added
to
the
global
configurations
under
your
store
configurations
inventory
setting.
E
So
you
can
see
all
those
including
how
to
configure
your
offline
calculations,
which
does
include
a
new
CLI
command
and
I've
included
kind
of
what
that
command
is
and
how
to
use
it.
Verify
this
with
Ricardo
and
may
have
some
updates
on
this
because
he's
a
little
busy
right
now
and
then
finally,
msi
fa
Q's,
as
we
keep
getting
questions
coming
in
issues
being
answered
by
I,
Gore
and
others
I'm
going
to
keep
collecting
that
information
here.
So
we
have
it
all
in
one
place
as
well
as
linking
to
documentation
as
we
can.
E
So,
if
you
ever
have
questions
feel
free
to
check
here
as
well.
If
you
have
some
information,
you'd
like
to
add
to
it,
just
let
me
know
and
I'll
get
that
in.
So
that's
where
we
are
right
now
as
well.
You
know
if
you're
new
to
msi
under
the
msi
user
guide
you'll
find
all
the
links
to
the
in
development
branch
user
guide.
This
will
always
be
ahead
of.
What's
live
with
a
link
to
live
as
well
as
links
to
all
of
our
dev
Docs
content,
which
is
continually
growing
thanks.
A
E
E
H
A
H
A
A
Looks
like
there
are
no
other
people
who
want
to
do
it,
and
so
that,
thank
you
guys
for
your
time
and
and
I
hope.
The
next
one
in
a
week
would
be
even
even
more
interesting
and
we
will
present
you
that
the
release
of
the
other
and
next
patch
release
of
the
MSI,
but
now
thank
you
for
your
time.
Guys.
Thank
you
for
a
contribution
and
see
you
soon,
my
life.
Thank
you.
Thank.