Method, device, electronic equipment and readable storage medium for initiating a to-do process

Abstract

Embodiments of the present application provide a method and device for initiating a to-do process, electronic equipment and a readable storage medium, and relate to the field of instant messaging. The method comprises: displaying a conversation interface of a work group, in response to a selection operation on a target conversation message, displaying a to-do new creation control, in response to a trigger operation on the to-do new creation control, displaying a to-do new creation interface, in response to a trigger operation on at least one process new creation control for newly creating a to-do process, generating a to-do item, and displaying the to-do item in the conversation interface. Embodiments of the present application realize the construction of a to-do process in the present application for at least one conversation message containing a to-do process described in natural language in the conversation interface of a work group. After the editing step and the node executor, a process execution reminder can be received in an instant messaging tool, and at the same time, a user can view the before-and-after dependency relationship of to-do work in an instant messaging application.

Description

Technical Field

[0001] This application relates to the field of instant messaging technology, and more specifically, to a method, apparatus, electronic device, computer-readable storage medium, and computer program product for initiating a to-do process. Background Technology

[0002] In today's internet-based work environment, communication and coordination of work tasks typically require the use of multiple office tools, including instant messaging and non-instant messaging tools. When arranging and communicating workflows and progress information using instant messaging tools, the use of natural language still necessitates setting up workflows on non-instant messaging tools, and the lack of intuitive progress tracking leads to inefficiency. For example, in scenarios where work coordination requires uploading and filling out work completion information using internal company email or the intranet, while communication of work content mostly takes place in instant messaging tools—specifically, creating group chats and sending messages. When tasks have a clear priority, current technology only provides reminders in internal company email, neglecting to provide reminders on commonly used instant messaging tools. This makes it difficult to intuitively understand work progress during coordination, resulting in time-consuming handovers, inefficient task processing, and the inability to immediately determine the corresponding workflow and responsible personnel based on a specific message in a group chat, potentially leading to the omission of important information. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for initiating a to-do process. It addresses the problem of not being able to immediately establish a to-do task process based on a single conversation message in a work group, leading to decreased work communication efficiency and uncertainty about task progress. The technical solution is as follows:

[0004] According to one aspect of the embodiments of this application, a method for initiating a to-do process is provided, applied to a client, the method comprising:

[0005] Display the chat interface of the work group, which includes at least one chat message;

[0006] In response to a selection action on a target session message, a new to-do control is displayed, which includes a to-do process described in natural language in the target session message;

[0007] In response to the triggering operation of the to-do creation control, the to-do creation interface is displayed; the to-do creation interface includes at least one process creation control for creating a new to-do process;

[0008] In response to a triggering operation on at least one process creation control for creating a new to-do process, a to-do item is generated, which includes information indicating the execution object of each process node in the to-do process.

[0009] The to-do items are displayed in the chat interface.

[0010] According to a second aspect of the embodiments of this application, displaying to-do items in the session interface further includes:

[0011] In response to a trigger action on a to-do item displayed in the chat interface, the execution details of the to-do item are displayed, including the execution status of each process node.

[0012] According to a third aspect of the embodiments of this application, displaying the execution details of a to-do item further includes:

[0013] In response to the triggering operation of the target process node of the pending process, if the account information corresponding to the client matches the execution object of the target process node, an edit box is displayed, and the execution status of the target process node is generated based on the editing result of the edit box;

[0014] If the account information corresponding to the client does not match the execution object of the target process node, the execution status of the target process node will be displayed.

[0015] According to a fourth aspect of the embodiments of this application, after generating the to-do list, the following is included:

[0016] Send configuration data for the pending tasks to the server. The configuration data includes the session ID of the session interface, the task ID of the pending task, the object ID of the processing object of each process node, and the target session message.

[0017] The server is instructed to send execution status reminders to the execution objects of each process node based on the configuration data of the pending items, and to receive and save the execution status of each process node.

[0018] According to a fifth aspect of the embodiments of this application, in response to a triggering operation on a to-do item displayed on the session interface, the execution details of the to-do item are displayed, including:

[0019] In response to the triggered operation of the pending task, a retrieval instruction is sent to the server. The retrieval instruction includes an instruction to the server to return the execution details of the pending task. The server retrieves the execution details of the pending task according to the instruction and sends the execution details of the pending task to the client.

[0020] Get and display the execution details of the to-do items.

[0021] According to a sixth aspect of the embodiments of this application, a method for initiating a to-do process is provided, applied on a server side, including:

[0022] Receive configuration data for to-do items sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message.

[0023] Based on the configuration data of the to-do items, send execution reminder information to the execution objects of each process node;

[0024] Receive and save the execution status of each process node.

[0025] According to a seventh aspect of the embodiments of this application, a to-do item includes at least one to-do step, and each to-do step includes at least one process node:

[0026] Based on the configuration data of the to-do items, send reminder messages to the execution objects of each process node, including:

[0027] Receive the execution status of process nodes sent by the client;

[0028] Determine the target pending step where the process node is located. If the execution status of all process nodes of the target pending step meets the preset conditions, then send execution status reminder information to the execution objects of each process node of the next pending step of the target pending step.

[0029] According to an eighth aspect of the embodiments of this application, a client device for initiating a to-do process is provided, the device comprising:

[0030] The conversation interface display module is used to display the conversation interface of the work group. The conversation interface includes at least one conversation message.

[0031] The control display module is used to display a new to-do control in response to a selection operation on a target session message. The target session message includes the to-do process described in natural language.

[0032] The to-do creation interface display module is used to display the to-do creation interface in response to the trigger operation of the to-do creation control; the to-do creation interface includes at least one process creation control for creating a new to-do process;

[0033] The to-do item generation module is used to generate to-do items in response to a trigger operation of at least one process creation control for creating a new to-do process. The to-do items include information indicating the execution objects of each process node in the to-do process; and the to-do items are displayed in the session interface.

[0034] According to a ninth aspect of the embodiments of this application, a client device for initiating a to-do process is provided, the device comprising:

[0035] The data sending module is used to send the configuration data of the pending items to the server. The configuration data includes the session ID of the session interface, the item ID of the pending items, the object ID of the processing object of each process node, and the target session message.

[0036] The process instruction module is used to instruct the server to send execution status reminder information to the execution objects of each process node according to the configuration data of the to-do items, and to receive and save the execution status of each process node.

[0037] According to a tenth aspect of the embodiments of this application, a server for initiating a to-do process is provided, comprising:

[0038] The data receiving module is used to receive configuration data of to-do items sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message.

[0039] The reminder message sending module is used to send execution reminder messages to the execution objects of each process node based on the configuration data of the to-do items;

[0040] The execution status recording module is used to receive and save the execution status of each process node.

[0041] According to another aspect of the embodiments of this application, an electronic device is provided, the electronic device including: a memory, a processor and a computer program stored in the memory, the processor executing the computer program to implement the steps of other aspects of the embodiments of this application.

[0042] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method for initiating a to-do process as described in any other embodiment of the present application.

[0043] According to one aspect of the embodiments of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described in any other embodiment of the present application.

[0044] The beneficial effects of the technical solutions provided in this application are:

[0045] In this application, a to-do process is constructed by including at least one conversational message in the conversational interface of a work group that describes the to-do process in natural language. After editing the steps and the personnel responsible for each node, the user can receive a process execution reminder in the instant messaging tool. In other words, this application can help users receive to-do messages in a timely manner when using instant messaging tools, and also allow users to view the dependencies between to-do tasks in the instant messaging tool. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0047] Figure 1 This application provides a schematic diagram of the system architecture for initiating a to-do process.

[0048] Figure 2 A flowchart illustrating a method for initiating a to-do process, provided as an embodiment of this application;

[0049] Figure 3 A schematic diagram illustrating a new task creation interface provided in an embodiment of this application;

[0050] Figure 4 A schematic diagram of an interface illustrating the steps of creating a to-do list, provided as an embodiment of this application;

[0051] Figure 5 A schematic diagram illustrating an interface for creating a to-do node, provided as an embodiment of this application;

[0052] Figure 6 This is a schematic diagram illustrating an interface shown in this application embodiment, displaying a user entering the pending results on the task details page;

[0053] Figure 7 A schematic diagram illustrating an interface for displaying a user's view of a to-do list details page, provided as an embodiment of this application;

[0054] Figure 8 A schematic diagram of a pop-up to-do reminder interface provided for an embodiment of this application;

[0055] Figure 9 This is a schematic diagram of an optional process execution provided for an embodiment of this application;

[0056] Figure 10 This is a schematic diagram of an optional process execution provided for an embodiment of this application;

[0057] Figure 11 This is a schematic diagram of the structure of a client device provided in an embodiment of this application;

[0058] Figure 12 This is a schematic diagram of the structure of a client device provided in an embodiment of this application;

[0059] Figure 13 This is a schematic diagram of the structure of a server provided in an embodiment of this application;

[0060] Figure 14 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0061] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0062] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” can be implemented as “A,” or as “B,” or as “A and B.”

[0063] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0064] First, let's introduce and explain several terms used in this application:

[0065] Instant messaging tools: Software that provides real-time online communication capabilities over the internet, also commonly known as instant messaging programs or applications. Users typically communicate via text, and some more advanced software offers multimedia communication and file transfer capabilities, and supports communication within a group. Instant messaging tools generally employ a client-server model. The client is the software installed on personal electronic devices such as mobile terminals, while the server is the software installed on servers or other equipment provided by the instant messaging tool manufacturer.

[0066] Notification: A function provided by an electronic device such as a mobile terminal, which informs the user of received content in a timely manner through sound or display, the content of which may include newly received conversation messages from instant messaging tools.

[0067] Workflow: When a task requires collaboration from multiple parties and the results of those parties are sequentially dependent, the workflow divides this relationship into nodes with dependencies, allowing the task to flow through these nodes. The task is considered complete when all nodes are finished.

[0068] The method, apparatus, electronic device, and readable storage medium for initiating a pending process provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0069] The technical solutions of this application and their effects are described below through several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0070] Figure 1 This is a schematic diagram of the system architecture for implementing the method of initiating a pending process according to an embodiment of this application, which may include a first terminal 101, a server 103, and a second terminal 105.

