Activiti related table introduction

The activiti system table has a total of 23 tables, including the process definition table, the general data information table, the process running instance table, the process history table, and the user group table.
1. Activiti process definition table
Process definition table, process definition table can also be called a static resource library, static resources include pictures, definition rules, etc. It has deployment information table, process model table, process definition table
1, ACT_RE_DEPLOYMENT (deployment information table)
including: deployment process name, type, deployment time

2, ACT_RE_MODEL (model table)
name, key, type, creation time, last modification time , version, data source information, deployment ID, edit source value ID, edit source extra value ID (foreign key ACT_GE_BYTEARRAY)

3. ACT_RE_PROCDEF (process definition table)
includes process definition, type, process name, process key, version number, deployment ID , resource name, image resource name, description information, whether to start from key, pause state.

2. Activiti running instance table The
running instance table records the data generated during the flow of the process. The general data is divided into two parts: process data and business data. Process data refers to the data in the flow of the activiti process engine, including process execution instance data connection, task data, task execution personnel information, and variable information. Business data is the form data saved in the process, such as: leave request form data, reimbursement form data, approval opinion information, etc. This part of the data generally needs to be saved by creating a data table by itself, and there was no business saved in the previous jbpm4. data.

1. The function of ACT_RU_EVENT_SUBSCR (event subscript) is unknown
Event name (EVENT_NAME_), event type (EVENT_TYPE_), process execution ID (EXECUTION_ID_), process instance ID (PROC_INST_ID_), activity ID (ACTIVITY_ID_), configuration information (CONFIGURATION_), creation time (CREATED_)

2, ACT_RU_EXECUTION (execution process Execution) core my agency task query table
Process instance ID (PROC_INST_ID_), business key (BUSINESS_KEY_), parent execution process (PARENT_ID_), process definition ID (foreign key PROC_DEF_ID_), instance id (ACT_ID_), activation status (IS_ACTIVE_), Concurrent state (is_concurrent), is_scope, is_evnet_scope, suspended state (suspension_state) ,

cached_end_state
Id (foreign key: TASK_ID_), process instance ID (foreign key: PROC_INST_ID_), process definition Id (foreign key: PROC_DEF_ID_)

4. ACT_RU_JOB (task in operation)
LOCK_EXP_TIME_ (lock release time), LOCK_OWNER_ (suspender), EXECUTION_ID_ (execution instance ID), PROCESS_INSTANCE_ID_ (process instance ID), PROC_DEF_ID_ (process definition ID), EXCEPTION_STACK_ID_ (exception information ID), EXCEPTION_MSG_ (exception information), DUEDATE_ (expiration time)
, REPEAT_ (repeated), HANDLER_TYPE_ (processing type)
HANDLER_CFG_ (identification)

5. ACT_RU_TASK (real-time task in execution) agent task query table
instance id (foreign key EXECUTION_ID_), process instance ID (foreign key PROC_INST_ID_), process definition ID (PROC_DEF_ID_ ), task name (NAME_), parent section task ID (PARENT_TASK_ID_)
, task description (DESCRIPTION_), task definition key (TASK_DEF_KEY_), owner (OWNER_), agent (ASSIGNEE_), agency group (DELEGATION_), priority ( PRIORITY_), creation time (CREATE_TIME_), execution time (DUE_DATE_), suspended state (SUSPENSION_STATE_)

6. ACT_RU_VARIABLE (real-time variable)
variable name (NAME_), encoding type (TYPE_), execution instance ID (EXECUTION_ID_), process instance Id ( PROC_INST_ID_), task id (TASK_ID_), byte group ID (BYTEARRAY_ID_), DOUBLE_, LONG_, TEXT_, TEXT2_

3. Process history

process history information table, activiti history table includes node information table, attachment information table, historical approval record table, ideal details table, historical identity information table, process instance history table, task history table, historical variable table. (Node Information Table, Attachment Information Table, Historical Approval Record Table, Ideal Details Table, Historical Identity Information Table) It is not yet known how these tables are used. The three tables (process instance history table, task history table, and historical variables) can query my completed tasks, task tracking, etc.


1. ACT_HI_ACTINST (activity instance information)
Process Definition ID (PROC_DEF_ID_), Process Instance ID (PROC_INST_ID_), Process Execution ID (EXECUTION_ID_), Activity ID (ACT_ID_), Activity Name (TASK_ID_), Activity Type (ACT_TYPE_), Task ID, (TASK_ID_), Request Process Instance ID (CALL_PROC_INST_ID_), agent (ASSIGNEE_), start time (START_TIME_), end time (END_TIME_), duration (DURATION_)

2, ACT_HI_ATTACHMENT (attachment information)
user id (USER_ID_), name (NAME_), description (DESCRIPTION_), type (TYPE_), task ID (TASK_ID_), process instance ID (PROC_INST_ID_), connection (URL_), content ID (CONTENT_ID_)

3, ACT_HI_COMMENT (historical approval information)
type (TYPE_), time (TIME_), user ID (USER_ID_) , Task Id (TASK_ID_), Process Instance Id (PROC_INST_ID_), Activity (ACTION_), Message (MESSAGE_), All Messages (FULL_MSG_)

4, ACT_HI_DETAIL (History Details)
Data Type (TYPE_), Creation Time (TIME_), Name (NAME_), Process Instance ID (PROC_INST_ID_), Execution Instance Id (EXECUTION_ID_), Task Id (TASK_ID_), Activity Instance Id (ACT_INST_ID_), Variable Type (VAR_TYPE_), Byte Array Id, DOUBLE_, LONG_, Value (TEXT_) , value 2 (TEXT2_)

5, ACT_HI_IDENTITYLINK (historical identity information)
Task Id (TASK_ID_), process instance Id (PROC_INST_ID_), userId (USER_ID_), user group type Type (TYPE_), user group ID (GROUP_ID_)

6, ACT_HI_PROCINST (historical process instance information) core table
process instance ID (PROC_INST_ID_), Business Key (BUSINESS_KEY_), Process Definition Id (PROC_DEF_ID_), Start Time (START_TIME_), End Time (END_TIME_), Duration (DURATION_), Initiator Id (START_USER_ID_), Start Node (START_ACT_ID_), End Node (END_ACT_ID_), Super Process instance ID (SUPER_PROCESS_INSTANCE_ID_), reason for deletion (DELETE_REASON_)

7. ACT_HI_TASKINST (historical task process instance information) core table
Process instance ID (PROC_INST_ID_), task definition Key (BUSINESS_KEY_), process definition ID (PROC_DEF_ID_), execution ID (EXECUTION_ID_) , name (NAME_), parent task iD (PARENT_TASK_ID_), description (DESCRIPTION_), owner (OWNER_), delegate (ASSIGNEE_), start time (START_TIME_), end time (END_TIME_), duration (DURATION_), reason for deletion ( DELETE_REASON__), priority (PRIORITY_), completion time (DUE_DATE_), form key (FORM_KEY_)

8, ACT_HI_VARINST (historical variable information)
Process instance ID (PROC_INST_ID_), execution ID (EXECUTION_ID_), task ID, name (NAME_), variable (TASK_ID_), type (VAR_TYPE_), byte array ID (BYTEARRAY_ID_), DOUBLE_, LONG_, TEXT_, TEXT2_


IV. General data
1. ACT_GE_BYTEARRAY (byte data table)
name (NAME_), deployment Id (DEPLOYMENT_ID_), byte data (BYTES_), occurred (GENERATED_)


2. ACT_GE_PROPERTY (general property table)
name (NAMe_), value (VALUe_)


last User user group table

Activit's user user group table, including user information, user group information, the relationship between users and user groups, and the relationship between user information and users. Not used in actual development, but used by users in actual systems.


1. ACT_ID_GROUP (user group table)
name (NAME_), type (TYPE_)

2, ACT_ID_USER (user table)
last name (FIRST_), name (LAST_), email (EMAIL_), password (PWD_), avatar Id (PICTURE_ID_)

3 , ACT_ID_INFO (user information table)
user Id (USER_ID_), type (TYPE_), formINPut name (KEY_), value (VALUE_), password (PASSWORD_), parent node (PARENT_ID_)

4, ACT_ID_MEMBERSHIP (user user group association table)
user Id (user_ID_), user group Id (group_Id)

The Activiti table structure analysis was completed, it took 5 hours, and there are still many questions that I don't understand. Let’s take care of the relationship between tables in the subsequent development process. The initial idea is to expand the table in the system to separate business data and process data.