Master data management process template construction method, device and equipment, and data approval method, device and equipment

Abstract

The invention relates to the technical field of electronic information, and discloses a master data management process template construction method, device and equipment, and a data approval method, device and equipment. Firstly, an initial parameter of a node required to be approved in a target business scene approval process is acquired; then, performing mapping integration processing on the initial parameters by utilizing the general node attribute structured data to construct an initial process template; then, outputting the initial process template so as to receive business parameters used for updating the initial process template; and finally, after the service parameters are received, performing mapping integration processing on the service parameters by using the general node attribute configuration template to update the initial process template to obtain a service process template. According to the main data management process template construction method, a general dynamic modeling method is adopted, and the dynamics and universality in the process modeling process are improved. And by adopting a dynamic variable transmission mode, the business scene requirements of a background system can be better met, so that the flexibility and adaptability of overall process modeling are improved.

Description

Technical Field

[0001] The present invention relates to the field of electronic information technology, and in particular to a master data management process template construction, data approval method, device and equipment. Background Art

[0002] Master data management is a critical data management strategy and process designed to ensure the consistency, accuracy and integrity of critical data within an organization.

[0003] In the related art, a lightweight business process engine is used to perform corresponding process modeling for different types of master data and different business scenarios. However, the method development efficiency in the related art is low. Therefore, it is necessary to propose a new master data management process template construction method. Summary of the invention

[0004] The implementation method of this specification aims to solve one of the technical problems in the related art at least to a certain extent. To this end, the implementation method of this specification proposes a master data management process template construction, data approval method, device and equipment.

[0005] This specification provides a method for constructing a master data management process template, the method comprising:

[0006] Obtain the initial parameters of the approval nodes required in the approval process of the target business scenario;

[0007] Mapping and integrating the initial parameters using the common node attribute structured data to construct an initial process template;

[0008] Outputting the initial process template so as to receive a business parameter for updating the initial process template;

[0009] After receiving the business parameters, the business parameters are mapped and integrated using a general node attribute configuration template to update the initial process template to obtain a business process template.

[0010] In one embodiment, there are multiple approval nodes, and the initial parameters include the process sequence of the approval nodes; the initial parameters are mapped and integrated using the common node attribute structured data to construct an initial process template, including:

[0011] Using a general node attribute configuration template, mapping and integrating the initial parameters of the approval nodes in sequence to determine a plurality of approval node templates;

[0012] According to the process sequence of the approval nodes, multiple approval node templates are connected to obtain an initial process template.

[0013] In one embodiment, the initial parameters include the person to be approved of the approval node; and the outputting of the initial process template to receive the business parameters for updating the initial process template includes:

[0014] In the case where there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template; wherein the business master data type and the business operation scenario are determined according to the input operation;

[0015] Outputting the approver of the approval node according to the initial process template;

[0016] Based on the selection operation of the persons to be approved at the approval node, determining the business approver of the approval node from the persons to be approved;

[0017] The business approver of the approval node is used to update the approver to be approved of the approval node to obtain the business parameter.

[0018] In one embodiment, the initial parameters include the person to be approved of the approval node and the custom content of the approval node; the outputting the initial process template to receive the business parameters for updating the initial process template also includes:

[0019] In the case where there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template;

[0020] According to the custom content of the approval node in the initial process template and the input content data, determine the target scenario node and output the approver of the target scenario node; wherein the target scenario node is the approval node to be output;

[0021] Determining a business approver of the target scenario node according to at least one approver assigned to the target scenario node;

[0022] The business approver of the target scene node is used to update the approver of the target scene node to obtain the business parameter of the target scene node.

[0023] In one embodiment, the mapping and integration processing of the business parameters using the general node attribute configuration template to update the initial process template includes:

[0024] Updating the process sequence of the target scene node;

[0025] Using a general node attribute configuration template, mapping and integrating the business parameters of the target scene nodes in sequence to determine a plurality of configuration node templates;

[0026] According to the updated process sequence of the target scene node, multiple configuration node templates are connected to obtain a business process template.

[0027] In one embodiment, the method further comprises:

[0028] Based on the business process template, push the approval details interface to the business approver of the target scenario node;

[0029] The approval result of the target scene node is determined according to the received approval parameter and the approval method of the target scene node.

[0030] In one embodiment, the method further comprises:

[0031] Determine the process sequence of the current target scene node; wherein the current target scene node corresponds to the next target scene node;

[0032] Determine a jump approval node based on the custom content of the current target scene node;

[0033] If the process sequence of the next target scenario node is smaller than the process sequence of the jump approval node, the approval details interface is pushed to the business approver of the jump approval node.

[0034] In one of the implementation modes, the method further includes: the approval mode is any one of signing and counter-signing, and the target business scenario is any one of adding, modifying and maintaining, cleaning, freezing, and deleting master data.

[0035] This specification provides a master data approval method, which includes:

[0036] Based on the business process template, push the approval details interface to the business approver, wherein the business process template is obtained according to any of the methods described above;

[0037] receiving an approval operation performed on the approval details interface, and determining an approval result based on the approval operation;

[0038] The approval result is output.

[0039] The present specification provides a master data management process template construction device, the device comprising:

[0040] The initial parameter acquisition module is used to obtain the initial parameters of the approval nodes required in the approval process of the target business scenario;

[0041] A process template determination module is used to map and integrate the initial parameters using the common node attribute structured data to construct an initial process template;

[0042] A business parameter acquisition module, used for outputting the initial process template so as to receive business parameters for updating the initial process template;

[0043] The business process template updating module is used to map and integrate the business parameters using a general node attribute configuration template after receiving the business parameters, so as to update the initial process template to obtain a business process template.

[0044] The present specification provides a master data approval device, the device comprising:

[0045] An approval details interface push module, used to push the approval details interface to the business approver based on the business process template, wherein the business process template is obtained according to the method according to any one of claims 1 to 8;

[0046] An approval result determination module, used for receiving an approval operation performed on the approval details interface, and determining an approval result based on the approval operation;

[0047] The approval result output module is used to output the approval result.

[0048] The present invention provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and wherein the processor implements the steps of the method described in any one of the above embodiments when executing the computer program.

[0049] The embodiments of this specification provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method described in any of the above embodiments are implemented.

[0050] An embodiment of the present specification provides a computer program product, wherein the computer program product includes instructions, and when the instructions are executed by a processor of a computer device, the computer device is enabled to perform the steps of the method described in any one of the above embodiments.

[0051] In the above-mentioned specification implementation, first, the initial parameters of the approval nodes required in the approval process of the target business scenario are obtained. Then, the initial parameters are mapped and integrated using the general node attribute structured data to construct an initial process template. Next, the initial process template is output to receive the business parameters for updating the initial process template. Finally, after receiving the business parameters, the business parameters are mapped and integrated using the general node attribute configuration template to update the initial process template to obtain the business process template. The above-mentioned master data management process template construction method adopts a general dynamic modeling method to improve the dynamic and universality in the process modeling process. Solve the problems of increased labor costs and reduced development efficiency and quality caused by the static and non-general offline process modeling methods of the existing process engine. By adopting the method of dynamically transferring variables, the business scenario requirements of the background system can be better met, thereby improving the flexibility and adaptability of the overall process modeling. Therefore, the above-mentioned implementation method can better cope with the ever-changing business needs, thereby improving the efficiency and quality of process modeling. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1a A flowchart of a method for constructing a master data management process template provided in the implementation manner of this specification;

[0053] Figure 1b A schematic diagram of the front-end page for adding TEST master data for the implementation method of this specification;

[0054] Figure 2a A schematic diagram of a process for constructing an initial process template provided in an implementation manner of this specification;

[0055] Figure 2b A newly added TEST master data process definition modeling diagram provided for the implementation method of this specification;

[0056] Figure 2c A schematic diagram of attribute configuration of a general node attribute configuration template provided in the implementation mode of this specification;

[0057] Figure 3 A schematic diagram of a process for obtaining service parameters provided in an implementation manner of this specification;

[0058] Figure 4 A schematic diagram of a process for obtaining the service parameters of a target scene node provided in an embodiment of this specification;

[0059] Figure 5 A flowchart of obtaining a business process template provided in the implementation mode of this specification;

[0060] Figure 6 A schematic diagram of a process for determining the approval result of a target scene node provided for an implementation mode of this specification;

[0061] Figure 7 A flowchart of a method for constructing a master data management process template provided in the implementation manner of this specification;

[0062] Figure 8 A flowchart of the master data approval method provided for the implementation of this specification;

[0063] Fig. 9 The overall architecture diagram of the master data Flowable process engine provided for the implementation of this specification;

[0064] Fig.10 A schematic diagram of a master data management process template construction device provided in an embodiment of this specification;

[0065] Fig.11 A schematic diagram of a master data approval device provided for an implementation of this specification;

[0066] Fig.12 An internal structural diagram of a computer device provided for an embodiment of this specification. DETAILED DESCRIPTION

[0067] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0068] Master data management is an important data management strategy and process that aims to ensure the consistency, accuracy and integrity of critical data within an organization. In large organizations, master data management involves data shared across multiple business units and applications, which is called "master data". Master data is required to perform key business processes.

[0069] The core goal of master data management is to ensure that key data serves as a single source of truth throughout an enterprise or organization. To achieve this goal, master data management covers a series of important steps, including defining standardized formats, rules, and processes for data to ensure data quality and accuracy. In addition, master data management is also responsible for managing the entire life cycle of data, such as from data creation and modification maintenance to data archiving and destruction.

[0070] It should be noted that master data management involves multiple key elements, which may include:

[0071] Master Data Identification: By introducing data experts to approve which data in the organization can be considered master data, ensuring the correct identification and management of critical data.

[0072] Master data standards: Develop standardized formats and rules for master data to ensure data consistency across different departments and applications.

[0073] Master data quality: Ensure the accuracy and completeness of master data through data cleaning, verification and other means, thereby improving data credibility and availability.

[0074] Master data sharing: Promote data sharing among different business departments within the organization to improve data reusability and liquidity and enhance collaboration efficiency.

[0075] Master Data Governance: Establish effective governance processes to ensure that the management and maintenance of master data are in line with business objectives and regulatory requirements, thereby reducing data management risks.

[0076] The above elements are closely connected and interdependent. Through workflow and layer-by-layer approval and verification, data quality can be effectively improved, data redundancy can be reduced, and the efficiency of business processes can be improved. This will make the collaboration and operation between departments smoother and the overall business more efficient.

[0077] In the related art, a lightweight business process engine written based on the BPMN2.0 standard is used to realize the automation of the business process of an enterprise. The engine provides a powerful process designer based on the BPMN 2.0 standard, which can help users design and draw complex business processes and can be integrated with other enterprise applications to realize the automation of business processes. In addition, the engine adopts an event-driven design, which makes it have excellent performance when processing large-scale business processes.

[0078] The data management system needs to define and maintain multiple types of master data, each of which involves five business scenarios, including creation, cleaning, modification and maintenance, freezing, and deletion, and needs to be completed through process approval. This means that if there are N types of master data that need to be governed, 5*N process definitions need to be created and maintained. The process definition modeling method requires manual offline flowchart drawing in the BMPN2.0 process definer, which causes professional developers to spend a lot of time on process modeling and cannot focus on their main work such as technology research and development innovation.

[0079] In addition, there is a need to dynamically skip nodes in the business. For example, in hierarchical approval, after the first level of approval is completed, according to the business scenario, there is no need for approval by more senior personnel. This requires dynamically skipping subsequent nodes and automatically completing the skipped nodes. There is a need to dynamically ignore nodes in the business. For example, in the reimbursement approval process, if the reimbursement expense is higher than 5K, it requires approval from both the finance and department leader nodes. If it is lower than 5K, only finance approval is required. Then, when the process is initiated, the department leader approval node needs to be ignored. However, the process engine in the relevant technology does not support dynamic and general configuration, and can only customize process definitions that meet specific scenarios. This reduces reusability, increases subsequent positioning problems and maintenance costs, and also limits the flexibility of the business.

[0080] In summary, the current non-universal static process modeling method does not make process modeling online a standard capability of the master data management system, which leads to increasing labor costs, reduced development efficiency, and extended development cycles.

[0081] Based on the above analysis, the implementation method of this specification provides a method for constructing a master data management process template. First, the initial parameters of the approval nodes required in the approval process of the target business scenario are obtained. Then, the initial parameters are mapped and integrated using the general node attribute structured data to construct an initial process template. Next, the initial process template is output to receive business parameters for updating the initial process template. Finally, after receiving the business parameters, the business parameters are mapped and integrated using the general node attribute configuration template to update the initial process template to obtain a business process template. The above-mentioned method for constructing a master data management process template adopts a general dynamic modeling method to improve the dynamics and universality of the process modeling process. It solves the problems of increased labor costs and reduced development efficiency and quality caused by the static and non-general offline process modeling methods of the existing process engine. By adopting the method of dynamically transferring variables, it can better meet the business scenario requirements of the background system, thereby improving the flexibility and adaptability of the overall process modeling. Therefore, the above-mentioned implementation method can better cope with the ever-changing business needs, thereby improving the efficiency and quality of process modeling.

[0082] This specification provides a method for constructing a master data management process template. Figure 1a The master data management process template construction method may include the following steps:

[0083] S110. Obtain initial parameters of approval nodes required in the approval process of the target business scenario.

[0084] The target business scenario may be a specific situation or operation type involved in a specific business operation or process, such as adding new master data or modifying and maintaining master data. The initial parameters may be the information or attributes required at the beginning of each approval node in the approval process of the target business scenario, such as the name of the approval node, the approver, etc.

[0085] Specifically, users need to define multiple different application scenarios for the types of master data they need. First, they must clearly define the application scenario that needs to be defined as the target application scenario, such as adding new master data. After determining the target application scenario, determine how many approval nodes are required to participate in the approval process of the target application scenario based on actual business conditions and needs. Subsequently, users need to configure each approval node in detail based on the determined approval node, and determine the initial parameters of each approval node, such as the initial parameters including but not limited to the name, order, approval method, approver, etc. of the approval node. By setting the initial parameters reasonably, users can ensure that the approval process can proceed smoothly in actual operation while meeting the needs and compliance requirements of the business process. In the back-end system, it is necessary to be able to interact with the configured initial parameters to obtain the initial parameters configured by the user for each approval node, so as to be used for the subsequent construction of the process template.

[0086] For example, the master data administrator logs in to the business scenario process management page to create process templates for business scenarios such as adding, cleaning, modifying and maintaining, freezing, and deleting master data. A process template includes several approval nodes, and each approval node can set initial parameters such as approval method, approval candidate, and copy recipient.

[0087] Take TEST master data as an example, and set the new TEST master data as the target business scenario. To configure the target business scenario, refer to Figure 1b , in the basic information section, configure the basic information for the target business scenario. The process name 102 of the target business scenario can be a newly added master data process definition. Description 104 can be a newly added TEST master data process definition, which is used to add notes or instructions for the target business scenario for subsequent review and understanding. Binding process type 106 can be a newly added master data, which is used to determine the target business scenario. Process engine 108 can be MDM, which is used to customize and optimize management processes for the target business scenario in the background. Approver source 110 can be MDM, which is used to determine the source of the approvers required for each approval node.

[0088] In the process setting section, configure the approval nodes for the target business scenario. The target business scenario of the newly added TEST master data can include three approval nodes. Set the node name 112 of the first approval node to preliminary review, the approval method 114 of the first approval node to joint signature, and the approvers 116 of the first approval node to A1, A3, B1. Set the node name 118 of the second approval node to review, the approval method 120 of the second approval node to or sign, and the approvers 122 of the second approval node to A2, B3, B2. Set the node name 124 of the third approval node to approval, the approval method 126 of the third approval node to or sign, and the approver 128 of the third approval node to C1. Among them, when each new approval node is added, a process sequence will be configured for it, which will be used to determine the order of approval later.

[0089] The backend system will call the above configuration information to obtain the initial parameters of the approval nodes required in the approval process of the target business scenario.

[0090] In some implementations, each approval node may be customized in the description 104, so that a technician can write a program according to the content in the description 104. In other implementations, there are more setting boxes after the approver of each approval node for custom configuration of each approval node.

[0091] S120, mapping and integrating the initial parameters using the common node attribute structured data to construct an initial process template.

[0092] S130: Output the initial process template to receive business parameters for updating the initial process template.

[0093] S140: After receiving the business parameters, the business parameters are mapped and integrated using the general node attribute configuration template to update the initial process template to obtain a business process template.

[0094] Among them, the general node attribute structured data can be a general data structure used to describe node attributes and parameters in the approval process. The initial process template can be a basic framework generated in the early stage of the approval process design. The business parameter can be the parameter information required for the approval process related to the specific business scenario. The business process template can be a template of the approval process designed according to the needs of a specific business scenario.

[0095] Specifically, the acquired initial parameters are integrated and mapped to the general node attribute structured data. The mapped parameters ensure that each approval node has the necessary configuration information, such as the completion conditions corresponding to each approval node. Therefore, using the mapped parameters, an initial approval process template framework is constructed to obtain an initial process template and configure a unique identifier for the initial process template to distinguish it from the business scenarios of other types of master data, so that each approval process template can be accurately identified and located later, thereby achieving more effective process management and optimization. In the actual business demand process, the constructed initial process template is output accordingly to receive the business parameters for updating. After receiving the business parameters, the acquired business parameters are integrated and mapped to the general node attribute structured data to update the data corresponding to the previous general node attribute structured data. Using the mapped parameters, the initial process template is updated to obtain a business process template suitable for a specific business scenario.

[0096] In the above-mentioned master data management process template construction method, first, the initial parameters of the approval nodes required in the target business scenario approval process are obtained. Then, the initial parameters are mapped and integrated using the general node attribute structured data to construct the initial process template. Next, the initial process template is output to receive the business parameters for updating the initial process template. Finally, after receiving the business parameters, the business parameters are mapped and integrated using the general node attribute configuration template to update the initial process template to obtain the business process template. The above-mentioned master data management process template construction method adopts a general dynamic modeling method to improve the dynamics and universality of the process modeling process. It solves the problems of increased labor costs and reduced development efficiency and quality caused by the static and non-general offline process modeling methods of the existing process engine. By adopting the method of dynamically transferring variables, it can better meet the business scenario requirements of the background system, thereby improving the flexibility and adaptability of the overall process modeling. Therefore, the above-mentioned implementation method can better cope with the ever-changing business needs, thereby improving the efficiency and quality of process modeling.

[0097] In some embodiments, see Figure 2a There are multiple approval nodes, and the initial parameters include the process sequence of the approval nodes; the initial parameters are mapped and integrated using the common node attribute structured data to construct an initial process template, which may include the following steps:

[0098] S210: Use the general node attribute configuration template to map and integrate the initial parameters of the approval nodes in sequence to determine multiple approval node templates.

[0099] S220. Connect multiple approval node templates according to the process sequence of the approval nodes to obtain an initial process template.

[0100] The approval node template may be a template corresponding to the initial parameters of the approval node that are configured.

[0101] Specifically, the general node attribute configuration template includes configuration information of the general attributes commonly included in each approval node, such as the name of the approval node, the approver, the completion condition, the sequence number, etc. The initial parameters of any approval node obtained are integrated and processed, and mapped to the general node attribute structured data. The mapped parameters ensure that the approval node has the necessary configuration information. Therefore, the approval node template corresponding to the approval node is constructed using the mapped parameters. Since there are multiple approval nodes, the above processing is performed for each approval node to obtain the approval node template corresponding to each approval node, thereby obtaining multiple approval node templates. Since there is a sequence between the approval nodes, the process sequence position of the approval node in the entire process is determined according to the process sequence corresponding to the approval node in the initial parameters of the approval node. Determining the sequence between multiple approval nodes based on the process sequence helps to ensure that the approval process is correctly executed according to the established flow logic and avoid confusion or wrong approval process sequence. Then, according to the process sequence of each approval node, the approval node template corresponding to each approval node is connected according to the process sequence to form a complete approval process template to obtain the initial process template. Configure a unique identifier for the initial process template to distinguish it from business scenarios of other types of master data, so that each approval process template can be accurately identified and located in the future, thereby achieving more effective process management and optimization.

[0102] It should be noted that you only need to pay attention to the number of approval nodes and determine the initial parameters of each approval node. Then use the general node attribute configuration template to determine the approval node template corresponding to each approval node to increase the versatility of process modeling. Regardless of how many application scenarios the master data corresponds to, how many approval nodes each application scenario corresponds to, and whether the application scenarios have the same approval node configuration, you can use the general node attribute configuration template to perform process modeling.

[0103] Exemplarily, the backend system implements the modeling function of the process by calling the BpmnModel module in the Flowable API. Specifically, the BpmnModel module is used to define and connect the various approval nodes, start nodes, and end nodes in the process. In this process, the BpmnModel module defines the start node as the start task StartEvent, defines the three approval nodes as the user task UserTask, and processes each approval node according to the common node attribute configuration template of the user task UserTask, and determines the approval node template corresponding to each approval node. In addition, in order to improve the process, the BpmnModel module adds an end node EndEvent to the process. Please refer to Figure 2b , use the sequence flow SequenceFlow to connect the three approval nodes of preliminary review, review, and approval as well as the start node and end node to obtain the initial process template and the newly added TEST master data process definition modeling diagram.

[0104] It should be noted that the BpmnModel module transforms the offline manual process modeling method into an online standard backend system function. It enables master data administrators (such as non-technical managers) to complete process configuration more easily without having to deeply understand complex technical details, thereby improving operational efficiency and accuracy. At the same time, it effectively reduces the labor cost of professional technicians intervening in process configuration, allowing technicians to devote more energy and time to technology development and innovation.

[0105] During the process modeling, the BpmnModel module uses a large number of system variables instead of constants before optimization for setting. Figure 2c The general node attribute configuration template of the user task UserTask includes the primary key ID, which is the process sequence of the approval node; the name, which is the node process of the approval node; the multi-instance type; the set (multi-instance), which is the set of approvers of the approval node; the cardinality (multi-instance), which is the total number of approvers of the approval node; the element variable (multi-instance), which is an approver of the approval node, used to describe the situation where a node needs to be executed multiple times according to certain rules; the assigned user, which is an approver who needs to approve, is used to achieve effective coordination and execution of tasks, ensuring that each task can be properly assigned to the approver responsible for execution; and the completion condition, which is the general EL expression of the completion condition of the approval node. Among them, the multi-instance type is set to Parallel, which generally does not need to be changed.

[0106] Finally, the background system calls the repositoryService in the Flowable API to complete the deployment of the initial process template, and saves the unique identifier of the initial process template, that is, the key information (key), to the business scenario list so that the initial process template can be accurately identified and located later.

[0107] In the above master data management process template construction method, the general node attribute configuration template is used to map and integrate the initial parameters of the approval nodes in turn, determine multiple approval node templates, and connect multiple approval node templates according to the process sequence of the approval nodes to obtain the initial process template, which provides a basis for the subsequent determination of specific business scenarios.

[0108] In some embodiments, see Figure 3 , the initial parameters include the approver of the approval node; outputting the initial process template so as to receive the business parameters for updating the initial process template may include the following steps:

[0109] S310: When there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template.

[0110] Among them, the business master data type and business operation scenario are determined according to the input operation.

[0111] Specifically, according to the user input operation, the business master data type and the business operation scenario corresponding to the input master data are determined. Using a matching algorithm, a rule engine or a predefined logic, the business master data type and the business operation scenario are used to search and match in at least one initial process template, and an initial process template matching it is determined from the at least one initial process template.

[0112] For example, a business person logs in to the master data maintenance page, adds a TEST master data and initiates a process. Based on the input data, the backend system determines that the business master data type is TEST master data and the business operation scenario is the newly added master data. Based on the business master data type and the business operation scenario, the initial process template corresponding to the newly added TEST master data is determined from at least one initial process template.

[0113] S320. Output the persons to be approved of the approval node according to the initial process template.

[0114] S330: Based on the selection operation of the person to be approved of the approval node, determine the business approver of the approval node from the persons to be approved.

[0115] S340: Use the business approver of the approval node to update the approver of the approval node to obtain business parameters.

[0116] The person to be approved can be a person who may perform the approval operation. The business approver can be a selected person with actual approval authority and responsibility.

[0117] Specifically, each approval node in the initial process template is configured with an approver, i.e., a person to be approved. After determining the initial process template, all approval nodes are identified, and the persons to be approved configured for each approval node are extracted therefrom. The persons to be approved configured for each approval node are returned for the user to select. Based on the persons to be approved provided by the system, the user assigns at least one person to be approved corresponding to each approval node according to the actual situation. After assigning the corresponding person to be approved to each approval node, obtain at least one person to be approved selected by each approval node and use it as the business approver. Using the obtained business approvers of each approval node, the persons to be approved of each approval node are updated, that is, the persons to be approved in the initial parameters are replaced with the business approvers, so that the initial parameters are updated to obtain the business parameters.

[0118] Exemplarily, the approvers configured in the approval node in the initial process template are returned to the business personnel for selection. The business personnel assign at least one approver to each approval node, and then click the submit button to send the request to the backend system. The backend system determines the business approver of the approval node from the approvers based on the selection operation of the approver of the approval node, and then uses the business approver of the approval node to update the approver of the approval node to obtain the business parameters.

[0119] In some implementations, the backend system matches the master data content and business operation scenarios submitted by the business personnel with the key information (key) corresponding to the process template, and determines the matched initial process template from at least one initial process template. According to the matched initial process template, the approver of the approval node is output, and based on the selection operation of the approver of the approval node, the business approver of the approval node is determined from the approver. The business approver of each approval node is transmitted to the runtimeService of FlowableAPI to dynamically determine the actual approver of each approval node. Compared with before optimization, the approver is fixed in the process definition. The above-mentioned method of dynamically transferring variables can better meet the business scenario requirements of the backend system and improve the dynamic nature of the overall process modeling.

[0120] In the above-mentioned master data management process template construction method, when there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and the matched initial process template is determined from at least one initial process template. According to the initial process template, the approver of the approval node is output, and based on the selection operation of the approver of the approval node, the business approver of the approval node is determined from the approver, and the business approver of the approval node is used to update the approver of the approval node, so as to obtain business parameters, determine the parameters required for the specific application scenario, and provide a data basis for the subsequent determination of the matching approval process.

[0121] In some embodiments, see Figure 4 The initial parameters include the approver of the approval node and the custom content of the approval node; outputting the initial process template to receive the business parameters for updating the initial process template may include the following steps:

[0122] S410: When there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template.

[0123] Specifically, according to the user input operation, the business master data type and the business operation scenario corresponding to the input master data are determined. Using a matching algorithm, a rule engine or a predefined logic, the business master data type and the business operation scenario are used to search and match in at least one initial process template, and an initial process template matching it is determined from the at least one initial process template.

[0124] S420: Determine the target scenario node and output the approver of the target scenario node according to the custom content of the approval node in the initial process template and the input content data.

[0125] Among them, the target scene node is the approval node required to be output.

[0126] Specifically, when analyzing the input content data, the custom content and input content data of the approval node in the initial process template are comprehensively considered, and the input content data is compared with the custom conditions of each approval node in the initial process template, that is, the custom settings of each approval node are checked one by one. When the input data does not meet the conditions of the approval node, the approval node is treated as an ignored node; when the input data meets the conditions of a certain approval node, the approval node is determined as the target scenario node. The node ignore function is implemented in the above manner to avoid problems caused by customized processes. After determining the target scenario node, the persons to be approved configured for each target scenario node are extracted, and the persons to be approved configured for each target scenario node are returned for the user to select.

[0127] For example, in the initial process template corresponding to the reimbursement approval process, there are two approval nodes, namely the financial approval node and the department leader approval node. The department leader approval node has a custom content corresponding to it, and the custom content is that if the reimbursement amount is less than 5K, the department leader approval node is ignored.

[0128] Therefore, when the input content data is expense reimbursement 6K, the target scenario nodes are determined to be the financial approval node and the department leader approval node according to the custom content of the department leader approval node in the initial process template and the input content data. When the input content data is expense reimbursement 4K, the target scenario node is determined to be the financial approval node according to the custom content of the department leader approval node in the initial process template and the input content data, and the department leader approval node will be ignored.

[0129] S430: Determine a business approver of the target scenario node according to at least one person to be approved assigned to the target scenario node.

[0130] S440: Use the business approver of the target scenario node to update the approver of the target scenario node to obtain the business parameters of the target scenario node.

[0131] Specifically, the user assigns at least one person to be approved corresponding to each target scene node according to the actual situation based on the person to be approved provided by the system, so as to ensure that each node has a corresponding approver. After assigning the corresponding person to be approved to each target scene node, obtain at least one person to be approved selected by each target scene node and use it as the business approver of the node. Using the acquired business approver of each target scene node, the person to be approved of each target scene node is updated, that is, the person to be approved in the initial parameters is replaced by the business approver, so that the initial parameters are updated to obtain the business parameters of the target scene node.

[0132] In the above-mentioned master data management process template construction method, when there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and the matched initial process template is determined from at least one initial process template. According to the custom content of the approval node in the initial process template and the input content data, the target scenario node is determined and the approver of the target scenario node is output. According to at least one approver assigned to the target scenario node, the business approver of the target scenario node is determined, and the approver of the target scenario node is updated using the business approver of the target scenario node. The business parameters of the target scenario node are obtained, and the parameters required for the specific application scenario are determined, so as to provide a data basis for the subsequent determination of the approval process that matches it.

[0133] In some embodiments, see Figure 5, using the general node attribute configuration template to map and integrate the business parameters to update the initial process template, which can include the following steps:

[0134] S510: Update the process sequence of the target scene node.

[0135] Specifically, since the number of target scene nodes is less than the number of approval nodes, the process sequence of the target scene nodes is discontinuous. In order to ensure the continuity and smoothness of the approval process, the process sequence of the target scene nodes needs to be updated and assigned, and the updated process sequence of the target scene nodes is continuous.

[0136] S520: Use the general node attribute configuration template to map and integrate the business parameters of the target scene nodes in sequence to determine multiple configuration node templates.

[0137] S530. Connect multiple configuration node templates according to the updated process sequence of the target scene node to obtain a business process template.

[0138] Specifically, the general node attribute configuration template includes configuration information of the general attributes commonly included in each target scene node, such as the name of the target scene node, the business approver, the completion condition, the process sequence, etc. The business parameters of any target scene node obtained are integrated and processed, and mapped to the general node attribute structured data so as to update the data corresponding to the general node attribute structured data before. The mapped parameters ensure that the target scene node has the necessary configuration information. Therefore, using the mapped parameters, the configuration node template corresponding to the target scene node is constructed. Since there are multiple target scene nodes, the above processing is performed for each target scene node to obtain the configuration node template corresponding to each target scene node, thereby obtaining multiple configuration node templates. Since there is a sequence between the target scene nodes, the process sequence position of the target scene node in the entire process is determined according to the process sequence of the updated target scene node. Determining the sequence between multiple target scene nodes based on the process sequence helps to ensure that the approval process is correctly executed according to the established flow logic and avoid confusion or wrong approval process sequence. Then, according to the updated process sequence of each target scenario node, the target scenario node template corresponding to each target scenario node is connected according to the process sequence to form a complete approval process template, thereby obtaining a business process template.

[0139] In some implementations, the background system deletes the ignored approval nodes from the approval node list, and then re-sorts and assigns values ​​to the remaining approval nodes, i.e., the process sequence of the target scenario nodes. When calling the runtimeService service in the Flowable API to generate a business process template, an unassigned variable exception is captured, and the process is directed to the end node, thereby terminating the process.

[0140] In the above-mentioned master data management process template construction method, the process sequence of the target scenario node is updated, and the business parameters of the target scenario node are mapped and integrated in turn using the general node attribute configuration template to determine multiple configuration node templates. According to the updated process sequence of the target scenario node, multiple configuration node templates are connected to obtain a business process template, thereby improving the dynamics and universality of the process modeling process.

[0141] In some embodiments, see Figure 6 , the method may further include the following steps:

[0142] S610: Based on the business process template, push the approval details interface to the business approver of the target scenario node.

[0143] S620: Determine the approval result of the target scene node according to the received approval parameters and the approval method of the target scene node.

[0144] The approval parameters may be information or operation options provided by the business approver during the approval process, and are used to determine the basis for the approval result.

[0145] Specifically, according to the business process template, it is determined that there is at least one target scenario node. According to the process sequence of the target scenario node, the corresponding approval details interface is pushed to each business approver of the corresponding target scenario node in turn. After receiving the approval details interface, the business approver will review the approval content and perform approval operations according to business needs to determine approval parameters, such as approval, rejection, transfer, etc. The approval result of the target scenario node is determined based on the received approval parameters and the approval method of the target scenario node.

[0146] In the above-mentioned master data management process template construction method, based on the business process template, the approval details interface is pushed to the business approver of the target scenario node, and the approval result of the target scenario node is determined according to the received approval parameters and the approval method of the target scenario node. The business process template is used to realize the automation of the approval process.

[0147] In some embodiments, see Figure 7 , the method may further include the following steps:

[0148] S710: Determine the process sequence of the current target scene node.

[0149] S720: Determine a jump approval node based on the custom content of the current target scene node.

[0150] S730: If the process sequence of the next target scenario node is smaller than the process sequence of the jump approval node, push the approval details interface to the business approver of the jump approval node.

[0151] Among them, the current target scene node corresponds to the next target scene node.

[0152] Specifically, the process sequence of the target scene node currently to be approved will be determined first, and then the custom content of the target scene node will be checked. The custom content may include approval rules, conditions or other constraints. If the custom content contains the conditions and nodes for jump approval, and the input content data meets the conditions for jump approval, the target scene node to be jumped to is determined to be the jump approval node based on the conditions and nodes for jump approval in the custom content. After all tasks under the target scene node currently to be approved have been approved and passed, the process sequence of the next target scene node corresponding to the current target scene node is compared with the process sequence of the jump approval node. If the process sequence of the next target scene node is less than the process sequence of the jump approval node, jump approval is required. If jump approval is required, the approval details interface will be pushed to each business approver corresponding to the jump approval node.

[0153] Exemplarily, when the background system uses the BpmnModel module for modeling, the process sequence of each target scene node is transmitted to the runtimeService service in the Flowable API to implement the node skipping function. Whenever the current target scene node is approved, the ability to skip nodes is dynamically implemented based on the process sequence of the next target scene node transmitted by the background system, namely NextPosition, and the process sequence of the jump approval node determined according to the custom content of the current target scene node, namely targetNextPosition. The skipped target scene node is approved by default. If the skipped target scene node is the last node, the process automatically ends with an approval result of approval.

[0154] In the above master data management process template construction method, the process sequence of the current target scenario node is determined, and the jump approval node is determined based on the custom content of the current target scenario node. If the process sequence of the next target scenario node is less than the process sequence of the jump approval node, the approval details interface is pushed to the business approver of the jump approval node, which increases the reusability of the function and facilitates subsequent operation and maintenance.

[0155] In some embodiments, the method further includes: the approval method is any one of signing or counter-signing.

[0156] Specifically, when the approval method is joint signing, the opinions of all business approvers must be considered. Therefore, the completion condition of joint signing is that all business approvers in the approval node need to approve it, that is, the number of business approvers who have approved it is the same as the cardinality (multiple instances) of the corresponding approval node, then the node will be considered passed. When the approval method is or-sign, the process will be more relaxed. The completion condition of or-sign is that at least one business approver approves it, that is, the number of business approvers who have approved it is greater than 1, then the node will be considered passed. However, it should be noted that if any of the business approvers rejects the approval, the entire process ends immediately.

