Configurable design event management system, method and equipment and storage medium

Abstract

The invention provides a configurable design event management system, method and device and a storage medium, and relates to the technical field of event management, the system comprises a front-end interaction module used for providing a user interaction interface and allowing a user to newly add, edit and view an event and configuration thereof; the event definition module is used for defining basic information and configuration parameters of an event; the rear-end RESTful API module is used for processing a request of a front-end page and realizing the operations of newly adding, editing and checking events; and the configuration management module is used for managing configuration parameters of the event and generating a corresponding dynamic SQL script according to the configuration parameters. Through the system, when the system function needs to be modified or expanded, only modification needs to be carried out on the corresponding module, and the whole system does not need to be reconstructed. Therefore, the event access period is greatly shortened, the development efficiency is remarkably improved, and the system can quickly respond to the change of service requirements.

Description

Technical Field

[0001] The present application relates to the technical field of event management, and in particular to a configurable event management system, method, device and storage medium. Background Art

[0002] Under the traditional event management model, the process of accessing new events is cumbersome and inefficient, which constitutes a significant operational bottleneck.

[0003] Whenever the business department raises the need to add or modify an event, developers need to engage in heavy coding work and manually write intricate codes and database scripts. For example, when the business department needs to add a new event, the development team needs to perform the following steps: 1. Discuss the specific requirements and parameters of the event with the business personnel. 2. Write the corresponding Java code according to the requirements to handle the event logic. 3. Create or modify the database table and write SQL scripts to insert or update data. 4. Deploy and test the new event and fix potential problems. This process not only consumes a lot of time and resources, but also often makes it difficult to ensure efficient and error-free completion due to human factors. Summary of the invention

[0004] In view of the above problems, the present application provides a configurable event management system, method, device and storage medium, including the following contents:

[0005] In a first aspect, the present application provides a configurable event management system, the system comprising:

[0006] The front-end interactive module is used to provide a user interactive interface, allowing users to add, edit and view events and their configurations;

[0007] Event definition module, used to define basic information and configuration parameters of events;

[0008] The back-end RESTful API module is used to process requests from the front-end page and implement operations such as adding, editing, and viewing events;

[0009] The configuration management module is used to manage the configuration parameters of the event and generate corresponding dynamic SQL scripts according to the configuration parameters.

[0010] Optionally, the event definition module includes:

[0011] An event name input unit, used to receive an event name input by a user;

[0012] An event type selection unit, used for the user to select an event type;

[0013] The event parameter setting unit is used to set the configuration parameters of the event.

[0014] Optionally, the configuration management module includes:

[0015] Configuration parameter management unit, used to manage detailed configuration parameters of events, including field name, field description, display type, and value type;

[0016] The dynamic SQL generation unit is used to automatically generate and execute corresponding SQL scripts according to the configuration parameters input by the user.

[0017] Optionally, the front-end interaction module includes:

[0018] Add an event page, where users can add events and configure parameters;

[0019] The edit event page is used by users to edit existing events;

[0020] The event details page is used for users to view event details and configuration parameters.

[0021] Optionally, the system further comprises a database for storing event definition and configuration information;

[0022] The database includes multiple association tables, and the multiple association tables are associated with each other through foreign keys;

[0023] The multiple association tables include an event basic information table, an event basic configuration information table, an event definition storage table, an event configuration information table, and a time access permission table.

[0024] Optionally, the backend RESTful API module includes:

[0025] Added event interface to receive basic event information and configuration parameters from the front end, generate corresponding SQL scripts and insert them into the database;

[0026] Edit event interface, used to receive event modification information from the front end, generate corresponding SQL scripts and update the database;

[0027] The event query interface is used to query event information in the database and return it to the front-end page for display.

[0028] In a second aspect, the present application provides a configurable event management method, the method comprising:

[0029] Get basic information and configuration parameters of the event;

[0030] Receive basic information and configuration parameters of the event through a RESTful API interface, and generate a corresponding SQL script based on the basic information and configuration parameters;

[0031] The data in the SQL script is stored in the database.

[0032] Optionally, obtaining basic information and configuration parameters of an event includes: receiving an event name and event type input by a user, and obtaining event configuration parameters set by the user.

[0033] Optionally, receiving basic information and configuration parameters of the event through a RESTful API interface, and generating a corresponding SQL script based on the basic information and configuration parameters includes:

[0034] Automatically generate and execute the corresponding SQL script based on detailed configuration parameters, including field name, field description, display type, and value type.

[0035] Optionally, the basic information and configuration parameters of the event obtained include:

[0036] Get the basic information and configuration parameters of a newly added event, edit the basic information and parameters of an existing event, or get detailed information and configuration parameters of a newly added event.

[0037] Optionally, a database is used to store event definitions and configuration information;

[0038] The database includes multiple association tables, and the multiple association tables are associated with each other through foreign keys;

[0039] The multiple association tables include an event basic information table, an event basic configuration information table, an event definition storage table, an event configuration information table, and a time access permission table.

[0040] Optionally, the RESTful API interface includes:

[0041] Added event interface to receive basic event information and configuration parameters from the front end, generate corresponding SQL scripts and insert them into the database;

[0042] Edit event interface, used to receive event modification information from the front end, generate corresponding SQL scripts and update the database;

[0043] The event query interface is used to query event information in the database and return it to the front-end page for display.

[0044] In a third aspect, the present application provides a device comprising a memory and a processor, wherein the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the configurable event management method introduced in any implementation of the aforementioned second aspect.

[0045] In a fourth aspect, the present application provides a computer-readable storage medium storing a code. When the code is executed, the device executing the code implements the configurable event management method introduced in any implementation of the second aspect.

[0046] The present application provides a configurable event management system, which includes a front-end interaction module for providing a user interaction interface, allowing users to add, edit and view events and their configurations; an event definition module for defining the basic information and configuration parameters of events; a back-end RESTful API module for processing requests from front-end pages to implement event addition, editing and viewing operations; and a configuration management module for managing the configuration parameters of events and generating corresponding dynamic SQL scripts based on the configuration parameters. Through the design of the front-end interaction module and the event definition module, business personnel can directly add, edit and view events and their configurations through the user interface without relying on frequent intervention by developers. In addition, by centrally managing the configuration parameters of events and automatically generating dynamic SQL scripts, the repetitiveness and complexity of the code are reduced. At the same time, the design mode of separating the front-end and the back-end enables the front-end and the back-end to be independently developed and deployed, reducing the coupling degree of the system and thus reducing the maintenance cost. When it is necessary to modify or expand the system function, it is only necessary to modify the corresponding module without reconstructing the entire system. This not only greatly shortens the cycle of event access, but also significantly improves development efficiency, enabling the system to quickly respond to changes in business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0048] Figure 1 A schematic diagram of the structure of a configurable event management system provided in an embodiment of the present application;

[0049] Figure 2 A flowchart of a configurable event management method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] Figure 1 A schematic diagram of a configurable event management system provided in an embodiment of the present application. Figure 1 As shown, the configurable event management system 100 provided in the embodiment of the present application includes:

[0052] The front-end interaction module 110 is used to provide a user interaction interface, allowing users to add, edit and view events and their configurations.

[0053] The front-end interaction module 110 is a direct interface for users to interact with the system, providing an intuitive and easy-to-use interface to support users in adding, editing and viewing events. This module simplifies the complex code writing and SQL script writing work in the traditional event access process through rich interactive functions, so that non-technical personnel (such as business personnel) can also easily configure events. This interface includes a variety of pages, a new event page: allowing users to enter basic information of the event (such as event name, type, status, etc.) and configuration parameters (such as field name, field description, display type, value type, etc.); edit event page: provides editing functions for existing events, and users can modify the basic information and configuration parameters of the event; view event details page: displays detailed information and configuration parameters of the event to help users quickly understand the specific situation of the event; RESTful API call: the front-end page interacts with the database by calling the RESTful API provided by the back-end to complete the operation of adding, deleting, modifying and checking events.

[0054] The implementation process of the new event can include the following two methods:

[0055] 1. Message message input and parsing into event configuration parameters

[0056] In this way, the user enters a complete message message (for example, a string in JSON or XML format) through the front-end page. After the system backend receives the message, it will parse it and extract the event name, type, and configuration parameters of each field (such as the Chinese name of the field, English name, display type, value type, etc.). These parsed configuration parameters are then saved to the database for subsequent event processing. This method is highly flexible. Users can directly enter message messages in any format, and the system can flexibly parse and generate event configurations. It can also reduce the workload of the front-end. Most of the parsing work is done by the back-end, and the front-end only needs to provide an input interface.

[0057] 2. Dynamically add configuration parameters to the page