[0071] The first terminal 101 and the second terminal 105 have application programs with conversational functionality installed and running, such as chat applications, online conferencing applications, and instant messaging tools. User A logs into the instant messaging tool through the first terminal 101, and the instant messaging tool has the right to access user A's information and related data. The first terminal 101 and the second terminal 105 do not have a specific execution order; it simply represents multiple devices interacting with the server. Users of the first terminal 101 and the second terminal 105 can be in the same workgroup of the instant messaging tool, or they can be in different workgroups. The first terminal 101 and the second terminal 105 are connected to the server 103 via a wireless or wired network. The server 103 can be a single server, multiple servers, a cloud computing platform, a virtualization center, etc. The server 103 mainly performs tasks such as retrieving data from the to-do list process, updating the to-do list process, and prompting users to execute the to-do list process.

[0072] This application provides a method for initiating a to-do process, such as... Figure 2 As shown, the method includes:

[0073] S101. Display the session interface of the work group, wherein the session interface includes at least one session message.

[0074] In this embodiment, the mobile terminals and other electronic devices used by members of the work group have a chat application installed, such as social chat applications like QQ, Lark, and WeChat, or office chat applications like WeChat Work. The work group can be a chat group with chat functionality. In addition to regular chat functions, the chat group can add work-related functions such as spreadsheet creation, or it can add functions for general social needs such as charades. This embodiment does not impose specific limitations. The chat messages on the chat interface in this embodiment can include text messages, voice messages, image messages, video messages, etc., and this embodiment does not impose specific limitations.

[0075] The client in this application embodiment may include a PC client, a mobile app client, a tablet app client, a smartwatch app client, etc. On electronic devices with smaller display screens, the client will display a simpler conversation interface, while on electronic devices with larger display screens, the client will display a more detailed conversation interface. For example, a PC client will display the sender's avatar, message content, sender's ID, message sending time, whether the message has been read, and the number of people who have read the message, etc., for each message. The smartwatch app client can be customized according to user settings and may only display the sender's avatar and message content. This application embodiment does not impose specific limitations.

[0076] When using instant messaging tools, users can enter the chat interface of a work group by clicking or other operations. The chat interface usually displays at least one chat message, which can show only the chat history of the same user or the complete chat history of different users in chronological order.

[0077] S102. In response to the selection operation of the target session message, display the to-do creation control, wherein the target session message includes the to-do process described in natural language.

[0078] In this embodiment, the selected target conversation message can be a message sent by the user themselves or a message sent by other users in the same work group. The selection method for the target conversation message can include long-pressing the message, swiping right, etc., and this embodiment does not impose specific limitations. It should be noted that when the user creates a to-do item based on the target conversation message, the displayed to-do creation control can also be named "To-do Control" or another name according to the user's settings. In the to-do creation process, this control's function is generally only to display the to-do creation interface on the work group's conversation interface; the name of the control is not specifically limited in this embodiment.

[0079] This embodiment describes the to-do process in natural language. The description may include detailed information, such as who performs a particular step; or it may include a simple description, such as dividing the to-do work into several stages, requiring the user to add details such as the specific steps for each stage and the specific person responsible for each step. This embodiment does not impose any specific limitations.

[0080] After the client detects the user's selection of a target session message, a message editing window can pop up. This window may include controls for creating a new to-do item, pinning a message, and forwarding a message. When the user selects a new to-do item displayed in the message editing window, the client can locally recognize the text content in the target session message and prompt the user to edit the steps or nodes of the to-do process. Optionally, the target session message can be an image of a to-do process containing a natural language description. When the user selects the target session message, the client can locally recognize the text content in the image within the session message and, based on this, prompt the user to edit the steps or nodes of the to-do process.

[0081] S103. In response to the triggering operation of the to-do creation control, display the to-do creation interface; the to-do creation interface includes at least one process creation control for creating a new to-do process.

[0082] like Figure 3 As shown in the embodiment of this application, the user selects the to-do creation control in the pop-up window. The editing method of the to-do creation control can be to leave the chat interface of the work group and jump to the to-do creation interface to edit the to-do process; or it can be that a new window pops up in the work group chat interface to display the to-do creation interface, and the user edits on the pop-up new window.

[0083] like Figure 4 As shown in the embodiments of this application, the interface for creating a new to-do item may specifically include a to-do item editing box, a to-do process creation control, a to-do process editing control, and a save control. The to-do process creation control may include a to-do step creation control and a to-do node creation control; the to-do process editing control may include a to-do step deletion control and a to-do node deletion control. If the to-do process in this embodiment has only one to-do step, this unique to-do step generally cannot be deleted by the to-do step deletion control; that is, in this embodiment, a to-do process contains at least one to-do step.

[0084] like Figure 5As shown, in this embodiment, the executor of a pending task node can include any member of the current work group, and generally one executor corresponds to one pending task node. The executor of a selected pending task node can be deleted and reselected. However, if a pending task step has no node executor, the pending process generally cannot be saved. That is, in this embodiment, a pending task step can only be saved when it contains at least one pending task node executor. In a pending process to be saved, after adding other pending tasks, the executor of the pending task node in the previous pending task step can be edited. Editing can include adding, deleting, or changing.

[0085] When a task has multiple nodes, reminder messages will be sent to the executors of multiple nodes simultaneously when the task is executed. If one executor completes their task but others do not, the user can customize whether to send reminder messages to the executors of the other nodes in the same task.

[0086] S104. In response to a trigger operation on the at least one process creation control for creating a new to-do process, a to-do item is generated, the to-do item including information indicating the execution object of each process node in the to-do process.

[0087] S105. Display the to-do items in the conversation interface.

[0088] After completing the editing of the to-do process in the to-do editing interface, users can click the save control to jump from the to-do creation interface to the to-do item generation interface, or they can jump back from the to-do creation interface to the conversation interface, where the to-do items are displayed.

[0089] In this embodiment, displaying to-do items in the conversation interface may include: displaying the generated to-do items in a pop-up window of the target conversation message; displaying the generated to-do items and the chat interface in a split-screen manner in the conversation interface, wherein the split-screen method and the display position of the to-do items can be customized by the user, and this embodiment does not impose specific limitations; displaying the generated to-do items in a subpage of the conversation interface, wherein entering the subpage may include entering by triggering the to-do item display control in the aforementioned to-do creation interface, entering by a preset gesture, entering by a preset interface swiping method, etc., wherein the preset gesture may include, for example, double-clicking the target conversation message, double-clicking a blank area of ​​the conversation interface, etc., and the preset interface swiping method may include, for example, swiping right on the conversation interface to enter the to-do item viewing interface, pulling down the conversation interface to enter the to-do item viewing interface, etc., and this embodiment does not impose specific limitations.

[0090] In this embodiment, the to-do items may include a to-do item display box, a flowchart-based to-do item, and a to-do item processing result display box. The flowchart-based to-do items may include vertically or horizontally arranged flowcharts, which can be displayed according to user-defined settings. If no personalized settings are specified, a simplified vertical flowchart can be used by default. This embodiment does not impose specific limitations on this.

[0091] The simplified vertical flowchart includes information such as the avatar and name of the node execution object, the node completion time, and the task initiation time. When a task node is completed, its color changes, allowing users to distinguish the task execution status by color and quickly and intuitively view the task progress.

[0092] If the user's electronic device has a large operable screen, such as a personal computer, the flowchart on the to-do list page can also display a summary of the current task and a summary of the completed tasks at each to-do node. If the user's electronic device has a small operable screen, such as a mobile phone, the to-do list page will selectively display the execution details of the to-do nodes according to the user's request, in order to simplify the to-do flowchart and reduce distracting information when the user views the work progress. It should be noted that when the user sets the display information for the to-do flowchart, they can view detailed execution information at each to-do node in the simplified flowchart using preset methods. These preset methods may include long-pressing the avatar of the to-do node object, double-clicking the avatar of the to-do node object, etc., which are not specifically limited in this embodiment.

[0093] This application embodiment allows users to directly create a to-do process by selecting a target session message in the work group's session interface and directly popping up a to-do creation control. This simplifies the process of initiating a to-do process and avoids the complex operation of the prior art, which requires first entering the to-do process creation interface and then searching through the session message record to determine the target session message, making it more timely and convenient. In response to the triggering operation of the to-do creation control, a to-do creation interface is displayed. Since the creation interface only requires adding the to-do steps and the executors of the to-do nodes, users can clearly and conveniently complete process creation on electronic devices with smaller operating interfaces, such as mobile terminals. Furthermore, the method of adding to-do steps and to-do nodes is simpler than the prior art, achieving the technical effect of simplifying operations during process configuration. In response to the triggering operation of at least one workflow control used to create a new to-do process, to-do items are generated. Depending on the size of the operating interface of different electronic devices, detailed or simple information can be displayed. It can also view detailed work content in a simplified flowchart operation interface according to user requirements, maximizing the display of more work details while ensuring the clarity and convenience of to-do items. Whether you only want to view the work progress or want to view the detailed work status of a certain work node, it can intuitively and conveniently meet the user's needs, achieving the technical effect of facilitating work advancement and intuitively viewing work progress.

[0094] Based on the above embodiments, as an optional embodiment, to-do items are displayed in the session interface, including:

[0095] S201. In response to the triggering operation of the to-do items displayed in the conversation interface, display the execution details of the to-do items, including the execution status of each process node.

[0096] After a to-do item is created, all members of the work group can view the newly created to-do item by triggering preset controls in the session interface. These preset controls may include controls located at the top right of the work group, group function controls in the work group settings interface, and pinned target session messages that serve as controls, etc. This embodiment of the application does not specifically limit these to any particular type.

[0097] After the user selects a preset control in the conversation interface to enter the relevant interface, they can select the to-do list view control to enter the to-do list view interface. In the to-do list view interface, the user can find the to-do list they need to view, and selecting the target to-do list will take them to the target to-do list details interface to view the progress of the to-do list. It should be noted that the to-do list view control and the to-do list creation control can be merged into a single to-do list control according to user settings; this embodiment does not specifically limit this.

