Information processing device, control method thereof, and program

Abstract

To solve the problem in which: conventionally, when transmitting a message to a thread that is a transmission destination on an information sharing service, it is difficult to specify a thread to which a user desires to transmit the message.SOLUTION: An information processing apparatus transmits messages to an information sharing service that manages messages on threads, and has: acquisition means that, when a user transmits a message as a reply of a thread, acquires information on threads in a transmission destination group of the message from the information sharing service; extraction means that extracts a thread in which the user participates from the information on the threads; and display means that displays the thread extracted by the extraction means as a transmission destination of the message.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present invention relates to an information processing device that presents information about candidate destinations to a user when the user is deciding on a destination of a message, a control method thereof, and a program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there are document management systems that scan paper documents to digitize them, and set metadata such as file names for the digitized documents and set destinations for saving the documents. It is also widely known that information sharing sites such as social networking sites, where users share messages and files, are used as storage locations for documents. It is also possible to imagine a system in which these document management systems are linked to information sharing sites. By using the API published by the information sharing service, this document management system can access information stored on the information sharing site, such as messages, files, message dates and times, and participating users. Patent Document 1 discloses a technology for linking an information sharing service and a document system, while Patent Document 2 describes a technology for acquiring information from a linked information sharing site and proposing a UI for setting the information as a destination. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-99017 [Patent Document 2] Japanese Patent Application Laid-Open No. 2014-203325 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 only provides a means for selecting the settings of the information sharing service itself that is to be the destination, and does not take into consideration the point of setting a specific message within the information sharing service as the destination. Furthermore, Patent Document 2 takes into consideration a means for specifying a specific message within the destination information sharing service as the destination. However, when specifying the destination message, only partial information of the message is displayed, making it difficult for the user to specify the message they want to send. Therefore, an object of the present invention is to provide a technology that makes it easy for users to set destinations by presenting a list of threads of messages that are highly relevant to the operating user and detailed information about each thread. [Means for solving the problem]

[0005] To solve the above problems, The present invention provides An information processing device that transmits a message to an information sharing service that manages messages in threads, On a screen for setting the message for the scanned document and transmitting it to the information sharing service, Thread messages against Send as a reply Mode set by user In case 、 From the information sharing service Thread information The acquisition method and 、 The aforementioned Based on the information in the thread thread a control means for controlling the display of a list of threads on the screen, and for allowing the user to specify a thread to which the scanned document and the message are to be sent from the displayed list of threads; The present invention is characterized by having the following. [Effects of the Invention]

[0006] According to the present invention, message threads that are highly relevant to the operating user are presented from a thread list on an information sharing service, and detailed information about each thread is also presented, making it easier for the user to set destinations. [Brief explanation of the drawings]

[0007] [Figure 1] System and network configuration for implementing the present invention [Figure 2] Information processing function hardware configuration diagram [Figure 3]Software and hardware configuration diagram of this system [Figure 4] Client application UI diagram [Figure 5] Business application UI diagram [Figure 6] Flowchart of the sending procedure from a client application to a business application [Figure 7] Client application UI diagram [Figure 8A] Client application UI diagram [Figure 8B] Client application UI diagram [Figure 9] Flowchart of a UI control method for presenting a destination [Figure 10] Diagram of history stored on the document processing server [Figure 11] Flowchart of a UI control method for presenting a destination DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0009] <Embodiment 1> [Overall system configuration] FIG. 1 shows an example of a system configuration and a network configuration for implementing the present invention. The network 101 is a network such as the Internet or an intranet. A scanned document processing server 111, which is an information processing device, performs predetermined processing on scanned document images and transmits the information, processing results, etc. to other servers, client terminals, etc. via the network 101. A business server 131 is a server that manages various business operations and, in this embodiment, provides an information sharing service. The client terminal 121 is a personal computer, laptop computer, tablet computer, smartphone, etc., and performs operations such as acquiring image data, transmitting data to the scanned document processing server, and receiving information from the business server. [Hardware configuration] FIG. 2 shows a modular configuration diagram of the information processing functions of the scanned document processing server 111, the client terminal 121, and the business server 131, which are information processing devices. The network interface 202 connects to a network such as a LAN and communicates with other computers and network devices. Communication can be via either wired or wireless means. The CPU 203 executes programs loaded from the ROM 204, RAM 205, secondary storage device 206, etc., and performs overall control of the server or client terminal. The ROM 204 stores pre-installed programs and data. The RAM 205 is a temporary memory area. The CPU 203 deploys and executes programs on the RAM 205 and also uses it as a work area. The secondary storage device 206 is a non-volatile storage device such as a hard disk drive or flash memory. The user interface 201 provides information to the user via a display, keyboard, mouse, buttons, touch panel, etc., and controls the input and output of signals such as information by the user. Computers that do not have this hardware can be connected and operated from other computers using remote desktops or remote shells. All components are interconnected via a common bus 207. [Software configuration] 3 is a diagram showing the software configuration of this system. The software installed on each piece of hardware is executed by the respective CPUs 203, and can communicate with each other via a network 101 (arrow).

[0010] (Scan document processing server) <Scan document processing application> The scanned document processing application 311 is installed on the scanned document processing server 111. In this embodiment, it is described as operating as a Web application server, but other application implementation forms are also possible. An API (Application Programming Interface) 312 is a programming interface provided by the scanned document processing application 311. A Web UI 313 is a user interface provided by the scanned document processing application 311.

[0011] <Data Store> The data store 321 saves and stores various data from the scan document processing application 311 or the back-end application 331 . In the scanned document storage unit 322, the file of the scanned document itself is saved as an image file such as a JPEG file or a document file such as a PDF (Portable Document Format). The scanned document job queue 323 holds a queue for managing jobs waiting for setting information input processing. The setting information management unit 324 stores and manages, for each job, the setting information set during scanning, the file name and destination of the scanned document image, account information required for collaboration with the business server, and setting items required when executing a request to the business server's API. The scanned document processing result storage unit 325 stores the OCR processing results and the form discrimination results.

[0012] <Backend application> The back-end application 331 is responsible for sequentially executing various types of background processing. The OCR processing unit 332 acquires an input image from the scanned document storage unit 322 and performs OCR on it. In the OCR process, the start coordinates, width, and height of an area recognized as a character string, and the recognized OCR result character string are extracted. The form processing unit 333 determines the type of form using information such as the input image, the area pattern of the OCR processing result, the OCR result character string, etc. The determination process may be performed using any method such as pattern recognition or machine learning. The external system communication unit 334 executes a process of transmitting the scanned document and the processing result thereof to the external business server 131 .

[0013] (Client terminal) <Client application> The client application 351 executes the web application of the scan document processing application 311. One way of providing the client application 351 is to display the Web UI 313 in a browser and execute the web application by sending and receiving necessary data to and from the API 312. Alternatively, the client application 351 may be an application for a computer or smartphone created to send and receive necessary data to and from the API 312.

[0014] (Business server) <Business applications> The business application 361 is an application for an information sharing service executed on the business server 131. For ease of explanation, the form and configuration are collectively referred to as the business application here. As with the scanned document processing server, it may be provided in a form and configuration that separates it into a backend, a data store, and a data processing application, each of which manages and processes data. The API 362 and the Web UI 363 are each provided by a business application 361 . The business data storage 364 stores data used by the business application 361 . The data processing unit 365 uses messages and document information stored in the business data storage to execute operation requests designated by the user. The external system communication unit 366 executes a response to the transmission process from the scanned document processing server. The following description assumes that the business application 361 is an information sharing service having functions of file and document management and messaging between users, but it may be any other business application. One or more business servers 131 that cooperate with the scanned document processing server 111 are required for the purpose of transmitting, processing, and storing the processing results of the scanned document processing server 111.

[0015] <UI displayed in the client application> FIG. 4 is a diagram illustrating a UI for executing settings for a scanned document and transmission from the scanned document processing server 111 to the business server 131 from the client application 351. The UI 401 is displayed on the client application 351, and the user sets the scanned document using the UI 401 and sends a message to the business server 131 with the scanned document attached to the set contents. A preview pane 411 displays a list of scanned jobs. The scanned jobs 421 and 431 are displayed in a preview pane 411 along with check boxes (described below), thumbnails of the scanned documents, the scan date and time, the file name, the destination, and so on. Any information about the scanned documents and the settings made when the documents were scanned is also displayed. The displayed jobs are the selected job 421 and the unselected job 431, respectively. Checkbox 422 is used to switch between the selected and unselected states of a job; when checked, the job is selected, and when unchecked, the job is unselected. To switch between the selected and unselected states of a job, the status is displayed by the background color of the selected job, and the status can be changed by selecting the image or area itself displayed in the job, but any other display or selection means can also be used. The setting information editing pane 441 displays a list of setting information linked to the selected job. As setting items linked to the selected job 421, it is possible to set the file name 451 of the scanned document, the subject 461 when notifying the business server of the message to be sent, and the message content 471 when notifying the business server of the message to be sent. Only the setting items necessary for the explanation are shown here, but any other setting items may be added. For each setting item, there are areas 452, 462, 472 that display the setting item name, and edit fields 453, 463, 473. The edit fields may display any editing method depending on the setting content, such as a text field, pull-down, calendar, or radio button. The client application 351 reflects the edited value here as the setting item value. The user can operate the [OK] button 481 and the [Cancel] button 482 to instruct the execution of saving and transmitting the setting values.

