Information processing device and program

Abstract

To allow for reducing the hassle of operations that should be done by a user when a message communicated among multiple users via communication means mentions that a certain process should be performed on a certain target, compared with a case where a user performs the process on the target on top of message communication via the communication means.SOLUTION: An information processing device provided herein comprises a processor configured to provide control to acquire a message communicated among multiple users via communication means, perform a process mentioned in the message on a target mentioned in the message, and display the fact that the process has been performed on the target.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] Patent document 1 describes a system and method for document processing in which a user sends a message and attached documents to a computer-based system with natural language instructions in the subject or body of the message, or as a script, and after user authentication, the subject and body of the message are interpreted to identify a document processing activity to be performed, and using the identified document processing activity, the attached or referenced documents are processed in accordance with instructions by a document processing server.

[0003] Patent document 2 describes a method and system for accessing print and scan functions of a multifunction printer, which includes receiving a text or voice message expressed in natural language from a mobile device of a user of the multifunction printer and received by one or more servers, extracting text data or audio data of the received text or voice message, transferring the extracted text data or audio data of the received text or voice message to one or more servers, receiving from the one or more servers one or more entities or intents related to the text or voice message based on processing of the text data or audio data by the one or more servers, processing the entities or intents to determine one or more functions related to the text or voice message from the mobile device of the user of the multifunction printer, and controlling the functions of the multifunction printer by executing the determined one or more functions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] US Patent Publication No. 2015 / 0256493 [Patent Document 2] U.S. Patent No. 10686951 Summary of the Invention [Problem to be solved by the invention]

[0005] In a message communicated between multiple users via a communication means, there may be a reference to executing a certain process on a certain target. In this case, in order to execute the process on the target, the user needs to execute the process on the target separately from communicating the message via the communication means.

[0006] The object of the present invention is to reduce the amount of operations that a user must perform when a message communicated between multiple users via a communication means mentions performing a certain process on a certain target, compared to when the user performs the process on the target separately from communicating the message via the communication means. [Means for solving the problem]

[0007] Claim 1 The invention described in a processor, the processor acquiring a message communicated between a plurality of users by a communication means, executing a process mentioned in the message on an object mentioned in the message, and displaying a message indicating that the process has been performed on the object, the processor, when there are a plurality of process candidates as candidates for the process on one object, displays the plurality of process candidates selectable for the one object, The processor prompts a specific user of the plurality of users to specify at least one piece of information of a target and a process when the message input by the specific user does not mention the at least one piece of information. Characterized by It is an information processing device. Claim 2 The invention described in a processor, the processor acquiring a message communicated between a plurality of users by a communication means, executing a process mentioned in the message on an object mentioned in the message, and displaying a message indicating that the process has been performed on the object, the processor, when there are a plurality of process candidates as candidates for the process on one object, displays the plurality of process candidates selectable for the one object, When the process mentioned in the message has not been executed for the target mentioned in the message, the processor re-executes the process for the target upon receiving an instruction from a user. Characterized by It is an information processing device. Claim 3The invention described in is characterized in that, when a process mentioned in a message input by a specific user of the multiple users is not executed for a target mentioned in the message, the processor permits the specific user to instruct the specific user to re-execute the process for the target. Claim 2 The present invention relates to an information processing device. Claim 4 The invention described in is an information processing device comprising a processor, which acquires messages communicated between a plurality of users via a communication means, controls to execute a process mentioned in the message on an object mentioned in the message, and displays a message indicating that the process has been performed on the object, and when the processor receives an instruction from a user, if the process mentioned in the message has not been executed on the object mentioned in the message, the processor re-executes the process on the object, and when the processor receives an instruction from a user, if the process mentioned in the message has not been executed on the object mentioned in the message input by a specific user of the plurality of users, the processor prohibits users other than the specific user from instructing the re-execution of the process on the object. Claim 5 The invention described in is an information processing device comprising a processor, which receives messages communicated between a plurality of users via a communication means, executes a process mentioned in the message on an object mentioned in the message, and displays a message indicating that the process has been performed on the object, and the processor controls a history of the executed processes to be displayed on the same screen as the screen displaying the message, and the processor accepts a designation of a specific process from a user on the history, and cancels any processes executed at the user's instruction after the specific process. The invention described in claim 6 is a program for causing a computer to realize a function of acquiring messages communicated between multiple users via a communication means, a function of executing a process mentioned in the message for an object mentioned in the message, and a function of controlling to display the fact that the process has been performed on the object, and for causing the computer to realize a function of displaying a selectable list of process candidates for a single object when there are multiple process candidates for the process for the single object, and a function of prompting a specific user among the multiple users to specify at least one piece of information about the object and the process when the message entered by the specific user does not mention the at least one piece of information about the object and the process. The invention described in claim 7 is a program for causing a computer to realize a function of acquiring messages communicated between multiple users via a communication means, a function of executing a process mentioned in the message on an object mentioned in the message, and a function of controlling to display the fact that the process has been performed on the object, and for causing the computer to realize a function of displaying a selectable list of process candidates for a single object when there are multiple process candidates for the process on the single object, and for causing the computer to realize a function of re-executing the process on the object mentioned in the message when instructions are received from a user if the process mentioned in the message has not been performed on the object mentioned in the message. Effect of the Invention

