Activiti is battle-tested Business Process Management. Organizations across the world depend on the open source platform in a huge range of demanding situations. It supports open standards with BPMN and DMN so you can create processes that suit you.
Workflow is the computational model of workflow, that is, the logic and rules of how the work in the workflow is organized together before and after are represented in a computer with an appropriate model and calculated. It mainly solves "to automate the process of passing documents, information or tasks among multiple participants according to some predefined rules, so as to achieve a certain expected business goal, or to promote the realization of this goal". (My understanding is: let the computer handle some or all of the workflow and logic for you to automate)
The founder of Activiti is also the founder of JBPM (also an excellent BPM engine). After leaving Jboss, he developed a new BPM engine: Activiti. Therefore, Activiti has the shadow of JBPM in many places. Therefore, it is said that friends who have studied JBPM learned Activiti very easily.
Activiti is an open source workflow engine, which implements the BPMN 2.0 specification, and can publish the designed process definition and schedule the process through api.
As an Apache-licensed open source platform for workflow and business process management, Activiti's core is a Java-based ultra-fast and ultra-stable BPMN2.0 process engine, emphasizing the embeddability and extensibility of process services, and at the same time emphasizing more Business people.
The Activiti process engine focuses on ease of use and lightness in system development. Each BPM business function Activiti process engine is provided to developers as a service. By using these services, developers can build feature-rich, lightweight and efficient BPM applications.
key object
1.Deployment: Process deployment object, created when a process is deployed.
2.ProcessDefinitions: Process definitions, which are automatically created after successful deployment.
3.ProcessInstances: Process instances, created when the process is started.
4. Task: Task, Task in Activiti only refers to tasks with roles participating, that is, UserTask in the definition.
5.Execution: Execution plan, process instance and all nodes in process execution are Execution, such as UserTask, ServiceTask, etc.
service interface
1.ProcessEngine: The abstraction of the process engine, through which we can get all the services we need.
2.RepositoryService: The definition of each different version of the business process in Activiti needs to use some definition files, deployment files and supporting data (such as BPMN2.0 XML files, form definition files, process definition image files, etc.), these files are stored In Activiti's built-in Repository. RepositoryService provides access to repository services.
3.RuntimeService: In Activiti, every time a process definition is started once, a corresponding process object instance will be generated. RuntimeService provides functions such as starting a process, querying process instances, and setting and obtaining process instance variables. In addition, it provides access to process deployment, process definitions and process instances.
4. TaskService: Each execution node in the business process definition in Activiti is called a Task, and operations such as data access and state changes in the process need to be completed in the Task. TaskService provides operations related to user Task and Form. It provides runtime task query, collection, completion, deletion, and variable setting functions.
5.IdentityService: Activiti has built-in user and group management functions, and the information of these users and groups must be used to obtain the corresponding Task. IdentityService provides management functions for users and groups in the Activiti system.
6.ManagementService: ManagementService provides management and maintenance functions for the Activiti process engine. These functions are not used in workflow-driven applications and are mainly used for the daily maintenance of the Activiti system.
7.HistoryService: HistoryService is used to obtain information about running or completed process instances. Different from the process information obtained in RuntimeService, history information contains persistent information that has been persisted and has been optimized for queries.