CN112926008B - Method, device, electronic equipment and storage medium for generating form page - Google Patents

Abstract

The invention discloses a method for generating a form page, relates to the technical field of artificial intelligence, and further relates to the technical field of cloud computing. The specific implementation scheme is as follows: acquiring a plurality of page components for generating a form page; calling at least one target page component in the plurality of page components based on type information, text information and layout information contained in the target form page to be generated; and generating a target form page according to the call result of at least one target page component in the plurality of page components. An apparatus, an electronic device and a storage medium for generating the form page are also disclosed.

Description

Method, device, electronic device and storage medium for generating form page

Technical field

The present disclosure relates to the field of artificial intelligence technology, further relates to the field of cloud computing technology, and in particular, to a method, device, electronic device and storage medium for generating a form page.

Background technique

Today, cloud computing technology is developing rapidly, and more and more services can be provided through cloud computing products. When users purchase cloud computing products, they need to provide information related to cloud computing products to the service provider. Typically, the service provider can present a form page to the user, and the user provides such information by filling in the form page. A dedicated form page needs to be generated for each cloud computing product. As the number of cloud computing products increases, the generation and management of form pages becomes difficult.

Contents of the invention

The present disclosure provides a method, device, electronic device and storage medium for generating a form page.

According to one aspect of the present disclosure, a method for generating a form page is provided, including:

Get multiple page components used to generate form pages;

Based on the type information, text information and layout information contained in the target form page to be generated, calling at least one target page component among the plurality of page components; and

The target form page is generated according to the result of calling at least one target page component among the plurality of page components.

According to another aspect of the present disclosure, a device for generating a form page is provided, including:

Obtain module, configured to obtain multiple page components used to generate form pages;

a calling module configured to call at least one target page component among the plurality of page components based on the type information, text information and layout information contained in the target form page to be generated; and

A generating module configured to generate the target form page according to the result of calling at least one target page component among the plurality of page components.

According to another aspect of the present disclosure, an electronic device is provided, including:

at least one processor; and

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

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the above method.

According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause the computer to perform the above method. According to another aspect of the present disclosure, a computer program product is provided, including a computer program that implements the above method when executed by a processor.

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

Description of the drawings

The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure. in:

Figure 1 is a flow chart of a method for generating a form page according to an embodiment of the present disclosure;

Figure 2 is a schematic diagram of obtaining multiple page components according to an embodiment of the present disclosure;

3A and 3B are examples of calling functions according to embodiments of the present disclosure;

Figure 4 is a schematic diagram of information contained in a target form page according to an embodiment of the present disclosure;

Figure 5 is an example of a JSON structure according to an embodiment of the present disclosure;

Figure 6 is a schematic diagram of calling a target page component according to an embodiment of the present disclosure;

7A and 7B are examples of generated target form pages according to embodiments of the present disclosure;

Figure 8 is a block diagram of a device for generating a form page according to an embodiment of the present disclosure; and

FIG. 9 is a block diagram of an electronic device used to implement a method for generating a form page according to an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the present disclosure are included to facilitate understanding and should be considered to be exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

In cloud computing products, users are required to complete product-related purchase information before purchasing products or related services. Different types of cloud computing products require different purchase information. For example, if the user purchases services related to providing a portal website, the user needs to provide the website's domain name, FTP (File Transfer Protocol, File Transfer Protocol) name and other information. As a service provider of cloud computing products, it is necessary to determine what purchase information users need to complete when the cloud computing product is released, generate a form page based on the information that needs to be completed, and display the generated form page to the user. Users fill in the corresponding information in the form page to complete the ordering process of cloud computing products.

There are two ways to generate form pages: dynamic and static. The static generation method is to create a static form page for each specific cloud computing product based on the information that needs to be completed by the user. Store the created form page in advance, and when it needs to be displayed to the user, just call the entire static form page directly. The implementation technology of this method is relatively simple, but as the number of cloud computing products increases, the workload of creating static form pages increases, and the maintenance cost of static form pages increases.

In the technology stack of cloud computing products, multiple component libraries are generally introduced, and form pages can be dynamically generated using component libraries. By using third-party dependency libraries to call components in the component library, and using components to dynamically generate form pages. The dynamic generation method does not require separate form pages for each cloud computing product, which can avoid a lot of repeated work, help reduce the workload of generating static form pages, and reduce the cost of maintaining form pages. However, with the reconstruction and upgrading of cloud computing product business lines, the technology stack of the old business line will be replaced by the technology stack of the new business line. It is necessary to transform the dependency library based on the technology stack of the old business line, and the transformation cost is often relatively high. high.

Embodiments of the present disclosure provide a method for dynamically generating form pages without resorting to third-party dependent libraries. FIG. 1 is a flow chart of a method 100 for generating a form page according to an embodiment of the present disclosure. As shown in Figure 1, the method 100 of generating a form page includes the following steps:

In step S110, multiple page components used to generate the form page are obtained.

In step S120, at least one target page component among the plurality of page components is called based on the type information, text information and layout information contained in the target form page to be generated.

In step S130, a target form page is generated according to the result of calling at least one target page component among the plurality of page components.

In embodiments of the present disclosure, in order to use the component library included in the current business technology stack, each component in the component library included in the technology stack introduced into the current business can be exported, and a component collection can be constructed to store each component. In this way, when you need to use a component in the component library, you no longer need to rely on a third-party dependency library to call the component. You can directly obtain the corresponding component from the component collection.

In the embodiment of the present disclosure, the target form page means a form page determined for a specific cloud computing product that displays product purchase information that needs to be completed by the user to the user. Various information contained in the target form page can be determined, such as type information, text information, layout information, etc. According to an embodiment, the type information of the target form page can be determined according to the type of the page component required by the target form page, the text information of the target form page can be determined according to the text content presented by the required page component on the target form page, and according to the required page The component's position on the target form page determines the layout information for the target form page.

In the embodiment of the present disclosure, the target page component means the page component required to generate the target form page, which may be one type of page component or multiple types of page components. The process of calling the target page component is the process of generating the form page. Therefore, according to embodiments of the present disclosure, the target form page can be dynamically generated. Compared with the static generation method of form pages, the repeated generation process of form page elements can be avoided, and the maintenance cost of form pages can be reduced.

In addition, according to embodiments of the present disclosure, when the technology stack of the new business line replaces the technology stack of the old business line, each component in the component library in the new technology stack can also be exported and the target page components can be modified. Called to dynamically generate the target form page. Since there is no need to resort to third-party dependency libraries to use component libraries, it can overcome the high cost of modifying dependency libraries based on old business line technology stacks, and is more suitable for cloud computing products that require frequent upgrades.

In an embodiment of the present disclosure, obtaining multiple page components used to generate the form page may include: exporting multiple page components from a component library included in the technology stack introduced into the current business, targeting the multiple page components. Each page component generates a calling function, and stores the page component and the calling function of the page component in a one-to-one correspondence in the component collection.

Figure 2 is a schematic diagram of obtaining multiple page components according to an embodiment of the present disclosure. As shown in Figure 2, the current business technology stack 21 includes two component libraries 211 and 212. The component libraries 211 and 212 may each include multiple page components for generating form pages. The embodiments of the present disclosure do not limit the number of component libraries included in the technology stack, nor the number of components included in each component library. All page components included in each of them are exported from component libraries 211 and 212 respectively, and this process is shown as 230 in Figure 2 . For each exported page component, a calling function is generated. And the page components and the generated calling functions are stored in the component collection 22 in one-to-one correspondence. As shown in Figure 2, for each element 220 in the component collection, it is composed of page components and calling functions. In a specific embodiment, the component collection 22 may be a global array structure, and a set of data composed of page components and calling functions is stored as an array element.

According to embodiments, other attribute information of the page components may also be stored in the component collection 22 . For example, each page component can be renamed so that it can be more easily found when selecting the page component from the component collection 22 .

By exporting the components in the component library included in the technology stack and storing them in the component collection together with the generated calling functions, the page components in the component library can be called without resorting to third-party dependent libraries. It can better adapt to the reconstruction and upgrade of business lines.

According to the embodiment, the page component is a code segment used to generate a structure such as an input box on the form page, and the calling function is used to call the page component to add the code segment corresponding to the page component to the HTML file of the form page. a piece of code.

3A and 3B are examples of calling functions according to embodiments of the present disclosure. As shown in Figure 3A and Figure 3B, the calling function completes the following process: first obtain the Component in each page component configuration in the component collection, and then load the page component. Next, do a mapping between "tagName" and the value of Component. For example, as shown in Figure 3A, "Calendar" is mapped to "ui-form-calendar". As shown in Figure 3B, map "BoxGroup" to "ui-form-boxgroup". Further, in the embodiment of the present disclosure, a "builder" function is defined, which performs the calling process of the page component. As shown in Figure 3A and Figure 3B, in the "builder" function, parameters related to the page component are passed in "<" and "/>".

In the embodiment of the present disclosure, after obtaining the configuration of each page component in the component collection, Component is not used directly, that is, "Calendar" or "BoxGroup" is used to make function calls, but the redefined " builder" function to call different page components. It can be seen from the calling function examples shown in Figure 3A and Figure 3B that although the two calling functions are called for different page components ("Calendar" and "BoxGroup" respectively), due to the use of "builder" Functions make the writing of function-calling codes more standardized and unified, which helps simplify the generation process of calling functions when adding new page components.

FIG. 4 is a schematic diagram of determining information contained in a target form page according to an embodiment of the present disclosure. As shown in Figure 4, the target form page 41 is a form page determined for a specific cloud computing product and showing the user product purchase information that needs to be completed by the user. Multiple pieces of product information are included in the target form page 41. For example, as shown in Figure 4, a piece of product information 411 may be information related to a domain name, and the product information has the text "bind domain name" to indicate to the user the type of information that needs to be filled in. The product information 411 includes an input box portion for user input, in which the user can set a domain name. Another product information 412 may be information related to the FTP user, and the product information has the text "FTP username". Similarly, the product information 412 also includes an input box part for user input, and the user can set FTP in the input box. username. The input box parts in product information 411 and 412 can both be generated by page components.

As shown in Figure 4, the information contained in the target form page 41 can be roughly divided into three categories. The first type of information is aimed at page components generated on the target form page 41, and is mainly type information 4111 of different page components. For example, the type of component can be text, email, textArea, select, radio or checkBox, etc. The second type of information is aimed at the text content presented on the target form page 41, mainly text information 4112. For example, "bind domain name" and "FTP username" are both text information. In addition, in some other embodiments, some prompt information used to explain to the user also belongs to text information. For example, "Please fill in the date in the format of year-month-day." The third type of information is aimed at the position where page components are placed on the target form page 41, mainly layout information 4113. For example, the coordinates of the respective page components of the product information 411 and 412 on the target form page 41, the length and width of the page components, and other information. Based on this information, the page components can be correctly placed at the desired position on the target form page 41. .

In the embodiment of the present disclosure, after the above-mentioned type information 4111, text information 4112 and layout information 4113 are determined, these information can be stored in a preset data structure, so that the desired target form page 41 can be represented for data. According to an embodiment, type information 4111, text information 4112, and layout information 4113 may be stored in a JSON (JavaScript Object Notation) structure. The JSON structure is a lightweight data exchange format. Easy to read and write, and easy for computing devices to parse and generate.

Figure 5 is an example of a JSON structure according to an embodiment of the present disclosure. As shown in Figure 5, the field "type" corresponds to type information. In the JSON structure, the type of the above page component is not defined. Therefore, the value of the field "type" can be converted to the type of the page component by establishing a conversion relationship between the value of the field "type" and the type of the page component. For example, common field "type" values include string, array, select, calendar, number, boolean, etc. The conversion relationship between the value of the field "type" and the type of the page component can be specified according to the actual situation. For example, the field value "string" is generally specified as a text type page component. According to embodiments, one or more fields other than "type" may be used to store text information and layout information respectively. As shown in Figure 5, the field "title" corresponds to text information, and the field value "bind domain name" represents the text that will be displayed on the target form page. The field "description" also corresponds to text information. The field value "Please fill in the domain name format correctly, such as test.baidu.com" can be displayed on the target form page under certain conditions. The field "maxLength" corresponds to the layout information, and the field value "20" can limit the page component, that is, the maximum length of the input box.

In some embodiments, other information related to the target form page may also be stored in the JSON structure. For example, the filling rules for the page components. As shown in Figure 5, the field "required" corresponds to the filling rules for the page component, and the field value "true" indicates that the input box corresponding to the page component cannot be empty. The field "default" also corresponds to the filling rule for the page component. The field value is empty, and the default value of the page component is given, which is set to empty.

In an embodiment of the present disclosure, based on the type information, text information and layout information contained in the target form page to be generated, calling at least one target page component among the plurality of page components may include: based on the type information, from the component Determine at least one target page component in the collection, obtain the calling function of the at least one target page component from the component collection, pass text information and layout information as parameters to the calling function of the target page component, and execute the calling function to call at least one The target page component is called.

Figure 6 is a schematic diagram of calling a target page component according to an embodiment of the present disclosure. As shown in Figure 6, the JSON structure 61 stores various information contained in the target form page, and the array 62 stores multiple page components used to generate the target form page. First, traverse the data object in the JSON structure and find the field "type". The value of the field "type" is "string". According to the conversion relationship between the JSON structure field value and the type of the page component, modify "string" to "text", as shown in step ① in Figure 6. Then, query in array 62 based on "text" to find the array element that stores the "text" page component, as shown in step ② in Figure 6. Then, the calling function 63 stored with the "text" page component is read from the found array element, as shown in step ③ in Figure 6 . Then, other attribute values in the JSON structure 61 are passed to the "builder" function as parameters 630, as shown in step ④ in Figure 6 . Multiple data objects can be stored in a JSON structure, only one example is shown in Figure 6. Traverse the JSON structure and perform the above process to get the calling functions for all components on the target form page. Next, the target form page can be generated based on the call results.

According to an embodiment, generating the target form page according to the calling result of at least one target page component among the plurality of page components may include: generating the target form page according to the calling result of at least one target page component among the plurality of page components. HTML source files, and parsing the HTML source files to generate target form pages. The result of calling the page component is to place the corresponding page component generation code in the HTML source file of the target form page. An application such as a browser can be used to parse the HTML source file and finally generate the target form page displayed to the user.

7A and 7B are examples of generated target form pages according to embodiments of the present disclosure. As shown in Figure 7A, a portion of the generated target form page is shown. There are two page components placed in this part of the target form page, namely the input box corresponding to the "bind domain name" and the input box corresponding to the "FTP user name". There is an "*" displayed in front of the title "Bind Domain Name", which can be defined by the value of the "required" field in the JSON structure, indicating that "Bind Domain Name" is information that must be filled in. A question mark with a box is displayed on one side of the two page components, which is a prompt message for the page components. As shown in Figure 7A, the prompt information for filling in the page components can be obtained through the question mark with a box.

As shown in Figure 7B, a portion of the generated target form page is also shown. The text information and page components contained in this part of the target form page are the same as those in Figure 7A. The difference is the mutual positional relationship between the two page components on the target form page. In Figure 7A, the input box corresponding to "Bind domain name" and the input box corresponding to "FTP user name" are located in the same row. In Figure 7B, the input box corresponding to "Bind domain name" and the input box corresponding to "FTP user name" are located in the same row. The input box for "FTP Username" is on a different line. This is defined by the values of fields in the JSON structure related to layout information.

According to embodiments of the present disclosure, form pages in any desired form can be dynamically generated based on the JSON structure without resorting to third-party dependent libraries. When designing a form page, just build the JSON structure according to the desired form page, and the operation is simple. When refactoring from an old technology stack using a new technology stack, the new refactoring process no longer needs to introduce external libraries for support. It can be implemented by covering it in the new technology stack. Therefore, it is especially suitable for Business line upgrades and expansions.

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

FIG. 8 is a block diagram of an apparatus 800 for generating a form page according to an embodiment of the present disclosure. As shown in FIG. 8 , the device 800 for generating a form page includes an acquisition module 810 , a calling module 820 and a generation module 830 .

According to an embodiment, the obtaining module 810 is configured to obtain a plurality of page components for generating the form page. The calling module 820 is configured to call at least one target page component among the plurality of page components based on the type information, text information and layout information contained in the target form page to be generated. The generating module 830 is configured to generate a target form page according to a result of calling at least one target page component among the plurality of page components.

The specific operations of each of the above functional modules can be obtained by referring to the operating steps of the method 100 for generating a form page in the previous embodiment, and will not be described again here.

Figure 9 shows a schematic block diagram of an example electronic device 900 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to refer to various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are examples only and are not intended to limit implementations of the disclosure described and/or claimed herein.

As shown in FIG. 9 , the device 900 includes a computing unit 901 that can execute according to a computer program stored in a read-only memory (ROM) 902 or loaded from a storage unit 908 into a random access memory (RAM) 903 Various appropriate actions and treatments. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. Computing unit 901, ROM 902 and RAM 903 are connected to each other via bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

Multiple components in the device 900 are connected to the I/O interface 905, including: an input unit 909, such as a keyboard, a mouse, etc.; an output unit 909, such as various types of displays, speakers, etc.; a storage unit 908, such as a magnetic disk, optical disk, etc. ; and communication unit 909, such as a network card, modem, wireless communication transceiver, etc. The communication unit 909 allows the device 900 to exchange information/data with other devices through computer networks such as the Internet and/or various telecommunications networks.

Computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processing processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 901 performs various methods and processes described above, such as the method of generating a form page. For example, in some embodiments, the method of generating a form page may be implemented as a computer software program that is tangibly embodied in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 900 via ROM 902 and/or communication unit 909 . When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the method of generating a form page described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the method of generating a form page of the present disclosure in any other suitable manner (eg, by means of firmware).

Various implementations of the systems and techniques described above may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip implemented in a system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or a combination thereof. These various embodiments may include implementation in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor The processor, which may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device. An output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that the program codes, when executed by the processor or controller, cause the functions specified in the flowcharts and/or block diagrams/ The operation is 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 may 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. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

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

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.

Computer systems may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communications network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other.

It should be understood that various forms of the process shown above may be used, with steps reordered, added or deleted. For example, each step described in the present disclosure can be executed in parallel, sequentially, or in a different order. As long as the desired results of the technical solution disclosed in the present disclosure can be achieved, there is no limitation here.

The above-mentioned specific embodiments do not constitute a limitation on the scope of the present disclosure. It will be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions are possible depending on design requirements and other factors. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this disclosure shall be included in the protection scope of this disclosure.

Claims (8)

1. A method of generating a form page, comprising:

acquiring a plurality of page components for generating a form page;

calling at least one target page component in the plurality of page components based on type information, text information and layout information contained in the target form page to be generated; and

generating the target form page according to a calling result of at least one target page component in the plurality of page components;

wherein the obtaining a plurality of page components for generating a form page comprises:

deriving the plurality of page components from a component library, the component library belonging to a technology stack introduced into the current service;

generating a calling function for each of the plurality of page components; and

and storing the page components and the calling functions of the page components in a component set in a one-to-one correspondence manner.

2. The method of claim 1, wherein the invoking at least one of the plurality of page components based on the type information, text information, and layout information contained by the target form page to be generated comprises:

selecting at least one target page component from the set of components based on the type information;

acquiring a calling function of the at least one target page component;

transferring the text information and the layout information as parameters to a calling function of the target page component; and

executing the calling function to call the at least one target page component.

3. The method of claim 2, wherein the generating the target form page based on the call to at least one target page component of the plurality of page components comprises:

generating an HTML source file of the target form page according to a calling result of at least one target page component in the plurality of page components; and

and analyzing the HTML source file to generate the target form page.

4. The method of claim 1, further comprising:

determining the type information according to the type of the page component required by the target form page;

determining the text information according to the text content presented by the required page component on the target form page; and

and determining the layout information according to the position of the required page component on the target form page.

5. The method of claim 1, further comprising:

the type information, the text information, and the layout information are stored in a JSON structure.

6. An apparatus for generating a form page, comprising:

an acquisition module configured to acquire a plurality of page components for generating a form page;

the calling module is configured to call at least one target page component in the plurality of page components based on type information, text information and layout information contained in the target form page to be generated; and

the generation module is configured to generate the target form page according to a call result of at least one target page component in the plurality of page components;

the acquiring module acquires a plurality of page components for generating a form page, including:

deriving the plurality of page components from a component library, the component library belonging to a technology stack introduced into the current service;

generating a calling function for each of the plurality of page components; and

and storing the page components and the calling functions of the page components in a component set in a one-to-one correspondence manner.

7. 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-5.

8. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-5.