Sipke Schoorstra
Sipke Schoorstra
The API currently has support for providing an expiration date (plus various modes). What would be nice however is to also have a way to provide change monitors (a la...
The API currently has a notion of a cache "region", which is a convenient way to group related cache entries so I can evict them using that region. But I...
This fixes the starter kit where the generated code would not build as described in #107 Fixes #107
Piotr Szmyd
This Tuesday June 22nd 2021, our dear friend Piotr Szmyd (@pszmyd) passed away. Piotr was a respected member of our community, a steering committee member, and a passionate contributor. Everyone...
Roadmap
This issue lists high-level functionality I'd like to add to Elsa 3 and beyond. It's not a final list and the order in which each milestone will be picked up...
### TLDR; Add a "multi-track" stack implementation so that the activity processor can process multiple branches in an alternating fashion. This enables scenarios where a forked workflow can have multiple...
We need to document how to configure the workflow server (ASP.NET Core) with authentication middleware and securing the Elsa API controllers and how to configure the dashboard with a plugin...
Currently, the proto actor runtime uses the in-memory cluster provider. We should add a feature that configures the Kubernetes cluster provider.
Similar to what's been done [here](https://github.com/elsa-workflows/elsa-core/issues/2572) for Elsa 2, we need a panel to manage workflow definition history on Elsa 3. Depends on #3029
Similar to what's been done [here](https://github.com/elsa-workflows/elsa-core/issues/2572) for Elsa 2, we need API endpoints to manage workflow definition version history. Blocks #3028