Program, scanning device, control method

Abstract

To provide a mechanism capable of easily discriminating a group sharing image data from an object by selecting the registered object.SOLUTION: The program of the present invention causes an image processing apparatus that generates image data by scanning a document and transmits the generated image data to execute a first display step of displaying a plurality of groups of a chat service, a reception step of receiving selection of a group by a user from the displayed plurality of groups, and a second display step of displaying a channel included in the selected group, An execution step of executing processing for generating the image data by scanning the document and processing for transmitting the generated image data.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] a program, a scanning apparatus, control and a method. [Background Art]

[0002] Patent Document 1 discloses an image processing apparatus that displays an acquired title and icon of an application as an object in order to make it easy to recognize which application an object for executing the application belongs to. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2018-133000 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] When a user uses a chat service published on the Internet to share image data generated by scanning in a specific talk room of the chat service, the following problems arise. For example, it is conceivable to store in advance information on a specific talk room (group information) with which image data is shared in association with an object, and transmit the image data to the specific talk room through an operation on the object.

[0005] In this case, as in Patent Document 1, merely displaying the title and icon of the application allows recognition of which chat service the object belongs to, but does not allow easy recognition of which group the object is for sharing image data with.

[0006] In particular, it's conceivable that multiple objects might be registered for each of the multiple chat rooms in order to share image data within each of them. In that case, it would be difficult for users to easily determine which object is for which chat room.

[0007] This invention has been made in view of the above problems, and aims to provide a mechanism that allows for easy identification of a group from which image data is shared by an object when a registered object is selected. [Means for solving the problem]

[0008] The program of the present invention, A program executed by a scanning device, The display unit of the scanning device A first display step of displaying multiple groups of a chat service, and a first reception step of accepting a group selection by the user from the displayed multiple groups, The display unit A second display step of displaying multiple channels included in the selected group, and a second reception step of accepting a channel selection by the user from the displayed multiple channels, Key operation for receiving execution instructions displayed on the display unit The scanning device is instructed to perform a third reception process to receive the original document, and both the scanning process, which scans the original document and generates image data, and the transmission process, which transmits the generated image data, are performed with the channel selected for one reception process received in the third reception process. Operation of the aforementioned key Based on this, the scanning device performs the operation once Operation of the aforementioned key The image data transmitted by the transmission process performed based on the above is stored in association with the selected channel. [Effects of the Invention]

[0009] By selecting a registered object, a mechanism can be provided that allows for easy identification of the group from which the image data is shared. [Brief explanation of the drawing]

[0010] [Figure 1] Diagram illustrating an example of the system configuration of the present invention [Figure 2] Diagram illustrating an example of the hardware configuration of an MFP 101 [Figure 3] Diagram illustrating an example of the hardware configuration of a mobile terminal 200 [Figure 4] Diagram illustrating an example of the hardware configuration of a messaging application server 300 [Figure 5] Diagram illustrating an example of the hardware configuration of a bot server 400 [Figure 6] Diagram illustrating an example of a sequence for transmitting a file generated by scanning by an MFP 101 to a messaging application server 300 [Figure 7] Flowchart illustrating an example of scan-to-chat processing executed by an MFP 101 [Figure 8] Diagram illustrating an example of a sequence for transmitting a file generated by scanning by an MFP 101 to a messaging application server 300 via a bot server 400 [Figure 9] Flowchart illustrating an example of scan-to-chat processing [Figure 10] Diagram illustrating an example of a file structure in a messaging application server [Figure 11] Diagram illustrating an example of a message screen of a messaging application [Figure 12] Diagram illustrating an example of a setting registration screen [Figure 13] Diagram illustrating an example of a home screen displayed on an operation unit 116 of an MFP 101 [Figure 14] Diagram illustrating an example of screen transition in scan-to-chat processing [Figure 15] Diagram illustrating an example of screen transition in scan-to-chat processing [Figure 16] Diagram illustrating an example of association between IDs and token information [Figure 17] Diagram illustrating an example of a button setting registration screen [Figure 18] Diagram illustrating each element of a message service and icons corresponding thereto [Figure 19]Flowchart showing processing when acquiring an icon DESCRIPTION OF THE EMBODIMENTS OF THE INVENTION

[0011] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. The configurations shown in the following examples are merely examples, and the present invention is not limited to the illustrated configurations. EXAMPLE

[0012] FIG. 1 is a diagram showing an example of the system configuration of the present invention. The system configuration of the present embodiment includes a mobile terminal 200 which is an example of a terminal device, an MFP (Multi Function Peripheral) 101 which is an image processing device capable of communicating via a network 100, and a message application server 300. A bot server 400 is also connected via the network 100 and is capable of communication. The message application server 300 is a chat server that receives messages and image data transmitted from the MFP 101 and the mobile terminal 200, and manages a chat service displayed on the mobile terminal 200 or a PC (not shown) in response to a user operation. The bot server 400 performs association with information (token information) corresponding to a bot application installed in the message application server 300 connected to the MFP 101, and transfers a request from the MFP 101 to the message application server 300. Note that the network 100 of the present embodiment may be the Internet or a LAN (Local Area Network). Further, the network 100 may be wired or wireless.

[0013] FIG. 2 is a diagram showing an example of the hardware configuration of the MFP 101. The MFP 101 includes a CPU 111, a ROM 112, a RAM 113, a storage 114, an operation unit I / F 115, an operation unit 116, a reading unit I / F 117, a reading unit 118, a printing unit I / F 119, a printing unit 120, a wireless communication unit I / F 121, and a wireless communication unit 122. The MFP 101 further includes a FAX unit I / F 123, a FAX communication unit 124, a communication unit I / F 125, and a communication unit 126.

[0014] The control unit 110, including the CPU 111, controls the operation of the entire MFP 101. The CPU 111 reads control programs stored in the ROM 112 or storage 114 into the RAM 113 and performs various controls such as read control and print control. The ROM 112 stores control programs that can be executed by the CPU 111. The ROM 112 also stores boot programs and font data. The RAM 113 is the main memory and is used as a temporary storage area for deploying the various control programs stored in the work area, ROM 112, and storage 114. The storage 114 stores image data, print data, various programs, and various setting information. In this embodiment, flash memory is assumed as the storage 114, but auxiliary storage devices such as SSDs (Solid State Drives) or HDDs (Hard Disk Drives) may be used. Alternatively, eMMC (embedded Multi Media Card) may be used.

[0015] In this embodiment, the MFP101 uses one CPU 111 and one memory (RAM 113) to execute each process shown in the flowchart described later, but it is not limited to this. For example, multiple CPUs, RAM, ROM, and storage can work together to execute each process shown in the flowchart described later. Alternatively, some processes may be executed using hardware circuits such as ASICs or FPGAs.

[0016] The control interface 115 connects the control unit 110 to the control unit 116, which includes a display unit such as a touch panel and hard keys. The control unit 116 displays information to the user and detects user input.

[0017] The reading unit interface 117 connects the reading unit 118, such as a scanner, to the control unit 110. The reading unit 118 reads the image of the document, and the CPU 111 converts that image into image data such as binary data. The image data generated based on the image read by the reading unit 118 is transmitted to an external device or printed on recording paper.

[0018] The printing interface 119 connects the printing unit 120, such as a printer, to the control unit 110. The CPU 111 transfers image data (print data) stored in the RAM 113 to the printing unit 120 via the printing interface 119. The printing unit 120 prints an image based on the transferred image data onto recording paper fed from the paper cassette.

[0019] The wireless communication interface 121 is an interface for controlling the wireless communication unit 122 and connects to the control unit 110 and an external wireless device (in this case, a mobile terminal 200) via wireless communication.

[0020] The control unit 110 connects to the public telephone network 107 by controlling the fax communication unit 124, which is similar to a facsimile machine, via the fax unit interface 123. The fax unit interface 123 is an interface for controlling the fax communication unit 124, and by controlling a modem or NCU for facsimile communication, it is possible to connect to the public telephone network and control the facsimile communication protocol.

[0021] The communication interface 125 connects the control unit 110 and the network 100. The communication interface 125 allows the communication unit 126 to transmit image data and various internal information to external devices on the network 100, and to receive print data and information on the network 100 from information processing devices on the network 100. Transmission and reception via the network 100 can be done using email or by sending files using other protocols (e.g., FTP, SMB, WebDAV, etc.). Furthermore, image data and various configuration data can also be transmitted and received over the network 100 via HTTP communication from mobile terminals 200, message application servers 300, and bot servers 400.

[0022] Figure 3 shows an example of the hardware configuration of the mobile terminal 200. In this embodiment, the mobile terminal 200 is assumed to be a device such as a smartphone or tablet PC, but it may be any other information processing device that is capable of Wi-Fi communication.

[0023] The CPU 207 reads the control program stored in the ROM 208 and executes various processes to control the operation of the mobile terminal 200. The ROM 208 stores the control program. The RAM 209 is used as the main memory and temporary storage area for the CPU 207, such as the work area. The HDD 210 stores various data such as photos and electronic documents.

[0024] The control panel 201 has a touch panel function that can detect user touch operations and displays various screens provided by the OS and email sending application. The control panel 201 is also used to check information stored in the message application server 300. The user can input desired operation instructions to the mobile terminal 200 by touching the control panel 201. The mobile terminal 200 is equipped with hardware keys (not shown), and the user can input operation instructions to the mobile terminal 200 using these hardware keys.

[0025] Camera 204 takes images according to the user's imaging instructions. The images taken by camera 204 are stored in a designated area of ​​HDD 210. It is also possible to obtain information from QR codes read by camera 204 using a program capable of analyzing QR codes (registered trademark).

[0026] The mobile terminal 200 can exchange data with various peripheral devices via the NFC communication unit 205, the Bluetooth® communication unit 206, and the wireless LAN communication unit 211. The Bluetooth communication unit 206 of the mobile terminal 200 may also support Bluetooth® Low Energy. The terminal is beginning to become widespread.

[0027] Figure 4 shows an example of the hardware configuration of the message application server 300. The CPU 301 reads the control program stored in the ROM 302 and executes various processes to control the operation of the message application server 300. The ROM 302 stores the control program. The RAM 303 is used as the main memory and temporary storage area for the CPU 301, such as the work area. The HDD 305 stores various data such as messages, images, and channel information. Data can be exchanged with various devices such as the mobile terminal 200 and MFP 101 via the communication unit 304. The communication unit 304 may perform wired communication using Ethernet® or wireless communication such as Wi-Fi.

[0028] Figure 5 shows an example of the hardware configuration of the bot server 400. The CPU 401 reads the control program stored in the ROM 402 and executes various processes to control the operation of the message application server. The ROM 402 stores the control program. The RAM 403 is used as the main memory and temporary storage area for the CPU 401, such as the work area. The HDD 405 stores various data such as messages, image data, and channel information. Data can be sent and received with various devices such as the mobile terminal 200, MFP 101, and message application server 300 via the communication unit 404.

[0029] Figure 13 shows an example of the home screen displayed on the operation unit 116 of the MFP101. The operation unit 116 consists of a touch panel 601 that displays the operation screen and LEDs 610 and 611. The touch panel 601 is an instruction means, and functions as both a receiving means for receiving instructions from the user and a display means for displaying the screen. The user directly touches the screen displayed on the touch panel 601 with an object such as a finger or stylus to instruct the execution of various functions based on the displayed screen.

[0030] The touch panel 601 shown in Figure 13 displays the home screen 608. The home screen 608 is the initial screen used to instruct the execution of each function of the MFP101, and it is the screen used to select the display for various settings for each function that the MFP101 performs, such as copy, fax, scan, and media print.

[0031] The status confirmation button 605 is an object used to display a screen (status confirmation screen) that allows you to check the status of the MFP101. From this status confirmation screen (not shown), it is possible to display the transmission history and job execution history.

[0032] The scan-to-chat button 602 is an object for executing the scan-to-chat process. When the scan-to-chat button 602 is selected by the user, predetermined screens shown in Figures 14 and 15 are displayed on the operation unit 116 according to the button's settings. The scan-to-chat process is explained in detail in Figures 6 and 7. The scan-to-chat button 602 can be registered on the button setting registration screen 1701 shown in Figure 17.

[0033] Additionally, users can register other scan-to-chat buttons 609 on the button setting registration screen 1701 shown in Figure 17.

[0034] The scan button 603 is an object used to display the scan selection screen (not shown). The scan selection screen is used to select a transmission function, such as sending an email, sending files via SMB, FTP, or HTTP, or sending an Internet fax (iFax). Touching the object representing the displayed transmission function will display the settings screen for that transmission function.

[0035] The address book button 604 is an object that, when selected by the user, displays the address book screen of the MFP101. LEDs 610 and 611 notify the user of the status of the MFP101. LED 610 lights up when receiving or executing emails or print jobs, and LED 611 lights up when any error occurs in the MFP101. The stop button 606 is an object that cancels various operations and is always displayed on the operation unit 116. The HOME button 607 is an object that displays the home screen 608 and is always displayed on the operation unit 116. The menu button 612 is an object that displays a screen for configuring environment settings such as the language used and settings for various functions.

[0036] Figure 6 shows an example of a sequence in which the MFP 101 scans a document and sends the generated file to the message application server 300. The sequence in Figure 6 is started when the scan-to-chat button 602 in this embodiment is selected. The processing of the MFP 101 is achieved by the CPU 111 of the MFP 101 reading the program stored in the ROM 112 into the RAM 113 and executing it. The processing of the message application server 300 is achieved by the CPU of the message application server 300 reading the program stored in the ROM 302 into the RAM 303 and executing it.

[0037] In S901, the CPU 111 of MFP101 accepts the selection of the scan-to-chat button 602, which is the instruction to start a scan. If the scan-to-chat button 602 is selected and a screen appears that allows selection of channels, mentioned users, and pre-written messages, the scan will start once these selections are accepted. Details are explained in the screen flow in Figures 14 and 15.

[0038] In S902, the CPU 111 controls the reading unit 118 to read the image of the document based on the scan settings set in the button setting registration screen 1701 shown in Figure 17, which will be described later. In S903, the CPU 111 generates image data (file) based on the read image.

[0039] In S904, the CPU 111 controls the communication unit 126 and executes a transmission process to post image data to the message application server 300 via HTTP communication. Here, the token information registered on the button setting registration screen 1701 in Figure 17, along with the channel information, mentioned user information, and comments set on the setting registration screen 1701 or on the screens in Figures 14 and 15, are sent along with the image data. This information is sent by executing the command "HTTP POST https: / / message.com / api / files.upload".

[0040] Here, token information refers to information corresponding to a bot application installed on the message application server 300, and is information that uniquely identifies the bot application. Furthermore, this bot application corresponds to information corresponding to a workspace registered on the message application server 300, and is information that uniquely identifies the workspace. In other words, token information is information corresponding to a workspace registered on the message application server 300, and is capable of uniquely identifying the workspace.

[0041] Here, a workspace is like an organization or group to which multiple users belong within a messaging app. A channel is like a chat room within a workspace. In this context, a chat room is a mechanism for multiple users participating in the chat room to send and receive messages and communicate in a conversational manner. In this embodiment, channels are described as chat rooms, but this is not limited to this; any mechanism for multiple users to send and receive messages and communicate in a conversational manner is acceptable. For example, group chats, rooms, talk rooms, or groups are also acceptable.

[0042] Here, a bot application is an application that registers the MFP101 as a user within the messaging application and is used to post messages and image data. It is installed on the messaging application server 300. By specifying a bot application and sending image data to the messaging application server 300, the bot application posts the received image data in the messaging application. The HDD 305 of the messaging application server 300 stores bot applications and token information in association with each other, and also associates bot applications with workspaces. Therefore, by receiving token information from the MFP101, the messaging application server 300 can return information about the workspace associated with the bot application associated with that token information. Alternatively, the token information, bot application, and workspace may be directly associated. This allows the user to select a workspace (the workspace to which they want to send image data) from among many workspaces that corresponds to the pre-registered token information.

[0043] In S905, the CPU 301 of the message application server 300 searches for registered workspace information and application information using the token information received in S904, and associates the received image data and channel information with the specified channel and stores it. In other words, it controls the posting of the received image data and comments to the specified channel. Furthermore, if a mentioned user is specified, the CPU 301 also associates the received image data with the channel and the user to whom the post is intended and stores it. As a result, when a user launches the message application on their mobile device 200 and selects a channel to check the content of the conversation in the aforementioned channel, a screen with the posted received image data is displayed.

[0044] In S906, the CPU 301 of the message application server 300 sends a result corresponding to whether the post was successful or not as HTTP communication response information to the MFP 101. If the post is successful, the CPU 111 of the MFP 101 may display a notification on the operation unit 116 indicating that the post was successful. If the post fails, the CPU 111 of the MFP 101 may display a notification on the operation unit 116 indicating that the post failed. Alternatively, no notification may be displayed when the post is successful, and a notification indicating that the post failed may only be displayed when it fails.

[0045] Figure 7 is a flowchart showing an example of the scan-to-chat process performed by the MFP101. The process in the flowchart in Figure 7 is executed when the CPU111 reads the program stored in ROM112 into RAM113 and executes it. The flow in Figure 7 also starts when the MFP101 is powered on. Note that the flow in Figure 7 assumes that the service, token information, and channel have been set on the button setting registration screen 1701 in Figure 17.

[0046] In S1001, the CPU 111 determines whether the scan-to-chat button 602 is selected. If it is selected, proceed to S1002. Otherwise, return to S1001.

[0047] In S1002, the CPU 111 uses the previously registered token information 1503 to send information to the message application server 300 indicating that it is requesting channel list information via HTTP communication.

[0048] In S1003, the CPU 111 determines whether or not it has received channel list information from the message application server 300 in response to the channel list information acquisition request sent in S1002. Specifically, it determines that the channel list information has not been received if the status code in the HTTP communication response is an error, or if the response body contains parameters indicating that the information could not be acquired. If it determines that the information has been received, the process proceeds to S1010. Otherwise, the process proceeds to S1004.

[0049] In S1004, CPU 111 identifies the cause of the error based on the results obtained in S1003. If it determines that the error code is due to the channel not existing on the message application server 300, it proceeds to S1005. Otherwise, it proceeds to S1007.

[0050] In S1005, the CPU 111 displays information on the operation unit 116 indicating that it was unable to receive channel list information.

[0051] In S1006, CPU111 determines whether the back button is selected or not. If it is selected, it returns to S1001. Otherwise, it returns to S1006.

[0052] In S1007, CPU111 requests and obtains icon information for other channels in the target workspace from the message application server 300.

[0053] In S1008, the CPU 111 displays a list of acquired icons and channel names on the control unit 116 on the channel selection screen.

[0054] In S1009, CPU111 determines whether a channel has been selected. If it is selected, proceed to S1010. Otherwise, return to S1009.

[0055] In S1010, CPU111 determines each time whether the scan-to-chat operation is in mention mode. If it is in mention mode, proceed to S1012; otherwise, proceed to S1011.

[0056] In S1011, CPU 111 determines from the received channel list information whether the user set as the target of the mention in the mention user selection field 1721 exists in the target channel. If it determines that the target user exists in the channel, it proceeds to S1015; otherwise, it proceeds to S1012.

