CN106897810B

CN106897810B - Business processing method and system, workflow engine and system and business system

Info

Publication number: CN106897810B
Application number: CN201510959011.7A
Authority: CN
Inventors: 朱峰
Original assignee: Beijing Qihoo Technology Co Ltd; Qizhi Software Beijing Co Ltd
Current assignee: Beijing Qihoo Technology Co Ltd
Priority date: 2015-12-17
Filing date: 2015-12-17
Publication date: 2021-07-13
Anticipated expiration: 2035-12-17
Also published as: CN106897810A

Abstract

The embodiment of the invention discloses a service processing method and system, a workflow engine and system and a service system, wherein the method comprises the following steps: receiving a flow instance creating request, and acquiring a flow ID corresponding to a system ID in the creating request from a workflow database; acquiring node information of a start node in a workflow from a workflow database, wherein the node information comprises a node ID and parameter values of node attributes; returning node information of the node to be executed to the service system by taking the starting node as the node to be executed; the node to be executed is preset in a service system; and receiving an execution result message returned by the service system, acquiring node information of the destination node from the workflow database, and executing the operation of returning the node information of the destination node to the service system by taking the destination node as a node to be executed. The embodiment of the invention can improve the configurability and reusability of the workflow.

Description

Business processing method and system, workflow engine and system and business system

Technical Field

The invention relates to a data processing technology, in particular to a business processing method and system, a workflow engine and system and a business system.

Background

The workflow refers to the sequence of the flow direction of the work items, including the work links, steps and procedures in the actual working process. In the traditional implementation mode of the business process, many companies adopt a mode of paper form and manual transmission, the work efficiency is very low due to the fact that the signature is approved at the first level and the second level, and the function of the statistical statement cannot be achieved.

With the development and popularization of computer technology, network technology and database technology, various enterprises and personal informatization applications emerge endlessly, and workflows (WorkFlow) come into force. A workflow is a computational model of a workflow, i.e., the logic and rules of how the work in the workflow is organized together in tandem are represented in a computer in an appropriate model and computed. The main problems to be solved by the workflow are: to achieve a business goal, documents, information or tasks are automatically transferred between multiple participants using computers according to certain predefined rules. By adopting the workflow software, a user only needs to fill in related forms on a computer, tasks can be automatically carried out downwards according to a defined flow, a next-level approver can receive related data and can modify, track, manage, query, count, print and the like according to needs, and compared with the traditional implementation mode of the workflow, the efficiency is greatly improved, the knowledge management is realized, and the core competitiveness of a company is improved.

However, in the course of implementing the present invention, the inventors found that: in the existing business systems such as sales and the like, the work flow is directly configured in a hard coding mode, and once the configuration is finished, the amount of business change caused by the adjustment of the work flow is huge because the work flow is a set of hard codes directly configured in the business system.

Disclosure of Invention

The embodiment of the invention aims to solve the technical problem that: a business processing method and system, a workflow engine and system and a business system are provided to improve the configurability and reusability of workflow.

In order to solve the above technical problem, according to an aspect of an embodiment of the present invention, a service processing method is provided, including:

responding to a received flow instance creating request sent by a service system, and acquiring a flow ID corresponding to a system ID in the creating request from a workflow database; the system ID uniquely identifies the service system, and the process ID uniquely identifies one work process;

acquiring node information of a starting node in a workflow identified by the flow ID from a workflow database, wherein the node information comprises the node ID and parameter values of node attributes;

returning node information of the node to be executed to a service system by taking a starting node as the node to be executed so as to execute the node to be executed by the service system; the node to be executed is preset in the service system;

and in response to receiving an execution result message returned by the node to be executed after the execution of the service system is finished, acquiring a destination node of which a source node is a circulation condition of the node to be executed from a workflow database, acquiring node information of the destination node from the workflow database, and executing the operation of returning the node information of the node to be executed to the service system by taking the destination node as the node to be executed.

In a service processing method of another embodiment, the executing, by the service system, the node to be executed includes:

and the service system acquires and executes the node to be executed from the service system according to the node information of the node to be executed, performs information interaction with the user, processes data submitted by the user, and records the data submitted by the user and the executed operation.

In the service processing method of another embodiment, the method further includes:

and after the business system finishes processing the data submitted by the user, acquiring and storing an execution data result, and returning an execution result message to the workflow engine.

In the service processing method according to another embodiment, the workflow database includes a flow information table for storing flow basic information of each workflow, and the flow basic information of each workflow includes a system ID and a flow ID;

the obtaining of the process ID corresponding to the system ID in the creation request from the workflow database includes: and inquiring the process ID corresponding to the system ID in the creation request from a process information table.

In the service processing method according to another embodiment, the workflow database includes a node information table for storing node basis information of each node, where the node basis information of each node includes a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute;

the obtaining node information of a start node in a workflow identified by the flow ID from a workflow database includes: acquiring all node basic information including the corresponding process ID from a node information table; acquiring parameter values of node types from all the node basic information as the node basic information of a starting node; and acquiring the node ID and the parameter value of the node attribute from the node basic information of the starting node by taking the parameter value of the node type as the parameter value of the starting node.

In the traffic processing method of another embodiment, the parameter values of the node types include: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node;

the node attribute comprises a service model or a circulation condition corresponding to the node type, the service model comprises a service logic function unit, a task execution role and a processing personnel, and the circulation condition comprises a source node, a destination node and a condition expression;

when the parameter value of the node type is a circulation condition node, a branch node or an aggregation node, the corresponding node attribute is a circulation condition, and the parameter value of the node attribute specifically is as follows: a source node ID, a destination node ID and a specific conditional expression;

when the node type value is a start node, an end node or a common node, the corresponding node attribute is a service model, and the parameter values of the node attribute specifically are as follows: the role ID and the user ID of the handler are executed.

According to another aspect of the embodiments of the present invention, there is provided a workflow engine, including:

a first receiving unit, configured to receive a message sent by a service system;

the first obtaining unit is used for obtaining a process ID corresponding to the system ID in the creating request from a workflow database when the first receiving unit receives the process instance creating request sent by the service system; the system ID uniquely identifies the service system, and the process ID uniquely identifies one work process;

a second obtaining unit, configured to obtain, from a workflow database, node information of a start node in a workflow identified by the flow ID, where the node information includes the node ID and a parameter value of a node attribute;

a first sending unit, configured to return node information of a node to be executed to a service system with a start node as the node to be executed, so that the service system executes the node to be executed; the node to be executed is preset in the service system;

and the third obtaining unit is used for obtaining a destination node of which a source node is a circulation condition of the node to be executed from the workflow database when the first receiving unit receives an execution result message returned by the node to be executed after the execution of the service system is finished, obtaining node information of the destination node from the workflow database, and executing the operation of returning the node information of the node to be executed to the service system by taking the destination node as the node to be executed.

According to another aspect of the embodiments of the present invention, there is provided a service system, including:

a second sending unit, configured to send a process instance creation request to a workflow engine, where the creation request includes a system ID; wherein the system ID uniquely identifies the business system; returning an execution result message to the workflow engine;

the second receiving unit is used for receiving the node information of the node to be executed returned by the workflow engine;

the service processing unit is used for acquiring and executing the node to be executed from the node library according to the node information of the node to be executed, performing information interaction with the user, processing data submitted by the user, and recording the data submitted by the user and the executed operation in the service database; after the data submitted by the user is processed, acquiring an execution data result and storing the execution data result in a service database, and indicating a second sending unit to return an execution result message to the workflow engine; wherein each node constituting the workflow is preset in the node library.

According to another aspect of the embodiments of the present invention, there is provided a workflow system, which is characterized by comprising the workflow engine according to the above embodiments of the present invention

According to another aspect of the embodiments of the present invention, a business processing system is provided, which includes the workflow engine according to any of the above embodiments of the present invention and the business system according to any of the above embodiments of the present invention. Based on the service processing method and system, the workflow engine and system, and the service system provided in the above embodiments of the present invention, each node constituting the workflow is preset in the service system, the node information, including the node ID and the parameter value of the node attribute, is stored in the workflow database, and when the service system calls the workflow, the node information may be sequentially queried from the workflow database according to the flow path by a device, such as the workflow engine, and sent to the service system, and the service system executes the corresponding node. In the embodiment of the invention, each node required by the workflow is independently set, the setting of the node and the configuration of the attribute parameter are independent processes, and the workflow engine and the service system do not belong to the same system on the coding, thereby realizing the decoupling of the code level; in data storage, the workflow database only stores the flow related information but not the business entity data, the business system only stores the business entity data but not the flow related information, decoupling of a data layer is achieved, when the business entity data changes, the workflow does not need to be changed, and configurability and reusability of the workflow are improved.

The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.

The invention will be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:

fig. 1 is a flowchart of an embodiment of a service processing method of the present invention.

Fig. 2 is a flowchart of another embodiment of a service processing method according to the present invention.

Fig. 3 is a flowchart of a service processing method according to another embodiment of the present invention.

Fig. 4 is a flowchart of a service processing method according to another embodiment of the present invention.

Fig. 5 is a flowchart of a service processing method according to another embodiment of the present invention.

FIG. 6 is a schematic structural diagram of an embodiment of a workflow engine of the present invention.

FIG. 7 is a schematic structural diagram of another embodiment of a workflow engine of the present invention.

Fig. 8 is a schematic structural diagram of an embodiment of the service system of the present invention.

Fig. 9 is a schematic structural diagram of another embodiment of the service system of the present invention.

Fig. 10 is a schematic structural diagram of an embodiment of the workflow system of the present invention.

Fig. 11 is a schematic structural diagram of an embodiment of a service processing system of the present invention.

Detailed Description

Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.

Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

Fig. 1 is a flowchart of an embodiment of a service processing method of the present invention. The service processing method of each embodiment of the present invention may be specifically executed by a device outside the service system, for example, a workflow engine. As shown in fig. 1, the service processing method of this embodiment includes:

and 102, responding to a received flow instance creating request sent by the service system, and acquiring a flow ID corresponding to the system ID in the creating request from a workflow database.

The system ID uniquely identifies one service system, and the process ID uniquely identifies one work process.

In a specific example of the present invention, a flow information table may be stored in the workflow database to store flow basic information of each workflow, and the flow basic information of each workflow may include a system ID and a flow ID, and may further include information such as a creation time, a last modification time, and a flow name of the workflow. The process ID corresponding to the system ID in the creation request may be queried from the process information table.

The workflow is a series of mutually connected and automatically performed business activities or tasks; the whole business process can be regarded as a river, and the river water flowing through the river is a form to be audited.

104, acquiring node information of a starting node in a workflow identified by a flow ID in the creation request from a workflow database, wherein the node information comprises the node ID and parameter values of node attributes; and performs operation 106 with the start node as the node to be executed.

In a specific example of the present invention, a node information table may be stored in the workflow database, and is used to store node basic information of each node, where the node basic information of each node may include a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute, and may further include information such as creation time and last modification time of the node. The node information of the start node may be acquired as follows: acquiring all node basic information including the process ID from a node information table; acquiring parameter values of node types from all the node basic information as the node basic information of a starting node; and acquiring the node ID and the parameter value of the node attribute from the node basic information of the starting node by taking the parameter value of the node type as the parameter value of the starting node.

The parameter values of the node type may include, for example: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node; the node attribute comprises a service model or a circulation condition corresponding to the node type, the service model can comprise a service logic function unit, a task execution role and a processing personnel, and the circulation condition can comprise a source node, a destination node and a condition expression.

The starting node and the ending node are special nodes and can fix an initialization task or end an ending task. In a workflow, there may be multiple end nodes with only one start node.

The flow condition node is a vector node with conditions, and the default condition is true. The conditional judgment of this node finally generates true or false to determine whether the flow can be transferred to the next node in the workflow. The common nodes are generally nodes binding a data model, and generally can present data in forms of operable forms and the like, and are used for man-machine interaction, and users can examine and approve the forms and the like. The aggregation node is also a special node for converging branches in the workflow, and the node is a node for binding a data model and automatically executing. The function of the branch node is to realize the parallel flow of the workflow, and because of the functional characteristics of the branch node, at least two outgoing connecting lines are determined below the branch node. In one workflow, there may be a plurality of flow condition nodes, normal nodes, branch nodes, aggregation nodes.

When the parameter value of the node type is a circulation condition node, a branch node or an aggregation node, the corresponding node attribute is a circulation condition, and the parameter value of the node attribute specifically is as follows: a source node ID, a destination node ID, and a specific conditional expression.

When the node type value is a start node, an end node or a common node, the corresponding node attribute is a service model, and the parameter values of the node attribute are specifically as follows: the role ID and the user ID of the handler are executed.

In a specific example of the present invention, the flow information table and the node information table may be generated by a device, for example, a workflow designer, when configuring parameter values for attribute parameters of each node constituting a workflow in a business system, where the attribute parameters include a node ID parameter, a node type, and a node attribute.

And 106, returning the node information of the node to be executed to the service system so as to execute the node to be executed by the service system.

Wherein, each node to be executed, namely each node forming the workflow, is preset in the service system.

Illustratively, the service system executes the node to be executed, namely: the service system acquires and executes the node to be executed from the service system according to the node information of the node to be executed, performs information interaction with the user, processes the data submitted by the user, and can selectively record the data submitted by the user and the executed operation. In addition, after the business system finishes processing the data submitted by the user, the data can be stored after the execution data result is obtained, and the execution result message is returned to the workflow engine.

And 108, in response to receiving an execution result message returned by the node to be executed after the execution of the service system is finished, acquiring the destination node of the circulation condition of the source node as the node to be executed from the workflow database.

Based on the example in operation 104, the node basic information of the corresponding flow ID may be queried from the node information table, and the source node ID may be the destination node ID in the parameter values of the flow condition of the node ID to be executed.

And 110, acquiring node information of the destination node from the workflow database, and executing the operation 106 by taking the destination node as a node to be executed.

Based on the service processing method provided by the above embodiment of the present invention, each node constituting the workflow is preset in the service system, the node information is stored in the workflow database, when the service system calls the workflow, the node information may be sequentially queried from the workflow database according to the flow path by a device, such as a workflow engine, and sent to the service system, and the service system executes the corresponding node. In the embodiment of the invention, each node required by the workflow is independently set, the setting of the node and the configuration of the attribute parameter are independent processes, and the workflow engine and the service system do not belong to the same system on the coding, thereby realizing the decoupling of the code level; in data storage, the workflow database only stores the flow related information but not the business entity data, the business system only stores the business entity data but not the flow related information, decoupling of a data layer is achieved, when the business entity data changes, the workflow does not need to be changed, and configurability and reusability of the workflow are improved.

In another embodiment of the service processing method of the present invention, if the parameter value of the flow condition further includes a specific conditional expression, correspondingly, the execution result message received in operation 108 further includes a value submitted by the user in the process of executing the node to be executed, for example, the number of leave-asking days submitted by the user in the leave-asking process; then in operation 108, the value submitted by the user may be calculated as the value of the free variable in the specific conditional expression, and the destination node ID is determined according to the calculation result, so as to obtain the destination node ID (i.e., the next node ID). For example, in the leave-asking process, the leave-asking conditions are: if the leave requests for less than five days only need to be examined and approved by the manager, and if the leave requests for more than five days need to be examined and approved by the general supervision, the leave requests days submitted by the user are used as the values of the free variables in the specific conditional expression for calculation, so that whether the next node is examined and approved by the manager or the general supervision can be known.

Fig. 2 is a flowchart of a service processing method according to an embodiment of the present invention. Compared with the embodiment shown in fig. 1, the embodiment may further include, before the flow of the embodiment shown in fig. 1:

202, the service system receives an instance creation instruction sent by the user after logging in, where the instance creation instruction includes a user ID.

Wherein the user ID uniquely identifies a user registered in the service system.

204, the service system queries the execution role ID corresponding to the user ID in the instance creation indication from the user information base, and sends a creation request to the workflow engine, where the creation request includes the system ID, the execution role ID, and the user ID.

In addition, after operation 104, further comprising:

and 206, performing authority authentication on the execution role ID and the user ID in the creation request according to the parameter value of the node attribute of the starting node.

Only when the execution role ID and the user ID in the creation request pass the authority authentication, operation 106 is executed, and the node information of the start node is returned to the service system. Otherwise, other operations of embodiments of the present invention are not performed.

Fig. 3 is a flowchart of a service processing method according to another embodiment of the present invention. As shown in fig. 3, the service processing method of this embodiment includes:

and 302, in response to receiving a flow instance creation request sent by the service system, obtaining a flow ID corresponding to the system ID in the creation request from the workflow database.

And 304, creating a workflow instance of the workflow identified by the flow ID, and distributing the flow instance ID to the workflow instance.

Wherein the process instance ID uniquely identifies a workflow instance.

And 306, recording the flow instance information of the workflow identified by the flow ID in the flow instance table of the workflow database, and setting the flow instance state as unfinished.

The process instance information may include a process instance ID, a process ID of a workflow to which the workflow instance belongs, a system ID, and a process instance status, where the process instance status includes incomplete or completed. In addition, the process instance information may also include information such as creation time, last modification time, whether the state of the process instance is normal, and the like of the process instance.

308, acquiring node information of a starting node in the workflow identified by the flow ID in the creation request from the workflow database, wherein the node information comprises the node ID and the parameter value of the node attribute; and performs operation 310 with the start node as the node to be executed.

And 310, returning the node information of the node to be executed to the service system so as to execute the node to be executed by the service system.

And 312, in response to receiving an execution result message returned by the node to be executed after the execution of the service system is completed, identifying whether the node to be executed is a node to be finished according to the node information of the node to be executed.

If the node to be executed is not an end node, operation 314 is performed. If the node to be executed is an end node, operation 316 is performed.

And 314, acquiring the destination node of the circulation condition of the source node as the node to be executed from the workflow database.

Thereafter, the subsequent operations of the present embodiment are not performed.

And 316, changing the state of the process instance in the process instance information to be completed.

Fig. 4 is a flowchart of a service processing method according to another embodiment of the present invention. As shown in fig. 4, compared with the embodiment shown in fig. 3, in this embodiment, after operation 308, the method further includes: 402, activating a start node, changing the node state of the start node into an activated state to be processed, and recording the node instance information of the start node in an instance node table of a workflow database, wherein the node instance information comprises a process instance ID, a node ID of the start node, a node state, parameter values of node attributes, and information such as creation time and final modification time of the node instance information; the node states include: inactive, pending, in progress, or complete.

After operation 310, further comprising: 404, the node status of the start node is changed to in-process.

Further, referring to fig. 4 again, in another embodiment of the service processing method of the present invention, after operation 314, the following steps may also be performed:

406, the destination node is activated, the destination node is changed to the node to be executed, and the node status of the source node is changed to done.

And 408, changing the node state of the node to be executed into the activated node to be processed, and recording the node instance information of the node to be executed in an instance node table of the workflow database, wherein the node instance information comprises the flow instance ID, the node ID of the node to be executed, the node state and the parameter value of the node attribute.

In addition, in a further embodiment of the service processing method of the present invention, after operation 406, if an execution failure message returned by the service system that the node to be executed is not successfully executed is received, the source node is changed to the node to be executed, the node status of the source node is changed to activated node to be processed, and then operation 310 of returning node information of the node to be executed to the service system is performed.

In an optional example of the present invention, the business model may further include a backtracking processing mode, and a parameter value of the backtracking processing mode is specifically whether the same processing person is required to process a backtracking task. In this example, the node information of the node to be executed returned to the service system in operation 310 further includes a parameter value of the backtracking processing mode, so that the service system determines the user ID of the processing person executing the task according to the parameter value of the backtracking processing mode, and the reasonability of task allocation and the high efficiency of the process are achieved.

In addition, in another embodiment of the service processing method of the present invention, after the node information of the node to be executed is returned to the service system through operation 310, the method may further include: and the service system sends a processing task notification message to the execution role ID in the node information of the node to be executed and the user ID of the processing personnel so as to facilitate the corresponding user to log in and then process the task.

After the user logs in, through the operation of the following embodiments of the present invention, it can be seen that the task needs to be processed by the user:

after receiving the task notification message, the user login service system sends a task request message, wherein the task request message comprises a user ID of a requesting user and an assigned execution role ID;

the service system forwards the task request message to a workflow engine;

the workflow engine inquires an example node table in a workflow database, acquires a node which is activated and to be processed and comprises an execution role ID and a user ID in a task request message, and returns the acquired node ID of the node to a service system;

and the service system displays the tasks in the corresponding nodes according to the node ID sent by the workflow engine so as to facilitate the requesting user to process the task.

In another embodiment of the service processing method of the present invention, the service model may further include a task allocation policy, and a parameter value of the task allocation policy is specifically a type of the task allocation policy, and may include, for example, an assignment type, a contention type, a dynamic session type, or an average allocation type.

If the type of the configuration task allocation strategy is an assignment type, configuring specific execution role IDs and user IDs of processing personnel in parameter values of node attributes;

if the type of the configuration task allocation strategy is competitive, configuring a user ID of a specific executive role ID which is not configured with a processing person in the parameter values of the node attributes;

if the type of the configuration task allocation strategy is a dynamic countersigning type, configuring a specific execution role ID in the parameter values of the node attributes, and configuring the parameter values of the processing personnel as the processing personnel with the highest task execution efficiency in the execution role ID;

if the type of the configuration task allocation strategy is an average allocation type, a specific execution role ID is configured in the parameter values of the node attributes, and the parameter values of the processing personnel are configured as the processing personnel determined in the execution role ID in a sequential rotation mode.

When the service model may further include a task allocation policy, the service system displays that the task in the corresponding node is specifically, the service system obtains a parameter value of the service model from the node information including the node ID according to the node ID sent by the workflow engine, and determines a user ID for processing the task according to the parameter value of the service model; and displaying the acquired tasks in the nodes to the user ID for processing the task so as to facilitate the user to process.

Fig. 5 is a flowchart of a service processing method according to another embodiment of the present invention. As shown in fig. 5, compared with the service processing method according to each of the above embodiments of the present invention, in this embodiment, after the service displays the acquired task in the node to the user ID for processing the current task, the method further includes:

502, in response to receiving a process instance progress display request sent by a user processing the task, the business system forwards the process instance progress display request to the workflow engine, where the process instance progress display request includes a process instance ID and a user ID.

And 504, the workflow engine acquires the corresponding process ID, the node information table related to the process ID and the node instance information related to the process ID from the workflow database according to the process instance ID, and returns the corresponding process ID, the node information table related to the process ID and the node instance information to the service system.

And 506, the business system displays the current workflow path and workflow instance progress according to the node information table and the node instance information returned by the workflow engine, and acquires and displays the user ID of the processing task and the operation information performed by the user on each node representing the workflow instance progress.

In the service processing method according to each embodiment of the present invention, the service system may specifically perform information interaction with the workflow engine by calling an Application Program Interface (API) of the workflow engine that is coupled and configured, for example, by using a hypertext transfer protocol (HTTP).

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

FIG. 6 is a schematic structural diagram of an embodiment of a workflow engine of the present invention. The workflow engine of this embodiment can be used to implement the above-described embodiments of the business processing method of the present invention. As shown in fig. 6, the workflow engine of this embodiment includes a first receiving unit, a first obtaining unit, a second obtaining unit, a first sending unit, and a third obtaining unit. Wherein:

the first receiving unit is used for receiving the message sent by the service system.

The first obtaining unit is used for obtaining the flow ID corresponding to the system ID in the creating request from the workflow database when the first receiving unit receives the flow instance creating request sent by the service system. The system ID uniquely identifies one service system, and the process ID uniquely identifies one work process.

And the second acquisition unit is used for acquiring node information of a starting node in the workflow identified by the flow ID in the creation request from the workflow database, wherein the node information comprises the node ID and the parameter value of the node attribute.

And the first sending unit is used for returning the node information of the node to be executed to the service system by taking the starting node as the node to be executed so as to execute the node to be executed by the service system. Wherein, the node to be executed is: each node constituting the workflow is preset in the service system.

And the third acquiring unit is used for acquiring a destination node of which the source node is the circulation condition of the node to be executed from the workflow database when the first receiving unit receives an execution result message returned by the node to be executed after the execution of the service system is finished, acquiring node information of the destination node from the workflow database, and executing the operation of returning the node information of the node to be executed to the service system by using the destination node as the node to be executed.

Based on the workflow engine provided in the above embodiment of the present invention, each node constituting the workflow is preset in the service system, the node information, including the node ID and the parameter value of the node attribute, is stored in the workflow database, when the service system calls the workflow, the workflow engine sequentially queries the node information from the workflow database according to the flow path and sends the node information to the service system, and the service system executes the corresponding node. In the embodiment of the invention, each node required by the workflow is independently set, the setting of the node and the configuration of the attribute parameter are independent processes, and the workflow engine and the service system do not belong to the same system on the coding, thereby realizing the decoupling of the code level; in data storage, the workflow database only stores the flow related information but not the business entity data, the business system only stores the business entity data but not the flow related information, decoupling of a data layer is achieved, when the business entity data changes, the workflow does not need to be changed, and configurability and reusability of the workflow are improved.

As a specific example of the embodiment of the workflow engine, the workflow database may include a flow information table for storing flow basic information of each workflow, where the flow basic information of each workflow includes a system ID and a flow ID. Correspondingly, the first obtaining unit specifically queries the flow ID corresponding to the system ID in the creation request from the flow information table.

As another specific example of the workflow engine embodiment, the workflow database may include a node information table for storing node basis information of each node, where the node basis information of each node includes a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute. Correspondingly, the second obtaining unit specifically obtains all the node basic information including the corresponding process ID from the node information table; acquiring parameter values of the node types from all the node basic information as the node basic information of the starting node; and acquiring the node ID and the parameter value of the node attribute from the node basic information of the starting node by taking the parameter value of the node type as the parameter value of the starting node.

Specifically, the parameter values of the node type may include: a start node, an end node, a flow condition node, a normal node, a branch node, or an aggregation node. The node attribute may include a service model or a flow condition corresponding to the node type, the service model includes a service logic function unit, a task execution role, and a processing person, and the flow condition includes a source node, a destination node, and a conditional expression.

In a specific example, the flow information table and the node information table may be generated by a device, such as a workflow designer, when configuring parameter values for attribute parameters of each node constituting a workflow in a business system, where the attribute parameters include a node ID parameter, a node type, and a node attribute.

As another specific example of the workflow engine embodiment, when the third obtaining unit obtains, from the workflow database, the source node as the destination node of the circulation condition of the node to be executed, the node base information of the corresponding flow ID may be specifically queried from the node information table, and the source node ID is the destination node ID in the parameter values of the circulation condition of the node ID to be executed.

In a further specific example, the parameter values of the flow conditions may further include specific conditional expressions, and the execution result message may further include values submitted by a user in the process of executing the node to be executed. When the third obtaining unit obtains the source node ID as the destination node ID in the parameter values of the flow condition of the node ID to be executed, the third obtaining unit specifically calculates the numerical value submitted by the user as the value of the free variable in the specific conditional expression, and determines the destination node ID according to the calculation result.

In addition, the business model may further include a task allocation policy, and the parameter value of the task allocation policy is specifically a type of the task allocation policy, and may include, for example, an assignment type, a competition type, a dynamic countersign type, or an average allocation type.

FIG. 7 is a schematic structural diagram of another embodiment of a workflow engine of the present invention. As shown in fig. 7, compared with the embodiment shown in fig. 6, the workflow engine of this embodiment further includes a flow instance management unit, configured to, after the first obtaining unit obtains the flow ID corresponding to the system ID in the creation request from the workflow database: creating a workflow instance of the workflow identified by the flow ID, and distributing the flow instance ID to the workflow instance; wherein, the process instance ID uniquely identifies a workflow instance; recording the process instance information of the workflow identified by the process ID in a process instance table of the workflow database, and setting the state of the process instance as unfinished; the process instance information includes a process instance ID, a process ID, a system ID, and a process instance status, which includes incomplete or completed.

Further, referring to fig. 7, in another embodiment of the workflow engine, the workflow engine may further include an identifying unit, configured to identify whether the node to be executed ends the node according to the node information of the node to be executed after the first receiving unit receives an execution result message returned by the node to be executed after the service system finishes executing the node to be executed. Accordingly, in this embodiment, the third obtaining unit specifically performs, according to the identification result of the identification unit, an operation of obtaining, from the workflow database, the destination node of the flow condition of the source node as the node to be executed when the node to be executed is not the end node. The flow instance management unit is further configured to change the state of the flow instance in the flow instance information to be completed when the node to be executed is the end node according to the identification result of the identification unit.

Further, referring to fig. 7 again, in yet another embodiment of the workflow engine, the workflow engine may further include a node instance management unit, configured to activate the start node after the second obtaining unit obtains node information of the start node in the workflow identified by the flow ID from the workflow database, change the node state of the start node into an activated pending state, and record node instance information of the start node in an instance node table of the workflow database, where the node instance information includes parameter values of the flow instance ID, the node ID of the start node, the node state, and the node attribute; the node states include: not activated, pending, in-process or completed; and after the first sending unit returns the node information of the node to be executed to the service system, changing the node state of the starting node into the processing.

In addition, in a further embodiment, the node instance management unit may be further configured to activate the destination node, change the destination node to the node to be executed, and change the node state of the source node to be completed after the third obtaining unit obtains the destination node of the circulation condition of the node to be executed from the workflow database; and changing the node state of the node to be executed into the activated node to be processed, and recording the node instance information of the node to be executed in an instance node table of the workflow database, wherein the node instance information comprises the flow instance ID, the node ID of the node to be executed, the node state and the parameter value of the node attribute.

Or, the node instance management unit may be further configured to, when the first receiving unit receives an execution failure message that the service system has not successfully executed the node to be executed, change the source node to the node to be executed, and change the node status of the source node to be activated to be processed, so that the first sending unit performs an operation of returning the node information of the node to be executed to the service system.

In another embodiment of the workflow engine, the business model may further include a backtracking processing mode, and the parameter values of the backtracking processing mode specifically include: whether the same processing personnel is required to handle the backtracking task. Correspondingly, the node information of the node to be executed, which is returned to the service system by the first sending unit, also includes a parameter value of the backtracking processing mode, so that the service system determines the user ID of the processing personnel executing the task according to the parameter value of the backtracking processing mode.

Referring again to FIG. 7, in a further embodiment of the workflow engine, the workflow engine further comprises a query unit. In this embodiment, the first receiving unit may be further configured to receive the task request message sent by the service system, where the task request message includes a user ID of the requesting user and an assigned execution role ID. Correspondingly, the query unit is used for querying the instance node table in the workflow database, and acquiring the node which is activated and to be processed and comprises the execution role ID and the user ID in the task request message. The first sending unit is further configured to return the node ID of the node acquired by the querying unit to the service system.

Referring again to fig. 7, in a further embodiment of the workflow engine, the workflow engine further comprises a fourth obtaining unit. In this embodiment, the first receiving unit may be further configured to receive a process instance progress display request sent by the service system, where the process instance progress display request includes a process instance ID and a user ID. The fourth obtaining unit is used for obtaining the corresponding flow ID, the node information table related to the flow ID and the node instance information related to the flow instance ID from the workflow database according to the flow instance ID in the flow instance progress display request. Correspondingly, the first sending unit may be further configured to return the node information table and the node instance information acquired by the fourth acquiring unit to the service system, so that the service system displays the current workflow path and the workflow instance progress according to the workflow path.

Fig. 8 is a schematic structural diagram of an embodiment of the service system of the present invention. The device of this embodiment can be used for implementing the corresponding functions of the service system in the above-mentioned service processing method embodiments of the present invention. As shown in fig. 8, the service system of this embodiment includes a second transmitting unit, a second receiving unit, and a service processing unit. Wherein:

and the second sending unit is used for sending a process instance creating request to the workflow engine, wherein the creating request comprises the system ID. Wherein, the system ID uniquely identifies a service system; and returning an execution result message to the workflow engine.

And the second receiving unit is used for receiving the node information of the node to be executed returned by the workflow engine.

The service processing unit is used for acquiring and executing the node to be executed from the node library according to the node information of the node to be executed, performing information interaction with the user, processing data submitted by the user, and recording the data submitted by the user and the executed operation in the service database; after the data submitted by the user is processed, acquiring an execution data result and storing the execution data result in a service database, and indicating a second sending unit to return an execution result message to the workflow engine; wherein, each node constituting the workflow is preset in the node library.

Based on the service system provided by the above embodiment of the present invention, preset nodes are stored in the service system, node information is stored in the workflow database, when the service system calls a workflow, the service system may sequentially query node information from the workflow database according to a flow path through a device, such as a workflow engine, and send the node information to the service system, and the service system executes a corresponding node. In the embodiment of the invention, each node required by the workflow is independently set, the setting of the node and the configuration of the attribute parameter are independent processes, and the workflow engine and the service system do not belong to the same system on the coding, thereby realizing the decoupling of the code level; in data storage, the workflow database only stores the flow related information but not the business entity data, the business system only stores the business entity data but not the flow related information, decoupling of a data layer is achieved, when the business entity data changes, the workflow does not need to be changed, and configurability and reusability of the workflow are improved.

In another embodiment of the service system of the present invention, the second sending unit may be further configured to send a processing task notification message to an execution role ID in the node information of the node to be executed and a user ID of a processing person, so that the corresponding user logs in and processes the task.

Fig. 9 is a schematic structural diagram of another embodiment of the service system of the present invention. As shown in fig. 9, compared with the embodiment shown in fig. 8, a human-computer interaction unit is further included in this embodiment. In this embodiment, the second receiving unit may be further configured to receive a task request message sent by the user, where the task request message is sent by the user login service system after receiving the task notification message, and the task request message includes a user ID of the requesting user and an assigned execution role ID; and receiving the node ID returned by the workflow engine after querying the instance node table in the workflow database. The second sending unit may be further operable to forward the task request message to the workflow engine. The man-machine interaction unit is used for displaying the tasks in the nodes identified by the node IDs received by the second receiving unit so that the requesting user can process the tasks.

Specifically, the human-computer interaction unit may obtain a parameter value of the service model from the node information including the node ID received by the second receiving unit, and determine the user ID for processing the task according to the parameter value of the service model; and displaying the acquired tasks in the nodes to the user ID for processing the task so as to facilitate the user to process.

Further, in another embodiment of the service system of the present invention, the second receiving unit may be further configured to receive a process instance progress display request sent by a user processing the task; and receiving the node information table and the node instance information returned by the workflow engine. Correspondingly, the second sending unit may be further configured to forward a process instance progress display request to the workflow engine, where the process instance progress display request includes a process instance ID and a user ID. The human-computer interaction unit can also be used for displaying the current workflow path and workflow instance progress according to the node information table and the node instance information returned by the workflow engine, and acquiring and displaying the user ID of the processing task and the operation information performed by the user on each node representing the workflow instance progress.

Referring again to fig. 9, in yet another embodiment of the service system of the present invention, any one or more of a node base, a service database, and a user information base may be further included. Wherein:

and the node library is used for storing all nodes forming the workflow.

And the business database is used for storing the data submitted by the user, the executed operation and the execution result data.

And the user information base is used for storing the user information of the registered user in the service system and executing the corresponding relation between the role ID and the user ID, and the user information comprises the user ID.

In addition, an API of the workflow engine may be further coupled and set in the service system in the embodiment of the present invention, and the second sending unit and the second receiving unit may specifically perform information interaction with the workflow engine by calling the API.

The workflow system provided in the embodiment of the present invention may include the workflow engine in any of the above embodiments of the present invention, and is configured to implement each of the above embodiments of the service processing method of the present invention.

Based on the workflow system provided by the above embodiment of the present invention, each node constituting the workflow is preset in the service system, the node information is stored in the workflow database, when the service system calls the workflow, the workflow engine can sequentially query the node information from the workflow database according to the flow path and send the node information to the service system, and the service system executes the corresponding node. In the embodiment of the invention, each node required by the workflow is independently set, the setting of the node and the configuration of the attribute parameter are independent processes, and the workflow engine and the service system do not belong to the same system on the coding, thereby realizing the decoupling of the code level; in data storage, the workflow database only stores the flow related information but not the business entity data, the business system only stores the business entity data but not the flow related information, decoupling of a data layer is achieved, when the business entity data changes, the workflow does not need to be changed, and configurability and reusability of the workflow are improved.

Fig. 10 is a schematic structural diagram of an embodiment of the workflow system of the present invention. As shown in fig. 10, the workflow system of this embodiment further includes a workflow designer, configured to configure parameter values for the attribute parameters of each node constituting the workflow, where the attribute parameters include a node ID parameter, a node type, and a node attribute.

Each node forming the workflow is preset in a service system, and a node ID uniquely identifies one node; the node attribute comprises a service model or a circulation condition, the service model comprises a service logic function unit, a task execution role and a processing personnel, and the circulation condition comprises a source node, a destination node and a conditional expression.

In addition, in another embodiment of the workflow system of the present invention, a workflow database may be further included, and is configured to store the flow information table, the node information table, the flow instance table, and the instance node table. Wherein:

and the flow information table comprises flow basic information of the workflow, and the flow basic information comprises a system ID and a flow ID.

And the node information table comprises node basic information of each node forming the workflow, wherein the node basic information comprises a node ID, a workflow ID of the workflow to which the node belongs, a parameter value of a node type and a parameter value of a node attribute.

The workflow system according to the above embodiment of the present invention further includes a workflow designer, which may preset each node required for forming the workflow in the business system, and then configure the parameter value for the attribute parameter of each node separately, so as to generate the workflow. Because each node required by the workflow is set independently and the setting of the node and the configuration of the attribute parameter are independent processes, after the workflow is generated, if a certain node needs to change the function, only a single node is modified; if the nodes need to be added, deleted or modified, only the relevant configuration parameters need to be modified, the operation is simple, the realization is easy, and the configurability and the reusability of the workflow are improved; moreover, the workflow designer for realizing the method is decoupled from the business system and can be used for providing general configuration service for all business system workflows.

The process instance table comprises process instance information of the workflow identified by the process ID, wherein the process instance information comprises the process instance ID, the process ID, the system ID and the process instance state, and the process instance state comprises incomplete or completed.

The example node table comprises node example information for recording the starting node, wherein the node example information comprises a process example ID, a node ID of the starting node, a node state and parameter values of node attributes; the node states include: inactive, pending, in progress, or complete.

Illustratively, the workflow database in the embodiment of the present invention may be, for example, a database of MySQL, MS SQL, SqlServer, Oracle, or the like type.

Fig. 11 is a schematic structural diagram of an embodiment of a service processing system of the present invention. The service processing system of this embodiment can be used to implement the above-mentioned embodiments of the service processing method of the present invention. As shown in fig. 11, the business processing system of this embodiment includes the workflow engine and the business system of any embodiment of the present invention.

In addition, in another embodiment of the service processing system of the present invention, a workflow database may be further included, which is used to store the flow information table, the node information table, the flow instance table, and the instance node table. Wherein:

The process instance table comprises process instance information of the workflow instance identified by the process ID, wherein the process instance information comprises the process instance ID, the process ID, the system ID and the process instance state, and the process instance state comprises incomplete state or completed state.

The example node table records node example information of each node in a workflow example, wherein the node example information comprises a flow example ID, a node ID of a starting node, a node state and parameter values of node attributes; the node states include: inactive, pending, in progress, or complete.

The embodiment of the invention provides the following technical scheme:

1. a service processing method comprises the following steps:

2. According to the method of 1, the service system executing the node to be executed includes:

3. The method of claim 2, further comprising:

4. According to the method of 3, the workflow database comprises a flow information table for storing the flow basic information of each workflow, and the flow basic information of each workflow comprises a system ID and a flow ID;

5. According to the method described in 4, the workflow database includes a node information table for storing the node basic information of each node, and the node basic information of each node includes a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute;

6. The method of 5, the parameter values for the node type comprising: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node;

7. According to the method of 6, the obtaining the destination node of the circulation condition of the source node as the node to be executed from the workflow database includes:

and inquiring the node basic information of the corresponding process ID from a node information table, and acquiring a source node ID as a destination node ID in the parameter values of the circulation condition of the to-be-executed node ID.

8. According to the method of 7, the parameter values of the circulation condition further include a specific condition expression;

the execution result message also comprises a numerical value submitted by a user in the process of executing the node to be executed;

the obtaining of the source node ID as the destination node ID in the parameter values of the flow condition of the to-be-executed node ID includes: and calculating the numerical value submitted by the user as the value of the free variable in the specific conditional expression, and determining the ID of the destination node according to the calculation result.

9. According to the method of 5 or 6, the flow information table and the node information table are generated by a workflow designer when parameter values are configured for attribute parameters of each node constituting the workflow in a business system, and the attribute parameters include a node ID parameter, a node type, and a node attribute.

10. The method of any of claims 1 to 9, further comprising:

the service system receives an instance creation instruction sent after a user logs in, wherein the instance creation instruction comprises a user ID; wherein, the user ID uniquely identifies a user registered in the service system;

the service system inquires an execution role ID corresponding to the user ID from a user information base and sends a creation request to a workflow engine, wherein the creation request also comprises the execution role ID and the user ID;

after the node information of the start node in the workflow identified by the flow ID is acquired from the workflow database, the method further comprises the following steps:

performing authority authentication on the execution role ID and the user ID in the creation request according to the parameter value of the node attribute of the starting node;

and responding to the fact that the execution role ID and the user ID in the creation request pass authority authentication, and returning the node information of the starting node to a service system.

11. The method according to any one of claims 1 to 10, further comprising, after obtaining the process ID corresponding to the system ID in the creation request from a workflow database:

creating a workflow instance of the workflow identified by the flow ID, and distributing the flow instance ID to the workflow instance; wherein, the process instance ID uniquely identifies a workflow instance;

recording the process instance information of the workflow identified by the process ID in a process instance table of a workflow database, and setting the state of the process instance as unfinished; the process instance information includes the process instance ID, the process ID, the system ID, and a process instance status, which includes incomplete or completed.

12. According to the method of 11, after receiving an execution result message returned by the node to be executed after the execution of the service system is completed, the method further includes:

identifying whether the node to be executed is a node ending according to the node information of the node to be executed;

responding to the condition that the node to be executed is not the end node, and executing the operation of acquiring the destination node of the circulation condition of the source node as the node to be executed from the workflow database;

and in response to the node to be executed being an end node, changing the state of the process instance in the process instance information to be completed.

13. According to the method of 12, after obtaining node information of a start node in a workflow identified by the flow ID from a workflow database, the method further includes:

activating the starting node, changing the node state of the starting node into an activated state to be processed, and recording node instance information of the starting node in an instance node table of a workflow database, wherein the node instance information comprises the process instance ID, the node ID of the starting node, the node state and the parameter value of the node attribute; the node states include: not activated, pending, in-process or completed;

after the node information of the node to be executed is returned to the service system, the method further comprises the following steps:

changing the node status of the start node to in-process.

14. According to the method of 13, after obtaining the destination node of the flow condition of the source node as the node to be executed from the workflow database, the method further includes:

activating the destination node, changing the destination node into a node to be executed, and changing the node state of the source node into completion;

changing the node state of the node to be executed into the activated node to be processed, and recording the node instance information of the node to be executed in an instance node table of a workflow database, wherein the node instance information comprises the flow instance ID, the node ID of the node to be executed, the node state and the parameter value of the node attribute.

15. According to the method of 14, after changing the node status of the source node to completion, the method further includes:

and in response to receiving an execution failure message returned by the service system when the execution of the node to be executed is not successful, changing the source node into the node to be executed, changing the node state of the source node into the activated node to be processed, and then executing the operation of returning the node information of the node to be executed to the service system.

16. According to the method of claim 15, the service model further includes a backtracking processing mode, and the parameter values of the backtracking processing mode include: whether the same processing personnel is required to process the backtracking task or not;

the node information of the node to be executed, which is returned to the service system, also includes the parameter value of the backtracking processing mode, so that the service system can determine the user ID of the processing personnel executing the task according to the parameter value of the backtracking processing mode.

17. The method according to any one of claims 13 to 16, further comprising, after returning the node information of the node to be executed to a service system:

and the service system sends a processing task notification message to the execution role ID in the node information of the node to be executed and the user ID of the processing personnel so as to facilitate the corresponding user to process the task after logging in.

18. The method of claim 17, further comprising:

the service system forwards the task request message to a workflow engine;

and the service system displays the acquired tasks in the nodes so that the requesting user can process the task.

19. The method of 17, the business model further comprising a task allocation policy; the parameter value of the task allocation strategy is specifically the type of the task allocation strategy.

20. According to the method of 19, the type of the task allocation policy comprises an assignment type, a competition type, a dynamic countersign type or an average allocation type;

if the type of the configuration task allocation strategy is an assignment type, configuring a specific execution role ID and a user ID of a processing person in the parameter values of the node attributes;

if the type of the configured task allocation strategy is a dynamic countersigning type, configuring a specific execution role ID in the parameter values of the node attributes, and configuring the parameter values of the processing personnel as the processing personnel with the highest task execution efficiency in the execution role ID;

and if the type of the configuration task allocation strategy is an average allocation type, a specific execution role ID is configured in the parameter values of the node attributes, and the parameter values of the processing personnel are configured as the processing personnel determined in the execution role ID in a sequential rotation mode.

21. According to the method of 20, the displaying, by the service system, the task in the acquired node includes:

the service system acquires the parameter value of a service model from the node information comprising the node ID according to the acquired node ID of the node, and determines the user ID for processing the task according to the parameter value of the service model;

and the service system displays the acquired tasks in the nodes to the user ID for processing the task so as to facilitate the user to process.

22. According to the method described in 21, after the service system displays the task in the acquired node to the user ID for processing the task, the method further includes:

in response to receiving a process instance progress display request sent by a user for processing the task, forwarding the process instance progress display request to a workflow engine by a service system, wherein the process instance progress display request comprises a process instance ID and a user ID;

the workflow engine acquires a corresponding flow ID, a node information table related to the flow ID and node instance information related to the flow ID from a workflow database according to the flow instance ID and returns the flow ID, the node information table related to the flow ID and the node instance information to the service system;

and the service system displays the current workflow path and workflow instance progress according to the node information table and the node instance information returned by the workflow engine, and acquires and displays the user ID of the processing task and the operation information performed by the user on each node representing the workflow instance progress.

23. The method according to any one of claims 1 to 22, wherein the business system performs information interaction with the workflow engine by calling an application program interface API of the workflow engine in a coupled setting.

24. A workflow engine, comprising:

25. According to the workflow engine of 24, the workflow database includes a flow information table for storing flow basic information of each workflow, and the flow basic information of each workflow includes a system ID and a flow ID;

the first obtaining unit specifically queries a process ID corresponding to the system ID in the creation request from a process information table.

26. According to the workflow engine of 25, the workflow database comprises a node information table for storing the node basic information of each node, wherein the node basic information of each node comprises a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type and a parameter value of a node attribute;

the second obtaining unit is specifically configured to obtain all the node basis information including the corresponding process ID from a node information table; acquiring parameter values of node types from all the node basic information as the node basic information of a starting node; and acquiring the node ID and the parameter value of the node attribute from the node basic information of the starting node by taking the parameter value of the node type as the parameter value of the starting node.

27. The workflow engine of 26, the parameter values for the node type comprising: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node;

28. The workflow engine of 27, the business model further comprising a task allocation policy; the parameter value of the task allocation strategy is specifically the type of the task allocation strategy.

29. According to the workflow engine of 28, the type of the task allocation policy comprises an assignment type, a competition type, a dynamic countersign type or an average allocation type;

