Attachable Forms Attachable Forms associate a data entry form with each activity so users fill in the right fields at the right step - without building custom UIs per activity.
BPMN Support BPMN support lets you import BPMN 2.0 diagrams from external modeling tools into Workflow Engine - no need to re-author process flows from scratch.
Bulk API Bulk API runs workflow operations on hundreds of process instances in parallel with per-instance error isolation so one failure does not block the rest.
Clustering Clustering lets you run multiple Workflow Engine servers against the same database for high availability and throughput - no external coordinator required.
Customization Customization lets you adapt the Visual Designer with custom activity types, controls, autocomplete, and conditions - without modifying the core libraries.
Database Versioning Workflow Engine manages database schema migrations through automatic RunMigrations calls or manual SQL scripts to keep schemas in sync with the runtime.
Direct State Control Direct state control moves a process instance to an approved target state through the runtime for recovery, migration, and administration.
HTTP API The Workflow Engine HTTP API exposes workflow commands and data operations over HTTP so any client can integrate without writing custom code.
Workflow Engine Features Workflow Engine delivers a visual designer, versioning, clustering, multitenancy, pluggable security, and plugins - all in one embeddable .NET library.
Interactive Designer The Interactive Designer shows process state changes in real time - activity transitions, timer firings, and command execution - without refreshing the page.
Multi-Database Support Store workflow state in the database you already use - SQL Server, PostgreSQL, MySQL, MongoDB, Oracle, or SQLite - without writing migration scripts.
Multitenancy Multitenancy lets a single Workflow Engine deployment serve many tenants with process data isolation via separate databases or TenantId filtering.
Offline API The Offline API provides approval mapping and batch command execution - compute transitions and execute multiple commands without a per-operation connection.
Parallel Processes Parallel processes let a parent spawn child instances that run independently - model concurrent work without splitting your main flow into disconnected pieces.
Pluggable Security Pluggable security lets you use your identity system - SSO, LDAP, Active Directory, or custom user store - to control who executes each command in a workflow.
Plugin System The plugin system lets you add reusable workflow capabilities - approvals, email, file attachments - to the runtime without writing custom action code.
Pre-Execution (Simulation) Pre-Execution (Simulation) shows users the predicted workflow path before committing - enabling confirm-before-execute UIs without altering process state.
Process Logs Process Logs record every state change on a process instance - who, what, when, and which path was taken - a complete audit trail without custom logging code.
Process Versioning Process versioning deploys new workflow definitions safely while running instances keep their scheme or migrate at configured activities.
Simple Process Notation Simple Process Notation lets business analysts and developers design workflows as flowcharts with just three building blocks - no BPMN certification required.
Timers & Scheduling Timers on transitions let Workflow Engine fire state changes automatically after a delay, at a specific time, or on a recurring schedule without user input.
Visual Designer Visual Designer lets business users build workflow schemes through drag-and-drop - process changes ship in hours instead of waiting on a development backlog.
Work Calendar Define business hours and holidays once so timers skip weekends, after-hours, and non-working days - no manual date arithmetic needed.
Workflow as Code Workflow as Code lets you create workflow schemes in C# using the fluent ProcessDefinitionBuilder API, with compile-time checking and full IDE support.
Workflow Templates Workflow templates let you define reusable process fragments that are inlined into a parent scheme at build time, producing one expanded process definition.

#features