Data operation management method and system based on process engine

Abstract

The invention provides a data operation management method and system based on a process engine. The method comprises the following steps: step A1, splitting data operation management into a plurality of process nodes; a2, performing flow definition on each flow node, and connecting the flow nodes in series through a flow engine; and step A3, obtaining a business project, and automatically initiating a process node according to a series sequence through a process engine so as to carry out operation management on the business project. On the premise that existing data application is guaranteed, the data operation management method based on the process engine is provided to meet new requirements of scenarized application. Data operation management is configured through a process engine, the whole operation management work is connected in series, and digital management of data operation is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of data operation management, and in particular to a method and system for data operation management based on a process engine. Background Art

[0002] With the rapid development of big data technology, a large amount of huge, complex and changeable data has emerged. In order to further strengthen the level of data operation and governance, a complete set of data operation management methods is needed. Data operation management mainly focuses on data aggregation, governance, management, sharing and openness, data security, etc. In the actual business system, since the specific business needs of various business departments for data operations are different and there are differences in the process links, special customized development is required for different businesses. Summary of the invention

[0003] Based on the above content, the present invention provides a method and system for data operation management based on a process engine, aiming to solve technical problems in the prior art such as complex data operation management, low flexibility and low efficiency.

[0004] The present invention provides a data operation management method based on a process engine, comprising:

[0005] Step A1: split data operation management into multiple process nodes;

[0006] Step A2, define the process for each process node, and connect the process nodes in series through the process engine;

[0007] Step A3, obtain the business project, and automatically initiate the process nodes in a serial order through the process engine to perform operation management on the business project.

[0008] Further, including:

[0009] The process definition of each process node includes a node form configuration; each process node is associated with a corresponding node form configuration;

[0010] In step A3, through the process engine, after the previous process node completes the execution of the business project, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

[0011] Furthermore, in step A2, a visual node form configuration is performed through an open source form generation tool.

[0012] Furthermore, in step A1, data operation management is split into process nodes including project requirements, task splitting, service splitting and service allocation;

[0013] In step A2, the process engine connects the process nodes in series according to the order of project requirements, task splitting, service splitting and service allocation;

[0014] At the process node of project requirements, form demand information about business projects;

[0015] At the task splitting process node, the total task to complete the demand information is split into subtasks;

[0016] At the service splitting process node, split the subtask into multiple services;

[0017] At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

[0018] Furthermore, in step A3, the process of automatically initiating the process nodes in a serial order by the process engine to execute the business project includes:

[0019] Step A31, in the process node of project requirements, automatically create a requirement sheet according to the business project;

[0020] Step A32, when the project requirement process node is completed, the process engine is transferred to the task splitting process node to automatically create a task order;

[0021] Step A33, when the task splitting process node is completed, the process engine transfers to the service splitting process node and automatically creates a service order;

[0022] Step A34, when the service splitting process node is completed, it is transferred to the service allocation process node through the process engine and a work order is automatically created.

[0023] A data operation management system based on a process engine, comprising:

[0024] Process splitting module, used to split data operation management into multiple process nodes;

[0025] The process engine module is connected to the process splitting module, which is used to define the process for each process node and connect the process nodes in series through the process engine;

[0026] The process execution module is used to obtain business projects and automatically initiate process nodes in a serial order through the process engine to perform operational management of business projects.

[0027] Further, the process definition of each process node includes a node form configuration, and each process node is associated with a corresponding node form configuration;

[0028] The process execution module is used to: through the process engine, after the previous process node completes the execution of the business project, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

[0029] Furthermore, the process engine module uses an open source form generation tool to perform visual node form configuration.

[0030] Furthermore, the process splitting module splits data operation management into process nodes including project requirements, task splitting, service splitting and service allocation;

[0031] The process engine module connects the process nodes in series according to the order of project requirements, task splitting, service splitting and service allocation through the process engine;

[0032] At the process node of project requirements, form demand information about business projects;

[0033] At the task splitting process node, the total task to complete the demand information is split into subtasks;

[0034] At the service splitting process node, split the subtask into multiple services;

[0035] At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

[0036] Furthermore, the process execution module executes:

[0037] In the process node of project requirements, a demand sheet is automatically created according to the business project;

[0038] When the project requirement process node is completed, it will be transferred to the task splitting process node through the process engine and a task order will be automatically created;

[0039] When the task splitting process node is completed, it is transferred to the service splitting process node through the process engine and a service order is automatically created;

