CN117764538A - Business process generation method, device and equipment - Google Patents

Abstract

The invention provides a method, a device and equipment for generating a business process. The method for generating the business process comprises the following steps: acquiring attribute information of a water management system in a metadata form; configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow. The scheme provided by the invention can realize the rapid adaptation and personalized operation of the flow change of the water management system.

Description

A business process generation method, device and equipment

Technical field

The present invention relates to the technical field of computer information processing, and in particular, to a method, device and equipment for generating a business process.

Background technique

In the smart water industry, faced with the highly customized needs of plant and station management systems of different sizes and needs, traditional water management system solutions often appear to be inflexible and poorly adaptable. These systems are often hard-coded and have difficulty adapting quickly to changes in business processes and emerging operational needs.

Contents of the invention

The invention provides a method, device and equipment for generating a business process, which solves the technical problem that the existing system cannot adaptively generate a water affairs business process.

In order to solve the above technical problems, the technical solutions of the present invention are as follows:

A business process generation method, including:

Obtain water management system attribute information in the form of metadata;

Configure the component elements required for the water affairs business process according to the water management system attribute information in the form of metadata;

Call at least one component element through microservice events;

Perform at least one operation on the at least one component element in the template area of the water affairs business process to generate a water affairs business process.

Optionally, obtain water management system attribute information in the form of metadata, including:

Obtain water management system attribute information in the form of metadata from a preset data source.

Optionally, configure the component elements required for the water affairs business process based on the water management system attribute information in the form of metadata, including:

Analyze the water management system attribute information in the form of metadata to obtain configuration information;

Configure attributes of component elements required by the water business process according to the configuration information.

Optionally, call at least one component element through microservice events, including:

Obtain each node of the water business process and the logical relationship between each node;

According to each node of the water business process and the logical relationship between the nodes, at least one component element is called through the microservice event.

Optionally, according to each node of the water business process and the logical relationship between the nodes, at least one component element is called through microservice events, including:

According to each node of the water business process, call the microservice event corresponding to each node;

According to the logical relationship between the nodes, at least one component element is called through the microservice event corresponding to each node, where one microservice event corresponds to one component element.

Optionally, perform at least one operation on the at least one component element in the template area of the water affairs business process to generate a water affairs business process, including:

Get the template area of the water business process;

placing the at least one component element in the template area;

Perform at least one operation on the at least one component element to generate a water business process.

Optional business process generation methods also include:

The process data of the water business process belonging to different users are isolated and/or encrypted and stored.

Embodiments of the present invention also provide a device for generating a business process, which includes:

The acquisition module is used to obtain the attribute information of the water management system in the form of metadata;

A processing module configured to configure the component elements required for the water affairs business process based on the water affairs management system attribute information in the form of metadata; to call at least one component element through microservice events; to configure the at least one component element in the water affairs business process Perform at least one operation in the template area to generate a water business process.

The present invention also provides a computing device, including: a processor and a memory storing a computer program. When the computer program is run by the processor, the method as described above is executed.

The present invention also provides a computer-readable storage medium that stores instructions. When the instructions are run on a computer, they cause the computer to execute the method as described above.

The above solution of the present invention at least includes the following beneficial effects:

The above solution of the present invention obtains the water management system attribute information in the form of metadata; configures the component elements required for the water affairs business process according to the water management system attribute information in the metadata form; and calls at least one component through microservice events. Elements; perform at least one operation on the at least one component element in the template area of the water affairs business process to generate the water affairs business process. The generated business process of the water affairs management system can be generated through adaptive operations, which improves the efficiency of business process generation. , and can meet the needs of smart water services.

Description of the drawings

Figure 1 is a schematic flow chart of a business process generation method according to an embodiment of the present invention;

Figure 2 is a schematic diagram of the module architecture of the water management system of the business process according to the embodiment of the present invention;

Figure 3 is a schematic diagram of the module architecture of microservices and containerized business deployment of the business process according to the embodiment of the present invention;

Figure 4 is a schematic diagram of the module architecture of the business process according to the embodiment of the present invention;

Figure 5 is an architectural schematic diagram of the multi-tenant data management isolation mechanism of the business process according to the embodiment of the present invention;

Figure 6 is a structural diagram of a business process generating device according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a thorough understanding of the invention, and to fully convey the scope of the invention to those skilled in the art.

As shown in Figure 1, an embodiment of the present invention proposes a method for generating a business process, which includes:

Step 11: Obtain the water management system attribute information in the form of metadata;

Step 12: Configure the component elements required for the water affairs business process based on the water management system attribute information in the form of metadata;

Step 13: Call at least one component element through microservice events;

Step 14: Perform at least one operation on the at least one component element in the template area of the water business process to generate a water business process.

This embodiment of the present invention obtains the water management system attribute information in the form of metadata; configures the component elements required for the water affairs business process according to the water management system attribute information in the metadata form; and calls at least one component through microservice events. Element; perform at least one operation on the at least one component element in the template area of the water affairs business process to generate the water affairs business process. The business process of the water affairs management system can be generated through adaptive operations, which improves the efficiency of business process generation, And can meet the needs of smart water services.

As shown in Figure 2, it is a schematic diagram of the module architecture of the water management system, including: edge device access layer, data collection layer located above the edge device access layer. After the data collection layer collects data, it is transmitted to the platform layer through the network layer. Relevant equipment management module, data analysis module and application management module; the platform layer transmits the results of relevant data processing to the application service layer for generating corresponding water affairs business processes. The application service layer provides water management system attribute information in the form of metadata ; According to the water management system attribute information in the form of metadata, configure the component elements required for the water affairs business process; call at least one component element through microservice events; place the at least one component element in the template area of the water affairs business process Perform at least one operation to generate a water affairs business process; finally, display the water affairs business process on the presentation layer.

Specifically, the application service layer supports data-driven dynamic attribute management: when the system starts, metadata is first loaded from preset sources (such as databases, configuration files, environment variables, etc.). These metadata contain critical information about system behavior and properties;

Parse and apply configuration: The system parses this metadata and configures itself based on this information. Including setting database connection, service port, security policy, etc.

Dynamic attribute management defines various attributes in the system, such as connection strings, service parameters, etc. These properties are not statically defined in code, but dynamically specified through metadata.

Property reading and application: The system reads these properties at runtime and adjusts its behavior based on the property value. For example, changing the database connection string allows the system to connect to a different database.

Runtime configuration adjustment, dynamic modification support: The system design allows dynamic modification of metadata at runtime, thereby changing system behavior. This modification can be performed through various interfaces, such as web interface, API calls, etc.

Real-time reaction: After modifying metadata, the system can react to these changes in real time or under predetermined conditions without restarting or reloading.

In an optional embodiment of the present invention, step 11 includes:

Obtain water management system attribute information in the form of metadata from a preset data source.

In the above embodiment, the metadata is data describing the data and its environment, including attribute information about system behavior. The preset data sources include: database, configuration files, environment variables, etc. The system attribute information includes connection strings, service parameters, etc. Further, the system can dynamically obtain the modified system attribute information in the form of metadata at runtime, so that the system attribute information is not statically defined in the data, but dynamically specified through metadata.

Further, according to the system attribute information in the form of metadata obtained in the preset data source, configure corresponding component elements for the business process; then call at least one component element that constitutes the business process through microservice events; finally Place at least one of the called component elements in the obtained template area and perform at least one operation to generate the business process. To solve the technical problem that the existing system is not flexible enough and has poor adaptability, making it difficult to adapt to changes in business processes and personalized operations.

In an optional embodiment of the present invention, step 12 includes:

Step 121, parse the water management system attribute information in the form of metadata to obtain configuration information;

Step 122: Configure attributes of component elements required for the water business process according to the configuration information.

In this embodiment, the configuration information includes database connection information, service port information, security policy information, etc. The database connection information includes host name, user name, password, etc., and the service port information may be a designated system communication port number, etc.

Specifically, in the water management system, the component elements may include: work order management, water pump room management, water tank cleaning business, process monitoring, inspection business, document library, equipment management, operation analysis, etc. The components constituting the component elements may include: preset built models and preset built scenes. Among them, the preset built models include: drainage pit valve, submersible pump, pressure relief valve, flow meter, pressure meter, pump, online residual chlorine meter, online turbidity meter, UV disinfection meter, float level switch, Hydrostatic liquid level meter, water tank inlet flow meter, total inlet flow meter, valve, pipe network pressure gauge, axial flow fan, dehumidifier, ball machine, spotlight, waterproof fluorescent lamp, access control, disinfection control cabinet, sewage control boxes, lighting distribution boxes, sub-control cabinets, main control cabinets, etc. The preset construction scenarios may include: single-unit pump room, double-unit pump room, three-unit pump room, four-unit pump room, etc.

Among them, parsing the system attribute information in the form of metadata refers to parsing and understanding the structure, meaning and relationship of the system attribute information in the metadata form. By parsing the system attribute information in the metadata form, the configuration obtained after the analysis is The information configures attributes of the component elements, enabling the component elements to understand the meaning, attributes, and relationships between the system attribute information, etc.

Since the system attribute information in the form of metadata can be dynamically modified, the system can obtain the modified system attribute information in the form of metadata during runtime and parse the system attribute information in the form of metadata to obtain new The configuration information is obtained, and then the new configuration information is used to configure attributes of the component elements, thereby realizing dynamic attribute management of the system, which can be completed without restarting or reloading the system. For example, changing the database connection string in the system property information can allow the component elements to connect to different databases.

And by using metadata to configure attributes of component elements in the water business process, it not only provides higher flexibility, but also allows you to customize the data structure and business process logic through a simple interface, which can speed up business adaptation and innovation. speed.

In an optional embodiment of the present invention, the above step 13 may include:

Step 131: Obtain each node of the water business process and the logical relationship between each node;

Step 132: Call at least one component element through microservice events according to each node of the water business process and the logical relationship between the nodes.

In an optional embodiment of the present invention, the above step 132 may include:

Step 1321: According to each node of the water business process, call the microservice event corresponding to each node;

Step 1322: According to the logical relationship between the nodes, at least one component element is called through the microservice event corresponding to each node, where one microservice event corresponds to one component element.

In the above embodiment, based on obtaining each node of the water business process and the number of component elements corresponding to each node, a corresponding number of microservice events are established for each node to ensure that each microservice event corresponds to a component element. Then according to the logical relationship between the nodes, the corresponding microservice event is called. The microservice events can all run independently, allowing users to independently upgrade and maintain component elements without affecting the normal operation of other component elements. Since the microservice events are called according to the logical relationship between the nodes, so that each microservice event corresponds to a specific function, it is also necessary to define responsibilities, interfaces and interaction protocols for each microservice event.

Through microservice events, each component element can be called independently, just like placing each component element (such as user rights management, work order management, process monitoring, etc.) in different "small boxes" to run separately. Do not interfere with each other. Since each microservice event can be developed by an independent team, different technology stacks and databases may be used between microservice events. Therefore, it is also necessary to define interfaces and contracts between microservice events to ensure compatibility between microservice events. and interoperability.

The nodes of the water business process are equivalent to the container images of one or more microservice events. The nodes contain the code, runtime library and setting information required to run the microservice events corresponding to the nodes. Use container management tools to handle the creation, deployment, scaling, and termination of said nodes. Use automation tools (such as CI/CD pipelines) to deploy microservice events to corresponding nodes, such as test nodes, pre-production nodes, production nodes, etc.

For the water management system, different component elements can be generated into independent microservices, and then deployed and run in the corresponding nodes. For example, we can deploy these component elements to a node to run so that it can independently monitor and analyze data. At the same time, we can also deploy a component element, such as a data analysis component, to another node to run it so that it can independently perform data analysis. Analysis and report generation work.

The component elements are deployed to the corresponding nodes through microservice events, which improves the maintainability and scalability of the system, allowing users to independently upgrade and maintain a module without affecting the normal operation of other modules. At the same time, rapid deployment and expansion are achieved through container technologies such as Docker to adapt to distributed and heterogeneous environments. Especially in the water management system, it can combine the characteristics of water plants and stations, bringing significant improvements to the reliability, maintainability and scalability of the water management system, and is particularly suitable for decentralized water infrastructure management.

In an implementable example, the graphical water business process generation process is:

1. User interface initialization, startup interface: When the user starts the tool, an intuitive user interface is first displayed, which usually includes a menu bar, toolbar, process design area and attribute editing area. Load component library: The tool loads a component library containing various components from which the user can select the required components.

2. Create a new water business process: Start a new water business process, with a blank canvas or basic template for users to edit.

Select and place components: Users select the required nodes from the component library and place them in the design area through drag-and-drop operations.

3. Design and connect process nodes: Users connect various nodes through visual connection lines to form a complete graphical water business process. These connecting lines represent data flow or control flow.

Configure node attributes: Each node has its own attributes. You can click on the node and configure it in the attribute editing area, such as setting parameters, defining behaviors, etc.

Further, graphical tools can be used to create or modify graphical water business process diagrams. Graphical tools display relevant parameters and expected results in real time to help operators make decisions.

Among them, the graphical water business process design tool includes two custom drag-and-drop modules. The first one is a visual interface for displaying interface information of functional modules such as secondary supply pump room management, water tank cleaning business, process monitoring, inspection business, document library, equipment management, and operation analysis. It can be freely dragged and combined. Define the generated business process. The second one is for the process monitoring module, which can carry out graphical model process design, including 2D, 3D and other effects. Real-life pictures of the installation site process equipment are modeled into corresponding plane or 3D stereoscopic diagrams for display. The graphical water business process design tool allows users to connect various nodes through visual connection lines to form a complete process flow. These connecting lines represent data flow or control flow. And the tool displays relevant parameters and expected results in real time to help users operate. This tool simplifies complex water business process design into intuitive graphical operations. Compared with traditional methods of coding or fixed templates, this method is easier to use, can respond faster to actual operational changes, and improves operations. autonomy and flexibility.

As shown in Figure 3, microservices and containerized business deployment:

1. Define microservice architecture and service splitting: Split the application into multiple small, independent services. Each service is responsible for a specific function of the application, such as user rights management, work order management, process monitoring, etc.

Service Definition: Define the responsibilities, interfaces and interaction protocols for each microservice.

2. Develop microservices: Each microservice is developed independently, using potentially different technology stacks and databases.

Define interfaces and contracts for communication between services to ensure compatibility and interoperability between services.

3. Containerize services and build container images: Build a container image for each microservice, which contains the code, runtime, libraries and settings required to run the service.

Container management: Use container management tools (such as Docker, Kubernetes) to handle the creation, deployment, scaling and termination of containers.

4. Deploy microservices, automatic deployment: Use automation tools (such as CI/CD pipelines) to deploy microservices into predefined environments, such as testing, pre-production, production, etc.

Service discovery: Configure the service discovery mechanism so that microservices can find and communicate with each other.

Highly customized front-end UI component library:

1. Requirements analysis: First conduct a requirements analysis to determine which types of components (such as buttons, tables, input boxes, charts, etc.) are necessary.

Design Principles: Determine the principles and standards for component design, such as accessibility, responsive design, consistency, and extensibility.

2. Component development, prototype design: Design a prototype for each component to determine its basic structure and function.

Coding implementation: Use front-end technologies (such as HTML, CSS, JavaScript, React, Vue.js, etc.) to code these components.

Style customization: Implement the style customization function of components so that the appearance can be easily changed as needed.

3. Component testing, unit testing: Write unit tests for each component to ensure the correctness and stability of its independent functions.

Integration testing: Conduct integration testing to ensure compatibility and performance of different components when working together.

4.Packaging and publishing

Packaging component libraries: Use tools (such as Webpack or Rollup) to package component libraries, making them easy to introduce and use in different projects.

Multi-tenant data management and isolation mechanism

1. User identification and login, user login: system user login account.

User Identification: Each user is given a unique identifier to identify and isolate their data within the system.

2. Data storage strategy, physical isolation: Create an independent database instance or schema (Schema) in the database for each tenant to achieve physical data isolation.

Logical isolation: Mark the ownership of each piece of data through the tenant ID in the shared database to achieve logical isolation.

3. Data access control, access control policy: Implement role-based access control (RBAC) to ensure that tenants can only access their own data.

Context-aware queries: All database queries are filtered by tenant context, ensuring data isolation.

4. Multi-tenant resource management and resource allocation: The system allocates necessary resources (such as storage space, computing power) to each user, and dynamically adjusts them according to needs.

Performance isolation: Ensure that the load of one tenant does not affect the performance of other tenants.

5. Security and compliance, data encryption: Encrypt stored data to enhance data security.

Compliance: Ensure data processing complies with relevant data protection and privacy regulations.

In an optional embodiment of the present invention, the above step 14 may include:

Step 141, obtain the template area of the business process;

Step 142, place the at least one component element in the template area;

Step 143: Perform at least one operation on the at least one component element to generate a business process.

In this embodiment, the template area is an area that can generate the business process after the system is started, and the template area can be an intuitive user interface. Specifically, the template area may be a blank canvas or a basic panel for the user to edit. The interface includes a menu bar, a toolbar, a process design area and an attribute editing area. Obtaining the template area of the business process includes loading the nodes that constitute the business process, a component library that contains multiple component elements and can be customized, the database and technology stack corresponding to each component element, and the relationships between the component elements. of connecting lines. Wherein, the component elements and the connection lines between the component elements are visualized, and the component elements can be placed into the template area by dragging and dropping.

Place the at least one component element in the template area, and then connect multiple of the component elements through visual connection lines according to actual needs, thereby achieving at least one operation on the at least one component element, Generate business processes. Specifically, visual connection lines represent data flow or control flow. Since the attributes of the component elements are different, the attributes of the component elements can be configured in the attribute editing area in the template area. For example: setting parameters, defining behaviors, etc. At the same time, the relevant parameters of the component elements and the expected results of the business process can be displayed in real time in the template area, which helps the operator make decisions.

By visualizing component elements, connection lines and business process nodes, complex business process design is simplified into intuitive graphical operations. Different business processes can be designed, and a friendly user interface is provided so that users can easily create and modify and optimize business processes. Users can design business processes that meet their own needs by dragging component elements and setting properties. Compared with the traditional way of relying on coding or fixed templates, it can respond to actual operational changes faster, provides operators with higher autonomy and flexibility, improves the operability and ease of use of the system, and makes Users can respond to business changes more quickly.

Performing at least one operation on the at least one component element also includes setting a set of componentized, reusable and configurable components for the business process from the component library, just like purchasing from a "parts supermarket" Furniture”, which can significantly reduce the cost of interface development and maintenance.

As shown in Figure 4: The following is a business process:

Step 1: The system starts and initializes, and loads the metadata-driven dynamic attribute management system. This step is what makes the system "out of the box". The system allows configuration at runtime and dynamic adjustment according to the special needs of different plants and stations. This design method reduces code-level changes and improves the flexibility and maintainability of the system. At the same time, through metadata-driven dynamic attribute management, the system can better adapt to changing business needs.

For example, when the system starts, it reads configuration information from metadata, such as database connection, service port, security policy, etc. Based on this configuration information, the system can flexibly adjust its behavior to meet the needs of different factories and stations.

Step 2: Users use the graphical water business process design tool to perform visual configuration and design different process flows. The tool provides a user-friendly interface that allows users to easily create, modify and optimize process flows. You can design a process flow that meets your own needs by dragging process nodes and setting node attributes. At the same time, the tool automatically generates monitoring points and control logic, and updates the process flow database. This design method improves the operability and ease of use of the system, allowing users to respond to business changes more quickly.

This step provides the basis for subsequent process execution and monitoring.

Step 3: Utilize microservices and containerized business deployment, and each module runs independently as a microservice. For example, the system can run different modules such as user rights management, work order management, and process monitoring as independent microservices. This step is like placing each module (such as user rights management, work order management, process monitoring, etc.) in a different "small box" to run independently without interfering with each other. This design method improves the maintainability and scalability of the system, allowing users to independently upgrade and maintain a module without affecting the normal operation of other modules. At the same time, rapid deployment and expansion are achieved through container technologies such as Docker to adapt to distributed and heterogeneous environments. This design method can reduce system deployment time and cost and improve system flexibility and scalability.

Step 4: Based on user needs, the highly customized front-end UI component library provides a set of componentized, highly reusable and configurable UI components. For example, users can choose components from different UI component libraries according to their own preferences and business needs, such as tables, forms, charts, etc. These components are highly reusable and configurable, just like purchasing "furniture" from a "parts supermarket", which can greatly reduce the cost of interface development and maintenance.

Step 5: Multi-tenant data management and isolation mechanism ensures the isolation and security of data from different factories. This design approach can improve the data security, integrity, and maintainability of the system. For example, the system can isolate and manage data from different factories through multi-tenant mode. This step is like establishing an independent "room" for each factory station. The data in each room can only be managed and used by the corresponding factory station, ensuring data security and isolation.

For water pump stations, appropriate component elements can be selected from the component library according to user needs to build the reusable and configurable components. The reusable and configurable components include tables, forms, charts and other components. Specifically, users can choose map positioning components, inspection track components, file library components, etc. At the same time, the reusable and configurable components can also support functions such as cross-factory data analysis and report generation to better meet the needs of customers. User’s business needs.

By providing a set of customizable and reusable component libraries to support various user interface requirements, it can support the rapid development of the system and improve the speed of responding to user feedback, providing personalized user experiences for different user groups.

Specifically, in the water management system, the component elements may include: work order management, water pump room management, water tank cleaning business, process monitoring, inspection business, document library, equipment management, operation analysis, etc. The components constituting the component elements may include: preset built models and preset built scenes. Among them, the preset built models include: drainage pit valve, submersible pump, pressure relief valve, flow meter, pressure meter, pump, online residual chlorine meter, online turbidity meter, UV disinfection meter, float level switch, Hydrostatic liquid level meter, water tank inlet flow meter, total inlet flow meter, valves, pipe network pressure gauge, axial flow fan, dehumidifier, ball machine, spotlight, waterproof fluorescent lamp, access control, sterilizer control cabinet, sewage control boxes, lighting distribution boxes, sub-control cabinets, main control cabinets, etc. The preset construction scenarios may include: single-unit pump room, double-unit pump room, three-unit pump room, four-unit pump room, etc.

By visualizing component elements, connection lines and business process nodes, complex business process design is simplified into intuitive graphical operations. Different business processes can be designed, and a friendly user interface is provided so that users can easily create and modify and optimize business processes. Just like putting together Lego blocks, users can design business processes that meet their own needs by dragging component elements and setting properties. Compared with the traditional way of relying on coding or fixed templates, it can respond to actual operational changes faster, provides operators with higher autonomy and flexibility, improves the operability and ease of use of the system, and makes Users can respond to business changes more quickly. Compared with traditional methods that rely on coding or fixed templates, this method is easier to use, can respond faster to actual operational changes, and provides factory operators with unprecedented autonomy and flexibility.

In an optional embodiment of the present invention, the method for generating the business process further includes: isolating and/or encrypting and storing process data of the business process belonging to different users.

In this embodiment, isolating process data of the business processes belonging to different users includes user identification, data storage policy, data access control and multi-tenant resource management.

The user identification assigns a unique identifier to each user, which serves to identify and isolate each user's account data in the system.

The data storage strategy includes physical isolation and logical isolation. Among them, physical isolation is to create an independent database instance or schema in the database for each user. Logical isolation is to mark the ownership of each piece of data through the user address in the shared database.

The data access control implements role-based access control to ensure that users can only access their own data, and the database queries need to be filtered to ensure data isolation.

The multi-user resource management includes allocating necessary resources (such as storage space, computing power) to each user, dynamically adjusting according to needs and ensuring that the load of one user does not affect the performance of other users.

Encrypted storage of process data belonging to said business processes of different users includes encrypting user data and ensuring that data processing complies with data protection and privacy regulations.

As shown in Figure 5, by isolating and/or encrypting the storage of process data of the business processes belonging to different users, the data security, integrity and maintainability of the system can be improved. For example, the system can isolate and manage data from different users. This step is like establishing an independent "room" for each user. The data in each room can only be managed and used by the corresponding user, ensuring data security and isolation. For example, in a water management system, it supports data analysis and report generation across plants and stations while maintaining data security and isolation. This is especially important for large water companies or government agencies to manage multiple water facilities. Since the data of different water pump stations may have isolation and security requirements, we isolate and/or encrypt the process data of the business processes belonging to different users to ensure that the data of users of different water pump stations are isolated from each other. and management. Each water pump station user has its own data storage and management space, and can only access and manage its own data but cannot access the data of other stations. This can effectively protect the privacy and security of data while also independently analyzing and managing the data of users at different factories and stations to better meet the business needs of users at different factories and stations.

As shown in Figure 6, an embodiment of the present invention also provides a business process generation device 60, which includes:

The acquisition module 61 is used to acquire the water management system attribute information in the form of metadata;

The processing module 62 is configured to configure the component elements required for the water affairs business process according to the water affairs management system attribute information in the form of metadata; call at least one component element through microservice events; and configure the at least one component element in the water affairs business Perform at least one operation in the template area of the process to generate a water business process.

Optionally, obtain water management system attribute information in the form of metadata, including:

Obtain water management system attribute information in the form of metadata from a preset data source.

Optionally, according to the water management system attribute information in the metadata form, component elements required for the water business process are configured, including:

Analyze the water management system attribute information in the form of metadata to obtain configuration information;

Configure attributes of component elements required by the water business process according to the configuration information.

Optionally, call at least one component element through microservice events, including:

Obtain each node of the water business process and the logical relationship between each node;

According to each node of the water business process and the logical relationship between the nodes, at least one component element is called through the microservice event.

Optionally, according to each node of the water business process and the logical relationship between the nodes, at least one component element is called through microservice events, including:

According to each node of the water business process, call the microservice event corresponding to each node;

According to the logical relationship between the nodes, at least one component element is called through the microservice event corresponding to each node, where one microservice event corresponds to one component element.

Optionally, perform at least one operation on the at least one component element in the template area of the water affairs business process to generate a water affairs business process, including:

Get the template area of the water business process;

placing the at least one component element in the template area;

Perform at least one operation on the at least one component element to generate a water business process.

Optionally, the processing module 62 is also configured to isolate and/or encrypt and store process data of the business processes belonging to different users.

It should be noted that this device is a device corresponding to the above method, and all implementation methods in the above method embodiments are applicable to the embodiments of the device, and the same technical effects can be achieved.

When the device is implemented, it is a comprehensive modular system for smart water management and a metadata-driven dynamic attribute management system: it allows runtime configuration to adapt to the special needs of different plants and stations, eliminating the need for code-level changes. Graphical water business process design tool: Provides visual configuration to facilitate users to design different process flows, and automatically generates monitoring points and control logic.

Microservices and containerized business deployment: Each module runs independently as a microservice, using container technologies such as Docker to achieve rapid deployment and expansion, adapting to distributed and heterogeneous environments.

Highly customized front-end UI component library: Provides a set of componentized, highly reusable and configurable UI component library to quickly build an interface that meets user needs.

Multi-tenant data management and isolation mechanism: Ensure the isolation and security of data from different factories and sites, while supporting cross-factory data analysis and report generation.

Standardization and reusability of core business modules: Core modules such as user rights management, work order management, and process monitoring are designed as standardized modules that can be reused between different factory sites.

Using metadata definition and dynamic attribute management, the system can adapt to different business needs and improve flexibility.

Graphical design tools transform process flow design into intuitive graphical operations, where users can design and adjust process flows by dragging, dropping and configuring elements.

The plug-in design of the security system allows security modules to be quickly integrated or replaced according to specific security requirements, improving the adaptability and security of the system.

The microservice architecture enables each functional module to run and update independently, while containerization technology simplifies the deployment and expansion of modules.

The rich elements in the UI component library enable users to quickly build and modify interfaces according to personalized needs.

The multi-tenant architecture allows complex data analysis and report generation while ensuring data security, and is suitable for managing multiple water facilities.

Metadata-driven dynamic attribute management system: Most existing water management systems are relatively fixed in data models, making it difficult to adapt to rapidly changing business needs. The metadata-driven dynamic attribute management system not only provides higher flexibility, but also customizes data structures and business logic through a simple interface. This is a breakthrough in management software for the water industry, significantly reducing reliance on technical experts and accelerating business adaptation and innovation.

Graphical process design tool: This tool simplifies complex process design into intuitive graphical operations, which is easier to use in water management systems, can respond to actual operation changes faster, and provides plant operators with Better autonomy and flexibility.

Microservices and containerized business deployment: In the water management system, it has significantly improved the reliability, maintainability and scalability of the system, and is especially suitable for decentralized water infrastructure management.

Highly customized front-end UI component library: Provides a set of highly customized and reusable UI component libraries to support various user interface needs. It supports rapid development and response to user feedback, providing personalized user experience for different user groups.

Multi-tenant data management and isolation mechanism: While maintaining data security and isolation, it supports cross-factory data analysis and report generation.