[0008] Claim 1According to the invention, if at least one piece of information regarding the object and the process is not mentioned in the message entered by the user, the user can be notified of this fact. Claim 2 According to the invention, when a process has not been executed on a target, it is possible to make the process re-executable on the target. Claim 3 According to the invention, when a user mentions executing a process on an object but the process is not executed, the user can instruct the object to re-execute the process. Claim 4 According to the invention, when a user mentions executing a process on a target but the process is not executed, it is possible to prevent users other than the user from instructing the target to re-execute the process. Claim 5 According to the invention, by specifying a process while checking the process history, the user can cancel processes executed after that process. According to the invention of claim 6, when at least one piece of information on the object and the process is not mentioned in the message input by the user, the user can be notified of this fact. According to the invention of claim 7, when a process has not been executed on an object, it is possible to make the process re-executable on the object. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram showing an example of the overall configuration of a computer system to which an embodiment of the present invention is applied; [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a server according to an embodiment of the present invention. [Diagram 3] FIG. 2 shows an example of a screen displayed on a client in a first scenario in an embodiment of the present invention. [Figure 4] FIG. 2 shows an example of a screen displayed on a client in a first scenario in an embodiment of the present invention. [Diagram 5] FIG. 2 shows an example of a screen displayed on a client in a first scenario in an embodiment of the present invention. [Figure 6] FIG. 13 shows an example of a screen displayed on a client in a second scenario in the embodiment of the present invention. [Figure 7] FIG. 13 shows an example of a screen displayed on a client in a second scenario in the embodiment of the present invention. [Figure 8] FIG. 13 shows an example of a screen displayed on a client in a second scenario in the embodiment of the present invention. [Figure 9] FIG. 13 shows an example of a screen displayed on a client in a second scenario in the embodiment of the present invention. [Figure 10] FIG. 13 shows an example of a screen displayed on a client in a third scenario in the embodiment of the present invention. [Figure 11] FIG. 13 shows an example of a screen displayed on a client in a third scenario in the embodiment of the present invention. [Figure 12] FIG. 2 is a block diagram showing an example of a functional configuration of a server according to an embodiment of the present invention. [Figure 13] 10 is a flowchart showing an example of the operation of a server according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0011] [Overall configuration of computer system] 1 is a diagram showing an example of the overall configuration of a computer system 1 to which the present embodiment is applied. As shown in the figure, this computer system 1 is configured by connecting clients 10a to 10c and a server 30 via a communication line 80. Although the clients 10a to 10c are shown in the figure, they may be referred to as clients 10 when there is no need to distinguish between them. Also, although only three clients 10 are shown in the figure, four or more clients 10 may be provided.

[0012] The client 10 is a computer used by a user who uses the computer system 1. An application for utilizing the services provided by the computer system 1 is installed on the client 10, and is configured to operate, for example, by a start-up operation by the user. For example, a personal computer, a tablet terminal, a smartphone, etc. may be used as the client 10.

[0013] The server 30 is a computer that provides a service to a user through the client 10 in response to a request sent from the client 10 by a user operation. For example, a general-purpose personal computer may be used as the server 30. In this embodiment, the server 30 is provided as an example of an information processing device.

[0014] The communication line 80 is a line used for information communication between the client 10 and the server 30. As the communication line 80, for example, the Internet may be used.

[0015] [Server hardware configuration] FIG. 2 is a diagram showing an example of a hardware configuration of the server 30 in this embodiment. As shown in the figure, the server 30 includes a processor 31, a main memory 32, and a hard disk drive (HDD) 33. Here, the processor 31 executes various software such as an operating system (OS) and applications to realize various functions described later. The main memory 32 is a storage area for storing various software and data used for executing the software, and the HDD 33 is a storage area for storing input data for the various software and output data from the various software. Furthermore, the server 30 includes a communication I / F (hereinafter, referred to as "I / F") 34 for communicating with the outside, a display device 35 such as a display, and an input device 36 such as a keyboard and a mouse.

[0016] 2 can also be regarded as the hardware configuration of the client 10. However, when describing the client 10, the processor 31, main memory 32, HDD 33, communication I / F 34, display device 35, and input device 36 in FIG. 2 will be expressed as the processor 11, main memory 12, HDD 13, communication I / F 14, display device 15, and input device 16, respectively.

[0017] [Outline of this embodiment] In this embodiment, the server 30 acquires messages communicated between multiple users via communication means, executes the processing mentioned in the message on the object mentioned in the message, and displays a message indicating that the processing has been performed on the object.

[0018] Here, the communication means may be any means for communicating messages between multiple users. Also, the message may be any message communicated between multiple users. Communication means include chat, e-mail, telephone, etc., and messages can be communicated by these communication means, but the following will take chat as an example of the communication means and a chat message as an example of the message. However, in the following, a "chat message" will also be simply referred to as a "message."

[0019] The target may be anything as long as it is an object to be processed. The target may be document data, image data, etc., but the following description will be given taking document data (hereinafter simply referred to as "document") as an example.

[0020] The process may be any process that is performed on an object, such as stamping a document (also called a "signing process") or sending a document to a destination.

[0021] Mentioning refers to talking about something in a message, whether it is explicit or implicit. In other words, mentioning includes not only explicitly specifying something in a message, but also stating it vaguely in a message. Mentioning it vaguely in a message means not specifying it explicitly in a message, but stating it in a way that is clear from the context of the message. When requesting approval for "Application No. 123", explicitly specifying it in a message means, for example, stating "Please approve Application No. 123", and stating it vaguely in a message means, for example, stating "Please approve the application I made the other day". Mentioning also includes not only asking other users to do some kind of process, but also informing other users that you will be performing some kind of process yourself. An example of the latter would be something like "I'll make a copy of the photo and give it to everyone."

[0022] In addition, in this embodiment, when there are multiple candidate processes, the server 30 executes one candidate process selected from the multiple candidate processes on the target. Here, the multiple candidate processes may be different processes themselves. In this case, the multiple candidate processes are, for example, a process of pressing a specified stamp on a document, a process of sending a document to a specified destination, and the like. Also, the multiple candidate processes may be processes in which each candidate process performs a process using data corresponding to each candidate process among the multiple data. That is, the multiple candidate processes may be processes in which the process itself is the same but the data used in the process is different. In this case, the multiple candidate processes are, for example, multiple processes using different stamps in a process of pressing a stamp on a document. Or, the multiple candidate processes may be, for example, multiple processes using different destinations in a process of sending a document to a destination. The stamp and destination are examples of data used in the process.

