Business process configuration method and related equipment

Abstract

The embodiment of the invention discloses a business process configuration method and related equipment, which are used for performing business process configuration under the condition of improving the business process configuration efficiency. The method comprises the steps of obtaining a configuration item set of each business scene in a basic data configuration layer, constructing a process model of each business scene in a process model construction layer based on determined nodes of each business scene and association relationships among the nodes, and generating a scene configuration scheme of each business scene, storing the scene configuration scheme of each business scene generated in the process model building layer in a configuration result layer, displaying the scene configuration scheme of each business scene to a client through a target interface, and displaying the scene configuration scheme of each business scene according to a target process model of a target business scene determined by the client in a business operation layer. And dynamically loading an input value of a target configuration item of the target service scene input by the client, generating a service flow of the target service scene, and returning the service flow to the client for execution.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of business process configuration, and more specifically, to a business process configuration method, a business process configuration apparatus, a business process configuration device, a computer-readable storage medium, and a computer program product containing instructions. Background Art

[0002] As corporate business expands and the market changes, business processes need to be continuously adjusted and optimized, so the demand for business process configuration is increasing.

[0003] The existing business process configuration method involves developers writing the scripts required for the business process and submitting them to a code project. The submitted scripts and related code are then packaged to generate a deployable project package. This packaged code project is then exported as a program package, typically an executable file or installation package. Finally, the generated program package is deployed to the server, allowing it to run in the server environment. This method often uses pre-configured SQL scripts to initialize system data. Developers need to write and submit these scripts to ensure that the system has the necessary pre-configured data and business processes during installation or initialization.

[0004] However, in existing business process configuration methods, each client needs to manually write possibly identical business process scripts, resulting in repeated development. Therefore, the business process configuration efficiency is low. Summary of the Invention

[0005] The embodiments of the present application provide a business process configuration method, a business process configuration apparatus, a business process configuration device, a computer-readable storage medium, and a computer program product containing instructions, which can perform business process configuration while improving the efficiency of business process configuration.

[0006] In a first aspect, an embodiment of the present application provides a business process configuration method, which is applied to a server side and includes:

[0007] Classify the configuration items of the target common configuration item set according to the business scenario type at the basic data configuration layer to obtain a configuration item set for each business scenario. The target common configuration item set includes common and unique configuration items for each business scenario.

[0008] At the process model construction layer, a process model for each business scenario is constructed based on the nodes of each business scenario and the association relationship between the nodes. A scenario configuration solution for each business scenario is generated based on the process model of each business scenario and the configuration item set of each business scenario determined at the basic data configuration layer, where the nodes are associated with the corresponding required configuration items.

[0009] The scenario configuration scheme for each business scenario generated in the process model construction layer is stored in the configuration result layer, and the scenario configuration scheme for each business scenario is displayed to the client through the target interface;

[0010] At the business operation layer, based on the target process model of the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface are dynamically loaded, the business flow of the target business scenario is generated and returned to the client for execution.

[0011] In a second aspect, an embodiment of the present application provides a business process configuration device, including:

[0012] An acquisition unit, configured to classify configuration items of a target common configuration item set according to business scenario type at a basic data configuration layer to obtain a configuration item set for each business scenario, wherein the target common configuration item set includes common and unique configuration items for each business scenario;

[0013] A generating unit, configured to construct a process model for each business scenario based on the nodes of each business scenario and the associations between the nodes at the process model construction layer, and generate a scenario configuration solution for each business scenario based on the process model of each business scenario and the set of configuration items for each business scenario determined at the basic data configuration layer, wherein the nodes are associated with the corresponding required configuration items;

[0014] A presentation unit, configured to store, in a configuration result layer, a scenario configuration scheme for each business scenario generated in the process model construction layer, and present the scenario configuration scheme for each business scenario to a client through a target interface;

[0015] The generation unit is also used to dynamically load the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface at the business operation layer according to the target process model of the target business scenario determined by the client in the target interface, generate the business flow of the target business scenario and return it to the client for execution.

[0016] In a third aspect, an embodiment of the present application provides a business process configuration device, including:

[0017] CPU, memory, input and output interfaces, wired or wireless network interfaces, and power supply;

[0018] The memory is a transient storage memory or a persistent storage memory;

[0019] The central processing unit is configured to communicate with the memory and execute instruction operations in the memory to perform the aforementioned business process configuration method.

[0020] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions. When the instructions are executed on a computer, the computer executes the aforementioned business process configuration method.

[0021] In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when the computer program product is run on a computer, enables the computer to execute the aforementioned business process configuration method.

[0022] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages: centralized integration and management of configuration items in the basic data configuration layer to form common sets and classifications, which are convenient for sharing and reuse, and reduce duplicate definitions. A common process model is constructed in the process model construction layer, and the client directly selects the applicable model without having to write the script from scratch. In the business operation layer, the system dynamically generates business flows based on the model and input values ​​selected by the client, speeding up the configuration. The responsibilities of each layer of the layered architecture are clear, which facilitates development and maintenance, and makes the system more flexible to adapt to different business needs. The configuration items and process models of various business scenarios are pre-integrated, and the client only needs to select the corresponding business model and load the data to quickly generate the business flow, further reducing duplicate development. In summary, this application avoids the repeated development work caused by each client needing to manually write the same business process script through centralized management, preset models, dynamic generation and layered design. Therefore, the business process configuration efficiency is high. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a schematic diagram of the architecture of a business process configuration system disclosed in an embodiment of the present application;

[0024] Figure 2 A flowchart of a business process configuration method disclosed in an embodiment of the present application;

[0025] Figure 2-1 A schematic diagram of a layered architecture for configuring a business process disclosed in an embodiment of the present application;

[0026] Figure 2-2 A schematic diagram of a scenario configuration scheme interface disclosed in an embodiment of the present application;

[0027] Figure 3 This is a structural diagram of a business process configuration device disclosed in an embodiment of the present application;

[0028] Figure 4 This is a structural diagram of a business process configuration device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The embodiments of the present application provide a business process configuration method, a business process configuration apparatus, a business process configuration device, a computer-readable storage medium, and a computer program product containing instructions, which can perform business process configuration while improving the efficiency of business process configuration.

[0030] See also Figure 1 , the architecture of the business process configuration system in the embodiment of the present application includes:

[0031] Server 101 and client 102. When configuring a business process, server 101 can connect to client 102. Server 101 can classify the configuration items of the target general configuration item set according to the business scenario type at the basic data configuration layer to obtain a configuration item set for each business scenario. Then, at the process model construction layer, a process model for each business scenario is constructed based on the nodes of each business scenario and the associations between the nodes. A scenario configuration plan for each business scenario is generated based on the process model of each business scenario and the configuration item set for each business scenario determined at the basic data configuration layer. The scenario configuration plan for each business scenario generated at the process model construction layer is then stored at the configuration result layer and displayed to client 102 via the target interface. Finally, at the business operation layer, the target configuration item input values ​​of the target business scenario entered by the client in the target interface are dynamically loaded based on the target process model of the target business scenario determined by the client in the target interface, a business flow for the target business scenario is generated, and the business flow is returned to client 102 for execution.

[0032] based on Figure 1 The business process configuration system shown is shown in Figure 2 , Figure 2 This is a flow chart of a business process configuration method disclosed in an embodiment of the present application, which is applied to the server side. The server side includes a basic data configuration layer, a process model construction layer, a configuration result layer, and a business operation layer. The method includes:

[0033] 201. At the basic data configuration layer, the configuration items of the target general configuration item set are classified according to the business scenario type to obtain a configuration item set for each business scenario. The target general configuration item set includes common and unique configuration items for each business scenario.

[0034] In an optional implementation, this application utilizes four components to implement its functionality: basic configuration definition, scenario parameter definition, process model definition, and scenario configuration scheme definition. These four components are all based on the business process configuration platform and support dozens of mainstream databases on the market. The basic data configuration layer is the foundation of business process configuration, responsible for processing and managing the basic data and parameters required for all business scenarios. It provides flexible configuration management capabilities, enabling business process configuration to adapt to diverse business needs. The target common configuration item set includes configuration items common to all business scenarios as well as configuration items unique to each business scenario. Business scenario types refer to different business scenarios, such as order management, inventory management, and user management, each with its own specific requirements and processes. Specifically, the basic data configuration layer includes basic configuration definitions and scenario parameter definitions. Basic configuration definitions define the basic data for common business parameters required for configuration objects, including field visibility, default values, and generation rules. Scenario parameter definitions encapsulate system parameter combinations into scenario parameters. Users simply select a specific scenario to automatically generate the relevant parameter configurations. This allows for flexible system data pre-configuration, allowing multiple sets of data to be pre-configured at once, allowing users to select different data for initialization based on different business needs.

[0035] 202. In the process model construction layer, a process model for each business scenario is constructed based on the nodes of each business scenario and the relationship between the nodes, and a scenario configuration plan for each business scenario is generated based on the process model of each business scenario and the configuration item set of each business scenario determined in the basic data configuration layer. The nodes are associated with the corresponding required configuration items.

[0036] In an optional embodiment, the process model construction layer is the core part of the business process configuration, responsible for building the business process model. It allows users to select process nodes, define the process direction, draw flowcharts, and generate scenario configuration plans. The process model construction layer contains the core components of this application: process plan definition and scenario plan definition. The process plan library (process plan definition) is used to select process nodes, define the direction of the process and draw flowcharts. The scenario plan definition is used to select the process plan, select the required business parameters according to the process plan, and generate preset data, which is the data of the result layer.

[0037] Specifically, the process solution library is used to define business processes. It uses nodes to introduce the basic data (basic configuration definitions) and scenario parameters (scenario parameter definitions) required for the process. Process node information is stored in XML (Extensible Markup Language) and parsed using DOM4J (a Java API for parsing XML) to display the process information on the front end. The scenario configuration solution selects the corresponding business process from the process solution library, parses the corresponding process model, the basic configuration definitions involved in the process nodes, and the configurations in the scenario parameter definitions. It dynamically loads the corresponding basic data fields and parameter configurations, supporting the adjustment of field and parameter values. Based on the final solution release, the corresponding basic data is generated, parameter values ​​are modified, and the corresponding business flow is generated. This also involves XML parsing and metadata and parameter analysis, and the business flow API is called to generate the corresponding business flow. In this way, by combining the process model definition with the basic data and parameters, the business process and the corresponding basic data are organically integrated, making it possible to package and migrate functional modules.

[0038] 203. The scenario configuration scheme for each business scenario generated in the process model construction layer is stored in the configuration result layer, and the scenario configuration scheme for each business scenario is displayed to the client through the target interface.

[0039] In an optional implementation, the configuration result layer is responsible for storing the scenario configuration solutions generated by the process model construction layer and presenting these solutions to the client through the target interface, allowing users to view and select the appropriate business process configuration. In this way, the application has a one-click publishing and generation function for scenario configuration solutions.

[0040] 204. At the business operation layer, based on the target process model of the target business scenario determined by the client in the target interface, dynamically load the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface, generate the business flow of the target business scenario and return it to the client for execution.

[0041] In an optional implementation, the business operation layer dynamically generates a business flow based on the target process model selected by the user and the configuration item values ​​input, and returns the business flow to the client for execution.

[0042] The following example illustrates the business process configuration solution provided by this application:

[0043] See also Figure 2-1 , Figure 2-1 A schematic diagram of a layered architecture of a business process configuration disclosed in an embodiment of this application, comprising Figure 2-1It can be seen that the layered architecture includes the basic configuration layer (basic data configuration layer), the core processing layer (process model construction layer), the result layer (configuration result layer) and the business operation layer. The basic configuration definition of the basic configuration layer defines the settings of the basic data related field values ​​used in the business process, including the display and hiding of the fields, default values, whether they are required, editability, etc. The scenario parameter definition defines the parameter settings used in the business process, including system parameters and document parameters. These parameters are packaged into scenario parameters. After the user selects a specific business scenario, the relevant parameter configuration is automatically generated. The process solution library of the core processing layer contains process solution definitions, which are used to define the nodes of the business process and the relationship between nodes, and to build a process model. The scenario data package contains scenario configuration solutions and functions that support overall data packaging and migration. The scenario configuration solution is a configuration solution for a specific business scenario generated based on the process model and configuration items. It supports overall data packaging and migration, allowing the configuration solution to be packaged and migrated as a whole. The result layer (configuration result layer) stores the results of business process configuration, including basic data (static data used in the business process, such as product and user information), system parameters (system configuration parameters, such as operating environment parameters and default values), and business flows (generated business process instances for client execution). These results can be displayed to clients through the target interface. The business operation layer is the level where users interact with the system. Here, users can perform specific business operations, such as viewing, editing, and executing business processes.