[0057] In S1012, CPU111 obtains icon information of users belonging to the target channel from the message application server 300.

[0058] In S1013, the CPU 111 displays the mention user selection screen 714 shown in Figure 14 on the touch panel 601 of the operation unit 116. After selecting the user to be mentioned in S1013, the system may also display an option to choose whether or not to register the selected user as a user to be mentioned in a fixed mention.

[0059] In S1014, CPU111 determines whether a destination mention has been selected. If it is selected, proceed to S1015. Otherwise, return to S1014.

[0060] In S1015, the CPU 111 displays the scan-to-chat setting confirmation screen 716 shown in Figure 15 on the operation unit 116. If S1015 detects that all settings for the mention target users and the comment selection screen to be set in scan-to-chat have been confirmed, the process proceeds to S1016.

[0061] In S1016, the CPU 111 controls the reading unit 118 based on the scan settings, reads the image of the document, and generates image data. The scan settings used are those specified by the user on the button setting registration screen 1701 in Figure 17.

[0062] In S1017, CPU111 converts the image data generated in S1016 into the file format set on the transmission settings screen.

[0063] In S1018, CPU111 generates posting parameters. These parameters include the destination channel information, file name, mention information, and posting comment. The file format is set to match the file format specified in the sending settings. The file name is the file name specified in the sending settings.

[0064] In S1019, CPU 111 sends the previously registered token information 1503, the files generated in S1017 and S1018, and the posting parameters to the message application server 300 using the HTTP POST method. Note that token information 1503 is the token information entered in the token information input field 1711 in Figure 17.

[0065] By sending this data (converted image data files and posting parameters) to the message application server 300, the message application server 300 performs the following process: it controls the posting of the received file to the user indicated by the received mention information in the channel indicated by the receiving channel information.

[0066] In S1020, the CPU 111 receives the posting result from the message application server 300 and displays it on the touch panel 601 of the operation unit 116. In this embodiment, the user can easily post files from the MFP 101 to the channel of the message application server.

[0067] In this embodiment, it is assumed that only one token is registered. However, if multiple tokens are registered, the processes involving the token information, such as S1002, S1003, and S1019, will be executed for each registered token.

[0068] An example of the screen displayed on the operation panel 201 of the mobile terminal 200, after the image data converted in processing S1019 and the posting parameters are sent to the message application server 300, will be described later with reference to Figure 11.

[0069] Figures 14 and 15 show an example of the screen transitions in the scan-to-chat process. The screens in Figures 14 and 15 are displayed on the touch panel 601 of the operation unit 116. When the scan-to-chat button 602 displayed on the home screen 608 is selected, the scan-to-chat screen is displayed on the touch panel 601 of the operation unit 116.

[0070] The icon displayed for the Scan to Chat button varies depending on the settings. If only the destination app service information is registered, the Scan to Chat button (708) will be displayed on the home screen (704).

[0071] When the scan-to-chat button 708 is selected, the organization selection screen 712 is displayed on the touch panel 601 of the control unit 116. On the organization selection screen 712, the user is shown a screen for selecting an organization that is included in the service registered in association with the scan-to-chat button 708.

[0072] Once an organization is selected on the organization selection screen 712 and the OK button is selected, the channel selection screen 713 is displayed, allowing the user to select a destination channel (posting destination) from the channels included in the selected organization.

[0073] On the channel selection screen 713, the destination channel (posting destination) is selected, and when the OK button is selected, the mention user selection screen 714 for selecting the mention user is displayed.

[0074] When a mention user is selected on the mention user selection screen 714 and the OK button is selected, the standard text selection screen 715, the recipient confirmation screen 716, or the sending screen 717 is displayed. If the user has set the standard text selection setting to ON, the standard text selection screen 715 is displayed, and the user selects the text to be displayed along with the image data. When a standard text is selected on the standard text selection screen 715 and the OK button is selected, the recipient confirmation screen 716 is displayed. The recipient confirmation screen 716 displays the username of the mention user and the standard text to be posted as recipient mentions, allowing the user to confirm the content of the post. The recipient confirmation screen 716 is also displayed when the user has set the standard text selection setting to OFF and the recipient confirmation setting to ON, and the mention user is selected on the mention user selection screen 714 and the OK button is pressed.

[0075] When the OK button is selected on the recipient confirmation screen 716, the document is scanned, the image data generated by the scan is sent, and the sending screen 717 is displayed. The sending screen may be displayed during the document scanning process, or after the document scanning is complete and the image data transmission has begun. Alternatively, if the user sets the standard text selection setting and recipient confirmation setting to OFF, selects a mentioned user on the mentioned user selection screen 714, and presses the OK button, the document is scanned. The image data generated by the scan is then sent, and the sending screen 717 is displayed. The timing of the display of the sending screen 717 may be during the scan process, or after the scan is complete and transmission is in progress.

[0076] If the recipient organization is registered to the Scan to Chat button, the Scan to Chat button 709 will be displayed on the home screen 705.

[0077] When the Scan to Chat button 709 is selected, the channel selection screen 713 is displayed. If the organization associated with the Scan to Chat button does not exist on the registered service, the organization selection screen 712 is displayed, and the user is asked to select an organization.

[0078] If the destination channel is registered to the Scan to Chat button, the Scan to Chat button 710 will be displayed on the home screen 706.

[0079] When the Scan to Chat button 710 is selected, the mention user selection screen 714 is displayed. If the channel associated with the Scan to Chat button does not exist on the registered service, the channel selection screen 713 is displayed, and the user is asked to select a channel.

[0080] If the Scan to Chat button includes a mentioned user, the Scan to Chat button (711) will appear on the home screen (707).

[0081] When the scan-to-chat button 711 is selected, the pre-written message selection screen 715 is displayed. If the mentioned user registered in association with the scan-to-chat button does not exist on the registered service, or if the scan-to-chat button is set to mention mode each time, the mentioned user selection screen 714 is displayed, and the user can select a mentioned user.

[0082] Furthermore, when the Scan to Chat button is selected, the organization, channel, and mentioned user registered to the button retrieve the latest information (such as channel list information) from the messaging application server 300, and it is determined whether the retrieved information includes the information registered in association with the button. This enables the above process.

[0083] Furthermore, if the information registered in association with a button does not exist in the service, that is, if it is not included in the information obtained from the message application server 300, the update screen 718 is displayed. If the YES button is selected on this update screen 718, the information selected by the user because it does not exist in the service is registered in association with the selected button. If the NO button is selected, the information is not registered in association with the button. Depending on whether the YES or NO button is selected, the standard phrase selection screen 715 is displayed.

[0084] In this embodiment, if the destination channel is set for the scan-to-chat button, the mention user selection screen 714, the standard text selection screen 715, and the recipient confirmation screen 716 do not need to be displayed even if no mention user is set. In other words, the system may be configured such that selecting the scan-to-chat button starts scanning the document and sends the generated image data.

[0085] Figure 11 shows an example of a message screen in a messaging application. The message screen 1201 in Figure 11 is displayed when the messaging application is launched on the mobile terminal 200 and the process S1019 is executed on the MFP 101. The mobile terminal 200 is also communicating with the messaging application server 300.

[0086] When a user launches the messaging app on their mobile device 200 and logs in using their account ID and password, a screen specific to that user is displayed.

[0087] Message 1204 is a message displayed (posted) when a user with user 1's account uses MFP 101 to scan and generate image data, along with posting parameters, and send them to the message application server 300. In the example in Figure 11, "Channel 1" is specified as the destination channel in the posting parameters, and "User 3," who belongs to Channel 1, is specified as the mentioned user. Also, "Document.pdf" is specified as the file name in the posting parameters, and "Sending." is specified as the comment. Note that the file name and comment are specified by the user in the detailed settings screen of Scan to Chat (not shown).

[0088] Additionally, the message screen (1201) displays the names and icons of the channels (1208), groups (1209), and users (1210) that the logged-in user is a part of. The icon of the messaging app to which the user is logged in (1205) is also displayed, and for the workspace (organization) to which the user is logged in, the workspace name and icon are displayed (1206). Furthermore, information about the recipient of the post (1202) and the message exchange are displayed (1203). When posting, adding a comment with "@" at the beginning of the username indicates that the recipient of the post specifically wants to inform a particular user within the channel (1204).

[0089] In the case of Figure 11, the messaging app notifies User 3's mobile device that a post has been received. This makes it easier for User 3 to notice User 1's post. If User 3's mobile device 200 is a smartphone, the user is notified via icon notification, vibration, or ringtone. If User 3's mobile device 200 is a desktop device, the user is notified via desktop notification or similar. In addition, to display this screen, the messaging app server 300 searches for and displays the necessary information from the data structure described in Figure 10. For example, the post in message 1204 corresponds to "Statement 3 + File 1" in the exchange content 505, and attribute information such as the name of File 1 is obtained from 504 and displayed on the message in the form of a file icon. When the user selects this file icon, they can obtain File 1, which belongs to file 504. Note that while files posted to this channel are displayed as icons here, a preview image of the file may also be displayed.

[0090] Figure 10 shows an example of the file structure within the message application server. This file structure is stored on the HDD 305 of the message application server 300, and the screen in Figure 11 is displayed based on this file structure. The message application server 300 manages data by having smaller groups such as channels, groups, users, and files within a larger group called workspace. Channel 501 is a type of chat room that all members of the workspace can join, and all posted content is searchable by anyone. Group 502 is a channel for discussions that should not be made public to all members, and an invitation is required to view and join. User 503 is a user participating in this workspace. File 504 stores attached files. Furthermore, the content of interactions 505 in channels, groups, and users are each linked and stored. For example, channel 1 is linked and stored with the users participating in channel 1, and messages and image data exchanged in channel 1 are also linked and stored with channel 1. This storage allows the system to display the users corresponding to the specified channel information when a channel is selected on the channel selection screen 713. It can display the users participating in that channel.

[0091] Figure 17 shows an example of the button setting registration screen 1701. The setting registration screen 1701 is a screen displayed on the operation unit 116 of the MFP 101. The setting registration screen 1701 may also be displayed as a web page on the operation unit of an information processing device such as a PC connected to the MFP 101 via a network.

[0092] The button setting registration screen 1701 in Figure 17 displays the service 1712, connection destination input field 1710, and token information input field 1711, which can be modified by inputting using the keyboard or other means. When the connection destination and token information are entered, the CPU 111 checks whether the connection destination is a compatible application service. At this time, if the application service of the connection destination has an API for providing service information, it queries the service. If it does not have an API for providing service information, it determines whether it is compatible based on the domain name of the URL information when it was registered using the new registration button 1507 in Figure 12.

[0093] Next, the system retrieves channel list information, including channel and user information, from the message application server 300, along with icon images that serve as identification information for each channel, which are present in the workspace corresponding to the token information entered in the token information input field 1711. At this time, the system also retrieves the icon images of each user belonging to each channel, and the icon image of the workspace corresponding to the token information entered in the token information input field 1711. Once the retrieval of the channel list information and icon images is complete, the system becomes able to select a channel in the channel selection field 1720 of the button setting registration screen 1701. The user then selects a channel from the list of channels to which they want to post the scanned image data.

[0094] Thus, on the button setting registration screen 1701, you can associate the group (workspace or channel) to which the image data will be sent with a button.

[0095] When CPU111 detects that the channel set in channel selection field 1720 has changed, it retrieves a list of mention users from the channel list information who belong to the channel set in channel selection field 1720 and who can be mentioned.

[0096] When the mention user list is retrieved from the channel list information, the user to be mentioned can be selected in the mention user selection field 1721. The user selects the user to be mentioned from the list of mention users displayed in the mention user selection field 1721. Note that the settings for the mention user selection field 1721 are optional, and if not set, the scan to chat may be executed according to the "mention on a case-by-case" screen flow shown in Figures 14 and 15. Alternatively, an option indicating "mention on a case-by-case" can be displayed in the mention user selection field 1721, and selecting this option will execute the scan to chat according to the "mention on a case-by-case" screen flow.

[0097] Furthermore, if a mention user is set in the mention user selection field 1721, Scan to Chat may be performed according to the "fixed mention" screen flow shown in Figures 14 and 15. Also, if no mention is set in the mention user selection field 1721, Scan to Chat may be performed according to the "no mention" screen flow shown in Figures 14 and 15. The "no mention" screen flow is, for example, the flow in Figures 14 and 15 where the standard text selection screen 715 is displayed after selecting the Scan to Chat button 711.

[0098] In the channel selection field 1720, multiple channels can be selected. In this case, information for multiple channels is sent to the message application server 300, and image data is posted to multiple channels. Also, if multiple channels are selected, mention users can be selected for each selected channel. Furthermore, even if only one channel is selected, multiple users belonging to that channel can be selected in the mention user selection field 1721.

[0099] The icon image display area 1730 displays an icon image according to the settings. For example, if one channel is set and multiple mentioned users are set, or if one channel is set and no mentioned users are set, the icon image of the channel set in the channel selection area 1720 will be automatically displayed. In other words, the channel icon image is selected without accepting any user input. If multiple channels are set, the workspace icon corresponding to the token information entered in the token information input area 1711 will be displayed.

[0100] When a workspace cannot be identified, the icon image for service 1712 is displayed. Note that the icon image displayed in the icon image display area 1730 will be used as the button icon when the scan-to-chat button is registered on the home screen 608.

[0101] If no icon image is registered for a channel, a predetermined image may be displayed. Furthermore, the displayed icon can be changed within the selectable range. For example, even if the icon image of the user in the mention user selection field 1721 is displayed, the icon image of service 1712 can also be displayed.

[0102] Thus, on the button setting registration screen 1701, the icon image for a button can be set by obtaining the icon image of a workspace or channel, which is the identification information of a group such as a workspace or channel, from the message application server 300. Similarly, the icon image of a mentioned user, who is the recipient of the notification, can also be obtained from the message application server 300 and used as the button's icon image.

[0103] The button name setting field 1731 contains the string that will be displayed as the button name when the Scan to Chat button is added to the home screen 608. This string is automatically set to the name corresponding to the icon image selected by the user. For example, in Figure 17, the icon image for Channel 1 is registered as the icon image and is displayed in the icon image display field 1730, so the name of the channel corresponding to that icon image, "Channel 1," is entered. If an icon image corresponding to a user is selected as the icon image, the username of that user (for example, "User 1") will be entered. Here, the names of channels and users entered are information included in the channel list information obtained from the message application server. In this way, on the button setting registration screen 1701, the name of the button can be set by obtaining the workspace name and channel name, which are identification information for groups such as workspaces and channels, from the message application server 300. Similarly, the username of the mentioned user, who is the user to be notified, can also be obtained from the message application server 300 and used as the name of the button.

[0104] The string displayed as the button name may be automatically set to the name of the channel selected in the channel selection field 1720, without requiring any user input.

[0105] The entered text can be modified later by the user, and can be deleted, added, or changed using the keyboard. The name of the button set here will be displayed as "Channel 1" on the button, as shown in the Scan to Chat button 602 on the home screen in Figure 13.

[0106] In the pre-set message mode selection field 1732, you can select the settings for the comment to be sent along with the scanned image data. For example, the pre-set message mode selection field 1732 displays "Selection Mode" as an option, which makes pre-set messages that have been set in the pre-set message settings field 1733 available to select when executing Scan to Chat. Additionally, "Fixed Mode" sends a single pre-set message that has been set in the pre-set message settings field 1733 as a fixed message, and "No Comment Mode" sends the image data without adding a comment are also displayed as options.

[0107] Additionally, scan settings can be configured on the button setting registration screen 1701. In the duplex setting section 1740, users can choose whether to scan both sides of the document or just one side. By selecting the duplex setting section 1740, users can choose between "single-sided" and "double-sided" from a dropdown menu.

[0108] Additionally, in the color settings section 1741, users can choose whether to scan the document in color or in monochrome. By selecting the color settings section 1741, users can choose between "Color" and "Monochrome" from a dropdown menu.

[0109] The user confirms the settings by pressing the settings button 1750 after making the settings on the settings registration screen 1701. The settings set here are stored in the storage 114. In the embodiment 2 described later, the above settings are stored in the HDD 405.

[0110] When you press the generate button 1506 on the settings registration screen 1501, a button to perform scan-to-chat according to the settings registered on the button settings registration screen 1701 will be added and displayed on the home screen 608.

[0111] Figure 18 shows a correspondence table listing the categories handled by the message application server 300, their names, icon images, and the sources from which MFP101 obtains icon images.

[0112] The icon image for Service A is managed by Service A, a messaging service provided by the messaging application server 300, and the MFP101 can retrieve it from the messaging application server 300. The icon image for Service B is stored within the MFP101 device.

[0113] The icon images for Organization A and Organization B are included in the management information for Service A. In other words, when MFP101 sends token information corresponding to the workspace managed by the message application server to the message application server 300, the icon image for either Organization A or Organization B is retrieved from the message application server.

[0114] The icon images for channels, groups, and users are information included in the channel list information of organization A, and are retrieved by MFP101 from the message application server 300.

[0115] Figure 19 is a flowchart showing an example of the process by which the CPU 111 of the MFP 101 acquires an icon image for displaying the scan-to-chat button 602 on the home screen 608. This flowchart is executed when the MFP 101 acquires icon information in S1007 and S1012 in Figure 7, S1307 and S1312 in Figure 9, Figures 17, 14, and 15, and when the operation unit 116 is activated and displays the home screen 608. The flow in Figure 19 is realized when the CPU 111 of the MFP 101 reads a program stored in ROM 112 into RAM 113 and executes it.

[0116] In S1901, the CPU 111 retrieves the button information registered on the screen shown in Figure 17 from the storage 114.

[0117] In S1902, the CPU 111 retrieves an icon image corresponding to target X from the message application server 300 and storage 114. Here, target X is information registered in the button information and indicates the destination. The elements that can be targets X, listed in order from the higher-level concept, are application services, workspaces, channels, and users.

[0118] In S1903, CPU 111 requests the icon image source shown in Figure 18 to obtain an icon image corresponding to target X. If the icon image is obtained, the process proceeds to S1904; otherwise, the process proceeds to S1905.

[0119] In S1904, the CPU 111 displays an icon image on the operation unit 116.

[0120] In S1905, CPU111 checks if a concept higher than target X exists. If it does, it proceeds to S1906. If it does not exist, it proceeds to S1907.

[0121] In S1906, CPU111 identifies the existing higher-level concept item as target X and proceeds to processing in S1902.

[0122] In S1907, CPU 111 retrieves a specific default icon from storage 114. In other words, S1907 is executed when an icon image does not exist for an app service, workspace, channel, or user.

[0123] This embodiment makes it easier to identify from the objects the group to which the image data generated by scanning the registered objects with the image processing device is shared. [Examples]

[0124] In Example 1, we described an example in which the MFP101 directly sends image data and posting parameters to the message application server 300. In this example, we describe an example in which the MFP101 sends image data and posting parameters to the message application server 300 via the bot server 400.

[0125] Figure 8 shows an example of a sequence in which the MFP101 scans and generates files, which are then sent to the message application server 300 via the bot server 400.

[0126] In S1101, the CPU 111 of the MFP 101 accepts the selection of the scan-to-chat button 602, which is the instruction to start a scan. If the scan-to-chat button 602 is selected and a screen appears allowing the user to select a channel, mentioned user, or pre-written message, the scan will start once that selection has been accepted.

[0127] In S1102, the CPU 111 controls the reading unit 118 to read the image of the document based on the scan settings set on the button setting registration screen 1701 in Figure 17. In S1103, the CPU 111 generates image data (file) based on the read image.

[0128] In S1104, the CPU 111 controls the communication unit 126 and sends various information to the bot server 400 in order to post image data, etc. Here, the token information registered on the button setting registration screen 1701 in Figure 17, the channel information set on the setting registration screen 1701 or on the screens in Figures 14 and 15, the user information to be mentioned, comments, etc. are sent along with the image data.

[0129] In S1105, the bot server's CPU 401 sends the received information to the message application server 300. This information is sent by executing the command "HTTP POST https: / / message.com / api / files.upload".

[0130] In S1106, the CPU 301 of the message application server 300 searches for registered workspace information and application information using the token information received in S1105, and associates the received image data and channel information with the specified channel and stores it. In other words, it controls the system to post the received image data and comments to the specified channel. Furthermore, if a mentioned user is specified, the system also associates the received image data with the channel and the user to whom the post is intended and stores it. As a result, when a user launches the message application on their mobile device 200 and selects a channel to check the content of the conversation in the aforementioned channel, a screen showing the posted received image data is displayed.

[0131] In S1107, the CPU 301 of the message application server 300 sends a result corresponding to whether the post was successful or not as HTTP communication response information to the bot server 400.

[0132] In S1108, the CPU 401 of the bot server 400 sends the result received in S1107 to the MFP 101. If the post is successful, the CPU 111 of the MFP 101 may display a notification on the operation unit 116 indicating that the post was successful. If the post fails, the CPU 111 of the MFP 101 may also display a notification on the operation unit 116 indicating that the post failed. Alternatively, no notification may be displayed when the post is successful, and a notification indicating that the post failed may only be displayed when it fails.

[0133] Figure 16 shows an example of the mapping between ID and token information. In the table in Figure 16, the user ID or device ID is registered in association with the authentication information (token information). This table is stored on the HDD 405 of the bot server 400. Here, the user ID and device ID are information stored in the MFP 101. The user ID is the user identification information set for each user using the MFP 101. The device ID is the device identification information set for each MFP. The user ID is the identification information set by the user when creating a user account to log in to the MFP 101, and the device ID is the MFP 101-specific identification information set at the factory.

[0134] The token information in Figure 16 is used when performing a scan-to-chat without selecting the scan-to-chat button 602.

[0135] Figure 9 is a flowchart showing an example of the processing that occurs when the scan-to-chat button 602 is selected in this embodiment. In this embodiment, each operation (step) in the flowchart is performed by the CPU 111 reading the control program recorded in the ROM 112 or storage 114 into the RAM 113 and executing it. The parts of the flowchart in Figure 9 that perform the same processing as in Figure 7 will be omitted from the explanation.

[0136] S1301 is the same process as S1001 in Figure 7.

[0137] In S1302, CPU 111 sends information to bot server 400 indicating a request for channel list information. At the same time, it sends pre-registered token information 1503 to the bot server. As a result, CPU 401 of bot server 400 sends the received token information and information indicating a request for channel list information to message application server 300.

[0138] In S1303, the CPU 111 determines whether it has received channel list information from the message application server 300 in response to the channel list information acquisition request sent in S1302. Specifically, it determines whether the bot server 400 has received channel list information from the message application server 300, and whether the MFP 101 has received channel list information from the bot server 400. It also determines that channel list information has not been received if the status code in the HTTP communication response is an error, or if the response body contains parameters indicating that the information could not be acquired.

[0139] S1304 to S1306 are the same processes as S1004 to S1005 in Figure 7.

[0140] In S1307, CPU 111 sends a request for icon information for other channels in the target workspace to bot server 400, which then sends it to message application server 300. As a result, MFP 101 obtains icon information for other channels in the target workspace from message application server 300 via bot server 400.

[0141] Steps S1308 to S1311 are the same as steps S1008 to S1011 in Figure 7.

[0142] In S1312, CPU 111 obtains the icon information of users belonging to the target channel from the message application server 300 via the bot server 400, as described above.

[0143] Steps S1313 to S1318 are the same as steps S1013 to S1018 in Figure 7.

[0144] In S1319, CPU 111 sends the pre-registered token information 1503, the file generated in S1317 and S1318, and posting parameters to bot server 400. Then, bot server 400 sends the token information 1503, the file generated in S1317 and S1318, and posting parameters to message application server 300 using the HTTP POST method. By sending this data (the converted image data file and posting parameters) to message application server 300, message application server 300 controls the posting of the received file to the user indicated by the received mention information in the channel indicated by the received channel information.

[0145] In S1320, the CPU 111 receives the posting results from the message application server 300 via the bot server 400 and displays them on the touch panel 601 of the operation unit 116.

[0146] In this embodiment, it is assumed that only one token is registered. However, if multiple tokens are registered, the processes involving the token information, such as S1302, S1303, and S1319, will be executed for each registered token.

[0147] This embodiment makes it possible to update the bot server program without uploading the MFP101 program, even if the interface specifications of the message application server 300 are changed. Furthermore, in workplaces with multiple MFPs, file posting can be performed without individually configuring tokens for each MFP.

[0148] <Other embodiments> The present invention provides 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. It can also be implemented by a process in which one or more processors in the computer of the system or device read and execute the program. Furthermore, it can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions. [Explanation of Symbols]

[0149] 101 MFP 300 Message App Servers 400 bot servers 111 CPU 118 Reading Unit

Claims

1. A program executed by a scanning device, A first display step involves displaying multiple groups of chat services on the display unit of the scanning device, A first reception step that accepts the user's selection of a group from the multiple groups displayed, A second display step involves displaying a plurality of channels included in the selected group on the display unit, A second reception step which accepts the user's selection of a channel from the multiple channels displayed above, The scanning device is instructed to perform a third receiving step, which involves receiving the operation of a key to receive the execution instruction displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are performed by the scanning device based on a single key operation received in the third reception step while the channel is selected. A program characterized in that the image data transmitted by executing the transmission process based on a single key operation is stored in association with the selected channel.

2. The program according to claim 1, characterized in that the scanning device further causes the scanning device to perform a third display step of displaying the aforementioned key on the display unit.

3. The program according to claim 1 or 2, characterized in that, upon execution of the transmission process, the image data and the information of the selected channel are transmitted to the server, and the image data is stored in association with the selected channel.

4. The scanning device is further instructed to perform a fourth acceptance step of accepting scan settings, The program according to any one of claims 1 to 3, characterized in that, in the scanning process, a document is scanned based on the scan settings and image data is generated.

5. The program according to claim 4, characterized in that the scan setting is a setting to scan both sides of the document or scan one side of the document.

6. The program according to claim 4, characterized in that the scan setting is a setting to either scan the document in color or scan the document in monochrome.

7. The program according to any one of claims 1 to 6, characterized in that the scanning device further performs a printing process of printing an image onto paper.

8. The scanning device is further instructed to perform a receiving step of receiving information from the aforementioned multiple channels. The program according to any one of claims 1 to 7, characterized in that in the second display step, the plurality of channels are displayed based on the information of the received channels.

9. The scanning device is further instructed to perform a transmission process to transmit token information. The program according to claim 8, characterized in that the receiving step receives information from the plurality of channels based on the transmitted token information.

10. The program according to any one of claims 1 to 9, characterized in that the image data is transmitted via HTTP communication during the transmission process.

11. The program according to any one of claims 1 to 10, characterized in that the scanning device further performs an execution step of performing the scanning process and the transmission process.

12. The scanning device is further instructed to perform a fifth reception step in which it receives a file name from the user before receiving a single key operation in the third reception step, The program according to any one of claims 1 to 11, characterized in that the transmission process transmits the image data having the received file name.

13. The scanning device is further instructed to perform an acquisition step to acquire an icon image corresponding to the group, The program according to any one of claims 1 to 12, characterized in that the acquired icon image and the group are displayed in the first display step.

14. The program according to any one of claims 1 to 13, characterized in that a button different from the scan function button for sending scanned and generated image data by email is selected, and when a button for a function different from the scan function is selected, a plurality of groups of the chat service are displayed in the first display step.

15. The program according to any one of claims 1 to 14, characterized in that when the key is operated once while the channel is selected, the transmission process is executed following the scan process.

16. In the first display step, a first screen in which the plurality of groups are displayed is shown. The program according to any one of claims 1 to 15, characterized in that in the second display step, after the group is selected via the first screen, a second screen displaying the plurality of channels is displayed.

17. A third screen, which is different from the first screen and the second screen and capable of accepting scan settings, is displayed on the display unit. The program according to claim 16, characterized in that, in the scanning process, the document is scanned and image data is generated based on the scan settings received on the third screen.

18. The program according to claim 16, characterized in that the key is displayed on a screen different from the first screen and the second screen.

19. A scanning device having a display unit, The display unit includes a first display means for displaying multiple groups of chat services, A first reception means that accepts a user's selection of a group from the multiple groups displayed, The display unit includes a second display means for displaying a plurality of channels included in the selected group, A second receiving means that accepts the user's selection of a channel from the multiple channels displayed, It has a third receiving means for receiving key operations for receiving execution instructions displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are executed based on a single key operation received by the third receiving means while the channel is selected. A scanning device characterized in that the image data transmitted by executing the transmission process based on a single key operation is stored in association with the selected channel.

20. The scanning device according to claim 19, further comprising a third display means for displaying the aforementioned keys on the display unit.

21. The scanning device according to claim 19 or 20, characterized in that, when the transmission process is executed, the image data and the information of the selected channel are transmitted to the server, and the image data is stored in association with the selected channel.

22. It further has a fourth means of receiving scan settings, The scanning apparatus according to any one of claims 19 to 21, characterized in that the scanning process scans a document based on the scan settings and generates image data.

23. The scanning device according to claim 22, characterized in that the scan setting is a setting to scan both sides of the document or scan one side of the document.

24. The scanning device according to claim 22, characterized in that the scan setting is a setting to either scan the document in color or scan the document in monochrome.

25. The scanning device according to any one of claims 19 to 24, further comprising a printing means for printing an image onto paper.

26. The system further includes receiving means for receiving information from the aforementioned multiple channels, The scanning device according to any one of claims 19 to 25, characterized in that the second display means displays the plurality of channels based on the information of the received channels.

27. It further has a means for transmitting token information, The scanning device according to claim 26, wherein the receiving means receives information of the plurality of channels based on the transmitted token information.

28. The scanning device according to any one of claims 19 to 27, characterized in that the image data is transmitted via HTTP communication during the transmission process.

29. The scanning device according to any one of claims 19 to 28, further comprising execution means for performing the scanning process and the transmission process.

30. The third receiving means further includes a fifth receiving means that receives a file name from the user before the third receiving means receives one operation of the key, The scanning device according to any one of claims 19 to 29, characterized in that the image data having the received file name is transmitted during the transmission process.

31. The system further includes an acquisition means for acquiring an icon image corresponding to the aforementioned group, The scanning device according to any one of claims 19 to 30, characterized in that the first display means displays the acquired icon image and the group.

32. The scanning device according to any one of claims 19 to 31, wherein the first display means displays a plurality of groups of the chat service when a button for a function other than the scanning function is selected, which is different from the button for the scanning function that sends the scanned and generated image data by email.

33. The scanning device according to any one of claims 19 to 32, characterized in that when the key is operated once while the channel is selected, the transmission process is executed following the scanning process.

34. The first display means displays a first screen on which the plurality of groups are displayed, The scanning apparatus according to any one of claims 19 to 33, characterized in that the second display means displays a second screen in which the plurality of channels are displayed after the group has been selected via the first screen.

35. A third screen, which is different from the first screen and the second screen and capable of accepting scan settings, is displayed on the display unit. The scanning device according to claim 34, characterized in that, in the scanning process, the document is scanned based on the scan settings received on the third screen and image data is generated.

36. The scanning device according to claim 34, characterized in that the key is displayed on a screen different from the first screen and the second screen.

37. A method for controlling a scanning device, A first display step involves displaying multiple groups of chat services on the display unit of the scanning device, A first reception step that accepts the user's selection of a group from the multiple groups displayed, A second display step involves displaying a plurality of channels included in the selected group on the display unit, A second reception step which accepts the user's selection of a channel from the multiple channels displayed above, It includes a third receiving step that receives the operation of a key to receive the execution instruction displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are performed by the scanning device based on a single key operation received in the third reception step while the channel is selected. A control method characterized in that the image data transmitted by executing the transmission process based on a single key operation is stored in association with the selected channel.

Images