Task management apparatus, program, task management method, and task management system

Abstract

To provide a technique for reliably transmitting e-mail to a target address when a task that includes e-mail transmission is executed.SOLUTION: A task management apparatus includes: a trigger information acquisition unit which acquires trigger information indicating a request from a client; a task determination unit that determines a task related to a service to be provided to the client, based on the trigger information; a task step extraction unit which extracts one or more task steps from the task determined by the task determination unit; and an e-mail control unit which controls executing an e-mail creation task step which is a task step of accepting creation of a message created by a person in charge to the client. The e-mail control unit determines an addressee based on the task, transmits the message to the addressee, and prohibits the person in charge from changing the addressee when executing the e-mail creation task step.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a task management device, a program, a task management method, and a task management system. [Background technology]

[0002] With the development of information processing technology, there is a demand for technology that can appropriately manage tasks according to client requests. There is a technology that uses email to transmit information about tasks.

[0003] In the task management system disclosed in Patent Document 1, when a user instructs an email client running on a PC to create a task based on an email, the email client instructs a workflow engine to create the task. When the email client notifies the workflow engine of an email reception notification accompanied by header information, the workflow engine performs a task search to identify the target task and registers the message ID of the email as an attachment to the task information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-049427 Summary of the Invention [Problem to be solved by the invention]

[0005] When executing a task that involves sending an email, there is a need for a technology that can reliably send the email to the target recipient. The technology disclosed in Patent Document 1 does not assume that emails will be reliably sent to the recipient when the task is executed.

[0006] The present invention has been made in consideration of the above points, and aims to provide a technology for reliably sending email to a target recipient when performing a task that involves sending email. [Means for solving the problem]

[0007] The present application includes a number of means for solving the above problems, examples of which are as follows.

[0008] In order to solve the above problem, a task management device according to one embodiment of the present invention comprises a trigger information acquisition unit that acquires trigger information indicating a client's request, a task determination unit that determines a task related to a business to be provided to the client based on the trigger information, a task step extraction unit that extracts one or more task steps from the task determined by the task determination unit, and an email control unit that controls the execution of an email creation task step, which is a task step that accepts a person in charge of creating a message to the client, and is characterized in that the email control unit determines a destination based on the task, sends the message to the destination, and when executing the email creation task step, prevents the person in charge from changing the destination.

[0009] The task management device may be characterized by including a task management unit that detects the completion of each task step and manages the progress of the task, and the email control unit may be characterized by accepting the creation of the message when the task management unit determines that the start conditions for the email creation task step are met.

[0010] The task management unit may be characterized in that, upon detecting the completion of another task step that is defined as a start condition for the email creation task step, it notifies a person in charge of the email creation task step.

[0011] The task management device may be characterized by having a person in charge determination unit that refers to member information that associates candidate persons with the skills they possess, and determines a person in charge for each task step based on the skills required by the task step.

[0012] The task management device may include a person in charge determination unit that refers to member information that associates candidate persons with the skills they possess, and determines a person in charge for each task step based on the skills required by the task step, and a task step execution unit that executes specified task steps that do not require operation by a person in charge, and the person in charge determination unit may be characterized in that it inhibits the determination of a person in charge for the specified task step.

[0013] The mail control unit may be characterized in that, upon receiving a specification of data to be attached to the message, it determines whether or not a character string indicating the client is included in a name of the data.

[0014] The mail control unit may be characterized in that, when it determines that the creation of the message is complete, it determines whether or not a character string indicating the client is included in a title of the message.

[0015] Another aspect of the present invention is a program that causes a computer processing unit to execute a task management method, and includes a trigger information acquisition procedure that acquires trigger information indicating a client's request, a task determination procedure that determines a task related to a business to be provided to the client based on the trigger information, a task step extraction procedure that extracts one or more task steps from the task determined in the task determination procedure, and an email control procedure that controls the execution of an email creation task step, which is a task step that accepts a person in charge from creating a message to the client, and is characterized in that the email control procedure determines a destination based on the task, sends the message to the destination, and when executing the email creation task step, prevents the person in charge from changing the destination.

[0016] Another aspect of the present invention is a task management method using a task management device, comprising: a trigger information acquisition procedure for acquiring trigger information indicating a client's request; a task determination procedure for determining tasks that constitute a business to be provided to the client based on the trigger information; a task step extraction procedure for extracting one or more task steps from the tasks determined in the task determination procedure; and an email control procedure for controlling the execution of an email creation task step, which is a task step that accepts a person in charge from creating a message to the client, wherein the email control procedure determines a destination based on the task, sends the message to the destination, and when executing the email creation task step, prevents the person in charge from changing the destination.

[0017] Another aspect of the present invention provides a task management system comprising a person in charge's terminal device and a task management device, wherein the person in charge's terminal device comprises a message creation unit that accepts input operations related to messages to clients, and the task management device comprises a trigger information acquisition unit that acquires trigger information indicating the client's request, a task determination unit that determines tasks related to business to be provided to the client based on the trigger information, a task step extraction unit that extracts one or more task steps from the tasks determined by the task determination unit, and a mail control unit that controls the execution of an email creation task step, which is the task step that accepts the creation of a message to the client based on input operations on the person in charge's terminal device, and wherein the mail control unit determines a destination based on the task, sends the message to the destination, and when executing the email creation task step, suppresses changes to the destination by the person in charge. [Effects of the Invention]

[0018] According to the present invention, it is possible to provide a technique for reliably sending an email to a target recipient when executing a task involving sending an email.

[0019] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 is a diagram illustrating an example of an overview of a task management system. [Figure 2] FIG. 2 is a diagram illustrating an example of functional blocks of a task management system. [Figure 3] 3A and 3B are diagrams showing examples of the data structure of task information, member information, and task step information, respectively. Fig. 3A shows an example of the data structure of task information, Fig. 3B shows an example of the data structure of member information, and Fig. 3C shows an example of the data structure of task step information. [Figure 4] FIG. 2 illustrates an example of a hardware configuration of a task management device. [Figure 5] 10 is a flowchart illustrating an example of a task execution process. [Figure 6] 10 is a flowchart showing an example of an email creation task step. [Figure 7] 7A and 7B are diagrams illustrating an example of a step definition information display screen and a client definition information display screen, respectively. Fig. 7A shows an example of the step definition information display screen, and Fig. 7B shows an example of the client definition information display screen. DETAILED DESCRIPTION OF THE INVENTION

[0021] An example of an embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing an example of an overview of a task management system 1. In the task management system 1, a series of operations generated in response to a client request is treated as a "task." A task management device 10 monitors the progress of a task in order to manage the task from start to finish. Each person in charge of the task management system 1 uses a dedicated application installed on a person in charge terminal device 40 (described later) to check the assigned work and report completion.

[0022] The task management system 1 includes a client terminal device owned by a client, a task management device 10, and a person in charge terminal device 40 (described later). The client terminal devices include a client terminal device 20 and a client system management device 30.

[0023] First, trigger information indicating some kind of request is sent from the client terminal device to the task management device 10. The task management device 10 acquires the trigger information using one of a number of different acquisition methods. As an example, a client person operates the client terminal device 20 and inputs information indicating a request to a portal site on a browser. The input information is treated as trigger information, and the task management device 10 acquires the trigger information from the client terminal device 20. Trigger information based on input to the portal site will be described as a portal trigger. The task management device 10 treats selections from options displayed on the portal site and input character strings as trigger information.

[0024] As another example, the task management device 10 acquires trigger information when a client person in charge calls a telephone number managed by the task management system 1. Trigger information input directly or indirectly by telephone will be described as a telephone response trigger. The task management device 10 acquires information input in response to an automated voice message using a telephone input reception system (not shown) and treats it as trigger information. The task management device 10 may also treat information input by a system person who understands the content of the call as trigger information.

[0025] As another example, the task management device 10 acquires trigger information by receiving an email from a client system management device 30 or an email from a client terminal device 20. Trigger information based on input via an email system will be described as an email trigger. For example, the task management device 10 handles a character string entered in an email as trigger information.

[0026] As another example, the client system management device 30 calls the task management device 10 via an API (Application Programming Interface), causing the task management device 10 to acquire trigger information. Trigger information acquired via the API will be described as an API trigger. The task management device 10 handles information received from a client-side terminal device via the API as trigger information.

[0027] As another example, the task management device 10 schedules a predetermined process to be performed at a predetermined timing in response to an input operation by a system administrator. Trigger information including the timing to start the process and the process content will be described as a schedule trigger. Each piece of trigger information can be identified by a trigger ID.

[0028] When the task management device 10 acquires trigger information by any of the acquisition methods, it determines a task related to the business to be provided to the client. The task management device 10 divides the determined task and extracts one or more task steps. The task management device 10 determines a person in charge of executing the task step and executes processing related to the task. The task management device 10 manages the execution processing of each task step and provides the business related to the task to the client.

[0029] The task management device 10 manages the progress of each task step, and when the start condition of a task step is met, it sends a notification to the person in charge of that task step. Note that at least the task manager can check the person in charge of each task step and the progress using the display screen of the dedicated application mentioned above. Each person assigned to a task step may also be able to check the progress of other task steps extracted from the same task.

[0030] In the example shown in FIG. 1, the task management device 10 determines a "trouble reception task" as a task related to a business to be provided to a client based on trigger information acquired by any of the acquisition methods. The task management device 10 extracts the following task steps from the "trouble reception task," namely, "Task 1: Work," "Task 1: Check," "Email creation: Work," "Email creation: Check," and "Email transmission." The task management device 10 determines the person in charge of "Task 1: Work" to be "Mr. A" and the person in charge of "Task 1: Check" to be "Mr. B" using the skills required for each task step and the skills possessed by the candidate person. The task management device 10 also determines the person in charge of "Email creation: Work" to be "Mr. C" and the person in charge of "Email creation: Check" to be "Mr. D." The task management device 10 does not determine the person in charge of "Email transmission."

[0031] Hereinafter, a task step for creating an email for a client will be described as an email creation task step, and a task step for sending a message created by the email creation task step will be described as an email sending task step. When executing an email creation task step, the task management device 10 suppresses changes to the destination by a person performing input operations related to the email. When executing an email sending task step, the task management device 10 determines a destination based on the task and sends a message to that destination.

[0032] In this embodiment, each person in charge checks the assigned work using a dedicated application. Similarly, the task manager uses a dedicated application to manage the progress of each task step. The dedicated application is not limited to an application installed on each person in charge terminal device 40. For example, the task management device 10 may provide a web application with the same functions as the dedicated application, and the person in charge of the person in charge terminal device 40 may operate the web application via a browser.

[0033] 2 is a diagram showing an example of functional blocks of the task management system 1. The task management system 1 includes a task management device 10, a client terminal device 20, a client system management device 30, and a person in charge terminal device 40. The task management device 10, the client terminal device 20, the client system management device 30, and the person in charge terminal device 40 are connected to each other via a network N so that they can communicate with each other.

[0034] The task management device 10 is an information processing device such as a server computer or a PC (Personal Computer), and is operated by a task management service provider that uses the task management system 1, for example.

[0035] The task management device 10 comprises a processing unit 110, a storage unit 120, an input unit 130, an output unit 140, and a communication unit 150. The processing unit 110 performs overall control of the task management device 10. The storage unit 120 stores information required for processing by the processing unit 110. The input unit 130 accepts information input to the task management device 10 using an input device. The output unit 140 outputs information stored in the task management device 10 to an output device. The communication unit 150 mediates the transmission and reception of information to and from the client terminal device 20, the client system management device 30, or the person in charge terminal device 40.

[0036] The processing unit 110 includes a trigger information acquisition unit 111, a task determination unit 112, a task step extraction unit 113, an email control unit 114, a person in charge determination unit 115, a task management unit 116, and a task step execution unit 117. The trigger information acquisition unit 111 acquires trigger information indicating a client request from the client terminal device 20 or the client system management device 30. The trigger information acquisition unit 111 identifies a method for acquiring the trigger information and stores the method in association with the acquired trigger information. Note that the trigger information acquisition unit 111 may acquire trigger information based on an input operation via the input unit 130 by a person in charge who receives a call from a client, or may acquire trigger information related to a schedule trigger that starts processing at a predetermined timing.

[0037] The task determination unit 112 determines a task related to a business to be provided to a client based on the trigger information. The task determination unit 112 determines a task corresponding to the acquired trigger information as a task related to a business to be provided to a client by referring to information indicating the correspondence between the trigger information and task information 121, which is stored in an area (not shown) of the storage unit 120. The task step extraction unit 113 extracts one or more task steps from the task determined by the task determination unit 112. For example, the task step extraction unit 113 refers to task information 121 (described later) to extract task steps related to the task determined by the task determination unit 112.

[0038] The mail control unit 114 controls the execution of a mail creation task step, which is a task step that accepts the creation of a message to a client by a person in charge. For example, the mail control unit 114 controls the creation of an e-mail using the mail function of a dedicated application installed on the person in charge terminal device 40. The mail control unit 114 accepts the creation of a message by the person in charge terminal device 40 when the task management unit 116 determines that the start conditions for the mail creation task step are met. In the mail sending task step, the mail control unit 114 determines a destination based on the task and sends the created message. Note that the mail control unit 114 suppresses changes to the destination by the person in charge terminal device 40 when executing the mail creation task step.

[0039] When the mail control unit 114 receives the specification of the attached data to be attached to the message, it determines whether the name of the attached data contains a character string indicating the client. The mail control unit 114 also determines whether the title of the message contains a character string indicating the client.

[0040] The person in charge determination unit 115 refers to member information 122 (described below) in which candidate persons are associated with the skills they possess, and determines a person in charge for each task step based on the skills required for the task step. For example, the person in charge determination unit 115 notifies candidate persons in charge who have the skills required for the task step in the member information 122, and determines a person in charge from among the candidate persons who responded, depending on the timing of the response. Note that the person in charge determination unit 115 determines a person in charge for the first task step (described below), and suppresses the determination of a person in charge for the second task step.

[0041] The task management unit 116 manages the progress of tasks by detecting the completion of processing for each task step. In the example shown below, task steps are classified into first task steps, in which processing is executed by an input operation by the person in charge, and second task steps, in which processing is executed by the task step execution unit 117 described below. The first task step is a task step that requires an input operation by the person in charge at some point, while the second task step is a task step that is executed automatically without requiring an input operation by the person in charge. An email creation task step corresponds to the first task step, and an email sending task step corresponds to the second task step.

[0042] When the progress of the task satisfies the start condition of a first task step, the task management unit 116 notifies the person in charge of the first task step. For example, when the task management unit 116 detects the end of another task step that is defined as the start condition of an email creation task step, it notifies the person in charge of the email creation task step. When the progress of the task satisfies the start condition of a second task step, the task management unit 116 causes the task step execution unit 117, described below, to execute the processing of the second task step.

[0043] The task step execution unit 117 executes a predetermined process in the second task step, which is a predetermined task step. The task step execution unit 117 receives a signal indicating an execution command that specifies the process from the task management unit 116, and executes the process related to the command. Note that the task step execution unit 117 may notify an administrator defined in the task information 121 (described later) when the process of the second task step is completed.

[0044] The storage unit 120 stores task information 121, member information 122, task step information 123, and client information 124. The task information 121 is information about a task that is activated by a trigger ID that identifies trigger information. The member information 122 is information that associates the skills possessed by each candidate person in charge. The task step information 123 is information that associates information indicating the content of the processing to be performed, the required position, etc., for each task step. The client information 124 is information that associates information that identifies a client that has a client-side terminal device with the destination of an email to that client.

[0045] The client terminal device 20 is a terminal device operated by a client staff member, and is, for example, an information processing device such as a PC, smartphone, PDA (Personal Digital Assistant), or tablet terminal. The client terminal device 20 includes a processing unit 210, a storage unit 220, an input unit 230, an output unit 240, and a communication unit 250. The processing unit 210 comprehensively controls the entire client terminal device 20. The storage unit 220 stores information required for processing by the processing unit 210. The input unit 230 accepts information input to the client terminal device 20 using an input device. The output unit 240 outputs information stored in the client terminal device 20 to an output device. The communication unit 250 mediates the transmission and reception of information to and from the task management device 10, the client system management device 30, or the staff member terminal device 40.

[0046] The processing unit 210 includes a trigger information output unit 211 and an email control unit 212. The trigger information output unit 211 outputs trigger information to the task management device 10 based on an input operation by a client person in charge. The trigger information output unit 211 transmits, for example, information input to a portal site to the task management device 10 as trigger information. The trigger information output unit 211 may output predetermined trigger information when executing a predetermined process that does not require an input operation by a client person in charge. The email control unit 212 controls the creation, reception, and transmission of emails. For example, the email control unit 212 acquires emails sent under the control of the email control unit 114 of the task management device 10.

[0047] The client system management device 30 is a terminal device owned by a client, such as a server computer or an information processing device such as a PC, and manages the client's business system. The client system management device 30 includes a processing unit 310, a storage unit 320, an input unit 330, an output unit 340, and a communication unit 350. The processing unit 310 not only controls the entire client system management device 30, but also executes predetermined business-related processes in the client system management device 30.

[0048] The storage unit 320 stores information necessary for processing by the processing unit 310. The input unit 330 accepts information input to the client system management device 30 using an input device. The output unit 340 outputs information stored in the client system management device 30 to an output device. The communication unit 350 mediates the transmission and reception of information to and from the task management device 10, the client terminal device 20, or the person in charge terminal device 40.

[0049] The processing unit 310 includes a trigger information output unit 311. When a command to output trigger information is executed by the processing unit 310 in a predetermined process related to a business, the trigger information output unit 311 outputs trigger information to the task management device 10. For example, when the execution of the predetermined process is stopped, the trigger information output unit 311 outputs trigger information indicating an error.

[0050] The person in charge terminal device 40 is a terminal device owned by a person in charge of executing a task managed by the task management device 10, and is, for example, an information processing device such as a PC, smartphone, PDA (Personal Digital Assistant), or tablet terminal. The person in charge terminal device 40 includes a processing unit 410, a storage unit 420, an input unit 430, an output unit 440, and a communication unit 450. The processing unit 410 comprehensively controls the entire person in charge terminal device 40 and executes predetermined processing related to task steps based on input operations by the person in charge. The storage unit 420 stores information necessary for processing by the processing unit 410. The input unit 430 accepts information input to the person in charge terminal device 40 using an input device. The output unit 440 outputs information stored in the person in charge terminal device 40 to an output device. The communication unit 450 mediates the transmission and reception of information between the task management device 10, the client terminal device 20, or the client system management device 30.

[0051] The processing unit 410 includes a message creation unit 411. The message creation unit 411 creates an email message using a dedicated application based on input operations by the person in charge. Note that the message creation unit 411 may create the email message using general email creation software installed on the person in charge terminal device 40, or may create the email message using general email creation software on the network N.

[0052] 3A and 3B are diagrams showing examples of the data structures of task information 121, member information 122, and task step information 123. Fig. 3A is a diagram showing an example of the data structure of task information 121, Fig. 3B is a diagram showing an example of the data structure of member information 122, and Fig. 3C is a diagram showing an example of the data structure of task step information 123.

[0053] Task information 121 is information about a task that is started by a trigger, and is information in which information indicating one or more task steps and an administrator are associated with a task ID. The task ID is identification information that identifies a task. The information indicating task steps is information that identifies the processing of each task step obtained by dividing the processing of a task. Note that in task information 121, information indicating one or more task steps is associated with one task ID so that the processing order can be identified. The administrator is identification information that identifies the administrator of the task.

[0054] As shown in FIG. 3(B), member information 122 is information in which position information and information identifying one or more skills are associated with a member ID. The member ID is identification information that identifies a candidate person who can execute the processing in the first task step. Position information is information that identifies the position of the candidate person. Information that identifies one or more skills is information that identifies the skills possessed by the candidate person. Skills include, for example, certification qualifications, skills such as compatible programming languages, compatible OSs (Operating Systems), and past experience in handling tasks. Note that member information 122 does not necessarily have to include position information.

[0055] As shown in FIG. 3(C), task step information 123 is information in which a task step ID is associated with a step type, processing content, job title, operation content, and remarks. The task step ID is identification information that identifies a task step. The step type is information that indicates whether the task step is a first task step or a second task step. The processing content is information that indicates the content of the processing performed in the task step. The job title is information that indicates the job title required of the person in charge when the task step is a first task step. For example, the job title indicates whether the task step is performed by a person in charge, a reviewer, or an approver.

[0056] The operation content is information that indicates the content of the operation to be performed by the person in charge or the reviewer if the task step is the first task step. The notes are information that indicates special notes regarding the task step. For example, if the task step is an "email sending task step," the notes include information that can identify the email recipient.

[0057] 4 is a diagram showing an example of the hardware configuration of task management device 10. Task management device 10 includes a processing unit 11, a memory 12, an external storage device 13, an input IF (Interface) 14, an output IF 15, and a communication IF 16, and these components are connected by a bus.

[0058] The arithmetic device 11 is a arithmetic device such as a CPU (Central Processing Unit), and executes processing in accordance with a program recorded in the memory 12 or the external storage device 13. In the task management device 10, processing is performed by the arithmetic device 11 that operates in accordance with a program read onto the memory 12 or the external storage device 13. Each processing unit constituting the processing unit 110 realizes its respective function by the arithmetic device 11 executing a program.

[0059] The memory 12 is a storage device such as RAM (Random Access Memory) or flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 13 is a writable and readable storage medium and storage media drive, such as an HDD (Hard Disk Drive), CD-R (Compact Disc-Recordable), or DVD-RAM (Digital Versatile Disk-Random Access Memory). The functions of the storage unit 120 are realized by the memory 12 or the external storage device 13. Note that the functions of the storage unit 120 may also be realized by a storage device connected via the communication IF 16.

[0060] The input IF 14 is an interface for receiving input operations from an operator, and is connected to input devices such as a touch panel, keyboard, mouse, microphone, etc. The output IF 15 is an interface for outputting information to a display device such as an LCD (Liquid Crystal Display) display built into the task management device 10.

[0061] The communication IF 16 is an interface for connecting the task management device 10 to the network N and a bus, and is connected to a communication device such as a LAN (Local Area Network) card. The functions of the communication unit 150 are realized by the communication IF 16. The task management device 10 may also have a storage medium drive device (not shown) and input / output information from portable media.

[0062] The processing of each component of task management device 10 may be executed by one piece of hardware or by multiple pieces of hardware. Furthermore, the processing of each component of task management device 10 may be realized by one program or by multiple programs.

[0063] The hardware configurations of the client terminal device 20, the client system management device 30, and the person in charge terminal device 40 are the same as those of the task management device 10, and therefore a description thereof will be omitted.

[0064] 5 is a flowchart showing an example of task execution processing. The processing of this flowchart is executed by the task management device 10.

[0065] First, the trigger information acquisition unit 111 acquires trigger information (step S11). Specifically, the trigger information acquisition unit 111 acquires trigger information due to a portal trigger, a telephone response trigger, or an email trigger output from the trigger information output unit 211 of the client terminal device 20. Alternatively, the trigger information acquisition unit 111 acquires trigger information due to an email trigger or an API trigger output from the trigger information output unit 311 of the client system management device 30. Alternatively, the trigger information acquisition unit 111 acquires trigger information due to a telephone trigger or a schedule trigger input from an input device via the input unit 130. The trigger information acquisition unit 111 associates information indicating a method for acquiring the acquired trigger information with the trigger information and stores it in an area (not shown) of the storage unit 120.

[0066] Next, the task determination unit 112 determines a task (step S12). Specifically, the task determination unit 112 determines the task information corresponding to the trigger information acquired in step S11 as the task to be processed by referring to information indicating the correspondence between trigger information and task information stored in an area (not shown) of the storage unit 120. The task determination unit 112 may determine whether the same task has already been determined within a predetermined time, and if it determines that the same task has already been determined, may end the processing of this flowchart without executing the processing from step S13 onwards. Since the task management device 10 may receive input of multiple pieces of trigger information for the same event, by determining whether the same task has already been determined within a predetermined time, it is possible to prevent the same task from being executed multiple times.

[0067] Next, the task step extraction unit 113 extracts task steps (step S13). Specifically, the task step extraction unit 113 refers to the task information 121 and extracts one or more task steps corresponding to the task ID of the task determined in step S12.

[0068] Next, the task management unit 116 determines the task step to be processed according to the processing order of the task information 121 (step S14). The task management unit 116 determines the task step to be processed from among the unprocessed task steps by referring to the processing order of the task information 121.

[0069] Next, the task management unit 116 determines whether a start condition is satisfied (step S15). Specifically, the task management unit 116 determines whether a start condition previously associated with the task step to be processed is satisfied. For example, when the task management unit 116 detects the end of another task step that is previously set as a start condition, the task management unit 116 determines that the start condition is satisfied.

[0070] Next, the task management unit 116 determines the type of task step to be processed (step S16). The task management unit 116 determines whether the task step determined to be the processing target in step S14 is a first task step or a second task step.

[0071] If the task management unit 116 determines that the task step to be processed is the first task step ("First" in step S16), the person in charge determination unit 115 determines a person in charge of the first task step (step S17). Specifically, the person in charge determination unit 115 identifies the skills and job title associated with the first task step to be processed by referring to the task step information 123. The person in charge determination unit 115 then refers to the member information 122 and determines the person in charge or the reviewer who has the identified skills and job title as the person in charge of the first task step to be processed.

[0072] Note that the method by which the person in charge determination unit 115 determines a person in charge of a task step is not limited to this method. For example, the person in charge determination unit 115 may identify a person in charge of a client and assign the task step to that person. Also, for example, the person in charge determination unit 115 may assign the task step to a person who has an open schedule at the start of processing the task step.

[0073] Next, the task management unit 116 notifies the person in charge (step S18). Specifically, the task management unit 116 transmits the notification to the person in charge terminal device 40 of the person in charge determined in step S17. The notification includes information indicating the processing content of the first task step to be processed.

[0074] Next, the mail control unit 114 determines whether or not the first task step to be executed is a mail creation task step (step S19). Specifically, the mail control unit 114 determines whether or not the first task step to be executed is a mail creation task step.

[0075] When determining that the task is a mail creation task step (YES in step S19), the mail control unit 114 executes the mail creation task step (step S20). This process will be described in detail later.

[0076] If the email control unit 114 determines that the task step is not an email creation task step ("NO" in step S19), the process proceeds to step S21. The person in charge who received the notification sent in step S18 operates the person in charge terminal device 40 to process the first task step to be processed.

[0077] If the task management unit 116 determines in step S19 that the task is not an email creation task step, or after the processing of step S20 is completed, the task management unit 116 detects the end of the work (step S21). Specifically, the task management unit 116 detects the end of the first task step executed in the person in charge terminal device 40 as a result of the notification in step S18. For example, when the task management unit 116 receives a notification indicating the end of the first task step from the person in charge terminal device 40, it considers this to be the detection of the end of the work.

[0078] If the task management unit 116 determines that the task step to be processed is the second task step (if "second" in step S16), the task step execution unit 117 executes the processing (step S22). Specifically, the task step execution unit 117 executes the processing predetermined in the task information 121 for the second task step determined to be the processing target in step S14. In addition, the person in charge determination unit 115 does not determine a person in charge for the second task step.

[0079] If the task step to be processed is an email sending task step, the end of the email creation task step is detected as the start condition for this task step. In the email creation task step, the email control unit 114 identifies the client defined in the task step (step S201, described below). The email control unit 114 identifies the email address of the client as the client's destination by referring to the client information 124. The email control unit 114 sends the message created in the email creation task step to the identified email address.

[0080] The process executed in step S23 is similar to the process executed in step S21, and therefore a description thereof will be omitted.

[0081] After the process of step S21 or step S23 is completed, the task management unit 116 determines whether or not there are any unprocessed task steps (step S24). Specifically, the task management unit 116 determines whether or not there are any task steps among the task steps extracted in step S13 that have not been determined as processing targets in step S14.

[0082] If the task management unit 116 determines that an unprocessed task step exists (YES in step S24), the process proceeds to step S14. That is, the process from step S14 onwards is executed for one of the unprocessed task steps.

[0083] If the task management unit 116 determines that there are no unprocessed task steps ("NO" in step S24), it notifies a predetermined person in charge (step S25). Specifically, the task management unit 116 refers to the task information 121, identifies the manager associated with the task to be processed, and transmits information indicating that the processing has ended. Note that this processing is not essential and may be omitted. The processing unit 110 then ends the processing of this flowchart.

[0084] As described above, according to this embodiment, task processing can be efficiently executed. In particular, when executing a task that includes an email creation task step and other task steps, it is possible to determine a person who is suitable for executing each task step and execute the processing of each task step at an appropriate timing.

[0085] Furthermore, even when executing a task that includes an email creation task step and a second task step, each task step can be executed at an appropriate timing. For example, when an inquiry is made to a client via email and then a second task step that does not require input operations by the person in charge is executed, or when the second task step is executed and then the results are reported via email, the processing of each task step can be managed efficiently.

[0086] Fig. 7 shows an example of a step definition information display screen 461 and a client definition information display screen 462. Fig. 7(A) shows an example of the step definition information display screen 461, and Fig. 7(B) shows an example of the client definition information display screen 462.

[0087] The manager can check the processing details of each task step using the person in charge terminal device 40. The step definition information display screen 461 is displayed on the manager's person in charge terminal device 40. As an example, the step definition information includes a step code, which is identification information that identifies the task step, a step name, which is the name of the task step, and arguments, which are values ​​passed during processing. The processing unit 110 of the task management device 10 uses the task step information 123 to identify information necessary to display the step definition information and transmits it to the person in charge terminal device 40.

[0088] The client definition information display screen 462 is displayed on the manager's terminal device 40. As an example, the client definition information display screen 462 includes a client code, which is identification information for identifying the client, a client tag code used for association with other information, and the client's email address. The processing unit 110 of the task management device 10 uses the client information 124 to identify information necessary for displaying the client definition information display screen 462 and transmits it to the manager's terminal device 40.

[0089] The step definition information display screen 461 shown in Fig. 7(A) includes "abc.mail" as an argument. The client definition information display screen 462 shown in Fig. 7(B) includes "abc.mail" as a client tag code, which is the same as the argument of the step definition information display screen 461 shown in Fig. 7(A). When executing a mail sending task step, the mail control unit 114 of the task management device 10 uses the argument of the step definition information to determine the corresponding email address as the destination.

[0090] 6 is a flowchart showing an example of the mail creation task step, which shows the details of the process executed in step S20 of FIG.

[0091] First, the email control unit 114 identifies a client (step S201). Specifically, the email control unit 114 identifies a client associated with the trigger information acquired in step S11 of Fig. 5. The email control unit 114 identifies a client that has the client terminal device 20 or client system management device 30 that sent the trigger information. Note that if the trigger information is acquired by a telephone trigger or a schedule trigger, the email control unit 114 identifies a client that has been previously associated with the trigger information by the trigger information acquisition unit 111 when acquiring the trigger information.

[0092] Next, the email control unit 114 displays an email creation screen on the person in charge's terminal device 40 (step S202). Specifically, the email control unit 114 displays the email creation screen on the person in charge's terminal device 40 owned by the person in charge determined in step S17 of FIG. 5. The message creation unit 411 of the person in charge's terminal device 40 displays the email creation screen using a dedicated application pre-installed on the person in charge's terminal device 40. When displaying the email creation screen, the email control unit 114 may display information indicating the client identified in step S201, or may display the client's email address. The email control unit 114 prevents changes to the client's destination address. In other words, the person in charge's terminal device 40 cannot change the client's email address.

[0093] Next, the email control unit 114 determines whether or not the selection of attached data has been accepted (step S203). Specifically, the email control unit 114 determines whether or not the attached data to be attached to the email has been selected on the person in charge terminal device 40.

[0094] When the mail control unit 114 determines that the selection of attached data has been accepted ("YES" in step S203), it determines whether the name of the attached data satisfies a predetermined condition (step S204). For example, the mail control unit 114 determines whether the name of the attached data includes a character string indicating the client identified in step S201. The character string indicating the client is, for example, the name of the client. Note that the predetermined condition is not limited to whether the name of the attached data includes a character string indicating the client. For example, the mail control unit 114 may determine whether the name of the attached data includes a character string indicating a task or a character string indicating a method for acquiring trigger information.

[0095] When the mail control unit 114 determines that the selection of the attached data has been accepted, it writes link information indicating the storage location of the attached data in the email. The client who receives the email can obtain the attached data at the link destination by operating the client terminal device 20.

[0096] In addition, the email control unit 114 can accept an input operation indicating an intention to attach data instead of selecting attached data. In this case, information indicating attached data is previously associated with an email creation task step in the task information 121. When the email control unit 114 accepts an input operation indicating an intention to attach data, it refers to the task information 121 to identify the target attached data.

[0097] If the email control unit 114 determines that the attached data name does not satisfy the predetermined condition ("NO" in step S204), the process proceeds to step S203. The email control unit 114 may cause the person in charge terminal device 40 to display an error screen indicating that the attached data name does not satisfy the predetermined condition.

[0098] When the mail control unit 114 determines that the selection of the attached data has not been accepted ("NO" in step S203), or when the mail control unit 114 determines that the attached data name satisfies a predetermined condition ("YES" in step S204), the mail control unit 114 determines whether or not an input operation for completing the work has been accepted (step S205). The mail control unit 114 determines whether or not the mail control unit 212 of the person in charge terminal device 40 has accepted an input operation for completing the work.

[0099] If the mail control unit 114 determines that the input operation for completing the work has not been received ("NO" in step S205), the process proceeds to step S203.

[0100] When the mail control unit 114 determines that an input operation for completing work has been received ("YES" in step S205), it determines whether the mail title satisfies a predetermined condition (step S206). Specifically, in step S205, the mail control unit 114 refers to the title of the e-mail in which the input operation for completing work has been received, and determines whether the predetermined condition is met. For example, the mail control unit 114 determines whether the title of the e-mail includes a character string indicating a client. Note that the predetermined condition is not limited to whether the title of the e-mail includes a character string indicating a client.

[0101] If the email control unit 114 determines that the email title does not satisfy the predetermined condition ("NO" in step S206), the process proceeds to step S205. The email control unit 114 may cause the person in charge terminal device 40 to display an error screen indicating that the email title does not satisfy the predetermined condition.

[0102] If the mail control unit 114 determines that the mail title satisfies the predetermined condition (YES in step S206), the process of this flowchart ends.

[0103] In this embodiment, after the processing of this flowchart is completed, the email control unit 114 executes a task step that has the reviewer confirm the email content. In addition, confirmation by a reviewer is not required in the email creation task step. For example, if the task step information 123 does not include a task step that has the reviewer confirm the email content, the email control unit 114 executes the email sending task step without executing a process that accepts input operations from the reviewer.

[0104] As described above, according to this embodiment, when a task involving sending an e-mail is executed, e-mail can be reliably sent to the target recipient by suppressing changes to the destination in the person in charge terminal device 40. In addition, by determining whether or not the attached data or the e-mail address meets a predetermined condition, it is possible to prevent messages or attached data from being sent to a destination other than the destination.

[0105] In this embodiment, emails are sent to clients under the control of the email control unit 114. However, the email control unit 114 may send information to the client terminal device 20 using means other than email. For example, the email control unit 114 can send messages to clients using specific software that uses email addresses. Even in this case, the email control unit 114 suppresses changes to the destination address in the person in charge terminal device 40.

[0106] In this embodiment, the email control unit 114 also includes link information for the attached data in the email. The email control unit 114 may be configured to prevent access to the attached data even if the link information is selected on the client terminal device 20 if the attached data does not satisfy a predetermined condition.

[0107] In addition, in this embodiment, the email control unit 114 of the task management device 10 executes the email creation task step shown in Fig. 6. However, the email creation task step may also be executed by the message creation unit 411 of the person in charge terminal device 40. In this case, when the email control unit 114 of the task management device 10 determines that the start conditions for the email creation task step are met, it notifies the person in charge terminal device 40 and allows the person in charge terminal device 40 to execute the email creation task step.

[0108] Although the above describes each embodiment of the present invention, the present invention is not limited to the above-described exemplary embodiment and includes various modifications. For example, the above-described exemplary embodiment has been described in detail to facilitate understanding of the present invention, and the present invention is not limited to an embodiment including all of the components described herein. Furthermore, part of the components of one exemplary embodiment can be replaced with the components of another exemplary embodiment. Furthermore, the components of another exemplary embodiment can be added to the components of one exemplary embodiment. Furthermore, part of the components of each exemplary embodiment can be added, deleted, or replaced with other components. Furthermore, some or all of the above-described components, functions, processing units, processing means, etc. may be implemented in hardware, for example, by designing them as integrated circuits. Furthermore, the control lines and information lines in the figures are only those considered necessary for explanation, and not necessarily all of them are shown. It can be assumed that almost all components are interconnected.

[0109] Furthermore, the functional configurations of the above-described task management device 10, client terminal device 20, client system management device 30, and person in charge terminal device 40 are categorized according to the main processing content for ease of understanding. The classification method and names of the components do not limit the present invention. As described above, the configurations of the task management device 10, client terminal device 20, client system management device 30, and person in charge terminal device 40 can be categorized into more components according to the processing content. Furthermore, a single component can be categorized to perform even more processing. [Explanation of symbols]

[0110] 1: Task management system, 10: Task management device, 11: Arithmetic unit, 12: Memory, 13: External storage device, 14: Input IF, 15: Output IF, 16: Communication IF, 20: Client terminal device, 30: Client system management device, 40: Person in charge terminal device, 110, 210, 310, 410: Processing unit, 111: Trigger information acquisition unit, 112: Task determination unit, 113: Task step extraction unit, 114, 212: Mail control unit, 115: Person in charge determination unit, 116: Task management unit, 117 : Task step execution unit, 120, 220, 320, 420: Memory unit, 121: Task information, 122: Member information, 123: Task step information, 124: Client information, 130, 230, 330, 430: Input unit, 140, 240, 340, 440: Output unit, 150, 250, 350, 450: Communication unit, 211, 311: Trigger information output unit, 411: Message creation unit, 461: Step definition information display screen, 462: Client definition information display screen, N: Network

Claims

1. a trigger information acquisition unit that acquires trigger information indicating a request from a client; a task determination unit that determines a task related to a business to be provided to the client based on the trigger information; a task step extraction unit that extracts one or more task steps from the task determined by the task determination unit; an email control unit that controls execution of an email creation task step that is the task step that accepts creation of a message to the client by a person in charge; The email control unit determining a destination based on the task and sending the message to the destination; A task management device characterized in that, when the email creation task step is executed, the person in charge is prevented from changing the destination.

2. 2. The task management device according to claim 1, a task management unit that detects the completion of each task step and manages the progress of the task; The task management device is characterized in that the email control unit accepts creation of the message when the task management unit determines that a start condition for the email creation task step is satisfied.

3. 3. The task management device according to claim 2, A task management device characterized in that, when the task management unit detects the completion of another task step that is defined as a start condition for the email creation task step, it notifies a person in charge of the email creation task step.

4. 3. The task management device according to claim 1, A task management device characterized by having a person in charge determination unit that refers to member information that associates candidate persons with the skills they possess, and determines a person in charge for each task step based on the skills required by the task step.

5. 4. The task management device according to claim 2, a person in charge determination unit that refers to member information in which person in charge candidates are associated with the skills they possess, and determines a person in charge for each task step based on the skills required for the task step; a task step execution unit that executes a predetermined task step that does not require the operation of a person in charge; The task management device is characterized in that the person in charge determination unit suppresses the determination of the person in charge of the predetermined task step.

6. 3. The task management device according to claim 1, The task management device is characterized in that, when the mail control unit receives a specification of data to be attached to the message, it determines whether or not a character string indicating the client is included in the name of the data.

7. 3. The task management device according to claim 1, The task management device is characterized in that, when it is determined that the creation of the message is completed, the mail control unit determines whether a character string indicating the client is included in the title of the message.

8. A program for causing a processing unit of a computer to execute a task management method, a trigger information acquisition step for acquiring trigger information indicating a client request; a task determination procedure for determining a task related to a business to be provided to the client based on the trigger information; a task step extraction step of extracting one or more task steps from the task determined in the task determination step; an email control procedure for controlling execution of an email creation task step, which is the task step for accepting creation of a message to the client by a person in charge; The program is characterized in that, in the email control procedure, a destination is determined based on the task, the message is sent to the destination, and when the email creation task step is executed, the program inhibits the person in charge from changing the destination.

9. A task management method by a task management device, a trigger information acquisition step for acquiring trigger information indicating a client request; a task determination procedure for determining tasks constituting a business to be provided to the client based on the trigger information; a task step extraction step of extracting one or more task steps from the task determined in the task determination step; an email control procedure for controlling execution of an email creation task step, which is the task step for accepting creation of a message to be sent to the client by a person in charge; A task management method characterized in that the email control procedure determines a destination based on the task, sends the message to the destination, and when executing the email creation task step, prevents the person in charge from changing the destination.

10. A task management system including a person in charge terminal device and a task management device, The person in charge terminal device a message creation unit that accepts an input operation regarding a message to a client; The task management device a trigger information acquisition unit that acquires trigger information indicating a request from the client; a task determination unit that determines a task related to a business to be provided to the client based on the trigger information; a task step extraction unit that extracts one or more task steps from the task determined by the task determination unit; an email control unit that controls execution of an email creation task step, which is the task step that accepts creation of a message to the client, based on an input operation to the person in charge terminal device; A task management system characterized in that the email control unit determines a destination based on the task, sends the message to the destination, and suppresses changes to the destination by the person in charge when executing the email creation task step.

Images