[0058] In this way, the front-end page provides the function of dynamically adding configuration parameters. Users can add, edit, and delete configuration parameter items on the page as needed. Each parameter item contains necessary fields (such as field name, field description, display type, value type, etc.), and the front-end will perform necessary input verification to ensure the correctness of the data. After the user completes the configuration, these parameters will be sent to the back-end and saved in the database. This method has a good user experience. Users can directly see and modify the configuration parameters on the front-end page, which is more intuitive and convenient. In addition, the front-end can strictly control the format and correctness of the input data, reducing the possibility of back-end processing errors. The back-end is mainly responsible for receiving and saving data, without the need for complex message parsing.

[0059] The event definition module 120 is used to define basic information and configuration parameters of an event.

[0060] The event definition module 120 is responsible for defining the basic information and configuration parameters of the event. These definitions are the core of the event configurable system and provide a basis for subsequent configuration management and dynamic SQL generation. The basic information definition of the event refers to the basic information of the stored event, such as the event name, type, status, etc., which are used to uniquely identify and classify events. The configuration parameter definition refers to the configuration parameters of the event, including field name, field description, display type, value type, etc. These parameters determine the specific format and processing method of the event data. Event storage is to store the defined events and their configuration parameters in the database for subsequent management and use.

[0061] The back-end RESTful API module 130 is used to process requests from the front-end page and implement operations of adding, editing and viewing events.

[0062] The back-end RESTful API module 130 provides a series of interfaces for processing requests from the front-end pages and implementing operations such as adding, editing, querying and deleting events. These interfaces realize loose coupling between the front-end and the back-end, so that the front-end page only needs to focus on the user interaction logic, while the back-end is responsible for specific data processing. The back-end RESTful API module includes a variety of interfaces, including a new event interface, which is used to receive basic event information and configuration parameters from the front-end, generate corresponding SQL scripts, and insert them into the database. The edit event interface is used to receive event modification information from the front-end, generate corresponding SQL scripts, and update the database. The query event interface is used to query event information in the database according to the front-end request, and return it to the front-end page for display. Different interfaces in the back-end RESTful API process front-end requests according to the specific type of front-end requests, call the configuration management module to generate dynamic SQL scripts, execute database operations, and return processing results.

[0063] The configuration management module 140 is used to manage the configuration parameters of the event and generate corresponding dynamic SQL scripts according to the configuration parameters.

[0064] The configuration management module 140 is one of the cores of the event configurable system. It is responsible for managing the configuration parameters of the event and generating the corresponding dynamic SQL scripts based on the configuration parameters. This module enhances the flexibility and maintainability of the system by centrally managing and dynamically loading configuration parameters. It can be used for configuration parameter management and provides a unified interface for the front end to call, which is used to add, modify and delete the configuration parameters of the event. According to the configuration parameters entered by the user through the front-end page, the corresponding SQL script is automatically generated and the insert or update operation is performed. For example, when a new event is added, the corresponding INSERT statement is generated to insert into the database; when the event configuration is modified, the corresponding UPDATE statement is generated to update the database. In addition, the configuration parameters can be verified to ensure the validity and legality of the input and prevent system anomalies caused by configuration errors; the access rights of the event are managed to ensure that only authorized users can configure and manage the event.

[0065] The above embodiment provides a configurable event management system, which realizes the automation and simplification of the event access process by integrating the front-end interaction module, event definition module, back-end RESTful API module and configuration management module, and significantly improves the development efficiency and system flexibility. The specific functions of each module in the system are introduced in detail below:

[0066] In an implementation method of an embodiment of the present application, the event definition module includes: an event name input unit for receiving an event name input by a user; an event type selection unit for the user to select an event type; and an event parameter setting unit for setting configuration parameters of the event.

[0067] The event definition module is responsible for defining the basic information and configuration parameters of the event and is one of the core components of the event management system. This module specifically includes the following units:

[0068] Event name input unit: used to provide an input box for users to enter the name of the event. The name entered by the user in the event name input unit must meet certain naming rules (such as uniqueness, non-empty, etc.), and be submitted to the backend for processing after being verified by the front end.

[0069] Event type selection unit: used to provide a drop-down list or radio button group to allow users to select one from the predefined event types. Event types can be predefined, such as "order creation", "user login", etc., or user-defined types can be supported.

[0070] Event parameter setting unit: used to provide a form or parameter setting interface, allowing users to set detailed configuration parameters of the event. Parameter settings can include field name, field description, display type (such as text box, drop-down selection, date selector, etc.), value type (such as string, number, Boolean value, etc.), etc. Users can flexibly configure the required parameters according to the event type.

[0071] In an implementation method of an embodiment of the present application, the configuration management module includes: a configuration parameter management unit, which is used to manage detailed configuration parameters of events, including field name, field description, display type, and value type; a dynamic SQL generation unit, which is used to automatically generate and execute corresponding SQL scripts based on the configuration parameters input by the user.

[0072] The configuration management module is responsible for managing the configuration parameters of events and generating corresponding dynamic SQL scripts based on these parameters. It includes the configuration parameter management unit: used to manage the detailed configuration parameters of events, including field name, field description, display type, value type, etc. The configuration parameter management unit supports users to add, edit, and delete configuration parameters, and provides parameter verification function to ensure the validity of parameters.

[0073] Dynamic SQL generation unit: Automatically generates and executes corresponding SQL scripts according to the configuration parameters entered by the user. Supports dynamic construction of SQL statements, such as INSERT, UPDATE, etc., to implement database operations. The generated SQL scripts must undergo strict verification and preprocessing to prevent security issues such as SQL injection.

[0074] In an implementation method of an embodiment of the present application, the front-end interaction module includes:

[0075] The Add Event page is used for users to add events and configure parameters; the Edit Event page is used for users to edit existing events; the View Event Details page is used for users to view event details and configure parameters.

[0076] The front-end interactive module provides a user interface that allows users to add, edit, and view events and their configurations. It includes the following pages:

[0077] Add event page: Provides a form interface for users to enter an event name, select an event type, and set configuration parameters to add an event. The interface is easy to use and supports real-time validation of user input.

[0078] Edit event page: used to display detailed information of existing events and provide editing functions, allowing users to modify event names, types or configuration parameters. It supports users to quickly locate events that need to be modified and provides an editing interface similar to that of newly added events.

[0079] View event details page: used to display detailed information and configuration parameters of the event, providing users with a clear interface and comprehensive information display, allowing users to quickly understand the details of the event.

[0080] In an implementation method of an embodiment of the present application, the system also includes a database for storing event definitions and configuration information; the database includes multiple related tables, and the multiple related tables are associated with each other through foreign keys; the multiple related tables include an event basic information table, an event basic configuration information table, an event definition storage table, an event configuration information table and a time access permission table.

[0081] The database is used to store event definitions and configuration information and is the data storage center of the event management system. The database includes multiple related tables, which are associated with each other through foreign keys to ensure data consistency and integrity. The main related tables include:

[0082] Event basic information table evt_base_event_define: stores basic information of events, such as event ID, event name, event type, etc.

[0083] Event basic configuration information table evt_base_config_define: stores common configuration parameters of events, such as creation time, modification time, etc.

[0084] Event definition storage table evt_event_define: stores detailed definition information of events, such as specific descriptions of events, associated business logic, etc.

[0085] Event configuration information table evt_event_config: stores event configuration parameters, such as field name, field description, value type, etc.

[0086] Time access permission table evt_base_event_rght: stores access permission information for events and controls the access permissions of different users to events.

[0087] In an implementation method of an embodiment of the present application, the backend RESTful API module includes:

[0088] Add an event interface to receive basic event information and configuration parameters from the front end, generate the corresponding SQL script and insert it into the database; edit event interface to receive event modification information from the front end, generate the corresponding SQL script and update the database; query event interface to query event information in the database and return it to the front end page for display. The back-end RESTful API module is responsible for processing requests from the front end page to implement event addition, editing and viewing operations. This module contains the following interfaces:

[0089] New event interface: Receive basic event information and configuration parameters from the front end, generate corresponding SQL scripts and insert them into the database. Support data transmission in JSON format to ensure data integrity and consistency.

[0090] Edit event interface: Receive event modification information from the front end, generate corresponding SQL scripts and update the database. Support locating events that need to be modified based on event ID or specific conditions.

[0091] Query event interface: query event information in the database and return it to the front-end page for display. Supports multiple query methods such as paging query and conditional query to meet different user needs.

[0092] The above is a specific structure of a configurable event management system provided in an embodiment of the present application. Based on this, the present application also provides a corresponding method.

[0093] Figure 2 A flowchart of a configurable event management method provided in an embodiment of the present application. Figure 2 As shown, the configurable event management method provided in the embodiment of the present application may include:

[0094] S201. Obtain basic information and configuration parameters of an event.

