Form modification method and device, computer equipment and computer readable storage medium
By displaying and modifying another form that references the form in one form and updating metadata on the server side, the problem of cumbersome form modification operations in the existing technology is solved, and a simplified form modification process is achieved.
Patent Information
- Application Number
- CN202411873230.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-17
- Publication Date
- 2025-04-29
- Estimated Expiration
- 2044-12-17
AI Technical Summary
In the prior art, modifying a reference form requires exiting the current form and modifying it in the reference form, which is cumbersome.
Display and modify another form that references the form in one form. After saving, the server updates the metadata of the original form according to the modified form, so as to modify the form without exiting the current form.
Simplify form modification operations, reduce user operation steps, and improve form modification efficiency.
Smart Images

Figure CN119903825A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a form modification method, device, computer equipment and computer-readable storage medium. Background Art
[0002] After referencing another form in a form, if you need to modify the other form, you need to exit this form first, then open the other form to modify it, save the modification, and then return to this form to refresh it before you can use the modified other form. It can be seen that modifying the referenced form requires exiting the current form and going to the referenced form to modify it, which is a cumbersome operation. Summary of the invention
[0003] Based on this, it is necessary to provide a form modification method, device, computer equipment and computer-readable storage medium for simplifying form modification operations in response to the above technical problems.
[0004] In a first aspect, the present application provides a form modification method, which is applied to a client, and the method comprises:
[0005] Displaying a first form in a first form, wherein the first form is a form of a second form, and the second form is any form referenced by the first form;
[0006] In response to a user's field modification operation on the first table, the fields in the first table are modified to obtain a second table;
[0007] In response to a first save operation of the user on the first form, a first save instruction is sent to the server, the first save instruction includes metadata of the first form, the metadata of the first form includes metadata of the second form, and the first save instruction is used by the server to update the metadata of the second form according to the metadata of the second form.
[0008] In one embodiment, in response to the user's field modification operation on the first table, modifying the fields in the first table to obtain the second table includes:
[0009] In the case that the client has the authority to modify the second form, in response to the user's field modification operation on the first form, the fields in the first form are modified to obtain the second form.
[0010] In one embodiment, the method further comprises:
[0011] displaying the second table in the first form;
[0012] In response to a user's data entry operation on a first field in the second form, determining the input data of the first field, where the first field is any field in the second form;
[0013] In response to the user's second save operation on the first form, a second save instruction is sent to the server, the second save instruction includes the input data of the first form, the input data of the first form includes the input data of the second form, and the second save instruction is used by the server to determine the input data of the second form based on the input data of the second form.
[0014] In one embodiment, the client includes an association form component, and the method further includes:
[0015] In response to a user's operation on the associated form component in the first form, displaying an associated form list;
[0016] In response to a user selecting a second form in the associated form list, displaying the second form in the first form;
[0017] Displaying the first table in the first form includes:
[0018] In response to a table display operation of the user on the second form, the first form is displayed in the first form.
[0019] In a second aspect, the present application provides a form modification method, which is applied to a server, and the method includes:
[0020] receiving a first save instruction from a client, wherein the first save instruction includes metadata of a first form;
[0021] In the case where it is determined according to the metadata of the first form that the first form references a second form, a second table is determined according to the metadata of the first form, the second form is any form referenced by the first form, and the second table is a table format of the second form included in the metadata of the first form;
[0022] When the metadata of the second table is different from the metadata of the second form, the metadata of the second form is updated according to the second table.
[0023] In one embodiment, updating the metadata of the second form according to the second form includes:
[0024] In a case where the metadata of the second form does not include the first field, adding the first field to the metadata of the second form;
[0025] When the metadata of the second form includes the first field, but the attributes of the first field in the metadata of the second form and the metadata of the second form are different, updating the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form;
[0026] If the second field exists, deleting the second field in the metadata of the second form;
[0027] The first field is any field in the second form, and the second field is a field that exists in the metadata of the second form but does not exist in the second form.
[0028] In one embodiment, updating the attribute of the first field in the metadata of the second form according to the attribute of the first field in the second form includes:
[0029] In the case that the second form does not isolate the attributes of the first field, the attributes of the first field in the metadata of the second form are updated according to the attributes of the first field in the second form.
[0030] In one embodiment, determining the second form according to the metadata of the first form includes:
[0031] In a case where the client has permission to modify the second form, the second table is determined according to metadata of the first form.
[0032] In one embodiment, the method further comprises:
[0033] Determine a form that references the second form to obtain a first form set;
[0034] updating data of the second form in the forms included in the first form set according to the updated metadata of the second form;
[0035] In a case where the first form is stored, updating the metadata of the first form according to the metadata of the first form;
[0036] Determine a form that references the first form to obtain a second form set;
[0037] According to the updated metadata of the second form, data of the second form in the forms included in the second form set is updated.
[0038] In one embodiment, the method further comprises:
[0039] If the first form is not stored, the first form is generated according to the metadata of the first form.
[0040] In one embodiment, the method further comprises:
[0041] receiving a second save instruction from the client, wherein the second save instruction includes input data of the first form;
[0042] In the case where the input data of the first form includes the input data of the second form and there is a data entry process of the second form, starting the data entry process of the second form according to the input data of the second form;
[0043] When the data entry process is completed and the result of the data entry process is passed, the input data of the second table is determined as the input data of the second form.
[0044] In a third aspect, the present application further provides a form modification device, applied to a client, the device comprising:
[0045] A display unit, used for displaying a first table in a first form, wherein the first table is a table of a second form, and the second form is any form referenced by the first form;
[0046] a modification unit, configured to modify the fields in the first table in response to a user's field modification operation on the first table, so as to obtain a second table;
[0047] A communication unit is used to send a first save instruction to a server in response to a first save operation of the user on the first form, wherein the first save instruction includes metadata of the first form, and the metadata of the first form includes metadata of the second form, and the first save instruction is used by the server to update the metadata of the second form according to the metadata of the second form.
[0048] In a fourth aspect, the present application further provides a form modification device, which is applied to a server, and the device includes:
[0049] A communication unit, configured to receive a first save instruction from a client, wherein the first save instruction includes metadata of a first form;
[0050] a determining unit, configured to determine a second form according to the metadata of the first form, when it is determined according to the metadata of the first form that the first form references a second form, wherein the second form is any form referenced by the first form, and the second form is a table format of the second form included in the metadata of the first form;
[0051] An updating unit is configured to update the metadata of the second form according to the second form when the metadata of the second form is different from the metadata of the second form.
[0052] In a fifth aspect, the present application further provides a computer device, on which a client is installed, including a memory, a transceiver, and a processor:
[0053] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:
[0054] Displaying a first form in a first form, wherein the first form is a form of a second form, and the second form is any form referenced by the first form;
[0055] In response to a user's field modification operation on the first table, the fields in the first table are modified to obtain a second table;
[0056] In response to a first save operation of the user on the first form, a first save instruction is sent to the server, the first save instruction includes metadata of the first form, the metadata of the first form includes metadata of the second form, and the first save instruction is used by the server to update the metadata of the second form according to the metadata of the second form.
[0057] In a sixth aspect, the present application further provides a computer device, which is a server, including a memory, a transceiver, and a processor:
[0058] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:
[0059] receiving a first save instruction from a client, wherein the first save instruction includes metadata of a first form;
[0060] In the case where it is determined according to the metadata of the first form that the first form references a second form, a second table is determined according to the metadata of the first form, the second form is any form referenced by the first form, and the second table is a table format of the second form included in the metadata of the first form;
[0061] When the metadata of the second table is different from the metadata of the second form, the metadata of the second form is updated according to the second table.
[0062] In a seventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.
[0063] In an eighth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.
[0064] In an embodiment of the present application, the client displays the first form of the second form in the first form, and in response to the user's field modification operation on the first form, the field in the first form is modified to obtain the second form, and in response to the user's first save operation on the first form, a first save instruction is sent to the server; when the server determines that the first form references the second form according to the metadata of the first form, the server determines the second form according to the metadata of the first form, and when the metadata of the second form is different from the metadata of the second form, the metadata of the second form is updated according to the second form. It can be seen that in the case of referencing another form in a form, if the user needs to modify the other form, the form of the other form can be modified directly in this form, and then the form can be saved so that the background server can directly update the metadata of the other form stored according to the modified form of the other form. Since there is no need to exit this form to modify another form, user operations can be reduced, thereby simplifying the form modification operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0065] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions 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 related drawings can be obtained based on these drawings without paying creative work.
[0066] Figure 1 It is a structural diagram of a network architecture provided by an embodiment of the present application;
[0067] Figure 2 It is a flowchart of a form modification method provided in an embodiment of the present application;
[0068] Figure 3 is a schematic diagram of a client displaying a first table in a first form provided by an embodiment of the present application;
[0069] Figure 4 It is a schematic diagram of a client displaying a second table in a first table provided by an embodiment of the present application;
[0070] Figure 5 is a schematic diagram of metadata of an updated second form provided in an embodiment of the present application;
[0071] Figure 6It is a flowchart of another form modification method provided in an embodiment of the present application;
[0072] Figure 7 is a schematic diagram of entering data in a second table in a first form provided in an embodiment of the present application;
[0073] Figure 8 It is a structural schematic diagram of a form modification device provided in an embodiment of the present application;
[0074] Fig. 9 is a structural schematic diagram of another form modification device provided in an embodiment of the present application;
[0075] Fig.10 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0076] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0077] In order to better understand the embodiments of the present application, the network architecture of the present application is first introduced below.
[0078] Figure 1 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 1 As shown, the network architecture may include a server 101 and multiple clients 102 .
[0079] The server 101 and the plurality of clients 102 are connected via a network, which may be a local area network or a wide area network.
[0080] The client 102 is a client of the server 101 .
[0081] When a user needs to use the client 102, the user can enter the user name information and password information in the login interface of the client 102. After the client 102 detects the login request, it can send a login request to the server 101. The login request includes the user name information and the password information. After receiving the login request, the server 101 can perform verification according to the user name information and the password information. If the user name information and the password information are correct, the verification pass information can be sent to the client 102, and then the client 102 can communicate with the server 101.
[0082] After the client 102 successfully logs in, the user can perform operations such as form creation, form modification, data entry, data modification, etc. through the client 102. Accordingly, the server 102 can store the created form, modified form, entered data, modified data, etc.
[0083] The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or 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, and big data and artificial intelligence platforms. The server can be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of the present application.
[0084] It should be understood that Figure 1 This is an exemplary description of the network architecture of the present application and does not limit the network architecture of the present application.
[0085] Based on the above network architecture, Figure 2 Schematic diagram of a form modification method provided in an embodiment of the present application. Figure 2 As shown, the form modification method may include the following steps.
[0086] 201. The client displays the first table in the first form.
[0087] The first form is a form that is in an editing state. The first form can be an existing form or a newly created form.
[0088] The first form is a form of the second form, that is, a form format of the second form, that is, a second form displayed in a form format. The second form is any form in the forms referenced by the first form. The forms referenced by the first form can be one or more.
[0089] During the process of the user creating the first form, or during the process of modifying the created first form, if the user needs to modify the referenced second form, the client can first display the second form in the first form in table form, that is, display the first form in the first form.
[0090] 202. In response to the user's field modification operation on the first table, the client modifies the fields in the first table to obtain a second table.
[0091] After the client displays the first form in the first form, if the user needs to modify the second form, the user can perform a field modification operation on the first form. Accordingly, the client can detect the user's field modification operation on the first form, and then can modify the fields in the first form to obtain the second form in response to the user's field modification operation on the first form.
[0092] A field modification operation may include one modification operation or multiple modification operations. A modification operation may be a field addition operation, a field deletion operation, a field attribute modification operation, or a field order adjustment operation. It can be seen that a field modification operation may include one or more operations of a field addition operation, a field deletion operation, a field attribute modification operation, and a field order adjustment operation.
[0093] The field adding operation is an operation for adding, appending or adding a new field in the first table. The field deleting operation is an operation for deleting a field in the first table. The field order adjusting operation is an operation for adjusting the order of the fields in the first table. The field attribute modifying operation is an operation for modifying the attributes of the fields in the first table. Field attributes are information for describing the characteristics of a field. The attributes of a field may include the name of the field, the type of the field, the format of the field, the length of the field, required / optional, default value, etc.
[0094] The user can modify the fields of the first table through one or more modification operations to obtain a second table.
[0095] For example, Figure 3 This is a schematic diagram of a client displaying a first table in a first form provided by an embodiment of the present application. Figure 4 Schematic diagram of a client displaying a second table in a first table provided by an embodiment of the present application. Figure 3 and Figure 4 As shown, the second form adds a field for developers compared to the first form.
[0096] 203. In response to the user's first save operation on the first form, the client sends a first save instruction to the server.
[0097] Accordingly, the server receives a first save instruction from the client.
[0098] After the user modifies the first form into the second form through the client, if the user needs to save the second form, the user can perform a save operation on the first form. Accordingly, the client can detect the user's first save operation on the first form, and then can respond to the first save operation, generate a first save instruction according to the first save operation, and then send the first save instruction to the server.
[0099] The first save instruction may include metadata of the first form. The metadata of the first form may include metadata of the second form.
[0100] 204. When it is determined according to the metadata of the first form that the first form references the second form, the server determines the second form according to the metadata of the first form.
[0101] After receiving the first save instruction, the server can parse the first save instruction to obtain the metadata of the first form, and then determine whether the first form references the second form according to the metadata of the first form. In the case that it is determined that the first form references the second form according to the metadata of the first form, the second form can be determined according to the metadata of the first form. The server can extract the data of the second form from the metadata of the first form, and then generate the second form according to the data of the second form. The second form is the table form of the second form included in the metadata of the first form.
[0102] In the case where the first form references the second form, the metadata of the first form may further include an identifier of the second form. The server may first determine whether the metadata of the first form includes the identifier of the second form. If it is determined that the metadata of the first form includes the identifier of the second form, it may be determined that the first form references the second form. If it is determined that the metadata of the first form does not include the identifier of the second form, it may be determined that the first form does not reference other forms. The identifier of the second form may be the name of the second form, or may be other information that can uniquely represent the second form.
[0103] 205. When the metadata of the second table is different from the metadata of the second form, the server updates the metadata of the second form according to the second table.
[0104] After the server determines the second form, it can determine whether the metadata of the second form is the same as the metadata of the second form, that is, determine whether the metadata of the second form is the same as the metadata of the stored second form. If it is determined that the metadata of the second form is different from the metadata of the second form, it indicates that the user has modified the referenced second form in the first form, and the metadata of the second form can be updated according to the second form, so that the modification of another referenced form in one form can be realized, and the form modification operation can be simplified. If it is determined that the metadata of the second form is the same as the metadata of the second form, it indicates that the user has not modified the referenced second form in the first form, and the metadata of the second form may not be updated.
[0105] For example, Figure 5 is a schematic diagram of metadata of an updated second form provided by an embodiment of the present application. Figure 5 As shown, the server automatically adds the developer's field to the metadata of the second form.
[0106] exist Figure 2 In the form modification method shown, the client displays the first form of the second form in the first form, and in response to the user's field modification operation on the first form, the field in the first form is modified to obtain the second form, and in response to the user's first save operation on the first form, a first save instruction is sent to the server; when the server determines that the first form references the second form according to the metadata of the first form, the server determines the second form according to the metadata of the first form, and when the metadata of the second form is different from the metadata of the second form, the metadata of the second form is updated according to the second form. It can be seen that in the case of referencing another form in a form, if the user needs to modify the other form, the form of the other form can be modified directly in this form, and then the form can be saved, so that the background server can directly update the metadata of the other form stored according to the modified form of the other form. Since there is no need to exit this form to modify another form, user operations can be reduced, thereby simplifying the form modification operation.
[0107] Based on the above network architecture, Figure 6 FIG. 1 is a flow chart of another form modification method provided in an embodiment of the present application. Figure 6 As shown, the form modification method may include the following steps.
[0108] 601. The client displays a first table in a first form.
[0109] The first form is a form that is in an editing state. The first form can be an existing form or a newly created form.
[0110] The first form is a form of the second form, that is, a form format of the second form. The second form is any form in the forms referenced by the first form. The forms referenced by the first form can be one or more.
[0111] During the process of the user creating the first form, or during the process of modifying the created first form, if the user needs to modify the referenced second form, the client can first display the second form in the first form in table form, that is, display the first form in the first form.
[0112] In some embodiments, the client may include an associated form component. In response to a user's operation on the associated form component in a first form, the client displays an associated form list. In response to a user's selection operation on a second form in the associated form list, the client displays the second form in the first form. In response to a user's table display operation on the second form, the client displays the first form in the first form.
[0113] During the process of a user creating a first form, or during the process of modifying the created first form, if the user needs to reference a second form, but the first form does not have the second form, the user can first operate the associated form component in the client display interface, and the client can detect the user's operation on the associated form component in the first form, and then can display the associated form list in response to the operation. The associated form list is a list of forms that can be referenced by the first form. The client can display the associated form list in a drop-down form, in a table form, or in other forms. The associated forms included in the associated form list can be the same or different for different users using the client.
[0114] When the user needs to associate the second form in the form list, the user can select the second form in the form list. Accordingly, the client can detect the user's selection of the second form in the form list, and then display the second form in the first form in response to the selection.
[0115] In response to the selection operation, the client may display the first form in the first form, that is, display the second form in a table form; or may display the second form in a drop-down form in response to the selection operation.
[0116] In the case where the second form referenced by the user does not meet the user's needs, the user can modify the referenced second form. When the second form is displayed in a drop-down form, it is difficult or impossible for the user to modify it. Therefore, the second form can be displayed in a table form first. The user can perform a table display operation on the second form, and the client can detect the user's table display operation on the second form, and then can respond to the table display operation and display the first form in the first form.
[0117] It can be seen that the user can first select the form to be referenced, and then switch the referenced form to a table format for display. Since the form displayed in table format is more intuitive and displays more information, the user can understand the information of the form at a glance, thus improving the user experience.
[0118] 602. When the client has permission to modify the second form, the client modifies the fields in the first form to obtain the second form in response to the user's field modification operation on the first form.
[0119] Different users may have different permissions. Therefore, some users may have permission to modify certain forms, while others may not.
[0120] After the client displays the first form in the first form, if the user needs to modify the second form, the user can perform a field modification operation on the first form. Accordingly, the client can detect the user's field modification operation on the first form, and then determine whether the client has the authority to modify the second form. If it is determined that the client has the authority to modify the second form, the client can respond to the user's field modification operation on the first form and modify the fields in the first form to obtain the second form. If it is determined that the client does not have the authority to modify the second form, the client may not respond to the user's field modification operation on the first form. The client can output a prompt message for prompting the user that he does not have the modification authority, so that the user can clearly understand the reason why the modification cannot be made.
[0121] Different users have different account information. Therefore, the client can first obtain the current account information, that is, the information of the account currently in use, and then determine whether the user corresponding to the current account information has the authority to modify the second form. If it is determined that the user corresponding to the current account information has the authority to modify the second form, it can be determined that the client has the authority to modify the second form. If it is determined that the user corresponding to the current account information does not have the authority to modify the second form, it can be determined that the client does not have the authority to modify the second form.
[0122] It can be seen that the referenced form can be modified only when the user has permission. If the user does not have permission, the referenced form cannot be modified, which can improve the flexibility, efficiency and security of data management.
[0123] For other detailed descriptions of step 602 , reference may be made to the description of step 202 .
[0124] 603. In response to the user's first save operation on the first form, the client sends a first save instruction to the server.
[0125] Accordingly, the server receives a first save instruction from the client.
[0126] For a detailed description of step 603 , reference may be made to the description of step 203 .
[0127] 604. When it is determined according to the metadata of the first form that the first form references the second form and the client has permission to modify the second form, the server determines the second form according to the metadata of the first form.
[0128] After receiving the first save instruction, the server can parse the first save instruction to obtain the metadata of the first form, and then determine whether the first form references the second form based on the metadata of the first form. In the case where it is determined that the first form references the second form based on the metadata of the first form, it can be determined whether the client has the authority to modify the second form. In the case where it is determined that the client has the authority to modify the second form, the second form can be determined based on the metadata of the first form. In the case where it is determined that the client does not have the authority to modify the second form, steps 604-606 can be omitted, which can reduce unnecessary processing processes, thereby saving processing resources and reducing power consumption. The server determines whether the client has the authority to modify the second form in the same way as the client determines whether the client has the authority to modify the second form. For a detailed description, please refer to the relevant description below 602.
[0129] For other detailed descriptions of step 604 , reference may be made to the description of step 204 .
[0130] 605. When the metadata of the second table is different from the metadata of the second form, the server updates the metadata of the second form according to the second table.
[0131] After the server determines the second form, it can determine whether the metadata of the second form is the same as the metadata of the second form, that is, determine whether the metadata of the second form is the same as the metadata of the stored second form. If it is determined that the metadata of the second form is different from the metadata of the second form, it indicates that the user has modified the referenced second form in the first form, and the metadata of the second form can be updated according to the second form, so that the modification of another referenced form in one form can be realized, and the form modification operation can be simplified. If it is determined that the metadata of the second form is the same as the metadata of the second form, it indicates that the user has not modified the referenced second form in the first form, and the metadata of the second form may not be updated.
[0132] The second form may include multiple fields. In the case where the metadata of the second form does not include the first field, the server may add the first field to the metadata of the second form, that is, synchronize the first field in the second form to the metadata of the second form. In the case where the metadata of the second form includes the first field, but the attributes of the first field are different in the metadata of the second form and the second form, the server may update the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form. In the case where the second field exists, the server may delete the second field in the metadata of the second form. The first field is any field in the second form. The second field is a field that exists in the metadata of the second form but does not exist in the second form.
[0133] The server can determine whether the metadata of the stored second form includes the first field. If it is determined that the metadata of the second form does not include the first field, it indicates that the first field is a newly added field, and the first field can be added to the metadata of the second form. It can be seen that the server can synchronize all the fields newly added by the user to the second form.
[0134] When it is determined that the metadata of the second form includes the first field, the server can determine whether the attributes of the first field are the same in the metadata of the second form and the second form. When it is determined that the attributes of the first field are different in the metadata of the second form and the second form, it indicates that the user has modified the attributes of the first field. The server can update the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form. When it is determined that the attributes of the first field are the same in the metadata of the second form and the second form, it indicates that the user has not modified the attributes of the first field. The server may not update the attributes of the first field in the metadata of the second form. It can be seen that the server can synchronize the attributes of all fields whose attributes are modified by the user to the second form.
[0135] The server can also determine whether the second field exists, that is, whether there is a field that exists in the metadata of the second form but does not exist in the second form. If it is determined that the second field does not exist, it indicates that the user has not deleted the field in the second form. If it is determined that the second field exists, it indicates that the user has deleted the second field in the second form, and the server can delete the second field in the metadata of the second form. It can be seen that the server can delete all fields deleted by the user.
[0136] It can be seen that all modifications made by the user to the second form in the first form that references the second form can be synchronized to the second form, cross-form modification can be achieved, form modification operations can be simplified, form modification efficiency can be improved, and user experience can be improved.
[0137] In the case that the second form does not isolate the attributes of the first field, the server may update the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form.
[0138] In the case where the user does not want the properties of a certain field of a certain form to be modified by other users, the user can set property isolation for this field in this form. Therefore, when it is determined that the properties of the first field are different in the metadata of the second form and the second form, the server can determine whether the second form has isolated the properties of the first field. When it is determined that the second form has isolated the properties of the first field, it indicates that the property modifications to the first field in the first form cannot be synchronized to the second form, and the server does not update the properties of the first field in the metadata of the second form. When it is determined that the second form has not isolated the properties of the first field, it indicates that the property modifications to the first field in the first form can be synchronized to the second form, and the server can update the properties of the first field in the metadata of the second form based on the properties of the first field in the second form.
[0139] Since users can set properties of a field in a form in isolation, different users can set different properties of this field in different forms that reference this form according to their needs, which can meet personalized settings in different scenarios, thereby improving the flexibility of property settings and user experience, as well as improving the stability and adaptability of the system.
[0140] 606. The server determines a form that references the second form to obtain a first form set, and updates data of the second form in the forms included in the first form set according to the updated metadata of the second form.
[0141] After the server updates the metadata of the second form, it can determine the forms that reference the second form in all stored forms to obtain a first form set, and then update the data of the second form in the forms included in the first form set, that is, update the data of the second form in the forms that reference the second form. The first form set is the forms that reference the second form in all stored forms on the server, excluding the first form.
[0142] Among them, step 604 and step 606 can be executed in series or in parallel.
[0143] 607. The server determines whether the first form is stored. If the first form is not stored, the server executes step 608. If the first form is stored, the server executes step 609.
[0144] After receiving the first save instruction, the server can parse the first save instruction to obtain metadata of the first form, and then determine whether the first form is stored. If it is determined that the first form is not stored, it indicates that the first form is a newly created form, and step 608 can be executed. If it is determined that the first form is stored, it indicates that the first form has been stored in the server, and step 609 can be executed.
[0145] 608. The server generates a first form according to the metadata of the first form.
[0146] When the first form is not stored, the server may generate and store the first form according to the metadata of the first form.
[0147] 609. The server updates the stored metadata of the first form according to the metadata of the first form.
[0148] In the case where the first form is stored, the server may update the metadata of the stored first form according to the metadata of the first form. The server may add the first data to the metadata of the stored first form, may delete the second data in the metadata of the stored first form, and may modify the third data in the metadata of the stored first form. The first data is data that exists in the metadata of the received first form but does not exist in the metadata of the stored first form. The second data is data that exists in the metadata of the stored first form but does not exist in the metadata of the received first form. The third data is data that is different between the metadata of the stored first form and the metadata of the received first form.
[0149] 610. The server determines a form that references the first form to obtain a second form set, and updates data of the first form in the forms included in the second form set according to the updated metadata of the first form.
[0150] After the server updates the metadata of the stored first form, it can determine the form that references the first form, that is, determine the form that references the first form among all the stored forms, and obtain a second form set. Then, according to the updated metadata of the first form, the server can update the data of the first form in the forms included in the second form set, that is, update the data of the first form in the forms that reference the first form.
[0151] Among them, step 601-step 610 is the design process of the form, and the following process is the data entry process of the form. It should be understood that the following process is executed after step 610, and the user using the client in the following process can be the same as or different from the user using the client in steps 601-step 610.
[0152] 611. The client displays the second form in the first form.
[0153] When the user is entering data into the first form, if the user needs to enter data into the second form referenced by the first form, the client may display the second form in the first form.
[0154] 612. The client determines the input data of the first field in response to the user's data entry operation on the first field in the second table.
[0155] When the user needs to enter data into the first field in the second form, the user can perform a data entry operation on the first field in the second form. Accordingly, the client can detect the user's data entry operation on the first field in the second form, and then can determine the input data of the first field in response to the data entry operation, that is, determine the data entered by the user as the input data of the first field.
[0156] The input data of the first field may include one data or multiple data.
[0157] For example, Figure 7 Schematic diagram of inputting data in the second table in a first form provided in an embodiment of the present application. Figure 7 As shown, the user enters an entry data for each field in the second table included in the first form.
[0158] 613. In response to the user's second save operation on the first form, the client sends a second save instruction to the server.
[0159] Accordingly, the server receives a second save operation from the client.
[0160] After the data entry of the first form is completed, the user can save the first form. Accordingly, the client can detect the user's second save operation on the first form, and then send a second save instruction to the server in response to the second save operation. The second save instruction may include the input data of the first form. The input data of the first form may include the input data of the second form.
[0161] 614. When the input data of the first form includes the input data of the second form, the server determines the input data of the second form according to the input data of the second form.
[0162] After receiving the second save instruction, the server may parse the second save instruction to obtain the input data of the first form, and then determine whether the input data of the first form includes the input data of the second form. If the input data of the first form includes the input data of the second form, the server may determine the input data of the second form according to the input data of the second form. If it is determined that the input data of the first form does not include the input data of the second form, the server may not determine the input data of the second form.
[0163] The server may first determine whether the client has the authority to modify the second form. If it is determined that the client has the authority to modify the second form, it may determine whether the input data of the first form includes the input data of the second form. If it is determined that the client has the authority to modify the second form, the server may not perform step 614, thereby avoiding unnecessary operations, thereby saving processing resources and reducing power consumption.
[0164] If there is no input data in the second form, the server can determine the input data of the second form as the input data of the second form and save it. If there is already input data in the second form, the server can update the input data of the second form according to the input data of the second form.
[0165] Some forms have corresponding data entry processes for data entry. For example, some forms have an approval process after data entry. Only when the approval is passed, the data entry is completed, otherwise it needs to be modified or re-entered.
[0166] Therefore, when the input data of the first form includes the input data of the second form, the server can first determine whether there is a data entry process for the second form. When it is determined that there is a data entry process for the second form, the data entry process for the second form can be started according to the input data of the second form. When the data entry process ends and the result of the data entry process is passed, the input data of the second form can be determined as the input data of the second form. When it is determined that there is no data entry process for the second form, the server can directly determine the input data of the second form as the input data of the second form.
[0167] It can be seen that after entering the data of the second form into the first form, the server can trigger the corresponding process to ensure the integrity of the business.
[0168] After the server updates the input data of the second form according to the input data of the second table, the server can update the input data of the second form in the form included in the first form set according to the input data of the second form. The server can update the input data of the second form in all forms that reference the second form, which can ensure the consistency of data in the system and improve the efficiency of form modification.
[0169] If there is no input data in the first form, the server may store the input data of the first form in the first form. If there is input data in the first form, the server may update the stored input data of the first form according to the input data of the first form.
[0170] The server may update the input data of the first form in the forms included in the second form set according to the input data of the first form.
[0171] exist Figure 6 In the form modification method shown, when another form is referenced in a form, if the user needs to modify the other form and the user has the modification authority, the table of the other form can be modified directly in this form, and then the form can be saved, so that the background server can directly update the metadata of the stored another form according to the modified table of the other form. Since there is no need to exit this form to modify another form, user operations can be reduced, thereby simplifying the form modification operation and ensuring data security. In addition, the server can synchronously modify the data of another form in the form that references another form, and can realize the modification of multiple forms at one time, which can improve the efficiency of form modification, improve the stability and applicability of the system, and improve the consistency and integrity of data. Further, the user can enter data for another form in this form, and then the form can be saved, so that the background server can directly determine the entry data of another form stored according to the entry data of another form, so as to ensure the integrity of the business.
[0172] It should be understood that some steps in the above embodiments may not be present (ie, not executed). For example, step 606 may not be present. For example, step 610 may not be present. For example, steps 611 to 614 may not be present.
[0173] It should be understood that the same or corresponding contents in different embodiments may be referenced to each other.
[0174] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0175] Based on the same inventive concept, the embodiment of the present application also provides a form modification device for implementing the form modification method involved above. The implementation solution provided by the form modification device to solve the problem is similar to the implementation solution recorded in the above form modification method, so the specific limitations in one or more form modification device embodiments provided below can refer to the limitations of the form modification method above, and will not be repeated here.
[0176] Based on the above network architecture, Figure 8 : is a structural diagram of a form modification device provided in an embodiment of the present application. The form modification device can be applied to a client. The form modification device may include:
[0177] The display unit 801 is used to display a first table in a first form, where the first table is a table of a second form, and the second form is any form referenced by the first form;
[0178] A modification unit 802, configured to modify the fields in the first table in response to a user's field modification operation on the first table, to obtain a second table;
[0179] The communication unit 803 is used to send a first save instruction to the server in response to the user's first save operation on the first form, where the first save instruction includes metadata of the first form, and the metadata of the first form includes metadata of the second form. The first save instruction is used by the server to update the metadata of the second form according to the metadata of the second form.
[0180] In some embodiments, the modifying unit 802 is specifically configured to modify the fields in the first form to obtain the second form in response to a user's field modification operation on the first form when the client has permission to modify the second form.
[0181] In some embodiments, the display unit 801 is further configured to display a second form in the first form;
[0182] The form modification device may also include:
[0183] a determining unit, configured to determine the input data of the first field in response to the user's data entry operation on the first field in the second form, wherein the first field is any field in the second form;
[0184] The communication unit 803 is also used to send a second save instruction to the server in response to the user's second save operation on the first form, where the second save instruction includes the input data of the first form, and the input data of the first form includes the input data of the second form. The second save instruction is used by the server to determine the input data of the second form based on the input data of the second form.
[0185] In some embodiments, the client includes an association form component;
[0186] The display unit 801 is further configured to display the associated form list in response to the user's operation on the associated form component in the first form;
[0187] The display unit 801 is further configured to display the second form in the first form in response to a user selecting the second form in the associated form list;
[0188] The display unit 801 displays the first table in the first form, including:
[0189] In response to the user's table display operation on the second form, the first table is displayed in the first form.
[0190] Based on the above network architecture, Fig. 9 : is a schematic diagram of the structure of another form modification device provided in an embodiment of the present application. The form modification device can be applied to a server. The form modification device may include:
[0191] The communication unit 901 is configured to receive a first save instruction from a client, where the first save instruction includes metadata of a first form;
[0192] A determining unit 902 is used to determine the second form according to the metadata of the first form, when it is determined according to the metadata of the first form that the first form references the second form, wherein the second form is any form referenced by the first form, and the second form is a table form of the second form included in the metadata of the first form;
[0193] The updating unit 903 is configured to update the metadata of the second form according to the second form when the metadata of the second form is different from the metadata of the second form.
[0194] In some embodiments, the updating unit 903 is specifically used to:
[0195] If the metadata of the second form does not include the first field, adding the first field to the metadata of the second form;
[0196] When the metadata of the second form includes the first field, but the attributes of the first field are different in the metadata of the second form and the second form, updating the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form;
[0197] If the second field exists, deleting the second field in the metadata of the second form;
[0198] The first field is any field in the second table, and the second field is a field that exists in the metadata of the second form but does not exist in the second table.
[0199] In some embodiments, the updating unit 903 updates the attribute of the first field in the metadata of the second form according to the attribute of the first field in the second form, including:
[0200] In the case that the second form does not isolate the attributes of the first field, the attributes of the first field in the metadata of the second form are updated according to the attributes of the first field in the second form.
[0201] In some embodiments, the determining unit 902 is specifically configured to determine the second form according to the metadata of the first form when the client has permission to modify the second form.
[0202] In some embodiments, the determining unit 902 is further configured to determine a form that references the second form to obtain a first form set;
[0203] The updating unit 903 is further used to update the data of the second form in the forms included in the first form set according to the updated metadata of the second form;
[0204] The updating unit 903 is further configured to update the metadata of the stored first form according to the metadata of the first form when the first form is stored;
[0205] The determining unit 902 is further used to determine a form that references the first form to obtain a second form set;
[0206] The updating unit 903 is further configured to update the data of the second form in the forms included in the second form set according to the updated metadata of the second form.
[0207] In some embodiments, the form modification device may further include:
[0208] The generating unit is configured to generate the first form according to metadata of the first form when the first form is not stored.
[0209] In some embodiments, the communication unit 901 is further configured to receive a second save instruction from the client, the second save instruction including the input data of the first form;
[0210] The determination unit 902 is further configured to start the data entry process of the second form according to the input data of the second form when the input data of the first form includes the input data of the second form and there is a data entry process of the second form;
[0211] When the data entry process is completed and the result of the data entry process is passed, the input data of the second table is determined as the input data of the second form.
[0212] Each unit in the above-mentioned form modification device can be implemented in whole or in part by software, hardware or a combination thereof. Each of the above-mentioned units can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above-mentioned units.
[0213] Based on the above network architecture, Fig.10 It is a structural schematic diagram of a computer device provided in an embodiment of the present application. The computer device may be a computer device with a client installed, or it may be a server. The computer device may include a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. 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 historical demand values, dangerous periods and safe periods of a first energy storage device. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external EMS through a network connection. When the computer program is executed by the processor, a form modification method is implemented.
[0214] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0215] 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 above-mentioned form modification method are implemented.
[0216] It should be noted that the information of the energy storage equipment involved in this application (including but not limited to the demand value of the energy storage equipment) is information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0217] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method 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 the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0218] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0219] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A form modification method, characterized in that: Applied to a client, the method comprises: Displaying a first form in a first form, wherein the first form is a form of a second form, and the second form is any form referenced by the first form; In response to a user's field modification operation on the first table, the fields in the first table are modified to obtain a second table; In response to a first save operation of the user on the first form, a first save instruction is sent to the server, the first save instruction includes metadata of the first form, the metadata of the first form includes metadata of the second form, and the first save instruction is used by the server to update the metadata of the second form according to the metadata of the second form.
2. The method according to claim 1, characterized in that In response to the user's field modification operation on the first table, modifying the fields in the first table to obtain the second table includes: In the case that the client has the authority to modify the second form, in response to the user's field modification operation on the first form, the fields in the first form are modified to obtain the second form.
3. The method according to claim 1, characterized in that The method further comprises: displaying the second table in the first form; In response to a user's data entry operation on a first field in the second form, determining the input data of the first field, where the first field is any field in the second form; In response to the user's second save operation on the first form, a second save instruction is sent to the server, the second save instruction includes the input data of the first form, the input data of the first form includes the input data of the second form, and the second save instruction is used by the server to determine the input data of the second form based on the input data of the second form.
4. The method according to claim 1, characterized in that The client includes an association form component, and the method further includes: In response to a user's operation on the associated form component in the first form, displaying an associated form list; In response to a user selecting a second form in the associated form list, displaying the second form in the first form; The displaying of the first table in the first form comprises: In response to a table display operation of the user on the second form, the first form is displayed in the first form.
5. A form modification method, characterized in that: Applied to a server, the method comprises: receiving a first save instruction from a client, wherein the first save instruction includes metadata of a first form; In the case where it is determined according to the metadata of the first form that the first form references a second form, a second table is determined according to the metadata of the first form, the second form is any form referenced by the first form, and the second table is a table format of the second form included in the metadata of the first form; When the metadata of the second table is different from the metadata of the second form, the metadata of the second form is updated according to the second table.
6. The method according to claim 5, characterized in that The updating of the metadata of the second form according to the second table includes: In a case where the metadata of the second form does not include the first field, adding the first field to the metadata of the second form; When the metadata of the second form includes the first field, but the attributes of the first field in the metadata of the second form and the metadata of the second form are different, updating the attributes of the first field in the metadata of the second form according to the attributes of the first field in the second form; If the second field exists, deleting the second field in the metadata of the second form; The first field is any field in the second form, and the second field is a field that exists in the metadata of the second form but does not exist in the second form.
7. The method according to claim 6, characterized in that The updating of the attribute of the first field in the metadata of the second form according to the attribute of the first field in the second form includes: In the case that the second form does not isolate the attributes of the first field, the attributes of the first field in the metadata of the second form are updated according to the attributes of the first field in the second form.
8. The method according to claim 5, characterized in that The method further comprises: Determine a form that references the second form to obtain a first form set; updating data of the second form in the forms included in the first form set according to the updated metadata of the second form; In a case where the first form is stored, updating the metadata of the first form according to the metadata of the first form; Determine a form that references the first form to obtain a second form set; According to the updated metadata of the second form, data of the second form in the forms included in the second form set is updated.
9. The method according to any one of claims 5 to 8, characterized in that: The method further comprises: receiving a second save instruction from the client, wherein the second save instruction includes input data of the first form; In the case where the input data of the first form includes the input data of the second form and there is a data entry process of the second form, starting the data entry process of the second form according to the input data of the second form; When the data entry process is completed and the result of the data entry process is passed, the input data of the second table is determined as the input data of the second form.
10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 9 are implemented.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.
12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.
Citation Information
Patent Citations
Form data association method and system
CN114297993A
Data insertion method and device, equipment and storage medium
CN114564924A
Table content processing method and device, equipment and storage medium
CN114997124A
Form processing method and device
CN115640354A
Form editing method and apparatus, and storage medium storing computer-readable program
US6959414B1