Activiti Workflow Engine database table structure

Engineering uni league tables

Copyright Notice: This article for Bo Master original article, without Bo Master permission not reproduced. Do not allow copy, to pursue legal responsibility, welcome to join our Learning Promotion Group 466355109, can communicate with each other

S earch engine land periodic table

Naming a database table

search engine land seo periodic table

The names of tables in the Acitiviti database begin with Act_. The second part is the identification of a two-character use case table. This use case is broadly matched to the service API.

L act_re_*: ' RE ' means repository. The table with the prefix contains static information, such as the process definition, the flow of resources (pictures, rules, etc.).

L act_ru_*: ' RU ' indicates runtime. This is the runtime table that stores the process variables, user tasks, variables, responsibilities (job), and other runtime data. Activiti only stores run-time data during instance execution, and when the process instance ends, the records are deleted. This ensures that these run-time tables are small and fast.

L act_id_*: ' ID ' denotes identity. These tables contain information that is identified, such as users, user groups, engineering drawing table buy online and so on.

L act_hi_*: ' HI ' means history. These are the tables that contain historical data, such as end-of-process instances, variables, tasks, and so on.

L Act_ge_*: General data, data used in various situations.

database table structure diagram

Civil engineering tables

database table Structure Description ( Beijing Edge Network collation )

L Act_ge_property: Attribute data table. Store data at this process engine level.

1. Name_: Attribute Name

2. Value_: Attribute value

3. Rev_int: Version number

Automotive engineering league tables

L Act_ge_bytearray: Large text data to save the deployment file

1. Id_: Resource file number, self-growth

2. Rev_int: Version number

3. Name_: Resource file name

4. Deployment_id_: Primary key from parent table Act_re_deployment

5. Bytes_: Large text type, storing text byte stream

L Act_re_deployment: Used to store information that needs to persist during deployment

1. Id_: Deployment number, self-growth

2. Name_: Name of the deployment package

3. Deploy_time_: Deployment Time

L ACT_RE_PROCDEF: Business process definition Data Sheet

1. ID_: Process ID, consisting of "process number: Process version number: Self-growth id"

2. Category_: Process Namespace (this number is the attribute value of the process file targetnamespace)

3. Name_: Process name (this is the name attribute value of the process file procedure element)

4. Key_: The process number (which is the id attribute value of the process file's procedure Element)

5. Version_: Process version number (by program control, added is 1, modified and then added to complete)

6. Deployment_id_: Deployment Number

7. Resource_name_: Resource file name

8. Dgrm_resource_name_: Picture resource file name

9. Has_start_from_key_: Do you have START from KEY

Note: This table and Act_re_deployment is a many-to-one relationship, that is, a deployed bar package may contain multiple process definition files, each process definition file will have a record in the Act_reprocdef table, each process-defined data, will be for act_ A resource file and a PNG image file in the Ge_bytearray table. The association with Act_ge_bytearray is through the program with Act_ge_bytearray. NAME and act_re_procdef.name_ do not manifest in the database table structure.

L Act_id_group: Used to store user group information.

1. Id_: User Group name *

2. Rev_int: Version number

3. Name_: User group description Information *

4. Type_: User Group type

L Act_id_membership: Used to save user's group information

1. User_id_: User Name

2. Group_id_: User group name

L Act_id_user:

1. Id_: User Name

2. Rev_int: Version number

3. First_: User Name

4. Last_: User Last Name

5. Email_: Email

6. Pwd_: Password

L Act_ru_execution:

1. Id_:

2. REV_: Version number

3. PROC_INST_ID_: Process Instance number

4. BUSINESS_KEY_: Business Number

5. Parent_id_: Find the parent of the execution instance and eventually find the execution instance of the entire process

6. Proc_def_id_: Process ID

7. Super_exec_: Referenced execution template

8. ACT_ID_: Node ID

9. Is_active_: Whether to access

Is_concurrent_:

One. Is_scope_:

L Act_ru_task: Run-time Task data table.

1. Id_:

2. REV_:

3. Execution_id_: The ID of the execution instance

4. Proc_inst_id_: ID of the process instance

5. Proc_def_id_: ID of the process definition, corresponding to Act_re_procdef id_

6. Name_: Task name, corresponding to ***task

7. PARENT_TASK_ID_: Corresponding parent task

8. Description_:

9. Task_def_key_: ID of ***task

Owner_: Initiator

Assignee_: The person assigned to the task

Delegation_: Principal

Priority_: Degree of urgency

Create_time_: Initiation Time

Due_time_: Length of approval

L Act_ru_identitylink: Task participant data Sheet. Primarily stores information about the current node participants.

1. Id_: Logo

2. REV_: Version

3. Group_id_: Organization ID

4. Type_: Type

5. User_id_: User ID

6. Task_id_: Task ID

L Act_ru_variable: Run-time process variable data table.

1. Id_: Logo

2. REV_: Version number

3. Type_: Data type

4. Name_: Variable name

5. Execution_id_: execution 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, save the data in this column

Long_: Save data to this column if the data type is LONG

Text_: String saved to this column

Text2_:

L 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_: Open Process user ID

9. Start_act_id_: Start node

End_act_id_: End Node

SUPER_PROCESS_INSTANCE_ID_: Parent Process Process ID

Delete_reason_: Removing the reason from the running task table

L Act_hi_actinst:

1. Id_: Logo

2. PROC_DEF_ID_: Process Definition ID

3. PROC_INST_ID_: Process Instance ID

4. Execution_id_: execution Example

5. ACT_ID_: Node ID

6. Act_name_: node name

7. Act_type_: Node type

8. Assignee_: Node task assignment person

9. Start_time_: Start time

End_time_: End Time

DURATION: Elapsed Time

L 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_: execution Instance ID

6. Parent_task_id_: Parent Task ID

7. Name_: Task Name

8. Description_: Description

9. Owner_: Owner (initiator)

Assignee_: The person assigned to the task

Start__time_: Start Task time

End_time_: End Task time

Duration_: Duration

Delete_reason_: Reasons for removing from the run-time task table

Priority_: Degree of urgency

Due_date_:

L Act_hi_detail: Start the process or record the history process variable after the task complete

1. Id_: Logo

2. Type_: Variableupdate and Formproperty two kinds of values

3. PROC_INST_ID_: Corresponding Process instance ID

4. Execution_id_: Corresponding execution instance ID

5. Task_id_: Corresponding task ID

6. ACT_INST_ID: Corresponding node ID

7. Name_: The history process variable name, or the name of the form property

8. Var_type_: Defining types

9. REV_: Version

Time_: Import Time

Bytearray_id_.

Double_: If the defined variable or form attribute is of type DOUBLE, his value exists here

Long_: If the defined variable or form attribute is of type LONG, his value exists here

Text_: If the defined variable or form property is of type string, the value exists here

Text2_:

L act_hi_comment Comment Form

1. Id_: Logo

2. Type_: Opinion record type is comment when processing comments

3. Time_: Recording Time

4. User_id_:

5. Task_id_: ID of the corresponding task

6. Proc_inst_id_: ID of the corresponding process instance

7. Action_: For AddComment when handling opinions

8. Message_: Handling Opinions

9. Full_msg_:

Conclusion and summary of Beijing-margin Network

L process file deployment mainly involves 3 tables, namely: Act_ge_bytearray, Act_re_deployment, Act_re_procdef. The main completion of the "deployment package"--"Process definition file"-"All in-Package files" resolution deployment relationship. As can be seen from the table structure, the elements of the process definition need to be loaded and parsed every time from the database, because the elements of the process definition are not translated into a database table to complete, of course, the process element is placed in the cache after parsing, the specific needs to be studied in detail later.

The Java class file in the process definition does not exist in the database.

The management of the organization is relatively weak, if it is to be included in the single sign-on system also needs to be completed, the concrete transformation method needs to be researched.

The relationship between the execution of the run-time object and the database record needs to be studied

The preservation and role of historical data need to be studied.

Activiti uses MYBATIS3 to do persistent work, you can set up the table when the process engine starts in the configuration.

The tables used by Activiti are act_ beginning with.

act_re_*: Process definition storage.

Act_ru_*: A process execution record that records all actions initiated to the end of the process and clears the relevant records when the process is finished.

act_id_*: User records, users and groups used in the process.

Act_hi_*: History of Process execution.

Act_ge_*: General data and settings.

Table to use:

Act_ge_bytearray: Data for process deployment.

Act_ge_property: General settings.

Act_hi_actinst: An instance of a process activity.

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: User.

Act_re_deployment: Deployment record.

ACT_RE_PROCDEF: Process definition.

Act_ru_execution: Process execution record.

Act_ru_identitylink:

Act_ru_job:

Act_ru_task: The task record executed.

Act_ru_variable: The variable record in execution.

Activiti-administrator

Self-contained user management system, maintenance users and groups, need to configure data connection parameters, in Activiti-administrator\web-inf\applicationcontext.xml, and join the JDBC driver package.

Activiti-cycle

PVM activity is detected by activiti-rest and is not required for configuration.

Activiti-explorer

You can view user tasks and start-up processes, which are serviced by activiti-rest and do not need to be configured.

Activiti-kickstart

Simple point-to-point process definition Maintenance tool, need to configure data connection, put Activiti.cfg.xml file under classes, and add driver package.

Activiti-modeler

Online editing and maintenance of process-defined tools and, finally, folder-based deployment, you need to configure the Activiti-modeler\web-inf\classes\configuration.properties file.

Activiti-probe

PVM's observation service, provided by Activiti-rest, does not need to be configured to view deployment, ProcessDefinition, ProcessInstance, database.

Activiti-rest

The service providers of several other applications need to configure the data connection, put the Activiti.cfg.xml file under classes, and add the driver package.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced. Do not allow copy, to pursue legal responsibility, welcome to join our Learning Promotion Group 466355109, can communicate with each other

Activiti Workflow Engine database table structure