[0044] More specifically, let's take the e-commerce order processing system as an example: in the basic data configuration layer, define the basic configuration items of the order management scenario, such as the display and hiding of fields such as order ID, user ID, and amount, and default values. Then, in the process model construction layer, build the order processing process model, define the nodes (such as order receipt, order verification, and order delivery) and their relationships, and generate the scenario configuration plan. Next, in the configuration result layer, store the configuration plan for the order processing scenario and present it to the user through the interface. Finally, in the business operation layer, based on the order processing process model selected by the user and the input configuration item values ​​(such as order priority and inventory threshold), dynamically generate the business flow and return it for execution. Through this design, business process configuration becomes more flexible and efficient, meeting the needs of different business scenarios.

[0045] In an optional embodiment, before the basic data configuration layer classifies the configuration items of the target general configuration item set according to the business scenario type to obtain the configuration item set for each business scenario, the method further includes: obtaining metadata of each business scenario from different data sources through a metadata parsing tool at the basic data configuration layer to integrate and obtain a general metadata set, and obtaining the target general configuration item set based on the general metadata set.

[0046] Specifically, metadata parsing tools can be used to identify all fields and field-related attributes (field type, required or not), system parameters, and document parameters in the basic data, and the parsed results can be provided for configuration selection. In this way, by using metadata parsing tools to obtain metadata from different data sources and integrate them into a common metadata set, data silos can be broken down and unified configuration and management of heterogeneous data sources can be achieved. Secondly, based on the common metadata set, the target common configuration item set is obtained, ensuring the integrity and consistency of the configuration items and providing a solid data foundation for business process configuration.

[0047] In one optional embodiment, obtaining a target set of general configuration items based on a general metadata set includes: obtaining an initial set of general configuration items based on the general metadata set; and obtaining an updated initial set of general configuration items based on a detected trigger signal for updating configuration items in the initial set of general configuration items. The updated initial set of general configuration items serves as the target set of general configuration items. This allows for updates to the initial set of general configuration items, promptly reflecting changes in business requirements and ensuring the accuracy and applicability of configuration items. Furthermore, after adjustments, the content can be integrated and easily migrated between systems for reuse.

[0048] In an optional implementation, the present application can first configure the basic configuration items required for the business process in the basic configuration layer, and then determine whether it is necessary to configure the scenario parameter definition. If so, enter the scenario parameter configuration step and configure the scenario parameters in the scenario parameter definition. If not, directly enter the process solution library, select or create a process solution (process model) from the process solution library, and then publish the generated process solution. In this way, you can selectively configure scenario parameters according to business needs, avoid unnecessary configuration steps, and improve configuration efficiency. For example, if a business process does not require additional parameter configuration, you can directly select an existing process model from the process solution library for deployment.

[0049] In an optional embodiment, a process model for each business scenario is constructed based on the determined nodes of each business scenario and the relationships between nodes, including: determining the nodes of each business scenario and the relationships between nodes according to the trigger signals of node selection and connection of each business scenario detected in the scenario configuration scheme interface, and constructing a process model for each business scenario based on the nodes of each business scenario and the relationships between nodes.

[0050] For details, please refer to Figure 2-2 , Figure 2-2 This is a schematic diagram of a scenario configuration scheme interface disclosed in an embodiment of the present application, which is composed of Figure 2-2It can be seen that the scenario configuration scheme interface specifically includes scenario configuration information, basic information (including the coding, name and effective status of the scenario configuration scheme, etc.), process information (including process coding, process name, process description, the switch for generating business flow and the organization to which the process belongs), flowchart (graphically displaying the nodes of the business process and the relationship between nodes. Users can add, delete, save nodes, etc. here), node configuration (displaying detailed configuration information of the node, such as node coding, node name, node type, etc.), other configuration information (planning information definition "including planning recommendation delivery model, supply network definition, planning scheme definition, planning scope definition, planning calendar and production transaction type definition, etc.", basic configuration "displaying the specific content of the basic configuration definition, such as planning organization, demand model and supply model, etc.", organizational parameters "displaying parameter configurations of different organizations, such as demand organization, supply network definition and inventory supply strategy, etc."). In this way, by detecting the user's operations in the scenario configuration scheme interface to determine the nodes and the relationship, the process of building the process model is simplified, the difficulty of users configuring business processes is reduced, and the configuration efficiency is improved.

[0051] In an optional embodiment, a process model for each business scenario is constructed based on the determined nodes of each business scenario and the associations between the nodes, including: obtaining a standard process model for each business scenario based on the determined standard nodes of each business scenario and the standard associations between the standard nodes, making sub-scenario adjustments to the standard process model of each business scenario for each sub-business scenario, obtaining a sub-process model for each sub-business scenario under each business scenario, and using the sub-process model for each sub-business scenario under each business scenario as the process model for each business scenario. Accordingly, according to the target process model of the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface are dynamically loaded, the business flow of the target business scenario is generated and returned to the client for execution, including: according to the target sub-process model of the target sub-business scenario under the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target sub-business scenario entered by the client in the target interface are dynamically loaded, the business flow of the target sub-business scenario is generated and returned to the client for execution.

[0052] Specifically, a business scenario is a broad, general business classification, such as "e-commerce order processing business," which covers all operations and processes related to order processing in the e-commerce field. Sub-business scenarios are smaller, more specific branches within this larger business scenario. For example, within the larger "e-commerce order processing business" scenario, different companies (Company A, Company B, Company C, etc.) can be divided into sub-scenarios, each with its own unique e-commerce order processing processes. While all of these sub-scenarios fall under the umbrella of e-commerce order processing, they each have their own unique characteristics, such as varying order processing rules, inventory management methods, or logistics and distribution processes. Introducing the concept of a standard process model for business scenarios and sub-process models for sub-business scenarios allows for better handling of complex business scenarios and improves the reusability and maintainability of process models. Furthermore, supporting the independent configuration and execution of sub-business scenarios makes business processes more flexible and modular, facilitating targeted adjustments and optimization. Furthermore, after adjustments, the content can be integrated and easily migrated between systems for reuse.

[0053] In an optional embodiment, based on the target process model of the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface are dynamically loaded, and before the business flow of the target business scenario is generated and returned to the client for execution, the method further includes: using the target process model of the target business scenario selected by the client in the target interface as the target process model of the determined target business scenario. In this way, before dynamically loading and generating the business flow, the process model selected by the user can be directly used as the determined target process model, thereby avoiding misuse or confusion of the process model, improving the efficiency of determining the target process model, and improving the reliability and efficiency of business process execution.

[0054] In an optional embodiment, based on the target process model of the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target business scenario input by the client in the target interface are dynamically loaded, and the business flow of the target business scenario is generated and returned to the client for execution. The method also includes: using the target process model of the target business scenario updated by the client in the target interface as the target process model of the determined target business scenario. In this way, the user is allowed to update the process model in the target interface for personalized updates (secondary development), and use the updated model as the determined target process model, so that the business process can adapt to changes in business needs in a timely manner, thereby improving the adaptability and competitiveness of the system. In addition, the scenario configuration solution supports one-click packaging and supports the introduction and export of packaged packages, and can quickly migrate and reuse the defined and verified more general scenario solution configurations as a whole.

[0055] For further information, see Figure 3, an embodiment of the business process configuration device in the embodiment of the present application includes:

[0056] An acquisition unit is used to classify the configuration items of the target common configuration item set according to the business scenario type at the basic data configuration layer to obtain a configuration item set for each business scenario. The target common configuration item set includes common and unique configuration items for each business scenario.

[0057] A generation unit is used to build a process model for each business scenario based on the nodes of each business scenario and the association relationship between the nodes at the process model construction layer, and generate a scenario configuration plan for each business scenario based on the process model of each business scenario and the configuration item set of each business scenario determined at the basic data configuration layer, with the nodes associated with the corresponding required configuration items;

[0058] The display unit is used to store the scenario configuration scheme of each business scenario generated in the process model construction layer in the configuration result layer, and display the scenario configuration scheme of each business scenario to the client through the target interface;

[0059] The generation unit is also used to dynamically load the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface according to the target process model of the target business scenario determined by the client in the target interface at the business operation layer, generate the business flow of the target business scenario and return it to the client for execution.

[0060] The acquisition unit is also used to obtain metadata of various business scenarios from different data sources through metadata parsing tools at the basic data configuration layer to integrate and obtain a common metadata set, and obtain a target common configuration item set based on the common metadata set.

[0061] The acquisition unit is specifically configured to obtain an initial general configuration item set based on the general metadata set, and obtain an updated initial general configuration item set according to a detected trigger signal for updating configuration items of the initial general configuration item set, wherein the updated initial general configuration item set is the target general configuration item set.

[0062] The generation unit is specifically used to determine the nodes of each business scenario and the relationship between nodes based on the trigger signals of node selection and connection of each business scenario detected in the scenario configuration scheme interface, and to build a process model for each business scenario based on the nodes of each business scenario and the relationship between nodes.

[0063] A generating unit is specifically configured to obtain a standard process model for each business scenario based on the determined standard nodes of each business scenario and the standard association relationship between the standard nodes, perform sub-scenario adjustments on the standard process model of each business scenario for each sub-business scenario, obtain a sub-process model for each sub-business scenario under each business scenario, and use the sub-process model for each sub-business scenario under each business scenario as the process model for each business scenario;

[0064] The generation unit is specifically used to dynamically load the input values ​​of the target configuration items of the target sub-business scenario entered by the client in the target interface according to the target sub-process model of the target sub-business scenario under the target business scenario determined by the client in the target interface, generate the business flow of the target sub-business scenario and return it to the client for execution.

[0065] The business process configuration device also includes:

[0066] The determination unit is configured to use the target process model of the target business scenario selected by the client in the target interface as the target process model of the determined target business scenario.

[0067] The determination unit is further configured to use the target process model of the target business scenario updated by the client in the target interface as the target process model of the determined target business scenario.

[0068] For further information, see Figure 4 , an embodiment of the business process configuration device in the embodiment of the present application includes:

[0069] CPU 401, memory 405, input / output interface 404, wired or wireless network interface 403 and power supply 402;

[0070] The memory 405 is a temporary storage memory or a permanent storage memory;

[0071] The CPU 401 is configured to communicate with the memory 405 and execute the instructions in the memory 405 to perform the aforementioned Figure 2 The method in the embodiment shown.

[0072] Furthermore, the embodiment of the present application also provides a computer-readable storage medium, which includes instructions. When the instructions are executed on a computer, the computer executes the aforementioned Figure 2 The method in the embodiment shown.

[0073] Furthermore, the present invention also provides a computer program product comprising instructions, which, when executed on a computer, causes the computer to execute the aforementioned Figure 2 The method in the embodiment shown.

[0074] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0075] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0076] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0077] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0078] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0079] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk, and other media that can store program code.

Claims

1. A business process configuration method, characterized in that: Applied to a server side, the server side includes a basic data configuration layer, a process model construction layer, a configuration result layer, and a business operation layer, and the method includes: Classifying the configuration items of the target general configuration item set according to the business scenario type at the basic data configuration layer to obtain a configuration item set for each business scenario, wherein the target general configuration item set includes common and unique configuration items for each business scenario; Constructing a process model for each business scenario at the process model construction layer based on the nodes of each business scenario and the association relationship between the nodes, and generating a scenario configuration solution for each business scenario based on the process model of each business scenario and the configuration item set of each business scenario determined at the basic data configuration layer, wherein the nodes are associated with the corresponding required configuration items; The scenario configuration scheme for each business scenario generated in the process model construction layer is stored in the configuration result layer, and the scenario configuration scheme for each business scenario is displayed to the client through the target interface; At the business operation layer, based on the target process model of the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface are dynamically loaded, the business flow of the target business scenario is generated and returned to the client for execution.

