CN116954597A

CN116954597A - Form page generation method and device, electronic equipment, storage medium and product

Info

Publication number: CN116954597A
Application number: CN202210395334.8A
Authority: CN
Inventors: 郑永升; 毛茂文; 赵爱松; 吕小敬; 宋德伟; 焦峰; 陈勋; 田清; 谢杰
Original assignee: Kunlun Digital Technology Co ltd; China National Petroleum Corp
Current assignee: Kunlun Digital Technology Co ltd; China National Petroleum Corp
Priority date: 2022-04-14
Filing date: 2022-04-14
Publication date: 2023-10-27

Abstract

The application provides a method and a device for generating a form page, electronic equipment, a storage medium and a product, and belongs to the technical field of computers. The method comprises the following steps: acquiring a plurality of metadata objects corresponding to a target service; configuring attribute values for metadata of a plurality of metadata objects to obtain a plurality of metadata components, wherein the metadata attribute values of each metadata object are matched with a target service; displaying a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface, the first sub-interface comprises a plurality of metadata components, and the second sub-interface comprises form layout information corresponding to the metadata components; and responding to triggering operation of the metadata components, and generating a target form page corresponding to the target service based on the form layout information and the metadata components. The method improves the efficiency of generating the form page.

Description

Form page generation method and device, electronic equipment, storage medium and product

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and apparatus for generating a form page, an electronic device, a storage medium, and a product.

Background

With the development of computer technology, form pages are widely used in business systems that interact with users. The form page is used for providing an information input page for a user, and the form page can send information input by the user to the background for processing so as to realize interaction with the user. Before the form page is applied, the technician is required to develop the form page.

In the related art, development languages corresponding to form pages of different service systems are different; therefore, for the development of form pages of different services of different service systems, technicians need to learn multiple development languages, so that the development of the form pages is slower, and the efficiency of generating the form pages is reduced.

Disclosure of Invention

The embodiment of the application provides a method, a device, electronic equipment, a storage medium and a product for generating a form page, which can improve the efficiency of generating the form page. The technical scheme is as follows:

in one aspect, a method for generating a form page is provided, where the method includes:

acquiring a plurality of metadata objects corresponding to a target service;

configuring attribute values for metadata of the metadata objects to obtain a plurality of metadata components, wherein the metadata attribute values of each metadata object are matched with the target service;

Displaying a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface, the first sub-interface comprises the metadata components, and the second sub-interface comprises form layout information corresponding to the metadata components;

and responding to triggering operation of the metadata components, and generating a target form page corresponding to the target service based on the form layout information and the metadata components.

In some embodiments, the first sub-interface further includes a plurality of generic components therein;

the generating, based on the form layout information and the metadata components, a target form page corresponding to the target service includes:

generating a first form page based on the form layout information and the plurality of metadata components;

in response to a trigger operation on a target generic component in the plurality of generic components, adding the target generic component to the first form page;

and responding to the dragging operation of any component in the first form page, and readjusting the layout of the component in the first form page based on the dragging track of any component to obtain the target form page.

In some embodiments, the first generation interface further includes a third sub-interface including form attribute information for the plurality of metadata components;

and setting attribute contents of the metadata components in the first form page based on the form attribute information of the metadata components to obtain the target form page.

In some embodiments, the obtaining the plurality of metadata objects corresponding to the target service includes:

displaying a second generation interface, wherein the second generation interface comprises a plurality of business controls;

and responding to the triggering operation of the service control corresponding to the target service, and acquiring a plurality of metadata objects corresponding to the target service from a metadata object library, wherein the metadata object library is used for storing metadata objects corresponding to a plurality of services respectively.

In some embodiments, the configuring attribute values for metadata of the plurality of metadata objects, to obtain a plurality of metadata components, includes:

Displaying a third generation interface, wherein the third generation interface comprises a fourth sub-interface and a fifth sub-interface, and the fourth sub-interface comprises the plurality of metadata objects;

responding to the triggering operation of any metadata object, and displaying an attribute configuration frame of the metadata object on the fifth sub-interface;

and responding to the input operation of the attribute configuration frame, acquiring an attribute value in the attribute configuration frame, and configuring the attribute value for the metadata of the metadata object to obtain a metadata component corresponding to the metadata object.

In some embodiments, the metadata of the metadata object includes at least one of an object key value, an object name, a component type, a component default value, a verification rule, a data type, and a data source corresponding to the metadata object;

the configuring attribute values for metadata of the metadata objects to obtain a plurality of metadata components includes:

and for each metadata object, respectively configuring attribute values for at least one of an object key value, an object name, a component type, a component default value, a verification rule, a data type and a data source corresponding to the metadata object to obtain a metadata component corresponding to the metadata object.

In another aspect, a generating device of a form page is provided, and the device includes:

the acquisition module is used for acquiring a plurality of metadata objects corresponding to the target service;

the configuration module is used for configuring attribute values for metadata of the metadata objects to obtain a plurality of metadata components, and the metadata attribute values of each metadata object are matched with the target service;

the display module is used for displaying a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface, the first sub-interface comprises the metadata components, and the second sub-interface comprises form layout information corresponding to the metadata components;

and the generation module is used for responding to the triggering operation of the metadata components and generating a target form page corresponding to the target service based on the form layout information and the metadata components.

In some embodiments, the first sub-interface further includes a plurality of generic components therein; the generating module is used for:

In some embodiments, the first generation interface further includes a third sub-interface including form attribute information for the plurality of metadata components; the generating module is used for:

In some embodiments, the acquiring module is configured to:

In some embodiments, the configuration module is configured to:

In some embodiments, the metadata of the metadata object includes at least one of an object key value, an object name, a component type, a component default value, a verification rule, a data type, and a data source corresponding to the metadata object; the configuration module is used for:

In another aspect, an electronic device is provided, where the electronic device includes one or more processors and one or more memories, where at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors, so as to implement the method for generating a form page according to any of the foregoing implementations.

In another aspect, a computer readable storage medium is provided, where at least one program code is stored, where the at least one program code is loaded and executed by a processor, to implement a method for generating a form page according to any of the foregoing implementations.

In another aspect, a computer program product is provided, including a computer program, which when executed by a processor implements the form page generation method according to any of the above implementations.

The embodiment of the application provides a generation method of a form page, which obtains a metadata component by configuring an attribute value matched with a service for metadata of a metadata object so that the metadata component is matched with the service; therefore, for a plurality of businesses, the corresponding form pages can be obtained through the layout of the corresponding metadata components, the learning process of various development languages is avoided, the development process of the form pages is further simplified, and therefore the efficiency of generating the form pages is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the present application;

FIG. 2 is a flowchart of a method for generating a form page according to an embodiment of the present application;

FIG. 3 is a flowchart of another method for generating a form page according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a structure definition of a metadata object according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an attribute value configuration provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a third generation interface provided by an embodiment of the present application;

FIG. 7 is a flow chart of generating form pages based on a metadata form designer provided by an embodiment of the application;

FIG. 8 is a flowchart of another method for generating a form page according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a first generation interface according to an embodiment of the present application;

FIG. 10 is a schematic view of a pop-up interface according to an embodiment of the present application;

FIG. 11 is an application flowchart of a method for generating a form page provided in an embodiment of the present application;

FIG. 12 is a flowchart of another method for generating a form page according to an embodiment of the present application;

FIG. 13 is a block diagram of a form page generation apparatus provided by an embodiment of the present application;

Fig. 14 is a block diagram of a terminal according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The terms "first," "second," "third," and "fourth" and the like in the description and in the claims and drawings are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprising," "including," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be noted that, the information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, presented data, etc.), and signals related to the present application are all authorized by the user or are fully authorized by the parties, and the collection, use, and processing of the related data is required to comply with the relevant laws and regulations and standards of the relevant countries and regions. For example, metadata referred to in the present application is obtained with sufficient authorization.

The method for generating the form page provided by the embodiment of the application can be executed by the electronic equipment, and in some embodiments, the electronic equipment is a terminal or a server. In the following, an implementation environment schematic diagram of a method for generating a form page according to an embodiment of the present application is described by taking an electronic device as an example. Referring to fig. 1, the implementation environment includes a terminal 10 and a server 20. The terminal 10 and the server 20 can be directly or indirectly connected through wired or wireless communication, and the present application is not limited thereto.

The terminal 10 is provided with a target application, and the server 20 is a background server 20 corresponding to the target application. The terminal can generate a form page through the target application, and the server 20 is used for providing background service for the target application to generate the form page. The terminal 10 is at least one of a mobile phone, a tablet computer, PC (Personal Computer) equipment and the like. Server 20 may be at least one of a server, a server cluster consisting of a plurality of servers, a cloud server, a cloud computing platform, and a virtualization center.

In some embodiments, the method for generating the form page provided by the embodiment of the application is widely applied to scenes of interaction with users, such as questionnaire investigation, activity registration, data acquisition, business processing and the like; after the form page is generated, the user inputs information based on the form page displayed by the terminal 10, so as to realize interaction with the user through the form page.

Fig. 2 is a method for generating a form page according to an embodiment of the present application, where an execution body is a terminal, and the method includes:

step 201: and acquiring a plurality of metadata objects corresponding to the target service.

Step 202: and configuring attribute values for metadata of the metadata objects to obtain a plurality of metadata components, wherein the metadata attribute values of each metadata object are matched with the target service.

Step 203: displaying a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface, the first sub-interface comprises a plurality of metadata components, and the second sub-interface comprises form layout information corresponding to the metadata components.

Step 204: and responding to triggering operation of the metadata components, and generating a target form page corresponding to the target service based on the form layout information and the metadata components.

based on the form layout information and the metadata components, generating a target form page corresponding to the target service comprises the following steps:

responding to triggering operation of a target general component in the plurality of general components, and adding the target general component into a first form page;

And responding to the dragging operation of any component in the first form page, and readjusting the layout of the components in the first form page based on the dragging track of any component to obtain the target form page.

and setting attribute contents of the metadata components in the first form page based on the form attribute information of the metadata components to obtain a target form page.

In some embodiments, obtaining a plurality of metadata objects corresponding to a target service includes:

and responding to the triggering operation of the service control corresponding to the target service, and acquiring a plurality of metadata objects corresponding to the target service from a metadata object library, wherein the metadata object library is used for storing metadata objects corresponding to the plurality of services respectively.

In some embodiments, configuring attribute values for metadata of a plurality of metadata objects results in a plurality of metadata components, comprising:

Displaying a third generation interface, wherein the third generation interface comprises a fourth sub-interface and a fifth sub-interface, and the fourth sub-interface comprises a plurality of metadata objects;

responding to the triggering operation of any metadata object, and displaying an attribute configuration frame of the metadata object on a fifth sub-interface;

In some embodiments, metadata of the metadata object includes at least one of an object key value, an object name, a component type, a component default value, a check rule, a data type, and a data source to which the metadata object corresponds;

configuring attribute values for metadata of a plurality of metadata objects to obtain a plurality of metadata components, including:

and for each metadata object, respectively configuring attribute values for at least one of an object key value, an object name, a component type, a component default value, a check rule, a data type and a data source corresponding to the metadata object to obtain a metadata component corresponding to the metadata object.

Fig. 3 is a method for generating a form page according to an embodiment of the present application, where the method includes:

step 301: the terminal displays a second generation interface, wherein the second generation interface comprises a plurality of business controls.

Wherein, each business control corresponds to one business, and each business can correspond to a plurality of metadata objects. In this embodiment, the services corresponding to the service controls include material basic information, material storage relationship, material purchase and storage conditions, material production and delivery conditions, and the like; accordingly, each business control corresponds to a plurality of metadata objects, for example, in the material base information business control, five metadata objects of material code, material name, material category, material specification and metering unit are corresponding. It should be noted that, the service in the embodiment of the present application may be a service corresponding to the service model, that is, the service in the embodiment of the present application generally refers to the service model.

Step 302: and the terminal responds to the triggering operation of the service control corresponding to the target service and acquires a plurality of metadata objects corresponding to the target service from the metadata object library.

The metadata object library is used for storing metadata objects corresponding to a plurality of services respectively. The metadata object is a necessary object describing the target service. For example, for the target business material basic information, the plurality of metadata objects comprise material codes, material names, material categories, material rules, measurement units and the like.

In one implementation, the terminal loads the service file in two formats, JSON (JavaScript Object Notation, JS object profile) or XML (Extensible Markup Language ), and then dynamically adapts the metadata objects in the service, storing the metadata objects in a metadata object library. In the embodiment of the application, the metadata objects corresponding to the services are stored in the metadata object library, so that the acquisition efficiency of the metadata objects corresponding to the services is improved, and the efficiency of generating metadata components based on the metadata objects in the follow-up process can be improved.

Step 303: the terminal configures attribute values for metadata of the plurality of metadata objects to obtain a plurality of metadata components.

Wherein the metadata attribute value of each metadata object matches the target service.

In some embodiments, the terminal configures attribute values for metadata of a plurality of metadata objects to obtain a plurality of metadata components, including the steps of: the terminal displays a third generation interface, wherein the third generation interface comprises a fourth sub-interface and a fifth sub-interface, and the fourth sub-interface comprises a plurality of metadata objects; the terminal responds to the triggering operation of any metadata object, and an attribute configuration frame of the metadata object is displayed on a fifth sub-interface; and the terminal responds to the input operation of the attribute configuration frame, acquires the attribute value in the attribute configuration frame, configures the attribute value for the metadata of the metadata object, and obtains the metadata component corresponding to the metadata object.

The metadata is data for describing the data, namely, the data describing the metadata object, and the more accurate the definition of the metadata object by the metadata is, the faster the understanding of the data and the more sufficient the mining of the data can be. With the use of new scenes, new modes, new technologies in software Development, and the like, such as a field model, agile Development, and DevOps (a combination of Development and Operations, which are a set of processes, methods, and systems), the role and value of metadata become particularly important. In some embodiments, the terminal determines metadata corresponding to the metadata object based on defining a metadata object structure, the metadata object structure definition comprising a plurality of structured nodes, made up of metadata corresponding to the metadata object.

Optionally, the metadata of the metadata object includes at least one of an object key value, an object name, a component type, a component default value, a check rule, a data type, and a data source corresponding to the metadata object. Correspondingly, the terminal configures attribute values for metadata of a plurality of metadata objects to obtain a plurality of metadata components, and the method comprises the following steps: and the terminal configures attribute values for at least one of an object key value, an object name, a component type, a component default value, a check rule, a data type and a data source corresponding to the metadata object for each metadata object respectively to obtain a metadata component corresponding to the metadata object. In the embodiment of the application, the metadata object can be effectively described due to the object key value, the object name, the component type, the component default value, the check rule, the data type, the data source and the like corresponding to the metadata object, and the generated metadata component is more matched with the metadata object by configuring the attribute values for the metadata.

Wherein the component type includes at least one of a text box, a radio box, a drop down box, a list box, and the like. The component default value is a default value set for a metadata component, such as for metadata object gender, and the corresponding component default value may be either female or male. The checking rule is used for checking the input value of the metadata component; for example, for the metadata object identification card number, the verification rule is to verify whether the input identification card number is 18 bits. The data type includes at least one of a boolean type, a byte type, a short integer type, an integer type, a long integer type, a character type, a single precision floating point type, a double precision floating point type, and the like. The data sources include at least one of table field sources, SQL (Structured Query Language ) statement sources, interface return value sources, data dictionary sources, and the like, without limitation.

It should be noted that, metadata of the metadata object further includes a CSS (Cascading Style Sheets, cascading style sheet) class name corresponding to the metadata object, and metadata of a custom extensible mechanism; such as a display type, for indicating whether the metadata component is displayed or hidden in the form page; the underlying engine technology provides an extensible mechanism for metadata object structure definition, so that metadata objects can also customize metadata. Referring to fig. 4, fig. 4 is a schematic diagram of defining a metadata object structure according to an embodiment of the present application, where a plurality of structure nodes are respectively an object key value, an object name, a component type, a component default value, a check rule, a CSS class name, a data type, and a data source corresponding to a metadata object.

In some embodiments, the terminal configures attribute values for metadata of the plurality of metadata objects through the metadata object designer to obtain a plurality of metadata components, i.e., the third generated interface is an interface in the metadata object designer. Referring to fig. 5, fig. 5 is a schematic diagram of an attribute value configuration according to an embodiment of the present application; one business may correspond to a plurality of business fields, for example, the business fields corresponding to the material basic information business include a material code, a material name, a material specification, a material category, a metering unit, and the like. The terminal configures attribute values for metadata of metadata objects corresponding to different service fields based on the metadata object designer, and stores the configured attribute values into a metadata object library to obtain a metadata assembly.

In the embodiment of the application, the positions of the fourth sub-interface and the fifth sub-interface in the third generation interface can be set and changed according to the needs; optionally, the fourth sub-interface and the fifth sub-interface are located to the left and right of the third sub-interface, respectively. Referring to fig. 6, fig. 6 is a schematic diagram of a third generation interface provided in an embodiment of the present application, where the third generation interface includes a fourth sub-interface on the left side and a fifth sub-interface on the right side; the fourth sub-interface includes a plurality of metadata objects, where the plurality of metadata objects corresponds to a plurality of services, and one service may correspond to a plurality of metadata objects. As shown in fig. 6, the terminal responds to the triggering of the metadata object material coding, and displays an attribute configuration box of the material coding on a fifth sub-interface, wherein the attribute configuration box comprises an object key value, an object name, a component type, a component default value, a check rule, a data type, a data source and a CSS class name of the metadata object material coding.

In some embodiments, after the terminal configures the attribute value for the metadata of the metadata object, the attribute value is further saved in the metadata object library, so as to facilitate subsequent searching and use. It should be noted that, when the plurality of services include the same metadata object, the terminal may automatically configure the attribute value for the metadata of the metadata object in the other services in response to configuring the attribute value for the metadata of the same metadata object in any service, thereby avoiding a repeated process of sequentially configuring the attribute value for the same metadata object in the plurality of services, and thus improving efficiency of configuring the attribute value for the metadata.

It should be noted that, after the metadata of any metadata object is configured with the attribute value, the attribute value of the metadata may be changed to obtain a new metadata object and store the new metadata object, so as to implement customization of the metadata object. If the metadata object mobile phone number is reconfigured to change the object name into the contact way, a new metadata object, namely the contact way, is obtained.

In the embodiment of the application, the metadata object designer configures attribute values for metadata of metadata objects of different services, namely, metadata objects with stronger universality are provided for service personnel in a component mode, so that a great amount of repeated design work in the front-end form page development process is reduced, and the self-definition needs of different services on the front-end form page design can be met based on the attribute values matched with the target service for metadata configuration of the metadata objects, so that the expansibility is enhanced. Alternatively, the metadata object designer is used by operators and configurators.

In some embodiments, after a terminal obtains a metadata component based on a metadata configuration attribute value of a metadata object corresponding to a target service, a corresponding relation between the target service and a plurality of metadata components corresponding to the target service is established, and the corresponding relation is stored in a metadata object library, so that when a form page of the target service is generated subsequently, the corresponding metadata component can be directly obtained from the metadata object library; after the subsequent terminal obtains the metadata component corresponding to the target service from the metadata object library, step 304 is executed to generate a form page of the target service. It should be noted that, when the metadata object library does not include any business of a form page to be generated, attribute values need to be configured for metadata of metadata objects corresponding to the business to obtain metadata components corresponding to the business, and the metadata components are stored in the metadata object library, so that the integrity of data in the metadata object library and the timeliness of data update are ensured.

In some embodiments, after the terminal generates the metadata component corresponding to the target service, step 304 may also be directly performed to generate a form page of the target service directly based on the metadata component.

Step 304: the terminal displays a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface.

The first sub-interface comprises a plurality of metadata components, and the second sub-interface comprises form layout information corresponding to the metadata components.

Step 305: and the terminal responds to the triggering operation of the metadata components, and generates a target form page corresponding to the target service based on the form layout information and the metadata components.

The form layout information of the metadata components may be set and changed as needed. Optionally, if the form layout information of the metadata components is default form layout information of the terminal, the terminal responds to a trigger operation on the metadata components, and arranges the metadata components on the second sub-interface according to the default form layout information, so as to obtain the target form page.

In some embodiments, the form layout information includes location information of any of the plurality of metadata components in the form page; in one implementation, the terminal responds to the triggering operation of any metadata component, and based on the position information of the metadata component in the form page in the form layout information, the metadata component is arranged in a second sub-interface to obtain a target form page. In another implementation, the terminal responds to the drag operation of any metadata component, and the metadata component is distributed on a second sub-interface based on the drag track of the metadata component; wherein the drag track of the metadata component matches the position information of the metadata component in the form page.

In some embodiments, the terminal generates the second form page based on the form layout information and the plurality of metadata components in response to a triggering operation on the plurality of metadata components. And the terminal responds to the drag operation of any metadata component in the second form page, and readjusts the layout of the metadata component in the second form page based on the drag track of any metadata component to obtain the target form page.

In some embodiments, the terminal responds to the drag operation of any metadata component in the first sub-interface, and lays out the metadata component in the second sub-interface based on the drag track of any metadata component to obtain a target form page; wherein the second sub-interface is a blank interface.

In some embodiments, the first generation interface further includes a third sub-interface including form attribute information for the plurality of metadata components; correspondingly, the terminal generates a target form page corresponding to the target service based on the form layout information and the metadata components, and the method comprises the following steps: the terminal generates a first form page based on the form layout information and the metadata components; and the terminal sets the attribute content of the metadata component in the first form page based on the form attribute information of the metadata components to obtain a target form page. Optionally, the attribute contents include at least one of a component type, a component icon, a component size, a component style, a component color, a display type, and the like of the metadata component, which are not particularly limited herein. In the embodiment, the attribute content of the metadata component is set by setting the third sub-interface, so that flexible adjustment of the attribute content of the metadata component is realized, and the layout of the metadata component in the form page is more reasonable and attractive. Optionally, after the terminal generates the target form page, the target form page is stored in the form page object library, so that the subsequent acquisition of the form page is facilitated.

In some embodiments, the terminal implements steps 304-305 based on passing through the metadata form designer, i.e., the first generated interface is an interface in the metadata form designer; in the embodiment of the application, the metadata component is arranged to replace the UI component (USER INTERFACE Module, user interface component) in the prior art, so that the technical performance is shielded, the business performance is highlighted, related business personnel can develop the form page based on triggering, dragging, layout, design and the like of the metadata component, the development and generation of the form page become simple and efficient, the configuration, namely the development and design, namely the development are realized, the development difficulty is reduced, and the development efficiency is improved. Alternatively, the metadata form designer is used by business personnel, demand personnel, designers, and the like.

Referring to fig. 7, fig. 7 is a flowchart of generating a form page based on a metadata form designer according to an embodiment of the present application, which mainly includes: the terminal responds to the selection of any service, loads a metadata object corresponding to a target service of the service, then lays out a metadata component based on the triggering and dragging operation of the metadata component of the metadata object, sets the page attribute of the metadata component to generate a form page object, and stores the generated form page into a form page object library, so that the rapid development of the form page is completed; and loading the form page from the form page object library for display.

Fig. 8 is a method for generating a form page according to an embodiment of the present application, where the method includes:

step 801: the terminal displays a second generation interface, wherein the second generation interface comprises a plurality of business controls.

Step 802: and the terminal responds to the triggering operation of the service control corresponding to the target service and acquires a plurality of metadata objects corresponding to the target service from the metadata object library.

Step 803: the terminal configures attribute values for metadata of the plurality of metadata objects to obtain a plurality of metadata components.

Step 804: the terminal displays a first generation interface, wherein the first generation interface comprises a first sub-interface and a second sub-interface.

Steps 801-804 are the same as steps 301-304 and are not described in detail herein.

Step 805: the terminal responds to triggering operation of the metadata components, and generates a first form page based on the form layout information and the metadata components.

The implementation manner of generating the first form page in step 805 is the same as the implementation manner of generating the target form page in step 305, and will not be described herein.

It should be noted that, if the first sub-interface does not include a general component or the general component does not need to be laid out in the target form page, the first form page is used as the target form page corresponding to the target service. If the first sub-interface includes a generic component and the generic component needs to be laid out in the target form page, steps 806-807 are executed to obtain the target form page corresponding to the target service.

Step 806: the terminal responds to triggering operation of a target general component in the plurality of general components, and the target general component is added to the first form page.

The first sub-interface also comprises a plurality of general components, and the general components are components shared by a plurality of services. Such as general components including a picture upload component, a file upload component, an editor component, a separator component, etc., are not specifically limited herein.

In some embodiments, the terminal adds the target generic component to the first form page and arranges behind the metadata component in response to a trigger operation on the target generic component. In other embodiments, the second sub-interface further includes form layout information of the target general component, and the terminal responds to the trigger operation on the target general component and adds the target general component to the first form page based on the form layout information, so that the position of the target general component in the first form page corresponds to the form layout information.

In some embodiments, the terminal responds to a drag operation on the target general component, and adds the target general component to the first form page based on a drag track of the target general component, so that the position of the target general component in the first form page corresponds to the drag track.

It should be noted that, if the layout of the components in the first form page does not need to be adjusted, the first form page is used as the target form page corresponding to the target service. If the layout of the components in the first form page still needs to be adjusted, step 807 is executed to obtain the target form page corresponding to the target service.

Step 807: and the terminal responds to the dragging operation of any component in the first form page, and readjusts the layout of the components in the first form page based on the dragging track of any component to obtain the target form page.

In some embodiments, the first generation interface further includes a third sub-interface including form attribute information for the plurality of metadata components and further including form attribute information for the plurality of generic components. Accordingly, the terminal can set attribute contents of the plurality of components in the first form page based on form attribute information of the plurality of components formed by the plurality of metadata components and the plurality of general components, so as to obtain a target form page.

In the embodiment of the application, the components for generating the form page are arranged based on the metadata object, so that any business personnel can generate the form page through the metadata component, the whole generation process of the form page is avoided, the dependence on the technical personnel is reduced, the development of the front-end form page is mapped from the technical view to the business view, and the rapid development and generation of the front-end form page are realized through definition of the metadata object, metadata attribute value configuration of the metadata object and visual design of the metadata form. In addition, the embodiment of the application shields the diversity of the existing form equipment and the diversity of the UI component library through the metadata object definition component, and reduces the difficulty of front-end development and the technical dependence on technicians.

In some embodiments, the first generation interface further includes a sixth sub-interface, which is a form list page including a plurality of business controls. And the terminal responds to the triggering operation of any business control, and displays the metadata component of the business corresponding to the business control on the first sub-interface. Referring to fig. 9, fig. 9 is a schematic diagram of a first generation interface provided in an embodiment of the present application, where a sixth sub-interface, a first sub-interface, a second sub-interface, and a third sub-interface are sequentially arranged on the first generation interface from left to right. The second sub-interface also comprises a query button, a new button and a delete button. The new adding button is used for adding new data in the form page corresponding to the second sub-interface. The terminal is used for jumping out of a popup window in response to the trigger of the newly added button, and the popup window comprises a data input box so as to add new data based on the data input in the data input box. Referring to fig. 10, fig. 10 is a schematic diagram of a pop-up interface according to an embodiment of the present application, where the pop-up interface includes a data input box with a plurality of metadata objects, and the terminal obtains input data in response to an input operation of the data input box, and further generates a new data record based on the obtained data, and displays the new data record in a table of the second sub-interface shown in fig. 9. The delete button is used for deleting any selected data record in the second sub-interface. The query button is used for querying the data records meeting the preset conditions in the table shown in fig. 9. And the preview of the target form page can be realized through the second sub-interface. The third sub-interface also comprises a conventional button and a high-level button which are respectively used for realizing page attribute setting of different display contents in the first form page. As seen in fig. 9, the third sub-interface in the drawing is an interface displayed in response to a trigger to a regular button, and form attribute information that can be set includes a label alignment manner, a form field width, a component size, a popup width, a popup window top width, a design movement view, a big data pattern, CSS enhancement, JS (JavaScript, a programming language) enhancement, and the like.

Referring to fig. 11, fig. 11 is an application flowchart of a method for generating a form page according to an embodiment of the present application, where the application flowchart is composed of two dimensions, namely, a longitudinal flow and a transverse flow; the transverse dimension is divided into three layers of design state, development state and running state, and the longitudinal dimension is divided into three layers of data layer, technology realization layer and user layer. As can be seen from the figure, the method for generating the form page provided by the embodiment of the application decouples the technical layer and the service layer for generating the form page, reduces the dependence on technicians, and enables the service personnel to complete the development and generation of the form page based on the method provided by the embodiment of the application. And for the design state or development state of the transverse dimension, the metadata component is used for generating the form page, so that the source code which is loaded, analyzed and generated is more standard, and the quality and performance of the code are improved, and meanwhile, the user experience is also improved. And through the sharing of metadata objects, repeated design work is reduced, and the development and generation efficiency of the form page is improved. And the individuation of different services is satisfied by the self-definition of the metadata object, so that the adaptation degree of the metadata object and the services is improved.

Referring to fig. 12, fig. 12 is a flowchart of a method for generating a form page according to an embodiment of the present application, including the following 5 steps. Firstly, business personnel do demand analysis offline. And secondly, the business personnel design a business model based on demand analysis, map the business model into fields in a data model, wherein the data model consists of metadata objects corresponding to the business, and the fields comprise the metadata objects. Thirdly, the service personnel uses the metadata object designer to configure attribute values for metadata of the metadata object, and the configurator uses the metadata object designer to customize the extension content (technical support is needed) of the metadata object structure. And fourthly, the business personnel uses a metadata form designer to design the form page, and generates the form page. And fifthly, the terminal stores the form page, and when receiving the request of the form page, the terminal loads and analyzes the form page and then presents the content of the form page.

It should be noted that, the method for generating the form page provided by the embodiment of the application can also be applied to workflow development; for each workflow instance, the terminal configures attribute values of environment variables, form information, event listeners and event triggers by means of a workflow designer; the terminal configures the attribute values based on the metadata object comprises the following steps: the terminal stores and configures the attribute values of the environment variables, the form information, the monitor and the trigger in the workflow process through the metadata object, and interfaces the workflow designer with the metadata object, so that the attribute value configuration of the environment variables, the form information, the monitor and the trigger in the workflow process is realized. In this way, when the workflow process is deployed, metadata objects are converted into environment variables, form information, attributes of listeners and triggers which can be identified by a process engine of the workflow, so that the development of the workflow is simpler, more convenient and more efficient.

In the embodiment of the application, the general component is arranged to generate the form page, so that the layout of the form page is more flexible and complete; and the layout of the components in the first form page can be readjusted through the dragging operation of any component in the first form page, so that the flexibility of page layout is further improved, and the generation of the form page is simpler and more efficient.

The embodiment of the application also provides a device for generating the form page, referring to fig. 13, the device comprises:

an obtaining module 1301, configured to obtain a plurality of metadata objects corresponding to a target service;

a configuration module 1302, configured to configure attribute values for metadata of a plurality of metadata objects, so as to obtain a plurality of metadata components, where the metadata attribute value of each metadata object is matched with a target service;

the display module 1303 is configured to display a first generation interface, where the first generation interface includes a first sub-interface and a second sub-interface, the first sub-interface includes a plurality of metadata components, and the second sub-interface includes form layout information corresponding to the plurality of metadata components;

the generating module 1304 is configured to generate, in response to a triggering operation on the plurality of metadata components, a target form page corresponding to the target service based on the form layout information and the plurality of metadata components.

In some embodiments, the first sub-interface further includes a plurality of generic components therein; a generating module 1304 for:

In some embodiments, the first generation interface further includes a third sub-interface including form attribute information for the plurality of metadata components; a generating module 1304 for:

and setting display contents of the metadata components in the first form page based on the form attribute information of the metadata components to obtain a target form page.

In some embodiments, the obtaining module 1301 is configured to:

In some embodiments, the configuration module 1302 is configured to:

In some embodiments, metadata of the metadata object includes at least one of an object key value, an object name, a component type, a component default value, a check rule, a data type, and a data source to which the metadata object corresponds; a configuration module 1302 for:

In some embodiments, the electronic device is configured as a terminal; fig. 14 shows a block diagram of a terminal 1400 provided by an exemplary embodiment of the present application. The terminal 1400 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 1400 may also be referred to as a user device, a portable terminal, a laptop terminal, a desktop terminal, and the like.

In general, terminal 1400 includes: a processor 1401 and a memory 1402.

Processor 1401 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 1401 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 1401 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 1401 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and rendering of content that the display screen is required to display. In some embodiments, the processor 1401 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

Memory 1402 may include one or more computer-readable storage media, which may be non-transitory. Memory 1402 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1402 is used to store at least one program code for execution by processor 1401 to implement the method of generating a form page provided by an embodiment of the method in the present application.

In some embodiments, terminal 1400 may optionally further include: a peripheral interface 1403 and at least one peripheral. The processor 1401, memory 1402, and peripheral interface 1403 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 1403 via buses, signal lines or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1404, a display screen 1405, a camera assembly 1406, an audio circuit 1407, a positioning assembly 1408, and a power source 1409.

Peripheral interface 1403 may be used to connect at least one Input/Output (I/O) related peripheral to processor 1401 and memory 1402. In some embodiments, processor 1401, memory 1402, and peripheral interface 1403 are integrated on the same chip or circuit board; in some other embodiments, either or both of processor 1401, memory 1402, and peripheral interface 1403 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 1404 is configured to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1404 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 1404 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1404 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuit 1404 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuit 1404 may also include NFC (Near Field Communication, short-range wireless communication) related circuits, which the present application is not limited to.

The display screen 1405 is used to display UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1405 is a touch display screen, the display screen 1405 also has the ability to collect touch signals at or above the surface of the display screen 1405. The touch signal may be input to the processor 1401 as a control signal for processing. At this time, the display 1405 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 1405 may be one, disposed on the front panel of the terminal 1400; in other embodiments, the display 1405 may be at least two, respectively disposed on different surfaces of the terminal 1400 or in a folded design; in other embodiments, the display 1405 may be a flexible display disposed on a curved surface or a folded surface of the terminal 1400. Even more, the display 1405 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The display 1405 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

The camera component 1406 is used to capture images or video. Optionally, camera assembly 1406 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 1406 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.

The audio circuitry 1407 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1401 for processing, or inputting the electric signals to the radio frequency circuit 1404 for voice communication. For purposes of stereo acquisition or noise reduction, a plurality of microphones may be provided at different portions of the terminal 1400, respectively. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 1401 or the radio frequency circuit 1404 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, audio circuitry 1407 may also include a headphone jack.

The locating component 1408 is used to locate the current geographic location of the terminal 1400 to enable navigation or LBS (Location Based Service, location-based services). The positioning component 1408 may be a positioning component based on the united states GPS (Global Positioning System ), the chinese beidou system, or the russian galileo system.

A power supply 1409 is used to power the various components in terminal 1400. The power supply 1409 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 1409 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1400 also includes one or more sensors 1140. The one or more sensors 1140 include, but are not limited to: acceleration sensor 1411, gyroscope sensor 1412, pressure sensor 1413, fingerprint sensor 1414, optical sensor 1415, and proximity sensor 1416.

The acceleration sensor 1411 may detect the magnitudes of accelerations on three coordinate axes of a coordinate system established with the terminal 1400. For example, the acceleration sensor 1411 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 1401 may control the display screen 1405 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal acquired by the acceleration sensor 1411. The acceleration sensor 1411 may also be used for the acquisition of motion data of a game or a user.

The gyro sensor 1412 may detect a body direction and a rotation angle of the terminal 1400, and the gyro sensor 1412 may collect a 3D motion of the user to the terminal 1400 in cooperation with the acceleration sensor 1411. The processor 1401 may implement the following functions based on the data collected by the gyro sensor 1412: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

Pressure sensor 1413 may be disposed on a side frame of terminal 1400 and/or on an underside of display 1405. When the pressure sensor 1413 is provided at a side frame of the terminal 1400, a grip signal of the terminal 1400 by a user can be detected, and the processor 1401 performs right-and-left hand recognition or quick operation according to the grip signal collected by the pressure sensor 1413. When the pressure sensor 1413 is disposed at the lower layer of the display screen 1405, the processor 1401 realizes control of the operability control on the UI interface according to the pressure operation of the user on the display screen 1405. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The fingerprint sensor 1414 is used to collect a fingerprint of a user, and the processor 1401 identifies the identity of the user based on the fingerprint collected by the fingerprint sensor 1414, or the fingerprint sensor 1414 identifies the identity of the user based on the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the user is authorized by the processor 1401 to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 1414 may be disposed on the front, back, or side of the terminal 1400. When a physical key or vendor Logo is provided on terminal 1400, fingerprint sensor 1414 may be integrated with the physical key or vendor Logo.

The optical sensor 1415 is used to collect the ambient light intensity. In one embodiment, processor 1401 may control the display brightness of display screen 1405 based on the intensity of ambient light collected by optical sensor 1415. Specifically, when the intensity of the ambient light is high, the display luminance of the display screen 1405 is turned high; when the ambient light intensity is low, the display luminance of the display screen 1405 is turned down. In another embodiment, the processor 1401 may also dynamically adjust the shooting parameters of the camera assembly 1406 based on the ambient light intensity collected by the optical sensor 1415.

A proximity sensor 1416, also referred to as a distance sensor, is typically provided on the front panel of terminal 1400. The proximity sensor 1416 is used to collect the distance between the user and the front of the terminal 1400. In one embodiment, when proximity sensor 1416 detects a gradual decrease in the distance between the user and the front of terminal 1400, processor 1401 controls display 1405 to switch from the on-screen state to the off-screen state; when the proximity sensor 1416 detects that the distance between the user and the front surface of the terminal 1400 gradually increases, the processor 1401 controls the display 1405 to switch from the off-screen state to the on-screen state.

Those skilled in the art will appreciate that the structure shown in fig. 14 is not limiting and that terminal 1400 may include more or less components than those illustrated, or may combine certain components, or employ a different arrangement of components.

The embodiment of the application also provides a computer readable storage medium, at least one program code is stored in the computer readable storage medium, and the at least one program code is loaded and executed by a processor to realize the method for generating the form page in any implementation mode.

The embodiment of the application also provides a computer program product, which comprises a computer program, wherein the computer program realizes the generation method of the form page in any implementation mode when being executed by a processor.

In some embodiments, a computer program product according to embodiments of the present application may be deployed for execution on one electronic device or on multiple electronic devices located at one site, or alternatively, for execution on multiple electronic devices distributed across multiple sites and interconnected by a communication network, where the multiple electronic devices distributed across multiple sites and interconnected by a communication network may constitute a blockchain system.

The foregoing is illustrative of the present application and is not to be construed as limiting thereof, but rather as various modifications, equivalent arrangements, improvements, etc., which fall within the spirit and principles of the present application.

Claims

1. A method for generating a form page, the method comprising:

acquiring a plurality of metadata objects corresponding to a target service;

2. The method of claim 1, wherein the first sub-interface further comprises a plurality of generic components therein;

3. The method of claim 1, wherein the first generation interface further comprises a third sub-interface comprising form attribute information for the plurality of metadata components;

and setting page attributes of the metadata components in the first form page based on the form attribute information of the metadata components to obtain the target form page.

4. The method according to claim 1, wherein the obtaining a plurality of metadata objects corresponding to the target service includes:

5. The method of claim 1, wherein configuring attribute values for metadata of the plurality of metadata objects results in a plurality of metadata components, comprising:

6. The method of any of claims 1-5, wherein the metadata of the metadata object includes at least one of an object key, an object name, a component type, a component default, a validation rule, a data type, and a data source to which the metadata object corresponds;

7. A form page generation apparatus, the apparatus comprising:

8. An electronic device comprising one or more processors and one or more memories, the one or more memories having stored therein at least one piece of program code that is loaded and executed by the one or more processors to implement the method of generating a form page of any of claims 1-6.

9. A computer readable storage medium having stored therein at least one program code, the at least one program code being loaded and executed by a processor to implement the method of generating a form page of any one of claims 1 to 6.

10. A computer program product comprising a computer program which, when executed by a processor, implements the form page generation method of any one of claims 1 to 6.