Information processing apparatus, method for controlling the same, and program
Patent Information
- Application Number
- JP2021185483
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-11-15
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2041-11-15
AI Technical Summary
Existing technologies lack the ability to facilitate easy destination setting in information sharing services by presenting a thread list of messages highly relevant to the user and detailed information of each thread, making it difficult for users to specify the message to be sent.
An information processing apparatus that acquires group thread information from an information sharing service, extracts threads in which the user participates, and displays them as potential message destinations, along with detailed thread information.
Enables users to easily set the destination by presenting message threads highly related to their operations and providing detailed thread information, simplifying the transmission process.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an information processing apparatus, a control method thereof, and a program that present information regarding candidates for a transmission destination to a user when the user determines a message to be a transmission destination.
Background Art
[0002] Conventionally, there has been a document management system that scans a paper document to digitize it and performs setting of metadata such as a file name and setting of a storage destination for the digitized document. In addition, an example of using an information sharing site that shares messages and files between users, such as SNS, as a storage destination for documents is widely known. And a system in which these document management systems and information sharing sites cooperate is also conceivable. By using an API published by an information sharing service, this document management system enables the use of information such as messages, files, dates and times related to messages, and participating users held in the information sharing site in the document management system. Patent Document 1 discloses a technique in which an information sharing service and a document system cooperate. Patent Document 2 also describes a technique for acquiring information in a cooperating information sharing site and proposing a UI for setting it as a transmission destination.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Patent Document 2
Summary of the Invention
Problems 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 will be the recipient, and does not consider the point of setting a specific message within the information sharing service as the recipient. Furthermore, Patent Document 2 considers a means of sending a message to a specific message within an information sharing service. However, when setting the message to be sent, only partial information about the message is displayed, making it difficult for the user to identify the message they want to send. Therefore, the present invention aims to provide a technology that facilitates the user's destination settings by presenting a list of message threads highly relevant to the user and detailed information about each thread. [Means for solving the problem]
[0005] To solve the above problems, the present invention is an information processing device for sending a message to an information sharing service that manages messages in threads, and is characterized by comprising: an acquisition means for obtaining information of the threads of the message recipient group from the information sharing service when a user sends a message as a reply to a thread; an extraction means for extracting the threads in which the user is participating from the thread information; and a display means for displaying the threads extracted by the extraction means as the message recipients. [Effects of the Invention]
[0006] According to the present invention, the system presents threads of messages highly relevant to the user from a list of threads on an information sharing service, and further presents detailed information about each thread, thereby facilitating the user's operation of setting the recipient. [Brief explanation of the drawing]
[0007] [Figure 1] System configuration and network configuration for carrying out the present invention [Figure 2] Information Processing Function Hardware Configuration Diagram [Figure 3]This system's software and hardware configuration diagram. [Figure 4] UI diagram for the client application [Figure 5] UI diagram for business applications [Figure 6] Flowchart of the procedure for sending data from a client application to a business application. [Figure 7] UI diagram for the client application [Figure 8A] UI diagram for the client application [Figure 8B] UI diagram for the client application [Figure 9] Flowchart for UI control method that displays the recipient [Figure 10] History diagram stored on the document processing server [Figure 11] Flowchart for UI control method that displays the recipient [Modes for carrying out the invention]
[0008] The embodiments for carrying out the present invention will be described below with reference to the drawings. Furthermore, the following embodiments are not intended to limit the invention as defined in the claims, and not all combinations of features described in the embodiments are necessarily essential to the solution of the invention.
[0009] <Embodiment 1> [Overall System Configuration] Figure 1 shows an example of a system configuration and network configuration for carrying out the present invention. Network 101 is a network such as the Internet or an intranet. The 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 Network 101. The business server 131 is a server that performs various business management, and in this embodiment, it provides an information sharing service. The client terminals 121 are personal computers, laptop computers, tablet computers, smartphones, etc., and perform tasks such as acquiring image data, sending data to the scanned document processing server, and receiving information from the business server. [Hardware configuration] Figure 2 shows a modular configuration diagram of the information processing functions of the information processing device, which consists of a scanned document processing server 111, a client terminal 121, and a business server 131. The network interface 202 connects to a network such as a LAN and communicates with other computers and network devices. The communication method can be either wired or wireless. The CPU 203 executes programs read from ROM 204, RAM 205, and secondary storage device 206, and comprehensively controls the server or client terminal. ROM 204 stores pre-installed programs and data. RAM 205 is a temporary memory area; the CPU 203 loads and executes programs on RAM 205 and also uses it as a work area. Secondary storage device 206 is a non-volatile storage device such as an HDD or flash memory. The user interface 201 provides information to the user through a display, keyboard, mouse, buttons, touch panel, etc., and manages the input and output of signals such as information from the user. Computers without this hardware can be connected to and operated from other computers using remote desktop or remote shell. Each part is interconnected via a common bus 207. [Software Configuration] Figure 3 is a diagram showing the software configuration of this system. The software installed on each hardware is executed by each CPU 203 and can communicate with each other via the network 101 (arrow).
[0010] (Scan Document Processing Server) <Scan Document Processing Application Application> The scan document processing application 311 is installed on the scan document processing server 111. In this embodiment, it will be described as operating as a web application server, but other application implementation forms may also be used. The API (Application Programming Interface) 312 is a programming interface provided by the scan document processing application 311. The WebUI 313 is a user interface provided by the scan document processing application 311.
[0011] <Data Store> The data store 321 stores and stores various data from the scan document processing application 311 or the backend application 331. In the scan document storage unit 322, the files of the scan documents themselves are stored as image files such as JPEG or document files such as PDF (Portable Document Format). The scan document job queue 323 holds a queue for managing jobs waiting for setting information input processing. In the setting information management unit 324, the setting information set at the time of scanning, the file names and destinations of the scan document images, the account information required for cooperation with the business server, and the setting items required when executing requests to the API of the business server are saved and managed for each job. In the scan document processing result storage unit 325, the OCR processing results and form discrimination results are stored.
[0012] <Backend Application> The backend application 331 is responsible for the sequential execution of various processes in the background. The OCR processing unit 332 acquires the input image from the scanned document storage unit 322 and performs OCR. The OCR processing extracts the starting coordinates, width, and height of the recognized text string and the OCR result text that was recognized. The form processing unit 333 uses information such as the input image, the region pattern of the OCR processing result, and the OCR result string to determine the type of form. The determination process may be performed using any method, such as pattern recognition machine learning. The external system communication unit 334 executes the process of sending the scanned document and its processing results to the external business server 131.
[0013] (Client terminal) <Client Application> The client application 351 runs the web application of the scanned document processing application 311. One way the client application 351 is provided is by displaying the WebUI 313 in a browser and sending and receiving the necessary data with API 312 to run the web application. Alternatively, it may be a computer or smartphone application created to send and receive the necessary data with API 312.
[0014] (Business server) <Business Applications> Business application 361 is an information sharing service application that runs on business server 131. For simplicity of explanation, its form and configuration are collectively referred to as "business application" here. Similar to the scanned document processing server, it may also be provided in a form and configuration where data management and processing are separated into components such as the backend, data store, and data processing application. API362 and WebUI363 are provided by business application 361, respectively. The business data storage 364 stores data used by the business application 361. The data processing unit 365 uses message and document information stored in the business data storage to execute operation requests specified by the user. The external system communication unit 366 executes the response to the transmission process from the scanned document processing server. The following description assumes that business application 361 is an information sharing service with file and document management and messaging functions between users, but any other business application may be used. 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> Figure 4 illustrates the UI for configuring scanned documents and sending them from the scanned document processing server 111 to the business server 131, which can be performed from the client application 351. UI401 is displayed in client application 351, and the user sends a message to business server 131 with the settings for scanned documents and the scanned documents attached to the settings. Preview pane 411 displays a list of scanned jobs. The scanned jobs 421 and 431 are displayed in the preview pane 411 along with the checkboxes described below, thumbnails of the scanned documents, scan date and time, file names, and destinations. Optional information regarding the scanned documents and settings configured during scanning is also displayed. The displayed jobs are job 421 (selected) and job 431 (deselected). Checkbox 422 is used to toggle the selection and deselection states of a job. Checking the box selects the job, while unchecking it deselects it. The status of a job can be indicated by the background color of the selected job. The status can also be changed by selecting the image or area displayed on the job, but other arbitrary means of display and selection are also acceptable. The settings information editing pane 441 displays a list of settings information associated with the selected job. For the selected job 421, you can configure the file name of the scanned document 451, the subject of the message when notifying the sending business server 461, and the message content when notifying the sending business server 471. Only the settings necessary for this explanation are shown here; you may add other arbitrary settings. Each setting item has areas 452, 462, and 472 that display the setting item name, and editing fields 453, 463, and 473. The editing fields can display any editing method depending on the setting, such as text fields, dropdown menus, calendars, or radio buttons. The client application 351 reflects the values edited here as the setting item values. Users can instruct the system to save and send settings by operating the [OK] button 481 and the [Cancel] button 482.
[0016] <Screen provided by the business application> Figure 5 illustrates the message exchange between users that takes place in the information sharing service on business server 131. Screen 501 shows the WebUI 363 provided by the business application 361, displayed on a client terminal. Group 511 is a group for exchanging messages, where 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 the conversation in a tree-like format, as seen with messages 531 and 541. Furthermore, conversations take place in independent units called threads, as seen with messages 521, 531, and 551, allowing users to participate in group conversations, define their purpose, and exchange messages. Additionally, threads can be given titles, such as subject 522. It is also possible to leave a thread title blank, as in message 531. The information contained in the message includes the posting date and time (523), the posting username (524), the posted message (525), and the message attachments (526).
[0017] (Instructions for sending a message) Next, using the flowchart in Figure 6, we will explain the operation of sending a message to the information sharing service of the business server 131 with the settings configured in the client application 351. The destination business server 131 and destination group are assumed to be already configured at the time of the scan, but the business server 131 and destination group may also be displayed on the configuration information editing pane 441 of the client application 351 for configuration. The following processes are implemented by executing predetermined programs on the scanned document processing server 111, client terminal 121, and business server 131. First, client application 351 is launched and begins to interact with the scanned document processing application. First, in S601, the scanned document processing application 311 obtains a processing queue from the scanned document job queue 323. The scanned document processing application 311 obtains image files from the scanned document storage unit 322 and configuration information made at the time of scanning, such as the destination, scan date and time, and file name, from the configuration information management unit 324. The scanned document processing application 311 provides these to the client application 351. Next, in S602, the client application 351 displays the received information in the preview pane 411 for each job. In S603, the client application 351 detects that the user has selected a specific job from the displayed jobs. If a specific job is selected (Yes in S603), the process proceeds to S604; otherwise (No in S603), this process terminates. In S604, when the client application 351 detects a job selection, it reflects the configuration information associated with the document job in the configuration information editing pane 441. For each configuration item, it displays the configuration item name and, if already configured, sets a value in the editing field and displays it. (This results in the UI state shown in Figure 4.)
[0018] At S605, the client application 351 detects a selection for the edit field of setting item [o]. If a selection is detected (Yes at S605), proceed to S606; otherwise (No at S605), return to S604 and wait. In S606, upon detection, editing becomes possible for the editing field of setting item [o], allowing the user to set any value according to the input method and rules for the editing field. In S607, check if the user has finished the setup. If it is confirmed that the setup is complete (Yes in S607), proceed to S608; otherwise (No in S607), return to S605 and wait until the setup is complete. The following sections will explain what to do after you have finished editing each setting item. In S608, after editing each setting is complete, 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 restarts from the state after selecting setting item [o]. On the other hand, after editing each setting, if the [Cancel] button 482 is not detected to have been pressed (No in S608), but the user has pressed the [OK] button 481 (Yes in S609), the process proceeds to S610 to save the settings. On the other hand, if pressing the [OK] button 481 is not detected in S609 (No in S609), the program returns to S608 and waits for editing to be completed and for the [Cancel] button 482 to be pressed.
[0019] From now on, to simplify the explanation, we will start saving and sending the settings simultaneously. However, it is also possible to separate the [OK] button and the send button into different buttons and execute them after detecting the operation on each button. In 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 configuration information associated with the job and the values set in each configuration item as parameters. In S612, the business application 361 determines whether it has successfully received the request. If it has been successfully received (Yes in S612), it proceeds to S613; otherwise (No in S612), it returns to S605. In S613, the data processing unit 365 of the business application 361 notifies a message in a new thread for a specific group of parameters received in the request. As an example, consider a case where userD makes a request to Group1 with the parameters "PurchaseOrder_20201201" in the "Subject" field and "Hi, userA! I confirmed it." in the "Content" field. In this case, a message like message 551 will be 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, displaying a success or failure notification to the user. The success or failure notification can be displayed on the client application 351 using a dialog box or toast notification, or by any other means, such as sending an email to a pre-configured email address. The above explains the procedure for configuring settings on scanned documents and sending messages to the business application 361. Next, we will describe the UI features of the present invention, which allows users to easily set recipients by providing them with detailed information (date and time, whether or not the user is a member of a group) in advance when setting recipients.
[0020] <UI for selecting the recipient of the reply> Figure 7 illustrates the operation of switching from a UI for the user to enter a subject to a UI for specifying and setting the reply destination in the present invention. Job 701 is selected from the jobs displayed in the job list. This is setting item 711 for displaying and setting the subject of the thread to which the message will be sent. Checking checkbox 712 switches the user to a mode where they can reply to a specific thread. Checking checkbox 712 also changes editing field 713 to a dropdown menu. When the checkbox 712 is checked, the client application 351 executes a request to retrieve thread information from the API 362 provided by the business application 361, using the destination group as a parameter. This request is processed by the data processing unit 365 of the business application 361. The client application 351 retrieves a list of all threads within the requested group. This retrieved list of threads 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 the business application 361 in a pull-down menu, and further prioritizes presenting threads that are highly relevant to the user in the present invention, as well as controls for obtaining detailed information about the threads. Job 801 is selected, and the pull-down menu 811 displays the list of threads acquired by client application 351, as explained in Figure 7. The pull-down menu 811 consists of two areas: area 821 and area 831. Area 821 prioritizes displaying threads containing messages recently received by the user. Area 831 displays a list of threads within a group. The number of threads displayed in areas 821 and 831 may be limited by any method of filtering the update time, number of retrieved items, or other data provided by the API. Whether or not to display the same items in area 831 as those displayed in area 821 is also optional. The information displayed in the pull-down menu 811 includes information 822 for identifying the thread and a control 823 associated with the thread. While the thread subject is used as an example of information for identifying the thread, any information such as the first sentence of the message, the poster, the date and time, or the filename of any attached files can be used. When the client application 351 detects a user action 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 exchange, date and time, etc. The display method is expected to be something like a tooltip 841 (balloon display), but any method is acceptable, such as the dialog 851 (dialog display) in Figure 8B.
[0022] (Example 1: Extract threads from the recipient group) <Processing to notify by specifying a thread> The flowchart in Figure 9 describes the operation of specifying the destination thread and notifying a message. Similar to the flowchart in Figure 6, it is assumed that the destination business server and destination group are already configured at the time of scanning. Alternatively, the business server and destination group may be displayed and configured on the configuration information editing pane 441 of the client application 351. If a destination thread is specified, the destination thread ID must be passed as a parameter to the business server 131 in step S611, as shown in the flowchart in Figure 6. For all other operations, from selecting the scan document job to editing other settings, the process can be explained using the same steps as in the flowchart in Figure 6, so the explanation is omitted here. In S901, when the client application 351 detects the selection of any job from the job list displayed in the user's preview pane 411 in Figure 4, it displays the configuration information associated with the selected job in the configuration information editing pane 441. In S902, the client application 351 displays a checkbox 712 on the editing item for the message subject setting information in the job, which allows switching to a mode where the destination thread is specified (Figure 7). If a user wants to send a message to a specific thread, they should check checkbox 712, which appears in the "Subject" field of the settings. In S903, if the client application 351 detects that checkbox 712 is checked (Yes in S903), it proceeds to S904 and switches the display of the editing field to a pull-down menu. If the checkbox is not checked (No in S903), this process ends and the operations in the flowchart in Figure 6 are performed.
[0023] In S905, the client application 351 requests API 362 provided by the business application 361 to retrieve a list of threads, using the configured destination group as a parameter. In S906, the business application 361 accepts the received request, and the data processing unit 365 processes it. Based on the destination group parameters received in the request, a list of threads within the group is sent to the client application 351 via the document processing server 111. If the request is not accepted correctly or processing is unsuccessful (No in S906), this process is terminated. The timing for making the request is currently set to checking checkbox 712, but it could also be set to start when the client application 351 is launched or when the job is displayed in the preview pane 411. Specifically, the request to retrieve the thread list for multiple jobs could be initiated when the client application 351 is launched or when the job is displayed in the preview pane 411, or the request could be initiated when a job is selected. If the request is processed successfully, client application 351 in S907 sorts the retrieved list of threads by update date and time. In the following S908, when filtering the number of threads displayed in the dropdown menu by date and time, only threads from the specified date and time onward will be extracted. Furthermore, in S907 and S908, you may set an upper limit on the setting value. In addition to the update date and time, the setting value for which you set an upper limit may also be the number of retrieved items or any other method of filtering the data provided by the API. For each of the acquired and extracted threads, the following series of processes (S910~S912) are repeatedly executed (S909b,e).
[0024] S910 requests API 362, provided by business application 361, to retrieve properties such as the 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 about 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 or not. If the request fails (No in S911), it returns to S910 and attempts to resubmit the request. An upper limit is set to prevent the resubmissions from being repeated indefinitely. On the other hand, if the request is successful (Yes in S911), it proceeds to S912. In S912, the client application 351 stores and retains the thread obtained in the request, associating it with its detailed information. The above process is repeated for each thread that has been acquired and extracted. Exiting the loop, in the subsequent S913, the client application 351 extracts only the threads in which the operating user is participating from among the threads that were successfully retrieved. In S914, client application 351 extracts the thread with the most recent update time. In S915, the client application 351 prioritizes displaying the most recent thread and control in which the user is participating on the pull-down menu 821. In S916, display all threads and controls, regardless of whether they are other threads or whether they have been extracted, on the 831 dropdown menu. In S917, the client application 351 determines whether an operation on the control has been detected. If an operation is detected (Yes in S917), it proceeds to S918; otherwise (No in S917), it terminates the process.
[0025] In S918, for the thread associated with the control that detected the operation, the stored thread details are used to create a message to be displayed in a tooltip or dialog, the message is displayed, and then the process is terminated. As a result, newer messages from groups the user is a part of will be prioritized. Furthermore, by checking the message displayed in the tooltip, users can understand the topic of the thread from the conversation content and date / time before setting the recipient, making it easier for them to identify the thread they want to send a message to.
[0026] (Example 2: Extracting highly relevant information from transmission history) Next, we will explain how to display threads that are highly relevant to the user by using the history sent via the document processing server 111 to indicate the destination. Figure 10 is a diagram illustrating the historical data. The storage area 1001 is for storing user operation logs and is located in the data store 321. Note that these logs may be stored on an external server different from the scanned document processing server 111. History Table 1002 summarizes the history in a tabular format. History Table 1002 stores information such as the serial number, history ID, username, result, transmission date and time, file name as file information, number of pages, recipient group name, and thread ID as thread information. Each history record is issued a unique history ID, which distinguishes them from each other. In addition to the above, if the configuration involves switching between multiple business servers, information about the business servers may be optionally added to the history.
[0027] <Process to determine the suggested thread from the history> The flowchart in Figure 11 explains how to determine which thread to present to the user from the history. The operations after identifying the thread from the target history and obtaining detailed information are the same as those explained from S912 onwards in the flowchart in Figure 9, so the explanation is omitted. This process is executed when the user checks checkbox 712 for replying. In S1101, the client application 351 retrieves the transmission history from the history storage area 1001. In S1102, the client application 351 extracts only the history from the transmission history that was recorded after the specified date and time. In S1103, client application 351 retrieves the destination group from the configuration information associated with the selected job and extracts the history of destinations that match this group. For each of the extracted histories, the following series of processes (S1105~S1108) are repeatedly executed between S1104b and S1104e. In S1105, for each extracted history, the client application 351 obtains the thread ID of the history.
[0028] In S1106, the client application 351 uses the acquired group and thread ID to make a request to API 362 provided by the business application 361 and retrieve 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 about the thread is sent to the client application 351 via the document processing server 111. The success of the request is determined in S1107. If the request fails (No in S1107), a re-request will be attempted. A limit will be placed on the number of re-requests to prevent them from being repeated indefinitely. If the client application 351 successfully completes the request, it proceeds to S1108. In S1108, the acquired thread and its detailed information are linked, stored, and retained. The above process is repeated for each extracted history entry. From this point onward, the system extracts messages that are highly relevant to the user from the threads the user is participating in and their update times, displays them in a dropdown menu, and then presents this stored detailed information to the user by detecting their actions on the controls displayed in the dropdown menu. By performing the above steps, it becomes possible to target only jobs sent via the document processing server and present messages that are highly relevant to the user.
[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 storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. [Explanation of symbols]
[0030] 111 Scanned Document Processing Server 121 Client terminals 131 Business Server 311 Scanned Document Processing Applications
Claims
1. An information processing device that transmits a message to an information sharing service that manages messages in a thread, an acquisition means for acquiring thread information from the information sharing service when a mode for sending the message as a reply to the 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 a thread list to be displayed 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 thread list; 13. 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 a list of 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, when the mode is set by the user on the screen, information on the thread regarding a conversation taking place within a group in which the user participates from the information sharing service.
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 a list of the threads with priority.
2. The information processing apparatus according to claim 1,
6. The acquiring means acquires information on threads having message transmission histories after a specified date and time from the information sharing service.
2. The information processing apparatus according to claim 1,
7. An information processing device as described in any one of claims 1 to 6, characterized in that the control means controls the display to present detailed information about a thread in the list of displayed threads for which a specified operation has been performed by the user.
8. The information processing device according to 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 as 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 a thread, comprising: an acquisition step of acquiring thread information from the information sharing service when a mode for sending the message as a reply to the 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 information of the threads, and controlling the user to specify a thread to which the scanned document and the message are to be sent from the displayed list of threads; 13. A method for controlling an information processing apparatus comprising the steps of:
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.
