TW201915849A - Task generation method and device - Google Patents

Abstract

A task generation method and device. The method comprises: according to conference minute content on a conference minute presentation interface, displaying a first task creation identifier regarding the conference minute content; and when it is determined that the first task creation identifier is triggered, generating a corresponding task according to the conference minute content.

Description

Task generation method and device

One or more embodiments of the present specification relate to the field of communication technologies, and in particular, to a task generation method and apparatus.

In the related technology, the mobile group office platform is more and more widely used in the business processes of various groups such as enterprises, educational institutions, government agencies, etc., which can not only improve communication efficiency between users, reduce communication costs, but also be effective. Improve user event processing efficiency and office efficiency.

In view of this, one or more embodiments of the present specification provide a task generation method and apparatus. In order to achieve the above object, one or more embodiments of the present specification provide a technical solution as follows: According to a first aspect of one or more embodiments of the present specification, a task generation method is proposed, including: meeting minutes according to a meeting minutes presentation interface Contents, showing an identifier created for the first task of the meeting minutes content; when it is determined that the first task creation identifier is triggered, generating a corresponding task according to the meeting minutes content. According to a second aspect of one or more embodiments of the present specification, a task generation method is provided, including: acquiring conference minutes content for a conference; and generating a corresponding task according to the conference minutes content. In accordance with a third aspect of one or more embodiments of the present specification, a task generating apparatus is provided, comprising: an identification display unit that displays a first content for the meeting minutes based on a meeting minutes content of a meeting minutes presentation interface The task creation unit generates a corresponding task according to the meeting minutes content when it is determined that the first task creation identifier is triggered. According to a fourth aspect of one or more embodiments of the present specification, a task generating apparatus is provided, including: an obtaining unit that acquires meeting minutes content for a meeting; and a generating unit that generates a corresponding task according to the meeting minutes content.

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of the specification. Instead, they are merely examples of devices and methods consistent with aspects of one or more embodiments of the present specification as detailed in the appended claims. It should be noted that the steps of the corresponding method are not necessarily performed in the order shown and described in the specification in other embodiments. In some other embodiments, the method may include more or fewer steps than those described herein. In addition, the individual steps described in this specification may be decomposed into multiple steps for description in other embodiments; while the multiple steps described in this specification may be combined into a single step in other embodiments. description. FIG. 1 is a schematic structural diagram of a task generation system according to an exemplary embodiment. As shown in FIG. 1, the system may include a server 11, a network 12, and a plurality of electronic devices, such as a user device 13, such as a mobile phone 131 and a PC 132, and a user device 14 such as a mobile phone 141 and a PC 142. The server 11 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster, or the server 11 may be a cloud server. During operation, the server 11 can run a program on the server side of an application to implement related business functions of the application, such as when the server 11 runs a program of the mobile group office platform. The server side of the group office platform. In this embodiment, the mobile group office platform can not only realize the communication function, but also can be used as an integrated function platform for many other functions, such as approval events (such as leave, office item application, financial and other approval events), attendance events. The processing of internal events of the group, such as task events, log events, and the like, such as ordering, purchasing, and other external events of the group, one or more embodiments of the present specification are not limited thereto. More specifically, the mobile group office platform can be carried in instant messaging applications in related technologies, such as enterprise instant messaging (EIM) applications, such as Skype For Business. ^® , Microsoft Teams ^® Yammer ^® Workplace ^® Slack ^® Enterprise WeChat ^® Share customers ^® Corporate letter ^® Enterprise letter ^® Wait. Of course, the instant messaging function is only one of the communication functions supported by the mobile group office platform. The mobile group office platform can also implement more functions such as the above, and will not be described here. User devices such as mobile phones 131-141, PC 132-142, etc. are only some types of electronic devices that the user can use. In fact, users obviously can also use electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), this manual One or more embodiments do not limit this. During operation, the electronic device can run a client-side program of an application to implement related business functions of the application, such as when the electronic device runs a program of the mobile group office platform. The client of the group office platform. It should be noted that the application of the client of the mobile group office platform can be pre-installed on the electronic device so that the client can be launched and run on the electronic device; of course, when adopting an online "customer such as HTML5 technology""End", you can get and run the client without installing the corresponding application on the electronic device. The network 12 that interacts between the user equipment 13-14 and the server 11 may include multiple types of wired or wireless networks. In an embodiment, the network 12 may include a Public Switched Telephone Network (PSTN) and an Internet. At the same time, the electronic devices such as the user equipment 13-14 can also communicate with each other through the network 12, such as establishing a single-chat communication session between any two electronic devices; or, several electronic devices can participate in the same group communication communication. The session enables any user to send a communication message to all other users in the group chat communication session through their own electronic device. FIG. 2 is a flowchart of a task generation method according to an exemplary embodiment. As shown in FIG. 2, the method may be applied to a server (such as the server 11 running above) or a client (such as the user equipment 13-14 running above), and may include the following steps: Step 202: Obtain a conference for the conference Meeting minutes content. In an embodiment, the minutes of the meeting are used to record and convey information about the meeting, the agreed matters, and the like, so that relevant work or activities can be carried out according to the meeting after the meeting ends. In an embodiment, after the meeting minutes can be created, the meeting minutes are associated with one or more meetings, such that the meeting minutes can be considered to be created for the one or more meetings. In an embodiment, after one or more meetings are selected by the user, the meeting minutes associated with the one or more meetings are created without subsequent associations. For example, when the conference-related interface of a conference is provided to the user, the user can create a conference minute through the conference-related interface or other associated interface, and can determine that the user selects the conference corresponding to the conference-related interface, and creates a conference for the conference. The corresponding meeting minutes. For another example, the user-created meeting minutes are determined to be associated with the one or more selected meetings by providing the user with an alternate number of meetings, and the user directly selects one or more meetings. In an embodiment, since the user typically creates a meeting minutes during the meeting, when the user creates the meeting minutes, the meeting the user is participating in can be identified, thereby associating the meeting minutes with the identified meeting. For example, the mobile group office platform can maintain the conferences in which the user participates, as well as the location, time, and attendees of the conference; in one case, when the user creates the conference minutes, the conference time of each conference in which the user participates can be used. The conference corresponding to the current conference time is determined as the conference in which the user is participating; in another case, the geographical location information of the user equipment used by the user (for example, the identified location of the GPS chip or the Beidou wafer built in the user equipment) can be obtained. Information, the near field detection information of the user equipment at the conference location, wherein the near field detection information can be detected based on near field communication technologies such as Bluetooth, RFID, ZigBee, etc., when the user is in a conference At the meeting place, it can be determined that the user is participating in the meeting. Step 204: Generate a corresponding task according to the meeting minutes content. In an embodiment, the task content of the task may include at least a portion of the meeting minutes content. For example, when the meeting minutes include multiple pieces of information, the task content of the task may contain at least one piece of information. During the process of generating a task, the user may choose to generate one or more pieces of information in the meeting minutes as a corresponding task, so that the task includes one or more pieces of information selected by the user; or, the user is in the meeting minutes for the meeting. When the corresponding task is generated, the task can contain all the information about the meeting minutes. In an embodiment, for the content of the meeting minutes, a corresponding task may be generated, which may include part or all of the meeting minutes. In another embodiment, for the content of the meeting minutes, a corresponding plurality of tasks may be generated, each task may include some or all of the contents of the meeting minutes. In an embodiment, the performer of the task may include at least one participant of the conference, and the participant may be an actual participant of the conference, or may be a scheduled participant of the conference (eg, The person who participates in the meeting in the meeting reservation information); in which the scheduled participants can attend the meeting and become the actual participants, the non-scheduled participants can also participate in the meeting and become the actual participants, of course, scheduled Participants may also not attend the meeting. In one case, at least one participant of the conference can be automatically configured as the performer of the task, for example, all participants of the conference can be automatically configured as the performer of the task. In another case, the participants of the meeting can be provided to the user, and the user selects one or more participants to be added as the performer of the task. In an embodiment, the performer of the task may be independent of the participant of the meeting, such as by the user manually selecting any one or more users as the performer of the task. Alternatively, one or more users can be configured by other means to configure the performer of the task. In an embodiment, the executor of the task may include at least one participant of the meeting, and at least one non-participant, who perform the task together. For example, in one case, all participants of the conference can be automatically configured as a preset performer, and the user can manually select other performers; in another case, the user can be provided with a first candidate list, which The first candidate list includes all participants of the conference for the user to select, and may also provide the user with a second candidate list, where the second candidate list includes the associated user of the user (eg The user recorded in the address book, etc., for the user to select. In an embodiment, the conference summary presentation interface may include a first task creation identifier for the content of the conference minutes; and correspondingly, when it is determined that the first task creation identifier is triggered, the task generation process may be implemented. The corresponding task is generated according to the content of the meeting minutes. For example, if it is determined that the user performs an input operation in the meeting minutes presentation interface, that is, the user creates a meeting minutes for the meeting (the input content formed by the input operation is the content of the meeting minutes), the content of the meeting minutes may be correspondingly displayed. The first task creates an identifier, so that the user can create an identifier by triggering the first task to generate a corresponding task. The content of the meeting minutes corresponding to the first task creation identifier may be automatically added as the task content of the task, and the user may accept the task content, or edit the task content according to actual needs. In an embodiment, the meeting summary display interface may include a second task creation identifier; correspondingly, when it is determined that the second task creation identifier is triggered, the task generation process may be implemented to generate a corresponding task. For example, even if the user has not entered the content of any meeting minutes through the meeting minutes presentation interface, the user can still create a corresponding task by triggering the second task to quickly generate a corresponding task, and the task is configured to be related to the meeting. In an embodiment, when a user creates a task by triggering a second task creation identifier, the task content of the task may be used as at least a portion of the meeting minutes content. In other words, when a user creates a task, the task content of the task can be added as a meeting minutes; wherein the user can edit the content of the meeting minutes, or continue to add other meeting minutes based on this. In an embodiment, the information about the task may be displayed on the conference-related interface corresponding to the conference, so that the user can conveniently view the information about the task related to the conference when viewing the related interface of the conference, and may also be convenient. The user clarifies the relationship between the task and the meeting. The conference related interface may include any interface related to the conference, and the description does not limit the present disclosure. For example, the conference related interface may include a message content display interface of the conference reminder message corresponding to the conference, or the conference related interface may be Including the meeting information display interface corresponding to the meeting. In an embodiment, the information of the task may include at least one of the following: task content, task performer, task deadline, task execution status, and the like, which is not limited in this specification. In an embodiment, the participant of the meeting has access to the information of the task. In one case, when a participant is the performer of the task, the participant must have the right to view the task, and the participant can also perform corresponding task processing operations on the task, such as The task is switched from the "not completed" state to the "completed" state. In another case, when a participant is not the performer of the task, the participant can have the right to view the task, so that even after the meeting is over, the participant can still understand the meeting process. The handling of negotiating matters (the handling of negotiating matters through tasks). In an embodiment, a task reminder message may be sent to an executor of the task to assist the performer in completing the related task as quickly as possible. The task reminder message can be sent by at least one of the following methods: an instant message, a short message, a voice broadcast message after the call is connected, etc., and the specification does not limit this. FIG. 3 is a flowchart of another task generation method provided by an exemplary embodiment. As shown in FIG. 3, the method may be applied to a client (such as the user equipment 13-14), and may include the following steps: Step 302: In the conference related interface corresponding to the conference, showing that the conference is related to the conference. Information of the task; wherein the task is related to the meeting minutes of the meeting. In an embodiment, the logged in user of the client may be configured as an executor of the task. In other words, only the executor of the task can view the information about the task related to the meeting in the relevant interface of the meeting, while other users cannot view it. In an embodiment, the logged-in user of the client may be configured as an executor of a part of the tasks, that is, the conference related interface may also show other tasks that the logged-in user is not an executor; in other words, Even if the logged in user is not the executor of the task, the information about the task associated with the meeting can still be viewed. For a non-task executor, the viewing rights of the task can be restricted by other dimensions; for example, it can be restricted to the participants of the meeting, restricted to the group members of the group to which the meeting belongs, and the like. List one by one. In an embodiment, when the logged-in user is an executor of a part of the tasks in the conference-related interface, and the conference-related interface further includes other tasks that the logged-in user is not an executor, the related interface may be in the conference-related interface. The task of the logged-in user as an executor is prioritized and displayed, so that the logged-in user can more easily find and process the task as an executor. In an embodiment, detecting a user-triggered operation for the task; when the logged-in user of the client is configured as an executor of the task, performing a corresponding task processing operation on the task, such as marking Task processing status, tag task processing stage, upload task processing result, application transfer task, application termination task, etc., are not listed here. In an embodiment, detecting a user-triggered operation for the task; when the logged-in user of the client is the creator of the task, performing a corresponding task management operation on the task, such as terminating the task, Transfer tasks, modify task content, modify task performers, modify task deadlines, etc., are not listed here. FIG. 4 is a flowchart of still another task generation method provided by an exemplary embodiment. As shown in FIG. 4, the method may be applied to a client (such as the user equipment 13-14 running above), and may include the following steps: Step 402, according to the meeting minutes of the meeting minutes presentation interface, showing the meeting The first task of the minutes content creates an identity. In an embodiment, the conference related interface may include any interface related to the conference, and the specification does not limit the disclosure; for example, the conference related interface may include a message content display interface of the conference reminder message corresponding to the conference, or the The conference related interface may include a conference information display interface corresponding to the conference. In an embodiment, the meeting summary display interface can be expressed in any form, such as a temporary window, a separate interface, etc., and the specification does not limit this. In an embodiment, the minutes of the meeting are used to record and convey information about the meeting, the agreed matters, and the like, so that relevant work or activities can be carried out according to the meeting after the meeting ends. In an embodiment, after the meeting minutes can be created, the meeting minutes are associated with one or more meetings, such that the meeting minutes can be considered to be created for the one or more meetings. In an embodiment, after one or more meetings are selected by the user, the meeting minutes associated with the one or more meetings are created without subsequent associations. For example, when the conference-related interface of a conference is provided to the user, the user can create a conference minute through the conference-related interface or other associated interface, and can determine that the user selects the conference corresponding to the conference-related interface, and creates a conference for the conference. The corresponding meeting minutes. For another example, the user-created meeting minutes are determined to be associated with the one or more selected meetings by providing the user with an alternate number of meetings, and the user directly selects one or more meetings. In an embodiment, since the user typically creates a meeting minutes during the meeting, when the user creates the meeting minutes, the meeting the user is participating in can be identified, thereby associating the meeting minutes with the identified meeting. For example, the mobile group office platform can maintain the conferences in which the user participates, as well as the location, time, and attendees of the conference; in one case, when the user creates the conference minutes, the conference time of each conference in which the user participates can be used. The conference corresponding to the current conference time is determined as the conference in which the user is participating; in another case, the geographical location information of the user equipment used by the user (for example, the identified location of the GPS chip or the Beidou wafer built in the user equipment) can be obtained. Information, the near field detection information of the user equipment at the conference location, wherein the near field detection information can be detected based on near field communication technologies such as Bluetooth, RFID, ZigBee, etc., when the user is in a conference At the meeting place, it can be determined that the user is participating in the meeting. Step 404: When it is determined that the first task creation identifier is triggered, generate a corresponding task according to the conference minutes content. In an embodiment, the task content of the task may include at least a portion of the meeting minutes content. For example, when the meeting minutes include multiple pieces of information, the task content of the task may contain at least one piece of information. During the process of generating a task, the user may choose to generate one or more pieces of information in the meeting minutes as a corresponding task, so that the task includes one or more pieces of information selected by the user; or, the user is in the meeting minutes for the meeting. When the corresponding task is generated, the task can contain all the information about the meeting minutes. In an embodiment, for the content of the meeting minutes, a corresponding task may be generated, which may include part or all of the meeting minutes. In another embodiment, for the content of the meeting minutes, a corresponding plurality of tasks may be generated, each task may include some or all of the contents of the meeting minutes. In an embodiment, the performer of the task may include at least one participant of the conference, and the participant may be an actual participant of the conference, or may be a scheduled participant of the conference (eg, The person who participates in the meeting in the meeting reservation information); in which the scheduled participants can attend the meeting and become the actual participants, the non-scheduled participants can also participate in the meeting and become the actual participants, of course, scheduled Participants may also not attend the meeting. In one case, at least one participant of the conference can be automatically configured as the performer of the task, for example, all participants of the conference can be automatically configured as the performer of the task. In another case, the participants of the meeting can be provided to the user, and the user selects one or more participants to be added as the performer of the task. In an embodiment, the performer of the task may be independent of the participant of the meeting, such as by the user manually selecting any one or more users as the performer of the task. Alternatively, one or more users can be configured by other means to configure the performer of the task. In an embodiment, the executor of the task may include at least one participant of the meeting, and at least one non-participant, who perform the task together. For example, in one case, all participants of the conference can be automatically configured as a preset performer, and the user can manually select other performers; in another case, the user can be provided with a first candidate list, which The first candidate list includes all participants of the conference for the user to select, and may also provide the user with a second candidate list, where the second candidate list includes the associated user of the user (eg The user recorded in the address book, etc., for the user to select. In an embodiment, the meeting summary display interface may include a second task creation identifier; correspondingly, when it is determined that the second task creation identifier is triggered, the task generation process may be implemented to generate a corresponding task. For example, even if the user has not entered the content of any meeting minutes through the meeting minutes presentation interface, the user can still create a corresponding task by triggering the second task to quickly generate a corresponding task, and the task is configured to be related to the meeting. In an embodiment, when a user creates a task by triggering a second task creation identifier, the task content of the task may be used as at least a portion of the meeting minutes content. In other words, when a user creates a task, the task content of the task can be added as a meeting minutes; wherein the user can edit the content of the meeting minutes, or continue to add other meeting minutes based on this. In an embodiment, the information about the task may be displayed on the conference-related interface corresponding to the conference, so that the user can conveniently view the information about the task related to the conference when viewing the related interface of the conference, and may also be convenient. The user clarifies the relationship between the task and the meeting. The conference related interface may include any interface related to the conference, and the description does not limit the present disclosure. For example, the conference related interface may include a message content display interface of the conference reminder message corresponding to the conference, or the conference related interface may be Including the meeting information display interface corresponding to the meeting. In an embodiment, the information of the task may include at least one of the following: task content, task performer, task deadline, task execution status, and the like, which is not limited in this specification. In an embodiment, the participant of the meeting has access to the information of the task. In one case, when a participant is the performer of the task, the participant must have the right to view the task, and the participant can also perform corresponding task processing operations on the task, such as The task is switched from the "not completed" state to the "completed" state. In another case, when a participant is not the performer of the task, the participant can have the right to view the task, so that even after the meeting is over, the participant can still understand the meeting process. The handling of negotiating matters (the handling of negotiating matters through tasks). In an embodiment, a task reminder message may be sent to an executor of the task to assist the performer in completing the related task as quickly as possible. The task reminder message can be sent by at least one of the following methods: an instant message, a short message, a voice broadcast message after the call is connected, etc., and the specification does not limit this. For ease of understanding, the technical solution of one or more embodiments of the present specification will be described by taking the enterprise instant messaging application "Enterprise WeChat" as an example. Assume that user A, user B, and user C in enterprise AA participate in the same conference. User A corresponds to enterprise WeChat client 1, user B corresponds to enterprise WeChat client 2, user C corresponds to enterprise WeChat client 3, and enterprise WeChat Clients 1 to 3 cooperate with the enterprise WeChat server to implement the task generation scheme of this specification. FIG. 5 is a schematic diagram of a conference related interface provided by an exemplary embodiment. As shown in FIG. 5, the enterprise WeChat client may provide a conference related interface 500, where the conference related interface 500 is used to display the conference information 502 of the related conference. For example, the conference information 502 may include the conference topic “H project design progress report” and the conference. The time is "16:00 ~ 18:00 on Tuesday, August 15", the meeting place "301 Huilongguan", the participants of the meeting (ie the participants) "user A, etc. 5 people", etc., this manual does not Make restrictions. It is assumed that the user A has the permission to create a meeting minutes for the above-mentioned meeting "H project design progress report", and the enterprise WeChat client 1 corresponding to the user A can show the meeting related interface 500 as shown in FIG. 5; When the user A triggers the add meeting minutes option 504 in the meeting related interface 500, the enterprise WeChat client 1 can transfer to the meeting minutes display interface 600 shown in FIG. 6 to perform operations such as creating meeting minutes by the user A. FIG. 6 is a schematic diagram of a conference minutes presentation interface provided by an exemplary embodiment; FIG. 7 is a schematic diagram of an input conference minutes provided by an exemplary embodiment. As shown in FIG. 6, the meeting summary display interface 600 can include a meeting minutes input area 602; wherein, by triggering the meeting minutes input area 602, the user A can input a corresponding meeting minutes in the meeting minutes input area 602, such as in FIG. Contains meeting minutes 606 entered by User A. In an embodiment, after user A forms any input content in the meeting minutes presentation interface 600, if user A intentionally or unintentionally triggers the "return" option in the upper left corner of the meeting minutes display interface 600, the enterprise WeChat client 1 may While returning to the conference related interface 500 described above, the input content formed by the user A is recorded, so that the user A can still return to the conference minutes presentation interface 600 to continue the input operation after temporarily processing other operations. For example, FIG. 8 is a schematic diagram of another conference related interface provided by an exemplary embodiment; as shown in FIG. 8, for the input content formed by the user A in the meeting minutes presentation interface 600, the enterprise WeChat client 1 may add a meeting minutes. The display content of the option 504 is changed from "Add Meeting Minutes" shown in FIG. 5 to "Add Meeting Minutes (Draft)" shown in FIG. 8 to prompt the user A that there are still meeting minutes that have not yet been created. When it is detected that the user A triggers the add meeting minutes option 504 shown in FIG. 8, the meeting minutes display interface 600 as shown in FIG. 7 can be returned. In an embodiment, when it is detected that the user A performs an input operation in the meeting minutes input area 602, the enterprise WeChat client 1 can display a corresponding function identifier in the meeting minutes display interface 600 for the input content of the user A, so that User A can quickly convert the corresponding input into a task by triggering the function identifier. For example, as shown in FIG. 7, for the meeting minutes 606 input by the user A, the enterprise WeChat client 1 can display the corresponding function identification 608 in the meeting minutes presentation interface 600. Similarly, FIG. 9 is a schematic diagram of another conference minutes presentation interface provided by an exemplary embodiment; as shown in FIG. 9, it is assumed that user A inputs conference minutes 606 and conference minutes 610 respectively on the conference minutes presentation interface 600. The WeChat client 1 can display a corresponding function identifier 608 and a function identifier 612 for the meeting minutes 606 and the meeting minutes 610, respectively. FIG. 10 is a schematic diagram of a task creation interface provided by an exemplary embodiment. Assuming that the user A is triggered to trigger the function identifier 612 shown in FIG. 9, the enterprise WeChat client 1 can show the task creation interface 1000 as shown in FIG. 10; wherein the task creation interface 1000 shown in FIG. 10 can be displayed for the conference minutes. The form of the floating window on the interface 600, and other interface forms may be used in other embodiments, and the description does not limit this. As shown in FIG. 10, the task creation interface 1000 may include several description options for the task, such as the task content option 1002, the task performer option 1004, the task deadline option 1006, etc., which is not limited in this specification. In an embodiment, when it is detected that the user A triggers the function identifier 612 as shown in FIG. 9, since the function identifier 612 corresponds to the meeting minutes 610, it indicates that the user A wishes to generate a corresponding task according to the content of the meeting minutes 610. Then, the enterprise WeChat client 1 can automatically fill the content of the meeting minutes 610 into the task content option 1002 shown in FIG. 10 without the user A manually inputting. FIG. 11 is a schematic diagram of a view creation task provided by an exemplary embodiment. In the task creation interface 1000 shown in FIG. 10, the task executor option 1004 can be defaulted. When the enterprise WeChat client 1 generates the task 614 as shown in FIG. 11, the user A can be automatically configured as the task 614. Task performer. Of course, other description options, such as task deadline option 1006, can also be defaulted without affecting the generation of task 614. FIG. 12 is a schematic diagram of another task creation interface provided by an exemplary embodiment. As shown in FIG. 12, in addition to the task content option 1002 automatically filled in by the enterprise WeChat client 1, the user A can perform other description options such as the task executor option 1004 and the task deadline option 1006 in the task creation interface 1000 according to actual needs. Perform input operations, such as configuring the task performer as "user B" and configuring the task deadline as "18:00 on August 31". Correspondingly, FIG. 13 is a schematic diagram of another view creation task provided by an exemplary embodiment; as shown in FIG. 13, corresponding to the content of the user A in FIG. 12, the enterprise WeChat client 1 can generate a corresponding task. 616, the task executor of the task 616 is user B, the task deadline is still 14 days remaining. In an embodiment, when it is detected that the user A triggers the function identifier 612 as shown in FIG. 9, since the function identifier 612 corresponds to the meeting minutes 610, it indicates that the user A wishes to generate a corresponding task according to the content of the meeting minutes 610; Assume that the enterprise WeChat client 1 obtains other task information such as a task executor, a task deadline, and other task presets that can be preset by the system or preset by the user A or other users with administrative rights. The enterprise WeChat client 1 can The content of the meeting minutes 610 is automatically filled into the task content, and the corresponding tasks are automatically generated, and the generated tasks can be automatically assigned. In an embodiment, in addition to first inputting the meeting minutes, and then converting and generating corresponding tasks according to the meeting minutes, User A can also directly generate tasks. For example, the conference creation display interface 600 shown in FIG. 13 includes a task creation identifier 604. When it is detected that the user A triggers the task creation identifier 604, the enterprise WeChat client 1 can invoke the task creation interface 1400 shown in FIG. 14; Similar to the task creation interface 1000 described above, the task creation interface 1400 may include a description option such as a task content option 1402, a task performer option 1404, and a task deadline option 1406, which may be input and filled by the user A. In an embodiment, based on the task uploaded by the task creation identifier 604, the enterprise WeChat client 1 can automatically add the task content of the task as a meeting minutes, so that the user A can generate the meeting minutes according to the content of the meeting minutes. Tasks can also create meeting minutes based on the task content after the task is generated, which can simplify user operations and improve operational efficiency. FIG. 15 is a schematic diagram of still another view creation task provided by an exemplary embodiment. As shown in FIG. 15, it is assumed that the user A creates the corresponding task 616 by triggering the function identifier 612 corresponding to the meeting minutes 610. In addition, the user A creates the task 618 and the task 620 by triggering the task creation identifier 604. The tasks 616-620 can be performed. The rankings are displayed in the meeting summary display interface 600. When it is detected that the user A triggers the "Complete" option in the upper right corner of the meeting summary display interface 600, the enterprise WeChat client 1 formally creates a meeting minutes 606, a meeting minutes 610, and tasks 616-620. FIG. 16 is a schematic diagram of a distribution task provided by an exemplary embodiment. As shown in FIG. 16, the enterprise WeChat client 1 can display the task assignment prompt information 1600 to make the user A more aware of the assignment operation of the task. FIG. 17 is a schematic diagram of information showing a meeting minutes and tasks in a conference related interface according to an exemplary embodiment. As shown in FIG. 17, the conference related interface 500 provided by the enterprise WeChat client 1 may include a display area 1700 for displaying information about conference minutes related to the conference, information of tasks, and the like. In the conference related interface 500 shown in FIG. 17, the display area 1700 may contain the information of the meeting minutes 1702. For example, the information 1702 may include the contents of the meeting minutes related to the meeting "H project design progress report", such as "Thursday" Complete the basic plan of the H project", "4. 0 style and specification determine "etc. Display area 1700 can contain information about the task, such as Figure 17 shows task 1704, task 1706, and task 1708, the information of the task can include the task content of task 1704-1708, the task performer, by The status of the task is indicated by the status information 1710, etc., of course, this specification does not limit this. When the user A views the tasks in the display area 1700 through the enterprise WeChat client 1, these tasks may include two types: user A as an executor. For example, task 1708, user A is not an executor's task, such as tasks 1704-1706. Wherein, display area 1700 includes task manipulation option 1708A corresponding to task 1708, and when user A is detected to trigger the task manipulation option 1708A, user A The task 1708 can be quickly configured to a "task completed" state or other state. The display area 1700 also includes a task manipulation option 1704A corresponding to the task 1704, but since the user A is not the performer of the task 1704, the task manipulation option 1704A is configured to be in an unmanageable state, such that user A cannot perform state configuration on the task 1704; The user A is also unable to perform the state configuration on the task 1706. Figure 18 is a schematic diagram showing the arrangement of the tasks provided by an exemplary embodiment. As shown in Figure 18, when the display area 1700 includes the user A as the performer. When the task and user A are not the performer's task, the enterprise WeChat client 1 can prioritize the tasks of user A as the performer. For example, when user A is the performer of task 1708, not the performer of tasks 1704-1706. As shown in FIG. 18, the enterprise WeChat client 1 can arrange the task 1708 above the tasks 1704-1706, so that the user A can preferentially view the task 1708, and more conveniently configure the task 1708, etc. In an embodiment, when it is detected that the user A triggers the task 1708 shown in FIG. 17-18, such as determining that the user A clicks on the task content of the task 1708, the enterprise WeChat client 1 may show the one shown in FIG. a task information display interface 1900 for displaying information of the task 1708, such as task content, task performer, task deadline, The task-related conference, task execution status, etc., is not limited in this specification. The task information display interface 1900 may include a task manipulation option 1902 (equivalent to the task manipulation option 1708A described above), so that the user A can control the task by triggering the task. Option 1902 implements state configuration for task 1708. When task 1708 is created by user A, task information presentation interface 1900 can include an "end task" option such that user A can end task 1708 through the option. Similarly, for user A For the triggering operation of the task 1704, the enterprise WeChat client 1 can display the task information display interface 2000 shown in FIG. 20, and the task information display interface 2000 is used to display the information of the task 1704. Here, the task information display interface can be referred to above. 1900. Since user A is not the executor of task 1704, the task information display interface 2000 included in the task information presentation interface 2000 is configured to be in an unmanageable state (corresponding to the task manipulation option 1704A described above), so that the user A can only view the information of the task 1704. It is not possible to implement state configuration for task 1704. Meanwhile, when the task 1704 is created by the user A, the task information presentation interface 2000 may include an "end task" option so that the user A can end the task 1704 through the option. In an embodiment, the enterprise WeChat client 1 may provide a "alert message" function, based on which the alert message for any event may be sent, such as a meeting reminder message for a meeting event, a task reminding message for a task, and an attendance event. Attendance reminder messages, etc. The enterprise WeChat client 1 can send reminder messages in various ways, such as through instant messaging, newsletter, telephone, etc., wherein when the enterprise WeChat client 1 sends a message type reminder message, the message type reminder message is compared to instant messaging. The message can provide a stronger reminder to the recipient. When the enterprise WeChat client 1 adopts the phone type, the caller is called by the phone and plays a reminder message in the form of a voice to the receiver after being connected, compared to the instant messaging message, Types such as newsletters can provide a stronger reminder. The enterprise WeChat client 1 can send a reminder message to the receiver each time by using one or more of the above ways. Based on the “alert message” function described above, the conference related interface 500 may include a message content display interface for the conference reminder message of the conference “H project design progress report”, and the user A may receive the message content after receiving the conference reminder message. The presentation mediation and unification of the content related to the meeting, the meeting minutes, tasks, etc., and the meeting “H project design progress report” facilitates user A to quickly obtain all the “H project design progress report” through the message content display interface. Related content. Based on the above-mentioned "alert message" function, the task information display interface 1900 may include a message content presentation interface of the task reminder message corresponding to the task 1708. The task information display interface 2000 may include a message content presentation interface of the task reminder message corresponding to the task 1704. Taking the task information display interface 1900 as an example, the user A can transfer to the task information display interface 1900 through the conference related interface 500, and can directly enter the task information display interface 1900 through the "alert message" function supported by the enterprise WeChat client 1. . In particular, when user A assigns a task to a non-participant who does not participate in the conference "H project design progress report", the non-participant can view the assigned task corresponding based on the "alert message" function supported by the enterprise WeChat client. The task content presentation interface of the task reminder message to complete related tasks. FIG. 21 is a schematic diagram showing another information showing a meeting minutes and tasks in a conference related interface according to an exemplary embodiment. As shown in FIG. 21, the conference related interface 2100 presented by the enterprise WeChat client 2 corresponding to the user B may include conference information 2102 (corresponding to the conference information 502 described above) and the display area 2104 (corresponding to the display area 1700 described above). The presentation area 2104 may show information of the meeting minutes created by the user A, and information of the tasks 2106-2110 (eg, task content, task performers, task execution status indicated by status information 2112, etc.). Wherein, since user B belongs to the executor of task 2106 and is not the executor of task 2108 and task 2110, enterprise WeChat client 2 can display task 2106 in front of task 2108 and task 2110, so that user B can perform task 2106. View and control, etc. Meanwhile, since the user B belongs to the executor of the task 2106, the task manipulation option 2106A corresponding to the task 2106 can be displayed in the display area 2104, so that the user B can perform the state configuration on the task 2106 by triggering the task manipulation option 2106A, and the task 2108 and Task 2110, etc. do not show the task control options that User B can control. In an embodiment, when it is detected that the user B triggers the task 2106 shown in FIG. 21, for example, determining that the user B clicks the task content of the task 2106, the enterprise WeChat client 2 may display the task information display interface shown in FIG. 2200. The task information display interface 2200 is configured to display information about the task 2106, such as task content, task performer, task deadline, task-related conference, task execution status, and the like, which are not limited in this specification. The task information presentation interface 2200 can include a task manipulation option 2202 (equivalent to the task manipulation option 2106A described above) such that the user A can implement state configuration for the task 2106 by triggering the task manipulation option 2202. In an embodiment, for the conference "H project design progress report" participants, even if no tasks are assigned, the corresponding conference related interface can be opened through the corresponding enterprise WeChat client, and related to the conference. View the meeting minutes, tasks, etc. related to the meeting in the interface so that they can get relevant information in time. For example, for business leaders, by looking at the executor of the task, the execution status of the task, etc., it is possible to understand the transformation of the results of the meeting, thereby making timely adjustments or changes. In an embodiment, when the user A has the meeting permission creation permission for the conference "H project design progress report", in the conference related interface 500 shown in FIG. 17-18, the display area 1700 may include an editing option. 1712, so that the user A can transfer the editing option 1712 to the meeting minutes display interface 600 as shown in FIG. 15, edit or delete the existing meeting minutes, tasks, etc., or create a new meeting minutes and tasks. Wait. For User B (or other users who do not have the permission to create a meeting minutes), in the meeting related interface 2100 such as shown in FIG. 21, the display area 2104 does not contain an editing option, so that User B cannot have an existing one. Edit or delete meetings, tasks, etc., or create new meeting minutes, tasks, and so on. Of course, in some embodiments, there may be multiple users with the creation rights of the meeting minutes. These users are similar to the user A, and can edit or delete the existing meeting minutes, tasks, etc., or create new ones. The minutes, tasks, etc. of this meeting do not limit the number of such users. In summary, this specification provides the function of creating and maintaining meeting minutes in the mobile group office platform, and realizes the function of generating tasks based on meeting minutes, so that users can conveniently generate tasks in the process of creating meeting minutes. To quickly achieve task assignment. FIG. 23 is a schematic structural diagram of an electronic device according to an exemplary embodiment. Referring to FIG. 23, on the hardware level, the electronic device includes a processor 2302, an internal bus 2304, a network interface 2306, a memory 2308, and a non-volatile memory 2310, and may of course include other hard services required by other services. body. The processor 2302 reads the corresponding computer program from the non-volatile memory 2310 into the memory 2308 and then operates to form a task generating device on a logical level. Of course, in addition to the software implementation, one or more embodiments of the present specification do not exclude other implementations, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited. In each logical unit, it can also be a hardware or a logic device. Referring to FIG. 24, in the software implementation, the task generating apparatus may include: an identifier display unit 2401, which displays a first task creation identifier for the conference minutes content according to the conference minutes content of the conference minutes presentation interface; The generating unit 2402, when it is determined that the first task creation identifier is triggered, generates a corresponding task according to the meeting minutes content. Optionally, the task content of the task includes at least a part of the meeting minutes content. Optionally, the executor of the task includes at least one of the following: an actual participant of the conference, a scheduled participant who does not participate in the conference, and an unscheduled participant who does not participate in the conference. Optionally, the conference summary presentation interface includes a second task creation identifier; the device further includes: an implementation unit 2403, when determining that the second task creation identifier is triggered, implementing a task generation process to generate a corresponding task . Optionally, the task content of the task is used as at least a part of the meeting minutes content. Optionally, information about the task is displayed in the conference related interface. Optionally, the information of the task includes at least one of the following: task content, task performer, task deadline, and task execution status. Optionally, the participant of the conference has the right to view the information of the task. Optionally, the method further includes: a reminding unit 2404, sending a task reminding message to an executor of the task. Referring to FIG. 25, in the software implementation, the task generating apparatus may include: an obtaining unit 2501, which acquires meeting minutes content for a meeting; and a generating unit 2502, which generates a corresponding task according to the meeting minutes content. The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an e-mail device, and a game control. A combination of a tablet, a tablet, a wearable device, or any of these devices. In a typical configuration, the computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include non-permanent memory, random access memory (RAM) and/or non-volatile memory in computer readable media, such as read only memory (ROM) or flash memory ( Flash RAM). Memory is an example of a computer readable medium. Computer readable media including both permanent and non-permanent, removable and non-removable media can be stored by any method or technology. Information can be computer readable instructions, data structures, modules of programs, or other materials. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM). Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM only, digitally versatile A disc (DVD) or other optical storage, magnetic cassette, disk storage, quantum memory, graphene-based storage media or other magnetic storage device or any other non-transportable media that can be used to store information that can be accessed by a computing device. . As defined herein, computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves. It is also to be understood that the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, Other elements not explicitly listed, or elements that are inherent to such a process, method, commodity, or equipment. An element defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device including the element. The foregoing description of the specific embodiments of the specification has been described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the scope of the claims may be performed in a different order than the embodiments and still achieve the desired results. In addition, the processes depicted in the figures are not necessarily in a particular order or in a sequential order to achieve the desired results. In some embodiments, multiplex processing and parallel processing are also possible or may be advantageous. The terms used in one or more embodiments of the present specification are for the purpose of describing particular embodiments, and are not intended to limit one or more embodiments. The singular forms "a", "the" and "the" It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of the specification, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information without departing from the scope of one or more embodiments of the present specification. Similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination." The above is only a preferred embodiment of one or more embodiments of the present specification, and is not intended to limit one or more embodiments of the present specification, which is within the spirit and principles of one or more embodiments of the present specification, Any modifications, equivalent substitutions, improvements, etc., are intended to be included within the scope of the protection of one or more embodiments.

11‧‧‧Server

12‧‧‧Network

13‧‧‧User equipment

131‧‧‧Mobile phones

132‧‧‧PC

14‧‧‧User equipment

141‧‧‧Mobile phones

142‧‧‧PC

500‧‧‧Meeting related interface

502‧‧‧Meeting information

504‧‧‧Add meeting minutes option

600‧‧‧Meetings presentation interface

602‧‧‧Memorial minutes input area

604‧‧‧Task creation logo

606‧‧‧ Minutes of the meeting

608‧‧‧ functional identification

Meeting minutes of 610‧‧

612‧‧‧ functional identification

614‧‧‧ Mission

616‧‧‧ tasks

618‧‧‧ mission

620‧‧‧ tasks

1000‧‧‧Task creation interface

1002‧‧‧Task content options

1004‧‧‧Task performer options

1006‧‧‧Task deadline options

1400‧‧‧Task creation interface

1402‧‧‧Task content options

1404‧‧‧Task performer options

1406‧‧‧Task deadline options

1600‧‧‧Task assignment prompt information

1700‧‧‧Display area

Information on the minutes of the 1702‧‧‧ meeting

1704‧‧‧Question

1704A‧‧‧Task control options

1706‧‧‧ Mission

1708‧‧‧ Mission

1708A‧‧‧Task control options

1710‧‧‧Status Information

1712‧‧‧Editing options

1900‧‧‧ Mission Information Display Interface

1902‧‧‧Task control options

2000‧‧‧ Mission Information Display Interface

2002‧‧‧Task control options

2100‧‧‧Meeting related interface

2102‧‧‧Meeting Information

2104‧‧‧Display area

2106‧‧‧Question

2106A‧‧‧Task control options

2108‧‧‧Question

2110‧‧‧Question

2112‧‧‧Status Information

2200‧‧‧ Mission Information Display Interface

2202‧‧‧Task control options

2302‧‧‧ Processor

2304‧‧‧Internal busbar

2306‧‧‧Network interface

2308‧‧‧ memory

2310‧‧‧ Non-volatile memory

2401‧‧‧ logo shows unit

2402‧‧‧Task generation unit

2403‧‧‧ Implementation unit

2404‧‧‧Reminder unit

2501‧‧‧Acquisition unit

2502‧‧‧Generating unit

FIG. 1 is a schematic structural diagram of a task generation system according to an exemplary embodiment. FIG. 2 is a flowchart of a task generation method according to an exemplary embodiment. FIG. 3 is a flowchart of another task generation method provided by an exemplary embodiment. FIG. 4 is a flowchart of still another task generation method provided by an exemplary embodiment. FIG. 5 is a schematic diagram of a conference related interface provided by an exemplary embodiment. FIG. 6 is a schematic diagram of a conference minutes presentation interface provided by an exemplary embodiment. FIG. 7 is a schematic diagram of an input meeting minutes provided by an exemplary embodiment. FIG. 8 is a schematic diagram of another conference related interface provided by an exemplary embodiment. FIG. 9 is a schematic diagram of another conference summary display interface provided by an exemplary embodiment. FIG. 10 is a schematic diagram of a task creation interface provided by an exemplary embodiment. FIG. 11 is a schematic diagram of a view creation task provided by an exemplary embodiment. FIG. 12 is a schematic diagram of another task creation interface provided by an exemplary embodiment. FIG. 13 is a schematic diagram of another view creation task provided by an exemplary embodiment. FIG. 14 is a schematic diagram of still another task creation interface provided by an exemplary embodiment. FIG. 15 is a schematic diagram of still another view creation task provided by an exemplary embodiment. FIG. 16 is a schematic diagram of a distribution task provided by an exemplary embodiment. FIG. 17 is a schematic diagram of information showing a meeting minutes and tasks in a conference related interface according to an exemplary embodiment. FIG. 18 is a schematic diagram showing an arrangement of tasks according to an exemplary embodiment. FIG. 19 is a schematic diagram of a task information display interface provided by an exemplary embodiment. FIG. 20 is a schematic diagram of another task information display interface provided by an exemplary embodiment. FIG. 21 is a schematic diagram showing another information showing a meeting minutes and tasks in a conference related interface according to an exemplary embodiment. FIG. 22 is a schematic diagram of still another task information display interface provided by an exemplary embodiment. FIG. 23 is a schematic structural diagram of an electronic device according to an exemplary embodiment. 24-25 are block diagrams of a task generating apparatus provided by an exemplary embodiment.

Claims (20)

A task generation method, comprising: displaying, according to a meeting minutes content of a meeting minutes presentation interface, a first task creation identifier for the meeting minutes content; when determining that the first task creation identifier is triggered, according to the meeting The minutes content generates the corresponding tasks. The method of claim 1, wherein the task content of the task includes at least a portion of the meeting minutes content. The method of claim 1, wherein the executor of the task comprises at least one of: an actual participant of the meeting, a predetermined participant who does not participate in the meeting, and an unscheduled participant who does not participate in the meeting. . The method of claim 1, wherein the meeting summary presentation interface includes a second task creation identifier; the method further comprising: when it is determined that the second task creation identifier is triggered, implementing a task generation process to generate a corresponding task . The method of claim 4, wherein the task content of the task is taken as at least a portion of the meeting minutes content. The method of claim 1, wherein the information of the task is displayed in the conference related interface. The method of claim 6, wherein the information of the task comprises at least one of the following: a task content, a task performer, a task deadline, and a task execution state. The method of claim 1, wherein the participant of the meeting has the viewing right of the information of the task. The method of claim 1, further comprising: sending a task reminder message to an executor of the task. A task generation method, comprising: obtaining meeting minutes content for a meeting; and generating a corresponding task according to the meeting minutes content. A task generating apparatus, comprising: an identifier display unit, according to a meeting minutes content of a meeting minutes presentation interface, showing a first task creation identifier for the meeting minutes content; a task generating unit, when determining the first task When the creation identifier is triggered, a corresponding task is generated according to the meeting minutes content. The device of claim 11, wherein the task content of the task comprises at least a portion of the meeting minutes content. The device of claim 11, wherein the executor of the task comprises at least one of: an actual participant of the meeting, a predetermined participant not participating in the meeting, and an unscheduled participant not participating in the meeting . The device of claim 11, wherein the meeting summary presentation interface includes a second task creation identifier; the apparatus further comprising: an implementation unit, when it is determined that the second task creation identifier is triggered, implementing a task generation process to generate The corresponding task. The device of claim 14, wherein the task content of the task is deemed to be at least a portion of the meeting minutes. The device of claim 11, wherein the information of the task is displayed in the conference related interface. The device of claim 16, wherein the information of the task comprises at least one of the following: task content, task performer, task deadline, task execution status. The device of claim 11, wherein the participant of the meeting has viewing rights to the information of the task. The device of claim 11, further comprising: a reminding unit that sends a task reminder message to an executor of the task. A task generating apparatus, comprising: an acquiring unit, acquiring meeting minutes content for a meeting; and a generating unit, generating a corresponding task according to the meeting minutes content.