CN112527260B - Method, device and storage medium for generating form JSON data - Google Patents
Method, device and storage medium for generating form JSON data Download PDFInfo
- Publication number
- CN112527260B CN112527260B CN202011519375.0A CN202011519375A CN112527260B CN 112527260 B CN112527260 B CN 112527260B CN 202011519375 A CN202011519375 A CN 202011519375A CN 112527260 B CN112527260 B CN 112527260B
- Authority
- CN
- China
- Prior art keywords
- field
- item
- assigning
- data
- input
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000008520 organization Effects 0.000 claims abstract description 15
- 238000004891 communication Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 abstract description 3
- 230000014509 gene expression Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a method, equipment and storage medium for generating form JSON data. The method comprises the steps of obtaining table unit data corresponding to a blockchain control document, wherein the organization structure of the table unit data is the same as that of a general table unit item protocol; and calling the form item protocol, and converting the form item data to obtain the form JSON data. Compared with the prior art, for the requirement of a given block chain service platform, the front end does not need to list required data fields, and the back end only needs to write simple table unit data, so that the development efficiency of the front end and the back end is improved.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a method, an apparatus, and a storage medium for generating form JSON data.
Background
BaaS (blockchain as a service) is a new type of cloud service platform based on providing blockchain to run and manage blockchain nodes and related applications for clients, and provides a series of services such as transaction operation and data analysis based on blockchain. BaaS as an internet project, front-end and back-end separation is required as a way of front-end and back-end data interaction.
Currently, when data interaction is performed based on BaaS platforms, JSON data is not designed, for a given requirement, the front end lists data fields corresponding to the requirement, and the data fields form the JSON data with front-back interface interaction. For example, a user needs to log in, and the user is required to input a user name and a password, then JSON data is composed of two fields, namely the user name and the password. It can be seen that in the prior art solution, each interface needs front-end personnel and back-end personnel to list the required data fields, which is time-consuming and labor-consuming.
Disclosure of Invention
The application provides a method, equipment and a storage medium for generating form JSON data, which are used for solving the problem of time and labor waste in front-end and back-end interaction in the prior art.
In a first aspect, a method for generating form JSON data is provided, including:
Obtaining table unit data corresponding to a blockchain control document, wherein the organization structure of the table unit data is the same as that of a general table unit program protocol;
and calling the form item protocol, and converting the form item data to obtain the form JSON data.
Optionally, invoking the form item protocol, converting the form item data to obtain the form JSON data, including:
and assigning a value to a first field in the form item protocol by using the form unit data to obtain the form JSON data.
Optionally, the form unit data includes a form;
Assigning a value to a first field in the form item protocol by using the form unit data to obtain the form JSON data, including:
Determining that the identification of the form is the same as the identification of the first field, and acquiring a second field from the form;
if the second field is a descriptive field, assigning a value to the first field by using the field content of the second field to obtain JSON data of the form;
If the second field is a nested field, acquiring field content of the second field, determining a sub-table corresponding to the field content of the second field in the form item protocol, and assigning a value to the first field in the sub-table by using a descriptive field corresponding to the second field in the table.
Optionally, assigning a value to the first field by using field content of the second field to obtain JSON data of the form, including:
and determining that the name of the second field is the same as the name of the first field, and assigning the field content of the second field to the first field to obtain the JSON data of the form.
Optionally, assigning a value to the first field in the sub-table by using a descriptive field corresponding to the second field includes:
and selecting a third field from descriptive fields corresponding to the second field, determining that the name of the third field is the same as the name of the first field, and assigning the field content of the third field to the first field.
Optionally, the form unit data includes a form entry;
Assigning a value to a first field in the form item protocol by using the form unit data to obtain the form JSON data, including:
Determining that the identity of the form entry is the same as the identity of the first field;
determining a fourth field with the same name as the first field from the form entry;
and assigning the field content of the fourth field to the first field.
Optionally, after assigning the field content of the fourth field to the first field, the method further includes:
When the form input item has an input linkage item, acquiring a target input item corresponding to the first field in the form item protocol, determining a target input linkage item corresponding to the target input item, and assigning a value to a field in the target input linkage item by using a descriptive field in the input linkage item.
Optionally, after assigning the fields in the target input linkage item by using the descriptive fields in the input linkage item, the method further includes:
Acquiring field content of an association field in the input linkage item, wherein the association field in the input linkage item comprises a form field;
When the form field is not empty, assigning a value to an association field corresponding to the form field in the target input item by utilizing the content of the form field, and determining a target form corresponding to the field content of the form field and a target input field corresponding to the field content of the form field in the form item protocol;
and assigning a value to the target input field by using the target form.
In a second aspect, there is provided an electronic device comprising: the device comprises a processor, a communication assembly, a memory and a communication bus, wherein the processor, the communication assembly and the memory are communicated with each other through the communication bus;
The memory is used for storing a computer program;
the processor is configured to execute the program stored in the memory, and implement the method for generating the form JSON data in the first aspect.
In a third aspect, a computer readable storage medium is provided, in which a computer program is stored, the computer program implementing the method for generating form JSON data described in the first aspect when executed by a processor.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: according to the technical scheme provided by the embodiment of the application, a general form item protocol is preset, when the blockchain control document exists, the form unit data corresponding to the blockchain control document is generated, and the form item protocol is called to convert the form unit data into the form JSON data. Compared with the prior art, for the requirement of a given block chain service platform, the front end does not need to list required data fields, and the back end only needs to write simple table unit data, so that the development efficiency of the front end and the back end is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
Fig. 1 is a schematic structural diagram of a system for generating form JSON data in the embodiment of the present application;
Fig. 2 is a flow chart of a method for generating form JSON data in an embodiment of the present application;
FIG. 3 is a flowchart of a method for generating JSON data in a form according to an embodiment of the present application;
Fig. 4 is a flow chart of a method for generating JSON data of another form according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a generating device of form JSON data in the embodiment of the present application;
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
For the sake of understanding the embodiments of the present application, a description is first given of a system architecture related to the present application:
referring to fig. 1, a schematic system architecture of a form JSON data generation system according to an embodiment of the present application is shown.
The system comprises: a front end device 110, a BaaS platform 120 in communication with the front end device 110, and a back end device 130 in communication with the BaaS platform 120.
The front-end equipment 110 is configured to send a blockchain control requirement or a blockchain control document corresponding to the blockchain control requirement to the BaaS platform 120; and receiving BaaS form JSON data corresponding to the block chain control requirement returned by the platform 120, and rendering the form JSON data to generate a form.
In this embodiment, the blockchain control requirement may be a requirement for creating a blockchain, a requirement for controlling start and stop of the blockchain, or a requirement for deleting the blockchain.
Illustratively, the need to create a blockchain may include the need to create different types of blockchains.
Among the different types of blockchains may include public chains, federated chains, and private chains.
Illustratively, the front-end devices include, but are not limited to, PCs, cell phones, tablet computers, and the like.
BaaS platform 120 for forwarding blockchain control requirements or blockchain control documents to backend device 130; form JSON data corresponding to blockchain control requirements is forwarded to the head-end equipment 110.
The back-end device 130 is configured to convert the blockchain control requirement into a blockchain control document, and acquire table unit data corresponding to the blockchain control document, where an organization structure of the table unit data is the same as an organization structure of a general table unit program protocol; and calling a form item protocol, and converting the form item data to obtain form JSON data.
Illustratively, the backend device may be a server or any electronic device, such as a PC, a cell phone, a tablet computer, etc.
The method for generating the form JSON data provided by the embodiment of the present application may be executed by the backend device 130, as shown in fig. 2, and may include the following steps:
step 201, obtaining table unit data corresponding to a blockchain control document.
The organization structure of the table unit data is the same as that of the general table unit program protocol.
The form item protocol is a language which is commonly agreed by the front-end equipment and the back-end equipment and used for describing the form format and is used for reflecting various attributes of the form.
Illustratively, the form item protocol may be BaaS form item protocols.
Optionally, the organization structure of the form item protocol may include:
Name, input field, input item, input linkage item, and EL expression;
wherein the name is a document for describing the form.
An input field for describing an organization of the form item protocol, which may exist in the form item protocol in a side-by-side or nested relationship.
An entry describing a data format in the form entry protocol that requires user input of parameters.
The input linkage item is a mechanism for triggering the change of the form content after a user inputs or selects a certain parameter in the form corresponding to the form item protocol.
For example, when the user selects the "Raft" option in the blockchain "consensus algorithm", the lower form will display Raft relevant parameters of the consensus algorithm for further input by the user; if the "Solo" option is selected, the following section of the form will display Solo the relevant parameters of the consensus algorithm for further input by the user.
The following illustrates the name, input field, input item, input linkage, and EL expression implementation, respectively:
the implementation of the name may be:
the implementation of the input field may be:
among the fields showing the type of the input field, the field content of the field may be shown in a corresponding list form or a table form.
Illustratively, the field content of the field is time-saving and the default correspondence table format is presented.
The implementation of the input item may be:
The input type (inputType) may include an input box (input), a number input box (numberInput), a multi-line number input box (numberInputs), a switch (switch), a selection (select), a multi-item selection (radio), a file (file), a multi-file (files), a date input box (date), a time input box (time), a date and time input box (dateTime), a number range input box (numberRange), or a button (button).
The implementation of the input linkage item may be:
The linkage type (REACTTYPE) in the input linkage is semantically as follows:
1) showInput: the Input field is displayed, defined in the inputs field, with the Input field labeled 0 being taken.
2) ShowInputsByNumber: repeatedly displaying an input field with the subscript of 0 in the inputs field according to the input number; for example, input 4, inputs are padded repeatedly into an array of length 4 using inputs [0] as templates.
3) ShowInputByUrl: a specified HTTP request needs to be sent that will return an Input, populate inputs [0] or the target Input field where the primary key is targetInputId.
EL expression:
in the Input field Input, the id, title, defaultValue field of the Input item InputField, and the url field in the linkage UrlAction, it is possible that the El expression in the form of $ { xxx } needs to appear depending on the context of the front-end dynamics filling, depending on the requirements of the BaaS item.
For example, when creating a Fabric blockchain, it is necessary to display the organization name corresponding to the current user in a form, and this data of the organization name is dynamically filled into the form according to the current user, which is implemented by using EL expressions.
The data sources that appear in the El expression include the value of the Input item, the field value of the user information, and the index of showInputsByNumber-type linkages.
The value of an entry is represented by the id field of the entry, e.g., an entry box with id "blockchainName" and the user entered "chain001", then the value of $ { blockchainName } is "chain001".
The field value of the user information is represented by $ { user. Xxx }, for example, $ { user. Org }, which represents the name of the organization where the user is located.
The index of showInputsByNumber type linkage is the index where the current repeat fill is located when the showInputsByNumber linkage type is obtained using $ { index }, starting with 1. For example, if the user inputs 4, the inputs array in InputReact is repeatedly populated into an array of length 4 using inputs 0 as templates, wherein $ { index } in inputs 0 is 1, $ { index } in inputs 1 is 2, $ { index } in inputs 2 is 3, and $ { index } in inputs 3 is 4.
Based on the general form item protocol, the generated form unit data may at least include a form array, a form input item array, and an input linkage item.
The form array corresponds to an input field of the form item protocol. Illustratively, the definition of the form array may be:
The form number group of the form unit data directly reflects the integral format of the form JSON data, and the Inputs contain Inputs so as to reflect the parallel relation of the forms; the Input contains SubInputs to represent the nested relationship of the form.
Wherein, the field content of SubInputs field is the ID of the sub-table, and the field content of Fields is the ID of the table entry.
Wherein the dependent field indicates the dependency between the block chain node in item BaaS on the host resource. The deployment of blockchain nodes depends on a host instance, and this field will specify the host form required by the blockchain node.
The form entry corresponds to an entry of a form entry protocol.
Illustratively, the definition of the form entry may be:
Finally, with respect to the input linkage item, the input linkage item of the form unit data corresponds to the input linkage item of the form protocol.
The definition of the input linkage item may be:
Wherein, reactions represent the input linkage array. For a single input linkage FieldReactions, the Field represents the ID of the form entry.
The input linkage reactions correspond to the input linkages InputReact in the project input protocol.
And 202, calling a form item protocol, and converting the form item data to obtain form JSON data.
Because the organization structure of the table unit data is the same as that of the table unit data, when the table unit data is converted, the table unit data can be utilized to assign a first field in the table unit protocol so as to obtain the table JSON data.
Wherein the first field is any description field in the form item protocol.
Alternatively, the description field in the form item protocol may be preset by the user.
For example, the description field may be a title, an wait, or the like field.
Alternatively, assignment of the table element data to the first field in the table element protocol may be implemented using correspondence of the identifiers of the different parts.
Illustratively, when the form unit data includes a form array, the form array includes a plurality of forms, as shown in fig. 3, for any form in the form array, a first field in the form item protocol is assigned, so as to obtain an implementation step of the form JSON data:
Step 301, determining that the identifier of the form is the same as the identifier of the first field, and acquiring a second field from the form.
The identifier of the first field is the identifier of the input domain where the first field is located.
And 302, if the second field is a descriptive field, assigning a value to the first field by using the field content of the second field to obtain the form JSON data.
The description field in the form may be preset, for example, the description field may include fields such as title or wait.
Optionally, when the first field is assigned with the field content of the second field, the field content of the second field is assigned to the first field when the name of the second field is the same as the name of the first field.
Step 303, if the second field is a nested field, obtaining the field content of the second field, determining a sub-table corresponding to the field content in the table list protocol, and assigning a value to the first field in the sub-table by using the descriptive field corresponding to the second field in the table list.
Wherein the field content of the nesting field can be an identification.
The nesting field may be preset. Such as the nestability field may include SubInputs (sub-input field) fields.
Illustratively, when the second field is SubInputs fields, the identity of the sub-input field is the same as the field content of SubInputs fields.
Optionally, the process of assigning a value to the first field in the sub-form may be selecting a third field from the descriptive fields by using the descriptive field in the form corresponding to the second field, determining that the name of the third field is the same as the name of the first field, and assigning the field content of the third field to the first field.
Illustratively, when the form element data includes an array of form entries, the array of form entries includes a plurality of form entries, and for any form entry in the array of form entries, as shown in fig. 4, a first field in a form entry protocol is provided with an assignment, resulting in an implementation step of the form JSON data:
Step 401, determining that the identification of the form entry is the same as the identification of the first field.
The identifier of the first field may be an identifier of a form entry to which the first field belongs.
Step 402, determining a fourth field with the same name as the first field from the form input item;
step 403, assigning the field content of the fourth field to the first field.
Further, when the form input item has an input linkage item, a value can be assigned to the target input linkage item corresponding to the first field in the form item protocol.
Optionally, the fields in the target input linkage item are assigned with descriptive fields in the input linkage item.
Illustratively, the descriptive field in the input linkage item may be TriggerRegex, reactType, targetInputId or the like.
Optionally, when the field content of the association field in the input linkage item is not empty, assigning a value to the association field corresponding to the form field in the target input item by using the content of the form field, and determining a target form corresponding to the field content of the form field and a target input field corresponding to the field content in the form item protocol; and assigning a value to the target input domain by using the target form.
Illustratively, the relevance field in the input linkage item may be InputId.
According to the technical scheme provided by the embodiment of the application, a general form item protocol is preset, when the blockchain control document exists, the form unit data corresponding to the blockchain control document is generated, and the form item protocol is called to convert the form unit data into the form JSON data. Compared with the prior art, for the requirement of a given block chain service platform, the front end does not need to list required data fields, and the back end only needs to write simple table unit data, so that the development efficiency of the front end and the back end is improved.
The embodiment of the application also provides a device for generating the form JSON data, the specific implementation of the device can be referred to the description of the embodiment part of the method, and the repetition is omitted, as shown in fig. 5, the device mainly comprises:
The acquiring unit 501 is configured to acquire table unit data corresponding to a blockchain control document, where an organization structure of the table unit data is the same as an organization structure of a general table unit item protocol;
And the conversion unit 502 is used for calling the form item protocol and converting the form item data to obtain form JSON data.
Based on the same concept, the embodiment of the application also provides an electronic device, as shown in fig. 6, where the electronic device mainly includes: processor 601, communication component 602, memory 603 and communication bus 604, wherein processor 601, communication component 602 and memory 603 complete communication with each other through communication bus 604. The memory 603 stores a program executable by the processor 601, and the processor 601 executes the program stored in the memory 603 to implement the following steps:
Obtaining the table unit data corresponding to the blockchain control document, wherein the organization structure of the table unit data is the same as that of a general table unit program protocol;
and calling a form item protocol, and converting the form item data to obtain form JSON data.
The communication bus 604 mentioned in the above electronic device may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated as EISA) bus, or the like. The communication bus 604 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 6, but not only one bus or one type of bus.
The communication component 602 is used for communication between the electronic device and other devices described above.
The memory 603 may include random access memory (Random Access Memory, abbreviated as RAM) or may include non-volatile memory (non-volatile memory), such as at least one disk memory. Alternatively, the memory may be at least one memory device located remotely from the aforementioned processor 601.
The processor 601 may be a general-purpose processor, including a central Processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a digital signal processor (DIGITAL SIGNAL Processing, DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer-readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to execute the form JSON data generation method described in the above embodiment.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, by a wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, microwave, etc.) means from one website, computer, server, or data center to another. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape, etc.), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. The method for generating the form JSON data is characterized by comprising the following steps:
Obtaining table unit data corresponding to a blockchain control document, wherein the organization structure of the table unit data is the same as that of a general table unit program protocol;
Assigning a value to a first field in the form item protocol by using the form unit data to obtain form JSON data;
Wherein the form unit data includes a form;
Assigning a value to a first field in the form item protocol by using the form unit data to obtain the form JSON data, including:
Determining that the identification of the form is the same as the identification of the first field, and acquiring a second field from the form;
if the second field is a descriptive field, assigning a value to the first field by using the field content of the second field to obtain JSON data of the form;
If the second field is a nested field, acquiring field content of the second field, determining a sub-table corresponding to the field content of the second field in the form item protocol, and assigning a value to the first field in the sub-table by using a descriptive field corresponding to the second field in the table.
2. The method of claim 1, wherein assigning the first field with the field content of the second field results in JSON data for the form, comprising:
and determining that the name of the second field is the same as the name of the first field, and assigning the field content of the second field to the first field to obtain the JSON data of the form.
3. The method of claim 1, wherein assigning the first field in the sub-table using the descriptive field corresponding to the second field comprises:
and selecting a third field from descriptive fields corresponding to the second field, determining that the name of the third field is the same as the name of the first field, and assigning the field content of the third field to the first field.
4. The method of claim 1, wherein the form element data comprises form entries;
Assigning a value to a first field in the form item protocol by using the form unit data to obtain the form JSON data, including:
Determining that the identity of the form entry is the same as the identity of the first field;
determining a fourth field with the same name as the first field from the form entry;
and assigning the field content of the fourth field to the first field.
5. The method of claim 4, wherein assigning field contents of the fourth field to the first field further comprises:
When the form input item has an input linkage item, acquiring a target input item corresponding to the first field in the form item protocol, determining a target input linkage item corresponding to the target input item, and assigning a value to a field in the target input linkage item by using a descriptive field in the input linkage item.
6. The method of claim 5, wherein assigning the field in the target input linkage item using the descriptive field in the input linkage item further comprises:
Acquiring field content of an association field in the input linkage item, wherein the association field in the input linkage item comprises a form field;
When the form field is not empty, assigning a value to an association field corresponding to the form field in the target input item by utilizing the content of the form field, and determining a target form corresponding to the field content of the form field and a target input field corresponding to the field content of the form field in the form item protocol;
and assigning a value to the target input field by using the target form.
7. An electronic device, comprising: the device comprises a processor, a communication assembly, a memory and a communication bus, wherein the processor, the communication assembly and the memory are communicated with each other through the communication bus;
The memory is used for storing a computer program;
the processor is configured to execute a program stored in the memory, and implement the method for generating form JSON data according to any one of claims 1 to 6.
8. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the method of generating form JSON data as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011519375.0A CN112527260B (en) | 2020-12-21 | 2020-12-21 | Method, device and storage medium for generating form JSON data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011519375.0A CN112527260B (en) | 2020-12-21 | 2020-12-21 | Method, device and storage medium for generating form JSON data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112527260A CN112527260A (en) | 2021-03-19 |
| CN112527260B true CN112527260B (en) | 2024-07-12 |
Family
ID=75002020
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011519375.0A Active CN112527260B (en) | 2020-12-21 | 2020-12-21 | Method, device and storage medium for generating form JSON data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112527260B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110941614A (en) * | 2019-11-21 | 2020-03-31 | 望海康信(北京)科技股份公司 | Form generation method and device, electronic equipment and computer readable storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130174181A1 (en) * | 2011-12-30 | 2013-07-04 | Sap Ag | Frontend - backend communication decision based on business object metadata |
| CN104657420B (en) * | 2015-01-09 | 2019-06-04 | 北京京东尚科信息技术有限公司 | Page display method and system |
| CN105183450A (en) * | 2015-07-28 | 2015-12-23 | 武汉驼峰信息技术有限公司 | E-government form model configuration system with foreground and background separation function |
| US10997362B2 (en) * | 2016-09-01 | 2021-05-04 | Wacom Co., Ltd. | Method and system for input areas in documents for handwriting devices |
| GB2563429A (en) * | 2017-06-15 | 2018-12-19 | Hsbc Group Man Services Limited | System for dynamic user interface generation |
| CN110244942B (en) * | 2019-06-19 | 2023-03-21 | 优信拍（北京）信息科技有限公司 | Page generation method, device and system |
| CN111178012A (en) * | 2019-12-03 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Form rendering method, device and equipment and storage medium |
| CN111597484B (en) * | 2020-07-22 | 2020-10-27 | 成都新希望金融信息有限公司 | UI dynamic generation method |
-
2020
- 2020-12-21 CN CN202011519375.0A patent/CN112527260B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110941614A (en) * | 2019-11-21 | 2020-03-31 | 望海康信(北京)科技股份公司 | Form generation method and device, electronic equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112527260A (en) | 2021-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11991238B2 (en) | Sharing network addresses | |
| CN109815261B (en) | Global search function implementation and data real-time synchronization method and device and electronic equipment | |
| CN1901547B (en) | Method and apparatus for making web service policy agreement | |
| CN110019080B (en) | Data access method and device | |
| CN106973075B (en) | Share comment method and system, domain name code-transferring method, client and server | |
| CN111460298A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN113364853B (en) | Business service system, business request method and gateway equipment | |
| CN110855555B (en) | Mail sending method, device, equipment and computer readable storage medium | |
| US20160219058A1 (en) | System and method for file sharing | |
| US8768949B2 (en) | Document management user interface with user customized application functionalities | |
| CN111988171A (en) | Method, proxy server and system for calling SOAP Web service based on RESTful style request | |
| CN113645304A (en) | Data service processing method and related equipment | |
| CN103023870A (en) | Method, device and equipment for outputting data in message | |
| JP2011141617A (en) | Web page browsing system, control method thereof, and relay server | |
| WO2011137643A1 (en) | Communication client and method for initiating communication service | |
| WO2019024275A1 (en) | Page loading method, device and computer equipment | |
| CN113806104A (en) | Interface access request processing method, API gateway, server and system | |
| CN112527260B (en) | Method, device and storage medium for generating form JSON data | |
| EP2511836A1 (en) | Virtual DNLA file system for navigating hierarchical HTML gation structures | |
| US20090172027A1 (en) | Telephone menu selection | |
| JP5348413B2 (en) | Application server, object management method, and object management program | |
| CN112947900A (en) | Web application development method and device, server and development terminal | |
| CN105378710B (en) | Identification search matching and the search result through changing | |
| JP2018120576A (en) | Method and device for generating web page | |
| CN114528510A (en) | Webpage data processing method and device, electronic equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |