Form page generation method and device, form page use method and device and terminal

Abstract

The invention provides a form page generation method and device, a form page use method and device and a terminal, and belongs to the technical field of computers. The method comprises the steps that a form configuration page of a target activity model is displayed, the form configuration page comprises a meta-component area and a form layout area, the meta-component area comprises multiple meta-components, the multiple meta-components are generated based on service data of multiple activity models, and one meta-component is used for achieving one service sub-logic in the activity model; in response to a selection operation on any one of the plurality of meta-components, adding the meta-components to the form layout area; based on the business data of the target activity model, performing attribute configuration on the meta-component in the form layout area to obtain the meta-component after attribute configuration; in response to confirmation operation on content displayed in the form layout area, a form page corresponding to the target activity model is obtained, and the content displayed in the form layout area comprises the meta-components with the configured attributes. According to the scheme, the efficiency and convenience of generating the form page are improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method for generating a form page, a method for using the form page, a device and a terminal. Background Art

[0002] With the development of computer technology, form pages are increasingly used in various activity models. An activity model is an activity form used to implement specific business logic. For example, a lottery activity model is used to implement the lottery business logic in a lottery activity. Form pages are used to configure the business parameters required by the activity model logic. Before the form page is applied, technical personnel are required to develop and generate the form page.

[0003] In the related art, form pages are generally customized and developed according to activity models. During the development process, the designer of the form page needs to communicate frequently with the front-end developer and the back-end developer so that the front-end developer can develop a form page that meets both the designer's needs and the back-end business logic. This method makes the development of form pages slower, thereby reducing the efficiency of generating form pages. Summary of the invention

[0004] The embodiment of the present application provides a method for generating a form page, a method for using the form page, a device and a terminal, which improves the efficiency and convenience of generating the form page. The technical solution is as follows:

[0005] In one aspect, a method for generating a form page is provided, which is applied to a first terminal, and the method includes:

[0006] Displaying a form configuration page of a target activity model, the form configuration page comprising a meta component area and a form layout area, the meta component area comprising a plurality of meta components, the plurality of meta components being generated based on business data of a plurality of activity models, one meta component being used to implement a business sub-logic in an activity model, the target activity model being an activity model among the plurality of activity models;

[0007] In response to a selection operation on any one of the plurality of component elements, adding the component element to the form layout area;

[0008] Based on the business data of the target activity model, attribute configuration is performed on the meta-components in the form layout area to obtain the meta-components after the attribute configuration;

[0009] In response to a confirmation operation on the content displayed in the form layout area, a form page corresponding to the target activity model is obtained, and the content displayed in the form layout area includes the meta-component after the configuration attributes.

[0010] On the other hand, a method for using a form page is provided, which is applied to a second terminal, and the method includes:

[0011] Sending a form acquisition request of a target activity model to a first terminal, wherein the form acquisition request is used to request to acquire a form page of the target activity model, wherein the form page is generated based on a meta-component and business data of the target activity model, wherein the meta-component is generated based on business data of multiple activity models, wherein one meta-component is used to implement one business sub-logic in the activity model, and wherein the target activity model is an activity model among the multiple activity models;

[0012] receiving a form identifier of a form page of the target activity model returned by the first terminal;

[0013] Based on the form identifier, obtaining form description data corresponding to the form identifier from a form server, the form server being used to store form description data and form identifiers of a plurality of form pages correspondingly, the form description data being used to render the form page;

[0014] Page rendering is performed based on the form description data to display the form page of the target activity model, and data configuration is performed on the form page.

[0015] On the other hand, a device for generating a form page is provided, the device comprising:

[0016] A display module, configured to display a form configuration page of a target activity model, wherein the form configuration page includes a meta component area and a form layout area, wherein the meta component area includes a plurality of meta components, wherein the plurality of meta components are generated based on business data of a plurality of activity models, and a meta component is used to implement a business sub-logic in an activity model, and the target activity model is an activity model among the plurality of activity models;

[0017] An adding module, configured to add any one of the plurality of element components to the form layout area in response to a selection operation on the element component;

[0018] A configuration module, configured to configure the attributes of the meta-components in the form layout area based on the business data of the target activity model, and obtain the meta-components after the attributes are configured;

[0019] A confirmation module is used to obtain a form page corresponding to the target activity model in response to a confirmation operation on the content displayed in the form layout area, wherein the content displayed in the form layout area includes the meta-component after the configuration attributes.

[0020] In some embodiments, the adding module is used to:

[0021] In response to a touch operation on any one of the plurality of component components, adding the component component to a reference sub-region in the form layout region;

[0022] In response to a drag operation on any one of the plurality of component components, the component is added to a sub-region corresponding to the drag operation in the form layout region.

[0023] In some embodiments, the adding module is used to:

[0024] In response to a touch operation on any one of the plurality of component components, determining a reference sub-region corresponding to the component component from a first form template, and adding the component component to the reference sub-region, wherein the first form template is used to indicate sub-regions in a form layout region corresponding to the plurality of component components respectively; or

[0025] In response to a touch operation on any component among the multiple components, an area after the display sub-area of ​​the last added component is used as the reference sub-area, and the component is added to the reference sub-area.

[0026] In some embodiments, the component area includes a plurality of sub-areas, and the plurality of sub-areas respectively display components of different types; the adding module is used to:

[0027] In response to a touch operation on a component in any of the multiple sub-areas, based on the type of the component corresponding to the sub-area, a reference sub-area corresponding to the type is determined from a second form template, and the component is added to the reference sub-area, wherein the second form template is used to indicate sub-areas in the form layout area corresponding to multiple types of component components.

[0028] In some embodiments, the device further comprises an adjustment module for

[0029] In response to a drag operation on any element in the form layout area, the display area of ​​the element is adjusted so that the adjusted element is displayed in a sub-area corresponding to the drag operation in the form layout area.

[0030] In some embodiments, the adding module is used to:

[0031] In response to a drag operation on any one of the plurality of component components, the component component is added to a sub-region corresponding to the drag operation in the form layout region, and a plurality of component components associated with the component component in the plurality of component components are highlighted; in response to a selection operation on any one of the associated plurality of component components, the selected component component is added to the form layout region; or,

[0032] In response to a touch operation on any one of the multiple components, multiple components associated with the component are highlighted; in response to a selection operation on the component and any one of the multiple associated components, the selected component is added to the form layout area.

[0033] In some embodiments, the adding module is used to:

[0034] In response to a selection operation on any one of the plurality of component components, the component component and component components associated with the component in the plurality of component components are added to the form layout area respectively.

[0035] In some embodiments, the business data includes sub-data corresponding to a plurality of meta-components, and the configuration module is used to:

[0036] In response to an attribute configuration operation on any meta-component in the form layout area, target sub-data corresponding to the meta-component is acquired from the business data, attribute data of the meta-component is configured based on the target sub-data, and the meta-component after attribute configuration is obtained.

[0037] In some embodiments, the configuration module is used to:

[0038] In response to a touch operation on any element in the form layout area, displaying an attribute configuration area of ​​the element on the form configuration page, the attribute configuration area being used to configure attributes of the element, and the attribute configuration area including at least one attribute configuration box;

[0039] In response to an input operation on the attribute configuration box, the input data is configured as attribute data of the meta-component to obtain a meta-component after the attributes are configured, and the input data includes the business data of the target activity model.

[0040] In some embodiments, the attribute configuration area includes a first sub-area and a second sub-area, the first sub-area is used to perform general attribute configuration on the meta-component, and the second sub-area is used to perform business attribute configuration on the meta-component based on business data of the target activity model.

[0041] In some embodiments, the apparatus further comprises:

[0042] An acquisition module, configured to acquire form description data and a form identifier corresponding to the form page in response to a confirmation operation on the content displayed in the form layout area, wherein the form description data is used to render the form page;

[0043] A storage module, used for storing the form description data and the form identifier corresponding to the form page in the form server;

[0044] The transceiver module is used to return the form identifier of the form page to the second terminal in response to receiving a form acquisition request for the target activity model from the second terminal, and the second terminal is used to obtain the form description data corresponding to the form identifier from the form server based on the form identifier, so as to render the form page based on the form description data.

[0045] In some embodiments, the acquisition module is used to:

[0046] In response to a confirmation operation on the content displayed in the form layout area, acquiring form description data corresponding to the form page;

[0047] Sending the form description data of the form page to the form server, the form server is used to generate a form identifier of the form page, and store the form description data and the form identifier of the form page in correspondence;

[0048] Receive the form identifier of the form page returned by the form server.

[0049] In some embodiments, the apparatus further comprises:

[0050] a sending module, configured to send update indication information to the second terminal in response to an update operation on any form description data in the form server, wherein the update indication information carries a form identifier corresponding to the updated form description data and is configured to indicate that the form description data corresponding to the carried form identifier is updated; or

[0051] The instruction module is used for instructing the form server to send the updated form description data to the second terminal in response to an update operation on any form description data in the form server.

[0052] In another aspect, a device for using a form page is provided, the device comprising:

[0053] a sending module, configured to send a form acquisition request of a target activity model to a first terminal, wherein the form acquisition request is used to request to acquire a form page of the target activity model, wherein the form page is generated based on a meta-component and business data of the target activity model, wherein the meta-component is generated based on business data of multiple activity models, wherein one meta-component is used to implement one business sub-logic in the activity model, and wherein the target activity model is an activity model among multiple activity models;

[0054] A receiving module, configured to receive a form identifier of a form page of the target activity model returned by the first terminal;

[0055] An acquisition module, configured to acquire form description data corresponding to the form identifier from a form server based on the form identifier, wherein the form server is configured to store form description data and form identifiers of a plurality of form pages correspondingly, and the form description data is used to render a form page;

[0056] The display module is used to perform page rendering based on the form description data to display the form page of the target activity model and perform data configuration on the form page.

[0057] In some embodiments, the display module is used to:

[0058] Based on the generation method of the form description data, the form description data is parsed to obtain form structure information of the form page, wherein the form structure information includes layout information of multiple areas in the form page and information of element components included in the multiple areas;

[0059] Page rendering is performed based on the form structure information to display the form page of the target activity model.

[0060] In some embodiments, the form description data further includes format information of multiple element components in the form page, and the format information is used to indicate the input format of data corresponding to the multiple element components; the device further includes:

[0061] A verification module is used to verify the data input in the form page based on the format information.

[0062] On the other hand, a terminal is provided, comprising a processor and a memory, wherein the memory is used to store at least one program, and the at least one program is loaded and executed by the processor to implement the method for generating a form page or the method for using a form page in an embodiment of the present application.

[0063] On the other hand, a computer-readable storage medium is provided, in which at least one program is stored. The at least one program is loaded and executed by a processor to implement the method for generating a form page or the method for using a form page in an embodiment of the present application.

[0064] On the other hand, a computer program product is provided, which includes a computer program code, and the computer program code is stored in a computer-readable storage medium. A processor of a terminal reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, so that the terminal executes the method for generating a form page or the method for using a form page described in any of the above-mentioned implementations.

[0065] The embodiment of the present application provides a method for generating a form page, which displays multiple meta-components on a form configuration page, and these meta-components are generated based on the business data of multiple active models, and are respectively used to implement a business sub-logic in the active model. In this way, when the scheme configures the form page of any active model, the business logic of the active model can be implemented by directly configuring the meta-components required in these meta-components to the form page without the participation of backend developers. And on the form configuration page, the properties of the meta-components can also be configured based on the business data, so that ordinary personnel can also configure the business data to the form page without the need for backend personnel development. The scheme can quickly and conveniently generate form pages through the form configuration page, thereby improving the efficiency and convenience of generating form pages. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0067] Figure 1 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;

[0068] Figure 2 It is a flow chart of a method for generating a form page provided in an embodiment of the present application;

[0069] Figure 3 is a flowchart of another method for generating a form page provided in an embodiment of the present application;

[0070] Figure 4 is a schematic diagram of a form configuration page provided in an embodiment of the present application;

[0071] Figure 5 is a schematic diagram of another form configuration page provided in an embodiment of the present application;

[0072] Figure 6 is a schematic diagram of a form page provided in an embodiment of the present application;

[0073] Figure 7 It is a flow chart of a method for using a form page provided in an embodiment of the present application;

[0074] Figure 8 is a flowchart of another method for using a form page provided in an embodiment of the present application;

[0075] Fig. 9 is a schematic diagram of the structure of a rendered form page provided in an embodiment of the present application;

[0076] Fig.10 It is a device relationship diagram provided in an embodiment of the present application;

[0077] Fig.11 It is a functional architecture diagram provided by an embodiment of the present application;

[0078] Fig.12 It is a block diagram of a form page generation device provided in an embodiment of the present application;

[0079] Fig.13 It is a block diagram of a device for using a form page provided in an embodiment of the present application;

[0080] Fig.14 is a block diagram of a terminal provided in an embodiment of the present application;

[0081] Fig.15 This is a block diagram of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0083] In this application, the terms "first", "second", etc. are used to distinguish identical or similar items with basically the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor is there any limitation on quantity and execution order.

[0084] In the present application, the term "at least one" means one or more, and the term "plurality" means two or more.

[0085] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the business data involved in this application are all obtained with full authorization.

[0086] The following is an introduction to the implementation environment involved in this application:

[0087] See also Figure 1 , Figure 1A schematic diagram of an implementation environment of a method for generating a form page provided in an embodiment of the present application, the implementation environment includes a first terminal 101, a server 102, and a second terminal 103. The first terminal 101, the server 102, and the second terminal 103 can be directly or indirectly connected via wired or wireless communication, and the present application does not limit this.

[0088] In some embodiments, a first application is installed on the first terminal 101, and the first application is used to generate a form page. A second application is installed on the second terminal 103, and the second application is used to configure data on the form page. The server 103 is a background server for the first application and the second application, and is used to provide a storage service for the form page for the first application, and is used to provide a form page for the second application, and can also provide a storage service for the form page configured with data for the second application, which is not specifically limited here.

[0089] In some embodiments, the terminal 101 can be a smart phone, a tablet computer, a laptop computer, a desktop computer, an intelligent voice interaction device, a smart home appliance, a vehicle terminal, an aircraft, a VR (Virtual Reality) device, an AR (Augmented Reality) device, etc., but is not limited thereto. In some embodiments, the server 102 is an independent server or a server cluster or a distributed system composed of multiple servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. In some embodiments, the server 102 mainly undertakes computing work, and the terminal 101 undertakes secondary computing work; or, the server 102 undertakes secondary computing services, and the terminal 101 undertakes the main computing work; or, the server 102 and the terminal 101 use a distributed computing architecture for collaborative computing.

[0090] See also Figure 2 , Figure 2 A flowchart of a method for generating a form page provided in an embodiment of the present application. The execution subject of the method is a first terminal, and the first terminal is used to generate a form page. The method includes the following steps.

[0091] 201. The first terminal displays a form configuration page of the target activity model, the form configuration page includes a meta-component area and a form layout area, the meta-component area includes multiple meta-components, the multiple meta-components are generated based on business data of multiple activity models, one meta-component is used to implement a business sub-logic in the activity model, and the target activity model is an activity model among the multiple activity models.

[0092] In the embodiments of the present application, business refers to the service provided by one entity unit to another entity unit. Logic refers to the law of drawing reasonable conclusions based on existing information. Correspondingly, business logic refers to the rules and processes that an entity unit should have in order to provide services to another entity unit. That is, business logic defines the entities in the business and the conditions that must be met to complete an action.

[0093] In an embodiment of the present application, multiple activity models may correspond to multiple businesses. The business logic of any business includes at least one business sub-logic. Accordingly, the activity model of any business includes at least one business sub-logic of the business, and then implements the service corresponding to the business based on the activity model. The business sub-logic included in the activity model is implemented based on the meta-component configured on the form configuration page.

[0094] In the embodiment of the present application, the activity model of any business is an activity form used to implement preset business logic, such as the activity model of the lottery business is used to implement the business logic in the lottery business.

[0095] In the embodiment of the present application, the form layout area is used to design the form page. Further, the form layout area is also used to preview the form page. The display position and size of the component area and the form layout area can be set and changed as needed. For example, the component area is displayed in the left area of ​​the form configuration page, and the form layout area is displayed in the middle area of ​​the form configuration page.

[0096] 202. In response to a selection operation on any one of the multiple component elements, the first terminal adds the component element to a form layout area.

[0097] In an embodiment of the present application, the selection operation may be a touch operation or a drag operation, etc. The first terminal adds the element component to the form layout area, that is, displays the element component in the form layout area. Optionally, the element component is displayed in the form layout area with a preset size, and the preset size can be set and changed as needed.

[0098] 203. The first terminal configures attributes of the meta-components in the form layout area based on the business data of the target activity model to obtain the meta-components after the attributes are configured.

[0099] In the embodiment of the present application, the attributes of the meta-component include field names, sizes, prompts, values ​​required for the operation of the meta-component, etc. Among them, the values ​​required for the operation of the meta-component are provided by business data. For example, for a drop-down selection box in a meta-component, multiple options in the drop-down selection box are configured based on business data; based on business data, the option content of multiple options can be male and female, or multiple different value ranges. Accordingly, the same meta-component may have different appearances and functions depending on the different attributes.

[0100] 204. In response to a confirmation operation on the content displayed in the form layout area, the first terminal obtains a form page corresponding to the target activity model, and the content displayed in the form layout area includes the meta-component after the attributes are configured.

[0101] In the embodiment of the present application, a confirmation control is displayed in the form configuration page, which is used to confirm the content displayed in the form layout area. Optionally, after the first terminal obtains the form page, the form page is stored.

[0102] The embodiment of the present application provides a method for generating a form page, which displays multiple meta-components on a form configuration page, and these meta-components are generated based on the business data of multiple active models, and are respectively used to implement a business sub-logic in the active model. In this way, when the scheme configures the form page of any active model, the business logic of the active model can be implemented by directly configuring the meta-components required in these meta-components to the form page without the participation of backend developers. And on the form configuration page, the properties of the meta-components can also be configured based on the business data, so that ordinary personnel can also configure the business data to the form page without the need for backend personnel development. The scheme can quickly and conveniently generate form pages through the form configuration page, thereby improving the efficiency and convenience of generating form pages.

[0103] Based on the above Figure 2 The embodiment of the present invention introduces the basic process of generating a form page. Figure 3 The process of generating a form page is further described in the embodiment of FIG. Figure 3 , Figure 3 This is a flow chart of a method for generating a form page provided in an embodiment of the present application. The execution subject of the method is a first terminal. The method includes the following steps.

[0104] 301. The first terminal displays a form configuration page of the target activity model. The form configuration page includes a meta-component area and a form layout area. The meta-component area includes multiple meta-components. The multiple meta-components are generated based on business data of multiple activity models. One meta-component is used to implement a business sub-logic in the activity model. The target activity model is an activity model among the multiple activity models.

[0105] In some embodiments, an application for configuring a form page is installed on the first terminal, and the form configuration page is a page in the application. Multiple meta-components are used to implement business logic in multiple activity models. One meta-component is used to implement a business sub-logic in at least one activity model, that is, one meta-component can be reused by multiple activity models.

[0106] In an embodiment of the present application, the form configuration page also includes a form basic information area and a button operation area. The form basic information area is used to display the name and description information of the form on the form page. The button operation area includes multiple function buttons for implementing different functions. For example, the button operation area includes a protocol button, an edit button, a save draft button, a preview button, a submit button, etc. Among them, the protocol button is used to view the form data protocol corresponding to the currently designed form, which is used to store form description data (json schema). The edit button is used to view the form description data corresponding to the currently designed form, and the current schema can be edited, and the editing results are also fed back to the form layout area. The save draft button is used to temporarily store the currently designed form to avoid data loss. The preview button is used to preview the currently designed form. The submit button is used to submit the form description data corresponding to the designed form page to the form server (Form Server) for storage, and obtain a unique form identifier (Form Id).

[0107] In an embodiment of the present application, the meta component area includes a plurality of meta components that can be used to configure a form page. Further, the meta components in the meta component area are displayed in groups according to different types. For example, the meta components in different groups have different functions or sizes, which are not specifically limited here. Optionally, the meta component area also displays a plurality of general components, which are not generated based on business data and can be used in common during the configuration process of any form page, such as a simple input box component.

[0108] In some embodiments, the form configuration page also includes a property configuration area, which is used to configure the properties of the element component. Figure 4 , Figure 4 4 is a schematic diagram of a form configuration page provided in an embodiment of the present application, wherein the form configuration page includes a component area 401 , a form layout area 402 , a form basic information area 403 , a button operation area 404 and an attribute configuration area 405 .

[0109] In some embodiments, the meta-component is generated by background code technology. For any meta-component, the business sub-data corresponding to the meta-component is added to the logic code of the meta-component, and then after running the logic code, the business sub-logic corresponding to the business sub-data can be implemented based on the meta-component. In other embodiments, the meta-component can also be generated by other implementation methods, which are not specifically limited here.

[0110] 302. In response to a touch operation on any component among the multiple components, the first terminal adds the component to a reference sub-area in the form layout area.

[0111] In the embodiment of the present application, the reference sub-region can be set and changed as needed. Accordingly, in response to the touch operation on any of the multiple components, the first terminal adds the component to the reference sub-region in the form layout area, including but not limited to the following three implementations.

[0112] In a first implementation, in response to a touch operation on any one of a plurality of components, the first terminal determines a reference sub-area corresponding to the component from a first form template, and adds the component to the reference sub-area. The first form template is used to indicate sub-areas in a form layout area to which the plurality of components respectively correspond.

[0113] The sub-area corresponding to each element component can be set and changed as needed, which is not specifically limited here. In this implementation, since the first form template is established in advance, the touch element component can be directly added to the corresponding position of the form layout area without manually determining the position, which improves the interaction efficiency and further improves the efficiency of generating the form page.

[0114] In a second implementation manner, in response to a touch operation on any component among the multiple components, the first terminal uses an area after the display sub-area of ​​the last added component as a reference sub-area and adds the component to the reference sub-area.

[0115] In this implementation, the touched meta-component is automatically added to the back of the last added meta-component, that is, the meta-component is actively added to the last item of the form, and so on, multiple meta-components can be arranged in sequence in the form layout area according to the order in which the meta-components are touched; this implementation can independently control the arrangement order of the meta-components on the basis of improving the interaction efficiency, thereby improving the flexibility of generating form pages.

[0116] In a third implementation, the component area includes multiple sub-areas, and the multiple sub-areas respectively display different types of component. Accordingly, in response to a touch operation on a component in any of the multiple sub-areas, the first terminal determines a reference sub-area corresponding to the type of component from the second form template based on the type of the component corresponding to the sub-area, and adds the component to the reference sub-area, and the second form template is used to indicate the sub-areas in the form layout area corresponding to the multiple types of component.

[0117] In the embodiments of the present application, different types of meta-components can be divided into general components and exclusive components. General components are components common to multiple businesses, and exclusive components are components that are exclusive to a certain business. Alternatively, different types of meta-components can be meta-components of different shapes. Alternatively, different types of meta-components can be meta-components with different functions; for example, different types of meta-components can be navigation meta-components, input meta-components, and information meta-components. For example, see Figure 5 , Figure 5 Schematic diagram of another form configuration page provided by an embodiment of the present application. The form configuration page includes several types of meta-components, namely, UI (User Interface) components, basic form components, advanced interaction components, and container components.

[0118] In this implementation, since the second form template is established in advance, the component can be directly added to the corresponding position of the form layout area based on the type of the touch component, without the need to manually determine the position, thereby improving the interaction efficiency and further improving the efficiency of generating form pages.

[0119] 303. In response to a drag operation on any one of the multiple component elements, the first terminal adds the component to a sub-region corresponding to the drag operation in the form layout region.

[0120] In the embodiment of the present application, the sub-region corresponding to the drag operation is the region corresponding to the end point of the drag track. The region can be the region where the end point of the drag track is located, or can be a region at a reference distance from the end point, which is not specifically limited here.

[0121] In some embodiments, the components in the form layout area can be adjusted based on the drag operation. Accordingly, in response to the drag operation of any component in the form layout area, the first terminal adjusts the display area of ​​the component so that the adjusted component is displayed in the sub-area corresponding to the drag operation in the form layout area. In this embodiment, the components in the form layout area can be freely dragged, and the layout of the form page can be changed, which improves the flexibility of adding components in the form page.

[0122] In the embodiment of the present application, the process of adding a component to the form layout area in response to the selection operation of any component among the multiple components can be implemented through any of the above steps 302 or 303, thereby improving the flexibility and convenience of adding components to the form layout area. The serial numbers of step 302 and step 303 are only for the convenience of explanation and are not used to limit the execution order of the two steps. In other embodiments, the process can also be implemented by any of the following three implementation methods.

[0123] In a first implementation, in response to a drag operation on any one of a plurality of components, the first terminal adds the component to a sub-area corresponding to the drag operation in a form layout area, and highlights a plurality of components associated with the component in the plurality of components; in response to a selection operation on any one of the plurality of associated components, the first terminal adds the selected component to the form layout area.

[0124] In this implementation, the mutually associated meta-components may be meta-components used in the same activity model. Optionally, the first terminal stores each meta-component and the activity model corresponding to each meta-component in advance. Accordingly, in response to a drag operation on any meta-component among the multiple meta-components, the first terminal determines the meta-component corresponding to the activity model based on the activity model corresponding to the meta-component and the corresponding relationship as the meta-component associated with the dragged meta-component.

[0125] Alternatively, the multiple mutually associated meta-components may be meta-components used in the same type of active model. Optionally, the first terminal stores each meta-component and the type of active model corresponding to each meta-component in advance. Accordingly, in response to a drag operation on any of the multiple meta-components, the first terminal determines the meta-component corresponding to the type of active model corresponding to the meta-component and the corresponding relationship as the meta-component associated with the dragged meta-component.

[0126] Alternatively, the mutually related meta-components may be meta-components associated with business sub-logics. For example, of the two mutually related meta-components, the first meta-component is used to implement the first business sub-logic, and the second meta-component is used to implement the second business sub-logic. The implementation of the first business sub-logic needs to rely on the implementation of the second business sub-logic, that is, the first business sub-logic can only be implemented based on the first meta-component after the second business sub-logic is implemented based on the second meta-component. Optionally, the first terminal stores each meta-component and the meta-components associated with each meta-component in advance. Accordingly, in response to a drag operation on any meta-component among the multiple meta-components, the first terminal determines the meta-component associated with the meta-component based on the corresponding relationship.

[0127] In the embodiment of the present application, the highlighting may be magnified display, special effect display, color change display, etc., which are not specifically limited here. In this implementation, by highlighting the associated components, the efficiency of selecting the sub-components can be improved, thereby improving the efficiency of generating the form page.

[0128] In a second implementation, in response to a touch operation on any one of the multiple components, multiple components associated with the component are highlighted; in response to a selection operation on the component and any one of the multiple associated components, the selected component is added to the form layout area.

[0129] In this implementation, the mutually related components are components of the same type. Optionally, they have the same functions. In response to a touch operation on any component, this implementation recommends components of the same type, so that the most appropriate component of this type can be selected and added to the form layout area, thereby improving the interactive experience.

[0130] In a third implementation, in response to a selection operation on any one of the plurality of component elements, the component element and component elements associated with the component element among the plurality of component elements are added to the form layout area respectively.

[0131] Optionally, the mutually associated meta-components may be meta-components used in the same activity model, or meta-components associated with business sub-logics. Optionally, the selected meta-components and the associated meta-components may be arranged in the form layout area based on a third form template. The third form template is used to indicate the sub-areas of the meta-components and the meta-components associated with the meta-components in the form layout area, respectively.

[0132] In this implementation, in response to a selection operation on any meta-component, not only the meta-component is added to the form layout area, but also the associated meta-components are added to the form layout area, so that multiple meta-components can be added to the form layout area with one click, thereby improving interaction efficiency.

[0133] 304. The first terminal configures attributes of the meta-components in the form layout area based on the business data of the target activity model to obtain the meta-components after the attributes are configured.

[0134] In an embodiment of the present application, the first terminal configures the attributes of the meta-components in the form layout area based on the business data of the target activity model to obtain the meta-components after the attributes are configured, including but not limited to the following two implementation methods.

[0135] In the first implementation, in response to an attribute configuration operation on any meta-component in the form layout area, the first terminal obtains the target sub-data corresponding to the meta-component from the business data, configures the attribute data of the meta-component based on the target sub-data, and obtains the meta-component after the attribute configuration. In this implementation, in response to the attribute configuration operation on the meta-component, the first terminal can automatically configure data for the meta-component, which improves the convenience of attribute configuration and thus improves the interaction efficiency.

[0136] Among them, the attribute configuration operation can be a single-click operation, a double-click operation, a long-press operation, etc. on the meta-component, which will not be repeated here. Optionally, each meta-component and the target sub-data corresponding to each meta-component are stored in the business data. The first terminal obtains the target sub-data corresponding to the meta-component from the business data based on the corresponding relationship.

[0137] In the second implementation, in response to a touch operation on any element in the form layout area, the first terminal displays the element's attribute configuration area on the form configuration page, the attribute configuration area is used to configure the element's attributes, and the attribute configuration area includes at least one attribute configuration box; in response to an input operation on the attribute configuration box, the first terminal configures the input data as the attribute data of the element, and obtains the element after the attribute is configured, and the input data includes the business data of the target activity model. In this implementation, the attributes are configured through the attribute configuration box, which improves the flexibility of the attribute configuration, thereby making the configured attributes more accurate.

[0138] In some embodiments, a property configuration area is always displayed in the form configuration page. Optionally, when any component is not touched, the property configuration area of ​​the form configuration page is a blank area. In response to a touch operation on any component, the property configuration area is transformed into the property configuration area of ​​the component, which is used to configure the properties of the component. In other embodiments, the form configuration page displays the property configuration area only after the component is touched, that is, in response to a touch operation on any component, the property configuration area of ​​the component is displayed in the form configuration page. The display position of the property configuration area in the form configuration page can be set and changed as needed; for example, the property configuration area is displayed in the right area of ​​the form configuration page.

[0139] Optionally, the attribute configuration area includes a first sub-area and a second sub-area, the first sub-area is used to configure the general attributes of the element component, and the second sub-area is used to configure the business attributes of the element component based on the business data of the target activity model. Figure 4 , the attribute configuration area displays a first sub-area 4051 and a second sub-area 4052. For example, continue to refer to Figure 5 , the right side of the form configuration page displays the attribute configuration area 502 of the element component 501. The attribute configuration area 502 includes a first sub-area 5021 and a second sub-area 5022.

[0140] Among them, general attribute configuration refers to the attributes that need to be configured for multiple components, such as the general attribute configuration can be used to configure the size, color, prompt, etc. of the component. Business attribute configuration refers to the numerical configuration of the component based on business data. For example, business attribute configuration can be used to configure the data range, time range, etc. corresponding to the component.

[0141] In this embodiment, the configuration of common attributes and the configuration of business attributes are distributed in different areas, thereby facilitating the configuration of different attributes based on different areas. In this way, the convenience of attribute configuration can be improved through obvious partitioning.

[0142] 305. In response to a confirmation operation on the content displayed in the form layout area, the first terminal obtains a form page corresponding to the target activity model, and the content displayed in the form layout area includes the meta-component after the attributes are configured.

[0143] In some embodiments, the form layout area displays a confirmation control for confirming the content displayed in the form layout area.

[0144] For example, see Figure 6 , Figure 6 is a schematic diagram of a form page provided in an embodiment of the present application. The form page is generated based on the method provided in an embodiment of the present application, includes multiple meta-components, and the multiple meta-components match the business data.

[0145] In an embodiment of the present application, the generation of the form page is completed through the above steps 301-305. In some embodiments, in response to the confirmation operation of the content displayed in the form layout area, the first terminal obtains the form page and stores the form page locally. In other embodiments, in response to the confirmation operation of the content displayed in the form layout area, the first terminal obtains the form page and stores the form page to the form server. Accordingly, in response to the confirmation operation of the content displayed in the form layout area, the first terminal obtains the form description data (json schema) and form identification (Form Id) corresponding to the form page, and the form description data is used to render the form page. The form description data and form identification corresponding to the form page are stored in the form server accordingly.

[0146] In an embodiment of the present application, the form description data is a set of data that describes the form page through json (JavaScript Object Notation, JS object notation) data. Among them, the form description data indicates the conditions that the json data needs to meet, and the conditions include members, structures, types and constraints in the form page. Members refer to the number of elements included in the form page. Structure refers to the distribution structure of meta-components in the form page, such as nested structures. Type refers to the meta-component type of the elements included in the form page, such as input box type and selection box type. Constraints refer to the formats that the data configured in the form page needs to meet, such as numbers, text and other formats. The form description data includes various information such as elements and element layouts in the form page. The form description data is a data storage format for the form page, and the form page can be restored based on the form description data.

[0147] In some embodiments, the form identifier is generated by a form server. Accordingly, the process in which the first terminal obtains the form description data and form identifier corresponding to the form page in response to the confirmation operation on the content displayed in the form layout area includes the following steps: in response to the confirmation operation on the content displayed in the form layout area, the first terminal obtains the form description data corresponding to the form page; the form description data of the form page is sent to the form server, the form server is used to generate the form identifier of the form page, and the form description data and form identifier of the form page are stored in correspondence; the first terminal receives the form identifier of the form page returned by the form server. For example, continue to refer to Figure 4 A submit control is displayed in the form configuration page. The submit control is used to confirm the content displayed in the form layout area, and obtain the form description data corresponding to the form page and send it to the form server.

[0148] Optionally, when sending the form description data, the first terminal also sends the model identifier of the target activity model, thereby facilitating the distinction between the form description data of the form pages of multiple activity models, and facilitating the form server to return the form identifier to the first terminal based on the model identifier of the target activity model, thereby enabling the first terminal to store each activity model and the form identifier corresponding to each activity model in correspondence with each other, for subsequent use.

[0149] In the embodiment of the present application, since the form description data is stored on the form server side, and then the form identifier is generated by the form server, the form identifier is more matched with the form server, which is convenient for the form server to store the form identifier and search for the form description data based on the form identifier. And the form identifier is generated based on the form server, which is convenient for the form server to provide storage services for multiple first terminals, and to coordinate the generation of form identifiers, so as to avoid confusion between the form identifiers provided by multiple first terminals. And it can also reduce the computing pressure of the first terminal.

[0150] The form identifier is used to obtain the form description data. Accordingly, in response to receiving the form acquisition request of the target activity model from the second terminal, the first terminal returns the form identifier of the form page to the second terminal, and the second terminal is used to obtain the form description data corresponding to the form identifier from the form server based on the form identifier, so as to render the form page based on the form description data. The second terminal is a terminal for configuring data on the form page.

[0151] In this embodiment, the form description data is stored in the form server, so that the first terminal only needs to inform the second terminal of the form identifier, so that the second terminal can obtain the form description data based on the form identifier and then render the form page. This avoids data confusion and loss caused by the transmission of form description data imported and exported between terminals.

[0152] In the embodiment of the present application, the form description data may be stored not only in the form server but also in the first terminal, or may be stored in the first terminal and the form server separately, which is not specifically limited here.

[0153] Through the method provided in the embodiment of the present application, any form page containing complex business logic can be created quickly, efficiently and conveniently, greatly reducing the cost of creating form pages, and does not need to rely on developers with specific skills, thus lowering the threshold for creating form pages.

[0154] The embodiment of the present application provides a method for generating a form page, which displays multiple meta-components on a form configuration page, and these meta-components are generated based on the business data of multiple active models, and are respectively used to implement a business sub-logic in the active model. In this way, when the scheme configures the form page of any active model, the business logic of the active model can be implemented by directly configuring the meta-components required in these meta-components to the form page without the participation of backend developers. And on the form configuration page, the properties of the meta-components can also be configured based on the business data, so that ordinary personnel can also configure the business data to the form page without the need for backend personnel development. The scheme can quickly and conveniently generate form pages through the form configuration page, thereby improving the efficiency and convenience of generating form pages.

[0155] Above Figure 2-3 The embodiment of the invention introduces the process of generating a form page. Figure 7 The embodiment of the invention introduces a method for using the generated form page. Figure 7 , Figure 7 This is a flow chart of a method for using a form page provided by an embodiment of the present application. The execution subject of the method is a second terminal, which is a terminal using the form page and is used to configure data on the form page. The method includes the following steps.

[0156] 701. The second terminal sends a form acquisition request of the target activity model to the first terminal. The form acquisition request is used to request to obtain a form page of the target activity model. The form page is generated based on a meta-component and business data of the target activity model. The meta-component is generated based on business data of multiple activity models. One meta-component is used to implement a business sub-logic in the activity model. The target activity model is an activity model among multiple activity models.

[0157] In an embodiment of the present application, the first terminal is used to generate a form page, and the second terminal is used to configure data on the form page. The form acquisition request carries the model identifier of the target activity model. The form acquisition request also carries the terminal identifier of the second terminal, thereby facilitating the first terminal to return the form identifier to the second terminal.

[0158] 702. The second terminal receives a form identifier of a form page of a target activity model returned by the first terminal.

[0159] In an embodiment of the present application, the first terminal stores model identifiers of multiple active models and form identifiers of form pages of multiple active models. The first terminal obtains the model identifier carried in the form request based on the corresponding relationship, determines the form identifier corresponding to the carried model identifier, and returns the form identifier to the second terminal.

[0160] 703. The second terminal obtains form description data corresponding to the form identifier from the form server based on the form identifier. The form server is used to store form description data and form identifiers of multiple form pages correspondingly. The form description data is used to render the form page.

[0161] In the embodiment of the present application, the form server is used to obtain the form description data corresponding to the form identifier, and send the form description data to the second terminal.

[0162] 704. The second terminal performs page rendering based on the form description data to display the form page of the target activity model and configures data on the form page.

[0163] In the embodiment of the present application, after the form page is configured with data, it can be used to implement the business logic in the activity model.

[0164] In the embodiment of the present application, the form description data is stored in the form server, so that the first terminal only needs to provide the form identifier to the second terminal, so that the second terminal obtains the form description data from the form server based on the form identifier. This method avoids data confusion and loss caused by the transmission of the form description data imported and exported between terminals, thereby improving the accuracy of obtaining the form description data, thereby improving the accuracy of the form page restored based on the form description data.

[0165] Above Figure 7 The embodiment of the present invention introduces the basic process of using the form page. Figure 8 The use of the form page is further described in the following examples. Figure 8 , Figure 8 This is a flow chart of a method for using a form page provided in an embodiment of the present application, and the method is described by taking the interaction process between the first terminal, the second terminal and the form server as an example. The method includes the following steps.

[0166] 801. The second terminal sends a form acquisition request of the target activity model to the first terminal. The form acquisition request is used to request to obtain a form page of the target activity model. The form page is generated based on a meta-component and business data of the target activity model. The meta-component is generated based on business data of multiple activity models. One meta-component is used to implement a business sub-logic in the activity model. The target activity model is an activity model among multiple activity models.

[0167] In the embodiment of the present application, step 801 is the same as step 701 and will not be described again here.

[0168] 802. The first terminal returns a form identifier of a form page of a target activity model to the second terminal based on the form acquisition request.

[0169] In an embodiment of the present application, the first terminal stores model identifiers of multiple activity models and form identifiers of form pages of multiple activity models. The form acquisition request carries the model identifier of the target activity model. Accordingly, the first terminal determines the form identifier corresponding to the model identifier carried based on the model identifier carried by the form acquisition request and the correspondence between the model identifier and the form identifier, and returns the form identifier to the second terminal.

[0170] Optionally, the first terminal also returns the server identifier of the form server to the second terminal, thereby facilitating the second terminal to send a form data acquisition request to the form server storing the form description data. Alternatively, the second terminal stores the server identifier of the form server in advance, so that the first terminal does not need to return the server identifier to the second terminal.

[0171] 803. The second terminal receives the form identifier of the form page of the target activity model, and based on the form identifier, sends a form data acquisition request to the form server, where the form data acquisition request is used to request to acquire form description data corresponding to the form identifier.

[0172] In the embodiment of the present application, the form data acquisition request carries the form identifier. Further, the form data acquisition request also carries the terminal identifier of the second terminal, thereby facilitating the form server to return the form description data to the second terminal.

[0173] 804. The form server determines form description data corresponding to the form identifier from the plurality of form description data based on the form data acquisition request, and sends the form description data corresponding to the form identifier to the second terminal.

[0174] In the embodiment of the present application, the form server stores form description data and form identifiers of multiple form pages accordingly. Accordingly, the form server determines the form description data corresponding to the carried form identifier based on the form identifier carried by the form data acquisition request and the correspondence between the form description data and the form identifier, and sends the form description data to the second terminal.

[0175] In the embodiment of the present application, the process of obtaining form description data corresponding to the form identifier from the server based on the form identifier is implemented through the above steps 801-804. The process can also be implemented in other ways, which will not be repeated here. For example, the first terminal or the form server sends the form identifiers of the form pages of multiple activity models to the second terminal in advance. When the second terminal obtains the form description data, it can directly send a form description acquisition request to the server based on the locally stored form identifier, without having to obtain the form identifier from the first terminal, thereby improving the efficiency of obtaining the form description data.

[0176] In some embodiments, the first terminal and the second terminal are the same terminal, that is, the generation of the form page and the data configuration of the form page are completed by the same terminal. Accordingly, there is no need to perform the above steps 801-802, and the second terminal can obtain the form description data from the form server based on the form identifier stored in itself.

[0177] 805. The second terminal performs page rendering based on the form description data to display a form page of the target activity model.

[0178] In some embodiments, the process of the second terminal performing page rendering based on the form description data includes the following steps: the second terminal parses the form description data based on the generation method of the form description data to obtain form structure information of the form page, the form structure information including layout information of multiple areas in the form page and information of meta-components included in the multiple areas; the second terminal performs page rendering based on the form structure information to display the form page of the target activity model.

[0179] In an embodiment of the present application, the method for generating form description data refers to a method for generating form description data based on a form page, and the generating method can be set and changed as needed. In an embodiment of the present application, based on the generating method of the form description data, it is parsed, and the form structure information of the form page can be restored. For example, based on the encoding method of the data, the data is decoded, and the data can be restored to the data before encoding. The page rendering method can be set and changed as needed. If it is rendered by a renderer, the form structure information is used as the input data of the renderer, and after rendering by the renderer, the form page corresponding to the form structure information is displayed.

[0180] For example, see Fig. 9 9 is a schematic diagram of the structure of a rendered form page provided by an embodiment of the present application. There are multiple types of form items in the form page, including single form items 901, nested form items, etc. Nested form items further include parent-child nested form items 902 and multi-level nested form items 903. Each form item is composed of at least one meta-component, and the layout of multiple form items in the form page constitutes the structure of the form page.

[0181] In some embodiments, the second terminal displays the form page through a form renderer, wherein the form identifier is used as input data of the form renderer, the form renderer obtains form description data from the form server based on the form identifier, parses the form description data and renders the form page.

[0182] 806. The second terminal performs data configuration on the form page.

[0183] In the embodiment of the present application, the form page displays multiple data configuration boxes for configuring data for the element components. Figure 6 , a plurality of data configuration boxes 601 are displayed in the form page, which are used to perform data configuration based on business data.

[0184] In some embodiments, the form description data further includes format information of multiple components in the form page, and the format information is used to indicate the input format of the data corresponding to the multiple components. Accordingly, the second terminal verifies the data input in the form page based on the format information.

[0185] In some embodiments, after any form page is updated, it can also be synchronized to the second terminal. Accordingly, the following two implementation methods are included. In response to an update operation on any form description data in the form server, the first terminal sends an update indication message to the second terminal, and the update indication message carries a form identifier corresponding to the updated form description data, which is used to indicate that the form description data corresponding to the carried form identifier has been updated; or, in response to an update operation on any form description data in the form server, the first terminal instructs the form server to send the updated form description data to the second terminal. This embodiment can synchronize the updated form description data to the second terminal in a timely manner, thereby improving the comprehensiveness of the update.

[0186] See also Fig.10 , Fig.10It is a device relationship diagram provided by an embodiment of the present application. Among them, the method provided by the implementation of the present application is executed by a first terminal, a form server and a second terminal. The first terminal, the form server and the second terminal are respectively configured as a form designer (Form Creator), a form server (Form Server) and a form renderer (Form Render). Among them, the form designer is used to visually design a form page, and the meta components are arranged and combined by touch or drag to design a form page of any structure. The form server is a bridge for docking the form designer and the form renderer. On the one hand, the form description data of the form page generated by the form designer is stored and the form identifier is returned; on the other hand, the corresponding form description data is queried according to the form identifier. The form renderer is used to restore the form description data to the form structure based on the same rules as the form designer, that is, according to the way the form designer generates the form description data, and render it to obtain a form page.

[0187] See also Fig.11 , Fig.11 It is a functional architecture diagram provided by an embodiment of the present application. Among them, the method provided by an embodiment of the present application is completed by a system including a form designer, a form server and a form renderer. Among them, the form designer generates a form page through a widget module (Widgets), a form layout module (Designer), and a property configuration module (Props Config), and generates form description data (json schema). These modules correspond to the widget area, form layout area and property configuration area of ​​the form configuration page respectively. The form server, as an intermediate layer, connects the upper and lower layers and provides storage services to the form designer. The form description data is stored and a unique form identifier is returned. And the form server provides a query service to the form renderer, and the form renderer obtains the corresponding form description data according to the form identifier query. The form renderer mainly includes a rendering module, a verification module and a storage module. The rendering module is used to parse the form description data and render the form page. The verification module is used to verify the data entered in the form page. The storage module is used as a memory to store the data entered in the form page, and when the entire form page is filled in, the data (Data) of the entire form page is output.

[0188] It should be noted that the form configuration page provided in the embodiment of the present application provides a method for registering custom meta-components, allowing users to develop meta-components containing specific complex business logic and add them to the form configuration page for use, thereby solving the problem of configuring form pages containing complex business logic. In this way, the corresponding form page needs to implement complex business logic based on components. Since components that can complete these complex business logics have been generated based on business data in advance, there is no need for backend developers to participate in the form page development process, thereby improving the development efficiency of the form page.

[0189] In the related art, the form page of the activity model is generally customized, so that the components generated for each activity model can only be applied in this activity model. The meta-components between activity models are generally universal, that is, the same meta-component may appear in multiple activity models. In this way, if multiple activity models use the same meta-component respectively, the meta-component needs to be generated multiple times. In the embodiment of the present application, multiple meta-components are generated in advance and displayed in the form configuration page, so that the same meta-component can be reused in multiple activity models, that is, the reusability of the meta-component is achieved, and multiple generation of the same meta-component is avoided, which saves resources and reduces time consumption.

[0190] The embodiment of the present application provides a specific visual form configuration platform, which analyzes the logical requirements of the activity model and uses basic element components for visual drag and drop free arrangement to combine into a set of data configuration forms that can meet the business logic of the activity. And a set of form structured description data json schema is defined. Through the visualization platform, any complete form can be quickly and flexibly dragged out, and unique form description data can be generated for storage. Other platforms can parse the form description data through the parser of the surface description data provided by the embodiment of the present application, and render the form page for data configuration.

[0191] In the related art, a form page is generally stored at a first terminal. When a second terminal obtains the form page from the first terminal, the second terminal exports the form description data of the form page from the first terminal, and then imports the form description data into the project to be used. In the process of importing and exporting data at the terminal, data confusion and loss may occur, resulting in incorrect or erroneous form pages rendered in the imported project. In the embodiment of the present application, the form description data is stored in a server, which avoids the process of importing and exporting data between terminals. In the project that needs to use the form, only the form identifier needs to be provided to render the form page, which solves the problems caused by importing and exporting form description data.

[0192] Fig.12is a block diagram of a form page generation device provided according to an embodiment of the present application. The device is used to perform the steps of the above-mentioned form page generation method, see Fig.12 , the device comprises:

[0193] Display module 1201, used to display the form configuration page of the target activity model, the form configuration page includes a meta component area and a form layout area, the meta component area includes multiple meta components, the multiple meta components are generated based on the business data of multiple activity models, one meta component is used to implement a business sub-logic in the activity model, and the target activity model is an activity model among the multiple activity models;

[0194] An adding module 1202, configured to add a component to the form layout area in response to a selection operation on any component among the multiple components;

[0195] Configuration module 1203, used for configuring the attributes of the meta-components in the form layout area based on the business data of the target activity model, and obtaining the meta-components after the attributes are configured;

[0196] The confirmation module 1204 is used to obtain a form page corresponding to the target activity model in response to a confirmation operation on the content displayed in the form layout area, where the content displayed in the form layout area includes the meta-component after the attributes are configured.

[0197] In some embodiments, a module 1202 is added to:

[0198] In response to a touch operation on any one of the plurality of component components, adding the component component to a reference sub-region in the form layout region;

[0199] In response to a drag operation on any one of the plurality of component elements, the component element is added to a sub-region corresponding to the drag operation in the form layout region.

[0200] In some embodiments, a module 1202 is added to:

[0201] In response to a touch operation on any one of the plurality of component components, a reference sub-region corresponding to the component component is determined from a first form template, and the component component is added to the reference sub-region, wherein the first form template is used to indicate sub-regions in the form layout region corresponding to the plurality of component components respectively; or

[0202] In response to a touch operation on any one of the multiple components, an area after the display sub-area of ​​the last added component is used as a reference sub-area, and the component is added to the reference sub-area.

[0203] In some embodiments, the component area includes multiple sub-areas, and the multiple sub-areas respectively display different types of components;

[0204] Add module 1202 for:

[0205] In response to a touch operation on a component in any of the multiple sub-areas, based on the type of the component corresponding to the sub-area, a reference sub-area corresponding to the type is determined from a second form template, and the component is added to the reference sub-area. The second form template is used to indicate the sub-areas in the form layout area corresponding to the multiple types of component.

[0206] In some embodiments, the device further comprises an adjustment module for

[0207] In response to a drag operation on any element in the form layout area, the display area of ​​the element is adjusted so that the adjusted element is displayed in a sub-area corresponding to the drag operation in the form layout area.

[0208] In some embodiments, a module 1202 is added to:

[0209] In response to a drag operation on any one of the plurality of component components, the component component is added to a sub-region corresponding to the drag operation in the form layout region, and a plurality of component components associated with the component component are highlighted; in response to a selection operation on any one of the associated plurality of component components, the selected component component is added to the form layout region; or,

[0210] In response to a touch operation on any one of the multiple components, multiple components associated with the component are highlighted; in response to a selection operation on the component and any one of the multiple associated components, the selected component is added to the form layout area.

[0211] In some embodiments, a module 1202 is added to:

[0212] In response to a selection operation on any one of the plurality of component elements, the component element and component elements associated with the component element in the plurality of component elements are added to the form layout area respectively.

[0213] In some embodiments, the business data includes sub-data corresponding to a plurality of meta-components, and the configuration module 1203 is used to:

[0214] In response to an attribute configuration operation on any meta-component in the form layout area, target sub-data corresponding to the meta-component is acquired from the business data, and attribute data of the meta-component is configured based on the target sub-data to obtain the meta-component after the attributes are configured.

[0215] In some embodiments, the configuration module 1203 is used to:

[0216] In response to a touch operation on any element in the form layout area, a property configuration area of ​​the element is displayed on the form configuration page, the property configuration area is used to configure the properties of the element, and the property configuration area includes at least one property configuration box;

[0217] In response to an input operation on the attribute configuration box, the input data is configured as attribute data of the meta-component to obtain the meta-component after the attributes are configured. The input data includes business data of the target activity model.

[0218] In some embodiments, the attribute configuration area includes a first sub-area and a second sub-area, the first sub-area is used to configure general attributes of the meta-component, and the second sub-area is used to configure business attributes of the meta-component based on business data of the target activity model.

[0219] In some embodiments, the apparatus further comprises:

[0220] An acquisition module, used for acquiring form description data and form identifier corresponding to the form page in response to a confirmation operation on the content displayed in the form layout area, wherein the form description data is used for rendering the form page;

[0221] A storage module, used to store the form description data and the form identifier corresponding to the form page in the form server;

[0222] The transceiver module is used to return the form identifier of the form page to the second terminal in response to receiving a form acquisition request for the target activity model from the second terminal. The second terminal is used to obtain the form description data corresponding to the form identifier from the form server based on the form identifier, so as to render the form page based on the form description data.

[0223] In some embodiments, the acquisition module is used to:

[0224] In response to a confirmation operation on the content displayed in the form layout area, obtaining form description data corresponding to the form page;

[0225] Sending the form description data of the form page to the form server, the form server is used to generate a form identifier of the form page, and store the form description data and the form identifier of the form page in correspondence;

[0226] Receive the form ID of the form page returned by the form server.

[0227] In some embodiments, the apparatus further comprises:

[0228] a sending module, configured to send update indication information to the second terminal in response to an update operation on any form description data in the form server, wherein the update indication information carries a form identifier corresponding to the updated form description data and is configured to indicate that the form description data corresponding to the carried form identifier has been updated; or

[0229] The instruction module is used for instructing the form server to send the updated form description data to the second terminal in response to an update operation on any form description data in the form server.

[0230] An embodiment of the present application provides a device for generating a form page, which displays multiple meta-components on a form configuration page, and these meta-components are generated based on the business data of multiple active models, and are respectively used to implement a business sub-logic in the active model. In this way, when the scheme configures the form page of any active model, the business logic of the active model can be implemented by directly configuring the meta-components required from these meta-components into the form page without the participation of backend developers. Moreover, on the form configuration page, the properties of the meta-components can also be configured based on the business data, so that ordinary personnel can also configure the business data into the form page without the need for backend personnel to develop. The scheme can quickly and conveniently generate form pages through the form configuration page, thereby improving the efficiency and convenience of generating form pages.

