CN112418796A - Sub-process node activation method and device, electronic equipment and storage medium - Google Patents
Sub-process node activation method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112418796A CN112418796A CN202011314845.XA CN202011314845A CN112418796A CN 112418796 A CN112418796 A CN 112418796A CN 202011314845 A CN202011314845 A CN 202011314845A CN 112418796 A CN112418796 A CN 112418796A
- Authority
- CN
- China
- Prior art keywords
- sub
- flow
- node
- static
- entity
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 281
- 230000004913 activation Effects 0.000 title claims description 25
- 230000008569 process Effects 0.000 claims abstract description 146
- 230000003068 static effect Effects 0.000 claims abstract description 109
- 230000002159 abnormal effect Effects 0.000 claims abstract description 38
- 230000003213 activating effect Effects 0.000 claims abstract description 34
- 238000012545 processing Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000011156 evaluation Methods 0.000 description 30
- 238000010586 diagram Methods 0.000 description 10
- 230000009969 flowable effect Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000007704 transition Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011112 process operation Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The present disclosure provides a method, an apparatus, a storage medium and an electronic device for activating a sub-process node; relates to the technical field of computers. The method comprises the following steps: acquiring a target process instance identifier; obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier; creating a new branch sub-execution flow of the sub-process through an execution flow entity of the sub-process; acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file; and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated. The method and the device can activate any non-starting point node in the sub-process in the process engine, avoid the process from being restarted due to the abnormity of the intermediate node, further save manpower and time and improve the operation and maintenance efficiency of operation and maintenance personnel.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method for activating a sub-process node, an apparatus for activating a sub-process node, a computer-readable storage medium, and an electronic device.
Background
At present, workflow is a function used at high frequency in an enterprise management system, and almost all scenes related to business circulation and working of multiple persons according to the flow can be supported by a flow engine. The process engine can implement and monitor the tasks according to certain principles and processes, so that the purposes of improving efficiency, controlling the processes, improving customer service, enhancing effective management business processes and the like are achieved.
The task node activation mode of the sub-process in the existing process engine only supports the activation of the starting node. When the intermediate node is abnormal, the flow initiator can only initiate the flow again, but the abnormal node cannot be directly activated, so that the waste of manpower and time is caused.
Therefore, it is necessary to provide a sub-process node activation method to activate any non-starting point node inside the sub-process in the process engine.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure is directed to provide a method for activating a sub-process node, a device for activating a sub-process node, a computer-readable storage medium, and an electronic device, so as to solve the problem that when an intermediate node is abnormal, only a process initiator can re-initiate a process, but the abnormal node cannot be directly activated.
According to a first aspect of the present disclosure, there is provided a method for activating a child process node, including:
acquiring a target process instance identifier;
obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to a static flow configuration file and the target flow instance identifier;
creating a new branch sub-execution flow of the sub-process through the execution flow entity of the sub-process;
acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file;
and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated.
In an exemplary embodiment of the present disclosure, the method further comprises:
starting a target process example corresponding to a business demand process;
and when the situation that the branch flow in the target flow example has abnormal nodes is monitored, acquiring the target flow example identification.
In an exemplary embodiment of the present disclosure, the obtaining, according to the static flow configuration file and the target flow instance identifier, an execution flow entity corresponding to a sub-flow in the target flow instance includes:
determining a static definition identifier of a sub-process where the abnormal branch is located according to the static process configuration file;
and querying an execution flow entity corresponding to the sub-process in the target process instance based on the target process instance identifier and the static definition identifier of the sub-process.
In an exemplary embodiment of the present disclosure, the creating, by the sub-process execution flow entity, a new branch sub-execution flow of the sub-process includes:
the sub-process execution flow entity receives a creation request of a new branch;
and in response to the creation request, creating basic data of the sub-execution flow corresponding to the new branch.
In an exemplary embodiment of the present disclosure, the creating, by the execution flow entity of the sub-flow, a new branch sub-execution flow of the sub-flow further includes:
setting the parent-child relationship between the sub-process execution flow and the new branch sub-execution flow based on the static process configuration file.
In an exemplary embodiment of the present disclosure, the obtaining, according to the static process configuration file, a static definition entity of a node to be activated in an abnormal branch includes:
determining a static task node of a node to be activated in the abnormal branch according to the static flow configuration file;
and inquiring the static definition entity of the node to be activated according to the static task node of the node to be activated.
In an exemplary embodiment of the present disclosure, the configuring, as a static definition entity of the node to be activated, a task node corresponding to the set new branch sub-execution flow, and activating the node to be activated includes:
setting a task node corresponding to the new branch sub-execution flow as a static definition entity of the node to be activated;
and processing the static definition entity of the node to be activated by utilizing the proxy entity in the process engine so as to activate the node to be activated.
According to a second aspect of the present disclosure, there is provided a device for activating a child flow node, including:
the identification acquisition module is used for acquiring the identification of the target process instance;
the entity generation module is used for obtaining an execution flow entity corresponding to the sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier;
the execution flow creating module is used for creating a new branch sub-execution flow of the sub-process through the execution flow entity of the sub-process;
the instance obtaining module is used for obtaining a static definition entity of a node to be activated in an abnormal branch according to the target process instance identifier;
and the node activation module is used for configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated and activating the node to be activated.
According to a third aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the sub-process node activation method described above.
According to a fourth aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the sub-process node activation method described above via execution of the executable instructions.
Exemplary embodiments of the present disclosure may have some or all of the following benefits:
in the method for activating the sub-process node provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier; creating a new branch sub-execution flow of the sub-process through an execution flow entity of the sub-process; acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file; and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated. The method can activate any non-starting point node in the sub-process in the process engine, avoids the process from being restarted due to the abnormity of the intermediate node, further saves manpower and time and improves the operation and maintenance efficiency of operation and maintenance personnel.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
Fig. 1 is a schematic diagram illustrating an exemplary system architecture of a method and apparatus for activating a child flow node to which embodiments of the present disclosure may be applied;
FIG. 2 illustrates a schematic structural diagram of a computer system suitable for use with the electronic device used to implement embodiments of the present disclosure;
FIG. 3 schematically illustrates a sub-flow diagram in a flow engine;
FIG. 4 schematically illustrates a flow diagram of a sub-process node activation method according to one embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow diagram for creation of a branch sub-execution flow, according to one embodiment of the present disclosure;
FIG. 6 schematically illustrates a flow diagram in accordance with a particular embodiment of the present disclosure;
fig. 7 schematically illustrates a block diagram of a sub-process node activation apparatus according to one embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 is a schematic diagram illustrating a system architecture of an exemplary application environment to which a method and an apparatus for activating a sub-flow node according to an embodiment of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include one or more of terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few. The terminal devices 101, 102, 103 may be various electronic devices having a display screen, including but not limited to desktop computers, portable computers, smart phones, tablet computers, and the like. It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.
The method for activating the sub-process node provided by the embodiment of the present disclosure is generally executed by the server 105, and accordingly, the sub-process node activating apparatus is generally disposed in the server 105. However, it is easily understood by those skilled in the art that the sub-process node activation method provided in the embodiment of the present disclosure may also be executed by the terminal devices 101, 102, and 103, and accordingly, the sub-process node activation apparatus may also be disposed in the terminal devices 101, 102, and 103, which is not particularly limited in this exemplary embodiment.
FIG. 2 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present disclosure.
It should be noted that the computer system 200 of the electronic device shown in fig. 2 is only an example, and should not bring any limitation to the functions and the scope of the application of the embodiments of the present disclosure.
As shown in fig. 2, the computer system 200 includes a Central Processing Unit (CPU)201 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)202 or a program loaded from a storage section 208 into a Random Access Memory (RAM) 203. In the RAM 203, various programs and data necessary for system operation are also stored. The CPU 201, ROM 202, and RAM 203 are connected to each other via a bus 204. An input/output (I/O) interface 205 is also connected to bus 204.
The following components are connected to the I/O interface 205: an input portion 206 including a keyboard, a mouse, and the like; an output section 207 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 208 including a hard disk and the like; and a communication section 209 including a network interface card such as a LAN card, a modem, or the like. The communication section 209 performs communication processing via a network such as the internet. A drive 210 is also connected to the I/O interface 205 as needed. A removable medium 211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 210 as necessary, so that a computer program read out therefrom is mounted into the storage section 208 as necessary.
In particular, the processes described below with reference to the flowcharts may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 209 and/or installed from the removable medium 211. The computer program, when executed by a Central Processing Unit (CPU)201, performs various functions defined in the methods and apparatus of the present application.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method as described in the embodiments below. For example, the electronic device may implement the steps shown in fig. 4 and 5, and the like.
It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The technical solution of the embodiment of the present disclosure is explained in detail below:
the process engine can implement and monitor target tasks according to certain principles and processes, so that the purposes of improving efficiency, controlling the processes, improving customer service, enhancing effective management business processes and the like are achieved. Taking a Flowable Process engine as an example, the Flowable Process engine is a lightweight Business Process engine, is a key module for supporting a configuration Business flow Process, and can be used for deploying BPMN 2.0(Business Process Modeling annotation, which is used for defining an industry standard of a Process) Process definition, creating a Process instance of the Process definition, and querying and accessing the Process instance, a historical Process instance and related data in operation.
Currently, one sub-flow implementation in the Flowable flow engine is an Ad-hoc (peer-to-peer mode) sub-flow. A plurality of flow nodes can be stored in the Ad-hoc sub-flow container, and the flow nodes do not have flow sequence before the flow operation, and the sequence and execution of the flow are dynamically determined by the execution.
Referring to the flowchart shown in fig. 3, the implementation manner of the Ad-hoc sub-process can meet the service logic requirement, that is, three situations that only the branch a is taken (the "task a 1" node → "task a 2" node → "task A3" node), only the branch B is taken, and the branch A, B is taken can be met, and a certain branch can be activated at any time. In addition, fig. 3 also includes "after task" of a node, and when the business process flow is transferred to the node, the sub-process is completed.
For some abnormal situations in Ad-hoc sub-processes, such as assuming that after the "task a 1" node is normally activated, if the state of the branch a1 is lost due to some reason, the process engine can only initiate the process by reactivating the "task a 1" node, but cannot directly activate from the "task a 2" node, which causes waste of labor and time. If the execution flow of the "task a 1" node and the "task a 2" node is disconnected, the whole flow is too dispersed to be easily understood, and the branch A, B cannot be intuitively distinguished.
Based on one or more of the above problems, the present exemplary embodiment provides a method for activating a sub-flow node, which may be applied to the server 105, or may be applied to one or more of the terminal devices 101, 102, and 103, and this is not particularly limited in this exemplary embodiment. Referring to fig. 4, the sub-flow node activation method may include the following steps S410 to S450:
and S410, acquiring a target process instance identifier.
And S420, obtaining an execution flow entity corresponding to the sub flow in the target flow instance according to the static flow configuration file and the target flow instance identifier.
And S430, creating a new branch sub-execution flow of the sub-process through the execution flow entity of the sub-process.
Step S440, acquiring a static definition entity of the node to be activated in the abnormal branch according to the static flow configuration file.
Step S450, configuring the task node corresponding to the new branch sub execution flow after setting as a static definition entity of the node to be activated, and activating the node to be activated.
In the method for activating a sub-process node provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier; creating a new branch sub-execution flow of the sub-process through an execution flow entity of the sub-process; acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file; and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated. The method can activate any non-starting point node in the sub-process in the process engine, avoids the process from being restarted due to the abnormity of the intermediate node, further saves manpower and time and improves the operation and maintenance efficiency of operation and maintenance personnel.
The above steps of the present exemplary embodiment will be described in more detail below.
In step S410, a target process instance identification is obtained.
The system can create the business work order according to the business requirement, and one process instance can be started simultaneously after one business work order is started, and the two are corresponding.
The service work order is a work task document of a target service, and generally, a service flow also needs to express an actual service through a service form, so that the service flow needs to be integrated with the service form to realize a service meaning, and the integration with the service form generally comprises automatic acquisition, storage and modification of service form data, authority control of a service form field, maintenance of process related data and binding of a process link form.
The process instance refers to an operation state defined by a process, records state information such as a starting time and an ending time of one process operation, and represents a data entity of a primary workflow. Correspondingly, the process definition refers to predefined business logic, and is an abstract object definition of a workflow, and a complete definition of the workflow, including key information such as the direction between nodes. The nodes are abstract object definitions of process links in the workflow, can realize a certain specified behavior, and can also forward and maintain the continuation of the workflow until the final nodes are reached.
That is, after a business process is started, corresponding to a process instance, the process instance currently running by the process engine is the currently running process instance. Each process instance is generated based on the static process configuration file, and a process instance ID can be created for each process instance while the process instance is created, so that the process instances of different business worksheets are subjected to node activation processing.
In this example embodiment, the corresponding target process instance may be started according to the business demand process, and when it is monitored that the branch process in the target process instance has an abnormal node, the target process instance identifier may be obtained.
The abnormal node is a node where an abnormal task processing result exists, and the abnormal node may be a plurality of nodes located in different branches in the current running process instance. Whether abnormal nodes such as sensors exist in the current running process instance can be monitored in real time through the electronic equipment. When the abnormal node exists in the current running process instance, the corresponding target process instance ID (Identification) can be obtained by inquiring the data in the service form, and the position of the abnormal node in the process can be quickly and accurately searched so as to be activated subsequently. In an example implementation, the name of the target process instance may also be obtained, which is not limited in this embodiment.
In step S420, an execution flow entity corresponding to the sub-flow in the target flow instance is obtained according to the static flow configuration file and the target flow instance identifier.
In this example embodiment, each flow instance may be generated based on its static flow profile. The static process configuration file is a static process definition file, and one static process definition file can generate a plurality of different process instances corresponding to different business work orders of the same process. Moreover, static flow definitions are pre-deployed in the project before a business work order has not been generated.
The static flow data in the static flow definition file may include, but is not limited to, task node IDs and task node names of the respective task nodes. The static task node is a static attribute definition of a specific task node in the static flow definition file, and may include a position, an ID, a node type, an attribute, a listener, and the like of the static task node in the flow chart.
Therefore, the static definition identification of the sub-process where the abnormal branch is located can be determined according to the static process definition file. Specifically, the static definition ID corresponding to the sub-process element may be queried through the static process definition file. The sub-process elements may be names of task nodes, attributes of the task nodes, process variables set by the task nodes, and the like in the sub-process in which the abnormal branch is located.
The outermost layer of a flow instance corresponds to the execution flow of a main flow, which may be referred to as a primary execution flow. Each branch of a flow instance corresponds to one execution flow, and each multi-instance task itself has multiple execution flows. In this exemplary embodiment, based on the ID of the target process instance and the static definition ID corresponding to the sub-process, the execution flow entity corresponding to the sub-process in the target process instance may be quickly queried, so as to create a new branch sub-execution flow through the execution flow entity.
In step S430, a new branch sub-execution flow of the sub-process is created by the execution flow entity of the sub-process. Referring to fig. 5, the process may include the steps of:
step s510, the sub-process execution flow entity receives a request for creating a new branch.
Step s520, in response to the creation request, creating basic data of the sub-execution stream corresponding to the new branch.
After the sub-process execution flow entity receives the creation request of the new branch, first, the basic data of the sub-execution flow corresponding to the new branch may be created, that is, the relevant attributes of the new branch execution flow, such as the ID, name, etc. of the new branch execution flow, may be created. Second, a deployment object may be created that defines it as data of the execution flow class and creates the execution flow.
The outermost layer of a flow instance corresponds to an execution flow of a main flow, each sub-flow corresponds to a sub-flow execution flow of an associated parent flow, and each branch corresponds to a branch execution flow. In an example embodiment, the new branch flow also corresponds to an execution flow and is a sub-execution flow with respect to the sub-flow execution flow. Therefore, the parent-child relationship between the new branch sub-execution flow and the sub-flow execution flow can be set based on the static flow definition file, so as to further improve the properties of the new branch sub-execution flow.
In the management activity based on the process engine, a general part, namely, the process management activity which can be repeatedly executed is separated to be a sub-process, and can be called by the management activities of other processes. Correspondingly, the child process is called as a parent process, and the child process can inherit part of the parent process attributes. One process may call other processes, as well as other processes. Therefore, whether a flow is a sub-flow is judged, and whether the flow is called or not can be seen. Whether a flow is a parent flow can be judged, and whether other child flows are called can be judged.
In step S440, a static definition entity of the node to be activated in the abnormal branch is obtained according to the static flow configuration file.
In an example embodiment, the static definition identifier of the node to be activated in the abnormal branch may be queried and determined according to the static flow definition file, for example, the static definition ID of the node to be activated is obtained, the position of the node to be activated may also be obtained, and the node type of the node to be activated may also be obtained. Compared with the position and the node type of the node to be activated, the static definition entity of the node to be activated can be queried more quickly and accurately according to the static definition ID of the node to be activated, namely, the static process instance corresponding to the node to be activated is obtained.
In step S450, configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated.
In an example embodiment, a task node corresponding to the new branch sub-execution flow may be set as a node to be activated, and a self-contained proxy entity in the process engine is used to process a statically defined entity of the node to be activated so as to activate the node to be activated.
Specifically, the node corresponding to the execution flow where the node to be activated is located is adjusted to be the task node corresponding to the new branch sub execution flow. Thus, the current operation flow example can jump to the task node corresponding to the new branch sub-execution flow. And after jumping to the task node corresponding to the new branch sub-execution flow, triggering the new branch sub-execution flow, namely triggering the current operation flow instance to start normal operation from the task node corresponding to the new branch sub-execution flow.
Then, the self-contained agent entity in the process engine can be utilized to enable the process to continue to flow, and meanwhile, the process variable of the normal process jump is processed. Wherein the setting of the process variable is to define a name of the process variable according to each task node ID and to set a value of the process variable. The jump between the nodes can be realized by processing the process variable of the normal flow jump.
It can be understood that the method can smoothly activate the new branch execution flow under the sub-flow and any task node thereon, and realizes the activation of the non-starting point node of the sub-flow by using the system containing the workflow module of the Flowable flow engine.
The method of the embodiment can activate nodes of non-starting points in the sub-processes at will, is more flexible than the conventional process, enables the original process which needs to be started from the beginning to be directly carried out from the intermediate nodes, saves the processes of non-necessary links in front of the target node, and reduces communication cost and manual operation. In addition, the solution timeliness of the operation and maintenance problem can be improved, and the user experience is further improved. Therefore, the method has better flexibility, universality and robustness when the Flowable process engine is used for activating any non-starting point node in any sub-process.
A specific application example of the method in the present exemplary embodiment takes a service demand flow based on a Flowable flow engine as an example. The Flowable flow engine may be applied to a business requirement module, for example, may be used to manage evaluation and staging state change display of requirement flow.
Referring to fig. 6, a flow chart of evaluation and phase state change of a demand flow is shown, and accordingly, the flow can be divided into a system demand flow branch and a transition flow branch. The system-to-system requirement flow branch and the transition updating flow branch respectively comprise a plurality of task nodes, wherein the task nodes comprise task nodes such as 'new establishment', 'evaluation in', 'evaluation pass', 'evaluation not pass', 'system-to-system requirement', 'schedule evaluation in', 'schedule evaluation pass', 'schedule evaluation not pass', 'schedule evaluation invalid', 'transition updating' and 'waiting for closing', and the task nodes comprise 'returned ITSM (system management)'.
Illustratively, only one branch in the above flow can be taken or the second branch can be taken at a certain time interval, and the corresponding actual scene can be refined for the preliminary demand convertible system demand and can also be directly transferred to a development team for processing. In addition, since a demand may involve multiple systems or multiple resolution situations, another leg may be activated at a certain time period.
Taking the branch of the system requirement flow as an example, after the task node in the evaluation is activated, the evaluation can be performed by the personnel corresponding to the task node in the evaluation. After the personnel corresponding to the task node under evaluation complete the evaluation operation corresponding to the business work order, the flow is transferred backwards to the next corresponding task node. Specifically, when the personnel perform the evaluation operation, two results are generated, and when the evaluation is passed, the process flow is transferred to the evaluation passing task node; when the evaluation fails, the process flow is transferred to the task node of which the evaluation fails; and continuing to perform backward flow transfer according to the actual situation until the flow corresponding to the business work order is finished, wherein the system transfer demand flow is finished when the system transfer demand flow reaches the task node to be closed.
When the system needs to create a new service requirement, the detailed form information can be filled in according to the service requirement. At the same time, a process instance corresponding to the flow chart shown in fig. 6 may be opened and the process instance ID stored in the database table.
For example, when a business requirement needs to be evaluated and a detailed system requirement is to be translated, a branch flow starting from a task node under evaluation can be started through a flow engine. When the schedule is required to be directly changed, a branch flow taking a task node in schedule evaluation as a starting point can be started through the flow engine.
For the branch flow for creating the scheduling, the starting point of the flow is a task node in scheduling evaluation. It is assumed that a system exception causes the task node "in scheduling evaluation" to not be activated, and the flow is found to have an exception when it flows to the task node "scheduling evaluation passes".
At this time, the flow instance ID recorded at the beginning of the flow can be acquired by querying the database table.
And inquiring and acquiring a static definition ID corresponding to the Ad-hoc sub-flow from the deployed static flow definition file, and acquiring an execution flow entity corresponding to the Ad-hoc sub-flow by combining the flow instance ID.
And creating a new branch sub-execution flow through the execution flow entity of the sub-flow, namely corresponding to the branch flow taking the task node in scheduling evaluation as a starting point, and setting the parent-child relationship between the branch flow and the Ad-hoc sub-flow execution flow.
And acquiring a static flow definition ID of the task node with the scheduling evaluation passing through by inquiring the static flow definition file, and finding a static flow instance corresponding to the task node with the scheduling evaluation passing through according to the static flow definition ID.
And setting the task node bound by the newly created branch sub execution flow as the static flow example corresponding to the task node with the scheduling evaluation passing, namely, switching the task node bound by the newly created branch sub execution flow to the task node bound by the abnormal task node with the scheduling evaluation passing.
And finally, triggering the newly created branch sub-execution flow, namely triggering the current operation flow instance to start normal operation from the bound task node. Specifically, a 'continuous flow operation' mode can be executed by an agent entity of the flow engine, the process variable of normal flow skipping is processed, and finally the 'scheduling evaluation is completely activated through' nodes. The problem that the conventional Flowable flow engine cannot activate any sub-flow execution flow non-starting point task node is solved, and the defect that the conventional sub-flow cannot be activated at will is overcome.
In the method for activating a sub-process node provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier; creating a new branch sub-execution flow of the sub-process through an execution flow entity of the sub-process; acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file; and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated. The method can activate any non-starting point node in the sub-process in the process engine, avoids the process from being restarted due to the abnormity of the intermediate node, further saves manpower and time and improves the operation and maintenance efficiency of operation and maintenance personnel.
It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Further, in this exemplary embodiment, a device for activating a child flow node is also provided. The device can be applied to a server or terminal equipment. Referring to fig. 7, the sub-process node activation apparatus 700 may include an identity obtaining module 710, an entity generating module 720, an execution flow creating module 730, an instance obtaining module 740, and a node activation module 750, wherein:
an identifier obtaining module 710, configured to obtain an identifier of a target process instance;
an entity generating module 720, configured to obtain, according to the static flow configuration file and the target flow instance identifier, an execution flow entity corresponding to the sub-flow in the target flow instance;
an execution flow creating module 730, configured to create a new branch sub-execution flow of the sub-flow through the execution flow entity of the sub-flow;
an instance obtaining module 740, configured to obtain a static definition entity of a node to be activated in an abnormal branch according to the target process instance identifier;
a node activating module 750, configured to configure the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activate the node to be activated.
In an example embodiment, the sub-process node activation apparatus 800 further includes: starting a target process example corresponding to a business demand process; and when the situation that the branch flow in the target flow example has abnormal nodes is monitored, acquiring the target flow example identification.
The entity generation module 720 includes:
the first node determining module is used for determining a static definition identifier of a sub-process where the abnormal branch is located according to the static process configuration file;
and the first entity query module is used for querying the execution flow entity corresponding to the sub-process in the target process instance based on the target process instance identifier and the static definition identifier of the sub-process.
The execution flow creation module 730 includes:
a receiving module, configured to receive, by the sub-process execution flow entity, a creation request of a new branch;
and the creating module is used for responding to the creating request and creating the basic data of the sub-execution flow corresponding to the new branch.
The execution flow creation module 730 further includes: and the first setting module is used for setting the parent-child relationship between the sub-process execution flow and the new branch sub-execution flow based on the static process configuration file.
The instance acquisition module 740 includes:
the second node determining module is used for determining a static task node of a node to be activated in the abnormal branch according to the static flow configuration file;
and the second entity query module is used for querying the static definition entity of the node to be activated according to the static task node of the node to be activated.
The node activation module 750 includes:
a second setting module, configured to set a task node corresponding to the new branch sub-execution flow as a static definition entity of the node to be activated;
and the entity processing module is used for processing the static definition entity of the node to be activated by utilizing the proxy entity in the process engine so as to activate the node to be activated.
The details of each module in the sub-process node activation apparatus have been described in detail in the corresponding sub-process node activation method, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for activating a child flow node, the method comprising:
acquiring a target process instance identifier;
obtaining an execution flow entity corresponding to a sub-flow in the target flow instance according to a static flow configuration file and the target flow instance identifier;
creating a new branch sub-execution flow of the sub-process through the execution flow entity of the sub-process;
acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file;
and configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated, and activating the node to be activated.
2. The method of sub-process node activation according to claim 1, further comprising:
starting a target process example corresponding to a business demand process;
and when the situation that the branch flow in the target flow example has abnormal nodes is monitored, acquiring the target flow example identification.
3. The method for activating a sub-process node according to claim 1, wherein the obtaining, according to the static process configuration file and the target process instance identifier, the execution flow entity corresponding to the sub-process in the target process instance includes:
determining a static definition identifier of a sub-process where the abnormal branch is located according to the static process configuration file;
and querying an execution flow entity corresponding to the sub-process in the target process instance based on the target process instance identifier and the static definition identifier of the sub-process.
4. The sub-process node activation method according to claim 1, wherein the creating a new branch sub-execution flow of the sub-process by the sub-process execution flow entity comprises:
the sub-process execution flow entity receives a creation request of a new branch;
and in response to the creation request, creating basic data of the sub-execution flow corresponding to the new branch.
5. The sub-process node activation method according to claim 4, wherein the creating a new branch sub-execution flow of the sub-process by the execution flow entity of the sub-process further comprises:
setting the parent-child relationship between the sub-process execution flow and the new branch sub-execution flow based on the static process configuration file.
6. The method for activating a sub-process node according to claim 1, wherein the obtaining a statically defined entity of a node to be activated in an abnormal branch according to the static process configuration file includes:
determining a static task node of a node to be activated in the abnormal branch according to the static flow configuration file;
and inquiring the static definition entity of the node to be activated according to the static task node of the node to be activated.
7. The method according to claim 1, wherein the step of configuring the task node corresponding to the new branch sub-execution flow after being configured as a statically defined entity of the node to be activated and activating the node to be activated includes:
setting a task node corresponding to the new branch sub-execution flow as a static definition entity of the node to be activated;
and processing the static definition entity of the node to be activated by utilizing the proxy entity in the process engine so as to activate the node to be activated.
8. A device for activating a child flow node, comprising:
the identification acquisition module is used for acquiring the identification of the target process instance;
the entity generation module is used for obtaining an execution flow entity corresponding to the sub-flow in the target flow instance according to the static flow configuration file and the target flow instance identifier;
the execution flow creating module is used for creating a new branch sub-execution flow of the sub-process through the execution flow entity of the sub-process;
the instance acquisition module is used for acquiring a static definition entity of a node to be activated in an abnormal branch according to the static flow configuration file;
and the node activation module is used for configuring the task node corresponding to the set new branch sub-execution flow as a static definition entity of the node to be activated and activating the node to be activated.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1 to 7.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the method of any of claims 1-7 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011314845.XA CN112418796B (en) | 2020-11-20 | 2020-11-20 | Sub-process task node activation method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011314845.XA CN112418796B (en) | 2020-11-20 | 2020-11-20 | Sub-process task node activation method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112418796A true CN112418796A (en) | 2021-02-26 |
| CN112418796B CN112418796B (en) | 2023-12-08 |
Family
ID=74776950
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011314845.XA Active CN112418796B (en) | 2020-11-20 | 2020-11-20 | Sub-process task node activation method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112418796B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113034107A (en) * | 2021-03-29 | 2021-06-25 | 北京沃东天骏信息技术有限公司 | Flow processing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9116777B1 (en) * | 2014-09-25 | 2015-08-25 | International Business Machines Corporation | In-flight process instance migration between business process execution language (BPEL) suites |
| CN106600226A (en) * | 2016-12-13 | 2017-04-26 | 泰康保险集团股份有限公司 | Method and device used for optimizing flow management system |
| CN109670664A (en) * | 2018-09-11 | 2019-04-23 | 深圳平安财富宝投资咨询有限公司 | Flow implementation method, user equipment, storage medium and device based on workflow |
| CN110147986A (en) * | 2019-05-21 | 2019-08-20 | 天津卡达克数据有限公司 | Flow node jump method, device, server and storage medium |
| CN111078371A (en) * | 2019-11-14 | 2020-04-28 | 泰康保险集团股份有限公司 | Branch task reconstruction method and device based on Flowable flow engine |
| CN111353752A (en) * | 2019-11-05 | 2020-06-30 | 泰康保险集团股份有限公司 | Flow processing method and device, electronic equipment and storage medium |
-
2020
- 2020-11-20 CN CN202011314845.XA patent/CN112418796B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9116777B1 (en) * | 2014-09-25 | 2015-08-25 | International Business Machines Corporation | In-flight process instance migration between business process execution language (BPEL) suites |
| CN106600226A (en) * | 2016-12-13 | 2017-04-26 | 泰康保险集团股份有限公司 | Method and device used for optimizing flow management system |
| CN109670664A (en) * | 2018-09-11 | 2019-04-23 | 深圳平安财富宝投资咨询有限公司 | Flow implementation method, user equipment, storage medium and device based on workflow |
| CN110147986A (en) * | 2019-05-21 | 2019-08-20 | 天津卡达克数据有限公司 | Flow node jump method, device, server and storage medium |
| CN111353752A (en) * | 2019-11-05 | 2020-06-30 | 泰康保险集团股份有限公司 | Flow processing method and device, electronic equipment and storage medium |
| CN111078371A (en) * | 2019-11-14 | 2020-04-28 | 泰康保险集团股份有限公司 | Branch task reconstruction method and device based on Flowable flow engine |
Non-Patent Citations (2)
| Title |
|---|
| 吴冰 等: "基于GERT网络的工作流动态调整引擎的设计与实现", 计算机工程与设计 * |
| 赵赛;: "Flowable工作流的高校财务报销系统的研究与实现", 石家庄学院学报 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113034107A (en) * | 2021-03-29 | 2021-06-25 | 北京沃东天骏信息技术有限公司 | Flow processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112418796B (en) | 2023-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110532020B (en) | Data processing method, device and system for micro-service arrangement | |
| CN109684057B (en) | Task processing method and device and storage medium | |
| US9519884B2 (en) | Data driven dynamic workflow | |
| CN100545851C (en) | The remote system administration of utility command row environment | |
| CN103984818B (en) | AUV (autonomous underwater vehicle) design flow visualization modeling method based on Flex technology | |
| CN114115852A (en) | Visual service arranging method, device, equipment and medium | |
| Hallerbach et al. | Context-based configuration of process variants | |
| US8365170B2 (en) | Realizing jumps in an executing process instance | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| CN110764752B (en) | System and method for realizing graphic service arrangement of Restful service | |
| CN110704749B (en) | Recommendation engine customization system, recommendation method, recommendation system and electronic equipment | |
| CN106600226B (en) | Method and device for optimizing process management system | |
| US20060250970A1 (en) | Method and apparatus for managing capacity utilization estimation of a data center | |
| JP2008112311A (en) | Method and system for business process execution, and program | |
| US20120173583A1 (en) | Automation framework | |
| CN114489954A (en) | Tenant creation method based on virtualization platform, tenant access method and equipment | |
| CN107896242B (en) | Service sharing method and device | |
| CN112418796A (en) | Sub-process node activation method and device, electronic equipment and storage medium | |
| CN112686580A (en) | Workflow definition method and system capable of customizing flow | |
| CN112558968A (en) | Resource tree view generation method, device, equipment and storage medium | |
| CN105592130A (en) | Service deployment method and device, and service management method | |
| JP7004930B2 (en) | Information processing equipment and its processing method and program | |
| CN115048158A (en) | Process arranging and calling method, system and computer equipment thereof | |
| CN114756224A (en) | Activity execution method and device | |
| CN114663177A (en) | State change control method, device, electronic equipment and storage medium |
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 |