Document collaborative management method and system, electronic equipment and storage medium

Abstract

The invention relates to the technical field of document management, and discloses a document collaborative management method and system, electronic equipment and a storage medium, and the method comprises the steps: obtaining to-do data of a to-do list, responding to a distribution instruction of the to-do list, determining a target executor executing the to-do list according to the distribution instruction, and executing the to-do list according to the target executor; synchronizing the to-be-handled data to a to-be-handled module of the target executor, wherein the to-be-handled module is used for displaying the to-be-handled list and tracking the execution condition of the to-be-handled list; through the above method, a more practical and more efficient document collaborative management method is provided to check and process backlogs in a centralized manner, so that the operation experience and the working efficiency of employees are improved.

Description

Technical Field

[0001] The present application relates to the technical field of document management, and in particular to a document collaborative management method, system, electronic device and storage medium. Background Art

[0002] In the current digital office environment, daily business operations involve a large amount of bill processing work. With the advancement of technology, these tasks have gradually shifted from traditional paper bills to electronic bills, which have been efficiently managed and operated through computers or various systems. However, although the application of electronic bills has significantly improved processing speed and accuracy, the so-called "information island" phenomenon still occurs because different departments, different business lines, and even systems introduced in different time periods are based on their own specific technology stacks and architecture designs.

[0003] "Information islands" not only mean the lack of effective data sharing and interaction mechanisms between systems, but also lead to the breakage and lack of coordination of business processes. Specifically, when processing bills, departments may need to frequently switch between different systems and manually input or export data, which not only increases the complexity and error rate of operations, but also causes a lot of time and resource waste. In addition, due to inconsistent data or untimely updates between systems, employees may face the situation of repeatedly processing the same bills or miss the opportunity to process key bills, which not only reduces work efficiency, but also affects employees' work experience and satisfaction. Obviously, there is an urgent need for a new document collaborative management method to solve at least one of the above problems.

[0004] It should be noted that the above content only provides background technical information related to the present application and does not necessarily constitute prior art. Summary of the invention

[0005] In view of the shortcomings of the prior art mentioned above, the present application provides a document collaborative management method, system, electronic device and storage medium to centrally view and process to-do items, thereby improving employee operating experience and work efficiency.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0007] According to one aspect of an embodiment of the present application, a document collaborative management method is provided, including: obtaining to-do data of a to-do item; in response to an assignment instruction of the to-do item, determining a target executor who is to execute the to-do item according to the assignment instruction; synchronizing the to-do data to a to-do module of the target executor so that the target executor can process the to-do item, and the to-do module is used to display the to-do item and track the execution status of the to-do item.

[0008] In one embodiment of the present application, based on the aforementioned scheme, after synchronizing the to-do data to the to-do module of the target executor, the method also includes: obtaining the execution status of the to-do items; if the execution status is successful, modifying the item status of the to-do items to processed, modifying the to-do items to completed items, and displaying the completed items through the completed module of the target executor, wherein the to-do data includes the item status; if the execution status is a failure, prompting the target executor according to the execution status.

[0009] In one embodiment of the present application, based on the aforementioned scheme, the target executor is prompted according to the execution status, including: obtaining the management basis of the to-do items; analyzing the cause of the execution failure according to the basic information of the to-do items and the management basis, wherein the to-do data includes the basic information; and prompting the target executor according to the cause of failure.

[0010] In one embodiment of the present application, based on the aforementioned scheme, the method also includes at least one of the following: after modifying the to-do item to a done item, changing the done data corresponding to the done item to a read-only state; if it is determined based on the item type of the to-do item that the next to-do item will be triggered after the to-do item is successfully executed, determining and displaying the next executor of the next to-do item based on the to-do data, wherein the to-do data includes the item type and the deadline; determining the priority of the to-do item based on the item type and the deadline, so as to determine the display method of the to-do item in the to-do module based on the priority.

[0011] In one embodiment of the present application, based on the aforementioned scheme, the allocation instruction is generated in the following manner: pre-setting multiple role types and role permissions corresponding to each of the role types, the role permissions including data viewing scope and / or data management scope; setting a user role for each user based on the role type, wherein the user role includes at least one of the role types; determining the role permissions corresponding to each of the users according to the user roles, so as to generate the allocation instruction according to the role permissions and the to-do data.

[0012] In one embodiment of the present application, based on the aforementioned scheme, the method further includes: calculating the remaining processing time of the to-do item based on the current time and the deadline of the to-do item; if the remaining processing time is less than or equal to a preset time threshold, generating a due date reminder message according to the remaining processing time, and prompting the target executor through the due date reminder message.

