Support Programmatic Definition of Dynamically Provided Activities

[sfmskywalker]

Support Programmatic Definition of Dynamically Provided Activities

[glime-ai]

To address the proposed enhancement for incorporating dynamically provided activities into programmatic workflows in Elsa Workflows, it's important to note that Elsa already supports a mechanism for defining workflows programmatically and dynamically. However, the current documentation and examples primarily illustrate the use of statically defined .NET classes.

The proposed API enhancement suggests extending the workflow builder API to allow for the inclusion of dynamically provided activities within programmatic workflows. This would indeed increase the flexibility of Elsa Workflows, enabling developers to define workflows that can adapt to changes without the need for recompilation.

As of my knowledge cutoff date in early 2023, the Elsa Workflows documentation and GitHub discussions indicate that Elsa 3 supports dynamic workflows and activities. For instance, the IWorkflowProvider interface allows for the dynamic provision of workflows, which can be read from JSON and mapped into Elsa workflows programmatically.

To implement the proposed enhancement, the Elsa team would need to extend the existing workflow builder API to support the instantiation and configuration of dynamically provided activities within the programmatic workflow definitions. This could involve creating a new API method or extending existing ones to accept activity identifiers (e.g., "Acme.DownloadOrder") and to configure their inputs and outputs dynamically.

It's also worth noting that Elsa Workflows is an open-source project, and contributions from the community are welcomed. If this feature is not yet available, you could consider contributing to the project by implementing the proposed API changes and submitting a pull request for review by the Elsa team.

For the most up-to-date information on this feature and to check if it has been implemented after my knowledge cutoff date, I recommend checking the official Elsa Workflows documentation, GitHub repository, and discussions for any updates or new releases that may address this enhancement.