[0016] <Screens provided by business applications> FIG. 5 is a diagram for explaining message exchange between users performed in the information sharing service of the business server 131. In FIG. A screen 501 is a screen in which the Web UI 363 provided by the business application 361 is displayed on the client terminal. Group 511 is a group for exchanging messages, and users participating in each group can converse with each other. Messages 521, 531, 541, and 551 are displayed as a list, and it is possible to continue exchanging messages in a tree format, such as between messages 531 and 541. Conversations, such as messages 521, 531, and 551, are carried out in independent units called threads, and users can participate in conversations within a group, determine the purpose, and exchange messages. It is also possible to give a thread a title such as subject 522. It is also possible to not set a thread title, such as message 531. The information contained in a message includes a posting date and time 523, a posting user name 524, a posted message 525, and a message attachment 526.

[0017] (Message sending procedure) Next, the operation of sending a message to the information sharing service of the business server 131 with the content set in the client application 351 will be described with reference to the flowchart of FIG. It is assumed that the destination business server 131 and destination group are already set at the time of scanning, but the business server 131 and destination group may be displayed on the setting information editing pane 441 of the client application 351 and set. The following processing is realized by executing predetermined processing programs in the scanned document processing server 111, the client terminal 121, and the business server 131, respectively. First, the client application 351 is started and starts to cooperate with the scan document processing application. First, in S601, the scanned document processing application 311 obtains a queue of pending jobs from the scanned document job queue 323. The scanned document processing application 311 obtains image files from the scanned document storage unit 322 and setting information set at the time of scanning, such as the destination, scan date and time, and file name, from the setting information management unit 324. The scanned document processing application 311 provides these to the client application 351. Next, in step S602, the client application 351 displays each job in the preview pane 411 based on the received information. In S603, the client application 351 detects that the user has selected a specific job from the displayed jobs. If a specific job has been selected (Yes in S603), the process proceeds to S604; if not (No in S603), the process ends. In step S604, when the client application 351 detects the selection of a job, it reflects the setting information associated with the document job in the setting information editing pane 441, displays the setting item name for each setting item, and sets and displays a value in the edit field if the setting has already been set. (This completes the UI state shown in FIG. 4.)

[0018] In S605, the client application 351 detects a selection in the edit field of the setting item [o]. If a selection is detected (Yes in S605), the process proceeds to S606, and if not (No in S605), the process returns to S604 and waits. When S606 detects this, the edit field of the setting item [o] becomes editable, and the user can set any value in accordance with the input method and rules of the edit field. In S607, it is confirmed whether the user has completed the settings. If it is confirmed that the settings have been completed (Yes in S607), the process proceeds to S608, and if not (No in S607), the process returns to S605 and waits until the settings are completed. The following describes the operations to be performed after editing each setting item is complete. In S608, after editing of each setting is completed, if the client application 351 detects that the user has pressed the [Cancel] button 482 (Yes in S608), the set values ​​are discarded without being saved. Then, the process returns to S606 and starts over from the state after selecting setting item [o]. On the other hand, after editing of each setting is completed, if pressing of the [Cancel] button 482 is not detected (No in S608) and pressing of the [OK] button 481 by the user is detected (Yes in S609), proceed to S610 and save the settings. On the other hand, if pressing of the [OK] button 481 is not detected in S609 (No in S609), the process returns to S608 and waits for the completion of editing and for the [Cancel] button 482 to be pressed.

[0019] Hereinafter, for simplicity of explanation, saving and sending of settings will be started at the same time, but the [OK] button and the send button may be separated into different buttons, and the operation for each button may be detected before execution. In step S611, the client application 351 executes a request to the API 362 provided by the information sharing service, which is the business application 361, using the setting information associated with the job and the values ​​set in each setting item as parameters. In S612, the business application 361 determines whether the received request has been accepted normally. If the request has been accepted normally (Yes in S612), the process proceeds to S613, and if not (No in S612), the process returns to S605. In S613, the data processing unit 365 of the business application 361 notifies a message to a specific group of parameters received in the request in a new thread. For example, let's assume that user D sends a request to Group 1 with the parameters "PurchaseOrder_20201201" in the "Subject" field and "Hi, user A! I confirmed it." in the "Content" field. In this case, a message like message 551 is sent. If the request is successful, in S614 the business application 361 notifies the scanned document processing server 111. Furthermore, the API 312 of the scanned document processing server 111 notifies the client application 351, and a notification of the success or failure of the request is displayed to the user. The notification of the success or failure may be by any means, such as a dialog or toast notification on the client application 351, or an email to a pre-set email address. The above has described the procedure for the user to set up a scanned document and notify a message to the business application 361. Next, we will explain a UI that is a feature of the present invention, which provides detailed information (date and time, whether the user is a member of a group) to the user in advance when setting a destination, making it easy for the user to set the destination.

[0020] <UI for selecting and specifying reply destination> FIG. 7 is a diagram illustrating an operation for the user to switch from a UI for inputting a subject to a UI for specifying and setting a reply destination in the present invention. Among the jobs displayed in the job list, job 701 is selected. This is a setting item 711 for displaying and setting the subject of the thread to be sent. Checking the checkbox 712 switches to a mode in which a message can be replied to a specific thread. When the checkbox 712 is checked, the edit field 713 switches to a pull-down menu. When the checkbox 712 is checked, the client application 351 executes a request to obtain thread information to the API 362 provided by the business application 361, using the destination group as a parameter. The request is processed by the data processing unit 365 of the business application 361. The client application 351 obtains a list of all threads in the requested group. The obtained thread list is displayed on the pull-down menu 713.

[0021] Figure 8A is a diagram illustrating the presentation and operation of a UI that displays a list of threads obtained from a business application 361 in a pull-down menu and further presents threads that are highly relevant to the user in the present invention, as well as controls for obtaining detailed information about the threads. A job 801 is selected, and a pull-down menu 811 displays a list of threads acquired by the client application 351 described with reference to FIG. The pull-down 811 is composed of two areas: an area 821 and an area 831. The area 821 is an area that preferentially displays threads that include the most recent message received by the operating user. The area 831 is an area that displays a list of threads within the group. The number of threads displayed in area 821 and area 831 may be limited by any method of filtering the update date and time, the number of retrieved items, or other data provided by the API. It is also optional whether the items displayed in area 821 are also displayed in area 831 in duplicate. The information displayed in the pull-down menu 811 includes information 822 for identifying the thread and controls 823 linked to the thread. The thread subject will be used as an example of information for identifying the thread, but any information may be used, such as the first sentence of the message, the posting user, the date and time, or the file name of the attached message. When the client application 351 detects a user operation such as hovering or clicking on the control 823, it displays details about the thread associated with the control, such as the thread subject, message exchanges, date and time, etc. The display method is assumed to be something like a tooltip 841 (balloon display), but any method such as the dialog 851 (dialog display) in FIG. 8B may be used.

[0022] (Application example 1: Extract threads by destination group) <Processing to notify by specifying a thread> The operation of specifying a thread to be the destination and notifying a message will be described using the flowchart in Figure 9. As with the flowchart in Figure 6, it is assumed that the destination business server and destination group have already been set at the time of scanning. The business server and destination group may also be displayed on the setting information editing pane 441 of the client application 351 and set. If a destination thread is specified, the ID of the destination thread must be passed as a parameter to the business server 131 in step S611 in the flowchart of Fig. 6. Other than that, the operations up to job selection for the scanned document and editing of other settings can be explained using the same operations as in the flowchart of Fig. 6, and therefore will not be explained here. In S901, when the client application 351 detects the selection of an arbitrary job from the job list displayed in the user preview pane 411 of FIG. 4, it displays the setting information associated with the selected job in the setting information editing pane 441. In step S902, the client application 351 displays a check box 712 for switching to a mode for specifying a thread to be a destination on the edit item for the setting information of the message subject in the job (FIG. 7). If the user wishes to send a message to a specific thread, the user checks a check box 712 displayed in the "Subject" setting item. In S903, if the client application 351 detects that the check box 712 is checked (Yes in S903), the process proceeds to S904, where the display of the edit field is switched to a pull-down menu. If the check box is not checked (No in S903), the process ends, and the operation in the flowchart of FIG. 6 is performed.

[0023] In S905, the client application 351 sends a request to the API 362 provided by the business application 361 to acquire a list of threads, using the set destination group as a parameter. In S906, the business application 361 accepts the received request and processes it in the data processing unit 365. Based on the parameters of the destination group received in the request, a list of threads within the group is sent to the client application 351 via the document processing server 111. Note that if the request is not accepted correctly or the processing is not successful (No in S906), this processing ends. Although the timing for making the request is set by checking the check box 712, it may also be set by starting the client application 351 or displaying a job in the preview pane 411. Specifically, a request to obtain a list of threads for multiple jobs may be initiated when the client application 351 is started or when a job is displayed in the preview pane 411, or the request may be initiated when a job is selected. If the request is successfully processed, in S907 the client application 351 sorts the acquired thread list in order of update date and time. In the next step S908, if the number of threads to be displayed in the pull-down menu is to be filtered by date and time, only threads after the specified date and time for filtering are extracted. Note that an upper limit may be set for the set value in S907 and S908. In addition to the update date and time, the upper limit may be set by any method such as filtering the number of acquisitions or other data provided by the API. The subsequent series of processes (S910 to S912) are repeatedly executed for each of the acquired and extracted threads (S909b, e).

[0024] In step S910, a request is made to the API 362 provided by the business application 361 to acquire properties such as participating users in the thread, all messages in the thread, and the posting date and time of each message. The business application 361 accepts the received request and processes it in the data processing unit 365. Based on the thread information parameters received in the request, detailed information within the thread is sent to the client application 351 via the document processing server 111. In S911, it is determined whether the request was successful, and if the request failed (No in S911), the process returns to S910 and executes the request again. An upper limit is set to prevent the request from being repeated indefinitely. On the other hand, if the request was successful (Yes in S911), the process proceeds to S912. In S912, the client application 351 stores and holds the thread acquired in response to the request in association with the detailed information. The above series of processes is repeated for all the threads acquired and extracted. After exiting the loop, in the next step S913, the client application 351 extracts only the threads in which the operating user is participating from among the threads that have been successfully acquired. In S914, the client application 351 extracts the thread with the most recent update date and time. In S915, the client application 351 displays on the pull-down menu 821 the latest thread and control in which the operating user is participating with priority. In S916, all threads and controls, other than the above, regardless of whether they are extracted or not, are displayed on the pull-down menu of 831. In S917, the client application 351 determines whether an operation on the control has been detected. If an operation on the control has been detected (Yes in S917), the process proceeds to S918; if not (No in S917), the process ends.

[0025] In S918, for the thread associated with the control for which the operation was detected, a message to be displayed in a tooltip or dialog box is created using the detailed information of the thread that was held, and the message is displayed, and the process ends. As a result, messages with the most recent update date will be displayed first in the groups the user is participating in. Also, by checking the message displayed in the tooltip, users can understand what the thread is about based on the conversation content, date and time before setting the recipient, making it easier for users to identify the thread they want to send to.

[0026] (Application example 2: Extracting highly relevant items from sending history) Next, a method for displaying threads that are highly relevant to the user and presenting destinations using the history of messages sent via the document processing server 111 will be described. FIG. 10 is a diagram for explaining history data. The storage area 1001 is for storing a user operation log, and is located in the data store 321. Note that the log may be located in an external server different from the scanned document processing server 111. History table 1002 is a tabular summary of the history contents. The history table 1002 stores the serial number, history ID, user name, result, transmission date and time, file name as file information, number of pages, destination group name, thread ID as thread information, etc. Each history record is issued a unique history ID, which distinguishes them from each other. In addition to this, if the configuration involves switching between multiple business servers, information about the business server may be added as desired to the contents registered in the history.

[0027] <Process for determining the proposed thread from the history> A method for determining a thread to present to a user from the history will be described using the flowchart in Fig. 11. The operations after identifying a thread from the target history and obtaining detailed information are the same as those described from step S912 onwards in the flowchart in Fig. 9, so a description thereof will be omitted. This process is executed when the user checks the reply check box 712. In step S1101, the client application 351 acquires the transmission history from the history storage area 1001. In S1102, the client application 351 extracts only the history from the transmission history after the specified date and time. In step S1103, the client application 351 acquires a destination group from the setting information associated with the selected job, and extracts a history of destinations that matches this group. For each of the extracted histories, the subsequent series of processes (S1105 to S1108) are repeatedly executed between S1104b and S1104e. In S1105, for each of the extracted histories, the client application 351 acquires the thread ID of the history.

[0028] In S1106, the client application 351 executes a request to the API 362 provided by the business application 361 using the acquired group and the acquired thread ID, and acquires detailed information. The business application 361 accepts the received request and processes it in the data processing unit 365. Based on the thread information parameters received in the request, detailed information within the thread is sent to the client application 351 via the document processing server 111. In S1107, it is determined whether the request was successful. If the request fails (No in S1107), a re-request is executed. An upper limit is set so that the re-request is not repeated endlessly. If the request is successful, the client application 351 proceeds to S1108. In S1108, the acquired thread and detailed information are linked and stored. The above series of processes is repeated the same number of times as the number of all extracted histories. From this point on, messages that are most relevant to the user are extracted from the threads the user is participating in and the update dates and times, and displayed in a pull-down menu.The system then detects operations on the controls displayed in the pull-down menu and presents this memorized detailed information to the user. By performing the above operations, it becomes possible to present messages that are highly relevant to the user, targeting only jobs sent via the document processing server.

[0029] (Other Examples) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. [Explanation of symbols]

[0030] 111 Scanned Document Processing Server 121 client terminals 131 Business Server 311 Scan Document Processing Application

Claims

1. An information processing device that transmits a message to an information sharing service that manages messages in threads, an acquisition means for acquiring thread information from the information sharing service when a mode for sending the message as a reply to a thread is set by a user on a screen for setting the message for the scanned document and sending the message to the information sharing service; a control means for controlling the display of a list of threads on the screen based on the thread information, and for allowing the user to specify a thread to which the scanned document and the message are to be sent from the displayed list of threads; An information processing device comprising:

2. The method further comprises extracting means for extracting threads related to the user from the thread information acquired by the acquiring means, 2. The information processing apparatus according to claim 1, wherein the list of threads displayed by the control means is threads related to the user extracted by the extraction means.

3. The information processing device according to claim 1, characterized in that the acquisition means acquires, from the information sharing service, information on the thread regarding a conversation taking place within a group in which the user participates, when the mode is set by the user on the screen.

4. 3. The information processing apparatus according to claim 2, wherein the extraction means further extracts, from the acquired thread information, information on threads that are related to the user and whose update dates and times are after a specified date and time.

5. The control means displays messages of threads with newer update dates and times in the list of threads with priority.

2. The information processing apparatus according to claim 1, wherein:

6. The acquiring means acquires information on threads whose message transmission histories are from a specified date and time from the information sharing service.

2. The information processing apparatus according to claim 1, wherein:

7. An information processing device described in any one of claims 1 to 6, characterized in that the control means controls the display to present detailed information about threads in the list of displayed threads on which a specified operation has been performed by the user.

8. The information processing device described in Claim 7, characterized in that the specified operation is an operation on a control displayed in association with each thread in the list of threads.

9. 8. The information processing apparatus according to claim 7, wherein the detailed information is presented by a tool tip or a dialog.

10. The list of threads is displayed in a pull-down menu on the screen.

10. The information processing device according to claim 1, further comprising:

11. An information processing device described in any one of claims 1 to 10, characterized in that the screen is a screen for setting the message and sending it to the information sharing service for a scanned document linked to a job selected by the user from a list of jobs related to multiple scanned documents.

12. A method for controlling an information processing device that transmits a message to an information sharing service that manages messages in threads, comprising: an acquisition step of acquiring thread information from the information sharing service when a mode for sending the message as a reply to a thread is set by a user on a screen for setting the message for the scanned document and sending the message to the information sharing service; a control step of displaying a list of threads on the screen based on the thread information, and controlling the display of the list of threads so that the user can specify a thread to which the scanned document and the message are to be sent from the displayed list of threads; 1. A method for controlling an information processing device, comprising:

13. A program for causing a computer to function as each of the means of the information processing device according to any one of claims 1 to 11.

Images