►
From YouTube: Elsa Workflows Community Meeting 7 ( 2022-05-03 )
Description
# May 3, 2022
## Topics
- Election results
- Elsa 2.7 was released :)
- Quick Elsa 3 update
- Server affinity
## Designer
**V3**
- Maybe smaller activities in activity picker toolbox
- Add search bar to activity picker
- Add new types of editors: Sequence, Flowchart (a la WF)
- Make it easy to integrate with e.g. Angular, React, Vue, Blazor
**V2**
- Make it easy to integrate with e.g. Angular, React, Vue, Blazor
# Elsa 2.8
- Need NPM preview packages on MyGet
- SQL intellisense
## Todo
- Steering committee gets access
- Create Elsa 2 project board
A
Yeah,
so
let's
take
a
look
at
the
topics
for
today.
Of
course,
election
has
come
to
an
end,
so
we
will
take
a
look
at
the
results.
I
already
took
a
sneak
peek,
but
we'll
take
a
take,
a
look
at
it
together.
I
didn't
prepare
any
demos.
I
don't
know
if,
if
you
guys
have
something
to
talk
about
or
a
demo
to
the
show
or
something
else.
B
A
Yeah,
I
do
thank
you
for
reminding
me
yeah.
So,
let's
talk
about
the
election
results,
the
server
affinity
and,
in
a
just
a
short
update
on
the
lz3.
I
did
a
little
bit
of
refactorings
to
make
the
apis
a
little
bit.
Nicer
did
some
small
work
on
the
designer
side
and
good
news,
there's
also
a
front-end
developer,
who
is
picking
up
some
of
the
front-end
tasks
to
work
on
the
designer?
So
that's
that
should
be
helpful.
All
right.
Let's
take
a
look
at
the
results,
so
here
it
is.
A
We
have
amanda
with
76
votes,
christina
60
votes,
france,
49
myself,
44
and
jeremy
43.
So
that's
one,
two,
three
four
five.
So
these
are
first
members
of
the
first
steering
committee
of
of
elsa.
So
congratulations,
everyone
so
moving
on.
Let
me
show
some
brief
updates
on
elsa
three.
Now
we
can
talk
about
the
server
affinity.
A
lot
of
the
updates
for
elsa
3
are
a
bit
of
refactoring
and
I
think
mostly
to
make
the
configuration
api
a
little
bit
more
extensible
modular
so
that
it
would
look
something
like
something
like
this.
A
This
will
probably
go
away.
This
will
be
encapsulated
in
within,
add
elsa
and
then
the
elsa
add
elsa
method
except
say
a
lambda.
That
gives
you
a
elsa
options
configurator,
and
this
is
an
object
that
can
that
holds
a
collection
of
configurator
objects,
and
that
means
any
packets
in
the
system
could
be
custom,
active
custom
packages.
Existing
packages
provided
by
this
repository
can
extend
this.
This
collection
with
custom
configurators,
and
this
allows
a
couple
of
useful
features.
A
For
example,
it
allows
you
to
replace
the
default
persistence
provider
which,
by
default,
will
be
a
null
implementation
of
the
provider,
which
you
can
then
replace
with
an
in-memory
one
if
you
want,
or
in
this
example,
an
entity
framework
provider
which
itself
can
then
be
configured
with
whatever
is
specific
to
that
configurator.
In
this
case,
the
entity
framework
provider
can
be
configured
with
the
sqlite
provider
or
a
sql
server
provider
or
postpress,
etc.
So
this
way
many
default
options
can
be
pre-configured
but
easily
replaced
or
overridden
by
the
user
as
they
want.
A
So
the
end
goal,
of
course,
is
to
be
able
to
just
say
when
you
start
a
new
project
to
say
just
add
elsa
and
that
should
allow
you
to
just
use
elsa
in
in
a
basic
fashion.
So
it
will
add
some
common
activities,
some
necessary
services,
a
runtime
which,
before
this
update,
was
proto
actor
and
then
proto
actor
will
be
using
the
in-memory
cluster.
But
now
it's
even
simpler.
It
doesn't
even
rely
on
protoactor.
A
It
uses
a
default
implementation
of
a
workflow
invoker
that
can
just
execute
workflows
without
needing
any
persistence
or
a
protoactor,
runtime
or
anything
else.
But
you
can,
with
the
system,
easily
configure
other
implementations
for
certain
services,
such
as
the
workflow
invoker.
So
that's
the
end
goal.
It's
not.
A
It's
getting
there,
so
that's
the
api
part.
The
designer
is
now
more
functional,
so
it
means
it.
It
allows
you
to
create
an
actual
flowchart
workflow
that
actually
executes.
So
that
was
something
that
didn't
actually
work
yet,
but
that's
that's
now
being
implemented
fully
and
and
what
I
mean
by
that
is
that
you
could,
for
example,
implement
an
hp,
endpoint
workflow,
connected
to
an
if
activity
and
then
before
the
change,
the
work,
the
flowchart
activity
didn't
completely
work,
so
it
wouldn't.
A
It
would
actually
invoke
the
if
and
over
item
activity,
but
then
the
next
one
wouldn't
be
invoked,
and
that's
because
this
rightline
activity
is
invoked
or
scheduled
by
the
if
activity,
because
this
one
actually
becomes
a
property
value
of
the
then
property
of
the
if
activity.
But
then,
once
this
one
executed
and
was
finished,
the
flowchart
activity-
that's
represented
by
this
canvas,
wasn't
being
signaled
with
the
completion
of
this
activity.
A
So
it
would
not
schedule
this
one,
because
this
one,
this
right
line
activity
is
not
a
property
of
then,
for
example,
it's
just
a
free
floating
activity
with
a
connection,
so
the
flow
chart
did
credits
their
connection
between
this
right
line
and
this
one,
but
it
wouldn't
then
actually
schedule
the
the
next
activity
connected
to
the
fitness,
one
so
technical
details,
but
that
now
works.
I
did
a
small
change
on
the
ui.
So
before
this
change,
everything
was
a
solid
color.
A
Now
it's
a
little
bit,
the
activities
are
a
little
bit
larger
and
the
body
is
white.
Does
decrease
the
contrast
between
the
the
background,
canvas
and
the
activities
themselves
so
might
need
some
some
more
work,
maybe
using
this
a
subtle
drop
shadow
or
something
else,
maybe
there's
a
designer
that
looks
at
this
and
has
some
good
idea
to
make
it
more
attractive,
yeah.
So
that's
that's
a
brief
brief
update
on
what
I've
been
up
to
last
week.
Let's
take
a
quick
look
at
the
board,
so
this
is
the
lc3
board.
A
Yeah
stuff
has
been
done
here
and
this
this
guy
is
working
on
on
an
issue
where
the
workflow
property
panel
doesn't
update.
So
that's
that's
the
issue
when
you
select
or
click
on
the
canvas
on
the
right
hand,
side.
You
now
see
the
workflow
property
editor,
but
there's
a
bug
where
the
settings
don't
get
updated.
So
if
I
say
sample
workflow
here
and
I
change
the
active
panel
to
the
to
some
activity,
property
editor
and
then
show
this
panel
again,
this
didn't
get
saved,
or
maybe
maybe
I
pulled
a
fix.
A
I
don't
know
because
this
used
to
be
empty.
Now
it's
only
working,
but
it's
not
very
reliable,
so
that's
being
worked
on.
Maybe
it
got
fixed
accidentally.
I
don't
know
but
didn't
work
before
this
demo.
Now
it
works
but,
as
I
said
it
needs
to,
we
need
to
make
sure
it
works
reliably.
So
it's
it's
small
issues
like
that.
A
It's
also
the
drag
and
drop
issue
when,
for
example,
when
you
zoom
out-
and
you
start
adding
activities
as
you
notice,
it's
it's
not
dropping
onto
the
released
location,
it
jumps
to
some
other
location.
So
that's
another
issue.
So
so
we
have
a
bunch
of
these
once
they
are
especially
this
one,
the
designer
one.
Once
they
are
implemented
like
automatic
layout,
a
toolbar,
then
it's
becoming
something
close
to
actually
production
ready,
so
making
progress
there.
C
I
have
one
comment
here
on
the
activities
list:
on
the
left
hand
side,
I
can
see
that
you
are
using
the
full
icon.
I
think.
If
we
have
a
lot
of
activities,
then
the
list
will
be
become
big
sure
so
can.
Instead
we
have
like
a
shorter
lines
for
each
one
of
the
activities
so
that
we
can
quickly
navigate
between
them.
You.
A
B
A
Absolutely
so
not
for
this
version,
not
the
initial
version,
but
this
this
flowchart
activity
I
will
display
that's
similar
to
elsa,
2
and
also
one,
but
I
as
a
additional
implementation.
I
want
to
have
a
different
kind
of
flow
chart
like
the
flowchart.
We
have
in
workflow
foundation
and
that's
there.
You
have
a
flowchart
where
every
node
in
the
in
the
diagram
is
a
container,
and
you
can
drill
into
that.
A
So
so
you
can
collapse
that
container
or
you
can
actually
look
at
its
contents,
which
could
be
any
activity
which
means
it
could
also
be
a
state
machine,
another
flowchart
or
a
sequence
whatever,
and
the
same
goes
for
the.
If
activity,
where
you
have
the
two
outcomes,
then
and
else
and
then
you
can
collapse
that
so
for
that
designer,
where
you
can
compose
your
activities
hierarchically,
that
would
be
great
to
have
so
that
you
can
keep
a
a
nice
overview
of
the
the
overall
flow.
B
A
A
Of
the
yeah
good
point,
because
if
you
were
adding
the
effect
to
a
sequence,
let's
say
then
the
if
it
would
execute
and
then
then
or
else
would
execute
and
after
that,
then
the
remainder
of
the
sequence
activity
would
execute.
So
that's
not
currently
modeled
in
this
editor,
but
that's
what
you
will
want
to
be
able
to
do
is
indeed
have
a
like
a
a
done
outcome
that
we
have
in
lsat,
2.
and
also
too.
C
A
Yeah
exactly
so,
that's
the
same
solution
to
having
a
different
flowchart.
Actually,
that's
that
resembles
the
windows,
workflow
foundation,
flowchart
activity.
Then
you
have
exactly
that.
Yes,
just
to
see
if
they
have
a
a
nice
example
here
yeah.
So
here
they
have
a
float
chart
activity,
and
here
they
have
an
assign
a
decision.
This
is
specific,
I
believe,
to
this
activity.
That's
false!
It's
not
using
true.
It
has
two
outcomes.
B
To
an
issue
on
github,
I
will
mute
it's
on
description.
It's
a
flow
sequence
context
execution
exactly
the
the
id
and
everything
is
explained
in
the
description
is
to
be
able
to
add
some
context,
information
to
explain
to
the
to
the
engine
where
we
want
to
execute
the
the
activity.
For
example,
we
have
a
cluster
with
two
virtual
machines
and
we
have
a
workflow
with
activity
that
are
spread
on
the
two
on
the
two
virtual
machine.
B
The
vm1
is
exposed,
for
example,
on
the
internet,
so
we
need
the
http
activity
to
be
a
bind
on
this
server
to
expose
an
endpoint
and
to
respond
with
a
with
the
answer,
and
the
vm2
has
an
access
to
a
secure
database.
So
we
need
to
put
the
sql
activity
on
this
server
and
it
should
be.
It
should
execute
on
this
server.
The
id
is
to
be
able
to
add
some
context
on
multiple
on
a
group
of
activity,
for
example,
say
hey.
I
want
you
to
execute
on
this
environment
and
you
on
this
environment.
A
It
makes
sense,
there's
another
use
case
that
I
came
across
with
another
customer
that
is
using
lsat-2
and
they
have
not
a
cloud
environment
but
a
on-premise
environment
with
a
cluster
of
two
nodes
and
in
their
workflow
what
they
want.
They
want
to
be
able
to
process
some
files
that
are
then
stored
locally
on
that
machine,
and
then
the
workflow
will
resume
should
resume
on
the
same
machine
because
it
needs
access
to
those
files
that
are
stored
only
on
a
given
node.
So
they
also
need
some
form.
A
I
think
this
would
be
very
useful
and
we
have
to
think
of
a
good
way
to
to
enable
this.
I
imagine
it
takes
a
little
depends
on
the
the
run
time
to
be
able
to
interpret
this.
This
context,
information-
and
that's
that's
one
of
the
other
nice
things
about
the
v3
implementation.
You
can
have
different
kinds
of
of
engines
that
can
interpret
different
different
contexts
from
from
activities
to
to
allow
you
to
na
to
implement
this
setup.
Yeah.
B
And
what
I
don't
see
for
the
moment
is
how
we
can
make
this
configuration
as
easy
as
possible
for
the
end
user
and
graphically
creating
some
some
kind
of
topology
in
an
architecture
to
to
be
able
to
to
say
where
we
want
to
execute
a
group
of
activity,
and
I
thought
about
the
the
sequence
that
you
mentioned:
the
z3,
which
is
a
group
of
activities.
So
if
we
can,
for
example,
say
a
sequence
can
execute
specifically
with
some
execution
context,
all
the
activity
inside
will
inherit
of
this
execution
engine.
Do
you
think.
A
B
A
Be
really
great
and
of
course,
call
me
if
you,
if
you
want
to
walk
me
through
the
the
code
base,
where
I
discussed
this
this
architecture
sure
great
yeah
I
like
it.
Oh,
I
completely
forgot,
but
elsa
2.7
was
released
yesterday
with
some
new
set
of
activities.
The
execute
sql
query
execute
sql
command.
This.
A
Retrieve
data
from
an
arbitrary
sql
server,
this
one
to
execute
a
command
hp,
endpoint
route
parameters.
Support
was
has
released.
This
was
demoed
a
couple
of
meetings
ago,
but
that's
now
a
part
of
2.7
same
goes
for
the
compensation
story
which
introduced
a
couple
of
new
activities
to
implement
workflow
compensation.
That's
art
of
2.7
swather
integration
and
cool
crown,
ui
created
by
muhammad,
also
part
of
2.7.
And
of
course
there
were
some
improvements.
A
You
would
be
able
to
do
it,
but
you
would
have
to
use
the
low-level
apis
and
now
you
can
do
it
more
easily,
because
there's
been
some
new
services
that
were
added
yeah
and
some
some
more
low-level
stuff
here
and
of
course,
some
important
bug
fixes
like
the
join
that
was
problematic
in
certain
scenarios:
yeah
some
some
small
stuff
and
of
course,
a
lot
of
lot
more
commits
were
made
full
commit.
History
can
be
found
here,
but
it's
it's
a
good
release.
I
feel
very
good
about
this
2.7.
A
It
makes
things
a
little
bit
more
stable,
squashes
some
blocks
and
has
some
cool
new
additions
for
2.8.
The
milestone
is
still
empty,
so
we
can
fill
it
up,
but
I
would
I'm
also
thinking
of
setting
up
a
board
similar
to
ls3
but
called
elsa
2
to
try
and
in
an
order
of
priority
of
items,
as
reported
by
users
and
hopefully
we'll
be
able
to
work
on
that.
A
B
A
That
makes
sense
yeah
right
now,
whenever
a
change
is
made
to
the
designer
code
in
stencil
and
it's
pushed
to
github,
a
github
workflow
will
be
executed
or
a
github
action,
and
that
will
push
the
build
output
directly
to
npm
at
this
moment.
So
actually,
npm
is
currently
always
showing
the
latest
packets,
which
is
problematic
because
it's
not
always
compatible
with
the
older
release
on
nougat
with
you
know,
which
contains
the
potentially
an
outdated
back-end
compared
to
whatever
npm
connects
to.
So
that's
that's
a
good
idea
to
have.
C
I'm
also
looking
to
have
some
option
for
sql
syntax,
so
that
is
something
I
would
like
to
be
able
to
see
in
2.8
to
have
sql
as
a
syntax
similar
to
what
we
have
now
as
a
javascript
and
liquid.
For
that
some
server
side
support
may
be
required.
That
is
something
that
I
am
looking
forward
to
maybe
able
to
create,
but
I
will
need
some
help.
Also.
C
A
B
A
But
many
many
bugs
two
pages
up
and
down
very
much
yeah
yeah.
So
I
would
also
like
to
include
some
of
the
more
important
ones
with
2.8.
I
think
that's
prudent
to
do
yeah.
I
will
take
care
of
creating
this
board.
I
will
add
these
items,
add
some
bugs
and,
of
course,
feel
free
to
suggest,
and
oh,
I
totally
forgot
to
mention
being
an
steering
committee
member
grants
you
access
rights
to
the
repo,
including
the
the
board,
so
you
can
also
create
and
prioritize
issues
assign
them
to
projects
etc.
B
Another
idea
about
the
dashboard
and
the
packaging,
we
have
see
a
different
issue
on
integrating
angular,
so
maybe
it
could
be
a
good
idea
also
to
update
a
little
bit
the
packaging
to
allow
the
framework
integration
more
easily
with
the
angular.
I
know
we
have
something
to
do
on
the
on
the
packaging.
Intensive
gs.
Aside
for
for
my
on
my
site,
I
have
no
issue
to
integrate
the
the
package
in
a
in
different
angular
application.
A
Man
that
would
be
really
sweet.
Yeah
many
many
have
been
asking
for
support,
or
you
know
how
do
you
integrate
it
with
angular
or
other
frameworks?
So
if
you
can
write
something
up
for
that
and
if
there's
something
we
need
to
do
to
make
it
easier
on
the
on
the
designer
packaging,
then
we
should
add
that
so
do
you
think
that
I
would
also
then
make
it
simple
for
people
who
want
to
integrate
it
with,
let's
say
react.
I
I.