Task processing method and device, computer equipment, storage medium and program product

Abstract

The embodiment of the invention provides a task processing method and device, computer equipment, a storage medium and a program product. The task processing method comprises the steps of displaying a session interface of a target social session in a social client, wherein the target social session communicates with a target document in a document service; displaying task information of a document task related to the target document in the session interface; and receiving an execution operation on the document task in the task information, and triggering the document service to write execution data corresponding to the execution operation in the target document. By adopting the embodiment of the invention, the execution efficiency of the document task can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a task processing method, a task processing apparatus, a computer device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] Currently, the execution flow of document-related tasks is very complex. Specifically, the document needs to be sent to each object to perform the document task, and the object needs to open the document and execute the task at the corresponding location within the document; for example, if the document is a table and the task is to fill in information in the table, the object needs to open the table and fill in the information in the corresponding cell. It's easy to see that the complex execution flow of document tasks currently leads to low execution efficiency. Therefore, how to improve the execution efficiency of document tasks has become a current research hotspot. Summary of the Invention

[0003] This application provides a task processing method, apparatus, computer equipment, storage medium, and program product that can improve the execution efficiency of document tasks.

[0004] On one hand, embodiments of this application provide a task processing method, which includes:

[0005] Displays the conversation interface of the target social conversation in the social client, and the target social conversation communicates with the target document in the document service;

[0006] Display task information for document tasks related to the target document in the session interface;

[0007] The task information receives the execution operation for the document task, triggering the document service to write the execution data corresponding to the execution operation into the target document.

[0008] Accordingly, embodiments of this application provide a task processing apparatus, which includes:

[0009] The display unit is used to display the session interface of the target social session in the social client, and the target social session communicates with the target document in the document service;

[0010] The display unit is also used to display task information of document tasks related to the target document in the session interface;

[0011] The processing unit is used to receive the execution operation for the document task in the task information;

[0012] The display unit is also used to trigger the document service to write the execution data corresponding to the execution operation into the target document.

[0013] In one implementation, the task information includes the task content of the document task and the execution area of ​​the document task; the processing unit, when receiving the execution operation for the document task in the task information, specifically performs the following steps:

[0014] Receive execution operations for document tasks in the execution area.

[0015] In one implementation, the processing unit, when receiving an execution operation on a document task in the execution area, is specifically configured to perform any of the following:

[0016] The execution area includes the execution button for the document task, and receives button trigger operations for the execution button in the execution area;

[0017] The execution area is the content input area, where content input operations are received.

[0018] The execution area is the content upload area, where content upload operations are received.

[0019] In one implementation, the display unit, when writing execution data corresponding to the execution operation into the target document, specifically performs the following steps:

[0020] Write the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document.

[0021] In one implementation, the document task is configured with the target execution flow type, execution fields, and execution field values ​​for the target document after the document task is executed; the display unit, used to write the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document, is specifically used to perform the following steps:

[0022] Write the execution field value into the cell corresponding to the execution field in the target document, according to the target execution flow type.

[0023] In one implementation, the display unit, used to write the execution field value into the cell corresponding to the execution field in the target document according to the target execution flow type, specifically performs the following steps:

[0024] If the target execution process type is record modification, then modify the field value in the cell corresponding to the execution field in the target document to the execution field value;

[0025] If the target execution process type is "new record", then add the execution field to the target document and add the execution field value to the cell corresponding to the execution field.

[0026] In one implementation, the cell corresponding to the document task includes any of the following:

[0027] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The document task is also configured with the task triggering conditions. The cell corresponding to the document task is determined by the row of the target cell in the target document that meets the task triggering conditions and the column of the execution field.

[0028] The document task is configured to specify the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The target cell of the target document is added with a conversation card of the target social conversation. The cell corresponding to the document task is determined based on the row where the target cell is located and the column where the execution field is located.

[0029] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed; the cell corresponding to the document task is a cell added at the end of the column where the execution field is located.

[0030] In one implementation, the target social session is a group social session; the display unit, used to write execution data corresponding to the execution operation into the target document, is specifically used to execute any of the following:

[0031] Write the execution data corresponding to each task execution member in the target social session into the target document;

[0032] The execution data corresponding to the next task execution member is used in the target document, overwriting the execution data corresponding to the previous task execution member.

[0033] In one implementation, a conversation card for the target social conversation is added to the target document; the display unit is also used to perform the following steps:

[0034] After the target social conversation and the target document are interconnected, the interconnection status information is displayed in response to the trigger operation of the conversation card;

[0035] Interoperability status information is used to indicate that the document service supports sending task information to the target social session.

[0036] In one implementation, a conversation card for the target social conversation is added to the target document; the display unit is also used to perform the following steps:

[0037] After receiving the execution operation for the document task in the task information, the document service is triggered to display the task execution notification in the session card;

[0038] The task execution notification indicates that the document task has been executed by the target social session.

[0039] In one implementation, a conversation card for the target social conversation is added to the target document; the display unit is also used to perform the following steps:

[0040] After receiving the execution operation for the document task in the task information, in response to the trigger operation of the conversation card, the task execution record of the target social conversation is displayed;

[0041] The task execution record of the target social session includes the task execution record of the session members who have performed document tasks in the target social session.

[0042] In one implementation, the task execution record of the target social session includes a jump control; a display unit, which is also used to perform the following steps:

[0043] In response to a triggering operation on the jump control, jump to the cell location where the execution data is written in the target document for display.

[0044] On the one hand, embodiments of this application provide another task processing method, which includes:

[0045] The document service interface is displayed, and the target document in the document service can communicate with the target social conversation in the social client.

[0046] Send document tasks related to the target document to the target social conversation;

[0047] In response to the execution operation of a document task in the target social session, the execution data corresponding to the execution operation is written into the target document.

[0048] Accordingly, embodiments of this application provide another task processing apparatus, which includes:

[0049] The display unit is used to display the service interface of the document service, and the target document in the document service can communicate with the target social conversation in the social client.

[0050] The processing unit is used to send document tasks related to the target document to the target social session;

[0051] The display unit is also used to write execution data corresponding to the execution operation into the target document in response to the execution operation of the document task in the target social session.

[0052] In one implementation, the display unit is also used to perform the following steps:

[0053] Configure document tasks related to the target document for the target social conversation.

[0054] In one implementation, the display unit, when configuring document tasks related to the target document for a target social session, specifically performs the following steps:

[0055] Configure the target task execution method for the target social session in the social client;

[0056] Configure the document service's document execution flow for the target document under the target task execution mode.

[0057] In one implementation, the display unit, used to configure the document service's document execution flow for the target document under the target task execution mode, specifically performs the following steps:

[0058] Configure the target execution flow type for the target document under the target task execution mode;

[0059] Configure the execution fields and their values ​​under the target execution process type.

[0060] In one implementation, the display unit, when configuring document tasks related to the target document for the target social session, is also used to perform at least one of the following:

[0061] Configure how the document task is sent to the social client;

[0062] Configure the target social conversation as the execution object for the document task;

[0063] Configure the task content of the document task;

[0064] Configure the document that communicates with the target social conversation as the target document;

[0065] Configure the task triggering conditions for the document task.

[0066] In one implementation, the target task execution method includes any of the following: button method, content input method, and content upload method;

[0067] The button method refers to the way document tasks are executed in social clients by triggering an action on an action button.

[0068] Content input method refers to the way document tasks are performed by executing content input operations in social clients;

[0069] Content upload refers to the method of performing document tasks by executing content upload operations in social clients.

[0070] Accordingly, embodiments of this application provide a computer device, which includes:

[0071] A processor is a tool for implementing computer programs.

[0072] A computer-readable storage medium storing a computer program adapted to be loaded by a processor and executed by the above-described task processing method.

[0073] Accordingly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when read and executed by the processor of a computer device, causes the computer device to perform the aforementioned task processing method.

[0074] Accordingly, this application provides a computer program product comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the aforementioned task processing method.

[0075] In this embodiment, after the target social session in the social client and the target document in the document service communicate with each other, document tasks related to the target document can be sent to the target social session. In response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation can be written into the target document. Therefore, document tasks can be executed in the target social session, meaning they can be executed in the social client. Furthermore, after executing a document task in the social client, the execution data of the document task can be automatically written to the target document without needing to open the target document to execute the document task. This simplifies the document task execution process and improves the execution efficiency of the document task. Attached Figure Description

[0076] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0077] Figure 1 This is a schematic diagram illustrating the relationship between a social client and a document service provided in an embodiment of this application;

[0078] Figure 2 This is a schematic diagram illustrating the relationship between another social client and document service provided in an embodiment of this application;

[0079] Figure 3 This is a schematic diagram of the architecture of a task processing system provided in an embodiment of this application;

[0080] Figure 4 This is a flowchart illustrating a task processing method provided in an embodiment of this application;

[0081] Figure 5 This is a schematic diagram of an interface for communicating prompts provided in an embodiment of this application;

[0082] Figure 6 This is a schematic diagram of an interface for displaying document tasks provided in an embodiment of this application;

[0083] Figure 7 This is a schematic diagram of another interface for displaying document tasks provided in an embodiment of this application;

[0084] Figure 8 This is a schematic diagram illustrating an execution operation provided in an embodiment of this application;

[0085] Figure 9 This is a schematic diagram illustrating another execution operation provided in an embodiment of this application;

[0086] Figure 10 This is a schematic diagram illustrating another execution operation provided in an embodiment of this application;

[0087] Figure 11 This is a flowchart illustrating another task processing method provided in an embodiment of this application;

[0088] Figure 12a This is a schematic diagram of a document task creation interface provided in an embodiment of this application;

[0089] Figure 12b This is a schematic diagram of a document task configuration interface provided in an embodiment of this application;

[0090] Figure 13 This is a schematic diagram of another document task configuration interface provided in an embodiment of this application;

[0091] Figure 14 This is a schematic diagram of another document task configuration interface provided in an embodiment of this application;

[0092] Figure 15 This is a schematic diagram illustrating the writing of execution data into a cell according to an embodiment of this application;

[0093] Figure 16 This is a schematic diagram of another execution data being written to a cell according to an embodiment of this application;

[0094] Figure 17 This is another schematic diagram of writing execution data into a cell provided in an embodiment of this application;

[0095] Figure 18 This is a schematic diagram illustrating a method for writing execution data according to an embodiment of this application;

[0096] Figure 19 This is a schematic diagram illustrating another method of writing execution data provided in an embodiment of this application;

[0097] Figure 20 This is a schematic diagram of the session card state before session document interoperability provided in an embodiment of this application;

[0098] Figure 21 This is a schematic diagram of the session card status after session document interoperability provided in an embodiment of this application;

[0099] Figure 22 This is a schematic diagram of the session card state after a document task is executed, provided in an embodiment of this application.

[0100] Figure 23a This is a schematic diagram of a task execution record viewing interface provided in an embodiment of this application;

[0101] Figure 23b This is a schematic diagram of an interface for viewing execution data by jumping through task execution records, provided in an embodiment of this application.

[0102] Figure 24a This is a schematic diagram illustrating a method for viewing task execution notifications and task execution records provided in an embodiment of this application;

[0103] Figure 24b This is a schematic diagram illustrating another way to view task execution notifications and task execution records provided in an embodiment of this application;

[0104] Figure 25 This is a schematic diagram of the technical flow of a task processing method provided in an embodiment of this application;

[0105] Figure 26 This is a schematic diagram of the structure of a task processing device provided in an embodiment of this application;

[0106] Figure 27 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0107] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0108] To better understand the technical solutions provided in the embodiments of this application, the technical terms involved in the embodiments of this application will be introduced first:

[0109] I. Social Media Clients:

[0110] Social clients, also known as IM (Instant Message) clients, are clients that enable real-time online communication over the internet. Real-time online communication means that social clients can send and receive internet messages instantly.

[0111] II. Social Conversation:

[0112] Social conversations refer to real-time online communication within a social networking client. Social conversations can include group social conversations or individual social conversations. Group social conversations, also known as group chats, refer to real-time online communication between two or more social individuals within a social networking client; the participants in the conversation are called conversation members. Individual social conversations, also known as one-on-one chats, refer to real-time online communication between two social individuals within a social networking client.

[0113] III. Document services, documents, and document tasks:

[0114] Document services refer to tools used for document operations, which may include at least one of the following: creating documents, editing documents, saving documents, creating document tasks, and executing document tasks, etc. A document refers to a tool within a document service used to display document data and interact with it. Document services can support document operations on various document types; for example, supported document types may include local Word documents, online Word documents, local spreadsheet documents, online spreadsheet documents, and smart spreadsheet documents, etc. In this embodiment, a document may be, for example, a smart spreadsheet document. A smart spreadsheet document refers to a new type of database spreadsheet, distinct from traditional Excel (i.e., local spreadsheet documents) and online spreadsheets, possessing rich column types and multi-dimensional view displays.

[0115] Document services serve as a medium for linking (or interoperating) documents with social conversations in social clients. Interoperability refers to the bidirectional data transmission and interaction between documents and social conversations. Document services can push document tasks to social conversations, and they can also feed back execution data of document tasks performed by conversation members in social conversations to the document (i.e., write it to the document).

[0116] A document task refers to a task that needs to be performed within a document. In this embodiment, a document task can be configured as an automated process, which is executed by a document service. The automated process means that when a configured trigger condition is met, the document task is automatically sent to a configured social session. After the document task is executed in the social session, the execution data can be written into the document according to the configured document execution flow.

[0117] Based on the above description of technical terms, this application provides a task processing method, which is a technical solution for interoperability between documents in a document service and social conversations in a social client. After interoperability, document tasks configured in an automated process can be sent to the corresponding social conversations via the document service. Conversation members in the social conversation can interact with the task information of the document tasks in the social conversation to execute the document tasks. The ideas during the execution of the document tasks can be converted into data (i.e., execution data) and written into the document. Furthermore, the task processing method provided by this application can also display the interoperability status information between the document and the social conversation, as well as the task execution records of the conversation members in the social conversation, in the conversation card of the social conversation within the document. Users can also quickly jump to the location where the execution data is written in the document through the task execution records.

[0118] Based on this task processing method, regarding the execution efficiency of document tasks, document tasks can be executed within social clients. Furthermore, after execution within a social client, the execution data is automatically written to the document without requiring the document to be opened, simplifying the execution process and thus improving efficiency. Regarding the accuracy of the document task process, the automated workflow allows for accurate and timely delivery of document tasks to social conversations. In terms of the user experience, using document services as a medium, data from conversation members can be conveniently and quickly collected directly within social conversations, eliminating the need for members to open and fill out documents. This simplifies the execution process and enhances the user experience. Additionally, conversation cards within the document can indicate new data being written, and clicking these cards displays the task execution record, providing prompts and documentation for the task's execution. Users can also quickly jump to the location where the data is written to the document, further improving the user experience.

[0119] It should be noted that the collection and processing of relevant data in this application embodiment (e.g., the collection and processing of execution data of session members performing document tasks) should strictly comply with the requirements of relevant laws and regulations when applied in practice, obtain the informed consent or separate consent of the personal information subject (or have a legal basis), and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0120] Next, we will introduce the entity responsible for executing the task processing method.

[0121] In this embodiment, the task processing method can be executed by a computer device, such as a terminal. The computer device may run a social client and a document service. The relationship between the social client and the document service on the computer device can include any of the following: A first relationship is as follows... Figure 1 As shown, the document service can be integrated into social clients. Integration means that the document service is integrated into the social client as a functional module; the second relationship is as follows... Figure 2 As shown, the document service is a separate client. In other words, the document service and the social client can be two separate clients. The document service and the social client are linked for login. Linked login means that the document service uses the social client for authorization login.

[0122] Furthermore, the terminal executing the task processing method can belong to, for example, Figure 3 The task processing system shown may include a terminal 301 and a backend server 302. A direct communication connection can be established between the terminal 301 and the backend server 302 via wired communication, or an indirect communication connection can be established between the terminal 301 and the backend server 302 via wireless communication.

[0123] Terminal 301 can run a social client and a document service. The relationship between the social client and the document service is as described above. Figure 1 or Figure 2As shown, the backend server 302 can be used to provide backend services for social clients and document services. In this embodiment, the type of client is not limited; the client can include any of the following: applications, mini-programs, and web (World Wide Web) applications, etc. The terminal 301 can be a smartphone, tablet, laptop, desktop computer, smart voice interaction device, smartwatch, in-vehicle terminal, smart home appliance, aircraft, etc., but is not limited to these. The backend server 302 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, as described herein.

[0124] In the task processing system, the task processing flow may include: a document service running in terminal 301 can be used to configure document tasks related to a target document. The execution object of the document task is the target social session in the social client. After configuration, the target document and the target social session communicate with each other. The document task is configured as an automated process. After the document service running in terminal 301 submits the automated process, the automated process can be stored in the database by the backend server 302. The backend server 302 can determine whether the task triggering condition for sending the document task in the automated process is met. If it is met, the backend server 302 can use the document service running in terminal 301 as a medium to send the document task to the social client running in terminal 301. The social client running in terminal 301 can display the task information of the document task in the session interface of the target social session. The social client running in terminal 301 can receive the execution operation for the document task in the task information and send the execution operation to the backend server 302. The backend server 302 can write the execution data to the target document at the database level according to the execution data corresponding to the execution operation in the automated process. After the target document is written, the backend server 302 can send the document data of the target document after the execution data is written to the terminal 301. The document service in the terminal 301 can present the target document with the execution data written, and the effect of writing the execution data in the target document is presented in the document service in the terminal 301.

[0125] It is understood that the task processing system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0126] The task processing method provided in the embodiments of this application will be described below from a visualization perspective.

[0127] This application provides a task processing method that describes the execution process of a document task on a social client side, including: the display method of the document task in the social client, and the execution operation of the document task in the social client. This task processing method can be executed by a terminal, which can be running a social client and a document service. Figure 4 As shown, the task processing method may include, but is not limited to, the following steps S401-S403:

[0128] S401, Displays the session interface of the target social session in the social client, where the target social session communicates with the target document in the document service.

[0129] In step S401, the session interface of the target social session refers to the interface used by session members in the social client to conduct social conversations. Interoperability between the target social session and the target document in the document service means that the target social session has been configured with document tasks related to the target document; that is, after configuring document tasks related to the target document for the target social session, the target social session and the target document can communicate with each other.

[0130] After the target social conversation and the target document are interconnected, an interconnection prompt message can be displayed in the conversation interface of the target social conversation. This prompt message indicates that the target social conversation and the document service are interconnected. For example... Figure 5 As shown, in the conversation interface 50 of the target social conversation, a first communication prompt message 502 is displayed in the conversation message display area 501 (for example, Figure 5 In the context of the chat, if you add the "Smart Table" application to the group chat, a second communication prompt message 504 will be displayed in the conversation management area 503 (for example, ...). Figure 5(The smart table is added as an application for sending messages). The conversation message display area 501 refers to the area within the conversation interface 50 of the target social conversation used to display the conversation messages of the target social conversation; the conversation management area 503 refers to the area within the conversation interface 50 of the target social conversation used to manage the target social conversation. This management may include, for example, managing the conversation members of the target social conversation in the conversation management area 503, or managing the applications that send messages to the target social conversation.

[0131] S402, Display task information for document tasks related to the target document in the session interface.

[0132] In step S402, the document task can be configured with task triggering conditions. When the task triggering conditions are met, the document task can be automatically sent to the target social session. After being sent to the target social session, the task information of the document task can be displayed in the session interface of the target social session. The task information refers to the presentation form of the document task in the social client.

[0133] like Figure 6 As shown, if the interface currently presented by the social client is the conversation interface 50 of the target social conversation, then after receiving the document task, the task information 505 of the document task can be displayed in the conversation message display area 501 of the conversation interface 50 of the target social conversation. In other words, the task information 505 of the document task can be displayed in the form of a conversation message, specifically in the form of a message card.

[0134] like Figure 7 As shown, if the interface currently displayed by the social client is not the conversation interface 50 of the target social conversation, but the conversation list interface 51 (the conversation list interface 51 refers to the interface in the social client used for social conversation management, and the conversation list interface 51 may include one or more conversation management items for social conversations), then after receiving the document task, a task prompt 512 for the document task can be displayed in the conversation management item 511 of the target social conversation in the conversation list interface 51 (for example, the task prompt 512 may include...). Figure 7 The message point prompt 5121 and message content prompt 5122 are specified in the document. Message content prompt 5122 may include the task source of the document task (the task source can be the name of the document service, for example, ...). Figure 7 In the context of smart tables and document task details (e.g., smart tables) and document task details, Figure 7 The task title in the text is: Activity Collection). In this case, if the session management item 511 of the target social session is triggered, the session interface 50 of the target social session can be displayed, and the task information 505 of the document task can be displayed in the session interface 50 of the target social session.

[0135] S403: Receive the execution operation for the document task in the task information, and trigger the document service to write the execution data corresponding to the execution operation into the target document.

[0136] In step S403, session members of the target social session can execute document tasks within the task information, thereby allowing the social client to receive execution operations on the document tasks within the task information. Specifically, the task information may include the task content of the document task and the execution area of ​​the document task, allowing the client to receive execution operations on the document task within the execution area.

[0137] The type of operation performed is related to the task execution method configured for the document task. The task execution method configured for the document task can include any of the following: button method, content input method, and content upload method; correspondingly, the operation performed can include any of the following: button-triggered operation, content input operation, and content upload operation. The different types of operations are described below:

[0138] ① Button-triggered operation: The execution area can include the execution button for the document task, and can receive button-triggered operations on the execution button within the execution area. For example... Figure 8 As shown, the task information 505 of the document task may include the task content 506 of the document task (for example, the task content 506 may include...). Figure 8 The task title ("Activity Collection") and task details ("Whether to Participate") and execution area 507, which may include an execution button 508 (e.g., Figure 8 The "Yes" and "No" buttons in the execution area 507 can receive button trigger operations on the execution button 508 (e.g., clicking the "Yes" button or clicking the "No" button) to execute the document task.

[0139] ② Content input operation: The execution area can be a content upload area, where content upload operations can be received. For example... Figure 9 As shown, the task information 505 of the document task may include the task content 506 of the document task (for example, the task content 506 may include...). Figure 9 The task title ("Activity Collection") and task details ("Participation Status") are in the code, along with execution area 507. Execution area 507 is the content input area, where you can enter the content used to perform the document task (e.g., ...). Figure 9 Enter "Yes" to indicate your willingness to participate in the activity, and submit the input to perform the document task.

[0140] ③ Content upload operation: The execution area can be a content upload area, and content upload operations can be received within the execution area. For example... Figure 10As shown, the task information 505 of the document task may include the task content 506 of the document task (for example, the task content 506 may include...). Figure 10 The task title is "Activity Collection," and the task details are "Collect images of entries." The task also includes an execution area (507), where you can upload files for the document task, such as images. Submit the uploaded content to complete the document task.

[0141] Based on the above description of task execution methods and operations, it can be seen that the embodiments of this application can configure different task execution methods for document tasks. Correspondingly, session members in a social conversation can execute document tasks through different execution operations. Therefore, different document tasks can be configured with task execution methods that are more adaptable and easier to execute, which is beneficial for session members in a social conversation to execute document tasks more conveniently and quickly.

[0142] In step S404, after receiving the execution operation for the document task in the task information, the social client can trigger the document service to write the execution data corresponding to the execution operation into the target document. This execution data can be configured during the document task configuration process. Specifically, the document task can be configured with execution field values ​​for the target document after the document task is executed. The execution data refers to the configured execution field values. In other words, after receiving the execution operation for the document task in the task information, the social client can trigger the document service to write the execution field values ​​into the target document. For example, in the button method, the "Yes" button is configured with the execution field value "Yes". If the button trigger operation is clicking the "Yes" button, the execution field value "Yes" can be written into the target document. Similarly, in the content input method, if the configured execution field value is the input content, then after performing the content input operation, the input content can be written into the target document. Furthermore, in the content upload method, if the configured execution field value is the uploaded file, then after performing the content upload operation, the uploaded file can be written into the target document.

[0143] Next, we will describe how the social client triggers the document service in step S404. As described above, the relationship between the social client and the document service can include an access relationship and an authorization login relationship. In the access relationship, the document service is accessed by the social client. The social client triggering the document service means that the social client calls the accessed document service to write the execution data corresponding to the execution operation into the target document. The target document is displayed in both the document service and the social client; that is, the target document is displayed in the document service within the social client. In the authorization login relationship, the document service can be authorized by the social client. The social client triggering the document service means that the social client can launch the document service, and the document service writes the execution data corresponding to the execution operation into the target document. Here, "launching" means changing the running state of the document service from "not running" to "running." The target document is displayed in the document service but not in the social client; that is, the target document is displayed in the separate document service.

[0144] In this embodiment, document tasks can be executed within a social client. After execution, the execution data is automatically written to the target document without needing to open the target document, thus simplifying the execution process and improving efficiency. Furthermore, in this embodiment, document tasks can be executed within a social session using different types of operations. The type of operation is related to the task execution method configured for the document task. Therefore, this embodiment allows for configuring more adaptable and efficient task execution methods for different document tasks, facilitating more convenient and faster execution within social sessions and further improving execution efficiency.

[0145] This application provides a task processing method, which describes the document task configuration process on the document service side. This task processing method can be executed by a terminal, which may be running a social client and a document service. Figure 11 As shown, the task processing method may include, but is not limited to, the following steps S1101-S1103:

[0146] S1101, Display the service interface of the document service, where the target document in the document service and the target social conversation in the social client can communicate with each other.

[0147] In step S1101, the service interface of the document service can be the interface used for document editing within the document service. Interoperability between the target social session and the target document in the document service means that the target social session is configured with document tasks related to the target document; that is, after configuring document tasks related to the target document for the target social session, the target social session and the target document can communicate with each other.

[0148] Configuring document tasks related to the target document for the target social session may include at least one of the following: ① Configuring task triggering conditions for the document task, which can be automatically sent when the triggering conditions are met; ② Configuring the sending method of the document task to the social client; ③ Configuring the target social session as the execution object of the document task; ④ Configuring the task content of the document task, which may include, for example, a task title and detailed task content; ⑤ Configuring the target task execution method for the target social session in the social client; ⑥ Configuring the document execution flow of the document service for the target document under the target task execution method; ⑦ Configuring documents that communicate with the target social session as the target document.

[0149] In configuring the document task described above, for step ⑤, there can be multiple task execution methods. The target task execution method can be any of the following: button method, content input method, and content upload method. Specifically, the button method refers to executing the document task by triggering an action on the execution button within the social client; the content input method refers to executing the document task by performing a content input action within the social client; and the content upload method refers to executing the document task by performing a content upload action within the social client.

[0150] In the above document task configuration process, for ⑥, the document execution process refers to the process of writing data into the target document. Configuring the document service's document execution process for the target document under the target task execution mode can include: configuring the target execution process type for the target document under the target task execution mode; configuring the execution fields and execution field values ​​under the target execution process type.

[0151] The execution flow type refers to the type of process in which data is written to the target document. It can be understood as the method of writing data to the target document. Multiple execution flow types are possible, and the target execution flow type can be any of them. For example, the execution flow type can include modifying a record or adding a record. Modifying a record means modifying existing data in the target document using configured data, while adding a record means adding configured data to the target document. The execution field refers to the field in the target document where data is written. Fields are columns in the document, and execution fields are used to determine the location where data is written in the target document. The execution field value refers to the data written to the target document. For example, for the "modify record" execution flow type, the configured execution field value can be used to modify the original value of the configured execution field in the target document; similarly, for the "add record" execution flow type, a configured execution field can be added to the target document, and a configured field value can be added to the execution field.

[0152] For example, such as Figure 12a As shown, the service interface 120 of the document service may include a document task configuration control 1201 (for example, Figure 12a If the document task configuration control 1201 is triggered, the document task configuration list 1202 can be displayed. Existing document tasks can be edited in the document task configuration list 1202, or new document tasks can be created in the document task configuration list. In this embodiment, taking a newly created document task related to the target document as an example, the document task creation control 1203 in the document task configuration list 1202 is triggered (e.g., ...). Figure 12a The control named "New Process" can display the document task configuration interface 1204, where document tasks related to the target document can be configured for the target social conversation.

[0153] See also Figure 12b In the document task configuration interface 1204, the task triggering conditions for the document task are configured, for example, Figure 12b The task execution condition is that a new record is added, specifically when a new record is added to "Smart Table 1", and the "Group Chat" field (in the document service, each column has a specific type when describing data; the "Group Chat" field refers to the type used to describe group chat information) is not empty. In the document task configuration interface 1204, the document task is configured to send messages to social clients in the form of social conversation messages (e.g., ...). Figure 12b (Group messages in the document). In the document task configuration interface 1204, the execution object of the document task is configured as the target social session (e.g., group messages in the document). Figure 12b (Sent to the target social conversation). The task content of the document task is configured in the document task configuration interface, for example, Figure 12b The task title for the Chinese document task is "Activity Collection," and the task details are "Participation Status." In the document task configuration interface 1204, the task execution method is configured as a button, with two buttons: "Yes" and "No." For the "No" button, the button title is "No," the execution flow type is "Modification Record," the execution field under "Modification Record" is "Participation Intention," and the value of the execution field under "Modification Record" is "No." In other words, if the execution operation for the document task in the target social conversation is a button trigger operation on the "No" button, then the value of the "Participation Intention" field in the target document can be modified to "No."

[0154] As can be seen from the document task configuration process described above, different task execution methods can be configured for document tasks. This allows for the configuration of task execution methods that are more adaptable to different document tasks and facilitate their execution, thus promoting faster execution of document tasks. Furthermore, the process of writing data into the target document after the document task is executed can also be configured. This makes the data writing process for the target document more standardized, better meeting the requirements of automated data writing and improving the accuracy of document data writing.

[0155] Optionally, in the above document task configuration process, there is also an alternative to ⑥. Specifically, the alternative is to configure the execution flow of the social client under the target task execution mode. That is, the target task execution mode for executing document tasks in the social client can be configured for the target social session, and the execution flow of the social client under the target task execution mode can be configured. This execution flow may include a link jump process.

[0156] For example, such as Figure 13 As shown, in the document task configuration interface 1204, the task execution method for the document task is configured as a button method, with two buttons configured: "Yes" and "No". For the "No" button, the button title is configured as "No", the execution flow type is configured as "Button Link", and a jump link is configured (for example, ...). Figure 13 (The "https: / / www......" in the URL), the rest of the configuration operations are the same as... Figure 12b The same applies. In this case, if the action performed on the document task in the target social session is a button trigger on the "No" button, the social client can execute a link redirection to the configured link. Based on the configuration process of this document task, it can be seen that the execution flow of the social client after the document task is executed can be configured. This allows the social client to execute according to the configured execution flow after the document task is executed, enabling the post-processing flow after the document task to be automatically executed as required.

[0157] Optionally, in the configuration process of the above document task, for ⑦, the target document that communicates with the target social session can be configured when configuring the task triggering conditions, or it can be configured separately. These two cases are described below:

[0158] The first type involves a target document that interacts with the target social session, which can be configured when setting task trigger conditions. For example, in... Figure 12bIn this scenario, the task is triggered when a new record is added to "Smart Table 1" and the "Group Chat" field is not empty. In this case, the document used for communication is Smart Table 1; that is, the target document is Smart Table 1. Using the document configured in the task trigger condition as the target document for communication with the target social session satisfies the configuration requirement that the document in the task trigger condition and the document used for communication are the same document, simplifying the document task configuration process.

[0159] The second approach involves configuring the target document for interaction with the target social dialogue separately. This target document is independent of the document configured in the task triggering conditions and is also independent of whether a document is configured in the task triggering conditions. In this case, configuring the document service's document execution flow for the target document under the target task execution mode can include: configuring the target execution flow type for the target document under the target task execution mode, and configuring the execution document, execution fields, and execution field values ​​under the target execution flow type. The configured execution document is the target document that interacts with the target social dialogue. Figure 14 As shown, the document task configuration interface 1204 configures the document task execution method as a button, with two buttons: "Yes" and "No". For the "No" button, the button title is "No", the execution flow type is "Modification Record", the execution document under "Modification Record" is "Smart Table 2", the execution field is "Participation Intent", and the execution field value is "No". In other words, if the execution operation of the document task in the target social session is triggered by the "No" button, the field value under "Participation Intent" in Smart Table 2 can be modified to "No". In this mode, document configuration is not required in the task trigger condition, or the document configured in the task trigger condition can be a different document from the document used for communication in the target social session. This makes the configuration of the document used for communication more flexible, offers more options, and is not limited to the document configured in the task trigger condition, better meeting the configuration needs of complex document tasks.

[0160] It should be noted that the above document task configuration process is described using one execution field as an example. This embodiment does not limit the number of execution fields that can be configured; one or more execution fields can be configured. That is, in the execution operation process of modifying a record, the field values ​​of one or more execution fields can be modified; in the execution operation process of adding a new record, one or more execution fields and their respective field values ​​can be added. This makes the document task configuration more flexible and better meets the copying needs of complex document tasks.

[0161] S1102, Send the document task related to the target document to the target social session.

[0162] In step S1102, the document task related to the target document can be configured with task triggering conditions. When the task triggering conditions are met, the document task related to the target document can be automatically sent to the target social session. The document task is presented as task information in the session interface of the target social session, and the task information can be displayed as a session message in the session interface of the target social session.

[0163] S1103, in response to the execution operation of the document task in the target social session, write the execution data corresponding to the execution operation into the target document.

[0164] In step S1103, in response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation can be written into the target document. Specifically, the document task can be configured with execution field values ​​for the target document after the document task is executed. Execution data refers to the configured execution field values, which can be written into the target document in response to the execution operation of the document task in the target social session.

[0165] It should be noted that steps S1101-S1103 are executed by a document service. This document service can be an integrated document service within the social client. In other words, steps S1101-S1103 are executed by a document service within the social client, and all interfaces presented by the document service are displayed within the social client. Alternatively, steps S1101-S1103 can be executed by a separate document service.

[0166] In this embodiment, document tasks can be executed within a social client. After execution, the task's execution data is automatically written to the target document without needing to open the target document. This simplifies the execution process and improves efficiency. Furthermore, this embodiment allows for configuring more adaptable and efficient execution methods for different document tasks, facilitating faster and more convenient execution within social conversations and further enhancing efficiency. Additionally, this embodiment can configure the process of writing data to the target document after execution, making the data writing process more standardized and ensuring data is written according to the established procedure, thus improving data writing accuracy.

[0167] In the above Figure 4 and Figure 11In the illustrated embodiment, for steps S403 and S1103, the execution data corresponding to the execution operation can be written into the target document by the document service in the social client. Alternatively, the execution data corresponding to the execution operation can be written into the target document by a separate document service. The process of writing the execution data corresponding to the execution operation into the target document in steps S403 and S1103 is described in detail below:

[0168] Taking a table as an example, the execution data corresponding to the operation can be written into the cells of the target document. Specifically, the execution data corresponding to the operation can be written into the cells corresponding to the document task in the target document. Here, a cell refers to a rectangular area in the table used to store and display data. Each cell is typically identified by a unique row and column coordinate, meaning that each cell can be uniquely identified based on its row and column.

[0169] Furthermore, as mentioned above Figure 11 The described document task configuration process involves configuring the target execution flow type, execution fields, and execution field values ​​for the target document after the document task is executed. The target execution flow type defines how data is written to the target document, the execution fields define the location of the data within the target document, and the execution field values ​​define the data written to the target document (i.e., the execution data). In this case, execution field values ​​can be written to the cells corresponding to the execution fields in the target document, according to the target execution flow type.

[0170] The target execution process type can include modifying a record or adding a record. If the target execution process type is modifying a record, the field value in the cell corresponding to the execution field in the target document can be modified to the execution field value; if the target execution process type is adding a record, an execution field can be added to the target document, and an execution field value can be added to the cell corresponding to the execution field.

[0171] Next, we will introduce how to determine the cell corresponding to the document task (i.e., the cell corresponding to the execution field). The execution field defines the location in the target document where the execution data is written. Specifically, the location refers to the column. The cell can be uniquely determined by both the row and column; therefore, it is also necessary to determine the row where the execution data is written. The cell corresponding to the document task (i.e., the cell corresponding to the execution field) can include any of the following:

[0172] The first method involves configuring a trigger field in the task triggering conditions of a document task. This allows you to determine the cell corresponding to the document task based on the row where the cell that meets the task triggering conditions is located and the column where the execution field is located.

[0173] Specifically, the document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The document task is also configured with task triggering conditions. The cell corresponding to the document task is determined by the row of the target cell that meets the task triggering conditions (i.e., the target cell is the cell under the triggering field that meets the task triggering conditions) and the column of the execution field.

[0174] For example, according to Figure 12b The configured document task is triggered when a new record is added to "Smart Table 1" and the "Group Chat" field is not empty. For example... Figure 15 As shown, if content is added to the target cell 1501 corresponding to the "Group Chat" field (for example, ...), Figure 15 If the added content is a conversation card of the target social conversation, the document task can be sent to the target social conversation; if the document task is executed in the target social conversation (for example, the "No" button in the document task's task information is triggered by a conversation member in the target social conversation), the original field value in cell 1502 corresponding to the document task (for example, ...) can be returned to the target social conversation. Figure 15 The empty value in the text should be changed to the execution field value "No". The cell 1502 corresponding to the document task is determined based on the row "1" of the target cell 1501 that meets the task triggering conditions and the column where the execution field "Participation Intention" is located.

[0175] As can be seen, the method for determining the cell where the execution data is written is combined with the task triggering conditions. Based on the row where the cell that meets the task triggering conditions is located and the column where the configured execution field is located, the cell where the execution data is written can be quickly determined. Furthermore, typically, when using documents for data collection, the cell where the data is collected (i.e., the cell where the data is written) and the cell that meets the task triggering conditions have a certain relationship. This relationship can be that the two cells are in the same row. This allows the document task's execution data to be written to the appropriate position related to the task triggering conditions when such conditions exist, improving the rationality of data collection from the table.

[0176] The second approach involves adding a conversation card for the target social session to the target document. The cell corresponding to the document task can be determined based on the row where the conversation card for the target social session is added and the column where the execution field is located.

[0177] Specifically, the document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The target cell of the target document is added with the conversation card of the target social conversation. The cell corresponding to the document task is determined based on the row of the target cell and the column of the execution field.

[0178] For example, the document task is configured to execute via buttons, with two buttons: "Yes" and "No". For the "No" button, the button title is "No", the execution flow type is "Add Record", the execution field is "Participation Intent", and the execution field value is "No". Figure 16 As shown, content has been added to target cell 1501 corresponding to the "Group Chat" field (for example, Figure 16 The content added is the conversation card of the target social conversation. If the document task is executed in the target social conversation (for example, the "No" button in the document task information is triggered by a conversation member in the target social conversation), then a "Participation Intention" field can be added to the target document, and the execution field value "No" can be added to cell 1502 corresponding to the document task. Cell 1502 corresponding to the document task is determined by row "2" where the target cell 1501 containing the conversation card of the target social conversation is added and the column where the newly added execution field "Participation Intention" is located.

[0179] As can be seen, the method for determining the cell where the execution data is written is combined with the conversation card of the target social conversation. Based on the row where the cell containing the conversation card of the target social conversation is added and the column where the configured execution field is located, the cell where the execution data is written can be quickly determined. Furthermore, typically when using tables for data collection, the target social conversation is configured as the execution object of the document task, and the cell where the data is written is associated with the target social conversation. This method establishes a connection between the cell where the data is written and the cell containing the conversation card of the target social conversation. This connection can be that the two cells are in the same row. This allows the execution data of the document task to be written to the appropriate position related to the object card of the execution object when an object card of the document task exists, improving the rationality of table-based data collection.

[0180] The third method is to determine the cell corresponding to the document task based on the cell added at the end of the column where the execution field is located.

[0181] Specifically, the document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed; the cell corresponding to the document task is a cell added at the end of the column where the execution field is located.

[0182] For example, such as Figure 17 The column containing the "Participation Intention" field has three cells, and cell 1502, corresponding to the document task, is the fourth cell added at the end of the column containing the execution field. If the document task is executed within the target social session (for example, if the "No" button in the document task information is triggered by a member of the target social session), a cell can be added at the end of the column containing the execution field, and the execution field value "No" can be added to the added cell. It can be seen that this method of determining the cell where the execution data is written ensures that the original document's format is not destroyed; instead, data is written to the data by adding new cells to the original document.

[0183] Next, we will introduce the cases where the target social conversation is a group social conversation or a one-on-one social conversation.

[0184] When the target social session is a standalone social session, of the two session members participating in the standalone social session, one session member is the first object configuring the document task, and the other session member is the second object configured as the execution object of the document task. The document task is usually executed by the second object. In this case, the execution data corresponding to the second object (i.e., the configured execution object) in the target social session can be written into the target document.

[0185] When the target social session is a group social session, a document task can be executed by multiple session members within the target social session. These session members executing the document task can be called task execution members. In this case, execution data corresponding to each task execution member in the target social session can be written into the target document; that is, the execution field value corresponding to each task execution member can be written into the cell corresponding to the document task in the target document. For example... Figure 18 As shown, the target social session includes session member 1, session member 2, and session member 3. Session members 1 and 2 in the target social session executed document tasks. For example, session member 1 triggered the "Yes" button in the document task's task information, and session member 2 triggered the "No" button in the document task's task information. The cell corresponding to the document task (i.e., the cell where data is written) contains the execution field value "Yes" for session member 1 and the execution field value "No" for session member 2. In other words, in this method, the execution data corresponding to each task execution member in the target social session who executes the document task can be written into the target document. This method focuses on each task execution object that executes the document task.

[0186] Alternatively, the execution data corresponding to the later task execution member can be used in the target document to overwrite the execution data corresponding to the earlier task execution member. In other words, in the cell corresponding to the document task in the target document, the execution field value corresponding to the later task execution member can be used to overwrite the execution field value corresponding to the earlier task execution member. For example... Figure 19 As shown, the target social session includes session member 1, session member 2, and session member 3. Session member 1 executes the document task first. For example, session member 1 triggers the "Yes" button in the document task's task information, and the cell corresponding to the document task (i.e., the cell where data is written) is filled with the execution field value "Yes" corresponding to session member 1. Session member 2 executes the document task after session member 1. For example, session member 2 triggers the "No" button in the document task's task information after session member 1, and the cell corresponding to the document task replaces the execution field value "Yes" corresponding to session member 1 with the execution field value "No" corresponding to session member 2. In other words, in this method, the execution data finally written into the target document is the execution data corresponding to the last task execution member in the target social session who executes the document task. This method focuses on the target social session as a whole that executes the document task and on the final result of the document task being executed.

[0187] As can be seen, the embodiments of this application can configure document tasks related to the target document for individual social sessions, and write the execution data into the target document after the document task is executed by the individual social session; the embodiments of this application can also configure document tasks related to the target document for group social sessions, and write the execution data into the target document after the document task is executed by the group social session; this can expand the types of social sessions that can communicate with the target document.

[0188] It should be noted that the number of target social sessions can be one or more. That is, a target document can communicate with one or more target social sessions. If a document task related to the target document is executed by one or more target social sessions, execution data corresponding to one or more target social sessions can be written into the target document. For the case where there is only one target social session communicating with the target document, please refer to the above description of "the process of writing execution data corresponding to the execution operation into the target document," which will not be repeated here. For the case where there are multiple target social sessions communicating with the target document, execution data corresponding to each target social session executing the document task can be written into the cell corresponding to the document task in the target document. The writing method can include any of the following: Execution data corresponding to each target social session executing the document task can be written; or, the execution data corresponding to the next target social session executing the document task can be used to overwrite the execution data corresponding to the previous target social session. For example, if session member 1 in target social session 1 executes the document task first, and session member 2 in target social session 2 executes the document task later, then the execution data corresponding to session member 2 can overwrite the execution data corresponding to session member 1.

[0189] As can be seen, the embodiments of this application can configure the same document task related to the target document for one or more social sessions, and after the document task is executed, write the execution data corresponding to the social session that executed the document task into the target document, thereby increasing the number of social sessions that communicate with the target document.

[0190] In the above Figure 4 and Figure 11 In the illustrated embodiment, conversation cards for the target social conversation can be added to the target document. A conversation card is an element within the document that displays conversation information about the target social conversation. The display state of the conversation cards for the target social conversation can change before and after the target social conversation interacts with the target document; similarly, the display state of the conversation cards for the target social conversation can change before and after the target social conversation performs document tasks. The changes in the display state of the conversation cards for the target social conversation are described below.

[0191] (1) The display status of the conversation cards in the target social conversation before and after the target social conversation and the target document are interconnected:

[0192] Before the target social conversation and the target document are interconnected, the display status of the conversation cards in the target social conversation is as follows: Figure 20 As shown, in the document editing interface 200 of the target document, the field type can be set to social conversation (e.g., Figure 20In the cell of the "Group Chat" field, add a conversation card 2001 displaying the target social conversation. Before the target social conversation and the target document communicate, in response to the triggering operation of the conversation card 2001, the conversation information 2002 of the target social conversation can be displayed (e.g., Figure 20 The target social session's avatar and session name, as well as the target social session's session control 2003; if the target social session's session control 2003 is triggered, the social client can display the target social session's session interface.

[0193] After the target social conversation and the target document are interconnected, the display status of the conversation cards in the target social conversation will be as follows: Figure 21 As shown, the document editing interface 200 of the target document displays a conversation card 2001 for the target social session. After the target social session and the target document communicate, in response to the triggering operation of the conversation card 2001, the conversation information 2002 and the conversation control 2003 of the target social session can be displayed; communication status information 2004 can also be displayed, which can be used to indicate that the document service supports sending task information to the target social session (e.g., ...). Figure 21 (The "automated process can send messages to this group chat" in the text). Based on the communication status information, the communication status between the target social session and the target document can be visualized, making it easy to clearly and intuitively obtain the communication status between the target social session and the target document.

[0194] (2) The display status of the conversation cards in the target social conversation before and after the document task is performed:

[0195] Before performing document tasks in the target social session, the display state of the session cards in the target social session is as follows: Figure 20 As shown, this will not be repeated here. After the document task is executed in the target social session, that is, after receiving the execution operation for the document task in the task information, as... Figure 22 As shown, this can trigger the document service to display the task execution notification 2005 of session card 2001 (for example, Figure 22 The message point displayed in the upper left corner of the conversation card 2001 indicates that the document task has been executed by the target social conversation. Based on the task execution notification, the execution status of the document task can be visualized, making it easy to clearly and intuitively obtain information such as that the document task has been executed by the target social conversation, and that the document service has received the execution data and written it to the target document.

[0196] In addition, after executing the document task in the target social session, and after receiving the execution operation for the document task in the task information, such as... Figure 23aAs shown, in response to a trigger operation on the session card 2001, the task execution record 2006 of the target social session can be displayed. The task execution record 2006 of the target social session can include the task execution records of session members in the target social session who have performed document tasks, for example, Figure 23a In the task execution log, session member 1 modifies the document data of the target document, and session member 2 adds new document data to the target document. The task execution log can also include the task execution time. Through the task execution log, the execution operations of session members in the target social session on document tasks can be clearly and intuitively obtained, and mapped to the write operations performed on the target document.

[0197] Furthermore, session cards can also navigate to the location where the execution data is written in the target document. Specifically, for example... Figure 23b As shown, the task execution record 2006 of the target social session may include a jump control 2007. In response to a trigger operation on the jump control 2007, the user can jump to cell 1502 where the execution data is written in the target document for display. This method allows for quick viewing of the written execution data when reviewing the task execution record of the target social session, especially when the location where the execution data is written in the target document is far from the location of the task execution record in the target document, thus improving the efficiency of viewing the execution data.

[0198] exist Figure 23a and Figure 23b In this context, task execution notifications can be displayed in the conversation card of the target social session within the target document. Task execution records can be displayed by triggering the conversation card containing the task execution notification. In other words, both task execution notifications and task execution records are displayed within the document service. Optionally, task execution notifications and task execution records can also be displayed in the social client, and in the form of service assistant notifications or social conversation notifications.

[0199] Specifically, task execution notifications can be displayed in the form of service assistant notifications. In the case of document services integrated with social clients, the social client can include a service assistant for the document service. This service assistant can provide an interface for interacting with the document service; for example, it can be used to create or open documents already created within the document service. After the document task is executed in the target social session, i.e., after receiving the execution operation for the document task in the task information, such as... Figure 24a As shown, task execution notification 2005 can be displayed in the service assistant interface 240 (for example, task execution notification 2005 includes...). Figure 24aThe message point and notification content displayed in the upper left corner of the document interaction interface 2401 of the target document are "Document task has been executed, click to view". The document interaction interface 2401 of the target document can be used to open the target document in the document service. The task execution notification 2005 can indicate that the document task has been executed by the target social session.

[0200] Similarly, such as Figure 24a As shown, in response to a trigger operation on the document interaction interface 2401 of the target document containing the task execution notification 2005, the task execution record 2006 of the target social session can be displayed; or, in response to a trigger operation on the document interaction interface of the target document containing the task execution notification, the document editing interface of the target document can be displayed, and a trigger operation can be performed on the session card of the target social session in the document editing interface to display the task execution record of the target social session. Similarly, the task execution record of the target social session may include a jump control, and in response to a trigger operation on the jump control, it can jump to the cell position where the execution data is written in the target document for display. In this way, the document assistant notification in the social client can quickly inform that the document task has been executed, and the execution status of the document task can be visualized, making it easy to clearly and intuitively obtain information such as that the document task has been executed by the target social session and that the document service has received the execution data and written it to the target document.

[0201] Alternatively, task execution notifications can be displayed in the form of social conversation notifications. This occurs after the document task is executed in the target social conversation, i.e., after receiving the execution operation for the document task in the task information, such as... Figure 24b As shown, a task execution notification 2005 can be displayed in the conversation interface 50 of the target social session (e.g., Figure 24b The message "Document task has been executed, click to view" displayed in the conversation message display area 501, and the task execution notification 2005 can indicate that the document task has been executed by the target social conversation.

[0202] Similarly, such as Figure 24b As shown, in response to the triggering operation of task execution notification 2005, the task execution record 2006 of the target social session can be displayed. Similarly, the task execution record of the target social session may include a jump control, which, in response to the triggering operation of the jump control, can jump to the cell position where the execution data is written in the target document for display. In this way, one can quickly know that a document task has been executed through social session notifications in the social client, visualize the execution status of the document task, and clearly and intuitively obtain information such as that the document task has been executed by the target social session and that the document service has received the execution data and written it to the target document.

[0203] The task processing method provided in the embodiments of this application will be described below from a technical perspective.

[0204] based on Figure 3 The task processing system shown is, for example Figure 25 As shown, the task processing method technical process may include the following seven steps:

[0205] Step 1: Configure and save the document tasks for the automated workflow in the document service.

[0206] (1) Configuration components:

[0207] ① Configure the execution object of the task: You can choose to configure the target social session as the execution object of the document task, and you can add the document service to the target social session.

[0208] ② Configure the task content of the document task: You can edit the task content of the document task, which can include the task title and detailed task information.

[0209] ③ Configure the document execution flow for the target document after the document task is executed: You can configure the task execution method of the document task, the flow type under the execution task execution method, the execution field and execution field value under the execution flow type.

[0210] (2) Save the document task of the automated process:

[0211] After the document service is configured, it will call the backend server to perform storage operations and store the document tasks of the automated process in the database.

[0212] Step 2: The conversation card of the target social conversation displays the communication status between the target document and the target social conversation.

[0213] After the document service configuration is complete, adding a conversation card for the target social session to the target document will trigger the conversation card of the target social session, which will display the communication status between the target document and the target social session, i.e., communication status information (e.g., Figure 21 The "automated process can send messages to this group chat" in the text.

[0214] Step 3: The background server calculates and pushes document tasks.

[0215] (1) Calculate whether the task triggering conditions are met:

[0216] When a document task from an automated workflow submitted by a document service is received, if the document task is a type of document task sent via a conversational message in the target social session, the backend server can start a corresponding task instance.

[0217] (2) Document task push:

[0218] When the task triggering conditions are met, the task instance can obtain the configured document task, concatenate and organize the obtained content to form the document task information, and then push the document task information to the target social session in the social client through the document service.

[0219] Step 4: The social client displays the document task and allows interaction with the document task.

[0220] The presentation of document tasks sent by document services on social clients can include: task prompts in the conversation list interface and task information of document tasks displayed as message cards in the conversation interface.

[0221] (1) Task prompt:

[0222] When a social client receives a document task, it can display a task prompt in the conversation management section of the target social conversation in the conversation list interface. The task prompt can include a message point prompt and a message content prompt. The display format of the message content prompt can be, for example, "Task Source (e.g., the task source is a smart table): Task Details (e.g., the task details are the task title: Activity Collection)". If the task title cannot be fully displayed, it can be displayed in the form of an ellipsis.

[0223] (2) Message cards in the conversation interface:

[0224] Message cards can include:

[0225] ① Task content for document tasks: The task content can include the task title and detailed task information, which is configured in the document service.

[0226] ② Document Task Execution Area: The execution area receives execution operations for document tasks. The execution method for document tasks within the execution area is configured in the document service. For example, if the configured execution method is a button, an execution button for the document task can be displayed in the execution area. Members of the target social session can execute the document task by clicking the execution button. After a member of the target social session clicks the execution button to execute the document task, the social client can trigger the document service to send the execution operation to the backend server.

[0227] Step 5: The backend server performs document operations on the target document according to the configured document execution process and pushes the latest document data.

[0228] (1) The background server performs document operations:

[0229] The backend server receives an execution message from the document service. This message includes the document task's automation process identifier (automation process ID) and execution operation identifier (execution operation ID). The backend server parses the execution message to obtain the automation process identifier and execution operation identifier. Then, the backend server uses the automation process identifier to find the corresponding automation process and the execution operation identifier to find the corresponding document execution process. Based on the configured document execution process, the backend server performs a document write operation on the target document and writes the latest document data to the database.

[0230] (2) Push the latest document data:

[0231] Once the backend server successfully writes the data to the database, it pushes the latest document data of the target document to the document service for display using existing communication protocols (e.g., Web Socket, a full-duplex communication protocol).

[0232] Step Six: The document service displays the latest document data for the target document.

[0233] After receiving the latest document data of the target document pushed by the backend server through the communication protocol, the document service can execute collaborative capabilities to display the latest document data of the target document.

[0234] Step 7: Display task execution notifications and task execution records in the conversation card of the target social conversation in the document service.

[0235] For example, displaying task execution notifications and task execution records in a document service:

[0236] (1) Task execution notification:

[0237] After receiving the latest document data for the target document, the document service, in addition to displaying the latest document data (i.e., the document data after writing the execution data), can also display a task execution notification in the target social session's session card, indicating that there is a new message in the target social session (the new message indicates that the document task has been executed by the target social session). (For example, the task execution notification could be...) Figure 22 (The message point shown).

[0238] (2) Task execution record:

[0239] If a session card containing task execution notifications is triggered, the task execution history of the target social session can be displayed. This history can include the task execution records of session members who performed document tasks within the target social session. The task execution history may also include a jump button, which can be used to trigger the writing of the latest document data (i.e., execution data).

[0240] The methods of the embodiments of this application have been described in detail above. In order to facilitate better implementation of the above solutions of the embodiments of this application, the apparatus of the embodiments of this application is provided below.

[0241] Please see Figure 26 , Figure 26 This is a schematic diagram of the structure of a task processing device provided in an embodiment of this application. The task processing device can be installed in the computer device provided in the embodiment of this application. The computer device can be a terminal, and the terminal runs a social client and a document service. Figure 26 The apparatus shown may be a computer program running on a computer device, and this task processing apparatus may be used to perform some or all of the steps of the social client in the above method embodiments. Please see Figure 26 The task processing device may include the following units:

[0242] Display unit 2601 is used to display the session interface of the target social session in the social client, and the target social session is interconnected with the target document in the document service;

[0243] The display unit 2601 is also used to display task information of document tasks related to the target document in the session interface;

[0244] Processing unit 2602 is used to receive execution operations for document tasks in task information;

[0245] The display unit 2601 is also used to trigger the document service to write the execution data corresponding to the execution operation into the target document.

[0246] In one implementation, the task information includes the task content of the document task and the execution area of ​​the document task; the processing unit 2602, when receiving the execution operation for the document task in the task information, specifically performs the following steps:

[0247] Receive execution operations for document tasks in the execution area.

[0248] In one implementation, when the processing unit 2602 receives an execution operation on a document task in the execution area, it is specifically configured to execute any of the following:

[0249] The execution area includes the execution button for the document task, and receives button trigger operations for the execution button in the execution area;

[0250] The execution area is the content input area, where content input operations are received.

[0251] The execution area is the content upload area, where content upload operations are received.

[0252] In one implementation, the display unit 2601, when writing execution data corresponding to the execution operation into the target document, specifically performs the following steps:

[0253] Write the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document.

[0254] In one implementation, the document task is configured with the target execution flow type, execution fields, and execution field values ​​for the target document after the document task is executed; the display unit 2601 is used to write the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document, specifically to perform the following steps:

[0255] Write the execution field value into the cell corresponding to the execution field in the target document, according to the target execution flow type.

[0256] In one implementation, display unit 2601 is used to execute the following steps when writing the execution field value into the cell corresponding to the execution field in the target document according to the target execution flow type:

[0257] If the target execution process type is record modification, then modify the field value in the cell corresponding to the execution field in the target document to the execution field value;

[0258] If the target execution process type is "new record", then add the execution field to the target document and add the execution field value to the cell corresponding to the execution field.

[0259] In one implementation, the cell corresponding to the document task includes any of the following:

[0260] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The document task is also configured with the task triggering conditions. The cell corresponding to the document task is determined by the row of the target cell in the target document that meets the task triggering conditions and the column of the execution field.

[0261] The document task is configured to specify the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The target cell of the target document is added with a conversation card of the target social conversation. The cell corresponding to the document task is determined based on the row where the target cell is located and the column where the execution field is located.

[0262] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed; the cell corresponding to the document task is a cell added at the end of the column where the execution field is located.

[0263] In one implementation, the target social session is a group social session; the display unit 2601, when writing execution data corresponding to the execution operation into the target document, is specifically used to execute any of the following:

[0264] Write the execution data corresponding to each task execution member in the target social session into the target document;

[0265] The execution data corresponding to the next task execution member is used in the target document, overwriting the execution data corresponding to the previous task execution member.

[0266] In one implementation, a conversation card for the target social session is added to the target document; the display unit 2601 is also used to perform the following steps:

[0267] After the target social conversation and the target document are interconnected, the interconnection status information is displayed in response to the trigger operation of the conversation card;

[0268] Interoperability status information is used to indicate that the document service supports sending task information to the target social session.

[0269] In one implementation, a conversation card for the target social session is added to the target document; the display unit 2601 is also used to perform the following steps:

[0270] After receiving the execution operation for the document task in the task information, the document service is triggered to display the task execution notification in the session card;

[0271] The task execution notification indicates that the document task has been executed by the target social session.

[0272] In one implementation, a conversation card for the target social session is added to the target document; the display unit 2601 is also used to perform the following steps:

[0273] After receiving the execution operation for the document task in the task information, in response to the trigger operation of the conversation card, the task execution record of the target social conversation is displayed;

[0274] The task execution record of the target social session includes the task execution record of the session members who have performed document tasks in the target social session.

[0275] In one implementation, the task execution record of the target social session includes a jump control; the display unit 2601 is also used to perform the following steps:

[0276] In response to a triggering operation on the jump control, jump to the cell location where the execution data is written in the target document for display.

[0277] According to one embodiment of this application, Figure 26 The various units in the task processing device shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above-mentioned units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the task processing device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0278] According to another embodiment of this application, a computer program capable of performing some or all of the steps involved in the methods of the aforementioned social client can be run on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), to construct a system such as... Figure 26 The task processing apparatus shown herein, and the task processing method for implementing the embodiments of this application, are described. A computer program may be recorded on, for example, a computer-readable storage medium, loaded onto the aforementioned computing device via the computer-readable storage medium, and executed therein.

[0279] In this embodiment, after the target social session in the social client and the target document in the document service communicate with each other, document tasks related to the target document can be sent to the target social session. In response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation can be written into the target document. Therefore, document tasks can be executed in the target social session, meaning they can be executed in the social client. Furthermore, after executing a document task in the social client, the execution data of the document task can be automatically written to the target document without needing to open the target document to execute the document task. This simplifies the document task execution process and improves the execution efficiency of the document task.

[0280] Please see Figure 26 , Figure 26 This is a schematic diagram of the structure of a task processing device provided in an embodiment of this application. The task processing device can be installed in the computer device provided in the embodiment of this application. The computer device can be a terminal, and the terminal runs a social client and a document service. Figure 26 The apparatus shown may be a computer program running on a computer device, and this task processing apparatus may be used to perform some or all of the document service steps in the above method embodiments. Please refer to... Figure 26 The task processing device may include the following units:

[0281] Display unit 2601 is used to display the service interface of document service, and the target document in document service and the target social conversation in social client are interconnected.

[0282] Processing unit 2602 is used to send document tasks related to the target document to the target social session;

[0283] The display unit 2601 is also used to write execution data corresponding to the execution operation into the target document in response to the execution operation of the document task in the target social session.

[0284] In one implementation, the display unit 2601 is further configured to perform the following steps:

[0285] Configure document tasks related to the target document for the target social conversation.

[0286] In one implementation, when configuring document tasks related to a target document for a target social session, the display unit 2601 specifically performs the following steps:

[0287] Configure the target task execution method for the target social session in the social client;

[0288] Configure the document service's document execution flow for the target document under the target task execution mode.

[0289] In one implementation, the display unit 2601, when configuring the document execution flow of the document service for the target document under the target task execution mode, is specifically used to execute the following steps:

[0290] Configure the target execution flow type for the target document under the target task execution mode;

[0291] Configure the execution fields and their values ​​under the target execution process type.

[0292] In one implementation, when configuring document tasks related to a target document for a target social session, the display unit 2601 is also configured to perform at least one of the following:

[0293] Configure how the document task is sent to the social client;

[0294] Configure the target social conversation as the execution object for the document task;

[0295] Configure the task content of the document task;

[0296] Configure the document that communicates with the target social conversation as the target document;

[0297] Configure the task triggering conditions for the document task.

[0298] In one implementation, the target task execution method includes any of the following: button method, content input method, and content upload method;

[0299] The button method refers to the way document tasks are executed in social clients by triggering an action on an action button.

[0300] Content input method refers to the way document tasks are performed by executing content input operations in social clients;

[0301] Content upload refers to the method of performing document tasks by executing content upload operations in social clients.

[0302] According to one embodiment of this application, Figure 26 The various units in the task processing device shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above-mentioned units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the task processing device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0303] According to another embodiment of this application, a method for performing some or all of the steps involved in the above-described document service can be constructed by running a computer program capable of executing some or all of the steps involved in the document service method on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access storage medium (RAM), and read-only storage medium (ROM). Figure 26 The task processing apparatus shown herein, and the task processing method for implementing the embodiments of this application, are described. A computer program may be recorded on, for example, a computer-readable storage medium, loaded onto the aforementioned computing device via the computer-readable storage medium, and executed therein.

[0304] In this embodiment, after the target social session in the social client and the target document in the document service communicate with each other, document tasks related to the target document can be sent to the target social session. In response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation can be written into the target document. Therefore, document tasks can be executed in the target social session, meaning they can be executed in the social client. Furthermore, after executing a document task in the social client, the execution data of the document task can be automatically written to the target document without needing to open the target document to execute the document task. This simplifies the document task execution process and improves the execution efficiency of the document task.

[0305] Based on the above methods and apparatus embodiments, this application provides a computer device. Please refer to... Figure 27 , Figure 27 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 27 The computer device shown includes at least a processor 2701, an input interface 2702, an output interface 2703, and a computer-readable storage medium 2704. The processor 2701, input interface 2702, output interface 2703, and computer-readable storage medium 2704 can be connected via a bus or other means.

[0306] Computer-readable storage medium 2704 can be stored in the memory of a computer device. Computer-readable storage medium 2704 is used to store computer programs, including computer instructions. Processor 2701 is used to execute the computer program stored in computer-readable storage medium 2704. Processor 2701 (or CPU (Central Processing Unit)) is the computing and control core of the computer device, suitable for implementing computer programs, specifically for loading and executing computer programs to achieve corresponding method flows or functions.

[0307] This application also provides a computer-readable storage medium (Memory), which is a memory device in a computer device used to store programs and data. It is understood that the computer-readable storage medium here can include both built-in storage media in the computer device and extended storage media supported by the computer device. The computer-readable storage medium provides storage space for storing the operating system of the computer device. Furthermore, the storage space also stores computer programs suitable for loading and execution by a processor. It should be noted that the computer-readable storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0308] In some embodiments, the computer device may be a terminal, on which a social networking client and a document service are running. Specifically, the processor 2701 may load and execute the computer program stored in the computer-readable storage medium 2704 to implement the corresponding steps related to the social networking client described above. Specifically, the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and executed as follows:

[0309] Displays the conversation interface of the target social conversation in the social client, and the target social conversation communicates with the target document in the document service;

[0310] Display task information for document tasks related to the target document in the session interface;

[0311] The task information receives the execution operation for the document task, triggering the document service to write the execution data corresponding to the execution operation into the target document.

[0312] In one implementation, the task information includes the task content of the document task and the execution area of ​​the document task; the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701. When receiving the execution operation on the document task in the task information, it is specifically used to perform the following steps:

[0313] Receive execution operations for document tasks in the execution area.

[0314] In one implementation, when a computer program in computer-readable storage medium 2704 is loaded and executed by processor 2701 to receive an execution operation on a document task in an execution area, it is specifically used to perform any of the following:

[0315] The execution area includes the execution button for the document task, and receives button trigger operations for the execution button in the execution area;

[0316] The execution area is the content input area, where content input operations are received.

[0317] The execution area is the content upload area, where content upload operations are received.

[0318] In one implementation, when the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701, and execution data corresponding to the execution operation is written into the target document, it specifically performs the following steps:

[0319] Write the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document.

[0320] In one implementation, the document task is configured with the target execution flow type for the target document after the document task is executed, as well as the execution fields and values ​​under the target execution flow type; the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701. When writing the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document, it is specifically used to perform the following steps:

[0321] Write the execution field value into the cell corresponding to the execution field in the target document, according to the target execution flow type.

[0322] In one implementation, when a computer program in computer-readable storage medium 2704 is loaded and executed by processor 2701, and when writing execution field values ​​to cells corresponding to execution fields in the target document according to the target execution flow type, it is specifically used to perform the following steps:

[0323] If the target execution process type is record modification, then modify the field value in the cell corresponding to the execution field in the target document to the execution field value;

[0324] If the target execution process type is "new record", then add the execution field to the target document and add the execution field value to the cell corresponding to the execution field.

[0325] In one implementation, the cell corresponding to the document task includes any of the following:

[0326] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The document task is also configured with the task triggering conditions. The cell corresponding to the document task is determined by the row of the target cell in the target document that meets the task triggering conditions and the column of the execution field.

[0327] The document task is configured to specify the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The target cell of the target document is added with a conversation card of the target social conversation. The cell corresponding to the document task is determined based on the row where the target cell is located and the column where the execution field is located.

[0328] The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed; the cell corresponding to the document task is a cell added at the end of the column where the execution field is located.

[0329] In one implementation, the target social session is a group social session; the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701, and when the execution data corresponding to the execution operation is written into the target document, it is specifically used to execute any of the following:

[0330] Write the execution data corresponding to each task execution member in the target social session into the target document;

[0331] The execution data corresponding to the next task execution member is used in the target document, overwriting the execution data corresponding to the previous task execution member.

[0332] In one implementation, a conversation card for the target social session is added to the target document; the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and is also used to perform the following steps:

[0333] After the target social conversation and the target document are interconnected, the interconnection status information is displayed in response to the trigger operation of the conversation card;

[0334] Interoperability status information is used to indicate that the document service supports sending task information to the target social session.

[0335] In one implementation, a conversation card for the target social session is added to the target document; the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and is also used to perform the following steps:

[0336] After receiving the execution operation for the document task in the task information, the document service is triggered to display the task execution notification in the session card;

[0337] The task execution notification indicates that the document task has been executed by the target social session.

[0338] In one implementation, a conversation card for the target social session is added to the target document; the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and is also used to perform the following steps:

[0339] After receiving the execution operation for the document task in the task information, in response to the trigger operation of the conversation card, the task execution record of the target social conversation is displayed;

[0340] The task execution record of the target social session includes the task execution record of the session members who have performed document tasks in the target social session.

[0341] In one implementation, the task execution record of the target social session includes a jump control; the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and is also used to perform the following steps:

[0342] In response to a triggering operation on the jump control, jump to the cell location where the execution data is written in the target document for display.

[0343] In other embodiments, the computer device may be a terminal running a social networking client and a document service. Specifically, the processor 2701 may load and execute the computer program stored in the computer-readable storage medium 2704 to implement the aforementioned steps related to the document service. Specifically, the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and executed as follows:

[0344] The document service interface is displayed, and the target document in the document service can communicate with the target social conversation in the social client.

[0345] Send document tasks related to the target document to the target social conversation;

[0346] In response to the execution operation of a document task in the target social session, the execution data corresponding to the execution operation is written into the target document.

[0347] In one implementation, the computer program in the computer-readable storage medium 2704 is loaded by the processor 2701 and is also used to perform the following steps:

[0348] Configure document tasks related to the target document for the target social conversation.

[0349] In one implementation, when a computer program in computer-readable storage medium 2704 is loaded and executed by processor 2701 to configure document tasks related to a target document for a target social session, it specifically performs the following steps:

[0350] Configure the target task execution method for the target social session in the social client;

[0351] Configure the document service's document execution flow for the target document under the target task execution mode.

[0352] In one implementation, when the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701, and the document execution flow of the document service on the target document under the configured target task execution mode is executed, it is specifically used to perform the following steps:

[0353] Configure the target execution flow type for the target document under the target task execution mode;

[0354] Configure the execution fields and their values ​​under the target execution process type.

[0355] In one implementation, when the computer program in the computer-readable storage medium 2704 is loaded and executed by the processor 2701 to configure document tasks related to the target document for the target social session, it is also used to perform at least one of the following:

[0356] Configure how the document task is sent to the social client;

[0357] Configure the target social conversation as the execution object for the document task;

[0358] Configure the task content of the document task;

[0359] Configure the document that communicates with the target social conversation as the target document;

[0360] Configure the task triggering conditions for the document task.

[0361] In one implementation, the target task execution method includes any of the following: button method, content input method, and content upload method;

[0362] The button method refers to the way document tasks are executed in social clients by triggering an action on an action button.

[0363] Content input method refers to the way document tasks are performed by executing content input operations in social clients;

[0364] Content upload refers to the method of performing document tasks by executing content upload operations in social clients.

[0365] In this embodiment, after the target social session in the social client and the target document in the document service communicate with each other, document tasks related to the target document can be sent to the target social session. In response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation can be written into the target document. Therefore, document tasks can be executed in the target social session, meaning they can be executed in the social client. Furthermore, after executing a document task in the social client, the execution data of the document task can be automatically written to the target document without needing to open the target document to execute the document task. This simplifies the document task execution process and improves the execution efficiency of the document task.

[0366] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the task processing method described above.

[0367] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0368] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0369] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0370] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A task processing method, characterized in that, include: The session interface of the target social session in the social client is displayed, and the target social session is interconnected with the target document in the document service; The task information of the document task related to the target document is displayed in the session interface; The task information receives the execution operation for the document task, triggering the document service to write the execution data corresponding to the execution operation into the target document.

2. The method as described in claim 1, characterized in that, The task information includes the task content of the document task and the execution area of ​​the document task; receiving the execution operation of the document task in the task information includes: The execution area receives the execution operation for the document task.

3. The method as described in claim 2, characterized in that, Receiving the execution operation on the document task in the execution area includes any of the following: The execution area includes an execution button for the document task, and the execution area receives button trigger operations for the execution button; The execution area is a content input area, where content input operations are received. The execution area is a content upload area, where content upload operations are received.

4. The method as described in claim 1, characterized in that, The step of writing the execution data corresponding to the execution operation into the target document includes: In the target document, in the cell corresponding to the document task, write the execution data corresponding to the execution operation.

5. The method as described in claim 4, characterized in that, The document task is configured with the target execution flow type for the target document after the document task is executed, as well as the execution fields and execution field values ​​under the target execution flow type; The step of writing the execution data corresponding to the execution operation into the cell corresponding to the document task in the target document includes: In the cell corresponding to the execution field in the target document, write the execution field value according to the target execution process type.

6. The method as described in claim 5, characterized in that, The step of writing the execution field value in the cell corresponding to the execution field in the target document according to the target execution flow type includes: If the target execution process type is record modification, then the field value in the cell corresponding to the execution field in the target document will be modified to the execution field value; If the target execution process type is to add a new record, then add the execution field to the target document and add the execution field value to the cell corresponding to the execution field.

7. The method according to any one of claims 4-6, characterized in that, The cell corresponding to the document task includes any of the following: The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The document task is also configured with task triggering conditions. The cell corresponding to the document task is determined based on the row of the target cell in the target document that meets the task triggering conditions and the column of the execution field. The document task is configured with the target execution flow type and the execution fields under the target execution flow type after the document task is executed. The target cell of the target document has a conversation card of the target social conversation added to it. The cell corresponding to the document task is determined based on the row where the target cell is located and the column where the execution field is located. The document task is configured with the target execution flow type for the target document and the execution fields under the target execution flow type after the document task is executed; the cell corresponding to the document task is a cell added at the end of the column where the execution field is located.

8. The method as described in claim 1, characterized in that, The target social session is a group social session; the step of writing the execution data corresponding to the execution operation into the target document includes any of the following: Write the execution data corresponding to each task execution member in the target social session into the target document; The execution data corresponding to the next task execution member is used in the target document, overwriting the execution data corresponding to the previous task execution member.

9. The method as described in claim 1, characterized in that, The target document includes a conversation card for the target social conversation; the method further includes: After the target social session and the target document communicate with each other, the communication status information is displayed in response to the triggering operation of the session card; The interoperability status information is used to indicate that the document service supports sending task information to the target social session.

10. The method as described in claim 1, characterized in that, The target document includes a conversation card for the target social conversation; the method further includes: After receiving the execution operation for the document task in the task information, the document service is triggered to display the task execution notification of the session card; The task execution notification indicates that the document task has been executed by the target social session.

11. The method as described in claim 1, characterized in that, The target document includes a conversation card for the target social conversation; the method further includes: After receiving the execution operation for the document task in the task information, in response to the trigger operation for the conversation card, the task execution record of the target social conversation is displayed; The task execution record of the target social session includes the task execution record of the session members who have executed the document task in the target social session.

12. The method as described in claim 11, characterized in that, The task execution record of the target social session includes a jump control; the method further includes: In response to the triggering operation of the jump control, the system jumps to the cell position where the execution data is written in the target document for display.

13. A task processing method, characterized in that, include: The document service interface is displayed, and the target document in the document service communicates with the target social conversation in the social client. Send document tasks related to the target document to the target social session; In response to the execution operation of the document task in the target social session, execution data corresponding to the execution operation is written into the target document.

14. The method as described in claim 13, characterized in that, The method further includes: Configure document tasks related to the target document for the target social session.

15. The method as described in claim 14, characterized in that, Configuring document tasks related to the target document for the target social session includes: Configure the target social session with the target task execution mode for executing the document task in the social client; Configure the document service's document execution flow for the target document under the target task execution mode.

16. The method as described in claim 15, characterized in that, The document execution process of the document service on the target document under the configured target task execution mode includes: Configure the target execution flow type for the target document under the target task execution mode; Configure the execution fields and execution field values ​​under the target execution process type.

17. The method as described in claim 15, characterized in that, Configuring document tasks related to the target document for the target social session further includes at least one of the following: Configure the way the document task is sent to the social client; Configure the target social session as the execution object of the document task; Configure the task content of the document task; Configure the document that communicates with the target social session as the target document; Configure the task triggering conditions for the document task.

18. The method according to any one of claims 15-17, characterized in that, The target task execution method includes any of the following: button method, content input method, and content upload method; The button method refers to the method of executing the document task by triggering the button in the social client; The content input method refers to the way to perform the document task by performing content input operations in the social client; The content upload method refers to the way the document task is performed by executing a content upload operation in the social client.

19. A task processing device, characterized in that, include: The display unit is used to display the session interface of the target social session in the social client, wherein the target social session is interconnected with the target document in the document service; The display unit is also used to display task information of document tasks related to the target document in the session interface; A processing unit is configured to receive an execution operation for the document task from the task information; The display unit is used to trigger the document service to write the execution data corresponding to the execution operation into the target document.

20. A task processing device, characterized in that, include: The display unit is used to display the service interface of the document service, wherein the target document in the document service and the target social session in the social client are interconnected. The processing unit is used to send document tasks related to the target document to the target social session; The processing unit is further configured to, in response to the execution operation of the document task in the target social session, write execution data corresponding to the execution operation into the target document.

21. A computer device, characterized in that, The computer device includes: A processor is a tool for implementing computer programs. A computer-readable storage medium storing a computer program adapted to be loaded by the processor and executed as the task processing method as claimed in any one of claims 1-12, or as the task processing method as claimed in any one of claims 13-18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and executed by the task processing method as described in any one of claims 1-12, or the task processing method as described in any one of claims 13-18.

23. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the task processing method as described in any one of claims 1-12, or the task processing method as described in any one of claims 13-18.

Images