Collaboration task processing method, device, equipment, and computer-readable storage medium

Abstract

A collaboration task processing method, an apparatus, a device, and a computer-readable storage medium, the method including the steps of: displaying a collaboration task list related to a first user on a collaboration task center interface of the first user (S102); determining a target task creation source type designated by the first user in response to a screening operation of the first user screening collaboration tasks according to task creation source types (S104); screening collaboration tasks in the collaboration task list based on the target task creation source type (S106); and displaying the screening results on the collaboration task center interface of the first user (S108). By screening collaboration tasks and displaying the screening results on the collaboration task center interface of the first user in response to a screening operation of the first user screening collaboration tasks according to task creation source types, the problem that the current task screening method is too limited can be alleviated, and the task screening needs of users can be met.

Description

[Technical Field]

[0001] This application claims priority from Chinese Patent Application No. 202210577437.6 filed on May 25, 2022, and the contents disclosed in the above Chinese patent application are hereby incorporated by reference into this application.

[0002] SUMMARY OF THE INVENTION Embodiments of the present disclosure relate to a collaborative task processing method, an apparatus, a device, and a computer-readable storage medium. [Background technology]

[0003] In the field of collaborative offices, task (also called "agenda") systems are a commonly used application. Current task systems provide users with a collaboration task center, through which they can create tasks and check all tasks related to them in the task system. Currently, users can screen collaboration tasks in the collaboration task center interface according to the progress of the collaboration tasks. However, this task screening method only allows users to screen tasks according to the task progress, which is too limited and cannot meet the ever-increasing task screening needs of users. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present disclosure provide a collaboration task processing method, device, equipment, and computer-readable storage medium that alleviate the problem that current task screening methods are too limited by screening collaboration tasks and displaying the screening results in the collaboration task center interface of a first user in response to a screening operation in which the first user screens collaboration tasks according to the task creation source type, thereby meeting the ever-increasing task screening needs of users and improving the user's experience when processing collaboration tasks. [Means for solving the problem]

[0005] In a first aspect, an embodiment of the present disclosure comprises: displaying a collaboration task list associated with the first user in a collaboration task center interface of the first user; determining a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; and displaying the screening result on a collaboration task center interface of the first user.

[0006] In a second aspect, an embodiment of the present disclosure comprises: a list display unit for displaying a collaboration task list associated with the first user in a collaboration task center interface of the first user; a type determination unit for determining a target task creation source type designated by the first user in response to a screening operation by the first user to screen collaboration tasks according to task creation source types; a task screening unit for screening collaboration tasks in the collaboration task list according to the target task creation source type; a result display unit for displaying the screening results in a collaboration task center interface of the first user.

[0007] In a third aspect, an embodiment of the present disclosure comprises: a processor; a memory configured to store computer-executable instructions, the computer-executable instructions, when executed by a processor, causing the processor to perform the steps of the method according to the first aspect above.

[0008] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing computer-executable instructions that, when executed by a processor, cause the processor to perform the steps of the method described in the first aspect above. [Effects of the Invention]

[0009] In an embodiment of the present disclosure, first, a collaboration task list related to the first user is displayed in the collaboration task center interface of the first user, then a target task creation source type specified by the first user is determined in response to a screening operation by the first user to screen the collaboration tasks according to the task creation source type, then the collaboration tasks in the collaboration task list are screened based on the target task creation source type, and finally the screening results are displayed in the collaboration task center interface of the first user. As can be seen from the above, this embodiment screens the collaboration tasks and displays the screening results in the collaboration task center interface of the first user in response to a screening operation by the first user to screen the collaboration tasks according to the task creation source type, thereby alleviating the problem that the current task screening method is too limited, meeting the ever-increasing task screening needs of users, and improving the user's experience when processing collaboration tasks. [Brief explanation of the drawings]

[0010] In order to more clearly describe one or more embodiments of the present disclosure, the following briefly introduces drawings that need to be used to describe the embodiments. Obviously, the drawings described below are merely some embodiments described in the present disclosure, and those skilled in the art can further obtain other drawings based on these drawings without any creative work. [Figure 1] 1 is a flowchart of a collaboration task processing method provided by one embodiment of the present disclosure. [Figure 2a] FIG. 1 is a schematic diagram of screening collaboration tasks according to task creation source type provided by an embodiment of the present disclosure; [Figure 2b] FIG. 10 is a schematic diagram of screening collaboration tasks according to task creation source type provided by another embodiment of the present disclosure; [Figure 2c] FIG. 10 is a schematic diagram of screening collaboration tasks according to task creation source type provided by yet another embodiment of the present disclosure; [Figure 3a] FIG. 10 is a schematic diagram exhibiting a task creation source identifier provided by one embodiment of the present disclosure. [Figure 3b] FIG. 10 is a schematic diagram exhibiting a task creation source identifier provided by another embodiment of the present disclosure. [Figure 4a] FIG. 1 is a schematic diagram of creating a collaboration task based on a session, provided by one embodiment of the present disclosure; [Figure 4b] FIG. 2 is a schematic diagram of a task creation source interface provided by one embodiment of the present disclosure. [Figure 4c] FIG. 1 is a schematic diagram of creating a collaboration task based on a session, provided by another embodiment of the present disclosure; [Figure 4d] FIG. 10 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 5a] FIG. 1 is a schematic diagram of creating a collaboration task based on a shared document provided by an embodiment of the present disclosure; [Figure 5b] FIG. 10 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 5c] FIG. 1 is a schematic diagram of creating a collaboration task based on a shared document provided by another embodiment of the present disclosure; [Figure 5d] FIG. 10 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 6a] FIG. 1 is a schematic diagram of updating a collaboration task list provided by an embodiment of the present disclosure; [Figure 6b] FIG. 10 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 6c] FIG. 10 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 6d] FIG. 10 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 7] FIG. 1 is a structural schematic diagram of a collaboration task processing device provided by an embodiment of the present disclosure; [Figure 8] 1 is a structural schematic diagram of an electronic device provided according to an embodiment of the present disclosure; DETAILED DESCRIPTION OF THE INVENTION

[0011] In order to allow those skilled in the art to better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only some embodiments of the present disclosure, not all embodiments. Based on one or more embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without any creative work should fall within the protection scope of the present application.

[0012] The collaboration task center according to each embodiment of the present disclosure is located in a task system, and the task system may be an application located within collaboration office software. Collaboration office software is office software for in-house staff of large companies, and the collaboration office software integrates various applications such as instant messaging, cloud documents, audio / video conferencing, and a task system, greatly improving the efficiency of collaboration office work among staff of large companies.

[0013] On the other hand, in the collaborative office software, a user may create a collaboration task in the task system, or may create a collaboration task in other applications other than the task system in the collaborative office software, for example, creating a collaboration task in instant messaging, cloud documents, etc. In the collaborative office software, other applications other than the task system can communicate with the task system, and the collaboration task created by the user in other applications other than the task system can be synchronized with the task system.

[0014] In the collaborative office software, applications other than the task system can communicate with the task system to synchronize collaborative tasks. One implementation is as follows: The collaborative office software can provide a block-based framework, which is a standard framework that allows any application integrated into the collaborative office software to open internal information, convert the internal information into data in a standard format, and display the data. This standard format data is combined with a view of the standard format data to form a component, i.e., a block. The block-based framework allows any application integrated into the collaborative office software to create and develop application segments that can be flexibly displayed and interacted with, and the application segments can be transferred in the form of blocks between applications within the collaborative office software. These blocks can be embedded and displayed in any application integrated into the collaborative office software, and when the same application segment is embedded and displayed in different applications, it is essentially the same block that is embedded and displayed. Based on this, applications other than the task system in the collaborative office software can create collaboration tasks based on the framework of the blocks, transfer the collaboration tasks in the form of blocks to the task system, and embed and display the collaboration tasks in the task system.

[0015] On the other hand, for certain external third-party systems other than the collaboration office software, such as a ticket system, after a user performs a certain operation, such as a ticket creation operation, in the external third-party system, the external third-party system can call an API (Application Programming Interface) provided by the task system to create a collaboration task and synchronize the collaboration task with the task system.

[0016] As can be seen from the above two aspects, a collaboration task in a task system may be created by a user in the task system, or may be created by a user in other applications other than the task system in the collaborative office software, or may be created by a user in an external third-party system. Therefore, a collaboration task in a user's task system has multiple creation sources, including but not limited to the above task system, instant messaging, cloud documents, audio-video conferencing, external third-party systems, etc.

[0017] Based on this, one embodiment of the present disclosure provides a collaboration task processing method that alleviates the problem that current task screening methods are too limited by screening collaboration tasks and displaying the screening results in the collaboration task center interface of the first user's task system in response to a screening operation in which the first user screens collaboration tasks according to the task creation source type, thereby meeting the ever-increasing task screening needs of users and improving the user's experience when processing collaboration tasks.

[0018] FIG. 1 is a flowchart of a collaboration task processing method provided by an embodiment of the present disclosure. As shown in FIG. 1, the flow includes the following steps S102 to S108.

[0019] In step S102, a collaboration task list associated with the first user is displayed in the collaboration task center interface of the first user.

[0020] In step S104, in response to a screening operation by the first user to screen collaboration tasks according to task creation source types, a target task creation source type designated by the first user is determined.

[0021] In step S106, the collaboration tasks in the collaboration task list are screened based on the target task creation source type.

[0022] In step S108, the screening results are displayed on the first user's collaboration task center interface.

[0023] In an embodiment of the present disclosure, first, a collaboration task list related to the first user is displayed in the collaboration task center interface of the first user, then a target task creation source type specified by the first user is determined in response to a screening operation by the first user to screen the collaboration tasks according to the task creation source type, then the collaboration tasks in the collaboration task list are screened based on the target task creation source type, and finally the screening results are displayed in the collaboration task center interface of the first user. As can be seen from the above, this embodiment screens the collaboration tasks and displays the screening results in the collaboration task center interface of the first user in response to a screening operation by the first user to screen the collaboration tasks according to the task creation source type, thereby alleviating the problem that the current task screening method is too limited, meeting the ever-increasing task screening needs of users, and improving the user's experience when processing collaboration tasks.

[0024] In one embodiment, for a collaboration task in the first user's task system, its task creation source type includes, but is not limited to, a normal task, a session, a shared document, an external third-party system, etc. A collaboration task whose task creation source type is "normal task" is a collaboration task created by a task creation entry provided by the task system or a shortcut key provided by the task system. The task creation entry provided by the task system may be located in the main interface of the first user's collaborative office software or in the collaboration task center interface of the first user's task system.

[0025] A collaboration task whose task creation source type is "session" is a collaboration task created by a session in an instant messaging application integrated into the collaboration office software. When creating a collaboration task by a session, the collaboration task may be created based on a session message in the session, or based on a task creation entry provided for the session. The task creation entry provided for the session may be located in the sidebar of the session or near the message input box of the session.

[0026] A collaboration task whose task creation source type is "shared document" is a collaboration task created by a shared document application (i.e., the above-mentioned cloud document application) integrated into the collaboration office software. When creating a collaboration task by a shared document application, the collaboration task may be created based on part of the document content in the shared document, or may be created based on a task creation entry provided to the shared document application. The task creation entry provided to the shared document application may be located in a sidebar of the interface of the shared document application.

[0027] A collaboration task whose task creation source type is "external third-party system" is a collaboration task created by a specific external third-party system associated with the collaboration office software. When a collaboration task is created by an external third-party system, a user can perform a specific operation in the external third-party system, and the external third-party system creates a collaboration task by calling an API interface provided by the task system based on the specific operation, and synchronizes the collaboration task with the task system.

[0028] 2a is a schematic diagram of screening collaboration tasks according to a task creation source type provided by one embodiment of the present disclosure, FIG. 2b is a schematic diagram of screening collaboration tasks according to a task creation source type provided by another embodiment of the present disclosure, and FIG. 2c is a schematic diagram of screening collaboration tasks according to a task creation source type provided by yet another embodiment of the present disclosure. As shown in FIG. 2a, a collaboration task center interface of a first user displays a collaboration task list related to the first user, and the collaboration task list related to the first user includes collaboration tasks related to the first user, which may be collaboration tasks assigned to the first user by other users, or collaboration tasks assigned by the first user to other users, etc.

[0029] The upper right corner of the collaboration task center interface of the first user has a control "Source" indicating that collaboration tasks are screened according to the task creation source type. After the first user triggers the control, multiple drop-down options shown in FIG. 2b can be displayed, each representing a task creation source type. The first user can select a target task creation source type from these multiple drop-down options. In the case of FIG. 2b, the first user selected "Session" as the target task creation source type. Next, the task system screens collaboration tasks in the displayed collaboration task list based on the target task creation source type selected by the first user, and displays the screening results in the collaboration task center interface of the first user, specifically, in the collaboration task list associated with the first user. In FIG. 2c, collaboration tasks with a task creation source type of "Session" are displayed in the collaboration task list associated with the first user, thereby presenting the screened collaboration tasks to the first user.

[0030] In Figure 2b, the first user may select all of the various task creation source types with one click, or clear the all selection mode with one click. After the first user selects one or more task creation source types, the corresponding marks are displayed for the selected types, and the number of types selected by the first user is displayed in the task collaboration center interface.

[0031] In one embodiment, after displaying the collaboration task list related to the first user, the method can further obtain a task creation source identifier corresponding to the collaboration task in the collaboration task list, display the task creation source identifier in the collaboration task list, and display a task creation source interface of the collaboration task to the first user in response to a trigger operation on the task creation source identifier of the first user.

[0032] 3A is a schematic diagram of a display of task creation source identifiers provided by an embodiment of the present disclosure. As shown in FIG. 3A, a computer-based task system displays task creation source identifiers for each collaboration task in a collaboration task list associated with a first user. The task creation source corresponds to a task creation source type, which includes at least one of a normal task, a session, a shared document, and an external third-party system. Therefore, the task creation source identifier also includes at least one of a normal task identifier corresponding to a normal task, a session identifier corresponding to a session, a shared document identifier corresponding to a shared document, and an external third-party system identifier corresponding to an external third-party system. The first user can trigger the task creation source identifier, for example, by clicking the task creation source identifier. In response to the triggering operation, the task system can display to the first user a task creation source interface for the collaboration task to which the triggered task creation source identifier belongs.

[0033] FIG. 3b is a schematic diagram of displaying a task creation source identifier provided by another embodiment of the present disclosure. As shown in FIG. 3b, a task system on a mobile phone is taken as an example, and the task creation source identifier of each collaboration task in the collaboration task list related to a first user is displayed.

[0034] In one embodiment, the task creation source of a collaboration task in the collaboration task list is a session, and the task creation source identifier is a session identifier, and accordingly, displaying a task creation source interface of the collaboration task to the first user may be obtaining a session corresponding to the session identifier and displaying an interface associated with the session to the first user as the task creation source interface.

[0035] As shown in FIG. 3a, the first collaboration task in the collaboration task list associated with the first user is a collaboration task created based on a session, and its task creation source is the session. Accordingly, a session identifier is displayed below the collaboration task. When the user triggers the session identifier, the task system can display to the first user an interface associated with the session for creating the collaboration task as a task creation source interface.

[0036] In one embodiment, after obtaining a session corresponding to a session identifier, before displaying an interface associated with the session to the first user, the first user is determined to have permission to view the session. If the first user has permission, the interface associated with the session is displayed to the first user. If the first user does not have permission, the first user is notified that the session cannot be viewed. If the first user is a session member of the session, the first user is determined to have permission to view the session. If the first user is not a session member of the session, the first user is determined to have no permission to view the session. Of course, this is merely an exemplary method for determining whether the first user has permission to view the session, and other methods may be used to determine whether the first user has permission to view the session, and the present disclosure does not limit the scope of the present disclosure.

[0037] After determining that the first user has the authority to view the session, first, the collaboration office software of the first user invokes an instant messaging application to open the session, and in the opened session, the first user is presented with an interface associated with the session, i.e., the first user can remain in the interface associated with the session, and the first user can also continue to send session messages in the session. In this case, the interface associated with the session can be obtained by scrolling the session.

[0038] In one embodiment, the collaboration task is created based on a first task creation entry associated with a session by a task creator, and the interface associated with the session is a random interface for the session or an interface that the session presents when the task creator creates the collaboration task based on the first task creation entry. The task creator and the first user may be the same user or different users.

[0039] FIG. 4a is a schematic diagram of creating a collaboration task based on a session provided by one embodiment of the present disclosure. As shown in FIG. 4a, in a session, task creation entries are displayed in both the charm bar of the session and the "+" pop-up list of the message input box of the session. These two task creation entries are first task creation entries, and a task creator can create a collaboration task in a session through the first task creation entry.

[0040] In one embodiment, after a task creator creates a collaboration task through the above-mentioned first task creation entry, when the first user triggers the session identifier shown in Fig. 3a, a random interface of the session can be displayed and provided to the first user as a task creation source interface. The random interface of the session can be obtained by opening the session, and the random interface of the session may be an interface obtained after opening the session, or may be an interface corresponding to any chat content.

[0041] 4b is a schematic diagram of a task creation source interface provided by one embodiment of the present disclosure, in which after the task creator creates the collaboration task through the above-mentioned first task creation entry, when the first user triggers the session identifier shown in Fig. 3a, in one embodiment, the interface presented by the session when the task creator creates the collaboration task through the first task creation entry can be displayed to the first user as a task creation source interface, as shown in Fig. 4b. As shown in Fig. 4b, when creating the collaboration task, each session member in Fig. 4a is considering where to hold the meeting.

[0042] In another embodiment, the collaboration task is created based on a second task creation entry associated with a session message in a session by the task creator, and the interface associated with the session is the interface in which the session message is located. The task creator and the first user may be the same user or different users.

[0043] 4c is a schematic diagram of creating a collaboration task based on a session provided by another embodiment of the present disclosure. As shown in FIG. 4c, after selecting a session message from a session, multiple operation entries for the session message can be displayed, including a task creation entry for creating a collaboration task, which is a second task creation entry. After selecting a session message in a session, a task creator can create a collaboration task through the second task creation entry.

[0044] 4d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure, in which after the task creator creates a collaboration task based on the above-mentioned second task creation entry, when the first user triggers the session identifier shown in FIG. 3a, an interface in which a session message for creating a collaboration task in the session is located can be displayed to the first user as a task creation source interface, as shown in FIG. 4d. In FIG. 4d, the task creation source interface contains the session message "Let's hold a meeting tomorrow at 3 o'clock to discuss," and the collaboration task to which the triggered task creation source identifier belongs is created based on the session message. Therefore, in the task creation source interface, the session message is displayed after being processed in a specific format, such as being bolded and underlined.

[0045] As can be seen from the above, when a collaboration task is created through a session, after a first user triggers a session identifier, an interface associated with the session can be displayed to the first user as a task creation source interface, thereby meeting the first user's need to trace back the task creation source.

[0046] In one embodiment, the task creation source of a collaboration task in the collaboration task list is a shared document, and the task creation source identifier is a document identifier. Accordingly, displaying a task creation source interface of the collaboration task to the first user may be to obtain the shared document corresponding to the document identifier and display a content interface of the shared document to the first user as the task creation source interface.

[0047] As shown in Figure 3a, the second collaboration task in the collaboration task list related to the first user is a collaboration task created based on a shared document, and its task creation source is the shared document. Accordingly, a document identifier is displayed below the collaboration task. When the user triggers the document identifier, the task system can display the content interface of the shared document for creating the collaboration task to the first user as a task creation source interface.

[0048] In one embodiment, after obtaining a shared document corresponding to the document identifier, before displaying the content interface of the shared document to the first user as a task creation source interface, the system determines whether the first user has permission to view the shared document. If the first user has permission, the system displays the content interface of the shared document to the first user. If the first user does not have permission, the system informs the first user that the shared document is not available to view. If the first user is the creator or designated recipient of the shared document, the system determines that the first user has permission to view the shared document. Conversely, the system determines that the first user does not have permission to view the shared document. Of course, this is merely an exemplary method for determining whether the first user has permission to view the shared document. Other methods for determining whether the first user has permission to view the shared document are also possible, and are not limited thereto.

[0049] After determining that the first user has the authority to view the shared document, the shared document application is first invoked in the collaboration office software of the first user to open the shared document, and the content interface of the shared document is presented to the first user in the opened shared document, that is, the first user can remain in the content interface of the shared document, and the first user can also scroll the screen to continue viewing the shared document, in this case, the content interface of the shared document can be obtained by scrolling the shared document.

[0050] In one embodiment, the collaboration task is created based on a third task creation entry associated with the shared document by the task creator, and the content interface is a random content interface of the shared document or an interface that the shared document presents when the task creator creates the collaboration task based on the third task creation entry, and the task creator and the first user may be the same user or different users.

[0051] FIG. 5a is a schematic diagram of creating a collaboration task based on a shared document provided by one embodiment of the present disclosure. As shown in FIG. 5a, in a shared document application, a task creation entry is displayed in the charm bar of the content interface of the shared document, and the task creation entry is a third task creation entry. A task creator can create a collaboration task in the shared document application through the third task creation entry.

[0052] In one embodiment, after the task creator creates a collaboration task through the above-mentioned third task creation entry, when the first user triggers the document identifier shown in Fig. 3a, a random content interface of the shared document can be displayed and provided to the first user as a task creation source interface. The random content interface of the shared document can be obtained by opening the shared document, and the random content interface of the shared document may be a content interface obtained after opening the shared document, or may be an interface corresponding to any content.

[0053] 5b is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. After the task creator creates the collaboration task through the above-mentioned third task creation entry, when the first user triggers the document identifier shown in FIG. 3a, in one embodiment, as shown in FIG. 5b, the content interface shown in the shared document when the task creator creates the collaboration task through the third task creation entry can be displayed to the first user as the task creation source interface. As shown in FIG. 5b, when creating the collaboration task, content related to the Dragon Boat Festival holiday is displayed in the shared document in FIG. 5a.

[0054] In another embodiment, the collaboration task is created based on a fourth task creation entry associated with document content in the shared document by the task creator, and the content interface is an interface in which the document content is located. The task creator and the first user may be the same user or different users.

[0055] 5c is a schematic diagram of creating a collaboration task based on a shared document provided by another embodiment of the present disclosure. As shown in FIG. 5c, after selecting a portion of document content in the shared document application, multiple operation entries for the document content can be displayed, including a task creation entry for creating a collaboration task, which is the fourth task creation entry. After selecting a portion of document content in the shared document application, the task creator can create a collaboration task through the fourth task creation entry.

[0056] 5d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. After a task creator creates a collaboration task through the above-mentioned fourth task creation entry, when a first user triggers the document identifier shown in FIG. 3a, a content interface in which the document content for creating a collaboration task in the shared document is located can be displayed to the first user as the task creation source interface, as shown in FIG. 5d. In FIG. 5d, the task creation source interface contains a portion of the document content "Dragon Boat Festival Holiday Notice." The collaboration task to which the triggered task creation source identifier belongs is created based on this portion of the document content. Therefore, in the task creation source interface, this portion of the document content is displayed after being processed in a specific format, such as bolding.

[0057] As can be seen from the above, when a collaboration task is created using a shared document, after a first user triggers a document identifier, the content interface of the shared document is displayed to the first user as a task creation source interface, thereby meeting the first user's need to trace back the task creation source.

[0058] In one embodiment, a task creation source of a collaboration task in the collaboration task list is an external third-party system, and the task creation source identifier is an external third-party system identifier; accordingly, displaying a task creation source interface of the collaboration task to the first user may be determining an external third-party system corresponding to the external third-party system identifier, and displaying a system interface of the external third-party system to the first user as a task creation source interface.

[0059] As shown in Figure 3a, the third collaboration task in the collaboration task list related to the first user is a collaboration task created based on an external third-party system, and its task creation source is the external third-party system. Accordingly, an external third-party system identifier is displayed below the collaboration task, and when the user triggers the external third-party system identifier, the task system can display the system interface of the external third-party system for creating the collaboration task to the first user as a task creation source interface.

[0060] In one embodiment, after determining the external third-party system corresponding to the external third-party system identifier, before displaying the system interface of the external third-party system to the first user as a task creation source interface, the system determines whether the first user has authorization to enter the external third-party system. If the first user has authorization, the system interface of the external third-party system is displayed to the first user. If the first user does not have authorization, the system determines that the first user has authorization to enter the external third-party system. Conversely, the system determines that the first user does not have authorization to enter the external third-party system. Of course, this is merely an exemplary method for determining whether the first user has authorization to enter the external third-party system. Other methods are also possible for determining whether the first user has authorization to enter the external third-party system, and are not limited thereto.

[0061] After determining that the first user has the authority to enter the external third-party system, the first user's browser can be first invoked to enter the external third-party system and jump to the system interface of the external third-party system, that is, the first user can remain in the system interface of the external third-party system, and the first user can also perform interface sharing or other system operations in the external third-party system.

[0062] In one embodiment, the collaboration task is created by an external third-party system based on a specific operation performed by a system operator in the external third-party system, and the system interface is an interface associated with the specific operation in the external third-party system. The system operator and the first user may be the same user or different users.

[0063] Specifically, after a system operator performs a specific operation in an external third-party system, the external third-party system can call an API provided by the task system to create a collaboration task based on the specific operation, and synchronize the created collaboration task with the task system. For example, after a system operator performs a ticket creation operation in an external third-party system, the external third-party system can call an API provided by the task system to create a collaboration task, and synchronize the created collaboration task with the task system.

[0064] Subsequently, after the external third-party system identifier is triggered by the first user as a task creation source identifier, an interface associated with the specific operation in the external third-party system can be displayed to the first user as a task creation source interface. Take the specific operation as an example, where the specific operation is a ticket creation operation, and the interface associated with the specific operation in the external third-party system can be a ticket details interface, and after the first user triggers the external third-party system identifier, the ticket details interface of the created ticket is displayed to the first user as a task creation source interface.

[0065] As can be seen from the above, when a collaboration task is created through an external third-party system, after a first user triggers an external third-party system identifier, the system interface of the external third-party system is displayed to the first user as a task creation source interface, thereby meeting the first user's need to trace back the task creation source.

[0066] In one embodiment, in step S108, after displaying the screening results on the collaboration task center interface of the first user, the method further includes performing a step of updating the collaboration tasks in the collaboration task list in response to an update operation on the collaboration task list of the first user, where the updated collaboration task list supports the display of collaboration tasks whose task creation sources match any one of the task creation source types.

[0067] Specifically, after the first user screens the collaboration tasks in the collaboration task list according to the task creation source type, the first user can further update the collaboration tasks in the collaboration task list, and the updated collaboration task list can display collaboration tasks whose task creation sources match any one of the task creation source types; that is, the updated collaboration task list will no longer display the screening results of the first user's screening of collaboration tasks according to the task creation source type, and the screening results are only valid before the first user updates the collaboration task list.

[0068] In one embodiment, the first user's collaboration task list displays the first user's completed collaboration tasks, and the first user performs a screening operation on the completed collaboration tasks according to a task creation source type to obtain tasks from sessions among the completed collaboration tasks through screening. Subsequently, the first user performs an update operation on the collaboration task list to update the tasks in the collaboration task list to unprocessed tasks. After the update, the collaboration task list displays all of the first user's unprocessed tasks, but does not display tasks from sessions that have not been processed based on the task screening operation previously performed by the first user.

[0069] As can be seen from this embodiment, every time the first user updates the collaboration task list, the task screening operation previously performed by the first user is disabled, for the following reason: if the task screening operation previously performed by the first user is still enabled after the first user updates the collaboration task list, the first user may forget that he or she has performed the task screening operation and easily mistake the tasks displayed in the updated task list for all the tasks obtained by the first user's update, resulting in the first user missing his or her own tasks. By disabling the task screening operation previously performed by the first user after the first user updates the task collaboration list, this prevents the first user from forgetting that he or she has performed the task screening operation and mistakenly mistake the tasks displayed in the updated task list for all his or her own tasks, thereby preventing the first user from missing his or her own collaboration tasks.

[0070] Of course, the first user's operation of updating the task collaboration list may be performed before screening the collaboration tasks according to the task creation source type, that is, after displaying the collaboration task list related to the first user, the first user can update the task collaboration list.

[0071] In one embodiment, updating the collaboration task in the collaboration task list in response to an update operation on the collaboration task list of the first user specifically includes: (a1) in response to an update operation on the collaboration task list of the first user, determining a target task display dimension for the first user to update the collaboration task list; (a2) Obtaining a collaboration task related to the first user in the target task display dimension, and updating the collaboration task in the collaboration task list with the obtained collaboration task.

[0072] In one embodiment, a user identifier of a second user having a task collaboration relationship with the first user is displayed in the collaboration task center interface of the first user, and the update operation includes a trigger operation on the user identifier of a target user among the second users.

[0073] Accordingly, determining a target task display dimension in which the first user updates the collaboration task list in response to an update operation on the collaboration task list of the first user specifically means (a11) determining the target user as the target task display dimension in which the first user updates the collaboration task list in response to the first user's trigger operation on a user identifier of the target user among the second users, and the collaboration task related to the first user in the target task display dimension is the collaboration task between the first user and the target user.

[0074] Specifically, the user identifiers of multiple second users are displayed in the collaboration task center interface of the first user, and the second users are users who have task collaboration relationships with the first user. Task collaboration relationships include, but are not limited to, task assignment relationships, task sharing relationships, task comment relationships, etc. When an update operation performed by the first user is a trigger operation on the user identifier of a target user among the second users, the target user can be used as a target task display dimension for the first user to update the collaboration task list. Accordingly, the collaboration task related to the first user in the target task display dimension refers to the collaboration task between the first user and the target user. Accordingly, the collaboration task in the collaboration task list related to the first user is updated to the collaboration task between the first user and the target user.

[0075] FIG. 6a is a schematic diagram of updating a collaboration task list provided by one embodiment of the present disclosure, and FIG. 6b is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure. As shown in FIGS. 6a and 6b, the user identifiers of multiple second users are displayed on the left side of the collaboration task center interface of a first user. When a first user triggers the identifier of a target user "Mr. Wang" among the second users in FIG. 6a, for example by clicking on his profile picture, as shown in FIG. 6b, the target user "Mr. Wang" is set as the target task display dimension, and the collaboration task in the collaboration task list related to the first user is updated to the collaboration task between the first user and Mr. Wang.

[0076] As can be seen from the above, in this embodiment, the user identifier of the second user who has a task collaboration relationship with the first user is displayed in the collaboration task center interface of the first user, and based on the first user's triggering operation on the user identifier of the target user among the second users, the collaboration task in the collaboration task list is updated to a collaboration task between the first user and the target user according to the dimension of the target user triggered by the first user, thereby meeting the need of the first user to update the collaboration task list according to the dimension of the collaboration users.

[0077] In one embodiment, task description information is displayed in a collaboration task center interface of a first user, and the update operation includes a trigger operation on target task description information of the task description information.

[0078] Accordingly, determining the target task display dimension in which the first user updates the collaboration task list in response to an update operation on the first user's collaboration task list specifically means setting the target task description information as the target task display dimension in which the first user updates the collaboration task list in response to a trigger operation on the target task description information among the first user's task description information, and the collaboration task associated with the first user in the target task display dimension is the collaboration task associated with the first user that satisfies the target task description information.

[0079] Specifically, a plurality of task description information is displayed in the collaboration task center interface of the first user. The task description information may include description information according to task type, such as "Assigned by me," "Assigned to me," "I am responsible for," or "I am following," or description information according to task attributes, such as "Task with no set time" or "Task with no assigned assignee," or description information according to task status, such as "Completed," "In progress," or "Expired." If an update operation performed by the first user is a trigger operation on target task description information among the task description information, the target task description information is used as a target task display dimension for the first user to update the collaboration task list. Accordingly, the collaboration task associated with the first user in the target task display dimension refers to the collaboration task associated with the first user that satisfies the target task description information. Accordingly, the collaboration task in the collaboration task list associated with the first user is updated to the collaboration task associated with the first user that satisfies the target task description information.

[0080] 6c is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure, and FIG. 6d is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure. As shown in FIG. 6c and FIG. 6d, multiple task description information are displayed on the left side of the collaboration task center interface of a first user. When a first user triggers the target task description information “task with no assigned assignee” in FIG. 6a, for example, upon triggering the target task description information, as shown in FIG. 6d, the target task description information “task with no assigned assignee” is used as the target task display dimension, and the collaboration task in the collaboration task list related to the first user is updated to a collaboration task related to the first user and with no assigned assignee.

[0081] As can be seen from the above, in this embodiment, multiple task description information are displayed in the collaboration task center interface of the first user, and based on the trigger operation on the target task description information among the task description information of the first user, the collaboration tasks in the collaboration task list are updated to collaboration tasks related to the first user that satisfy the target task description information according to the dimensions of the target task description information triggered by the first user, thereby meeting the needs of the first user to update the collaboration task list according to the dimensions of the task description information.

[0082] In summary, the above embodiments enable the collaboration task center interface of the first user to screen collaboration tasks according to the task creation source type in response to a screening operation by the first user to screen collaboration tasks and display the screening results; and in response to a trigger operation by the first user on the task creation source identifier, display the task creation source interface of the collaboration task to the first user, realizing tracing of the task creation source; and updating the collaboration tasks in the collaboration task list according to the target task display dimension with which the first user updates the collaboration task list, thereby realizing updating of the collaboration task list.

[0083] FIG. 7 is a structural schematic diagram of a collaboration task processing device provided in one embodiment of the present disclosure. As shown in FIG. 7, the device includes: a list display unit 71 for displaying a collaboration task list associated with the first user in the collaboration task center interface of the first user; a type determination unit 72 for determining a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to a task creation source type; a task screening unit 73 for screening collaboration tasks in the collaboration task list based on the target task creation source type; and a result display unit 74 for displaying the screening results in the collaboration task center interface of the first user.

[0084] Selectively, After displaying a collaboration task list related to the first user, obtain a task creation source identifier corresponding to a collaboration task in the collaboration task list, and display the task creation source identifier in the collaboration task list; The collaboration task creation system further includes a sorting and displaying unit for displaying a task creation source interface of the collaboration task to the first user in response to a trigger operation of the first user on the task creation source identifier.

[0085] Optionally, the task creation source of the collaboration task is a session, the task creation source identifier is a session identifier, and the source display unit is specifically used to obtain a session corresponding to the session identifier and display an interface associated with the session to the first user as the task creation source interface.

[0086] Optionally, the collaboration task is created based on a first task creation entry associated with the session by a task creator, and the interface associated with the session is an interface presented by the session when a task creator creates the collaboration task based on the first task creation entry; Or, The collaboration task is created based on a second task creation entry associated with a session message in the session by a task creator, and the interface associated with the session is the interface in which the session message is located.

[0087] Optionally, the task creation source of the collaboration task is a shared document, the task creation source identifier is a document identifier, and the source display unit is specifically used to obtain the shared document corresponding to the document identifier and display the content interface of the shared document to the first user as the task creation source interface.

[0088] Optionally, the collaboration task is created based on a third task creation entry associated with the shared document by a task creator, and the content interface is an interface presented by the shared document when the task creator creates the collaboration task based on the third task creation entry; Or, The collaboration task is created based on a fourth task creation entry associated by a task creator with document content in the shared document, and the content interface is an interface in which the document content is located.

[0089] Optionally, the task creation source of the collaboration task is an external third-party system, the task creation source identifier is an external third-party system identifier, and the source display unit is specifically used for determining the external third-party system corresponding to the external third-party system identifier and displaying the system interface of the external third-party system to the first user as the task creation source interface.

[0090] Optionally, the collaboration task is created by the external third-party system based on a specific operation performed by a system operator in the external third-party system, and the system interface is an interface associated with the specific operation in the external third-party system.

[0091] Optionally, after displaying the screening result on the collaboration task center interface of the first user, further comprising: an update unit for updating the collaboration tasks in the collaboration task list in response to an update operation on the collaboration task list of the first user; The updated collaboration task list supports displaying collaboration tasks whose task creation source matches any one task creation source type.

[0092] Optionally, the update unit specifically: In response to an update operation of the first user on the collaboration task list, determining a target task display dimension in which the first user updates the collaboration task list; It is used to obtain collaboration tasks related to the first user in the target task display dimension, and update the collaboration tasks in the collaboration task list with the obtained collaboration tasks.

[0093] Optionally, a user identifier of a second user having a task collaboration relationship with the first user is displayed in a collaboration task center interface of the first user, and the update operation includes a trigger operation on a user identifier of a target user among the second users; The update unit is specifically used to, in response to a trigger operation by the first user on a user identifier of a target user among the second users, set the target user as a target task display dimension for the first user to update the collaboration task list, and the collaboration task related to the first user in the target task display dimension is a collaboration task between the first user and the target user.

[0094] Optionally, task description information is displayed in a collaboration task center interface of the first user, and the update operation includes a trigger operation on target task description information among the task description information; The update unit is specifically used to, in response to a trigger operation on target task description information among the task description information of the first user, set the target task description information as a target task display dimension for the first user to update the collaboration task list, and the collaboration task related to the first user in the target task display dimension is the collaboration task related to the first user that satisfies the target task description information.

[0095] It should be noted that the collaboration task processing device in this embodiment can implement each process of the collaboration task processing method embodiment described above and achieve the same effects and functions, so the description will not be repeated here.

[0096] An embodiment of the present disclosure further provides an electronic device. FIG. 8 is a structural schematic diagram of an electronic device provided by an embodiment of the present disclosure. As shown in FIG. 8, the electronic device may vary greatly in terms of configuration or performance. It may include one or more processors 801 and memory 802, and one or more application programs or data may be stored in the memory 802. The memory 802 may store data for short periods or permanently. The application program stored in the memory 802 may include one or more modules (not shown), each of which may include a set of computer-executable instructions for the electronic device. Furthermore, the processor 801 may be configured to communicate with the memory 802 and execute the set of computer-executable instructions in the memory 802 for the electronic device. The electronic device may further include one or more power sources 803, one or more wired or wireless network interfaces 804, one or more input or output interfaces 805, one or more keyboards 806, etc.

[0097] In a specific embodiment, the electronic device may be a server or terminal device of an instant messaging application, and includes a processor and a memory configured to store computer-executable instructions, which, when executed by the processor, cause the processor to: displaying a collaboration task list associated with the first user in a collaboration task center interface of the first user; determining a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; A flow is implemented with a step of displaying the screening result on the collaboration task center interface of the first user.

[0098] It should be noted that the electronic device in this embodiment can implement each process of the embodiment of the collaboration task processing method described above and achieve the same effects and functions, so the description will not be repeated here.

[0099] Another embodiment of the present disclosure further provides a computer-readable storage medium for storing computer-executable instructions, which, when executed by a processor, displaying a collaboration task list associated with the first user in a collaboration task center interface of the first user; determining a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; A flow is implemented with a step of displaying the screening result on the collaboration task center interface of the first user.

[0100] It should be noted that the storage medium in this embodiment can implement each process of the embodiment of the collaboration task processing method described above, and achieve the same effects and functions, so the description will not be repeated here.

[0101] The computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, and so on.

[0102] In the 1990s, technological improvements could be clearly distinguished between hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, and switches) and software improvements (improvements to method flows). However, with the development of technology, many current method flow improvements can be considered direct improvements to hardware circuit structures. Most designers obtain the corresponding hardware circuit structures by programming the improved method flows into the hardware circuits. Therefore, it cannot be said that method flow improvements cannot be realized in hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logical function is determined by user programming. Instead of requiring chip manufacturers to design and manufacture dedicated integrated circuit chips, designers can program and "integrate" digital systems into PLDs.Furthermore, instead of manually manufacturing integrated circuit chips, such programming is now mostly accomplished using "logic compiler" software, similar to software compilers used in program development and compilation. The pre-compiled source code must also be compiled in a specific programming language, known as a hardware description language (HDL). There are not just one, but multiple HDLs, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). The most commonly used HDLs are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. It is clear to those skilled in the art that a hardware circuit embodying a method flow can be easily obtained by simply programming the method flow logically in one of the above hardware description languages ​​and programming it into an integrated circuit.

[0103] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor, a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, an embedded microcontroller, etc. Examples of controllers include, but are not limited to, microcontrollers such as the ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. A memory controller may also be implemented as part of the memory's control logic. Those skilled in the art will recognize that in addition to implementing the controller purely in the form of computer-readable program code, the controller can also achieve the same functions in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by fully logically programming method steps. Therefore, such a controller can be considered a hardware component, and the devices for implementing various functions contained therein can also be considered structures within the hardware component. Alternatively, the apparatus for realizing various functions may be considered as software modules that implement methods or as structures within hardware components.

[0104] The systems, devices, modules, or units described in the above embodiments may be specifically implemented by computer chips or entities, or may be implemented by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a mobile phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0105] For convenience of explanation, the above-described apparatus will be described by dividing it into various units according to their functions. Of course, when implementing the embodiments of the present disclosure, the functions of each unit may be realized by the same or multiple pieces of software and / or hardware.

[0106] Those skilled in the art will appreciate that one or more embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Accordingly, one or more embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, one or more embodiments of the present disclosure may take the form of a computer program product embodied in one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0107] The present disclosure has been described with reference to flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, thereby generating an apparatus for implementing the function specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams by the instructions executed by the processor of the computer or other programmable data processing device.

[0108] These computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture that includes an instruction apparatus, which implements the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0109] These computer program instructions may be loaded into a computer or other programmable data processing device to cause the computer or other programmable device to perform a series of operational steps to generate a computer-implemented process, whereby the instructions that execute on the computer or other programmable device provide steps for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0110] It should be noted that the terms "comprise," "including," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, product, or device that includes a set of elements not only includes those elements, but also includes other elements not expressly listed, or further elements inherent in such process, method, product, or device. Unless further limited, elements qualified by the phrase "comprise..." do not exclude the presence of additional identical elements in the process, method, product, or device that includes said elements.

[0111] One or more embodiments of the present disclosure may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0112] Each embodiment in the present disclosure has been described in a progressive manner, and the same or similar parts between the embodiments may be referred to, and each embodiment has been described by focusing on the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is simple, and you may refer to the relevant parts of the method embodiments.

[0113] The above is merely an example of the present application and is not intended to limit the present application. Those skilled in the art may find various modifications and variations of the present application. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present application should be included within the scope of the claims of the present application.

Claims

1. displaying a collaboration task list related to the first user in a collaboration task center interface of the first user's task system, wherein the collaboration tasks in the collaboration task list include at least one of collaboration tasks created in the task system, collaboration tasks created in an instant messaging application, collaboration tasks created in a shared document application, and collaboration tasks created in an external third-party system, wherein the task system, the instant messaging application, and the shared document application are integrated into collaboration office software; determining a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; and displaying the screening results in a collaboration task center interface of the first user.

2. After the step of displaying a collaboration task list associated with the first user, the method further comprises: obtaining a task creation source identifier corresponding to the collaboration task in the collaboration task list, and displaying the task creation source identifier in the collaboration task list; and exposing a task creation source interface of the collaboration task to the first user in response to a trigger operation of the first user on the task creation source identifier; The creation source of the collaboration task is at least one of a normal task, a session, a shared document, and an external third-party system; The collaboration task processing method of claim 1 , wherein the task creation source identifier is at least one of a normal task identifier, a session identifier, a document identifier, and an external third-party system identifier.

3. a task creation source of the collaboration task is the session, and the task creation source identifier is the session identifier; 3. The collaboration task processing method of claim 2, wherein the step of displaying a task creation source interface for the collaboration task to the first user includes the steps of obtaining a session corresponding to the session identifier and displaying an interface associated with the session as the task creation source interface to the first user.

4. the collaboration task is created based on a first task creation entry associated with the session by a task creator; the interface associated with the session is a random interface of the session or an interface that the session presents when a task creator creates the collaboration task based on the first task creation entry; Or, 4. The collaboration task processing method of claim 3, wherein the collaboration task is created based on a second task creation entry associated with a session message in the session by a task creator, and the interface associated with the session is the interface in which the session message is located.

5. a task creation source of the collaboration task is the shared document, and the task creation source identifier is the document identifier; 3. The collaboration task processing method of claim 2, wherein the step of displaying a task creation source interface of the collaboration task to the first user includes the steps of obtaining a shared document corresponding to the document identifier and displaying a content interface of the shared document to the first user as the task creation source interface.

6. the collaboration task is created based on a third task creation entry associated with the shared document by a task creator; the content interface is a random content interface of the shared document or an interface that the shared document presents when the task creator creates the collaboration task based on the third task creation entry; Or, 6. The collaboration task processing method of claim 5, wherein the collaboration task is created based on a fourth task creation entry associated by the task creator with document content in the shared document, and the content interface is an interface in which the document content is located.

7. a task creation source of the collaboration task is the external third-party system, and the task creation source identifier is the external third-party system identifier; 3. The collaboration task processing method of claim 2, wherein the step of displaying a task creation source interface of the collaboration task to the first user includes the steps of determining an external third-party system corresponding to the external third-party system identifier and displaying a system interface of the external third-party system to the first user as the task creation source interface.

8. the collaboration task is created by the external third-party system based on a specific operation performed by a system operator on the external third-party system; The collaborative task processing method of claim 7 , wherein the system interface is an interface associated with the specific operation in the external third-party system.

9. After the step of displaying the screening results in the collaboration task center interface of the first user, the method further comprises: updating the collaboration task in the collaboration task list in response to an update operation on the collaboration task list by the first user; The collaboration task processing method according to claim 1 , wherein the updated collaboration task list supports displaying collaboration tasks whose task creation sources match any one of the task creation source types.

10. The step of updating the collaboration task in the collaboration task list in response to an update operation on the collaboration task list by the first user includes: determining a target task display dimension in response to an update operation on the collaboration task list of the first user by the first user; 10. The collaboration task processing method of claim 9, further comprising: acquiring collaboration tasks related to the first user in the target task display dimension; and updating collaboration tasks in the collaboration task list with the acquired collaboration tasks.

11. a user identifier of a second user having a task collaboration relationship with the first user is displayed in a collaboration task center interface of the first user, and the update operation includes a trigger operation on a user identifier of a target user among the second users; 11. The collaboration task processing method of claim 10, wherein the step of determining a target task display dimension in which the first user updates the collaboration task list in response to an update operation on the collaboration task list of the first user includes a step of determining the target user as the target task display dimension in which the first user updates the collaboration task list in response to a trigger operation by the first user on a user identifier of a target user of the second users, and a collaboration task related to the first user in the target task display dimension is a collaboration task between the first user and the target user.

12. Task description information is displayed in a collaboration task center interface of the first user, and the update operation includes a trigger operation on target task description information among the task description information; 11. The collaboration task processing method according to claim 10, wherein the step of determining a target task display dimension in which the first user updates the collaboration task list in response to an update operation on the collaboration task list of the first user includes a step of setting the target task description information as a target task display dimension in which the first user updates the collaboration task list in response to a trigger operation on target task description information of the task description information of the first user, and a collaboration task related to the first user in the target task display dimension is a collaboration task related to the first user that satisfies the target task description information.

13. a list display unit configured to display a collaboration task list related to a first user in a collaboration task center interface of a task system of the first user, wherein collaboration tasks in the collaboration task list include at least one of collaboration tasks created in the task system, collaboration tasks created in an instant messaging application, collaboration tasks created in a shared document application, and collaboration tasks created in an external third-party system, and the task system, the instant messaging application, and the shared document application are integrated into collaboration office software; a type determination unit configured to determine a target task creation source type designated by the first user in response to a screening operation in which the first user screens collaboration tasks according to a task creation source type; a task screening unit configured to screen collaboration tasks in the collaboration task list based on the target task creation source type; a results display unit configured to display the screening results in a collaboration task center interface of the first user.

14. a processor; and a memory configured to store computer-executable instructions that, when executed by the processor, cause the processor to perform the collaboration task processing method of any one of claims 1 to 12.

15. A computer-readable storage medium configured to store computer-executable instructions that, when executed by a processor, cause the processor to implement the collaboration task processing method of any one of claims 1 to 12.

Images