Is there any roadmap for ABPs Elsa integration? Especially per Tenant Workflows are needed for our product.
Also an updated documentation for using your module within a layered WebApp would be great.
2 Answer(s)
-
0
- Solution
Current status
- ABP provides a Pro Elsa integration module (ABP Team license or higher). The module integrates authentication/permissions and basic wiring, but documentation explicitly states it is not yet fully integrated because Elsa has its own DB and Identity/Tenant systems under active development. Several ABP Elsa sub-modules are placeholders to be implemented as Elsa evolves.
- Per-tenant workflows: There is no official statement in ABP docs that per-tenant workflow isolation/management is delivered as a turnkey ABP feature today. You can still run Elsa in a multi-tenant ABP app by isolating workflows via Elsa’s own persistence and scoping, but a fully unified ABP multi-tenancy model for Elsa is not documented as complete.
Roadmap
- The ABP Platform Road Map is the only authoritative, public plan. It does not publish a specific milestone/date for “Elsa full integration” or “per-tenant workflows in ABP Elsa module.” Therefore, there is no public, dated roadmap item for those features at this time. Track the platform roadmap and release notes for updates.
What you can do today (ABP 10.0, Blazor Web App)
- Use ABP Elsa Module (Pro) to integrate with ABP auth and permissions, and host Elsa Studio separately. Follow the Elsa sample to see a working reference.
- For per-tenant needs:
- Keep your app multi-tenant with ABP (SaaS/MultiTenancy enabled).
- Configure Elsa persistence to store workflow definitions/instances per tenant (e.g., separate schemas/DBs or tenant-discriminators in Elsa’s EF persistence).
- Use ABP’s ICurrentTenant to pass current tenant context into activities/input/output or to resolve tenant-specific configuration (connection strings, endpoints).
- Expose Elsa endpoints through your gateway and secure them with ABP permissions; ensure tenant context is required to access/operate on workflows.
- For layered WebApp documentation: Use the Elsa Pro module page plus the Elsa sample (it shows solution layout, hosting Elsa server + Studio). For general layered web app setup, follow the “Get Started with ABP: Layered Web Application” guide, then add Elsa as shown in the sample.
- Sources
- ABP Elsa Module (Pro) overview and current integration status:
- https://abp.io/docs/10.0//modules/elsa-pro
- ABP Platform Road Map:
- https://abp.io/docs/10.0//release-info/road-map
- Elsa Workflows sample for ABP (structure/topology reference):
- https://abp.io/docs/10.0//samples/elsa-workflows-demo
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
hi
Is there any roadmap for ABPs Elsa integration?
Elsa is still under continuous development, and ABP will continue to follow up on any new features.
Especially per Tenant Workflows are needed for our product.
Elsa doesn't support this case very well. But it will be supported later. see
Also an updated documentation for using your module within a layered WebApp would be great.
We have a demo https://abp.io/docs/10.0//samples/elsa-workflows-demo
ElsaDemoApp.Server is an ABP application with Identity and Elsa modules. It is used as the authentication server and Elsa workflow server. ElsaDemoApp.Studio.WASM is a Blazor WebAssembly application with Elsa Studio. It is used as the Elsa Studio client application. ElsaDemoApp.Ordering and ElsaDemoApp.Payment are two microservices that can be used to test the Elsa workflows in distributed systems.
Thanks.