Elsa Pro Module Roadmap #10610

4 Answer(s)

• 

  0

  AI-Bot created 5 months ago

  Support Team ABP Agent

  • ABP does not publish a public, detailed roadmap per module (including Elsa Pro) in the documentation or in a verifiable official source that lists “planned features in the near future”, so I can’t give you a confirmed roadmap or ETA for “tenant users can login to WASM studio and manage their own workflows / workflows per tenant”.
  • The currently verifiable official Elsa Pro documentation page is an overview page and does not document tenant-scoped Elsa Studio login/workflow management. So, based on verified sources, there’s no official confirmation that “tenant login to WASM Studio + per-tenant workflow isolation” is already implemented in the ABP Elsa Pro module for your version (10.0.3), nor a documented configuration to enable it.
  • For roadmap/commitment/priority (and to ensure the ABP team sees your multi-tenancy requirements and Elsa 3.6.0 impact), the correct channel is ABP Commercial contact/support.

  Actionable next step (the only definitive one):

  • Please contact ABP/Volosoft through: https://abp.io/contact
    Include:
    • Your ABP version (10.0.3), UI (Blazor Web App), and that you’re using Elsa Pro
    • The exact missing capabilities: “tenant users can login to WASM Studio”, “workflows isolated per tenant”, and whether you need isolated tenancy or “shared user accounts” style behavior
    • Whether you’re targeting Elsa 3.6.0 specifically and what breaking changes you’ve hit

  (If you want, you can also point them to the current public claim on the module page about multi-tenancy and ask for clarification/updated docs, but I can’t provide a verified roadmap beyond directing you to the official channel.)

  Links used:

  • https://abp.io/docs/10.0//modules/elsa-pro
  • https://abp.io/docs/10.2//modules/elsa-pro
  • https://abp.io/contact

  ---

  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.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 5 months ago

  Support Team Fullstack Developer

  Hi,

  Elsa Studio is a UI project that can be used in Blazor Server and WASM projects. It can be viewed as a standalone project, and currently it is still challenging to fully integrate it into our own project.

  Elsa has its own user/role/tenant system, and it is different from ABP:

  • Elsa has its own Tenant entity, ITenantStore, ITenantsProvider, ITenantResolver, and /tenants CRUD endpoints.
  • Elsa entities use string? TenantId, but ABP uses Guid?.
  • Elsa reads the tenant from the http://schemas.microsoft.com/identity/claims/tenantid claim (CustomClaimTypes.TenantId), which is not the same claim name that ABP writes by default.

  So all Elsa permissions in AbpElsaPermissionDefinitionProvider are registered as MultiTenancySides.Host for now, and the elsa-pro.md doc also says the module is "not yet fully integrated".

  Tenant users logging into Elsa Studio to manage their own workflows is not supported yet. To make it work properly we need a mapping layer between ABP tenants and Elsa tenants, write the Elsa tenant claim to the token, open the permissions to the Tenant side, and optionally bridge ABP's tenant connection string to Elsa's Tenant.Configuration for per-tenant workflow databases.

  ---

  For now, the suggested way to use the module is:

  • Keep the workflow definitions on the Host side and let only host admins log in to Elsa Studio.
  • Pass TenantId into the workflow as an input/variable, and let the workflow branch on it when needed.
  • In your custom activities, use ICurrentTenant.Change(tenantId) to switch to the target tenant before calling any ABP service (repositories, managers, email, etc.).
  • Trigger workflows from ABP distributed events. ABP events already carry the TenantId, so the workflow naturally runs in the context of the right tenant. This is the same pattern used in the ElsaDemoApp sample.

  This way a single set of workflow definitions can serve all tenants, and you don't need to work around the multi-tenancy limitation on the Elsa side.

  ---

  We have already seen the 3.6.0 changes on the Elsa side: TenantsOptions.IsEnabled, "" as the default tenant id, null as tenant-agnostic, the TenantDeleted event, tenant id added to the stored trigger index, etc. These are good improvements, but the multi-tenancy model on the Elsa side is still moving. If we build the integration right now, we will likely have to redo parts of it after the next change on their side.

  We will keep the Host-only setup for now, and do a proper multi-tenant integration once Elsa's multi-tenancy is stable. We will update the module and the docs at that time.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rcalv002 created 5 months ago

  We too are waiting on abp delivered pro module for elsa, we'd love to offload our other workflow solutions to an integrated abp module.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 5 months ago

  Support Team Fullstack Developer

  Hi @rcalv002,

  Thanks for letting us know. We will continue working on the Elsa module, and any updates will be included in the release notes for upcoming versions.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel