CN117785164A

CN117785164A - Method for generating service interface for low-code platform and related device

Info

Publication number: CN117785164A
Application number: CN202311744575.XA
Authority: CN
Inventors: 骈瑞杰
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2023-12-18
Filing date: 2023-12-18
Publication date: 2024-03-29

Abstract

The disclosure provides a method and a related device for generating a service interface for a low-code platform, and relates to the technical fields of low-code platforms, interface development, data processing and artificial intelligence. One embodiment of the method comprises the following steps: in response to receiving a service interface generation request sent by a user, presenting the user with a set of nodes for configuring a table operation for a pre-configured data table including at least one of an add table, a read table, an update table, and a delete table operation performed for the data table; configuring corresponding target table operation for the target node based on the operation configuration instruction received for the target node; generating an operation sequence based on the configured target table operation of all target nodes in response to receiving the configuration completion instruction; and encapsulating the operation sequence and generating a service interface for executing the operation sequence. According to the implementation mode, the difficulty of generating the service interface for the low-code platform can be reduced, and the efficiency of generating the service interface for the low-code platform can be improved.

Description

Method for generating service interface for low-code platform and related device

Technical Field

The present disclosure relates to the field of computer technology, and in particular, to the field of low-code platforms, interface development, data processing, and other artificial intelligence technologies, and more particularly, to a method, an apparatus, an electronic device, a computer readable storage medium, and a computer program product for generating a service interface for a low-code platform.

Background

Software development is the process of building a software system or software parts of a system according to user requirements. Software development is a system project that includes demand capture, demand analysis, design, implementation, and testing.

In order to simplify the development difficulty of software and codes and reduce the requirements for code developers, low-code development technologies are developed. In the low code development technology, the relation between the code modules and the code blocks and the low code language and the simple operation can be preconfigured, so that a user can call the corresponding code modules and the code blocks by utilizing the low code language and the simple operation to rapidly configure codes and generate service interfaces such as application programming interfaces (Application Programming Interface, abbreviated as API). In this context, how to further help users to improve coding efficiency of service interfaces and reduce coding difficulty is worth focusing and urgent need.

Disclosure of Invention

The embodiment of the disclosure provides a method, a device, electronic equipment, a computer readable storage medium and a computer program product for generating a business interface for a low-code platform.

In a first aspect, an embodiment of the present disclosure provides a method for generating a service interface for a low-code platform, including: in response to receiving a service interface generation request sent by a user, presenting a set of nodes for the user, wherein the nodes in the set of nodes are used for configuring table operations for at least part of a pre-configured set of data tables, and the table operations comprise at least one of table adding operation, table reading operation, table updating operation and table deleting operation which are executed for at least one data table in the set of data tables; configuring corresponding target table operations for the at least one target node based on the operation configuration instruction received for the at least one target node; generating an operation sequence based on the configured target table operation of all target nodes in response to receiving the configuration completion instruction; and encapsulating the operation sequence and generating a service interface for executing the operation sequence.

In a second aspect, an embodiment of the present disclosure provides a device for generating a service interface for a low-code platform, including: a node presenting unit configured to present a set of nodes for a user in response to receiving a service interface generation request sent by the user, wherein the nodes in the set of nodes are configured to perform table operations for at least part of a data table in a pre-configured set of data tables, the table operations including at least one of an add table operation, a read table operation, an update table operation, and a delete table operation performed for at least one data table in the set of data tables; an operation configuration unit configured to configure a corresponding target table operation for at least one target node based on an operation configuration instruction received for the at least one target node; a sequence generating unit configured to generate an operation sequence based on target table operations in which all target nodes are configured, in response to receiving a configuration completion instruction; and the interface generating unit is configured to package the operation sequence and generate a service interface for executing the operation sequence.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to implement a method of generating a business interface for a low code platform as described in any one of the implementations of the first aspect when executed.

In a fourth aspect, embodiments of the present disclosure provide a non-transitory computer-readable storage medium storing computer instructions for enabling a computer to implement a method of generating a business interface for a low-code platform as described in any one of the implementations of the first aspect when executed.

In a fifth aspect, embodiments of the present disclosure provide a computer program product comprising a computer program which, when executed by a processor, is capable of implementing a method of generating a business interface for a low code platform as described in any of the implementations of the first aspect.

The embodiment of the disclosure provides a method, a device, an electronic device, a computer readable storage medium and a computer program product for generating a service interface for a low-code platform, wherein in response to receiving a service interface generation request sent by a user, a group of nodes are presented for the user, wherein the nodes in the group of nodes are used for configuring a table operation for at least part of a data table in a preconfigured group of data tables, and the table operation comprises at least one of adding table operation, reading table operation, updating table operation and deleting table operation executed for at least one data table in the group of data tables; configuring corresponding target table operations for the at least one target node based on the operation configuration instruction received for the at least one target node; generating an operation sequence based on the configured target table operation of all target nodes in response to receiving the configuration completion instruction; and encapsulating the operation sequence and generating a service interface for executing the operation sequence.

The user can build the operation sequence based on the mode of selecting the node and operating the node configuration table, and obtain the service interface based on the encapsulation result of the operation sequence. In this way, when editing the service interface, the user can instruct linkage and continuously realize a series of table operations based on the mode of concatenating the code modules and the code actions, and the service interface comprising complex and multi-step execution steps can be realized simply and conveniently. Therefore, the difficulty of generating the service interface for the low-code platform can be reduced, and the efficiency of generating the service interface for the low-code platform can be improved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

Other features, objects and advantages of the present disclosure will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings:

FIG. 1 is an exemplary system architecture in which the present disclosure may be applied;

FIG. 2 is a flowchart of a method for generating a business interface for a low code platform according to an embodiment of the present disclosure;

FIG. 3 is a flow chart of a process for configuring a linked list operation provided by an embodiment of the present disclosure;

fig. 4 is a flowchart of a method for generating a service interface for a low-code platform under an application scenario according to an embodiment of the present disclosure;

fig. 5 is a block diagram of a device for generating a service interface for a low-code platform according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device adapted to perform a method for generating a service interface for a low-code platform according to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other.

In addition, in the technical scheme related to the disclosure, the processes of acquiring, storing, using, processing, transporting, providing, disclosing and the like of related user personal information (such as a data sheet related to later in the disclosure) all conform to the regulations of related laws and regulations and do not violate the popular public order.

FIG. 1 illustrates an exemplary system architecture 100 of an embodiment of a method, apparatus, electronic device, and computer-readable storage medium for generating a business interface for a low code platform to which the present disclosure may be applied.

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.

A user (not shown in the figure) 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. Various applications for implementing information communication between the terminal devices 101, 102, 103 and the server 105, such as a service interface generation type application, a code development type application, an instant messaging type application, and the like, may be installed on the terminal devices.

The terminal devices 101, 102, 103 and the server 105 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smartphones, tablets, laptop and desktop computers, etc.; when the terminal devices 101, 102, 103 are software, they may be installed in the above-listed electronic devices, which may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not particularly limited herein. When the server 105 is hardware, it may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server; when the server is software, the server may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not particularly limited herein.

The server 105 may provide various services through various built-in applications, and may provide, for example, a service interface generation class application for executing an addition table, a reading table, an update table, and a deletion table on a data table, and the server 105 may achieve the following effects when running the service interface generation class application: firstly, receiving a generation request of a service interface sent by a user from terminal equipment 101, 102, 103 through a network 104, and providing a group of nodes for the user through the terminal equipment 101, 102, 103, wherein the nodes in the group of nodes are used for configuring a table operation for at least part of a data table in a preconfigured group of data tables, and the table operation comprises at least one of an adding table operation, a reading table operation, a table updating operation and a table deleting operation which are executed for at least one data table in the group of data tables; then, the server 105 configures a corresponding target table operation for the at least one target node based on the operation configuration instruction received for the at least one target node; then, in response to receiving the configuration completion instruction, the server 105 generates an operation sequence based on the target table operations in which all the target nodes are configured; finally, the server 105 encapsulates the sequence of operations, generating a traffic interface for executing the sequence of operations.

Because storing the data table and packaging the operation sequence may occupy more operation resources and stronger operation capability, the method for generating the service interface for the low-code platform provided in the subsequent embodiments of the present disclosure is generally executed by the server 105 having stronger operation capability and more operation resources, and correspondingly, the device for generating the service interface for the low-code platform is also generally disposed in the server 105. However, it should be noted that, when the terminal devices 101, 102, 103 also have the required computing capability and computing resources, the terminal devices 101, 102, 103 may also complete each operation performed by the server 105 through the service interface generation class application installed thereon, and further output the same result as the server 105. Especially in the case that there are multiple terminal devices with different computing capabilities at the same time, but when the terminal device where the service interface generation class application determines that the terminal device has a stronger computing capability and more computing resources remain, the terminal device can execute the above computation, so as to properly reduce the computing pressure of the server 105, and correspondingly, the device for generating the service interface for the low-code platform can also be set in the terminal devices 101, 102 and 103. In this case, the exemplary system architecture 100 may also not include the server 105 and the network 104. For example, the terminal devices 101, 102, 103 may provide a set of nodes to the user upon user request, interaction with the user, and enable the user to generate a service interface locally at the terminal devices 101, 102, 103.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring to fig. 2, fig. 2 is a flowchart of a method for generating a service interface for a low-code platform according to an embodiment of the disclosure, where the flowchart 200 includes the following steps:

step 201: responding to a service interface generation request sent by a user, and presenting a group of nodes for the user;

this step is intended to be performed by the execution body of the method of generating a business interface for a low code platform (e.g. server 105 shown in fig. 1), presenting a set of nodes in response to receiving a business interface generation request sent by a user. For example, in the case where a user communicates with the server 105 via the terminal device 101, 102, 103, and sends an interface request, the executing entity may be presentation material (or presentation data) of the terminal device 101, 102, 103 associated with a set of nodes, such that the terminal device 101, 102, 103 may generate a visual interface using the presentation material and present the set of nodes to the user using the visual interface. In some embodiments, when the terminal device 101, 102, 103 is the subject of execution of a method of generating a business interface for a low code oriented platform, for example, the terminal device 101, 102, 103 may likewise generate, combine, based on pre-configured material data, a set of nodes for presentation to a user based on a similar manner, and the description will not be repeated here.

In the embodiment of the disclosure, after receiving the service interface generation request sent by the user, the execution body may locally generate an initial service interface, set a request path and a name for the initial service interface, and present and provide a set of nodes for configuring execution codes for the initial service interface for the user. The user can configure and combine corresponding codes (code groups and code modules) for the initial service interface through interaction with the node and configuration operation for the node, so as to obtain a complete service interface.

In general, different rows and columns (or cells) may be used to record different information in the data table, and accordingly, the contents of each portion may be marked in the data table by a field. Thus, the execution subject and the user can locate and indicate the content included in the data table based on the field. A set of data tables, or data tables, may be provided in advance by a user, or may be provided in advance by, for example, a maintainer of an execution subject (e.g., a maintainer of a code development platform). For example, the user may communicate with the executing body and upload a set of data tables when sending a service interface generation request, or before sending a service interface generation request.

In other words, the data table may be obtained directly from a local storage device by the execution body, or may be obtained from a non-local storage device (for example, the terminal devices 101, 102, 103 shown in fig. 1). The local storage device may be a data storage module, such as a server hard disk, provided in the execution body, in which case the data table may be read quickly locally; the non-local storage device may also be any other electronic device arranged to store data, such as some user terminal or the like, in which case the executing entity may obtain the desired data table by communication with the electronic device (e.g. based on an acquisition command).

In an embodiment of the present disclosure, a node in a set of nodes is configured to configure a table operation for at least a portion of a data table in a preconfigured set of data tables, the table operation including at least one of an add table operation (i.e., adding a new data table to be selected), a read table operation (i.e., obtaining a data table indicated by a user), an update table operation (i.e., updating a corresponding content in the data table indicated by the user based on an update content indicated by the user), and a delete table operation (i.e., deleting the data table indicated by the user) performed for at least one data table in the set of data tables. In some scenarios, add table operations, read table operations, update table operations, and delete table operations may also be collectively referred to as add-drop-and-rebuild operations (CRUDs).

It should be appreciated that the associated data table in each node may be one or more, i.e., the operations in each node may be performed or validated against one or more different data tables at the same time. For example, node a may be configured to add an add table operation of data table a, while node B may be configured to update table operations that modify fields in data table B and data table C that belong to the same content. For example, in the case where the number of nail objects is recorded in both data table B and data table C, the update table operation in node B based on the configured number of nail object modifying objects may indicate that the number of nail objects recorded in data table C needs to be updated at the same time.

In embodiments of the present disclosure, the execution body may present a predetermined number of nodes to the user in advance (e.g., one value determined based on historical statistics of the number of nodes actually used by the user). In addition, the mode of adding the control can be configured by the user, so that when the node is insufficient to meet the use requirement, the user can adjust the number of the nodes by triggering the mode of adding the control to the node so as to meet the actual use requirement of the user. Therefore, the problem that the presentation effect is poor due to the fact that too many nodes are provided for the user (for example, icons are too small due to the fact that the number of the nodes is too large and the user is inconvenient to click) is avoided, and the use experience of the user is improved.

Step 202: configuring corresponding target table operations for the at least one target node based on the operation configuration instruction received for the at least one target node;

on the basis of step 201, this step aims at configuring, by the above-mentioned execution body, a corresponding target table operation for the target node according to the operation configuration instruction received for the target node. For example, after receiving a set of nodes, a user may select one or more target nodes based on the needs and configure corresponding target table operations for the target nodes, respectively. For example, a group of nodes may include nodes a through c, and a user may indicate that the user wishes to configure a corresponding target table operation for a target node by, for example, clicking on the node, sending a configuration operation command language for the node. For example, the user may configure the add data table a for node a, the update the number of the nail objects recorded in both the data table and the data table C (e.g., both to Y) for node b, and the delete data table D for node C. It should be appreciated that when there are more than two nodes in a group of nodes, the user may configure the target table operation for only some of the nodes according to the need, thereby facilitating the user to more flexibly configure the number of steps that need to be performed. For example, in the above example, even if the execution body provides the user with the nodes a to c, the user may select to configure only the target table operation at the nodes a and b, and not the target table operation at the node c.

As described above, after the user actually configures, or is configured with, the node of the target table operation, its form may be understood as "at least one of adding a table operation, reading a table operation, updating a table operation, and deleting a table operation" is performed on one or more data tables indicated by the user at the node.

Further, after completing the desired target table operation configuration, the user may interact with the execution subject by, for example, triggering a completion control, sending a completion message, or the like, to instruct the execution subject to perform a subsequent operation.

Further, for ease of understanding, the determination of the target table operation based on the operation configuration instruction, and the specific manner of execution of the table operation, will be described in detail below.

Step 203: generating an operation sequence based on the configured target table operation of all target nodes in response to receiving the configuration completion instruction;

on the basis of step 202, this step is intended to be responded to by the executing body described above in the event that it is determined that the user has completed configuring the target table operation for the node. For example, the execution body may respond upon receiving a configuration completion instruction sent by the user (e.g., the configuration completion instruction may be an instruction sent by the user through a trigger completion control). Further, the executing body may obtain all target nodes for which the user is configured with the target table operation. Further, the execution body may integrate the target nodes and the target table operations corresponding to the target nodes into one operation sequence. In some embodiments, the execution body may determine an operation sequence of the target table operation associated with each target node based on a time sequence in which the target node is configured with the target table operation, to obtain the operation sequence.

In some optional line-of-sight manners of this embodiment, the execution body may also configure the operation logic between the nodes, so that the user may configure the actions accordingly according to the operation logic between the nodes. For example, the order in which operations are performed may be associated among the various nodes in a presented set of nodes. For example, in a group of nodes a to c, the execution order may be to sequentially execute the target table operations corresponding to each of the nodes a, b, and c. Thus, the execution body may select an operation execution order corresponding to each node in the set of nodes when presenting the set of nodes, and sequentially present each node. For example, the execution body may sequentially present the respective nodes with an indication arrow for indicating the execution order, an addition of an execution order label, or the like, so that the user understands the execution order between the nodes. In some embodiments, the executing entity may also present node b to node a by presenting the nodes in turn, e.g., after the user configures the target table operation for it. Thus, based on a set of nodes presented sequentially, a user can configure the execution order, logic between the various nodes according to needs to meet their different configuration needs.

In some embodiments, the execution body allows for adjustment of the order of presentation, or execution logic, between nodes according to the need even though the execution body sequentially presents the various nodes. For example, the user may interact with the execution body by dragging the indication arrow, changing the execution order index, to change the execution order between nodes. The method is convenient for the user to adjust the execution logic according to the requirement, and can avoid the problems of influencing the user to configure the execution sequence and the execution logic due to insufficient preset sequence.

Step 204: and encapsulating the operation sequence and generating a service interface for executing the operation sequence.

On the basis of step 203, this step aims at encapsulating the actions performed at each node by the above-mentioned execution body according to the sequence of operations, generating a service interface for executing the sequence of operations. Alternatively, the execution body may sequentially encapsulate the code and the code blocks of the actions performed by each target node, corresponding to the operation sequence, to generate the service interface. In this way, when the service interface is called and executed to the corresponding target node, the action configured by the user through the operation configuration instruction can be realized based on the corresponding code. In some scenarios, such a manner may also be referred to as low code encoding, which generates a traffic interface. In embodiments of the present disclosure, the service interface, when invoked, may correspondingly perform operations on the data table in each node. For example, the user may invoke a business interface to perform an "update table operation" after providing updated target data. Similarly, if an add table operation, a delete table operation, or the like is included in the service interface, the execution subject may correspondingly perform these operations based on the service interface. Thus, the execution body may interact with the user using a set of nodes to complete the orchestration of the business interfaces, so that the user may obtain the business interfaces implementing the operation chain, operation sequence based on the combination between the nodes after configuring actions in the nodes by a low code configuration manner (e.g., only indicating the operations performed at the nodes, instead of providing the complete manner required for performing the operations).

Alternatively or additionally, the execution body may build code based on table information (e.g., table names) of the data table in the process of generating the service interface for the low code platform, and then adjust the data table into an entity by using, for example, an object relational mapping (Object Relational Mapping, ORM) tool to actually perform the operation of the table.

According to the method for generating the service interface for the low-code platform, which is provided by the embodiment of the disclosure, a user can build an operation sequence based on a mode of selecting the node and operating the node configuration table, and the service interface is obtained based on the encapsulation result of the operation sequence. In this way, when editing the service interface, the user can instruct linkage and continuously realize a series of table operations based on the mode of concatenating the code modules and the code actions, and the service interface comprising complex and multi-step execution steps can be realized simply and conveniently. Therefore, the difficulty of generating the service interface for the low-code platform can be reduced, and the efficiency of generating the service interface for the low-code platform can be improved.

In some embodiments, there may be some content-related, membership-related associations between data tables, e.g., corresponding to the same content, may be recorded in both data table A and data table B. That is, the data table a and the data table B have a linkage relationship with respect to the same content. Typically, users want to adjust data sheets that have a linkage relationship in order to avoid errors in the contents of the data sheet records. For example, in modifying content u in data table a, the user may also desire to modify content u in data table B in tandem. Alternatively, when the data tables E and F have a superior-inferior relationship, if the data table E is deleted, the user may also desire to delete the data table F synchronously. Therefore, in order to facilitate the user to realize linkage configuration and avoid errors caused by unlink modification of the recorded content of the data table, the execution main body can also adjust the data table in a linkage manner based on the linkage relationship.

In some optional implementations of this embodiment, the executing body may receive linkage description information for a set of data tables, where the linkage description information is used to indicate a linkage relationship between the first data table and the second data table. For example, linkage description information may be entered by a user, who may indicate a linkage relationship between the first data table and the second data table using the description information. For example, the description information may indicate a case where there is an upper and lower level between the first data table and the second data table, including the same content, and a linkage relationship of linkage actions that need to be performed for each case. For example, the description information may indicate that there is a superior-inferior relationship between the first data table and the second data table, which needs to be deleted in linkage. For another example, the descriptive information may indicate that the first data table and the second data table include the same content, and that the first data table and the second data table need to be adjusted in tandem when the portion of the same content is adjusted.

Further, if the execution subject determines, based on the linkage description information, that the first target table operation at the first target node points to the first data table, that is, the data table for which the first target table operation is configured at the first target node is the first data table, the execution subject may generate the linkage table operation for the second data table based on the first target table operation. For example, if the executing body determines at the first target node that the deleted data table H is the upper level data table with the data table J, the executing body may generate a linked-table operation for the data table J (in this example, the linked-table operation may be a delete-table operation to delete the data table J).

It should be appreciated that the above example of "determining that the first target table operation at the first target node points to the first data table based on the linkage description information" is merely an exemplary illustration of "the first data table. In some embodiments, the executing body may also configure the linked list operation for the first data list by "determining that the second target list operation at the second target node points to the second data list based on the linked description information," and the description is not repeated here.

Further, the executing body may simultaneously configure, at the first target node, the linked list operation for the second data list to adjust the first data list and the second data list in linkage. Therefore, the execution main body automatically complements the operation of the linkage table aiming at the data table with the linkage relation, so that the user can conveniently configure the linkage table, and meanwhile, the abnormal data table caused by the lack of linkage operation is avoided.

It should be appreciated that the step of generating a linked-list operation for the second data list based on the first target list operation may be performed at different stages based on different needs. For example, in some embodiments, the executing body may perform the step of generating the linked-list operation for the second data list based on the first target-list operation to directly follow the user's actions, supplementing the linked-list operation after the completion of the above-described step 202 execution. For another example, the execution body may execute the step of generating the linked list operation for the second data list based on the first target list operation after generating the operation sequence to detect the operation sequence and select the replenishment linked list operation.

Similarly, the user may also enter different linkage description information based on different needs. For example, the user may have the option of providing the linkage description information after providing the operation configuration instruction, as well as before providing the operation configuration instruction.

In some embodiments, the executing body may also provide the currently recorded linkage description information for the executing body according to a request of a user, so that the user can modify and update the existing linkage description information to maintain the usability of the linkage description information.

To facilitate an understanding of the above described execution sequence, fig. 3 is provided as one implementation by way of example. Fig. 3 is a flowchart of a process 300 for configuring a linked list operation provided by an embodiment of the present disclosure. For example, in process 300, the executing body may receive the incoming linkage description information and configure the linkage table operation after configuring the corresponding target table operation for the at least one target node based on the pre-configuration. Process 300 may specifically include the steps of:

step 301: responding to a service interface generation request sent by a user, and presenting a group of nodes for the user;

step 302: configuring corresponding target table operations for the at least one target node based on the operation configuration instruction received for the at least one target node;

Step 303: receiving linkage description information transmitted to a group of data tables;

specifically, the user may provide linkage description information for a group of data tables after configuring a corresponding target table operation for at least one target node;

step 304: responsive to determining, based on the linkage description information, that a first target table operation at the first target node points to the first data table, generating, based on the first target table operation, a linkage table operation for the second data table;

specifically, if the executing body determines that the first target table operation at the first target node points to the first data table based on the linkage description information, the executing body may simultaneously configure the linkage table operation for the second data table at the first target node to adjust the first data table and the second data table in linkage.

Step 305: additionally configuring a linkage table operation for the first target node;

specifically, the execution body may configure the linked list operation configured for the second data list linkage at the first target node so that the adjustment may be performed on the first data list and the second data list in linkage at the first target node.

Step 306: generating an operation sequence based on the configured target table operation and the linkage table operation of all the target nodes in response to receiving the configuration completion instruction;

Specifically, the execution body may generate the sequence of operations based on the target table operation and the linked table operation in which the target node is configured. It should be appreciated that at a target node without a linked list operation, the executing body may process, generate a sequence of operations in a manner described with reference to step 203 shown in fig. 2, and will not be described again. And for the target node of the linked list operation, the execution body may add corresponding target list operation and linked list operation in the operation sequence corresponding to the position of the target node, so that the target list operation and the linked list operation may be executed simultaneously to perform adjustment on the first data list and the second data list in a linked manner.

Step 307: and encapsulating the operation sequence and generating a service interface for executing the operation sequence.

The steps 301, 302 and 307 correspond to the steps 201, 202 and 204 shown in fig. 2, respectively, and the same content is referred to the corresponding parts of the previous embodiment, and will not be described again here.

In some embodiments, to further facilitate user configuration operations in the node, the execution body may also: in response to receiving a query indication for at least one target node in a set of nodes, a set of candidate data tables is presented in association with the at least one target node. In particular, the user may interact with the execution body, for example by clicking, or based on pre-configured query instructions, to send a query indication for at least one target node in a set of nodes.

Accordingly, upon receiving the query indication, the executing body may provide it with a set of candidate data tables associated with the target node, the candidate data tables in the set of candidate data tables comprising data tables that may be used at the target node. For example, the execution body may filter the data tables in the set of data tables based on constraints (e.g., whether there is a conflict with a target table operation in a previously configured node, a user's usage rights for the data tables, etc.), and further select the data table that may be used, operated by the user, at the target node as a candidate data table, and further generate a set of candidate data tables. Therefore, the user can intuitively know the data table which can be processed by the candidate data table, and the configuration is convenient for the user.

In some optional implementations of this embodiment, if the user sent the linkage description information before sending the operation configuration instruction, the execution body may further generate an indication identifier for indicating the linkage relation, and respond when the first data table is presented based on the query indication for the at least one target node, presenting the indication identifier in association with the first data table. Therefore, the execution main body can further utilize the indication mark to prompt the linkage relation, so that a user can more clearly understand the linkage relation between the data tables, and the user can conveniently configure the table operation with higher quality.

In some alternative implementations of the present embodiment, the execution body may also present table operations that may be performed by the user in association with the candidate data table to further assist in user understanding.

In addition, the user may also provide additional auxiliary information to the execution body, such as description information of the data table desired to be selected (e.g., fields included in the data table, etc.). Accordingly, when the execution body screens a group of candidate data tables, the execution body can further screen a group of candidate data tables meeting the use requirement of the user according to the description information provided by the user.

Next, description will be made in detail of the fact that the execution body configures, for at least one target node, the relevant contents of the corresponding target table operation based on the operation configuration instruction of the user, that is, the execution body may associate, based on the operation configuration instruction, a code (code module, code group) implementing the action indicated by the operation configuration instruction with the target node.

As described above, the node may be configured as a control that can be triggered, so that after the user clicks the node, a data table that can be processed and a table operation that can be selected may be provided for the node, so as to interact with the user and obtain an operation configuration instruction sent by the user. Similarly, the user may also achieve similar objectives through pre-configured code instructions, for example, the user may specify the node, the table operation to be performed, and the data table for which the table operation is intended through an instruction language (e.g., database language Structured Query Language, simply SQL).

Examples are given of embodiments in which a user is provided with a data table that can be processed and a table operation that can be selected interacts with the user to obtain an operation configuration instruction issued by the user.

For example, at a target node (which is described as a second target node for ease of understanding), a user may instruct the second target node to add a selected data table by selecting the data table and selecting an add table operation. In some alternative implementations of the present embodiment, the data table may include some non-empty fields, i.e., fields that must be filled with content, as the data table is newly added. For example, the newly added data table may be determined based on a pre-configured data table template, in which case some "non-empty fields" may be included in the data table template that need to be filled in.

In this case, the execution body may present a parameter acquisition window for acquiring the content of the non-null field in association with the second target node in response to the second data table including the non-null field. Specifically, the execution body may present the parameter acquisition window at a position associated with the presentation position of the second target node (for example, a position located within a certain distance range of the presentation position of the second target node) after the user configures the table adding operation for the second target node, so that the user may fill out the content of the non-empty field using the parameter acquisition window while prompting the user that the content of the "non-empty field" needs to be filled out using the parameter acquisition window. Therefore, the method is convenient for the user to fill in, and simultaneously can prompt the user to require the user to complement the content of the missing non-empty field, avoid the abnormal execution caused by the field missing in the added list scene, and promote the usability of the finally generated service interface.

It should be understood that, for the update table operation, the read table operation, and the delete table operation, the user may also interact with the execution body in a similar manner to add table operations, and only differences in the execution process of the actual table operation will be described without repeated description.

For an update table operation, the operation configuration instruction may be an instruction to perform, at a target node (described as a third target node for ease of understanding), an update table operation on a data table to be updated including an update field name based on an update field value. For example, the user may select an update table operation by clicking on the third target node and interacting with the execution body to provide the update field that is desired to be updated, as well as the updated update field value. Accordingly, when receiving such an operation configuration instruction, the execution body configures the target table operation at the third node including: the acquired data table to be updated; and updating the content of the corresponding updated field name part in the data table to be updated by using the updated field value.

Specifically, the executing body may obtain the to-be-updated data table including the to-be-updated field, and perform updating on the content of the to-be-updated field portion in the to-be-updated data table (that is, update the content of the to-be-updated field portion to the updated field value) as a specific implementation manner of the target table operation, and associate the to-be-updated data table with the third target node, so that when the service interface is invoked and executed to the third target node, the data table is updated based on the above manner. Therefore, the user can edit the operation function of the update table in the node (service interface) in a mode of indicating the updated content and the updated value, and the coding difficulty of the user is reduced.

Alternatively or additionally, the user may also directly provide the execution body with the data table to be updated that needs to be updated to more finely indicate the target operation table that needs to be updated.

For a read table operation, the operation configuration instruction may be an operation indicating that the indicated target data table is read, presented at the target node (described as a fourth target node for ease of understanding). Alternatively or additionally, the user may also indicate the policy of the target data table, so that the executing body may present the target data table in a certain order and sequence according to the requirement of the user, so as to facilitate the reading of the user.

Accordingly, the execution body may perform, at the fourth target node, a read table operation in response to the operation configuration instruction indication, the read table including rendering a set of target data tables including the query field based on the rendering ordering policy, the target table operation configured at the fourth target node including: determining a set of target data tables based on the query field; based on the presentation ordering strategy, ordering a group of target data tables to obtain an ordering result; and presenting the sequencing result.

In particular, if the target table operation that the execution body is configured at the fourth target node is a read table operation, the execution body may call a set of target data tables including the query field and present a set of data tables presented based on the presentation ordering policy as a specific implementation of the read table operation. Therefore, the user can edit the operation or the function of the reading table in the node (service interface) by only providing the presentation strategy and the query field, and the coding difficulty of the user is reduced.

For the delete table operation, the user may instruct, by operating the configuration instruction, that the delete table operation be performed on the existing data table including the target field at the target node (described as the fifth target node for convenience of understanding), similarly to the add table. For example, the executing body may identify an existing data table for the user at the fifth target node. The existing data table includes a data table added based on other nodes before the fifth target node. The user may instruct the execution body to configure the target table operation at the fifth target node by selecting the existing data table for which the delete table operation is configured, including to delete the existing data table. Therefore, the user can utilize the delete table operation selected from the nodes to edit the delete table operation or function for the service interface, thereby reducing the coding difficulty of the user.

For further understanding, the present disclosure also provides a specific implementation in connection with a specific application scenario, please refer to the flowchart 400 shown in fig. 4.

In fig. 4, the main body may be executed by the server 105 as a low code platform oriented generation service interface. For example, the user may communicate with the server 105 using the terminal device 103, perform step S401, to send a service generation request. Accordingly, the server 105 may perform step S402, providing the nodes 411 to 413 to the terminal device. For example, server 105 may present, after locally creating an initial business interface, setting a request path and name for the initial business interface, a set of nodes 411-413 for executing code for the initial business interface configuration for the user.

Further, the terminal device 103 may utilize its screen to present the interface 103-a for user interaction.

For example, the example of configuring a target table operation with node 411 as a target node by a user through interface 103-a (e.g., a node selected by the user and currently executing configuration may be embodied in terminal device 103 with a different presentation style). The user may click on node 411 to request that a target table operation be configured for it. Accordingly, the terminal device 103 may present the user with a plurality of table operations provided by the server 105 that may be configured in the node 411 for selection by the user. For example, terminal device 103 may utilize menu 420 to present a "table operation" that may be selected. Illustratively, the user selects "add table operation" by clicking on icon 421. Further, the terminal device 103 may provide a menu 430 for the user to ask the user to select a "candidate data table" that needs to be added. Illustratively, the user selects that the data table that needs to be added is "candidate data table a" by clicking on icon 431. Accordingly, the terminal device 103 may perform step S403 (multiple times) to (continuously) communicate the user-configured target table operation to the server 105, so that the server 105 can configure the corresponding target table operation for the at least one target node based on the operation configuration instruction received for the at least one target node.

Further, the user may complete the configuration of nodes 412 and 413 in a similar manner, which is not repeated here. After the user considers that the node configuration table operation is completed, the user may click on the control 440 to execute step S404 to send a configuration completion instruction to the server 105.

Thus, the server 105 may generate a sequence of operations based on the target table operations for which all target nodes are configured in response to receiving the configuration completion instruction. The sequence of operations may then ultimately be encapsulated by the server 105, generating a business interface for executing the sequence of operations.

With further reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of an apparatus for generating a service interface for a low-code platform, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied in various electronic devices.

As shown in fig. 5, the apparatus 500 for generating a service interface for a low code platform according to the present embodiment may include: a node presenting unit 501, an operation configuration unit 502, a sequence generating unit 503, and an interface generating unit 504. Wherein the node presenting unit 501 is configured to present a set of nodes for a user in response to receiving a service interface generation request sent by the user, where a node in the set of nodes is configured to perform a table operation for at least a part of a data table in a preconfigured set of data tables, and the table operation includes at least one of an add table operation, a read table operation, an update table operation, and a delete table operation performed for at least one data table in the set of data tables; an operation configuration unit 502 configured to configure a corresponding target table operation for at least one target node based on an operation configuration instruction received for the at least one target node; a sequence generating unit 503 configured to generate an operation sequence based on target table operations in which all target nodes are configured, in response to receiving a configuration completion instruction; an interface generating unit 504 configured to encapsulate the operation sequence and generate a service interface for executing the operation sequence.

In this embodiment, in the device 500 for generating a service interface for a low-code platform: the specific processing of the node presenting unit 501, the operation configuring unit 502, the sequence generating unit 503 and the interface generating unit 504 and the technical effects thereof may refer to the relevant descriptions of steps 201 to 204 in the corresponding embodiment of fig. 2, and are not repeated here.

In some optional implementations of this embodiment, the apparatus 500 further includes: the linkage relation receiving unit is configured to receive linkage description information transmitted to a group of data tables, wherein the linkage description information is used for indicating linkage relation between the first data table and the second data table; a linkage operation determining unit configured to generate a linkage table operation for the second data table based on the first target table operation in response to determining that the first target table operation at the first target node points to the first data table based on the linkage description information, wherein the linkage table operation performs linkage adjustment on the second data table according to the table operation of the first data table by the first target table operation; a linked operation configuration unit configured to additionally configure a linked list operation for the first target node; and the sequence generating unit 503 is further configured to generate an operation sequence based on the target table operation and the linked table operation in which all the target nodes are configured, in response to receiving the configuration completion instruction.

In some optional implementations of this embodiment, in response to receiving the linkage description information prior to receiving the operation configuration instruction, the apparatus 500 further includes: an instruction identifier generating unit configured to generate an instruction identifier for indicating the linkage relation; an indication identity presenting unit configured to present an indication identity in association with the first data table in response to the first data table being presented based on the query indication for the at least one target node.

In some optional implementations of this embodiment, the apparatus 500 further includes: and a candidate data table presentation unit configured to present a set of candidate data tables in association with at least one target node in the set of nodes in response to receiving the query indication for the at least one target node.

In some alternative implementations of the present embodiment, in response to the operation configuration instruction indicating that the add table operation is performed at the second target node based on a third data table of the set of data tables, the apparatus 500 further includes: and a parameter acquisition unit configured to present a parameter acquisition window for acquiring contents of the non-null field in association with the second target node in response to the second data table including the non-null field.

In some optional implementations of the embodiment, in response to the operation configuration instruction indicating at the third target node that the update table operation is performed on the data table to be updated including the update field name based on the update field value, the target table operation configured at the third node includes: the acquired data table to be updated; and updating the content of the corresponding updated field name part in the data table to be updated by using the updated field value.

In some alternative implementations of the present embodiment, in response to the operation configuration instruction indicating at the fourth target node, performing a read table operation, the read table including rendering a set of target data tables including a query field based on a rendering ordering policy, the target table operation configured at the fourth target node including: determining a set of target data tables based on the query field; based on the presentation ordering strategy, ordering a group of target data tables to obtain an ordering result; and presenting the sequencing result.

In some optional implementations of the embodiment, in response to the operation configuration instruction indicating at the fifth target node that the delete table operation is performed on an existing data table including the target field, the existing data table including a data table added based on other nodes preceding the fifth target node, the target table operation configured at the fifth target node includes: the existing data table is deleted.

In some optional implementations of this embodiment, the node presenting unit is further configured to sequentially present the respective nodes in the corresponding set of nodes in order of execution of operations of the respective nodes in response to receiving the service interface generation request.

The embodiment exists as an embodiment of a device corresponding to the embodiment of the method, and the device for generating the service interface for the low-code platform provided by the embodiment can be used for setting up an operation sequence based on a mode of selecting a node and operating a node configuration table by a user, and obtaining the service interface based on a packaging result of the operation sequence. In this way, when editing the service interface, the user can instruct linkage and continuously realize a series of table operations based on the mode of concatenating the code modules and the code actions, and the service interface comprising complex and multi-step execution steps can be realized simply and conveniently. Therefore, the difficulty of generating the service interface for the low-code platform can be reduced, and the efficiency of generating the service interface for the low-code platform can be improved.

According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

Fig. 6 illustrates a schematic block diagram of an example electronic device 600 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the apparatus 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 may also be stored. The computing unit 601, ROM 602, and RAM 603 are connected to each other by a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

Various components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, mouse, etc.; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as the method of generating a business interface for a low code platform. For example, in some embodiments, the method of generating a business interface for a low code platform may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM 603 and executed by computing unit 601, one or more steps of the method of generating a business interface for a low code platform described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method of generating a business interface for a low code platform in any other suitable way (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of large management difficulty and weak service expansibility in the traditional physical host and virtual private server (VPS, virtual Private Server) service. Servers may also be divided into servers of a distributed system or servers that incorporate blockchains.

According to the technical scheme of the embodiment of the disclosure, a user can build an operation sequence based on a mode of selecting a node and operating a node configuration table, and a service interface is obtained based on a packaging result of the operation sequence. In this way, when editing the service interface, the user can instruct linkage and continuously realize a series of table operations based on the mode of concatenating the code modules and the code actions, and the service interface comprising complex and multi-step execution steps can be realized simply and conveniently. Therefore, the difficulty of generating the service interface for the low-code platform can be reduced, and the efficiency of generating the service interface for the low-code platform can be improved.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions provided by the present disclosure are achieved, and are not limited herein.

The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A method of generating a business interface for a low code platform, comprising:

in response to receiving a service interface generation request sent by a user, presenting a set of nodes for the user, wherein the nodes in the set of nodes are used for configuring a table operation for at least part of a pre-configured set of data tables, and the table operation comprises at least one of an adding table operation, a reading table operation, a updating table operation and a deleting table operation which are executed for at least one data table in the set of data tables;

configuring corresponding target table operations for at least one target node based on operation configuration instructions received for the at least one target node;

generating an operation sequence based on the configured target table operation of all target nodes in response to receiving the configuration completion instruction;

and encapsulating the operation sequence and generating a service interface for executing the operation sequence.

2. The method of claim 1, further comprising:

receiving linkage description information transmitted to the group of data tables, wherein the linkage description information is used for indicating linkage relation between the first data table and the second data table;

responsive to determining that a first target table operation at a first target node points to the first data table based on the linkage description information, generating a linkage table operation for the second data table based on the first target table operation, wherein the linkage table operation performs linkage adjustment on the second data table according to the table operation of the first data table by the first target table operation;

Additionally configuring the linkage table operation for the first target node; and

generating an operation sequence based on the target table operations configured by all the target nodes, including:

and generating an operation sequence based on the configured target table operation of all the target nodes and the linked table operation.

3. The method of claim 2, wherein responsive to receiving the linkage description information prior to receiving the operational configuration instruction, further comprising:

generating an indication mark for indicating the linkage relation;

in response to the first data table being presented based on a query indication for the at least one target node, the indication identification is presented in association with the first data table.

4. The method of claim 1, further comprising:

in response to receiving a query indication for at least one target node in the set of nodes, a set of candidate data tables is presented in association with the at least one target node.

5. The method of claim 1, responsive to the operation configuration instruction indicating that the add table operation is performed at a second target node based on a third data table of the set of data tables, further comprising:

In response to the second data table including a non-null field, a parameter acquisition window for acquiring content of the non-null field is presented in association with the second target node.

6. The method of claim 1, wherein responsive to the operation configuration instruction indicating at a third target node that the update table operation is performed on a data table to be updated including an update field name based on an update field value, the target table operation configured at the third node comprises:

acquiring the data table to be updated;

and updating the content of the part corresponding to the updated field name in the data table to be updated by utilizing the updated field value.

7. The method of claim 1, responsive to the operation configuration instruction indicating at a fourth target node that the read table operation is performed, the read table comprising a set of target data tables comprising query fields based on a presentation ordering policy, the target table operation configured at the fourth target node comprising:

determining the set of target data tables based on the query field;

based on the presentation ordering strategy, ordering the group of target data tables to obtain an ordering result;

And presenting the sequencing result.

8. The method of claim 1, wherein the delete table operation is performed at a fifth target node on an existing data table including a target field, the existing data table including a data table that is added based on other nodes preceding the fifth target node, in response to the operation configuration instruction indicating that a target table operation configured at the fifth target node includes:

and deleting the existing data table.

9. The method of any of claims 1-8, wherein presenting a set of nodes comprises:

the respective nodes of the set of nodes are presented sequentially in correspondence to an order of execution of operations of the respective nodes.

10. An apparatus for generating a business interface for a low code platform, comprising:

a node presenting unit configured to present a set of nodes for a user in response to receiving a service interface generation request sent by the user, wherein the nodes in the set of nodes are configured to perform a table operation for at least part of a pre-configured set of data tables, the table operation including at least one of an add table operation, a read table operation, an update table operation, and a delete table operation performed for at least one of the set of data tables;

An operation configuration unit configured to configure a corresponding target table operation for at least one target node based on an operation configuration instruction received for the at least one target node;

a sequence generating unit configured to generate an operation sequence based on target table operations in which all target nodes are configured, in response to receiving a configuration completion instruction;

and the interface generating unit is configured to encapsulate the operation sequence and generate a service interface for executing the operation sequence.

11. The apparatus of claim 10, further comprising:

a linkage relation receiving unit configured to receive linkage description information transmitted for the group of data tables, wherein the linkage description information is used for indicating linkage relation between the first data table and the second data table;

a linked operation determining unit configured to generate a linked table operation for the second data table based on a first target table operation at a first target node in response to determining that the first target table operation is directed to the first data table based on the linked description information, wherein the linked table operation performs linked adjustment on the second data table according to a table operation of the first data table by the first target table operation;

A linked operation configuration unit configured to additionally configure the linked list operation for the first target node;

and the sequence generating unit is further configured to generate an operation sequence based on the target table operation and the linked table operation in which all target nodes are configured, in response to receiving a configuration completion instruction.

12. The apparatus of claim 11, wherein responsive to receiving the linkage description information prior to receiving the operational configuration instruction, further comprising:

an instruction identifier generating unit configured to generate an instruction identifier for indicating the linkage relation;

an indication identity presenting unit configured to present the indication identity in association with the first data table in response to the first data table being presented based on a query indication for the at least one target node.

13. The apparatus of claim 10, further comprising:

a candidate data table presentation unit configured to present a set of candidate data tables in association with at least one target node of the set of nodes in response to receiving a query indication for the at least one target node.

14. The apparatus of claim 10, responsive to the operation configuration instruction indicating that the add table operation is performed at a second target node based on a third data table of the set of data tables, further comprising:

And a parameter acquisition unit configured to present a parameter acquisition window for acquiring contents of a non-null field in association with the second target node in response to the second data table including the non-null field.

15. The apparatus of claim 10, the update table operation being performed on a data table to be updated including an update field name based on an update field value at a third target node in response to the operation configuration instruction indicating that a target table operation configured at the third node comprises:

acquiring the data table to be updated;

16. The apparatus of claim 10, in response to the operation configuration instruction indicating at a fourth target node that the read table operation is performed, the read table comprising a set of target data tables comprising query fields based on a presentation ordering policy, the target table operation configured at the fourth target node comprising:

determining the set of target data tables based on the query field;

And presenting the sequencing result.

17. The apparatus of claim 10, the delete table operation being performed at a fifth target node on an existing data table comprising target fields, the existing data table comprising a data table that was added based on other nodes preceding the fifth target node, in response to the operation configuration instruction indicating that a target table operation configured at the fifth target node comprises:

and deleting the existing data table.

18. The apparatus according to any of claims 10-17, wherein the node presenting unit is further configured to sequentially present respective nodes in the set of nodes in response to receiving a traffic interface generation request in response to an order of execution of operations of the respective nodes.

19. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of generating a business interface for a low code platform of any one of claims 1-9.

20. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of generating a business interface for a low code platform of any one of claims 1-9.

21. A computer program product comprising a computer program which, when executed by a processor, implements a method of generating a business interface for a low code oriented platform according to any of claims 1-9.