A method and device for presetting an experience environment on a low-code platform

Abstract

The present invention discloses a method and device for presetting an experience environment on a low-code platform, which relates to the field of code development technology. By keeping the table structure of the metadata of the low-code consistent in the design state and the running state, and directly connecting the running state backend process with the design state database or the environment metadata database, a set of experience environments is preset, and the running state process and the running state instance database are deployed in the experience environment. If the version of the application is consistent with the existing version of the application in the current experience environment, the real-time publishing interface of the running state is called to publish it. When switching the version of the application in the experience environment, the design state calls the version switching interface of the running state of the experience environment to update the experience environment. During external access, the routing is distinguished by the environment flag in the URL, and the corresponding interface is displayed to the user through the running state background interface; the user's development and testing efficiency is improved, and the development has a what-you-see-is-what-you-get effect.

Description

Technical Field

[0001] The present invention relates to the field of code development technology, and specifically to a method and device for presetting an experience environment on a low-code platform. Background Art

[0002] A low-code platform is a development platform that eliminates the need for extensive coding. It enables rapid application development through a graphical user interface and visual drag-and-drop components. Compared to traditional software development models, low-code platforms offer higher productivity and lower development costs. Low-code platforms are primarily divided into two phases: design phase and runtime phase. The design phase refers to the application design phase within a low-code platform. In this phase, users can visually drag and drop components, define processes, configure services, and integrate data sources to build application prototypes and logic.

[0003] The running state refers to the link in the low-code platform used to deploy and run applications.

[0004] When low-code is released from the design state to the running state environment, metadata such as the front-end page schema, custom interfaces, data models, static resources, and running state processes in the design state need to be published to the corresponding environment. This involves a large amount of data and a long publishing time. Compared with the zero-code platform with WYSIWYG, the user experience is not as good.

[0005] In the SAAS model architecture of existing technology, the design state is multi-tenant sharing, and the low-code application products are published to the running environment. The environment is physically isolated according to the tenant application, which can effectively improve performance. However, due to the large amount of published resources, it does not have a what-you-see-is-what-you-get development effect, and the experience is poor.

[0006] To this end, the present invention proposes a method and device for presetting an experience environment on a low-code platform. Summary of the Invention

[0007] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a method and device for presetting an experience environment on a low-code platform to improve user development and testing efficiency and achieve a what-you-see-is-what-you-get effect.

[0008] To achieve the above objectives, according to embodiment 1 of the present invention, a method for presetting an experience environment on a low-code platform is proposed, comprising the following steps:

[0009] Step 1: Keep the table structure of the low-code metadata consistent in the design state and the running state, and directly connect the running state backend process to the design state database or the environment metadata database;

[0010] Step 2: Preset a set of experience environments and deploy two modules, the running process and the running instance database, in the experience environment;

[0011] Step 3: Record the version association relationship in the low-code design state. When the application in the design state involves the preset version comparison condition, first determine whether the application version is consistent with the existing version of the application in the current experience environment. If they are consistent, call the real-time publishing interface in the running state to publish; if not, ignore it;

[0012] Step 4: When switching the version of the specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment;

[0013] Step 5: When accessing the design state and experience environment externally, use the same domain name for access and differentiate the routes using the environment flag in the URL. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes.

[0014] Step 6: When the user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state back-end interface;

[0015] The metadata table structure includes tenant, application, and version identifiers;

[0016] The metadata and static resources that the experience environment depends on are obtained from the design state, and in the experience environment, only one version of the same application can be run at the same time;

[0017] The version association relationship includes the association relationship among applications, versions and experience environments;

[0018] The version comparison conditions include database model, process orchestration, service orchestration, and running instance data of timer configuration;

[0019] The design state calls the switching version interface of the experience environment running state to update the experience environment in the following manner:

[0020] The running process queries the metadata information of the old and new versions, compares the metadata information of the old and new versions, updates the content of the instance database with the new version data, and updates the version information of the current application in the experience environment stored in the design state;

[0021] The method of displaying the corresponding interface to the user through the running background interface is:

[0022] Call the interface of the running background process to obtain metadata and running instance data, and parse them to present on the front-end page.

[0023] A device for presetting the experience environment on a low-code platform is proposed, including a design state, an experience environment, and an external environment interface;

[0024] Design state refers to the phase of designing applications in a low-code platform. In design state, users generate application prototypes and logic by visually dragging and dropping components, defining processes, configuring services, and integrating data sources.

[0025] Deploy two modules, a running process and a running instance database, in the experience environment;

[0026] In the experience environment, the version association relationship is recorded in the low-code design state. When the application in the design state involves the preset version comparison condition, it is first determined whether the version of the application is consistent with the existing version of the application in the current experience environment. If they are consistent, the real-time publishing interface of the running state is called to publish; if they are inconsistent, it is ignored;

