CN115455915A - Form operation method and device - Google Patents

Abstract

The invention discloses a form operation method and device, and relates to the technical field of cooperative office. One embodiment of the method comprises: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at the forms to be edited, which are sent by the plurality of first type clients; displaying a current form to be edited in a plurality of first type clients according to a collaborative editing link, acquiring a plurality of post-editing instructions sent by one or a plurality of first type clients based on the current form to be edited by utilizing the collaborative editing link, determining an execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule, and executing the instructions in sequence; and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited. The embodiment can draw the form in a mode of multi-person cooperation without conflict, so that a single form version corresponding to the same task is formed.

Description

Form operation method and device

Technical Field

The invention relates to the technical field of cooperative office, in particular to a form operation method and device.

Background

In the Web end and the page of the mobile terminal APP, the input information of the user can be collected through the form. At present, in a task requiring collection of related data through a form, the form is generally generated in a single drawing manner (that is, only one person draws at the same time, rather than multiple persons draw in cooperation at the same time), and because there may be a situation that multiple persons draw successively many times, it is inevitable to form multiple different versions in the same task, and further it is easy for a user who fills in data to fill in the form incorrectly, for example, a user fills in a form that is not the latest version, and it is also difficult for an administrator to select a proper form version when viewing data submitted by the user, and because the form data viewed by the administrator is generally displayed in a form, when the same task has multiple versions, each version corresponds to one data form, so that data displayed by each data form is uneven, and large pieces of data are often hollowed out, which is not beneficial to subsequent data analysis.

Disclosure of Invention

In view of this, embodiments of the present invention provide a form operation method and apparatus, which can draw a form in a multi-user cooperation manner without conflict, so as to form a single form version corresponding to the same task.

To achieve the above object, according to one aspect of the present invention, a form manipulation method is provided.

The form operation method provided by the embodiment of the invention comprises the following steps: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients; displaying a current form to be edited in the first type of clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or more first type of clients based on the current form to be edited by using the collaborative editing link, and determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule and executing the instructions in sequence; and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

Optionally, the form to be edited corresponds to a current task; and, the method further comprises: in response to receiving the editing completion instruction, determining a current form to be edited as a unique form of the current task; after the unique form is edited according to an additional editing instruction which is sent by a first type of client and aims at the unique form, determining the form formed by editing as the unique form of the current task; after the unique form is formed, a form fill notification is sent to at least one second type client.

Optionally, the method further comprises: in response to receiving a first submission instruction which is sent by a second type of client and carries a user identifier and an identifier of the unique form, storing current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form; after the current filling data is submitted, in response to receiving an access request which is sent by a second type of client and carries a user identifier and the identifier of the unique form, returning the pre-stored current filling data to the second type of client; wherein the returned current filling data is externally displayed based on a page rendered by the document data; and in response to receiving a modified submission instruction which is sent by a second type of client and carries a user identifier and the identifier of the unique form, storing the current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form.

Optionally, the unique form has at least one control therein, and the control corresponds to a field in a data table associated with the unique form one to one; and storing the current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form, wherein the record comprises: and for the filled data which is related to any control in the unique form in the current filled data, storing the filled data into a field of the record corresponding to the control.

Optionally, the method further comprises: under the condition that the additional editing instruction indicates that any control in the unique form is deleted, judging whether submitted data exists in a field of the data table corresponding to the control or not; if the control does not exist, deleting the control in the unique form and the field of the data table corresponding to the control; and if the control exists, the control in the unique form and the field of the data table corresponding to the control are reserved, and the field is set to be in a hidden state in the form structure data of the unique form.

Optionally, the form structure data of the unique form includes: attribute information of a field corresponding to each control in the unique form; and, the method further comprises: responding to a viewing instruction which is sent by a first type client and aims at the unique form, generating a header according to the pre-stored form structure data of the unique form, taking the submitted data in the pre-stored data table associated with the unique form as data in the table to form a target form, and returning and displaying the target form to the first type client; in the target form, the same record corresponds to the same user identifier, and the same field corresponds to the same control in the unique form.

Optionally, the method further comprises: after the target form is returned to the first type client and displayed, establishing cooperative editing links with the first type clients in response to receiving form editing instructions aiming at the target form and sent by the first type clients; displaying a current target form in the first type of clients according to the cooperation editing link, acquiring a plurality of additional editing instructions sent by one or more first type of clients based on the current target form by using the cooperation editing link, determining an execution sequence of the additional editing instructions according to a preset editing instruction execution rule, and executing the additional editing instructions in sequence; and in response to receiving an editing ending instruction sent by the first type client, storing the in-table data of the current target form into the data table associated with the unique form.

Optionally, the document data includes: the first type of client has administrator authority, and the second type of client has data filling authority.

To achieve the above object, according to another aspect of the present invention, there is provided a form manipulation apparatus.

The form operation apparatus of the embodiment of the present invention may include: a link establishment unit for: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients; the collaborative editing unit is used for displaying a current form to be edited in the first type of clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or more first type of clients based on the current form to be edited by using the collaborative editing link, and determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule and executing the instructions in sequence; a form storage unit for: and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

Optionally, the form to be edited corresponds to a current task; and the apparatus further comprises an additional editing unit for: in response to receiving the editing completion instruction, determining a current form to be edited as a unique form of the current task; after the unique form is edited according to an additional editing instruction which is sent by a first type of client and aims at the unique form, determining the form formed by editing as the unique form of the current task; after the unique form is formed, a form fill notification is sent to at least one second type client.

To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.

An electronic device of the present invention includes: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the form operation method provided by the invention.

To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable storage medium.

A computer-readable storage medium of the present invention stores thereon a computer program, which when executed by a processor implements the form manipulation method provided by the present invention.

According to the technical scheme of the invention, the embodiment of the invention has the following advantages or beneficial effects:

in consideration of the problems of user misfilling, difficult version selection, data hollowing and the like caused by the current situation of multiple versions of a form generated by a single-person form drawing mode in the prior art, the embodiment of the invention provides a multi-person collaborative form writing mode, latest form content can be displayed and latest editing instructions can be obtained in real time through collaborative editing links pre-established by a server and each client, and then the editing instructions are sequentially executed through preset rules to realize multi-person collaborative editing of the form, so that data collision is avoided, a single-version form (a unique form) corresponding to the same task is finally formed, and the problems caused by multiple versions in the prior art are effectively solved. Further, the embodiment of the invention also provides a related execution process of a multi-person collaborative form editing mode, such as form creation, information sharing after form editing is completed, user data filling, temporary storage and submission of filled data, modification of submitted data, summary viewing of collected data, modification of collected data in a viewing process and the like.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic diagram illustrating the main steps of a form operation method according to an embodiment of the present invention;

FIG. 2 is a block diagram of the overall architecture of an embodiment of the present invention;

FIG. 3 is a schematic diagram of a form editing flow according to an embodiment of the invention;

FIG. 4 is a schematic diagram of a form filling flow according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a form viewing flow in accordance with an embodiment of the present invention;

FIG. 6 is a schematic diagram of the components of the form manipulation apparatus in an embodiment of the present invention;

FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 8 is a schematic structural diagram of an electronic device for implementing the form operation method in the embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In computer front-end technology, a form (form) is a page element used for collecting user input information, and the page can be a Web page or a mobile terminal APP page. The form typically contains one or more controls, each of which can gather corresponding information, including a single-line text entry field, a multi-line text entry field, a rich text entry field, a radio box, a multi-box, a date control, a button, etc. In practical application, scenes in which multiple persons are required to cooperatively draw a form often exist, for example, a form of a certain task includes a large number of functional regions, multiple persons are required to respectively draw different regions to accelerate development progress, the tasks include annual leave application information collection, software system experience investigation and the like, and the form drawing includes a mode of generating a form by writing codes and a mode of forming a form by dragging controls.

In the prior art, a form drawing mode with cooperation of multiple persons cannot be realized, so that data conflict is generated when the multiple persons draw, for example, contents edited by one person are deleted by another person, and multiple form versions exist in the same task, so that the problems that a user filling data wrongly fills forms, an administrator is difficult to select a proper form version when viewing data submitted by the user, data hollowing exists in a data display form, and the like are caused. Aiming at the problems, the invention provides a multi-user online collaboration form drawing method, which can avoid data conflict in the multi-user drawing process, and only forms a form with a unique version (namely, a unique form below) for the same task, thereby avoiding the problems caused by multiple versions.

It should be noted that the embodiments of the present invention and the technical features of the embodiments may be combined with each other without conflict.

FIG. 1 is a diagram illustrating the main steps of a form operation method according to an embodiment of the present invention.

As shown in fig. 1, the form operation method according to the embodiment of the present invention is executed by a collaborative document service at a service end, where the collaborative document service is a service for collaborating documents on line for multiple people. The method for operating the form comprises the following specific steps:

step S101: and in response to receiving initial editing instructions which are sent by the first type clients and aim at the form to be edited, establishing collaborative editing links with the first type clients.

In the embodiment of the present invention, the first type of client refers to a client having administrator authority (an operator of which is referred to as an administrator), and the second type of client (an operator of which is referred to as a user) refers to a client having fill-in authority. The administrator authority can perform the following operations: creating forms, editing forms, viewing all the data collected by the forms, and modifying the data, the fill authority can perform the following operations: filling data in the form, editing the data filled by the user, and submitting the data. In the specific application, other types of clients may also be formed according to the service requirement, for example, a third type of client having a filing authority and being capable of viewing part or all of the form collected data, and a fourth type of client having a filing authority and being capable of viewing part of the form collected data and modifying the data, where the execution flow of the two types of clients when filing data is the same as that of the second type of client, the execution flow of the fourth type of client when viewing the form collected data is the same as that of the first type of client, and the execution flow of the fourth type of client when modifying the form collected data is the same as that of the first type of client, and only the first type of client and the second type of client are taken as examples for description below. In addition, the administrator can further assign administrator rights or fill-in rights to other clients.

Before step S101 is performed, a first type of client needs to create a form. Specifically, the first type of client may interact with the collaborative document service to create a form on the basis of an empty document, or select a form template stored in advance to create a form, or copy a form stored in advance to create a form, and then may perform drawing of a form in collaboration with multiple persons.

The steps for multiple administrators to collaboratively edit forms are as follows. Firstly, the first class clients where the administrators are located send initial editing instructions to the collaborative document service, after receiving the instructions, the collaborative document service establishes specific collaborative editing links with the first class clients, the links are special channels for executing multi-person collaborative editing forms, and data and instructions can be transmitted between the collaborative document service and the first class clients in a two-way mode.

Step S102: displaying a current form to be edited in a plurality of first type clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or a plurality of first type clients based on the current form to be edited by utilizing the collaborative editing link, determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule, and executing the instructions in sequence.

After the collaborative editing link is established, the current latest form to be edited can be transmitted to each first-class client in real time, and a later editing instruction sent by each first-class client can also be transmitted to the collaborative document service in real time. After the collaborative document service receives a plurality of later editing instructions within a certain time, the execution sequence can be determined according to the sending time or the receiving time of each later editing instruction, and then the corresponding editing operation is executed in sequence according to the determined sequence. If the collaborative document service receives a plurality of post-editing instructions simultaneously, the post-editing instructions can be sequenced according to preset rules and relevant characteristics of an administrator and the first class of clients. The rule for determining the execution sequence of the later-stage editing instruction is a preset editing instruction processing rule, and the rule can be flexibly set according to actual needs. Through the setting, data conflict in the multi-person collaborative form editing process can be avoided. It should be noted that, in the above, the collaborative editing by multiple administrators is directed to the same version of the form for the same task, and finally only a single form for the same task can be formed, thereby avoiding various problems caused by the multi-version form generated for the same task in the prior art.

Step S103: and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

When the multi-person collaborative editing is finished, any first-class client can send an editing completion instruction to the collaborative document service. After receiving the instruction, the collaborative document service executes storage of the form to be edited, so that the form to be edited becomes an edited form. In practical application, the form related data to be stored includes document data and form structure data of the form to be edited, and the document data may include metadata of the form and rich text data of the form page. For example, the metadata of the form may contain corresponding task identifier, form name, creator identifier, belonging directory identifier, current state, etc., and the rich text data of the form page may contain identifier, position, style, etc. data of each control in the form, through which the form page frame can be rendered. The form structure data may include attribute information of a field corresponding to each control in the form, where, regarding the field, each form is displayed in a form in a subsequent filled data viewing process, each form may correspond to a unique data table (table) for display, the field refers to a field in the data table, each field corresponds to one control in the form, each record corresponds to one user, and the attribute information of the field may include a field identifier (where the field identifier corresponds to the control identifier one to one), a field name (which may correspond to a corresponding control name), an output state (which may be hidden or displayed in a subsequent display form), and the like. In a specific scenario, the collaborative document service may store the metadata, the rich text data, and the form structure data of the form into corresponding tables of a preset database.

After the data storage related to the form is completed, the administrator may determine the sharing object and authority of the form through interaction with the collaborative document service, for example, select a certain person from a preset person list as the administrator, and select a certain person as the user for filling data. Finally, the collaborative document service may send a notification to the shared object, for example, send a form fill-in notification to the selected user.

In the embodiment of the invention, the administrator can also continue to edit the edited form. Specifically, the first type of client sends an additional editing instruction for a form edited and completed by a certain task to the collaborative document service, and the collaborative document service executes editing according to the instruction to form a latest unique form of the task. Thereafter, the collaborative document service may determine the shared objects and rights and send form fill notifications. It can be seen that in the technical scheme of the invention, a single-version form is formed by multiple editions of multiple administrators aiming at the same task, so that the defects of the existing multi-version form are overcome. In addition, the above editing process may be collaborative editing by multiple administrators, and as in step S102, in this case, the collaborative document service needs to establish the aforementioned collaborative editing link and determine the execution order of each instruction according to the editing instruction processing rule.

The following describes the form filling process.

After completing the filling of the form page of the second type of client, the user may send a first submission instruction to the collaborative document service for submission, where the instruction carries the user identifier and the form identifier. After receiving the instruction, the collaborative document service may store current fill-in data in the form, which is transmitted by the second type of client, in a record corresponding to the user identifier in the data table associated with the form, that is, for fill-in data in the current fill-in data, which is associated with any control in the form, store the fill-in data in a field of the record corresponding to the control. In practical application, a user can modify and temporarily store the filled data in the data filling process, and the data is stored in a corresponding data table through the first-class client during temporary data storage.

In one embodiment, when the user accesses the form again after completing the filling, the previously filled data can still be displayed back, and the implementation principle is that the second type of client sends an access request for a form to the collaborative document service, where the request carries the user identifier and the form identifier. And the collaborative document service returns the users of the corresponding records pre-stored in the corresponding data table of the form to the second type client, so that the users are shown in the form page. And after the modification is completed, the user sends a modified submission instruction to the collaborative document service through the second type of client, and the collaborative document service stores the current filled data in the form into a corresponding data table.

Specifically, in the form editing process in step S101 to step S103, if the user wants to delete a control existing in the form, that is, if a certain additional editing instruction indicates to delete a control in the form, the collaborative document service first determines whether the submitted data exists in the field corresponding to the control of the data table corresponding to the form: if the data does not exist, the control does not acquire the data, and the collaborative document service deletes the control in the form and the field of the data table corresponding to the control; if the field exists, the data is collected by the control, and the collaborative document service reserves the field of the control in the form and the data table corresponding to the control, but the field can be set to be in a hidden state in the corresponding form structure data (namely, the output state of the field is set to be hidden). The above operation can avoid data collision and user report data loss.

The following describes the viewing and presentation process of the collected data.

When an administrator wants to check data filled in a form by a plurality of users, a checking instruction for the form can be sent to the collaborative document service through the first class client, and the instruction carries a form identifier. After receiving the instruction, the collaborative document service may first query form structure data of the form stored in advance according to the above form, and generate a header of a target table for displaying the collected data according to the form structure data, for example, taking a name of each field as a column name of each column in the target table, and determining whether the field is hidden or displayed in the target table according to an output state of each field.

And then, the collaborative document service inquires submitted data in a pre-stored data table corresponding to the form through the form identification, fills all the submitted data in corresponding positions of the target form according to the user identification and the field to which the submitted data belongs, and finally forms the target form to return to the first type of client and display the target form. It can be seen that each row of the target form corresponds to a user and each column corresponds to a control in the form.

In a specific application, if some data in the target table needs to be adjusted by an administrator, the administrator can modify the target table and store the final data in the corresponding data table, and the above editing can also support multi-person collaborative editing. Similar to the steps S101 to S103, the first type client where the administrator is located issues a form editing instruction to the collaborative document service, after receiving the instruction, the collaborative document service establishes a specific collaborative editing link with the first type client, where the link is a dedicated channel for performing multi-user collaborative editing of form data, and data and instructions can be bidirectionally transmitted between the collaborative document service and the first type client, that is, the above collaborative editing link may transmit the current latest form data to each first type client in real time, and may also transmit an additional editing instruction issued by each first type client to the collaborative document service in real time.

After the collaborative document service receives a plurality of additional editing instructions within a certain time, the execution sequence can be determined according to the sending time or the receiving time of each additional editing instruction, and then the corresponding editing operation is executed in sequence according to the determined sequence. If the collaborative document service receives a plurality of additional editing instructions at the same time, the later editing instructions can be sequenced according to the relevant characteristics of the administrator and the first class of client sides according to the preset rule. The rule for determining the execution sequence of the later-stage editing instruction is a preset editing instruction execution rule, and the rule can be flexibly set according to actual needs. Through the setting, data conflict in the multi-person collaborative form editing process can be avoided.

When the multi-person collaborative editing table is finished, any first-class client can send an editing end instruction to the collaborative document service. After receiving the instruction, the collaborative document service stores the in-table data of the target table into the corresponding data table, thereby ending the table editing.

An embodiment of the present invention is described below with reference to fig. 2 to 5.

Fig. 2 is a schematic diagram of the overall architecture of the present embodiment, as shown in fig. 2. When the administrator draws the form in a coordinated mode, the administrator firstly selects a drawing mode, the drawing mode comprises self-defining (namely creating a blank document), a form template and form copying, drawing is started after the drawing mode is selected, and page controls are selected through an editor of the online coordinated document, so that the simultaneous drawing of the form by multiple persons is supported. The data can be dynamically stored in real time in the drawing process, the data storage comprises a document storage part and a form storage part, the document stores rich text data aiming at table unit data and a form page, the document storage part and the rich text data are respectively stored in a document basic information table and a document rich text table, the form storage part aims at form structure data and filling data, and the form structure data and the filling data are respectively stored in a form structure information table and a form data information table (the table is a data table corresponding to the form). After the form is drawn, sharing is needed, an administrator selects a sharing object, the sharing object comprises a user, a group and a department organization, after the sharing object is determined, authorization needs to be conducted on the sharing object, and a notification needs to be sent, wherein the authority comprises a filling authority and an administrator authority. After the user receives the form filling notification, the following filling-related operations can be executed: submitting data, temporarily storing the data, editing the data and displaying the data back, wherein each operation needs to call a corresponding filling interface. At the later stage, the administrator can inquire the submitted form data, the data are displayed through the online collaborative form, and a corresponding inquiry interface is required to be called during displaying.

Fig. 3 is a schematic diagram of a form editing process in this embodiment, as shown in fig. 3, an administrator selects three ways of a user-defined form, a form template, and a form copy at a client to create a form, then a plurality of administrators select controls to draw the form in a coordinated manner, finally formed form unit data can be stored in a structured database, formed form page rich text data and form structure data can be stored in an unstructured database, and finally a shared object is selected from a user list to allocate a right and send a notification.

Fig. 4 is a schematic diagram of a form filling process in an embodiment of the present invention, as shown in fig. 4, a user fills in data through a client (such as a Web end and an APP end), if data needs to be temporarily stored in a filling process, a temporary storage interface provided by a gateway service can be called, the gateway service first verifies the validity of the user identity, and calls the temporary storage interface of a collaborative document service after the user identity passes the temporary storage interface, after receiving a request, the collaborative document service calls a permission service to verify whether the user has permission to fill in the form, and if no permission exists, the collaborative document service returns a corresponding prompt; if the authority exists, the collaborative document service stores the filled data in a database. The user can submit after the filling report is finished, the client side calls a submission interface provided by the gateway service, the gateway service firstly verifies the validity of the user identity, and then calls the submission interface provided by the collaborative document service, and the collaborative document service stores the filling data in the database. And then, when the user opens the form again, the collaborative document service calls a display interface provided by the gateway service to check the identity validity of the user, and after the user passes the display interface, the collaborative document service inquires the submitted data of the user according to the user identification and the form identification to assemble and return the data. The user may then edit the corresponding data in the form in a similar manner.

