CN112418796B - Sub-process task node activation method and device, electronic equipment and storage medium - Google Patents
Sub-process task node activation method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112418796B CN112418796B CN202011314845.XA CN202011314845A CN112418796B CN 112418796 B CN112418796 B CN 112418796B CN 202011314845 A CN202011314845 A CN 202011314845A CN 112418796 B CN112418796 B CN 112418796B
- Authority
- CN
- China
- Prior art keywords
- flow
- sub
- branch
- task node
- static
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 194
- 230000004913 activation Effects 0.000 title claims abstract description 42
- 230000003068 static effect Effects 0.000 claims abstract description 124
- 230000008569 process Effects 0.000 claims abstract description 103
- 230000002159 abnormal effect Effects 0.000 claims abstract description 67
- 238000012545 processing Methods 0.000 claims description 15
- 230000003213 activating effect Effects 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 9
- 230000000694 effects Effects 0.000 claims description 9
- 230000009191 jumping Effects 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 abstract description 10
- 230000005856 abnormality Effects 0.000 abstract description 4
- 238000011156 evaluation Methods 0.000 description 22
- 238000010586 diagram Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 7
- 230000009969 flowable effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 230000002708 enhancing effect Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 235000008694 Humulus lupulus Nutrition 0.000 description 2
- 230000009471 action 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
- 230000001960 triggered effect Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 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
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
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 disclosure provides a sub-process node activation method, a device, a storage medium and electronic equipment; relates to the technical field of computers. The method comprises the following steps: starting a target process instance corresponding to the business demand process; when the abnormal task node exists in the branch flow in the target flow instance, a target flow instance identifier is obtained; obtaining an execution flow entity corresponding to a sub-flow where an abnormal branch is located in the target flow instance according to the static flow configuration file and the target flow instance identifier; creating a new branch execution flow through an execution flow entity corresponding to the sub-flow where the abnormal branch is located; acquiring a static flow instance of a task node to be activated in an abnormal branch according to the static flow configuration file; and configuring a static flow instance of the task node to be activated in the abnormal branch for the task node corresponding to the new branch execution flow. The method and the device can activate any non-starting point node in the sub-process in the process engine, avoid restarting the process due to the abnormality 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 disclosure relates to the field of computer technology, and in particular relates to a sub-process node activation method, a sub-process node activation device, a computer readable storage medium and electronic equipment.
Background
At present, the workflow is a high-frequency use function in an enterprise management system, and almost all scenes related to business circulation and work completed by a plurality of persons according to the flow can be supported by a flow engine. The process engine can implement the tasks and monitor the tasks according to certain principles and processes, so that the purposes of improving efficiency, controlling the process, 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 initial node. When the middle node is abnormal, the process can only be restarted by a process initiator, but the abnormal node cannot be directly activated, so that the waste of manpower and time is caused.
It is therefore highly desirable to provide a sub-process node activation method that facilitates activation of any non-origin nodes within a sub-process in a process engine.
It should be noted that the information disclosed in the above background section is only for enhancing 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 disclosure aims to provide a sub-process node activation method, a sub-process node activation device, a computer-readable storage medium and electronic equipment, so as to solve the problem that when an intermediate node is abnormal, a process can only be restarted by a process initiator, and the abnormal node cannot be directly activated.
According to a first aspect of the present disclosure, there is provided a sub-flow node activation method, including:
acquiring a target flow 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-flow through an execution flow entity of the sub-flow;
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 instance corresponding to the business demand process;
and when the abnormal node exists in the branch flow in the target flow instance, acquiring the target flow instance identifier.
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 inquiring an execution flow entity corresponding to the sub-flow in the target flow instance based on the target flow instance identifier and the static definition identifier of the sub-flow.
In an exemplary embodiment of the disclosure, the creating, by the sub-process execution flow entity, a new tributary sub-execution flow of the sub-process includes:
the sub-flow execution flow entity receives a creation request of a new branch;
and responding to the creation request, and 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 tributary sub-execution flow of the sub-flow further includes:
and setting a parent-child relationship between the child flow execution flow and the new branch child execution flow based on the static flow configuration file.
In an exemplary embodiment of the present disclosure, the obtaining, according to the static flow configuration file, a static definition entity of a node to be activated in an abnormal leg includes:
Determining static task nodes of the nodes to be activated in the abnormal branch according to the static flow configuration file;
inquiring a 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 the task node corresponding to the set new tributary sub-execution flow as a static definition 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 using a proxy entity in the flow engine to activate the node to be activated.
According to a second aspect of the present disclosure, there is provided a sub-flow node activation apparatus, comprising:
the identification acquisition module is used for acquiring the target flow instance identification;
the entity generating 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;
an execution flow creation module, configured to create a new branch sub-execution flow of the sub-flow through an execution flow entity of the sub-flow;
The example acquisition module is used for acquiring static definition entities of the nodes to be activated in the abnormal branch according to the target flow example 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-flow 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 above described sub-flow node activation method via execution of the executable instructions.
Exemplary embodiments of the present disclosure may have some or all of the following advantages:
in the sub-process node activation method provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; 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; creating a new branch sub-execution flow of the sub-flow through an execution flow entity of the sub-flow; acquiring a static definition entity of a node to be activated in an abnormal branch according to a 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, avoid restarting the process due to the abnormality of the intermediate node, further save manpower and time and improve 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 disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 illustrates a schematic diagram of an exemplary system architecture to which a sub-flow node activation method and apparatus of embodiments of the present disclosure may be applied;
FIG. 2 illustrates a schematic diagram of a computer system suitable for use in implementing 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-flow node activation method according to one embodiment of the disclosure;
FIG. 5 schematically illustrates a flow diagram for creating a tributary sub-execution flow according to one embodiment of the present disclosure;
FIG. 6 schematically illustrates a flow diagram according to one particular embodiment of the present disclosure;
Fig. 7 schematically illustrates a block diagram of a sub-flow node activation apparatus according to one embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many 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 the 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 present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. 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 a repetitive description thereof 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 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 illustrates a schematic diagram of a system architecture of an exemplary application environment in which a sub-flow node activation method and apparatus of embodiments of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include one or more of the terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The terminal devices 101, 102, 103 may be various electronic devices with display screens 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, the server 105 may be a server cluster formed by a plurality of servers.
The sub-flow node activation method provided in the embodiments of the present disclosure is generally executed by the server 105, and accordingly, the sub-flow node activation device is generally disposed in the server 105. However, it is easily understood by those skilled in the art that the method for activating a sub-flow node provided in the embodiment of the present disclosure may also be performed by the terminal devices 101, 102, 103, and accordingly, the sub-flow node activating apparatus may also be provided in the terminal devices 101, 102, 103, which is not specifically limited in the present exemplary embodiment.
Fig. 2 shows a schematic diagram of a computer system suitable for use in implementing embodiments 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 impose any limitation on the functions and the application scope of the embodiments of the present disclosure.
As shown in fig. 2, the computer system 200 includes a Central Processing Unit (CPU) 201, which can perform various appropriate actions and processes according to 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 required for the system operation are also stored. The CPU 201, ROM 202, and RAM 203 are connected to each other through 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 section 206 including a keyboard, a mouse, and the like; an output portion 207 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage section 208 including a hard disk or the like; and a communication section 209 including a network interface card such as a LAN card, a modem, and the like. The communication section 209 performs communication processing via a network such as the internet. The 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 installed on the drive 210 as needed, so that a computer program read out therefrom is installed into the storage section 208 as needed.
In particular, according to embodiments of the present disclosure, the processes described below with reference to flowcharts may be implemented as computer software programs. 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 shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 209, and/or installed from the removable medium 211. The computer program, when executed by a Central Processing Unit (CPU) 201, performs the various functions defined in the method and apparatus of the present application.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer-readable medium carries one or more programs which, when executed by one of the electronic devices, cause the electronic device to implement the methods described in the embodiments below. For example, the electronic device may implement the steps shown in fig. 4 and 5, and so on.
It should be noted that the computer readable medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 context of this 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 the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 following describes the technical scheme of the embodiments of the present disclosure in detail:
the process engine can implement target tasks and monitor according to certain principles and processes, so that the purposes of improving efficiency, controlling processes, improving customer service, enhancing effective management business processes and the like are achieved. Taking a flow process engine as an example, the flow process engine is a lightweight business process engine, is a key module for supporting configuration business circulation process, can be used for deploying BPMN 2.0 (Business Process Modeling Notation, business process model annotation, industry standard for defining processes) process definition, creating process instances of the process definition, and querying and accessing the running process instances, historical process instances and related data.
Currently, one sub-process implementation in the Flowable process engine is an Ad-hoc (peer-to-peer mode) sub-process. A plurality of process nodes can be stored in the Ad-hoc sub-process container, and the process nodes have no process sequence before the process runs, and the sequence and execution of the process are dynamically determined by the execution time.
Referring to the flowchart shown in fig. 3, the implementation manner of the Ad-hoc sub-flow can meet the service logic requirement, namely, three situations of only the branch a ("task A1" node→ "task A2" node→ "task A3" node), only the branch B and the branch A, B all travel can be met, and a certain branch can be activated at any time. In addition, fig. 3 also includes a node "after task", and when the business process flows to the node, the sub-process is completed.
For some abnormal situations in the Ad-hoc sub-flow, for example, after the normal activation of the 'task A1' node, the process engine can initiate the flow only by reactivating the 'task A1' node and can not be directly activated from the 'task A2' node because of abnormal loss of some reasons, namely, the state of the branch A1 is lost, so that the manpower and time waste are caused. If the execution flows of the "task A1" node and the "task A2" node are disconnected, the whole flow is too dispersed and is not easy to understand, and the branches A, B cannot be intuitively distinguished.
Based on one or more of the above problems, the present exemplary embodiment provides a sub-flow node activation method, which may be applied to the server 105 or one or more of the terminal devices 101, 102, 103, which is not specifically limited in the present exemplary embodiment. Referring to fig. 4, the sub-flow node activation method may include the following steps S410 to S450:
step S410, obtaining the target flow 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-flow through an execution flow entity of the sub-flow.
S440, acquiring static definition entities of the nodes to be activated in the abnormal branch according to the static flow configuration file.
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 the sub-process node activation method provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; 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; creating a new branch sub-execution flow of the sub-flow through an execution flow entity of the sub-flow; acquiring a static definition entity of a node to be activated in an abnormal branch according to a 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, avoid restarting the process due to the abnormality of the intermediate node, further save manpower and time and improve the operation and maintenance efficiency of operation and maintenance personnel.
Next, the above steps of the present exemplary embodiment will be described in more detail.
In step S410, a target flow instance identification is obtained.
The system can create a service work order according to service requirements, and one service work order can be started to simultaneously start one flow instance, and the two flow instances correspond to each other.
The business worksheet refers to a work task document of a target business, and the actual business is usually expressed by a business form, so that business meaning is realized by integrating the business worksheet, and the integration of the business worksheet and the business form usually comprises automatic acquisition, storage and modification of business form data, authority control of a business form domain, maintenance of flow related data and binding of a flow link form.
The flow instance refers to a flow defined running state, which records state information such as a start time and an end time of a flow running, and represents a data entity of a workflow. Correspondingly, the flow definition refers to predefined business logic, is an objectified definition of a workflow abstraction, and is a complete definition of the workflow, and includes key information such as the trend among nodes. The node is abstract objectification definition of a process link in the workflow, and the node can realize a certain appointed behavior and can also forward and maintain the continuation of the workflow until reaching a final node.
That is, after a business process is started, a process instance corresponds to a current running process instance of the process engine. Each flow instance is generated based on the static flow configuration file, and a flow instance ID can be created for each flow instance while the flow instance is created, so that node activation processing is performed on the flow instances of different service work orders.
In this example embodiment, a corresponding target flow instance may be started according to a service demand flow, and when it is monitored that an abnormal node exists in a branch flow in the target flow instance, the target flow instance identifier may be obtained.
The abnormal node is a node with abnormal task processing results, and the abnormal node may be a plurality of nodes located in different branches in the current operation flow example. Whether abnormal nodes exist in the current operation flow example or not can be monitored in real time through the electronic equipment, and the abnormal nodes are sensors. When the abnormal node exists in the current operation flow instance, the corresponding target flow instance ID (Identification) can be obtained by inquiring the data in the service form, and the position of the abnormal node in the flow can be quickly and accurately searched so as to be convenient for subsequent activation. In an exemplary embodiment, the name of the target flow instance may also be obtained, which is not limited in this embodiment.
In step S420, 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 is obtained.
In this example embodiment, each flow instance may be generated based on its static flow profile. The static flow configuration file is a static flow definition file, and one static flow definition file can generate different flow instances corresponding to different service worksheets of a plurality of identical flows. Furthermore, static flow definitions are pre-deployed in the project before the service work order has 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-flow element may be queried through the static flow definition file. The sub-flow elements may be names of various task nodes, attributes of the task nodes, flow variables set by the task nodes, etc. in the sub-flow where the abnormal branch is located.
The outermost layer of a flow instance corresponds to an execution flow of a main flow, which may be referred to as a primary execution flow. Each branch of a flow instance corresponds to an execution flow, and each multi-instance task itself may have multiple execution flows. In this example embodiment, based on the target flow instance ID and the static definition ID corresponding to the sub-flow, the execution flow entity corresponding to the sub-flow in the target flow instance may be quickly queried, so as to create a new tributary sub-execution flow through the execution flow entity.
In step S430, a new tributary sub-execution flow of the sub-flow is created by the execution flow entity of the sub-flow. Referring to fig. 5, the process may include the steps of:
step S510, the sub-flow execution flow entity receives a creation request of a new branch.
And S520, responding to the creation request, and creating basic data of the sub-execution flow corresponding to the new branch.
After receiving the creation request of the new branch, the sub-flow execution flow entity may first create the basic data of the sub-execution flow corresponding to the new branch, that is, create the relevant attribute of the new branch execution flow, such as the ID, the name, etc. of the new branch execution flow. Second, a deployment object may be created, defined as data of the execution flow class, and an execution flow created.
An 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 exemplary embodiment, the new bypass flow also corresponds to an execution flow and is a sub-execution flow relative to the sub-flow execution flow. Therefore, the parent-child relationship between the new tributary sub-execution flow and the sub-flow execution flow can be set based on the static flow definition file, so as to further perfect the attribute of the new tributary sub-execution flow.
In the process engine-based management activities, a general part, namely, the process management activities which can be repeatedly executed, is independent to form sub-processes, and can be called by the management activities of other processes. Correspondingly, the sub-process is called to be the parent process, and the sub-process can inherit part of the attribute of the parent process. One flow may call other flows, or may be called by another flow. Thus, a determination is made as to whether a flow is a sub-flow, and it can be seen whether it is invoked. A determination is made as to whether a flow is a parent flow and can see if it invokes other child flows.
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 may be obtained, the location of the node to be activated may be obtained, and the node type of the node to be activated may be obtained. The static definition entity of the node to be activated can be more quickly and accurately queried according to the static definition ID of the node to be activated, namely, the static flow instance corresponding to the node to be activated is acquired, relative to the position and the node type of the node to be activated.
In step S450, the task node corresponding to the set new tributary sub-execution flow is configured as a static definition entity of the node to be activated, and the node to be activated is activated.
In an example implementation manner, a task node corresponding to a new branch sub-execution flow may be set as a node to be activated, and a static definition entity of the node to be activated is processed by using a proxy entity of the flow engine to activate the node to be activated.
Specifically, a node corresponding to an execution flow where the node to be activated is located is adjusted to be a task node corresponding to a new branch sub-execution flow. Thus, the current running process instance can jump to the task node corresponding to the new branch sub-execution flow. After the task node corresponding to the new branch sub-execution flow is jumped, the new branch sub-execution flow is triggered, namely, the current operation flow instance is triggered to start normal operation from the task node corresponding to the new branch sub-execution flow.
The process can then continue through the flow engine using the agent entity itself while processing the process variables of the normal process jump. Wherein the setting of the process variable is to define the name of the process variable according to each task node ID, and to set the value of the process variable. By processing the process variables of the normal flow hops, hops between nodes can be achieved.
It can be understood that the method can smoothly activate the new branch execution flow and any task node on the new branch execution flow under the sub-flow, and realize the activation of the non-starting point node of the sub-flow by using the system containing the workflow module of the flow engine.
The method of the example embodiment can randomly activate non-starting point nodes in the sub-process, is more flexible than the conventional process, so that the process which is originally started from the beginning can be directly performed from the intermediate node, the process of unnecessary links before the target node is saved, and the communication cost and the manual operation are reduced. In addition, the timeliness of the operation and maintenance problem can be improved, and further the user experience is improved. Therefore, the method has good flexibility, universality and robustness based on the activation of any non-starting point node in any sub-flow by the Flowable flow engine.
One specific application example of the method in this example embodiment is exemplified by a business requirement flow based on a Flowable flow engine. The Flowable flow engine can be applied to a business requirement module, for example, can be used for controlling the evaluation and the stage state change presentation of the requirement circulation.
Referring to fig. 6, a flow chart for evaluating demand flows and changing stage states is shown, and the flow can be divided into a branch of a system demand flow and a branch of a system demand flow. The transition system demand flow branch and the transition more flow branch respectively comprise a plurality of task nodes, such as task nodes named as 'new', 'evaluate pass', 'evaluate fail', 'transition system demand', 'schedule evaluate pass', 'schedule evaluate fail', 'schedule evaluate invalid', 'transition more', 'wait close', and the task nodes are returned to ITSM (system management) ".
For example, only one branch in the above flow or a second branch in a certain period may be taken, and the corresponding actual scenario may be refined for the primary demand-convertible system demand, or may be directly transferred to a development team for processing. In addition, since one demand may involve multiple systems or multiple-stage resolution, another leg may be activated at a certain time period.
Taking the branch of the system demand flow as an example, after the task node in evaluation is activated, the person corresponding to the task node in evaluation can evaluate the task node in evaluation. After the personnel corresponding to the task node in evaluation completes the evaluation operation corresponding to the service work order, the flow backwards flows to the next corresponding task node. Specifically, when a person performs an evaluation operation, two results are generated, and when the evaluation passes, the flow flows to an evaluation pass task node; when the evaluation fails, the flow flows to a task node of 'evaluation failed'; and continuing to flow backwards according to the actual situation until the flow corresponding to the service work order is finished, wherein it can be understood that when the transfer system demand flow reaches the task node to be closed, the transfer system demand flow is finished.
When the system needs to create new business requirements, the detailed form information can be filled in according to the business requirements. Meanwhile, a flow instance corresponding to the flow chart shown in fig. 6 may be started, and the flow instance ID may be stored in the database table.
For example, when a business need needs to be evaluated and an exhaustive system need is to be met, a bypass flow may be initiated by the flow engine starting with the task node "under evaluation". When the direct transfer schedule is required to be changed, a branch flow taking a task node in schedule evaluation as a starting point can be started by a flow engine.
For a branch flow creating a schedule, the start point of the flow is a task node in the schedule evaluation. Assuming that a system exception results in a "task under evaluation" node not being activated, and that flow is not found to be abnormal when it goes to a "task under evaluation" node.
At this time, the flow instance ID recorded at the beginning of the flow may be obtained by querying the database table.
And inquiring and acquiring a static definition ID corresponding to the Ad-hoc sub-process from the deployed static process definition file, and acquiring an execution flow entity corresponding to the Ad-hoc sub-process by combining the process instance ID.
And creating a new branch sub-execution flow through an execution flow entity of the sub-flow, namely, correspondingly taking a task node in scheduling evaluation as a starting point, and setting a 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 schedule evaluation passing through by inquiring a static flow definition file, and finding a static flow instance corresponding to the task node with the schedule evaluation passing through according to the static flow definition ID.
Setting the task node of the newly created branch sub-execution flow binding as the static flow instance corresponding to the task node of the 'schedule evaluation pass', namely, jumping the 'schedule evaluation pass' abnormal task node to the task node of the newly created branch sub-execution flow binding.
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, the process engine can execute a 'continue flow operation' mode by a proxy entity of the process engine, process variables of normal flow jump are processed, and finally 'schedule evaluation pass' nodes are completely activated. The method solves the problem that the existing Flowable flow engine cannot activate any sub-flow execution flow non-starting point task node, and fills the defect that the existing sub-flow cannot be activated arbitrarily.
In the sub-process node activation method provided by the exemplary embodiment of the present disclosure, a target process instance identifier is obtained; 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; creating a new branch sub-execution flow of the sub-flow through an execution flow entity of the sub-flow; acquiring a static definition entity of a node to be activated in an abnormal branch according to a 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, avoid restarting the process due to the abnormality of the intermediate node, further save manpower and time and improve the operation and maintenance efficiency of operation and maintenance personnel.
It should be noted that although the steps of the methods in the present disclosure are depicted in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
Further, in this example embodiment, a sub-process node activation apparatus is also provided. The device can be applied to a server or terminal equipment. Referring to fig. 7, the sub-flow node activation apparatus 700 may include an identification acquisition module 710, an entity generation module 720, an execution flow creation module 730, an instance acquisition module 740, and a node activation module 750, wherein:
an identifier obtaining module 710, configured to obtain a target flow instance identifier;
the entity generating module 720 is configured to obtain 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;
an execution flow creation module 730, configured to create a new tributary sub-execution flow of the sub-flow through an 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 the abnormal branch according to the target flow instance identifier;
the node activating module 750 is configured to configure the task node corresponding to the set new tributary 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-flow node activation apparatus 800 further includes: starting a target process instance corresponding to the business demand process; and when the abnormal node exists in the branch flow in the target flow instance, acquiring the target flow instance identifier.
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 an execution flow entity corresponding to the sub-flow in the target flow instance based on the target flow instance identifier and the static definition identifier of the sub-flow.
The execution flow creation module 730 includes:
the receiving module is used for receiving a creation request of a new branch by the sub-flow execution flow entity;
and the creation module is used for responding to the creation 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 father-son relationship between the sub-flow execution flow and the new branch sub-execution flow based on the static flow configuration file.
The instance acquisition module 740 includes:
the second node determining module is used for determining static task nodes of the nodes 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:
the second setting module is used for setting the 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 using the proxy entity in the flow engine so as to activate the node to be activated.
The details of each module in the above-mentioned sub-flow node activation apparatus are described in detail in the corresponding sub-flow node activation method, so that details are not repeated here.
It should be noted that although in the above detailed description several modules or units of a 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 in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (4)
1. A method for activating a sub-process task node, the method comprising:
step S1, starting a target flow instance corresponding to a business demand flow; wherein,
a service work order is started, and then a flow instance is started at the same time, wherein the service work order and the flow instance correspond to each other;
each branch of a flow instance corresponds to an execution flow;
the outermost layer of one flow instance corresponds to the execution flow of one main flow;
each flow instance is generated based on its pre-deployed static flow configuration file;
the static flow data in the static flow configuration file at least comprises each task node ID and task node name;
the flow instance refers to a flow-defined running state, records the state information of the starting time and the ending time of the running of one flow, and represents the data entity of one working flow;
the flow definition refers to predefined business logic, the flow definition is an objectification definition abstracted to a work flow, and the complete flow definition comprises a task node and a trend between task nodes;
Step S2, when the abnormal task node exists in the branch flow in the target flow instance, a target flow instance identifier is obtained; the abnormal task node is a task node with abnormal task processing results;
step S3, according to the static flow configuration file and the target flow instance identifier, obtaining an execution flow entity corresponding to the sub-flow where the abnormal branch is located in the target flow instance; in particular, the method comprises the steps of,
inquiring static definition identifiers corresponding to the sub-flow elements through the static flow configuration file;
the sub-process elements comprise names of all task nodes and task node attributes in the sub-process where the abnormal branch is located;
inquiring an execution flow entity corresponding to the sub-flow where the abnormal branch is located in the target flow instance based on the static definition identifier corresponding to the sub-flow element and the target flow instance identifier;
step S4, creating a new branch execution flow through an execution flow entity corresponding to the sub-flow where the abnormal branch is located, including:
step S41, receiving a creation request of a new branch by an execution flow entity corresponding to the sub-flow where the abnormal branch is located;
step S42, responding to the creation request of the new branch, and creating basic data of the new branch execution flow, wherein the basic data comprise the ID and the name of the new branch execution flow;
Step S43, setting the parent-child relationship between the child flow execution flow of the child flow where the abnormal branch is located and the new branch execution flow based on the static flow configuration file;
wherein, in the management activities based on the flow engine, the general part is the flow management activities which can be repeatedly executed, and the general part is independent to be sub-flows;
the sub-processes can be invoked by management activities of other processes; calling the sub-process to be a parent process;
each sub-process corresponds to a sub-process execution flow of an associated parent process, each branch corresponds to a branch execution flow, and the branch execution flow is a sub-execution flow relative to the sub-process execution flow;
s5, acquiring a static flow instance of a task node to be activated in the abnormal branch according to the static flow configuration file; in particular, the method comprises the steps of,
inquiring and determining a static definition identifier of a task node to be activated in an abnormal branch according to the static flow configuration file, wherein the static definition identifier of the task node to be activated comprises: static definition ID of task node to be activated, position of task node to be activated, type of task node to be activated;
acquiring a corresponding static flow instance according to a static definition identifier of a task node to be activated in the abnormal branch;
Step S6, configuring a static flow instance of the task node to be activated in the abnormal branch for the task node corresponding to the new branch execution flow, namely, jumping the task node to be activated in the abnormal branch to the task node corresponding to the new branch execution flow, so that the current running flow instance jumps to the task node corresponding to the new branch execution flow;
after jumping to the task node corresponding to the new branch execution flow, triggering the current running process instance to start normal running from the task node corresponding to the new branch execution flow; the process is continuously circulated by utilizing the proxy entity in the process engine, and meanwhile, the skip among nodes is realized by processing the skip process variable so as to complete the activation; wherein the name of the process variable and the value of the set process variable are defined according to each task node ID.
2. A sub-process task node activation device, comprising:
the identification acquisition module is used for acquiring the target flow instance identification;
the entity generating module is used for obtaining an execution flow entity corresponding to the sub-flow where the abnormal branch is located in the target flow instance according to the static flow configuration file and the target flow instance identifier; specifically, inquiring static definition identifiers corresponding to the sub-flow elements through a static flow configuration file; the sub-process elements comprise names of all task nodes and task node attributes in the sub-process where the abnormal branch is located; inquiring an execution flow entity corresponding to the sub-flow where the abnormal branch is located in the target flow instance based on the static definition identifier corresponding to the sub-flow element and the target flow instance identifier;
The execution flow creation module is configured to create a new branch execution flow by using an execution flow entity corresponding to a sub-flow where the abnormal branch is located, where the execution flow creation module includes: step S41, receiving a creation request of a new branch by an execution flow entity corresponding to the sub-flow where the abnormal branch is located; step S42, responding to the creation request of the new branch, and creating basic data of the new branch execution flow, wherein the basic data comprise the ID and the name of the new branch execution flow; step S43, setting the parent-child relationship between the child flow execution flow of the child flow where the abnormal branch is located and the new branch execution flow based on the static flow configuration file; wherein, in the management activities based on the flow engine, the general part is the flow management activities which can be repeatedly executed, and the general part is independent to be sub-flows; the sub-processes can be invoked by management activities of other processes; calling the sub-process to be a parent process; each sub-process corresponds to a sub-process execution flow of an associated parent process, each branch corresponds to a branch execution flow, and the branch execution flow is a sub-execution flow relative to the sub-process execution flow;
the example obtaining module is used for obtaining a static flow example of the task node to be activated in the abnormal branch according to the static flow configuration file; specifically, according to the static flow configuration file, inquiring and determining a static definition identifier of a task node to be activated in the abnormal branch, wherein the static definition identifier of the task node to be activated comprises: static definition ID of task node to be activated, position of task node to be activated, type of task node to be activated; acquiring a corresponding static flow instance according to a static definition identifier of a task node to be activated in the abnormal branch;
The task node activating module is used for configuring a static flow instance of the task node to be activated in the abnormal branch for the task node corresponding to the new branch execution flow, namely, jumping the task node to be activated in the abnormal branch to the task node corresponding to the new branch execution flow, so that the currently operated flow instance jumps to the task node corresponding to the new branch execution flow; after jumping to the task node corresponding to the new branch execution flow, triggering the current running process instance to start normal running from the task node corresponding to the new branch execution flow; the process is continuously circulated by utilizing the proxy entity in the process engine, and meanwhile, the skip among nodes is realized by processing the skip process variable so as to complete the activation; wherein the name of the process variable is defined and the value of the process variable is set according to each task node ID;
the device is also for: starting a target process instance corresponding to the business demand process; one flow instance is started after one service work order is started, and the two flow instances are corresponding to each other; each branch of a flow instance corresponds to an execution flow; the outermost layer of one flow instance corresponds to the execution flow of one main flow; each flow instance is generated based on its pre-deployed static flow configuration file; the static flow data in the static flow configuration file at least comprises each task node ID and task node name; the flow instance refers to a flow-defined running state, records the state information of the starting time and the ending time of the running of one flow, and represents the data entity of one working flow; the flow definition refers to predefined business logic, the flow definition is an objectification definition abstracted to a work flow, and the complete flow definition comprises a task node and a trend between task nodes;
When the abnormal task node exists in the branch flow in the target flow instance, a target flow instance identifier is obtained; the abnormal task node is a task node with abnormal task processing results.
3. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of claim 1.
4. 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 claim 1 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 CN112418796A (en) | 2021-02-26 |
| CN112418796B true 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) |
Families Citing this family (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 |
|---|
| Flowable工作流的高校财务报销系统的研究与实现;赵赛;;石家庄学院学报(第03期);全文 * |
| 基于GERT网络的工作流动态调整引擎的设计与实现;吴冰 等;计算机工程与设计(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112418796A (en) | 2021-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109670951B (en) | Block chain intelligent contract debugging and publishing method and system | |
| CN109684057B (en) | Task processing method and device and storage medium | |
| US20110004564A1 (en) | Model Based Deployment Of Computer Based Business Process On Dedicated Hardware | |
| CN111930372A (en) | Service arrangement solution method and system realized through draggable flow chart | |
| CN106600226B (en) | Method and device for optimizing process management system | |
| CN109032590B (en) | Configuration method, device, terminal and storage medium of visual development environment | |
| CN110764752B (en) | System and method for realizing graphic service arrangement of Restful service | |
| CN111695827B (en) | Business process management method and device, electronic equipment and storage medium | |
| US9380001B2 (en) | Deploying and modifying a service-oriented architecture deployment environment model | |
| CN112003754A (en) | Visual node registration method for OpenStack cluster | |
| CN115185496A (en) | Service arrangement method based on Flowable workflow engine | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
| CN114489954A (en) | Tenant creation method based on virtualization platform, tenant access method and equipment | |
| Lascu et al. | Automatic deployment of component-based applications | |
| CN112558968A (en) | Resource tree view generation method, device, equipment and storage medium | |
| CN108536447B (en) | Operation and maintenance management method | |
| CN116107694A (en) | Deployment method and device of k8s sub-cluster and storage medium | |
| CN112099879B (en) | Configuration information management method and device, computer equipment and storage medium | |
| CN115048158A (en) | Process arranging and calling method, system and computer equipment thereof | |
| CN108776618A (en) | Distributed workflow management method and device | |
| CN111736930B (en) | Program front-back end interface calling method and device, computer equipment and storage medium | |
| CN114185557A (en) | Software product deployment method, device, medium and electronic equipment | |
| US20090293064A1 (en) | Synchronizing shared resources in an order processing environment using a synchronization component | |
| US20160232595A1 (en) | Methods, systems, and computer readable media for processing an order with a start-start dependency | |
| JP2020170530A (en) | Information processing apparatus, processing method thereof, and program |
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 |