1) What workflow
A simple understanding is the process of work. The process here refers to a series of work steps to complete a specific business in an enterprise . All the steps together are the flow of business from start to finish .
From the point of view of computer system, workflow system represents: the automatic operation of part and whole of business process in computer application environment.
2) Three elements of workflow
①What should be done in this process?
②How many steps did you go through?
③ Who will do each step, what to do, how to do it
The ProcessEngine class is the core of Activiti5. All services need to be created through ProcessEngine. This class is thread-safe.
The persistence layer of Activiti5 uses Mybatis, so it has good portability.
Activiti5 mainly includes 7 services. ProcessEngine creates
repositoryService (persistence service)
runtimeService (runtime service)
formService (form service)
identityService (identity information)
taskService (task service) historyService
(historical information)
managementService (manage timed tasks)
activiti5 maven dependency
<dependency>
<groupId>org.activiti</groupId>
<artifactId>activiti-spring-boot-starter-basic</artifactId>
<version>5.21.0</version>
</dependency>
Table structure of activiti5
The tables used by Activiti all start with ACT_.
ACT_RE_*: 'RE' represents repository (storage), the table operated by the RepositoryService interface. Tables with this prefix contain static information, such as process definitions, process resources (images, rules, etc.).
ACT_RU_*: 'RU' means runtime, runtime table - RuntimeService. This is the runtime table that stores process variables, user tasks, variables, responsibilities (jobs) and other runtime data. Activiti only stores runtime data during instance execution, and these records are deleted when the process instance ends. This ensures that these runtime tables are small and fast.
ACT_ID_*: 'ID' represents the identity (organization), the table operated by the IdentityService interface. User records, users and groups used in the process. These tables contain identifying information such as users, user groups, and so on.
ACT_HI_*: 'HI' means history, history data table, HistoryService. It is these tables that contain historical data related to process execution, such as terminated process instances, variables, tasks, etc.
ACT_GE_*: Global general data and settings (general), data used in various situations.
act_ge_bytearray binary data table
act_ge_property attribute data table stores the data of the entire process engine level. When initializing the table structure, three records will be inserted by default,
act_hi_actinst historical node table
act_hi_attachment historical attachment table
act_hi_comment historical opinion table
act_hi_identitylink historical process personnel table
act_hi_detail historical detail table, providing Query of historical variables
act_hi_procinst historical process instance table
act_hi_taskinst historical task instance table
act_hi_varinst historical variable table
act_id_group user group information table
act_id_info user extension information table
act_id_membership user and user group correspondence information table
act_re_deployment deployment information table
act_re_model process design model deployment table
act_re_procdef process definition data table
act_ru_event_subscr throwEvent, catchEvent time monitoring information table
act_ru_execution runtime process execution instance table
act_ru_identitylink runtime process personnel table, which mainly stores information about task nodes and participants
act_ru_job runtime timing task data table
act_ru_task runtime task node table
act_ru_variable runtime process variable data table