Application program construction method, device and equipment based on low-code platform

Abstract

The invention relates to an application program construction method, device and equipment based on a low-code platform. Comprising the following steps: receiving deployment information and attribute information of a developer on a functional module in a visual interface of a low-code platform; generating a function configuration file according to the deployment information and the corresponding server interface; generating a library table configuration file according to the attribute information; after a deployment issuing instruction of a developer for all deployed function modules in the visual interface is received, the function configuration file and the library table configuration file are issued to the application system, the application system generates a database table according to the library table configuration file, an application program ID is created, and the application program ID is sent to the developer; and recording the function configuration file and the library table configuration file in the application ID to complete the construction of the application. Through the embodiment of the specification, developers can complete the function realization without mastering professional knowledge, the technical threshold is reduced, and then the function can be realized only by reading and writing the configuration file without additionally changing codes.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of application service development, and in particular, to a method, device, and equipment for building an application based on a low-code platform. Background Art

[0002] As digital transformation gradually deepens, banks have put forward higher requirements for the delivery speed and development quality of IT systems. Therefore, on the basis of the maturity of cloud-native infrastructure and microservice architecture, exploring and promoting the integration of low-code technology and financial IT systems can help IT systems improve development quality, reduce development costs, and improve delivery efficiency, while also contributing to the sustainable development of financial business.

[0003] Currently, the common low-code platform design scheme is form-driven and code-generated. By providing visual design tools and model-driven logic, developers of different experience levels can create applications through a graphical user interface, using drag-and-drop components and model-driven logic.

[0004] However, the form-driven and code-generated low-code design platform design has the following disadvantages: (1) The cost of use for developers is high, requiring developers to have certain database knowledge and to master the use of database visualization tools; (2) The system redundancy, maintenance cost, and testing cost are high. The template-based code generation model will inevitably greatly increase the redundancy of the system, and the system maintenance cost and testing cost will also increase accordingly; (3) The system integration capability is insufficient. The interaction between applications in the enterprise is very frequent, and the interaction of system interfaces is often designed. These system interaction interfaces make it difficult for the form-driven model to run in a lightweight mode.

[0005] How to improve the development convenience of applications based on low-code platforms, lower the technical threshold for developers, and at the same time reduce the system redundancy of applications and improve operational efficiency is a technical problem that needs to be solved urgently. Summary of the invention

[0006] In order to solve the problems of low development convenience, high technical threshold requirements for developers, high system redundancy of applications, and low operating efficiency in the low-code design platform driven by forms and generated by code in the prior art, the embodiments of this specification provide an application construction method, device and equipment based on a low-code platform. Developers develop applications by dragging and combining functional modules and entering attribute content on a visual interface. The system generates a functional configuration file based on the functional modules dragged and combined by the developer, generates a library table configuration file based on the attribute information of the corresponding functional modules entered by the developer, and automatically associates the function modules with the calls of the server interface to realize the visual development of the application.

[0007] The specific technical solutions of the embodiments of this specification are as follows:

[0008] On the one hand, an embodiment of this specification provides a method for building an application based on a low-code platform, the method comprising:

[0009] Receive deployment information of at least one functional module from a developer in a visualization interface of a low-code platform and attribute information of the deployed functional module input by the developer in the visualization interface;

[0010] Generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module;

[0011] Generate a library table configuration file according to the attribute information of the functional module;

[0012] After receiving the deployment instructions issued by the developer for all deployed functional modules in the visual interface, the functional configuration file and the library table configuration file are sent to the application system so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the functional configuration file and the library table configuration file under the application ID to complete the construction of the application.

[0013] Further, the type of the functional module includes a data type;

[0014] Receiving the attribute information of the deployed functional module input by the developer in the visual interface further includes:

[0015] Receive attribute information of the functional module of the data type, wherein the attribute information at least includes a field name and a data type.

[0016] Furthermore, generating a library table configuration file according to the attribute information of the functional module further includes:

[0017] The field names and data types are written into the library table configuration file according to the corresponding relationship.

[0018] Furthermore, the application system generates a database table according to the library table configuration file, further comprising:

[0019] The application system parses the library table configuration file to obtain the field name and the corresponding data type, and uses the field name and data type as parameters to execute a database table construction script to generate the database table.

[0020] Furthermore, the deployment information includes a function module ID, location information, and a call relationship with a currently deployed function module; the function configuration file includes a front-end configuration layer and an interface call layer;

[0021] Generating a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module further includes:

[0022] Write the location information of each function module, the calling relationship between each function module, and the rendering style information of each function module into the front-end configuration layer of the function configuration file with the function module ID as the primary key;

[0023] The calling relationship between each functional module and the corresponding server interface is written into the interface calling layer of the functional configuration file with the functional module ID as the primary key.

[0024] Furthermore, after completing the construction of the application, the method further includes:

[0025] When the application system receives an instruction from the user to start the application, it notifies the front-end rendering component to render each functional module in the front-end configuration layer of the functional configuration file according to the rendering style information and location information, obtains the interface of the application, and displays the interface of the application to the user, so that the user can interact with the functional modules in the interface of the application and perform corresponding business processing.

[0026] Furthermore, the user interacts with the functional modules in the interface of the application program to perform corresponding business processing further including:

[0027] After the application system receives the user's operation instruction on the target function module in the interface, it takes the application interacted by the user as the target application, determines the function configuration file corresponding to the target application ID as the target function configuration file, determines the server interface corresponding to the target function module from the interface call layer of the target function configuration file, and calls the server interface corresponding to the target function module. At the same time, it determines the function module that has a calling relationship with the target function module from the front-end configuration layer of the target function configuration file as the called function module, and calls the server interface corresponding to the called function module.

[0028] Furthermore, the method further comprises:

[0029] The application system determines the library table configuration file corresponding to the target application ID as the target library table configuration file, and stores the business data of the target function module input by the user in the database table corresponding to the target library table configuration file according to the format recorded in the target library table configuration file.

[0030] Furthermore, the functional configuration file also includes a functional function call layer;

[0031] The method further comprises:

[0032] Each functional module and the corresponding functional function are written into the functional function calling layer of the functional configuration file with the ID of the functional module as the primary key.

[0033] Furthermore, the operation types of the functional modules include adding, deleting, modifying and / or querying;

[0034] When the developer deploys the to-be-deployed functional module into the visual interface, the method further includes:

[0035] Displaying, in the visual interface, at least one call relationship to be selected between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module;

[0036] The calling relationship selected by the developer from the calling relationships to be selected is received, and the selected calling relationship is recorded in the attribute information of the function module to be deployed.

[0037] Furthermore, displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises:

[0038] Calculate the distance between the to-be-deployed function module and each deployed function module according to the position information of the to-be-deployed function module and the position information of each deployed function module;

[0039] The deployed function module whose distance is less than the first preset distance threshold is used as the function module to be called;

[0040] At least one to-be-selected calling relationship between at least one operation type of the functional module to be deployed and at least one operation type of the functional module to be called is displayed in the visual interface.

[0041] Furthermore, after receiving the call relationship selected by the developer from the call relationships to be selected, the method further includes:

[0042] Calculate the distance between the function module to be deployed and the deployed function module corresponding to the selected call relationship according to the position information of the function module to be deployed and the position information of the deployed function module corresponding to the selected call relationship;

[0043] Determining whether the distance exceeds a second preset distance threshold;

[0044] If so, the developer is prompted in the visualization interface to adjust the position of the to-be-deployed functional module in the visualization interface.

[0045] Furthermore, the method further comprises:

[0046] If the developer does not select a calling relationship from the calling relationships to be selected, the calling relationship in the attribute information of the function module to be deployed is set to empty.

[0047] Furthermore, before displaying at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module in the visual interface, the method further comprises:

[0048] Filtering function modules that have no calling relationship with the function module to be deployed from the deployed function modules, and searching for all the calling relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules;

[0049] Displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises:

[0050] All the call relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules are displayed in the visual interface.

[0051] On the other hand, the embodiment of this specification also provides an application building device based on a low-code platform, the device comprising:

[0052] A function module information receiving unit, used to receive deployment information of at least one function module by a developer in a visualization interface of a low-code platform and attribute information of the deployed function module input by the developer in the visualization interface;

[0053] A function configuration file generating unit, configured to generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module;

[0054] A library table configuration file generating unit, used to generate a library table configuration file according to the attribute information of the functional module;

[0055] The application construction unit is used to send the function configuration file and the library table configuration file to the application system after receiving the deployment instructions of the developer for all deployed function modules in the visual interface, so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the function configuration file and the library table configuration file under the application ID to complete the construction of the application.

[0056] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, and the processor implements the above method when executing the computer program.

[0057] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0058] Finally, the embodiments of this specification also provide a computer program product, wherein the computer program product includes a computer program, and the computer program implements the above method when executed by a processor.

[0059] Using the embodiment of this specification, when the developer deploys the function module in the designated area of ​​the visual interface of the low-code platform, the deployment information of the function module and the attribute information entered by the developer are recorded, and then the function configuration file is generated according to the deployment information and the server interface corresponding to the function module, and the library table configuration file is generated according to the attribute information of the function module. The configuration file is used to replace the front-end code generated by the existing low-code platform, and the update and maintenance of the configuration file is more convenient and the operation difficulty is low. Then, after receiving the deployment instruction issued by the developer, the function configuration file and the library table configuration file are issued to the application system, so that the application system generates a database table according to the library table configuration file, creates an application ID, and records the function configuration file and the library table configuration file under the application ID to complete the construction of the application. The method of the embodiment of this specification does not require the developer to understand the database knowledge. It only needs to enter the attribute information in the visual interface to generate the library table configuration file and automatically create the database table. The developer does not need to master the relevant professional knowledge to complete the implementation of the function, which reduces the technical threshold of the developer. At the same time, because the way of generating the front-end code is abandoned, that is, the developer does not need to change the code additionally after building the application, and the function can be realized only by reading and writing the configuration file. In addition, it supports developers to combine multiple function modules to realize more complex functions. When a user uses the application to process business, the various functional modules of the application are first rendered in the visualization page, and then the user's operation information and / or input data for the functional modules are received. According to the server interface called by the operation information determined from the function configuration file, the input data is formatted according to the library table configuration file and stored in the database table to complete the business processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the embodiments of this specification or the technical solutions in 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 embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0061] Figure 1 The figure shows a schematic diagram of an implementation system of a method for building an application based on a low-code platform in an embodiment of this specification;

[0062] Figure 2 The figure is a flowchart of a method for building an application based on a low-code platform according to an embodiment of the present specification;

[0063] Figure 3 It is a schematic diagram of a process of generating a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module in an embodiment of this specification;

[0064] Figure 4 The figure is a flow chart of a developer inputting a calling relationship between a function module to be deployed and a function module that has been deployed in an embodiment of the present specification;

[0065] Figure 5 The figure shows a flow chart of displaying at least one candidate calling relationship between at least one operation type of the functional module to be deployed and at least one operation type of the functional module already deployed in the visual interface in an embodiment of the present specification;

[0066] Figure 6 The figure is a flow chart of reminding developers to adjust the position of the function module to be deployed in the embodiment of this specification;

[0067] Figure 7 It is a schematic diagram of a process of filtering deployed function modules that do not have a calling relationship in an embodiment of this specification;

[0068] Figure 8 The figure shows a schematic diagram of the structure of an application building device based on a low-code platform in an embodiment of this specification;

[0069] Fig. 9 The figure is a schematic diagram of the structure of a computer device in an embodiment of the present specification.

[0070]

Description of reference numerals

[0071] 101. Terminal;

[0072] 102. Server;

[0073] 801, functional module information receiving unit;

[0074] 802. Functional configuration file generating unit;

[0075] 803, library table configuration file generation unit;

[0076] 804, application building unit;

[0077] 902. Computer equipment;

[0078] 904. Processing equipment;

[0079] 906. Storage resources;

[0080] 908, drive system;

[0081] 910, input / output module;

[0082] 912. Input device;

[0083] 914. Output device;

[0084] 916. Presentation equipment;

[0085] 918. Graphical user interface;

[0086] 920, network interface;

[0087] 922, communication link;

[0088] 924. Communication bus. DETAILED DESCRIPTION

[0089] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of this specification.

[0090] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0091] It should be noted that the acquisition, storage, use, and processing of data in the technical solutions of the embodiments of this specification comply with the relevant provisions of national laws and regulations.

[0092] It should be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0093] like Figure 1The diagram is a schematic diagram of an implementation system of a method for building an application based on a low-code platform in an embodiment of the specification, including a terminal 101 and a server 102. The terminal 101 and the server 102 can communicate through a network, and the network can include a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and is connected to a website, a user device (such as a computing device), and a back-end system.

[0094] The terminal 101 can be a visualization device with input function, such as a combination of a display and an input device or a touch screen, etc. The server 102 can be a server running a low-code platform, sending data to the terminal 101 for display, and receiving input from the developer through the terminal 101.

[0095] Alternatively, the server 102 may be a node of a cloud computing system (not shown), or each server may be a separate cloud computing system including a plurality of computers interconnected by a network and operating as a distributed processing system.

[0096] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the embodiment of this specification. In actual application, other application environments may also be included, and this specification does not limit it.

[0097] In response to the problems existing in the prior art, the embodiments of this specification provide an application building method based on a low-code platform. Developers develop applications by dragging and combining functional modules and entering attribute content on a visual interface. The system generates a functional configuration file based on the functional modules dragged and combined by the developer, generates a library table configuration file based on the attribute information of the corresponding functional modules entered by the developer, and automatically associates the functional modules with the calls of the server interface to realize visual development of the application. Figure 2 The figure shows a flow chart of the method for building an application based on a low-code platform in an embodiment of this specification. This figure describes the process of developers building an application. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or device product is executed, it can be executed in the order of the method shown in the embodiment or the accompanying drawings or in parallel.

[0098] Specific as Figure 2 As shown, the method may include:

[0099] Step 201: receiving deployment information of at least one functional module from a developer in a visualization interface of a low-code platform and attribute information of the deployed functional module input by the developer in the visualization interface;

[0100] Step 202: Generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module;

[0101] Step 203: Generate a library table configuration file according to the attribute information of the functional module;

[0102] Step 204: After receiving the deployment instructions of all deployed functional modules from the developer in the visual interface, the functional configuration file and the library table configuration file are sent to the application system so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the functional configuration file and the library table configuration file under the application ID to complete the construction of the application.

[0103] Using the embodiment of this specification, when the developer deploys the function module in the designated area of ​​the visual interface of the low-code platform, the deployment information of the function module and the attribute information entered by the developer are recorded, and then the function configuration file is generated according to the deployment information and the server interface corresponding to the function module, and the library table configuration file is generated according to the attribute information of the function module. The configuration file is used to replace the front-end code generated by the existing low-code platform, and the update and maintenance of the configuration file is more convenient and the operation difficulty is low. Then, after receiving the deployment instruction issued by the developer, the function configuration file and the library table configuration file are issued to the application system, so that the application system generates a database table according to the library table configuration file, creates an application ID, and records the function configuration file and the library table configuration file under the application ID to complete the construction of the application. The method of the embodiment of this specification does not require the developer to understand the database knowledge. It only needs to enter the attribute information in the visual interface to generate the library table configuration file and automatically create the database table. The developer does not need to master the relevant professional knowledge to complete the implementation of the function, which reduces the technical threshold of the developer. At the same time, because the way of generating the front-end code is abandoned, that is, the developer does not need to change the code additionally after building the application, and the function can be realized only by reading and writing the configuration file. In addition, it supports developers to combine multiple function modules to realize more complex functions. When a user uses the application to process business, the various functional modules of the application are first rendered in the visualization page, and then the user's operation information and / or input data for the functional modules are received. According to the server interface called by the operation information determined from the function configuration file, the input data is formatted according to the library table configuration file and stored in the database table to complete the business processing.

[0104] In the embodiment of this specification, the developer first enters the account password, logs in the application construction platform (that is, the front-end platform of the application system), then selects the template, area or component material in the task bar of the application construction platform, drags it to the preview interface, clicks the component material (that is, the functional module) that needs to be edited, and can configure the attribute information of the component material (including: field attributes, field names, permission configuration, associated attributes, interactive mode and other attributes) in the pop-up interface, and the application construction platform records the developer's deployment information of the component material and the server interface corresponding to the component material. Generate a function configuration file (Schema configuration file) and a library table configuration file. After the developer has configured it in the visual interface, he can click the "deployment and distribution" button, and the application construction platform will issue the function configuration file and the library table configuration file to the server of the application system (such as the bank back-end server), and the application system obtains the table field information in the library table configuration file, automatically generates a library table creation statement after parsing the field attributes, field names, permissions and other information, and imports the library table creation statement into the connected database for automatic execution, and creates a database table for user storage business data. And create an application ID. The purpose of the application ID is to manage the application, and record the function configuration file and library table configuration file under the application ID to complete the construction of the application.

[0105] Then, the thumbnail corresponding to the application ID can be displayed on the front-end page (different from the visual interface released by the low-code platform on which developers build applications). When the user (the party using the application to handle business) starts the application, the front-end page notifies the application system (the bank's back-end server) that the application corresponding to the application ID needs to be started. The application system then notifies the front-end rendering component to read and parse the functional configuration file to implement business functions. The front-end rendering engine obtains the Schema configuration file in the application system, maps the ComponentName field in the Schema configuration file to the component instance (Components), and can render the effects designed by the user in the model instantiation operation platform based on other attribute fields.

[0106] Afterwards, the user can see the page of the application built by the developer in the front-end page of the application system. When the user triggers the function module of the application, the user's operation information on the function module is received (which may also include input data). The front-end packages the user's operation information (which may also include input data) in the format specified by the system's internal protocol and sends it to the application system (bank back-end server). The application system parses the data packet, reads the function configuration file according to the operation information, and obtains the called server interface. After completing the business function, the server interface returns completion information to the front-end (if it contains input data, the input data will be formatted according to the library table configuration file and stored in the database table), so that the user can learn about the execution of the business from the front-end page.

[0107] For example, if the user's operation information for a function module is a click, the front end will parse the operation type corresponding to the click operation (such as adding, deleting, and other operations of the function module), and then send the operation information to the application system. The application system finds the server interface corresponding to the adding or deleting operation of this function module from the function configuration file, and then calls the server interface. The server interface is pre-built by the developer in the bank's back-end server. The parameters required for the server interface call, the database table from which data is obtained when the server interface is executed, what kind of calculation is performed, and the database table in which the generated results are stored are all pre-defined. When calling the server interface, you only need to call the required parameters (this parameter can be the data of the function module entered by the user recorded by the front end), or store the data of the function module entered by the user in the database table built through the library table configuration file, and then call the server interface.

[0108] According to one embodiment of the present specification, the type of the functional module includes a data type;

[0109] Receiving the attribute information of the deployed functional module input by the developer in the visual interface further includes:

[0110] Receive attribute information of the functional module of the data type, wherein the attribute information at least includes a field name and a data type.

[0111] For example, the functional module is an input box, and the type of the input box is a data type. When the developer deploys the input box in the visual interface, the visual interface prompts the developer to configure the attribute information of the input box (including field name and data type), and then the application building platform writes the field name and data type into the library table configuration file according to the corresponding relationship.

[0112] According to an embodiment of the present specification, the application system generates a database table according to the library table configuration file further comprising:

[0113] The application system parses the library table configuration file to obtain the field name and the corresponding data type, and uses the field name and data type as parameters to execute a database table construction script to generate the database table.

[0114] The database table is then associated with the library table configuration file and / or application ID.

[0115] According to an embodiment of the present specification, the deployment information includes a function module ID, location information, and a call relationship with a currently deployed function module; the function configuration file includes a front-end configuration layer and an interface call layer;

[0116] like Figure 3 As shown, generating a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module further includes:

[0117] Step 301: writing the location information of each function module, the calling relationship between each function module and the rendering style information of each function module into the front-end configuration layer of the function configuration file with the function module ID as the primary key;

[0118] Step 302: Write the calling relationship between each functional module and the corresponding server interface into the interface calling layer of the functional configuration file using the functional module ID as the primary key.

[0119] In the embodiments of this specification, the location information indicates the location where the developer deploys the function module in the specified area of ​​the visual interface, including the horizontal coordinate and the vertical coordinate. The calling relationship between the function modules means that after the user operates a function module, the system automatically calls other function modules. For example, after the user enters content in the input box, the system automatically calls the query function to echo the content entered by the user, or after the user clicks the delete button, the system automatically issues a delete instruction to the corresponding function module. In the prior art, developers need to write code to implement the calling logic between function modules.

[0120] In the embodiment of the present specification, when the developer deploys the function module in the visual interface, the location information of the function module and the calling relationship between the function modules deployed in the current visual interface (that is, the application currently being built) will be recorded. The calling relationship can be input by the developer when deploying the function module. Then, the location information of each function module, the calling relationship between each function module, and the rendering style information of each function module are written into the front-end configuration layer of the function configuration file with the function module ID as the primary key.

[0121] Furthermore, the calling relationship between each functional module and the corresponding server interface is written into the interface calling layer of the functional configuration file using the ID of the functional module as the primary key.

[0122] When the application system receives an instruction from the user to start the application, it notifies the front-end rendering component to render each functional module in the front-end configuration layer of the functional configuration file according to the rendering style information and location information, obtains the interface of the application, and displays the interface of the application to the user, so that the user can interact with the functional modules in the interface of the application and perform corresponding business processing.

[0123] Furthermore, the user interacts with the functional modules in the interface of the application program to perform corresponding business processing further including:

[0124] After the application system receives the user's operation instruction on the target function module in the interface, it takes the application interacted by the user as the target application, determines the function configuration file corresponding to the target application ID as the target function configuration file, determines the server interface corresponding to the target function module from the interface call layer of the target function configuration file, and calls the server interface corresponding to the target function module. At the same time, it determines the function module that has a calling relationship with the target function module from the front-end configuration layer of the target function configuration file as the called function module, and calls the server interface corresponding to the called function module.

[0125] In the embodiments of this specification, the function modules can also be called nested, that is, when the application system automatically calls the called function module, it can also determine from the front-end configuration layer of the called function module whether there is a function module with a calling relationship, and if so, call the function module.

[0126] Furthermore, the application system determines the library table configuration file corresponding to the target application ID as the target library table configuration file, and stores the business data of the target function module input by the user in the database table corresponding to the target library table configuration file according to the format recorded in the target library table configuration file.

[0127] According to an embodiment of the present specification, in order to avoid business processing failure due to the server interface being unable to meet business requirements, the function configuration file in the embodiment of the present specification also includes a function calling layer, and each function module and the corresponding function and calling parameters are written into the function calling layer of the function configuration file with the function module ID as the primary key.

[0128] It can be understood that when the server interface cannot meet the requirements, for example, calling the server interface returns an exception, the system application can determine the corresponding function in the function call layer of the function configuration file, execute the function, and process the business normally.

[0129] It should be noted that not all functional modules need to call the server interface or have functional functions. When building functional modules, developers can determine whether it is necessary to call the server interface or configure functional functions based on the functions of the functional modules. If it is not necessary to call the server interface or configure functional functions, the interface call layer and the functional function call layer are configured to be empty. For example, the delete button does not need to call the server interface or execute functional functions. It only needs to call the delete operation of other functional modules. Therefore, the interface call layer and functional function call layer of the delete button are configured to be empty, and the front-end configuration layer only needs to record its calling relationship with other functional modules.

[0130] According to one embodiment of the present specification, the operation types of the functional modules include adding, deleting, modifying and / or querying;

[0131] In the embodiments of this specification, when a developer deploys a function module, the calling relationship between the function module and the deployed function modules is input by the developer. Figure 4 As shown, when the developer deploys the function module to be deployed into the visual interface, the method further includes:

[0132] Step 401: displaying at least one call relationship to be selected between at least one operation type of the function module to be deployed and at least one operation type of the deployed function module in the visual interface;

[0133] Step 402: receiving the call relationship selected by the developer from the call relationships to be selected, and recording the selected call relationship in the attribute information of the function module to be deployed.

[0134] In the embodiment of the present specification, after the developer deploys the function module to be deployed in the visual interface, the operation type (addition, deletion, modification and / or query) of the function module to be deployed and the operation type (addition, deletion, modification and / or query) of the deployed function module are displayed in the visual interface to be selected (addition of the selected function module calls the query of the deployed function module, etc.), all the operation types can be displayed around the function module to be deployed, and all the operation types of the deployed function module can be displayed around the deployed function module, and then a connection line with an arrow is displayed between an operation type of the function module to be deployed and an operation type of the deployed function module, and the arrow points to an operation type of the deployed function module. If the developer selects the connection line, the connection line is highlighted, and after a period of time (for example, 0.5 seconds), all the connections between the function module to be deployed and the deployed function module disappear, so as to avoid visual inconvenience to the developer. In addition, multiple selection of connections is also supported, so as to meet the configuration of the calling relationship between multiple operation types of the function module to be deployed and multiple operation types of the deployed function module.

[0135] The calling relationship between the operation type of the function module to be deployed and the operation type of the deployed function module is recorded in the front-end configuration layer of the function module to be deployed.

[0136] It can be understood that developers can input call relationships in a selected form to improve development efficiency.

[0137] According to one embodiment of the present specification, in order to improve the intelligence level of building an application, such as Figure 5 As shown, displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further includes:

[0138] Step 501: Calculate the distance between the to-be-deployed function module and each deployed function module according to the position information of the to-be-deployed function module and the position information of each deployed function module;

[0139] Step 502: taking the deployed function module whose distance is less than the first preset distance threshold as the function module to be called;

[0140] Step 503: displaying at least one candidate calling relationship between at least one operation type of the functional module to be deployed and at least one operation type of the functional module to be called in the visual interface.

[0141] It can be understood that if the developer wants to configure a calling relationship between the function module to be deployed and a deployed function module, the function module to be deployed will mostly be deployed near the deployed function module, so as to conform to the user's operating habits. If the developer places the function module to be deployed far away from a deployed function module, the possibility of a calling relationship between the two is very small. Therefore, the embodiment of this specification first calculates the distance between the function module to be deployed and the deployed function module, and then uses the deployed function module whose distance is less than the first preset distance threshold value (which can be an empirical value) as the function module to be called. The function module to be called is a function module that the system predicts may have a calling relationship with the function module to be deployed, but it does not mean that there must be a calling relationship between the two. Whether there is a calling relationship needs to be selected by the developer.

[0142] Then, the candidate calling relationships between the operation types of the function modules to be deployed and the operation types of the function modules to be called are displayed in the visual interface for the developers to select.

[0143] It can be understood that when the developer drags the function module to be deployed in the visual interface, the system will calculate the distance between the function module to be deployed and the deployed function modules in real time, and find out the function module to be called whose distance is less than the first preset distance threshold value, and display the connection between the operation type of the function module to be called and the operation type of the function module to be deployed. The developer determines the deployment location of the function module to be deployed based on the connection and the development requirements of the application, and then selects the required connection after deployment.

[0144] In some other embodiments of this specification, if the developer wants to configure the calling relationship between the function module to be deployed and a deployed function module, but if the developer deploys the two modules too far apart, this will not conform to the user's operating habits. Therefore, according to one embodiment of this specification, Figure 6 As shown, after receiving the call relationship selected by the developer from the call relationships to be selected, the method further includes:

[0145] Step 601: Calculate the distance between the function module to be deployed and the deployed function module corresponding to the selected calling relationship according to the position information of the function module to be deployed and the position information of the deployed function module corresponding to the selected calling relationship;

[0146] Step 602: Determine whether the distance exceeds a second preset distance threshold;

[0147] Step 603: If yes, prompting the developer in the visualization interface to adjust the position of the to-be-deployed functional module in the visualization interface.

[0148] In the embodiment of the present specification, the second preset distance threshold value may be an empirical value, which is not limited in the embodiment of the present specification.

[0149] In the embodiments of this specification, not all functional modules can have a calling relationship. Therefore, according to an embodiment of this specification, Figure 7 As shown, before displaying at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module in the visual interface, the method further includes:

[0150] Step 701: filtering function modules that have no calling relationship with the function module to be deployed from the deployed function modules, and searching for all the calling relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules;

[0151] Displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises:

[0152] Step 702: Displaying all the call relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules in the visual interface.

[0153] In the embodiments of this specification, whether there can be a calling relationship between functional modules can be determined by the developer when constructing the functional modules, and this embodiment of this specification does not impose any limitation.

[0154] It can be understood that after filtering out the deployed functional modules that do not have a calling relationship, the number of connections in the visual interface will be greatly reduced, thereby preventing excessive connections from hindering developers' development.

[0155] Based on the same inventive concept, the embodiment of this specification also provides an application building device based on a low-code platform, such as Figure 8 As shown, the device comprises:

[0156] The function module information receiving unit 801 is used to receive the deployment information of at least one function module by the developer in the visualization interface of the low-code platform and the attribute information of the deployed function module input by the developer in the visualization interface;

[0157] A function configuration file generating unit 802 is used to generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module;

[0158] A library table configuration file generating unit 803 is used to generate a library table configuration file according to the attribute information of the functional module;

[0159] The application construction unit 804 is used to send the function configuration file and the library table configuration file to the application system after receiving the deployment instructions of the developer for all deployed function modules in the visual interface, so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the function configuration file and the library table configuration file under the application ID to complete the construction of the application.

[0160] Further, the type of the functional module includes a data type;

[0161] Receiving the attribute information of the deployed functional module input by the developer in the visual interface further includes:

[0162] Receive attribute information of the functional module of the data type, wherein the attribute information at least includes a field name and a data type.

[0163] Furthermore, generating a library table configuration file according to the attribute information of the functional module further includes:

[0164] The field names and data types are written into the library table configuration file according to the corresponding relationship.

[0165] Furthermore, the application system generates a database table according to the library table configuration file, further comprising:

[0166] The application system parses the library table configuration file to obtain the field name and the corresponding data type, and uses the field name and data type as parameters to execute a database table construction script to generate the database table.

[0167] Furthermore, the deployment information includes a function module ID, location information, and a call relationship with a currently deployed function module; the function configuration file includes a front-end configuration layer and an interface call layer;

[0168] Generating a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module further includes:

[0169] Write the location information of each function module, the calling relationship between each function module, and the rendering style information of each function module into the front-end configuration layer of the function configuration file with the function module ID as the primary key;

[0170] The calling relationship between each functional module and the corresponding server interface is written into the interface calling layer of the functional configuration file with the functional module ID as the primary key.

[0171] Furthermore, the device also includes a processing unit, which is used to control the application system to notify the front-end rendering component to render each functional module in the front-end configuration layer of the functional configuration file according to the rendering style information and location information after completing the construction of the application, when receiving the user's instruction to start the application, to obtain the interface of the application, and to display the interface of the application to the user, so that the user can interact with the functional modules in the interface of the application and perform corresponding business processing.

[0172] Furthermore, the user interacts with the functional modules in the interface of the application program to perform corresponding business processing further including:

[0173] After the application system receives the user's operation instruction on the target function module in the interface, it takes the application interacted by the user as the target application, determines the function configuration file corresponding to the target application ID as the target function configuration file, determines the server interface corresponding to the target function module from the interface call layer of the target function configuration file, and calls the server interface corresponding to the target function module. At the same time, it determines the function module that has a calling relationship with the target function module from the front-end configuration layer of the target function configuration file as the called function module, and calls the server interface corresponding to the called function module.

[0174] Furthermore, the processing unit is further used for:

[0175] The application system determines the library table configuration file corresponding to the target application ID as the target library table configuration file, and stores the business data of the target function module input by the user in the database table corresponding to the target library table configuration file according to the format recorded in the target library table configuration file.

[0176] Furthermore, the functional configuration file also includes a functional function call layer;

[0177] The function profile generating unit 802 is further used for:

[0178] Each functional module and the corresponding functional function are written into the functional function calling layer of the functional configuration file with the ID of the functional module as the primary key.

[0179] Furthermore, the operation types of the functional modules include adding, deleting, modifying and / or querying;

[0180] When the developer deploys the to-be-deployed functional module into the visual interface, the device further includes a rendering unit, which is used to:

[0181] Displaying, in the visual interface, at least one call relationship to be selected between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module;

[0182] The calling relationship selected by the developer from the calling relationships to be selected is received, and the selected calling relationship is recorded in the attribute information of the function module to be deployed.

[0183] Furthermore, displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises:

[0184] Calculate the distance between the to-be-deployed function module and each deployed function module according to the position information of the to-be-deployed function module and the position information of each deployed function module;

[0185] The deployed function module whose distance is less than the first preset distance threshold is used as the function module to be called;

[0186] At least one to-be-selected calling relationship between at least one operation type of the functional module to be deployed and at least one operation type of the functional module to be called is displayed in the visual interface.

[0187] Furthermore, the rendering unit is further configured to, after receiving the call relationship selected by the developer from the call relationships to be selected, calculate the distance between the function module to be deployed and the deployed function module corresponding to the selected call relationship according to the location information of the function module to be deployed and the location information of the deployed function module corresponding to the selected call relationship;

[0188] Determining whether the distance exceeds a second preset distance threshold;

[0189] If so, the developer is prompted in the visualization interface to adjust the position of the to-be-deployed functional module in the visualization interface.

[0190] Furthermore, the function configuration file generating unit 802 is further used for:

[0191] If the developer does not select a calling relationship from the calling relationships to be selected, the calling relationship in the attribute information of the function module to be deployed is set to empty.

[0192] Furthermore, the rendering unit is further used to filter out functional modules that do not have a calling relationship with the functional module to be deployed from the deployed functional modules before displaying at least one calling relationship to be selected between at least one operation type of the functional module to be deployed and at least one operation type of the deployed functional modules in the visual interface, and search for all calling relationships to be selected between the functional module to be deployed and each functional module in the filtered deployed functional modules;

[0193] Displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises:

[0194] All the call relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules are displayed in the visual interface.

[0195] Since the principle of solving the problem by the above device is similar to that of the above method, the implementation of the above system can refer to the implementation of the above method, and the repeated parts will not be repeated.

[0196] like Fig. 9 The figure is a schematic diagram of the structure of the computer device in the embodiment of this specification. The method in the embodiment of this specification can be applied to the computer device in this embodiment.

[0197] Specifically, Fig. 9 As shown, the computer device 902 may include one or more processing devices 904, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 902 may also include any storage resource 906, which is used to store any kind of information such as code, settings, data, etc. Without limitation, for example, the storage resource 906 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any storage resource may use any technology to store information.

[0198] Further, any storage resource may provide volatile or non-volatile retention of information.

[0199] Further, any storage resource may represent a fixed or removable component of the computer device 902. In one case, when the processing device 904 executes the associated instructions stored in any storage resource or combination of storage resources, the computer device 902 may perform any operation of the associated instructions. The computer device 902 also includes one or more drive systems 908 for interacting with any storage resource, such as a hard disk drive system, an optical disk drive system, etc.

[0200] The computer device 902 may also include an input / output module 910 (I / O) for receiving various inputs (via input devices 912) and for providing various outputs (via output devices 914). A specific output mechanism may include a presentation device 916 and an associated graphical user interface (GUI) 918. In other embodiments, the input / output module 910 (I / O), the input device 912, and the output device 914 may not be included, and the computer device 902 may be used as a computer device in a network. The computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the components described above together.

[0201] The communication link 922 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0202] The embodiments of the present specification also provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0203] The embodiments of the present specification also provide a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to execute the above method.

[0204] It should be understood that in the various embodiments of the present specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present specification.

[0205] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the embodiments of this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0206] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of this specification can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of this specification.

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

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

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

[0210] In addition, each functional unit in each embodiment of the present specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

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

[0212] The embodiments of this specification use specific embodiments to illustrate the principles and implementation methods of the embodiments of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of the embodiments of this specification. At the same time, for those skilled in the art, according to the ideas of the embodiments of this specification, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of this specification.

Claims

1. A method for building an application based on a low-code platform, characterized in that: The method comprises: Receive deployment information of at least one functional module from a developer in a visualization interface of a low-code platform and attribute information of the deployed functional module input by the developer in the visualization interface; Generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module; Generate a library table configuration file according to the attribute information of the functional module; After receiving the deployment instructions issued by the developer for all deployed functional modules in the visual interface, the functional configuration file and the library table configuration file are sent to the application system so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the functional configuration file and the library table configuration file under the application ID to complete the construction of the application.

2. The method according to claim 1, characterized in that The types of the functional modules include data types; Receiving the attribute information of the deployed functional module input by the developer in the visual interface further includes: Receive attribute information of the functional module of the data type, wherein the attribute information at least includes a field name and a data type.

3. The method according to claim 2, characterized in that Generating a library table configuration file according to the attribute information of the functional module further includes: The field names and data types are written into the library table configuration file according to the corresponding relationship.

4. The method according to claim 3, characterized in that The application system generates a database table according to the library table configuration file further comprising: The application system parses the library table configuration file to obtain the field name and the corresponding data type, and uses the field name and data type as parameters to execute a database table construction script to generate the database table.

5. The method according to claim 1, characterized in that: The deployment information includes the function module ID, location information and the calling relationship with the currently deployed function module; the function configuration file includes the front-end configuration layer and the interface calling layer; Generating a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module further includes: Write the location information of each function module, the calling relationship between each function module, and the rendering style information of each function module into the front-end configuration layer of the function configuration file with the function module ID as the primary key; The calling relationship between each functional module and the corresponding server interface is written into the interface calling layer of the functional configuration file with the functional module ID as the primary key.

6. The method according to claim 5, characterized in that After completing the construction of the application, the method further includes: When the application system receives an instruction from the user to start the application, it notifies the front-end rendering component to render each functional module in the front-end configuration layer of the functional configuration file according to the rendering style information and location information, obtains the interface of the application, and displays the interface of the application to the user, so that the user can interact with the functional modules in the interface of the application and perform corresponding business processing.

7. The method according to claim 6, characterized in that The user interacts with the functional modules in the interface of the application program to perform corresponding business processing further comprising: After the application system receives the user's operation instruction on the target function module in the interface, it takes the application interacted by the user as the target application, determines the function configuration file corresponding to the target application ID as the target function configuration file, determines the server interface corresponding to the target function module from the interface call layer of the target function configuration file, and calls the server interface corresponding to the target function module. At the same time, it determines the function module that has a calling relationship with the target function module from the front-end configuration layer of the target function configuration file as the called function module, and calls the server interface corresponding to the called function module.

