Low-code application generation method, low-code development platform and storage medium

Abstract

An embodiment of the present invention provides a method for generating a low-code application, a low-code development platform and a storage medium, the method comprising: displaying an interactive interface corresponding to a preset business scenario, the interactive interface comprising at least one operation object; upon detecting interaction information of a user on a newly added function object in the operation object, determining a target function corresponding to the newly added function object in a FaaS environment according to the interaction information; generating a low-code application based on an association between the target function and the newly added function object of the preset business scenario, so as to improve the convenience of extending the business logic of the low-code application, and improve the convenience of extending the business scenarios to which the low-code application is applicable, thereby improving the user experience of the low-code application.

Description

Technical Field

[0001] The present invention relates to the field of application development technology, and in particular to a method for generating a low-code application, a low-code development platform and a storage medium. Background Art

[0002] Currently, users can quickly build low-code applications such as mini-programs, H5, PC, and WEB applications that support various business scenarios. For example, users can use the preset drag-and-drop operation in the low-code development platform to replace the code writing operation, so that they can get low-code applications with less or no code.

[0003] However, since the business logic of low-code applications is relatively simple and the business scenarios in which low-code applications are applicable are limited, it is easy for the generated low-code applications to fail to meet the complex business logic required by users, resulting in a poor user experience with low-code applications. Summary of the invention

[0004] The main purpose of this invention is to provide a low-code application generation method, a low-code development platform and a storage medium, aiming to improve the convenience of extending the business logic of low-code applications, which is conducive to improving the convenience of extending the business scenarios applicable to low-code applications, thereby enhancing the user experience of low-code applications.

[0005] In the first aspect, an embodiment of the present invention provides a method for generating a low-code application, the generation method comprising: displaying an interactive interface corresponding to a preset business scenario, the interactive interface comprising at least one operation object; upon detecting interaction information of a user on a newly added function object in the operation object, determining a target function corresponding to the newly added function object in a FaaS environment according to the interaction information; and generating a low-code application based on the association relationship between the target function and the newly added function object of the preset business scenario.

[0006] In a second aspect, an embodiment of the present invention further provides a low-code development platform, which provides an interactive interface corresponding to a preset business scenario, and the low-code development platform is used to implement the steps of any low-code application generation method provided in the specification of the present invention.

[0007] In the third aspect, an embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program. The computer program can be executed by a processor, and the processor implements any method for generating a low-code application provided in the specification of the present invention.

[0008] An embodiment of the present invention provides a method for generating a low-code application, a low-code development platform, and a storage medium. The embodiment of the present invention displays an interactive interface corresponding to a preset business scenario, wherein the interactive interface includes at least one operation object; when the user's interaction information on a newly added function object in the operation object is detected, the target function corresponding to the newly added function object is determined in a FaaS environment according to the interaction information; and a low-code application is generated based on the association between the target function and the newly added function object of the preset business scenario. By determining the target function in a FaaS environment, and generating a low-code application based on the association between the target function and the newly added function object, it is beneficial to improve the convenience of extending the business logic of the low-code application, and to improve the convenience of extending the business scenarios applicable to the low-code application, thereby improving the user experience of the low-code application. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0010] Figure 1 A flowchart of a method for generating a low-code application provided in an embodiment of the present invention;

[0011] Figure 2 A schematic block diagram of a method for generating a low-code application according to an embodiment of the present invention;

[0012] Figure 3 A schematic diagram of an interactive interface corresponding to a preset business scenario involved in an embodiment of the present invention;

[0013] Figure 4 A schematic block diagram of a method for generating a low-code application according to another embodiment of the present invention;

[0014] Figure 5 A schematic diagram of an interactive interface corresponding to a preset business scenario involved in another embodiment of the present invention;

[0015] Figure 6 A schematic block diagram of a method for generating a low-code application according to another embodiment of the present invention;

[0016] Figure 7 A schematic block diagram of a method for generating a low-code application according to another embodiment of the present invention;

[0017] Figure 8 It is a schematic diagram of an interactive interface corresponding to a preset business scenario involved in yet another embodiment of the present invention. DETAILED DESCRIPTION

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

[0019] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.

[0020] It should be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0021] The embodiment of the present invention provides a method for generating a low-code application, a low-code development platform, and a storage medium. Among them, the method for generating a low-code application can be applied to a low-code development platform.

[0022] Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0023] See also Figure 1 , Figure 1 A flow chart of a method for generating a low-code application provided in an embodiment of the present invention. Exemplarily, the method for generating a low-code application is applied to a low-code development platform. The low-code development platform can be deployed in an electronic device, and the electronic device can be a mobile phone, a tablet computer, a laptop computer, a desktop computer, etc. The low-code development platform business can be deployed in a server, and the server can be a separate server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. The server can be a separate server or a server cluster, and there is no limitation here.

[0024] like Figure 1 As shown, the method for generating the low-code application includes steps S101 to S103.

[0025] Step S101: displaying an interactive interface corresponding to a preset business scenario, where the interactive interface includes at least one operation object.

[0026] For example, before obtaining a low-code application, the user needs to orchestrate the business logic of the low-code application. In some embodiments, the user can orchestrate the business logic of the low-code application through a low-code development platform. In response to the user's business orchestration needs for the low-code application, for example, the user requires the low-code application to implement a certain business logic in a preset business scenario, the low-code application can display the interactive interface corresponding to the preset business scenario, and the interactive interface includes at least one operation object. The user can operate the operation object in the interactive interface, such as dragging the operation object into the business logic setting area corresponding to the preset business scenario to add the business logic carried by the operation object to the business logic set corresponding to the preset business scenario. Based on this, the low-code application generated by the low-code development platform can implement the business logic carried by the operation object in the preset business scenario. Of course, it is not limited to this, and no limitation is made here.

[0027] In an embodiment of the present invention, an interactive interface corresponding to a preset business scenario is displayed, and the interactive interface includes at least one operation object. When a user needs to orchestrate the business logic of a low-code application, the user can operate the operation object in the interactive interface to orchestrate the business logic of the low-code application, which is conducive to improving the convenience of users in orchestrating the business logic of the low-code application.

[0028] Step S102: When detecting the user's interaction information on the newly added function object in the operation object, determine the target function corresponding to the newly added function object in the FaaS environment according to the interaction information.

[0029] For example, the user's interaction information on the operation object can be detected in the interactive interface. For example, the interactive interface detects whether the user drags the operation object into the business logic setting area corresponding to the preset business scenario. If it is detected that the user drags the operation object into the business logic setting area corresponding to the preset business scenario, the business logic carried by the operation object is added to the business logic set corresponding to the preset business scenario. Of course, it is not limited to this and is not limited here.

[0030] However, the business logic carried by the operation objects in the interactive interface is generally pre-set, and the number of operation objects included in the interactive interface is limited. Therefore, when users arrange the business logic of low-code applications based on the operation objects included in the interactive interface, since users cannot add operation objects to increase the business logic carried by the operation objects, or modify the business logic carried by the operation objects, it is easy for the business logic carried by the operation objects to fail to meet the user's business logic requirements for the low-code application.

[0031] In order to better meet the user's business logic requirements for low-code applications, a new function object is also provided in the operation object of the present invention. For example, the new function object in the operation object can be used to establish an association relationship between the low-code development platform and the Function as a Service (FaaS) environment. Since the FaaS environment can provide full life cycle management services for editing, deploying, and running functions, when users interact with the new function objects in the operation object, they can use the FaaS environment to expand the business logic of the low-code application. For example, the target function required by the user is developed with the help of the script development function of the FaaS environment, thereby expanding the business logic of the low-code application according to the target function.

[0032] In some embodiments, the low-code development platform can detect the user's interaction information with the newly added function object in the operation object. When the user's interaction information with the newly added function object in the operation object is detected, the low-code development platform determines that the user needs to expand the business logic of the low-code application. The low-code development platform can transmit the detected user's interaction information with the newly added function object to the FaaS environment, and the FaaS environment can determine the target function corresponding to the newly added function object based on the received interaction information. When the low-code application is subsequently generated, the target function can be used to expand the business logic of the low-code application. In this way, when the user's interaction information with the newly added function object of the operation object is detected, the target function corresponding to the newly added function object is determined in the FaaS environment based on the interaction information, which is conducive to improving the convenience of expanding the business logic of the low-code application.

[0033] Exemplarily, the interactive interface includes at least one of an information input field corresponding to the newly added function object and an information selection field corresponding to the newly added function object. For example, the information input field may include at least one of a required information input field and an optional information input field, and the information selection field may include at least one of a required information selection field and an optional information selection field, which is not limited here.

[0034] In some embodiments, when at least one of the input information of the user in the information input bar and the selection information of the user in the information selection bar is detected, in the FaaS environment, based on at least one of the association relationship between the input information and the information input bar and the association relationship between the selection information and the information selection bar, at least one of the input information and the selection information is orchestrated with low-code logic to obtain the target function corresponding to the newly added function object.

[0035] For example, the preset business scenario may include a form submission scenario. When users obtain low-code applications through the low-code development platform, they can expand the business logic corresponding to the low-code application in the form submission scenario. Figure 2 As shown, the business logic corresponding to different form submission stages in the form submission scenario can be expanded. For example, in the FaaS environment, the objective function corresponding to at least one of the form submission stages before, during, and after form submission is determined; of course, it is not limited to this and is not limited here.

[0036] When users expand the business logic corresponding to different form submission stages in the form submission scenario, they can interact with the newly added function objects corresponding to different form submission stages in the interactive interface corresponding to the form submission scenario. Figure 3 As shown, the newly added function objects included in the form submission scenario include binding action identifier 1 and binding action identifier 2. For example, when the user's interaction information for binding action identifier 1 is detected, such as when the user triggers binding action identifier 1, the target function 1 corresponding to binding action identifier 1 determined in the FaaS environment based on the interaction information can be used to extend the corresponding business logic before the form is submitted; when the user's interaction information for binding action identifier 2 is detected, such as when the user triggers binding action identifier 2, the target function 2 corresponding to binding action identifier 2 determined in the FaaS environment based on the interaction information can be used to extend the corresponding business logic after the form is submitted; of course, it is not limited to this and is not limited here.

[0037] In an exemplary embodiment, when a user triggers binding action identifier 1, the interactive interface corresponding to the form submission scenario displays an information input bar, for example. The information input bar is used to indicate the binding action that needs to be performed before the user enters the form submission. In the FaaS environment, the binding action input by the user can be arranged with low-code logic based on the association between the input information and the information input bar, and the objective function 1 corresponding to the binding action identifier 1 can be obtained, so that the corresponding business logic before the form submission can be expanded according to the objective function 1; of course, it is not limited to this and is not limited here. For example, when the user triggers binding action identifier 1 and binding action identifier 2, the interactive interface corresponding to the form submission scenario displays an information input bar. Regardless of whether the user enters the same binding action or a different binding action, the objective function obtained is different based on the different associations between the input information and the information input bar.

[0038] In an exemplary embodiment, when a user triggers binding action identifier 2, the interactive interface corresponding to the form submission scenario displays an information selection bar, for example. The information selection bar is used to instruct the user to select the binding action to be performed after the form is submitted. In the FaaS environment, the binding action selected by the user can be arranged with low-code logic based on the association between the selection information and the information selection bar, and the objective function 2 corresponding to the binding action identifier 2 can be obtained, so that the corresponding business logic after the form submission can be expanded according to the objective function 2; of course, it is not limited to this. For example, when the user triggers binding action identifier 1 and binding action identifier 2, the interactive interface corresponding to the form submission scenario displays an information selection bar. Whether the user selects the same binding action or a different binding action, the objective function obtained is different based on the different associations between the selection information and the information selection bar, and there is no limitation here.

[0039] For example, the preset business scenarios may include workflow scenarios. When users obtain low-code applications through low-code development, they can expand the business logic corresponding to the workflow scenarios of low-code applications. Figure 4 As shown, the business logic corresponding to different workflow nodes in the workflow scenario can be expanded. For example, in the FaaS environment, the objective function corresponding to the process start node and the leader approval node is determined; of course, it is not limited to this and is not limited here.

[0040] In some implementations, when a user expands the business logic corresponding to different workflow nodes in a workflow scenario, the user can interact with the newly added function objects corresponding to different workflow nodes in the interaction interface corresponding to the workflow scenario. Figure 5As shown, the newly added function objects included in the workflow scenario include a process start identifier, a file addition identifier, a leader 1 approval identifier, a leader 2 approval identifier, and a process end identifier. For example, when the user's interactive information on the process start identifier is detected, such as when the user triggers the process start identifier, the target function 3 corresponding to the process start identifier determined in the FaaS environment according to the interactive information can be used to expand the business logic corresponding to the process start node; when the user's interactive information on the file addition identifier is detected, such as when the user triggers the file addition identifier, the target function 4 corresponding to the file addition identifier determined in the FaaS environment according to the interactive information can be used to expand the business logic corresponding to the file addition node, and so on; of course, it is not limited to this, and no limitation is made here.

[0041] In an exemplary embodiment, when a user triggers to add a tag to a file, the interactive interface corresponding to the workflow scenario displays, for example, an information input bar and an information selection bar. Figure 5 As shown, the information input bar includes, for example, a rule name input bar and an associated operation input bar, and the information selection bar includes, for example, a node action selection bar. Among them, the rule name input bar is used to indicate the name of the file adding rule corresponding to the file adding node input by the user, the associated operation input bar is used to indicate the associated operation corresponding to the file adding node input by the user, and the node action selection bar is used to indicate the node action corresponding to the file adding node selected by the user. In the FaaS environment, based on the association relationship between the input information and the information input bar, and the association relationship between the selected information and the information selection bar, the name of the file adding rule input by the user, the associated operation, and the node action selected by the user can be arranged with low-code logic to obtain the objective function 4 corresponding to the file adding node, so that the business logic corresponding to the file adding node can be expanded according to the objective function 4; of course, it is not limited to this, and no limitation is made here.

[0042] For example, the preset business scenarios may include API open scenarios. When users obtain low-code applications through the low-code development platform, they can expand the interfaces of low-code applications that can be accessed by external applications. Figure 6 As shown, the target function corresponding to the target endpoint is determined in the FaaS environment to expose one or more interfaces corresponding to the target endpoint to external applications, and the external applications can access the interfaces exposed in the low-code application; of course, it is not limited to this and is not limited here.

[0043] In some embodiments, when a user expands the interface of a low-code application that can be accessed by external applications, the user can interact with the corresponding newly added function object in the interactive interface corresponding to the open API scenario. The newly added function object corresponding to the open API scenario includes a newly added service identifier. For example, when the user's interaction information with the newly added service identifier is detected, such as when the user triggers the newly added service identifier, the interactive interface of the open API scenario, for example, displays an information input bar and an information selection bar, which are used to instruct the user to input or select the information required for the exposed interface, such as the API access path, the unique code of the API, and so on. In the FaaS environment, based on the association between the input information and the information input bar, and the association between the selection information and the information selection bar, the information required for the exposed interface input or selected by the user can be arranged with low-code logic to obtain the target function 5 corresponding to the newly added service identifier, so as to facilitate the subsequent expansion of the interface of the low-code application that can be accessed by external applications according to the target function 5; of course, it is not limited to this, and no limitation is made here.

[0044] Exemplarily, the interactive interface includes an information selection bar corresponding to the newly added function object. For example, the information selection bar may include at least one of a required information selection bar and an optional information selection bar, which is not limited here.

[0045] In some embodiments, when the user's selection information in the information selection bar is detected, the target function corresponding to the newly added function object is determined from at least one preset function based on the association between the selection information and the information selection bar, and the preset function is generated in the FaaS environment.

[0046] For example, the preset business scenario may include a connector scenario. When a user obtains a low-code application through a low-code development platform, the user can expand the connector required by the low-code application. For example, the low-code application can access an external application and obtain corresponding information through a connector at the corresponding form submission stage or the corresponding workflow node; of course, it is not limited to this and is not limited here. Figure 7 As shown, an OpenAPI is developed in a FaaS environment, and the developed OpenAPI is published to the API gateway and integrated into the connector scenario as a preset function, so that the connectors required for low-code applications can be expanded in the connector scenario; of course, it is not limited to this and is not restricted here.

[0047] In an exemplary implementation, when a user expands a connector of a low-code application, the user can interact with the corresponding newly added function object in the interactive interface corresponding to the connector scenario. Figure 8As shown, the newly added function object included in the connector scenario includes a newly created connector identifier. For example, when the user's interactive information on the newly created connector identifier is detected, such as when the user triggers the newly created connector identifier, the interactive interface corresponding to the connector scenario, for example, displays an information selection bar. The information selection bar is used to instruct the user to select a connector type. Among them, the connector type can be determined based on a preset function integrated in the connector scenario. When the connector type selected by the user in the information selection bar is detected, the preset function corresponding to the connector type is determined from at least one preset function as the target function 6 corresponding to the newly added connector identifier, based on the association between the selection information and the information selection bar, for subsequent expansion of the connector of the low-code application; of course, it is not limited to this, and no limitation is made here.

[0048] The embodiment of the present application determines the target function corresponding to the newly added function object. When the low-code application is subsequently generated, the business logic of the low-code application can be expanded based on the target function, which is conducive to improving the convenience of expanding the business logic of the low-code application. In addition, different target functions can be determined for different newly added function objects in different preset business scenarios. When the low-code application is subsequently generated, the business logic of the low-code application can be expanded based on different target functions to make the low-code application suitable for different preset business scenarios, which is conducive to improving the convenience of expanding the business scenarios applicable to the low-code application.

[0049] Step S103: Generate a low-code application based on the association relationship between the target function and the newly added function object of the preset business scenario.

[0050] For example, when users are orchestrating the business logic of a low-code application, they can interact with the newly added function objects in different operation objects through the interactive interface corresponding to different preset business scenarios displayed by the low-code development platform, so as to expand the business logic of the low-code application corresponding to different preset business scenarios.

[0051] In some embodiments, the objective function includes, for example, an objective function A and an objective function B. There is an association relationship between the objective function A and the newly added function object A of the preset business scenario A, and there is an association relationship between the objective function B and the newly added function object B of the preset business scenario B. If a low-code application is not generated based on the association relationship between the objective function and the newly added function object of the preset business scenario, it is easy to expand the business logic corresponding to the newly added function object B according to the objective function A, or expand the business logic corresponding to the newly added function object A according to the objective function B. However, since there is no association relationship between the objective function A and the newly added function object B, and there is no association relationship between the objective function B and the newly added function object A, it is easy to cause the business logic expansion to fail, thereby failing to meet the user's business logic requirements for low-code applications.

[0052] In an embodiment of the present invention, a low-code application is generated based on the association relationship between the target function and the newly added function object of the preset business scenario. The business logic corresponding to the newly added function object of the preset business scenario in the low-code application can be expanded according to the target function, which is conducive to improving the accuracy of the business logic of the extended low-code application.

[0053] Exemplarily, based on the association relationship between the target function and the newly added function object of the preset business scenario, a low-code application is generated, including: adding the target function to the business logic set corresponding to the newly added function object of the preset business scenario to generate a low-code application.

[0054] For example, based on the association between the target function A and the newly added function object A of the preset business scenario A, the target function A is added to the business logic set corresponding to the newly added function object A of the preset business scenario A to generate a low-code application. Accordingly, when the low-code application is subsequently run, if the newly added function object A in the preset business scenario is involved, the target function A can be called and the result can be returned; of course, it is not limited to this and is not limited here.

[0055] In some implementations, the preset business scenario includes at least one of a form submission scenario, a workflow scenario, a connector scenario, and an API open scenario.

[0056] For example, when the preset business scenario includes a form submission scenario, the target function is added to the business logic set corresponding to the target form submission stage of the form submission scenario, so that the target function is called and the result is returned when the low-code application runs to the target form submission stage.

[0057] In an exemplary embodiment, in a form submission scenario, target function 1 can be used to extend the business logic corresponding to before form submission, then target function 1 is added to the business logic set corresponding to the pre-form submission stage of the form submission scenario, so that when the low-code application runs to the pre-form submission stage, target function 1 can be called and the result can be returned. For example, target function 1 is used to obtain the user avatar information of the edited form before the form is submitted, then when the low-code application runs to the editing stage before the form submission, target function 1 can be called to obtain the user avatar information of the edited form. In the form submission scenario, target function 2 can be used to extend the business logic corresponding to after the form is submitted, then target function 2 is added to the business logic set corresponding to the post-form submission stage of the form submission scenario, so that when the low-code application runs to the post-form submission stage, target function 2 can be called and the result can be returned. For example, target function 2 is used to generate a form editing record after the form is submitted, then target function 2 can be called to generate a form editing record when the low-code application runs to the post-form submission stage. Of course, it is not limited to this, and no limitation is made here.

[0058] For example, when the preset business scenario includes a workflow scenario, the target function is added to the business logic set corresponding to the target workflow node of the workflow scenario, so that the target function is called and the result is returned when the low-code application runs to the target flow work node.

[0059] For example, in a workflow scenario, target function 3 can be used to extend the business logic corresponding to the process start node, then add target function 3 to the business logic set corresponding to the process start node of the workflow scenario, so that when the low-code application runs to the process start node, target function 3 can be called and the result can be returned; target function 4 can be used to extend the business logic corresponding to the file addition node, then add target function 4 to the business logic set corresponding to the file addition node of the workflow scenario, so that when the low-code application runs to the file addition node, target function 4 can be called and the result can be returned. Of course, it is not limited to this, and no limitation is made here.

[0060] For example, when the preset business scenario includes a connector scenario, the target function is registered as the target connector of the low-code application so that the target function is called and the result is returned when the low-code application calls the target connector.

[0061] In an exemplary embodiment, in a connector scenario, the target function 6 can be used to extend the connector of a low-code application, and the target function 6 is registered as the target connector of the low-code application. In this way, when the low-code application calls the target connector, the target function 6 can be called and the result can be returned. For example, when the low-code application runs to the corresponding form submission stage or the corresponding workflow node, the low-code application calls the target connector, and then the target function 6 can be called to access the external application and obtain the corresponding information. Of course, it is not limited to this, and no limitation is made here.

[0062] For example, when the preset business scenario includes an API open scenario, the target function is added to the business logic set corresponding to the target endpoint of the low-code application, so that the target function is called and the result is returned when the external application accesses the target endpoint.

[0063] In an exemplary embodiment, in an API open scenario, the target function 5 can be used to expand the interface of the low-code application that can be accessed by external applications. For example, the interface is connected to the target endpoint of the low-code application. Then, the target function 5 is added to the business logic set corresponding to the target endpoint of the low-code application. In this way, when the external application accesses the target endpoint, the target function 5 can be called and the result can be returned. For example, when an external application accesses the target endpoint, the low-code application calls the target function 5 to expose the interface to the external application, and the external application can obtain the corresponding information of the low-code application through the exposed interface. Of course, it is not limited to this, and no limitation is made here.

[0064] Of course, the preset business scenarios are not limited to at least one of the form submission scenarios, workflow scenarios, connector scenarios, and API open scenarios. For example, new function objects can be set for other scenarios, and the business logic corresponding to the new function objects of other scenarios can be expanded. There is no restriction here.

[0065] The embodiment of the present invention adds different objective functions to the business logic set of newly added function objects for different preset business scenarios. When the subsequent low-code application runs to the corresponding preset business scenario, it can call the corresponding objective function and return the result, which is conducive to meeting the user's business logic requirements for the low-code application, and is conducive to the expansion of the business logic of the low-code application, as well as the expansion of the business scenarios applicable to the low-code application.

[0066] Exemplarily, when the number of objective functions is greater than or equal to a preset number threshold, the logical relationship between the preset business scenarios is obtained; based on the logical relationship between the preset business scenarios and the association relationship between the objective function and the newly added function objects of the preset business scenarios, a low-code application is generated.

[0067] In some embodiments, when the low-code application is running, there is a certain running order between different preset business scenarios, that is, there is a certain logical relationship between different preset business scenarios. Accordingly, when a low-code application is generated and the number of objective functions is greater than or equal to the preset number threshold, the objective function can also be added to the business logic set corresponding to the newly added function object of the associated preset business scenario according to the logical relationship between the preset business scenarios. For example, if the objective function is not added to the business logic set corresponding to the newly added function object of the associated preset business scenario according to the logical relationship between the preset business scenarios, it is easy for the low-code development platform to add multiple objective functions to the business logic set of the newly added function object of the associated preset business scenario in the same time period. Based on this, it is easy for different business logics to interfere with each other when the subsequent low-code application is running, resulting in low operating efficiency of the business logic in the low-code application, such as low efficiency of computing, storage IO, network IO, etc. when the low-code application is running. Therefore, by generating a low-code application based on the logical relationship between preset business scenarios and the association relationship between the objective function and the newly added function object of the preset business scenario, it is possible to determine the operating logic between different objective functions of the subsequent low-code application at runtime by restricting the adding logic of different objective functions. This will help reduce the risk of mutual interference between different business logics of the low-code application at runtime and improve the operating efficiency of the business logic in the low-code application.

[0068] In an exemplary implementation, the logical relationship between the preset business scenarios is determined according to the logical relationship between the newly added function objects of different preset business scenarios.

[0069] Taking the newly added function object A of the preset business scenario A and the newly added function object B of the preset business scenario B as an example, if the logical relationship between the newly added function object A and the newly added function object B is the preset sequential logic, it can be determined that the logical relationship between the preset business scenario A and the preset business scenario B includes the preset sequential logic; if the logical relationship between the newly added function object A and the newly added function object B is the preset parallel logic, it can be determined that the logical relationship between the preset business scenario A and the preset business scenario B includes the preset parallel logic; if the logical relationship between the newly added function object A and the newly added function object B is the preset jump logic, it can be determined that the logical relationship between the preset business scenario A and the preset business scenario B includes the preset jump logic; of course, it is not limited to this, the logical relationship between different preset business scenarios may include one or more, for example, the preset business scenario A also includes a newly added function object C, when the logical relationship between the newly added function object A and the newly added function object B is the preset sequential logic, and the logical relationship between the newly added function object C and the newly added function object B is the preset jump logic, the logical relationship between the preset business scenario A and the preset business scenario B includes the preset sequential logic and the preset jump logic, which is not limited here. In this way, by determining the logical relationship between the preset business scenarios, when generating a low-code application, the business logic of the low-code application can be expanded according to the logical relationship between the preset business scenarios. Then, when the low-code application is running subsequently, different preset business scenarios can run according to the logical relationship between different preset business scenarios, which is conducive to reducing the risk of mutual interference between the business logics corresponding to different preset business scenarios during the operation of the low-code application, and is conducive to improving the operating efficiency of the business logic in the low-code application.

[0070] In some embodiments, when the logical relationship between preset business scenarios includes preset sequential logic, a low-code application is generated based on the preset sequential logic based on the association relationship between the target function and the newly added function object of the preset business scenario.

[0071] For example, when the logical relationship between the preset business scenario A and the preset business scenario B includes a preset sequential logic, when generating a low-code application, the target function A can be first added to the business logic set corresponding to the newly added function object A of the preset business scenario A according to the preset sequential logic, and then the target function B can be added to the business logic set corresponding to the newly added function object B of the preset business scenario B.

[0072] In some embodiments, when the logical relationship between preset business scenarios includes preset parallel logic, a low-code application is generated based on the preset parallel logic based on the association relationship between the target function and the newly added function object of the preset business scenario.

[0073] For example, when the logical relationship between the preset business scenario A and the preset business scenario B includes the preset parallel logic, when generating a low-code application, the target function A can be added to the business logic set corresponding to the newly added function object A of the preset business scenario A according to the preset parallel logic, and the target function B can be added to the business logic set corresponding to the newly added function object B of the preset business scenario B.

[0074] In some embodiments, when the logical relationship between preset business scenarios includes preset jump logic, a low-code application is generated based on the preset jump logic based on the association relationship between the target function and the newly added function object of the preset business scenario.

[0075] For example, when the logical relationship between the preset business scenario A and the preset business scenario B includes a preset jump logic, when generating a low-code application, you can jump from the business logic set corresponding to the newly added function object A that adds the target function A to the preset business scenario A to the business logic set corresponding to the newly added function object B that adds the target function B to the preset business scenario B according to the preset jump logic; or jump from the business logic set corresponding to the newly added function object B that adds the target function B to the preset business scenario B to the business logic set corresponding to the newly added function object A that adds the target function A to the preset business scenario A according to the preset jump logic.

[0076] In an exemplary embodiment, the preset business scenario A also includes a newly added function object C. When the logical relationship between the newly added function object A and the newly added function object B is the preset sequential logic, and the logical relationship between the newly added function object C and the newly added function object B is the preset jump logic, when generating a low-code application, the target function A can be first added to the business logic set corresponding to the newly added function object A of the preset business scenario A according to the preset sequential logic, and then the target function B can be added to the business logic set corresponding to the newly added function object B of the preset business scenario B, and then jump to the business logic set corresponding to the newly added function object C added to the preset business scenario A according to the preset jump logic. Of course, it is not limited to this. When the logical relationship between the newly added function object A and the newly added function object C and the newly added function object B is the preset sequential logic, the logical relationship between the newly added function object A and the newly added function object C can be the preset parallel logic or the preset sequential logic, which is not limited here.

[0077] The embodiment of the present invention generates a low-code application based on the logical relationship between preset business scenarios and the association relationship between the target function and the newly added function object of the preset business scenario. According to the logical relationship between different preset business scenarios, the target function can be added to the business logic set corresponding to the newly added function object of the preset business scenario according to at least one of the preset sequential logic, preset parallel logic, and preset jump logic to determine the operating logic between different target functions when the subsequent low-code application is running, which is beneficial to reducing the risk of mutual interference between different business logics of the low-code application during runtime, and is beneficial to improving the operating efficiency of the business logic in the low-code application.

[0078] The method for generating a low-code application provided in the above embodiment displays an interactive interface corresponding to a preset business scenario, where the interactive interface includes at least one operation object; when detecting the user's interaction information on a newly added function object in the operation object, determining the target function corresponding to the newly added function object in the FaaS environment based on the interaction information; generating a low-code application based on the association between the target function and the newly added function object of the preset business scenario, thereby improving the convenience of extending the business logic of the low-code application and the convenience of extending the business scenarios to which the low-code application is applicable, thereby improving the user experience of the low-code application.

[0079] An embodiment of the present invention also provides a low-code development platform, which provides an interactive interface corresponding to a preset business scenario.

[0080] Exemplarily, the low-code development platform is used to implement the following steps:

[0081] Displaying an interactive interface corresponding to a preset business scenario, wherein the interactive interface includes at least one operation object;

[0082] When detecting user interaction information on a newly added function object in the operation object, determining, in the FaaS environment, a target function corresponding to the newly added function object according to the interaction information;

[0083] Based on the association relationship between the objective function and the newly added function object of the preset business scenario, a low-code application is generated.

[0084] The specific principles and implementation methods of the low-code development platform provided by the embodiment of the present invention are similar to the low-code application generation method of the aforementioned embodiment, and will not be repeated here.

[0085] An embodiment of the present invention also provides a computer-readable storage medium, which stores a computer program. The computer program can be executed by a processor, and the processor implements the steps of any method for generating a low-code application provided in the description of the embodiment of the present invention.

[0086] The storage medium may be an internal storage unit of the electronic device where the low-code development platform described in the aforementioned embodiment is located, such as a hard disk or memory of the electronic device. The storage medium may also be an external storage device of the electronic device where the low-code development platform described in the aforementioned embodiment is located, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device.

[0087] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware embodiment, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0088] It should be understood that the term "and / or" used in the present specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system including the element.

[0089] The serial numbers of the embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for generating a low-code application, characterized in that: include: Displaying an interactive interface corresponding to a preset business scenario, wherein the interactive interface includes at least one operation object; In the case of detecting user interaction information on a newly added function object in the operation object, determining a target function corresponding to the newly added function object in the FaaS environment according to the interaction information, and the newly added function object is used to establish an association relationship between the low-code development platform and the FaaS environment; Generate a low-code application based on the association relationship between the target function and the newly added function object of the preset business scenario; The generating of a low-code application based on the association relationship between the target function and the newly added function object of the preset business scenario includes: When the number of the objective functions is greater than or equal to a preset number threshold, determining the logical relationship between the preset business scenarios according to the logical relationship between the newly added function objects of different preset business scenarios; Based on the logical relationship between the preset business scenarios and the association relationship between the objective function and the newly added function objects of the preset business scenarios, a low-code application is generated.

2. The generation method according to claim 1, characterized in that: The interactive interface includes at least one of an information input column corresponding to the newly added function object and an information selection column corresponding to the newly added function object; The step of, in a case where the user's interaction information with respect to the newly added function object in the operation object is detected, determining the target function corresponding to the newly added function object according to the interaction information in the FaaS environment includes: When at least one of the input information of the user in the information input bar and the selection information of the user in the information selection bar is detected, in the FaaS environment, based on at least one of the association relationship between the input information and the information input bar and the association relationship between the selection information and the information selection bar, at least one of the input information and the selection information is orchestrated with low-code logic to obtain the objective function corresponding to the newly added function object.

3. The generation method according to claim 1, characterized in that: The interactive interface includes an information selection bar corresponding to the newly added function object; The step of, in a case where the user's interaction information with respect to the newly added function object in the operation object is detected, determining the target function corresponding to the newly added function object according to the interaction information in the FaaS environment includes: When the user's selection information in the information selection bar is detected, the target function corresponding to the newly added function object is determined from at least one preset function according to the association between the selection information and the information selection bar, and the preset function is generated in the FaaS environment.

4. The generation method according to claim 1, characterized in that: The generating of a low-code application based on the association relationship between the target function and the newly added function object of the preset business scenario includes: Add the target function to the business logic set corresponding to the newly added function object of the preset business scenario to generate a low-code application.

5. The generation method according to claim 4, characterized in that: The preset business scenario includes at least one of a form submission scenario, a workflow scenario, a connector scenario, and an API open scenario; The step of adding the objective function to the business logic set corresponding to the newly added function object of the preset business scenario to generate a low-code application includes at least one of the following: In the case where the preset business scenario includes a form submission scenario, the objective function is added to the business logic set corresponding to the target form submission phase of the form submission scenario, so as to call the objective function and return the result when the low-code application runs to the target form submission phase; In the case where the preset business scenario includes a workflow scenario, the objective function is added to the business logic set corresponding to the target workflow node of the workflow scenario, so as to call the objective function and return the result when the low-code application runs to the target workflow node; In the case where the preset business scenario includes a connector scenario, registering the target function as a target connector of the low-code application, so that when the low-code application calls the target connector, the target function is called and the result is returned; When the preset business scenario includes an API open scenario, the target function is added to the business logic set corresponding to the target endpoint of the low-code application so that the target function is called and the result is returned when an external application accesses the target endpoint.

6. The generation method according to claim 1, characterized in that: The generating of the low-code application based on the logical relationship between the preset business scenarios and the association relationship between the objective function and the newly added function object of the preset business scenario includes at least one of the following: In the case where the logical relationship between the preset business scenarios includes a preset sequential logic, a low-code application is generated based on the association relationship between the target function and the newly added function object of the preset business scenario according to the preset sequential logic; In the case where the logical relationship between the preset business scenarios includes preset parallel logic, a low-code application is generated based on the association relationship between the target function and the newly added function object of the preset business scenario by using the preset parallel logic; When the logical relationship between the preset business scenarios includes preset jump logic, a low-code application is generated based on the preset jump logic based on the association relationship between the target function and the newly added function object of the preset business scenario.

7. A low-code development platform, characterized in that: The low-code development platform provides an interactive interface corresponding to a preset business scenario, and the low-code development platform is used to implement the steps of the method for generating a low-code application as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which can be executed by a processor, and the processor implements the method for generating a low-code application as described in any one of claims 1 to 6.

Images