1. Brief description of the
process Approval generally uses flowable or activiti. Let's not talk about the difference. You can download it by yourself on Baidu. Currently, only the table structure description is recorded for activiti.
2. Version introduction (take version 6.0 as an example)
Document: activiti6.0 official document .
Download: activiti6.0 official download address
github: activiti6.0 Github address
In activiti5.0 version, there are 25 tables generated by default, and 6.0 There are 28 tables generated by default in the version.
It can be seen that the 6.0 version has three more tables than the 5.xx version. From the official upgrade document, you can also see that the job job table is mainly split: activiti version 5 is upgraded to version 6 The document guide
here is mainly for the task job table It is divided into: timed task table, suspended task table and failed task table. The functions of other tables are basically unchanged.
Third, table analysis
The tables used by Activiti are all ACT_ prefixes, and column names are all underscore suffixes to prevent keyword conflicts.
ACT_RE_*:
'RE' represents the repository (storage), the table operated by the RepositoryService interface. Tables with this prefix contain static information, such as process definitions, process resources (pictures, rules, etc.).
ACT_RU_*:
'RU' means runtime, the runtime table-RuntimeService. This is the runtime table that stores runtime data such as process variables, user tasks, variables, and responsibilities (job). Activiti only stores runtime data during the execution of the instance, and these records will be deleted when the process instance ends. This ensures that these runtime tables are as small as possible and run fast enough.
ACT_ID_*:
'ID' represents 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, historical data table, HistoryService. It is these tables that contain historical data related to process execution, such as process instances that ended, variables, tasks, etc.
ACT_GE_*:
Global general data and settings (general), data used in various situations.
| Table classification | Table Name | description |
|---|---|---|
| Log | act_evt_log | Event processing log table |
| General data | act_ge_bytearray | General process definition and process resources (binary data table) |
| act_ge_property | System related property configuration | |
| Process history | act_hi_actinst | Historical process examples |
| act_hi_attachment | Slightly longer text | |
| act_hi_comment | Historical process attachment | |
| act_hi_detail | Detailed information in historical process operation | |
| act_hi_identitylink | User relationship during historical process operation | |
| act_hi_procinst | Historical process examples | |
| act_hi_taskinst | Historical mission examples | |
| act_hi_varinst | Variable information in historical process operation | |
| User User Group Table | act_id_group | Identity Information-Group Information |
| act_id_info | User Information-Extended Information | |
| act_id_membership | Identity Information-Intermediate Table of User and Group Relationship | |
| act_id_user | Identity Information-User Information | |
| act_procdef_info | Dead letter mission | |
| Process definition table | act_re_deployment | Deployment unit information |
| act_re_model | Model information | |
| act_re_procdef | Deployed process definition | |
| Run instance table | act_ru_deadletter_job | Execution failed job table |
| act_ru_event_subscr | Runtime events | |
| act_ru_execution | Runtime process execution example | |
| act_ru_identitylink | User relationship information at runtime | |
| act_ru_job | Runtime job | |
| act_ru_suspended_job | Pause task while running | |
| act_ru_task | Runtime task | |
| act_ru_timer_job | Runtime scheduled tasks | |
| act_ru_variable | Runtime variable table |
For details, please refer to: Activiti 5.22 framework database design instructions . There is a detailed introduction to each table.
Fourth, the final
table analysis is over. A version of springboot+gradle+activiti6.0 idea construction instructions will be issued later, as well as the automatic generation of tables.