8. The method according to claim 7, characterized in that The method further comprises: The application system determines the library table configuration file corresponding to the target application ID as the target library table configuration file, and stores the business data of the target function module input by the user in the database table corresponding to the target library table configuration file according to the format recorded in the target library table configuration file.

9. The method according to claim 5, characterized in that The functional configuration file also includes a functional function call layer; The method further comprises: Each functional module and the corresponding functional function are written into the functional function calling layer of the functional configuration file with the ID of the functional module as the primary key.

10. The method according to claim 5, characterized in that The operation types of the functional modules include adding, deleting, modifying and / or querying; When the developer deploys the to-be-deployed functional module into the visual interface, the method further includes: Displaying, in the visual interface, at least one call relationship to be selected between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module; The calling relationship selected by the developer from the calling relationships to be selected is received, and the selected calling relationship is recorded in the attribute information of the function module to be deployed.

11. The method according to claim 10, characterized in that Displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises: Calculate the distance between the to-be-deployed function module and each deployed function module according to the position information of the to-be-deployed function module and the position information of each deployed function module; The deployed function module whose distance is less than the first preset distance threshold is used as the function module to be called; At least one to-be-selected calling relationship between at least one operation type of the functional module to be deployed and at least one operation type of the functional module to be called is displayed in the visual interface.