[0023] Furthermore, in this embodiment, when there are multiple target candidates, the server 30 executes processing on one target candidate selected from the multiple target candidates. Here, the multiple target candidates may be multiple documents when the target is a document. Alternatively, the multiple target candidates may be multiple pages of one document or multiple locations of one document when the target is a document. However, the following description will be given taking multiple documents as an example.

[0024] [Specific example of this embodiment] 3 to 11 are diagrams showing examples of a screen 100 displayed on a client 10 in this embodiment. As shown in these diagrams, the screen 100 includes a chat display field 500, a processing history display field 600, and a processed image display field 700.

[0025] The chat display section 500 is a section for displaying chat messages and the like exchanged between a plurality of users or between the server 30 and a user.

[0026] The processing history display field 600 is a field that displays the processing history, which is the history of processing performed by the server 30. If the processing performed by the server 30 is processing instructed by the user using the client 10, the processing history is displayed in the processing history display field 600 with "you" as the subject. Also, if the processing performed by the server 30 is processing instructed by a user other than the user using the client 10, the processing history is displayed in the processing history display field 600 with the name of the other user as the subject.

[0027] The processed image display field 700 is a field for displaying a processed image, which is an image that represents processing performed by the server 30. In the processed image display field 700, an icon representing a document is displayed, and an icon representing the processing content for the document is displayed in association with the icon.

[0028] First, a description will be given of the screen 100 displayed in the first scenario. The first scenario is a scenario assuming a scene in which Alice stamps a document and asks Bob to stamp the document again.

[0029] FIG. 3 shows an example of a screen 100 displayed on Bob's client 10 when Alice stamps "Doc1" and requests Bob to stamp "Doc1". At this time, a message 511 from Alice, "Bob, I'm signing Doc1 now. Can you sign it too?" is displayed in the chat display field 500. Also, a processing history 611, "Alice signed Doc1", is displayed in the processing history display field 600. Here, the processing history 611 is displayed grayed out because it is not the history of the processing instructed by Bob. Furthermore, the processed image display field 700 shows that Alice's stamp has been stamped on "Doc1" by displaying an icon 713 of Alice's stamp superimposed on an icon 711 of "Doc1".

[0030] 4 shows an example of a screen 100 displayed on Bob's client 10 when Bob stamps "Doc1" in response to Alice's request. At this time, a message 512 from Bob saying "OK. I'm signing now" is displayed in the chat display field 500. However, in this example, it is assumed that Bob has multiple stamps. Therefore, the chat display field 500 further displays a message 513 from the server 30 saying "Please select a stamp" and a stamp selection list 514 consisting of "STAMP 1" to "STAMP 5".

[0031] FIG. 5 shows an example of the screen 100 displayed on Bob's client 10 when Bob selects "Stamp 1" and presses it on "Doc1". At this time, the chat display field 500 displays a message 515 from the server 30 saying "You signed with Stamp 1". In addition, the processing history display field 600 displays a processing history 612 saying "You signed on Doc1" and an "Undo" button 613 for canceling the processing shown in the processing history 612. This allows Bob to cancel the processing he instructed in the message 512 by clicking the "Undo" button 613. On the other hand, the processing history display field 600 of Alice's client 10 does not display the "Undo" button, so Alice cannot cancel the processing instructed by Bob. In addition, the processed image display field 700 shows that "Stamp 1" has been further pressed on "Doc1" by further displaying Bob's "Stamp 1" icon 714 superimposed on the "Doc1" icon 711.

[0032] Next, a description will be given of the screen 100 displayed in the second scenario. The second scenario is a scenario assuming a situation in which Alice requests Bob to stamp a document, but the content of the request is unclear.

[0033] 6 shows an example of a screen 100 displayed on Alice's client 10 when Alice requests Bob to stamp a document. At this time, a message 521 from Alice, "Bob, can you sign the document?", is displayed in the chat display field 500. However, no document is specified in this message 521. Therefore, a message 522 from the server 30, "Please specify the document," is displayed in the chat display field 500. In response to this message 522, Alice enters a message 523, "Doc2."

[0034] 7 shows an example of the screen 100 displayed on Alice's client 10 when Alice inputs "Doc2". At this time, a message 524 from Alice, "Bob, can you sign Doc2 for me?", is displayed in the chat display field 500. This message 524 is an edited version of the message 521, which was generated by Alice inputting the message 522, "Doc2", in FIG. 6.

[0035] 8 shows an example of a screen 100 displayed on Bob's client 10 when Bob stamps "Doc2" in response to Alice's request. At this time, a message 525 from Bob saying "OK. I'm signing now" is displayed in the chat display field 500. However, even in this example, it is assumed that Bob has multiple stamps. Therefore, a message 526 from the server 30 saying "Please select a stamp" and a stamp selection list 527 consisting of "STAMP 1" to "STAMP 5" are also displayed in the chat display field 500.

[0036] FIG. 9 shows an example of the screen 100 displayed on Bob's client 10 when Bob selects "Stamp 5" and presses it on "Doc2". At this time, the chat display field 500 displays a message 528 from the server 30 saying "You signed with Stamp 5". In addition, the processing history display field 600 displays a processing history 621 saying "You signed on Doc2" and an "Undo" button 622 for canceling the processing shown in the processing history 621. This allows Bob to cancel the processing he instructed in the message 525 by clicking the "Undo" button 622. On the other hand, the "Undo" button is not displayed in the processing history display field 600 of Alice's client 10 screen 100, so Alice cannot cancel the processing instructed by Bob. In addition, the processed image display field 700 shows that "Stamp 5" has been pressed on "Doc2" by displaying Bob's "Stamp 5" icon 723 superimposed on the "Doc2" icon 722.

[0037] Next, a description will be given of the screen 100 displayed in the third scenario. The third scenario is a scenario assuming a situation in which Bob attempts to stamp a document in response to Alice's request in Fig. 7, but an error occurs.

[0038] FIG. 10 shows an example of a screen 100 displayed on Bob's client 10 when Bob stamps "Doc2" in response to Alice's request in FIG. 7. At this time, a message 531 of Bob's "OK. I'm signing now" is displayed in the chat display field 500. However, in this example, it is assumed that Bob has one stamp. Also, in this example, it is assumed that an error occurs during the process of the server 30 stamping Bob's stamp on "Doc2". Then, a message 532 of the server 30 "Oops, something went wrong. Please try again" is displayed in the chat display field 500. Also, in the process history display field 600, a process history 631 of "You signed Doc2" and a "Retry" button 632 for retrying the process indicated by the process history 631 are displayed. This allows Bob to retry the process he instructed in the message 531 by clicking the "Retry" button 632. On the other hand, since the "Retry" button is not displayed in the processing history display section 600 on the screen 100 of Alice's client 10, Alice cannot retry the processing instructed by Bob.

[0039] FIG. 11 shows an example of the screen 100 displayed on Bob's client 10 when Bob clicks the "Retry" button 632 in FIG. 10. At this time, in the chat display field 500, a message 533 of the server 30 saying "You have signed Doc2" is displayed instead of the message 532 in FIG. 10. Also, in the processing history display field 600, an "Undo" button 633 for canceling the processing shown in the processing history 631 is displayed instead of the "Retry" button 632 in FIG. 10. This allows Bob to cancel the processing he instructed in the message 531 by clicking the "Undo" button 633. On the other hand, since the "Undo" button is not displayed in the processing history display field 600 of the screen 100 of Alice's client 10, Alice cannot cancel the processing instructed by Bob. Furthermore, in the processed image display field 700, it is shown that Bob's stamp has been pressed on "Doc2" by displaying the icon 733 of Bob's stamp superimposed on the icon 732 of "Doc2".

[0040] [Server Functionality Configuration] 12 is a block diagram showing an example of the functional configuration of the server 30 in this embodiment. As shown in the figure, the server 30 includes a receiving unit 41, a message analyzing unit 42, a document storage unit 43, a processing information storage unit 44, a document processing unit 45, a processing history storage unit 46, and a transmitting unit 47.

[0041] The receiving unit 41 receives a chat message from the client 10 that sent the message (hereinafter simply referred to as the "sender client 10") and passes it to the message analyzing unit 42. Here, the message includes a message sent as retry information by clicking the "Retry" button on the client 10. In this embodiment, this process is performed by the receiving unit 41 as an example of acquiring messages communicated between a plurality of users by communication means.

[0042] The receiving unit 41 also receives a message indicating the application data selected by the user from among a plurality of application data used in the process mentioned in the message from the client 10 that is the sender, and passes the message to the document processing unit 45.

[0043] Furthermore, the receiving unit 41 receives cancellation information indicating that the "Undo" button has been clicked on the client 10 from that client 10. Here, the cancellation information includes process identification information for identifying the process corresponding to the "Undo" button. In this embodiment, this process is performed by the receiving unit 41 as an example of accepting a designation of a specific process from the user on the history.

[0044] The message analysis unit 42 receives a message from the receiving unit 41, analyzes the message, and determines whether the message refers to a document and a process. If the message analysis unit 42 determines that the message refers to a document and a process, it conveys the document and the process to the document processing unit 45 and instructs the sending unit 47 to send the message as is. If the message analysis unit 42 determines that the message does not refer to at least one of the document and the process, it instructs the sending unit 47 to send a message encouraging the user to complete the document or the process that is not mentioned.

[0045] In addition, in response to an inquiry from the document processing unit 45, the message analysis unit 42 determines whether the message is a request for processing to the server 30 or a request for processing to the destination user, and returns the determination result to the document processing unit 45.

[0046] The document storage unit 43 stores the document to be processed. Here, the document is stored in association with document identification information that identifies the document. The document identification information includes, for example, the document name, information on the storage location of the document, etc. This makes it possible to obtain a document based on the document identification information when the document is referred to in a message by the document identification information.

[0047] The processing information storage unit 44 stores processing information, which is information about processing performed on a document. Here, the processing information includes data used when performing processing (hereinafter, referred to as "use data"). The processing information storage unit 44 may store use data for each process for each user. For example, for a process of stamping a document, the processing information storage unit 44 stores the type of stamp as use data. In this case, the type of stamp varies depending on the user, so the processing information storage unit 44 stores the type of stamp for each user. There may be only one type of stamp or there may be two or more types. In addition, for example, for a process of requesting a destination user to send a document, the processing information storage unit 44 stores destination information when sending the document as use data. In this case, the destination information varies depending on the user, so the processing information storage unit 44 stores destination information for each user. There may be only one type of destination information or there may be two or more types of destination information. Furthermore, for a process that does not require use data, the processing information storage unit 44 stores processing information without including use data.

[0048] The document processing unit 45 determines the number of application data usable in the process conveyed from the message analyzing unit 42 by referring to the process information storage unit 44 .

[0049] If the document processing unit 45 determines that the number of application data available for processing is 0, it inquires of the message analyzing unit 42 as to whether the message is a request for processing to the server 30 or not.

[0050] If the document processing unit 45 determines that the number of application data available for processing is 1, it acquires the application data from the processing information storage unit 44. Then, the document processing unit 45 inquires of the message analysis unit 42 whether the message is a request for processing to the server 30.

[0051] If the document processing unit 45 determines that the number of application data available for processing is two or more, it instructs the transmitting unit 47 to transmit a message prompting the selection of one application data from the two or more application data. Thus, when the document processing unit 45 receives a message indicating the selected application data from the receiving unit 41, it acquires the selected application data from the processing information storage unit 44. Then, the document processing unit 45 inquires of the message analyzing unit 42 whether the message first received by the receiving unit 41 is a message requesting the server 30 to perform processing.

[0052] If the message is a request for processing to server 30, document processing unit 45 instructs sending unit 47 to send a processing history, and acquires the document transmitted from message analysis unit 42 from document storage unit 43. Then, document processing unit 45 executes the processing transmitted from message analysis unit 42 for the acquired document, using the utilization data, if any, that has been acquired. In this embodiment, this processing by document processing unit 45 is performed as an example of executing the processing mentioned in the message for the target mentioned in the message.

[0053] When the document processing unit 45 processes the document in this manner, it stores the processing history in the processing history storage unit 46 and instructs the transmission unit 47 to transmit the processing results.

[0054] In addition, when the receiving unit 41 receives a message as retry information for a process instructed by a user when the process instructed by the user is not executed, the document processing unit 45 performs the same process as described above. In this embodiment, this process of the document processing unit 45 is performed as an example of permitting a user to retry a process on a target mentioned in a message when the process instructed by the user is not executed on the target mentioned in the message. However, when the process instructed by the user is not executed, retry information for the process may be sent to the user, and retry information for the process may not be sent to users other than the user. In that sense, this process of the document processing unit 45 is an example of permitting a specific user to retry a process on a target mentioned in a message input by a specific user among multiple users when the process instructed by the message is not executed on the target mentioned in the message. In addition, this process of the document processing unit 45 is also an example of prohibiting users other than the specific user from retrying a process on a target mentioned in a message input by a specific user among multiple users when the process instructed by the message is not executed on the target mentioned in the message.

[0055] Furthermore, when the receiving unit 41 receives cancellation information including the process identification information, the document processing unit 45 identifies the process based on the process identification information from the process history stored in the process history storage unit 46 and cancels the process. At that time, if the same user has performed processes after the process, these processes may also be canceled. Alternatively, if the same user has performed processes on the same document after the process, these processes may also be canceled. In this embodiment, this process of the document processing unit 45 is performed as an example of canceling processes performed by user instructions after a specific process.

[0056] The processing history storage unit 46 stores a processing history, which is a history of processing executed by the document processing unit 45. Here, the processing history is stored in association with processing history identification information that identifies the processing history. The processing history identification information includes, for example, the time when the processing was instructed, and a serial number that is assigned each time a processing is instructed. The processing history is also stored in association with user identification information that identifies the user who instructed the processing. As a result, when the receiving unit 41 receives cancellation information accompanied by the processing history identification information and user identification information from the client 10, the processing history can be identified based on the processing history identification information and the user identification information, and the processing indicated in the processing history can be canceled.

[0057] When the message received by the receiving unit 41 is passed from the message analyzing unit 42 to the transmitting unit 47, the transmitting unit 47 transmits the message to the destination client 10. As a result, the message is displayed in the chat display field 500 on the screen 100 of the destination client 10.

[0058] Furthermore, when the sending unit 47 is instructed by the message analyzing unit 42 to send a message encouraging the receiving unit 41 to supplement a document or process not mentioned in the message received by the receiving unit 41, the sending unit 47 sends a message encouraging the receiving unit 41 to supplement the document or process to the sending client 10. As a result, the sending client 10 displays a message encouraging the receiving unit 41 to supplement the document or process in the chat display field 500 of the screen 100. In this embodiment, this process is performed by the sending unit 47 as an example of encouraging a specific user to specify at least one piece of information when at least one piece of information of a target and a process is not mentioned in a message input by a specific user of multiple users.

[0059] Furthermore, when the sending unit 47 is instructed by the document processing unit 45 to send a message prompting the selection of one of a plurality of application data usable for the process mentioned in the message received by the receiving unit 41, the sending unit 47 sends a message prompting the selection of the application data to the sending client 10. As a result, the sending client 10 displays the message prompting the selection of the application data in the chat display field 500 on the screen 100.

[0060] Furthermore, when the sending unit 47 is instructed by the document processing unit 45 to send the processing history, it sends the processing history to the source and destination clients 10. As a result, the source and destination clients 10 display the processing history in a processing history display field 600 on the screen 100. In this embodiment, this processing by the sending unit 47 is performed as an example of control to display the history of executed processing on the same screen as the screen displaying the message.

[0061] Furthermore, when the sending unit 47 is instructed by the document processing unit 45 to send the processing results, it sends the processing results to the source and destination clients 10. As a result, in the source client 10 and destination client 10, a message indicating the processing results is displayed in the chat display field 500 of the screen 100, and an image indicating the processing results is displayed in the processed image display field 700 of the screen 100. In this embodiment, this processing by the document processing unit 45 is performed as an example of control to display the fact that processing has been performed on the target.

[0062] [Server operation] FIG. 13 is a flowchart showing an example of the operation of the server 30 in this embodiment.

[0063] As shown in the figure, in the server 30, the receiving unit 41 first receives a message from the client 10 that is the sender of the message (step 401).

[0064] Next, the message analyzer 42 determines whether a document and a process are mentioned in the message received in step 401 (step 402).

[0065] As a result, if it is determined in step 402 that the message received in step 401 refers to a document and a process, the sending unit 47 sends the message to the destination client 10 (step 403).

[0066] Next, the document processing unit 45 refers to the processing information storage unit 44 to determine the number of application data available for the processing specified in step 402 (step 404).

[0067] If it is determined in step 404 that the number of available application data is 0, that is, that no application data is required, the process proceeds to step 409 .

[0068] If it is determined in step 404 that the number of available application data is one, the document processing unit 45 acquires the one application data from the processing information storage unit 44 (step 405).

[0069] If it is determined in step 404 that the number of available application data is two or more, the transmitting unit 47 transmits a message to the transmitting client 10 prompting the user to select application data from the two or more application data (step 406). As a result, when the transmitting user selects application data, the receiving unit 41 receives a message indicating the selected application data from the transmitting client 10 (step 407). Then, the document processing unit 45 acquires the selected application data from the processing information storage unit 44 (step 408). Then, the process proceeds to step 409.

[0070] Next, message analysis unit 42 judges whether the message received in step 401 is a request for the process specified in step 402 to itself (step 409).

[0071] If it is not determined in step 409 that the message is a request for processing by the user itself, that is, if it is determined that the message is a request for processing by the destination user, the process ends. Note that in this operation example, even if it is determined that the message is a request for processing by the destination user, the processes in steps 404 to 408 are performed. This is because, even if the message is a request for processing by the destination user, for example, if the process mentioned in the message is a process for sending a document to the destination, usage data such as destination information may be acquired.

[0072] If it is determined in step 409 that the message is a request for processing by the sending unit 47, the sending unit 47 sends the processing history to the client 10 which is the sender and the client 10 which is the destination (step 410).

[0073] Furthermore, the document processing unit 45 executes the process specified in step 402 for the document specified in step 402 (step 411). Here, the document processing unit 45 may acquire the document specified in step 402 from among the documents stored in the document storage unit 43. Furthermore, if the usage data has been acquired in step 405 or step 408, the document processing unit 45 may execute the process using this usage data.

[0074] Furthermore, document processing unit 45 stores a processing history, which is a history of the processing in step 411, in processing history storage unit 46 (step 412).

[0075] Furthermore, the transmitting unit 47 transmits the processing result, which is the result of the processing in step 411, to the sending client 10 and the destination client 10 (step 413). At this time, if the sending client 10 receives the processing result normally, an "Undo" button may be displayed in the processing history display field 600 in association with the processing history transmitted in step 410. On the other hand, if the sending client 10 does not receive the processing result normally and a timeout occurs, a "Retry" button may be displayed in association with the processing history transmitted in step 410.

[0076] After the above processing is performed, the processing ends.

[0077] On the other hand, if it is not determined in step 402 that the document and the process are mentioned in the message received in step 401, the sending unit 47 sends a message to the sending client 10 prompting the sending client 10 to complete the document or the process that is not mentioned (step 414).Then, the process ends.

[0078] Here, the operation example shown in FIG. 13 will be specifically described along the first scenario described above.

[0079] In the first scenario, when a message 511 is entered in the chat display field 500 in Alice's client 10 , the receiving unit 41 receives the message 511 from Alice's client 10 in step 401 .

[0080] Next, in step 402, message analysis unit 42 determines that a document and a process are mentioned in message 511. Here, it is determined that a document is mentioned because the document name "Doc1" is included in message 511. Also, it is determined that a process is mentioned because message 511 contains "signing," which indicates the process of pressing a stamp.

[0081] Then, in step 403, the sending unit 47 sends the message 511 to Bob's client 10. As a result, the message 511 is displayed in the chat display field 500 of Bob's client 10, as shown in FIG.

[0082] Next, in step 404, the document processing unit 45 refers to the processing information storage unit 44 to determine the number of use data available for the stamping process. Here, it is assumed that the number of Alice's stamps available for the stamping process is one.

[0083] Then, in step 405, the document processing unit 45 acquires the one stamp from the processing information storage unit 44.

[0084] Next, in step 409, the message analysis unit 42 determines that the message 511 is a request for processing to the server 30.

[0085] Then, in step 410, the transmission unit 47 transmits the processing history 611 to Alice's client 10 and Bob's client 10. As a result, the processing history 611 is displayed grayed out in the processing history display field 600 of Bob's client 10, as shown in FIG.

[0086] Furthermore, in step 411, the document processing unit 45 executes a process of pressing Alice's stamp on "Doc1". Furthermore, in step 412, the document processing unit 45 stores the processing history in the processing history storage unit 46. Furthermore, in step 413, the transmission unit 47 transmits a processing result indicating that the process of pressing Alice's stamp on "Doc1" has been executed to Alice's client 10 and Bob's client 10. As a result, an image in which icon 713 is superimposed on icon 711 is displayed in the processed image display field 700 of Bob's client 10, as shown in Fig. 3.

[0087] Next, as shown in FIG. 4, when a message 512 is entered in the chat display field 500 in Bob's client 10 , the receiving unit 41 receives the message 512 from Bob's client 10 in step 401 .

[0088] Next, in step 402, message analysis unit 42 determines that a document and a process are mentioned in message 511. Here, it is determined that a document is mentioned because it is possible to determine that the process target is "Doc1" from the context of message 511. It is also determined that a process is mentioned because message 512 contains "Signing," which indicates the process of pressing a stamp.

[0089] Then, in step 403 , the sending unit 47 sends a message 512 to Alice's client 10 .

[0090] Next, in step 404, the document processing unit 45 refers to the processing information storage unit 44 to determine the number of use data available for the stamping process. Here, it is assumed that the number of Bob's stamps available for the stamping process is five.