Fig. 5 is a schematic diagram of a form viewing process according to an embodiment of the present invention, as shown in fig. 5, an administrator queries a form data form submitted by a user through a client, a gateway service first performs identity verification, then performs authority verification in cooperation with a document service call authority service, queries previously stored form structure data through a form identifier to generate a header, queries previously stored submitted data as in-table data, assembles the header and the in-table data to form a target form, and returns the target form to the client. The administrator can also perform multi-person collaborative table data modification through the collaborative editing link.

In the technical scheme of the embodiment of the invention, a plurality of persons are supported to simultaneously draw the form in an online and coordinated manner, and the same task only has a single-version form, so that the conflict of multiple versions is avoided, and the complexity of drawing the form and the complexity of dynamically creating the form are reduced. Because the same task only has a form with a single version, the user can fill in the form, and therefore the situation that the form is filled in by mistake is avoided. In addition, the administrator checks the data submitted by the user in a form, the form is also a collaborative form, online collaborative editing of multiple persons is supported, rapid modification of form data from a global view is facilitated, data accuracy is guaranteed, a single-version form only corresponds to one form, and the data display does not have the data hollowing problem.

It should be noted that, for the convenience of description, the foregoing method embodiments are described as a series of acts, but those skilled in the art will appreciate that the present invention is not limited by the order of acts described, and that some steps may in fact be performed in other orders or concurrently. Moreover, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no acts or modules are necessarily required to implement the invention.

To facilitate a better implementation of the above-described aspects of embodiments of the present invention, the following also provides relevant means for implementing the above-described aspects.

Referring to fig. 6, a form operation apparatus 600 according to an embodiment of the present invention may include: a link establishing unit 601, a collaborative editing unit 602, and a form storage unit 603.

The link establishing unit 601 may be configured to: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients; the collaborative editing unit 602 may be configured to display a current form to be edited in the multiple first-class clients according to the collaborative editing link, obtain, by using the collaborative editing link, multiple post-editing instructions sent by one or more first-class clients based on the current form to be edited, determine an execution sequence of the multiple post-editing instructions according to a preset editing instruction processing rule, and execute the multiple post-editing instructions in sequence; the form storage unit 603 may be used to: and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

In the embodiment of the invention, the form to be edited corresponds to the current task; and the apparatus further comprises an additional editing unit for: in response to receiving the editing completion instruction, determining a current form to be edited as a unique form of the current task; after the unique form is edited according to an additional editing instruction which is sent by a first type of client and aims at the unique form, determining the form formed by editing as the unique form of the current task; after the unique form is formed, a form fill notification is sent to at least one second type client.

As a preferred solution, the apparatus 600 may further include a filling processing unit, configured to: in response to receiving a first submission instruction which is sent by a second type of client and carries a user identifier and an identifier of the unique form, storing current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form; after the current filling data is submitted, responding to an access request which is sent by a second type client and carries a user identifier and the identifier of the unique form, and returning the pre-stored current filling data to the second type client; wherein the returned current fill-in data is externally displayed based on a page rendered by the document data; and in response to receiving a modified submission instruction which is sent by a second type of client and carries a user identifier and the identifier of the unique form, storing the current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form.

Preferably, the unique form has at least one control, and the control corresponds to fields in a data table associated with the unique form one by one; and, the filling processing unit may be further configured to: and for the filled data which is related to any control in the unique form in the current filled data, storing the filled data into a field of the record corresponding to the control.

In a specific application, the additional editing unit may be further configured to: under the condition that the additional editing instruction indicates that any control in the unique form is deleted, judging whether submitted data exists in a field of the data table corresponding to the control or not; if the control does not exist, deleting the control in the unique form and the field of the data table corresponding to the control; and if the control exists, the control in the unique form and the field of the data table corresponding to the control are reserved, and the field is set to be in a hidden state in the form structure data of the unique form.

In practical applications, the form structure data of the unique form includes: attribute information of a field corresponding to each control in the unique form; and, the apparatus 600 may further comprise a data viewing unit for: responding to a viewing instruction which is sent by a first type client and aims at the unique form, generating a header according to the pre-stored form structure data of the unique form, taking the submitted data in the pre-stored data table associated with the unique form as data in the table to form a target form, and returning and displaying the target form to the first type client; in the target form, the same record corresponds to the same user identifier, and the same field corresponds to the same control in the unique form.

