Roadmap
This page outlines the .NET support policy, the current status of planned features, and ongoing work items. It covers which .NET versions are supported, what features are in progress or planned, recently shipped capabilities, and how to request new functionality or influence the product direction.
This roadmap is a living document. Dates and scope may change based on feedback and development progress.
.NET support policy
Workflow Engine packages use netstandard2.0 (the Oracle provider uses netstandard2.1). The following .NET releases are supported:
- .NET 8 (LTS)
- .NET 10 (LTS)
- .NET Framework 4.6.2 (except the Oracle Database provider)
The Workflow Engine team constantly makes sure that Workflow Engine is compatible with the minimum supported version of the .NET (LTS version) / .NET Framework. Versions of .NET / .NET Framework that Microsoft no longer supports are not supported (although the product may work correctly).
Dependency policy: Workflow Engine (NuGet) and Workflow Designer (NPM) packages are regularly updated to remove vulnerable dependencies. The team patches vulnerabilities as soon as fixes are available.
Designer packages are periodically updated to work with the latest versions of React and Angular.
Want to add a feature to the roadmap? Open an issue on GitHub.
Feature status
The table below lists planned and in-progress features. Shipped features are listed in a separate section below.
| Task | Status |
|---|---|
| Event-triggered transitions | In progress |
| Start a workflow by event | Planned |
| Workflow that can run on a schedule | Planned |
| Embeddable administration panel | Planned |
| Tenant-aware activities | Planned |
| Plugin for integration with message queues | Planned |
| Asynchronous activities (remote execution) | Planned |
| Unification of relational database providers | Planned |
| API for starting and stopping processes | Planned |
| Open-source React and Angular Designer packages | Planned |
| New end-user customizable designer | Planned |
| Role-based access in Workflow Designer | Analysis |
Recently shipped
- WFE: Workflow Engine.
- WFS: Workflow Server.
| Task | Released in |
|---|---|
| Human task plugin with embedded form engine | WFE 20.0 |
| Web API RPC (manage workflows via HTTP API) | WFE 19.0 |
| BPMN plugin (import BPMN schemas, BPMN-like activities) | WFE 16.0 |
| Parameters for Inline activity | WFE 16.0 |
| Web API Data (HTTP API for workflow entities) | WFE 14.0 |
| Real-time tracking plugin | WFE 13.0 |
| Automatic database schema versioning and migration | WFE 13.0 |
| Business calendars (timers in working hours/days) | WFE 11.0 / WFS 4.0 |
| Advanced process monitoring (logs, state counters) | WFE 5.1 / WFS 2.8 |
| Decision table | WFE 5.1 / WFS 2.8 |
| New plugins with typical operations support (File operations, Parallel Branches, Loops, etc.) | WFE 5.0 / WFS 2.7 |
| Library of typical processes (snippets) | WFE 5.0 / WFS 2.7 |
| Export and import Workflow Server configurations | WFS 2.7 |
| Forms (Vue.js) and business entities in Workflow Server | WFS 2.7 |
| Timer Manager and process status restore for Multi- and Single-server | WFE 4.2 / WFS 2.6 |
Frequently asked questions
How is the roadmap prioritized?
Items are prioritized based on customer demand, strategic value, and engineering investment. Enterprise customers can influence priority through their account team.
When will the next release ship?
Workflow Engine follows a continuous delivery model. Minor and patch releases ship as features and fixes are ready. See Release Notes for the latest shipped version.
How do I request a feature?
Open an issue on GitHub or contact sales@optimajet.com.