30. According to the workflow engine of 29, when the third obtaining unit obtains the destination node of the flow condition of the source node as the to-be-executed node from the workflow database, the third obtaining unit specifically queries the node basis information of the corresponding flow ID from the node information table, and obtains the destination node ID of the parameter value of the flow condition of the source node ID as the to-be-executed node ID.

31. According to the workflow engine of 30, the parameter values of the circulation conditions further include specific condition expressions;

when the third obtaining unit obtains the source node ID as the destination node ID in the parameter values of the flow condition of the to-be-executed node ID, specifically, a numerical value submitted by a user is calculated as a value of a free variable in the specific condition expression, and the destination node ID is determined according to a calculation result.

32. According to the workflow engine 28 or 29, the flow information table and the node information table are generated by a workflow designer when parameter values are configured for attribute parameters of each node constituting the workflow in a business system, and the attribute parameters include a node ID parameter, a node type, and a node attribute.

33. The workflow engine according to any one of claims 26 to 32, further comprising a process instance management unit, configured to, after the first obtaining unit obtains the process ID corresponding to the system ID in the creation request from the workflow database: creating a workflow instance of the workflow identified by the flow ID, and distributing the flow instance ID to the workflow instance; wherein, the process instance ID uniquely identifies a workflow instance; recording the process instance information of the workflow identified by the process ID in a process instance table of a workflow database, and setting the state of the process instance as unfinished; the process instance information includes the process instance ID, the process ID, the system ID, and a process instance status, which includes incomplete or completed.

34. The workflow engine of 33, further comprising:

the identification unit is used for identifying whether the node to be executed finishes the node or not according to the node information of the node to be executed after the first receiving unit receives the execution result message returned by the node to be executed after the execution of the service system finishes;

the third obtaining unit is specifically configured to, according to the identification result of the identification unit, execute the operation of obtaining, from the workflow database, the destination node of the circulation condition of the source node as the node to be executed when the node to be executed is not the end node;

and the process instance management unit is further configured to change the state of the process instance in the process instance information to be completed when the node to be executed is the end node according to the identification result of the identification unit.

35. The workflow engine of 34, further comprising a node instance management unit, configured to, after the second obtaining unit obtains node information of a start node in the workflow identified by the flow ID from the workflow database:

activating the starting node, changing the node state of the starting node into an activated state to be processed, and recording node instance information of the starting node in an instance node table of a workflow database, wherein the node instance information comprises the process instance ID, the node ID of the starting node, the node state and the parameter value of the node attribute; the node states include: not activated, pending, in-process or completed; and after the first sending unit returns the node information of the node to be executed to the service system, changing the node state of the starting node into the processing.

36. The workflow engine according to 35, wherein the node instance management unit is further configured to, after the third obtaining unit obtains, from the workflow database, the destination node of the flow condition of the node to be executed as the source node:

activating the destination node, changing the destination node into a node to be executed, and changing the node state of the source node into completion; and

37. The workflow engine according to 36, wherein the node instance management unit is further configured to change the source node to a node to be executed when the first receiving unit receives an execution failure message that the service system does not successfully execute the node to be executed, and change the node status of the source node to be activated to be processed, so that the first sending unit executes the operation of returning the node information of the node to be executed to the service system.

38. The workflow engine of 37, wherein the business model further includes a backtracking processing mode, and the parameter values of the backtracking processing mode include: whether the same processing personnel is required to process the backtracking task or not;

the node information of the node to be executed, which is returned to the service system by the first sending unit, further includes a parameter value of the backtracking processing mode, so that the service system determines the user ID of the processing personnel executing the task according to the parameter value of the backtracking processing mode.

39. The workflow engine according to any one of claims 33 to 38, wherein the first receiving unit is further configured to receive the task request message sent by the service system, where the task request message includes a user ID of a requesting user and an assigned execution role ID;

the workflow engine also comprises a query unit, a task processing unit and a task processing unit, wherein the query unit is used for querying an instance node table in a workflow database and acquiring a node which is activated and to be processed and comprises an execution role ID and a user ID in a task request message;

the first sending unit is further configured to return the node ID of the node acquired by the querying unit to the service system.

40. The workflow engine according to any one of claims 35 to 39, wherein the first receiving unit is further configured to receive a process instance progress display request sent by a business system, where the process instance progress display request includes a process instance ID and a user ID;

the workflow engine further comprises a fourth obtaining unit, configured to obtain, according to the process instance ID, a corresponding process ID, a node information table related to the process ID, and node instance information related to the process instance ID from a workflow database;

the first sending unit is further configured to return the node information table and the node instance information acquired by the fourth acquiring unit to the service system, so that the service system displays the current workflow path and the workflow instance progress according to the workflow path.

41. A business system comprising:

42. According to the service system described in 41, the second sending unit is further configured to send a processing task notification message to an execution role ID in the node information of the node to be executed and a user ID of a processing person, so that the corresponding user logs in and processes the task.

43. According to the service system described in 42, the second receiving unit is further configured to receive a task request message sent by a user, where the task request message is sent after the user logs in the service system and receives a task notification message, and the task request message includes a user ID of a requesting user and an assigned execution role ID; receiving a node ID returned by the workflow engine after the workflow engine inquires an instance node table in a workflow database;

the second sending unit is further configured to forward the task request message to a workflow engine;

the service system further comprises a human-computer interaction unit, which is used for displaying the task in the node identified by the node ID received by the second receiving unit so that the requesting user can process the task.

44. According to the business system of 43, the human-computer interaction unit is specifically configured to:

acquiring a parameter value of a service model from node information including the node ID received by the second receiving unit, and determining a user ID for processing the task according to the parameter value of the service model; and

and displaying the acquired tasks in the nodes to the user ID for processing the task so as to facilitate the user to process.

45. According to the service system of 44, the second receiving unit is further configured to receive a process instance progress display request sent by a user processing the task; receiving a node information table and node instance information returned by the workflow engine;

the second sending unit is further configured to forward the process instance progress display request to a workflow engine, where the process instance progress display request includes a process instance ID and a user ID;

and the human-computer interaction unit is also used for displaying the current workflow path and workflow instance progress according to the node information table and the node instance information returned by the workflow engine, and acquiring and displaying the user ID of the processing task and the operation information performed by the user on each node representing the workflow instance progress.

46. The business system of any one of 41 to 45, further comprising:

the node library is used for storing all nodes forming the workflow; and/or

The business database is used for storing data submitted by users, executed operations and executed result data; and/or

47. The service system according to any one of claims 41 to 46, wherein the service system is provided with an application program interface API of the workflow engine in a coupled manner, and the second sending unit and the second receiving unit perform information interaction with the workflow engine by specifically calling the API.

48. A workflow system comprising the workflow engine of any one of 24 to 40;

49. the workflow system according to 48, further comprising a workflow designer configured to configure parameter values for attribute parameters of each node constituting a workflow, respectively, the attribute parameters including a node ID parameter, a node type, and a node attribute;

each node forming the workflow is preset in a service system, and a node ID uniquely identifies one node; the node attributes comprise a service model or a circulation condition, the service model comprises a service logic function unit, a task execution role and a processing personnel, and the circulation condition comprises a source node, a destination node and a conditional expression.

50. The workflow system of 48 or 49, further comprising a workflow database for storing:

the flow information table comprises flow basic information of the workflow, wherein the flow basic information comprises a system ID and a flow ID;

a node information table including node basic information of each node constituting the workflow, the node basic information including a node ID, a workflow ID of the workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute;

a process instance table including process instance information of a workflow identified by the process ID, the process instance information including the process instance ID, the process ID, the system ID, and a process instance status, the process instance status including incomplete or completed;

an example node table, which records node example information of the start node, wherein the node example information includes the process example ID, the node ID of the start node, the node state and the parameter value of the node attribute; the node states include: inactive, pending, in progress, or complete.

51. A business process system comprising the workflow engine of any one of 24 to 40 and the business system of any one of 41 to 47.

52. The business processing system of 51, further comprising a workflow database for storing:

a process instance table including process instance information of a workflow instance identified by the process ID, the process instance information including the process instance ID, the process ID, the system ID, and a process instance status, the process instance status including incomplete or completed;

