Low-code development method, device, system, server and storage medium

Abstract

The embodiments of the present application provide a low-code development method, device, system, server and storage medium. The low-code development method is applicable to a server, and the method includes: obtaining the front-end components and back-end components required for the business scenario to be developed; receiving a business scenario page from a client, the business scenario page is generated by the client after performing page layout of the front-end components according to the front-end display requirements of the business scenario; performing process layout on the front-end components and the back-end components to obtain the scenario process of the business scenario; determining a business scenario model composed of the business scenario page and the scenario process; sending the business scenario model to the client to coordinate the client to run the business scenario according to the business scenario model. The present application is used to improve the efficiency of code development.

Description

Technical Field

[0001] The present application relates to the field of code development technology. Specifically, the present application relates to a low-code development method, device, system, server and storage medium. Background Art

[0002] Low-code development platforms allow business personnel (non-technical personnel) to easily control the software development process, break free from the constraints of other high-level languages, and create a new way of human-computer interaction. This low-code development technology avoids the consistency issues between documents and codes during the maintenance process, simplifies the knowledge transfer and software engineering control process to the greatest extent, and provides great convenience for system maintenance. In response to changes in requirements, the system prototype can be modified directly through graphical tools. Secondly, low-code development technology itself does not provide functional implementation or business solutions. It only helps ecological partners provide a unified technical architecture and a minimalist development method. Users can choose a suitable system according to their needs on the low-code development platform or even completely customize a personalized system.

[0003] Currently, there are two common implementation methods for low-code development platforms: First, the front-end low-code development platform is more inclined towards front-end style components, and a simple application is formed by establishing multiple forms and processes. This platform is easy to learn, but can only handle simple processes and cannot implement complex functions and data associations. Second, the back-end low-code development platform is more inclined towards the construction of a modeling layer to implement complex functions and logic, as well as data interaction. It can meet various complex requirements, logical operations, etc. on the enterprise side, and has a faster code development speed. However, since some functions of this platform still need to be completed by writing code, the learning cost is very high. Therefore, existing low-code development platforms have certain problems in development efficiency. Summary of the Invention

[0004] In response to the shortcomings of existing methods, this application proposes a low-code development method, device, system, server and storage medium to improve code development efficiency.

[0005] In a first aspect, an embodiment of the present application provides a low-code development method applicable to a server, the method comprising:

[0006] Obtain the front-end and back-end components required for the business scenario to be developed;

[0007] Receiving a business scenario page from a client, the business scenario page being generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario;

[0008] Performing process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario;

[0009] Determine a business scenario model consisting of the business scenario page and the scenario process;

[0010] The business scenario model is sent to the client, so as to cooperate with the client to run the business scenario according to the business scenario model.

[0011] In some embodiments, before obtaining the front-end components and back-end components required for the business scenario, the following steps are included:

[0012] Get the preset front-end components and the preset back-end components;

[0013] The preset front-end component and the preset back-end component are published to the component library through component registration.

[0014] In some embodiments, receiving a business scenario page from a client includes:

[0015] Filter the front-end components required for the front-end display of the business scenario from the component library;

[0016] Sending the filtered front-end components to the client, so that the client performs page layout for the filtered front-end components according to the front-end display requirements of the business scenario, and sets specific scenario style parameters and event responses that meet the specific scenario interaction requirements for the filtered front-end components to generate the business scenario page;

[0017] Receive the business scenario page fed back by the client.

[0018] In some embodiments, orchestrating the front-end component and the back-end component to obtain the scenario process of the business scenario includes:

[0019] Select the required front-end components and back-end components from the component library according to the process of the business scenario;

[0020] Organizing the selected front-end components and back-end components according to the process to form multiple front-end processing processes and multiple back-end processing processes;

[0021] Connections are established between nodes in the front-end processing flow and the back-end processing flow to form a scenario flow of the business scenario.

[0022] In some embodiments, a node in a process flow includes a plurality of endpoints, and a connection between nodes in the process flow is established by the following steps, including:

[0023] Get the key attributes of each node and its endpoint in the processing flow;

[0024] Calculating the matching degree between each endpoint according to the key attributes;

[0025] A connection is established between the nodes where the two endpoints whose matching degree reaches a preset matching threshold are located.

[0026] In some embodiments, the business scenario page includes a main scenario page and multiple sub-scenario pages, and determining a business scenario model composed of the business scenario page and the scenario process includes:

[0027] The main scenario page and the sub-scenario page are arranged based on the scenario process to form the business scenario model.

[0028] In some embodiments, sending the business scenario model to the client to collaborate with the client to execute the business scenario according to the business scenario model includes:

[0029] Converting the business scenario model into a backend program flowchart so as to execute backend business logic according to the backend program flowchart, wherein the backend program flowchart includes the backend components and the logical execution sequence between the backend components; and

[0030] The business scenario model is sent to the client, so that the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart, wherein the front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components.

[0031] In some embodiments, obtaining a component from the component library is performed by the following steps, including:

[0032] Obtaining labels of components in the component library, where each component corresponds to a number of labels;

[0033] Determine the search conditions by selecting tags or writing expressions;

[0034] Components that meet the search criteria are obtained from the component library.

[0035] In a second aspect, an embodiment of the present application provides a low-code development method applicable to a client, the method comprising:

[0036] Receive the front-end components required for the business scenarios to be developed from the server;

[0037] Performing page layout on the front-end components according to the front-end presentation requirements of the business scenario, generating a business scenario page and feeding it back to the server, so that the server can perform process layout on the front-end components and the back-end components required by the business scenario, obtain the scenario process of the business scenario, and determine a business scenario model consisting of the business scenario page and the scenario process;

[0038] Receive the business scenario model sent by the server, and cooperate with the server to run the business scenario according to the business scenario model.

[0039] In a third aspect, the embodiments of the present application provide a low-code development system, server, and client;

[0040] The server obtains the front-end components and back-end components required for the business scenario to be developed;

[0041] The client receives the front-end component from the server, arranges the front-end component into pages according to the front-end display requirements of the business scenario, generates a business scenario page, and sends the business scenario page to the server;

[0042] The server receives the business scenario page, performs process orchestration on the front-end component and the back-end component, obtains a scenario process of the business scenario, determines a business scenario model composed of the business scenario page and the scenario process, and sends the business scenario model to the client;

[0043] The server and the client collaboratively run the business scenario according to the business scenario model.

[0044] In a fourth aspect, an embodiment of the present application provides a low-code development device, including:

[0045] The component acquisition module is used to obtain the front-end components and back-end components required for the business scenario to be developed;

[0046] A page layout module is used to receive a business scenario page from a client, wherein the business scenario page is generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario;

[0047] A process orchestration module, configured to perform process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario;

[0048] A scenario construction module, used to determine a business scenario model consisting of the business scenario page and the scenario process;

[0049] The scenario running module is used to send the business scenario model to the client to cooperate with the client to run the business scenario according to the business scenario model.

[0050] In a fifth aspect, an embodiment of the present application provides a server, including:

[0051] processor; and

[0052] The memory is communicatively connected to the processor and is configured to store machine-readable instructions. When the machine-readable instructions are executed by the processor, they implement the low-code development method described in the above embodiment.

[0053] In the sixth aspect, an embodiment of the present application provides a computer-readable storage medium, a computer-readable storage medium, characterized in that the computer storage medium is used to store computer instructions, and when the computer instructions are run on a computer, the computer can execute the low-code development method described in the above embodiment.

[0054] The low-code development method, device, system, server, and storage medium provided in the embodiments of the present application have the following beneficial technical effects:

[0055] The front-end components and back-end components required for the business scenario to be developed are obtained through the server, and the business scenario page from the client is received. The business scenario page is generated by the client after the front-end components are arranged according to the front-end display requirements of the business scenario. Then, the front-end components and the back-end components are arranged into processes to obtain the scenario process of the business scenario, and then the business scenario model composed of the business scenario page and the scenario process is determined, so as to send the business scenario model to the client to coordinate the client to run the business scenario according to the business scenario model. In this way, the front-end and back-end development are integrated, which can realize the processing of complex business scenarios while improving the flexibility of scenarioization, simple operation, greatly reducing the learning cost, and a wide range of applications. The use of a unified process orchestration method further improves the efficiency of low-code development, which is used to solve the problem of low development efficiency of low-code development platforms in the existing technology.

[0056] Additional aspects and advantages of the present application will be given in part in the following description, which will become apparent from the following description, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0058] Figure 1 A schematic diagram of the structure of a low-code development system provided in an embodiment of the present application;

[0059] Figure 2 A flowchart of a low-code development method for a server provided in an embodiment of the present application;

[0060] Figure 3 A flowchart of a low-code development method applicable to a client provided in an embodiment of the present application;

[0061] Figure 4 A schematic diagram of the low-code development system structure and processing flow provided in an embodiment of the present application;

[0062] Figure 5 A schematic diagram of the structure of a low-code development device provided in an embodiment of the present application;

[0063] Figure 6 A schematic diagram of the structure of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and are not to be construed as limiting the present application.

[0065] It will be understood by those skilled in the art that, unless expressly stated otherwise, the singular forms "a", "an", "said" and "the" used herein may also include the plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be intermediate elements. In addition, "connected" or "coupled" as used herein may include wireless connections or wireless couplings. The term "and / or" used herein includes all or any units and all combinations of one or more associated listed items.

[0066] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0067] See also Figure 1, which is a structural diagram of a low-code development system provided in an embodiment of the present application, the low-code development system includes: a server 11 and a client 12. The server 11 and the client 12 are connected via a wired network or a wireless network, wherein the wired network includes but is not limited to: a universal serial bus, and the wireless network includes but is not limited to: WiFi, Bluetooth, etc.

[0068] based on Figure 1 The low-code development system shown, the low-code development method in the embodiment of the present application is based on the code development performed by the low-code development system. Specifically, a business scenario is first determined, and the server 11 obtains the front-end components and back-end components required for the business scenario. The client 12 receives the front-end components sent by the server 11, and arranges the pages of the front-end components according to the front-end display requirements of the business scenario to generate a business scenario page. At the same time, the server 11 arranges the processes of the front-end components and the back-end components according to the process of the business scenario to form a scenario process of the business scenario, and then receives the business scenario page sent by the client 12, and determines the business scenario model composed of the business scenario page and the scenario process. The server 11 sends the business scenario model to the client 12, so that the server 11 and the client 12 can collaboratively run the business scenario according to the business scenario model.

[0069] The low-code development system provided in the embodiment of the present application integrates the front-end and back-end code development, which can realize the processing of complex business scenarios while improving the scenario flexibility. It is easy to operate, greatly reduces the learning cost, has a wide range of applications, and uses a unified process orchestration method to further improve the low-code development efficiency, so as to solve the problem of low development efficiency of low-code development platforms in the existing technology.

[0070] See also Figure 2 , which is a flow chart of a low-code development method applicable to a server provided in an embodiment of the present application. The method is applicable to server 11 and includes steps S201 to S205.

[0071] S201. Obtain the front-end components and back-end components required for the business scenario to be developed.

[0072] It should be noted that the front-end component can be exemplified as each independent visual / interactive area on the front-end page, and its code includes but is not limited to structural code, logic code and style code. Each component has independent logical functions, so components can be freely combined to form a functionally complete interface. The back-end component is an executable code with specific logical operations, such as storage, resource orchestration, etc. Preferably, the front-end components and the back-end components have strong reusability during the code development process, with low operational difficulty, thereby improving code development efficiency.

[0073] In some embodiments, before obtaining the front-end components and back-end components required for the business scenario, the following steps are included:

[0074] Get the preset front-end components and the preset back-end components;

[0075] The preset front-end component and the preset back-end component are published to the component library through component registration.

[0076] In this embodiment, the preset front-end component is a front-end component that meets the component development specification, and the preset back-end component is a back-end component that meets the component development specification, and then the preset front-end component and the preset back-end component are published to the component library through component registration. At the same time, after the component registration is completed, the relevant metadata is saved to the system, and the metadata includes but is not limited to the input parameters, output parameters and parameter definitions of the component interface, and then the server 11 manages the metadata of the component. In addition, during the component registration process, the server 11 obtains the component label and then manages the label. In addition, the component library manages the entire life cycle of the saved front-end components and back-end components, and provides a component query function for the page layout and process layout operations of the front-end and back-end in subsequent steps.

[0077] In a preferred embodiment, the steps of obtaining a component from the component library include:

[0078] Obtaining labels of components in the component library, where each component corresponds to a number of labels;

[0079] Determine the search conditions by selecting tags or writing expressions;

[0080] Components that meet the search criteria are obtained from the component library.

[0081] Exemplarily, when obtaining the front-end components and back-end components required for the business scenario, the target component required for the business scenario can be determined by writing an expression using the name, function and other information of the target component to determine the search conditions, and then generating a conditional expression according to specific expression rules to parse the conditional expression, such as extracting keywords, semantic analysis, etc., and converting it into the final query condition, so as to obtain the target component that meets the query condition from the component library. In another optional embodiment, the search condition can be determined by selecting the label of the target component. For example, if the label of component 1 includes label a, label b and label c, at least one of label a, label b and label c can be selected to combine into a search condition. Among them, the component label of the present application can represent the content type of the component, and can also represent the function of the component, which is not limited here. Therefore, this embodiment can improve the accuracy and operation speed of component retrieval during the agent development process by using the component retrieval method of labels, further improve the subsequent editing efficiency and accuracy, and thus improve the code development efficiency.

[0082] S202: Receive a business scenario page from a client, where the business scenario page is generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario.

[0083] In some embodiments, receiving a business scenario page from a client includes:

[0084] Filter the front-end components required for the front-end display of the business scenario from the component library;

[0085] Sending the filtered front-end components to the client, so that the client performs page layout for the filtered front-end components according to the front-end display requirements of the business scenario, and sets specific scenario style parameters and event responses that meet the specific scenario interaction requirements for the filtered front-end components to generate the business scenario page;

[0086] Receive the business scenario page fed back by the client.

[0087] In this embodiment, the server 11 retrieves and filters out the front-end components required for the front-end display from the front-end components required for the business scenario stored in the component library, and sends the filtered front-end components to the client 12. The client 12 performs page layout on the front-end components. Specifically, the client layouts the filtered front-end components on the page according to the front-end display requirements, sets specific scene style parameters for the components to meet the style required by the business scenario, and sets event response settings for the components to meet the scene interaction requirements, thereby obtaining a visual main scene page and multiple sub-scene pages. Therefore, this embodiment realizes page layout through the layout of front-end components, reducing the difficulty of layout.

[0088] S203: Perform process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario.

[0089] In some embodiments, orchestrating the front-end component and the back-end component to obtain the scenario process of the business scenario includes:

[0090] Select the required front-end components and back-end components from the component library according to the process of the business scenario;

[0091] Organizing the selected front-end components and back-end components according to the process to form multiple front-end processing processes and multiple back-end processing processes;

[0092] Connections are established between nodes in the front-end processing flow and the back-end processing flow to form a scenario flow of the business scenario.

[0093] In this embodiment, the server 11 retrieves and filters the front-end components and back-end components required for the overall process of the business scenario from the front-end components and back-end components required for the business scenario stored in the component library. Furthermore, since the components have independent functions, the filtered front-end components and back-end components are orchestrated according to the overall process of the business scenario, resulting in a number of front-end processing flows organized by multiple front-end components, and a number of back-end processing flows organized by multiple back-end components. Furthermore, the front-end processing flows and back-end processing flows are logically unified and integrated, specifically by establishing connections between the nodes in each flow according to the overall process of the business scenario to form the scenario flow of the business scenario.

[0094] Therefore, this embodiment unifies and integrates front-end development and back-end development through process orchestration, and uses an organizational method similar to a program flowchart to link the nodes of the front-end processing flow and the back-end processing flow to form a logical flow of executable code for executing the business scenario, realizing various business logics such as CRUD, data processing, processing, conversion and complex business scenario processing, while being simple to operate.

[0095] In a specific embodiment, the nodes in the processing flow include a plurality of endpoints, and two nodes are connected via the endpoints. The connection between the nodes in the processing flow is established by the following steps, including:

[0096] Get the key attributes of each node and its endpoint in the processing flow;

[0097] Calculating the matching degree between each endpoint according to the key attributes;

[0098] A connection is established between the nodes where the two endpoints whose matching degree reaches a preset matching threshold are located.

[0099] In this embodiment, the key attributes of a node endpoint can be key field information for a node in one of its logical directions. Furthermore, based on the key attributes of the endpoints, the logical flow of the connection path between the endpoints is determined, and the matching degree between the endpoints is calculated. Consequently, two endpoints whose matching degree reaches a preset matching threshold are connected. Therefore, this embodiment uses automatic matching to establish connections between process orchestration nodes, improving orchestration efficiency and reducing error rates.

[0100] S204: Determine a business scenario model consisting of the business scenario page and the scenario process.

[0101] In one embodiment, the business scenario page includes a main scenario page and multiple sub-scenario pages, and determining the business scenario model composed of the business scenario page and the scenario process includes:

[0102] The main scenario page and the sub-scenario page are arranged based on the scenario process to form the business scenario model.

[0103] Based on the above embodiment, in this embodiment, the server receives a business scenario page (i.e., a page layout result) sent by the client. The business scenario page includes a main scenario page and multiple sub-scenario pages. Furthermore, the sub-scenario pages in each page layout result are combined to form a sub-scenario. Each sub-scenario is uniformly arranged using the main scenario page and the scenario flow to obtain a business scenario model (i.e., a scenario layout result). The client can then render the business scenario interface based on the business scenario model and coordinate with the server to respond to events.

[0104] S205: Send the business scenario model to the client to collaborate with the client to run the business scenario according to the business scenario model.

[0105] In one embodiment, sending the business scenario model to the client to collaborate with the client to execute the business scenario according to the business scenario model includes:

[0106] Converting the business scenario model into a backend program flowchart so as to execute backend business logic according to the backend program flowchart, wherein the backend program flowchart includes the backend components and the logical execution sequence between the backend components; and

[0107] The business scenario model is sent to the client, so that the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart, wherein the front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components.

[0108] In this embodiment, the relevant scenario processes in the constructed business scenario model are deployed in the system. Specifically, server 11 sends the business scenario model to client 12, so that when client 12 loads the business scenario front-end runtime, it converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart. More specifically, the front-end program flowchart includes front-end components and the logical connections between them. This logical connection relationship represents the logical execution order of the front-end program flowchart. Based on the logical connections in the front-end program flowchart, front-end executable code is generated to execute the front-end program flowchart, so that the front-end business logic is executed according to the front-end executable code.

[0109] Similarly, when server 11 loads the business scenario backend runtime, it converts the business scenario model into a backend program flowchart to execute the backend business logic according to the backend program flowchart. More specifically, the backend program flowchart includes backend components and the logical connections between them. This logical connection relationship represents the logical execution order of the backend program flowchart. Based on the logical connections in the backend program flowchart, the frontend executable code for executing the backend program flowchart is generated, so that the backend business logic is executed according to the backend executable code.

[0110] The low-code development method provided in the embodiment of the present application obtains the front-end components and back-end components required for the business scenario to be developed through the server, and receives the business scenario page from the client. The business scenario page is generated by the client after performing page arrangement of the front-end components according to the front-end display requirements of the business scenario, and then the front-end components and the back-end components are process-orchestrated to obtain the scenario process of the business scenario, and then the business scenario model composed of the business scenario page and the scenario process is determined, so as to send the business scenario model to the client to coordinate the client to run the business scenario according to the business scenario model. In this way, the front-end and back-end development are integrated, which can realize the processing of complex business scenarios while improving the flexibility of scenarioization, simple operation, greatly reducing the learning cost, and a wide range of applications. The use of a unified process orchestration method further improves the efficiency of low-code development, which is used to solve the problem of low development efficiency of low-code development platforms in the existing technology.

[0111] See also Figure 3 , which is a flowchart of a low-code development method applicable to a client provided in an embodiment of the present application, including steps S301 to S303

[0112] S301: Receive front-end components required for the business scenario to be developed from the server.

[0113] S302. Perform page layout on the front-end components according to the front-end display requirements of the business scenario, generate a business scenario page and feed it back to the server, so that the server can perform process layout on the front-end components and the back-end components required for the business scenario, obtain the scenario process of the business scenario, and determine the business scenario model composed of the business scenario page and the scenario process.

[0114] S303: Receive the business scenario model sent by the server, and collaborate with the server to run the business scenario according to the business scenario model.

[0115] In one embodiment, step S303 of the method includes:

[0116] Receive the business scenario model sent by the server, convert the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart, and the front-end program flowchart includes the front-end components and the logical execution order between the front-end components.

[0117] The low-code development method provided in the embodiment of the present application receives the front-end components required for the business scenario to be developed from the server through the client, arranges the pages of the front-end components according to the front-end display requirements of the business scenario, and generates a business scenario page, so that the server can arrange the processes of the front-end components and the back-end components required for the business scenario, obtain the scenario process of the business scenario, and determine the business scenario model composed of the business scenario page and the scenario process, receive the business scenario model sent by the server, and cooperate with the server to run the business scenario according to the business scenario model. In this way, the front-end and back-end development are integrated, which can realize the processing of complex business scenarios while improving the flexibility of scenarioization, simple operation, greatly reducing the learning cost, and a wide range of applications. The use of a unified process orchestration method further improves the efficiency of low-code development, which is used to solve the problem of low development efficiency of low-code development platforms in the existing technology.

[0118] For example, see Figure 4 , which is a schematic diagram of the low-code development system structure and processing flow provided by an embodiment of the present application. The functional modules of the server 11 include a component library 113, a component registration module 111, a process orchestration module 114, a metadata management module 112, a scenario construction module 115, a scenario publishing module 116, and a backend executor 117. The functional modules of the client 12 include a page orchestration module 121 and a frontend executor 122. The server 11 is in communication with the client 12.

[0119] Step 1: Register the preset front-end and back-end components developed according to the component specification on the component registration module 111. After the component registration is completed, the relevant metadata is saved to the metadata management module 112 so that the metadata management module 112 can manage the metadata.

[0120] Step 2: The component registration module 111 publishes the registered preset front-end and back-end components to the component library 113.

[0121] In step 3, the server 11 selects the front-end components required for the front-end display of the business scenario from the component library 113, and sends the selected front-end components to the page layout module 121 of the client 12, so that the page layout module 121 layouts the front-end components according to the front-end display requirements of the business scenario.

[0122] In step 4, the server 11 selects required front-end components and back-end components from the component library 113 according to the process of the business scenario. The process orchestration module 114 orchestrates the selected front-end components and back-end components to obtain the scenario process of the business scenario.

[0123] Step 5: The page layout module 121 sends the business scenario page to the scenario construction module 115 of the server 11 .

[0124] In step 6, the process arrangement module 114 sends the scenario process to the scenario construction module 115 so that the scenario construction module 115 can determine the business scenario model composed of the business scenario page and the scenario process.

[0125] Step 7: The scenario construction module 115 publishes the business scenario model to the scenario publishing module 116 .

[0126] In step 8, the scenario publishing module deploys the relevant processes into the system according to the business scenario model, and sends the business scenario model to the front-end executor 122 of the client 12, so that the front-end executor 122 is responsible for loading the scenario front-end runtime and converting the business scenario model into a front-end program flowchart, thereby executing the front-end business logic according to the front-end program flowchart.

[0127] Step 9: The scenario publishing module 116 sends the business scenario model to the backend executor 117.

[0128] In step 10, the metadata management module 112 sends the relevant metadata to the backend executor 117, so that the backend executor 117 is responsible for loading the scenario backend runtime and converting the business scenario model into a backend program flowchart, thereby executing the backend business logic according to the backend program flowchart.

[0129] Exemplarily, and more specifically, the low-code development method is applied to scenario A. The server selects the front-end components a11, a12, and a13 required for the front-end page display of scenario A from the component library. For example, the front-end components required for the front-end display in the information search scenario include, but are not limited to, text editing components and data list display components. The client receives the above-mentioned front-end components and drags the front-end components a11, a12, and a13 according to the preset page editing rules to organize them into the scenario A page displayed on the front-end of scenario A. Furthermore, the server selects the front-end components a21, a22, and a23 required to implement the logical process of scenario A, as well as the back-end components b1, b2, and b3 from the component library. First, according to the process of scenario A, the front-end components a21, a22, and a23 are organized into multiple front-end processing flows, such as a21-a22-a23. Similarly, the back-end components b1, b2, and b3 are organized into multiple back-end processing flows, such as b1-b2 and b2-b3. Next, the nodes in the front-end and back-end processing flows are connected to form the scenario flow for Scenario A, such as a21-b1-b2-a22-b2-b3-a23. Thus, the Scenario A page and its scenario flow constitute the Scenario A model. Furthermore, the server sends the Scenario A model to the client's front-end executor, which collaborates with the client to run the Scenario A model. The client executes the front-end page display and the front-end logic of Scenario A, while the server executes the back-end logic of Scenario A.

[0130] See also Figure 5 , is a structural diagram of a low-code development device provided in an embodiment of the present application, the device is applicable to a server 11, and includes:

[0131] Component acquisition module 501, used to obtain the front-end components and back-end components required for the business scenario to be developed;

[0132] The page layout module 502 is used to receive a business scenario page from a client, wherein the business scenario page is generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario;

[0133] A process orchestration module 503 is configured to perform process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario;

[0134] A scenario construction module 504 is used to determine a business scenario model consisting of the business scenario page and the scenario process;

[0135] The scenario running module 505 is configured to send the business scenario model to the client to cooperate with the client to run the business scenario according to the business scenario model.

[0136] In one embodiment, the apparatus further comprises:

[0137] A preset component acquisition unit, used to acquire a preset front-end component and a preset back-end component;

[0138] The component registration unit is used to publish the preset front-end component and the preset back-end component to the component library through component registration.

[0139] In one embodiment, the page layout module 502 includes:

[0140] A front-end display component screening unit, configured to screen the front-end components required for the front-end display of the business scenario from the component library;

[0141] A front-end component sending unit is configured to send the filtered front-end components to the client, so that the client performs page layout for the filtered front-end components according to the front-end display requirements of the business scenario, and sets specific scenario style parameters and event responses that meet the specific scenario interaction requirements for the filtered front-end components to generate the business scenario page;

[0142] A page receiving unit is used to receive the business scenario page fed back by the client.

[0143] In one embodiment, the process orchestration module 503 includes:

[0144] A process component screening unit, configured to select required front-end components and back-end components from the component library according to the process of the business scenario;

[0145] A processing flow generation unit, configured to organize the selected front-end components and back-end components according to the flow to form a plurality of front-end processing flows and a plurality of back-end processing flows;

[0146] The process node connection unit is used to establish connections between nodes in the front-end processing process and the back-end processing process to form a scenario process of the business scenario.

[0147] In one embodiment, the process node connection unit includes:

[0148] A key attribute acquisition unit is used to acquire key attributes of nodes and endpoints in each processing flow;

[0149] A matching degree calculation unit, configured to calculate the matching degree between the endpoints based on the key attributes;

[0150] The node connection unit is used to establish a connection between the nodes where the two endpoints whose matching degree reaches a preset matching threshold are located.

[0151] In one embodiment, the scene construction module 504 includes:

[0152] A scenario arrangement unit is used to arrange the main scenario page and the sub-scenario page based on the scenario process to form the business scenario model.

[0153] In one embodiment, the scenario running module 505 includes:

[0154] a backend operation unit, configured to convert the business scenario model into a backend program flowchart, so as to execute the backend business logic according to the backend program flowchart, wherein the backend program flowchart includes the backend components and the logical execution sequence between the backend components; and

[0155] A front-end running unit is used to send the business scenario model to the client, so that the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart, and the front-end program flowchart includes the front-end components and the logical execution order between the front-end components.

[0156] In one embodiment, the apparatus further comprises:

[0157] A component label acquisition unit, configured to acquire labels of components in the component library, wherein each component corresponds to a plurality of labels;

[0158] A search condition determination unit, used to determine the search condition by selecting a tag or writing an expression;

[0159] The component query unit is used to obtain components that meet the search conditions from the component library.

[0160] The low-code development device provided in the embodiment of the present application is used to execute the steps of low-code development described in the above embodiment. The working principles and beneficial effects of the two correspond one to one, so they will not be repeated here.

[0161] Based on the same inventive concept, an embodiment of the present application provides a server, which includes: a memory and a processor.

[0162] The memory is communicatively connected to the processor.

[0163] At least one computer program, stored in a memory, is used to implement various optional implementations of the low-code development method provided in the embodiments of the present application when executed by a processor.

[0164] A structural diagram of a server provided in an embodiment of the present application, wherein an embodiment of the present application provides a server 11, which includes: a memory and a processor; at least one program stored in the memory, for being executed by the processor, which can achieve, compared with the prior art: integrating front-end and back-end development, which can realize complex business scenario processing while improving scenario flexibility, is easy to operate, greatly reduces learning costs, has a wide range of applications, and uses a unified process orchestration method to further improve the efficiency of low-code development, so as to solve the problem of low development efficiency of low-code development platforms in the prior art.

[0165] In an optional embodiment, a server is provided, such as Figure 6 As shown, Figure 6 The server 11 shown includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the server 11 may also include a transceiver 4004, which can be used for data exchange between the server 11 and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the number of transceivers 4004 is not limited to one, and the structure of the server 11 does not constitute a limitation on the embodiments of the present application.

[0166] Processor 4001 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor.

[0167] Bus 4002 may include a path for transmitting information between the above components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. Bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0168] The memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0169] The memory 4003 is used to store the application code (computer program) for executing the solution of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the application code stored in the memory 4003 to implement the content shown in the above method embodiment.

[0170] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer-readable storage medium is run on a computer, the computer can execute the corresponding contents of the aforementioned method embodiment.

[0171] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0172] The above description is only a partial implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A low-code development method, characterized in that: Applicable to a server, the method includes: Obtain the front-end and back-end components required for the business scenario to be developed; Receiving a business scenario page from a client, the business scenario page being generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario; Performing process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario; Determine a business scenario model consisting of the business scenario page and the scenario process; Sending the business scenario model to the front-end executor of the client to cooperate with the client to run the business scenario according to the business scenario model; The sending of the business scenario model to the front-end executor of the client to cooperate with the client to run the business scenario according to the business scenario model includes: The business scenario model is converted into a backend program flowchart by a backend executor of the server, so as to execute backend business logic according to the backend program flowchart, wherein the backend program flowchart includes the backend components and the logical execution sequence between the backend components, and the backend executor includes backend processing logic, which includes various data processing, logical operations and IO operations; and The business scenario model is sent to the front-end executor of the client, so that the front-end executor of the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart. The front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components. The front-end executor includes front-end functions, and the front-end functions include page layout, rendering, page jump and data processing.

2. The low-code development method according to claim 1, characterized in that: Before obtaining the front-end and back-end components required for the business scenario, including: Get the preset front-end components and the preset back-end components; The preset front-end component and the preset back-end component are published to the component library through component registration.

3. The low-code development method according to claim 2, characterized in that: The receiving of the business scenario page from the client includes: Filter the front-end components required for the front-end display of the business scenario from the component library; Sending the filtered front-end components to the client, so that the client performs page layout for the filtered front-end components according to the front-end display requirements of the business scenario, and sets specific scenario style parameters and event responses that meet the specific scenario interaction requirements for the filtered front-end components to generate the business scenario page; Receive the business scenario page fed back by the client.

4. The low-code development method according to claim 2, characterized in that The process orchestration of the front-end component and the back-end component to obtain the scenario process of the business scenario includes: Select the required front-end components and back-end components from the component library according to the process of the business scenario; Organizing the selected front-end components and back-end components according to the process to form multiple front-end processing processes and multiple back-end processing processes; Connections are established between nodes in the front-end processing flow and the back-end processing flow to form a scenario flow of the business scenario.

5. The low-code development method according to claim 4, characterized in that: The nodes in the process flow include several endpoints. The connections between the nodes in the process flow are established through the following steps, including: Get the key attributes of each node and its endpoint in the processing flow; Calculating the matching degree between each endpoint according to the key attributes; A connection is established between the nodes where the two endpoints whose matching degree reaches a preset matching threshold are located.

6. The low-code development method according to claim 3, characterized in that The business scenario page includes a main scenario page and multiple sub-scenario pages, and determining the business scenario model composed of the business scenario page and the scenario process includes: The main scenario page and the sub-scenario page are arranged based on the scenario process to form the business scenario model.

7. The low-code development method according to claim 2, characterized in that: Obtaining a component from the component library through the following steps includes: Obtaining labels of components in the component library, where each component corresponds to a number of labels; Determine the search conditions by selecting tags or writing expressions; Components that meet the search criteria are obtained from the component library.

8. A low-code development method, characterized in that: Applicable to the client, the method includes: Receive the front-end components required for the business scenarios to be developed from the server; Performing page layout on the front-end components according to the front-end presentation requirements of the business scenario, generating a business scenario page and feeding it back to the server, so that the server can perform process layout on the front-end components and the back-end components required by the business scenario, obtain the scenario process of the business scenario, and determine a business scenario model consisting of the business scenario page and the scenario process; The business scenario model sent by the server is received by the front-end executor of the client, so that the front-end executor of the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart. The front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components, and cooperates with the server to run the business scenario according to the business scenario model. The front-end executor includes front-end functions, and the front-end functions include page layout, rendering, page jump and data processing.

9. A low-code development system, characterized in that: include: Server and client; The server obtains the front-end components and back-end components required for the business scenario to be developed; The client receives the front-end component from the server, arranges the front-end component into pages according to the front-end display requirements of the business scenario, generates a business scenario page, and sends the business scenario page to the server; The server receives the business scenario page, performs process orchestration on the front-end component and the back-end component, obtains a scenario process of the business scenario, determines a business scenario model composed of the business scenario page and the scenario process, and sends the business scenario model to the front-end executor of the client; The server and the client collaboratively run the business scenario according to the business scenario model; The sending the business scenario model to the client includes: The server sends the business scenario model to the front-end executor of the client, so that the front-end executor of the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart. The front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components. The front-end executor includes front-end functions, and the front-end functions include page layout, rendering, page jump and data processing.

10. A low-code development device, characterized in that: include: The component acquisition module is used to obtain the front-end components and back-end components required for the business scenario to be developed; A page layout module is used to receive a business scenario page from a client, wherein the business scenario page is generated by the client after performing page layout on the front-end component according to the front-end display requirements of the business scenario; A process orchestration module, configured to perform process orchestration on the front-end component and the back-end component to obtain a scenario process of the business scenario; A scenario construction module, used to determine a business scenario model consisting of the business scenario page and the scenario process; A scenario running module, configured to send the business scenario model to the front-end executor of the client, so as to cooperate with the client to run the business scenario according to the business scenario model; The scenario running module is specifically used to: The business scenario model is converted into a backend program flowchart by a backend executor of the server, so as to execute the backend business logic according to the backend program flowchart, wherein the backend program flowchart includes the backend components and the logical execution sequence between the backend components, and the backend executor includes backend processing logic, which includes various data processing, logical operations and IO operations; and The business scenario model is sent to the front-end executor of the client, so that the front-end executor of the client converts the business scenario model into a front-end program flowchart to execute the front-end business logic according to the front-end program flowchart. The front-end program flowchart includes the front-end components and the logical execution sequence between the front-end components. The front-end executor includes front-end functions, and the front-end functions include page layout, rendering, page jump and data processing.

11. A server, characterized in that: include: processor; as well as A memory, communicatively connected to the processor, is configured to store machine-readable instructions, which, when executed by the processor, implement the low-code development method as described in any one of claims 1-7.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium is used to store computer instructions. When the computer instructions are executed on a computer, the computer can execute the low-code development method described in any one of claims 1 to 7.

Images