CN115907683A

CN115907683A - Realization system and method of workflow engine based on financial product management

Info

Publication number: CN115907683A
Application number: CN202211630621.9A
Authority: CN
Inventors: 俞枫; 王立; 陈文培; 吴锴
Original assignee: Guotai Junan Securities Co Ltd
Current assignee: Guotai Junan Securities Co Ltd
Priority date: 2022-12-19
Filing date: 2022-12-19
Publication date: 2023-04-04

Abstract

The invention relates to a realization system of a workflow engine based on financial product management, wherein the system comprises: a workflow system architecture is provided, the workflow system architecture comprising: the external service and tool module is used for carrying out flow design, monitoring management and information statistical analysis processing; the workflow engine is connected with the external service and tool module and is used for providing resource management service and flow processing and scheduling service for the system; and the workflow database is connected with the workflow engine and used for storing the process data generated in the operation process of the system so as to provide the landing data to the service system for corresponding function processing. The invention also relates to a corresponding method. The implementation system and the implementation method of the workflow engine based on the financial product management support the demands of distinguishing different trends of the flow according to different types and states of products and different departments and authorities of processing persons in the flow of the financial products.

Description

Realization system and method of workflow engine based on financial product management

Technical Field

The invention relates to the technical field of workflow engines, in particular to the technical field of financial product management, and specifically relates to a realization system and method of a workflow engine based on financial product management.

Background

The financial product management business process is extremely complex, and relates to the personnel interaction of various departments and subsidiaries. The processes to be performed by different types of financial products and the functions in the processes are different, and different processes also have mutual influence.

The existing business process is generated by a general workflow engine, and the main defects are as follows:

1. the flow logic is simple, and the function support for determining different trends of the flow according to different types and different attributes of products related to financial product business is insufficient;

2. for the same product, the modification of the data by different processes which are carried out simultaneously can generate conflict, so that the data is wrong;

3. multiple jumps, continuous backspacing and backspacing of branch nodes may be involved in the process, and a general workflow engine cannot support the steps;

4. the flow template, the database structure and the like need to be formulated by professional technicians according to business requirements, and the process is complex and is easy to make mistakes.

Based on this, a method for processing a workflow engine, which can effectively overcome the complexity and inapplicability between different processes, is needed.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provides a realization system and a method of a workflow engine based on financial product management, which can simultaneously meet diversified demands.

In order to achieve the above object, the system and method for implementing a workflow engine based on financial product management according to the present invention are as follows:

the realization system of the workflow engine based on financial product management is mainly characterized by comprising the following steps: a workflow system architecture is provided, the workflow system architecture comprising:

the external service and tool module is used for carrying out flow design, monitoring management and information statistical analysis processing;

the workflow engine is connected with the external service and tool module and is used for providing resource management service and flow processing and scheduling service for the system; and

and the workflow database is connected with the workflow engine and used for storing the process data generated in the operation process of the system so as to provide the landing data to the service system for corresponding function processing.

Preferably, the external service and tool module is configured with:

the flow design tool is used for designing a new flow chart, and/or modifying an old flow chart, and/or designing flow form configuration, and setting fields and display modes required by the flow;

the monitoring management tool is used for monitoring the process examples and the tasks of each process node in the system operation process, checking the flow chart and the context variables of the current process examples, allowing process skipping and context variable modification, checking the current task processing condition and reallocating task handlers;

the statistical analysis tool is used for monitoring the number of instances, the processing condition and the processing time consumption of each process; and

and the external interface is used for being called by an external service system.

Preferably, the workflow engine is configured with:

the resource management service module is connected with the flow design tool and is used for managing a flow chart, context variables, flow form configuration and external service resources in the current system; and

and the flow processing and scheduling service module is connected with the monitoring management tool, the statistical analysis tool and the external interface and is used for being responsible for processing and operating the tasks of the flow instances and the flow nodes.

Preferably, the workflow system architecture adopts a DUBBO micro-service architecture, and the workflow system architecture further provides an external interface for other micro-services to initiate a flow, obtain a current node and a handler of the flow, and process a current task of the flow, or adds a service interface suitable for other systems in the resource management service module, and is configured in an event of the node, and is invoked when a task is distributed or when a task of the node starts or ends according to a service requirement.

Preferably, the resource management service module is internally provided with a process context variable, the process context variable is set through data in a process form field during process initialization and each node task processing, the context variable is calculated through an expression function of the workflow engine, and the trend of the flow chart is controlled by using a calculation result.

Preferably, each branch node in the flow uses the expression of the workflow engine to perform flow direction judgment, so as to determine the next branch of the flow.

Preferably, the resource management service module further has built-in basic flow components supporting dragging, and the basic flow components include but are not limited to: the system comprises a starting node, an ending node, a decision node, a parallel node, a sink node, a manual node, a waiting node, an automatic task node, a pause node and a sub-process node;

business personnel can design a business flow component by dragging, set fields required by a product by the configuration of a flow form, and automatically generate a corresponding flow chart and a corresponding table structure.

Preferably, the workflow engine further supports a data isolation function, and the data isolation function specifically is:

when the system starts a data isolation process, the workflow engine creates a process table in the workflow database according to the field name and the table name configured by the process table when the process is initialized, stores the data of the process example into the process table, and provides the final landing data to the service system when the process is finished, and the service system lands the data, so that the conflict caused by the mutual influence of different processes is avoided.

Preferably, the process example uses a stack + linked list data structure, each branch node uses a linked list, each process branch is stored by using a different stack, the flow jump and the return are both new tasks to be stacked, the process can jump to any node in the flow chart behind the current node, the task can be popped out by the submission after the process return, and after the process return occurs for a plurality of times continuously, the node returned for the previous time in each submission continues to process the process.

Preferably, after the business personnel configures the business process, the system automatically generates a flow chart, a flow form page and a database table structure, and the background technical personnel writes a micro-service interface of the business system according to the business needs and configures the micro-service interface in the flow chart node event, so that the process can be operated.

The method for realizing the workflow engine based on the financial product management by using the system is mainly characterized by comprising the following steps:

(1) A service person uses a flow design tool to design a flow chart according to service logic and determines a flow name and a number;

(2) In the node configuration processing person and the required context variable and the branch node in the flow chart, the branch condition is configured by using an expression;

(3) Configuring a design flow form, determining a table name and a field name of a field required by a service, configuring display modes and sequences of the field at different nodes according to requirements, and associating with a newly-built flow according to a flow key to complete the design of service personnel;

(4) The system generates a flow chart, a flow form page and a database table interface according to the configuration of a service person, and a background technician writes a micro-service interface of the service system according to service needs to realize corresponding service functions;

(5) And configuring an interface of the service system to the event configuration of the corresponding process node, and setting the execution time, so that the process can be executed.

By adopting the implementation system and the method of the workflow engine based on financial product management, the process context variable is built in the resource management service, the setting can be carried out through the data in the process form field during the process initialization and the task processing process of each node, meanwhile, the context variable can be calculated through the expression function of the workflow engine, and the trend of the flow chart is controlled by the calculation result, so that the requirement of distinguishing different trends of the process according to different types, different states and different departments and authorities of a processor in the financial product process is supported. Meanwhile, the workflow engine supports data isolation. Starting a data isolation process, creating a process table in a workflow database according to a field name and a table name configured in a process table during process initialization, storing data of a process example in the process table, providing final landing data to a service system after the process is finished, and landing the data by the service system so as to avoid conflicts caused by mutual influence of different processes.

In addition, the flow example uses a data structure of stack + linked list, the branch nodes use linked list, the flow branches are stored by different stacks respectively, and the flow jump and the return are all new tasks to be stacked, so that the flexible flow jump is supported, and after continuous multiple returns, the node returning to the previous return can be submitted every time to continue processing the flow. Meanwhile, a basic flow component capable of supporting dragging is arranged in the resource management service, and the requirements of all financial product management business flows can be basically covered. Business personnel can design a business process by dragging, and set fields required by a product by configuration of a process form, and automatically generate a flow chart and a table structure, so that the whole process does not need participation of technical personnel, the communication cost is reduced, errors possibly occurring in demand communication are avoided, and the development efficiency of the process is greatly improved.

Drawings

FIG. 1 is a schematic diagram of a workflow system architecture of a system for implementing a workflow engine based on financial product management according to the present invention.

FIG. 2 is a diagram illustrating the configuration of flow task events according to the present invention.

FIG. 3 is a diagram illustrating a context variable initialization process according to the present invention.

FIG. 4 is a diagram illustrating a process trend determination according to context variables.

FIG. 5 is a diagram illustrating an example data structure of a process of the present invention.

FIG. 6 is a schematic diagram of the basic flow components of the present invention.

FIG. 7 is a diagram illustrating the configuration of workflow forms according to the present invention.

FIG. 8 is a flow chart of a method of implementing a financial product management-based workflow engine of the present invention.

Fig. 9 is an interaction diagram of the workflow system of the present invention and an external system.

Detailed Description

In order that the technical contents of the present invention can be more clearly described, the present invention will be further described with reference to specific embodiments.

Before describing in detail embodiments that are in accordance with the present invention, it should be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

Referring to fig. 1, the system for implementing a workflow engine based on financial product management includes: a workflow system architecture is provided, the workflow system architecture comprising:

As a preferred embodiment of the present invention, the external service and tool module is configured with:

In a preferred embodiment of the present invention, the workflow engine is configured with:

As a preferred embodiment of the present invention, the workflow system architecture adopts a DUBBO micro-service architecture, and the workflow system architecture further provides an external interface for other micro-services to initiate a flow, obtain a current node of the flow and a handler, and process a current task of the flow, or adds a service interface suitable for other systems in the resource management service module, and is configured in an event of the node, and is selected to be invoked when a task is distributed or when a task of the node starts or ends according to a service requirement.

As a preferred embodiment of the present invention, a process context variable is built in the resource management service module, and the process context variable is set by data in a process form field during process initialization and during task processing of each node, and is calculated by an expression function of the workflow engine, and the trend of the flowchart is controlled by using a calculation result.

As a preferred embodiment of the present invention, each branch node in the flow uses the expression of the workflow engine to perform the judgment of the flow direction, so as to determine the next branch of the flow.

As a preferred embodiment of the present invention, the resource management service module further has built-in basic flow components supporting dragging, and the basic flow components include but are not limited to: the system comprises a starting node, an ending node, a decision node, a parallel node, a sink node, a manual node, a waiting node, an automatic task node, a pause node and a sub-process node;

As a preferred embodiment of the present invention, the workflow engine further supports a data isolation function, where the data isolation function specifically is:

As a preferred embodiment of the present invention, the process example uses a stack + linked list data structure, each branch node uses a linked list, each process branch is stored by using a different stack, the process jump and the rollback are both new task stacking, and the process can jump to any node in the process diagram after the current node, the submission after the process rollback will make the task pop, and after the process rollback occurs for a plurality of consecutive times, each submission will return to the node which backed the previous time to continue processing the process.

As a preferred embodiment of the invention, after a business worker configures a business process, the system automatically generates a flow chart, a flow form page and a database table structure, a background technician writes a micro-service interface of the business system according to business needs and configures in a flow chart node event, and the process can run.

The method for realizing the workflow engine based on financial product management by using the system comprises the following steps:

(1) A service person uses a flow design tool to design a flow chart according to service logic, and determines a flow name and a number;

In practical applications, the workflow system is structured as shown in fig. 1, and the system is internally provided with a flow design tool, a monitoring management tool and a statistical analysis tool, and provides an external interface for external business system call.

The flow design tool can be used for designing a new flow chart, modifying an old flow chart, designing flow form configuration and setting fields and display modes required by the flow;

the monitoring management tool can monitor the running process example and the task of each process node, can check the flow chart and the context variable of the current process example, allows the process skip and the context variable modification, can check the current task processing condition and can reallocate task handlers;

the statistical analysis tool can monitor the number of instances, the processing condition and the processing time consumption of each process;

the workflow system adopts a DUBBO micro-service architecture, other micro-services can initiate a flow, acquire a current node and a handler of the flow, process a current task of the flow and the like through an external interface provided by the workflow system, or add service interfaces of other systems in the resource management service, then configure the service interfaces in an event of the node, and select to call when the task is distributed or when the node task starts and ends according to service requirements.

The workflow engine mainly provides resource management service and flow processing and scheduling service, and the resource management service mainly manages resources such as a flow chart, context variables, flow form configuration, external service and the like; the flow processing and scheduling service is mainly responsible for processing and operating flow instances and flow node tasks.