[0157] It should be noted that the approval parameters can be parameters determined by the business approver corresponding to each approval node performing the operation. For example, the approval parameters can be pass, reject, etc., or they can be parameters used to characterize specific states, such as using parameter 1 to indicate pass and parameter 2 to indicate reject.

[0158] In the above master data management process template construction method, the approval method is either signature or joint signature, so that according to specific business needs and process design, a suitable approval method can be selected to implement the process.

[0159] In some implementations, the method further includes: the target business scenario is any one of adding, modifying and maintaining, cleaning, freezing, and deleting master data.

[0160] Specifically, as the business expands and develops, it may be necessary to add new master data to the system to support new business scope and market demand, so the newly added master data can be used as the target business scenario.

[0161] In actual business operations, data errors or inconsistencies may occur, which need to be corrected by modifying and maintaining master data. Therefore, modifying and maintaining master data can be used as a target business scenario.

[0162] Cleansing master data can identify and correct errors, omissions, duplications, and inconsistencies in data, thereby improving data accuracy, completeness, and consistency. Therefore, cleaning master data can be used as a target business scenario.

[0163] In some cases, freezing master data can reduce potential risks and errors. For example, during system maintenance or upgrades, master data can be frozen to avoid accidental modification or damage to data, thereby reducing the risk of business interruption and data loss. Therefore, freezing master data can be used as a target business scenario.

[0164] In order to clean up outdated, invalid or no longer needed data in the system to improve data quality and system performance, deleting unnecessary master data can make the system more streamlined and efficient, so deleting master data can be used as a target business scenario.

[0165] In the above master data management process template construction method, the target business scenario is any one of adding, modifying and maintaining, cleaning, freezing and deleting master data, so that according to specific business needs, a suitable target business scenario can be selected to implement the process.

[0166] This specification provides a master data approval method. Figure 8 , the master data approval method may include the following steps:

[0167] S810. Based on the business process template, push the approval details interface to the business approver.

[0168] The business process template is obtained according to any one of the above methods.

[0169] Specifically, when business data needs to be approved, the system receives and stores the business data. Then, the corresponding business process template is determined based on the stored data. The business process template includes the required nodes and the business approvers corresponding to each node. Once the approval process is triggered, the system will push the corresponding approval details interface to each business approver of the corresponding node in turn, and display the approval details interface for each business approver to view.

[0170] S820: Receive an approval operation performed on the approval details interface, and determine an approval result based on the approval operation.

[0171] S830. Output the approval result.

[0172] Specifically, after receiving the approval details interface, the approval content is approved, such as approval, rejection, transfer, etc. The corresponding approval parameters are determined for the approval operation performed on the approval details interface. The approval result of the node is determined based on the received approval parameters and the approval method of the corresponding node. If the approval result of the node is approved, the approval operation is continued for the next node. If all nodes are approved, the approval result indicating that the process is approved is output. If the approval result of any node is not passed or rejected, the process is terminated immediately, and the approval result indicating that the process is not approved is output.

[0173] Exemplarily, the approver logs in to the master data approval page, and then performs approval operations such as viewing, passing, and rejecting on the approval details interface.

[0174] In the above master data approval method, based on the business process template, the approval details interface is pushed to the business approver, the approval operation performed on the approval details interface is received, and the approval result is determined based on the approval operation, and the approval result is output to ensure the efficiency and reliability of the approval process.

[0175] The implementation method of this specification to implement the master data management process template construction method and the master data approval method may include three steps, please refer to Fig. 9 , the master data administrator configures through the process definition front-end interface and determines the initial parameters. The process definition back-end interface receives the initial parameters configured by the master data administrator and passes them to the Flowable process engine. The Flowable process engine uses the common node attribute structured data to map and integrate the initial parameters to achieve dynamic modeling of the process template to build the initial process template. The Flowable process engine publishes and deploys the constructed initial process template to make it an executable process definition. During the process definition deployment process, the Flowable process engine saves the used parameters and process information to the Flowable& business database.

[0176] Please continue reading Fig. 9 , business personnel input business master data types and business operation scenarios through the master data maintenance front-end interface. The master data maintenance back-end interface receives the business master data types and business operation scenarios input by business personnel, and passes them to the process template intelligent module. The process template intelligent module performs intelligent matching based on the business master data types and business operation scenarios, selects appropriate process templates from the existing process template library, and determines the initial process template that matches it. The initial process template is output for subsequent master data maintenance. In the master data maintenance process, the approver of each approval node is determined by dynamic parameter transmission. According to business needs and conditions, the corresponding parameters can be dynamically passed in at each node to determine the specific approver. Perform master data maintenance operations based on the initial process template and the approver obtained by dynamic parameter transmission. In the process of initiating / completing the process instance, the data obtained by dynamic parameter transmission can be stored in the Flowable& business database.

[0177] Please continue reading Fig. 9, the approver browses the master data to be approved through the process approval front-end page and performs the approval operation. The process approval back-end interface is responsible for connecting the front-end page and the Flowable process engine. Using the standard API interface of the Flowable process engine, the approval parameters such as approval details, pass or reject can be determined according to the approval operation. The corresponding parameters are dynamically passed in during the approval process. If a node meets specific conditions, the node is intelligently skipped based on the id of the next node of the node to improve the approval efficiency. Once the master data is approved, the subsequent business data can be further processed.

[0178] This specification provides a master data management process template construction device 1000, see Fig.10 The master data management process template construction device 1000 includes: an initial parameter acquisition module 1010 , a process template determination module 1020 , a business parameter acquisition module 1030 , and a business process template update module 1040 .

[0179] The initial parameter acquisition module 1010 is used to acquire the initial parameters of the approval nodes required in the approval process of the target business scenario;

[0180] The process template determination module 1020 is used to map and integrate the initial parameters using the common node attribute structured data to construct an initial process template;

[0181] The business parameter acquisition module 1030 is used to output the initial process template so as to receive the business parameters used to update the initial process template;

[0182] The business process template updating module 1040 is used to map and integrate the business parameters using the general node attribute configuration template after receiving the business parameters, so as to update the initial process template to obtain the business process template.

[0183] This specification embodiment provides a master data approval device 1100, see Fig.11 The master data approval device 1100 includes: an approval details interface push module 1110 , an approval result determination module 1120 , and an approval result output module 1130 .

[0184] An approval details interface push module 1110 is used to push the approval details interface to the business approver based on the business process template, wherein the business process template is obtained according to any one of the methods of claims 1-8;

[0185] The approval result determination module 1120 is used to receive the approval operation performed on the approval details interface and determine the approval result based on the approval operation;

[0186] The approval result output module 1130 is used to output the approval result.

[0187] For the specific description of the master data management process template construction and the master data approval device, please refer to the description of the master data management process template construction and the master data approval method in the above text, which will not be repeated here.

[0188] An embodiment of the present specification provides a computer device, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the method steps in the above embodiment are implemented.

[0189] An embodiment of the present specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method in any of the above embodiments are implemented.

[0190] One embodiment of the present specification provides a computer program product, which includes instructions. When the instructions are executed by a processor of a computer device, the computer device can perform the steps of the method of any of the above embodiments.

[0191] In some embodiments, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.12 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a master data management process template construction method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0192] Those skilled in the art will understand that Fig.12 The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution disclosed in this specification, and does not constitute a limitation on the computer device to which the solution disclosed in this specification is applied. Specifically, the computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0193] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing in a suitable manner if necessary, and then stored in a computer memory.

Claims

1. A method for constructing a master data management process template, characterized in that: The method comprises: Obtain the initial parameters of the approval nodes required in the approval process of the target business scenario; Mapping and integrating the initial parameters using the common node attribute structured data to construct an initial process template; Outputting the initial process template so as to receive a business parameter for updating the initial process template; After receiving the business parameters, the business parameters are mapped and integrated using a general node attribute configuration template to update the initial process template to obtain a business process template.

2. The method according to claim 1, characterized in that There are multiple approval nodes, and the initial parameters include the process sequence of the approval nodes; the initial parameters are mapped and integrated using the common node attribute structured data to construct an initial process template, including: Using a general node attribute configuration template, mapping and integrating the initial parameters of the approval nodes in sequence to determine a plurality of approval node templates; According to the process sequence of the approval nodes, multiple approval node templates are connected to obtain an initial process template.

3. The method according to claim 1, characterized in that The initial parameters include the person to be approved of the approval node; the outputting the initial process template so as to receive the business parameters for updating the initial process template includes: In the case where there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template; wherein the business master data type and the business operation scenario are determined according to the input operation; Outputting the approver of the approval node according to the initial process template; Based on the selection operation of the persons to be approved at the approval node, determining the business approver of the approval node from the persons to be approved; The business approver of the approval node is used to update the approver to be approved of the approval node to obtain the business parameter.

4. The method according to claim 1, characterized in that: The initial parameters include the approver of the approval node and the custom content of the approval node; The step of outputting the initial process template so as to receive a business parameter for updating the initial process template further includes: In the case where there is at least one initial process template, matching is performed based on the business master data type and the business operation scenario, and a matched initial process template is determined from the at least one initial process template; According to the custom content of the approval node in the initial process template and the input content data, determine the target scenario node and output the approver of the target scenario node; wherein the target scenario node is the approval node to be output; Determining a business approver of the target scenario node according to at least one approver assigned to the target scenario node; The business approver of the target scene node is used to update the approver of the target scene node to obtain the business parameter of the target scene node.

5. The method according to claim 4, characterized in that The mapping and integration processing of the business parameters by using the general node attribute configuration template to update the initial process template includes: Updating the process sequence of the target scene node; Using a general node attribute configuration template, mapping and integrating the business parameters of the target scene nodes in sequence to determine a plurality of configuration node templates; According to the updated process sequence of the target scene node, multiple configuration node templates are connected to obtain a business process template.

6. The method according to claim 1, characterized in that The method further comprises: Based on the business process template, push the approval details interface to the business approver of the target scenario node; The approval result of the target scene node is determined according to the received approval parameter and the approval method of the target scene node.

7. The method according to claim 6, characterized in that The method further comprises: Determine the process sequence of the current target scene node; wherein the current target scene node corresponds to the next target scene node; Determine a jump approval node based on the custom content of the current target scene node; If the process sequence of the next target scenario node is smaller than the process sequence of the jump approval node, the approval details interface is pushed to the business approver of the jump approval node.

8. The method according to claim 1, characterized in that The method also includes: the approval mode is any one of signing or counter-signing, and the target business scenario is any one of adding, modifying and maintaining, cleaning, freezing, and deleting master data.

9. A master data approval method, characterized in that: The method comprises: Based on the business process template, pushing the approval details interface to the business approver, wherein the business process template is obtained according to the method according to any one of claims 1 to 8; receiving an approval operation performed on the approval details interface, and determining an approval result based on the approval operation; The approval result is output.

10. A master data management process template construction device, characterized in that: The device comprises: The initial parameter acquisition module is used to obtain the initial parameters of the approval nodes required in the approval process of the target business scenario; A process template determination module is used to map and integrate the initial parameters using the common node attribute structured data to construct an initial process template; A business parameter acquisition module, used for outputting the initial process template so as to receive business parameters for updating the initial process template; The business process template updating module is used to map and integrate the business parameters using a general node attribute configuration template after receiving the business parameters, so as to update the initial process template to obtain a business process template.

11. A master data approval device, characterized in that: The device comprises: An approval details interface push module, used to push the approval details interface to the business approver based on the business process template, wherein the business process template is obtained according to the method according to any one of claims 1 to 8; An approval result determination module, used for receiving an approval operation performed on the approval details interface, and determining an approval result based on the approval operation; The approval result output module is used to output the approval result.

12. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 9 are implemented.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images