Shulou(Shulou.com)06/03 Report--

This article mainly explains the "methods and steps of flowable table carding", the content of the article is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "flowable table carding methods and steps" bar!

The flowable table is sorted out, and the details are as follows:

1. Table carding

(refer to Flowable user manual)

1) General data sheets (2)

Act_ge_bytearray: binary data tables, such as process definitions, process templates, byte flow files for flowcharts

Act_ge_property: attribute data sheet (not commonly used)

2) History tables (8, tables operated by HistoryService interface)

Act_hi_actinst: historical node table, which stores the information of each node running by the process instance (including non-task nodes such as start and end)

Act_hi_attachment: history attachment table, which stores the attachment information uploaded by history nodes (not commonly used)

Act_hi_comment: historical opinion form

Act_hi_detail: historical details table, storing some information about the operation of nodes (not commonly used)

Act_hi_identitylink: historical process personnel table, which stores information about candidates and managers of each node of the process. It is often used to query the completed tasks of a person or department.

Act_hi_procinst: historical process instance table, which stores historical data of process instances (including running process instances)

Act_hi_taskinst: historical process task table, storage historical task node

Act_hi_varinst: process history variable table, which stores the variable information of the process history node

3) user-related tables (4, tables operated by IdentityService interface)

Act_id_group: user group information table, corresponding to the candidate group information selected by the node

Act_id_info: user extension information table, storing user extension information

Act_id_membership: user and user group relationship table

Act_id_user: user information table, corresponding to the information of the manager or candidate selected by the node

4) process definition, process template related tables (3, tables operated by RepositoryService interface)

Act_re_deployment: subordinate information table, storing process definition, template deployment information

Act_re_procdef: the process definition information table stores the description information related to the process definition, but its real content is stored in the act_ge_ bytearray table in bytes

Act_re_model: the process template information table, which stores the description information related to the process template, but its real content is stored in the act_ge_ byte table in bytes.

5) process runtime tables (6, tables operated by RuntimeService interface)

Act_ru_task: runtime process task node table, which stores the task node information of the running process. It is important and is often used when querying people or departments'to-do tasks.

Act_ru_event_subscr: monitoring information table, not commonly used

Act_ru_execution: runtime process execution instance table, recording each branch information of the running process (when there is no sub-process, its data corresponds to the act_ru_ task table data one to one)

Act_ru_identitylink: runtime process personnel table, important, often used when querying people or department to-do tasks

Act_ru_job: runtime timed task data table, which stores timed task information of the process

Act_ru_variable: runtime process variable data table, which stores the variable information of each node of the running process; summary

ACT_RE_*: 'RE' stands for repository. Tables with this prefix contain "static" information, such as process definitions and process resources (pictures, rules, etc.).

ACT_RU_*: 'RU' stands for runtime. These tables store runtime information, such as process instances (process instance), user tasks (user task), variables (variable), jobs (job), and so on. Flowable saves run-time data only when the process instance is running and deletes the record when the process instance ends. This ensures that the runtime table is small and fast.

ACT_HI_*: 'HI' stands for history. These tables store historical data, such as completed process instances, variables, tasks, and so on.

ACT_GE_*: common data. Use in many places

ACT_RE_*: 'RE' stands for repository. Tables with this prefix contain "static" information, such as process definitions and process resources (pictures, rules, etc.).

ACT_RU_*: 'RU' stands for runtime. These tables store runtime information, such as process instances (process instance), user tasks (user task), variables (variable), jobs (job), and so on. Flowable saves run-time data only when the process instance is running and deletes the record when the process instance ends. This ensures that the runtime table is small and fast.

ACT_HI_*: 'HI' stands for history. These tables store historical data, such as completed process instances, variables, tasks, and so on.

ACT_GE_*: common data. Use in many places

two。 Step by step

Process design

-ACT_DE_MODEL saves the json format file of the process design

-ACT_DE_MODEL_HISTORY saves the history file of the process design

Process deployment

-ACT_GE_BYTEARRAY saves the xml file and process picture of the process design (two records)

-ACT_RE_DEPLOYMENT saves process deployment information, name, deployment time, and classification

-ACT_RE_PROCDEF saves process definition information, key, and name (multiple deployment records and process definition records will be generated if the same process file is deployed multiple times. The ID of process definition is composed of key+ version and id)

Starting the process

-ACT_RU_VARIABLE saves the parameter information of the startup process

-ACT_RU_TASK saves task node information, which is used to query to-do tasks.

-ACT_RU_IDENTITYLINK stores the personnel information of the runtime process, which is used to query to-do tasks.

-ACT_RU_EXECUTION records process branch information

-Parameter information of ACT_HI_VARINST process history node

-ACT_HI_TASKINST storage history task node

-ACT_HI_PROCINST stores historical data of process instances

-ACT_HI_IDENTITYLINK stores process history node personnel information, which is used to query completed tasks.

-ACT_HI_ACTINST stores process history node information

3. Process definition

When a process definition is deployed, it distinguishes whether it is the same process according to the key of the process definition, so when the same process definition of key is deployed one after another, a new version of the process definition corresponding to the key will be generated. Key refers to the id attribute in the process definition

Thank you for your reading, the above is the content of "the methods and steps of combing the flowable table". After the study of this article, I believe you have a deeper understanding of the methods and steps of combing the flowable table, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.