CN117032777A

CN117032777A - Low-code platform configuration method, device, electronic equipment and readable storage medium

Info

Publication number: CN117032777A
Application number: CN202310932144.XA
Authority: CN
Inventors: 周芷煜; 谢晓军; 黄泽源; 薛龙; 张会炎
Original assignee: China Telecom Technology Innovation Center; China Telecom Corp Ltd
Current assignee: China Telecom Technology Innovation Center; China Telecom Corp Ltd
Priority date: 2023-07-27
Filing date: 2023-07-27
Publication date: 2023-11-10

Abstract

The disclosure provides a low-code platform configuration method, a low-code platform configuration device, electronic equipment and a readable storage medium, and relates to the technical field of computers and Internet. The method is applied to a low-code platform, the low-code platform comprises a first application, the first application is constructed by one or more first components in the low-code platform, the low-code platform comprises a full configuration data table, the full configuration data table is used for carrying out initial configuration on all the components in the low-code platform, and the first application has carried out initial configuration on the low-code platform through the full configuration data table, and the method comprises the steps of: receiving a configuration modification instruction for a first application; caching configuration modification instructions; identifying the configuration of the first component in the first application according to the configuration modification instruction, and determining a first component configuration rule corresponding to the first component in the full configuration rules; the first component configuration modification sub-module may be for configuring the first component in the first application based on the first component configuration rules and via the configuration modification data.

Description

Low-code platform configuration method, device, electronic equipment and readable storage medium

Technical Field

The disclosure relates to the technical field of computers and the internet, and in particular relates to a low-code platform configuration method and device, electronic equipment and a computer readable storage medium.

Background

This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

In the related art, a user can build an application through components in a low code platform. Wherein the application can be normally used only if components in the application built in the low code platform are correctly configured. The configuration method commonly adopted in the related art is to manually write a configuration file, load data in the configuration file for initialization after the application is started, and when configuration is modified, the configuration file is also required to be modified.

In the case of complex application scenarios, a large number of components need configuration data, and a large number of configuration files are corresponding, so that the manual work is heavy and the operators may need to know the configuration flow and the configuration files deeply. Because the users corresponding to the low-code platform may not have enough expertise, too complex configuration procedures are not beneficial to the common users corresponding to the low-code platform.

Disclosure of Invention

The disclosure aims to provide a low-code platform configuration method, a device, an electronic device and a computer readable storage medium, which can facilitate a user to configure an application in a low-code platform.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

The embodiment of the disclosure provides a low-code platform configuration method, which comprises the following steps: receiving a configuration modification instruction for the first application; caching the configuration modification instruction; modifying the configuration of the first component in the first application according to the configuration modification instruction; and after the first application normally operates for a target time period, modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache.

In some embodiments, the configuration modification instruction includes a first component identification and configuration modification data of the first component; the low-code platform further comprises a full-quantity configuration rule, wherein the full-quantity configuration rule comprises component configuration rules corresponding to all components in the low-code platform; wherein modifying the configuration of the first component in the first application according to the configuration modification instruction comprises: determining the first component in the first application according to the first component identification in the configuration modification instruction; determining a first component configuration rule corresponding to the first component in the full configuration rule according to the first component identifier; the configuration of the first component in the first application is modified based on the first component configuration rules and by the configuration modification data.

In some embodiments, the first component includes scene configuration data corresponding to a plurality of scenes, the scene configuration data corresponding to the plurality of scenes including first scene configuration data corresponding to a first scene, the configuration modification instruction further including a first scene identification of the first scene; wherein modifying the configuration of the first component in the first application based on the first component configuration rules and via the configuration modification data comprises: determining that the first component meets a configuration modification condition according to the first component configuration rule; and modifying the first scene configuration data corresponding to the first scene identifier in the first component through the configuration modification data.

In some embodiments, the full configuration data table includes a plurality of component initial configuration data including first component initial configuration data corresponding to a first component; wherein modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache includes: determining the first component initial configuration data corresponding to the first component in the full configuration data table according to the first component identifier; modifying the first component initial-configuration data in the full configuration data table by the configuration modification data in the cache.

In some embodiments, the low code platform further comprises a second application, the second application being one or more second component builds in the low code platform, the second component comprising the first component, the second application not being configured; wherein after modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache, the method further comprises: responding to an initialization configuration instruction for the second application; determining a second component identifier of each second component in the second application; determining second component configuration data corresponding to the second component according to the second component identifier in the full configuration data table; determining a second component configuration rule corresponding to the second component according to the second component identifier in the full configuration rule; each second component in the second application is configured based on the second component configuration rules and via the second component configuration data.

In some embodiments, the method further comprises: acquiring configuration data in the first application according to a period; comparing the configuration data in the first application with the configuration data in the full configuration data table; if the configuration data in the first application is changed, determining that the configuration data in the first application is abnormally changed.

In some embodiments, after modifying the configuration of the first component in the first application according to the configuration modification instruction, the method further comprises: determining that the first application is in error operation; discarding the configuration modification instruction in the cache; restoring the configuration of the first component in the first application to be before modification by the configuration modification instruction.

In some embodiments, the low-code platform further comprises a full-scale configuration rule for representing dependency relationships and constraint relationships between all components in the low-code platform; wherein the method further comprises: acquiring a configuration query instruction; analyzing the configuration rules corresponding to all the components in the full configuration data table to obtain a plurality of component configuration rules; and processing the plurality of component configuration rules according to the full configuration rules to generate a configuration data topological graph, wherein nodes in the configuration data topological graph are configuration data corresponding to each component in the low-code platform.

The embodiment of the disclosure provides a low-code platform configuration device, which comprises: the device comprises a configuration modification instruction receiving module, an instruction cache module, a configuration first modification module and a configuration second modification module.

The configuration modification instruction receiving module is used for receiving a configuration modification instruction aiming at the first application; the instruction cache module may be configured to cache the configuration modification instruction; the configuration first modification module may be configured to modify a configuration of the first component in the first application according to the configuration modification instruction; the configuration second modification module may be configured to modify, according to the configuration modification instruction in the cache, configuration data of the first component in the full configuration data table after the first application normally runs for a target period of time.

The embodiment of the disclosure provides an electronic device, which comprises: a memory and a processor; the memory is used for storing computer program instructions; the processor invokes the computer program instructions stored by the memory to implement the low code platform configuration method of any one of the above.

Embodiments of the present disclosure provide a computer readable storage medium having stored thereon computer program instructions for implementing a low code platform configuration method as described in any one of the above.

Embodiments of the present disclosure propose a computer program product or a computer program comprising computer program instructions stored in a computer-readable storage medium. The computer program instructions are read from a computer readable storage medium and executed by a processor to implement the low code platform configuration method described above.

The low-code platform configuration method, the low-code platform configuration device, the electronic equipment and the computer readable storage medium provided by the embodiment of the disclosure can initially configure the application in the low-code platform through the full configuration data table on one hand; on the other hand, configuration information in the configured application can be modified by receiving a configuration modification instruction given by a user from the outside; in addition, when the application with the modified configuration information normally operates for a period of time, the configuration modification instruction given by the user is used for modifying the full configuration data table, so that the requirements of the user can be met when other applications or components are configured later. In a word, the method can provide basic configuration for the application constructed by the user through the full configuration data table when the user does not have the configuration capability, can allow the user to modify the configuration information of the application in the low-code platform when the user has special configuration requirements, and can timely record the configuration requirements of the user (namely the configuration information modified at the time) through the full configuration data table so that the modified configuration information can be used when the application newly constructed by the user is configured next time, and the requirements of the user can be better met.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.

Fig. 1 shows a schematic view of a scenario of a low code platform configuration method or a low code platform configuration apparatus that may be applied to embodiments of the present disclosure.

FIG. 2 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 3 is a schematic diagram of a full configuration data table, shown according to an example embodiment.

FIG. 4 is a schematic diagram of a full configuration data table, shown in accordance with an exemplary embodiment.

FIG. 5 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 6 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 7 is a flowchart illustrating a low code platform configuration exception determination method, according to an example embodiment.

FIG. 8 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 9 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 10 is a flowchart illustrating a low code platform configuration method according to an example embodiment.

FIG. 11 is a schematic diagram illustrating the architecture of a low code platform configuration data management system, according to an example embodiment.

FIG. 12 is a block diagram illustrating a low code platform configuration device according to an example embodiment.

Fig. 13 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.

One skilled in the art will appreciate that embodiments of the present disclosure may be a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

The described features, structures, or characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. However, those skilled in the art will recognize that the aspects of the present disclosure may be practiced with one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

The drawings are merely schematic illustrations of the present disclosure, in which like reference numerals denote like or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and not necessarily all of the elements or steps are included or performed in the order described. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

In the description of the present disclosure, unless otherwise indicated, "/" means "or" and, for example, a/B may mean a or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more. The terms "first," "second," and the like do not limit the amount and order of execution, and the terms "first," "second," and the like do not necessarily differ; the terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements/components/etc., in addition to the listed elements/components/etc.

In order that the above-recited objects, features and advantages of the present invention can be more clearly understood, a more particular description of the invention will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings, it being understood that embodiments of the present disclosure and features of the embodiments may be combined with each other without departing from the scope of the appended claims.

It should be noted that, in the technical solution of the present disclosure, the related aspects of collecting, updating, analyzing, processing, using, transmitting, storing, etc. of the personal information of the user all conform to the rules of the related laws and regulations, and are used for legal purposes without violating the public order colloquial. Necessary measures are taken for the personal information of the user, illegal access to the personal information data of the user is prevented, and the personal information security and network security of the user are maintained.

The existing configuration method of the low-code platform mainly relies on manual operation on configuration files, which requires operators to know the configuration flow and the configuration files in detail, is unfavorable for common users, and has low operation and maintenance efficiency due to a large amount of manual work when the situations are complex or batch operation is needed.

The patent provides a low-code platform configuration data management system, which is used for uniformly managing configuration data by constructing a configuration rule and a configuration data table, and a user can perform operations such as initialization, modification, inquiry and the like of configuration on a low-code platform by inputting simple instructions, so that the problems that the configuration files are difficult to manage and the node configuration operation is complex are avoided; meanwhile, the probes are introduced into the application, the change of node configuration data is monitored, the data synchronism is ensured, and misoperation or system errors are prevented from affecting the operation of the application.

The following describes example embodiments of the present disclosure in detail with reference to the accompanying drawings.

Referring to fig. 1, a schematic diagram of an implementation environment provided by an exemplary embodiment of the present disclosure is shown.

As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, wearable devices, virtual reality devices, smart homes, etc.

The server 105 may be a server providing various services, such as a background management server providing support for devices operated by users with the terminal devices 101, 102, 103. The background management server can analyze and process the received data such as the request and the like, and feed back the processing result to the terminal equipment.

The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server or the like for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network ), basic cloud computing services such as big data and artificial intelligent platform, and the disclosure is not limited thereto.

The server 105 may, for example, receive a configuration modification instruction for the first application; server 105 may, for example, cache configuration modification instructions; the server 105 may modify the configuration of the first component in the first application, e.g., according to configuration modification instructions; the server 105 may modify the configuration data of the first component in the full configuration data table according to the configuration modification instructions in the cache, for example, after the first application is running normally for the target period of time.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative, and that the server 105 may be a server of one entity, or may be composed of a plurality of servers, and may have any number of terminal devices, networks and servers according to actual needs.

FIG. 2 is a flowchart illustrating a low code platform configuration method according to an example embodiment. The method provided by the embodiments of the present disclosure may be performed by any electronic device having computing processing capability, for example, the method may be performed by a server or a terminal device in the embodiment of fig. 1, or may be performed by both the server and the terminal device, and in the following embodiments, the server is taken as an example to illustrate an execution subject, but the present disclosure is not limited thereto.

In some embodiments, the low code platform configuration method provided in this embodiment may be applied to a low code platform.

In some embodiments, different users may correspond to different low code platforms, which may include different components, which may be the same or different in different low code platforms.

For example, the low code platform of user a may include components a1, a2, a3, a4, … …, etc.; the low code platform of the B user can comprise B1, B2, B3, B4 and … … components and the like; the low code platform of the C user may include components C1, C2, C3, C4 … … and the like,

in some embodiments, the low code platform described above may be used offline.

In some embodiments, each low code platform may correspond to a full configuration data table that may be used to initially configure all of the components in the low code platform. For example, assuming that the low-code platform may include a1, a2, a3, a4, … …, etc., the full-scale data table corresponding to the low-code platform may respectively perform basic configuration on the a1, a2, a3, a4, … …, etc.

In some embodiments, the full configuration data table may be a generic configuration data table provided empirically by a developer of the low code platform at an initial stage. In the use process of the low-code platform, according to a configuration modification instruction input by a user, the configuration data in the configuration data table can be dynamically changed so as to better meet the actual requirements of the user on the low-code platform.

In some embodiments, the full configuration data table may include a plurality of Key (Key) Value (Value) pairs, where Key is a unique identifiable identifier corresponding to a component to be configured, and Value includes configuration data (and a unique identifiable application scenario identifier) corresponding to the component to be configured.

As shown in fig. 3, a plurality of key-value pairs may be included in the full configuration data table, each key-value pair being usable to configure one component. As shown in fig. 3, a key-value pair may include a key, which may be a component identification, and a value, which may be configuration data of a component to which the component identification corresponds.

In some embodiments, one component in the low code platform may correspond to multiple scenarios. For example, for a card punching component, it may correspond to a work-in card punching scene, a work-out card punching scene, or an active card punching scene.

Then a plurality of key-value pairs may be included in the full configuration data table, each key-value pair being usable to configure one component, as shown in fig. 4. As shown in fig. 4, a key-value pair may include a key and a value, where the key may be a component identifier, and the value may include a plurality of scene identifiers and configuration data for each scene identifier, where the component may be configured by the configuration data under the corresponding scene identifier.

As shown in fig. 4, the configuration data of the component identified as the component a may include configuration data corresponding to the scene identified as the scene a and the scene b, so that the configuration data corresponding to the scene a may configure the component a under the scene a, and the configuration data corresponding to the scene b may configure the component a under the scene b, which is not limited in this application.

In some embodiments, the low-code platform may include a first application already built therein, which may be built by one or more first components in the low-code platform.

Referring to fig. 2, the low code platform configuration method provided by the embodiments of the present disclosure may include the following steps.

Step S202, a configuration modification instruction for a first application is received.

In some embodiments, the configuration modification instructions described above may be entered by a user through a low code platform.

In some embodiments, a key-value pair may also be included in the configuration modification instruction, each key-value pair being used to configure a component. The specific contents of the key value pair may refer to those in fig. 4 and 5, and the present application is not limited thereto.

In step S204, the configuration modification instruction is cached.

In some embodiments, the configuration modification instructions may be cached in a device cache.

In some embodiments, the configuration modification instruction may be a modification instruction for some or all of the first components, which is not limited by the present application.

Step S206, the configuration of the first component in the first application is modified according to the configuration modification instruction.

Step S208, after the first application normally operates for the target period of time, the configuration data of the first component in the full configuration data table is modified according to the configuration modification instruction in the cache.

In some embodiments, when the first application is still capable of operating normally for a period of time after the configuration data is modified, indicating that the modification to the configuration data of the first application is correct and usable, the configuration data of the first component in the full configuration data table may be modified according to the configuration modification instruction in the cache, so that the configuration data in the configuration modification instruction input by the user is used continuously next time when the configuration to the first component is required in other applications of the low code platform. It can be understood that the configuration data in the configuration modification instruction is the configuration data which is given by the user aiming at the first component and meets the requirement of the user, and the configuration data is recorded in the full configuration data table, so that when the user builds other applications to use the first component, the user can still use the configuration data which meets the requirement of the user to configure the first component, thereby not only meeting the requirement of the user, but also improving the configuration efficiency when the user builds the application next time.

According to the method, on one hand, the application in the low-code platform can be initially configured through the full configuration data table; on the other hand, configuration information in the configured application can be modified by receiving a configuration modification instruction given by a user from the outside; in addition, when the application with the modified configuration information normally operates for a period of time, the full configuration data table is modified according to the configuration modification instruction given by the user, so that the requirements of the user can be met when other applications or components are configured later. In a word, the method can provide basic configuration for the application constructed by the user through the full configuration data table when the user does not have the configuration capability, can allow the user to modify the configuration information of the application in the low-code platform when the user has special configuration requirements, and can timely record the configuration requirements of the user (namely the configuration information modified at the time) through the full configuration data table so that the modified configuration information can be used when the application newly constructed by the user is configured next time, and the requirements of the user can be better met.

Referring to fig. 5, the low code platform configuration method described above may include the following steps.

In some embodiments, the configuration modification instruction may include a first component identifier of the first component and configuration modification data corresponding to the first component identifier, where the configuration modification data may be used to perform configuration modification on the first component corresponding to the first component identifier.

In some embodiments, the low code platform may also include a full-scale configuration rule, which may include component configuration rules corresponding to all components in the low code platform. The component configuration rule corresponding to each component may include a configuration condition of the component when the component is configured, for example, a dependency relationship, an association relationship, a configuration method, and the like when the component is configured.

Step S502, a configuration modification instruction for a first application is received.

Step S504, the configuration modification instruction is cached.

Step S506, determining a first component in the first application according to the first component identification in the configuration modification instruction.

In some embodiments, the first component identifier in the configuration modification instruction may be one or more, which is not limited by the present application.

In some embodiments, the first component identifier in the configuration modification instruction may be a component identifier of all the first components in the first application, or may be a partial component identifier of all the first components in the first application. That is, the configuration modification instruction may perform configuration modification on all the first components in the first application, or may perform configuration modification on a part of the first components in the first application, which is not limited in the present application.

Step S508, determining a first component configuration rule corresponding to the first component in the full configuration rules according to the first component identification.

In some embodiments, assuming that N components are included in the low code platform, the configuration rules corresponding to the N components may be included in the full configuration rule, where the configuration rule corresponding to each component may be used to configure the component.

Step S510, modifying the configuration of the first component in the first application based on the first component configuration rule and by the configuration modification data.

In some embodiments, the first component in the first application may be configured according to the first component configuration rule using the configuration modification data.

In some embodiments, the first component may include scene configuration data corresponding to a plurality of scenes, and the scene configuration data corresponding to the plurality of scenes may include first scene configuration data corresponding to the first scene and second scene configuration data corresponding to the second scene.

In some embodiments, the configuration modification instruction further includes a first scene identification of the first scene.

In some embodiments, modifying the configuration of the first component in the first application based on the first component configuration rule and by the configuration modification data may include: determining that the first component meets the configuration modification condition according to the first component configuration rule; and modifying the first scene configuration data corresponding to the first scene identifier in the first component through the configuration modification data.

In some embodiments, the full configuration data table may include initial configuration data corresponding to all components in the low code platform, and the full configuration data table may include first component initial configuration data corresponding to the first component.

Step S512, determining first component initial configuration data corresponding to the first component in the full configuration data table according to the first component identification.

Step S514, the first component initial configuration data in the full configuration data table is modified by the configuration modification data in the cache.

By the method, the configuration data of the user aiming at the first component can be recorded in the full configuration data table, so that the first component can be configured according to the configuration data input by the user when the first component is reused next time.

In some embodiments, the low code platform may further include a second application that is built from one or more second components in the low code platform, which may include all or part of the first components, the second application being unconfigured.

In some embodiments, the second application may be configured on a basic basis using the method shown in FIG. 6. In addition, it will be appreciated by those skilled in the art that the first application may be configured with reference to the technical solution shown in fig. 6, which is not limited by the present application.

Referring to fig. 6, the above-described low code platform configuration method may include the following steps.

Step S602, in response to an initialization configuration instruction for the second application.

Step S604, determining a second component identifier of each second component in the second application.

Step S606, determining second component configuration data corresponding to the second component according to the second component identification in the full configuration data table.

Step S608, determining a second component configuration rule corresponding to the second component according to the second component identifier in the full configuration rule.

In step S610, each second component in the second application is configured based on the second component configuration rule and by the second component configuration data, respectively.

The method can use the full configuration data in the low-code platform to carry out basic configuration on the second application without configuration by a user, so that the low-code platform is used more simply and edited; on the other hand, the historical configuration data of the first component aiming at the user can be used for configuring the first component, so that the configuration information of the first component meets the requirements of the user, and the user experience is improved.

Referring to fig. 7, the low code platform configuration anomaly determination method described above may include the following steps.

In step S702, configuration data in the first application is acquired according to the period.

In some embodiments, the configuration data in the first application may be obtained by the probe according to a preset period, for example, the configuration data corresponding to each component in the first application may be obtained according to the preset period.

Step S704, comparing the configuration data in the first application with the configuration data in the full configuration data table.

In some embodiments, the obtained configuration data corresponding to each component may be compared with the configuration data of each component in the full data table, so as to determine whether the configuration data of each component in the first application is abnormal.

In step S706, if the configuration data in the first application changes, it is determined that the configuration data in the first application changes abnormally.

In some embodiments, after determining that the first application is abnormal, it may be further determined which components in the first application are abnormal for subsequent operation and maintenance.

In some embodiments, after determining that the configuration data of some components in the first application are abnormal, the configuration data of the abnormal components may be restored to a default configuration (i.e., a configuration provided by a low code platform developer).

Referring to fig. 8, the above-described low code platform configuration method may include the following steps.

Step S802, a configuration modification instruction for a first application is received.

In step S804, the configuration modification instruction is cached.

Step S806, modifying the configuration of the first component in the first application according to the configuration modification instruction.

Step S808, controlling the first application running target period.

Step 810, judging whether the first application operates normally in the target time period.

If the first application is operating normally within the target period, step S812 is performed.

In step S812, the configuration data of the first component in the full configuration data table is modified according to the configuration modification instruction in the cache.

If the first application is running in error within the target period, steps S814 to S816 are performed.

In step S814, the configuration modification instruction in the cache is discarded.

Step S816, restore the configuration of the first component in the first application to before modification by the configuration modification instruction.

By the method, on one hand, whether the configuration data in the configuration modification instruction can be normally used can be judged by running the first application for a period of time, and if so, the configuration data given by a user for the first component in the first application is recorded in a full configuration data table so that the configuration data given by the user can be used when the first component in other applications is configured next time; on the other hand, when the first application cannot normally run, the configuration data in the configuration modification instruction is proved to be wrong and cannot be used, and the configuration of the first component in the first application is restored to be before the first component is modified by the configuration modification instruction, so that the first application can normally use the configuration data.

Referring to fig. 9, the above-described low code platform configuration method may include the following steps.

In some embodiments, the low-code platform may also include a full-scale configuration rule that is used to represent dependencies and constraint relationships between all components in the low-code platform.

Step S902, a configuration query instruction is obtained.

Step S904, analyzing the configuration rules corresponding to each component in the full configuration data table to obtain a plurality of component configuration rules.

Step S906, processing the plurality of component configuration rules according to the full configuration rules to generate a configuration data topological graph, wherein nodes in the configuration data topological graph are configuration data corresponding to each component in the low code platform.

In some embodiments, the data topology may be presented to a user for modification and operation of the configuration data of the first application by the user.

The technical solution provided in the foregoing embodiment may specifically include a process shown in fig. 10, where, as shown in fig. 10, the probe may perform periodic detection on configuration data in a first application in the low code platform, so as to read and compare current configuration data of the low code platform with full configuration data; if the data acquired by the probe is consistent with the full configuration data, continuing to operate the first application, and if the data acquired by the probe is inconsistent with the full configuration data, sending a prompt to modify or store as new configuration data.

FIG. 11 is a schematic diagram illustrating the architecture of a low code platform configuration data management system, according to an example embodiment. The configuration data is uniformly managed by constructing the configuration rules and the configuration data table, and a user can perform operations such as initialization, modification, inquiry and the like of configuration on the low-code platform or the application generated in the low-code platform by inputting simple instructions, so that the problems that the configuration files are difficult to manage and the node configuration operation is complex are avoided; meanwhile, the probes are introduced into the application, the change of node configuration data is monitored, the data synchronism is ensured, and misoperation or system errors are prevented from affecting the operation of the application.

The corresponding low-code platform configuration data management method in the low-code platform configuration data management system can comprise the following contents:

1. configuration rules: constructing a configuration rule according to the association and sequence of the configuration nodes required by the application; the flow model includes a full configuration rule and a node configuration rule. The full configuration rule corresponds to the application configuration overall flow, and the node configuration rule corresponds to each node which can be configured in a split mode. The configuration rules include an identification that identifies each node. The rules described above may be provided by a low code platform developer.

2. Configuration data table: and storing all configuration data required by a user in a database in the form of Key Value pairs, wherein Key is a unique identifiable identifier of a node to be configured, and Value comprises a Value configured by the node and the unique identifiable application scene identifier. The configuration data table described above may be provided by a low code platform developer.

3. Caching a data table: the cache data table stores the configuration data to be modified, the application automatically or manually updates the data in the configuration data table by using the cache configuration table data after finishing the configuration updating and stable operation, and if the application fails, the cache configuration table data is automatically discarded and the configuration data is restored.

4. And (3) probe: the probe is used for monitoring node configuration data, and the node configuration data is manually triggered by one key or automatically periodically read, and is compared with a configuration data table, so that the consistency of the data is ensured, and configuration data errors caused by misoperation or system errors are avoided.

5. The user inputs a simple configuration instruction through the interface, and the automation script reads the configuration data table and loads the configuration rule to perform corresponding operation according to the instruction.

In some embodiments, when an application in a low code platform is built, the application may be configured based on the full-scale data table and the full-scale configuration rules in the low code platform, and then the configuration in the application may be modified using the following method.

a) Configuration data: the automation script acquires a configuration rule (full quantity or node) to be configured according to the instruction, reads corresponding data of the cache data table, and completes configuration operation according to the model flow;

b) Modifying data: the automation script stores the modification data into a cache data table, acquires a flow needing modification from the instruction to complete modification, and normally operates manually or automatically (sets a time threshold) to modify the configuration data table by using the value of the cache data table after the modification is applied, and automatically discards the value of the cache data table and restores the original configuration value if the operation is wrong;

c) Querying data: the automation script reads the corresponding value from the configuration data table according to the instruction, and can generate the configuration data topological graph corresponding to the flow according to the configuration rule, so that the user can conveniently know the application configuration details

The technical scheme provided by the embodiment has the following advantages: 1. the configuration data can be operated through simple instruction input, and a specific configuration flow is not required to be known; 2. the configuration files of different scenes of different nodes are managed in a unified way, and the configuration details are known without looking up the different configuration files; 3. the synchronicity of the configuration data may be automatically detected.

It should be noted that, in the embodiments of the low-code platform configuration method, the steps may be intersected, replaced, added, and subtracted. Therefore, these rational permutation and combination transformation and low code platform configuration methods should also fall within the protection scope of the present disclosure, and should not limit the protection scope of the present disclosure to the embodiments.

Based on the same inventive concept, the embodiments of the present disclosure also provide a low code platform configuration device, such as the following embodiments. Since the principle of solving the problem of the embodiment of the device is similar to that of the embodiment of the method, the implementation of the embodiment of the device can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

FIG. 12 is a block diagram illustrating a low code platform configuration device according to an example embodiment. Referring to fig. 12, a low code platform configuration apparatus 1200 provided by an embodiment of the present disclosure may include: a configuration modification instruction receiving module 1201, an instruction cache module 1202, a configuration first modification module 1203 and a configuration second modification module 1204.

Wherein, the configuration modification instruction receiving module 1201 may be configured to receive a configuration modification instruction for a first application; instruction cache module 1202 may be configured to cache configuration modification instructions; the configuration first modification module 1203 may be configured to modify the configuration of the first component in the first application according to the configuration modification instruction; the configuration second modification module 1204 may be configured to modify, after the first application normally operates for the target period of time, configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache.

It should be noted that, the configuration modification instruction receiving module 1201, the instruction cache module 1202, the configuration first modification module 1203, and the configuration second modification module 1204 correspond to S202 to S208 in the method embodiment, and the above modules are the same as examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the method embodiment. It should be noted that the modules described above may be implemented as part of an apparatus in a computer system, such as a set of computer-executable instructions.

In some embodiments, the configuration modification instruction includes first component identification and configuration modification data for the first component; the low code platform also comprises a full configuration rule, wherein the full configuration rule comprises component configuration rules corresponding to all components in the low code platform; wherein configuring the first modification module 1203 may include: the first component determination sub-module, the first component configuration rule determination sub-module, and the first component configuration modification sub-module.

Wherein the first component determination submodule may be configured to determine the first component in the first application according to the first component identification in the configuration modification instruction; the first component configuration rule determining submodule may be configured to determine a first component configuration rule corresponding to the first component in the full configuration rule according to the first component identifier; the first component configuration modification sub-module may be configured to modify a configuration of the first component in the first application based on the first component configuration rules and through the configuration modification data.

In some embodiments, the first component includes scene configuration data corresponding to a plurality of scenes, the scene configuration data corresponding to the plurality of scenes includes first scene configuration data corresponding to the first scene, and the configuration modification instruction further includes a first scene identifier of the first scene; wherein the first component configuration modification sub-module may include: a rule judging unit and a scene configuration data modifying unit.

The rule judging unit may be configured to determine, according to a first component configuration rule, that the first component satisfies a configuration modification condition; the scene configuration data modification unit may be configured to modify, by configuring modification data, first scene configuration data corresponding to a first scene identifier in the first component.

In some embodiments, the full configuration data table includes a plurality of component initial configuration data including first component initial configuration data corresponding to the first component; wherein configuring the second modification module 1204 may include: the first component initial-configuration data determination sub-module and the first component initial-configuration data modification sub-module.

The first component initial configuration data determining submodule can be used for determining first component initial configuration data corresponding to the first component in a full configuration data table according to the first component identification; the first component initial-configuration data modification sub-module may be configured to modify the first component initial-configuration data in the full configuration data table by the configuration modification data in the cache.

In some embodiments, the low code platform further comprises a second application, the second application being built from one or more second components in the low code platform, the second components comprising the first components, the second application being unconfigured; wherein the low code platform configuration device further comprises: the system comprises an initialization configuration instruction response module, a second component identification determining module, a second component configuration data determining module, a second component configuration rule determining module and a second application initial configuration module.

The initialization configuration instruction response module may be configured to respond to an initialization configuration instruction for a second application after modifying configuration data of a first component in the full configuration data table according to a configuration modification instruction in the cache; the second component identification determination module may be configured to determine a second component identification of each second component in the second application; the second component configuration data determining module may be configured to determine second component configuration data corresponding to the second component in the full configuration data table according to the second component identifier; the second component configuration rule determining module may be configured to determine, according to the second component identifier, a second component configuration rule corresponding to the second component in the full configuration rule; the second application initial configuration module may be configured to configure each second component in the second application based on the second component configuration rules and via the second component configuration data.

In some embodiments, the low code platform configuration device may further comprise: the device comprises a period acquisition data module, a data comparison module and an abnormality determination module.

The period acquisition data module can be used for acquiring configuration data in the first application according to the period; the data comparison module can be used for comparing the configuration data in the first application with the configuration data in the full configuration data table; the anomaly determination module may be configured to determine that the configuration data in the first application has changed abnormally if the configuration data in the first application has changed.

In some embodiments, the low code platform configuration device may include: an error determining module, a discarding module and a recovering module.

The error determining module may be configured to determine that the first application is in error operation after modifying the configuration of the first component in the first application according to the configuration modification instruction; the discarding module may be configured to discard the configuration modification instruction in the cache; the restoration module may be configured to restore the configuration of the first component in the first application to before modification by the configuration modification instruction.

In some embodiments, the low code platform further comprises a full configuration rule for representing dependencies and constraint relationships between all components in the low code platform; wherein, the low code platform configuration device may further include: query instruction acquisition module, analysis module and topological graph generation module.

The query instruction acquisition module can be used for acquiring configuration query instructions; the analysis module can be used for analyzing the configuration rules corresponding to each component in the full configuration data table to obtain a plurality of component configuration rules; the topology graph generation module may be configured to process the plurality of component configuration rules according to the full configuration rules to generate a configuration data topology graph, wherein nodes in the configuration data topology graph are configuration data corresponding to respective components in the low code platform.

Since the functions of the apparatus 1200 are described in detail in the corresponding method embodiments, the disclosure is not repeated herein.

The modules and/or sub-modules and/or units referred to in the embodiments of the present disclosure may be implemented in software or hardware. The described modules and/or sub-modules and/or units may also be provided in a processor. Wherein the names of the modules and/or sub-modules and/or units do not in some cases constitute a limitation of the module and/or sub-modules and/or units themselves.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module or portion of a program that comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer program instructions.

Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.

Fig. 13 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure. It should be noted that the electronic device 1300 shown in fig. 13 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present disclosure.

As shown in fig. 13, the electronic apparatus 1300 includes a Central Processing Unit (CPU) 1301, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1302 or a program loaded from a storage portion 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation of the electronic apparatus 1300 are also stored. The CPU 1301, ROM 1302, and RAM 1303 are connected to each other through a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input section 1306 including a keyboard, a mouse, and the like; an output portion 1307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 1308 including a hard disk or the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs a communication process via a network such as the internet. The drive 1310 is also connected to the I/O interface 1305 as needed. Removable media 1311, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is mounted on drive 1310 as needed so that a computer program read therefrom is mounted into storage portion 1308 as needed.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising computer program instructions for performing the method shown in the flowchart. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1309 and/or installed from the removable medium 1311. The above-described functions defined in the system of the present disclosure are performed when the computer program is executed by a Central Processing Unit (CPU) 1301.

It should be noted that the computer readable storage medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable computer program instructions embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Computer program instructions embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

As another aspect, the present disclosure also provides a computer-readable storage medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer-readable storage medium carries one or more programs which, when executed by a device, cause the device to perform functions including: receiving a configuration modification instruction for a first application; caching configuration modification instructions; modifying the configuration of the first component in the first application according to the configuration modification instruction; and after the first application normally operates for the target time period, modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache.

According to one aspect of the present disclosure, there is provided a computer program product or computer program comprising computer program instructions stored in a computer readable storage medium. The computer program instructions are read from a computer-readable storage medium and executed by a processor to implement the methods provided in the various alternative implementations of the above embodiments.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solutions of the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.), and include several computer program instructions for causing an electronic device (may be a server or a terminal device, etc.) to perform a method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the disclosure is not to be limited to the details of construction, the manner of drawing, or the manner of implementation, which has been set forth herein, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A low code platform configuration method, which is characterized by being applied to a low code platform, wherein the low code platform comprises a first application, the first application is constructed by one or more first components in the low code platform, the low code platform comprises a full configuration data table, the full configuration data table is used for carrying out initial configuration on all components in the low code platform, and the first application is initially configured through the full configuration data table; wherein the method comprises the following steps:

receiving a configuration modification instruction for the first application;

caching the configuration modification instruction;

modifying the configuration of the first component in the first application according to the configuration modification instruction;

and after the first application normally operates for a target time period, modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache.

2. The method of claim 1, wherein the configuration modification instruction includes first component identification and configuration modification data for the first component; the low-code platform further comprises a full-quantity configuration rule, wherein the full-quantity configuration rule comprises component configuration rules corresponding to all components in the low-code platform; wherein modifying the configuration of the first component in the first application according to the configuration modification instruction comprises:

Determining the first component in the first application according to the first component identification in the configuration modification instruction;

determining a first component configuration rule corresponding to the first component in the full configuration rule according to the first component identifier;

the configuration of the first component in the first application is modified based on the first component configuration rules and by the configuration modification data.

3. The method of claim 2, wherein the first component comprises scene configuration data corresponding to a plurality of scenes, the scene configuration data corresponding to the plurality of scenes comprising first scene configuration data corresponding to a first scene, the configuration modification instruction further comprising a first scene identification of the first scene; wherein modifying the configuration of the first component in the first application based on the first component configuration rules and via the configuration modification data comprises:

determining that the first component meets a configuration modification condition according to the first component configuration rule;

and modifying the first scene configuration data corresponding to the first scene identifier in the first component through the configuration modification data.

4. The method of claim 2, wherein the full configuration data table includes a plurality of component initial configuration data including first component initial configuration data corresponding to a first component; wherein modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache includes:

determining the first component initial configuration data corresponding to the first component in the full configuration data table according to the first component identifier;

modifying the first component initial-configuration data in the full configuration data table by the configuration modification data in the cache.

5. The method of claim 2, wherein the low code platform further comprises a second application, the second application being one or more second component constructs in the low code platform, the second component comprising the first component, the second application not being configured; wherein after modifying the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache, the method further comprises:

Responding to an initialization configuration instruction for the second application;

determining a second component identifier of each second component in the second application;

determining second component configuration data corresponding to the second component according to the second component identifier in the full configuration data table;

determining a second component configuration rule corresponding to the second component according to the second component identifier in the full configuration rule;

each second component in the second application is configured based on the second component configuration rules and via the second component configuration data.

6. The method according to claim 1, wherein the method further comprises:

acquiring configuration data in the first application according to a period;

comparing the configuration data in the first application with the configuration data in the full configuration data table;

if the configuration data in the first application is changed, determining that the configuration data in the first application is abnormally changed.

7. The method of claim 1, wherein after modifying the configuration of the first component in the first application according to the configuration modification instruction, the method further comprises:

Determining that the first application is in error operation;

discarding the configuration modification instruction in the cache;

restoring the configuration of the first component in the first application to be before modification by the configuration modification instruction.

8. The method of claim 1, wherein the low code platform further comprises a full configuration rule for representing dependencies and constraints between all components in the low code platform; wherein the method further comprises:

acquiring a configuration query instruction;

analyzing the configuration rules corresponding to all the components in the full configuration data table to obtain a plurality of component configuration rules;

and processing the plurality of component configuration rules according to the full configuration rules to generate a configuration data topological graph, wherein nodes in the configuration data topological graph are configuration data corresponding to each component in the low-code platform.

9. A low code platform configuration device, characterized by being applied to a low code platform, wherein the low code platform comprises a first application, the first application is constructed by one or more first components in the low code platform, the low code platform comprises a full configuration data table, the full configuration data table is used for carrying out initial configuration on all components in the low code platform, and the first application has been initially configured through the full configuration data table comprises:

A configuration modification instruction receiving module, configured to receive a configuration modification instruction for the first application;

the instruction caching module is used for caching the configuration modification instruction;

a configuration first modification module, configured to modify a configuration of the first component in the first application according to the configuration modification instruction;

and the second modification module is configured to modify the configuration data of the first component in the full configuration data table according to the configuration modification instruction in the cache after the first application normally operates for a target period of time.

10. An electronic device, comprising:

a memory and a processor;

the memory is used for storing computer program instructions; the processor invoking the computer program instructions stored in the memory for implementing the low code platform configuration method of any of claims 1-8.

11. A computer readable storage medium having stored thereon computer program instructions, which when executed by a processor, implement the low code platform configuration method according to any of claims 1-8.