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 to Chinese Patent Application No. 202210577437.6 filed on May 25, 2022, and the contents disclosed in the above-mentioned Chinese patent application are hereby incorporated by reference into this application.

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

[0003] In the field of collaboration office, a task (also called "agenda") system is a popular application. Current task systems provide users with a collaboration task center, through which users can create tasks and check all tasks related to them in the task system. Currently, users can screen collaboration tasks in the interface of the collaboration task center according to the progress of the collaboration tasks. However, such a task screening method only allows users to screen tasks according to the progress of the tasks, and the screening method is too limited, so it cannot meet the task screening needs of users, which are increasing day by day. 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 alleviates the problem that current task screening methods are too limited by screening collaboration tasks and displaying screening results in a 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 in 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 a task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; displaying the screening result in 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 in which the first user screens collaboration tasks according to a task creation source type; a task screening unit for screening collaboration tasks in the collaboration task list based on 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; and a memory configured to store computer-executable instructions that, when executed by a processor, cause the processor to perform 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 which, when executed by a processor, cause the processor to perform steps of the method according to the first aspect above. Effect of the Invention

[0009] In the embodiment of the present disclosure, firstly, display the collaboration task list related to the first user on the collaboration task center interface of the first user, then determine the target task creation source type specified by the first user in response to the screening operation of the first user screening the collaboration tasks according to the task creation source type, then screen the collaboration tasks in the collaboration task list according to the target task creation source type, and finally display the screening result on the collaboration task center interface of the first user. As can be seen from the above, the embodiment screens the collaboration tasks and displays the screening result on the collaboration task center interface of the first user in response to the screening operation of the first user screening 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 task screening needs of users that are increasing day by day, and improving the experience of users when processing collaboration tasks. [Brief description 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 creative labor. [Figure 1] 1 is a flowchart of a collaboration task processing method provided by an embodiment of the present disclosure. [Figure 2a] FIG. 2 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. 11 is a schematic diagram of screening collaboration tasks according to task creation source types provided by another embodiment of the present disclosure; [Figure 2c] FIG. 11 is a schematic diagram of screening collaboration tasks according to task creation source types provided by yet another embodiment of the present disclosure; [Figure 3a] FIG. 1 is a schematic diagram exhibiting a task creation source identifier provided by one embodiment of the present disclosure. [Figure 3b] FIG. 13 is a schematic diagram exhibiting a task creation source identifier provided by another embodiment of the present disclosure. [Figure 4a] FIG. 2 is a schematic diagram of creating a collaboration task based on a session, provided by one embodiment of the present disclosure; [Figure 4b] 1 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. 13 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 5a] FIG. 2 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. 13 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 5c] FIG. 11 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. 13 is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure. [Figure 6a] FIG. 2 is a schematic diagram of updating a collaboration task list provided by one embodiment of the present disclosure; [Figure 6b] FIG. 13 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 6c] FIG. 13 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 6d] FIG. 13 is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure; [Figure 7] FIG. 2 is a structural schematic diagram of a collaboration task processing device provided by an embodiment of the present disclosure; [Figure 8] FIG. 2 is a structural schematic diagram of an electronic device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] In order to make those skilled in the art 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 described below clearly and completely with reference to the drawings in one or more embodiments of the present disclosure, and obviously, 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 creative labor 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 inside collaboration office software. The collaboration office software is office software for in-house staff of large companies, and various applications such as instant messaging, cloud documents, audio-video conferencing, and task systems are integrated into the collaboration office software, which greatly improves the efficiency of collaboration office among staff of large companies.

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

[0014] In the collaboration office software, applications other than the task system can communicate with the task system to realize the synchronization of collaboration tasks, and one implementation is as follows: The collaboration office software can provide a block-based framework, which is a standard framework, and allows any one application integrated into the collaboration office software to open internal information, convert the internal information into data in a standard format, and display the data, and the data in the standard format is combined with a view of the data in the standard format to become a component, i.e., a block. According to the block-based framework, application segments that can be flexibly displayed and interacted with in any one application integrated into the collaboration office software can be created and developed, and the application segments can be transferred between each application in the collaboration office software in the form of blocks. These blocks can be embedded and displayed in any one application integrated into the collaboration 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, other 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 a specific external third-party system other than the collaboration office software, such as a ticket system, after a user performs a specific 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, the collaboration task in the task system may be created by the user in the task system, may be created by the user in other applications other than the task system in the collaboration office software, or may be created by the user in an external third-party system, so the collaboration task in the 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 the current task screening method is 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 of the first user screening 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 in the collaboration task center interface of the first user.

[0023] In the embodiment of the present disclosure, firstly, display the collaboration task list related to the first user on the collaboration task center interface of the first user, then determine the target task creation source type specified by the first user in response to the screening operation of the first user screening the collaboration tasks according to the task creation source type, then screen the collaboration tasks in the collaboration task list according to the target task creation source type, and finally display the screening result on the collaboration task center interface of the first user. As can be seen from the above, the embodiment screens the collaboration tasks and displays the screening result on the collaboration task center interface of the first user in response to the screening operation of the first user screening 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 task screening needs of users that are increasing day by day, and improving the experience of users when processing collaboration tasks.

[0024] In one embodiment, for a collaboration task in the task system of the first user, its task creation source type includes, but is not limited to, normal task, session, shared document, external third-party system, etc. A collaboration task with a task creation source type of "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 collaboration office software of the first user, or may be located in the collaboration task center interface of the task system of the first user.

[0025] A collaboration task with a task creation source type of "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 the collaboration task may be created based on a task creation entry provided in the session. The task creation entry provided in the session may be located in a sidebar of the session or near a 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 a part of the document content in the shared document, or the collaboration task 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 creating a collaboration task 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] Fig. 2a is a schematic diagram of screening collaboration tasks according to a task creation source type provided by an 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 to other users by the first user, etc.

[0029] The upper right corner of the collaboration task center interface of the first user has a control "Source" which indicates screening collaboration tasks according to the task creation source type, and after the first user triggers the control, multiple drop-down options shown in FIG. 2b can be displayed, each drop-down option represents one task creation source type, and the first user can select a target task creation source type from these multiple drop-down options, and in the case of FIG. 2b, the first user selects "Session" as the target task creation source type. Then, the task system screens collaboration tasks in the displayed collaboration task list according to the target task creation source type selected by the first user, and can display the screening result in the collaboration task center interface of the first user, specifically, in the collaboration task list associated with the first user. In FIG. 2c, the screened collaboration tasks are presented to the first user by displaying the collaboration tasks with the task creation source type of "Session" in the collaboration task list associated with the first user.

[0030] In Fig. 2b, the first user may select all the various task creation source types with one click, and 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 include obtaining a task creation source identifier corresponding to a collaboration task in the collaboration task list, displaying the task creation source identifier in the collaboration task list, and displaying 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 displaying a task creation source identifier provided by an embodiment of the present disclosure. As shown in FIG. 3a, a computer-side task system is taken as an example, and in a collaboration task list related to a first user, a task creation source identifier of each collaboration task in the collaboration task list is displayed, and the task creation source is consistent with 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, so that 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, and in response to the triggering operation, the task system can display to the first user a task creation source interface of 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, taking a task system on a mobile phone side as an example, in a collaboration task list related to a first user, the task creation source identifier of each collaboration task in the collaboration task list 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, exposing a task creation source interface of the collaboration task to the first user may be to obtain a session corresponding to the session identifier and expose 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, and accordingly, a session identifier is displayed below the collaboration task, and when a 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 the session identifier, before displaying an interface associated with the session to the first user, determine whether the first user has permission to view the session, and if so, display the interface associated with the session to the first user, and if not, present the first user with a message that the session cannot be viewed. If the first user is a session member in the session, determine that the first user has permission to view the session, and if the first user is not a session member in the session, determine that the first user does not have 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 there can be other methods for determining whether the first user has permission to view the session, and the present invention is not limited thereto.

[0037] After determining that the first user has the authority to view the session, first, invoke an instant messaging application in the collaboration office software of the first user to open the session, and present the interface associated with the session to the first user in the opened session, i.e., the first user can stay 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 a method of 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, a task creation entry is displayed in both the charm bar of the session and the “+” pop-up list of the message input box of the session, and 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 the task creator creates a collaboration task via 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 an interface corresponding to any chat content.

[0041] Fig. 4b is a schematic diagram of a task creation source interface provided by an embodiment of the present disclosure, 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, as shown in Fig. 4b, 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, when creating the collaboration task, each session member in Fig. 4a is discussing the location where the meeting will be held.

[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, and the task creation entry 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] Fig. 4d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure, after the task creator creates a collaboration task based on the above 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 a 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 has a session message "Let's hold a meeting at 3 o'clock tomorrow to discuss", and the collaboration task to which the triggered task creation source identifier belongs is created based on the session message, so 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, a 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, and accordingly, displaying a task creation source interface of the collaboration task to the first user may be to obtain a 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 FIG. 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, and accordingly, a document identifier is displayed below the collaboration task, and when a 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 the 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, determine whether the first user has the authority to view the shared document, and if so, display the content interface of the shared document to the first user, and if not, indicate to the first user that the shared document cannot be viewed. If the first user is the creator or designated shared recipient of the shared document, determine that the first user has the authority to view the shared document, and conversely, determine that the first user does not have the authority to view the shared document. Of course, this is only an exemplary method for determining whether the first user has the authority to view the shared document, and there can be other methods for determining whether the first user has the authority to view the shared document, and the method is not limited here.

[0049] After determining that the first user has the authority to view the shared document, first, invoke a shared document application in the collaboration office software of the first user to open the shared document, and present the content interface of the shared document to the first user in the opened shared document, i.e., the first user can stay on the content interface of the shared document, and the first user can also continue to view the shared document by scrolling the screen. 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, and 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 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] Fig. 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 a task creation source interface. As shown in Fig. 5b, when creating a collaboration task, the shared document in Fig. 5a displays content related to the Dragon Boat Festival holiday.

[0054] In another embodiment, the collaboration task is created based on a fourth task creation entry associated with the 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 a 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] Fig. 5d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure, after the task creator creates a collaboration task through the above-mentioned fourth task creation entry, when the 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 a task creation source interface, as shown in Fig. 5d. In Fig. 5d, there is a part of the document content "Dragon Boat Festival Holiday Notice" in the task creation source interface, and the collaboration task to which the triggered task creation source identifier belongs is created based on this part of the document content, so in the task creation source interface, this part of the document content is displayed after being processed in a specific format, such as bold processing.

[0057] As can be seen from the above, when a collaboration task is created through a shared document, after a first user triggers a document identifier, the content interface of the shared document can be displayed to the first user as a task creation source interface, thereby meeting the needs of the first user 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, and accordingly, exhibiting 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 exhibiting a system interface of the external third party system to the first user as a task creation source interface.

[0059] As shown in FIG. 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, and accordingly, an external third-party system identifier is displayed below the collaboration task, and when a 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, determine whether the first user has the authority to enter the external third-party system, and if so, display the system interface of the external third-party system to the first user, and if not, present the first user with the inability to enter the external third-party system. If the first user is a registered user of the external third-party system, determine that the first user has the authority to enter the external third-party system, and conversely, determine that the first user does not have the authority to enter the external third-party system. Of course, this is only an exemplary method for determining whether the first user has the authority to enter the external third-party system, and there are other methods for determining whether the first user has the authority to enter the external third-party system, and the method is not limited here.

[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 particular operation performed by a system operator in the external third-party system, and the system interface is an interface associated with the particular 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] Then, 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 that the specific operation is a ticket creation operation, 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 can be displayed to the first user as a task creation source interface, thereby meeting the need of the first user to trace back the task creation source.

[0066] In one embodiment, in step S108, after displaying the screening results in 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 screening the 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 collaboration task list of a first user 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 completed collaboration tasks from sessions through screening. Then, the first user performs an update operation on the collaboration task list to update the tasks in the collaboration task list to unprocessed tasks, so that the updated collaboration task list displays all unprocessed tasks of the first user without displaying tasks from sessions that are not 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 invalidated, and the reason for this is as follows: if the task screening operation previously performed by the first user is still valid after the first user updates the collaboration task list, the first user is likely to mistake the tasks displayed in the updated task list for all the tasks obtained by the first user's update if he forgets that he has performed the task screening operation, and thus misses his own tasks; by invalidating the task screening operation previously performed by the first user after the first user updates the task collaboration list, it is possible to prevent the first user from forgetting that he has performed the task screening operation and mistakenly thinking that the tasks displayed in the updated task list are all his own tasks, and prevent the first user from missing his own collaboration tasks.

[0070] Of course, the operation of the first user 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 first user's collaboration task list, determining a target task display dimension for the first user to update the collaboration task list; (a2) Obtain a collaboration task related to the first user in a target task display dimension, and update the collaboration task in the collaboration task list to 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 a 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 includes (a11) determining, in response to a trigger operation by the first user on a user identifier of the target user among the second users, the target user as the target task display dimension in which the first user updates the collaboration task list, and the collaboration task associated with 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 a plurality of second users are displayed in the collaboration task center interface of the first user, and the second users are users having a task collaboration relationship with the first user. The task collaboration relationship includes, but is not limited to, a task assignment relationship, a task sharing relationship, a task comment relationship, etc. When the update operation performed by the first user is taken as a trigger operation on the user identifier of the target user among the second users, the target user can be taken as the target task display dimension for the first user to update the collaboration task list, and 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, update the collaboration task in the collaboration task list related to the first user 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 FIG. 6a and FIG. 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 the profile photo, 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 triggering operation of the first user 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, so as to meet 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 a target task description information of the task description information.

[0078] 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 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 target task description information of the first user's task description information, 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.

[0079] Specifically, a plurality of task description information are exhibited in the collaboration task center interface of the first user, and the task description information may include description information according to a task type such as "assigned by me", "assigned to me", "responsible for me", "following by me", or may include description information according to a task attribute such as "task with no time fixed" or "task with no assigned person", or may include description information according to a task state such as "completed", "in progress", or "expired". If the update operation performed by the first user is a trigger operation on a target task description information among the task description information, the target task description information is taken as a target task display dimension for the first user to update the collaboration task list, and accordingly, the collaboration task related to the first user in the target task display dimension refers to the collaboration task related to the first user that satisfies the target task description information. Accordingly, the collaboration task in the collaboration task list related to the first user is updated to the collaboration task related to the first user that satisfies the target task description information.

[0080] FIG. 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 person” 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 person” is taken 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 person.

[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 dimension of the target task description information triggered by the first user, so as to meet the need of the first user to update the collaboration task list according to the dimension of the task description information.

[0082] In summary, the above embodiments enable the first user to screen collaboration tasks and display the screening results in the collaboration task center interface of the first user in response to a screening operation in which the first user screens collaboration tasks according to the task creation source type, and to 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, thereby realizing tracing of the task creation source, and to update the collaboration tasks in the collaboration task list according to the target task display dimension in 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 related to the first user in a 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 a 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 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 for 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.

[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 for 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.

[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 a 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 with document content in the shared document by a task creator, 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 particular operation performed by a system operator in the external third party system, and the system interface is an interface associated with the particular 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 collaboration tasks in the collaboration task list in response to an update operation of the first user on the collaboration task list; After updating, the collaboration task list supports displaying collaboration tasks whose task creation source matches any one of the task creation source types.

[0092] Optionally, the update unit specifically: determining a target task display dimension in response to an update operation of the first user on the collaboration task list for the first user to update 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 of the second user; The update unit is specifically used for, in response to a trigger operation of the first user on a user identifier of a target user among the second users, making the target user a target task display dimension for the first user to update the collaboration task list, 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.

[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 of 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 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.

[0095] It should be noted that the collaboration task processing device in this embodiment can realize 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.

[0096] An embodiment of the present disclosure further provides an electronic device, and 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, and may include one or more processors 801 and memory 802, and may store one or more application programs or data in the memory 802. The memory 802 may store short-term or permanently. The application program stored in the memory 802 may include one or more modules (not shown), and each module may include a set of computer-executable instructions in the electronic device. Furthermore, the processor 801 may be provided to communicate with the memory 802 and execute the set of computer-executable instructions in the memory 802 in 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 a 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 a 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 realize 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 a task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; A flow is realized 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 realize each process of the embodiment of the collaboration task processing method described above, and achieve the same effects and functions, so that 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, improvements to technology 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 regarded as 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., Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by the user programming the device. There is no need for chip manufacturers to design and manufacture dedicated integrated circuit chips, and designers program and "integrate" digital systems into PLDs.Also, nowadays, instead of manually manufacturing integrated circuit chips, such programming is realized by "logic compiler" software similar to software compilers used in program development and compilation, and the source code before compilation must also be compiled in a specific programming language, which is called Hardware Description Language (HDL). There are not only one but multiple HDLs, such as 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, RHDL (Ruby Hardware Description Language), etc., and the most commonly used at present are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. It is also clear to those skilled in the art that a hardware circuit that realizes a logical method flow can be easily obtained by simply programming a method flow in some of the above hardware description languages ​​and programming it into an integrated circuit.

[0103] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, Application Specific Integrated Circuits (ASICs), programmable logic controllers, embedded microcontrollers, etc., examples of controllers include, but are not limited to, microcontrollers such as ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may be implemented as part of the control logic of the memory. Those skilled in the art will appreciate that in addition to implementing the controller in the form of a pure computer readable program code, the controller may also realize the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. by fully logically programming the method steps. Thus, such a controller may be considered as a hardware component, and the devices for implementing various functions contained therein may also be considered as structures within the hardware component. Alternatively, the apparatus for implementing various functions may be viewed as either software modules implementing the methods or structures within hardware components.

[0104] The system, device, module or unit described in the above embodiments may be specifically realized by a computer chip or entity, or may be realized by a product having a certain function. 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-mentioned device 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 can be realized by the same or multiple pieces of software and / or hardware.

[0106] It will be appreciated by those skilled in the art that one or more embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Thus, 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. Also, 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.) that contain computer usable program code.

[0107] The present disclosure has been described with reference to flowcharts and / or block diagrams of methods, devices (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 a function specified in one or more flows of the flowcharts and / or one or more blocks of 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 generate 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 executed 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 terms such as "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 includes elements inherent to such process, method, product, or device. Unless further limited, an element qualified by the phrase "comprises" does not exclude the presence of additional identical elements in the process, method, product, or device that includes the element.

[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 be implemented 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 is described in a progressive manner, and the same or similar parts between each embodiment may be referred to each other, and each embodiment is described by focusing on the differences from other embodiments. In particular, the system embodiment is basically similar to the method embodiment, so the description is simple, and the relevant parts may be referred to part of the description of the method embodiment.

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

Claims

1. 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 a task creation source type; screening collaboration tasks in the collaboration task list based on the target task creation source type; 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 a collaboration task in the collaboration task list, and displaying the task creation source identifier in the collaboration task list; 2. The collaboration task processing method of claim 1, further comprising: 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.

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

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 an interface in which the session message is located.

5. a task creation source of the collaboration task is a shared document, and the task creation source identifier is a 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, The collaboration task processing method of claim 5 , wherein 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.

7. a task creation source of the collaboration task is an external third-party system, and the task creation source identifier is an external third-party system identifier; 3. The collaboration task processing method of claim 2, wherein the step of exposing 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 exposing 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 particular operation performed by a system operator on the external third-party system; The method of claim 7 , wherein the system interface is an interface associated with the particular operation in the external third-party system.

9. After the step of displaying the screening results in a 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 of the first user; The collaboration task processing method according to any one of claims 1 to 8, wherein the collaboration task list after updating supports displaying collaboration tasks whose task creation source matches any one task creation source type.

10. The step of updating the collaboration task in the collaboration task list in response to an update operation on the collaboration task list of the first user includes: determining a target task display dimension in response to an update operation of the first user on the collaboration task list in which the first user updates the collaboration task list; 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 to 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 of 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 of the first user on the collaboration task list includes a step of setting the target user as a target task display dimension in which the first user updates the collaboration task list in response to a trigger operation of the first user on a user identifier of a target user among 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 of 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 of the first user on the collaboration task list 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 of the first user on target task description information among the task description information, 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 associated with the first user in a collaboration task center interface of the first user; 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 result 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 which, 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 which, when executed by a processor, cause the processor to implement a collaboration task processing method according to any one of claims 1 to 12.

Images