an example node table, which records node example information of each node in a workflow example, wherein the node example information comprises the flow example ID, the node ID of the starting node, the node state and the parameter value of the node attribute; the node states include: inactive, pending, in progress, or complete.

In the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts in the embodiments are referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The method and apparatus of the present invention may be implemented in a number of ways. For example, the methods and apparatus of the present invention may be implemented in software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustrative purposes only, and the steps of the method of the present invention are not limited to the order specifically described above unless specifically indicated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.

The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A method for processing a service, comprising:

2. The method of claim 1, wherein the service system executing the node to be executed comprises:

3. The method of claim 2, further comprising:

4. The method according to claim 3, wherein the workflow database comprises a flow information table for storing flow basic information of each workflow, and the flow basic information of each workflow comprises a system ID and a flow ID;

5. The method according to claim 4, wherein the workflow database comprises a node information table for storing node basis information of each node, and the node basis information of each node comprises a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute;

6. The method of claim 5, wherein the parameter values for the node type comprise: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node;

7. The method according to claim 6, wherein the obtaining the destination node of the flow condition of the source node as the node to be executed from the workflow database comprises:

8. The method according to claim 7, wherein the parameter values of the circulation condition further include a specific conditional expression;

9. The method according to claim 5 or 6, wherein the flow information table and the node information table are generated by a workflow designer when configuring parameter values for attribute parameters of each node constituting the workflow in a business system, and the attribute parameters include a node ID parameter, a node type, and a node attribute.

10. The method of any one of claims 1 to 8, further comprising:

11. The method according to any one of claims 6 to 8, wherein after obtaining the process ID corresponding to the system ID in the creation request from a workflow database, the method further comprises:

12. The method according to claim 11, wherein after receiving an execution result message returned by the node to be executed after the service system finishes executing, the method further comprises:

13. The method of claim 12, wherein after obtaining node information of a start node in the workflow identified by the flow ID from a workflow database, further comprising:

changing the node status of the start node to in-process.

14. The method according to claim 13, wherein after obtaining the destination node of the flow condition of the source node as the node to be executed from the workflow database, further comprising:

15. The method of claim 14, wherein changing the node status of the source node to complete further comprises:

16. The method of claim 15, wherein the business model further comprises a backtracking processing means, and the parameter values of the backtracking processing means comprise: whether the same processing personnel is required to process the backtracking task or not;

17. The method according to any one of claims 13 to 16, wherein after returning the node information of the node to be executed to the service system, further comprising:

18. The method of claim 17, further comprising:

the service system forwards the task request message to a workflow engine;

19. The method of claim 18, wherein the business model further comprises a task allocation policy; the parameter value of the task allocation strategy is specifically the type of the task allocation strategy.

20. The method of claim 19, wherein the type of task allocation policy comprises assignment type, contention type, dynamic countersign type, or average allocation type;

21. The method of claim 20, wherein the business system displaying the acquired tasks in the node comprises:

22. The method according to claim 21, wherein after the service system displays the acquired task in the node to the user ID for processing the task, the method further comprises:

23. The method of claim 1, wherein the business system interacts information with the workflow engine by calling an Application Program Interface (API) of the workflow engine coupled to the settings.

24. A workflow engine, comprising:

25. The workflow engine of claim 24 wherein the workflow database comprises a flow information table for storing flow basic information of each workflow, the flow basic information of each workflow comprising a system ID and a flow ID;

26. The workflow engine according to claim 25, wherein the workflow database comprises a node information table for storing node basis information of each node, and the node basis information of each node comprises a node ID, a process ID of a workflow to which the node belongs, a parameter value of a node type, and a parameter value of a node attribute;

27. The workflow engine of claim 26 wherein the parameter values for a node type comprise: a start node, an end node, a flow condition node, a common node, a branch node or an aggregation node;

28. The workflow engine of claim 27 wherein the business model further comprises a task allocation policy; the parameter value of the task allocation strategy is specifically the type of the task allocation strategy.

29. The workflow engine of claim 28 wherein the type of task allocation policy comprises assignment type, contention type, dynamic session type or average allocation type;

30. The workflow engine according to claim 29, wherein when the source node is a destination node of the flow condition of the node to be executed, the third obtaining unit specifically queries the node basis information of the corresponding flow ID from the node information table, and obtains the source node ID as the destination node ID among the parameter values of the flow condition of the node to be executed ID.

31. The workflow engine of claim 30 wherein the parameter values of the flow conditions further comprise specific conditional expressions;

32. The workflow engine of claim 28 or 29 wherein the flow information table and the node information table are generated by a workflow designer when configuring parameter values for attribute parameters of each node constituting the workflow in a business system, wherein the attribute parameters include a node ID parameter, a node type and a node attribute.

33. The workflow engine according to any one of claims 27 to 31, further comprising a process instance management unit configured to, after the first obtaining unit obtains the process ID corresponding to the system ID in the creation request from the workflow database: creating a workflow instance of the workflow identified by the flow ID, and distributing the flow instance ID to the workflow instance; wherein, the process instance ID uniquely identifies a workflow instance; recording the process instance information of the workflow identified by the process ID in a process instance table of a workflow database, and setting the state of the process instance as unfinished; the process instance information includes the process instance ID, the process ID, the system ID, and a process instance status, which includes incomplete or completed.

34. The workflow engine of claim 33 further comprising:

35. The workflow engine according to claim 34, further comprising a node instance management unit configured to, after the second obtaining unit obtains node information of a start node in the workflow identified by the flow ID from the workflow database:

36. The workflow engine of claim 35, wherein the node instance management unit is further configured to, after the third obtaining unit obtains the destination node of the flow condition of the to-be-executed node from the workflow database, the source node:

37. The workflow engine of claim 36, wherein the node instance management unit is further configured to change the source node to the node to be executed and change the node status of the source node to be activated to be processed when the first receiving unit receives an execution failure message returned by the service system that the execution of the node to be executed fails, so that the first sending unit performs the operation of returning the node information of the node to be executed to the service system.

38. The workflow engine of claim 37 wherein the business model further comprises a backtracking process, wherein the parameter values of the backtracking process comprise: whether the same processing personnel is required to process the backtracking task or not;

39. The workflow engine of claim 33, wherein the first receiving unit is further configured to receive a task request message sent by the business system, wherein the task request message includes a user ID of a requesting user and an assigned execution role ID;

40. The workflow engine according to any one of claim 35, wherein the first receiving unit is further configured to receive a process instance progress display request sent by a business system, where the process instance progress display request includes a process instance ID and a user ID;

41. A business system, comprising:

42. The business system of claim 41, wherein the second sending unit is further configured to send a processing task notification message to an execution role ID in the node information of the node to be executed and a user ID of a processing person, so that the corresponding user logs in and processes the task.

43. The service system according to claim 42, wherein the second receiving unit is further configured to receive a task request message sent by a user, where the task request message is sent by the user after the user logs in the service system and receives a task notification message, and the task request message includes a user ID of a requesting user and an assigned execution role ID; receiving a node ID returned by the workflow engine after the workflow engine inquires an instance node table in a workflow database;

44. The business system of claim 43, wherein the human-computer interaction unit is specifically configured to:

45. The business system of claim 44, wherein the second receiving unit is further configured to receive a process instance progress display request sent by a user processing the task; receiving a node information table and node instance information returned by the workflow engine;

46. A business system of any one of claims 41 to 45 further comprising:

the node library is used for storing all nodes forming the workflow; and/or

47. The business system of claim 41, wherein the business system is coupled with an Application Program Interface (API) provided with the workflow engine, and the second sending unit and the second receiving unit perform information interaction with the workflow engine by specifically calling the API.

48. A workflow system comprising the workflow engine of any one of claims 24 to 40.

49. The workflow system of claim 48 further comprising a workflow designer for configuring parameter values for attribute parameters of each node constituting the workflow, respectively, said attribute parameters comprising a node ID parameter, a node type and a node attribute;

50. The workflow system of claim 48 further comprising a workflow database for storing:

51. A business process system comprising the workflow engine of any one of claims 24 to 40 and the business system of any one of claims 41 to 47.

52. A transaction system according to claim 51, further comprising a workflow database for storing: