►
From YouTube: Magento MSI Open Demo. October 26, 2018
Description
Agenda:
- Status of regression
- MSI Documentation updates
- Web API changes we've introduced
- API interfaces have been adjusted
- Demonstrate several bugfixes done during the week
A
So
hello
guys
welcome
everybody
who
joined
today's
meeting
today
today
is
Friday
and
the
as
usual.
We
will
show
you
update
for
the
for
the
current
week
and
what
have
been
done
on
MSI
track,
what
the
progress
we
have
during
this
week
and
what
what
interesting
news
we
honed
on
a
sidetrack.
So,
first
of
all,
let
me
share
my.
A
Final
T,
final
tickets,
final
issues,
bug
fixes
we
we
had
assigned
to
this
mountain
to
so
actually,
we
delivered
143
story
points
out
of
188
and
they
were
164
pull
request,
deliver
it
in
the
scope
of
milestone
2,
so
we
actually
started
milestone
2
from
from
the
middle
of
July,
and
this
is
how
this
is
actually
burn
down.
Shadow
of
the
of
the
work
done
in
the
scope
of
this
milestone.
A
So,
as
you
know
the
last
three
weeks
we
had
a
regression
and
during
this
regression
we
found
several
bugs.
Actually,
there
were
45
different,
bugs
found
during
all
this
time
and
37
out
of
this
45
bucks
fixed
in
deliberate
and
the
last
bunch
of
bugs
delivery
delivery
things
early
on
Tuesday
and
we
still
have
some
bugs
to
fix,
but
we
actually,
we
don't
consider
them
as
a
as
a
highest
priority.
So
we
probably
this
box.
A
So
this
is
this
is
what
this
is.
A
style
tree
currently
have
regarding
the
bug
fixes
and
now,
after
after
the
delivery
of
the
late
latest
bunch,
and
usually,
we
started
the
final
final
cycle
of
the
regular
version
where
we
just
make
the
final
stabilization
testing
to
to
make
sure
that
everything
everything
works,
and
we
don't
have
some
unexpected
issues
on
a
problem.
So
flour
will
share
the
status
of
the
latest
step
of
the
regression
and
he
will
show
you
the
heap
test
and
the
word
start
we
haven't.
B
A
A
Here
is
here's.
You
can
see
the
statistic
of
all
the
of
all
the
work
done.
So
this
is
small
statistic.
We
gather
regarding
the
pull
request
processing
so
here
you
can
see
that
at
this
point
of
time,
in
the
middle
of
June,
we
actually
release
this
milestone,
one
that
was
done
during
the
mid
magenta
Germany
in
black
in
Leipzig,
and
here
we
we're
releasing
the
mouse
tone.
A
So,
as
you
can
see,
for
example,
during
this
during
this
month,
during
the
squash
tober
first,
we
processed
85
pull
requests,
so
this
is
probably
all
regarding
regarding
the
studies
of
regression,
so
we
will
continue
it
on
the
next
week
and
we
will
ensure
that
everything
works
as
expected
and
we
will
start
working
on
a
product
backlog
as
a
milestone
3.
So
currently
we
have
any
ideas
proposals.
Maybe
some
features
need
to
be
delivered.
A
We
will
add
this
proposal
to
the
milestone,
3
and
3,
and
starting
from
the
next
week,
I
will
share
the
schedule
of
groomin
meetings,
there's
going
to
be
as
usual,
open
groomings
and
everybody
of
you
can
join
and
take
Parsons
discussion
with
product
owner
of
project
with
court.
In
with
me
and
with
main
contributors
of
the
project
and
one
of
the
feature-
and
we
already
started
to
to
work
on-
is
the
integration
of
the
B
to
B,
plus
MSI,
and
today,
Lars
with
us
and
he'll
he'll
share
the
update
of
the
investigation.
A
C
C
Cool
so
the
last
two
weeks,
I
was
working
on
some
issues
about
b2b
in
the
creation
of
MSI.
The
main
reason
was
some
investigation
of
forum,
some
guy,
our
head
of
commerce
attack,
diversion
and
I
created.
Currently
two
issues
at
MSI.
The
first
one
is
for
the
advanced
checkout,
because
the
enterprise
module
didn't
work
with
MSI
I.
Do
some
tastic
manual
testing?
C
What
was
the
problem?
It
use
currently
the
old
inventory
staff,
and
this
was
the
reason
wide
sellable
quantity
ISM
calculated
correctly.
There
was
some
questions
from
you
because
MSI
can
be
shipped
currently
with
out
or
b2b
can
ship
without
MSI,
and
this
is
currently
to
clarify,
and
if
we
do
that,
yeah,
it's
I
can
finish.
This
pull
request.
Also
I
will
finish
the
pull
request
for
the
advanced
checkout
module.
C
C
A
We
have
until
magenta
to
that
sweet
at
all,
but
taking
into
account
that
currently,
we
still
have
magenta
order
management.
So
our
our
enterprise
solution,
which
still
relies
fully
on
legacy
interfaces.
We
are
not
able
to
to
utilize
MSI
interfaces,
because
this
will
affect
our
enterprise
merchants,
who
use
who
use
them
on
and
they
would
be
affected
because
Magento
borders
management
would
not
work.
So
the
b2b
would
not
work
for
them
and
actually
that's
why
we
discussed
yesterday
with
guys
from
Magento
order
management.
So
we
agreed
that
first
of
all,
they
from
their
side.
A
They
prioritize
the
refactoring
of
magenta
order
management
as
much
as
possible,
and
we
will
be.
We
will
be
attracting
our
partners
to
contribute
for
refactoring
of
mom
connector,
so
maybe
tech
division
will
join
us
and
also
today,
I
had
a
conversation
with
guys
from
Chora,
so
Cora
also
interested
to
contribute
to
non
connector,
because
they
also
have
b2b
merchants.
We
use
to
use
more
so,
but,
along
with
that,
at
least
now,
we
will
write
all
our
b2b
fixes
as
an
optional
one.
A
So
we
will
introduce
optional
module
with
this
fixes
as
usual
and
they
actually
in
this
module.
We
will
provide
some
kind
of
around
plugins
and
so
doing
this.
This
module
actually
will
have
dependency
both
to
be
to
be
an
MSI,
so
it
would
be
switchable
and
if
a
Messiah
would
be
just
disabled,
so
in
case
merchant
emergent
uses
Mon
and
B
2
B.
So
this
optional
module
wouldn't
be
wouldn't
be
enabled
as
well,
and
the
the
merchant
will
still
use
the
old
interfaces,
so
the
Catholic
invent
everyone
and
everything
should
work
too
much
reflection.
A
So
I
will
ask
you
to
introduce
light
refactoring
to
use
this
optional
module
with
the
dependency
to
both
be
to
be
an
MSI
and
actually
at
least
now.
This
will.
This
will
fix
this
issue
and
that
would
be
fully
backward-compatible
for
all
our
energy,
but
I
really
liked
how
you
did
it
before,
because,
as
you
did
before
this,
our
desirable
state,
we
want
the
stuff
be
implemented,
so
the
direct
dependency
from
you
to
beat
them
side.
A
So
thank
you
very
much
Lars
for
your
work
and
for
your
first
question
regarding
is
that
b2b
and
I
believe
we
will
deliver.
Unfortunately,
these
issues
wouldn't
be
delivered
for
2.0,
but
I
believe
they
would
be
delivery
to
the
first
batch
version.
So
two
to
the
three
that
one
where
we
supposed
to
provide
the
full
support
of
b2b
and
MSI
Amy.
C
Maybe
if
we
can
push
this
in
a
separate
repository
or
something
like
that
for
to
have
an
installable
and
meter
package
for
for
the
customers,
it's
maybe
a
good
point
to
do
that.
We
must
only
think
about
a
very
place.
This
repository,
maybe
we
place
that
and
in
the
end
comm
repository
or
we
case
that
in
the
private
repository
it's
only
some
some
modules.
They
have
a
dependency,
but
in
a
different
repository
to
build
a
bundle
or
bid
hey.
C
A
Actually
I
believe
food,
this
optional
module
to
be
repository,
because
this
is
supposed
to
be
a
part
of
the
b2b
and,
as
we
already
discuss,
this
is
a
pretty
valid
dependency
for
me
to
beat
Messiah,
so
we
will
put
it
to
the
B
to
B,
but
this
module
would
still
be
optional.
So
if
the
MSI
would
be
disabled,
that
module
would
be
disabled.
Okay,.
C
A
Thank
You
Lars
for
your
update
and
the
next
one
gonna
be
update
regarding
the
documentation.
Probably
you,
you
hurt
the
boss
in
Twitter
during
this
week,
looking
at
how
our
how
our
documentation
devoted
to
REST
API
has
been
changed,
and
now
Kevin,
who
is
also
one
of
the
author
of
these
changes,
will
show
you
update
for
MSI
REST
API
Kevin
feel
free
to
share
your
screen.
D
D
D
D
D
D
The
first
change
in
the
MSI
documentation
is
that
this
API
right
here
used
to
be
delete,
low-quality
notifications,
change
to
a
post
under
check
saleable
quantities.
There
are
two
new
endpoints
these
two
right
here
and
they
are
documented
down
at
the
bottom
here
with
examples,
as
always
and
I
believe
those
that's
also.
These
were
not
previously
documented,
but
I'm
talking
in
for
the
first
time
about
SSA
endpoints,
and
so
these
will
also
be
included.
I
also
like
to
point
out
for
the
first
time
this
has
already
been
published
when
I'm
about
the
time.
D
D
The
deprecation
notices
inside
catalog
inventory
point
to
various
couple
of
documents
here:
I
didn't
want
anyone
to
get
a
404
if
they
just
a
link,
but
this
is
a
list
of
the
interfaces
and
classes
that
have
been
deprecated,
and
so
there
will
fill
this
out
in
the
near
future.
But
this
is
what
is
here
also
sort
of
related.
D
It
was
just
mentioned
that
the
dev
Docs
has
a
new
way
of
displaying
the
the
rest.
Documentation
and
I'll
just
show
that
off
real
quickly.
It's
under
s,
quick
reference,
and
you
have
now
schemas
for
whether
your
admin
customer
or
guest.
Unfortunately,
when
you
load
that
admin,
it's
a
takes
a
long
time
and
we're
working
to
improve
that.
But
I
would
like
to
point
out
that
you
can
search
for
your
favorite
inventory
endpoint
and
find
it
quickly.
So
there
you
go
any
questions.
I.
A
A
A
D
A
Thank
you,
Kevin
for
your
update,
and
now
we
can
go
to
Yvonne
who
will
show
on
behalf
of
Zurich,
who
is
currently
on
a
way
to
meet
unconference
and
curl,
so
he's
not
able
to
present
it
by
by
himself,
but
he
one
will
make
it
on
behalf
of
Rick,
so
it
won't
feel
free
to
share
your
screen
and
make
a
presentation
of
the
day.
Ten
points.
Hi.
A
E
E
A
E
E
E
A
Can
you
please
share
my
screen,
so
the
other
interesting
thing
to
add
regarding
the
Web
API
is
so,
as
you
already
understood,
we,
we
reviewed
all
our
API
before
the
release,
because
for
us
it's
pretty
critical
to
make
a
release
with
all
the
API
is
in
a
good
shape,
because
for
all
the
API
we
introduce
a
backward
compatibility
policies.
You
know
so
we
wouldn't
be
able
to
to
introduce
changes
to
the
guy's
father,
because
all
the
changes
to
ApS
will
definitely
break
introduce,
introduce
some
some
break
for
our
merchants.
A
That's
why
we
are
so
careful
regarding
the
API
and
we
check
them
pretty
carefully,
and
here
I
will
also
show
you
another
update
and
the
pork
was
created
by
by
Ricardo.
So
in
this
cope
of
one
of
his
PO
requests
where
he
was
providing
the
database
consistency
for
them
for
the
in
for
the
stock
migration
from
the
from
the
full
source
to
custom
sources,
he
introduced
the
logic
regarding
them:
data
regarding
the
configuration
migration
on
the
source
level.
A
So
currently
we
have
the
inventory
configuration
on
the
source
level
as
long
as
inventory
configuration
and
stock
level.
So
while
we
provide
the
functionality
with
the
bulk
transfer
of
the
of
the
source
items
along
with
the
transfer,
we
supposed
to
migrate,
also
the
configuration-
and
here
actually
it
was
a
snippet
of
code
recorder-
initially
brought.
A
It
was
the
bulk
API,
because
for
them
you
know
in
mother,
since
Magento
2.2,
all
the
new
API
is
written
actually
should
be
bulky
by
so
the
API
which
accept
an
area
of
entity
entities,
but
not
not
the
only
and
that's
why.
For
example,
you
can
see
that
you
can
see
that
all
our
API
is
except
an
area
of
entities,
but
not
the
single
entity.
So
that's
gonna
solve
that
performance
issue.
We
currently
have
with
our
existing
service
contracts
because,
for
example,
repositories
save
accepts
only
entity,
and
this
introduced
it
performance
degradation.
A
When
we
have
to
process
many
entities
at
once
and
as
you
can
see,
all
our
eight
guys
in
in
introducing
scope
of
the
MSI
are
bulky
guys,
so
they
accept
an
area
of
entities
and,
in
this
cope
of
the
inventory,
catalog
API
required
to
introduce
several
several
copies,
like
bulk
inventory,
transfer,
bulk
source
assign
and
all
of
them
all
over.
This
API
is
actually
worked
with
with
a
bunch
of
entities,
but
the
synchronization
of
inventory
was
a
was
working
on
a
single
entity
basis.
That's
why
I
asked
recorder
to
refactor
this
functionality
and
record.
A
Low
quantity
notification,
in
our
case-
and
this
is
how
record
refactor
this
code,
so
actually
he
totally
eliminated
the
existing
API.
So
the
API
source
item
configuration
delete
which
worked
on
on
a
scope
of
the
single
entity.
So
initially
this
API
accepted
the
only
source
code
and
sq.
By
means
of
this
input
parameters,
it
was
possible
just
to
identify
the
only
entity
and
we
instead
of
this
API,
we
introducing
new
API,
which
process
the
bulk
entity.
So
now
it
accept
it
accept
the
Eric
of
the
source
items
and
you
can
see
that
plug-in
now.
A
Any
loop
inside
so
we
don't
have
that
for
each
loop
on
we
have
the
drastic
another
call
which
accept
a
whole
bunch
of
errors.
That's
all
because
this
implementation
actually
introduces
a
potential,
not
potential
but
real
performance
degradation,
and
now
we
improve
the
performance
introducing
the
corrected
image
which
process
the
bulk
of
entity
and,
along
with
that,
we
also
updated
our
web
api
endpoint
and
now
web
api
endpoint
inventory
configuration
now
they
may
be.
There's
gonna
be
in
inventory,
low
quantity
notification,
so
the
the
bell
web
api
endpoint
was
updated.
A
Now
it
looks
like
low
quantity
notification
delete
and
following
the
restful
architecture,
we
don't
expose
anymore
delete
method,
but
they
can
into
account
that
we
work
in
the
scope
of
this
method.
In
the
scope
of
this
method
called
we
work
with
many
entities,
we
use
the
post
HTTP
method
and
that
led
to
change
the
actually
unified
resource
identifier,
because
before
that
it
was
a
long-haul,
little
notification,
but
now
it
became
a
low-quality
notification.
A
A
This
is
not
all
because
we
had
another
changes
of
API,
so
we
during
during
the
end
of
the
previous
week
and
the
beginning
of
this
week,
and
actually
during
the
weekend,
we
spent
quite
a
lot
of
time
for
adjusting
all
our
API
and
the
next
present
are
going
to
be
with
Charlie
boy
go
from
our
tweaks.
We
will
show
you
another
update
and
not
update,
but
adjustments
of
how
and
why
women
students
the
show,
then
the
show
so
stop.
Sharing
my
screen
and
vitaliy
through
through
tor
share
here,
update
hi.
F
Great
so
I
was
working
on.
I
worked
on
introduced,
PHP,
70.1
syntax
for
IP
arts,
where
it
was
missed.
What
it
means.
I
was
strict
on
values
and
add
five
hits
two
input
parameters.
It
was
quite
important
to
do
it
before
the
release
because,
as
you
mention
it,
if
we
do,
if
you
would
do
it
right,
it's
you
break
backward
compatibility
policy
and
it
will
be
not
so
introducing
the
HP
sample
in
one
simple.
Stick.
Typed
will
be
a
lot
of
benefits
as.
F
F
F
F
F
F
F
F
A
Out
good,
but
I
won't
visit
for
better
customization
abilities.
We
have
to
provide
the
interface
week,
which
accepts
a
whole
sales
channel,
and
actually
this
is
what
led
it.
So
he
could
use
the
get
stopped
by
the
sales
channel
and
please
it's
not
just
codecs,
which
excels,
not
just
couldn't
I,
but
actually
the
real
sales
channel
interface,
because
the
sales
channel
interface
could
be
extended
with
the
extension
attributes.
As
you
know,
all
the
data
interfaces
in
magenta
could
be
extended
with
the
help
of
the
gate
extension
attribute
method,
which
returns
that
the
code
generated
entities.
A
A
Documents
and
for
example,
and
actually
heaven
are
two
interfaces
simultaneously
in
the
code
base,
so
the
stockers
over
I
want
with
the
get
stop
biases
sales
channel
interface.
We
introduce
some
unclarity
for
the
extension
developers
because
they
don't
have
a
clue.
What
exactly
interface
should
be
should
be
plugin,
iced
and
and
the
currently
we
consider
the
stock
resolver
interface
is
the
kind
of
the
sugar
service
on
top
of
the
get
stock
by
the
sales
channel
interface
and
the
real
interface
of
the
plugin
ization
and
for
modification
is
a
get
stop
by
the
sales
channel
interface.
A
That's.
Why
is
implementation
of
our
stock
stock
resolver
interface?
What
we
do
we
inject
the
newly
created
interface
they're,
real
SPI
interface,
so
the
get
stock
by
the
sales
channel
interface
and
the
who
implementation
of
our
sugar
service
is
actually
nothing
more
than
just
a
broker
on
top
of
the
real
service.
So
you
can
see
that
the
this
implementation
is
just
make
a
preparation
of
the
input
data
and,
after
that
it
makes
a
quote
to
the
get
stop
by
the
sales
channel
interface.
A
So
the
extension
developer,
need.if
extension
developer-
wants
to
make
a
plugin
ization,
for
example,
of
the
stock
resolve
and
mechanism
you
just
need
to
plug
in
eyes
get
stopped
by
the
sales
channel
interface,
because
this
is
this
is
more
generalized
interface.
It's
not
just
a
sugar
service
which
can
be
easily
applicable
for
the
rest,
api,
oh
for
for
business
logic,
but
it's
more
generalized
interface
and
this
that
will
work
for
different
sales
channel,
for
example,
guys
from
Amnesty
introducing
own
sales
channel
for
the
customer
group
plus
website.
A
Some
other
agency
could
introduce
even
more
sophisticated
sales
channel.
For
example,
you
see
one
of
the
pop-up
notification
from
my
slack
it
was
the
Amazon
project
and
in
the
Amazon
integration
we
we
create
the
catalog
and
the
catalog
is
sync
up
with
with
Amazon,
so
the
catalog
could
be
created
as
a
sales
channel.
So
for
this
more
generic
API,
this
interface
supposed
to
be
used,
and
actually
this
is
the
only
interface
which
should
be
recognized.
A
So
this
is
under
one
more
addition
regarding
the
first
issue
demonstrated
by
vitaliy,
so
you
probably
mentioned
that
all
of
our
api's
are
using
the
7hb
7.1
Cintas,
so
we
use
also
new
label
nullable
types.
We
also
use
a
vulgar
term
types,
so
these
are
tricky.
So
these
are
the
most
modern
interfaces
and
the
most
modern
style
of
writing
interfaces.
You
can
see
in
the
magenta
code
base
so
far.
A
Zetz,
probably
all
this
probably
all
regarding
the
demonstration
from
vitaly
not
sure
whether
we
have
any
any
other
presentation
left,
looks
like
we.
We
are
good
now,
and
that
was
the
last
presentation
and
now
actually
is
the
latest
update
that
we
are
in
the
process
of
packaging
and
bonding
the
latest
version
of
better,
which
will
include
all
the
bug
fixes.
We
are
doing
it
right
now.
That's
why?
A
Probably
you
see
so
many
pop-ups
from
my
slack
when
I
was
sharing
my
screen,
and
this
is
actually
all
from
our
side
for
for
today,
product
owner
of
MSI,
mark
greens
and,
unfortunately,
is
not
able
to
present
on
today's
demo
meeting.
But,
as
usual,
we
will
upload
the
recording
of
presentation
to
YouTube
and
the
recording
will
be
shared
in
the
satisfied
channels
and
Mark
will
have
an
ability
to
watch
it
later,
other
any
open
questions
or
ideas
or
anything
you
would
like
to
raise
for
today.