CN113535684B - Autonomous command control method based on Activiti - Google Patents
Autonomous command control method based on Activiti Download PDFInfo
- Publication number
- CN113535684B CN113535684B CN202110841561.4A CN202110841561A CN113535684B CN 113535684 B CN113535684 B CN 113535684B CN 202110841561 A CN202110841561 A CN 202110841561A CN 113535684 B CN113535684 B CN 113535684B
- Authority
- CN
- China
- Prior art keywords
- task
- commit
- node
- partial
- status
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 230000000694 effects Effects 0.000 title claims abstract description 32
- 230000008569 process Effects 0.000 claims abstract description 30
- 230000007246 mechanism Effects 0.000 claims abstract description 17
- 230000006870 function Effects 0.000 claims description 16
- 230000009471 action Effects 0.000 claims description 4
- RWSOTUBLDIXVET-UHFFFAOYSA-N Dihydrogen sulfide Chemical compound S RWSOTUBLDIXVET-UHFFFAOYSA-N 0.000 claims description 2
- 238000013461 design Methods 0.000 claims description 2
- 230000002708 enhancing effect Effects 0.000 abstract description 3
- 238000007711 solidification Methods 0.000 abstract description 3
- 230000008023 solidification Effects 0.000 abstract description 3
- 101150039208 KCNK3 gene Proteins 0.000 description 11
- 101150083764 KCNK9 gene Proteins 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 241001409866 Actitis Species 0.000 description 4
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to an autonomous command control method based on Activiti, belonging to the field of workflow control. The invention adds part of submitting function to the task node of the Activiti workflow to realize multi-node concurrent execution and dynamically control the multi-node concurrent execution, and a process rollback mechanism is added to allow the free rollback of the task node in the process. The invention continuously monitors the state of the task node by adding the function of allowing partial submission to the task node so as to realize dynamic control of the flow, shortens the execution time of the flow while enhancing the parallelism of the task node of the flow, increases the rollback mechanism, improves the fault tolerance of the flow, and solves the problems of solidification of the active node and incapability of arbitrarily rollback among the nodes encountered in the active workflow.
Description
Technical Field
The invention belongs to the field of workflow control, and particularly relates to an autonomous command control method based on Activiti.
Background
Today, with the continued depth of informatization, a large number of files, models, and data need to be circulated in the system, for which an efficient, robust workflow engine is critical. The active is used as an open source workflow platform, the core of which is an ultra-fast and ultra-stable BPMN2.0 flow engine based on Java, and the active is applicable to an extensible cloud architecture, and has strong usability and good integration capability, so that the active becomes one of the most widely applied workflow systems in the market at present.
The actiti workflow engine has great limitation on application in the field of command control due to static state and relative solidification of task nodes in a flow, once a flow instance is generated, the application cannot be modified, so that various emergency conditions in a command control scene cannot be timely and effectively responded, dynamic description of the flow is insufficient, requirements of real-time response and on-machine adjustment of the flow by command control are not supported, fault tolerance is poor, and a good rollback mechanism is lacked, so that the system cannot be matched with requirements of a command control system.
Disclosure of Invention
First, the technical problem to be solved
The invention aims to solve the technical problem of how to provide an autonomous command control method based on Activiti so as to solve the problems that active nodes in an Activiti workflow are solidified and the nodes cannot be retracted randomly.
(II) technical scheme
In order to solve the technical problems, the invention provides an autonomous command control method based on active, which adds a part of submitting functions to task nodes of an active workflow to realize multi-node concurrent execution and dynamically control the multi-node concurrent execution, and adds a flow rollback mechanism to allow free rollback of the task nodes in the flow.
Further, the adding part of the commit function to the task node of the active workflow realizes the concurrent execution of multiple nodes and dynamically controls the multiple nodes, which specifically comprises the following steps:
step one: in the process of service design, expanding part of submitted attributes of task nodes;
step two: newly adding a database table structure in the active flow;
step three: and establishing the association between the newly added table and the Activiti.
Further, the partial submission attribute in the first step includes the following: after the first partial submission, the subsequent node of the node can be activated to sign and transact the task; the task node can carry out multiple partial submissions, and the last partial submission content in time is taken as the reference; after the node task is completely submitted, the node task executor can not check and modify the node task; the method comprises the steps of manually defining the STATE of a task node in a flow instance, recording the STATE of an active STATE in execution as 1, recording the STATE of an active node which is completely submitted as 2, and recording the task in a partially submitted STATE, wherein the task still belongs to the STATE in execution, and when the task node is completely submitted, the task enters the STATE in which execution is completed.
Further, the step two specifically includes: a partial COMMIT LOG table (part_commit_log) and a partial COMMIT STATUS table (part_commit_status) are added to the activity to record the COMMIT history of the current task and the COMMIT STATUS of the current task in the flow instance, respectively.
Further, in the partial COMMIT LOG table (part_commit_log), a setting field CREATETIME is used to record the time of task creation, update is used to record the update time of the partial COMMIT, execute_id is used to record the instance ID being executed, act_id is used to record the current task ID in the flowchart, COMMIT is used to record the number of partial COMMIT times of the current task, COMMIT is used to record the current task COMMIT content, and isopart_action is used to record whether the current task node is a permitted partial COMMIT.
Further, setting a field STATE in the partial COMMIT STATUS table (part_commit_status) and the partial COMMIT LOG table (part_commit_log) to record the execution STATUS of the current node, null indicates that the current node is not started, 1 indicates that the current node is executing, and 2 indicates that the current node is executing.
Further, the third step specifically includes: the method comprises the steps that through the fact that a field TASK_ID is associated with a main key TASK_ID in an active original table ACT_RU_TASK, the EXECUTION_ID is associated with a main key EXECUTION_ID of the active original table ACT_RU_EXECUTION, and accordingly association relations between a newly added partial COMMIT LOG table (part_COMMIT_LOG) and a partial COMMIT STATUS table (part_COMMIT_STATUS) and the original table are established, and therefore the newly added table can conveniently acquire relevant data in an active workflow engine.
Further, the adding a rollback mechanism for the process allows the free rollback of the task node in the process specifically includes: setting a task attribute field STATE through a newly added partial COMMIT STATUS table (PART_COMMIT_STATUS), and expanding the command method of the Activiti to realize rollback among task nodes.
Further, the setting the task attribute field STATE through the newly added partial COMMIT STATUS table (part_commit_status) specifically includes: when the task needs to be rolled back to the task X, the task state STATUS of the currently executed task is set from 1 to 2, and the task state STATUS of the task X is set from 2 to 1.
Further, the method for realizing rollback between task nodes by expanding the command of the Activiti specifically comprises the following steps: first, the current activity ID (activityId) of the flow, the flow instance ID (processInstanceId), and the jump start point are acquired; the trend of the next step of the flow instance is obtained through the 'jump' operation customized by the active workflow, and then the rollback operation is executed through the execution method in the command provided by the active.
(III) beneficial effects
The invention provides an autonomous command control method based on an Activiti, which adds a part of submitting functions to task nodes of an Activiti workflow to realize multi-node concurrent execution and dynamically control the task nodes, and adds a flow rollback mechanism to allow free rollback of the task nodes in the flow. The invention continuously monitors the state of the task node by adding the function of allowing partial submission to the task node so as to realize dynamic control of the flow, shortens the execution time of the flow while enhancing the parallelism of the task node of the flow, increases the rollback mechanism, improves the fault tolerance of the flow, and solves the problems of solidification of the active node and incapability of arbitrarily rollback among the nodes encountered in the active workflow.
Drawings
FIG. 1 is a simple flow chart;
FIG. 2 is a diagram illustrating the state of an active node in a flow example;
FIG. 3 is a diagram of the active node state after adding a permission portion commit function;
FIG. 4 is a state of an active node after setting an "allow partial commit" attribute for the active node;
FIG. 5 is a rollback flowchart of a prior art Activiti workflow Engine;
FIG. 6 illustrates the state of an active node prior to rollback in accordance with the present invention;
fig. 7 is a diagram illustrating the status of the active node after the backoff of the present invention.
Detailed Description
To make the objects, contents and advantages of the present invention more apparent, the following detailed description of the present invention will be given with reference to the accompanying drawings and examples.
The patent aims to provide an autonomous command control method based on Activiti, which continuously monitors the state of task nodes to realize dynamic control of a flow by adding a function allowing partial submission to the task nodes, shortens the execution time of the flow while enhancing the parallelism of the task nodes of the flow, increases a rollback mechanism, improves the fault tolerance of the flow, and solves the problems that the active nodes in an Activiti workflow are solidified and the nodes cannot rollback at will.
In order to solve the ending problem, the patent discloses an autonomous command control method based on the Activit, which can dynamically control task nodes and realize an autonomous command control method of a rollback mechanism through service calling and interface transformation of an Activit workflow engine. The invention mainly comprises two aspects: the task node adding part of the Activiti workflow is submitted to realize multi-node concurrent execution and dynamic control of the multi-node concurrent execution, and a process rollback mechanism is added to allow free rollback of the task node in the process.
Content one: adding partial commit function of task nodes in flow
The core of the actiti workflow engine is BPMN2.0 modeling language, in the description of the business flow, all task nodes of the flow chart are relatively solidified, once a flow instance is generated, automatic jump of an active node is started according to the flow instance, and for the active node in the flow chart, once the operation content of the active node is submitted, the activity cannot be checked and secondarily modified, so that the flexibility and instantaneity of the flow are poor, and the requirement of command and control scenes cannot be met.
The patent provides a dynamic processing mechanism for active nodes in a flow, so that the dynamic processing mechanism meets the requirements of the command control field. And adding a partial submission function to the active node in the flow, and allowing the active node to perform multiple partial submissions on the task content of the current active node until the task content is completely submitted finally. The partial submission allows the executor of the active node to make an adjustment to the task content submitted by the node according to the real-time message and then submit again, so that the executor can respond to the received real-time message in a short time.
Step one: extending partially submitted attributes of task nodes during a business design process
Taking a simple flowchart as an example in fig. 1, a corresponding explanation is made for a partial commit function. The existing active node state in the flow example is shown in fig. 2.
Taking Task1 as an example, before the process flow goes to the active node, the state of the node is in a ready state, i.e. the node is not started, after the active node signs in, the executing state is carried out, the submitting is that the current node is executed, the current Task node in the process instance fails after the submitting, the Task cannot be checked and modified by an executor of the Task, and the next node Task2 starts to sign in and execute.
The active node state after adding the allowed partial commit function is shown in figure 3.
For ease of distinction, the last commit is defined as a complete commit, taking Task1 as an example, the Task node is in a ready state, i.e., not started, before signing. After signing a Task node, entering an execution state, and after partial submission, activating the next node Task2 to start signing and executing, and meanwhile, the node Task1 can also carry out the submitted job content before partial submission coverage for a plurality of times until the Task node is completely submitted, wherein the Task node represents that the Task1 is completely executed, and enters a failure state, so that an executor of the Task1 can not check and modify the flow instance any more.
The partial commit attribute includes the following:
1. after the first partial submission, the subsequent node of the node can be activated to perform task signing and handling;
2. the task node can perform multiple partial submissions, and the content of the last partial submission in time is determined, for example, the data y submitted by task1 in the process is the partial submission, namely y (2) Cover y (1) And so on;
3. after the complete submission, the node task executor can no longer view and modify the node task executor.
4. To facilitate the recording of the extended attributes of the active node, the task node STATE in the flow instance is artificially defined, the active STATE under execution is recorded as 1, and the active node that has been fully committed is recorded as 2. And the task in the partial submitting state still belongs to the executing state, and after the task node completely submits, the task enters the executing state.
TABLE 1 Attribute notation
Functional comparison before and after expansion
Table 2 node function lookup table before and after expansion
Step two: database table structure in newly added flow
After the attribute expansion of each task node in the process is completed, in order to call the expansion attribute STATE and realize the coupling of the expansion attribute STATE and the process logic, the semi-concurrent execution of a plurality of nodes is realized, so that the partial submission function of the process node is realized, and the existing database table structure of the Activiti needs to be expanded.
The partial COMMIT function involves two original database tables (ACT_RU_EXECUTION and ACT_RU_TASK) of the action, and a partial COMMIT LOG table (part_COMMIT_LOG) and a partial COMMIT STATUS table (part_COMMIT_STATUS) are added on the basis of the existing tables and are used for recording the COMMIT history of the current TASK and the COMMIT STATUS of the current TASK in the flow instance respectively.
In the partial COMMIT LOG table (part_commit_log), a setting field CREATETIME is used to record the time of task creation, update is used to record the update time of the partial COMMIT, execution_id is used to record the instance ID being executed, act_id is used to record the current task ID in the flowchart, COMMIT is used to record the number of partial COMMIT of the current task, COMMIT is used to record the current task COMMIT content, and isopart_action is used to record whether the current task node is a permitted partial COMMIT. The submitting record of the current task ACT_ID can be seen through key fields in the table, and the task update time and the corresponding submitting content COMMITCONTENT are updated each time, so that the record of the task node submitting history in the process instance is realized.
Table 3 field association table
Setting a field STATE in a partial COMMIT STATUS table (part_commit_status) and a partial COMMIT LOG table (part_commit_log) to record the execution STATUS of the current node, null indicates that the current node is not started, 1 indicates that the current node is executing, and 2 indicates that the current node is executing.
Step three: establishing association between the newly added table and the Activiti
The method comprises the steps that through the fact that a field TASK_ID is associated with a main key TASK_ID in an active original table ACT_RU_TASK, the EXECUTION_ID is associated with a main key EXECUTION_ID of the active original table ACT_RU_EXECUTION, and accordingly association relations between a newly added partial COMMIT LOG table (part_COMMIT_LOG) and a partial COMMIT STATUS table (part_COMMIT_STATUS) and the original table are established, and therefore the newly added table can conveniently acquire relevant data in an active workflow engine. When the flow instance operates, whether the current node is in partial submission is judged by acquiring a partial submission state ISPART_ACTIVIT field value of the flow node, and the front page acquires data by calling a corresponding interface so as to display the data, so that parallel execution of a plurality of serial nodes is realized.
When the flow chart is created, by setting an allowed partial submission attribute on the active node, a task executor of the active node can partially submit task contents in the circulation process of the flow example generated by deployment, and after the task executor of the active node submits the task contents, a subsequent active node is activated, and the node can still continue task handling and content submission. Taking the above flow as an example, after the Task1 is completely submitted, the flow goes to the next Task2, after the Task2 is partially submitted, the next Task3 is activated, and the executor can process the Task3 to submit the Task content, while at the same time, the Task2 can still continue to process and submit the Task until the Task is completely submitted. A schematic diagram thereof is shown in fig. 4.
Content II: rollback mechanism for adding task nodes in flow
The active workflow engine has no rollback function for task nodes, so that the fault tolerance of the active workflow engine is poor, and the active workflow engine lacks good adaptability and flexibility and cannot cope with emergency conditions in command and control scenes.
In the existing active workflow engine, if a task needs to be rolled back, a corresponding flow branch must be added when a task flow is defined, taking the task3 rolled back to the task1 as an example, in order to realize arbitrary rollback between nodes, a control flow of a front task node needs to be added to the task3, and the change flow chart is shown in fig. 5 by a dotted line.
When rollback among a plurality of nodes exists in the flow, a loop is needed to exist between the current node and any front node, and the loop is obviously unrealistic in a workflow diagram with complex business logic, the workflow loop is not supported by the action, the realization is difficult, the BPMN visualization flow diagram becomes disordered, and the solidified flow jump mode is not suitable for a complicated and changeable command and control scene. Therefore, the patent improves the control method suitable for autonomous command control.
According to the method, the task attribute field STATE is set through the newly-added PART COMMIT STATUS table (PART_COMMIT_STATUS) under the condition that a flow chart is not changed through interface call of an active workflow engine and the new addition of a self-created data table, and the command method of the active is expanded to realize rollback among task nodes.
Taking the above process as an example, when the process instance is rolled back from the node Task3 to the Task1, the relevant states before and after rollback of each node are as follows:
before rollback:
task1, state=2, and execution is completed;
task2, state=2, finish execution;
task3, state=1, executing;
act_id=task 3; (indicating that the Task is currently being executed is Task 3)
The current executing node act_id is Task3, and its STATE is 1, which indicates that Task3 is executing in the process instance, and Task1 and Task2 are all submitted completely, and its STATE is 2, which indicates that execution is completed. An example of the flow is shown in fig. 6.
After the back-off:
the STATE values of the nodes in the flow are adjusted as follows:
task1: state=1; is executing;
task2, state=2; after execution is completed
Task3, state=2; after execution is completed
Act_id=task 1; (indicating that the Task is currently being executed is Task 1)
An example of the flow is shown in fig. 7.
When the task needs to be rolled back to task x, the task state STATUS of the currently executing task is set from 1 to 2, the task state STATUS of task x is set from 2 to 1, and act_id=is set to task x. When Task3 needs to fall back to Task1, in order to achieve node fall back, a new execution process needs to be generated in the process instance, and at this time, task STATE of Task3 is adjusted from 1 to 2, and at the same time, task STATE of Task1 is adjusted from 2 to 1. Under the process instance EXECUTION_ID, a new EXECUTION process set according to a process template from Task node Task1 is realized by using a Command provided by Activiti. By the method, any rollback of the task nodes in the flow is realized, so that a rollback mechanism of the task nodes in the flow is increased.
The Command is used for updating corresponding data after the return, and in order to avoid unsafe caused by direct operation of a database, the patent realizes an org.actiti.engine.image.interface.command interface for realizing a node return mechanism by carrying out self-defined improvement on a Command method provided by an actiti workflow engine.
The Command method implements the relevant jumps of the active nodes in the flow after rollback by defining the object JumpActive Cmd. The current activity ID (activityId) of the flow, the flow instance ID (processInstanceId), and the jump start point are first obtained. The trend of the next step of the flow instance is obtained through the 'jump' operation customized by the active workflow, and then the rollback operation is executed through the execution method in the command provided by the active.
The specific contents are as follows:
core code fragments:
the foregoing is merely a preferred embodiment of the present invention, and it should be noted that modifications and variations could be made by those skilled in the art without departing from the technical principles of the present invention, and such modifications and variations should also be regarded as being within the scope of the invention.
Claims (3)
1. An autonomous command control method based on an action is characterized in that a part of submitting functions are added to task nodes of the action workflow to realize multi-node concurrent execution and perform dynamic control on the multi-node concurrent execution, and a process rollback mechanism is added to allow free rollback of the task nodes in the process;
wherein,
the task node adding part submitting function of the Activiti workflow realizes multi-node concurrent execution and dynamically controls the multi-node concurrent execution, and specifically comprises the following steps:
step one: in the process of service design, expanding part of submitted attributes of task nodes;
step two: newly adding a database table structure in the active flow;
step three: establishing the association between the new table and the Activiti;
the partial submission attribute in the first step includes the following contents: after the first partial submission, the subsequent node of the node can be activated to sign and transact the task; the task node can carry out multiple partial submissions, and the last partial submission content in time is taken as the reference; after the node task is completely submitted, the node task executor can not check and modify the node task; the method comprises the steps of manually defining the STATEs of task nodes in a flow instance, recording the STATE of activity in execution as 1, recording the completely submitted active nodes as 2, and recording the tasks in a partially submitted STATE as well as belonging to the executing STATE, wherein when the task nodes are completely submitted, the tasks enter the executing STATE;
the second step specifically comprises the following steps: a partial COMMIT LOG table (part_commit_log) and a partial COMMIT STATUS table (part_commit_status) are added in the activity and are used for recording the COMMIT history of the current task and the COMMIT STATUS of the current task in the flow instance respectively;
in the partial COMMIT LOG table (part_commit_log), a setting field CREATETIME is used for recording the time of task creation, update is used for recording the update time of partial COMMIT, execution_id is used for recording the instance ID being executed, act_id is used for recording the current task ID in the flowchart, COMMIT is used for recording the partial COMMIT times of the current task, COMMIT is used for recording the current task COMMIT content, and isopart_action is used for recording whether the current task node is a permitted partial COMMIT;
setting a field STATE in the partial COMMIT STATUS table (part_commit_status) and the partial COMMIT LOG table (part_commit_log) to record the execution STATUS of the current node, wherein null indicates that the current node is not started, 1 indicates that the current node is executing, and 2 indicates that the current node is executing;
the third step specifically comprises the following steps: the method comprises the steps that through the fact that a field TASK_ID is associated with a main key TASK_ID in an active original table ACT_RU_TASK, the EXECUTION_ID is associated with a main key EXECUTION_ID of the active original table ACT_RU_EXECUTION, and accordingly association relations between a newly added partial COMMIT LOG table (part_COMMIT_LOG) and a partial COMMIT STATUS table (part_COMMIT_STATUS) and the original table are established, and therefore the newly added table can conveniently acquire relevant data in an active workflow engine;
the adding a process rollback mechanism allows the free rollback of task nodes in the process specifically comprises: setting a task attribute field STATE through a newly added partial COMMIT STATUS table (PART_COMMIT_STATUS), and expanding the command method of the Activiti to realize rollback among task nodes.
2. The autonomous command control method based on Activiti of claim 1, wherein said setting task attribute field STATE by means of a newly added partial COMMIT STATUS table (part_commit_state) specifically comprises: when the task needs to be rolled back to the task X, the task state STATUS of the currently executed task is set from 1 to 2, and the task state STATUS of the task X is set from 2 to 1.
3. The autonomous command control method based on Activiti according to claim 2, wherein the command method for expanding Activiti specifically comprises: first, the current activity ID (activityId) of the flow, the flow instance ID (processInstanceId), and the jump start point are acquired; the trend of the next step of the flow instance is obtained through the 'jump' operation customized by the active workflow, and then the rollback operation is executed through the execution method in the command provided by the active.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110841561.4A CN113535684B (en) | 2021-07-26 | 2021-07-26 | Autonomous command control method based on Activiti |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110841561.4A CN113535684B (en) | 2021-07-26 | 2021-07-26 | Autonomous command control method based on Activiti |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535684A CN113535684A (en) | 2021-10-22 |
| CN113535684B true CN113535684B (en) | 2024-02-27 |
Family
ID=78120703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110841561.4A Active CN113535684B (en) | 2021-07-26 | 2021-07-26 | Autonomous command control method based on Activiti |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535684B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114971566A (en) * | 2022-05-31 | 2022-08-30 | 浙江省标准化研究院(金砖国家标准化(浙江)研究中心、浙江省物品编码中心) | Activiti-based predefined process dynamic approval method, system and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302581A (en) * | 2015-12-02 | 2016-02-03 | 南京莱斯信息技术股份有限公司 | Workflow event mechanism implementation method based on script engine |
| CN105912384A (en) * | 2016-04-01 | 2016-08-31 | 广东凯通软件开发有限公司 | Transaction processing method and device for workflow engine |
| CN106971293A (en) * | 2017-03-23 | 2017-07-21 | 广东亿迅科技有限公司 | A kind of business event based on activiti and flow separation method and system |
| CN109542556A (en) * | 2018-10-30 | 2019-03-29 | 珠海伟诚科技股份有限公司 | A kind of process based on Activiti and list exchange method and system |
| CN109784859A (en) * | 2019-01-17 | 2019-05-21 | 四川驹马科技有限公司 | A kind of work process flow configuration method without configuring rejection node |
| CN110517018A (en) * | 2019-08-26 | 2019-11-29 | 深圳前海环融联易信息科技服务有限公司 | A kind of any jump method of node based on activiti workflow and device |
| CN110852623A (en) * | 2019-11-12 | 2020-02-28 | 北京计算机技术及应用研究所 | BPMN-based command control process design method |
| CN112114894A (en) * | 2020-08-14 | 2020-12-22 | 咪咕文化科技有限公司 | Process processing method and device based on Activiti process engine and electronic equipment |
| CN112445472A (en) * | 2020-11-26 | 2021-03-05 | 山东健康医疗大数据有限公司 | Workflow module based on Activiti and business interaction method |
-
2021
- 2021-07-26 CN CN202110841561.4A patent/CN113535684B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302581A (en) * | 2015-12-02 | 2016-02-03 | 南京莱斯信息技术股份有限公司 | Workflow event mechanism implementation method based on script engine |
| CN105912384A (en) * | 2016-04-01 | 2016-08-31 | 广东凯通软件开发有限公司 | Transaction processing method and device for workflow engine |
| CN106971293A (en) * | 2017-03-23 | 2017-07-21 | 广东亿迅科技有限公司 | A kind of business event based on activiti and flow separation method and system |
| CN109542556A (en) * | 2018-10-30 | 2019-03-29 | 珠海伟诚科技股份有限公司 | A kind of process based on Activiti and list exchange method and system |
| CN109784859A (en) * | 2019-01-17 | 2019-05-21 | 四川驹马科技有限公司 | A kind of work process flow configuration method without configuring rejection node |
| CN110517018A (en) * | 2019-08-26 | 2019-11-29 | 深圳前海环融联易信息科技服务有限公司 | A kind of any jump method of node based on activiti workflow and device |
| CN110852623A (en) * | 2019-11-12 | 2020-02-28 | 北京计算机技术及应用研究所 | BPMN-based command control process design method |
| CN112114894A (en) * | 2020-08-14 | 2020-12-22 | 咪咕文化科技有限公司 | Process processing method and device based on Activiti process engine and electronic equipment |
| CN112445472A (en) * | 2020-11-26 | 2021-03-05 | 山东健康医疗大数据有限公司 | Workflow module based on Activiti and business interaction method |
Non-Patent Citations (1)
| Title |
|---|
| 面向二次开发工作流引擎的流程定义系统的设计与实现;周海洋;《中国优秀硕士学位论文全文数据库 (信息科技辑)》;第2017年卷(第09期);I138-95 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535684A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109684057B (en) | Task processing method and device and storage medium | |
| US10453010B2 (en) | Computer device, method, and apparatus for scheduling business flow | |
| CN112287007B (en) | Industrial production data real-time processing method and system based on Flink SQL engine | |
| WO2021052502A1 (en) | Configuration change method and related apparatus | |
| CN115629746B (en) | Method and system for multi-person collaborative development of low-code platform | |
| CN113535684B (en) | Autonomous command control method based on Activiti | |
| CN111666088A (en) | Pod replacement method and device, electronic equipment and computer-readable storage medium | |
| US20120316927A1 (en) | Computer-implemented method and apparatus for integrating heterogeneous business processes | |
| CN113094125B (en) | Business process processing method, device, server and storage medium | |
| CN110852623A (en) | BPMN-based command control process design method | |
| CN113919041A (en) | Collaborative design method and electronic equipment | |
| CN116911763A (en) | Flow approval method, device, terminal equipment and storage medium | |
| CN110276152A (en) | A kind of band non-critical time management method of time remaining of parallel discrete time emulation | |
| CN110276153A (en) | The non-uniform non-critical time management method of time remaining of parallel discrete time emulation | |
| CN113448493B (en) | Method, electronic device and computer readable medium for backing up data | |
| JP2846047B2 (en) | Shadow process generation method | |
| CN115630835A (en) | Activity-based workflow general parameter configuration method and system | |
| CN114997805A (en) | Configuration method and device of approval business, electronic equipment and storage medium | |
| CN112418796A (en) | Sub-process node activation method and device, electronic equipment and storage medium | |
| CN114020506A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112486474A (en) | Method for manufacturing visual workflow configuration platform based on mxgraph and activiviti technology | |
| JP2021521570A (en) | Managing shared resources in a distributed computing system | |
| CN113296892B (en) | Dormancy method and device of development environment, electronic equipment and storage medium | |
| CN117808406A (en) | Technical state management method, device, equipment and medium for aircraft system | |
| WO2024114153A1 (en) | Resource configuration method and apparatus based on parasitic program, device, medium, and product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |