ABCDEFGHIJKLMNOPQRSTUVWXY
1
WorkflowEngineWorkflowServer
2
General
3
Main purposeAn embedded component designed to be fully integrated into your .NET Framework or .NET Core project.WorkflowServer is a stand-alone application which includes an admin panel and an integration HTTP API. It was designed for microservices-based architecture.
4
OSWindows, Linux, MacOSWindows, Linux, MacOS
5
DatabaseMS SQL Server, MongoDB, Oracle, MySQL, PostgreSQL, RedisMS SQL Server, PostgreSQL, Oracle, MySQL, and MongoDB
6
Graphical/Visual DesignerYes, HTML5Yes, HTML5
7
SecurityWorkflow Engine does not have its own security system. Workflow Engine has IWorkflowRuleProvider for integration with external security system.

How to Manage User Roles in WorkflowEngine: https://workflowengine.io/documentation/faq/workflow-engine/manage-roles/
>= 2.7 OpenId Connect authorization & LDAP user imports OR connecting to an external user catalog

<= 2.6 Workflow Server does not have its own security system. Workflow Server API has identityId (ID of a user who creates or executes workflow). Additionally, you can add Rules via Callback API for checking roles and permissions.

You can set login&password and access token for access to the admin panel and API.
8
APIC# APIHTTP/REST API:
- WorkflowAPI for managing workflows
- CallbackAPI for executing Actions, Rules and Conditions
9
DockerYes, it can be included in the container of your application.Yes
10
Admin panelNoYes
11
File formatXMLXML
12
Demohttps://workflowengine.io/demo/designer/Front-end: https://forms.workflowserver.io/
Admin panel: https://demo.workflowserver.io/
13
14
Features
15
Regular processYesYes
16
Parallel processYesYes
17
Multi Server / Horizontal scalabilityYes (Ultimate version only)Yes (Ultimate version only)
18
Forms and business entitiesNoYes
19
Multi-tenantYesYes
20
Calling external codeYesYes
21
Expressions / Business RulesYesYes
22
Writting code in DesignerYes with IntelliSenseYes with IntelliSense
23
Scheme updatingYesYes
24
Workflow Sheme Generation in codeYesYes
25
ComandsYesYes
26
TimersYesYes
27
LocalizationYesYes
28
User's parametersYesYes
29
LoggingYou can find changes of states in WorkflowTransitionHistory tableYes
30
TemplatesYesYes
31
HTTP(s) RequestYesYes
32
EmailYes, SendingYes, Sending
33
File operationsYesYes
34
SMSYesYes
35
SlackYesYes
36
TelegramYesYes
37
Advanced process monitoringYesYes
38
API for starting and stopping processesYesYes
39
Offline mode of processes execution suitable for mobile applicationsSoonSoon
40
Library of typical processes, i.e. snippetsYesYes
41
Sync with Google SheetsNo>= 3.0 version
42
Sync with Elastic CloudNo>= 3.0 version
43
Export data to ExcelNo>= 3.0 version
44
45
Workflow Desinger
46
Annotations / Custom fields in DesignerYesYes
47
CustomizationYesYes
48
Custom Designer ElementsYesYes
49
Heat MapSoonSoon
50
BPMN ElementsSoonSoon
51
CMMN ElementsSoonSoon
52
53
Integration into ...
54
Custom Web-pageNo, it requires a web-server for processing workflowYes (via iFrame or JavaScript injection)
55
ASP NET MVCYesYes, HTTP API
56
ASP NET Core MVCYesYes, HTTP API
57
ASP NET WebFormsYesYes, HTTP API
58
ASP ClasicYesYes, HTTP API
59
WinForms/WPF/XAMLCore - yes.
Designer via WebBrowser component.
Yes, HTTP API
60
PHP solutionNoYes, HTTP API
61
Python solutionNoYes, HTTP API
62
NodeJs solutionNoYes, HTTP API
63
Java solutionNoYes, HTTP API
64
65
Roadmap
https://workflowengine.io/documentation/roadmap/
66
Email for feature requrestsdmelnikov (at) optimajet.com
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100