[0098] After entering the to-do list execution details page, users can view the to-do items, current process progress, completion time of processed nodes, and completed content of processed nodes. Processed nodes are highlighted with a different color than pending nodes, providing a more intuitive view of task progress. Optionally, users can customize the display position of completed nodes based on their preferences, such as displaying them below the process list sorted by completion time, or displaying detailed information about completed nodes when the user selects a node.

[0099] This application embodiment displays the execution details of a to-do item in response to its trigger operation, making it more convenient and faster to view the execution progress. Users can access the execution details page to view the progress through various methods, achieving the technical effect of allowing users to intuitively and conveniently view to-do nodes. Simultaneously, all members of the work group can view to-do nodes. If group member A is not the executor of any to-do node in the workflow, group member A can still access the to-do details page to view the task execution progress using the aforementioned methods. This satisfies the technical requirement that group members who are concerned about the overall work progress but do not execute the workflow can still participate in work communication and advance the work.

[0100] Based on the above embodiments, as an optional embodiment, displaying the execution details of the to-do items also includes:

[0101] S301. In response to the triggering operation of the target process node of the pending process, if the account information corresponding to the client matches the execution object of the target process node, an edit box is displayed, and the execution status of the target process node is generated according to the editing result of the edit box.

[0102] S302. If the account information corresponding to the client does not match the execution object of the target process node, display the execution status of the target process node.

[0103] The account information corresponding to the client is matched with the execution object of the target process node. This can include the person executing the to-do node clicking on the to-do node they are responsible for to view information; it can also include the step where group member B executes the to-do node, and group member B enters the to-do item details page to view the progress of the to-do item, etc.

[0104] like Figure 6 As shown, when the to-do list process reaches node C, if the executor of that node (hereinafter referred to as C without ambiguity) enters the to-do list details page, then the to-do result editing box and save button will be displayed on the client interface of the executor of that node; if other executors of to-do lists enter the to-do list details page when the to-do list process reaches node C, such as... Figure 7As shown, only the flowchart of the task and the result display box are displayed on the client interface of other task executors. The result editing box and save button are only displayed when the task execution process reaches the node handled by other delegated task executors. The result display box can be canceled according to the user's personalized settings.

[0105] After the person executing the pending task enters the execution result of the pending task and saves it, the client updates the pending task flowchart, marks the completed nodes, and sends a reminder message to the client of the next person executing the pending task.

[0106] By matching the client information of the person executing the task node with the client information entering the task details interface, and selectively displaying the task result editing box, the correct flow of tasks can be ensured. Tasks proceed step-by-step according to a preset sequence, preventing chaotic and disorderly workflow. It also ensures the security and traceability of work content. Only the person executing the task node can enter the node completion status, allowing for accurate identification of the person executing the node with errors or problems to further understand the details. If group members could edit the completion status of any step, the security and authenticity of the work could not be guaranteed. In other words, the implementation method of this application, in addition to simplifying the creation process, also ensures the security of work content.

[0107] Based on the above embodiments, as an optional embodiment, a to-do list is generated, followed by:

[0108] S401. Send the configuration data of the pending items to the server. The configuration data includes the session ID of the session interface, the item ID of the pending items, the object ID of the processing object of each process node, and the target session message.

[0109] After users set up their to-do items, steps, and executors for each task node on the client and save the edited information, the client sends the user-input configuration data to the server. The server then sets up a flowchart for the work group based on the received configuration data, generating process steps according to the marked order of the to-do steps, and generating specific implementation details for each process step based on the different to-do nodes and their executors. Once the basic flowchart is set up, it is returned to the clients of each work group member. The client then adds further details based on the user's personalized settings, such as marking detailed work content and the start time of each task node, before saving the flowchart and waiting for the user to retrieve and view it.

[0110] The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message. The server matches these ID information with the generated basic flowchart, sets the current to-do status of the process according to the received data information, and saves the to-do status in the server. When the to-do item process reaches a certain node, the server sends a reminder message to the client to prompt the user to execute the to-do item.

[0111] S402. Instruct the server to send execution status reminder information to the execution objects of each process node according to the configuration data of the pending items, and receive and save the execution status of each process node.

[0112] like Figure 8 As shown, the server sends a reminder message to the client of the task node to be executed. The reminder message may include: the session ID of the session interface, the task ID of the task, etc. After receiving the reminder message, the client finds the content of the task node in the work group that the user needs to process, and sends a reminder message to the user. The reminder message may include: the name of the session interface, the name of the task, the content of the task node, etc. In this way, the user can quickly locate the task in the work group that needs to be processed and edit the content of the task node that needs to be executed.

