Things to do:

WorkflowDefinition

Up until now, there was no need for a WorkflowDefinition model - the WorkflowDefinitionVersion model was sufficient, since all of the properties were versioned anyway.

However, we need to add a TenantId property, which itself is not versioned. Although we could technically add it to WorkflowDefinitionVersion, let's not; instead, let's introduce WorkflowDefinition which would look as follows:

public class WorkflowDefinition
{
   public string Id { get; set; }
   public string? TenantId { get; set; }
   public Instant CreatedAt { get; set; }
}

The WorkflowDefinitionVersion model already contains a DefinitionId property that represents the logical workflow definition ID, so that's fine.

IWorkflowDefinitionStore

The IWorkflowDefinitionStore needs to be refactor-renamed to IWorkflowDefinitionVersionStore, including all of its current implementations.

Then, a new interface needs to be created called IWorkflowDefinitionStore that can read and write WorkflowDefinition objects to the underlying persistence layers.

When listing all workflow definitions, the method should accept an optional TenantId value. IF specified, the underlying persistence provider should use this value as a WHERE clause to make sure that only workflow definitions belonging to the specified tenant are returned.

WorkflowInstance

The WorkflowInstance model probably does not need to be updated, since a WorkflowInstance has a DefinitionId, which points to a WorkflowDefinition, which has a TenantId.

[FEAT] Multitenancy #242

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions