A method and system for designing form pages that allow users to customize metadata.

Abstract

This invention provides a method and system for designing form pages with user-defined metadata. The method includes: obtaining first page field information; a first processing terminal obtaining a first AJAX request, parsing the first page field information based on the first AJAX request, and obtaining a first parsing result; rendering a control on the first parsing result through the first processing terminal to obtain a rendering control; obtaining first custom configuration information through the rendering control; the first processing terminal sending the first custom configuration information to a second processing terminal through the first AJAX request; and the second processing terminal re-rendering the first page. This solves the technical problem in the prior art where changes to company form pages require code adjustments and involve multiple departments, resulting in low efficiency in secondary form development.

Description

Technical Field

[0001] This invention relates to the technical field of page design, specifically a method and system for designing form pages that allow users to customize metadata. Background Technology

[0002] As businesses diversify and their operations expand, their complexity and flexibility also increase. To improve management efficiency, companies often customize forms based on their specific business needs.

[0003] Application systems for professional users have always been a focus of software development. Management systems play a very important role in the daily operation of a company. However, due to adjustments in company business and other reasons, the required forms and pages often need to be changed accordingly, which increases the workload of development and makes the system very inflexible.

[0004] Currently, the development process of form pages requires the cooperation of multiple departments and code adjustments, because the development work of forms becomes more arduous when the company's business changes.

[0005] However, in the process of implementing the inventive technical solution in the embodiments of this application, the inventors of this application discovered that the above-mentioned technology has at least the following technical problems:

[0006] In existing technologies, changes to company form pages require code adjustments and involve multiple departments, resulting in low efficiency in secondary form development. Summary of the Invention

[0007] This application provides a method and system for designing form pages with user-defined metadata. It solves the technical problem in existing technologies where changes to company form pages require code adjustments and involve multiple departments, leading to low efficiency in secondary form development. The method parses form page field information via AJAX requests, and renders the form using rendering controls based on the parsed results. When page modifications are needed, users edit and save their configuration information based on the rendering controls and the corresponding page rendering settings by calling a custom configuration function. The front-end then sends the custom configuration information to the back-end via an AJAX request, and the back-end updates the form page based on the custom configuration information. AJAX requests enable the rapid creation of dynamic forms and asynchronous partial updates; the custom functionality allows users or product managers to directly perform custom editing; and the development of general components eliminates the need to modify the original code. This achieves a simple, efficient, and highly applicable technical effect.

[0008] In view of the above problems, this application provides a method and system for designing form pages for user-defined metadata.

[0009] In a first aspect, embodiments of this application provide a form page design method for user-defined metadata. The method is applied to a custom system, which includes a first processing terminal and a second processing terminal. The method includes: obtaining first page field information; the first processing terminal obtaining a first AJAX request, parsing the first page field information based on the first AJAX request, and obtaining a first parsing result; rendering a control on the first parsing result through the first processing terminal to obtain a rendering control; obtaining first custom configuration information through the rendering control, and the first processing terminal sending the first custom configuration information to the second processing terminal through the first AJAX request, and the second processing terminal re-rendering the first page.

[0010] On the other hand, embodiments of this application provide a form page design system for user-defined metadata, wherein the system includes: a first obtaining unit, the first obtaining unit being used to obtain first page field information; a second obtaining unit, the second obtaining unit being used by a first processing terminal to obtain a first AJAX request, and to parse the first page field information based on the first AJAX request to obtain a first parsing result; a third obtaining unit, the third obtaining unit being used to render a control on the first parsing result through the first processing terminal to obtain a rendering control; and a first execution unit, the first execution unit being used to obtain first custom configuration information through the rendering control, the first processing terminal sending the first custom configuration information to a second processing terminal through the first AJAX request, and the second processing terminal re-rendering the first page.

[0011] Thirdly, embodiments of this application provide a form page design system for user-defined metadata, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method described in any of the first aspects.

[0012] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0013] This technical solution employs the following steps: obtaining first page field information; the first processing end receives a first AJAX request, parses the first page field information based on the first AJAX request to obtain a first parsing result; the first processing end renders the first parsing result using controls to obtain a rendering control; first custom configuration information is obtained through the rendering control; the first processing end sends the first custom configuration information to the second processing end via the first AJAX request; and the second processing end re-renders the first page. This solution parses the form page field information using AJAX requests, renders it using rendering controls based on the parsing results, and when the page needs modification, the user edits and saves the configuration information based on the rendering control and the corresponding page rendering status by calling the custom configuration function. The front end then sends the custom configuration information to the back end via an AJAX request, and the back end calls the rendering control to update the page form based on the custom configuration information. This achieves a simple, efficient, and highly applicable technical effect. Dynamic forms can be quickly created via AJAX requests, enabling asynchronous partial updates; users or product managers can directly perform custom editing through the custom function; and the development of general components eliminates the need to modify the original code.

[0014] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0015] Figure 1 This application provides a flowchart illustrating a method for designing form pages for user-defined metadata.

[0016] Figure 2 This application provides a flowchart illustrating a method for customizing user field names.

[0017] Figure 3 This application provides a flowchart illustrating a method for customizing user field widths in an embodiment.

[0018] Figure 4 This application provides a flowchart illustrating a user-oriented field type customization method in its embodiments.

[0019] Figure 5 This application provides a schematic diagram of a form page design system for user-defined metadata.

[0020] Figure 6 This is a schematic diagram of the structure of an exemplary electronic device according to an embodiment of this application.

[0021] Explanation of reference numerals in the attached drawings: First obtaining unit 11, Second obtaining unit 12, Third obtaining unit 13, First execution unit 14, Electronic device 300, Memory 301, Processor 302, Communication interface 303, Bus architecture 304. Detailed Implementation

[0022] This application provides a method and system for designing form pages with user-defined metadata. It solves the technical problem in existing technologies where changes to company form pages require code adjustments and involve multiple departments, leading to low efficiency in secondary form development. The method parses form page field information via AJAX requests, and renders the form using rendering controls based on the parsed results. When page modifications are needed, users edit and save their configuration information based on the rendering controls and the corresponding page rendering settings by calling a custom configuration function. The front-end then sends the custom configuration information to the back-end via an AJAX request, and the back-end updates the form page based on the custom configuration information. AJAX requests enable the rapid creation of dynamic forms and asynchronous partial updates; the custom functionality allows users or product managers to directly perform custom editing; and the development of general components eliminates the need to modify the original code. This achieves a simple, efficient, and highly applicable technical effect.

[0023] Application Overview

[0024] As businesses diversify and their operations expand, their complexity and flexibility also increase. To improve management efficiency, companies often customize forms based on their specific business needs.

[0025] Application systems targeting professional users have always been a focus of software development. Management systems play a crucial role in the daily operations of a company. However, due to changes in company business and other reasons, the required form pages often need to be modified accordingly, increasing the development workload and making them inflexible. Currently, the development process of form pages requires collaboration among multiple departments and code adjustments, as the development work becomes quite demanding when company business changes. Furthermore, changes to company form pages in existing technologies require code adjustments and involve multiple departments, resulting in low efficiency in secondary form development.

[0026] To address the aforementioned technical problems, the overall approach of the technical solution provided in this application is as follows:

[0027] This application provides a form page design method for user-defined metadata. The method is applied to a custom system, which includes a first processing terminal and a second processing terminal. The method includes: obtaining first page field information; the first processing terminal obtaining a first AJAX request, parsing the first page field information based on the first AJAX request, and obtaining a first parsing result; rendering a control on the first parsing result through the first processing terminal to obtain a rendered control; obtaining first custom configuration information through the rendered control; the first processing terminal sending the first custom configuration information to the second processing terminal through the first AJAX request; and the second processing terminal re-rendering the first page.

[0028] After introducing the basic principles of this application, various non-limiting embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0029] Example 1

[0030] like Figure 1 As shown in the figure, this application provides a form page design method for user-defined metadata. The method is applied to a custom system, which includes a first processing terminal and a second processing terminal. The method includes:

[0031] S100: Obtain field information from the first page;

[0032] Specifically, the first page field information refers to information describing the field data on the page that needs secondary design. Preferably, metadata can be used for description, including but not limited to element or attribute information such as name, size, and data type, or its structure such as length, fields, and data columns, as well as data such as field component type and field validation information. By comprehensively describing the field information on the first page and storing it on the second processing end, i.e., the backend, it is convenient to quickly call the corresponding first page field information to modify the specific content when the page needs to be modified.

[0033] S200: The first processing terminal receives the first AJAX request, parses the field information of the first page based on the first AJAX request, and obtains the first parsing result;

[0034] Specifically, the first processing end refers to the front-end of the developer of the first page; the first AJAX request refers to the technology used to quickly create dynamic form pages; the first parsing result refers to the metadata information required for configuring the first page by parsing the field information of the first page, such as field names, field widths, field validation information, etc., without limitation; the first processing end sends the first AJAX request to the second processing end, and the second processing end returns the first parsing result corresponding to the first AJAX request information to the first processing end. The first AJAX request enables asynchronous updates to the first page, facilitating front-end and back-end interaction and allowing for partial modifications.

[0035] S300: The first processing terminal renders the first parsing result into a control to obtain a rendered control;

[0036] Specifically, the rendering control refers to the control that needs to be called after the first processing end receives the first parsing result and obtains the metadata information of the configuration fields that need to be modified, such as the field name, field width, and field validation information mentioned above, and then renders the corresponding field on the first page after modification. By rendering the corresponding control, the page location where the configuration information of the field corresponding to the rendering control needs to be customized can be determined.

[0037] S400: Obtain first custom configuration information through the rendering control, the first processing end sends the first custom configuration information to the second processing end through the first AJAX request, and the second processing end re-renders the first page.

[0038] Furthermore, the method described in step S400 includes:

[0039] S450: Obtain a first storage instruction, and store the first custom configuration information through the second processing terminal according to the first storage instruction.

[0040] Specifically, the first custom configuration information refers to the process of calling the custom configuration information function after determining the field whose configuration information needs to be modified and rendering the corresponding control to obtain the rendering control. This allows the user to customize the configuration information, such as editing the field name, field width, field validation information, and other specific data of the corresponding field. After the user completes and saves the custom configuration information, the first processing end receives the first custom configuration information. Furthermore, the first processing end sends the first custom configuration information to the second processing end via the first AJAX request and stores the first custom configuration information according to the first storage instruction. The second processing end updates the configuration information of the corresponding field represented in the first AJAX request information using the first custom configuration information. Even further, the second processing end calls the rendering control to render the first page based on the updated configuration information, obtaining an updated page form, thus achieving the technical effect of simply updating the page form.

[0041] Furthermore, such as Figure 2 As shown, the system also includes a field name control, and step S400, based on obtaining the first custom configuration information through the rendering control, further includes step S410:

[0042] S411: Obtain the custom configuration information of the first field name through the field name control;

[0043] S412: Use the first field name custom configuration information as the first custom configuration information.

[0044] Specifically, the field name control refers to a general control for customizing field names; the first field name customization configuration information refers to the result obtained by the user calling the field name control to customize the field name configuration information. The first field name customization configuration information and the field name control are stored accordingly as the first customization configuration information, which is conveniently retrieved when updating field name information later.

[0045] Furthermore, such as Figure 3 As shown, the system also includes a field width control, and based on step S400 of obtaining the first custom configuration information through the rendering control, it further includes step S420:

[0046] S421: Obtain the custom configuration information for the first field width through the field width control;

[0047] S422: Use the first field width custom configuration information as the first custom configuration information.

[0048] Specifically, the field width control refers to a general control that allows for customization of field width; the first field width customization configuration information refers to the result obtained by the user calling the field width control to customize the field width configuration information. The first field width customization configuration information and the field width control are stored accordingly as the first customization configuration information, which is conveniently retrieved when updating the field width information later.

[0049] Furthermore, such as Figure 4 As shown, the system also includes a field type control, and based on step S400 of obtaining the first custom configuration information through the rendering control, it further includes step S430:

[0050] S431: Obtain the custom configuration information of the first field type through the field type control;

[0051] S432: Use the first field type custom configuration information as the first custom configuration information.

[0052] Specifically, the field type control refers to a general control for customizing field types; the first field type custom configuration information refers to the result obtained by the user calling the field type control to customize the configuration information of the field type. The first field type custom configuration information and the field type control are stored accordingly as the first custom configuration information, which is conveniently retrieved when updating the field type information later.

[0053] Furthermore, based on obtaining the first custom configuration information through the rendering control, step S400 further includes step S440:

[0054] S441: Obtain a first field modification instruction, add and / or delete field information on the first page according to the first field modification instruction, and obtain a first modification result;

[0055] S442: Use the first modification result as the first custom configuration information.

[0056] Specifically, the first field modification instruction is a signal issued by the first processing terminal to add, delete, or modify a field; the first modification result refers to the result after modifying the field information on the first page, and there are three main modification results: the result after both adding and deleting; the result after only adding information to the first page; and the result after only deleting information from the first page. Furthermore, the first modification result is stored as the first custom configuration information on the second processing terminal for easy retrieval during subsequent page configuration.

[0057] Furthermore, step S300, which involves rendering the first parsing result using the first processing terminal to obtain the rendered control, further includes:

[0058] S310: Develop a control through the first processing terminal and obtain a first control development result, wherein the first control development result includes a basic control and an extended control;

[0059] S320: Render the first parsing result and the first control development result to obtain the rendered control.

[0060] Specifically, the first control development result refers to various controls developed by the first processing terminal that are needed when designing the form page, including but not limited to the basic controls: such as input controls, select controls, and date controls; and the extended controls: address controls, phone controls, and date-range controls. Further, the controls corresponding to the configuration information in the first parsing result are called, and the rendered controls are obtained. By developing various form controls through the first processing terminal and rendering them when needed, the custom operations of the first page are supported, thus achieving simple and efficient customization of the form page. Because common components are used, there is no need to edit the original code, improving work efficiency.

[0061] In summary, the form page design method and system for user-defined metadata provided in this application have the following technical effects:

[0062] 1. The system parses form field information via AJAX requests, renders the form using rendering controls based on the parsed results, and allows users to edit and save their custom configurations by calling a custom configuration function. The front-end then sends the custom configuration information to the back-end via an AJAX request, and the back-end updates the form based on the custom configuration. This approach allows for the rapid creation of dynamic forms and asynchronous partial updates via AJAX requests; user or product manager customization is possible through custom functionality; and the development of general-purpose components eliminates the need to modify the original code. This results in a simple, efficient, and highly adaptable technical solution.

[0063] Example 2

[0064] Based on the same inventive concept as the form page design method for user-customizable metadata in the foregoing embodiments, such as Figure 5 As shown in the figure, this application embodiment provides a form page design system for user-defined metadata, wherein the system includes:

[0065] The first obtaining unit 11 is used to obtain the field information of the first page;

[0066] The second obtaining unit 12 is used by the first processing end to obtain the first AJAX request, parse the field information of the first page based on the first AJAX request, and obtain the first parsing result;

[0067] The third obtaining unit 13 is used to render a control on the first parsing result through the first processing terminal to obtain a rendered control.

[0068] The first execution unit 14 is used to obtain first custom configuration information through the rendering control. The first processing end sends the first custom configuration information to the second processing end through the first AJAX request, and the second processing end re-renders the first page.

[0069] Furthermore, the system also includes:

[0070] The fourth obtaining unit is used to obtain the custom configuration information of the first field name through the field name control;

[0071] The first setting unit is used to set the first field name custom configuration information as the first custom configuration information.

[0072] Furthermore, the system also includes:

[0073] The fifth obtaining unit is used to obtain the custom configuration information of the first field width through the field width control;

[0074] The second setting unit is used to use the first field width custom configuration information as the first custom configuration information.

[0075] Furthermore, the system also includes:

[0076] The sixth obtaining unit is used to obtain the custom configuration information of the first field type through the field type control;

[0077] The third setting unit is used to use the first field type custom configuration information as the first custom configuration information.

[0078] Furthermore, the system also includes:

[0079] The seventh obtaining unit is used to obtain a first field modification instruction, and add and / or delete the field information of the first page according to the first field modification instruction to obtain a first modification result;

[0080] The fourth setting unit is used to take the first modification result as the first custom configuration information.

[0081] Furthermore, the system also includes:

[0082] The first storage unit is used to obtain a first storage instruction and, according to the first storage instruction, store the first custom configuration information through the second processing terminal.

[0083] Furthermore, the system also includes:

[0084] The eighth obtaining unit is used to develop controls through the first processing terminal and obtain a first control development result, wherein the first control development result includes basic controls and extended controls;

[0085] The ninth obtaining unit is used to perform control rendering on the first parsing result and the first control development result to obtain the rendered control.

[0086] Exemplary electronic devices

[0087] The following is for reference. Figure 6 To describe the electronic device in the embodiments of this application,

[0088] Based on the same inventive concept as the form page design method for user-defined metadata in the foregoing embodiments, this application also provides a form page design system for user-defined metadata, comprising: a processor coupled to a memory for storing a program, wherein when the program is executed by the processor, the system performs the method described in any of the first aspects.

[0089] The electronic device 300 includes a processor 302, a communication interface 303, and a memory 301. Optionally, the electronic device 300 may also include a bus architecture 304. The communication interface 303, processor 302, and memory 301 can be interconnected via the bus architecture 304; the bus architecture 304 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus architecture 304 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0090] Processor 302 may be a CPU, microprocessor, ASIC, or one or more integrated circuits used to control the execution of programs according to the present application.

[0091] Communication interface 303 is used in any transceiver system for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0092] Memory 301 can be ROM or other types of static storage devices capable of storing static information and instructions, RAM or other types of dynamic storage devices capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory can exist independently and be connected to the processor via bus architecture 304. Memory can also be integrated with the processor.

[0093] The memory 301 stores computer execution instructions for implementing the scheme of this application, and the processor 302 controls the execution. The processor 302 executes the computer execution instructions stored in the memory 301, thereby realizing the form page design method for user-customizable metadata provided in the above embodiments of this application.

[0094] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0095] This application provides a method for designing form pages with user-defined metadata. The method is applied to a custom system, which includes a first processing end and a second processing end. The method includes: obtaining first page field information; the first processing end obtaining a first AJAX request, parsing the first page field information based on the first AJAX request to obtain a first parsing result; rendering the first parsing result using a control on the first processing end to obtain a rendering control; obtaining first custom configuration information through the rendering control; the first processing end sending the first custom configuration information to the second processing end via the first AJAX request; and the second processing end re-rendering the first page. By parsing the form page field information using the AJAX request information and rendering it using the rendering control based on the parsing result, when the page needs modification, the user can edit and save the configuration information based on the rendering control and the corresponding rendering status of the page by calling the custom configuration function. The front end will then send the custom configuration information to the back end via an AJAX request, and the back end will call the rendering control to update the page form based on the custom configuration information. Dynamic forms can be quickly created via AJAX requests, enabling asynchronous partial updates; users or product managers can directly perform custom editing through the custom function; and the development of general components eliminates the need to modify the original code. It achieves a simple, efficient, and widely applicable technical effect.

[0096] Those skilled in the art will understand that the various numerical designations, such as "first" and "second," used in this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application, nor do they indicate a sequential order. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one" refers to one or more. "At least two" refers to two or more. "At least one," "any one," or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0097] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable system. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0098] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic system, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing systems, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0099] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be disposed in an ASIC, which can be disposed in a terminal. Optionally, the processor and storage medium can also be disposed in different components of the terminal. These computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0100] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application intends to include such modifications and modifications.

Claims

1. A method for designing form pages for user-defined metadata, the method being applied to a custom system, the system comprising a first processing terminal and a second processing terminal, wherein, The method includes: Obtain the field information of the first page, which refers to the information used to describe the field data on the page that needs to be redesigned. The first processing end receives the first AJAX request, parses the field information of the first page based on the first AJAX request, and obtains the first parsing result, which includes: configuration fields that need to be modified; The first processing terminal renders the first parsing result into a control, thereby obtaining the rendering control that needs to be called after modifying the configuration field that needs to be modified in the first page. The first custom configuration information is obtained through the rendering control. The first processing end sends the first custom configuration information to the second processing end through the first AJAX request, and the second processing end re-renders the first page.

2. The method as described in claim 1, wherein, The system also includes a field name control, and obtaining the first custom configuration information through the rendering control further includes: The custom configuration information for the first field name is obtained through the field name control; Use the first field name custom configuration information as the first custom configuration information.

3. The method as described in claim 1, wherein, The system also includes a field width control, and obtaining the first custom configuration information through the rendering control further includes: The custom configuration information for the first field width is obtained through the field width control. Use the custom configuration information for the width of the first field as the first custom configuration information.

4. The method of claim 1, wherein, The system also includes a field type control, and obtaining the first custom configuration information through the rendering control further includes: The custom configuration information of the first field type is obtained through the field type control; Use the first field type custom configuration information as the first custom configuration information.

5. The method of claim 1, wherein, The step of obtaining the first custom configuration information through the rendering control also includes: Obtain a first field modification instruction, add and / or delete field information on the first page according to the first field modification instruction, and obtain a first modification result; The first modification result is used as the first custom configuration information.

6. The method of claim 1, wherein, The method includes: A first storage instruction is obtained, and the first custom configuration information is stored through the second processing terminal according to the first storage instruction.

7. The method of claim 1, wherein, The step of rendering the first parsing result into a control through the first processing terminal to obtain the rendered control further includes: The control is developed through the first processing terminal to obtain a first control development result, wherein the first control development result includes a basic control and an extended control; The first parsing result and the first control development result are used to render the control to obtain the rendered control.

8. A form page design system for user-defined metadata, wherein, The system includes: The first obtaining unit is used to obtain first page field information, which refers to information used to describe the field data on the page that needs to be redesigned. The second obtaining unit is used by the first processing end to obtain the first AJAX request, parse the field information of the first page based on the first AJAX request, and obtain the first parsing result. The first parsing result includes: configuration fields that need to be modified. The third obtaining unit is used to render the first parsing result through the first processing terminal to obtain the rendering control that needs to be called after modifying the configuration field that needs to be modified in the first page. The first execution unit is used to obtain first custom configuration information through the rendering control. The first processing end sends the first custom configuration information to the second processing end through the first AJAX request, and the second processing end re-renders the first page.

9. A form page design system for user-defined metadata, comprising: A processor coupled to a memory for storing a program that, when executed by the processor, causes the system to perform the method as described in any one of claims 1 to 7.

Images