[0040] When the service splitting process node is completed, it will flow to the service allocation process node through the process engine and automatically create a work order.

[0041] The beneficial technical effect of the present invention is that, under the premise of ensuring existing data applications, a method for data operation management based on a process engine is proposed to meet the new needs of scenario-based applications. The management of data operations is configured through the process engine, and the entire operation management work is connected in series to realize the digital management of data operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1-2A flowchart of the steps of a method for data operation management based on a process engine of the present invention;

[0043] Figure 3 The present invention is a flowchart of the steps of a method for data operation management based on a process engine. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0045] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0046] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

[0047] See also Figure 1 The present invention provides a data operation management method based on a process engine, comprising:

[0048] Step A1: split data operation management into multiple process nodes;

[0049] Step A2, define the process for each process node, and connect the process nodes in series through the process engine;

[0050] Step A3, obtain the business project, and automatically initiate the process nodes in a serial order through the process engine to perform operation management on the business project.

[0051] Specifically, the process engine is a flowable process engine. Combined with the flowable process engine, each process node is connected in series to achieve functions such as automatic initiation and closing of the process.

[0052] After the process is split and connected in series, and after the process is released, the process is initiated through the process initiation page. Each process node executes the process through the to-do task page, and the process operation process and completion status are recorded in real time. The process operation record and status can be viewed through the completed tasks page.

[0053] On the premise of ensuring the existing data applications, a data operation management method based on process engine is proposed to meet the new needs of scenario-based applications. The management of data operation is configured through process engine, and the entire operation management work is connected in series to realize the digital management of data operation.

[0054] Further, including:

[0055] The process definition of each process node includes a node form configuration; each process node is associated with a corresponding node form configuration;

[0056] In step A3, through the process engine, after the previous process node completes the execution of the business project, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

[0057] Specifically, the process definition is based on the flowable process engine and is configured through a self-developed visual process configuration tool to implement the process definition of each process node.

[0058] Specifically, the process definition of each process node not only includes the node form configuration of the process node, but also includes the process details, process node executors, etc.

[0059] The node executor of each process node has certain authority restrictions. Further, in step A2, a visual node form configuration is performed through an open source form generation tool.

[0060] Specifically, the visualization of the node form configuration can be achieved through Form Generator, that is, the open source form generation tool is Form Generator.

[0061] Furthermore, in step A1, data operation management is split into process nodes including project requirements, task splitting, service splitting and service allocation;

[0062] In step A2, the process engine connects the process nodes in series according to the order of project requirements, task splitting, service splitting and service allocation;

[0063] At the process node of project requirements, form demand information about business projects;

[0064] At the task splitting process node, the total task to complete the demand information is split into subtasks;

[0065] At the service splitting process node, split the subtask into multiple services;

[0066] At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

[0067] Data operation management is divided into processes such as demand orders, task orders, service orders, and work orders. Each process can be configured with process configuration and process node form configuration. The processes are connected in series through the process engine. Once there are new requirements and changes in the operation management process, they can be implemented simply and quickly through visual configuration, thereby meeting the digital management requirements of data operations.

[0068] Specifically, the demand list, such as which suppliers are needed, etc. The task list, such as different suppliers, the executors will split the tasks into subtasks according to the task list, for example, different suppliers correspond to one subtask. At the service splitting process node, one subtask forms a service list, and the executors can further subdivide a subtask into multiple services. At the service allocation process node, each service forms a work order, and the executors further split the service into multiple sub-services, and the sub-services are handed over to different personnel at the back to complete. For example, a service is divided into front-end sub-services and back-end sub-services, and the front-end is handed over to the front-end personnel to complete, and the back-end is handed over to the back-end personnel to complete.

[0069] See also Figure 2 , further, in step A3, the process of automatically initiating the process nodes in a serial order through the process engine to execute the business project includes:

[0070] Step A31, in the process node of project requirements, automatically create a requirement sheet according to the business project;

[0071] Step A32, when the project requirement process node is completed, the process engine is transferred to the task splitting process node to automatically create a task order;

[0072] Step A33, when the task splitting process node is completed, the process engine transfers to the service splitting process node and automatically creates a service order;

[0073] Step A34, when the service splitting process node is completed, it is transferred to the service allocation process node through the process engine and a work order is automatically created.

[0074] Specifically, after creating a demand order, if there is a task configuration requirement in the demand order, it will automatically flow to the task splitting process node, and automatically start a new task order instance through the flowable.start method. If there is a service configuration requirement in the task order, it will automatically flow to the service splitting process node, and automatically start a new service order instance through the flowable.start method.

[0075] Specifically, in each process node of the project requirement process node, project requirement process node, task splitting process node, and service splitting process node, the node form needs to be finally reviewed, and the next process node is triggered after the review is passed.

[0076] For example, in the process node of project requirements, after the demand form is formed, the demand form is reviewed. If the review is passed, it triggers the entry into the task splitting process node. If the review fails, the content in the demand form can be modified and reviewed again.

[0077] For example, in the task splitting process node, after the task order is created, the executor with the authority of the process node splits the task in the task order to form multiple tasks. Then the reviewer with the authority of the process node reviews the splitting results. If the review passes, it triggers entering the service splitting process node. If the review fails, the executor modifies the splitting results and submits them for review again.

[0078] For example, at the service splitting process node, after a service order is created, the executor with the authority of the process node splits the tasks in the service order to form multiple services. Then the reviewer with the authority of the process node reviews the splitting results. If the review passes, it triggers entry into the service allocation process node. If the review fails, the executor modifies the splitting results and submits them for review again.

[0079] For example, at the service allocation process node, after a work order is created, the executor with the authority of the process node allocates the service in the work order to form multiple sub-services. Then the reviewer with the authority of the process node reviews the split results. If the review is passed, the sub-services are handed over to the corresponding personnel to execute the sub-services. If the review fails, the executor modifies the split results and submits them for review again.

[0080] See also Figure 3 The present invention provides a data operation management system based on a process engine, comprising:

[0081] Process splitting module (1), used to split data operation management into multiple process nodes;

[0082] A process engine module (2), connected to the process splitting module (1), is used to define the process for each process node and connect the process nodes in series through the process engine;

[0083] The process execution module (3) is connected to the process engine module (2) and is used to obtain business projects and automatically initiate process nodes in a serial order through the process engine to perform operation management on the business projects.

[0084] Specifically, the process engine is a flowable process engine. Combined with the flowable process engine, each process node is connected in series to achieve functions such as automatic initiation and closing of the process.

[0085] After the process is split and connected in series, and after the process is released, the process is initiated through the process initiation page. Each process node executes the process through the to-do task page, and the process operation process and completion status are recorded in real time. The process operation record and status can be viewed through the completed tasks page.

[0086] On the premise of ensuring the existing data applications, a data operation management method based on process engine is proposed to meet the new needs of scenario-based applications. The management of data operation is configured through process engine, and the entire operation management work is connected in series to realize the digital management of data operation.

[0087] Further, the process definition of each process node includes a node form configuration, and each process node is associated with a corresponding node form configuration;

[0088] The process execution module (3) is used to: after the previous process node completes the execution of the business project through the process engine, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

[0089] Specifically, the process definition is based on the flowable process engine and is configured through a self-developed visual process configuration tool to implement the process definition of each process node.

[0090] Specifically, the process definition of each process node not only includes the node form configuration of the process node, but also includes the process details, process node executors, etc.

[0091] The node executor of each process node has certain authority restrictions.

[0092] Furthermore, the process engine module (2) performs visual node form configuration through an open source form generation tool.

[0093] Specifically, the visualization of the node form configuration can be achieved through Form Generator, that is, the open source form generation tool is Form Generator.

[0094] Furthermore, the process splitting module (1) splits the data operation management into process nodes including project requirements, task splitting, service splitting and service allocation;

[0095] The process engine module (2) connects the process nodes in series according to the order of project requirements, task splitting, service splitting and service allocation through the process engine;

[0096] At the process node of project requirements, form demand information about business projects;

[0097] At the task splitting process node, the total task to complete the demand information is split into subtasks;

[0098] At the service splitting process node, split the subtask into multiple services;

[0099] At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

[0100] Specifically, the demand list, such as which suppliers are needed, etc. The task list, such as different suppliers, the executors will split the tasks into subtasks according to the task list, for example, different suppliers correspond to one subtask. At the service splitting process node, one subtask forms a service list, and the executors can further subdivide a subtask into multiple services. At the service allocation process node, each service forms a work order, and the executors further split the service into multiple sub-services, and the sub-services are handed over to different personnel at the back to complete. For example, a service is divided into front-end sub-services and back-end sub-services, and the front-end is handed over to the front-end personnel to complete, and the back-end is handed over to the back-end personnel to complete.

[0101] Furthermore, the process execution module (3) executes:

[0102] In the process node of project requirements, a demand sheet is automatically created according to the business project;

