Method and system for application rapid deployment based on visual data model

Abstract

Embodiments of the present disclosure disclose a method and system for application rapid deployment based on a visual data model. A specific embodiment of the method comprises: creating a target application data object group; generating a field association information group; constructing a target application data table for each target application data object in the target application data object group to obtain a target application data table set; generating a visual data model; and performing plug-in deployment on the visual data model to generate a target application function page. The embodiment improves the deployment efficiency of an application.

Description

Technical Field

[0001] The embodiments disclosed herein relate to the field of computer technology, and more particularly to the field of application development technology, specifically to a method and system for rapid application deployment based on a visual data model. Background Technology

[0002] When users' businesses undergo digital transformation, they need to develop the necessary software systems for their business scenarios. Common software development methods typically divide project development into front-end page development and back-end development. Then, the front-end pages and back-end are integrated and deployed to obtain the required software system or functions.

[0003] However, when deploying applications using the above methods, the following technical problems often arise: The lack of a real-time collaboration mechanism between backend and frontend development, such as developing and integrating frontend pages and backend pages separately and then deploying them, can easily lead to integration problems such as incompatible interfaces and misaligned functions. This requires the frontend and backend to be reworked and modified, which prolongs the application deployment cycle and reduces the efficiency of application deployment. Summary of the Invention

[0004] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0005] Some embodiments of this disclosure propose a method and system for rapid application deployment based on a visual data model to address the technical problems mentioned in the background section above.

[0006] In a first aspect, some embodiments of this disclosure provide a method for rapid application deployment based on a visual data model. The method includes: creating a target application data object group based on configuration parameters for the target application in an application deployment page, wherein the application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios, and the target application data objects represent data objects involved in the target application; generating a field association information group based on the target application data object group; constructing a target application data table for each target application data object in the target application data object group based on the field association information group, obtaining a target application data table set; generating a visual data model based on the target application data object group, the field association information group, and the target application data table set, wherein the visual data model has a jump relationship with the application deployment page; and deploying a plugin for the visual data model based on the target application data table set and the target application data object group to generate a target application function page.

[0007] Secondly, some embodiments of this disclosure provide a rapid application deployment system based on a visual data model, applied to the method described in the first aspect. The system includes: a user interaction layer, a visual data model configuration layer, a plugin extension layer, and a data recording layer. The system is characterized by: the user interaction layer being configured to: acquire configuration parameters for the target application, code files for the visual data model, and logical modification operations for the current functional flow page from the user's application deployment page; the visual data model configuration layer being configured to: generate a visual data model based on the configuration parameters for the target application; the plugin extension layer being configured to: deploy plugins to the visual data model based on the code files for the visual data model to obtain a deployed data model, and dynamically render the initial functional page corresponding to the target application based on the deployed data model to generate a functional page for the target application; and the data recording layer being configured to: save operation records for the target application to obtain an operation record sequence, and perform application anomaly analysis based on the operation record sequence to generate anomaly analysis results.

[0008] Thirdly, some embodiments of this disclosure provide an application rapid deployment apparatus based on a visual data model. The apparatus includes: a creation unit configured to create a target application data object group according to configuration parameters for a target application in an application deployment page, wherein the application deployment page is a page for configuring relevant configuration parameters of the application to be deployed for different application deployment scenarios, and the target application data object represents the data objects involved in the target application; a construction unit configured to construct a target application data table for each target application data object in the target application data object group according to the aforementioned field association information group, thereby obtaining a target application data table set; a second generation unit configured to generate a visual data model according to the target application data object group, the aforementioned field association information group, and the aforementioned target application data table set, wherein there is a jump relationship between the visual data model and the aforementioned application deployment page; and a plug-in deployment unit configured to perform plug-in deployment on the visual data model according to the aforementioned target application data table set and the aforementioned target application data object group to generate a target application function page.

[0009] Fourthly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect or the system described in the second aspect.

[0010] Fifthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any implementation of the first aspect or the system described in the second aspect.

[0011] The above embodiments of this disclosure have the following beneficial effects: the application rapid deployment method based on a visual data model according to some embodiments of this disclosure can improve the application deployment efficiency. In practice, during software development, the conventional approach usually executes front-end development and back-end development separately. Therefore, due to various factors, problems such as interface incompatibility and functional misalignment often arise between front-end and back-end development. Consequently, it is necessary to re-modify the collaboration between the front-end and back-end, thus occupying a certain development and deployment cycle and reducing application deployment efficiency. Specifically, the application rapid deployment method based on a visual data model according to some embodiments of this disclosure firstly creates a target application data object group based on the configuration parameters for the target application in the application deployment page. The application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios. The target application data object represents the data objects involved in the target application. Here, when deploying the application, the user can input configuration parameters on the application deployment page according to development needs. This quickly creates the required target application data object group, realizes the standardized extraction of field components, and effectively avoids the tedious and error-prone problem of defining fields one by one in the back-end. Then, based on the aforementioned target application data object group, a field association information group is generated. Next, based on the aforementioned field association information group, a target application data table is constructed for each target application data object in the target application data object group, resulting in a set of target application data tables. Here, generating field association information can be used to determine the relationships between field components within the target application data object (e.g., query relationships between fields, function field dependencies, business field constraints, etc.). This facilitates the creation of adapted target application data tables for each target application data object, achieving automated and rapid database construction for the target application. Afterwards, based on the aforementioned target application data object group, the aforementioned field association information group, and the aforementioned set of target application data tables, a visual data model is generated, wherein there is a jump relationship between the aforementioned visual data model and the aforementioned application deployment page. In practice, the definition of the data model and the front-end display page lack real-time linkage, leading to a disconnect between application front-end development and back-end development, which is detrimental to the rapid deployment and updates of the application. This application combines visualization to define the data model and configure fields, generating a visual data model. This facilitates the integration of backend database operations with frontend development pages, forming a dynamic closed loop of configuration and modeling. The visual data model can be flexibly modified and invoked, thus avoiding problems such as inconsistencies in frontend and backend development interfaces and functional misalignments, significantly improving application development and deployment efficiency. Finally, based on the aforementioned target application data table set and target application data object group, the visual data model is deployed as a plugin to generate the target application's functional pages.Therefore, this application, through a plugin deployment mechanism, can extend functionality based on a visual data model without modifying the underlying application deployment logic, generating target application function pages. This enables rapid and flexible deployment of functions from the front end, further improving the overall deployment efficiency of the application. Attached Figure Description

[0012] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0013] Figure 1 This is a schematic diagram of the hierarchical structure of a rapid application deployment system based on a visual data model, representing some embodiments of this disclosure. Figure 2 This is a flowchart of a method for rapid application deployment based on a visual data model, which is one of the embodiments of this disclosure; Figure 3 This is a page illustration of a visual data model; Figure 4 This is a diagram of the plugin deployment page; Figure 5 This is a schematic diagram of the current functional flow page; Figure 6 These are schematic diagrams illustrating the structure of some embodiments of the application rapid deployment apparatus based on a visual data model according to the present disclosure; Figure 7 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0014] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0015] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0016] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0017] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0018] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0019] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0020] Figure 1 A schematic diagram of the hierarchical structure of a rapid application deployment system based on a visual data model, according to some publicly disclosed embodiments, is shown.

[0021] like Figure 1 As shown, the application rapid deployment system based on a visual data model includes: a user interaction layer 101, a visual data model configuration layer 102, a plugin extension layer 103, and a data recording layer 104. Among them: The aforementioned user interaction layer 101 is configured to: obtain configuration parameters for the target application, code files for the visual data model, and logical modification operations for the current functional flow page from the user's application deployment page. The application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios. The target application is the application to be deployed through the application deployment page, containing application functions and functional pages. Configuration parameters are parameters related to the target application. For example, configuration parameters may include the following parameters: project name, project number, customer name, and functional parameters. The code file can be a program function that sets a specific parameter in the visual data model. The current functional flow page can be a page displaying the functional implementation process. The logical modification operations can be process modification operations for the functional implementation process.

[0022] Here, each parameter item in the configuration parameters corresponds to the following sub-items: setting sub-item, field sub-item, interface sub-item, display sub-item, etc. The setting sub-item is used to set the parameter type of the parameter item. For example, the status sub-item may include: keyword, field type, field length, default value, whether nullables are allowed, whether unique values ​​exist, etc. The field sub-item is used to set the status of the parameter item. For example, the field sub-item may include: whether it is a read-only field, whether it is a hidden field, field comments, whether it is a required field, etc. The interface sub-item is used to set the field interface of the parameter item. The interface sub-item may include: field icon, maximum field value limit, field font, field interface address, code editing options, etc. In practice, code editing options are controls used for visual plugin extensions. The display sub-item is used to set the display method of the parameter item. For example, the display sub-item may include: the size of the field component of the parameter item, whether the field component of the parameter item is on top, etc.

[0023] The aforementioned visualization data model configuration layer 102 is configured to generate a visualization data model based on configuration parameters for the target application. This visualization data model can be a data model used to integrate fields required for project or application functionality. For example, when the visualization data model lacks calculation capabilities, it can be used as a dynamic field setting model. When the visualization data model has calculation capabilities, it can execute corresponding program functions based on the included code files. The visualization data model can be applied to a single implementation process or application, or simultaneously to multiple implementation processes, application functions, or projects. Here, each parameter item in the configuration parameters can be populated into the corresponding page container component in metadata format. Each page container component corresponds one-to-one with a parameter item. Then, each page container component is added to a blank page to obtain the initialized data model.

[0024] The aforementioned plugin extension layer 103 is configured to: deploy the plugin to the visual data model based on the code file for the visual data model, obtaining a deployed data model; and dynamically render the initial functional page corresponding to the target application based on the deployed data model, thereby generating the target application's functional page. The deployed data model can be the visual data model with the plugin added. Secondly, the target application's functional page is a front-end user page used to display the target application's running results. The target application's functional page can be dynamically rendered based on the display settings of various parameter items in the deployed data model. Here, the code file can be added to the corresponding page container component in the visual data model based on the field names in the code file, resulting in the deployed data model. Each page container component in the visual data model can be read, and dynamic page rendering can be performed based on the content of the parameter items in each page container component to obtain the target application's functional page. When the visual data model is invoked, the code file in the visual data model can be read and executed, and the execution result can be synchronized to the corresponding display position on the target application's functional page.

[0025] The aforementioned data recording layer 104 is configured to: save operation records for the target application, obtain an operation record sequence, and perform application anomaly analysis based on the operation record sequence to generate anomaly analysis results. The operation records can be modification operations on the target application. Operation records may include: operation account, operation time period, operation status, operation title, and operation description information. The operation account represents the object to which the modification record was executed. The operation status indicates whether the operation is complete. The operation title can be the name of the operated field or function. The operation description information is text used to describe the operation content. The anomaly analysis results indicate whether the target application is running abnormally. For example, if a field value exceeds the maximum constraint value, the system determines that the target application is running abnormally. Therefore, when the anomaly analysis results indicate that an anomaly is detected in the target application, the system can output the error time point, error code, and anomaly information. Here, the anomaly information is the operation record corresponding to the application error time point and error code.

[0026] Specifically, the user interaction layer 101 can also be used to display the pages corresponding to the visualization data model configuration layer 102, the plugin extension layer 103, and the data recording layer 104. Furthermore, there are jump relationships between the visualization data model configuration layer 102, the plugin extension layer 103, and the data recording layer 104.

[0027] In practice, common software development methods often involve developing independent software systems for different business scenarios, requiring redeployment and thus incurring long development cycles without increasing the number of developers, leading to reduced application deployment efficiency. Secondly, in different software system scenarios (e.g., water management systems, medical data management systems, project management systems, etc.), the application deployment system based on the visual data model described in this application can be used for rapid system construction. Furthermore, when different software systems share the same business logic (e.g., CRUD operations, list display pages, detail items, access control, etc.), the visual data model corresponding to the same business logic, or a portion of the functional data within the visual data model, can be reused. This significantly improves the system's cross-industry reusability and application deployment efficiency. Additionally, the data recording layer enables field-level anomaly tracing for system exceptions, allowing for precise identification of anomalies and improving system robustness.

[0028] See next Figure 2 , Figure 2 A flow 200 is shown illustrating some embodiments of a rapid application deployment method based on a visual data model according to this disclosure. This rapid application deployment method based on a visual data model includes the following steps: Step 201: Create a target application data object group based on the configuration parameters for the target application in the application deployment page.

[0029] In some embodiments, the execution entity of the application rapid deployment method based on a visual data model (e.g., an application rapid deployment system based on a visual data model) can create a target application data object group based on the configuration parameters for the target application in the application deployment page. The application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios. Specifically, the application deployment page can define and manage field components related to configuration parameters, such as adding, updating, and deleting fields. Field components are visual components related to the target application selected by developers based on the characteristics of the field configuration parameters. Therefore, field components corresponding to the target application can be defined in the application deployment page for parameter configuration. Here, field components may include input controls, form controls, radio buttons, or checkboxes. The target application is the application to be deployed through the application deployment page, containing application functions and function pages. Target application data objects represent the data objects involved in the target application. Specifically, target application data objects are application configuration parameters encapsulated in structured data corresponding to the target application. A target application data object group consists of multiple data objects involved in the target application. Target application data objects are defined by field configuration parameters. Field configuration parameters represent the configuration parameters involved in the target application. Field configuration parameters can include: field name, field type, and field attribute constraints. Field attribute constraints are restrictions used to constrain field values. For example, a field attribute constraint of "int" (integer) is used to constrain field values ​​to be integers.

[0030] As an example, taking a water project management deployment scenario, the target application is the water bill calculation application within the water project management system. The application deployment page can be used to configure parameters related to the water bill calculation application. These include, for example, user name, user ID, user's monthly water consumption, water price per unit, and the calculation relationship between the user's monthly water consumption and water price per unit. Then, following a structured data encapsulation approach, the configuration parameters (i.e., user name, user ID, user's monthly water consumption, water price per unit, and the calculation relationship between the user's monthly water consumption and water price per unit) are encapsulated into a target application data object.

[0031] As another example, taking a human resources project management deployment scenario, the target application is a personnel attendance tracking application for human resources project management. The application deployment page can be used to configure configuration parameters related to the personnel attendance tracking application. For example, personnel name, personnel number, personnel attendance time, start time, and end time. Then, following the structured data encapsulation method, the above configuration parameters can be encapsulated into target application data objects.

[0032] Step 202: Generate a field association information group based on the target application data object group.

[0033] In some embodiments, the execution entity can generate a field association information group based on the target application data object group. The field association information represents the field association relationships among different target application data objects. Here, field association information corresponding to the target field can be established based on the association relationships selected for the target field in the configuration parameters. Specifically, the field association information is a triple, including the source field, the associated field, and the field identifier representing the association relationship.

[0034] In practice, when users input configuration parameters, corresponding associated fields can be added to fields that require setting association relationships. Here, associated fields can correspond to checkboxes, thus determining the association relationship between the target field and at least one other field. These association relationships can be categorized as one-to-many, many-to-one, and many-to-many. A one-to-many relationship indicates that the target field corresponds to multiple fields. A many-to-one relationship indicates that multiple fields containing the target field correspond to one other field. A many-to-many relationship indicates that multiple fields containing the target field correspond to multiple other fields. Therefore, the field association information group can be obtained by storing the names of each field corresponding to each associated field in the target application data object group according to the association relationship, in JSON format.

[0035] As an example, taking a human resources project management deployment scenario, target application data object 1 contains: personnel a, ID a1, clock-in time of 9:00 AM, and clock-out time of 5:00 PM. Target application data object 2 contains the lateness function calculation logic, including logical calculation fields. The field values ​​of the logical calculation fields are used to calculate whether someone is late. For example, if the clock-in time is later than 9:00 AM, then it is determined to be late. Therefore, there is a logical relationship between the clock-in time in target application data object 1 and the logical calculation fields in target application data object 2.

[0036] In some optional implementations of certain embodiments, the execution entity generates a field association information group based on the target application data object group, including: For each of the target application data objects in the aforementioned target application data object group, perform the following first processing step: Step S1: In response to determining that the target application data object contains a field identifier representing a related field, the field identifier representing the related field is determined as a field association identifier. The field association identifier represents the correspondence between the target application data object and the created data application model set. Here, the field association identifier can be pre-selected in configuration parameters. Each field association identifier can correspond to a single data application model or multiple data application models in the created data application model set. Secondly, the field identifier of the associated field represents the field attribute constraint. Additionally, one field from the target application data object corresponding to the field association identifier is extracted. The target application data object can correspond to one data application model or multiple data application models in the data application model set.

[0037] Step S2: Based on the aforementioned field association identifiers and the created data application model set, application data objects matching the target application data object are identified as candidate data objects, resulting in a candidate data object set. Specifically, data application models corresponding to the field association identifiers can be selected from the created data application model set as candidate data models. Then, application data objects corresponding to the field association identifiers are selected from the candidate data models as candidate data objects. Candidate data objects are application data objects that are associated with the target application data object. Here, the candidate data object set corresponds one-to-one with the data application model.

[0038] As an example, the field association identifier can be: [a1-B-b1]. Here, "a1" represents the application data object containing the field association identifier, i.e., the target application data object. "B" represents the model identifier of the data application model corresponding to the field association identifier. "b1" represents the data object in the candidate data model that has a relationship with the field association identifier. Therefore, application data objects matching the target application data object can be selected as candidate data objects using the field association identifier.

[0039] Step S3: Based on the target application data object and the candidate data object set, perform field association to generate a candidate associated field group. The candidate associated fields are fields that are related to fields in the target application data object. First, filter each field in each candidate data object in the candidate data object set to obtain a filtered field group set. Non-associated fields such as dates and field types in the candidate data objects can be removed. Second, the fields in the target application data object marked as associated fields are used as the target application fields.

[0040] Next, the data type matching degree, field constraint matching degree, and semantic similarity between the target application field and each filtered field are determined. Specifically, if the data types of the target application field and the filtered fields are consistent, a preset data type matching degree threshold (e.g., 0.4) is used as the data type matching degree. Field constraint matching degree is generated based on the number of identical constraint fields (e.g., field length, field non-nullability, and field index) between the target application field and the filtered fields. For each identical constraint field, the field constraint matching degree increases by 0.1. Field indexes can include primary key indexes, unique indexes, and regular indexes. Finally, the Word2Vec word vector similarity between the target application field and the filtered fields is determined as the semantic similarity.

[0041] Next, the sum of the data type matching degree, field constraint matching degree, and semantic similarity of each filtered field is determined as the comprehensive matching degree. The filtered fields in the filtered field group are sorted in descending order of comprehensive matching degree to obtain a sorted field sequence. Finally, the sorted fields in the sorted field sequence with a comprehensive matching degree greater than a preset similarity threshold are determined as candidate relation fields. Each candidate relation field group contains at least one candidate relation field. If the comprehensive matching degree of all sorted fields in the sorted field sequence is less than the preset similarity threshold, the sorted field with the highest comprehensive matching degree is selected as the candidate relation field.

[0042] Step S4: Based on the aforementioned field association identifiers, perform association verification on the aforementioned candidate associated field groups to generate field verification information. First, determine the field relationship type corresponding to the aforementioned field association identifiers. Here, the field relationship type represents the association relationship between fields. For example, the field relationship type can be: one-to-one, one-to-many, many-to-one, or many-to-many. Specifically, a one-to-one type represents a target application field corresponding to a single sorted field; a one-to-many type represents a target application field corresponding to multiple sorted fields; a many-to-one type represents multiple fields containing the target application field corresponding to a single sorted field; and a many-to-many type represents multiple fields containing the target application field corresponding to multiple sorted fields. Then, if the field relationship type does not match the number of candidate associated fields in the candidate associated field group, generate field verification information indicating that the verification failed. If the field relationship type matches the number of candidate associated fields in the candidate associated field group, generate field verification information indicating that the verification passed.

[0043] As an example, if the above candidate association field group contains only one candidate association field, and the field relationship type is one-to-one or many-to-one, then the field relationship type matches the number of candidate association fields in the candidate association field group. If the above candidate association field group contains at least two candidate association fields, and the field relationship type is one-to-one or many-to-one, then the field relationship type does not match the number of candidate association fields in the candidate association field group. If the above candidate association field group contains at least two candidate association fields, and the field relationship type is one-to-many or many-to-many, then the field relationship type matches the number of candidate association fields in the candidate association field group.

[0044] Step S5: In response to the field validation information meeting the preset validation conditions, determine the field association information between each candidate association field in the above candidate association field group and the above target application data object. The preset validation conditions are that the field validation information indicates successful validation. Secondly, if the field relationship type is one-to-one or one-to-many, then the target application field, candidate association fields, and field relationship type are determined as the field association information.

[0045] If the field relationship type is many-to-one or many-to-many, determine whether the target application field already has corresponding field association information. If it does, add each candidate association field to that field association information. If it does not exist, determine the target application field, field relationship type, and candidate association field group as the field association information.

[0046] In addition, if the field verification information does not meet the preset verification conditions, the preset similarity threshold can be adjusted according to the specific situation of the association verification in step S4, so as to filter the sorted field sequence again and execute the association verification step in step S4 again.

[0047] Step 203: Based on the field association information group, construct a target application data table for each target application data object in the target application data object group to obtain a set of target application data tables.

[0048] In some embodiments, the execution entity may construct a target application data table for each target application data object in the target application data object group based on the aforementioned field association information group, thereby obtaining a set of target application data tables. The target application data table is a structured data table used to store the field values ​​of each field in the target application data object and includes the relationships between the fields.

[0049] Using a pre-defined data table creation script, a target application data table corresponding to the target application data object is created. Here, the data table creation script can read parameters such as field names, field types, and field attribute constraints contained in each field component of the target application data object. Furthermore, the data table creation script can also build field indexes between target application data tables based on field association information.

[0050] Specifically, the name of the target application data table can be extracted from the field names of the target application data object. The construction of the target application data table includes: field name mapping, field type mapping, field attribute constraint mapping, primary key constraint construction, field index construction, and foreign key constraint construction. Field name mapping uses underscore naming conventions to map field names to field names in the data table. For example, mapping "userid" to "user_id". Field type mapping maps field types to the database's native data types. Here, the database can be a structured database, such as MySQL. Field attribute constraints include: primary key constraints, NOT NULL constraints, unique constraints, auto-increment constraints, and default value constraints. Field index construction is used to construct the primary key of the target application data table (e.g., single primary key, composite primary key, or auto-increment primary key). Foreign key constraint construction is used to construct foreign key field indexes, unique constraint indexes, and composite indexes. Specifically, the data table creation script can generate SQL statements based on various parameters in the target application data object and perform syntax validation. If an exception is found during syntax validation, an exception message window will pop up on the application deployment page. Finally, if the syntax validation passes, the generated SQL statement can be executed to construct the target application data table and establish the field relationships between the target application data tables.

[0051] In practice, the application rapid deployment system based on the visual data model of this application does not require building a database by creating tables separately. Instead, it is automatically constructed through target application data objects and field association information groups. Therefore, when the system architecture is upgraded or system anomalies occur, targeted local adjustments can be made (e.g., adjusting only a specific visual data model or a specific code file within the visual data model) to simultaneously complete the iteration of the front-end and back-end, thereby reducing the system maintenance cost.

[0052] Step 204: Generate a visual data model based on the target application data object group, field association information group, and target application data table set.

[0053] In some embodiments, the execution entity can generate a visual data model based on the target application data object group, the field association information group, and the target application data table set. A redirection relationship exists between the visual data model and the application deployment page. This allows users to navigate from the application deployment page to the page containing the constructed visual data model, enabling operations such as uploading code files. The visual data model is a data model that includes data objects related to the target application, the relationships between these data objects, and the target application data tables corresponding to those data objects, and can be invoked by the target application. Specifically, other application functions can also invoke the visual data model when they need to access data objects or tables within it.

[0054] Here, you can add field association information to the corresponding field description information in the target application data object, and add the port number of the target application data table to the corresponding field component of the target application data object, resulting in a group of added data objects. Then, you can import each group of added data objects into the initial data model page to obtain a visual data model. Here, both the page containing the visual data model and the application deployment page are development-side pages.

[0055] In practice, the application deployment page includes a navigation control for the data model, which can be used to navigate to the page containing the visual data model. This page contains entry controls for each visual data model. The name of each entry control is the name of the visual data model. Clicking another entry control for a visual data model will navigate to the page containing the target application data object within that visual data model.

[0056] In some optional implementations of certain embodiments, the execution entity generates a visual data model based on the target application data object group, the field association information group, and the target application data table set, including: Step S1: On the initial data model page, add object entry components corresponding to each target application data object in the aforementioned target application data object group to obtain the current data model. The object entry components are used to navigate to the corresponding settings page, which includes a set of field components from the target application data object corresponding to the object entry component. The object name of the target application data object can be used as the name of the object entry component, and then each field component from the target application data object is bound to the object entry component. Finally, arrange the object entry components in order to obtain the current data model.

[0057] Step S2: Based on the aforementioned field association information group and the aforementioned target application data table set, add data access interfaces to each field component in the current data model to obtain a visual data model. The data access interfaces are used to access the target application data table corresponding to the field component. Here, field components corresponding to the field association information can be added to the object entry component to display the field association information and data access interfaces.

[0058] As an example, see Figure 3 The illustrated data model page includes object entry components for four target application data objects: Project Name, Project Number, Customer Name, and Functional Parameters. Each target application data object (in its corresponding pop-up window) can include a set of field components. Here, each field component includes: Field Name, Field Type, and Field Attribute Constraints. The three vertical dots on the right side of each object entry component are setting options that can be used to adjust the data in the target application data object. For example, adjusting the field component representing field relationships or the field component representing the data access interface will simultaneously adjust the metadata, field relationships, and data table call relationships corresponding to the entry component.

[0059] Step 205: Based on the target application data table set and the target application data object group, deploy the plugin to the visualization data model to generate the target application function page.

[0060] In some embodiments, the execution entity can deploy plugins to the visualization data model based on the target application data table set and the target application data object group to generate target application function pages. These target application function pages can be the user page of the target application. The target application function pages can be used to display the target application's running results in real time. Specifically, when plugins are added to the target application's functions, the corresponding plugin function controls can be displayed in real time on the target application function pages.

[0061] Plugin deployment establishes a connection between plugin functionality and a visual data model, enabling the plugin to function based on the data within the model. The plugin functionality can be a feature within the target application. Plugin deployment can be categorized as external or internal plugins. When the plugin is external: deployment can establish an access connection between the target application's data table and the plugin functionality, or between a data object of the target application and the plugin functionality, allowing the plugin to function based on the accessed data and generate the target application's functional page. When the plugin is internal: the plugin code can be written into the metadata of the corresponding target application data object in the visual data model, so that the plugin functionality is launched synchronously when the visual data model is started. Here, the system corresponding to the application deployment page has a code environment deployed suitable for launching the plugin functionality.

[0062] As an example, see Figure 4 Users can upload code files through the plugin deployment page. The plugin deployment page includes three options: Fields, Interface, and Display. Each option can include: Name, Keyword, Run Script, and Code. The Name and Keyword components are text input components. The Code component can be used for code text input and code file upload. The Run Script component is clickable to run the uploaded code.

[0063] In some optional implementations of certain embodiments, the execution entity deploys a plugin for the visualization data model based on the target application data table set and the target application data object group to generate target application function pages, including: Step S1 involves reading the received code file for the target application data object in the visualization data model to obtain a code text string. This can be done using the `readAsText` function from the FileReader API to read the code file as text. The default encoding is UTF-8.

[0064] Step S2 involves performing line-level validation on the code text string to obtain the validation results. First, the code text string is converted into an array of line objects with line numbers using a normalization conversion operator. Then, for each line object array corresponding to a line number, the whitespace character at the beginning of the line is extracted to determine if it is an indentation character, and the characters at the end of the line are extracted to check for duplicate characters, useless spaces, or invalid newline characters. Finally, if there is no indentation character at the beginning of the line, duplicate characters at the end of the line, or useless spaces or invalid newline characters, a line-level validation result indicating that the validation failed is generated.

[0065] Step S3 involves performing code block-level validation on the aforementioned code text string to obtain the block-level validation result. First, an AST (Abstract Syntax Tree Parser) is used to split the code text string into code blocks, resulting in a set of code blocks. Specifically, code blocks can be categorized into data object body blocks, entity attribute blocks, constructor blocks, method declaration blocks, etc. Second, a Tree-sitter parser is used to perform code structure checks on each code block. If no code block anomalies are detected, a block-level validation result indicating that the validation has passed is generated.

[0066] Step S4 involves performing a minimum unit validation on the code text string to obtain the minimum unit validation result. This can be achieved by using an AST parser to break the code text string down into lexical units, thus removing formatting interference. Then, each lexical unit is validated using a lexical analyzer identical to the one used in the code language. Finally, if no lexical unit anomalies are detected, a minimum unit validation result indicating successful validation is generated.

[0067] Step S5: In response to the above row-level verification result, the above block-level verification result, and the above minimum unit verification result all indicating that the verification has passed, the above code file is written to the field component corresponding to the target application data object to complete the field component plugin deployment. The target application data object has a field component for storing code, which is used to write the code file to complete the field component plugin deployment.

[0068] Step S6: In response to the field components included in each target application data object in the above-mentioned visual data model, the field component plugins are deployed, generating the deployed data model. The deployed data model is the visual data model after all functional plugins have been deployed.

[0069] Step S7: Based on the deployed data model described above, dynamically render the initial functional page corresponding to the target application to generate the target application functional page. This target application functional page displays the target application's runtime data. In practice, the deployed data model includes the field components and rendering parameters required to be displayed on the target application functional page. Therefore, the target application functional page can be generated using a page rendering engine.

[0070] Optionally, the target application's functional page may contain at least one application functional component. This application functional component is used to trigger the program functions of the target application. In the case of a water management system, the included application functional components may correspond to functions such as card replacement, card issuance, and card loss reporting.

[0071] The aforementioned implementing entities may also perform the following steps: Step S1: For each application function component in the target application function page mentioned above, perform the following second processing step: Step S11: Based on the above application functional components, construct an abstract component tree. The abstract component tree is an abstract expression of the functional structure of the application functional components.

[0072] First, read the JSON configuration files corresponding to the aforementioned application functional components. Then, iterate through the JSON configuration files, converting each event action (e.g., calling an API, reading data output results, etc.) into tree nodes of the abstract component tree. Next, based on the tree data structure in the JSON configuration files, determine the hierarchical relationship of each tree node, thereby establishing the initial abstract component tree. This initial abstract component tree can include action nodes for calling the visual data model and calling the database.

[0073] Next, the visual data models invoked by the aforementioned application functional components are treated as invoked data models, resulting in an invoked data model group. Then, each invoked data model in this group is read to extract its code function name as a logical event node. Here, the logical event node is the node that executes the visual data model. Simultaneously, read operations on the target application's data table can be extracted as data read nodes, and write operations on the target application's data table can be extracted as data storage nodes. Finally, the logical event node, data read node, and data storage node corresponding to each invoked data model are inserted into the action nodes of the initial abstract syntax tree, resulting in an abstract component tree. In practice, the abstract component tree represents the logical execution flow of the aforementioned application functional components.

[0074] Step S12 involves extracting logical features from the abstract component tree to generate a sequence of logical feature nodes. Each application functional component corresponds to at least one visual data model, and the sequence of logical feature nodes represents the logical processing order of the application functional components. Logical feature nodes include, but are not limited to, at least one of the following: node name, node description information, node type, node data model, node address, and node rules. Here, a logical feature node can be a tree node containing node information. Next, according to a preset node information list, node information corresponding to each tree node can be extracted from the abstract component tree and the visual data model called by the abstract component tree, and the tree nodes and node information can be used as logical feature nodes. In practice, the node information list can be a form containing at least one information attribute. The node information list can be set on the initial functional flow page. The initial functional flow page is a page that does not display the logical steps corresponding to the current application functional component.

[0075] Here, the node name is the name of the tree node in the abstract component tree. The node description information describes the functionality of the tree node. For example, if the tree node's function is to retrieve data, then the node description information would be "Retrieve Data". The node type represents the event type of the tree node. The node data model represents the name of the visual data model called by the node. The node address is the network address of the visual data model called by the node. The node rule represents the judgment statement that enables the data reading node or data storage node.

[0076] Step S13: Based on the aforementioned logical feature node sequence, construct a logical flow component sequence in the initial functional flow page to obtain the current functional flow page. The logical flow component sequence is used to display the logical steps of the aforementioned application functional components on the current functional flow page. The logical flow components have editing options for modifying logical functions, and there is a jump relationship between the current functional flow page and the aforementioned application deployment page. Here, a flow node component can be created for each logical feature node in the initial functional flow page. The name of the flow node component is the node description information of the logical feature node. The display content of the flow node component is the other node information of the logical feature node. Then, connect the various flow node components according to the flow steps to obtain the current functional flow page.

[0077] As an example, see Figure 5 As shown, the current functional flow page displays the flow of the application's functional components. Specifically, the flow includes the following logical feature nodes: trigger, read data, run script, and create data. Here, the trigger can be a component function set within the functional component. For example, clicking the component triggers the data using the POST protocol. The trigger can point to the data to be read through a set address. In practice, when a trigger is activated, the corresponding logical flow component can be marked as "active." Next, the read data logical flow node determines (visualizes) the target application data table corresponding to the data model based on the address. Then, the run script logical flow node executes the data model to perform the function. Finally, the create data logical flow node stores the results of the data model's execution through executed statements (e.g., data insertion statements). Thus, the current functional flow page visualizes the operational flow of the application's functional components.

[0078] Step S2: In response to detecting a logical modification operation on the logical flow component in the current functional flow page, modify the corresponding logical feature node according to the above logical modification operation to obtain the modified functional flow page.

[0079] The current functional flow page includes a modification control. When triggered, this control retrieves user input. The modified logical feature nodes in the abstract component tree are then synchronously updated based on this modification, resulting in the revised functional flow page. In practice, modifications to the abstract component tree can also simultaneously alter the execution logic of application functional components. Specifically, the current functional flow page allows for setting the functional flow of application components, adjusting the invoked visual data models and data table query statements, and thus enabling rapid and visual adjustments to the target application functionality.

[0080] Optionally, the above-mentioned implementing entity may further include the following steps: Step S1: Save the operation records for the target application to obtain an operation record sequence. The operation record includes: modified account, modified time period, modified status, modified title, and modified description. Here, modified account refers to the user account performing the modification operation. Modified status indicates whether the modification is complete. Modified title is the title of the modified target; for example, if the target is a visualization data model, the modified title is the name of the visualization data model. Modified description is information describing the modified content. The modification operation record is a log stored for the modification operations. Specifically, the operation records for the target application can be saved to the corresponding target application data table or to a unified log database. Here, building a corresponding target application data table for each target application data object can also be used to record operation records for the target application data objects, facilitating the tracing of system anomalies.

[0081] Step S2: In response to the detection of an abnormal operation record in the program corresponding to the modified functional flow page, the operation record matching the abnormal operation record is retrieved as the target operation record. Specifically, if an abnormal situation occurs during the operation of the program corresponding to the modified functional flow page, an abnormal operation record is output. For example, abnormal situations include: a field value exceeding a constraint, data retrieval errors, etc. Secondly, the operation record with the shortest time interval to the abnormal operation record can be retrieved as the target operation record. For example, if the abnormal operation record indicates a field error, the operation record that modifies the title or description information containing that field name and has the shortest time interval to the abnormal time point can be used as the target operation record.

[0082] Step S3: Based on the target operation record and abnormal operation record, generate an anomaly analysis result and send the anomaly analysis result to the target application function page. Specifically, if no anomaly corresponding to the abnormal operation record occurs within the target time period prior to the modification operation corresponding to the target operation record, then the target operation record and abnormal operation record are identified as anomaly analysis results. If an anomaly corresponding to the abnormal operation record occurs within the target time period prior to the modification operation corresponding to the target operation record, then a new target operation record is selected. If no target operation record related to the abnormal operation record is found within the target time period, then an anomaly analysis result representing an anomaly in the target application function is generated.

[0083] The above embodiments of this disclosure have the following beneficial effects: the application rapid deployment method based on a visual data model according to some embodiments of this disclosure can improve the application deployment efficiency. In practice, during software development, the conventional approach usually executes front-end development and back-end development separately. Therefore, due to various factors, problems such as interface incompatibility and functional misalignment often arise between front-end and back-end development. Consequently, it is necessary to re-modify the collaboration between the front-end and back-end, thus occupying a certain development and deployment cycle and reducing application deployment efficiency. Specifically, the application rapid deployment method based on a visual data model according to some embodiments of this disclosure firstly creates a target application data object group based on the configuration parameters for the target application in the application deployment page. The application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios. The target application data object represents the data objects involved in the target application. Here, when deploying the application, the user can input configuration parameters on the application deployment page according to development needs. This quickly creates the required target application data object group, realizes the standardized extraction of field components, and effectively avoids the tedious and error-prone problem of defining fields one by one in the back-end. Then, based on the aforementioned target application data object group, a field association information group is generated. Next, based on the aforementioned field association information group, a target application data table is constructed for each target application data object in the target application data object group, resulting in a set of target application data tables. Here, generating field association information can be used to determine the relationships between field components within the target application data object (e.g., query relationships between fields, function field dependencies, business field constraints, etc.). This facilitates the creation of adapted target application data tables for each target application data object, achieving automated and rapid database construction for the target application. Afterwards, based on the aforementioned target application data object group, the aforementioned field association information group, and the aforementioned set of target application data tables, a visual data model is generated, wherein there is a jump relationship between the aforementioned visual data model and the aforementioned application deployment page. In practice, the definition of the data model and the front-end display page lack real-time linkage, leading to a disconnect between application front-end development and back-end development, which is detrimental to the rapid deployment and updates of the application. This application combines visualization to define the data model and configure fields, generating a visual data model. This facilitates the integration of backend database operations with frontend development pages, forming a dynamic closed loop of configuration and modeling. The visual data model can be flexibly modified and invoked, thus avoiding problems such as inconsistencies in frontend and backend development interfaces and functional misalignments, significantly improving application development and deployment efficiency. Finally, based on the aforementioned target application data table set and target application data object group, the visual data model is deployed as a plugin to generate the target application's functional pages.Therefore, this application, through a plugin deployment mechanism, can extend functionality based on a visual data model without modifying the underlying application deployment logic, generating target application function pages. This enables rapid and flexible deployment of functions from the front end, further improving the overall deployment efficiency of the application.

[0084] Further reference Figure 6 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a rapid application deployment device based on a visual data model. These device embodiments are similar to... Figure 2 Corresponding to the method embodiments shown, this application rapid deployment device based on a visual data model can be specifically applied to various electronic devices.

[0085] like Figure 6 As shown, some embodiments of the application rapid deployment device 600 based on a visual data model include: a creation unit 601, a first generation unit 602, a construction unit 603, a second generation unit 604, and a plug-in deployment unit 605. The creation unit 601 is configured to create a target application data object group based on configuration parameters for the target application in the application deployment page. The application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios. The target application data objects represent the data objects involved in the target application. The first generation unit 602 is configured to generate a field association information group based on the target application data object group; the construction unit 603 is configured to construct a target application data table for each target application data object in the target application data object group based on the field association information group, thereby obtaining a target application data table set; the second generation unit 604 is configured to generate a visual data model based on the target application data object group, the field association information group, and the target application data table set, wherein there is a jump relationship between the visual data model and the application deployment page; the plug-in deployment unit 605 is configured to perform plug-in deployment on the visual data model based on the target application data table set and the target application data object group, thereby generating a target application function page.

[0086] It is understandable that the units and references described in the application rapid deployment device 600 based on the visualization data model are... Figure 2 The steps in the described method correspond accordingly. Therefore, the operations, features, and beneficial effects described above for the method also apply to the application rapid deployment device 600 based on the visualization data model and the units contained therein, and will not be repeated here.

[0087] The following is for reference. Figure 7The diagram illustrates the structure of an electronic device (e.g., a rapid application deployment system based on a visual data model) 700 suitable for implementing some embodiments of the present disclosure. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0088] like Figure 7 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory 702 or a program loaded from a storage device 708 into a random access memory 703. The random access memory 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, the read-only memory 702, and the random access memory 703 are interconnected via a bus 704. An input / output interface 705 is also connected to the bus 704.

[0089] Typically, the following devices can be connected to the input / output interface 705: input devices 706 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 707 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 708 including, for example, magnetic tape, hard disk, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 7 Each box shown can represent a device or multiple devices as needed.

[0090] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 709, or installed from a storage device 708, or installed from a read-only memory 702. When the computer program is executed by the processing device 701, it performs the functions defined in the methods of some embodiments of this disclosure.

[0091] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0092] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0093] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: create a target application data object group based on the configuration parameters for the target application in the application deployment page, wherein the application deployment page is a page used for configuring relevant configuration parameters of the application to be deployed in different application deployment scenarios, and the target application data objects represent the data objects involved in the target application; generate a field association information group based on the aforementioned target application data object group; construct a target application data table for each target application data object in the aforementioned target application data object group based on the aforementioned field association information group, obtaining a target application data table set; generate a visual data model based on the aforementioned target application data object group, the aforementioned field association information group, and the aforementioned target application data table set, wherein there is a jump relationship between the aforementioned visual data model and the aforementioned application deployment page; and deploy a plug-in to the aforementioned visual data model based on the aforementioned target application data table set and the aforementioned target application data object group to generate a target application function page.

[0094] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0095] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0096] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0097] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A method for rapid application deployment based on a visual data model, characterized in that, include: Based on the configuration parameters for the target application in the application deployment page, create a target application data object group. The application deployment page is a page used for different application deployment scenarios to configure the relevant configuration parameters of the application to be deployed. The target application data object represents the data objects involved in the target application. Based on the target application data object group, generate a field association information group; Based on the field association information group, construct a target application data table for each target application data object in the target application data object group to obtain a target application data table set. A visual data model is generated based on the target application data object group, the field association information group, and the target application data table set, wherein there is a jump relationship between the visual data model and the application deployment page; Based on the target application data table set and the target application data object group, the visualization data model is deployed as a plugin to generate the target application function page.

2. The rapid application deployment method based on a visual data model according to claim 1, characterized in that, The step of generating a visual data model based on the target application data object group, the field association information group, and the target application data table set includes: In the initial data model page, add an object entry component corresponding to each target application data object in the target application data object group to obtain the current data model. The object entry component is used to jump to the corresponding settings page, which includes a set of field components in the target application data object corresponding to the object entry component. Based on the field association information group and the target application data table set, data access interfaces are added to each field component corresponding to the current data model to obtain a visual data model. The data access interfaces are used to access the target application data table corresponding to the field component.

3. The rapid application deployment method based on a visual data model according to claim 1, characterized in that, The step of generating a field association information group based on the target application data object group includes: For each target application data object in the target application data object group, perform the following first processing step: In response to determining that the target application data object contains a field identifier representing an associated field, the field identifier representing the associated field is determined as a field association identifier, wherein the field association identifier represents the correspondence between the target application data object and the created data application model set; Based on the field association identifier and the created data application model set, the application data objects that match the target application data object are identified as candidate data objects, thus obtaining a set of candidate data object groups; Based on the target application data object and the candidate data object set, field associations are performed to generate candidate associated field groups; Based on the field association identifier, perform association verification on the candidate associated field group to generate field verification information, and obtain the field verification information. In response to the field validation information meeting the preset validation conditions, the field association information between each candidate association field in the candidate association field group and the target application data object is determined.

4. The rapid application deployment method based on a visual data model according to claim 1, characterized in that, The step of deploying a plugin for the visualization data model based on the target application data table set and the target application data object group to generate target application function pages includes: The received code file targeting the data object in the visual data model is read to obtain the code text string; Perform line-level validation on the code text string to obtain the line-level validation result; Perform code block-level validation on the code text string to obtain the block-level validation result; Perform minimum unit validation on the code text string to obtain the minimum unit validation result; In response to the row-level verification result, the block-level verification result, and the smallest unit verification result all indicating that the verification has passed, the code file is written to the field component corresponding to the target application data object to complete the field component plugin deployment; In response to the field components included in each target application data object in the visualized data model, the field component plugin is deployed, and the deployed data model is generated; Based on the deployed data model, the initial functional page corresponding to the target application is dynamically rendered to generate the target application functional page, which is used to display the running data of the target application.

5. The rapid application deployment method based on a visual data model according to claim 4, characterized in that, The target application feature page contains at least one application feature component, and the method further includes: For each application function component in the target application function page, perform the following second processing step: Based on the application functional components, construct an abstract component tree; Logical features are extracted from the abstract component tree to generate a sequence of logical feature nodes. Each application function component corresponds to at least one visual data model. The sequence of logical feature nodes represents the logical processing order of the application function components. Each logical feature node includes at least one of the following: node name, node description information, node type, node range, node data model, node address, node code identifier, and node rule. Based on the logical feature node sequence, a logical flow component sequence is constructed in the initial functional flow page to obtain the current functional flow page. The logical flow component sequence is used to display the logical steps of the application functional components on the current functional flow page. The logical flow components are set with editing options for modifying logical functions. There is a jump relationship between the current functional flow page and the application deployment page. In response to detecting a logical modification operation on a logical flow component in the current functional flow page, the corresponding logical feature node is modified according to the logical modification operation to obtain the modified functional flow page.

6. The rapid application deployment method based on a visual data model according to claim 5, characterized in that, The method further includes: Save the operation logs for the target application to obtain the operation log sequence. The operation logs include: modify account, modify time period, modify status, modify title and modify description information. In response to the detection of abnormal operation records of the program corresponding to the modified function flow page, the operation record that matches the abnormal operation record is retrieved as the target operation record; Based on the target operation record and abnormal operation record, generate anomaly analysis results and send the anomaly analysis results to the target application function page.

7. A rapid application deployment system based on a visual data model, applied to the rapid application deployment method based on a visual data model as described in any one of claims 1 to 6, wherein, The application rapid deployment system based on a visual data model includes: a user interaction layer, a visual data model configuration layer, a plugin extension layer, and a data recording layer, characterized in that it includes: The user interaction layer is configured to: obtain the user's configuration parameters for the target application, the code file for the visual data model, and the logical modification operations for the current functional flow page in the application deployment page; The visualization data model configuration layer is configured to generate a visualization data model based on configuration parameters for the target application. The plugin extension layer is configured to: deploy a plugin to the visual data model based on the code file for the visual data model to obtain the deployed data model; and dynamically render the initial functional page corresponding to the target application based on the deployed data model to generate the functional page of the target application. The data recording layer is configured to: save operation records for the target application to obtain an operation record sequence, and perform application anomaly analysis based on the operation record sequence to generate anomaly analysis results.

8. An electronic device, characterized in that, include: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 6 or the system as described in claim 7.

9. A computer-readable medium, characterized in that, It stores a computer program thereon, wherein the computer program, when executed by a processor, implements the method as described in any one of claims 1 to 6 or the system as described in claim 7.

Images