►
From YouTube: Compliance Weekly 2023-04-25
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
All
right
welcome
to
the
compliance
weekly
for
the
25th
of
April
since
I've
been
away
the
last
couple
of
weeks,
whose
day
for
do
you
want
to
take
us
through
the
what's
happening.
Sure.
B
C
The
this
was
basically
already
present
in
our
code
base.
B
Okay,
thanks
I
guess:
jihu
contributed
to
this
right,
probably
yeah.
C
C
C
B
B
A
There
was
one
that
I
wanted
to
ask
about:
I
did
I
knew
who's,
faithful,
that's
in
solution,
validation,.
D
A
B
B
A
B
I
guess
this
is
just
something
that
we
need
to
do
in
this
Milestone,
not
on
the
highest
priority
right.
A
Yes,
great
yeah,
it's
unlike
something
it's
not
often
here
the
other
one
was
just
something
that
we
want
to
get
a
bit
of
feedback
to
the
customer.
Obviously,
if
possible.
B
E
I
think
the
view
project
is
no
CD,
so
I
mean
this
one.
This
one
is
not
for
good
for
design,
yet
I'm
still
working
on
this,
so
I
think
there
are
some
discussion
about
like
which
direction
we
are
taking
about
to
manage
it,
and
there
are
some
more
things
need
to
be
done.
Based
on
the
discussion.
I
think
I
need
to
still
go
through
the
last
comment
and
talk
about
it
anyway,
like
no
matter
which
direction
we
go.
We
still
needs
a
research
like
solution,
validation,
research
on
this,
so
This
I.
E
A
It's
just
good
to
know
that
so
that
we're
clear
on
whether
we're
gonna
stick
in
any
engineering
effort
in
the
next
milestone.
E
B
I
can
just
give
the
gist,
so
we
have
the
compliance
Frameworks
report.
We
we
want
the
feature
where
we
filter
the
projects
by
some
like
we
filter
something
the
projects
by
let's.
B
So,
for
example,
if
you
just
filter
by
compliance
framework,
is
it
not
just,
then
we
need
to
apply
a
bulb
flame
framework
here,
for
example,
if
you
don't
have
a
framework,
we
get
a
lot
of
projects.
So,
on
the
first
page
we
just
see
like
20
physics
or,
like
maybe
a
hundred
items,
but
not
more
than
that,
but
in
reality
it
could
be
more
than
100
this
list.
B
So
what
we
need
is
we
should
have
an
option
to
select
everything
like,
including
all
the
items
that
are
on
the
next
page
as
well,
which
are
not
shown
on
the
front
end
and
choose
a
bulk
action
and
then
apply
the
work
action
there.
So
the
issue
there
here
is
that
front
end
doesn't
know
a
lot
of
things
because
we're
still
not
displaying
the
project
on
that,
like
the
information
on
that
particular
page,
so
we
need
a
a
way
for
the
front
end
to
actually
issue,
maybe
a
graphql
query
or
anything.
B
If
anyone
has
any
other
ideas
where
we
have
a
graphql
mutation,
which
sends
a
request
to
the
backend
with
the
applied
filter,
like
all
the
projects
that
doesn't
have
a
framework
and
do
some
action
like
action
as
in
like
apply
this
particular
HIPAA
framework
to
all
of
them.
So
right
now,
we
just
have
limitation
to
select
only
the
the
projects
that
are
there
on
the
current
page.
But
we
want
to
expand
that
expand
the
ability
to
apply
the
compliance
framework
to
all
the
projects.
Much
in
the
filters
so.
B
So
we
need
a,
we
need,
a
graphql
mutation
for
that
and
the
other
thing
for
that
is
like,
even
if
front-end
issues
a
mutation
where
they
give
us
the
matching
filter
and
the
bulk
action.
It's
easy
at
the
back
end
to
apply
that
action,
but
then
we
also
need
a
feature
to
actually
undo
that
functionality.
So
there
also
needs
to
be
an
undo
button
which
will
do
the
exact
opposite
of
the
thing
that
happened
initially.
F
Like
this
actually
I'm
like
working
on
this
issue,
in
terms
of
providing
my
suggestions,
we
probably
will
need
to
refactor
our
current
query
beat,
or
at
least
to
think
about
it,
because
it
would
be
great
to
have
a
single
filter
type
describing
actually
filters
type.
F
So
we
could
reuse
it
both
for
querying
the
projects
and
using
this
mutation,
which
is
applies
filters,
because
otherwise
it
will
be
a
big
pain
to
keep
them
in
sync,
and
it
will
be
a
potential
source
of
errors,
so
which
would
be
what
I
was
like
researching.
Is
that
how
we
could
without
breaking
stuff?
Because
it
is
graphql?
It
is
not
versioned
to
introduce
filters
which
will
have
a
separate
type
on
our
schema
and
to
reuse
it.
F
On
this
newly
proposed
mutation
and
our
projects
get
compliance
framework,
query
which
is
already
exists,
because
right
now
on
the
get
project,
it
is
just
a
number
of
fields,
and
otherwise
we
just
will
need
to
like
copy
and
paste
this
Fields
while
forget
it
for
mutations,
which
is
like
quite
problematic.
F
Will
be
the
same
problem
like
keeping
keeping
keeping
keeping
things
consistent
like
we
will
need
to
able
to
query
something
which
has
filters
and
to
apply
mutation
to
something
based
on
the
same
set
of
filters,
so
making
sure
that
we
are
handling
filters
simult
identically
on
in
both
cases.
It's
a
good
bet.
B
What
I'm
just
proposing
is
like
if
we,
if
you
have
a
rest,
API
like
a
post
request
where
we
send
the
payload
as
like
a
filter
which
is
a
hash.
B
You
provide
the
filter
and
then
the
action
is
also
a
hash
where
you
say
like
apply
or
remove
this
compliance
framework
for
all
for
the
things
that
matches
the
filter,
then,
at
the
back
end,
we
we
can
again
have
like
we'll
run
the
same
query
with
the
filter
that
was
provided
by
the
front
end
in
the
request
and
then
apply
the
action
that
was
provided
by
the
front
end
and
for
the
for
the
undue
action.
B
I'm,
not
sure.
If
we
can,
we
just
have
two
bulk
actions
right.
Either
we
can
apply
the
framework
or
we
can
like
remove
a
particular
framework
right.
So
can
we
just
like
in
the
undo
button?
Can
we
just
have
like
remember
the
previous
action
that
we
performed
and
for
that
particular
filter?
And
as
this,
if
it's
the
same
filter
we
just
like?
If
it's
the
undo
action,
we
just
provide
the
same
filter
and
the
opposite
action
that
was
applied
like
intercourse.
F
No
well
actually,
this
is
not
possible
because,
like
you,
could
have
an
action
like
clear,
remove
compliance
framework
on
the
bulk
items
where,
like
half
of
the
items
have
like
framework,
one
applied
and
half
half
frames
to
apply
it.
So
it
is
not
possible.
So,
as
we
decided
in
discussion,
we
will
have
as
a
result
of
no
matter
graphql
mutation,
rest
API.
F
We
will
return
as
some
very
lightweight
response
stating
hey
this
project
previously
had
this
framework
and
we
will
have
it
cache
it
on
front
end
for
a
short
living
time
of
undo
operation,
and
if
someone
hits
undo,
we
will
issue
existing
mutations
or
for
now
or
probably
we
will
still
introduce
a
new
bulk
mutation
to
set
like
okay.
Let's
set
this
project
to
this
framework,
specifying
payrolls
project
compliance
framework
pairs.
F
So
this
is
how
it
will
be
done
and
I
see,
like
not
big
difference
between
using
rest
here
and
graphql,
and
that's
why
I
prefer
to
stick
to
graphql
test
because
we
already
are
using
graphql.
The
only
reason
yeah.
B
That's
fine
yeah,
I
I
can
understand
like
at
least
integrating
that
on
the
front
end
would
be
much
easier
since
you
already
have
the
graphical
in
the
client
side.
That's
fine,
then
then
I
think
it's
it's
still
on
this,
like
we're.
Still
on
the
same
page,
where
we
need
to
decide
the
new,
the
mutation
for
applying
the
filters
and
then
the
response
of
that
mutation
and
which
front
end
would
be
using.
F
C
Thanks
so
I
have
a
question
here
for
the
first
invitation
when
we
are
trying
to
apply
the
filters.
Why
can't
we
just
pass
the
project
IDs,
which
we
display
on
the
front
end
and.
F
This
is
how
it
works
now,
but
we
could
have
projects
which
match
filters
buttons
as
next
Pages,
which
are
not
yet
loaded
on
front
end.
So
front-end
simply
doesn't
no
knows
nothing
about
them.
That's.
B
F
B
Harsham,
what
we're
actually
trying
to
implement
is
like,
if
I,
if
I've
added
this
particular
printer
I,
can
even
the
select
all
buttons
only
allows
me
to
select
only
20
projects,
because
these
are
the
things
that
are
listed
there.
But
what
we
want
from
this
particular
feature
is
to
be
able
to
select
all
the
projects
like
it
could
be
100
projects
that
are
matching
this
particular
filter,
so
I
want
to
apply
the
bulk
action
to
all
the
100
projects
and
how
front-end
works
is
like.
B
G
While
marking
a
lot
of
emails,
unread
emails
to
be
read,
so
they
they
do,
they
are
doing
the
solution
that
we
are
providing
right.
Now
that
you
need
to
do
it
in
batches
of
50
50.,
you
can't
do
it
for
all
so
I
think.
Rather
than
disturbing
this,
we
should
create
some
another
option
for
bulk
update
rather
than
because
this
ux
uxy's
there
is
more
entity
that
it
will
Mark
these
20,
not
all.
B
I
I
correlated
this
with
the
Gmail
filters
action
where,
if
you
create
a
new
filter,
it
will
say
like
this.
Please
mute
yourself.
E
Yeah,
like
what
I
imagine
like
I,
think
if
you
go
to
refresh
issue
I
just
quickly
post
a
comment
at
the
bottom.
D
E
Like
there
is
a
screenshot
I've
put
it
there,
I
think
that's
the
pattern
you
mentioned
yeah
like
currently.
If
you
have
a
checkbox
for
user,
they
understand
it
and
to
select
everything
on
this
page.
If
we
select
more,
we
need
to
have
additional
pattern
there
by
kind
of
indicate,
select
everything
and
then
we
select
it.
Otherwise,
it's
unclear
and
I've
checked,
like
other
lists
in
gilab
when
they
select
the
checkbox
on
the
top.
B
But
I
like
how
tomorrow's
idea
of
like,
if
you're,
going
ahead
with
this
feature,
then
I
like
her
Summer's
idea
of
probably
caching
the
result
at
the
back
end
and
providing
like
having
a
unique
graphql.
What
do
what
do
we
call
it?
The
unique
code
that
we
sent
for
the
for
each
graphql
request
and
preserve
that
particular
like
cash,
that
request
ID
at
the
front
end
then
for
the
undo.
F
I
need
to
check
I
like
there
are
too
many
things
to
consider
and
I
really
appreciate
if
you
lock
this
in
asynchronous
way
into
the
issue.
So
we
have
like
this
discussion
captured
this
might
work,
but
you
need
to
think
about
it,
just
to
say
like
if
this
will
be
viable.
B
B
We
have
a
couple
of
Mrs
with
maintenance,
I
guess
the
audit
event
types
have
has
maintenance
levels
like
all
the
emers
that
we
have
in
the
probably
that's
the
reason
for
the
spike
in
Mrs
labeled,
with
type
maintenance
and.
B
A
Sorry,
if
you
go
to
the
filters
at
the
top
and
select
yeah
compliance
from
there.
B
We
have
some
issue
with
this
one:
okay,
just
because
we
we're
not
using
bamboo
HR
anymore,
probably
not
sure,
has
not
taken
a
look
at
this
one.
B
We
also
have
this
one
where,
if
you
have
any
Mrs
that
are
open
for
more
than
60
days
or
if
they
are
Community
emerged,
we
have
is
like
zero
is
false
and
one
is
true,
so
we
have
a
community
Mr,
which
is
open,
probably
no
one
is
assigned.
We
should
just
take
a
look
into
this.
D
B
B
A
Type
information
cleanup:
okay,
yes
to
do
with
this
one.
A
H
Yeah
that
one's
on
me
and
I
just
haven't
gotten
around
to
it
anymore,
because
it's
power
priority
than
what
I
was
working
on.
A
Yeah,
just
the
Retro
issue
is
open
and
ready
for
any
feedback.
They
have
so
we're
gonna
have
the
seek
section
retro
coming
up,
so
please
fill
out
anything
that
you
have
in
there.
Any
comments
feedback
be
great
to
get
it.
Thank
you.