CN117290018A - Node jump method, device, equipment, storage medium and product of workflow - Google Patents
Node jump method, device, equipment, storage medium and product of workflow Download PDFInfo
- Publication number
- CN117290018A CN117290018A CN202311109705.2A CN202311109705A CN117290018A CN 117290018 A CN117290018 A CN 117290018A CN 202311109705 A CN202311109705 A CN 202311109705A CN 117290018 A CN117290018 A CN 117290018A
- Authority
- CN
- China
- Prior art keywords
- node
- workflow
- task
- jump
- target node
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 230000002159 abnormal effect Effects 0.000 claims abstract description 52
- 230000008569 process Effects 0.000 claims abstract description 29
- 238000004590 computer program Methods 0.000 claims description 13
- 230000008859 change Effects 0.000 claims description 8
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 241001409866 Actitis Species 0.000 description 5
- 238000004891 communication Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a node jump method, a device, equipment, a storage medium and a product of a workflow, which relate to the technical field of flow management, wherein the method comprises the following steps: determining a current node needing to be jumped in the workflow; the original task flow direction of the current node is cleared; creating a new task flow direction of the current node; setting a target node of a new task flow direction and participants of the target node; the current node to target node jump task is performed such that the target node participants handle the target node task. By the method, a task flow branch line does not need to be preset for the low-probability abnormal condition, and only when the abnormal condition occurs, the current node directly jumps to the corresponding target node, so that the process is concise, the flexibility is high, and the abnormal workflow in the actual business scene can be effectively processed.
Description
Technical Field
The present invention relates to the field of flow management technologies, and in particular, to a method, an apparatus, a device, a storage medium, and a product for node skipping of a workflow.
Background
The actiti is a workflow engine, which can extract complex business processes from a business system, define specific processes of the business by using a modeling language, and therefore determine specific workflows of the business, so that the business system can execute according to a predefined process, and efficient business process management is realized.
The normal circulation mode of the actiti workflow is to circulate according to branch lines in a flow chart customized in a demand analysis stage, wherein the flow chart comprises all nodes, participants corresponding to all nodes and conditions of circulation of all branches in the whole business flow. However, abnormal business scenarios often occur, for example, when the branch circulation condition is not satisfied, the flow is easily closed abnormally, and at this time, the flow needs to be restarted. However, part of the business flow is very long, and before the flow is abnormally closed, many nodes pass the approval, and if the flow is restarted, many participants can be caused to repeatedly operate at the respective nodes, so that the timeliness of the approval is reduced.
In order to solve the above problem, when customizing the flow chart in the demand analysis stage, it is necessary to fully consider possible anomalies in the actual business scenario, and design corresponding branches in the flow chart for all possible anomalies, so that when anomalies occur, circulation can be performed according to branch lines of the flow chart, and abnormal closing of the flow is avoided.
However, the abnormal situation in the actual service scene is difficult to predict, and the existing scheme is difficult to effectively process the abnormal workflow in the actual service scene.
Disclosure of Invention
The invention provides a node jump method, device, equipment, storage medium and product of workflow, which are used for solving the defect that the prior art is difficult to effectively process abnormal workflow in actual business scene.
The invention provides a node jump method of a workflow, which comprises the following steps: determining a current node needing to be jumped in the workflow; the original task flow direction of the current node is cleared; creating a new task flow direction of the current node; setting a target node of a new task flow direction and participants of the target node; the current node to target node jump task is performed such that the target node participants handle the target node task.
According to the node jump method of the workflow provided by the invention, after executing the jump task from the current node to the target node, the method further comprises the following steps: deleting the new task flow direction of the target node; and restoring the original task flow direction of the target node.
According to the node jump method of the workflow provided by the invention, after the original task flow direction of the target node is restored, the method further comprises the following steps: if the original task flow direction of the target node has a countersign task, monitoring the approval result of each participant in the countersign task; the countersign task is a task jointly approved by a plurality of participants; if the approval result of any participant is monitored to be refused, the refusing operation is executed for the countersignature task.
According to the node jump method of the workflow, if the countersign task exists in the original task flow direction of the target node and the participant of the countersign task is changed, the information of the changed participant is determined; based on the changed participant information, performing a change operation on the participant of the countersign task; wherein the altering operation includes adding a participant, deleting a participant, replacing a participant.
According to the method for node jump of the workflow provided by the invention, before determining the current node needing to jump in the workflow, the method further comprises the following steps: judging whether the workflow is in a finishing state or an abnormal closing state; if the workflow is determined to be in the finished state or the workflow is determined to be in an abnormally closed state, restarting the workflow based on the historical workflow data.
According to the node skipping method of the workflow provided by the invention, the workflow is restarted based on historical workflow data, and the node skipping method comprises the following steps: determining a historical task node ID for the workflow based on the historical workflow data; determining workflow flow information based on the historical task node ID; the to-Do data, the participant data, and the flow engine data of the workflow are restored based on the flow information.
The invention also provides a node jump device of the workflow, which comprises: the node determining module is used for determining the current node needing to be jumped in the workflow; the clearing module is used for clearing the original task flow direction of the current node; the creation module is used for creating a new task flow direction of the current node; the setting module is used for setting a target node of the new task flow direction and participants of the target node; and the execution module is used for executing the jump task from the current node to the target node so as to enable the participant of the target node to process the task of the target node.
The invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing a node jump method of any one of the above workflows when executing the program.
The present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a node jump method of any of the workflows described above.
The invention also provides a computer program product comprising a computer program which when executed by a processor implements a node jump method of any of the workflows described above.
According to the method, the device, the equipment, the storage medium and the product for node jump of the workflow, when the workflow is abnormal and the node needs to jump, the current node needing to jump in the workflow is determined, the original task flow direction of the current node is cleared, the new task flow direction of the current node is created, the target node with the new task flow direction and the participant of the target node are set, the jump task from the current node to the target node is executed, so that the participant of the target node processes the task of the target node, a task flow branch line does not need to be preset for the low-probability abnormal condition, and only when the abnormal condition occurs, the current node directly jumps to the corresponding target node, so that the process is concise, the flexibility is high, and the abnormal workflow in the actual service scene can be effectively processed.
Drawings
In order to more clearly illustrate the invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for node skipping of a workflow provided by the present invention;
FIG. 2 is a schematic diagram of node jumps of an Activiti workflow provided by the present invention;
FIG. 3 is a schematic diagram of a node jump device of a workflow provided by the present invention;
fig. 4 is a schematic structural diagram of an embodiment of the electronic device of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, fig. 1 is a flow chart of a node jump method of a workflow provided by the present invention, in this embodiment, the node jump method of the workflow includes steps S110 to S150, and the steps are as follows:
s110: and determining the current node needing to jump in the workflow.
In this embodiment, the workflow is defined based on workflow engine Activiti.
Specifically, based on the workflow engine activity, a business process is extracted from the business system, and a modeling language is used to define a specific process of the business, so as to determine a specific workflow of the business.
In general, the normal circulation mode of the Activiti workflow is circulation according to the customized branch line in the flowchart. The flow chart comprises all nodes in the whole business flow, participants corresponding to all nodes and conditions of all branch circulation.
It can be appreciated that after the flow chart is customized, a test flow branch can be established in the flow chart to detect whether the node in the flow chart can perform normal jump according to the preset branch circulation condition, so as to ensure that the workflow created based on the workflow engine activity can normally run.
Nodes in an actiti workflow are key elements in a flow definition and are used for representing different tasks in the flow, and participants corresponding to the nodes are actual personnel, roles or organizations for executing and approving the tasks.
It can be understood that in the Activiti workflow, different nodes need different participants to execute corresponding tasks, determine approval results, and perform branch circulation according to the approval results corresponding to the nodes, i.e. for each node, it is required to determine and jump to the next node according to the approval results corresponding to the node.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating node jump of an active workflow according to the present invention.
As shown in fig. 2, a node may have multiple branches of the flow, and the conditions of each branch flow may be set according to the service.
Specifically, after the service flow is started, that is, after the service is started, the corresponding participant of the node 1 executes a corresponding task, and determines an approval result, and according to different approval results, the next node determined and jumped to by the node 1 is different, for example, according to different approval results, the next node determined and jumped to by the node 1 may be the node 2 or the node 5.
However, in an actual scenario, an abnormal situation cannot be avoided, for example, an abnormal node occurs between the node 2 and the node 3, which may be caused by an error in the approval result or an abnormal change of a participant corresponding to the node.
When the nodes in the workflow are abnormal, the flow is abnormally closed, and the workflow is in a finished state or an abnormally closed state, and the workflow needs to be restarted.
Specifically, a current node in the workflow that needs to be jumped is determined so that the workflow can be restarted based on the current node.
In general, an abnormal node or a node preceding the abnormal node in the workflow may be selected as a current node in the workflow that needs to be jumped.
As shown in fig. 2, an abnormal node occurs between the node 2 and the node 3, and at this time, if the workflow is to be restarted, the abnormal node, or a node previous to the abnormal node, that is, the node 2, may be used as a current node in the workflow, where a jump needs to be performed, and the workflow may be restarted based on the current node.
S120: and clearing the original task flow direction of the current node.
Specifically, the original task flow between the current node and other nodes is emptied to redefine or create a new task flow for the current node.
S130: a new task flow direction for the current node is created.
Specifically, a new task flow direction is created for the current node to direct the task flow direction to the target node.
S140: the target node and the participants of the target node to which the new task flows are set.
Specifically, the target node and the participants of the target node for the new task flow direction are set, and the new task flow direction is ensured to point to the target node, so that the current node can jump to the target node correctly.
As shown in fig. 2, when an abnormal node occurs between the node 2 and the node 3, the abnormal node is used as a current node needing to be skipped in the workflow when the workflow is restarted.
Further, the original task flow direction between the current node, namely the abnormal node, and other nodes is emptied, a new task flow direction is created for the current node, and a target node of the new task flow direction and participants of the target node are set.
For example, the target node of the new task flow direction of the abnormal node in fig. 2 may be node 4.
S150: the current node to target node jump task is performed such that the target node participants handle the target node task.
As shown in fig. 2, if the target node of the new task flow direction of the abnormal node in fig. 2 is node 4, the jump task from the abnormal node to node 4 is performed, so that the participant of node 4 processes the task of node 4. The node 4 is not an abnormal node, and when the participant of the node 4 executes the corresponding task of the node 4 and determines the approval result, normal branch circulation can be carried out according to the approval result, so that the normal business flow is recovered.
It can be understood that, after the current node jumps to the target node, in order to avoid the subsequent node from jumping to the abnormal node again, the cause of the abnormality of the abnormal node should be determined in time, and the abnormal node should be repaired.
According to the node jump method of the workflow, when the work flow is abnormal and the node needs to jump, the current node needing to jump in the workflow is determined, the original task flow direction of the current node is cleared, the new task flow direction of the current node is created, the target node with the new task flow direction and the participants of the target node are set, the jump task from the current node to the target node is executed, so that the participants of the target node process the task of the target node, task flow branch lines do not need to be formulated in advance for the low-probability abnormal condition, only the current node needs to jump to the corresponding target node directly when the abnormal condition occurs, the process is simple, the flexibility is high, and the abnormal workflow in the actual service scene can be effectively processed.
In some embodiments, after performing the current node to target node jump task, further comprising: deleting the new task flow direction of the target node; and restoring the original task flow direction of the target node.
It will be appreciated that the current node to target node jump is to cope with occasional anomalies, and such jump may not be a normal business process.
Therefore, in order to ensure consistency of the business process, a new task flow direction between the current node and the target node can be deleted, and the original task flow direction of the target node can be restored, so that the workflow state is consistent with that before the jump.
For example, if the target node of the new task flow direction of the abnormal node in fig. 2 is node 5, the jump task from the abnormal node to node 5 is executed, but in the normal business process, the abnormal node should jump to node 3 or node 4 according to the approval result, the abnormal node should not jump to node 5, i.e. the jump from the abnormal node to node 5 is not the normal business process. Therefore, to ensure consistency of the business process, the new task flow direction between the abnormal node and the node 5 can be deleted, and the original task flow direction of the node 5 is restored.
According to the node jump method of the workflow, after the jump task from the current node to the target node is executed, the new task flow direction of the target node is deleted, the original task flow direction of the target node is restored, and the consistency of the business flow can be ensured.
In some embodiments, after restoring the original task flow direction of the target node, the method further includes: if the original task flow direction of the target node has a countersign task, monitoring the approval result of each participant in the countersign task; if the approval result of any participant is monitored to be refused, the refusing operation is executed for the countersignature task.
A countersign task is a task that is jointly approved by several participants.
Generally, in a countersign task, the approval results include "pass" and "reject", and only when the approval results of all participants are passed, the node will jump to the next node, otherwise, the reject operation is executed for the countersign task, and the previous node is returned.
Specifically, if a countersign task exists in the original task flow direction of the target node, monitoring approval results of each participant in the countersign task based on the workflow engine actiti, and if only the approval results of any participant are monitored to be refused, marking the task of the node as refused by the workflow engine actiti, and executing refusing operation on the countersign task without approval of other participants.
For example, assume that the task of the node 6 in fig. 2 is to collect business data of each department, the task of the node 7 is to perform multi-person auditing on the business data collected by the node 6, and the task of the node 7 is a countersignature task because the task of the node 7 is a task commonly approved by a plurality of participants. Only when the approval results of all the participants of the node 7 are passed, the process jumps to the next node, namely the process node is ended, otherwise, the rejection operation is executed on the countersignature task, and the process returns to the node 6.
According to the node jump method of the workflow, if the target node has the countersign task in the original task flow direction, the approval result of each participant in the countersign task is monitored, if the approval result of any participant is monitored to be refused, the refusing operation is executed on the countersign task, so that the workflow engine automatically carries out the refusing operation when the specific condition is met, unnecessary flow waiting is avoided, the approval time cost is reduced, and the flow management efficiency is improved.
In some embodiments, if a countersign task exists in the original task flow direction of the target node and a participant of the countersign task changes, determining information of the participant that changes; and carrying out changing operation on the participants of the countersign task based on the changed participant information.
Wherein the altering operation includes adding a participant, deleting a participant, replacing a participant.
The countersign task is a task which is jointly approved by a plurality of participants, a multi-person auditing mechanism can ensure the safety of service data and the accuracy of approval results, if the participants of the countersign task change, the process can not be continued, and therefore, the change of the participants of the countersign task needs to be monitored and processed in time.
Specifically, if a countersign task exists in the original task flow direction of the target node and a participant of the countersign task changes, for example, the participant of the countersign task needs to be added/deleted/replaced, the information of the changed participant is determined, and the participant of the countersign task is subjected to change operation based on the information of the changed participant through the workflow engine Activiti, so that the occurrence of abnormal nodes is avoided, and smooth performance of the countersign task is ensured.
In some embodiments, before determining the current node in the workflow that needs to be jumped, further comprising: judging whether the workflow is in a finishing state or an abnormal closing state; if the workflow is determined to be in the finished state or the workflow is determined to be in an abnormally closed state, restarting the workflow based on the historical workflow data.
The jump of the workflow node can be used for restarting the abnormal workflow, so that before the current node needing to jump in the workflow is determined, whether the workflow is abnormal or not needs to be judged.
Specifically, whether the workflow is in a finishing state or an abnormal closing state is judged, if the workflow is determined to be in the finishing state or the abnormal closing state is determined, the workflow is determined to be abnormal, and the workflow is restarted based on historical workflow data.
In some embodiments, restarting the workflow based on historical workflow data includes: determining a historical task node ID for the workflow based on the historical workflow data; determining workflow flow information based on the historical task node ID; the to-Do data, the participant data, and the flow engine data of the workflow are restored based on the flow information.
The workflow engine activity may read historical workflow data including information for each node in the historical workflow.
Further, a historical task node ID of the workflow is determined based on the historical workflow data, and flow information of the workflow is determined based on the historical task node ID.
The workflow engine activity may assign a corresponding ID, i.e., a task node ID, to each node to uniquely identify a node, and detailed information of the corresponding node, such as a node task type, belonging process information, a current task state, an associated process definition, and the like, may be obtained based on the task node ID.
The flow information of the workflow may be determined based on the detailed information of each node.
Specifically, the historical task node ID of the workflow is determined based on the historical workflow data, the flow information of the workflow is determined based on the historical task node ID, the to-Do data, the participant data and the flow engine data of the workflow are restored based on the flow information, so that the restoration of the service data is realized, and the workflow is restarted based on the restored service data.
The data to be handled comprises tasks to be handled corresponding to all nodes; the participant data comprises participant information corresponding to each node for executing the task to be handled; the flow engine data includes states, flow labels and the like corresponding to the nodes, and can be used for restarting the workflow.
The present invention also provides a node jump device of a workflow, please refer to fig. 3, fig. 3 is a schematic structural diagram of the node jump device of a workflow provided by the present invention, in this embodiment, the node jump device of a workflow includes a node determining module 310, a clearing module 320, a creating module 330, a setting module 340 and an executing module 350.
The node determining module 310 is configured to determine a current node in the workflow that needs to be skipped.
The clearing module 320 is configured to clear an original task flow direction of the current node.
A creation module 330, configured to create a new task flow direction of the current node.
A setting module 340, configured to set a target node to which the new task flows and a participant of the target node.
An execution module 350 is configured to execute the current node to target node jump task, so that the target node participant processes the target node task.
In some embodiments, the execution module 350 is configured to delete the new task flow direction of the target node; and restoring the original task flow direction of the target node.
In some embodiments, the execution module 350 is configured to monitor an approval result of each participant in the countersignature task if the countersignature task exists in the original task flow direction of the target node; the countersign task is a task jointly approved by a plurality of participants; if the approval result of any participant is monitored to be refused, the refusing operation is executed for the countersignature task.
In some embodiments, the execution module 350 is configured to determine the changed participant information if the countersign task exists in the original task flow direction of the target node and the participant of the countersign task changes; based on the changed participant information, performing a change operation on the participant of the countersign task; wherein the altering operation includes adding a participant, deleting a participant, replacing a participant.
In some embodiments, the node jump device of the workflow further comprises a restart module.
The restarting module is used for judging whether the workflow is in a finishing state or an abnormal closing state; if the workflow is determined to be in the finished state or the workflow is determined to be in an abnormally closed state, restarting the workflow based on the historical workflow data.
In some embodiments, a restart module to determine a historical task node ID for the workflow based on the historical workflow data; determining workflow flow information based on the historical task node ID; the to-Do data, the participant data, and the flow engine data of the workflow are restored based on the flow information.
The invention also provides an electronic device, referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of the electronic device of the invention. In this embodiment, the electronic device may include a processor (processor) 410, a communication interface (Communications Interface) 420, a memory (memory) 430, and a communication bus 440, where the processor 410, the communication interface 420, and the memory 430 communicate with each other through the communication bus 440. Processor 410 may invoke logic instructions in memory 430 to execute a node jump method of a workflow, the method comprising: determining a current node needing to be jumped in the workflow; the original task flow direction of the current node is cleared; creating a new task flow direction of the current node; setting a target node of a new task flow direction and participants of the target node; the current node to target node jump task is performed such that the target node participants handle the target node task.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a node jump method for executing a workflow provided by the methods described above.
The present invention also provides a computer program product comprising a computer program storable on a non-transitory computer readable storage medium, the computer program, when executed by a processor, being capable of executing the node jump method of a workflow provided by the methods described above.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for node skipping of a workflow, comprising:
determining a current node needing to be jumped in the workflow;
the original task flow direction of the current node is cleared;
creating a new task flow direction of the current node;
setting a target node of a new task flow direction and participants of the target node;
and executing the jump task from the current node to the target node so as to enable the participant of the target node to process the task of the target node.
2. The method of node jump of workflow of claim 1, wherein after said performing the jump task of the current node to the target node, further comprising:
deleting the new task flow direction of the target node;
and restoring the original task flow direction of the target node.
3. The method for node jump of workflow according to claim 2, further comprising, after said restoring the original task flow direction of said target node:
if the countersign task exists in the original task flow direction of the target node, monitoring the approval result of each participant in the countersign task; wherein the countersign task is a task jointly approved by a plurality of participants;
if the approval result of any participant is monitored to be refused, carrying out refusing operation on the countersignature task.
4. A method of node jump for a workflow according to claim 3 further comprising:
if the countersign task exists in the original task flow direction of the target node and the participant of the countersign task is changed, determining the changed participant information;
based on the changed participant information, performing a change operation on the participant of the countersign task; wherein the change operation includes adding a participant, deleting a participant, replacing a participant.
5. The method for node jump of workflow of claim 1, wherein prior to determining the current node in the workflow that needs to be jumped, further comprising:
judging whether the workflow is in a finishing state or an abnormal closing state;
and restarting the workflow based on historical workflow data if the workflow is determined to be in a finished state or the workflow is determined to be in an abnormal closed state.
6. The method of node jump for a workflow of claim 5, wherein said restarting said workflow based on historical workflow data comprises:
determining a historical task node ID for the workflow based on the historical workflow data;
determining flow information of the workflow based on the historical task node ID;
and restoring to-Do data, participant data and flow engine data of the workflow based on the flow information.
7. A node jump apparatus for a workflow, comprising:
the node determining module is used for determining the current node needing to be jumped in the workflow;
the clearing module is used for clearing the original task flow direction of the current node;
the creation module is used for creating a new task flow direction of the current node;
the setting module is used for setting a target node of the new task flow direction and participants of the target node;
and the execution module is used for executing the jump task from the current node to the target node so as to enable the participant of the target node to process the task of the target node.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements a node jump method of the workflow of any of claims 1 to 6 when the program is executed by the processor.
9. A non-transitory computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements a node jump method of a workflow according to any of claims 1 to 6.
10. A computer program product comprising a computer program which, when executed by a processor, implements a node jump method of a workflow according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311109705.2A CN117290018A (en) | 2023-08-30 | 2023-08-30 | Node jump method, device, equipment, storage medium and product of workflow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311109705.2A CN117290018A (en) | 2023-08-30 | 2023-08-30 | Node jump method, device, equipment, storage medium and product of workflow |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117290018A true CN117290018A (en) | 2023-12-26 |
Family
ID=89239985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311109705.2A Pending CN117290018A (en) | 2023-08-30 | 2023-08-30 | Node jump method, device, equipment, storage medium and product of workflow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117290018A (en) |
-
2023
- 2023-08-30 CN CN202311109705.2A patent/CN117290018A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5119935B2 (en) | Management program, management apparatus, and management method | |
| CN106503132B (en) | A kind of distributed transaction management method and system | |
| US20100082708A1 (en) | System and Method for Management of Performance Fault Using Statistical Analysis | |
| US20080270212A1 (en) | Method, apparatus or software for managing a data processing process | |
| CN107357730B (en) | System fault diagnosis and repair method and device | |
| US20110252019A1 (en) | Project management system | |
| CN112486640B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN113590370A (en) | Fault processing method, device, equipment and storage medium | |
| CN110275992B (en) | Emergency processing method, device, server and computer readable storage medium | |
| CN106991002B (en) | Method and equipment for realizing task scheduling management | |
| CN115700669B (en) | Material difference list generation method, electronic equipment and computer storage medium | |
| CN113537837A (en) | Automatic sorting method and device and computer equipment | |
| CN117290018A (en) | Node jump method, device, equipment, storage medium and product of workflow | |
| Kolisnichenko et al. | Software security risk management in DEVOPS methodology | |
| CN110347525A (en) | A kind of fault handling method and device | |
| CN113014675A (en) | Data processing method and device, electronic equipment and storage medium | |
| US20180012119A1 (en) | Robotic Conductor of Business Operations Software | |
| CN111130955B (en) | Distributed link monitoring method based on internet credit system | |
| CN112380042A (en) | Fault positioning and analyzing method and device for database software and storage medium | |
| CN115002042B (en) | Special line flow control method and device based on machine learning and computer equipment | |
| CN112116330B (en) | Automatic workflow error queue processing method and device | |
| CN118041759A (en) | Method, device and equipment for locating fault root cause of server cluster | |
| CN117093346A (en) | Method, device and medium for scheduling offline tasks | |
| CN115953118A (en) | Transaction forwarding abnormity repairing method and device | |
| KR20240062266A (en) | Method for processing event and system for the same |
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 |