Standardization and reusability of core business modules: The standardization and reusability of modules such as user rights management, work order management, and process monitoring improve the versatility and scalability of the system, and reduce the cost of new function deployment and maintenance.

An embodiment of the present invention also provides a computing device, including: a processor and a memory storing a computer program. When the computer program is run by the processor, the method described in the above embodiment is executed. All implementations in the above method embodiment are applicable to this embodiment and can achieve the same technical effect.

Embodiments of the present invention also provide a computer-readable storage medium that stores instructions. When the instructions are run on a computer, they cause the computer to execute the method described in the above embodiments. All implementations in the above method embodiment are applicable to this embodiment and can achieve the same technical effect.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered to be beyond the scope of the present invention.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

In addition, it should be pointed out that in the device and method of the present invention, obviously, each component or each step can be decomposed and/or recombined. These decompositions and/or recombinations should be regarded as equivalent solutions of the present invention. Furthermore, the steps for executing the above series of processes can naturally be executed in chronological order in the order described, but they do not necessarily need to be executed in chronological order, and some steps may be executed in parallel or independently of each other. For those of ordinary skill in the art, it can be understood that all or any steps or components of the method and device of the present invention can be implemented in any computing device (including processor, storage medium, etc.) or a network of computing devices in the form of hardware or firmware. , software or their combination, this can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present invention.

Therefore, the objects of the invention can also be achieved by running a program or a set of programs on any computing device. The computing device may be a well-known general-purpose device. Therefore, the object of the present invention can also be achieved only by providing a program product containing a program code for implementing the method or apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium may be any known storage medium or any storage medium developed in the future. It should also be pointed out that in the device and method of the present invention, obviously, each component or each step can be decomposed and/or recombined. These decompositions and/or recombinations should be regarded as equivalent solutions of the present invention. Furthermore, the steps for executing the above series of processes can naturally be executed in chronological order in the order described, but do not necessarily need to be executed in chronological order. Certain steps can be performed in parallel or independently of each other.

The above is the preferred embodiment of the present invention. It should be pointed out that for those of ordinary skill in the art, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications can also be made. should be regarded as the protection scope of the present invention.

Claims (10)

1. A method for generating a business process, comprising:

acquiring attribute information of a water management system in a metadata form;

configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form;

invoking at least one component element through the microservice event;

and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.

2. The method for generating a business process according to claim 1, wherein acquiring the water management system attribute information in the form of metadata comprises:

and acquiring attribute information of the water management system in the form of metadata from a preset data source.

3. The method for generating a business process according to claim 1, wherein configuring the component elements required for the business process according to the metadata-form water management system attribute information comprises:

analyzing the attribute information of the water management system in the metadata form to obtain configuration information;

and carrying out attribute configuration on the component elements required by the water service flow according to the configuration information.

4. The method of claim 1, wherein invoking at least one component element via a microservice event comprises:

obtaining logic relations among all nodes of the water service flow;

and calling at least one component element through a micro-service event according to each node of the water service flow and the logic relation among the nodes.

5. The method for generating a business process according to claim 4, wherein invoking at least one component element through a microservice event according to each node of the water business process and a logical relationship between each node comprises:

calling micro-service events corresponding to all nodes according to all nodes of the water service flow;

and calling at least one component element through the micro-service event corresponding to each node according to the logic relation among the nodes, wherein one micro-service event corresponds to one component element.

6. The method for generating a water service flow according to claim 1, wherein performing at least one operation on the at least one component element in a template area of the water service flow, generating the water service flow comprises:

Obtaining a template area of a water service flow;

placing the at least one component element in the template region;

and performing at least one operation on the at least one component element to generate a water service flow.

7. The method for generating a business process according to claim 1, further comprising:

and isolating and/or encrypting and storing the flow data of the water service flow belonging to different users.

8. A business process generation device, comprising:

the acquisition module is used for acquiring attribute information of the water management system in the form of metadata;

the processing module is used for configuring the component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.

9. A computing device, comprising: a processor, a memory storing a computer program which, when executed by the processor, performs the method of any one of claims 1 to 7.

10. A computer readable storage medium, characterized in that instructions are stored which, when run on a computer, cause the computer to perform the method of any of claims 1 to 7.