Roadmap
Workflow Server uses net8.0 as its Target Framework.
The Workflow Server team constantly makes sure that Workflow Server is compatible with the minimum supported version of the .NET LTS version.
The Workflow Server team does not support versions of the .NET that Microsoft no longer supports (although the product may work correctly).
The Workflow Server team constantly makes sure that NuGet and NPM Workflow Server packages are updated and do not contain any vulnerable dependencies. The team tries to update vulnerable packages as quickly as possible if patches are available for them.
Workflow Server operates on Workflow Engine. As we continuously update the Workflow Engine version, the Workflow Server benefits from allits new features and security patches. To understand the development roadmap of Workflow Engine, you can follow this link.
If you want to add a feature to our roadmap - please open an issue in our GitHub repository.
| Task | Status |
|---|---|
| New plugins with typical operations support. Such as File operations, Parallel Branches, Loops, etc | Done. |
| New Timer Manager and process status restore mechanism for Multi and Single server applications. | Done. |
| Export and import configurations of Workflow Server | Done. |
| Library of typical processes, i.e. snippets. | Done. |
| Forms (based on Vue.js) and business entities in the Workflow Server. | Done. |
| Advanced process monitoring. Logs for each process and state counters. | Done. |
| Decision table. | Done. |
| Real-time workflow tracking. | Done. |
| BPMN elements support. BPMN diagram import. | Done. |
| Parameters for Inline activity. This will allow you to parameterize the Inline activity. | Done. |
| Event-triggered transitions. This will allow you to initiate a transition in a process or a group of processes. | In progress |
| New embedded form engine. | |
| Improved version of Business Flow. | |
| Simultaneous work with multiple databases in multi-tenant mode. | |
| Start a workflow by event. This will allow a process or group of processes to be started by an event. | |
| Workflow that can run on a schedule. | |
| Tenant-aware activities. It will allow you to create custom activities that relate only to the specified tenant. | |
| Asynchronous activities. The actions of such activities can be executed asynchronously, for example on a remote server. | |
| API for starting and stopping processes in Workflow Engine and Workflow Server. | |
| New end-user customizable process designer. |