[0231] Fig.13 is a block diagram of a form page usage device provided according to an embodiment of the present application. The device is used to perform the steps of the above form page usage method, see Fig.13 , the device comprises:

[0232] A sending module 1301 is used to send a form acquisition request of a target activity model to a first terminal, where the form acquisition request is used to request to acquire a form page of the target activity model, where the form page is generated based on a meta-component and business data of the target activity model, where the meta-component is generated based on business data of multiple activity models, where one meta-component is used to implement one business sub-logic in the activity model, and where the target activity model is an activity model among multiple activity models;

[0233] A receiving module 1302 is used to receive a form identifier of a form page of a target activity model returned by the first terminal;

[0234] The acquisition module 1303 is used to acquire form description data corresponding to the form identifier from the form server based on the form identifier. The form server is used to store the form description data and form identifiers of multiple form pages correspondingly. The form description data is used to render the form page.

[0235] The display module 1304 is used to perform page rendering based on the form description data to display the form page of the target activity model and perform data configuration on the form page.

[0236] In some embodiments, the display module 1304 is used to:

[0237] Based on the generation method of the form description data, the form description data is parsed to obtain form structure information of the form page, where the form structure information includes layout information of multiple areas in the form page and information of meta-components included in the multiple areas;

[0238] The page is rendered based on the form structure information to display the form page of the target activity model.

[0239] In some embodiments, the form description data further includes format information of multiple meta-components in the form page, and the format information is used to indicate the input format of data corresponding to the multiple meta-components; the device further includes:

[0240] The validation module is used to validate the data entered in the form page based on the format information.

[0241] In the embodiment of the present application, the form description data is stored in the form server, so that the first terminal only needs to provide the form identifier to the second terminal, so that the second terminal obtains the form description data from the form server based on the form identifier. This method avoids data confusion and loss caused by the transmission of the form description data imported and exported between terminals, thereby improving the accuracy of obtaining the form description data, thereby improving the accuracy of the form page restored based on the form description data.

[0242] Fig.14 The structure block diagram of a terminal 1400 provided by an exemplary embodiment of the present application is shown. 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), an MP4 player (Moving Picture Experts Group Audio Layer IV), a laptop computer or a desktop computer. The terminal 1400 may also be called a user device, a portable terminal, a laptop terminal, a desktop terminal or other names.

[0243] Typically, the terminal 1400 includes a processor 1401 and a memory 1402 .

[0244] The processor 1401 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 1401 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1401 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1401 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1401 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

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

[0246] In some embodiments, the terminal 1400 may further optionally include: a peripheral device interface 1403 and at least one peripheral device. The processor 1401, the memory 1402 and the peripheral device interface 1403 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1403 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1404, a display screen 1405, a camera assembly 1406, an audio circuit 1407 and a power supply 1408.

[0247] The peripheral device interface 1403 may be used to connect at least one peripheral device related to I / O (Input / Output) to the processor 1401 and the memory 1402. In some embodiments, the processor 1401, the memory 1402, and the peripheral device interface 1403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1401, the memory 1402, and the peripheral device interface 1403 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

[0248] The radio frequency circuit 1404 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1404 communicates with the communication network and other communication devices through electromagnetic signals. The radio frequency circuit 1404 converts the electrical signal into an electromagnetic signal for transmission, or converts the received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, and the like. The radio frequency circuit 1404 can communicate with other terminals through at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 1404 may also include circuits related to NFC (Near Field Communication), which is not limited in this application.

[0249] The display screen 1405 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, 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 on the surface or above the surface of the display screen 1405. The touch signal can be input to the processor 1401 as a control signal for processing. At this time, the display screen 1405 can also be used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards. In some embodiments, the display screen 1405 can be one, set on the front panel of the terminal 1400; in other embodiments, the display screen 1405 can be at least two, respectively set on different surfaces of the terminal 1400 or in a folding design; in other embodiments, the display screen 1405 can be a flexible display screen, set on a curved surface or a folding surface of the terminal 1400. Even, the display screen 1405 can also be set to a non-rectangular irregular shape, that is, a special-shaped screen. The display screen 1405 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0250] The camera assembly 1406 is used to capture images or videos. Optionally, the camera assembly 1406 includes a front camera and a rear camera. Typically, the front camera is arranged on the front panel of the terminal, and the rear camera is arranged on the back of the terminal. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, the fusion of the main camera and the wide-angle camera to realize panoramic shooting and VR (Virtual Reality) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 1406 may also include a flash. The flash can be a monochrome temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cold light flash, which can be used for light compensation at different color temperatures.

[0251] The audio circuit 1407 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals and input them into the processor 1401 for processing, or input them into the radio frequency circuit 1404 to achieve voice communication. For the purpose of stereo acquisition or noise reduction, there may be multiple microphones, which are respectively arranged at different parts of the terminal 1400. The microphone may also be an array microphone or an omnidirectional acquisition microphone. The speaker is used to convert the electrical signal from the processor 1401 or the radio frequency circuit 1404 into sound waves. The speaker may be a traditional film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can not only convert the electrical signal into sound waves audible to humans, but also convert the electrical signal into sound waves inaudible to humans for purposes such as ranging. In some embodiments, the audio circuit 1407 may also include a headphone jack.

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

[0253] In some embodiments, the terminal 1400 further includes one or more sensors 1409 . The one or more sensors 1409 include, but are not limited to: an acceleration sensor 1410 , a gyroscope sensor 1411 , a pressure sensor 1412 , an optical sensor 1413 , and a proximity sensor 1414 .

[0254] The acceleration sensor 1410 can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established by the terminal 1400. For example, the acceleration sensor 1410 can be used to detect the components of gravity acceleration on the three coordinate axes. The processor 1401 can control the display screen 1405 to display the user interface in a horizontal view or a vertical view according to the gravity acceleration signal collected by the acceleration sensor 1410. The acceleration sensor 1410 can also be used for collecting game or user motion data.

[0255] The gyro sensor 1411 can detect the body direction and rotation angle of the terminal 1400, and the gyro sensor 1411 can cooperate with the acceleration sensor 1410 to collect the user's 3D actions on the terminal 1400. The processor 1401 can implement the following functions based on the data collected by the gyro sensor 1411: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

[0256] The pressure sensor 1412 may be provided at the side frame of the terminal 1400 and / or the lower layer of the display screen 1405. When the pressure sensor 1412 is provided at the side frame of the terminal 1400, it may detect the user's holding signal of the terminal 1400, and the processor 1401 may perform left and right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 1412. When the pressure sensor 1412 is provided at the lower layer of the display screen 1405, the processor 1401 may control the operability control on the UI interface according to the user's pressure operation on the display screen 1405. The operability control includes at least one of a button control, a scroll bar control, an icon control, and a menu control.

[0257] The optical sensor 1413 is used to collect the ambient light intensity. In one embodiment, the processor 1401 can control the display brightness of the display screen 1405 according to the ambient light intensity collected by the optical sensor 1413. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1405 is increased; when the ambient light intensity is low, the display brightness of the display screen 1405 is reduced. In another embodiment, the processor 1401 can also dynamically adjust the shooting parameters of the camera assembly 1406 according to the ambient light intensity collected by the optical sensor 1413.

[0258] The proximity sensor 1414, also called a distance sensor, is usually arranged on the front panel of the terminal 1400. The proximity sensor 1414 is used to collect the distance between the user and the front of the terminal 1400. In one embodiment, when the proximity sensor 1414 detects that the distance between the user and the front of the terminal 1400 is gradually decreasing, the processor 1401 controls the display screen 1405 to switch from the screen-on state to the screen-off state; when the proximity sensor 1414 detects that the distance between the user and the front of the terminal 1400 is gradually increasing, the processor 1401 controls the display screen 1405 to switch from the screen-off state to the screen-on state.

[0259] Those skilled in the art will understand that Fig.14 The structure shown in the figure does not constitute a limitation on the terminal 1400, and the terminal 1400 may include more or less components than those shown in the figure, or combine some components, or adopt a different component arrangement.

[0260] Fig.15It is a structural diagram of a server provided according to an embodiment of the present application. The server 1500 may have relatively large differences due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 1501 and one or more memories 1502, wherein the memory 1502 is used to store executable program codes, and the processor 1501 is configured to execute the above executable program codes to implement the method for generating a form page or the method for using a form page provided in the above various method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the server may also include other components for implementing device functions, which will not be described in detail here.

[0261] An embodiment of the present application also provides a computer-readable storage medium, in which at least one program is stored. The at least one program is loaded and executed by a processor to implement a method for generating a form page or a method for using a form page of any of the above-mentioned implementation modes.

[0262] An embodiment of the present application also provides a computer program product, which includes a computer program code, and the computer program code is stored in a computer-readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, so that the terminal executes the method for generating a form page or the method for using a form page of any of the above-mentioned implementation methods.

[0263] In some embodiments, the computer program product involved in the embodiments of the present application may be deployed and executed on one terminal, or on multiple terminals located at one location, or on multiple terminals distributed at multiple locations and interconnected by a communication network. Multiple terminals distributed at multiple locations and interconnected by a communication network may constitute a blockchain system.

[0264] The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for generating a form page, characterized in that: Applied to a first terminal, the method includes: Displaying a form configuration page of a target activity model, the form configuration page comprising a meta component area and a form layout area, the meta component area comprising a plurality of meta components, the plurality of meta components being generated based on business data of a plurality of activity models, one meta component being used to implement a business sub-logic in an activity model, the target activity model being an activity model among the plurality of activity models; In response to a selection operation on any one of the plurality of component elements, adding the component element to the form layout area; Based on the business data of the target activity model, attribute configuration is performed on the meta-components in the form layout area to obtain the meta-components after the attribute configuration; In response to a confirmation operation on the content displayed in the form layout area, a form page corresponding to the target activity model is obtained, and the content displayed in the form layout area includes the meta-component after the configuration attributes.

2. The method according to claim 1, characterized in that In response to a selection operation on any one of the plurality of element components, adding the element component to the form layout area comprises: In response to a touch operation on any one of the plurality of component components, adding the component component to a reference sub-region in the form layout region; In response to a drag operation on any one of the plurality of component components, the component is added to a sub-region corresponding to the drag operation in the form layout region.

3. The method according to claim 2, characterized in that In response to a touch operation on any one of the plurality of component components, adding the component component to a reference sub-region in the form layout region comprises: In response to a touch operation on any one of the plurality of component components, determining a reference sub-region corresponding to the component component from a first form template, and adding the component component to the reference sub-region, wherein the first form template is used to indicate sub-regions in a form layout region corresponding to the plurality of component components respectively; or In response to a touch operation on any component among the multiple components, an area after the display sub-area of ​​the last added component is used as the reference sub-area, and the component is added to the reference sub-area.

4. The method according to claim 2, characterized in that: The component area includes a plurality of sub-areas, and the plurality of sub-areas respectively display components of different types; In response to a touch operation on any one of the plurality of component components, adding the component component to a reference sub-region in the form layout region comprises: In response to a touch operation on a component in any of the multiple sub-areas, based on the type of the component corresponding to the sub-area, a reference sub-area corresponding to the type is determined from a second form template, and the component is added to the reference sub-area, wherein the second form template is used to indicate sub-areas in the form layout area corresponding to multiple types of component components.

5. The method according to claim 2, characterized in that: The method further comprises: In response to a drag operation on any element in the form layout area, the display area of ​​the element is adjusted so that the adjusted element is displayed in a sub-area corresponding to the drag operation in the form layout area.

6. The method according to claim 1, characterized in that In response to a selection operation on any one of the plurality of element components, adding the element component to the form layout area comprises: In response to a drag operation on any one of the plurality of component components, the component component is added to a sub-region corresponding to the drag operation in the form layout region, and a plurality of component components associated with the component component in the plurality of component components are highlighted; in response to a selection operation on any one of the associated plurality of component components, the selected component component is added to the form layout region; or, In response to a touch operation on any one of the multiple components, multiple components associated with the component are highlighted; in response to a selection operation on the component and any one of the multiple associated components, the selected component is added to the form layout area.

7. The method according to claim 1, characterized in that In response to a selection operation on any one of the plurality of element components, adding the element component to the form layout area comprises: In response to a selection operation on any one of the plurality of component components, the component component and component components associated with the component in the plurality of component components are added to the form layout area respectively.

8. The method according to claim 1, characterized in that The business data includes sub-data corresponding to a plurality of meta-components, and the business data based on the target activity model configures the meta-components in the form layout area with attributes to obtain the meta-components after the attributes are configured, including: In response to an attribute configuration operation on any meta-component in the form layout area, target sub-data corresponding to the meta-component is acquired from the business data, attribute data of the meta-component is configured based on the target sub-data, and the meta-component after attribute configuration is obtained.

9. The method according to claim 1, characterized in that: The step of configuring the attributes of the meta-components in the form layout area based on the business data of the target activity model to obtain the meta-components after the attributes are configured includes: In response to a touch operation on any element in the form layout area, displaying an attribute configuration area of ​​the element on the form configuration page, the attribute configuration area being used to configure attributes of the element, and the attribute configuration area including at least one attribute configuration box; In response to an input operation on the attribute configuration box, the input data is configured as attribute data of the meta-component to obtain a meta-component after the attributes are configured, and the input data includes the business data of the target activity model.

10. The method according to claim 9, characterized in that The attribute configuration area includes a first sub-area and a second sub-area, the first sub-area is used to perform general attribute configuration on the meta-component, and the second sub-area is used to perform business attribute configuration on the meta-component based on business data of the target activity model.

11. The method according to claim 1, characterized in that: The method further comprises: In response to a confirmation operation on the content displayed in the form layout area, obtaining form description data and a form identifier corresponding to the form page, wherein the form description data is used to render the form page; The form description data and the form identifier corresponding to the form page are stored in the form server in correspondence; In response to receiving a form acquisition request for the target activity model from the second terminal, a form identifier of the form page is returned to the second terminal, and the second terminal is used to obtain form description data corresponding to the form identifier from the form server based on the form identifier, so as to render the form page based on the form description data.

12. The method according to claim 11, characterized in that The method further comprises: In response to an update operation on any form description data in the form server, an update indication message is sent to the second terminal, wherein the update indication message carries a form identifier corresponding to the updated form description data and is used to indicate that the form description data corresponding to the carried form identifier is updated; or In response to an update operation on any form description data in the form server, instruct the form server to send the updated form description data to the second terminal.

13. A method for using a form page, characterized in that: Applied to the second terminal, the method includes: Sending a form acquisition request of a target activity model to a first terminal, wherein the form acquisition request is used to request to acquire a form page of the target activity model, wherein the form page is generated based on a meta-component and business data of the target activity model, wherein the meta-component is generated based on business data of multiple activity models, wherein one meta-component is used to implement one business sub-logic in the activity model, and wherein the target activity model is an activity model among the multiple activity models; receiving a form identifier of a form page of the target activity model returned by the first terminal; Based on the form identifier, obtaining form description data corresponding to the form identifier from a form server, the form server being used to store form description data and form identifiers of a plurality of form pages correspondingly, the form description data being used to render the form page; Page rendering is performed based on the form description data to display the form page of the target activity model, and data configuration is performed on the form page.

14. The method according to claim 13, characterized in that The performing page rendering based on the form description data to display the form page of the target activity model includes: Based on the generation method of the form description data, the form description data is parsed to obtain form structure information of the form page, wherein the form structure information includes layout information of multiple areas in the form page and information of element components included in the multiple areas; Page rendering is performed based on the form structure information to display the form page of the target activity model.

15. The method according to claim 13, characterized in that The form description data also includes format information of multiple element components in the form page, and the format information is used to indicate the input format of data corresponding to the multiple element components; The method further comprises: Based on the format information, the data input in the form page is verified.

16. A device for generating a form page, characterized in that: The device comprises: A display module, configured to display a form configuration page of a target activity model, wherein the form configuration page includes a meta component area and a form layout area, wherein the meta component area includes a plurality of meta components, wherein the plurality of meta components are generated based on business data of a plurality of activity models, and a meta component is used to implement a business sub-logic in an activity model, and the target activity model is an activity model among the plurality of activity models; An adding module, configured to add any one of the plurality of element components to the form layout area in response to a selection operation on the element component; A configuration module, configured to configure the attributes of the meta-components in the form layout area based on the business data of the target activity model, and obtain the meta-components after the attributes are configured; A confirmation module is used to obtain a form page corresponding to the target activity model in response to a confirmation operation on the content displayed in the form layout area, wherein the content displayed in the form layout area includes the meta-component after the configuration attributes.

17. A device for using a form page, characterized in that: The device comprises: a sending module, configured to send a form acquisition request of a target activity model to a first terminal, wherein the form acquisition request is used to request to acquire a form page of the target activity model, wherein the form page is generated based on a meta-component and business data of the target activity model, wherein the meta-component is generated based on business data of multiple activity models, wherein one meta-component is used to implement one business sub-logic in the activity model, and wherein the target activity model is an activity model among multiple activity models; A receiving module, configured to receive a form identifier of a form page of the target activity model returned by the first terminal; An acquisition module, configured to acquire form description data corresponding to the form identifier from a form server based on the form identifier, wherein the form server is configured to store form description data and form identifiers of a plurality of form pages correspondingly, and the form description data is used to render a form page; The display module is used to perform page rendering based on the form description data to display the form page of the target activity model and perform data configuration on the form page.

18. A terminal, characterized in that: The terminal includes a processor and a memory, the memory is used to store at least one program, and the at least one program is loaded by the processor and executes the method for generating a form page described in any one of claims 1 to 12 or the method for using a form page described in any one of claims 13 to 15.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store at least one program, and the at least one program is used to execute the method for generating a form page described in any one of claims 1 to 12 or the method for using a form page described in any one of claims 13 to 15.

20. A computer program product, characterized in that The computer program product includes a computer program code, which is stored in a computer-readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, so that the terminal executes the method for generating a form page as described in any one of claims 1 to 12 or the method for using a form page as described in any one of claims 13 to 15.

Images