In one embodiment, the apparatus 600 may further comprise a table cooperation unit for: after the target form is returned to the first type client and displayed, establishing cooperative editing links with the first type clients in response to receiving form editing instructions aiming at the target form and sent by the first type clients; displaying a current target form in the first type of clients according to the cooperation editing link, acquiring a plurality of additional editing instructions sent by one or more first type of clients based on the current target form by using the cooperation editing link, determining an execution sequence of the additional editing instructions according to a preset editing instruction execution rule, and executing the additional editing instructions in sequence; and in response to receiving an editing ending instruction sent by the first type client, storing the in-table data of the current target form into the data table associated with the unique form.

Further, in an embodiment of the present invention, the document data includes: the first type of client has administrator authority, and the second type of client has data filling authority.

According to the technical scheme of the embodiment of the invention, the problem that the online drawn form cannot execute multi-person collaborative editing is solved, various problems caused by multi-version forms are avoided, the complexity of drawing the forms and dynamically creating the forms is reduced, and the problems of collaborative editing of form data and data hollowing in form display when submitted data is checked through the forms are solved. In addition, the data of the collaborative form and the collaborative form are communicated, the filled form data is displayed in the collaborative form, multiple persons are supported to collaboratively edit the submitted form data on line at the same time, and the data can be finely adjusted rapidly through the global view.

Fig. 7 shows an exemplary system architecture 700 of a form manipulation method or a form manipulation apparatus to which embodiments of the present invention may be applied.

As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704 and a server 705 (this architecture is merely an example, and the components included in a specific architecture may be adjusted according to specific application). The network 704 is the medium used to provide communications links between terminal devices 701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use the terminal devices 701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. Various client applications, such as a form editing application (for example only), may be installed on the terminal devices 701, 702, 703.

The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 705 may be a server providing various services, such as a document server (for example only) providing support for a user using a form editing application operated by the terminal devices 701, 702, 703. The document server may process the received form editing request and feed back the processing result (e.g., a form formed after editing-by way of example only) to the terminal devices 701, 702, 703.

It should be noted that the form operation method provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the form operation apparatus is generally disposed in the server 705.

It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The invention also provides the electronic equipment. The electronic device of the embodiment of the invention comprises: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the form operation method provided by the invention.

Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the present invention. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU) 801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the computer system 800 are also stored. The CPU801, ROM 802, and RAM803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted into the storage section 808 as necessary.

In particular, the processes described in the main step diagrams above may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the main step diagram. In the above-described embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the central processing unit 801, performs the above-described functions defined in the system of the present invention.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present invention may be implemented by software or hardware. The described units may also be provided in a processor, which may be described as: a processor includes a link establishing unit, a collaborative editing unit, and a form storing unit. Where the names of these units do not in some cases constitute a limitation on the unit itself, for example, the link establishing unit may also be described as a "unit providing a collaborative editing link to a collaborative editing unit".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to perform steps comprising: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients; displaying a current form to be edited in the first type of clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or more first type of clients based on the current form to be edited by using the collaborative editing link, and determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule and executing the instructions in sequence; and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

In the technical scheme of the embodiment of the invention, in consideration of the problems of user misfilling, difficult version selection, data hollowing and the like caused by the current situation of multiple versions of the form generated by a single-person form drawing mode in the prior art, the embodiment of the invention provides a multi-person collaborative form writing mode, latest form contents can be displayed and latest editing instructions can be obtained in real time through collaborative editing links pre-established by a server and various clients, and then the editing instructions are sequentially executed through preset rules to realize multi-person collaborative editing of the form, so that data collision is avoided, a single-version form (unique form) corresponding to the same task is finally formed, and the problems caused by multiple versions in the prior art are effectively solved. Further, the embodiment of the invention also provides a related execution process of a multi-person collaborative form editing mode, such as form creation, information sharing after form editing is completed, user data filling, temporary storage and submission of filled data, modification of submitted data, summary viewing of collected data, modification of collected data in a viewing process and the like.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (12)

1. A method of form manipulation, comprising:

establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients;