In the practical application, the workflow engine of the technical scheme has the following innovations:

1. the resource management service embeds a process context variable, which can be set by data in the fields of the process form when the process is initialized and during the task processing of each node, as shown in fig. 3, a new context variable a is added and assigned by the value of the form _ field _ a field in the configuration of the process form, and each node can be set. Meanwhile, the context variable can be calculated through the expression function of the workflow engine, and the trend of the flow chart is controlled by the calculation result, as shown in fig. 4, each branch node can be judged by the expression, so that the next branch of the flow is determined.

2. The workflow engine supports data isolation. Starting a data isolation process, creating a process table in a workflow database according to a field name and a table name configured in the process table during process initialization, storing data of a process example in the process table, providing final landing data to a service system after the process is finished, and landing the data by the service system so as to avoid conflict caused by mutual influence of different processes.

3. The flow example uses a data structure of stack + linked list, as shown in fig. 5, the branch nodes use the linked list, the flow branches are stored by different stacks, the jump and the return of the flow are both new tasks to be stacked, and the flow can jump to any node in the flow chart behind the current node. Since the return-back submission can cause the task to be popped, after the return-back is continuously performed for multiple times, each submission returns to the previous return-back node to continue the processing flow.

4. The resource management service is internally provided with basic flow components capable of supporting dragging, as shown in fig. 6, the basic flow components comprise a start ending component, a waiting pause component, a branch parallel node, a manual node, an automatic task node and the like, the requirements of all financial product management business flows can be basically covered, business personnel can design the business flows by dragging, product required fields are configured and set through a flow form shown in fig. 7, a flow chart and a table structure are automatically generated, and technical personnel do not need to participate in the whole process.

The use flow of the workflow system is as shown in fig. 8, after the business personnel configures the flow, the system automatically generates a flow chart, a flow form page and a database table structure, the technical personnel writes a micro-service interface of the business system according to the business needs, and the flow can be operated after the configuration in the flow chart node event.

In an embodiment of the present invention, the product admission flow of the financial product management platform is taken as an embodiment to further explain the technical solution:

the system is deployed as shown in fig. 9, and a business system, namely a financial product management platform, is responsible for the management of the life cycle of financial products of the whole company; the operator management system is responsible for the management of system operators and the control of authority; the workflow system is responsible for the creation of the product flow and the monitoring and scheduling of the running state of the flow. The system is deployed in a DUBBO micro-service architecture, and interaction can be carried out between every two systems after the system is registered in a service management platform.

In a specific embodiment of the present invention, the following will further describe the technical solution by taking a product admission flow as an embodiment:

as shown in FIG. 7, the fields required for a flow are first configured in the flow form configuration. The workflow system can generate a table building statement according to the configured field name and the table name and the type of the standard field, determine the display of a node page according to the configuration, configure whether a certain node in the process of each field is displayed, filled, disabled or not and display sequence according to business requirements, use a single selection box with dictionary items, use a check box to display in support of multiple selections, and set other display requirements in field configuration by technical personnel.

The workflow engine reads out the configuration data when each node task starts to process, and dynamically generates a page of the node task according to the configuration.

In practical applications, when implementing a product admission flow, the following processes are generally performed:

except for the starting and ending nodes, the flow chart mainly comprises manual nodes, action nodes, waiting nodes, branch nodes, parallel nodes and automatic task nodes. The artificial nodes are the most common nodes in the flow chart, and can be configured with the processing persons and the front-back processing method of the nodes; the artificial node is followed by an action node, and auditing actions (generally agreement and disagreement) of the artificial node can be configured and connected with the next node; the waiting node can configure waiting time to suspend the process; the branch node can be configured with a judgment condition, a plurality of branches appear in the subsequent flow, which branch is taken is determined according to the judgment condition, and the parallel node has no judgment condition and can simultaneously take the subsequent branches; the automatic task node can be configured with a processing method (the nature is the same as the front-back processing method of the manual node), and the automatic task node is automatically executed when walking to the node and is generally used for sending an email to inform related personnel when the process is finished.

The above steps are completed by business personnel through a flow design tool, and the workflow system generates corresponding pages and database tables according to the configuration of the flow form, and then the flow can be initiated.

When a flow is initiated, a workflow engine generates a flow instance according to the configuration of the flow diagram, the flow instance stores flow nodes by using a data structure of a stack + linked list shown in fig. 5, and the nodes in the flow find a next node through the connection of action nodes or by using modes of backspacing, skipping and the like, and directly stack the next node. At the moment, the financial management platform acquires the processor configured by the next node, then calls an operator management system interface to acquire specific processor information, and reminds corresponding personnel in the to-do list. And the processor can process the node task after seeing the prompt, if the action of the previous step is rollback, the current node processor normally submits the node and then the next node is the node before rollback. The parallel nodes are stored by using a linked list data structure, and each branch is a new flow stack. The branch node can obtain the context variable to judge or calculate, and then judge the trend of the subsequent flow according to the configured conditions. The data isolation is opened in the admission process, and after the task processing of each node is completed, the process information can be stored in the process table, so that the conflict between the modified information in the process of the process and other processes is avoided, and the information can be stored in the earth surface only when the process is finished and the node is finished.

The product access flow is a flow with higher complexity, and the workflow engine based on the financial product management of the technical scheme can efficiently complete the design and development of the flow, support the functions of branch judgment, flexible jump, continuous rollback, data isolation and the like with complex flow, and meet the business requirements of the financial product management.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by suitable instruction execution devices.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, and the program may be stored in a computer readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.

In the description herein, references to the description of terms "an embodiment," "some embodiments," "an example," "a specific example," or "an embodiment," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.

In this specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Claims

1. A system for implementing a workflow engine based on financial product management, the system comprising: a workflow system architecture is provided, the workflow system architecture comprising:

2. The system of claim 1, wherein the external services and tools module comprises:

3. The system of claim 2, wherein the workflow engine is configured with:

4. The system of claim 3, wherein the workflow system architecture employs a DUBBO micro-service architecture, and the workflow system architecture further provides an external interface for other micro-services to initiate a process, obtain a current node and a handler of the process, and process a current task of the process, or adds a service interface suitable for other systems in the resource management service module, and the service interface is configured in an event of the node and is selectively invoked when a task is assigned or when a task of the node starts or ends according to a business requirement.

5. The system of claim 3, wherein the resource management service module has a process context variable embedded therein, the process context variable is set by data in fields of a process form at the time of process initialization and during task processing of each node, and the context variable is calculated by an expression function of the workflow engine, and the trend of the flowchart is controlled by the calculation result.

6. The system of claim 5, wherein each branch node in the process uses the workflow engine expression to make a decision on the run of the process, thereby deciding the branch of the next step of the process.

7. The system as claimed in claim 5, wherein the resource management service module further comprises basic process components for supporting drag and drop, the basic process components include but are not limited to: the system comprises a start node, an end node, a decision node, a parallel node, a sink node, a manual node, a waiting node, an automatic task node, a pause node and a sub-process node;

8. The system for implementing a workflow engine based on financial product management as claimed in claim 5, wherein the workflow engine further supports a data isolation function, and the data isolation function is specifically:

when the system starts a data isolation process, the workflow engine creates a process table in the workflow database according to the field name and the table name configured by the process table when the process is initialized, stores the data of the process example into the process table, provides the final landing data to the service system when the process is finished, and the service system lands the data so as to avoid the conflict caused by the mutual influence of different processes.

9. The system of claim 8, wherein the process instance uses a stack + linked list data structure, each branch node uses a linked list, each process branch is stored using a different stack, the flow jump and rollback are both new task stacking, the process can jump to any node in the flow chart after the current node, the submission after the flow rollback can make the task pop up, and after a plurality of continuous rollbacks, each submission can return to the previous rolled back node to continue processing the flow.

10. The system for implementing workflow engine based on financial product management as claimed in any one of claims 1 to 9, wherein when the business personnel configure the business process, the system will automatically generate the flow chart, flow form page and database table structure, and the background technician will write the micro service interface of the business system according to the business requirement and configure in the event of flow chart node, and the process can run.

11. A method for implementing a workflow engine based on financial product management using the system of any one of claims 1 to 9, the method comprising the steps of:

(4) The system generates a flow chart, a flow table page and a database table interface according to the configuration of a service worker, and a background technician writes a micro-service interface of the service system according to service needs so as to realize corresponding service functions;