Write directory title here
1. flowable official document
Flowable official document: https://flowable.com/open-source/docs/bpmn/ch02-GettingStarted/
Based on 6.5 Chinese translation document: https://l1yp.com/docs/flowable/bpmn/#bpmnGateways
It is recommended to check the official test cases to understand and use flowable: https://github.com/flowable/flowable-engine/tree/982be7e47facf17bb779571ba663bdf8f86947a3/modules/flowable-engine/src/test/java/org/flowable/ engine/test
2. Flowable related table description
Flowable's database names start with ACT_. The second part is the two-character identifier for the table use case.
- ACT_RE_*: "RE" stands for repository. Tables with this prefix contain "static" information such as process definitions and process resources (images, rules, etc.).
- ACT_RU_*: "RU" stands for runtime. These are runtime tables that contain runtime data for process instances, user tasks, variables, jobs, etc. Flowable only stores runtime data during the execution of a process instance and deletes the records when the process instance ends. This keeps the runtime
table small and fast. - ACT_HI_*: "HI" stands for history. These tables contain all historical data in the process, such as past process instances, variables, tasks, etc.
- ACT_GE_ *: General data, including files such as bpmn.xml and flowable's own flow chart, for various use cases.
- flw_*: Tables related to the extended function of the new version of flowable
Flowable related table description
Detailed table description (official): https://documentation.flowable.com/latest/develop/dbs/repository/Detailed
table description (CSDN): https://blog.csdn.net/qq_42277412/article/details/121830797
3. Explanation of operating terms
| Process operation | describe |
|---|---|
| approval | The current node processor will review the current process node and enter the next node after completion |
| claim | The current node candidate or the person belonging to the candidate group claims the current node. At this time, the task belongs to the claimant |
| unclaim | The current node processor cancels the task to be processed by himself, so that the task enters the state of pending claim |
| Rejected / Returned | The current node processor rejects/returns the process to the task node that has been processed before and requires reprocessing |
| Turn to do | The current node processor transfers the operation authority to others for processing, and then enters the next node after processing (no longer processing by yourself) |
| commission / delegation | The current node processor entrusts its hosting tasks to other users for processing, returns to the current processor after processing, and enters the next node after the current processor finishes processing |
| Retrieve | The previous node processor operated on the current node, and the current node processor has not processed it. The previous node processor can return it to his own hands and re-operate (retrieve and redo) |
| cc | The current node processor, after the processing is completed, copy the processing result to others |
| Countersignature/Multiple Instances | General countersigning means that in the process management, the initiator can initiate countersigning to multiple people at the same time, and multiple people can process it at the same time. Only when all responsible persons pass the approval, the approval node will pass. (Support one-vote veto/one-vote pass/vote according to the percentage to give the conclusion to pass or fail) |