[0091] Then, in step 406, the document processing unit 45 transmits a message 513 to Bob's client 10, prompting the client to select one of the five stamps. As a result, the message 513 is displayed in the chat display field 500 of Bob's client 10, as shown in FIG. 4. When Bob selects one stamp, the receiving unit 41 receives a message indicating the selected stamp in step 407. Then, in step 408, the document processing unit 45 acquires the selected stamp from the processing information storage unit 44.

[0092] Next, in step 409, the message analysis unit 42 determines that the message 512 is a request for processing to the server 30.

[0093] Then, in step 410, the transmission unit 47 transmits the processing history 612 to Alice's client 10 and Bob's client 10. As a result, the processing history 612 is displayed in the processing history display field 600 of Bob's client 10, as shown in FIG.

[0094] Furthermore, in step 411, the document processing unit 45 executes a process of pressing Bob's stamp on "Doc1". Furthermore, in step 412, the document processing unit 45 stores the process history in the process history storage unit 46. Furthermore, in step 413, the transmission unit 47 transmits a process result indicating that the process of pressing Bob's stamp on "Doc1" has been executed to Alice's client 10 and Bob's client 10. As a result, as shown in FIG. 5, a message 515 is displayed in the chat display field 500 of Bob's client 10, and an image in which icons 713 and 714 are superimposed on an icon 711 is displayed in the processed image display field 700 of Bob's client 10. At that time, an "Undo" button 613 is also displayed in the process history display field 600 of Bob's client 10.

[0095] Next, the operation example shown in FIG. 13 will be specifically described along the above-mentioned second scenario.

[0096] In the second scenario, as shown in FIG. 6, when a message 521 is entered in the chat display field 500 in Alice's client 10, the receiving unit 41 receives the message 521 from Alice's client 10 in step 401.

[0097] Next, in step 402, message analysis unit 42 determines that message 521 does not mention a document but does mention a process. Here, it is determined that a document is not mentioned because the document name is not included in message 521 and cannot be determined from the context. Also, it is determined that a process is mentioned because message 521 contains "sign," which indicates the process of pressing a stamp.

[0098] Then, in step 414, the sending unit 47 sends a message 522 prompting the sender client 10 to complete the document name. As a result, the message 522 is displayed in the chat display field 500 of Alice's client 10, as shown in FIG.

[0099] Next, when a message 523 indicating "Doc2" is entered in the chat display field 500 in Alice's client 10 as shown in Fig. 6, the message 521 in Fig. 6 is edited. As a result, when a message 524 is entered in the chat display field 500 in Alice's client 10 as shown in Fig. 7, the receiving unit 41 receives the message 524 from Alice's client 10 in step 401.

[0100] Next, in step 402, message analysis unit 42 determines that a document and a process are mentioned in message 524. Here, it is determined that a document is mentioned because the document name "Doc2" is included in message 524. Also, it is determined that a process is mentioned because message 524 contains "sign" which represents the process of pressing a stamp.

[0101] Then, in step 403, the sending unit 47 sends the message 524 to Bob's client 10. As a result, the message 524 is displayed in the chat display field 500 of Bob's client 10, as shown in FIG.

[0102] Thereafter, in step 409, the message analysis unit 42 determines that the message 524 is not a request for processing to the server 30.

[0103] Next, as shown in Fig. 8, a message 525 is entered in the chat display field 500 of Bob's client 10. The subsequent operations are basically the same as those in the case where a message 512 is entered in the chat display field 500 of Bob's client 10 in Fig. 4, and therefore a description thereof will be omitted.

[0104] Next, the operation example shown in FIG. 13 will be specifically described along the above-mentioned third scenario.

[0105] In the third scenario, as shown in FIG. 10, when a message 531 is entered in the chat display field 500 in Bob's client 10 , the receiving unit 41 receives the message 531 from Bob's client 10 in step 401 .

[0106] Next, in step 402, message analysis unit 42 determines that a document and a process are mentioned in message 531. Here, it is determined that a document is mentioned because it is possible to determine that the process target is "Doc2" from the context of message 531. It is also determined that a process is mentioned because message 531 includes "Signing," which indicates the process of pressing a stamp.

[0107] Then, in step 403 , the sending unit 47 sends a message 531 to Alice's client 10 .

[0108] Next, in step 404, the document processing unit 45 refers to the processing information storage unit 44 to determine the number of use data available for the stamping process. Here, it is assumed that the number of Bob's stamps available for the stamping process is one.

[0109] Then, in step 405, the document processing unit 45 acquires the one stamp from the processing information storage unit 44.

[0110] Next, in step 409, the message analysis unit 42 determines that the message 531 is a message requesting the server 30 to perform processing.

[0111] Then, in step 410, the transmission unit 47 transmits the processing history 631 to Alice's client 10 and Bob's client 10. As a result, the processing history 631 is displayed in the processing history display field 600 of Bob's client 10, as shown in FIG.

[0112] Also, the document processing unit 45 executes a process of stamping Bob's stamp on "Doc2" in step 411. Now, let us assume that an error occurs during the process. Then, since Bob's client 10 does not receive a normal processing result, a message 532 indicating the occurrence of an error is displayed in the chat display field 500, and a "Retry" button 632 for retrying the process is displayed in the processing history display field 600.

[0113] Next, when the “Retry” button 632 in FIG. 10 is clicked, the receiving unit 41 receives the message 531 from Bob's client 10 in step 401 .

[0114] Next, message analyzer 42 determines in step 402 that message 531 refers to a document and a process.

[0115] Then, in step 403 , the sending unit 47 sends a message 531 to Alice's client 10 .

[0116] Next, in step 404, the document processing unit 45 refers to the processing information storage unit 44 to determine the number of use data available for the stamping process. Here, it is assumed that the number of Bob's stamps available for the stamping process is one.

[0117] Then, in step 405, the document processing unit 45 acquires the one stamp from the processing information storage unit 44.

