WO2023226891A1 - 协作任务处理方法、装置、设备及计算机可读存储介质 - Google Patents

协作任务处理方法、装置、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2023226891A1
WO2023226891A1 PCT/CN2023/095271 CN2023095271W WO2023226891A1 WO 2023226891 A1 WO2023226891 A1 WO 2023226891A1 CN 2023095271 W CN2023095271 W CN 2023095271W WO 2023226891 A1 WO2023226891 A1 WO 2023226891A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
user
collaboration
interface
collaborative
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/095271
Other languages
English (en)
French (fr)
Inventor
吴丹妮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zitiao Network Technology Co Ltd
Original Assignee
Beijing Zitiao Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zitiao Network Technology Co Ltd filed Critical Beijing Zitiao Network Technology Co Ltd
Priority to US18/847,094 priority Critical patent/US12346540B2/en
Priority to JP2024554637A priority patent/JP7753565B2/ja
Publication of WO2023226891A1 publication Critical patent/WO2023226891A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management

Definitions

  • Embodiments of the present disclosure relate to a collaborative task processing method, device, equipment and computer-readable storage medium.
  • task also known as "to-do"
  • the existing task system will provide users with a collaborative task center, through which users can create tasks and view all tasks related to themselves in the task system.
  • users can filter collaboration tasks on the interface of the collaboration task center according to their progress.
  • this task filtering method only allows users to filter tasks according to task progress.
  • the filtering method is too limited and cannot meet users' increasing task filtering needs.
  • Embodiments of the present disclosure provide a collaborative task processing method, device, equipment and computer-readable storage medium, which can respond to the first user's screening of collaborative tasks according to the task creation source type in the first user's collaborative task center interface. Operation, filter collaboration tasks and display the filtering results, thereby alleviating the problem that the current task filtering method is too limited, meeting users' increasing task filtering needs, and improving users' experience in processing collaborative tasks.
  • an embodiment of the present disclosure provides a collaborative task processing method, including:
  • collaboration task center interface of the first user display a list of collaboration tasks related to the first user
  • the filtering results are displayed in the collaboration task center interface of the first user.
  • an embodiment of the present disclosure provides a collaborative task processing device, including:
  • a list display unit configured to display a list of collaboration tasks related to the first user in the collaboration task center interface of the first user
  • a type determination unit configured to determine the target task creation source type specified by the first user in response to the first user's filtering operation of filtering the collaborative tasks according to the task creation source type
  • a task screening unit configured to filter collaboration tasks in the collaboration task list according to the target task creation source type
  • the result display unit is configured to display the filtering results in the collaboration task center interface of the first user.
  • an electronic device including:
  • a memory configured to store computer-executable instructions that, when executed by a processor, cause the processor to implement the steps of the method described in the first aspect.
  • an embodiment of the present disclosure provides a computer-readable storage medium.
  • the computer-readable storage medium is used to store computer-executable instructions. When executed by a processor, the computer-executable instructions implement the above-mentioned first step. The steps of the method described in this aspect.
  • a list of collaboration tasks related to the first user is displayed, and then, in response to the first user's filtering operation of filtering the collaboration tasks according to the task creation source type, it is determined
  • the first user specifies the target task creation source type, and then filters the collaboration tasks in the collaboration task list according to the target task creation source type.
  • the filtering results are displayed in the collaboration task center interface of the first user. It can be seen that through this embodiment, in the first user's collaboration task center interface, in response to the first user's filtering operation of filtering collaboration tasks according to the task creation source type, the collaboration tasks can be filtered and the filtering results can be displayed, thereby alleviating the current problem.
  • the task filtering method is too limited to meet users' increasing task filtering needs and improve users' experience in handling collaborative tasks.
  • Figure 1 is a schematic flowchart of a collaborative task processing method provided by an embodiment of the present disclosure
  • Figure 2a is a schematic diagram of filtering collaboration tasks according to task creation source type provided by an embodiment of the present disclosure
  • Figure 2b is a schematic diagram of filtering collaboration tasks according to task creation source types provided by another embodiment of the present disclosure.
  • Figure 2c is a schematic diagram of filtering collaboration tasks according to task creation source type provided by yet another embodiment of the present disclosure.
  • Figure 3a is a schematic diagram showing a task creation source identification provided by an embodiment of the present disclosure
  • Figure 3b is a schematic diagram showing a task creation source identification provided by another embodiment of the present disclosure.
  • Figure 4a is a schematic diagram of creating a collaboration task based on a session according to an embodiment of the present disclosure
  • Figure 4b is a schematic diagram of a task creation source interface provided by an embodiment of the present disclosure.
  • Figure 4c is a schematic diagram of creating a collaboration task based on a session provided by another embodiment of the present disclosure.
  • Figure 4d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • Figure 5a is a schematic diagram of creating a collaboration task based on a shared document according to an embodiment of the present disclosure
  • Figure 5b is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • Figure 5c is a schematic diagram of creating a collaborative task based on a shared document provided by another embodiment of the present disclosure.
  • Figure 5d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • Figure 6a is a schematic diagram of updating a collaboration task list provided by an embodiment of the present disclosure.
  • Figure 6b is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure.
  • Figure 6c is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure.
  • Figure 6d is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure.
  • Figure 7 is a schematic structural diagram of a collaborative task processing device provided by an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • the collaborative task center involved in various embodiments of the present disclosure is located in a task system, and the task system may be an application located within collaborative office software.
  • Collaborative office software is a kind of office software for internal employees of large enterprises.
  • Collaborative office software integrates instant messaging, cloud documents, audio and video conferencing, task systems and other applications, which greatly improves the efficiency of collaborative office work among employees of large enterprises. .
  • collaborative office software users can create collaborative tasks in the task system, or in other applications other than the task system in collaborative office software, such as instant messaging and cloud documents.
  • collaborative office software other applications other than the task system are connected to the task system, and collaborative tasks created by users in other applications other than the task system can be synchronized to the task system.
  • collaborative office software can provide a set of block-based frameworks.
  • the block-based framework is a set of standards.
  • the framework allows any application integrated with the collaborative office software to open up internal information, convert the internal information into a piece of data in a standard format and display the data.
  • the data in a standard format is combined with the view of the data in a standard format. Together they are components, which are blocks.
  • a flexible and interactive application fragment can be created and developed on any application integrated with the collaborative office software, and the application fragment can be transferred between various applications in the collaborative office software in the form of blocks. .
  • These blocks can be embedded and displayed in any application integrated with the collaborative office software.
  • different applications embed and display the same application fragment, they essentially embed and display the same block.
  • other applications other than the task system in collaborative office software can create collaboration tasks based on the framework of this block, and flow the collaboration task to the task system in the form of blocks, so that the task system can embed and display the collaboration task.
  • the external third-party system can call the task system to provide The API (Application Programming Interface, application program interface) creates collaborative tasks and synchronizes collaborative tasks to the task system.
  • API Application Programming Interface, application program interface
  • collaborative tasks in the task system can be created by users in the task system, or they can be created by users in other applications other than the task system in collaborative office software, or they can be created by users in external third-party systems. Therefore, users' collaborative tasks in the task system have multiple sources of creation, including but not limited to the above-mentioned task system, instant messaging, cloud documents, audio and video conferencing, external third-party systems, etc.
  • an embodiment of the present disclosure provides a collaboration task processing method that can respond to the first user's filtering operation of filtering collaboration tasks according to the task creation source type in the collaboration task center interface of the first user's task system. Screen collaboration tasks and display the screening results, thereby alleviating the problem that the current task screening method is too limited, meeting users' increasing task screening needs, and improving users' experience in processing collaborative tasks.
  • FIG. 1 is a schematic flowchart of a collaborative task processing method provided by an embodiment of the present disclosure. As shown in Figure 1, the process includes the following steps:
  • Step S102 Display a list of collaboration tasks related to the first user in the collaboration task center interface of the first user;
  • Step S104 in response to the first user's filtering operation of filtering collaborative tasks according to the task creation source type, determining the target task creation source type specified by the first user;
  • Step S106 filter the collaboration tasks in the collaboration task list according to the target task creation source type
  • Step S108 Display the filtering results in the collaboration task center interface of the first user.
  • a list of collaboration tasks related to the first user is displayed, and then, in response to the first user's filtering operation of filtering the collaboration tasks according to the task creation source type, it is determined
  • the first user specifies the target task creation source type, and then filters the collaboration tasks in the collaboration task list according to the target task creation source type.
  • the filtering results are displayed in the collaboration task center interface of the first user. It can be seen that through this embodiment, in the first user's collaboration task center interface, in response to the first user's filtering operation of filtering collaboration tasks according to the task creation source type, the collaboration tasks can be filtered and the filtering results can be displayed, thereby alleviating the current problem.
  • the task filtering method is too limited to meet users' increasing task filtering needs and improve users' experience in handling collaborative tasks.
  • the task creation source types of the first user's collaborative tasks in the task system include but are not limited to common tasks, sessions, shared documents, external third-party systems, etc.
  • mission creation Collaboration tasks whose creation source type is "normal task” are collaboration tasks created through the task creation entrance provided by the task system or the shortcut keys provided by the task system.
  • the task creation entrance provided by the task system may be located in the main interface of the first user's collaborative office software, or in the collaborative task center interface of the first user's task system.
  • Collaboration tasks whose task creation source type is "session” are collaboration tasks created through sessions in instant messaging applications integrated with collaborative office software.
  • the task creation entry provided in the session can be located on the sidebar of the session, or near the message input box of the session.
  • Collaboration tasks whose task creation source type is "shared document” are collaboration tasks created through a shared document application integrated with collaborative office software (i.e., the above-mentioned cloud document application).
  • the collaboration task can be created based on part of the document content in the shared document, or based on the task creation entry provided in the shared document application.
  • the task creation entrance provided in the shared document application may be located in the sidebar of the interface of the shared document application.
  • Collaboration tasks whose task creation source type is "external third-party system” are collaboration tasks created through a specific external third-party system associated with collaborative office software.
  • the user can perform a specific operation in the external third-party system.
  • the external third-party system creates a collaboration task by calling the API interface provided by the task system and synchronizes the collaboration task to in the mission system.
  • Figure 2a is a schematic diagram of filtering collaboration tasks according to task creation source type provided by one embodiment of the present disclosure.
  • Figure 2b is a schematic diagram of filtering collaboration tasks according to task creation source type provided by another embodiment of the present disclosure.
  • Figure 2c is another embodiment of the present disclosure.
  • the embodiment provides a schematic diagram of filtering collaboration tasks according to task creation source type.
  • a collaboration task list related to the first user is displayed, and the collaboration task list related to the first user includes collaboration tasks related to the first user, and
  • the collaboration tasks related to the first user may be collaboration tasks assigned by other users to the first user, or collaboration tasks assigned by the first user to other users, etc.
  • each drop-down option represents a task creation source type
  • the first The user can select the target task creation source type from these multiple drop-down options.
  • the first user selects "session” as the target task creation source type.
  • the task system filters the collaboration tasks in the displayed collaboration task list according to the target task creation source type selected by the first user, and displays the filtering results in the collaboration task center interface of the first user. Specifically, it can be displayed in in the collaborative task list related to the first user.
  • collaboration tasks whose task creation source type is "session” are displayed in the collaboration task list related to the first user, thereby presenting the filtered collaboration tasks to the first user.
  • the first user can select all types of task creation sources with one click, and can also clear the all-select mode with one click. After the first user selects one or more task creation source types, the selected types are displayed with corresponding marks, and the number of types selected by the first user is displayed on the task collaboration center interface.
  • Figure 3a is a schematic diagram showing a task creation source identifier provided by an embodiment of the present disclosure.
  • the task creation source identifier of each collaboration task.
  • the task creation source is consistent with the task creation source type. They both include at least one of ordinary tasks, sessions, shared documents, and external third-party systems. Therefore, the task creation source identifier also includes the corresponding common tasks. At least one of the common task identifier, the session identifier corresponding to the session, the shared document identifier corresponding to the shared document, and the external third-party system identifier corresponding to the external third-party system.
  • the first user can trigger the task creation source identification, for example, click the task creation source identification.
  • the task system can display the task creation source interface of the collaborative task to which the triggered task creation source identification belongs to the first user.
  • Figure 3b is a schematic diagram showing a task creation source identifier provided by another embodiment of the present disclosure. As shown in Figure 3b, taking the task system on the mobile phone as an example, in the collaboration task list related to the first user, the collaboration task list is displayed The task creation source ID for each collaboration task.
  • the task creation source of the collaboration task in the collaboration task list is the session; the task creation source identifier is the session identifier; accordingly, the task creation source of the collaboration task is displayed to the first user.
  • the task creation source identifier is the session identifier; accordingly, the task creation source of the collaboration task is displayed to the first user.
  • the first collaboration task in the collaboration task list related to the first user is a collaboration task created based on the session.
  • the task creation source is the session.
  • Session ID Correspondingly, below the collaboration task, there is Session ID. If the user triggers the session ID, the task system can display the associated interface of the session used to create the collaboration task as the task creation source interface to the first user.
  • the session's associated interface is displayed to the first user. If there is no associated interface, it will prompt the first user that the session cannot be browsed.
  • the first user is a session member in the session, it is determined that the first user has the permission to browse the session; if the first user is not a session member in the session, it is determined that the first user does not have the permission to browse the session. .
  • this is just a schematic way to determine whether the first user has the permission to browse the session. There can also be other ways to determine whether the first user has the permission to browse the session, which is not limited here.
  • the instant messaging application can be called in the first user's collaborative office software to open the session, and the associated interface of the session is presented to the first user in the opened session, that is, the first user can When a user stays on the associated interface of the session, the first user can also continue to send session messages in the session. In this case, the session's associated interface can be obtained by scrolling the session.
  • the collaboration task is created by the task creator based on the first task creation entry associated with the session, and the associated interface of the session is a random interface of the session, or when the collaboration task is created by the task creator based on the first task creation entry, The interface presented by the session.
  • the task creator and the first user may be the same user or different users.
  • Figure 4a is a schematic diagram of creating a collaboration task based on a session provided by an embodiment of the present disclosure. As shown in Figure 4a, in a session, in the pull-down list of "+" on the right sidebar of the session and the message input box of the session, Both task creation entrances are displayed. These two task creation entrances are the first task creation entrance. The task creator can create collaboration tasks through the first task creation entrance in the session.
  • a random interface of the session can be displayed as a task creation
  • the source interface is provided to the first user. Among them, you can open the meeting
  • the random interface of the session can be obtained by using the chat method.
  • the random interface of the session can be the interface obtained immediately after opening the session, or can be the interface corresponding to any chat content.
  • Figure 4b is a schematic diagram of a task creation source interface provided by an embodiment of the present disclosure.
  • the task creator creates a collaboration task through the above-mentioned first task creation portal
  • the first user triggers the session identification shown in Figure 3a
  • the interface presented in the session is displayed to the first user as the task creation source interface.
  • Figure 4b when creating a collaboration task, various conversation members in Figure 4a are discussing where to hold the meeting.
  • the collaboration task is created by the task creator based on the second task creation portal associated with the session message in the session; the associated interface of the session is the interface where the session message is located.
  • the task creator and the first user may be the same user or different users.
  • Figure 4c is a schematic diagram of creating a collaboration task based on a session provided by another embodiment of the present disclosure.
  • multiple operation portals for the session message can be displayed, where It includes a task creation entrance for creating collaboration tasks, and this task creation entrance is the second task creation entrance.
  • the task creator can create a collaboration task through the second task creation portal after selecting a session message.
  • Figure 4d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • the task creator creates a collaboration task through the above-mentioned second task creation entrance
  • the interface where the session message for creating the collaboration task in the session is located can be displayed to the first user as the task creation source interface.
  • the collaboration task to which the triggered task creation source ID belongs is created based on this conversation message. Therefore, in the task creation source interface, the Conversation messages are formatted in a specific format such as bold and underlined and displayed.
  • the associated interface of the session can be displayed to the first user as the task creation source interface, thereby allowing the first user to trace the task creation source. needs.
  • the task creation source of the collaboration task in the collaboration task list is a shared document; the task creation source identifier is the document identifier; accordingly, the task creation source interface of the collaboration task is displayed to the first user, which may be: obtaining the document The corresponding shared document is identified, and the content interface of the shared document is displayed to the first user as the task creation source interface.
  • the second collaboration task in the collaboration task list related to the first user is a collaboration task created based on the shared document.
  • the task creation source is the shared document. Accordingly, below the collaboration task A document identifier is displayed. If the user triggers the document identifier, the task system can display the content interface of the shared document used to create the collaboration task as the task creation source interface to the first user.
  • the first user after obtaining the shared document corresponding to the document identifier, and before displaying the content interface of the shared document to the first user as the task creation source interface, it is determined whether the first user has permission to browse the shared document. If so, , then the content interface of the shared document is displayed to the first user; if not, the first user is prompted that the shared document cannot be browsed. Wherein, if the first user is the creator of the shared document or the designated sharing recipient, it is determined that the first user has the permission to browse the shared document; otherwise, it is determined that the first user does not have the permission to browse the shared document. Of course, this is just a schematic way to determine whether the first user has the permission to browse the shared document. There can also be other ways to determine whether the first user has the permission to browse the shared document, which is not limited here.
  • the shared document application can be called in the first user's collaborative office software 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, even if the first user stays on the content interface of the shared document, the first user can continue to scroll the screen to browse the shared document.
  • the content interface of the shared document can be obtained by scrolling the shared document.
  • the collaboration task is created by the task creator based on the third task creation entry associated with the shared document;
  • the content interface is a random content interface of the shared document, or when the collaboration task is created by the task creator based on the third task creation entry,
  • the interface presented by the shared document; the task creator and the first user can be the same user or different users.
  • Figure 5a is a schematic diagram of creating a collaborative task based on a shared document provided by an embodiment of the present disclosure.
  • a task creation entry is displayed in the right sidebar of the content interface of the shared document.
  • the task creation portal is a third task creation portal.
  • the task creator can create collaboration tasks through the third task creation portal in the shared document application.
  • the random content interface of the shared document can be displayed, as The task creation source interface is provided to the first user.
  • the random content interface of the shared document can be obtained by opening the shared document.
  • the random content interface of the shared document can be obtained by opening the shared document.
  • the content interface can be the content interface obtained after opening the shared document, and can be an interface corresponding to any content.
  • Figure 5b is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • the task creator creates a collaboration task through the above-mentioned third task creation portal
  • the first user triggers the document identification as shown in Figure 3a
  • the content interface presented by the shared document is displayed to the first user as the task creation source interface.
  • the shared document in Figure 5a is displaying content about the Dragon Boat Festival holiday.
  • the collaboration task is created by the task creator based on the fourth task creation entry associated with the document content in the shared document; the content interface is the interface where the document content is located.
  • the task creator and the first user may be the same user or different users.
  • Figure 5c is a schematic diagram of creating a collaboration task based on a shared document provided by another embodiment of the present disclosure.
  • a shared document application after a certain part of the document content is selected, a variety of operations for the document content can be displayed.
  • the portal includes a task creation portal for creating collaboration tasks.
  • This task creation portal is the fourth task creation portal.
  • the task creator can create a collaboration task through the fourth task creation portal after selecting a certain part of the document content.
  • Figure 5d is a schematic diagram of a task creation source interface provided by another embodiment of the present disclosure.
  • the task creator creates a collaboration task through the fourth task creation entrance, if the first user triggers the document identification shown in Figure 3a, Then, as shown in Figure 5d, the content interface in the shared document where the document content used to create the collaboration task is located can be displayed to the first user as the task creation source interface.
  • the document content "Dragon Boat Festival Holiday Notice” in the task creation source interface.
  • the collaboration task to which the triggered task creation source ID belongs is created based on this part of the document content. Therefore, in the task creation source interface, this part of the document The content is displayed after being processed in a specific format such as bold processing.
  • the task creation source of the collaboration task in the collaboration task list is an external third-party system;
  • the task creation source identifier is the external third-party system identifier; accordingly, the task creation source interface of the collaboration task is displayed to the first user, It can be: determine the external third-party system corresponding to the external third-party system identifier, and use the system interface of the external third-party system as a task to create a source interface display. shown to the first user.
  • 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.
  • the task creation source is the external third-party system. Accordingly, in this An external third-party system identifier is displayed below the collaboration task. If the user triggers the external third-party system identifier, the task system can display the system interface of the external third-party system used to create the collaboration task as the task creation source interface to the first user. .
  • the system interface of the external third-party system will be displayed to the first user. If there is no permission, the first user will be prompted that he cannot enter the external third-party system.
  • the first user is a registered user of the external third-party system, it is determined that the first user has the authority to enter the external third-party system; otherwise, it is determined that the first user does not have the authority to enter the external third-party system.
  • this is just a schematic way to determine whether the first user has the authority to enter the external third-party system.
  • the first user's browser can be called to enter the external third-party system and jump to the system interface of the external third-party system, that is, even if the first user stays in For the system interface of an external third-party system, the first user can also perform interface jumps or other system operations in the external third-party system.
  • the collaboration task is created by the external third-party system based on a specific operation performed by the 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.
  • the external third-party system can call the API provided by the task system to create a collaboration task based on the specific operation, and synchronize the created collaboration task to the task system.
  • the external third-party system can call the API provided by the task system to create a collaboration task and synchronize the created collaboration task to the task system.
  • the interface associated with the above-mentioned specific operation in the external third-party system can be used as the task creation source.
  • the interface is displayed to the first user. Taking a specific operation as a work order creation operation as an example, the interface associated with the specific operation in the external third-party system can be the work order details interface. After the first user triggers the identification of the external third-party system, the created work order will be The work order details interface is displayed to the first user as the task creation source interface.
  • step S108 after the filtering results are displayed in the collaboration task center interface of the first user, the following steps are also performed: in response to the first user's update operation on the collaboration task list, updating the collaboration task list Collaboration tasks; among them, the updated collaboration task list supports displaying collaboration tasks whose task creation source matches any task creation source type.
  • the first user can also update the collaboration tasks in the collaboration task list.
  • the updated collaboration task list can display that the task creation source matches any Collaboration tasks of this type of task creation source type, that is, the updated collaboration task list no longer displays the first user’s filtering results of filtering collaboration tasks according to the task creation source type. This filtering result is only available before the first user does not update the collaboration task list. efficient.
  • the first user's collaborative task list displays the first user's completed collaboration tasks, and the first user performs an operation of filtering the completed collaboration tasks according to the task creation source type, and the filtered results are obtained Completed collaboration tasks from the session. Then, the first user performs an update operation on the collaboration task list and updates the tasks in the collaboration task list to unprocessed tasks. Then, in the updated collaboration task list, all the unprocessed tasks of the first user are displayed. Tasks, rather than filtering based on tasks previously performed by the first user, display tasks that have not yet been processed and are from the session.
  • the task filtering operation previously performed by the first user becomes invalid.
  • the reason for this is: if the first user updates the collaboration task list , the task filtering operation previously performed by the first user is still valid.
  • the first user forgets that he has performed the task filtering operation, the first user can easily mistake the tasks displayed in the updated task list for Update all tasks obtained by yourself, thus missing own tasks; by invalidating the task filtering operation previously performed by the first user after the first user updates the task collaboration list, it can be avoided that the first user forgets that he has performed the task filtering operation and will be included in the updated task list.
  • the displayed tasks are mistakenly thought to be all of one's own tasks, preventing the first user from missing one's own collaborative tasks.
  • the first user's operation of updating the task collaboration list can also be performed before filtering 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 This task collaboration list.
  • the collaboration tasks in the collaboration task list are updated, specifically:
  • the first user's collaborative task center interface displays the user identification of the second user who has a task collaboration relationship with the first user; the above update operation includes targeting the user identification of the target user among the second users. triggering operation.
  • the target task display dimension to which the first user updates the collaborative task list specifically: (a11) in response to the first user targeting the target in the second user
  • the triggering operation of the user's user ID takes the target user as the first user to update the collaboration task list to the target task display dimension; wherein, the collaboration tasks related to the first user under the target task display dimension are the first user and the target user collaborative tasks between.
  • the collaborative task center interface of the first user user identifications of multiple second users are displayed, and the second users are users who have a task collaboration relationship with the first user.
  • Task collaboration relationships include but are not limited to task assignment relationships, task sharing relationships, task comment relationships, etc.
  • the target user can be used as the target task display dimension to which the first user updates the collaborative task list.
  • the target Collaboration tasks related to the first user under the task display dimension refer to collaboration tasks between the first user and the target user.
  • the collaboration tasks in the collaboration task list related to the first user are updated to collaboration tasks between the first user and the target user.
  • Figure 6a is a schematic diagram of updating a collaboration task list provided by an embodiment of the present disclosure
  • Figure 6b is a schematic diagram of this disclosure.
  • FIG 6a and Figure 6b on the left side of the collaboration task center interface of the first user, user identifications of multiple second users are displayed. If the first user A user triggers the identification of the target user "Xiao Wang" among the second users in Figure 6a. If he clicks on the avatar, as shown in Figure 6b, the target user "Xiao Wang" will be used as the target task display dimension, which will be the same as that of the first user.
  • the collaboration tasks in the related collaboration task list are updated to be collaboration tasks between the first user and Xiao Wang.
  • the user identification of the second user who has a task collaboration relationship with the first user can be displayed in the collaboration task center interface of the first user.
  • the triggering operation of the user's user ID updates the collaboration tasks in the collaboration task list to the collaboration tasks between the first user and the target user according to the dimension of the target user triggered by the first user, thereby satisfying the first user's requirements according to the collaboration user's
  • the dimension needs to update the collaborative task list.
  • task description information is displayed in the collaborative task center interface of the first user; the update operation includes a triggering operation for target task description information in the task description information.
  • determining the target task display dimension to which the first user updates the collaborative task list in response to the first user's update operation on the collaborative task list, determining the target task display dimension to which the first user updates the collaborative task list, specifically: in response to the first user's target task description information in the task description information.
  • the triggering operation uses the target task description information as the target task display dimension to which the first user updates the collaboration task list; wherein, the collaboration tasks related to the first user under the target task display dimension are those that satisfy the target task description information and the third A user-related collaborative task.
  • the task description information may include description information according to the task type, such as "Assigned by me”, “Assigned to me”, “"What I am responsible for", “What I am concerned about”, etc. can also include description information according to task attributes, such as "tasks without scheduled time”, “tasks without designated responsible person”, etc., and can also include description information according to task status. For example, “Completed”, “In Progress", “Expired”, etc.
  • the target task description information can be used as the target task display dimension to which the first user updates the collaborative task list.
  • collaboration tasks related to the first user under the target task display dimension refer to the collaboration tasks related to the first user that satisfy the target task description information.
  • the collaboration tasks in the collaboration task list related to the first user are updated to satisfy the target task description information. collaborative tasks related to the first user.
  • Figure 6c is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure.
  • Figure 6d is a schematic diagram of updating a collaboration task list provided by another embodiment of the present disclosure.
  • the target task description information "Task without designated person in charge” in Figure 6a Clicks on the target task description information, then as follows
  • the target task description information "Tasks without designated responsible persons” is used as the target task display dimension, and the collaborative tasks in the collaborative task list related to the first user are updated to those related to the first user and without designated responsible persons. Human collaborative tasks.
  • multiple task description information can be displayed in the first user's collaborative task center interface.
  • the dimension of the triggered target task description information updates the collaboration task in the collaboration task list to the collaboration task related to the first user that satisfies the target task description information, thereby satisfying the first user's requirements for the collaboration task list according to the dimension of the task description information. Update requirements.
  • the collaboration tasks in response to the first user's filtering operation of filtering collaboration tasks according to the task creation source type, the collaboration tasks can be filtered and the filtering results can be displayed, and in response
  • the task creation source interface of the collaboration task is displayed to the first user to realize the tracing of the task creation source, and according to the target task display dimension to which the first user updates the collaboration task list , update the collaboration tasks in the collaboration task list, and implement the update of the collaboration task list.
  • Figure 7 is a schematic structural diagram of a collaborative task processing device provided by an embodiment of the present disclosure. As shown in Figure 7, the device includes:
  • List display unit 71 configured to display a list of collaboration tasks related to the first user in the collaboration task center interface of the first user
  • the type determination unit 72 is configured to determine the target task creation source type specified by the first user in response to the first user's filtering operation of filtering the collaborative tasks according to the task creation source type;
  • Task filtering unit 73 configured to filter collaboration tasks in the collaboration task list according to the target task creation source type
  • the result display unit 74 is configured to display the filtering results in the collaboration task center interface of the first user.
  • source display units for:
  • a task creation source interface of the collaboration task is displayed to the first user.
  • the task creation source of the collaboration task is a session; the task creation source identifier is a session identifier; the source display unit is specifically configured to: obtain the session corresponding to the session identifier, and use the associated interface of the session as the session identifier.
  • the task creation source interface is displayed to the first user.
  • the collaboration task is created by the task creator based on the first task creation portal associated with the session;
  • the associated interface of the session is when the task creator creates the collaboration task based on the first task creation portal, The interface presented by the session;
  • the collaboration task is created by the task creator based on the second task creation entrance associated with the session message in the session; the associated interface of the session is the interface where the session message is located.
  • the task creation source of the collaboration task is a shared document;
  • the task creation source identifier is a document identifier;
  • the source display unit is specifically configured to: obtain the shared document corresponding to the document identifier, and display the content of the shared document The interface is displayed to the first user as the task creation source interface.
  • the collaboration task is created by a task creator based on a third task creation portal associated with the shared document;
  • the content interface is the interface that is created when the task creator creates the collaboration task based on the third task creation portal. Describes the interface presented by shared documents;
  • the collaboration task is created by a task creator based on a fourth task creation entry associated with document content in the shared document;
  • the content interface is an interface where the document content is located.
  • 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;
  • the source display unit is specifically used to: determine the external third-party system identifier corresponding to the external third-party system identifier.
  • the third-party system displays the system interface of the external third-party system as the task creation source interface to the first user.
  • the collaboration task is created by the external third-party system according to specific operations performed by the system operator in the external third-party system; the system interface is the external third-party system The interface associated with the specific operation.
  • an update unit configured to: after displaying the filtering results in the collaboration task center interface of the first user, update the collaboration task list in response to the first user's update operation on the collaboration task list. Describe the collaboration tasks in the collaboration task list;
  • the updated collaboration task list supports displaying collaboration tasks whose task creation source matches any task creation source type.
  • the update unit is specifically used for:
  • the first user's collaborative task center interface displays the user identification of the second user who has a task collaboration relationship with the first user; the update operation includes targeting the second user's Trigger action by the user ID of the target user;
  • the update unit is specifically configured to: in response to the first user's triggering operation on the user identification of the target user among the second users, update the collaboration task list to the target user as the first user.
  • Target task display dimension wherein, the collaboration tasks related to the first user in the target task display dimension are collaboration tasks between the first user and the target user.
  • task description information is displayed in the collaborative task center interface of the first user;
  • the update operation includes a triggering operation for target task description information in the task description information;
  • the update unit is specifically configured to: in response to the first user's triggering operation for the target task description information in the task description information, update the collaborative task list to the first user using the target task description information as the first user.
  • the collaborative task processing device in this embodiment can implement each process of the aforementioned collaborative task processing method embodiment and achieve the same effects and functions, which will not be repeated here.
  • FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure.
  • the electronic device may have relatively large differences due to different configurations or performances. It may include one or more processors 801 and memory 802 to store One or more application programs or data may be stored in the device 802. Among them, the memory 802 may be short-term storage or persistent storage. Application programs stored in memory 802 may include one or more modules (not shown), each of which may include a sequence of computer-executable instructions in the electronic device. Furthermore, the processor 801 may be configured to communicate with the memory 802 and execute a series of computer-executable instructions in the memory 802 on the electronic device.
  • the electronic device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input or output interfaces 805, one or more keyboards 806, etc.
  • the electronic device may be a server or terminal device for an instant messaging application, including a processor; and a memory configured to store computer-executable instructions, which are executed by the processor.
  • the processor is then enabled to implement the following process:
  • collaboration task center interface of the first user display a list of collaboration tasks related to the first user
  • the filtering results are displayed in the collaboration task center interface of the first user.
  • the electronic device in this embodiment can implement each process of the aforementioned collaborative task processing method embodiment and achieve the same effects and functions, which will not be repeated here.
  • Another embodiment of the present disclosure also provides a computer-readable storage medium.
  • the computer-readable storage medium is used to store computer-executable instructions. When executed by a processor, the computer-executable instructions implement the following process:
  • collaboration task center interface of the first user display a list of collaboration tasks related to the first user
  • the filtering results are displayed in the collaboration task center interface of the first user.
  • the storage medium in this embodiment can realize the aforementioned collaborative task processing.
  • Each process of the method embodiment achieves the same effect and function, and will not be repeated here.
  • the computer-readable storage medium includes read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers, Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320.
  • the memory controller may also be implemented as part of the control logic of the memory.
  • the controller in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular 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 A combination of any of these devices.
  • one or more embodiments of the present disclosure may be provided as a method, system, or 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 that combines software and hardware aspects. Furthermore, one or more embodiments of the present disclosure may employ a computer program embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. Product form.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • 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.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific 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 connected through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Information Transfer Between Computers (AREA)
  • User Interface Of Digital Computer (AREA)
  • Document Processing Apparatus (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种协作任务处理方法、装置、设备及计算机可读存储介质，该方法包括：在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表（S102）；响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型（S104）；根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选（S106）；将筛选结果展示在所述第一用户的协作任务中心界面中（S108）。能够在第一用户的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，从而缓解目前的任务筛选方式过于局限的问题，满足用户的任务筛选需求。

Description

协作任务处理方法、装置、设备及计算机可读存储介质
本申请要求于2022年5月25日递交的中国专利申请第202210577437.6号的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。
技术领域
本公开的实施例涉及一种协作任务处理方法、装置、设备及计算机可读存储介质。
背景技术
在协作办公领域，任务(又称“待办”)系统是常用的应用。现有任务系统会向用户提供协作任务中心，用户通过协作任务中心能够创建任务以及查看任务系统中与自己相关的所有任务。目前，用户可以按照协作任务的进度，在协作任务中心的界面上筛选协作任务。然而，这种任务筛选方式只能够使用户按照任务进度筛选任务，筛选方式过于局限，无法为满足用户与日俱增的任务筛选需求。
发明内容
本公开实施例提供了一种协作任务处理方法、装置、设备及计算机可读存储介质，能够在第一用户的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，从而缓解目前的任务筛选方式过于局限的问题，满足用户与日俱增的任务筛选需求，提高用户处理协作任务的体验。
第一方面，本公开一实施例提供了一种协作任务处理方法，包括：
在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
将筛选结果展示在所述第一用户的协作任务中心界面中。
第二方面，本公开一实施例提供了一种协作任务处理装置，包括：
列表展示单元，用于在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
类型确定单元，用于响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
任务筛选单元，用于根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
结果展示单元，用于将筛选结果展示在所述第一用户的协作任务中心界面中。
第三方面，本公开一实施例提供了一种电子设备，包括：
处理器；以及，
被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被处理器执行时使所述处理器实现上述第一方面所述的方法的步骤。
第四方面，本公开一实施例提供了一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现上述第一方面所述的方法的步骤。
本公开实施例中，首先，在第一用户的协作任务中心界面中，展示与第一用户相关的协作任务列表，接着，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定第一用户指定的目标任务创建来源类型，然后，根据目标任务创建来源类型，对协作任务列表中的协作任务进行筛选，最后，将筛选结果展示在第一用户的协作任务中心界面中。可见，通过本实施例，能够在第一用户的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，从而缓解目前的任务筛选方式过于局限的问题，满足用户与日俱增的任务筛选需求，提高用户处理协作任务的体验。
附图说明
为了更清楚地说明本公开一个或多个实施例，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图；
图1为本公开一实施例提供的协作任务处理方法的流程示意图；
图2a为本公开一实施例提供的按照任务创建来源类型筛选协作任务的示意图；
图2b为本公开另一实施例提供的按照任务创建来源类型筛选协作任务的示意图；
图2c为本公开又一实施例提供的按照任务创建来源类型筛选协作任务的示意图；
图3a为本公开一实施例提供的展示任务创建来源标识的示意图；
图3b为本公开另一实施例提供的展示任务创建来源标识的示意图；
图4a为本公开一实施例提供的基于会话创建协作任务的示意图；
图4b为本公开一实施例提供的任务创建来源界面的示意图；
图4c为本公开另一实施例提供的基于会话创建协作任务的示意图；
图4d为本公开另一实施例提供的任务创建来源界面的示意图；
图5a为本公开一实施例提供的基于共享文档创建协作任务的示意图；
图5b为本公开另一实施例提供的任务创建来源界面的示意图；
图5c为本公开另一实施例提供的基于共享文档创建协作任务的示意图；
图5d为本公开另一实施例提供的任务创建来源界面的示意图；
图6a为本公开一实施例提供的更新协作任务列表的示意图；
图6b为本公开另一实施例提供的更新协作任务列表的示意图；
图6c为本公开另一实施例提供的更新协作任务列表的示意图；
图6d为本公开另一实施例提供的更新协作任务列表的示意图；
图7为本公开一实施例提供的协作任务处理装置的结构示意图；
图8为本公开一实施例提供的电子设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本公开一个或多个实施例中的技 术方案，下面将结合本公开一个或多个实施例中的附图，对本公开一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开的一部分实施例，而不是全部的实施例。基于本公开一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本公开各个实施例中所涉及的协作任务中心，位于任务系统中，该任务系统可以是位于协同办公软件内部的应用。协同办公软件是一种面向大型企业内部员工的办公软件，协同办公软件集成有即时通讯、云文档、音视频会议、任务系统等多种应用，极大提高了大型企业员工之间的协作办公效率。
一方面，在协同办公软件中，用户可以在任务系统中创建协作任务，也可以在协同办公软件中任务系统以外的其他应用中创建协作任务，如在即时通讯、云文档中创建协作任务。在协同办公软件中，任务系统以外的其他应用与任务系统打通，用户在任务系统以外的其他应用中创建的协作任务，能够同步到任务系统中。
在协同办公软件中，任务系统以外的其他应用与任务系统打通，实现协作任务的同步，一种实现方式为：协同办公软件可以提供一套基于块的框架，该基于块的框架是一套标准框架，可以让协同办公软件集成的任意一个应用将内部信息开放出来，将内部信息转换为一段格式标准的数据并展示这段数据，这段格式标准的数据与这段格式标准的数据的视图组合在一起即为组件，也就是块(Block)。基于该块的框架，能在协同办公软件集成的任意一个应用上创建并开发一段灵活展现、可交互的应用片段，并将该应用片段以块的形式在协同办公软件内的各个应用之间流转。在协同办公软件集成的任意一个应用中，可以嵌入并展示这些块，而不同应用嵌入并展示相同的应用片段时，本质上嵌入并展示的是同一个块。基于此，协同办公软件中任务系统以外的其他应用，可以基于该块的框架创建协作任务，并以块的形式将该协作任务流转到任务系统，以供任务系统嵌入并展示该协作任务。
另一方面，对于协同办公软件以外的特定的外部第三方系统，比如工单系统，用户在外部第三方系统中执行特定操作之后，比如工单创建操作之后，外部第三方系统可以调用任务系统提供的API(Application Programming Interface，应用程序接口)创建协作任务，并将协作任务同步到任务系统中。
根据以上两方面可见，任务系统中的协作任务，可以是用户在任务系统中创建，也可以是用户在协同办公软件中任务系统以外的其他应用中创建，也可以是用户在外部第三方系统中创建，因此，用户在任务系统中的协作任务具有多种创建来源，包括但不限于上述的任务系统、即时通讯、云文档、音视频会议、外部第三方系统等。
基于此，本公开一实施例提供了一种协作任务处理方法，能够在第一用户的任务系统的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，从而缓解目前的任务筛选方式过于局限的问题，满足用户与日俱增的任务筛选需求，提高用户处理协作任务的体验。
图1为本公开一实施例提供的协作任务处理方法的流程示意图，如图1所示，该流程包括以下步骤：
步骤S102，在第一用户的协作任务中心界面中，展示与第一用户相关的协作任务列表；
步骤S104，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定第一用户指定的目标任务创建来源类型；
步骤S106，根据目标任务创建来源类型，对协作任务列表中的协作任务进行筛选；
步骤S108，将筛选结果展示在第一用户的协作任务中心界面中。
本公开实施例中，首先，在第一用户的协作任务中心界面中，展示与第一用户相关的协作任务列表，接着，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定第一用户指定的目标任务创建来源类型，然后，根据目标任务创建来源类型，对协作任务列表中的协作任务进行筛选，最后，将筛选结果展示在第一用户的协作任务中心界面中。可见，通过本实施例，能够在第一用户的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，从而缓解目前的任务筛选方式过于局限的问题，满足用户与日俱增的任务筛选需求，提高用户处理协作任务的体验。
在一个实施例中，第一用户在任务系统中的协作任务，其任务创建来源类型包括但不限于普通任务、会话、共享文档、外部第三方系统等。任务创 建来源类型为“普通任务”的协作任务，是通过任务系统提供的任务创建入口或者任务系统提供的快捷键创建的协作任务。任务系统提供的任务创建入口可以位于第一用户的协同办公软件的主界面中，或者，位于第一用户的任务系统的协作任务中心界面中。
任务创建来源类型为“会话”的协作任务，是通过协同办公软件集成的即时通讯应用中的会话创建的协作任务。在通过会话创建协作任务时，可以基于会话中的某条会话消息创建协作任务，也可以基于会话中提供的任务创建入口创建协作任务。会话中提供的任务创建入口可以位于会话的侧边栏，或者，位于会话的消息输入框附近。
任务创建来源类型为“共享文档”的协作任务，是通过协同办公软件集成的共享文档应用(即上述的云文档应用)创建的协作任务。在通过共享文档应用创建协作任务时，可以基于被共享的文档中的部分文档内容创建协作任务，也可以基于共享文档应用中提供的任务创建入口创建协作任务。共享文档应用中提供的任务创建入口可以位于共享文档应用的界面的侧边栏。
任务创建来源类型为“外部第三方系统”的协作任务，是通过协同办公软件关联的特定的外部第三方系统创建的协作任务。在通过外部第三方系统创建协作任务时，用户可以在外部第三方系统中执行特定操作，外部第三方系统基于该特定操作，通过调用任务系统提供的API接口创建协作任务，并将协作任务同步到任务系统中。
图2a为本公开一实施例提供的按照任务创建来源类型筛选协作任务的示意图，图2b为本公开另一实施例提供的按照任务创建来源类型筛选协作任务的示意图，图2c为本公开又一实施例提供的按照任务创建来源类型筛选协作任务的示意图。如图2a所示，在第一用户的协作任务中心界面中，显示有与第一用户相关的协作任务列表，与第一用户相关的协作任务列表中包括与第一用户相关的协作任务，与第一用户相关的协作任务，可以是其他用户指派给第一用户的协作任务，或者，第一用户指派给其他用户的协作任务等。
在第一用户的协作任务中心界面的右上角，具有表示按照任务创建来源类型筛选协作任务的控件“来源”，第一用户触发该控件后，可以显示如图2b中所示的多个下拉选项，每个下拉选项都表示一个任务创建来源类型，第一 用户可以在这多个下拉选项中选择目标任务创建来源类型，若在图2b中，第一用户选择了“会话”作为目标任务创建来源类型。接着，任务系统根据第一用户选择的目标任务创建来源类型，对所展示的协作任务列表中的协作任务进行筛选，并将筛选结果展示在第一用户的协作任务中心界面中，具体可以展示在与第一用户相关的协作任务列表中。如图2c中，在与第一用户相关的协作任务列表中展示任务创建来源类型为“会话”的协作任务，从而向第一用户呈现筛选得到的协作任务。
在图2b中，第一用户可以一键全选各种任务创建来源类型，也可以一键清除全选模式。第一用户选择一个或多个任务创建来源类型之后，被选择的类型显示有相应记号，任务协作中心界面上显示有第一用户所选的类型的数量。
在一个实施例中，在展示与第一用户相关的协作任务列表之后，还可以：获取协作任务列表中的协作任务对应的任务创建来源标识，在协作任务列表中展示任务创建来源标识；响应于第一用户对任务创建来源标识的触发操作，向第一用户展示协作任务的任务创建来源界面。
图3a为本公开一实施例提供的展示任务创建来源标识的示意图，如图3a所示，以电脑端的任务系统为例，在与第一用户相关的协作任务列表中，展示协作任务列表中的每个协作任务的任务创建来源标识，任务创建来源与任务创建来源类型一致，均包括普通任务、会话、共享文档、外部第三方系统中的至少一项，因此任务创建来源标识也包括普通任务对应的普通任务标识、会话对应的会话标识、共享文档对应的共享文档标识、外部第三方系统对应的外部第三方系统标识中的至少一项。第一用户可以触发任务创建来源标识，比如点击任务创建来源标识，响应于该触发操作，任务系统可以向第一用户展示被触发的任务创建来源标识所属的协作任务的任务创建来源界面。
图3b为本公开另一实施例提供的展示任务创建来源标识的示意图，如图3b所示，以手机端的任务系统为例，在与第一用户相关的协作任务列表中，展示协作任务列表中的每个协作任务的任务创建来源标识。
在一个实施例中，协作任务列表中的协作任务的任务创建来源为会话；任务创建来源标识为会话标识；相应地，向第一用户展示协作任务的任务创 建来源界面，可以为：获取会话标识对应的会话，将会话的关联界面作为任务创建来源界面展示给第一用户。
如图3a所示，与第一用户相关的协作任务列表中的第一个协作任务，是基于会话创建的协作任务，其任务创建来源为会话，则相应地，在该协作任务的下方显示有会话标识，用户若触发该会话标识，任务系统可以将用于创建该协作任务的会话的关联界面作为任务创建来源界面展示给第一用户。
在一个实施例中，在获取会话标识对应的会话之后，在向第一用户展示会话的关联界面之前，判断第一用户是否有浏览该会话的权限，如有，则向第一用户展示会话的关联界面，如没有，则提示第一用户无法浏览该会话。其中，若第一用户为该会话中的会话成员，则确定第一用户有浏览该会话的权限，若第一用户不为该会话中的会话成员，则确定第一用户没有浏览该会话的权限。当然，这只是一种示意性的判断第一用户是否有浏览该会话的权限的方式，还可以有其他方式判断第一用户是否有浏览该会话的权限，这里不做限定。
在确定第一用户有浏览该会话的权限之后，可以先在第一用户的协同办公软件中调用即时通讯应用打开该会话，在打开的会话中向第一用户呈现会话的关联界面，也即使第一用户停留在会话的关联界面，第一用户也可以继续在该会话中发送会话消息。这种情况下，会话的关联界面可以通过对会话进行滚屏的方式得到。
一个实施例中，协作任务由任务创建者基于会话关联的第一任务创建入口创建，会话的关联界面为该会话的随机界面，或者，为任务创建者基于第一任务创建入口创建协作任务时，会话所呈现的界面。其中，任务创建者与第一用户可以为同一用户可以为不同用户。
图4a为本公开一实施例提供的基于会话创建协作任务的示意图，如图4a所示，在会话中，在会话的右侧边栏和会话的消息输入框的“+”的上拉列表中，均显示有任务创建入口，这两处任务创建入口为第一任务创建入口，任务创建者在会话中，可以通过第一任务创建入口创建协作任务。
在一个实施例中，当任务创建者通过上述的第一任务创建入口创建协作任务后，若第一用户触发了如图3a所示的会话标识，则可以显示该会话的随机界面，作为任务创建来源界面提供给第一用户。其中，可以通过打开该会 话的方式得到该会话的随机界面，该会话的随机界面可以为打开该会话后即得到的界面，可以为任意聊天内容对应的界面。
图4b为本公开一实施例提供的任务创建来源界面的示意图，当任务创建者通过上述的第一任务创建入口创建协作任务后，若第一用户触发了如图3a所示的会话标识，则在一个实施例中，可以如图4b所示，将任务创建者通过第一任务创建入口创建协作任务时，会话所呈现的界面作为任务创建来源界面显示给第一用户。如图4b所示，在创建协作任务时，图4a中的各个会话成员正在讨论关于会议的召开位置。
另一个实施例中，协作任务由任务创建者基于会话中的会话消息关联的第二任务创建入口创建；会话的关联界面为会话消息所在的界面。其中，任务创建者与第一用户可以为同一用户可以为不同用户。
图4c为本公开另一实施例提供的基于会话创建协作任务的示意图，如图4c所示，在会话中，在选中某条会话消息后，可以显示针对该会话消息的多种操作入口，其中就包括用于创建协作任务的任务创建入口，该任务创建入口即为第二任务创建入口。任务创建者在会话中，可以在选中某条会话消息后，通过第二任务创建入口创建协作任务。
图4d为本公开另一实施例提供的任务创建来源界面的示意图，当任务创建者通过上述的第二任务创建入口创建协作任务后，若第一用户触发了如图3a所示的会话标识，则可以如图4d所示，将会话中用于创建协作任务的会话消息所在的界面，作为任务创建来源界面显示给第一用户。图4d中，任务创建来源界面中具有一句会话消息“明天三点开会讨论吧”，被触发的任务创建来源标识所属的协作任务基于该句会话消息创建，因此，在任务创建来源界面中，该句会话消息被特定格式处理如加粗并添加下划线后显示出来。
由上可以看出，在通过会话创建协作任务的情况下，第一用户触发会话标识之后，可以将会话的关联界面作为任务创建来源界面展示给第一用户，从而满足第一用户追溯任务创建来源的需求。
在一个实施例中，协作任务列表中的协作任务的任务创建来源为共享文档；任务创建来源标识为文档标识；相应地，向第一用户展示协作任务的任务创建来源界面，可以为：获取文档标识对应的共享文档，将共享文档的内容界面作为任务创建来源界面展示给第一用户。
如图3a所示，与第一用户相关的协作任务列表中的第二个协作任务，是基于共享文档创建的协作任务，其任务创建来源为共享文档，则相应地，在该协作任务的下方显示有文档标识，用户若触发该文档标识，任务系统可以将用于创建该协作任务的共享文档的内容界面作为任务创建来源界面展示给第一用户。
在一个实施例中，在获取文档标识对应的共享文档之后，在将共享文档的内容界面作为任务创建来源界面展示给第一用户之前，判断第一用户是否有浏览该共享文档的权限，如有，则向第一用户展示共享文档的内容界面，如没有，则提示第一用户无法浏览该共享文档。其中，若第一用户为该共享文档的创建者或者指定分享接收者，则确定第一用户有浏览该共享文档的权限，反之，则确定第一用户没有浏览该共享文档的权限。当然，这只是一种示意性的判断第一用户是否有浏览该共享文档的权限的方式，还可以有其他方式判断第一用户是否有浏览该共享文档的权限，这里不做限定。
在确定第一用户有浏览该共享文档的权限之后，可以先在第一用户的协同办公软件中调用共享文档应用打开该共享文档，在打开的共享文档中向第一用户呈现共享文档的内容界面，也即使第一用户停留在共享文档的内容界面，第一用户也可以继续滚动屏幕浏览该共享文档。这种情况下，共享文档的内容界面可以通过对共享文档进行滚屏的方式得到。
一个实施例中，协作任务由任务创建者基于共享文档关联的第三任务创建入口创建；内容界面为共享文档的随机内容界面，或者，为任务创建者基于第三任务创建入口创建协作任务时，共享文档呈现的界面；其中，任务创建者与第一用户可以为同一用户可以为不同用户。
图5a为本公开一实施例提供的基于共享文档创建协作任务的示意图，如图5a所示，在共享文档应用中，在共享文档的内容界面的右侧边栏中，显示有任务创建入口，该任务创建入口为第三任务创建入口，任务创建者在共享文档应用中，可以通过第三任务创建入口创建协作任务。
在一个实施例中，当任务创建者通过上述的第三任务创建入口创建协作任务后，若第一用户触发了如图3a所示的文档标识，则可以显示该共享文档的随机内容界面，作为任务创建来源界面提供给第一用户。其中，可以通过打开该共享文档的方式得到该共享文档的随机内容界面，该共享文档的随机 内容界面可以为打开该共享文档后即得到的内容界面，可以为任意内容对应的界面。
图5b为本公开另一实施例提供的任务创建来源界面的示意图，当任务创建者通过上述的第三任务创建入口创建协作任务后，若第一用户触发了如图3a所示的文档标识，则在一个实施例中，可以如图5b所示，将任务创建者通过第三任务创建入口创建协作任务时，共享文档所呈现的内容界面作为任务创建来源界面显示给第一用户。如图5b所示，在创建协作任务时，图5a中的共享文档正在显示关于端午节放假的内容。
另一个实施例中，协作任务由任务创建者基于共享文档中的文档内容关联的第四任务创建入口创建；内容界面为文档内容所在的界面。其中，任务创建者与第一用户可以为同一用户可以为不同用户。
图5c为本公开另一实施例提供的基于共享文档创建协作任务的示意图，如图5c所示，在共享文档应用中，在选中某部分文档内容后，可以显示针对该文档内容的多种操作入口，其中就包括用于创建协作任务的任务创建入口，该任务创建入口即为第四任务创建入口。任务创建者在共享文档应用中，可以在选中某部分文档内容后，通过第四任务创建入口创建协作任务。
图5d为本公开另一实施例提供的任务创建来源界面的示意图，当任务创建者通过上述的第四任务创建入口创建协作任务后，若第一用户触发了如图3a所示的文档标识，则可以如图5d所示，将共享文档中用于创建协作任务的文档内容所在的内容界面，作为任务创建来源界面显示给第一用户。图5d中，任务创建来源界面中具有部分文档内容“端午节放假通知”，被触发的任务创建来源标识所属的协作任务基于该部分文档内容创建，因此，在任务创建来源界面中，该部分文档内容被特定格式处理如加粗处理后显示出来。
由上可以看出，在通过共享文档创建协作任务的情况下，第一用户触发文档标识之后，可以将共享文档的内容界面作为任务创建来源界面展示给第一用户，从而满足第一用户追溯任务创建来源的需求。
在一个实施例中，协作任务列表中的协作任务的任务创建来源为外部第三方系统；任务创建来源标识为外部第三方系统标识；相应地，向第一用户展示协作任务的任务创建来源界面，可以为：确定外部第三方系统标识对应的外部第三方系统，将外部第三方系统的系统界面作为任务创建来源界面展 示给第一用户。
如图3a所示，与第一用户相关的协作任务列表中的第三个协作任务，是基于外部第三方系统创建的协作任务，其任务创建来源为外部第三方系统，则相应地，在该协作任务的下方显示有外部第三方系统标识，用户若触发该外部第三方系统标识，任务系统可以将用于创建该协作任务的外部第三方系统的系统界面作为任务创建来源界面展示给第一用户。
在一个实施例中，在确定外部第三方系统标识对应的外部第三方系统之后，在将外部第三方系统的系统界面作为任务创建来源界面展示给第一用户之前，判断第一用户是否有进入该外部第三方系统的权限，如有，则向第一用户展示外部第三方系统的系统界面，如没有，则提示第一用户无法进入该外部第三方系统。其中，若第一用户为该外部第三方系统的注册用户，则确定第一用户有进入该外部第三方系统的权限，反之，则确定第一用户没有进入该外部第三方系统的权限。当然，这只是一种示意性的判断第一用户是否有进入该外部第三方系统的权限的方式，还可以有其他方式判断第一用户是否有进入该外部第三方系统的权限，这里不做限定。
在确定第一用户有进入该外部第三方系统的权限之后，可以先调用第一用户的浏览器进入该外部第三方系统并跳转至外部第三方系统的系统界面，也即使第一用户停留在外部第三方系统的系统界面，第一用户也可以在外部第三方系统中执行界面跳转或其他系统操作。
一个实施例中，协作任务由外部第三方系统根据系统操作者在外部第三方系统中执行的特定操作创建，系统界面为外部第三方系统中与该特定操作相关联的界面。其中，系统操作者与第一用户可以为同一用户可以为不同用户。
具体而言，当系统操作者在外部第三方系统中执行特定操作后，外部第三方系统可以基于该特定操作，调用任务系统提供的API创建协作任务，并将创建的协作任务同步到任务系统中。比如，系统操作者在外部第三方系统中执行工单创建操作后，外部第三方系统可以调用任务系统提供的API创建协作任务，并将创建的协作任务同步到任务系统中。
继而，当外部第三方系统标识作为任务创建来源标识被第一用户触发后，可以将外部第三方系统中与上述特定操作相关联的界面，作为任务创建来源 界面显示给第一用户。以特定操作为工单创建操作为例，外部第三方系统中与特定操作相关联的界面，可以为工单详情界面，在第一用户触发外部第三方系统标识之后，将所创建的工单的工单详情界面作为任务创建来源界面显示给第一用户。
由上可以看出，在通过外部第三方系统创建协作任务的情况下，第一用户触发外部第三方系统标识之后，可以将外部第三方系统的系统界面作为任务创建来源界面展示给第一用户，从而满足第一用户追溯任务创建来源的需求。
在一个实施例中，在步骤S108，将筛选结果展示在第一用户的协作任务中心界面中之后，还包括执行以下步骤：响应于第一用户对协作任务列表的更新操作，更新协作任务列表中的协作任务；其中，更新后的协作任务列表支持展示任务创建来源匹配任意一种任务创建来源类型的协作任务。
具体而言，第一用户在按照任务创建来源类型对协作任务列表中的协作任务进行筛选之后，还可以更新协作任务列表中的协作任务，更新后的协作任务列表可以显示任务创建来源匹配任意一种任务创建来源类型的协作任务，也即更新后的协作任务列表不再显示第一用户的按照任务创建来源类型筛选协作任务的筛选结果，该筛选结果只在第一用户没有更新协作任务列表之前有效。
在一实施例中，第一用户的协作任务列表中显示有第一用户的已经完成的协作任务，第一用户对该已经完成的协作任务执行按照任务创建来源类型进行筛选的操作，筛选得到已完成的协作任务中来自于会话的任务。继而，第一用户针对协作任务列表执行了更新操作，将协作任务列表中的任务更新为还未处理的任务，则在更新后的协作任务列表中，显示第一用户的全部的还未处理的任务，而不根据第一用户之前执行的任务筛选操作显示还未处理的且来自于会话的任务。
从这一实施例中可以看出，每当第一用户更新协作任务列表后，第一用户之前执行过的任务筛选操作即失效，这样做的理由是：若当第一用户更新协作任务列表后，仍然使第一用户之前曾经执行过的任务筛选操作有效，则在第一用户忘记自己曾经执行过任务筛选操作的情况下，第一用户容易将更新后的任务列表中显示的任务误以为是自己更新得到的全部任务，从而遗漏 自己的任务；通过在第一用户更新任务协作列表之后，使第一用户之前曾经执行过的任务筛选操作失效，可以避免第一用户忘记自己曾经执行过任务筛选操作而将更新后的任务列表中显示的任务误以为是自己的全部任务，防止第一用户遗漏自己的协作任务。
当然，第一用户更新任务协作列表的操作，也可以在按照任务创建来源类型对协作任务进行筛选之前执行，也即，在展示与第一用户相关的协作任务列表之后，第一用户即可更新该任务协作列表。
在一个实施例中，响应于第一用户对协作任务列表的更新操作，更新协作任务列表中的协作任务，具体为：
(a1)响应于第一用户对协作任务列表的更新操作，确定第一用户将协作任务列表更新至的目标任务显示维度；
(a2)获取在目标任务显示维度下与第一用户相关的协作任务，将协作任务列表中的协作任务更新为获取的协作任务。
在一个实施例中，第一用户的协作任务中心界面中展示有与第一用户之间具有任务协作关系的第二用户的用户标识；上述更新操作包括针对第二用户中的目标用户的用户标识的触发操作。
相应地，响应于第一用户对协作任务列表的更新操作，确定第一用户将协作任务列表更新至的目标任务显示维度，具体为：(a11)响应于第一用户针对第二用户中的目标用户的用户标识的触发操作，将目标用户作为第一用户将协作任务列表更新至的目标任务显示维度；其中，目标任务显示维度下与第一用户相关的协作任务，为第一用户与目标用户之间的协作任务。
具体而言，在第一用户的协作任务中心界面中，展示有多个第二用户的用户标识，第二用户是与第一用户之间具有任务协作关系的用户。任务协作关系包括但不限于任务指派关系、任务分享关系、任务评论关系等。当第一用户执行的更新操作为针对第二用户中的目标用户的用户标识的触发操作时，可以将目标用户作为第一用户将协作任务列表更新至的目标任务显示维度，相应地，在目标任务显示维度下与第一用户相关的协作任务，指的是，第一用户与目标用户之间的协作任务。相应地，将与第一用户相关的协作任务列表中的协作任务，更新为第一用户与目标用户之间的协作任务。
图6a为本公开一实施例提供的更新协作任务列表的示意图，图6b为本 公开另一实施例提供的更新协作任务列表的示意图，如图6a和图6b所示，在第一用户的协作任务中心界面的左侧边，展示有多个第二用户的用户标识，若第一用户触发了图6a中第二用户中目标用户“小王”的标识，如点击了头像，则如图6b所示，将目标用户“小王”作为目标任务显示维度，将与第一用户相关的协作任务列表中的协作任务，更新为第一用户与小王之间的协作任务。
可以看出，本实施例中，可以在第一用户的协作任务中心界面中展示与第一用户之间具有任务协作关系的第二用户的用户标识，根据第一用户对第二用户中的目标用户的用户标识的触发操作，按照第一用户所触发的目标用户的维度，将协作任务列表中的协作任务更新为第一用户与目标用户之间的协作任务，从而满足第一用户按照协作用户的维度对协作任务列表的更新需求。
在一个实施例中，第一用户的协作任务中心界面中展示有任务描述信息；更新操作包括针对任务描述信息中的目标任务描述信息的触发操作。
相应地，响应于第一用户对协作任务列表的更新操作，确定第一用户将协作任务列表更新至的目标任务显示维度，具体为：响应于第一用户针对任务描述信息中的目标任务描述信息的触发操作，将目标任务描述信息作为第一用户将协作任务列表更新至的目标任务显示维度；其中，目标任务显示维度下与第一用户相关的协作任务，为满足目标任务描述信息的与第一用户相关的协作任务。
具体而言，在第一用户的协作任务中心界面中，展示有多项任务描述信息，任务描述信息可以包括按照任务类型的描述信息，比如“我指派的”、“指派给我的”、“我负责的”“我关注的”等，还可以包括按照任务属性的描述信息，比如“未安排时间的任务”、“未指定负责人的任务”等，还可以包括按照任务状态的描述信息，比如“已完成”、“进行中”、“已过期”等。当第一用户执行的更新操作为针对任务描述信息中的目标任务描述信息的触发操作时，可以将目标任务描述信息作为第一用户将协作任务列表更新至的目标任务显示维度，相应地，在目标任务显示维度下与第一用户相关的协作任务，指的是，满足目标任务描述信息的与第一用户相关的协作任务。相应地，将与第一用户相关的协作任务列表中的协作任务，更新为满足目标任务描述信 息的与第一用户相关的协作任务。
图6c为本公开另一实施例提供的更新协作任务列表的示意图，图6d为本公开另一实施例提供的更新协作任务列表的示意图，如图6c和图6d所示，在第一用户的协作任务中心界面的左侧边，展示有多项任务描述信息，若第一用户触发了图6a中目标任务描述信息“未指定负责人的任务”，如点击了该目标任务描述信息，则如图6d所示，将目标任务描述信息“未指定负责人的任务”作为目标任务显示维度，将与第一用户相关的协作任务列表中的协作任务，更新为第一用户相关的且未指定负责人的协作任务。
可以看出，本实施例中，可以在第一用户的协作任务中心界面中展示多项任务描述信息，根据第一用户对任务描述信息中的目标任务描述信息的触发操作，按照第一用户所触发的目标任务描述信息的维度，将协作任务列表中的协作任务更新为满足目标任务描述信息的与第一用户相关的协作任务，从而满足第一用户按照任务描述信息的维度对协作任务列表的更新需求。
综上，通过以上实施例，能够在第一用户的协作任务中心界面中，响应于第一用户按照任务创建来源类型筛选协作任务的筛选操作，对协作任务进行筛选并展示筛选结果，并且，响应于第一用户对任务创建来源标识的触发操作，向第一用户展示协作任务的任务创建来源界面，实现任务创建来源的追溯，并且，按照第一用户将协作任务列表更新至的目标任务显示维度，更新协作任务列表中的协作任务，实现协作任务列表的更新。
图7为本公开一实施例提供的协作任务处理装置的结构示意图，如图7所示，该装置包括：
列表展示单元71，用于在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
类型确定单元72，用于响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
任务筛选单元73，用于根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
结果展示单元74，用于将筛选结果展示在所述第一用户的协作任务中心界面中。
可选地，还包括来源展示单元，用于：
在展示与所述第一用户相关的协作任务列表之后，获取所述协作任务列表中的协作任务对应的任务创建来源标识，在所述协作任务列表中展示所述任务创建来源标识；
响应于所述第一用户对所述任务创建来源标识的触发操作，向所述第一用户展示所述协作任务的任务创建来源界面。
可选地，所述协作任务的任务创建来源为会话；所述任务创建来源标识为会话标识；来源展示单元具体用于：获取所述会话标识对应的会话，将所述会话的关联界面作为所述任务创建来源界面展示给所述第一用户。
可选地，所述协作任务由任务创建者基于所述会话关联的第一任务创建入口创建；所述会话的关联界面为任务创建者基于所述第一任务创建入口创建所述协作任务时，所述会话所呈现的界面；
或者，
所述协作任务由任务创建者基于所述会话中的会话消息关联的第二任务创建入口创建；所述会话的关联界面为所述会话消息所在的界面。
可选地，所述协作任务的任务创建来源为共享文档；所述任务创建来源标识为文档标识；来源展示单元具体用于：获取所述文档标识对应的共享文档，将所述共享文档的内容界面作为所述任务创建来源界面展示给所述第一用户。
可选地，所述协作任务由任务创建者基于所述共享文档关联的第三任务创建入口创建；所述内容界面为任务创建者基于所述第三任务创建入口创建所述协作任务时，所述共享文档呈现的界面；
或者，
所述协作任务由任务创建者基于所述共享文档中的文档内容关联的第四任务创建入口创建；所述内容界面为所述文档内容所在的界面。
可选地，所述协作任务的任务创建来源为外部第三方系统；所述任务创建来源标识为外部第三方系统标识；来源展示单元具体用于：确定所述外部第三方系统标识对应的外部第三方系统，将所述外部第三方系统的系统界面作为所述任务创建来源界面展示给所述第一用户。
可选地，所述协作任务由所述外部第三方系统根据系统操作者在所述外部第三方系统中执行的特定操作创建；所述系统界面为所述外部第三方系统 中与所述特定操作相关联的界面。
可选地，还包括更新单元，用于：在将筛选结果展示在所述第一用户的协作任务中心界面中之后，响应于所述第一用户对所述协作任务列表的更新操作，更新所述协作任务列表中的协作任务；
其中，更新后的所述协作任务列表支持展示任务创建来源匹配任意一种任务创建来源类型的协作任务。
可选地，更新单元具体用于：
响应于所述第一用户对所述协作任务列表的更新操作，确定所述第一用户将所述协作任务列表更新至的目标任务显示维度；
获取在所述目标任务显示维度下与所述第一用户相关的协作任务，将所述协作任务列表中的协作任务更新为获取的协作任务。
可选地，所述第一用户的协作任务中心界面中展示有与所述第一用户之间具有任务协作关系的第二用户的用户标识；所述更新操作包括针对所述第二用户中的目标用户的用户标识的触发操作；
更新单元具体用于：响应于所述第一用户针对所述第二用户中的目标用户的用户标识的触发操作，将所述目标用户作为所述第一用户将所述协作任务列表更新至的目标任务显示维度；其中，所述目标任务显示维度下与所述第一用户相关的协作任务，为所述第一用户与所述目标用户之间的协作任务。
可选地，所述第一用户的协作任务中心界面中展示有任务描述信息；所述更新操作包括针对所述任务描述信息中的目标任务描述信息的触发操作；
更新单元具体用于：响应于所述第一用户针对所述任务描述信息中的目标任务描述信息的触发操作，将所述目标任务描述信息作为所述第一用户将所述协作任务列表更新至的目标任务显示维度；其中，所述目标任务显示维度下与所述第一用户相关的协作任务，为满足所述目标任务描述信息的与所述第一用户相关的协作任务。
需要说明的是，本实施例中的协作任务处理装置，能够实现前述的协作任务处理方法实施例的各个过程，并达到相同的效果和功能，这里不再重复。
本公开一实施例还提供了一种电子设备，图8为本公开一实施例提供的电子设备的结构示意图，如图8所示，电子设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器801和存储器802，存储 器802中可以存储有一个或一个以上应用程序或数据。其中，存储器802可以是短暂存储或持久存储。存储在存储器802的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括电子设备中的一系列计算机可执行指令。更进一步地，处理器801可以设置为与存储器802通信，在电子设备上执行存储器802中的一系列计算机可执行指令。电子设备还可以包括一个或一个以上电源803，一个或一个以上有线或无线网络接口804，一个或一个以上输入或输出接口805，一个或一个以上键盘806等。
在一个具体的实施例中，电子设备可以为即时通讯应用的服务器或者终端设备，包括有处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被处理器执行时使所述处理器实现以下流程：
在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
将筛选结果展示在所述第一用户的协作任务中心界面中。
需要说明的是，本实施例中的电子设备，能够实现前述的协作任务处理方法实施例的各个过程，并达到相同的效果和功能，这里不再重复。
本公开另一实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
将筛选结果展示在所述第一用户的协作任务中心界面中。
需要说明的是，本实施例中的存储介质，能够实现前述的协作任务处理 方法实施例的各个过程，并达到相同的效果和功能，这里不再重复。
其中，所述的计算机可读存储介质包括只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如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)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式， 控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本公开实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本公开一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本公开一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功 能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本公开一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本公开的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本公开中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围 之内。

Claims (15)

  1. 一种协作任务处理方法，包括：
    在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
    响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
    根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
    将筛选结果展示在所述第一用户的协作任务中心界面中。
  2. 根据权利要求1所述的协作任务处理方法，其中，在展示与所述第一用户相关的协作任务列表之后，所述方法还包括：
    获取所述协作任务列表中的协作任务对应的任务创建来源标识，在所述协作任务列表中展示所述任务创建来源标识；
    响应于所述第一用户对所述任务创建来源标识的触发操作，向所述第一用户展示所述协作任务的任务创建来源界面。
  3. 根据权利要求2所述的协作任务处理方法，其中，所述协作任务的任务创建来源为会话；所述任务创建来源标识为会话标识；
    所述向所述第一用户展示所述协作任务的任务创建来源界面，包括：获取所述会话标识对应的会话，将所述会话的关联界面作为所述任务创建来源界面展示给所述第一用户。
  4. 根据权利要求3所述的协作任务处理方法，其中，
    所述协作任务由任务创建者基于所述会话关联的第一任务创建入口创建；所述会话的关联界面为所述会话的随机界面，或者，为任务创建者基于所述第一任务创建入口创建所述协作任务时，所述会话所呈现的界面；
    或者，
    所述协作任务由任务创建者基于所述会话中的会话消息关联的第二任 务创建入口创建；所述会话的关联界面为所述会话消息所在的界面。
  5. 根据权利要求2所述的协作任务处理方法，其中，所述协作任务的任务创建来源为共享文档；所述任务创建来源标识为文档标识；
    所述向所述第一用户展示所述协作任务的任务创建来源界面，包括：获取所述文档标识对应的共享文档，将所述共享文档的内容界面作为所述任务创建来源界面展示给所述第一用户。
  6. 根据权利要求5所述的协作任务处理方法，其中，
    所述协作任务由任务创建者基于所述共享文档关联的第三任务创建入口创建；所述内容界面为所述共享文档的随机内容界面，或者，为所述任务创建者基于所述第三任务创建入口创建所述协作任务时，所述共享文档呈现的界面；
    或者，
    所述协作任务由所述任务创建者基于所述共享文档中的文档内容关联的第四任务创建入口创建；所述内容界面为所述文档内容所在的界面。
  7. 根据权利要求2所述的协作任务处理方法，其中，所述协作任务的任务创建来源为外部第三方系统；所述任务创建来源标识为外部第三方系统标识；
    所述向所述第一用户展示所述协作任务的任务创建来源界面，包括：确定所述外部第三方系统标识对应的外部第三方系统，将所述外部第三方系统的系统界面作为所述任务创建来源界面展示给所述第一用户。
  8. 根据权利要求7所述的协作任务处理方法，其中，
    所述协作任务由所述外部第三方系统根据系统操作者在所述外部第三方系统中执行的特定操作创建；所述系统界面为所述外部第三方系统中与所述特定操作相关联的界面。
  9. 根据权利要求1-8任一项所述的协作任务处理方法，其中，在将筛选 结果展示在所述第一用户的协作任务中心界面中之后，所述方法还包括：
    响应于所述第一用户对所述协作任务列表的更新操作，更新所述协作任务列表中的协作任务；
    其中，更新后的所述协作任务列表支持展示任务创建来源匹配任意一种任务创建来源类型的协作任务。
  10. 根据权利要求9所述的协作任务处理方法，其中，所述响应于所述第一用户对所述协作任务列表的更新操作，更新所述协作任务列表中的协作任务，包括：
    响应于所述第一用户对所述协作任务列表的更新操作，确定所述第一用户将所述协作任务列表更新至的目标任务显示维度；
    获取在所述目标任务显示维度下与所述第一用户相关的协作任务，将所述协作任务列表中的协作任务更新为获取的协作任务。
  11. 根据权利要求10所述的协作任务处理方法，其中，所述第一用户的协作任务中心界面中展示有与所述第一用户之间具有任务协作关系的第二用户的用户标识；所述更新操作包括针对所述第二用户中的目标用户的用户标识的触发操作；
    所述响应于所述第一用户对所述协作任务列表的更新操作，确定所述第一用户将所述协作任务列表更新至的目标任务显示维度，包括：响应于所述第一用户针对所述第二用户中的目标用户的用户标识的触发操作，将所述目标用户作为所述第一用户将所述协作任务列表更新至的目标任务显示维度；其中，所述目标任务显示维度下与所述第一用户相关的协作任务，为所述第一用户与所述目标用户之间的协作任务。
  12. 根据权利要求10所述的协作任务处理方法，其中，所述第一用户的协作任务中心界面中展示有任务描述信息；所述更新操作包括针对所述任务描述信息中的目标任务描述信息的触发操作；
    所述响应于所述第一用户对所述协作任务列表的更新操作，确定所述第一用户将所述协作任务列表更新至的目标任务显示维度，包括：响应于所述 第一用户针对所述任务描述信息中的目标任务描述信息的触发操作，将所述目标任务描述信息作为所述第一用户将所述协作任务列表更新至的目标任务显示维度；其中，所述目标任务显示维度下与所述第一用户相关的协作任务，为满足所述目标任务描述信息的与所述第一用户相关的协作任务。
  13. 一种协作任务处理装置，包括：
    列表展示单元，被配置为在第一用户的协作任务中心界面中，展示与所述第一用户相关的协作任务列表；
    类型确定单元，被配置为响应于所述第一用户按照任务创建来源类型筛选协作任务的筛选操作，确定所述第一用户指定的目标任务创建来源类型；
    任务筛选单元，被配置为根据所述目标任务创建来源类型，对所述协作任务列表中的协作任务进行筛选；
    结果展示单元，被配置为将筛选结果展示在所述第一用户的协作任务中心界面中。
  14. 一种电子设备，其中，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被所述处理器执行时使所述处理器实现上述权利要求1-12任一项所述的协作任务处理方法。
  15. 一种计算机可读存储介质，其中，所述计算机可读存储介质被配置为存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现上述权利要求1-12任一项所述的协作任务处理方法。
PCT/CN2023/095271 2022-05-25 2023-05-19 协作任务处理方法、装置、设备及计算机可读存储介质 Ceased WO2023226891A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/847,094 US12346540B2 (en) 2022-05-25 2023-05-19 Collaborative task processing method, device, and computer-readable storage medium
JP2024554637A JP7753565B2 (ja) 2022-05-25 2023-05-19 コラボレーションタスク処理方法、装置、機器及びコンピュータ可読記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210577437.6A CN114860126B (zh) 2022-05-25 2022-05-25 协作任务处理方法、装置、设备及计算机可读存储介质
CN202210577437.6 2022-05-25

Publications (1)

Publication Number Publication Date
WO2023226891A1 true WO2023226891A1 (zh) 2023-11-30

Family

ID=82639640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/095271 Ceased WO2023226891A1 (zh) 2022-05-25 2023-05-19 协作任务处理方法、装置、设备及计算机可读存储介质

Country Status (4)

Country Link
US (1) US12346540B2 (zh)
JP (1) JP7753565B2 (zh)
CN (1) CN114860126B (zh)
WO (1) WO2023226891A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114860126B (zh) 2022-05-25 2024-04-05 北京字跳网络技术有限公司 协作任务处理方法、装置、设备及计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100070463A1 (en) * 2008-09-18 2010-03-18 Jing Zhao System and method for data provenance management
CN109150901A (zh) * 2018-09-18 2019-01-04 北京达佳互联信息技术有限公司 一种信息来源的提示方法、装置、电子设备及存储介质
CN112686552A (zh) * 2020-12-31 2021-04-20 青岛海尔科技有限公司 待办任务推送方法、装置、电子设备及存储介质
CN113806049A (zh) * 2021-09-17 2021-12-17 金蝶软件（中国）有限公司 任务排队方法、装置、计算机设备和存储介质
CN114860126A (zh) * 2022-05-25 2022-08-05 北京字跳网络技术有限公司 协作任务处理方法、装置、设备及计算机可读存储介质

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003044747A (ja) * 2001-08-02 2003-02-14 Map System:Kk 情報提供システム
JP2005222246A (ja) * 2004-02-04 2005-08-18 Fuji Xerox Co Ltd 共同作業支援システム及び方法
US8302096B2 (en) * 2004-11-12 2012-10-30 Sap Ag Methods and systems to perform individual tasks as a composite task
US9116889B2 (en) * 2005-01-21 2015-08-25 International Business Machines Corporation Publishing activity tasks in a collaborative environment
US8464164B2 (en) * 2006-01-24 2013-06-11 Simulat, Inc. System and method to create a collaborative web-based multimedia contextual dialogue
US8682973B2 (en) * 2011-10-05 2014-03-25 Microsoft Corporation Multi-user and multi-device collaboration
EP2798526A4 (en) * 2011-12-29 2015-09-02 Amore Brandon Evan D SYSTEMS AND METHODS FOR COLLABORATIVE SYSTEMS FOR CREATIVE WORK
US20140237387A1 (en) * 2013-02-21 2014-08-21 Atlassian Pty Ltd Integrated notifications in a collaborative electronic information system
CN104156465B (zh) * 2014-08-22 2018-07-20 金石易诚（北京）科技有限公司 一种实时网页同步及后台分布式数据存储系统
CN104376407A (zh) * 2014-11-06 2015-02-25 河南智业科技发展有限公司 任务分配应用系统及方法
US20160277341A1 (en) * 2015-03-20 2016-09-22 Micah Garen Network collaboration tool
CN106059895A (zh) * 2016-04-25 2016-10-26 上海云睦网络科技有限公司 协同任务生成方法、装置和系统
CN107870805B (zh) * 2016-09-23 2021-06-25 腾讯科技（深圳）有限公司 任务系统的信息处理方法及装置
CN107346199A (zh) * 2017-07-03 2017-11-14 浪潮软件集团有限公司 一种基于任务的协同工作结构及方法
CN107977715A (zh) * 2017-11-15 2018-05-01 重庆衡大科技有限公司 工程中心网上报修服务平台
CN110322158A (zh) 2019-07-10 2019-10-11 浪潮卓数大数据产业发展有限公司 一种协同工作的方法及装置
US20210350303A1 (en) * 2020-05-08 2021-11-11 Dropbox, Inc. Task list for tasks created at a third-party source
CN111709698A (zh) * 2020-05-15 2020-09-25 常州市盈能电气有限公司 一种企业级的任务管理方法
CN114118937A (zh) * 2021-10-19 2022-03-01 北京百度网讯科技有限公司 基于任务的信息推荐方法、装置、电子设备及存储介质
US12026672B2 (en) * 2021-10-28 2024-07-02 Microsoft Technology Licensing, Llc Managing a collaborative workspace to identify relevant activities and present the relevant activities to a user
CN114338576A (zh) * 2021-12-31 2022-04-12 北京字跳网络技术有限公司 任务参与者的添加方法、装置、电子设备以及存储介质
CN114493541A (zh) * 2022-02-09 2022-05-13 北京字跳网络技术有限公司 任务创建方法、装置、电子设备、存储介质和程序产品

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100070463A1 (en) * 2008-09-18 2010-03-18 Jing Zhao System and method for data provenance management
CN109150901A (zh) * 2018-09-18 2019-01-04 北京达佳互联信息技术有限公司 一种信息来源的提示方法、装置、电子设备及存储介质
CN112686552A (zh) * 2020-12-31 2021-04-20 青岛海尔科技有限公司 待办任务推送方法、装置、电子设备及存储介质
CN113806049A (zh) * 2021-09-17 2021-12-17 金蝶软件（中国）有限公司 任务排队方法、装置、计算机设备和存储介质
CN114860126A (zh) * 2022-05-25 2022-08-05 北京字跳网络技术有限公司 协作任务处理方法、装置、设备及计算机可读存储介质

Also Published As

Publication number Publication date
US12346540B2 (en) 2025-07-01
JP7753565B2 (ja) 2025-10-14
CN114860126B (zh) 2024-04-05
US20250110621A1 (en) 2025-04-03
JP2025508588A (ja) 2025-03-26
CN114860126A (zh) 2022-08-05

Similar Documents

Publication Publication Date Title
US11093715B2 (en) Method and system for learning and enabling commands via user demonstration
EP2699029B1 (en) Method and device for providing a message function
KR101835588B1 (ko) 메시지 제공 방법을 실행하기 위하여 기록 매체에 저장된 컴퓨터 프로그램 및 방법
US11175823B2 (en) Method and apparatus for controlling terminal device using gesture control function, and non-transitory computer-readable storage medium
US10394431B2 (en) Apparatus and method for running application in mobile terminal
CN112333086B (zh) 一种基于聊天群的服务方法、装置以及电子设备
CN105453024A (zh) 用于显示的方法及其电子装置
CN107515707B (zh) 移动终端多级菜单控制方法及系统、存储介质、电子设备
WO2023226891A1 (zh) 协作任务处理方法、装置、设备及计算机可读存储介质
WO2022237595A1 (zh) 信息处理方法、装置、电子设备和存储介质
US20120278078A1 (en) Input and displayed information definition based on automatic speech recognition during a communication session
CN107844494A (zh) 词条审核的方法及终端、词条处理的方法及服务器
US20160253062A1 (en) Method for presentation by terminal device, and terminal device
WO2025176025A1 (zh) 信息处理方法、装置及相关产品
WO2017166665A1 (zh) 基于移动终端日历事件模式切换方法、装置和电子设备
CN112581102B (zh) 任务管理方法、装置、电子设备及存储介质
CN117369683A (zh) 界面跳转方法、装置、设备及存储介质
CN111190523A (zh) 一种界面处理方法、终端及计算机可读存储介质
CN117032524A (zh) 页面交互方法、装置、电子设备和存储介质
CN114329088A (zh) 目录结构文件生成方法、装置、设备及存储介质
EP2493158B1 (en) Apparatus and method for managing call notes in a wireless device
CN114095611A (zh) 来电显示界面的处理方法、装置和电子设备
CN106598460A (zh) 提醒信息显示方法、装置及其移动终端
US20120214551A1 (en) Apparatus and method for managing call notes in a wireless device
CN114841604B (zh) 协作任务处理方法、装置、设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23810962

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024554637

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 18847094

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 18847094

Country of ref document: US

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07-03-2025)

WWG Wipo information: grant in national office

Ref document number: 18847094

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 23810962

Country of ref document: EP

Kind code of ref document: A1