[0095] S202: Receive basic information and configuration parameters of the event through a RESTful API interface, and generate a corresponding SQL script based on the basic information and configuration parameters.

[0096] S203: Store the data in the SQL script into a database.

[0097] In an implementation method of an embodiment of the present application, obtaining basic information and configuration parameters of an event includes: receiving an event name and event type input by a user, and obtaining event configuration parameters set by the user.

[0098] In an implementation method of an embodiment of the present application, receiving basic information and configuration parameters of the event through a RESTful API interface, and generating a corresponding SQL script based on the basic information and configuration parameters includes:

[0099] Automatically generate and execute the corresponding SQL script based on detailed configuration parameters, including field name, field description, display type, and value type.

[0100] In an implementation method of an embodiment of the present application, the basic information and configuration parameters of the event are obtained including:

[0101] Get the basic information and configuration parameters of a newly added event, edit the basic information and parameters of an existing event, or get detailed information and configuration parameters of a newly added event.

[0102] In an implementation method of an embodiment of the present application, the database is used to store event definitions and configuration information;

[0103] The database includes multiple association tables, and the multiple association tables are associated with each other through foreign keys;

[0104] The multiple association tables include an event basic information table, an event basic configuration information table, an event definition storage table, an event configuration information table, and a time access permission table.

[0105] In an implementation method of an embodiment of the present application, the RESTful API interface includes:

[0106] Added event interface to receive basic event information and configuration parameters from the front end, generate corresponding SQL scripts and insert them into the database;

[0107] Edit event interface, used to receive event modification information from the front end, generate corresponding SQL scripts and update the database;

[0108] The event query interface is used to query event information in the database and return it to the front-end page for display.

[0109] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.

[0110] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the method described in any embodiment of the present application.

[0111] The computer storage medium stores codes, and when the codes are executed, a device executing the codes implements the method described in any embodiment of the present application.

[0112] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0113] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0114] It should also be noted that the various embodiments in this specification are described in a progressive manner, and the same and similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0115] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A configurable event management system, characterized in that: The system comprises: The front-end interactive module is used to provide a user interactive interface, allowing users to add, edit and view events and their configurations; Event definition module, used to define basic information and configuration parameters of events; The back-end RESTful API module is used to process requests from the front-end page and implement operations such as adding, editing, and viewing events; The configuration management module is used to manage the configuration parameters of the event and generate corresponding dynamic SQL scripts according to the configuration parameters.

2. The event management system according to claim 1, characterized in that: The event definition module includes: An event name input unit, used to receive an event name input by a user; An event type selection unit, used for the user to select an event type; The event parameter setting unit is used to set the configuration parameters of the event.

3. The event management system according to claim 1, characterized in that: The configuration management module includes: Configuration parameter management unit, used to manage detailed configuration parameters of events, including field name, field description, display type, and value type; The dynamic SQL generation unit is used to automatically generate and execute corresponding SQL scripts according to the configuration parameters input by the user.

4. The event management system according to claim 1, characterized in that: The front-end interaction module includes: Add an event page, where users can add events and configure parameters; The edit event page is used by users to edit existing events; The event details page is used for users to view event details and configuration parameters.

5. The event management system according to claim 1, characterized in that: The system also includes a database for storing event definition and configuration information; The database includes multiple association tables, and the multiple association tables are associated with each other through foreign keys; The multiple association tables include an event basic information table, an event basic configuration information table, an event definition storage table, an event configuration information table, and a time access permission table.

6. The event management system according to claim 1, characterized in that: The backend RESTful API module includes: Added event interface to receive basic event information and configuration parameters from the front end, generate corresponding SQL scripts and insert them into the database; Edit event interface, used to receive event modification information from the front end, generate corresponding SQL scripts and update the database; The event query interface is used to query event information in the database and return it to the front-end page for display.

7. A configurable event management method, characterized in that: An event management system applied to a configurable design, the method comprising: Get basic information and configuration parameters of the event; Receive basic information and configuration parameters of the event through a RESTful API interface, and generate a corresponding SQL script based on the basic information and configuration parameters; The data in the SQL script is stored in the database.

8. The method according to claim 7, characterized in that The basic information and configuration parameters of the acquisition event include: Receive the event name and event type entered by the user, and obtain the event configuration parameters set by the user.

9. A computing device, characterized in that The computing device includes: a memory and a processor; The memory is used to store computer programs; The processor is used to implement the method according to any one of claims 7 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 7 to 8 is implemented.

Images