[0103] When the project requirement process node is completed, it will be transferred to the task splitting process node through the process engine and a task order will be automatically created;

[0104] When the task splitting process node is completed, it is transferred to the service splitting process node through the process engine and a service order is automatically created;

[0105] When the service splitting process node is completed, it will flow to the service allocation process node through the process engine and automatically create a work order.

[0106] Specifically, after creating a demand order, if there is a task configuration requirement in the demand order, it will automatically flow to the task splitting process node, and automatically start a new task order instance through the flowable.start method. If there is a service configuration requirement in the task order, it will automatically flow to the service splitting process node, and automatically start a new service order instance through the flowable.start method.

[0107] Specifically, in each process node of the project requirement process node, project requirement process node, task splitting process node, and service splitting process node, the node form needs to be finally reviewed, and the next process node is triggered after the review is passed.

[0108] The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.

Claims

1. A data operation management method based on a process engine, characterized in that: include: Step A1: split data operation management into multiple process nodes; Step A2, defining a process for each of the process nodes, and connecting the process nodes in series through a process engine; Step A3, obtaining the business project, and automatically initiating the process nodes in a serial order through the process engine to perform operation management on the business project.

2. A data operation management method based on a process engine as claimed in claim 1, characterized in that: include: The process definition of each process node includes the node form configuration; Each process node is associated with the corresponding node form configuration; In step A3, through the process engine, after the previous process node completes the execution of the business project, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

3. A data operation management method based on a process engine as claimed in claim 2, characterized in that: In the step A2, a visual node form configuration is performed using an open source form generation tool.

4. A data operation management method based on a process engine as claimed in claim 2, characterized in that: In step A1, data operation management is divided into process nodes including project requirements, task splitting, service splitting and service allocation; In step A2, the process nodes are connected in series according to the order of project requirements, task splitting, service splitting and service allocation through the process engine; At the process node of project requirements, form demand information about business projects; At the task splitting process node, the total task to complete the demand information is split into subtasks; At the process node of service splitting, split the subtask into multiple services; At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

5. A data operation management method based on a process engine as claimed in claim 4, characterized in that: In step A3, the process of automatically initiating the process nodes in a serial order by the process engine to execute the business project includes: Step A31, in the process node of the project requirement, automatically create a requirement sheet according to the business project; Step A32, when the project requirement process node is completed, the process engine is transferred to the task splitting process node to automatically create a task order; Step A33, when the task splitting process node is completed, the process engine is transferred to the service splitting process node to automatically create a service order; Step A34, when the service splitting process node is completed, it is transferred to the service allocation process node through the process engine and a work order is automatically created.

6. A data operation management system based on a process engine, characterized in that: include: Process splitting module, used to split data operation management into multiple process nodes; A process engine module, connected to the process splitting module, is used to define the process for each of the process nodes and connect the process nodes in series through the process engine; The process execution module is used to obtain the business project and automatically initiate the process nodes in a serial order through the process engine to perform operation management on the business project.

7. A data operation management system based on a process engine as claimed in claim 6, characterized in that: The process definition of each of the process nodes includes a node form configuration, and each of the process nodes is associated with a corresponding node form configuration; The process execution module is used to: after the previous process node completes the execution of the business project through the process engine, the next process node automatically creates a node form according to the associated node form configuration to start executing the business project.

8. A data operation management system based on a process engine as claimed in claim 7, characterized in that: The process engine module performs visual node form configuration through an open source form generation tool.

9. A data operation management system based on a process engine as claimed in claim 7, characterized in that: The process splitting module splits data operation management into process nodes including project requirements, task splitting, service splitting and service allocation; The process engine module connects the process nodes in series according to the order of project requirements, task splitting, service splitting and service allocation through the process engine; At the process node of project requirements, form demand information about business projects; At the task splitting process node, the total task to complete the demand information is split into subtasks; At the process node of service splitting, split the subtask into multiple services; At the process node of service allocation, the service is split into sub-services, and the sub-services are allocated to corresponding operation objects, which complete the sub-services.

10. A data operation management system based on a process engine as claimed in claim 9, characterized in that: The process execution module executes: In the process node of project requirements, a requirement sheet is automatically created according to the business project; When the project requirement process node is completed, it is transferred to the task splitting process node through the process engine to automatically create a task order; When the task splitting process node is completed, it is transferred to the service splitting process node through the process engine to automatically create a service order; When the service splitting process node is completed, it is transferred to the service allocation process node through the process engine and a work order is automatically created.

Images