act_ge_property attribute data table storage engine entire process level data, initialization table structure, default insert three records,
Naming database tables
Naming tables in the database are based ACT_ Acitiviti beginning. The second part is a two character identification table with the embodiment. This use case is substantially matched with the service API.
* ACT_RE_ : 'RE' represents the repository. Table with this prefix contains the static information, such as process definition, process resources (images, rules, etc.).
* ACT_RU_ : 'RU' represent runtime. This table is stored in the process variables at runtime, runtime data user tasks, variables, functions (job) and so on. Activiti only stores data during runtime execution instance, when the end of the process instance, to delete these records. This ensures that the table is small and fast runtime of these.
* ACT_ID_ : 'ID' represents identity. These tables contain information identifying, such as users, groups, and the like.
* ACT_HI_ : 'HI' represents history. These tables that contain historical data, such as the end of the process instances, variables, tasks, and so on.
* ACT_GE_ : general data, the data are used in each case.
Database table structure explained
ACT_GE_PROPERTY : attribute table. The storage process engine level data.
1. NAME_: Property Name
2. VALUE_: Property Value
3. REV_INT: version number
ACT_GE_BYTEARRAY : to hold the deployment of large text data files
1. ID_: resource file number, since growth
2. REV_INT: version number
3. NAME_: resource file name
4. DEPLOYMENT_ID_: derived from the primary key of the parent table ACT_RE_DEPLOYMENT
5. BYTES_: large text type, text stored byte stream
ACT_RE_DEPLOYMENT : require persistence information is stored when preserved deployment
1. ID_: deployment number, since growth
2. NAME_: the name of the deployment package
3. DEPLOY_TIME_: deployment time
ACT_RE_PROCDEF : business process definition data table
1. ID_: Process ID, the "Process ID: Process Version: self-growth ID" composition
2. CATEGORY_: Process namespace (the property value is the number of process files targetNamespace)
3. NAME_: name of the process (the number is the name attribute value of the process flow document elements)
4. KEY_: Process number (the number is the value of the id attribute of the process element process file)
5. VERSION_: Process version (controlled by the program, namely a new, incremented by 1 after modification to complete)
6. DEPLOYMENT_ID_: Number deployment
7. RESOURCE_NAME_: resource file name
8. DGRM_RESOURCE_NAME_: image resource file name
9. HAS_START_FROM_KEY_:是否有Start From Key
NOTE: This table and ACT_RE_DEPLOYMENT is many relationship, i.e., a deployment bag bar may contain a plurality of process definition files, each process definition file will have an entry in ACT_REPROCDEF in the table, data for each process definition, It will be a resource file and PNG image files to within ACT_GE_BYTEARRAY table. And ACT_GE_BYTEARRAY association by procedures ACT_GE_BYTEARRAY .NAME with ACT_RE_PROCDEF .NAME_ completed, is not reflected in the database table structure.
ACT_ID_GROUP : used to store user group information.
1. ID_: User Group Name *
2. REV_INT: version number
3. NAME_: user group descriptive information *
4. TYPE_: User Group Type
ACT_ID_MEMBERSHIP : to save the user group information
1. USER_ID_: Username
2. GROUP_ID_: User Group Name
ACT_ID_USER:
1. ID_: Username
2. REV_INT: version number
3. FIRST_: User Name
4. LAST_: user surname
5. EMAIL_: E-mail
6. PWD_: Password
ACT_RU_EXECUTION：
1. ID_：
2. REV_: version number
3. PROC_INST_ID_: process instance ID
4. BUSINESS_KEY_: Business Number
5. PARENT_ID_: Locate the parent executing instances, eventually find examples of execution of the entire process
6. PROC_DEF_ID_: flow ID
7. SUPER_EXEC_: reference implementation template
8. ACT_ID_: node id
9. IS_ACTIVE_: Accesses
10. IS_CONCURRENT_：
11. IS_SCOPE_：
ACT_RU_TASK : task data table runtime.
1. ID_：
2. REV_：
3. EXECUTION_ID_: execution instance id
4. PROC_INST_ID_: id of the process instance
5. PROC_DEF_ID_: id process definition, corresponding to the id_ act_re_procdef
6. NAME_: task name, the name corresponds *** task
7. PARENT_TASK_ID_: corresponds to the parent task
8. DESCRIPTION_：
9. TASK_DEF_KEY_： ***task 的id
10. OWNER_: sponsors
11. ASSIGNEE_: people assigned to the task
12. DELEGATION_: principal
13. PRIORITY_: the urgency of the
14. CREATE_TIME_: Started
15. DUE_TIME_: long-approval
ACT_RU_IDENTITYLINK : Task participant data table. The main participants in the current node to store information.
1. ID_: logo
2. REV_: version
3. GROUP_ID_: Organization id
4. TYPE_: Type
5. USER_ID_: user id
6. TASK_ID_: task id
ACT_RU_VARIABLE : Process variable data table runtime.
1. ID_: logo
2. REV_: version number
3. TYPE_: Data Type
4. NAME_: variable name
5. EXECUTION_ID_: executing instance id
6. PROC_INST_ID_: process instance id
7. TASK_ID_: task id
8. BYTEARRAY_ID_：
9. DOUBLE_: if the data type is double, the data stored in this column
10. LONG_: if the data type is stored data to this Long column
11. TEXT_: string save this column
12. TEXT2_：
ACT_HI_PROCINST：
1. ID_: unique identification
2. PROC_INST_ID_: Process ID
3. BUSINESS_KEY_: Business Number
4. PROC_DEF_ID_: process definition id
5. START_TIME_: Process Start Time
6. ENT__TIME: End Time
7. DURATION_: Process elapsed time
8. START_USER_ID_: user id Open Process
9. START_ACT_ID_: Start Node
10. END_ACT_ID_: End Node
11. SUPER_PROCESS_INSTANCE_ID_: process id parent process
12. DELETE_REASON_: Remove the reason of the operation of the task from the table
ACT_HI_ACTINST：
1. ID_: logo
2. PROC_DEF_ID_: process definition id
3. PROC_INST_ID_: process instance id
4. EXECUTION_ID_: executing instances
5. ACT_ID_: node id
6. ACT_NAME_: Node Name
7. ACT_TYPE_: Node Type
8. ASSIGNEE_: Node Task Assignment people
9. START_TIME_: Start Time
10. END_TIME_: End Time
11. DURATION: Long passes
ACT_HI_TASKINST：
1. ID_: logo
2. PROC_DEF_ID_: process definition id
3. TASK_DEF_KEY_: Task Definition id
4. PROC_INST_ID_: process instance id
5. EXECUTION_ID_: executing instance id
6. PARENT_TASK_ID_: parent task id
7. NAME_: Task Name
8. DESCRIPTION_: Description
9. OWNER_: owner (sponsor)
10. ASSIGNEE_: people assigned to the task
11. START__TIME_: task start time
12. END_TIME_: End Time
13. DURATION_: Duration
14. DELETE_REASON_: reasons for the deletion from the runtime task table
15. PRIORITY_: the urgency of the
16. DUE_DATE_ :
ACT_HI_DETAIL : start the process or after the task complete, recorded history of process variables
1. ID_: logo
2. TYPE_: variableUpdate and formProperty two kinds of value
3. PROC_INST_ID_: the corresponding process instance id
4. EXECUTION_ID_: perform the corresponding instance id
5. TASK_ID_: the corresponding task id
6. ACT_INST_ID: correspondent node id
The name of a historical process variable name, or form attributes: 7. NAME_
8. VAR_TYPE_: Defined Type
9. REV_: version
10. TIME_: introducing time
11. BYTEARRAY_ID_
12. DOUBLE_:, his type variable value exists or if there form attributes defined for double
13. LONG_:, his type variable value exists or if there form attributes defined for LONG
14. TEXT_: If the type or form variable attributes defined for the string, this value is present
15. TEXT2_:
ACT_HI_COMMENT Feedback Form
1. ID_: logo
2. TYPE_: Opinions record type is a comment for the treatment advice
3. TIME_: Record Time
4. USER_ID_ :
5. TASK_ID_: corresponding task id
6. PROC_INST_ID_: id corresponding process instance
7. ACTION_: when AddComment to handle comments
8. MESSAGE_: Disposition
9. FULL_MSG_ :
Conclusion and summary
Process file is deployed mainly related to three tables, namely: ACT_GE_BYTEARRAY , ACT_RE_DEPLOYMENT , ACT_RE_PROCDEF . Mainly to complete the "deployment package" -> "Process Definition File" -> "All files in the package," the deployment of analytic relations. As can be seen from the table structure, the flow defined elements required load and parse each from the database, because no process definition element is converted into complete database tables, of course, the analytical element is placed in the flow cache, the specific needs study in detail later.
Process definition java class files are not stored in the database.
Management organization of relatively weak, if required to be included in the transformation was complete within single sign-on system, the specific transformation method to be studied.
The relationship between the Executive and the database objects need to continue record run-time study
Save and continue to study the role of historical data needs.
Activiti use Mybatis3 persistent work to do, create a table when the process engine start can be set in the configuration.
Activiti tables are beginning to use the ACT_.
* ACT_RE_ : process definition storage.
* ACT_RU_ : process execution record, recording process starts all action to end after the end of the process will erase records.
* ACT_ID_ : user record, the process used to users and groups.
* ACT_HI_ : history of process execution.
* ACT_GE_ : general data and settings.
Use the table:
ACT_GE_BYTEARRAY : data flow deployment.
ACT_GE_PROPERTY : General settings.
ACT_HI_ACTINST : Examples of process activities.
ACT_HI_ATTACHMENT：
ACT_HI_COMMENT：
ACT_HI_DETAIL：
ACT_HI_PROCINST : process instance.
ACT_HI_TASKINST : task instance.
ACT_ID_GROUP : User Group.
ACT_ID_INFO：
ACT_ID_MEMBERSHIP：
ACT_ID_USER : users.
ACT_RE_DEPLOYMENT : deployment records.
ACT_RE_PROCDEF : process definition.
ACT_RU_EXECUTION : process execution record.
ACT_RU_IDENTITYLINK：
ACT_RU_JOB：
ACT_RU_TASK : record execution of the task.
ACT_RU_VARIABLE : variable record implementation.
Transfer from https://www.cnblogs.com/liuqing576598117/p/9816214.html