[0113] In addition to common pop-up reminders, client-side reminders can also include persistent reminders within work group interfaces, such as: message bar reminders, where a message bar is set at the top of the relevant interface of the instant messaging tool, and reminder messages are placed within the message bar until the task of this to-do node is completed; group badge reminders in the message list, where a badge is set at the group avatar of the work group with to-do tasks in the instant messaging tool's message list to indicate to the user that there are to-do tasks in the group that have not been completed, and users can customize the shape, color, etc. of the reminder badge; and reminders at the top of the group chat area, where a persistent information bar is set at the top of the work group chat to display the name of the to-do item, and prompts the user to click on the information bar to enter the details page. It should be noted that users can display multiple to-do reminders simultaneously according to their personalized needs, or they can display only one or two to-do reminders. Multiple to-do reminder methods can be randomly combined according to the user's personalized needs, and this application embodiment does not make specific limitations; however, if there are no personalized settings, this application embodiment can include to-do reminder methods that prioritize adapting to the size of the operable screen. If the operable screen is large, this application embodiment prioritizes enabling multiple to-do reminder methods, and this application embodiment does not make specific limitations in this regard.

[0114] Based on the above embodiments, as an optional embodiment, such as Figure 9 As shown, in response to a triggered operation on a to-do item displayed in the session interface, the execution details of the to-do item are displayed, including:

[0115] S501. In response to the triggering operation of the pending task, a retrieval instruction is sent to the server. The retrieval instruction includes an instruction to the server to return the execution details of the pending task. The server retrieves the execution details of the pending task according to the instruction and sends the execution details of the pending task to the client.

[0116] S502. Obtain and display the execution details of the to-do items.

[0117] When a user accesses the to-do list client to view the details of a task, the client sends a retrieval command to the server to retrieve real-time execution details data for the tasks in that work group. This execution details data may include the completion time of completed tasks, the completion result of completed tasks, and the start time of the task.

[0118] The real-time execution details data in this embodiment may include real-time data from clients of all group members within the work group, and the execution details of the most recently stored to-do items corresponding to the work group on the server. It should be noted that if the server is currently acquiring real-time data, it will prioritize sending the execution details of the most recently stored to-do items corresponding to the work group on the server to the client. In other cases, such as... Figure 10 As shown, the server typically prioritizes sending real-time data information of all clients within the work group, obtained from the server, to the client. This embodiment does not specify the server's execution status under different circumstances. After the client receives the execution details data sent by the server, the information is displayed on the client for the user to view.

[0119] It should be noted that each time a user opens the to-do details page on the client, the client records data in the background, including the ID of the to-do item execution details viewed by the user, the content of the to-do item execution details, the sequence number of the to-do steps and nodes corresponding to the user, the IDs of the executors of other to-do nodes within the to-do steps, and the processing results and processing time of the to-do items saved in the user's client. Some of this data is uploaded to the server. The uploaded data includes: the client ID of the user's client, the item ID of the to-do item viewed by the user, and the node handler ID of the to-do node that is currently in progress. The data can be stored on the server for a client to retrieve for weekly reports or to track and investigate execution progress. Users can configure the client to record some data each time the to-do item interface is opened, as needed. This application embodiment does not impose any specific limitations.

[0120] The client sends a retrieval command to the server and displays the retrieved data, ensuring the timeliness of the data. This helps users view the real-time progress of tasks when using instant messaging tools for work communication and allows them to promptly see the dependencies between ongoing tasks.

[0121] A method for initiating a to-do process, applied on the server side, includes:

[0122] S601. Receive configuration data for to-do items sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message.

[0123] S602. Based on the configuration data of the to-do items, send execution reminder information to the execution objects of each process node;

[0124] S603. Receive and save the execution status of each process node.

[0125] In this embodiment, the server receives configuration data sent by the client. The configuration data sent by the client corresponds to user account information, and the instant messaging tool has pre-authorized the user to access the configuration data. The client sends the configuration data to promptly update the progress data of the to-do list stored on the server and to send execution reminder messages to the execution objects of each process node based on the configuration data of the to-do list. After the server obtains the user's authorization information for the client to access the relevant configuration data, the server can establish corresponding markers between clients at corresponding nodes and between clients at corresponding nodes and the server based on the execution order of each node in the to-do list process, and save the corresponding relationships on the server for the client to access and view. After receiving the reminder message sent by the server, the client will prompt the user to enter the to-do list process interface through a preset method to view the specific information of this to-do node. After the to-do node completes the to-do item and updates the to-do list process status, the server saves the relevant processing data of the to-do node returned by the client, such as processing time and processed documents. This relevant processing data of the to-do node can be extracted and viewed by a client; this embodiment does not impose specific limitations on this.

[0126] Based on the above embodiments, as an optional embodiment, the to-do list includes at least one to-do step, and each to-do step includes at least one process node;

[0127] Based on the configuration data of the to-do items, send reminder messages to the execution objects of each process node, including:

[0128] S701, Receive the execution status of the process node sent by the client;

[0129] S702. Determine the target pending step where the process node is located. If the execution status of all process nodes of the target pending step meets the preset conditions, send execution status reminder information to the execution objects of each process node of the next pending step of the target pending step.

[0130] After receiving the execution status data of a node in the to-do process from the client, the server updates the status of that node on the server based on the data. It then checks if there are other pending nodes in the to-do step. If there are, it only records the data and does not send a second reminder to the client corresponding to the other pending nodes. If there are no other pending nodes in the current to-do step, the server updates the to-do process and proceeds to the next step. It then retrieves the client corresponding to the to-do node in the next step and sends a reminder to that client. If the server does not find any next pending step in the to-do process, it terminates the current to-do process and sends a to-do process completion notification to some clients based on user-personalized settings. This notification indicates that the to-do task has been completed. Users receiving this notification can be any member of the same group, not limited to the person who executed the to-do node.

[0131] This application provides an apparatus for initiating a pending process, such as... Figure 11 As shown, the client may include: a session interface display module 101, a control module 102, a to-do creation interface display module 103, and a to-do item generation module 104, wherein,

[0132] The conversation interface display module 101 is used to display the conversation interface of the work group, and the conversation interface includes at least one conversation message;

[0133] The control display module 102 is used to display a new to-do control in response to a selection operation on a target session message. The target session message includes a to-do process described in natural language.

[0134] The to-do creation interface display module 103 is used to display the to-do creation interface in response to the trigger operation of the to-do creation control; the to-do creation interface includes at least one process creation control for creating a new to-do process.

[0135] The to-do item generation module 104 is used to generate to-do items in response to a trigger operation of at least one process creation control for creating a new to-do process. The to-do items include information indicating the execution objects of each process node in the to-do process; and display the to-do items in the session interface.

[0136] This application provides an apparatus for initiating a pending process, such as... Figure 12As shown, the client may include: a data sending module 201 and a process instruction module 202, wherein,

[0137] The data sending module 201 is used to send configuration data of the pending items to the server. The configuration data includes the session ID of the session interface, the item ID of the pending items, the object ID of the processing object of each process node, and the target session message.

[0138] The process instruction module 202 is used to instruct the server to send execution status reminder information to the execution objects of each process node according to the configuration data of the to-do items, and to receive and save the execution status of each process node.

[0139] This application provides an apparatus for initiating a pending process, such as... Figure 13 As shown, the server may include: a data receiving module 301, a reminder information sending module 302, and an execution status recording module 303, wherein,

[0140] The data receiving module 301 is used to receive configuration data of the to-do items sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do items, the object ID of the processing object of each process node, and the target session message.

[0141] The reminder message sending module 302 is used to send execution reminder messages to the execution objects of each process node according to the configuration data of the to-do items;

[0142] The execution status recording module 303 is used to receive and save the execution status of each process node.

[0143] The apparatus in this application embodiment can execute the method provided in this application embodiment, and the implementation principle is similar. The actions performed by each module in the apparatus of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For detailed functional descriptions of each module of the apparatus, please refer to the descriptions in the corresponding methods shown above, which will not be repeated here.

[0144] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of initiating a to-do process method. Compared with related technologies, this application can achieve the following: a to-do process is constructed for at least one session message in the session interface of a work group that contains a description of the to-do process in natural language. After editing the steps and the executors of the nodes, a process execution reminder can be received in an instant messaging tool. That is, this application can help users receive to-do messages in a timely manner when using instant messaging applications, and at the same time, it allows users to view the dependencies between to-do tasks in the instant messaging application.

[0145] In one alternative embodiment, an electronic device is provided, such as Figure 14 As shown, Figure 14 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0146] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0147] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0148] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0149] The memory 4003 is used to store computer programs that execute the embodiments of this application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0150] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments.

[0151] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0152] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.

[0153] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0154] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A method for initiating a to-do process, characterized in that, Applied to the client side, including: Display the conversation interface of the work group, the conversation interface including at least one conversation message; In response to a selection operation on a target session message, a to-do creation control is displayed, wherein the target session message includes a to-do process described in natural language; In response to a trigger operation on the to-do creation control, a to-do creation interface is displayed; the to-do creation interface includes at least one process creation control for creating a new to-do process; the process creation control includes a to-do node creation control for creating each to-do node in the to-do process, a to-do step creation control for creating each to-do step in the to-do process, a to-do node deletion control for deleting each to-do node in the to-do process, and a to-do step deletion control for deleting each to-do step in the to-do process; In response to a trigger operation on the at least one process creation control for creating a new to-do process, a to-do item is generated, the to-do item including a vertical simplified flowchart, the vertical simplified flowchart including each process node in the to-do process and the connecting lines between each pair of process nodes, the connecting lines being used to represent the execution order relationship between corresponding two process nodes, the process node indicating information about the execution object of each process node in the to-do process; The to-do items are displayed in the chat interface.

2. The method according to claim 1, characterized in that, The process of displaying the to-do items in the session interface also includes: In response to a trigger operation on a to-do item displayed in the session interface, the execution details of the to-do item are displayed, including the execution status of each process node; The display of execution details for the to-do items also includes: In response to the triggering operation of the target process node of the pending process, if the account information corresponding to the client matches the execution object of the target process node, an edit box is displayed, and the execution status of the target process node is generated based on the editing result of the edit box; If the account information corresponding to the client does not match the execution object of the target process node, the execution status of the target process node will be displayed.

3. The method according to claim 1, characterized in that, The generation of to-do items then includes: Send the configuration data of the to-do item to the server. The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message. The server is instructed to send execution status reminder information to the execution objects of each process node according to the configuration data of the pending items, and to receive and save the execution status of each process node.

4. The method according to claim 3, characterized in that, The response to a triggered operation on a to-do item displayed on the session interface, displaying the execution details of the to-do item, includes: In response to a triggering operation on the pending task, a retrieval instruction is sent to the server, the retrieval instruction including an instruction to the server to return the execution details of the pending task, the server obtains the execution details of the pending task according to the instruction, and sends the execution details of the pending task to the client; Retrieve and display the execution details of the to-do items.

5. A method for initiating a to-do process, characterized in that, Applied to the server side, the method includes: The system receives configuration data for a to-do item sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do item, the object ID of the processing object of each process node, and the target session message. The to-do item includes at least one to-do step, and each to-do step includes at least one process node. Based on the configuration data of the to-do items, send execution reminder information to the execution objects of each process node; Receive and save the execution status of each process node; Based on the configuration data of the to-do items, reminder information is sent to the execution objects of each process node, including: Receive the execution status of the process node sent by the client; Determine the target pending step where the process node is located. If the execution status of all process nodes in the target pending step meets the preset conditions, then send execution status reminder information to the execution objects of each process node in the next pending step of the target pending step. Wherein, the to-do item is generated by the client in response to the triggering operation of at least one process creation control for creating a new to-do process in the to-do creation interface, the to-do creation interface is generated by the client in response to the triggering operation of the to-do creation control, and the to-do creation control is generated by the client in response to the selection operation of the target message in the session interface of the displayed work group. The process creation controls include a to-do node creation control for creating each to-do node in the to-do process, a to-do step creation control for creating each to-do step in the to-do process, a to-do node deletion control for deleting each to-do node in the to-do process, and a to-do step deletion control for deleting each to-do step in the to-do process.

6. A client device for initiating a to-do process, characterized in that, include: The conversation interface display module is used to display the conversation interface of the work group, and the conversation interface includes at least one conversation message; The control display module is used to display a new to-do control in response to a selection operation on a target session message, wherein the target session message includes a to-do process described in natural language; The to-do creation interface display module is used to display the to-do creation interface in response to the trigger operation of the to-do creation control; the to-do creation interface includes at least one process creation control for creating a to-do process; the process creation control includes a to-do node creation control for creating each to-do node in the to-do process, a to-do step creation control for creating each to-do step in the to-do process, a to-do node deletion control for deleting each to-do node in the to-do process, and a to-do step deletion control for deleting each to-do step in the to-do process. The to-do item generation module is used to generate to-do items in response to the trigger operation of the at least one process creation control for creating a new to-do process. The to-do item includes a vertical simplified flowchart. The vertical simplified flowchart includes each process node in the to-do process and the connecting lines between each pair of process nodes. The connecting lines are used to indicate the execution order relationship between the corresponding two process nodes. The process nodes indicate the information of the execution object of each process node in the to-do process. The to-do items are displayed in the chat interface.

7. A client device for initiating a to-do process, characterized in that, include: The data sending module is used to send the configuration data of the pending items to the server. The configuration data includes the session ID of the session interface, the item ID of the pending items, the object ID of the processing object of each process node, and the target session message. The process instruction module is used to instruct the server to send execution status reminder information to the execution objects of each process node according to the configuration data of the to-do items, and to receive and save the execution status of each process node. Wherein, the to-do item is generated by the client in response to the triggering operation of at least one process creation control for creating a new to-do process in the to-do creation interface, the to-do creation interface is generated by the client in response to the triggering operation of the to-do creation control, and the to-do creation control is generated by the client in response to the selection operation of the target message in the session interface of the displayed work group. The process creation controls include a to-do node creation control for creating each to-do node in the to-do process, a to-do step creation control for creating each to-do step in the to-do process, a to-do node deletion control for deleting each to-do node in the to-do process, and a to-do step deletion control for deleting each to-do step in the to-do process.

8. A server-side device for initiating a pending process, characterized in that, include: The data receiving module is used to receive configuration data of the to-do items sent by the client. The configuration data includes the session ID of the session interface, the item ID of the to-do items, the object ID of the processing object of each process node, and the target session message. The reminder message sending module is used to send execution reminder messages to the execution objects of each process node according to the configuration data of the to-do items; The execution status recording module is used to receive and save the execution status of each process node; Wherein, the to-do item is generated by the client in response to the triggering operation of at least one process creation control for creating a new to-do process in the to-do creation interface, the to-do creation interface is generated by the client in response to the triggering operation of the to-do creation control, and the to-do creation control is generated by the client in response to the selection operation of the target message in the session interface of the displayed work group. The process creation controls include a to-do node creation control for creating each to-do node in the to-do process, a to-do step creation control for creating each to-do step in the to-do process, a to-do node deletion control for deleting each to-do node in the to-do process, and a to-do step deletion control for deleting each to-do step in the to-do process.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method for initiating a to-do process as described in any one of claims 1-5.

Images