Driven form rendering method and device applied to blockchain management platform

Abstract

The present invention belongs to the field of blockchain technology, and provides a driver form rendering method and device applied to a blockchain management platform. By agreeing on a form protocol with a backend and a driver end, the driver end develops form definition data according to the form protocol, configures a request entry address and related parameters, obtains a request trigger instruction from a user end, triggers the request backend to obtain complete form definition data from the driver end, and dynamically fills in blockchain platform information, parses the form definition data to obtain form content for page display, thereby effectively solving the technical problem that the front end alone writes a form that cannot adapt to the technical requirements of the blockchain management platform form, avoids the lengthy front-end logic implementation code, and avoids repetitive labor caused by a large number of similar form pages, so as to achieve a close connection between the driver end and the form, and the driver function can be independently implemented without relying on the front-end project, providing "plug and play" and "pluggable" functions, and a technical effect of flexible driving.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and more specifically, to a method, device, computer equipment, and computer-readable storage medium for driving form rendering applied to a blockchain management platform. Background Art

[0002] The various functions of the blockchain management platform need to be developed based on the driver, and many functions of the driver need to be implemented by the user filling out the form. A form is a common web page control for data collection. A form generally consists of three parts: a form tag, a form field, and a form button. The form tag is used to declare the form; the form field collects the data entered by the user, including multiple input controls such as text boxes and selection boxes; the form button controls the operation logic of the user submitting the form, such as verifying the configuration items of the form field.

[0003] At present, the blockchain management platform form generally involves four major resources and organizational information: credentials, hosts, chains, and nodes. The form content is composed of the information of the four resources, which requires the linkage of the front-end, back-end, and driver to achieve together. The driver provides driver information, and the back-end provides user-end and organizational information related to the blockchain platform. The combination of the two generates the form that is finally displayed to the user end. This also determines that the blockchain management platform form has the characteristics of scattered data sources, complex linkage, and a wide variety of configuration items.

[0004] The logic and verification of each form need to be written separately on the front end, and the implementation of general forms is not complicated. However, when facing the blockchain management platform form, there will be the following problems:

[0005] First, the front-end logic implementation code is lengthy;

[0006] Second, there are many similar form pages, which leads to duplication of work;

[0007] Third, the addition and deletion of form configuration items can only be done by the front end, which is not flexible enough for the driver configuration party;

[0008] Fourth, the connection between the driver and the form is not close enough. The driver's functions rely on the front-end project to be realized, and cannot provide "plug and play" and "pluggable" functions.

[0009] To sum up, there is a technical problem that the form written separately on the front end cannot meet the technical requirements of the blockchain management platform form. Summary of the invention

[0010] In order to solve the above technical problems, the present invention provides a driven form rendering method, device, computer equipment and computer-readable storage medium applied to a blockchain management platform.

[0011] A driven form rendering method applied to a blockchain management platform, comprising:

[0012] Agreeing on a form protocol with the backend and the driver, so that the driver develops form definition data according to the form protocol;

[0013] Configure the request entry address and related parameters, obtain the request trigger instruction from the user end, trigger the request to the backend to obtain the complete form definition data from the driver end, and dynamically fill in the blockchain platform information;

[0014] Parse the form definition data to obtain form content for page display.

[0015] A drive form rendering device applied to a blockchain management platform, comprising:

[0016] The agreement development module is used to agree on a form protocol with the back end and the driver end, so that the driver end develops form definition data according to the form protocol;

[0017] A trigger acquisition module is used to configure the request entry address and related parameters, obtain the request trigger instruction of the user end, trigger the request to the backend to obtain the complete form definition data from the driver end, and dynamically fill in the blockchain platform information;

[0018] The parsing module is used to parse the form definition data to obtain the form content for page display.

[0019] A computer device comprises a memory and a processor, wherein the memory stores a computer program and the computer program executes an implementable method in the processor.

[0020] A computer-readable storage medium stores a computer program, wherein the computer program can implement the above method when executed in a processor.

[0021] The present invention provides a driver form rendering method and device applied to a blockchain management platform. By agreeing on a form protocol with a back end and a driver end, the driver end develops form definition data according to the form protocol, configures a request entry address and related parameters, obtains a request trigger instruction from a user end, triggers a request to request the back end to obtain complete form definition data from the driver end, dynamically fills in blockchain platform information, parses the form definition data to obtain form content for page display, thereby effectively solving the technical problem that the front end alone writes a form that cannot adapt to the technical requirements of the blockchain management platform form, avoids lengthy front end logic implementation code, and avoids repetitive labor caused by a large number of similar form pages, so as to achieve a close connection between the driver end and the form, and the driver function can be independently realized without relying on the front end project, providing "plug and play" and "pluggable" functions, and a technical effect of flexible driving. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A schematic diagram of a framework of a drive form rendering system applied to a blockchain management platform provided by an embodiment;

[0023] Figure 2 A flowchart of a method for driving form rendering applied to a blockchain management platform provided by an embodiment;

[0024] Figure 3 A flowchart of a form parsing method provided by an embodiment;

[0025] Figure 4 A flowchart of a form parsing method provided by an embodiment;

[0026] Figure 5 A schematic diagram of the architecture of a form-driven rendering device applied to a blockchain management platform provided by an embodiment;

[0027] Figure 6 A schematic diagram of a computer device provided in accordance with an embodiment of the present invention. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0029] The driven form rendering method applied to the blockchain management platform provided in this embodiment can be applied in Figure 1 In the application environment, the participants may include a user end, a front end, a back end, and a driver end. This method takes the front end as the execution subject, and the execution operations of other participants are the environmental characteristics of this method, which limit this method.

[0030] like Figure 1 , the user end, front end, back end and driver end start running. The front end, back end and driver end can run in the same server, as program modules that implement different functions in the server. Among them, the driver end drives the generation of the blockchain managed by the blockchain platform, the form is saved in the driver end, the back end saves the blockchain platform data and communicates and transmits it for the driver end and the front end, and the front end faces the user end and interacts with the user end for form information.

[0031] The client communicates with the server through the network, and the client can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices. The server can be implemented as an independent server or a server cluster consisting of multiple servers.

[0032] The division of labor and cooperation between the various ends is roughly as follows:

[0033] First, the user enters the form page, triggers the component to run, and performs operations such as filling out the form, submitting the form, and modifying the form information.

[0034] Secondly, the front-end executes the form protocol agreed upon with the developer, configures the entry URL address and form callback parameters, starts the component code to run and render the form, sends a request to the back-end according to the configured URL address, obtains the form definition data returned by the back-end for parsing, displays the parsed form content on the page and renders it to the user end, performs form verification and prompts the user end to modify the form information when the verification fails, and fills the form content back into the form definition data when the verification succeeds, submits the form definition data with user data to the back-end, and prompts the back-end to save the blockchain platform data when the submission is successful.

[0035] Furthermore, the backend executes operations such as receiving the request for form definition data initiated by the frontend, sending a request to the driver to obtain the form data, filling the blockchain platform information into the form definition data, and saving the blockchain platform data.

[0036] Finally, the driver side executes the form protocol agreed with the developer, develops the form definition data, returns the form definition data, and saves the driver side data.

[0037] In one embodiment, if Figure 2 As shown, a driving form rendering method applied to a blockchain management platform is provided. The method is applied in Figure 1 The server in the example is used as an example to illustrate the process, including the following steps:

[0038] S1. Agree on the form protocol with the backend and the driver, so that the driver can develop the form definition data according to the form protocol;

[0039] S2. Configure the request entry address and related parameters, obtain the request trigger instruction from the user side, trigger the request backend to obtain the complete form definition data from the driver side, and dynamically fill in the blockchain platform information;

[0040] S3. Parse the form definition data to obtain the form content for page display.

[0041] In this embodiment, the form protocol is agreed upon with the back-end and the driver end, so that the driver end develops the form definition data according to the form protocol, configures the request entry address and related parameters, obtains the request trigger instruction of the user end, triggers the request back-end to obtain the complete form definition data from the driver end, and dynamically fills in the blockchain platform information, parses the form definition data to obtain the form content for page display, thereby effectively solving the technical problem that the front-end alone writes the form and cannot adapt to the form technology requirements of the blockchain management platform, avoids the front-end logic implementation code being lengthy, and similar form pages leading to repetitive work, so as to achieve the close connection between the driver end and the form, and the driving function can be independently realized without relying on the front-end project, providing "plug and play" and "pluggable" functions, and flexible driving technical effects.

[0042] In step S1, the form protocol is agreed upon with the back-end and the driver end so that the driver end develops the form definition data according to the form protocol, thereby solving the technical problem that the front-end alone writes the form and cannot adapt to the form technology requirements of the blockchain management platform, avoiding the front-end logic implementation code being lengthy and the large number of similar form pages leading to repetitive work.

[0043] It should be noted that a form is a common web page control for data collection, which generally includes three parts: form tag, form field and form button. The form tag is used to declare the form. The form field collects the data entered by the user, including multiple input controls such as text boxes and selection boxes. The form button controls the operation logic of the user submitting the form, such as verifying the configuration items of the form field, etc. If the logic, verification and other contents of each form need to be written separately by the front end, the form data of the blockchain management platform will be extremely complicated.

[0044] This solution lets the driver process the data definition of the form, and then saves the form data and generates the form content in combination with subsequent steps 2 and 3, thereby avoiding problems such as lengthy front-end logic implementation code and repetitive work caused by a large number of similar form pages.

[0045] In step S2, by configuring the request entry address and related parameters on the back end, the request trigger instruction of the user end is obtained, the trigger request back end obtains the complete form definition data from the driver end, and dynamically fills in the blockchain platform information, so that the back end saves the business data of the form (including but not limited to user data, platform information, etc.), and the driver end saves the driver data of the form, so as to release the driver end, so that the driver end can be flexibly driven independently, closely connected with the form, and the driving function can be independently implemented without relying on the front-end project, realizing the technical effects of "plug and play" and "pluggable" functions.

[0046] It should be noted that the form may include driver data and business data, the driver data is saved by the driver end, and the business data is saved by the back end.

[0047] It should also be noted that the request entry address may be a URL address; related parameters may be data related to form processing such as a form verification failure callback and a form submission success callback.

[0048] Specifically, when a user enters a page to fill in a form, the component code is triggered to run, and the component sends a request to the backend. The frontend obtains the request trigger instruction from the user and initiates a request to the driver. The component can be a UI module written in js language, which can be introduced and called by other js files, and parameters such as the entry point are input when calling.

[0049] In step S3, the form content is obtained by parsing the form definition data for page display, which can be used as a basis for the user to fill in the form. The user fills in the form based on the form content generated by the driver form definition data, which can avoid repetitive work.

[0050] In an improved embodiment, the front end can send the form content to the user end, and the user end fills in the form or renders the form according to the form content. The form rendering will modify the form definition data in a linked manner, thereby flexibly meeting user needs and avoiding repetitive work.

[0051] It should be noted that form rendering can be understood as whether the form is modified or adjusted.

[0052] In an improved embodiment, the front end can receive the form submitted by the user, perform form verification, and fill the content of the successfully verified form back into the form definition data or the modified form definition data, thereby avoiding repetitive work and avoiding user-side form filling errors.

[0053] In an improved embodiment, the front end can receive the form submitted by the user end, perform form verification, and allow the content of the form that failed the verification to be modified by the user end and then re-verified, thereby achieving the technical effect of obtaining the correct form.

[0054] In an improved embodiment, see Figure 3 The front end can parse the form definition data to generate a node object. When the type value of the node object is a list, it determines whether there is a child node object list. If there is a child node object list, it traverses the child node object list and determines the type value of the child node object one by one. If there is no child node object list, it parses and generates input items according to the type, and parses the verification rules and binds them to the input items to generate form items. In addition, when the type value of the node object is a table, the front end can traverse the child node object list to generate the table header and row and column values, thereby providing a variety of form generation methods to meet the specific needs of users.

[0055] In an improved embodiment, see Figure 4The front end can determine whether the input item has a linkage list. If the input item has a linkage list, it traverses the linkage list to determine whether the initial value of the current node object matches the regular expression of the linkage list item. If it matches, it obtains the value of the linkage list item to request the back end to return the form definition data that conforms to the form protocol, thereby efficiently obtaining the form definition data that conforms to the form protocol and avoiding repetitive work.

[0056] It should be noted that the list item of the linkage list is an object: the key is a regular expression, and the value is a node object or a URL address.

[0057] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0058] In one embodiment, see Figure 5 , provides a drive form rendering device applied to a blockchain management platform, which corresponds one-to-one with the drive form rendering method applied to the blockchain management platform in the above embodiment. Figure 5 As shown, the device comprises:

[0059] Agreement development module 1, used to agree on the form agreement with the back-end and the driver end, so that the driver end develops the form definition data according to the form agreement;

[0060] Trigger acquisition module 2 is used to configure the request entry address and related parameters, obtain the form filled in by the user and the trigger instruction, trigger the request backend to obtain the complete form definition data from the driver, and dynamically fill in the blockchain platform information;

[0061] Parsing module 3 is used to parse the form definition data to obtain the form content for page display.

[0062] It should be noted that the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules clearly listed, but may include other steps or modules that are not clearly listed or are inherent to these processes, methods, products or devices. The division of modules appearing in this application is merely a logical division, and there may be other division methods when implemented in actual applications.

[0063] It should also be noted that, for the specific limitations and descriptions of the above-mentioned device, please refer to the limitations and descriptions of the driver form rendering method applied to the blockchain management platform above, which will not be repeated here. Each module in the above-mentioned device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0064] In one embodiment, see Figure 5 and Figure 6 , a computer device is provided, which may be a server, and the server runs an agreement development module 1, a trigger acquisition module 2, and a parsing module 3. The internal structure diagram of the computer device may be as follows Figure 6 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data involved in the driver form rendering method applied to the blockchain management platform. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the driver form rendering method applied to the blockchain management platform is implemented.

[0065] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the driving form rendering method applied to the blockchain management platform in the above embodiment are implemented, such as Figure 2 Steps 1 to 3 shown in the figure and other extensions of the method and extensions of related steps. Alternatively, when the processor executes the computer program, the functions of each module / unit of the driving form rendering device applied to the blockchain management platform in the above embodiment are realized, for example Figure 5 The functions of modules 1 to 3 are shown in Figure 1. To avoid repetition, they will not be described here.

[0066] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of a computer device, and uses various interfaces and lines to connect various parts of the entire computer device.

[0067] The memory can be used to store computer programs and / or modules. The processor implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, video data, etc.), etc.

[0068] The memory may be integrated into the processor or provided separately from the processor.

[0069] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the driving form rendering method applied to the blockchain management platform in the above embodiment are implemented, such as Figure 2 Steps 1 to 3 shown in the figure and other extensions of the method and related steps. Alternatively, when the computer program is executed by the processor, the functions of each module / unit of the driving form rendering device applied to the blockchain management platform in the above embodiment are realized, for example Figure 5 The functions of modules 1 to 3 are shown in Figure 1. To avoid repetition, they will not be described here.

[0070] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0071] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0072] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A drive form rendering method applied to a blockchain management platform, characterized in that: include: Agreeing on a form protocol with the backend and the driver end, so that the driver end develops form definition data according to the form protocol, wherein the driver end drives the generation of a blockchain managed by the blockchain platform, and the form is stored in the driver end; Configure the request entry address and related parameters, obtain the request trigger instruction from the user end, trigger the request to the backend to obtain the complete form definition data from the driver end, and dynamically fill in the blockchain platform information; Parse the form definition data to obtain form content for page display.

2. The method according to claim 1, characterized in that Also includes: The form content is sent to the user end, and the user end fills in the form or renders the form according to the form content. The form rendering will modify the form definition data in a linked manner.

3. The method according to claim 2, characterized in that Also includes: Receive the form submitted by the user and perform form verification; The content of the form that has been successfully verified is filled back into the form definition data or the modified form definition data.

4. The method according to claim 2, characterized in that Also includes: Receive the form submitted by the user and perform form verification; The content of the form that failed the verification is modified on the user side and then re-verified.

5. The method according to claim 1, characterized in that The parsing of the form definition data includes: Parsing the form definition data to generate a node object; When the type value of the node object is a list, determining whether there is a child node object list; If there is the child node object list, traverse the child node object list and determine the type value of each child node object one by one; If there is no child node object list, the input item is parsed and generated according to the type, and the verification rule is parsed and bound to the input item to generate a form item.

6. The method according to claim 1, characterized in that The parsing of the form definition data includes: Parsing the form definition data to generate a node object; When the type value of the node object is a table, the child node object list is traversed to generate a table header and row and column values.

7. The method according to claim 5, characterized in that include: Determine whether the input item has a linkage list; If the input item has a linkage list, traverse the linkage list to determine whether the initial value of the current node object matches the regular expression of the linkage list item; If there is a match, the value of the linkage list item is obtained to request the backend to return form definition data that complies with the form protocol.

8. A drive form rendering device applied to a blockchain management platform, characterized in that: include: An agreement development module, used to agree on a form protocol with the backend and the driver end, so that the driver end develops form definition data according to the form protocol, wherein the driver end drives the generation of a blockchain managed by the blockchain platform, and the form is stored in the driver end; A trigger acquisition module is used to configure the request entry address and related parameters, obtain the request trigger instruction of the user end, trigger the request to the backend to obtain the complete form definition data from the driver end, and dynamically fill in the blockchain platform information; The parsing module is used to parse the form definition data to obtain the form content for page display.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: The computer program is executed in the processor to implement any one of the methods in claims 1-7.

10. A computer-readable storage medium storing a computer program, characterized in that: The computer program is executed in a processor to implement any method in claims 1-7.

Images