12. The method according to claim 10, characterized in that After receiving the call relationship selected by the developer from the call relationships to be selected, the method further includes: Calculate the distance between the function module to be deployed and the deployed function module corresponding to the selected call relationship according to the position information of the function module to be deployed and the position information of the deployed function module corresponding to the selected call relationship; Determining whether the distance exceeds a second preset distance threshold; If so, the developer is prompted in the visualization interface to adjust the position of the to-be-deployed functional module in the visualization interface.

13. The method according to claim 10, characterized in that The method further comprises: If the developer does not select a calling relationship from the calling relationships to be selected, the calling relationship in the attribute information of the function module to be deployed is set to empty.

14. The method according to claim 10, characterized in that Before displaying at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module in the visual interface, the method further includes: Filtering function modules that have no calling relationship with the function module to be deployed from the deployed function modules, and searching for all the calling relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules; Displaying in the visual interface at least one to-be-selected calling relationship between at least one operation type of the to-be-deployed functional module and at least one operation type of the deployed functional module further comprises: All the call relationships to be selected between the function module to be deployed and each function module in the filtered deployed function modules are displayed in the visual interface.

15. An application building device based on a low-code platform, characterized in that: The device comprises: A function module information receiving unit, used to receive deployment information of at least one function module by a developer in a visualization interface of a low-code platform and attribute information of the deployed function module input by the developer in the visualization interface; A function configuration file generating unit, configured to generate a function configuration file according to the deployment information of the function module and the server interface corresponding to the function module; A library table configuration file generating unit, used to generate a library table configuration file according to the attribute information of the functional module; The application construction unit is used to send the function configuration file and the library table configuration file to the application system after receiving the deployment instructions of the developer for all deployed function modules in the visual interface, so that the application system can generate a database table according to the library table configuration file, create an application ID, and record the function configuration file and the library table configuration file under the application ID to complete the construction of the application.

16. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 14 is implemented.

17. 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 1 to 14 is implemented.

18. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 14 is implemented.

Images