2. The method according to claim 1, characterized in that Before classifying the configuration items of the target general configuration item set according to the business scenario type at the basic data configuration layer to obtain the configuration item set for each business scenario, the method further includes: At the basic data configuration layer, metadata of various business scenarios from different data sources are obtained through metadata parsing tools to integrate and obtain a common metadata set, and the target common configuration item set is obtained based on the common metadata set.

3. The method according to claim 2, characterized in that The obtaining the target general configuration item set based on the general metadata set includes: Obtaining an initial set of general configuration items based on the general metadata set; According to the detected trigger signal for updating the configuration items of the initial general configuration item set, an updated initial general configuration item set is obtained, and the updated initial general configuration item set is the target general configuration item set.

4. The method according to claim 1, wherein The process model of each business scenario is constructed based on the determined nodes of each business scenario and the relationship between the nodes, including: Determine the nodes of each business scenario and the relationships between the nodes based on the trigger signals of node selection and connection of each business scenario detected in the scenario configuration scheme interface; A process model for each business scenario is constructed based on the nodes of each business scenario and the association relationships between the nodes.

5. The method according to claim 1, wherein The process model of each business scenario is constructed based on the determined nodes of each business scenario and the relationship between the nodes, including: Based on the determined standard nodes of each business scenario and the standard association relationships between the standard nodes, a standard process model for each business scenario is obtained; The standard process model of each business scenario is adjusted for each sub-business scenario to obtain a sub-process model of each sub-business scenario under each business scenario, and the sub-process model of each sub-business scenario under each business scenario is used as the process model of each business scenario; The step of dynamically loading the input values ​​of the target configuration items of the target business scenario input by the client in the target interface according to the target process model of the target business scenario determined by the client in the target interface, generating the business flow of the target business scenario and returning it to the client for execution includes: According to the target sub-process model of the target sub-business scenario under the target business scenario determined by the client in the target interface, the input values ​​of the target configuration items of the target sub-business scenario entered by the client in the target interface are dynamically loaded, and the business flow of the target sub-business scenario is generated and returned to the client for execution.

6. The method according to claim 1, wherein Before dynamically loading the input values ​​of the target configuration items of the target business scenario input by the client in the target interface based on the target process model of the target business scenario determined by the client in the target interface, generating the business flow of the target business scenario and returning it to the client for execution, the method further includes: The target process model of the target business scenario selected by the client in the target interface is used as the target process model of the determined target business scenario.

7. The method according to claim 1, characterized in that Before dynamically loading the input values ​​of the target configuration items of the target business scenario input by the client in the target interface based on the target process model of the target business scenario determined by the client in the target interface, generating the business flow of the target business scenario and returning it to the client for execution, the method further includes: The target process model of the target business scenario updated by the client in the target interface is used as the target process model of the determined target business scenario.

8. A business process configuration device, characterized in that: include: An acquisition unit, configured to classify configuration items of a target common configuration item set according to business scenario type at a basic data configuration layer to obtain a configuration item set for each business scenario, wherein the target common configuration item set includes common and unique configuration items for each business scenario; A generating unit, configured to construct a process model for each business scenario based on the nodes of each business scenario and the associations between the nodes at the process model construction layer, and generate a scenario configuration solution for each business scenario based on the process model of each business scenario and the set of configuration items for each business scenario determined at the basic data configuration layer, wherein the nodes are associated with the corresponding required configuration items; A presentation unit, configured to store, in a configuration result layer, a scenario configuration scheme for each business scenario generated in the process model construction layer, and present the scenario configuration scheme for each business scenario to a client through a target interface; The generation unit is also used to dynamically load the input values ​​of the target configuration items of the target business scenario entered by the client in the target interface at the business operation layer according to the target process model of the target business scenario determined by the client in the target interface, generate the business flow of the target business scenario and return it to the client for execution.

9. A business process configuration device, characterized in that: include: central processing unit and memory; The memory is a transient storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium comprises instructions, which, when executed on a computer, enable the computer to perform the method according to any one of claims 1 to 7.

11. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 7.

Images