displaying a current form to be edited in the first type of clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or more first type of clients based on the current form to be edited by using the collaborative editing link, and determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule and executing the instructions in sequence;

and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

2. The method of claim 1, wherein the form to be edited corresponds to a current task; and, the method further comprises:

in response to receiving the editing completion instruction, determining a current form to be edited as a unique form of the current task;

after the unique form is edited according to an additional editing instruction which is sent by a first type of client and aims at the unique form, determining the form formed by editing as the unique form of the current task;

after the unique form is formed, a form fill notification is sent to at least one second type client.

3. The method of claim 2, further comprising:

in response to receiving a first submission instruction which is sent by a second type of client and carries a user identifier and an identifier of the unique form, storing current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form;

after the current filling data is submitted, in response to receiving an access request which is sent by a second type of client and carries a user identifier and the identifier of the unique form, returning the pre-stored current filling data to the second type of client; wherein the returned current fill-in data is externally displayed based on a page rendered by the document data;

and in response to receiving a modified submission instruction which is sent by a second type of client and carries a user identifier and the identifier of the unique form, storing the current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form.

4. The method according to claim 3, wherein the unique form has at least one control therein, and the control corresponds to a field in a data table associated with the unique form in a one-to-one manner; and storing the current filled data in the unique form of the second type of client into a record corresponding to the user identifier in a data table associated with the unique form, wherein the record comprises:

and for the filled data which is related to any control in the unique form in the current filled data, storing the filled data into a field of the record corresponding to the control.

5. The method of claim 4, further comprising:

under the condition that the additional editing instruction indicates that any control in the unique form is deleted, judging whether submitted data exist in a field of the data table corresponding to the control or not;

if the control does not exist, deleting the control in the unique form and the field of the data table corresponding to the control;

and if the control exists, the control in the unique form and the field of the data table corresponding to the control are reserved, and the field is set to be in a hidden state in the form structure data of the unique form.

6. The method of claim 4, wherein the form structure data for the unique form comprises: attribute information of a field corresponding to each control in the unique form; and, the method further comprises:

responding to a viewing instruction which is sent by a first-class client and aims at the unique form, generating a header according to the pre-stored form structure data of the unique form, taking the submitted data in the pre-stored data table associated with the unique form as data in the table to form a target form, and returning and displaying the target form to the first-class client; in the target form, the same record corresponds to the same user identifier, and the same field corresponds to the same control in the unique form.

7. The method of claim 6, further comprising:

after the target form is returned to the first type client and displayed, establishing cooperative editing links with the first type clients in response to receiving form editing instructions aiming at the target form and sent by the first type clients;

displaying a current target form in the first type of clients according to the cooperation editing link, acquiring a plurality of additional editing instructions sent by one or more first type of clients based on the current target form by using the cooperation editing link, determining an execution sequence of the additional editing instructions according to a preset editing instruction execution rule, and executing the additional editing instructions in sequence;

and in response to receiving an editing ending instruction sent by the first type client, storing the in-table data of the current target form into the data table associated with the unique form.

8. The method according to any one of claims 2 to 7, wherein the document data includes: the first type of client has administrator authority, and the second type of client has data filling authority.

9. A form manipulation apparatus, comprising:

a link establishment unit for: establishing collaborative editing links with a plurality of first type clients in response to receiving initial editing instructions aiming at a form to be edited, which are sent by the first type clients;

the collaborative editing unit is used for displaying a current form to be edited in the first type of clients according to the collaborative editing link, acquiring a plurality of post-editing instructions sent by one or more first type of clients based on the current form to be edited by using the collaborative editing link, and determining the execution sequence of the plurality of post-editing instructions according to a preset editing instruction processing rule and executing the instructions in sequence;

a form storage unit for: and responding to the received editing completion instruction sent by the first type client, and storing the document data and the form structure data of the current form to be edited.

10. The apparatus of claim 9, wherein the form to be edited corresponds to a current task; and the apparatus further comprises an additional editing unit for:

in response to receiving the editing completion instruction, determining a current form to be edited as a unique form of the current task; after the unique form is edited according to an additional editing instruction which is sent by a first type of client and aims at the unique form, determining the form formed by editing as the unique form of the current task; after the unique form is formed, a form fill notification is sent to at least one second type client.

11. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-8.

Images