CN117931322A - Interface calling method and device of low-code platform and electronic equipment - Google Patents
Interface calling method and device of low-code platform and electronic equipment Download PDFInfo
- Publication number
- CN117931322A CN117931322A CN202311767007.1A CN202311767007A CN117931322A CN 117931322 A CN117931322 A CN 117931322A CN 202311767007 A CN202311767007 A CN 202311767007A CN 117931322 A CN117931322 A CN 117931322A
- Authority
- CN
- China
- Prior art keywords
- interface
- service
- parameter
- parameters
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000004044 response Effects 0.000 claims abstract description 16
- 238000012360 testing method Methods 0.000 claims description 57
- 238000012545 processing Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 12
- 230000001960 triggered effect Effects 0.000 claims description 9
- 230000005540 biological transmission Effects 0.000 claims description 4
- 238000013475 authorization Methods 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000006243 chemical reaction Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The disclosure provides an interface calling method of a low-code platform, relates to the technical field of computers, and particularly relates to an interface calling method and device of a low-code platform and electronic equipment. The specific implementation scheme is as follows: responding to a service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction, and acquiring preset interface calling parameters corresponding to the calling interface; generating a service parameter request according to the interface calling parameters and the service parameter acquisition instructions, and sending the service parameter request to a corresponding service server through the calling interface; and receiving the service parameters returned by the service server in response to the service parameter request.
Description
Technical Field
The disclosure relates to the field of computer technology, and in particular relates to a method and a device for calling an interface of a low-code platform and electronic equipment.
Background
For a service page generated by a low-code platform, the service page may have a service logic construction which depends on a third party service server to acquire service parameters, and a call interface provided by the third party service server is required to be called for the third party service server.
Disclosure of Invention
The disclosure provides an interface calling method and device for a low-code platform for solving at least one of the technical problems and electronic equipment.
According to an aspect of the present disclosure, there is provided an interface calling method of a low code platform, the method including:
Responding to a service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction, and acquiring preset interface calling parameters corresponding to the calling interface;
Generating a service parameter request according to the interface calling parameters and the service parameter acquisition instructions, and sending the service parameter request to a corresponding service server through the calling interface;
And receiving the service parameters returned by the service server in response to the service parameter request.
According to another aspect of the present disclosure, there is provided an interface calling apparatus of a low code platform, the apparatus including:
the parameter acquisition module is used for responding to the service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction and acquiring preset interface calling parameters corresponding to the calling interface;
The request generation module is used for generating a service parameter request according to the interface calling parameter and the service parameter acquisition instruction, and sending the service parameter request to a corresponding service server through the calling interface;
and the parameter receiving module is used for receiving the service parameters returned by the service server in response to the service parameter request.
According to another aspect of the present disclosure, there is provided an electronic device including:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described above.
According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method according to the above.
According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method according to the above.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a flow chart of an interface calling method of a low code platform according to a first embodiment of the present disclosure;
FIG. 2 is a flow chart of an interface calling method of a low code platform according to a second embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an exemplary call interface list;
FIG. 4 is a schematic diagram of an exemplary call interface configuration interface;
FIG. 5 is a schematic diagram of an exemplary call interface test page;
FIG. 6 is a schematic diagram of an interface calling device of a low code platform according to a third embodiment of the present disclosure;
fig. 7 is a block diagram of an electronic device for implementing the methods of embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Embodiments of the disclosure and features of embodiments may be combined with each other without conflict.
As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The interface invoking method of the low-code platform according to the present disclosure may be performed by an electronic device such as a terminal device or a server, where the terminal device may be a vehicle-mounted device, a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc., and the method may be implemented by a processor invoking computer readable program instructions stored in a memory. Or the interface calling method of the low code platform provided by the present disclosure may be executed by a server.
The call interface (API, application Programming Interface) is a predefined interface (e.g., function, HTTP interface) or a convention that refers to the engagement of different components of a software system to provide a set of routines that an application and developer can access based on certain software or hardware without having to access source code or understand the details of the internal operating mechanism.
In the disclosure of the first embodiment, referring to fig. 1, fig. 1 shows a flow chart of an interface calling method of a low code platform according to the first embodiment of the disclosure. The method may be performed by a backend of low code, the method comprising:
s101, responding to a service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction, and acquiring an interface calling parameter corresponding to a preset calling interface.
A plurality of calling interfaces corresponding to the service and parameters of the calling interfaces can be preconfigured according to the required service to generate a calling interface list, for example, as shown in fig. 3, fig. 3 shows a schematic diagram of an exemplary calling interface list; taking a call interface with an address (IP) query function in the figure as an example, if the service parameter obtaining instruction is an IP address query instruction, the user triggers the IP address query instruction, and the low-code platform determines an IP query call interface corresponding to the IP address query instruction and obtains interface call parameters (such as a request address and the like) corresponding to the IP query call interface.
S102, generating a service parameter request according to the interface calling parameters and the service parameter acquisition instructions, and sending the service parameter request to a corresponding service server through the calling interface.
The service server is a third party server for providing service parameters corresponding to the service parameter obtaining instruction, and the service parameters can be requested to the service server through a calling interface provided by the service server. The interface calling parameters are used for realizing the function of acquiring the service parameters corresponding to the service parameter acquisition instruction by calling the interface.
S103, receiving the service parameters returned by the service server in response to the service parameter request.
By the mode, the configuration of the calling interface can be simplified and managed, so that the low-code platform can call the calling interface provided by the service server through the interface calling parameter, and interaction is established with the service server, so that cross-domain interaction is realized, and service parameters can be requested from the service server.
In some examples, the interface call parameters further include: retry times; based on this, after S102, before S103, the method further includes:
Step one: under the condition that the service parameter request is overtime, the retry times in the interface call parameters are obtained, and the service parameter request is retransmitted through the call interface according to the preset sending interval time according to the retry times.
In some cases, the retry number of the call interface may be set when the call interface is configured, so that when a call failure may occur, the service parameter request is resent to the service server according to a preset sending time interval, and the resending number is limited, so as to avoid downtime. The preset transmission time interval may be set as needed, and is not limited herein.
In some examples, after S101, before S102, the method further comprises:
step one: responding to the additional parameter instruction, and acquiring an additional parameter carried by the additional parameter instruction;
step two: and adding the additional parameters into the service parameter acquisition instruction.
In the embodiment provided by the application, an append mode is further provided, referring to fig. 4, fig. 4 shows a schematic diagram of an exemplary call interface configuration interface. In some examples, the append mode may be turned on, setting append parameters, and thus flexibly adjusting the traffic parameters to be requested from the traffic server. The additional parameter may be any condition parameter that is desired to be added, such as: service parameter date to obtain service parameter in required date; and the service parameter numerical range is used for acquiring the service parameters of the required numerical range. It should be noted that, the setting of the additional parameter may be set when the interface configuration is invoked, or may be configured when the interface is invoked after S101 and before S102, so that the service parameter to be acquired may be modified at any time.
In the disclosure of the second embodiment, referring to fig. 2, fig. 2 shows a flow chart of an interface calling method of a low code platform according to the second embodiment of the disclosure. The method comprises the following steps:
s201, adding a calling interface and configuring interface calling parameters corresponding to the calling interface.
With continued reference to fig. 4, a plurality of call interfaces having responsive functions may be preconfigured to obtain corresponding service parameters, and the interface call parameters may include a plurality of parameters, for example, at least including: interface header and request address. The function of the calling interface to send a request to the service server can be realized by simply configuring the interface title (interface title displayed in the calling interface list) and the request address (address to receive the service parameter acquisition instruction). And a calling interface identifier is automatically generated for each calling interface, and the calling interface identifier is carried by the information of the return point of each calling interface, so that the calling interface received by the information received by the low-code platform can be rapidly identified, and the service distinction is convenient.
S202, responding to a call test instruction, obtaining test parameters, generating a test parameter request according to the test parameters, and sending the test parameter request to a corresponding service server through a call interface.
S203, receiving test result parameters returned by the service server in response to the test parameter request, and generating test result display information according to the test result parameters.
Referring to fig. 5, fig. 5 shows a schematic diagram of an exemplary call interface test page.
In the present disclosure, after the call interface is configured, the low code platform further provides a function of fast testing the call interface, where a test instruction may be called by starting from the page shown in fig. 5, a test parameter may be input in the request content portion, and a test parameter request may be generated according to the test parameter and the call interface call parameter, and sent to a corresponding service server through the call interface. And receiving test result parameters returned by the service server in response to the test parameter request, and generating test result display information according to the test result parameters, wherein the test result display information is used for displaying the test result on the interface test page, and the test result display information can comprise a request result and an operation log. The request result is used for displaying the test result parameters which are requested back, and the operation log comprises the parameter output and input of the related intermediate server in the process of sending the test parameter request to the process of receiving the test result parameters of the return point, so that the abnormality can be rapidly removed when the test fails. Based on this, after S202, before S203, further includes: and obtaining and recording the out-going and in-going parameters of the intermediate server.
S204, responding to a service parameter acquisition instruction triggered by a front-end service page received through a preset interface agent identifier, determining a calling interface corresponding to the service parameter instruction, and acquiring interface calling parameters corresponding to the preset calling interface.
The service parameter acquisition instruction is triggered by a front-end service page of the low-code platform.
The low-code platform is connected with a plurality of front-end service pages, a user starts a service parameter acquisition instruction through the front-end service pages (such as webpages) of the low-code platform, and in the method, the service parameter acquisition instructions triggered by the plurality of service pages are received to the rear end of the low-code platform through the same interface proxy identifier, so that the received service parameters are convenient to manage, and service differentiation is performed rapidly.
S204 is one implementation of S101, and S101 is not limited herein, and other implementations are also possible.
In some examples, the interface call parameters include: request address and request format.
S205, generating a service parameter request by the service parameter acquisition instruction according to the request format.
With continued reference to fig. 3, the request address is an address for receiving a service parameter request, the request format is a command format compliant with the service server, and the service parameter acquisition instruction is converted according to the request format, so as to generate a service parameter request, so that the service server can identify and process the service parameter request.
In one implementation, the interface call parameters further include: output parameters and output parameter configuration information. S205 includes the following sub-steps:
adding the output parameters into the service parameter acquisition instruction, and processing the service parameter acquisition instruction added with the output parameters according to the output parameter configuration information;
and step two, generating a service parameter request by the service parameter acquisition instruction according to the request format.
With continued reference to fig. 3, the service parameter in the figure is the output parameter, and the request configuration is the output parameter configuration. The output parameters are parameters which are wanted to be carried when sending the service parameter request, can be set in a self-defined way, and can also adopt default parameters; the output parameters are configured for processing of the output parameters, including, for example: outputting a conversion rule, outputting a parameter position, and the like, so that the service parameter obtaining instruction after adding the output parameter according to the output parameter configuration information in the first substep comprises: determining the carrying position of the output parameter through the position of the output parameter; and converting the service parameter acquisition instruction into a format conforming to the output conversion rule through the output conversion rule so as to ensure the validity of the output parameter.
In some examples, the interface call parameters further include: based on the authentication information, after S204, before S205, the method further comprises:
Step one, authentication information is added into a service parameter request.
With continued reference to fig. 3, the authentication is a setting column of authentication information in fig. 3, and some third party services need to be used to perform authentication, so that the authentication information can be set therein, and when the call interface is used, the authentication information is added to the service parameter request and sent to the service server, so that the service server performs identity authentication according to the authentication information, and the service parameter can be successfully invoked.
S206, sending the service parameter request to the request address corresponding to the service server through the calling interface.
It should be noted that S205-S206 (may also include step one) are one implementation of S102, and S102 is not limited herein.
In some examples, the interface call parameters further include: input parameters and input parameter configuration information.
S207, acquiring input parameters and input parameter configuration information corresponding to the calling interface, adding the input parameters into the service parameters, and processing the service parameters added with the input parameters according to the input parameter configuration information to obtain final service parameters.
With continued reference to fig. 3, the service parameter is input parameter, and the response configuration is input parameter configuration. The input parameters are parameters which are carried in the service parameters and returned to the front-end service page after the service parameters are received, and can be set by user definition or default parameters can be adopted; the input parameters are configured for processing of the input parameters, for example including: inputting the conversion rule, the input parameter position, and the like, so that processing the service parameter added with the input parameter according to the input parameter configuration information in S207, obtaining the final service parameter includes: determining an input parameter by the position of the input parameter, and adding the input parameter into the service parameter; and converting the business parameters into a format conforming to the input conversion rule through the output conversion rule so as to ensure the validity of the input parameters.
S207 is one implementation of S103, and S103 is also another implementation, which is not limited herein.
In the third embodiment of the disclosure, based on the same principle as fig. 1, fig. 6 shows an interface calling device of a low code platform provided in the third embodiment of the disclosure, where the device includes:
the parameter obtaining module 601 is configured to determine a call interface corresponding to the service parameter instruction in response to the service parameter obtaining instruction, and obtain an interface call parameter corresponding to a preset call interface;
The request generating module 602 is configured to generate a service parameter request according to the interface call parameter and the service parameter acquisition instruction, and send the service parameter request to a corresponding service server through the call interface;
The parameter receiving module 603 is configured to receive a service parameter returned by the service server in response to the service parameter request.
In some examples, the interface call parameters include: request address and request format;
The request generation module is used for generating a service parameter request according to the interface calling parameter and the service parameter acquisition instruction, and transmitting the service parameter request to the corresponding service server through the calling interface, and is specifically used for:
Generating a service parameter request by a service parameter acquisition instruction according to a request format;
And sending the service parameter request to a request address corresponding to the service server through the calling interface.
In some examples, the interface call parameters further include: output parameters and output parameter configuration information;
the request generation module is specifically configured to, when generating a service parameter request according to a request format by using a service parameter acquisition instruction:
adding the output parameters into the service parameter acquisition instruction, and processing the service parameter acquisition instruction added with the output parameters according to the output parameter configuration information;
and generating a service parameter request by the service parameter acquisition instruction according to the request format.
In some examples, the interface call parameters further include: authentication information;
The request generation module is further configured to:
and adding authentication information into the service parameter request.
In some examples, the interface call parameters further include: input parameters and input parameter configuration information;
the parameter receiving module is specifically configured to:
And acquiring input parameters and input parameter configuration information corresponding to the calling interface, adding the input parameters into the service parameters, and processing the service parameters added with the input parameters according to the input parameter configuration information to obtain final service parameters.
In some examples, the interface call parameters further include: retry times;
The apparatus further comprises:
And the retry module is used for acquiring the retry times in the interface call parameters under the condition that the service parameter request is overtime, and retransmitting the service parameter request through the call interface according to the preset transmission interval time according to the retry times.
In some examples, the apparatus further comprises:
The additional module is used for responding to the additional parameter instruction and acquiring additional parameters carried by the additional parameter instruction;
And the assembly module is used for adding the additional parameters into the service parameter acquisition instruction.
In some examples, the business parameter acquisition instruction is triggered by a front-end business page of the low code platform;
the parameter acquisition module is specifically used for:
responding to a service parameter acquisition instruction triggered by a front-end service page received through a preset interface proxy identifier, determining a calling interface corresponding to the service parameter instruction, and acquiring interface calling parameters corresponding to the preset calling interface.
In some examples, the apparatus further comprises:
the interface configuration module is used for adding a calling interface and configuring interface calling parameters corresponding to the calling interface;
The interface call parameters include at least: interface header and request address.
In some examples, the apparatus further comprises:
The test module is used for responding to the call test instruction, obtaining test parameters, generating a test parameter request according to the test parameters, and sending the test parameter request to the corresponding service server through the call interface;
The result generation module is used for receiving the test result parameters returned by the service server in response to the test parameter request and generating test result display information according to the test result parameters.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
Fig. 7 shows a schematic block diagram of an example electronic device 400 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 7, the apparatus 700 includes a computing unit 701 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 may also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in device 700 are connected to I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, etc.; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, an optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above, such as the interface call method of the low code platform. For example, in some embodiments, the interface call method of the low code platform may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 700 via ROM 702 and/or communication unit 709. When the computer program is loaded into the RAM 703 and executed by the computing unit 701, one or more steps of the interface call method of the low code platform described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured as an interface call method for a low code platform by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the disclosed aspects are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (23)
1. An interface call method of a low code platform, the method comprising:
Responding to a service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction, and acquiring preset interface calling parameters corresponding to the calling interface;
Generating a service parameter request according to the interface calling parameters and the service parameter acquisition instructions, and sending the service parameter request to a corresponding service server through the calling interface;
And receiving the service parameters returned by the service server in response to the service parameter request.
2. The method of claim 1, the interface call parameters comprising: request address and request format;
The step of generating a service parameter request according to the interface calling parameter and the service parameter obtaining instruction and sending the service parameter request to a corresponding service server through the calling interface comprises the following steps:
generating a service parameter request by the service parameter acquisition instruction according to the request format;
And sending the service parameter request to the request address corresponding to the service server through the calling interface.
3. The method of claim 2, the interface call parameter further comprising: output parameters and output parameter configuration information;
the generating a service parameter request according to the request format by the service parameter acquisition instruction includes:
adding the output parameters into the service parameter acquisition instruction, and processing the service parameter acquisition instruction added with the output parameters according to the output parameter configuration information;
and generating a service parameter request by the service parameter acquisition instruction according to the request format.
4. A method according to claim 2 or 3, the interface call parameters further comprising: authentication information;
after the service parameter obtaining instruction generates a service parameter request according to the request format, before the service parameter request is sent to the request address corresponding to the service server through the calling interface, the generating a service parameter request according to the interface calling parameter and the service parameter obtaining instruction, and sending the service parameter request to the corresponding service server through the calling interface, and the method further includes:
And adding the authentication and authorization information into the service parameter request.
5. The method of any of claims 1-4, the interface call parameters further comprising: input parameters and input parameter configuration information;
The receiving the service parameters returned by the service server in response to the service parameter request comprises the following steps:
And acquiring input parameters and input parameter configuration information corresponding to the calling interface, adding the input parameters into the service parameters, and processing the service parameters added with the input parameters according to the input parameter configuration information to obtain final service parameters.
6. The method of any of claims 1-5, the interface call parameters further comprising: retry times;
After generating a service parameter request according to the interface call parameter and the service parameter acquisition instruction and sending the service parameter request to a corresponding service server through the call interface, before receiving the service parameter returned by the service server in response to the service parameter request, the method further comprises:
And under the condition that the service parameter request is overtime, acquiring the retry times in the interface call parameters, and retransmitting the service parameter request through the call interface according to the preset transmission interval time according to the retry times.
7. The method according to any one of claims 1-6, wherein after the responding to the service parameter obtaining instruction, determining a call interface corresponding to the service parameter instruction, and obtaining an interface call parameter corresponding to a preset call interface, the method further comprises, before generating a service parameter request according to the interface call parameter and the service parameter obtaining instruction, and sending the service parameter request to a corresponding service server through the call interface:
Responding to the additional parameter instruction, and acquiring an additional parameter carried by the additional parameter instruction;
And adding an additional parameter into the service parameter acquisition instruction.
8. The method according to any one of claims 1-7, wherein the service parameter acquisition instruction is triggered by a front-end service page of the low-code platform;
The responding to the service parameter obtaining instruction, determining a calling interface corresponding to the service parameter instruction, and obtaining the preset interface calling parameter corresponding to the calling interface, comprising:
Responding to the service parameter acquisition instruction triggered by the front-end service page received through a preset interface proxy identifier, determining a calling interface corresponding to the service parameter instruction, and acquiring an interface calling parameter corresponding to the preset calling interface.
9. The method according to any one of claims 1-8, wherein before the responding to the service parameter obtaining instruction, determining a call interface corresponding to the service parameter instruction, and obtaining an interface call parameter corresponding to a preset call interface, the method further comprises:
Adding a calling interface and configuring interface calling parameters corresponding to the calling interface;
The interface calling parameters at least comprise: interface header and request address.
10. The method of claim 9, after the adding a call interface and configuring an interface call parameter corresponding to the call interface, the responding to a service parameter obtaining instruction, determining a call interface corresponding to a service parameter instruction, and before obtaining a preset interface call parameter corresponding to the call interface, the method further comprises:
Responding to a call test instruction, obtaining test parameters, generating a test parameter request according to the test parameters, and sending the test parameter request to a corresponding service server through the call interface;
And receiving test result parameters returned by the service server in response to the test parameter request, and generating test result display information according to the test result parameters.
11. An interface invocation apparatus of a low-code platform, the apparatus comprising:
the parameter acquisition module is used for responding to the service parameter acquisition instruction, determining a calling interface corresponding to the service parameter instruction and acquiring preset interface calling parameters corresponding to the calling interface;
The request generation module is used for generating a service parameter request according to the interface calling parameter and the service parameter acquisition instruction, and sending the service parameter request to a corresponding service server through the calling interface;
and the parameter receiving module is used for receiving the service parameters returned by the service server in response to the service parameter request.
12. The apparatus of claim 11, the interface call parameters comprising: request address and request format;
The request generation module is specifically configured to, when generating a service parameter request according to the interface call parameter and the service parameter acquisition instruction, and sending the service parameter request to a corresponding service server through the call interface:
generating a service parameter request by the service parameter acquisition instruction according to the request format;
And sending the service parameter request to the request address corresponding to the service server through the calling interface.
13. The apparatus of claim 12, the interface call parameters further comprising: output parameters and output parameter configuration information;
the request generation module is specifically configured to, when the service parameter obtaining instruction generates a service parameter request according to the request format:
adding the output parameters into the service parameter acquisition instruction, and processing the service parameter acquisition instruction added with the output parameters according to the output parameter configuration information;
and generating a service parameter request by the service parameter acquisition instruction according to the request format.
14. The apparatus of claim 12 or 13, the interface call parameters further comprising: authentication information;
The request generation module is further configured to:
And adding the authentication and authorization information into the service parameter request.
15. The apparatus of any of claims 11-14, the interface call parameters further comprising: input parameters and input parameter configuration information;
The parameter receiving module is specifically configured to:
And acquiring input parameters and input parameter configuration information corresponding to the calling interface, adding the input parameters into the service parameters, and processing the service parameters added with the input parameters according to the input parameter configuration information to obtain final service parameters.
16. The apparatus of any of claims 11-15, the interface call parameters further comprising: retry times;
The apparatus further comprises:
And the retry module is used for acquiring the retry times in the interface call parameters under the condition that the service parameter request is overtime, and retransmitting the service parameter request through the call interface according to the preset transmission interval time according to the retry times.
17. The apparatus according to any one of claims 11-16, further comprising:
The additional module is used for responding to the additional parameter instruction and acquiring additional parameters carried by the additional parameter instruction;
and the assembly module is used for adding the additional parameters into the service parameter acquisition instruction.
18. The apparatus according to any one of claims 11-17, wherein the service parameter acquisition instruction is triggered by a front-end service page of the low-code platform;
the parameter acquisition module is specifically configured to:
Responding to the service parameter acquisition instruction triggered by the front-end service page received through a preset interface proxy identifier, determining a calling interface corresponding to the service parameter instruction, and acquiring an interface calling parameter corresponding to the preset calling interface.
19. The apparatus according to any one of claims 11-18, the apparatus further comprising:
the interface configuration module is used for adding a calling interface and configuring interface calling parameters corresponding to the calling interface;
The interface calling parameters at least comprise: interface header and request address.
20. The apparatus of claim 19, the apparatus further comprising:
The test module is used for responding to the call test instruction, obtaining test parameters, generating a test parameter request according to the test parameters and sending the test parameter request to the corresponding service server through the call interface;
and the result generation module is used for receiving the test parameters returned by the service server in response to the test result parameter request and generating test result display information according to the test result parameters.
21. An electronic device, comprising:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.
22. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-10.
23. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311767007.1A CN117931322A (en) | 2023-12-20 | 2023-12-20 | Interface calling method and device of low-code platform and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311767007.1A CN117931322A (en) | 2023-12-20 | 2023-12-20 | Interface calling method and device of low-code platform and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117931322A true CN117931322A (en) | 2024-04-26 |
Family
ID=90767749
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311767007.1A Pending CN117931322A (en) | 2023-12-20 | 2023-12-20 | Interface calling method and device of low-code platform and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117931322A (en) |
-
2023
- 2023-12-20 CN CN202311767007.1A patent/CN117931322A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110838071B (en) | Policy data processing method, device and server | |
| CN108696899B (en) | SIP message transmitting and receiving method and transmitting and receiving device | |
| CN113076153B (en) | Interface calling method and device | |
| CN110704200A (en) | Method and device for converting call interface | |
| CN113821352A (en) | Remote service calling method and device | |
| CN114979295B (en) | Gateway management method and device | |
| CN112732547B (en) | Service testing method and device, storage medium and electronic equipment | |
| CN115934076B (en) | Cross-platform client micro-service providing device and method and electronic equipment | |
| CN114374703B (en) | Cloud mobile phone information acquisition method, device, equipment and storage medium | |
| CN113691937B (en) | Method for determining position information, cloud mobile phone and terminal equipment | |
| CN113905040B (en) | File transmission method, device, system, equipment and storage medium | |
| CN117931322A (en) | Interface calling method and device of low-code platform and electronic equipment | |
| CN112925623B (en) | Task processing method, device, electronic equipment and medium | |
| CN113760487B (en) | Service processing method and device | |
| CN114625458A (en) | Page data processing method and device, electronic equipment and storage medium | |
| CN113890906A (en) | Call forwarding method and device, electronic equipment and computer readable storage medium | |
| CN114448703B (en) | Request processing method, request processing device, electronic equipment and storage medium | |
| CN112651212A (en) | Method and terminal for remotely acquiring word stock | |
| CN113326060A (en) | Service request processing method, device and system and service configuration method and device | |
| CN112650601B (en) | Method, apparatus, device, storage medium, and program for opening applet across hosts | |
| CN115840604B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN113361235B (en) | HTML file generation method and device, electronic equipment and readable storage medium | |
| CN113726922B (en) | Network application layer connection protocol determining method and device and electronic equipment | |
| CN113472565B (en) | Method, apparatus, device and computer readable medium for expanding server function | |
| CN113535187B (en) | Service online method, service updating method and service providing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |