CN116402474B - Workflow engine circulation method and device supporting circulation in non-routing direction - Google Patents
Workflow engine circulation method and device supporting circulation in non-routing direction Download PDFInfo
- Publication number
- CN116402474B CN116402474B CN202310636385.XA CN202310636385A CN116402474B CN 116402474 B CN116402474 B CN 116402474B CN 202310636385 A CN202310636385 A CN 202310636385A CN 116402474 B CN116402474 B CN 116402474B
- Authority
- CN
- China
- Prior art keywords
- node
- circulation
- service
- circulated
- current
- 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 53
- 238000004458 analytical method Methods 0.000 claims description 7
- 230000003213 activating effect Effects 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 6
- 230000004913 activation Effects 0.000 claims description 3
- 238000000605 extraction Methods 0.000 claims description 3
- 238000012546 transfer Methods 0.000 abstract description 9
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000009191 jumping Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000009517 secondary packaging Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- KLDZYURQCUYZBL-UHFFFAOYSA-N 2-[3-[(2-hydroxyphenyl)methylideneamino]propyliminomethyl]phenol Chemical compound OC1=CC=CC=C1C=NCCCN=CC1=CC=CC=C1O KLDZYURQCUYZBL-UHFFFAOYSA-N 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 201000001098 delayed sleep phase syndrome Diseases 0.000 description 1
- 208000033921 delayed sleep phase type circadian rhythm sleep disease Diseases 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a workflow engine circulation method and a device supporting circulation in a non-routing direction, which relate to the technical field of workflow circulation and comprise the steps of obtaining node information, routing information and the pointing relation between nodes and routes of all nodes so as to generate model data of each node; determining a current node where a service is located, acquiring model data of the current node and service flow requirements, and extracting flow records of the service from the service flow requirements; judging whether the service is transferred to the node to be transferred according to the transfer record of the current node and the preset condition of the service transfer type; the application is used for solving the technical problems that the existing workflow products cannot directly carry out the circulation of the non-routing mode, and the workload and the time cost are greatly increased.
Description
Technical Field
The application relates to the technical field of workflow transfer, in particular to a workflow engine transfer method and device supporting transfer in a non-routing direction.
Background
The current domestic workflow products are mainly based on secondary packaging of foreign open source products, and the open source products have the routing direction planned at first, so that the circulation mode of the workflow products obtained after the secondary packaging also needs to circulate according to the planned routing direction. However, in practical application, when a workflow product often encounters a scene of irregular circulation, the workflow product cannot directly circulate in a non-routing mode, and in practical project implementation, a large amount of additional secondary codes are needed to realize, so that the workload and the time cost are increased.
Disclosure of Invention
The application aims to provide a workflow engine circulation method and device supporting circulation in a non-routing direction so as to solve the problems. In order to achieve the above purpose, the technical scheme adopted by the application is as follows:
in a first aspect, the present application provides a workflow engine circulation method for supporting circulation in a non-routing direction, including:
acquiring node information, route information and pointing relation between nodes and routes of all nodes to generate model data of each node;
determining a current node where a service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements;
obtaining a node to be circulated of the service according to the service circulation demand, and obtaining model data of the node to be circulated;
analyzing the model data of the current node and the model data of the node to be transferred to obtain a service transfer type;
judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type.
In a second aspect, the present application further provides a workflow engine circulation method for supporting circulation in a non-routing direction, including:
a first acquisition module: the method comprises the steps of obtaining node information, route information and the pointing relation between nodes and routes of all nodes to generate model data of each node;
and an extraction module: the method comprises the steps of determining a current node where a service is located, obtaining model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements;
and a second acquisition module: the method comprises the steps of obtaining a node to be circulated of a service according to the service circulation requirement, and obtaining model data of the node to be circulated;
and an analysis module: the method comprises the steps of analyzing model data of a current node and model data of a node to be circulated to obtain a service circulation type;
and a judging module: and judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type.
The beneficial effects of the application are as follows:
the application can realize the requirements of returning, taking back and jumping in various scenes without secondary coding in project implementation, establishes a more free circulation concept, and uses a loose structure to perform circulation among nodes: the method and the system enable the circulation among the nodes to be carried out according to the routing direction or not, fundamentally break through the logic that the circulation is carried out according to the routing direction, and save a great deal of workload and time cost in the project implementation process.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the embodiments of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a workflow engine circulation method supporting circulation in a non-routing direction according to an embodiment of the present application;
fig. 2 is a schematic diagram of a peer branch node according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a workflow engine circulation device supporting circulation in a non-routing direction according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a workflow engine circulation device supporting circulation in a non-routing direction according to an embodiment of the present application.
The marks in the figure:
800. workflow engine circulation equipment supporting circulation in a non-routing direction; 801. a processor; 802. a memory; 803. a multimedia component; 804. an I/O interface; 805. a communication component.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Example 1:
the embodiment provides a workflow engine circulation method supporting circulation in a non-routing direction.
Referring to fig. 1, the method is shown to include:
s1, acquiring node information, route information and pointing relation between nodes and routes of all nodes to generate model data of each node;
specifically, the node information includes a node ID, a node name, a node type, a next node, and the like;
the routing information comprises a routing ID, a routing name, a pointing node ID, a pointing node name, a pointing node type, a routing ordering and routing passing adjustment;
the generated model data of the node comprises: an operation list, a sponsor list, a transacted role, a flow creator role and the like corresponding to the identity of each role.
S2, determining a current node where the service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements, wherein the circulation records comprise:
all the nodes which flow through are listed as route ID, node ID, ordering in the circulation route and current operator information of the nodes;
list of people transacted: to-Do data ID, sponsor name;
list of people not transacted: a list of people to be transacted and a person transacting role;
all readers list;
all route lists;
list of order of nodes already in circulation in the current route: current node ID under current route, current node name;
the next route list is provided with branch nodes;
a last route list, etc.
S3, obtaining a node to be circulated of the service according to the service circulation demand, and obtaining model data of the node to be circulated;
s4, analyzing the model data of the current node and the model data of the node to be circulated to obtain a service circulation type;
specifically, the step S4 includes:
analyzing the circulation record of the service to obtain a first node list in which the service is circulated, a second node list to be circulated and all sponsors in the first node list;
obtaining a sponsor of the node to be circulated according to the model data of the node to be circulated;
if the node to be circulated is in the first node list, the service circulation type is returned;
if the sponsor of the node to be circulated is a sponsor in the first node list, the service circulation type is taken back;
if the node to be circulated is in the second node list, judging whether the node to be circulated is the node which is ordered to be first in the second node flow list:
if yes, the service circulation type is circulation; otherwise, the service flow type is jump.
S5, judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type;
specifically, when the service flow type is return, step S5 includes:
s51, acquiring the type of the current node:
if the type of the current node is a single handling node, judging whether the current node has a same-level branch node or not:
if yes, acquiring a starting node and all peer branch nodes of the current node from the circulation record;
s52, judging whether the node to be circulated is a starting node of a same-level branch node or not:
if yes, the service flow is transferred to the node to be transferred, and the service handling authority of all the same-level branch nodes is cancelled and the service handling authority of the current sponsor of the current node is ended;
if the current node is a multi-person handling node, acquiring the last sponsor of the current node;
s53, designating the last sponsor as the sponsor of the node to be circulated, and ending the business handling authority of the current sponsor of the current node.
Specifically, as shown in fig. 2, the task 1 is a start node, the task 2, the task 3 and the task 4 are next nodes of the task 1, and the task 2, the task 3 and the task 4 are peer branch nodes;
when the business needs to go from the task 2 to the task 1, the business belongs to a return operation;
based on the above embodiment, the method further includes that if the service flow type is return, the activation states of all peer branch nodes are revoked, and revocation messages are sent to sponsors of each peer branch node.
After the service flow is transferred to the node to be transferred, the method further comprises the following steps:
updating the node to be circulated as the current node;
and updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
Example 2
The embodiment provides a workflow engine circulation method supporting circulation in a non-routing direction, which comprises the following steps:
s1, acquiring node information, route information and pointing relation between nodes and routes of all nodes to generate model data of each node;
s2, determining a current node where the service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements;
s3, obtaining a node to be circulated of the service according to the service circulation demand, and obtaining model data of the node to be circulated;
s4, analyzing the model data of the current node and the model data of the node to be circulated to obtain a service circulation type;
s5, judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type;
specifically, when the service flow type is taken back, step S5 includes:
judging whether the current node is transacted:
if the processing is finished, the preset conditions are not met;
and if the current node is not processed and the node to be transferred is the last node in the first node flow table, transferring the current node flow to the node to be transferred.
After the service flow is transferred to the node to be transferred, the method further comprises the following steps:
updating the node to be circulated as the current node;
and updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
Example 3
The embodiment provides a workflow engine circulation method supporting circulation in a non-routing direction, which comprises the following steps:
s1, acquiring node information, route information and pointing relation between nodes and routes of all nodes to generate model data of each node;
s2, determining a current node where the service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements;
s3, obtaining a node to be circulated of the service according to the service circulation demand, and obtaining model data of the node to be circulated;
s4, analyzing the model data of the current node and the model data of the node to be circulated to obtain a service circulation type;
s5, judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type;
specifically, when the service flow type is skip, step S5 includes:
acquiring association information of a current node and a node to be circulated;
if the association information accords with the preset rule, the service flow is transferred to the node to be transferred, specifically, the preset rule is to preset a transfer packet, the transfer packet comprises a plurality of stages of nodes which can transfer mutually, for example, two stages of nodes are separated from each other between the task 1 and the task 6, a condition capable of jumping is set between the task 1 and the task 6, and whether the task 1 and the task 6 meet the condition capable of jumping can be judged according to the association relation.
After the service flow is transferred to the node to be transferred, the method further comprises the following steps:
updating the node to be circulated as the current node;
and updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
Example 4:
as shown in fig. 3, the present embodiment provides a workflow engine circulation device supporting circulation in a non-routing direction, where the device includes:
a first acquisition module: the method comprises the steps of obtaining node information, route information and the pointing relation between nodes and routes of all nodes to generate model data of each node;
and an extraction module: the method comprises the steps of determining a current node where a service is located, obtaining model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements;
and a second acquisition module: the method comprises the steps of obtaining a node to be circulated of a service according to the service circulation requirement, and obtaining model data of the node to be circulated;
and an analysis module: the method comprises the steps of analyzing model data of a current node and model data of a node to be circulated to obtain a service circulation type;
and a judging module: and judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type.
Based on the above embodiments, the analysis module includes:
analysis unit: the method comprises the steps of analyzing a circulation record of a service to obtain a first node list, a second node list to be circulated and all sponsors in the first node list;
a first acquisition unit: the method comprises the steps of obtaining sponsors of nodes to be circulated according to model data of the nodes to be circulated;
a first judgment unit: if the node to be circulated is in the first node list, the service circulation type is returned;
a second judgment unit: if the sponsor of the node to be circulated is a sponsor in the first node list, the service circulation type is taken back;
a third judgment unit: if the node to be circulated is in the second node list, judging whether the node to be circulated is the node which is ordered to be first in the second node flow list:
if yes, the service circulation type is circulation; otherwise, the service flow type is jump.
Based on the above embodiment, the judging module includes:
a second acquisition unit: when the service flow type is returned, the type of the current node is acquired:
fourth judgment unit: if the type of the current node is a single handling node, judging whether the current node has a same-level branch node or not:
if yes, acquiring a starting node and all peer branch nodes of the current node from the circulation record;
fifth judging unit: the starting node is used for judging whether the node to be circulated is a peer branch node or not:
if yes, the service flow is transferred to the node to be transferred, and the service handling authority of all the same-level branch nodes is cancelled and the service handling authority of the current sponsor of the current node is ended.
Based on the above embodiment, the judging module further includes:
a third acquisition unit: if the current node is a multi-person handling node, acquiring the last sponsor of the current node;
and a processing unit: and designating the last sponsor as the sponsor of the node to be circulated, and ending the business handling authority of the current sponsor of the current node.
Based on the above embodiments, the analysis module includes:
sixth judgment unit: when the service flow type is taken back, judging whether the current node is transacted:
if the processing is finished, the preset conditions are not met;
and if the current node is not processed and the node to be transferred is the last node in the first node flow table, transferring the current node flow to the node to be transferred.
Based on the above embodiments, the analysis module includes:
a third acquisition unit: when the service circulation type is jump, acquiring the association information of the current node and the node to be circulated;
and if the associated information accords with the preset rule, the service flow is transferred to the node to be circulated.
Based on the above embodiment, after the traffic flows to the node to be circulated, the method further includes:
and an updating module: the method comprises the steps of updating a node to be circulated into a current node;
and an activation module: the method is used for updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
It should be noted that, regarding the apparatus in the above embodiments, the specific manner in which the respective modules perform the operations has been described in detail in the embodiments regarding the method, and will not be described in detail herein.
Example 5:
corresponding to the above method embodiment, a workflow engine circulation device supporting circulation in a non-routing direction is further provided in this embodiment, and a workflow engine circulation device supporting circulation in a non-routing direction described below and a workflow engine circulation method supporting circulation in a non-routing direction described above may be referred to correspondingly.
Fig. 4 is a block diagram illustrating a workflow engine circulation device 800 supporting circulation in a non-routing direction, according to an example embodiment. As shown in fig. 4, the workflow engine circulation device 800 supporting circulation in a non-routing direction may include: a processor 801, a memory 802. The workflow engine circulation device 800 supporting non-routing direction circulation may also include one or more of a multimedia component 803, an I/O interface 804, and a communication component 805.
The processor 801 is configured to control the overall operation of the workflow engine circulation device 800 supporting circulation in the non-routing direction, so as to complete all or part of the steps in the workflow engine circulation method supporting circulation in the non-routing direction. The memory 802 is used to store various types of data to support operation of the workflow engine circulation device 800 in the non-routing-enabled direction, such data may include, for example, instructions for any application or method operating on the workflow engine circulation device 800 in the non-routing-enabled direction, as well as application-related data such as contact data, messages, pictures, audio, video, and the like. The Memory 802 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as static random access Memory (Static Random Access Memory, SRAM for short), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM for short), programmable Read-Only Memory (Programmable Read-Only Memory, PROM for short), read-Only Memory (ROM for short), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia component 803 may include a screen and an audio component. Wherein the screen may be, for example, a touch screen, the audio component being for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in the memory 802 or transmitted through the communication component 805. The audio assembly further comprises at least one speaker for outputting audio signals. The I/O interface 804 provides an interface between the processor 801 and other interface modules, which may be a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 805 is configured to perform wired or wireless communication between the workflow engine circulation device 800 and other devices that support circulation in a non-routing direction. Wireless communication, such as Wi-Fi, bluetooth, near field communication (Near FieldCommunication, NFC for short), 2G, 3G or 4G, or a combination of one or more thereof, the respective communication component 805 may thus comprise: wi-Fi module, bluetooth module, NFC module.
In an exemplary embodiment, the workflow engine circulation device 800 supporting circulation in the non-routing direction may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), digital signal processors (DigitalSignal Processor, abbreviated as DSP), digital signal processing devices (Digital Signal Processing Device, abbreviated as DSPD), programmable logic devices (Programmable Logic Device, abbreviated as PLD), field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), controllers, microcontrollers, microprocessors, or other electronic components for performing the above-described workflow engine circulation method supporting circulation in the non-routing direction.
In another exemplary embodiment, a computer readable storage medium is also provided, comprising program instructions which, when executed by a processor, implement the steps of the above-described workflow engine circulation method supporting circulation in a non-routing direction. For example, the computer readable storage medium may be the memory 802 including program instructions described above that are executable by the processor 801 of the workflow engine circulation device 800 supporting non-routing direction circulation to perform the workflow engine circulation method supporting non-routing direction circulation described above.
Example 6:
corresponding to the above method embodiment, a readable storage medium is further provided in this embodiment, and a readable storage medium described below and a workflow engine circulation method supporting circulation in a non-routing direction described above may be referred to correspondingly.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the workflow engine circulation method of the above method embodiment supporting circulation in a non-routing direction.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, and the like.
The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (8)
1. A workflow engine circulation method supporting circulation in a non-routing direction, comprising:
acquiring node information, route information and pointing relation between nodes and routes of all nodes to generate model data of each node;
determining a current node where a service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements, wherein the circulation records comprise: all the node lists which flow, the staff lists which are processed, the staff lists which are not processed, the reader lists, the route lists, the node sequence list which is already flowing in the current route, the next route list with branch nodes and the last route list;
obtaining a node to be circulated of the service according to the service circulation demand, and obtaining model data of the node to be circulated;
analyzing the model data of the current node and the model data of the node to be circulated to obtain the service circulation type, comprising the following steps:
analyzing the circulation record of the service to obtain a first node list in which the service is circulated, a second node list to be circulated and all sponsors in the first node list;
obtaining a sponsor of the node to be circulated according to the model data of the node to be circulated;
if the node to be circulated is in the first node list, the service circulation type is returned;
if the sponsor of the node to be circulated is a sponsor in the first node list, the service circulation type is taken back;
if the node to be circulated is in the second node list, judging whether the node to be circulated is the node which is ordered to be first in the second node flow list:
if yes, the service circulation type is circulation; otherwise, the service flow type is jump;
judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type.
2. The workflow engine circulation method supporting circulation in a non-routing direction according to claim 1, wherein judging whether a service flows to a node to be circulated according to a circulation record of a current node and a preset condition of a service circulation type, when the service circulation type is a return, comprises:
acquiring the type of the current node:
if the type of the current node is a single handling node, judging whether the current node has a same-level branch node or not:
if yes, acquiring a starting node and all peer branch nodes of the current node from the circulation record;
judging whether the node to be circulated is a starting node of a same-level branch node or not:
if yes, the service flow is transferred to the node to be transferred, and the service handling authority of all the same-level branch nodes is cancelled and the service handling authority of the current sponsor of the current node is ended.
3. The workflow engine circulation method supporting circulation in a non-routing direction according to claim 1, wherein judging whether a service flows to a node to be circulated according to a circulation record of a current node and a preset condition of a service circulation type, when the service circulation type is a return, further comprising:
if the current node is a multi-person handling node, acquiring the last sponsor of the current node;
and designating the last sponsor as the sponsor of the node to be circulated, and ending the business handling authority of the current sponsor of the current node.
4. The method for forwarding the workflow engine supporting forwarding in the non-routing direction according to claim 1, further comprising, after forwarding the service flow to the node to be forwarded:
updating the node to be circulated as the current node;
and updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
5. A workflow engine circulation device supporting circulation in a non-routing direction, comprising:
a first acquisition module: the method comprises the steps of obtaining node information, route information and the pointing relation between nodes and routes of all nodes to generate model data of each node;
and an extraction module: the method is used for determining the current node where the service is located, acquiring model data of the current node and service circulation requirements, and extracting circulation records of the service from the service circulation requirements, wherein the circulation records comprise: all the node lists which flow, the staff lists which are processed, the staff lists which are not processed, the reader lists, the route lists, the node sequence list which is already flowing in the current route, the next route list with branch nodes and the last route list;
and a second acquisition module: the method comprises the steps of obtaining a node to be circulated of a service according to the service circulation requirement, and obtaining model data of the node to be circulated;
and an analysis module: the method for analyzing the model data of the current node and the model data of the node to be circulated to obtain the service circulation type comprises the following steps:
analyzing the circulation record of the service to obtain a first node list in which the service is circulated, a second node list to be circulated and all sponsors in the first node list;
obtaining a sponsor of the node to be circulated according to the model data of the node to be circulated;
if the node to be circulated is in the first node list, the service circulation type is returned;
if the sponsor of the node to be circulated is a sponsor in the first node list, the service circulation type is taken back;
if the node to be circulated is in the second node list, judging whether the node to be circulated is the node which is ordered to be first in the second node flow list:
if yes, the service circulation type is circulation; otherwise, the service flow type is jump;
and a judging module: and judging whether the service flows to the node to be circulated or not according to the circulation record of the current node and the preset condition of the service circulation type.
6. The workflow engine circulation device supporting circulation in a non-routing direction of claim 5, wherein the judgment module comprises:
a second acquisition unit: when the service flow type is returned, the type of the current node is acquired:
fourth judgment unit: if the type of the current node is a single handling node, judging whether the current node has a same-level branch node or not:
if yes, acquiring a starting node and all peer branch nodes of the current node from the circulation record;
fifth judging unit: the starting node is used for judging whether the node to be circulated is a peer branch node or not:
if yes, the service flow is transferred to the node to be transferred, and the service handling authority of all the same-level branch nodes is cancelled and the service handling authority of the current sponsor of the current node is ended.
7. The workflow engine circulation device supporting circulation in a non-routing direction of claim 5, wherein the judgment module further comprises:
a third acquisition unit: if the current node is a multi-person handling node, acquiring the last sponsor of the current node;
and a processing unit: and designating the last sponsor as the sponsor of the node to be circulated, and ending the business handling authority of the current sponsor of the current node.
8. The workflow engine forwarding device supporting forwarding in a non-routing direction of claim 5 further comprising, after forwarding the traffic to the node to be forwarded:
and an updating module: the method comprises the steps of updating a node to be circulated into a current node;
and an activation module: the method is used for updating the circulation record, the sponsor and the same-level branch node of the current node according to the model data of the current node, and activating the same-level branch node of the current node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310636385.XA CN116402474B (en) | 2023-06-01 | 2023-06-01 | Workflow engine circulation method and device supporting circulation in non-routing direction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310636385.XA CN116402474B (en) | 2023-06-01 | 2023-06-01 | Workflow engine circulation method and device supporting circulation in non-routing direction |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116402474A CN116402474A (en) | 2023-07-07 |
| CN116402474B true CN116402474B (en) | 2023-09-05 |
Family
ID=87007929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310636385.XA Active CN116402474B (en) | 2023-06-01 | 2023-06-01 | Workflow engine circulation method and device supporting circulation in non-routing direction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116402474B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103617066A (en) * | 2013-12-16 | 2014-03-05 | 中国农业银行股份有限公司 | Workflow engine and implementation method thereof |
| CN109636306A (en) * | 2018-10-29 | 2019-04-16 | 平安医疗健康管理股份有限公司 | Node-flow shifting method, device, terminal and storage medium |
| CN112685017A (en) * | 2020-12-31 | 2021-04-20 | 江苏元图信息技术有限公司 | Workflow engine facing mobile internet |
| CN114663177A (en) * | 2022-03-03 | 2022-06-24 | 北京城市网邻信息技术有限公司 | State change control method, device, electronic equipment and storage medium |
| CN115907683A (en) * | 2022-12-19 | 2023-04-04 | 国泰君安证券股份有限公司 | Realization system and method of workflow engine based on financial product management |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190318283A1 (en) * | 2018-04-12 | 2019-10-17 | Crosswind Communications | System and method for adaptively executing user routines based on user interactions |
-
2023
- 2023-06-01 CN CN202310636385.XA patent/CN116402474B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103617066A (en) * | 2013-12-16 | 2014-03-05 | 中国农业银行股份有限公司 | Workflow engine and implementation method thereof |
| CN109636306A (en) * | 2018-10-29 | 2019-04-16 | 平安医疗健康管理股份有限公司 | Node-flow shifting method, device, terminal and storage medium |
| CN112685017A (en) * | 2020-12-31 | 2021-04-20 | 江苏元图信息技术有限公司 | Workflow engine facing mobile internet |
| CN114663177A (en) * | 2022-03-03 | 2022-06-24 | 北京城市网邻信息技术有限公司 | State change control method, device, electronic equipment and storage medium |
| CN115907683A (en) * | 2022-12-19 | 2023-04-04 | 国泰君安证券股份有限公司 | Realization system and method of workflow engine based on financial product management |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116402474A (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150281138A1 (en) | Keyword based automatic reply generation in a messaging application | |
| JP2005346543A (en) | Method of inheriting community, community management apparatus, and community management program | |
| CN106681698B (en) | Dynamic list generation method and device | |
| CN1964358A (en) | Messaging service interoperability methods and related devices | |
| CN111144320A (en) | Image processing method and device, computer equipment and storage medium | |
| CN104765596A (en) | Request handling method and device | |
| CN110941779A (en) | Page loading method and device, storage medium and electronic equipment | |
| JP2020021485A (en) | Method, system, and non-transitory computer-readable recording medium for searching for non-text using text in conversation | |
| CN114676205A (en) | Event information processing method and device | |
| CN111144837A (en) | Flow arrangement method and device, storage medium and electronic equipment | |
| CN116402474B (en) | Workflow engine circulation method and device supporting circulation in non-routing direction | |
| CN111984264B (en) | Static library generation method and device | |
| CN116088829A (en) | Data processing method, device, storage medium and equipment | |
| CN115951923A (en) | Subscription event management method and related product | |
| CN115660591A (en) | Process configuration method, system, electronic device and medium for business approval | |
| CN110875960A (en) | Address book updating method, server and terminal | |
| CN107113557B (en) | Information processing method and device | |
| CN109274808B (en) | Address book information management method and system, electronic equipment and storage medium | |
| US11277300B2 (en) | Method and apparatus for outputting information | |
| CN104486487A (en) | Contact-photo editing method and terminal | |
| CN103731798A (en) | Method and system for ordering telecommunication businesses | |
| CN109710579B (en) | Log processing method, server and article system | |
| JP6178119B2 (en) | Data migration system and data migration method | |
| CN104462219A (en) | Information agent interface and application system based on information agent interface | |
| US9940554B2 (en) | Data analysis and management methods and systems for social networks |
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 |