当前位置:网站首页>Activity workflow table structure learning
Activity workflow table structure learning
2022-07-29 05:01:00 【Blue sky ⊙ white clouds】
One 、 Seven core interfaces
RepositoryService: Provides a series of tools to manage process deployment and process definition API
RunntimeService: Manage and control process instances when the process is running
TaskService: Manage process tasks , For example, task reminder , Task completion and creation, etc
IdentityService: Provides a way to manage process role data API, These roles include user groups 、 Users and their relationships
ManagementService: Provide services to manage and maintain the process engine
HistoryService: Operate on the historical data of the process , Including inquiries , Delete these historical data
FormService: Provide form filling service for operation flow
Two 、28 The data structure of a table

act_ge_ The beginning represents the general table ,ge yes general Abbreviation
act_hi_ The beginning represents the historical data table ,hi yes history Abbreviation , Corresponding HistoryService Interface API
act_id_ The beginning represents identity authentication data ,id yes identity Abbreviation , Corresponding IdentityService Interface API
act_re_ The beginning represents the process storage table ,re yes repository Abbreviation , Corresponding RepositoryService Interface API, Store static data of process deployment and process definition
act_ru_ The beginning represents the process operation data table ,ru yes runntime Abbreviation , Corresponding RunntimeService Interface API, Store dynamic data such as process instances and user tasks
Table structure operations :
Resource pool process rule table
- 1) act_re_deployment Deployment information sheet
- 2) act_re_model Process design model deployment table
- 3) act_re_procdef Process definition data sheet
Runtime database tables
- 1) act_ru_execution Runtime process execution instance table
- 2) act_ru_identitylink Run time process personnel table , It mainly stores information about task nodes and participants
- 3) act_ru_task Runtime task node table
- 4) act_ru_variable Runtime process variable data table
Historical database tables
- 1) act_hi_actinst History node table
- 2) act_hi_attachment Historical attachment table
- 3) act_ih_comment Historical opinion form
- 4) act_hi_identitylink Historical process personnel list
- 5) act_hi_detail Historical details , Provide query of historical variables
- 6) act_hi_procinst Historical process example table
- 7) act_hi_taskinst Examples of historical tasks
- 8) act_hi_varinst Table of historical variables
Organization chart
- 1) act_id_group User group information table
- 2) act_id_info User extended information table
- 3) act_id_membership User and user group corresponding information table
- 4) act_id_user User information sheet
These four tables are very common , Basic organizational management , As for user authentication, it is suggested to develop a set of , The function of the component is too simple , There are many requirements that are difficult to meet in use
General data sheet
- 1) act_ge_bytearray Binary data table
- 2) act_ge_property The attribute data table stores data at the entire process engine level , When initializing the table structure , Three records will be inserted by default
activiti.cfg.xml(activiti Configuration file for )
Activiti Core profile , Configure the basic parameters of the process engine creation tool and database connection pool parameters .
Define database configuration parameters :
- jdbcUrl: Database JDBC URL.
- jdbcDriver: Drivers corresponding to different database types .
- jdbcUsername: User name to connect to the database .
- jdbcPassword: Password to connect to the database .
be based on JDBC Parameter configuration of the database connection Will use the default MyBatis Connection pool . The following parameters can be used to configure the connection pool ( come from MyBatis Parameters ):
- jdbcMaxActiveConnections: The maximum number of connections in use in the connection pool . The default is 10.
- jdbcMaxIdleConnections: The maximum number of idle connections in the connection pool .
- jdbcMaxCheckoutTime: The longest time the connection has been taken out of use , Over time will be forced to recycle . The default is 20000(20 second ).
- jdbcMaxWaitTime: This is an underlying configuration , So that the connection pool can be unable to get a connection for a long time , Print a log , And try again to get a connection .( Avoid silent operation failure due to wrong configuration ). The default is 20000(20 second ).
Process deployment related table
- act_re_deployement Deployment object table
- act_rep_procdef Process definition form
- act_ge_bytearray Resource file table
- act_ge_prperty Generate policy table from primary key ( For the primary key of the deployment object table ID)
Process instance related table
- act_ru_execution Executing object table ( Contains the execution object ID And process instances ID, If there are multiple threads, there may be process instances ID Dissimilarity )
- act_hi_procinst Process instance history table
- act_hi_actinst Store all completed tasks in history
Task Task related table
- act_ru_task To do list ( Only the corresponding node is UserTask Of )
- act_hi_taskinst The history table of the entrusted tasks ( Only the corresponding node is UserTask Of )
- act_hi_actinst Activity history table of all nodes ( The activity history of all nodes of the corresponding process , The activities of all nodes from the start node to the end node will be recorded )
Process variable table
- act_ru_variable Executing process variable table
- act_hi_variable Process variable history
3、 ... and 、 The data dictionary
Save the process definition image and xml、Serializable( serialize ) The variable of , Save all binary data , Pay special attention to class path deployment , Don't put the svn And other hidden files or other files unrelated to the process are also deployed to the table , It will cause some mistakes ( The process definition may not be deleted )
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key | varchar | ||
| REV_ | Version number | int | version | |
| NAME_ | Deployed file name | varchar | ||
| DEPLOYMENT_ID_ | From the parent table ACT_RE_DEPLOYMENT Primary key of | varchar | The deployment of ID | |
| BYTES_ | Big text types , Store text words throttle | LONGBLOB | ||
| GENERATED_ | Is it engine generation | int | 0 Generate... For users 1 by Activiti Generate |
Attribute data sheet . Store this process engine level data
| Field name | Field description | data type | The default value | Value description ( Example ) |
| NAME_ | The attribute name | varchar | schema.version schema.history next.dbid | |
| VALUE_ | Property value | varchar | 5.* create(5.*) | |
| REV_INT | Version number | int |
Information on historical activities . Here, all nodes of the process flow are recorded , And HI_TASKINST The difference is ,taskinst Record only usertask Content
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| PROC_DEF_ID_ | Process definition ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| EXECUTION_ID_ | Process execution ID | varchar | ||
| ACT_ID_ | Activities ID | varchar | Node definition ID | |
| TASK_ID_ | Mission ID | varchar | Task instance ID , Other node type instances ID It's empty here | |
| CALL_PROC_INST_ID_ | Request process instance ID | varchar | Call the process instance of the external process ID | |
| ACT_NAME_ | The name of the event | varchar | Node definition name | |
| ACT_TYPE_ | Type of activity | varchar | Such as startEvent、userTask | |
| ASSIGNEE_ | Agent | varchar | Node signer | |
| START_TIME_ | Starting time | datetime | ||
| END_TIME_ | End time | datetime | ||
| DURATION_ | Duration 、 Time consuming | int | Millisecond value |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| REV_ | Version number | int | ||
| USER_ID_ | user ID | varchar | ||
| NAME_ | Appendix name | varchar | ||
| DESCRIPTION_ | Attachment description | varchar | ||
| TYPE_ | Attachment type | varchar | ||
| TASK_ID_ | Mission ID | varchar | Node instance ID | |
| PROC_INST_ID_ | Process instance ID | varchar | ||
| URL_ | Attachment link | varchar | ||
| CONTENT_ID_ | Content ID | varchar | ||
| START_TIME_ | Starting time | datetime | ACT_GE_BYTEARRAY Of ID |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| TYPE_ | Type of opinion record , by comment when , To deal with opinions | varchar | type :event( event )、comment( opinion ) | |
| TIME_ | Recording time | datetime | ||
| USER_ID_ | user ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| ACTION_ | Type of behavior . by addcomment when , To deal with opinions | varchar | The value is A kind of : AddUserLink、 DeleteUserLink、 AddGroupLink、 DeleteGroupLink、 AddComment、 AddAttachment、 DeleteAttachment | |
| MESSAGE_ | Handling opinions | varchar | ||
| FULL_MSG_ | All messages | longblob |
Historical details : The variables generated in the process are detailed , Include variables that control the flow of the process , Variables needed for the process filled in the business form
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| TYPE_ | data type | varchar | type : FormProperty, // Forms VariableUpdate // Parameters | |
| PROC_INST_ID_ | Process instance id | varchar | ||
| EXECUTION_ID_ | Execution examples id | varchar | ||
| TASK_ID_ | Mission ID | varchar | ||
| ACT_INST_ID_ | Examples of activities ID | varchar | ACT_HI_ACTINST Tabular ID | |
| NAME_ | name | varchar | ||
| VAR_TYPE_ | Variable type | longblob | jpa-entity、boolean、bytes、serializable( Serializable )、 Customize type( According to your own configuration )、CustomVariableType、date、double、integer、long、null、 short、string | |
| REV_ | Version number | int | ||
| TIME_ | Creation time | datetime | ||
| BYTEARRAY_ID_ | Byte array id | ACT_GE_BYTEARRAY Tabular ID | ||
| DOUBLE_ | The storage variable type is Double | double | ||
| LONG_ | The storage variable type is Long | long | ||
| TEXT_ | The storage variable type is String | varchar | ||
| TEXT2_ | The storage variable type is String | varchar | What's stored here is JPA When persisting objects , It's worth it . This value is the object ID |
Task participant data sheet . It mainly stores the information of historical node participants
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| GROUP_ID_ | User group ID | varchar | ||
| TYPE_ | User group type | datetime | Mainly divided into the following kinds :assignee、candidate、owner、starter 、participant | |
| USER_ID_ | user ID | varchar | ||
| TASK_ID_ | Mission ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| BUSINESS_KEY_ | Business Key | datetime | ||
| PROC_DEF_ID_ | Process definition Id | varchar | ||
| START_TIME_ | Starting time | datetime | ||
| END_TIME_ | End time | datetime | ||
| DURATION_ | Duration | int | ||
| START_USER_ID_ | Initiator ID | varchar | ||
| START_ACT_ID_ | Start node | varchar | ||
| END_ACT_ID_ | The end node | varchar | ||
| SUPER_PROCESS_INSTANCE_ID_ | Super process instance Id | varchar | ||
| DELETE_REASON_ | Delete reason | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| PROC_DEF_ID_ | Process definition ID | varchar | ||
| TASK_DEF_KEY_ | Task definition ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| EXECUTION_ID_ | perform ID | varchar | ||
| NAME_ | name | varchar | ||
| PARENT_TASK_ID_ | Father task ID | varchar | ||
| DESCRIPTION_ | describe | varchar | ||
| OWNER_ | The actual signer 、 The owner of the task | varchar | Signed by ( The default is empty. , It's only worth it when it's commissioned ) | |
| ASSIGNEE_ | The agent | varchar | ||
| START_TIME_ | Starting time | datetime | ||
| CLAIM_TIME_ | Reminder time | datetime | ||
| END_TIME_ | End time | datetime | ||
| DURATION_ | Time consuming | bigint | ||
| DELETE_REASON_ | Delete reason | varchar | ||
| PRIORITY_ | priority | int | ||
| DUE_DATE_ | Due completion time | datetime | Expiration time , Indicate how long the task should be completed | |
| FORM_KEY_ | Forms key | varchar | desinger Node defined form_key attribute |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Primary key ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| EXECUTION_ID_ | perform ID | varchar | ||
| TASK_ID_ | Mission ID | varchar | ||
| NAME_ | name | varchar | ||
| VAR_TYPE_ | Variable type | varchar | ||
| REV_ | edition | int | ||
| BYTEARRAY_ID_ | Byte array ID | varchar | ACT_GE_BYTEARRAY Primary Key | |
| DOUBLE_ | The storage variable type is Double | double | ||
| LONG_ | The storage variable type is Long | long | ||
| TEXT_ | The storage variable type is String | varchar | ||
| TEXT2_ | The storage variable type is String | varchar | What's stored here is JPA When persisting objects , It's worth it . This value is the object ID |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | User group ID | varchar | ||
| REV_ | edition | int | ||
| NAME_ | User group description information | varchar | ||
| TYPE_ | User group type | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | edition | int | ||
| USER_ID_ | user ID | varchar | ||
| KEY_ | formINPut name | varchar | ||
| VALUE_ | value | varchar | ||
| PASSWORD_ | password | LONGBLOB | ||
| PARENT_ID_ | Parent node | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| GROUP_ID_ | User group ID | varchar | ||
| USER_ID_ | user ID | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | ||
| FIRST_ | User name | varchar | ||
| LAST_ | User last name | varchar | ||
| EMAIL_ | mailbox | varchar | ||
| PWD_ | password | varchar | ||
| PICTURE_ID_ | Head portrait ID | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Deployment number | varchar | ||
| NAME_ | The name of the deployment package | varchar | ||
| CATEGORY_ | type | varchar | ||
| TENANT_ID_ | Tenant | varchar | Multi tenancy is usually a concept that arises when software needs to serve multiple different organizations | |
| DEPLOY_TIME_ | Deployment time | TIMESTAMP |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | Deployment number | varchar | ||
| REV_ | Optimism lock | int | ||
| NAME_ | The name of the model | varchar | ||
| KEY_ | Key words of the model , The process engine uses | varchar | ||
| CATEGORY_ | type , User's own classification of process model | varchar | ||
| CREATE_TIME_ | Creation time | TIMESTAMP | ||
LAST_UPDATE_TIME_ | Last modified | TIMESTAMP | ||
| VERSION_ | edition , from 1 Start | int | ||
| META_INFO_ | Data source information , such as :{"name":"FTOA_SWGL","revision":1,"description":"xx The Bureau of Finance OA, Incoming document management process "} | varchar | With json Save process definition information in format | |
| DEPLOYMENT_ID_ | Deploy ID | varchar | ||
EDITOR_SOURCE_VALUE_ID_ | Edit source value ID | varchar | ||
EDITOR_SOURCE_EXTRA_VALUE_ID_ | Edit source extra value ID( Foreign keys ACT_GE_BYTEARRAY | varchar | ||
| TENANT_ID_ | Tenant | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | technological process ID, from “ Process number : Process version number : Self growth ID” form | varchar | ||
| REV_ | Version number | int | Optimism lock | |
| CATEGORY_ | Process namespace ( This number is the process document targetNamespace The attribute value ) | varchar | Process defined Namespace It's the category | |
| NAME_ | Process name ( This number is the process document process Elemental name Property value ) | varchar | ||
| KEY_ | Process number ( This number is the process document process Elemental id Property value ) | varchar | ||
| VERSION_ | Process version number ( Controlled by program , The new one is 1, After modification, proceed in sequence 1 To complete | int | ||
DEPLOYMENT_ID_ | Deployment number | varchar | ||
RESOURCE_NAME_ | Resource file name | varchar | ||
DGRM_RESOURCE_NAME_ | Picture resource name | varchar | With json Save process definition information in format | |
| DESCRIPTION_ | describe | varchar | ||
HAS_START_FORM_KEY_ | Whether from key start-up | int | start Whether the node exists formKey 0 no 1 yes | |
SUSPENSION_STATE_ | Whether to suspend | int | 1 Activate 2 Hang up |
notes : This watch and ACT_RE_DEPLOYMENT It's many-to-one , namely , A deployed war The package may contain multiple process definition files , Each process definition file will have a record in ACT_RE_PROCDEF In table , Data defined for each process , Will be for ACT_GE_BYTEARRAY A resource file in the table and PNG Picture file . and ACT_GE_BYTEARRAY The connection is through the program ACT_GE_BYTEARRAY.NAME And ACT_RE_PROCDEF.NAME_ Accomplished , It is not reflected in the database table structure .
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| EVENT_TYPE_ | Event type | varchar | ||
| EVENT_NAME_ | Event name | varchar | ||
| EXECUTION_ID_ | Process execution ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| ACTIVITY_ID_ | Activities ID | varchar | ||
| CONFIGURATION_ | Configuration information | varchar | ||
| CREATED_ | Creation time | TIMESTAMP | CURRENT_TIMESTAMP |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| PROC_INST_ID_ | Process instance number | varchar | ||
| BUSINESS_KEY_ | Business number | varchar | ||
| PARENT_ID_ | Parent execution process | varchar | ||
| PROC_DEF_ID_ | Process definition ID | varchar | ||
| SUPER_EXEC_ | varchar | |||
| ACT_ID_ | example ID | varchar | ||
| IS_ACTIVE_ | active | int | Whether to activate | |
| IS_CONCURRENT_ | Concurrent state | int | Is it parallel true、false | |
| IS_SCOPE_ | int | |||
| IS_EVENT_SCOPE_ | int | |||
SUSPENSION_STATE_ | Pause state | int | Pending state :1 Activate 2 Hang up | |
CACHED_ENT_STATE_ | Cache end state | int |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| GROUP_ID_ | User group ID | varchar | ||
| TYPE_ | User group type | varchar | Mainly divided into the following kinds :assignee、candidate、owner、starter、participant. namely : Transferee , The candidate , owner 、 starter 、 participants | |
| USER_ID_ | user ID | varchar | ||
| TASK_ID_ | Mission ID | varchar | ||
| PROC_INST_ID_ | Process instance ID | varchar | ||
| PROC_DEF_ID_ | Process definition ID | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| TYPE_ | type | varchar | Mainly divided into the following kinds :assignee、candidate、owner、starter、participant. namely : Transferee , The candidate , owner 、 starter 、 participants | |
| LOCK_EXP_TIME_ | Lock release time | TIMESTAMP | ||
| LOCK_OWNER_ | Suspended | varchar | ||
| EXCLUSIVE_ | int | |||
| EXECUTION_ID_ | Execution examples ID | varchar | ||
PROCESS_INSTANCE_ID_ | Process instance ID | varchar | ||
| PROC_DEF_ID_ | Process definition id | varchar | ||
| RETRIES_ | varchar | |||
EXCEPTION_STACK_ID_ | Abnormal information ID | varchar | ||
| EXCEPTION_MSG_ | Abnormal information | varchar | ||
| DUEDATE_ | Due time | TIMESTAMP | ||
| REPEAT_ | repeat | varchar | ||
| HANDLER_TYPE_ | Type of treatment | varchar | ||
| HANDLER_CFG_ | identification | varchar |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| EXECUTION_ID_ | Execution examples ID | varchar | ||
PROCESS_INSTANCE_ID_ | Process instance ID | varchar | ||
| PROC_DEF_ID_ | Process definition id | varchar | ||
| NAME_ | The name of the task | Node definition name | ||
PARENT_TASK_ID_ | Parent node task ID | varchar | Parent node instance ID | |
| DESCRIPTION_ | Task description | varchar | ||
| TASK_DEF_KEY_ | Task definition key | varchar | ||
| OWNER_ | Owner | varchar | The owner ( Generally, it is empty , It's only worth it when it's commissioned ) | |
| ASSIGNEE_ | The agent | varchar | ||
| PRIORITY_ | Priority | int | Priority , The default is :50 | |
| CREATE_TIME_ | Creation time | TIMESTAMP | ||
| DUE_DATE_ | execution time | DATETIME | Time consuming | |
SUSPENSION_STATE_ | Pause state | int | 1 Represents activation 、2 Stands for pending |
| Field name | Field description | data type | The default value | Value description ( Example ) |
| ID_ | varchar | |||
| REV_ | Version number | int | Optimism lock | |
| TYPE | The encoding type | varchar | ||
| NAME_ | Variable name | varchar | ||
| EXECUTION_ID_ | Execution examples ID | varchar | ||
| PROC_INST_ID_ | Process instance id | varchar | ||
| TASK_ID_ | Mission ID | |||
| BYTEARRAY_ID_ | Byte array ID | varchar | ACT_GE_BYTEARRAY Primary Key | |
| DOUBLE_ | The storage variable type is Double | double | ||
| LONG_ | The storage variable type is Long | long | ||
| TEXT_ | The storage variable type is String | varchar | ||
| TEXT2_ | The storage variable type is String | varchar | What's stored here is JPA When persisting objects , It's worth it . This value is the object ID |
</article>
边栏推荐
- Basic grammar of C language
- Un7.28: common commands of redis client.
- ODOO开发教程之透视表
- 2021-10-23
- Excel卡住了没保存怎么办?Excel还没保存但是卡住了的解决方法
- How is the entered query SQL statement executed?
- 使用近场探头和电流探头进行EMI干扰排查
- MySQL定时调用预置函数完成数据更新
- Various configurations when pulsar starts the client (client, producer, consumer)
- PHP判断用户是否已经登录,如果登录则显示首页,如果未登录则进入登录页面或注册页面
猜你喜欢

2022杭电多校联赛第四场 题解

EMI interference troubleshooting with near-field probe and current probe

五个关联分析,领略数据分析师一大重要必会处理技能

Traffic flow prediction pit climbing record (I): traffic flow data set, original data
带你搞懂 Kubernetes 集群中几种常见的流量暴露方案

2021-10-23

【无标题】

MySQL regularly calls preset functions to complete data update

Excel怎么筛选出自己想要的内容?excel表格筛选内容教程

SSM integration, addition, deletion, modification and query
随机推荐
ODOO开发教程之图表
Ethernet of network
Wechat picture identification
Download addresses of various versions of MySQL and multi version coexistence installation
How to make the characters in the photos laugh? HMS core video editing service one click smile function makes people smile more naturally
What if excel is stuck and not saved? The solution of Excel not saved but stuck
Huawei ilearning AI mathematics foundation course notes
虚拟偶像的歌声原来是这样生成的!
ODOO开发教程之透视表
How does WPS use smart fill to quickly fill data? WPS method of quickly filling data
Let you understand several common traffic exposure schemes in kubernetes cluster
Mapper agent development
ios面试准备 - objective-c篇
2021-10-11
带你一文理解JS数组
IOS interview preparation - Online
Opencv learning 1 (environment configuration)
Big silent event Google browser has no title
DataSourceClosedException: dataSource already closed at Mon Oct 25 16:55:48 CST 2021
excel怎么设置行高和列宽?excel设置行高和列宽的方法