Multi-tenancy support is missing in Elsa 3

[cvijayak]

Please confirm whether Elsa 3 supports Multi-tenancy because the following observations show that multi-tenancy support is missing in Elsa 3.

In older versions (1.x, 2.x), Elsa had an interface called ITenantAccessor that would be used by store classes. During CRUD operations, store classes used the instance of ITenantAccessor to find the TenantID and insert, update, delete, or get appropriate workflows from the database.

In the current version (3.x), the ITenantAccessor interface is missing, and even the TenantID is absent in the database as a column.

Below is the WorkflowDefinitions table from Elsa 2.x:

Below is the WorkflowDefinitions table from Elsa 3.x:

The WorkflowDefinition table from Elsa 3.x does not have TenantID as a column. But WorkflowDefinition from Elsa 1.x, 2.x has TenantID as a column.

If support is not present in Elsa 3, please confirm whether there are plans in place to add it in upcoming releases

[kitsunoff]

Multi Tenancy it's planned in 3.1

[cvijayak]

Thanks for the update

[cvijayak]

@ZverGuy Please confirm the release date of 3.1 if it has already been decided

Also, please confirm whether anybody is currently working on the feature

[kitsunoff]

please confirm whether anybody is currently working on the feature

https://github.com/elsa-workflows/elsa-core/pull/4739

[cvijayak]

If this feature will take time to complete, perhaps the column called 'TenantId' can be added to all the tables atleast. This will help users to implement the feature on their side and share their workable code.