►
From YouTube: Magento MSI Open Demo. February 22, 2019
Description
Agenda:
hey guys @here in 10 minutes we will start MSI weekly demo where we'll highlight
- what MSI 1.1.0 consists of
- the principle behind independent releases of Core Bundle Extensions by the example of MSI
- tell you about preparation for Magento 2.3.1 patch release
- show several bug fixes fixed during this week
- and last but not least provide an update regarding In-Store Pickup track which we launched during MLAU
A
A
Okay,
so
today
we
will
will
share
with
you
updates
regarding
the
release
we
made
on
a
previous
week,
so
this
releases
1.1
dot
o
of
MSI.
So
we
will
show
you
the
list
of
tickets,
which
already
published,
which
already
got
to
the
to
the
latest
package,
which
is
accessible.
Now
we
have
the
very
cool
magenta
dot-com.
A
So
we
also
will
highlight
this.
This
pool
request
here,
unfortunately
guys
from
Australia,
are
not
able
to
connect
this
meeting,
because
the
current
time
in
Australia
and
the
in
party
in
that
part
where
they
are
III,
am
off
Saturday
right
now,
also
they're
there,
it's
not
really
convenient
for
them
to
join
today's
meeting.
Also,
we
will
will
talk
a
little
bit
about
the
upcoming
release
of
magenta
to
the
three
that
one
and
what
the
msi
version
will
we'll
deliver
it.
A
What
has
been
actually
fixed
and
how
how
currently
works
with
MSI
and
last
but
not
least,
max
Bronco,
who
is
currently
joining
to
today's
meeting,
will
will
demonstrate
you
his
proposal
regarding
how
he,
how
he
see
and
how
he
proposed
to
improve
to
boost
the
performance
of
saleable
quantity
on
the
magenta
product
product
grid
page.
So
that
quite
a
lot
of
updates
for
you.
But
taking
into
account
that
one
of
the
today's
presenter
slalom
scalloped
asked
me
to
make
his
update
to
be
first
in
our
today's
demo
because
he's
in
hurry.
A
So,
let's
swallow
moskaluke
to
to
make
an
update
regarding
regarding
the
current
regression
status.
The
we
now
in
regression,
but
not
in
in
regression
which
students
endured
all
but
integration
regression
which,
to
the
three
that
one
because,
as
you
know,
the
magenta
two
digit
one
release.
It
is
be
unprepared
right
now
to
be
to
be
launched
and
we
are
making
the
latest
preparation
and
chicken
weather
the
latest
version
of
MSI
fully
compatible
and
whether
we
have
any
issue
with
this
release.
So
slower
feel
free
to
share
your
screen
and
make
it.
And
what
you
have.
A
B
B
B
190
is
past
it.
Well,
we
have
five
station
area
as
failed
and
today
even
found
two
new
box,
probably
we're
not
quite
sure
if
it
knew-
or
we
will
investigate
this
issue,
but
it's
about
this
box
about
group
of
products
and
custom
source
and
some
for
test
scenario
skip
because
they
dedicated
to
pill
and
realized
that
the
worker
bundle
product
on
a
custom
source
which
will
be
finalized
later
on
milestone
brief.
B
So
and
to
fail
at
the
dedicated
they
already
known,
but
but
it's
one
backwards,
not
fix
it
yet
I
think
that's
all
about
regression.
We
doing
it
on
cloud
instance,
not
just
with
a
messiah
but
also
enterprise
version
of
magenta,
to
be
sure
that
we're
not
broken
something
on
enterprise
version
of
magenta
as
well.
B
So
let
me
go
to
the
issues
is
what
was
created
for
core
team
of
magenta
and
I've
been
investigating
all
the
issues.
What
we
have
in
our
wiki
page.
One
issue
was
fixed
it
before
it's
96,
six,
it's
already
and
magenta
2.30
unreleased
version
magenta
its
order
status
after
consolation
and
after
my
investigation,
another
four
issuses
I
found
out
that
two
already
been
fix.
It
one
is
number
ninety,
six,
five,
four
five.
B
B
B
B
B
B
D
B
B
Yeah,
so
order
status
is
complete.
Now
the
problem
was
that
order
status
was
protesting
and
this
problem
is
solved
or
the
status
complete
order
status
complete.
If
we
are
these
two
issues,
what
was
sold
in
core
magenta
I,
as
you
may
see
here,
I
am
taking
on
branch.
They
have
2.3
that
one
release
I
think
that's
all
about
issues,
because
two
other
issues
are
not
fix
it.
Yet
it's
about.
B
B
B
A
This
leads
to
the
correct
computation
of
the
saleable
quantity
for
our
products,
and
if
we
have
some,
if
they
have
this
occasion,
when
the
order
is
not
completed
when
it's
not
closed,
this
is
almost
for
sure
leads
to
the
to
the
problem
of
quantity
calculation.
There
was
no
such
problem
before
we
introduced
him
aside,
because
at
the
time
of
of
magenta,
1
or
magenta
to
that
altar,
that
one
were
to
the
two
we
made
all
that
one.
So
the
quantity
calculation
was
really
simple
and
all
the
quantity
calculation.
A
A
Statuses
could
not
interfere
and
break
the
quantity
calculation
and
the
scenes
changed
drastically
since
we
added
MSI
and
now,
if
the
order
is
not
in
the
correct
status
or
if
there
are
some
poor
buck
core
box
or
bugs
with
with
the
checkout
process
or
box
with
the
order
processing,
this
box
will
directly
lead
to
problems
with
the
quantity
calculation
in
inventory.
That's
why,
for
us,
the
box
with
the
order
processing
are
really
these
bugs
have
really
high
severity
for
us
and
the
high
priority.
A
B
B
B
It
observes
some
item
of
such
products
and
when
I
creating
shipment,
it's
keeping
constellation
page
because
we're
not
managing
stock
in
this
case,
and
it's
go
to
directly
to
creating
different,
though
I
miss
Machiko,
because
there
is
no
sense
of
selecting
in
any
sources
when
you
not
managing
source
stock
sources.
It's
all
the
same
in
other
back
also,
a
PR
was
also
provided
by
vitaliy
bottom.
B
B
A
A
You
swallow
a
presentation
and
810
the
next
one
gonna
be
max
Ponte,
because
max
is
also
short
on
time
and
I
will
just
provide
a
short
the
ground.
Regarding
the
regarding
the
thing
which
muslin
are
going
to
present,
the
marks
like
back
to
week
ago
or
maybe
two
weeks
ago,
max
grab
a
ticket
regarding
the
performance
improvement
for
MSI
and.
A
A
And
I
still
did
not
manage
how
to
share
the
stream
yeah.
So
actually
we
have
pretty
tricky
task,
because
what
we
edit
on
the
product
grid
page
we
added
these
two
columns
of
the
quantity
per
source
and
saleable
quantity
and
both
of
these
columns
actually
formed
by
like
porn
by
additional
calls
to
our
service
layer
to--for
for
the
quantity
per
source.
We
are
retrieving
all
the
source
item
by
by
particular
sq
for
each
particular
cell.
A
Regarding
the
saleable
quantity,
the
computation
even
more
tricky,
because
on
the
front
end
we
did
not.
We
didn't
have
a
situation
when
one
product
could
be
considered
in
the
scope
of
different
stocks
so
like,
because
we
consider
the
the
like
stock
at
some
kind
of
the
context
for
product
and
on
a
front
end.
A
We
also
make
all
the
operation
with
the
product
in
some
particular
one
and
only
one
stock,
but
here
on
the
on
the
product
page
on
the
product,
page
click
on
the
product
grid
page,
it
makes
sense-
and
this
is
really
usable
for
merchants-
to
see
different-
that
saleable
quantity
on
different
stocks
and
especially
taking
into
account
that
each
stock
is
represented
by
own
table
in
our
database.
We
end
up
with
quite
a
lot
of
additional
additional
service
calls
and
quite
a
lot
of
additional
my
sequel
queries,
because
this
data
grab
from
different
different
tables.
A
That's
why
adding
this
functionality?
We
are
like,
like
we
added
this
performance
degradation
for
this
page,
because
this
additional
functionality
brought
additional
resources
to
be
utilized
and
additional
like
using
resources
to
be
spent
to
build
these
two
columns
and
like
this
pretty
tricky,
because
what
can
we
do
like
from
one
side
is
to
make
this
data
is
not
so
accurate
so
because,
like
for
example,
regarding
the
saleable
quantity,
we
can
just
not
apply
all
the
reservations.
A
But
this
can
lead
to
some
confused
from
the
merchants
point
of
view,
because
if
you,
because
in
Magento
we
used
to
have
the
latest
and
the
most
fresh
data
in
the
degrees
and
if
it's
acceptable
to
provide
some
delay
in
the
some
stale
data
on
the
front
end,
it's
not
possible
to
provide
this
data
for
merchants
on
the
back
end.
So
merchants
who
usually
wants
to
see
they're
the
most
updated
and
the
most
fresh
data
in
the
magenta
back-end.
A
D
However,
as
part
of
an
aside
and
project
I
did
assign
to
myself
performance
improvement,
tasks
to
improve
sellable
quantity
on
product
grid,
I
spent
about
an
hour
or
so
to
figure
out
how
overall
MSI
works
in
terms
of
stocks
sources
and
so
on
different
assignments
and
before
I
actually
jumped
into
performance,
optimization
or
while
I
was
working
on
performance.
Optimization
I
found
out
that
I
could
create
a
small
improvement
for
manage
stock
grid
for
fixing
a
label
of
assignment
sources.
As
you
can
see,
it's
a
fixed
version
of
a
silent
sources.
D
I
created
the
poly
quest
in
this
pool
request.
We
can
find
a
label
change
which
includes
a
pop-up
stop
grid
and
translations
and
MFDs
test,
and
if
you
guys
would
like
to
check
marriage,
this
poly
course
it
would
be
really
appreciated
because
I've
waited
couple
of
days
but
going
forward.
As
I
said,
while
I
was
doing
this
performance
investigation,
I
I
did
share
how
so
the
quantity
field
works
and
have
it
Lamas
information
pours
the
sewol
quantity
column
for
value
pair
product
and
what
I
need
I
generated.
D
First
of
all,
I
started
using
much
of
a
compiler
to
find
out
some
points
in
terms
of
how
fast
the
pair
data
source
method
is
execute
and
provide
sellable
quality.
Information
and,
as
part
of
this
is
profile
to
generate
result
for
one
product
execution
and,
as
you
can
see,
is
almost
super
fast,
almost
right
and
then
I
used
performance
profile,
medium-sized
performance
profile
in
order
to
generate
generating
40k
products
or
I
had
a
screen
shot.
A
D
A
Yes
and
you-
yes,
yes,
yes,
sorry
I
missed
what
you
just
yeah
yeah
yeah
I
just
wanted
to
clarify
and
make
sure
that
you,
edit
use
not
stock
stocks
and
sources,
because
the
profile
which
you
used
generate
data
just
for
the
single
stock
notion.
So
it
creates
just
a
single
stock
and
visible
source
and
fill
it
with
it
like
that
data.
But
after
that
to
make
the
performance
measurement,
especially
for
this
particular
case,
where
you
have
the
issues
with
the
saleable
quantity
you're
supposed
to
use
these
additional
stocks.
A
E
D
The
problem
in
performance,
not
only
in
spokes
less
courses,
but
also
in
amount
of
SQL
queries
or
database
operations
or
yeah,
probably
number
of
queries
generated
for
a
single
product
item
in
order
to
return
back
sellable
quantity,
because
there
are
some
calculations
on
PHP
side
as
well
as
independent
requests
to
database.
So
long
story,
short
I
generated
medium
profile,
I
checked,
and
it
appeared
that
if
it's
sometime
around
14
second
and
yes
eager
you
write
14
seconds,
it's
only
with
default,
talk
and
default
source.
D
Then
I
removed
all
this,
because
my
my
machine
was
dying
with
all
this
I,
don't
know,
probably
with
database
CPU
and
memory
issues
on
my
local
I
I
did
remove
whole
database
and
I
created
from
scratch,
and
then
I
created
two
sources:
two
stalks
and
two
products.
Probably
for
me,
it's
more
than
enough
in
order
to
first
of
all,
I
found
out
the
problem
where
it's
coming
from
and
second
of
all
like
understanding
in
which
way
we
potentially
can
improve
performance
and
introduce
performance
fixes
for
this.
D
I
also
went
ahead
and
created
sellable
quantity,
column
and
product
read
performance
proposal
which
I
encourage
you
guys
to
review
and
provide
feedback.
So
in
terms
of
performance
proposal,
there
are
a
couple
of
things
we
can
do
in
order
to
improve
so
the
quantity
or
prepare
the
test
data
source
method
execution.
D
D
Prepare
data
source
method
execute
in
order
to
provide
a
list
of
sellable
quantities.
So
in
terms
of
a
solutions
there
are
a
couple
of
items.
I
would
like
to
propose.
First
of
all,
is
the
whole
idea
about
prepare
data
source
before
you
have
a
look
into
the
code
is
that
when
we
go
through
each
row
and
each
row,
it's
data
representation
of
a
product
for
a
product
grid
and,
as
we
can
see,
line
number
70.
D
D
D
F
D
First,
we
will
check
prepare
data
source.
It
checks,
whether
not
for
a
particular
product
type
in
product.
We
can
have
a
stock
management,
so
we
can
filter
a
list
of
schools
or
items
which
we
can
work
with
going
forward
and
we
can
put
it
in
search
criteria
interface
and
we
can
provide
in
to
execute
method.
And
then
this
gets
all
the
quantity
data
execute
method
will
be
responsible
for
retrieving.
D
So
several
quantity
list
of
parameters
and
as
I
said
that
there
are
top
options,
how
we
can
work
with
or
implement,
execute
method.
First,
one
is
introduced
to
pass
one
search
criteria,
argument
and
execute
method
will
be
responsible
for
dealing
with
the
search
criteria,
depending
on
on
answer
to
a
question
which
is
still
open.
I
have
a
single
open
question,
but
we
will
get
into
this
in
a
couple
of
seconds,
so
we
will
pass
search
criteria
and
based
on
this
input,
arguments
which
is
going
to
be
a
filter
of
all
schools
available
for
Stockman.
D
We
will
return
a
list
of
sellable
quantity
data.
Our
second
second
option
would
be
instead
of
search
criteria
for
execute
method
for
get
sellable.
Quantity
data
is
to
pass
list
of
schools
and
list
of
type
II's
which
are
which
are
available
for
stock
management.
However,
the
second
option
is
not
preferable,
because
I
think
Iger
can
can
correct
me
or
add
few
cents
about
consistency
and
about
optional
arguments
or
or
the
fact
that
we
don't
really
need
to
pass
types.
Tigey's
type
II's,
however,
like
there
is
option
number
2
what
we
can
do.
D
We
can
pass
array
of
schools
and
array
of
type
Aggies
and
based
on
this
data
inside
gets
all
the
quantity
data
we
can
process
logic,
processes,
information
and
return.
Data
back
for
problem
did
ii
ii
improvement.
What
we
can
do,
we
can
use
stock
repository,
get
list
method
instead
of,
as
far
as
I
remember,
if
we
will
go
deeper.
D
Stock
repository,
yes,
stock
repository
at
least
matter,
because
here
we
can
see,
we
return
a
list
of
senate
school
stock,
ids
forgiven
school
and
then
we
perform
for
each
and
for
each
stock
a
new
way
with
them
trigger
the
repository
god
and
with
the
single
waiver.
If
a
return,
a
stock
instance,
we
instead
of
this
cat,
we
can
use
it
at
least-
and
this
is
a
second
proposal-
what
we
can
do
another
time
for
performance.
A
D
A
Interruption
just
to
like
just
to
summarize,
because
you
just
described
like
two
contracts,
so
one
of
them
accept
switch
criteria
and
other
one
except
the
and
Harry
excuse.
But
what's
going
to
be
inside
of
the
implementation
of
that
service
like
how
we
reach
this
performance
improvement
because,
currently,
like
all
the
stock
data,
are
located
in
the
separate
tables
and
potentially
especially
like
for
b2b
users,
it
could
be
in
like
a
numerous
number
of
stocks
that
we
are
still
and
dogs
in
varying
different
storages.
A
D
A
D
No
no
I
proposed
instead
of
using,
for
example,
stock
repository,
great
method,
which
will
return
a
single
stock
instance.
I
propose
to
use
a
get
list
method
which
will
return
a
list
of
available
stock,
Spurs
sk,
you
assign
it
stock,
iespera
scale
and
not
per
SKU,
but
per
the
list
of
schools
PhotoPass.
A
But
yeah
I
got
your
point
so
but
then,
for
example,
you
you
see
that,
for
this
particular
SQ
is
assigned
to
100
stops
the.
In
any
case,
you
end
up
with
Quarian
for
one
particular
product
like
this
100
different
stock
tables,
even
so
that
this
query
would
be
pretty
fast
because
you
hear
Aquarian
by
the
primary
key
in
this
table.
But
in
any
case
is
gonna,
be
like
100
different
queries
just
for
one
row
or
one
cell
in
in
the
product
table.
F
A
You're
talking
about
the
service
which
will
provide
you
a
list
of
stocks
to
which
this
product
is
assigned
to
so
here
you
make
some
performance
improvement
regarding
the
regarding
the
determine
in
part
to
how
many
stocks
the
given
product
is
assigned
to.
But
now
you
let's
say
your
service
returned
like
100
different
stocks,
so
now
you're
supposed
to
retrieve
all
that
quantities
on
all
of
these
stops
and
currently
it's
implemented.
We
are
independent,
independent
service
calls
and
independent
independent
data
like
database
query.
So
in
any
case
he
would
be.
D
We
can
improve
all
this
SQL
queries
and
data
retrieval
by
minimizing
amount
of
requests
which
we
can
set
and
the
open
question
I
have
is
related
to
get
product
saleable
quantity
class,
which
contains
logic,
calculation,
logic,
sellable
quantity,
taking
into
account.
Existing
reservation
also
reservation,
because
I
found
this
like
15
lines
of
logic,
on
how
to.
F
D
D
A
Like
you
wanted
to
optimize
the
the
logic
behind
the
get
product,
saleable
quantity
service
call,
and
you
wanted
to
move
this
logic
on
to
the
database
level
so
that
try
to
optimize
the
whole
computation
of
the
of
the
determining
the
saleable
quantity
for
for
a
bunch
of
products
at
once,
but
not
making
it
like
product
by
product
in
in
a
loop.
What
we
actually
do
building
the
product
grid,
so
they
get
products
available.
Quantity
is
it
actually.
This
is
one
of
the
main
services
in
MSI
and
this
service.
A
Now
it's
not
just
a
static
quantity
which
is
just
retrieved
from
the
from
the
index
table,
but
also
we
apply
all
the
reservation
placed
for
this
in
the
scope
of
different
orders.
Also,
we
apply
the
inventory
configuration,
it
does
depend
on
the
inventory
configuration
like
whether
product
product
is
assigned
like
top
manageability
or
whether
product
is
assigned
some
particular
value
of
back
order
or
whether
product
is
assigned
some
particular
well
to
you
for
minimal
stress,
sold
quantity.
This
Taurus
will
return
the
correct
date.
A
Not
with
join
in
but
Union
in
all
the
table,
all
of
the
stock
table
and
taking
into
account
that
we
don't
have
in
our
stock
table
the
stock
ID
as
a
part
of
the
table,
so
the
stock
ID
actually
contained
in
the
name
of
the
of
this
particular
table.
So
we
have
like
inventory,
underscore
stock
underscore
one
where
the
one
is
the
ID
of
the
of
the
Union
table.
A
So
if
you
will
just
make
a
union,
we
will
violate
the
constraint
we
have
on
this
particular
table
level,
so
we
have
to
do
like
some
additional
tables
like
altering
them
on
the
fly,
and
these
like
this
also
can
be
considered
as
optimal
solution,
though
this
is
actually
pretty
tricky.
That's
why
I
don't
think
that
it
is.
It
is
easy
to
move
this
logic
on
to
the
database
follow
first
of
all,
so
what
we
can
potentially
do.
A
We
can
like
decrease
the
accuracy
of
this
data,
so
we
can
show
stale
data,
not,
for
example,
taking
a
reservation
into
account,
but
that
would
be
misleading
for
merchants,
so
that,
like
merchants
will
see
that
sellable
quantity
is
100,
but
that
would
not
take
into
account
several
orders,
which
already
placed
and
actually
which
is
literally
deducted
that
quantity
and
maybe
the
data
would
be
fresh
from
the
product
page.
But
so
it's
not
it's
not
probably
what
our
merchants
want,
at
least
like
I,
had
several
conversation
regarding
that
with
these
different
guys.
Making
this
presentation.
F
A
From
creeks-
and
they
told
me
like
that
this
one
like
they
realize
that
data
on
on
a
product
grid
afresh,
so
that
they
are
not
stale
so
ignorant
with
the
quick
glance
looking
at
the
product
product
Rick
wants
to
get
the
latest
data.
So
currently
it's
really
hard
to
achieve
this
functionality
with,
like
with
database
queries,
so
potentially
what
we
can
do.
A
We
can
try
to
like
to
build
this
grid
with
the
dummy
data
and
like
we're
ajax.request
applauds
in
your
data,
so
the
merchant
will
be
given
like
the
first
response
very
quickly,
but
the
saleable
data
would
be
calculated
a
little
bit
with
some
delay
and
it
will
arrive
with
the
Ajax
response
little
bit
later.
So
this
is
this
kind
of
possible
solution
for
this
problem,
or
actually
I,
don't
even
know
maybe
like
mark.
A
Maybe
you'd
have
any
idea
how
this
problem
could
be
resolved
from
the
look
and
feel
side
not
from
the
technical
perspective,
because
callate
I,
don't
like
we.
What
we're
discussing
just
so
like
worsen,
makes
it
make.
The
data
is
like
not
so
fresh
so
like
the
spoiled
merchants
experience,
but
maybe
it's
somehow
possible
to
improve
the
performance.
We
are
changing
the
look
and
feel.
E
F
E
D
D
A
A
That's
why,
like
most
of
the
operations
for
most
of
the
entities
we
introduced
and
MSI,
we
support
the
bulk
API.
But,
regarding
this
talk
we
always
considered
that
like
when
we're
dealing
with
the
system
when
we
are
customer
or
we
are
working
with
emissaries
Magento
on
a
headless
way,
you
will
be
always
work
in
a
context
of
a
single
school.
That's
actually
why?
How
typically,
how
the
typical
scenario
works
on
magenta,
so
when
one
customer
comes
to
to
Magento
front
end,
we
based
on
that
sales
channel
in
our
Cadence's
website.
A
We
resolve
the
current
stock
and
then
all
the
operations
are
Gardens.
A
regarding
the
inventory
are
like
a
maid
in
a
Cove
of
the
given
stock.
That's
why
owner
on
a
front
end?
It's
not!
So
we
don't
consider
that
this
is
correct
business
separation
that
that
that
customer
will
deal
with
different
talks
when
he,
when
he
working
with
with
the
magenta
front,
and
let's
say
because
if
you
place
an
order,
you
are
dealing
with
one
stop.
A
Only
if
you,
if
you're,
making
a
return,
you
are
dealing
with
one
stop
only
if
you're,
if
you're,
making
invoice
or
partial
shipment
you're
dealing
with
one
stop
only.
So
there
is
no
any
business
separation
except
this
admin
grid,
where
we
just
want
to
simplify
this
realization,
poor
merchant.
So
we
don't
have
any
example
of
the
business
operation
when
whether
merchants
or
customers
supposed
to
deal
with
different
stocks.
That's
actually
why
we
don't
introduce
the
service
service
layer
which
provide
the
possibility
to
work
with
products
from
different
different
stocks.
D
It's
implied
introducing
a
service
layer
or
to
work
with
bulk
of
products.
It's
it's
about
rendering
existing
data
and
calculating
this
data
on
the
fly,
and
the
question
would
be
whether
merchants
and
you
said
that
merchants
would
like
to
see
an
up-to-date
sellable
quantity
per
product
for
all
products
like
immediately.
However,
let's
consider
the
fact
that
order
treatise
is
updated,
I
synchronously,
and
even
with
at
the
given.
Second,
we
have
five
new
orders.
Merchants
will
not
buy
initial
ceases.
Five
new
products
order,
grief
like
it
would
be
like
so
from
one
site.
D
A
We
track
the
changes
and
update
this
grid
automatically.
So
yes,
so
all
the
data
which
is
shown
on
a
non
magenta
admin
panel
is
a
stale.
The
only
issue
were
talking
about
the
delay.
How
like
what
this
tail
in
this
case
mean,
so,
whether
it's
like
mean
minutes
hours
or
whether
it
mean
like
that,
if
you
refresh
the
grid,
you
will
get
the
updated
data.
A
So
if
you
would
not
keep
track
that
reservations,
our
data
would
be
like
would
be
really
stale
and
it
would
be
confusing
because
we
would
be
showing
different
data
on
the
level
of
product
and
on
the
level
of
product
Li.
So
probably
it's
a
good
discussion
and
let's
proceed
further
regarding
the
regarding
the
demonstration,
because
we
also
have
several
topics
to
highlight
more.
A
But
let's
proceed
with
the
discussion,
father
on
a
massive
channel
or,
let's
schedule
a
dedicated
meeting,
because
this
topic
is
very
interesting,
because
this
kind
of
collusion
of
the
business
like
business
use
cases
from
the
merchants
point
of
view
in
the
data
visualization.
So
now,
because
I'm
considered
that
product
read
as
a
part
of
the
report
in
tool
in
this
case,
but
not
as
a
part
of
that
real
use
case,
merchants
or
customer
wants
to
deal
in
with
those
picky
pretty
important,
pretty
important
task
to
figure
out
and
to
solve
it.
A
And
this
is
reaching
pretty
important
both
from
technical
and
business
perspective.
But
now,
let's
proceed
further,
because
we
already,
like
you
always
say
in
like
the
long
story
short
but
probably
in
this.
In
this
particular
case,
we
can
just
express
it
the
one
story
short,
so
the
long
story,
long
hidden
right
now,
and
but
this
definitely
makes
sense
for
us.
So,
let's
proceed
with
further
discussions
topic
and.
D
Before
you
will
jump
into
another
topic,
as
I
said
long
story
short,
we
can
proceed
with
this
performance.
Improvements
in
two
steps.
First
step
is
to
optimize
all
single
operations
to
perform
bulk
operations,
and
second
step
is
to
sync
on
about
how
we
can
deal
with
calculation
of
up-to-date,
saleable
quantity
per
product,
and
this
is
what
we
would
do
would
be
to
discuss
offline.
Thank
you
very.
Thank
you.
Thank.
A
A
Dun
dundun,
so
we
just
got
a
performance
issue
so
yeah.
Let's
let
me
switch
switch.
The
the
the
topic
it'll
be
drastically
and
discuss
the
the
release
which
we
done
so
independent
masai
release,
which
was
which
was
done
on
the
previous
week.
You
know
what
it
actually
means:
the
independence
releases,
because
we
are
constantly
saying
that
we
we've
done
the
independent
release,
but
people
many
people
are
still
curious
like
what
what
it?
What
did
that
surely
means.
A
So
let
me
just
of
all,
let
me
show
you
what
what
we,
what
we
released
the
will
release
this
bunch
of
tickets,
so
more
than
30
different,
you
should
be
been
added
to
the
latest
Assembly
of
of
MSI.
The
number
of
these
stories
is
one
that
one
dot
o
as
you
as
you,
as
you
can
notice.
We
both
the
minor
version
of
MSI,
and
actually
this
leads
that
we
did.
This
means
that
we
introduce
some
more
new
functionality
regarding
the
new
functionality.
A
We
like
elasticsearch
port
and
some
some
performance
improvement
and
what
it
actually
means
like
independent
releases,
because
you
know
like
people
from
the
magenta
from
the
magenta
world
are
used
to
the
big
damp
releases,
which
magenta
usually
do
so
like
approximately
once
per
year,
we
launched
the
the
major
release
like
to
the
tree.
The
next
one
gonna
be
to
the
fool
and
along
to
hear,
like
literally
each
quarter
of
we
are
releasing
patch
releases.
But
this
patch
release
is
up
also
they're,
not
really
semantically
correct
I
mean
like
they
not
this
release
the
releases.
A
Don't
follow
this
semantic
versioning,
so
they
don't
follow
somewhere
and
in
this
covers
a
patch
releases
like
to
the
treated
like
just
just
an
example
like
to
the
3.1
or
to
the
studio.
We
are
releasing
new
functionality
like
in
the
scope
of
the
to
the
3.1.
We
are
releasing
the
page
builder
and
the
page
builder
and
is
a
new
big
feature
so
like
if,
if
we
were
following
the
assembler,
probably
it's
supposed
to
bump
at
least
it
is
a
minor
version,
but
taking
into
account
that
our
to
the
tree
dot
Samson.
A
It's
not
that
simple
releases,
but
this
a
commercial
releases
yet
just
to
provide
the
ability
for
merchants
to
get
we're
like
about
our
timelines
and
they
release
cycles.
So
so
this
release
is
usually
bring
quite
a
lot
of
changes
and
some
of
these
changes
could
be
backwards
incompatible.
That's
why
even
upgrading
to
to
fight
releases
merchants
and
the
third-party
developers
usually
start
with
the
situation
when
come
backer
team
competed
incompatible
changes
appears
during
the
release,
and
this
issue
should
be
resolved
many
early
like
programmatically,
etc,
etc.
A
Where
is
this
composer,
this
computer
now
available
via
Reaper
magenta
comb
in
all
the
first
magenta
installation
will
include
the
latest
version
of
msi.
So
if
you
are,
if
you
are
installing
him,
if
you
install
in
magenta,
we
are
come
further
from
the
screech
now
you
will
be
given
the
latest
version
of
homicide.
If
you
already
have
the
magenta
like
magenta
to
the
tree,
that
all
plus
amis
I
wanted
all
the
three
does,
the
previous
version
of
MSI,
you
can
upgrade
the
msi
via
composure,
update
and
comment,
though
this
is
pretty
pretty
straightforward.
A
This
is
pretty
like
easy
to
get
to
get
update
for
the
latest
component
version
and
yeah,
and
thank
you
like
this
is
why
it
is
so
important
for
us
because
we
expect
so
like.
As
it
already
said,
there
is
a
pioneering
project,
but
this
product
is
gonna,
be
like
common
for
other
projects
as
well.
So
that's
gonna
be
adopted
by
page
builders,
they're,
going
to
be
adopted
to
other
components
like
isolated
components.
Probably
you
heard
that
our
chief
architect
control
crew
is
talking
and
spreading
their
main
idea.
A
A
Given
the
updates
and,
of
course,
thank
you
very
much
for
our
major
contributors.
Thank
you
very
much
for
percolating
faster
push,
our
tough
guys
Rick,
who
is
implemented
by
his
own.
He
was
implemented
by
his
own
distant
base.
Algorism
and
too
many
other
guys,
including
Alex
Walloon,
which
he
introduced,
support
for
the
bulk
API
and
who
fixed
several
memory
leakage
at
the
time
of
the
of
the
inventory
transition
from
one
source
to
another
source.
A
So
all
these
contributions
counted
all
these
particular
contributions
matters,
and
we
already
see
that,
like
we
have
bunch
of
updates
and
the
question
regarding
the
new
release
of
homicide.
That's
probably
all
from
my
side.
I
know
that
Laurie
will
add
a
little
bit
more
about
the
release
and
about
the
publication
did
regarding
this
release,
highlighting
the
release
so
worried
feel
free
to
share
what
you
have.
F
Hey
everyone
so
I'll
keep
this
really
short
and
quick.
We
did
release
a
dev
blog.
That
includes
all
the
information
you
need
to
know
to
get
started
with
sigh
1.10
we've
also
updated
the
upgrade
information
if
you're
upgrading
from
10.3.
That
was
the
initial
package
with
two
three.
We
included
a
few
bits
and
pieces
here
of
the
highlights
of
what
we've
provided,
which
you
know,
has
gone
over
extensively
and
very
well,
including
a
few
little
screenshots
to
get
you
interested,
including
as
well
links
to
all
the
documentation
everything
you
need
to
know
to
get
started.
F
It's
all
at
the
bottom
I'll.
Let
you
walk
through
those
look
over
everything
and
a
major
new
addition
for
the
documentation
is.
We
do
have
msi
release
notes.
We
are
going
to
be.
You
know,
engaging
in
these
smaller
releases
that
are
going
to
be
staggered
within
and
outside
of
core,
so
we've
also
got
a
set
of
release,
notes
that
are
completely
specific
to
msi
and
if
we
have
to
have
any
additional
information
on
core
release,
notes
will
provide
links
back
and
forth
between
the
two.
F
C
If
you'd,
like
her
gone
through
a
brief
presentation,
there's
been
no
update
on
automation
and
beliefs.
Lava
covered
all
of
the
manual
so
no
update
there
beyond
Slava's
regression
run
which,
when
it
finishes
up,
will
benchmark
against
the
previous
one.
But
I
can
make
my
presentation
available
to
the
group.
Okay.
A
Cool,
so
probably
this
is
pretty
much
all
this
time.
We
like
the
demonstration,
was
unintentionally
long,
but
I
hope
that
that
was
not
so
boring
and
you
you
enjoy
it
with
with
what
we
shared
with
you
and,
of
course,
like
don't
wait
for
like
don't
wait
for
other
demonstration
and
if
you
had
some
particular
question,
pingas
chat
results
scheduled
medium
and
we
we
are
ready
to
discuss
by
the
way
I
want
to
present
you
one
one
of
the
fork
fork
and
the
I
believe.
Most
of
you
know
this
guy.
A
So
this
is
you
again
Chuck
saguaro
he's
currently
on
a
call,
and
this
guy
will
go
into
draw
in
an
aside
shortly,
because
we
see
that
there
are
too
many
work
on
the
MSI
track.
So
again
we'll
be
working
with
us.
We
will
be
helping
to
you,
and
so
this
is
definitely
good
news
for
us
and
I
hope
that
you
again
will
push
the
PR
processing
and
all
the
other
stuff.
A
We
have
new
project
and
also
I
want
to
take
high
two
guys
from
the
ICM
company
who
can't
they
only
call
the
guys
who
would
like
to
join
the
implementation
of
in-store
pickup
project.
We
already,
we
already
had
two
meetings
with
them
regarding
the
burgundy,
in-store
pickup,
so
the
guys
especially
interested
in
this
future,
and
we
will
schedule
shortly.
The
grooming
and
the
discard
held
it
in
store
pickup
can
be
implemented
implemented.
You,
though,
probably
but
that's
probably
all
for
today's.