[0027] The external environment interface is used to provide users with an access interface for accessing the design state and experience environment;

[0028] When switching the version of a specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment;

[0029] When users access the design state and experience environment through the external environment interface, they use the same domain name for access and use the environment flag in the URL to distinguish the routes. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes.

[0030] When a user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state background interface.

[0031] Compared with the prior art, the present invention has the following beneficial effects:

[0032] The present invention keeps the table structure of the low-code metadata consistent in the design state and the running state, and directly connects the running state backend process with the design state database or the environment metadata database, presets a set of experience environments, deploys two modules, the running state process and the running state instance database in the experience environment, and records the version association relationship in the low-code design state. When the design state application involves the preset version comparison condition, it first determines whether the version of the application is consistent with the existing version of the application in the current experience environment. If they are consistent, the real-time publishing interface of the running state is called for publishing; if they are inconsistent, it is ignored. When the version of the specified application in the experience environment is switched, the design state calls the experience environment The experience environment is updated through the switching version interface of the design state and the running state. When accessing the design state and the experience environment from the outside, the same domain name is used for access, and the routing is distinguished by the environment flag in the URL. Nginx forwards to different front-end modules of the design state and the running state according to the route. When the user accesses the front-end page of the running state, the corresponding interface is displayed to the user through the running state background interface; by presetting a tenant-shared "experience environment" in the low-code platform, sharing metadata / static resources with the design state, and real-time incremental publishing to the experience environment, the user's investment cost in setting up the environment is reduced, the user's development and testing efficiency is improved, and the development has a what-you-see-is-what-you-get effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a flowchart of a method for presetting an experience environment on a low-code platform in embodiment 1 of the present invention;

[0034] Figure 2 This is a module connection relationship diagram of the device for presetting the experience environment on the low-code platform in Example 2 of the present invention. DETAILED DESCRIPTION

[0035] The technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0036] like Figure 1 As shown, a method for presetting an experience environment on a low-code platform includes the following steps:

[0037] Step 1: Keep the table structure of the low-code metadata consistent in the design state and the running state, and directly connect the running state backend process to the design state database or the environment metadata database;

[0038] Step 2: Preset a set of experience environments and deploy two modules, the running process and the running instance database, in the experience environment;

[0039] Step 3: Record the version association relationship in the low-code design state. When the application in the design state involves the preset version comparison condition, first determine whether the application version is consistent with the existing version of the application in the current experience environment. If they are consistent, call the real-time publishing interface in the running state to publish; if not, ignore it;

[0040] Step 4: When switching the version of the specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment;

[0041] Step 5: When accessing the design state and experience environment externally, use the same domain name for access and differentiate the routes using the environment flag in the URL. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes.

[0042] Step 6: When the user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state back-end interface;

[0043] It should be noted that the design phase refers to the phase of the low-code platform used to design applications. In the design phase, users can visually drag and drop components, define processes, configure services, and integrate data sources to generate application prototypes and logic.

[0044] The running state refers to the part of the low-code platform used to deploy and run applications;

[0045] The metadata table structure includes tenant, application, and version identifiers;

[0046] Furthermore, the metadata and static resources that the experience environment depends on are obtained from the design state, and in the experience environment, only one version of the same application can be run at the same time;

[0047] Furthermore, the version association relationship includes the association relationship among applications, versions and experience environments;

[0048] Furthermore, the version comparison conditions include running instance data of database models, process orchestration, service orchestration, and timer configuration;

[0049] Furthermore, the design state calls the switching version interface of the experience environment running state to update the experience environment in the following manner:

[0050] The running process queries the metadata information of the old and new versions, compares the metadata information of the old and new versions, updates the content of the instance database with the new version data, and updates the version information of the current application in the experience environment stored in the design state;

[0051] Furthermore, the method of displaying the corresponding interface to the user through the running background interface is:

[0052] Call the interface of the running background process to obtain metadata and running instance data, and parse them to present on the front-end page.

[0053] It is understandable that by presetting a set of "operational-experience environments", including three processes: operational backend / database / operational frontend, all tenants share this method. This method does not significantly increase the operation and maintenance costs of the system, and can save costs compared to each tenant purchasing independent environment resources on their own.

[0054] Furthermore, the experience environment obtains application metadata and static resources from the design state. Compared with the existing technical solution of "full resources in the running state", it reduces the resources synchronized from the design state to the running state, significantly improving the release efficiency;

[0055] Since the resources released to the running state are reduced, for metadata such as "models, scheduled tasks" that need to take effect in the experience environment, the incremental real-time call experience environment interface is used for release, which eliminates the need for manual full release, improves release efficiency, and allows users to experience the release effect in real time in the experience environment.

[0056] like Figure 2 As shown, a device for presetting an experience environment on a low-code platform includes a design state, an experience environment, and an external environment interface;

[0057] Design state refers to the phase of designing applications in a low-code platform. In design state, users visually drag and drop components, define processes, configure services, and integrate data sources to generate application prototypes and logic.

[0058] Among them, the experience environment deploys two modules: a running process and a running instance database;

[0059] In the experience environment, the version association relationship is recorded in the low-code design state. When the application in the design state involves the preset version comparison condition, it is first determined whether the version of the application is consistent with the existing version of the application in the current experience environment. If they are consistent, the real-time publishing interface of the running state is called to publish; if they are inconsistent, it is ignored;

[0060] The external environment interface is used to provide users with an access interface to the design state and experience environment;

[0061] When switching the version of a specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment;

[0062] When users access the design state and experience environment through the external environment interface, they use the same domain name for access and use the environment flag in the URL to distinguish the routes. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes.

[0063] When a user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state background interface.

[0064] The above preset parameters or preset thresholds are all set by those skilled in the art according to actual conditions or obtained through large amounts of data simulation.

[0065] The above embodiments are only used to illustrate the technical method of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical method of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical method of the present invention.

Claims

1. A method for presetting an experience environment on a low-code platform, characterized in that: The following steps are involved: Step 1: Keep the table structure of the low-code metadata consistent in the design state and the running state, and directly connect the running state backend process to the design state database or the environment metadata database; Step 2: Preset a set of experience environments and deploy two modules, the running process and the running instance database, in the experience environment; Step 3: Record the version association relationship in the low-code design state. When the application in the design state involves the preset version comparison condition, first determine whether the application version is consistent with the existing version of the application in the current experience environment. If they are consistent, call the real-time publishing interface in the running state to publish; if not, ignore it; Step 4: When switching the version of the specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment; Step 5: When accessing the design state and experience environment externally, use the same domain name for access and differentiate the routes using the environment flag in the URL. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes. Step 6: When the user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state background interface.

2. A method for presetting an experience environment on a low-code platform according to claim 1, characterized in that: The metadata table structure includes tenant, application, and version identifiers.

3. A method for presetting an experience environment on a low-code platform according to claim 2, characterized in that: The metadata and static resources that the experience environment depends on are obtained from the design state, and in the experience environment, the same application only supports running one version at the same time.

4. A method for presetting an experience environment on a low-code platform according to claim 3, characterized in that: The version association relationship includes the association relationship among applications, versions and experience environments.

5. A method for presetting an experience environment on a low-code platform according to claim 4, characterized in that: The version comparison conditions include runtime instance data of database models, process orchestration, service orchestration, and timer configuration.

6. A method for presetting an experience environment on a low-code platform according to claim 5, characterized in that: The design state calls the switching version interface of the experience environment running state to update the experience environment in the following manner: The running process queries the metadata information of the old version and the new version, compares the metadata information of the old version and the new version, updates the content of the instance database with the new version data, and updates the version information of the current application of the experience environment stored in the design state.

7. A method for presetting an experience environment on a low-code platform according to claim 6, characterized in that: The method of displaying the corresponding interface to the user through the running background interface is: Call the interface of the running background process to obtain metadata and running instance data, and parse them to present on the front-end page.

8. A device for presetting an experience environment on a low-code platform, which is used to implement the method for presetting an experience environment on a low-code platform as described in any one of claims 1 to 7, characterized in that: Including design state, experience environment and external environment interface; Design state refers to the phase of designing applications in a low-code platform. In design state, users visually drag and drop components, define processes, configure services, and integrate data sources to generate application prototypes and logic. The experience environment deploys two modules: a running process and a running instance database; The external environment interface is used to provide users with an access interface for accessing the design state and experience environment.

9. The device for presetting an experience environment on a low-code platform according to claim 8, characterized in that: In the experience environment, the version association relationship is recorded in the low-code design state. When the application in the design state involves the preset version comparison conditions, it is first determined whether the version of the application is consistent with the existing version of the application in the current experience environment. If they are consistent, the real-time publishing interface of the running state is called for publishing; if they are inconsistent, it is ignored.

10. The device for presetting an experience environment on a low-code platform according to claim 9, characterized in that: When switching the version of a specified application in the experience environment, the design state calls the version switching interface of the experience environment running state to update the experience environment; When users access the design state and experience environment through the external environment interface, they use the same domain name for access and use the environment flag in the URL to distinguish the routes. Nginx forwards the routes to different front-end modules in the design state and running state according to the routes. When a user accesses the running state front-end page, the corresponding interface is displayed to the user through the running state background interface.

Images