[0013] In one embodiment of the present application, based on the aforementioned scheme, the method also includes: receiving an association request, the association request including the current first to-do item of the target executor and the second to-do item of the associated executor to be associated; according to the association request, establishing an association relationship between the first to-do data corresponding to the first to-do item and the second to-do data corresponding to the second to-do item, so that the target executor can view the second to-do data, and / or the associated executor can view the first to-do data.

[0014] According to one aspect of an embodiment of the present application, a document collaborative management system is provided, including: a data acquisition module, used to obtain to-do data of a to-do item; a task allocation module, used to respond to the allocation instruction of the to-do item, and determine the target executor who executes the to-do item according to the allocation instruction; a data synchronization module, used to synchronize the to-do data to the to-do module of the target executor, and the to-do module is used to display the to-do item and track the execution status of the to-do item.

[0015] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements a document collaborative management method as described in any one of the above embodiments.

[0016] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer, the computer is enabled to execute the document collaborative management method as described in any one of the above embodiments.

[0017] Beneficial effects of the present application: The present application obtains the to-do data of the to-do items, responds to the allocation instructions of the to-do items, determines the target executors who are to execute the to-do items according to the allocation instructions, and synchronizes the to-do data to the to-do module of the target executors so that the target executors can process the to-do items. The to-do module is used to display the to-do items and track the execution status of the to-do items. The to-do items can be directly assigned to the corresponding target executors, and the to-do modules of the target staff members can be used to uniformly and intuitively display the to-do items of the target executors, which not only improves work efficiency, but also improves the work experience and satisfaction of employees.

[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0020] Figure 1 is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application;

[0021] Figure 2 is a flowchart of a document collaborative management method shown in an exemplary embodiment of the present application;

[0022] Figure 3 is a block diagram of a document collaborative management system shown in an exemplary embodiment of the present application;

[0023] Figure 4 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0024] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0025] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present application in a schematic manner, and therefore the illustrations only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0026] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0027] First of all, it should be noted that in today's digital transformation, enterprises are facing an increasingly complex and diverse business operation environment, which directly leads to the increased heterogeneity of information system architecture. Systems introduced in different departments, different business lines, and even different time periods are often based on different technology stacks and architectural designs, forming the so-called "information islands". Although this phenomenon of coexistence of heterogeneous systems has met the business needs of a specific period to a certain extent, it has also brought about problems such as information not being shared, process not being coordinated, and repeated and inefficient operations, which has seriously restricted the overall operational efficiency of the enterprise and the work experience of employees.

[0028] In order to break this dilemma, building an integrated platform (that is, the document collaborative management system in this application) has become a consensus among many companies. The integrated platform aims to achieve seamless integration and data interoperability between heterogeneous systems through a unified interface, standardized data exchange protocols, and intelligent business process management. Among them, the employee to-do workbench (that is, the to-do module in this application), as one of the core components of the integrated platform, plays a key role in connecting various business systems, centrally displaying and processing to-do items. It can not only help employees quickly master to-do tasks across systems, promote efficient execution and closed-loop management of tasks, but also improve operational convenience and user experience.

[0029] In this context, as an important support for corporate financial management, it is particularly important for the comprehensive bill processing system to fully integrate its functions into the integrated platform. Bill processing involves multiple key links such as reconciliation, invoice management, and payment and collection. These links often span multiple departments such as finance, procurement, and sales, and involve a large amount of cross-system data interaction and process collaboration. Therefore, seamlessly integrating the to-do and done items in the comprehensive bill processing system into the workbench of the integrated platform means that the bill processing status can be monitored in real time, and relevant personnel can be reminded to handle key tasks in a timely manner, effectively avoiding omissions or delays, thereby accelerating capital circulation, reducing financial risks, and further improving the overall operational efficiency and response speed of the enterprise.

[0030] To sum up, building an employee to-do workbench on an integrated platform and integrating the relevant to-do information of the comprehensive bill processing system into it is a key measure to cope with the challenges of heterogeneous systems, optimize business processes, and improve work efficiency and employee satisfaction. It is of great significance to promote the digital transformation and sustainable development of enterprises.

[0031] Figure 1 It is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application.

[0032] Reference Figure 1As shown, the system architecture may include a data acquisition device 101 and a computer device 102. Among them, the computer device 102 may be at least one of a desktop graphics processing unit (Graphic Processing Unit, GPU) computer, a GPU computing cluster, a neural network computer, etc. The data acquisition device 101 is used to collect the to-do data of the to-do items. In this embodiment, the data acquisition device 101 obtains the above data and provides it to the computer device 102 for processing. Relevant technical personnel can use the computer device 102 to respond to the allocation instructions of the to-do items, determine the target executor who executes the to-do items according to the allocation instructions, and synchronize the to-do data to the to-do module of the target executor. The to-do module is used to display the to-do items and track the execution of the to-do items. It should be noted that the data acquisition device 101 and the computer device 102 provided in this embodiment are only an example and should not bring any restrictions to the functions and scope of use of the embodiments of the present application.

[0033] It should be noted that the document collaborative management method provided in the embodiment of the present application is generally executed by the computer device 102 , and accordingly, the document collaborative management system is generally set in the computer device 102 .

[0034] Figure 2 is a flowchart of a document collaborative management method shown in an exemplary embodiment of the present application. The document collaborative management method can be executed by a computing and processing device. The computing and processing device can be Figure 1 The computer device 102 shown in FIG. Figure 2 As shown, the document collaborative management method at least includes steps S210 to S230, which are described in detail as follows:

[0035] In step S210, to-do data of the to-do item is obtained.

[0036] In one embodiment of the present application, the document collaborative management system that executes the document collaborative management method can obtain the to-do data of the to-do items from each system or platform associated with the document collaborative management system. Among them, the to-do items include but are not limited to the to-do items of reconciliation, invoicing, collection, refund, and payment, and the to-do items of reconciliation include but are not limited to the to-do items of purchase and sales. The to-do data includes but is not limited to the status of the item, the type of item, the content of the item, i.e., the basic information, and the deadline.

[0037] In step S220, in response to the assignment instruction of the to-do item, a target executor for executing the to-do item is determined according to the assignment instruction.

[0038] In one embodiment of the present application, access and operation permissions to specific to-do items are restricted through user role permissions, which can ensure data security and compliance and avoid problems such as data leakage or abuse due to improper permissions.

[0039] In one embodiment of the present application, the allocation instruction is generated in the following manner: pre-setting a plurality of role types and the role permissions corresponding to each role type, the role permissions include data viewing scope and / or data management scope; setting the user role of each user based on the role type, wherein the user role includes at least one role type, that is, a user can have multiple roles; determining the role permissions corresponding to each user according to the user role, so as to generate the allocation instruction according to the role permissions and the to-do data. The allocation instruction generated by the role permissions of each user and the to-do data of the to-do items can not only accurately match the personnel suitable for executing the item, but also avoid the irrationality and blindness of task allocation, so that the task can be quickly and accurately transmitted to the target executor; and because the task allocation is based on the user's role permissions and the to-do data of the to-do items, the target executor who is finally determined usually has a clearer understanding of the task, which reduces the communication cost caused by unclear tasks or misunderstandings, so that the executor can get involved in the work faster and improve work efficiency.

[0040] In this embodiment, the data viewing scope and / or data management scope of the role authority can be set according to business attributes, document fields, role relationships, etc., for example: according to pre-set business types (such as centralized procurement, bidding service fees, bidding platform usage fees, centralized procurement service fees), unit levels (for example, the account manager determines the jurisdiction based on the level of the unit served), and suppliers (for example, the purchasing manager determines the jurisdiction of the purchasing staff based on the agreement number signed with the supplier); it can also be based on the amount of the document (for example, the processor is determined based on the size of the invoice amount); it can also be set to only view data related to your own department (for example, department managers can view the data of everyone in the department, and managers of the superior department can view the data of the subordinate department), or it can be set to only view data related to yourself (for example, to-do items created on your own page, or with a user ID (userID) from the interface).

[0041] In one embodiment of the present application, in response to an assignment instruction for a to-do item, a process of determining a target executor for executing the to-do item based on the assignment instruction includes the following steps: in response to an assignment instruction for the to-do item, displaying corresponding candidate executors; in response to a selection instruction for the candidate executors, determining the target executor for executing the to-do item.

[0042] In step S230, the to-do data is synchronized to the to-do module of the target executor so that the target executor can process the to-do items.

[0043] Among them, the To-do module is used to display the to-do items and track the execution of the to-do items. The to-do module of the target staff uniformly and intuitively displays the to-do items of the target executors, which not only improves work efficiency, but also improves the work experience and satisfaction of employees.

[0044] In one embodiment of the present application, the to-do module displays to-do items and to-do data of the to-do items. The to-do module is also used to process the displayed to-do items, and in response to an execution instruction for executing the to-do items, execute the to-do items based on the to-do data. Take the to-do items as an example of invoicing to-do: obtain an invoicing application, which includes the to-do invoice data of the to-do invoice; determine the target executor of the to-do invoice based on the to-do invoice data and role authority, and synchronize the to-do invoice data to the to-do module corresponding to the target executor, so that the target executor can issue invoices based on the to-do invoice data. In response to the invoicing execution instruction for executing the invoicing to-do, invoices are issued based on the to-do invoice data.

[0045] In one embodiment of the present application, after synchronizing the to-do data to the to-do module of the target executor, the method also includes: obtaining the execution status of the to-do items; if the execution status is successful, changing the item status of the to-do items to processed, changing the to-do items to completed items, and displaying the completed items through the completed module of the target executor, wherein the to-do data includes the item status; if the execution status is failed, prompting the target executor according to the execution status.

[0046] In one embodiment, a table can be used to record the item data corresponding to the item (including the to-do data of the to-do items and the done data of the done items), and the to-do data and the done data can be distinguished by a flag / mark. For example, when the flag variable flag is false, the item data corresponding to the item is the to-do data, and when the flag variable flag is true, the item data corresponding to the item is the done data. If the execution status is successful, the item status of the to-do item is modified to be handled by modifying the flag variable corresponding to the item status, and the to-do item is modified to the done item. It can be understood that since the to-do item has been modified to the done item, the item is no longer displayed in the to-do module, but the item (done item) is displayed through the done module of the target executor. By recording the distribution and execution of the to-do items, the audit and tracking of the task execution process can be achieved, which helps to ensure the legality and compliance of the task, and provide relevant evidence and basis when necessary.

[0047] In one embodiment of the present application, prompting the target executor based on the execution status includes: obtaining the management basis of the to-do items; analyzing the cause of the execution failure based on the basic information and management basis of the to-do items, wherein the to-do data includes basic information; and prompting the target executor based on the cause of failure.

[0048] In this embodiment, still taking the to-do items as the invoicing to-do as an example, the management basis of the invoicing to-do items is obtained. For example, the invoicing data to be issued needs to be complete, standardized, and accurate, and it is necessary to avoid issuing invoices for the same transaction repeatedly to ensure the uniqueness of the invoice. For example: check whether the basic information such as the invoice type, invoice code, invoice number, etc. is complete, verify whether the key information such as the name, taxpayer identification number, address and telephone number of the seller and the buyer is complete, verify whether the detailed information such as the name, specification model, unit, quantity, unit price, amount, etc. of the goods or services is complete, and verify whether the invoicing amount exceeds the limit. The verification mechanism of the invoicing system, such as the automatic verification function, can be used to check the accuracy and completeness of the invoice information. The failure reason of the execution failure is analyzed according to the to-do invoicing data and the management basis. If the analysis shows that the failure reason is the lack of necessary information such as the name of the seller and the buyer, the taxpayer identification number, etc., the target execution personnel are prompted according to the failure reason.

[0049] In one embodiment of the present application, it also includes at least one of the following: after modifying a to-do item to a done item, changing the done data corresponding to the done item to a read-only state; if it is determined based on the item type of the to-do item that the next to-do item will be triggered after the to-do item is successfully executed, determining and displaying the next executor of the next to-do item based on the to-do data, wherein the to-do data includes the item type and deadline; determining the priority of the to-do item based on the item type and deadline, so as to determine the display method of the to-do item in the to-do module based on the priority.

[0050] In one embodiment, after a to-do item is modified to a done item, the corresponding item data (done data) is changed to a read-only state. In other words, after the to-do item is completed, the done data can no longer be modified or deleted. In other embodiments, administrator rights can also be set, and only users with administrator rights can modify or delete the done data.

[0051] In one embodiment, the newly created item is set as a to-do item by default. Refer to Table 1 to determine whether the next to-do item will be triggered after the to-do item is successfully executed:

[0052] Table 1

[0053]

[0054] As can be seen from Table 1, different item types have different item definitions. Whether they will trigger the next to-do item is referred to Table 1 above, and will not be repeated here. It should be noted that this embodiment and Table 1 are only examples, and the item type, the item definition corresponding to the item type, and whether it will trigger the next to-do item can be modified according to actual needs, and this application does not limit this.

[0055] In one embodiment, the priority of the to-do items is determined according to the item type and deadline, and the display method of the to-do items in the to-do module is determined according to the priority, and the display method includes one or more of the display order, display color, display size, etc. Among them, the display order is determined by the sorting result obtained according to the priority sorting. If there are multiple to-do items with the same priority, the display order between the multiple to-do items is determined according to their corresponding deadlines. The display color is determined by the priority, for example, the display color of the first priority is red, the display color of the second priority is orange, and the display color of the third priority is yellow. The display size is determined by the priority, for example, the display size of the first priority is the largest, the display size of the second priority is the second largest (smaller than the display size of the first priority), and the display size of the third priority is the third largest (smaller than the display size of the second priority), etc.

[0056] In one embodiment, the importance of the to-do items can be determined according to the item type, and the urgency of the to-do items can be determined according to the deadline, so that the to-do items can be marked according to their importance and urgency, and the to-do items can be displayed more intuitively through marking.

[0057] In one embodiment of the present application, the remaining processing time of the to-do items is calculated based on the current time and the deadline of the to-do items; if the remaining processing time is less than or equal to the preset time threshold, a prompt message is generated based on the remaining processing time, and the target executor is prompted by the prompt message. The prompt message is used to remind the target executor to process the to-do items in a timely manner, effectively avoiding omissions or delays, and further improving the overall operational efficiency and response speed.

[0058] In this embodiment, if the remaining processing time is less than or equal to the first time threshold, a first prompt message is generated according to the remaining processing time, and the target executor is prompted by the first prompt message; if the remaining processing time is less than or equal to the second time threshold, wherein the second time threshold is less than the first time threshold, a second prompt message is generated according to the remaining processing time, and the target executor is prompted by the second prompt message; if the remaining processing time is less than or equal to the third time threshold, wherein the third time threshold is less than the second time threshold, a third prompt message is generated according to the remaining processing time, and the target executor is prompted by the third prompt message. Different prompt messages are sent to the target executor through different preset time thresholds to further avoid omissions or delays.

[0059] In one embodiment of the present application, an association request is received, the association request includes the current first to-do item of the target executor and the second to-do item of the associated executor to be associated; according to the association request, the first to-do data corresponding to the first to-do item is associated with the second to-do data corresponding to the second to-do item, so that the target executor can view the second to-do data, and / or the associated executor can view the first to-do data. By associating the to-do data of different executors, the real-time process of the to-do items can be better understood.

[0060] In one embodiment of the present application, the push status of all current matters is obtained. If the push status is push failure, in response to a re-push instruction for matters corresponding to the push failure, the matters corresponding to the push failure are re-pushed in batches.

[0061] In this embodiment, a re-push instruction is generated according to at least one of the following methods: receiving a re-push instruction input by the user; obtaining the last push time of the item corresponding to the push failure, and if the last push time is greater than the preset push time, a re-push instruction is generated.

[0062] It should be noted that the to-do data and other data obtained in the embodiments of the present application are obtained with the user's permission, or are actively submitted after the user's relevant instructions, or are uploaded by the user when using the corresponding application through the client, web page, etc. In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision, disclosure and application of the user's personal information involved are in compliance with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and do not violate public order and good customs.

[0063] This application can break down information silos and achieve seamless integration and data interoperability between different systems, thereby optimizing the bill processing process and improving overall operational efficiency and employee work experience.

[0064] Figure 3 is a block diagram of a document collaborative management system shown in an exemplary embodiment of the present application. The system can be applied to Figure 1 The implementation environment shown in the figure is specifically configured in the computer device 102. The system can also be applied to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the system is applicable.

[0065] like Figure 3 As shown, the exemplary document collaborative management system includes: a data collection module 310 , a task matching module 320 and a data synchronization module 330 .

[0066] Among them, the data collection module 310 is used to obtain the to-do data of the to-do items; the task allocation module 320 is used to respond to the allocation instructions of the to-do items and determine the target executor who executes the to-do items according to the allocation instructions; the data synchronization module 330 is used to synchronize the to-do data to the to-do module of the target executor, and the to-do module is used to display the to-do items and track the execution status of the to-do items.

[0067] The document collaborative management system is connected to each preset business system to centrally display and process to-do items. In one embodiment, the document collaborative management system is connected to the supplier e-commerce platform, the enterprise management system, the enterprise mall and the bill platform to obtain and / or send target data.

[0068] It should be noted that the document collaborative management system provided in the above embodiment and the document collaborative management method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here. In actual applications, the document collaborative management system provided in the above embodiment can distribute the above functions to different functional modules as needed, that is, divide the internal structure of the system into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0069] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the electronic device implements the document collaborative management method provided in the above-mentioned embodiments.

[0070] Figure 4 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 4 The computer system 400 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0071] like Figure 4As shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 402 or the program loaded from the storage part 408 to the random access memory (RAM) 403, such as executing the methods provided in the above-mentioned various embodiments. In the RAM 403, various programs and data required for system operation are also stored. The CPU 401, the ROM 402 and the RAM 403 are connected to each other through the bus 404. The input / output (I / O) interface 405 is also connected to the bus 404.

[0072] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, etc.; an output section 407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as needed so that a computer program read therefrom is installed into the storage section 408 as needed.

[0073] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 409, and / or installed from a removable medium 411. When the computer program is executed by a central processing unit (CPU) 401, various functions defined in the system of the present application are executed.

[0074] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0075] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0076] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0077] Another aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor of a computer, causes the computer to execute the document collaborative management method provided in the above-mentioned embodiments. The computer-readable storage medium may be included in the electronic device described in the above-mentioned embodiments, or may exist independently without being assembled into the electronic device.

[0078] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0079] Another aspect of the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the document collaborative management method provided in each of the above embodiments.

[0080] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0081] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0082] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A document collaborative management method, characterized in that: include: Get the to-do data of the to-do item; In response to the assignment instruction of the to-do item, determining a target executor for executing the to-do item according to the assignment instruction; The to-do data is synchronized to the to-do module of the target executor so that the target executor can process the to-do items. The to-do module is used to display the to-do items and track the execution status of the to-do items.

2. The document collaborative management method according to claim 1, characterized in that: After synchronizing the to-do data to the to-do module of the target executor, the method further includes: Obtaining the execution status of the to-do items; If the execution status is successful, the item status of the to-do item is changed to completed, the to-do item is changed to a completed item, and the completed item is displayed through the completed module of the target executor, wherein the to-do data includes the item status; If the execution status is execution failure, the target executor is prompted according to the execution status.

3. The document collaborative management method according to claim 2, characterized in that: Prompting the target executor according to the execution status includes: Obtaining management basis for the to-do items; Analyzing the cause of the execution failure according to the basic information of the to-do items and the management basis, wherein the to-do data includes the basic information; The target executor is prompted according to the failure reason.

4. The document collaborative management method according to claim 2, characterized in that: The method further comprises at least one of the following: After the to-do item is modified into a done item, the done data corresponding to the done item is changed to a read-only state; If it is determined according to the item type of the to-do item that the to-do item will trigger the next to-do item after successful execution, the next executor of the next to-do item is determined and displayed according to the to-do data, wherein the to-do data includes the item type and deadline; The priority of the to-do item is determined according to the item type and the deadline, so as to determine the display method of the to-do item in the to-do module according to the priority.

5. The document collaborative management method according to any one of claims 1 to 4, characterized in that: The allocation instructions are generated in the following way: Pre-set multiple role types and role permissions corresponding to each role type, wherein the role permissions include data viewing scope and / or data management scope; Setting a user role for each user based on the role type, wherein the user role includes at least one of the role types; The role authority corresponding to each of the users is determined according to the user roles, so as to generate the allocation instruction according to the role authority and the to-do data.

6. The document collaborative management method according to any one of claims 1 to 4, characterized in that: The method further comprises: Calculate the remaining processing time of the to-do item based on the current time and the deadline of the to-do item; If the remaining processing time is less than or equal to a preset time threshold, a deadline reminder message is generated according to the remaining processing time, and the target executor is reminded through the deadline reminder message.

7. The document collaborative management method according to any one of claims 1 to 4, characterized in that: The method further comprises: receiving an association request, the association request including a current first to-do item of the target executor and a second to-do item of an associated executor to be associated; According to the association request, an association relationship is established between the first to-do data corresponding to the first to-do item and the second to-do data corresponding to the second to-do item, so that the target executor can view the second to-do data, and / or the associated executor can view the first to-do data.

8. A document collaborative management system, characterized in that: include: The data collection module is used to obtain the to-do data of the to-do items; A task assignment module, configured to respond to an assignment instruction of the to-do item and determine a target executor for executing the to-do item according to the assignment instruction; A data synchronization module is used to synchronize the to-do data to the to-do module of the target executor, and the to-do module is used to display the to-do items and track the execution status of the to-do items.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the document collaborative management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the document collaborative management method according to any one of claims 1 to 7.

Images