Slickflow.NET核心开源工作流引擎

介绍 (Introduction)

For developers eager to understand the engine function, after downloading the version, they want to try to write code to complete the development and testing of a process. This article attempts to illustrate how to quickly understand engine code writing from a simple process.

对于渴望了解引擎功能的开发人员，在下载版本后，他们希望尝试编写代码以完成流程的开发和测试。 本文试图说明如何通过一个简单的过程快速理解引擎代码编写。

背景 (Background)

.NET/.NET Core Workflow Engine With Full Source Code

带有完整源代码的.NET / .NET Core工作流引擎

Github: https://github.com/besley/Slickflow

GitHub ： https : //github.com/besley/Slickflow

1. .NET, .NET CORE version both supported: Slickflow is an open source project based on .NET Framework 4.5, .NET CORE 2; It's easy to use engine product into cross platform application.

   都支持.NET和.NET CORE版本 ：Slickflow是一个基于.NET Framework 4.5，.NET CORE 2的开源项目。 易于将引擎产品用于跨平台应用程序。

2. BPMN graphic style process diagram: Slickflow is using BPMN notation to descript process diagram, the Slickflow designer is HTML5 graph editor and user friendly to business process communication and business analysis.

   BPMN图形样式流程图 ：Slickflow使用BPMN表示法来描述流程图，Slickflow设计器是HTML5图形编辑器，对业务流程通信和业务分析用户友好。

3. High performance with Dapper.NET library: Dapper is a simple object mapper for .NET and own the title of King of Micro ORM in terms of speed and is virtually as fast as using a raw ADO.NET data reader. An ORM is an Object Relational Mapper, which is responsible for mapping between database and programming language. (Reference: https://dapper-tutorial.net/dapper)

   Dapper.NET库具有高性能 ：Dapper是.NET的简单对象映射器，就速度而言，它拥有Micro ORM之王的称号，实际上与使用原始ADO.NET数据读取器一样快。 ORM是对象关系映射器，它负责数据库和编程语言之间的映射。 ( 参考 ： https : //dapper-tutorial.net/dapper )

4. Multiple database supported: Slickflow supports SQLSERVER, ORACLE, MySQL and other database, it implemented by Dapper.NET extension library. The .NET Core version using EF core to support different database products.

   支持多个数据库 ：Slickflow支持SQLSERVER，ORACLE，MySQL等数据库，它由Dapper.NET扩展库实现。 使用EF核心支持不同数据库产品的.NET核心版本。

5. Workflow patterns supported:

   支持的工作流程模式 ：

   

   1. Sequence: The most frequently process pattern

      顺序 ：最常用的处理模式

   2. Split/Merge: Support and/or gateway such as and/or split, and/or join, together with condition variables on the transition

      拆分/合并 ：支持和/或网关，例如和/或拆分 ， 和/或联接 ，以及过渡时的条件变量

   3. Sub-process: In the main process, a sub process node can start a new process life cycle.

      子流程 ：在主流程中，子流程节点可以启动新的流程生命周期。

   4. Multi-instance: Multiple performers processing a task together by multiple task instances. All performers both compete their task, then the process can be continued on. There are sequence and parallel pattern, and the percentage or count parameters can be set on it to ensure when you can go to the next step.

      多实例 ：多个执行者通过多个任务实例一起处理一个任务。 所有表演者都在竞争他们的任务，然后可以继续进行该过程。 有顺序和并行模式，可以在其上设置百分比或计数参数，以确保何时可以进行下一步。

      

   5. Event interoperation: Process instance and activity instance event delegation service, such as process/activity start, execute and complete. The event is also supported to call external method through the configuration of the node on the property page. such as WebApi, SQL, StoreProcedure and Python script.

      事件互操作 ：流程实例和活动实例事件委托服务，例如流程/活动的启动，执行和完成。 还支持通过属性页面上节点的配置来调用外部方法的事件。 例如WebApi，SQL，StoreProcedure和Python脚本。

   6. Timer: Integrated with HangFire library, and with CRON expression supported

      计时器 ：与HangFire库集成，并支持CRON表达式

   7. Email: To do or overdue tasks email notification

      电子邮件 ：待办事项或过期任务的电子邮件通知

   8. Withdraw: Withdraw the task after just being sent out to next step users.

      提现 ：仅在发送给下一步用户后才提现任务。

   9. Sendback: Send back to previous step user, because there are some exceptions.

      Sendback &#