[0118] Next, in step 409, the message analysis unit 42 determines that the message 531 is a message requesting the server 30 to perform processing.

[0119] Then, in step 410, the transmission unit 47 transmits the processing history 631 to Alice's client 10 and Bob's client 10. As a result, the processing history 631 is displayed in the processing history display field 600 of Bob's client 10, as shown in FIG.

[0120] Also, in step 411, the document processing unit 45 executes a process of pressing Bob's stamp on "Doc2". Here, it is assumed that no error occurs during the process. Then, in step 412, the document processing unit 45 stores the process history in the process history storage unit 46. Also, in step 413, the transmission unit 47 transmits a process result indicating that the process of pressing Bob's stamp on "Doc2" has been executed to the Alice client 10 and the Bob client 10. As a result, as shown in FIG. 11, a message 533 is displayed in the chat display field 500 of the Bob client 10, and an image in which an icon 733 is superimposed on an icon 732 is displayed in the processed image display field 700 of the Bob client 10. At that time, an "Undo" button 633 is also displayed in the process history display field 600 of the Bob client 10.

[0121] Next, an example of the operation when the "Undo" button of the server 30 in this embodiment is clicked will be described.

[0122] When the "Undo" button is clicked on the client 10 and cancellation information including process identification information for identifying the process to be cancelled is transmitted, the receiving unit 41 of the server 30 first receives this cancellation information. Then, the document processing unit 45 identifies the process identified by the process identification information included in the cancellation information from the process history stored in the process history storage unit 46, and cancels that process.

[0123] [Processor] In this embodiment, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0124] In addition, the operations of the processor in this embodiment may be performed not only by one processor, but also by multiple processors located at physically separate locations working together. The order of the operations of the processor is not limited to the order described in this embodiment, and may be changed.

[0125] [program] The processes performed by the server 30 in this embodiment are prepared as a program such as application software, for example.

[0126] In other words, the program that realizes this embodiment can be seen as a program that causes a computer to realize the functions of acquiring messages communicated between multiple users via a communication means, executing processing mentioned in the message on an object mentioned in the message, and controlling the computer to display a message indicating that processing has been performed on the object.

[0127] The program for realizing the present embodiment can be provided not only by communication means but also by being stored in a recording medium such as a CD-ROM. [Explanation of symbols]

[0128] 10 client, 30 server, 41 receiving section, 42 message analysis section, 43 document storage section, 44 processing information storage section, 45 document processing section, 46 processing history storage section, 47 transmitting section

Claims

1. A processor comprising: The processor, Acquire messages communicated between a plurality of users via a communication means; Execute the process mentioned in the message on the object mentioned in the message; Controlling the target to display a message indicating that the processing has been performed; When there are a plurality of candidate processes as candidates for the process for one target, the processor displays the plurality of candidate processes selectably for the one target; The information processing device is characterized in that the processor prompts a specific user among the multiple users to specify at least one piece of information regarding a target and a process when the message entered by the specific user does not mention the at least one piece of information regarding the target and a process.

2. A processor comprising: The processor, Acquire messages communicated between a plurality of users via a communication means; Execute the process mentioned in the message on the object mentioned in the message; Controlling the target to display a message indicating that the processing has been performed; When there are a plurality of candidate processes as candidates for the process for one target, the processor displays the plurality of candidate processes selectably for the one target; The information processing device is characterized in that, when the processor receives instructions from a user, if the processing mentioned in the message has not been performed for the object mentioned in the message, the processor re-executes the processing for the object.

3. The information processing device according to claim 2, characterized in that the processor allows a specific user among the multiple users to instruct a specific user to re-execute a process on an object mentioned in the message when the process is not executed on the object mentioned in the message.

4. A processor is provided. The processor, Acquire messages communicated between a plurality of users via a communication means; Execute the process mentioned in the message on the object mentioned in the message; Controlling the target to display a message indicating that the processing has been performed; When the process mentioned in the message has not been executed for the target mentioned in the message, the processor re-executes the process for the target upon receiving an instruction from a user; The information processing device is characterized in that, when a process mentioned in a message input by a specific user of the multiple users is not performed for an object mentioned in the message, the processor prohibits users other than the specific user from instructing the specific user to re-execute the process for the object.

5. A processor is provided. The processor, Acquire messages communicated between a plurality of users via a communication means; Execute the process mentioned in the message on the object mentioned in the message; Controlling the target to display a message indicating that the processing has been performed; the processor controls to display a history of the executed processes on the same screen as the screen displaying the message; The processor, Accepting a designation of a specific process from a user on the history; Canceling the process executed by the user's instruction after the specific process 23. An information processing apparatus comprising:

6. A computer comprising: A function of acquiring messages communicated between a plurality of users via a communication means; A function of executing a process mentioned in the message on an object mentioned in the message; A function of controlling the display of a message indicating that the processing has been performed on the target; Realize this, a function of displaying a plurality of candidate processes for a single target in a selectable manner when the plurality of candidate processes are present as candidates for the single target in the computer; A program for causing the computer to realize a function of prompting a specific user among the multiple users to specify at least one piece of information regarding a target and a process when the message entered by the specific user does not mention the at least one piece of information regarding the target and the process.

7. A computer comprising: A function of acquiring messages communicated between a plurality of users via a communication means; A function of executing a process mentioned in the message on an object mentioned in the message; A function of controlling the display of a message indicating that the processing has been performed on the target; Realize this, a function of displaying a plurality of candidate processes for a single target in a selectable manner when the plurality of candidate processes are present as candidates for the single target in the computer; A program for causing the computer to realize a function of re-executing the processing for the target mentioned in the message when the processing mentioned in the message has not been executed for the target mentioned in the message and instructions are received from a user.

Images