Program, scanning device, and scanning 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] The present invention relates to a program, an image processing device, and an image transmission method. [Background technology]

[0002] Patent Document 1 discloses an image processing device that displays the title and icon of an acquired application as an object, in order to make it easy to understand which application's object is an object for executing the application. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-133000 A Summary of the Invention [Problem to be solved by the invention]

[0004] When a user uses a chat service available on the Internet to share scanned image data in a specific chat room on the chat service, the following problems arise: For example, it is conceivable to associate an object with information about the specific chat room (group information) in which the image data will be shared and store the information, and then operate the object to send the image data to the specific chat room.

[0005] In this case, as in Patent Document 1, the display of the application title and icon alone makes it possible to determine which chat service the object belongs to, but it is not easy to determine which group the object is for sharing image data with.

[0006] In particular, in order to share image data in multiple talk rooms, multiple objects may be registered for each talk room, making it difficult for users to easily determine which object is for which talk room.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a mechanism that makes it possible to easily determine from a registered object the group with which image data is shared by selecting the object. [Means for solving the problem]

[0008] The program of the present invention is characterized in that it causes an image processing device that scans a document to generate image data and transmits the generated image data to execute a first display step of displaying multiple groups of a chat service, an acceptance step of accepting a user's selection of a group from the displayed multiple groups, and a second display step of displaying channels included in the selected group, and causes the image processing device to execute an execution step of scanning the document to generate the image data and transmitting the generated image data by inputting a single execution instruction after the user selects a channel from the displayed channels. [Effects of the Invention]

[0009] By selecting a registered object, it is possible to provide a mechanism that allows a group with which image data is shared to be easily identified from the object. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of the present invention. [Figure 2] A diagram showing an example of the hardware configuration of the MFP101 [Figure 3] FIG. 2 is a diagram showing an example of the hardware configuration of a mobile terminal 200. [Figure 4]FIG. 1 is a diagram illustrating an example of a hardware configuration of a message application server 300. [Figure 5] FIG. 1 shows an example of the hardware configuration of a bot server 400. [Figure 6] FIG. 10 shows an example of a sequence in which the MFP 101 transmits a file generated by scanning to the message application server 300. [Figure 7] A flowchart showing an example of scan-to-chat processing executed by the MFP 101. [Figure 8] FIG. 10 shows an example of a sequence in which a file generated by scanning by the MFP 101 is transmitted to the message application server 300 via the bot server 400. [Figure 9] Flowchart showing an example of scan-to-chat processing [Figure 10] A diagram showing an example of the file structure in the Message App server [Figure 11] A diagram showing an example of a message screen in a messaging app [Figure 12] FIG. 10 is a diagram showing an example of a setting registration screen. [Figure 13] FIG. 10 shows an example of a home screen displayed on an operation unit 116 of the MFP 101. [Figure 14] An example of the screen transition for scan-to-chat processing [Figure 15] An example of the screen transition for scan-to-chat processing [Figure 16] A diagram showing an example of association between ID and token information [Figure 17] FIG. 10 is a diagram showing an example of a button setting registration screen. [Figure 18] Diagram showing message service elements and their corresponding icons [Figure 19] Flowchart showing the process for obtaining an icon DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the configurations shown in the following embodiments are merely examples, and the present invention is not limited to the configurations shown in the drawings. [Example]

[0012] FIG. 1 is a diagram illustrating an example of a system configuration of the present invention. The system configuration of this embodiment includes an MFP (Multi Function Peripheral) 101, which is an image processing device capable of communicating with a mobile terminal 200, which is an example of a terminal device, via a network 100, and a message app server 300. A bot server 400 is also connected via the network 100 and is capable of communication. The message app 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 that displays the messages and image data on the mobile terminal 200 or a PC (not shown) in response to a user operation. The bot server 400 associates the MFP 101 with information (token information) corresponding to a bot app installed in the message app server 300 connected to the MFP 101, and forwards a request from the MFP 101 to the message app server 300. The network 100 in this embodiment may be the Internet or a local area network (LAN). The network 100 may be wired or wireless.

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

[0014] The control unit 110, including the CPU 111, controls the overall operation of the MFP 101. The CPU 111 loads a control program stored in the ROM 112 or the storage 114 into the RAM 113 to perform various control operations, such as scanning control and printing control. The ROM 112 stores control programs executable by the CPU 111. The ROM 112 also stores a boot program, font data, and the like. The RAM 113 is a main memory and is used as a work area and a temporary storage area for expanding the various control programs stored in the ROM 112 and the storage 114. The storage 114 stores image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 114, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may also be used. An eMMC (Embedded Multi Media Card) may also be used.

[0015] In the MFP 101 of this embodiment, one CPU 111 executes each process shown in the flowcharts described below using one memory (RAM 113), but this is not limited to this. For example, each process shown in the flowcharts described below can be executed by using multiple CPUs, RAMs, ROMs, and storages in cooperation with each other. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0016] The operation unit I / F 115 connects the control unit 110 to an operation unit 116 including a display unit such as a touch panel and hard keys. The operation unit 116 displays information to the user and detects inputs from the user.

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

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

[0019] The wireless communication unit I / F 121 is an I / F for controlling the wireless communication unit 122, and connects the control unit 110 to an external wireless device (here, the mobile terminal 200) via wireless communication.

[0020] The control unit 110 is connected to the public line network 107 by controlling a FAX communication unit 124 such as a facsimile via a FAX unit I / F 123. The FAX unit I / F 123 is an I / F for controlling the FAX communication unit 124, and by controlling a modem and NCU for facsimile communication, it is possible to connect to the public line network, control the facsimile communication protocol, and the like.

[0021] The communication unit I / F 125 connects the control unit 110 to the network 100. The communication unit I / F 125 allows the communication unit 126 to transmit image data and various internal device 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. Methods for transmitting and receiving data via the network 100 include transmission and reception using email and file transmission using other protocols (e.g., FTP, SMB, WEBDAV, etc.). Furthermore, image data and various setting data can be transmitted and received over the network 100 by accessing via HTTP communication from the mobile terminal 200, the message application server 300, and the bot server 400.

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

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

[0024] The operation panel 201 has a touch panel function capable of detecting a user's touch operation, and displays various screens provided by the OS and email sending application. The operation 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 inputting a touch operation to the operation panel 201. The mobile terminal 200 is also 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 an image in response to an image capture instruction from the user. The photograph taken by camera 204 is stored in a predetermined area of ​​HDD 210. It is also possible to obtain information from a QR code read by camera 204 using a program capable of analyzing QR codes (registered trademark).

[0026] Mobile terminal 200 can exchange data with various peripheral devices via NFC communication unit 205, Bluetooth (registered trademark) communication unit 206, and wireless LAN communication unit 211. Bluetooth communication unit 206 of mobile terminal 200 may be compatible with Bluetooth (registered trademark) Low Energy. Such terminals are beginning to become widespread.

[0027] FIG. 4 is a diagram showing an example of the hardware configuration of the message application server 300. The CPU 301 reads out a control program stored in the ROM 302 and executes various processes for controlling the operation of the message application server 300. The ROM 302 stores the control program. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. 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 (registered trademark) or wireless communication such as Wi-Fi.

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

[0029] 13 is a diagram showing an example of a home screen displayed on operation unit 116 of MFP 101. Operation unit 116 is made up of touch panel 601 that displays the operation screen, and LEDs 610 and 611. Touch panel 601 is an instruction means, and functions both as an acceptance means that accepts instructions from the user and as a display means that displays the screen. The user directly touches the screen displayed on touch panel 601 with a finger, a stylus, or other object to instruct the execution of each function based on the displayed screen.

[0030] 13 displays a home screen 608. The home screen 608 is the first screen for instructing the execution of each function of the MFP 101, and is a screen for selecting a screen display for making various settings for each function executed by the MFP 101, such as copy, fax, scan, and media print.

[0031] A status check button 605 is an object for displaying a screen (status check screen) for checking the status of the MFP 101. A transmission history and job execution history can be displayed from the status check screen (not shown).

[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, a predetermined screen shown in Fig. 14 or 15 is displayed on the operation unit 116 according to the setting information of the button. The scan-to-chat process will be described in detail with reference to Figs. 6 and 7. The scan-to-chat button 602 can be registered on the button setting registration screen 1701 in Fig. 17.

[0033] Furthermore, the user can register another scan-to-chat button 609 on the button setting registration screen 1701 in FIG.

[0034] The scan button 603 is an object for displaying a scan selection screen (not shown). The scan selection screen is a screen for selecting a transmission function, such as email transmission (Email), file transmission via SMB, FTP, or HTTP, or Internet fax (I-fax) transmission. Touching the object representing the displayed transmission function displays a setting screen for each transmission function.

[0035] An address book button 604 is an object for displaying an address book screen of the MFP 101 when selected by the user. LEDs 610 and 611 notify the user of the status of the MFP 101. The LED 610 lights up while an e-mail or a print job is being received or executed, and the LED 611 lights up when an error occurs in the MFP 101. The stop button 606 is an object for canceling various operations and is an object that is always displayed on the operation unit 116. The HOME button 607 is an object for displaying a home screen 608 and is an object that is always displayed on the operation unit 116. The menu button 612 is an object for displaying a screen for setting the environment, such as the language used, and for setting each function.

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

[0037] In S901, the CPU 111 of the MFP 101 accepts the selection of the scan-to-chat button 602, which is an instruction to start scanning. Note that if the selection of the scan-to-chat button 602 causes a screen to be displayed that accepts the selection of a channel, a mention user, or a fixed phrase, scanning is started by accepting the selection. Details will be described in the screen flows of FIGS. 14 and 15.

[0038] In S902, the CPU 111 controls the reading unit 118 to read an image of the document based on the scan settings set on a button setting registration screen 1701 in Fig. 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 to execute a transmission process for posting image data to the message app server 300 via HTTP communication. Here, the token information registered on the button setting registration screen 1701 in Fig. 17, the channel information set on the setting registration screen 1701 or the screens in Figs. 14 and 15, the user information of the mention target, comments, etc. are transmitted together with the image data. In addition, the above information is transmitted by executing the command "HTTP POST https: / / message.com / api / files.upload".

[0040] Here, the token information is information corresponding to a bot app installed in the message app server 300, and is information that can uniquely identify the bot app. Note that this bot app is information corresponding to a workspace registered in the message app server 300, and is information that can uniquely identify the workspace. In other words, the token information is information corresponding to a workspace registered in the message app server 300, and is information that can uniquely identify the workspace.

[0041] Here, a workspace is like an organization or group to which multiple users belong within a messaging app. Also, a channel is like a chat room within a workspace. The chat room here is a mechanism by which multiple users participating in the chat room can send and receive messages with each other and interact like a conversation. Also, in this embodiment, a channel is described as a chat room, but it is not limited to this as long as it is a mechanism by which multiple users can send and receive messages and interact like a conversation. For example, it may be something like a group chat, room, talk room, or group.

[0042] Here, the bot app is an application for registering the MFP 101 as a user in a message app and posting messages and image data, and is installed in the message app server 300. By specifying a bot app and sending image data to the message app server 300, the bot app posts the sent image data in the message app. Furthermore, the HDD 305 of the message app server 300 stores bot apps and token information in association with each other, and also associates bot apps with workspaces. Therefore, by receiving token information from the MFP 101, the message app server 300 can return information about the workspace associated with the bot app associated with the token information. Note that the token information, bot app, and workspace may also be directly associated with each other. This allows a workspace (a workspace to which the user wants to send image data) corresponding to pre-registered token information to be selected from a large number of workspaces.

[0043] In S905, the CPU 301 of the message app server 300 searches for registered workspace information and app information using the token information received in S904, and associates the received image data and channel information with the specified channel and stores them. That is, the CPU 301 controls the posting of the received image data and comment to the specified channel. Furthermore, if a mention user is specified, the CPU 301 also associates the received image data with the channel and the user to whom the post is to be made and stores them. As a result, when the user starts the message app on the mobile terminal 200 and specifies a channel to check the content of the conversation on the channel, a screen on which the received image data has been posted is displayed.

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

[0045] Fig. 7 is a flowchart showing an example of scan-to-chat processing executed by MFP 101. The processing of the flowchart in Fig. 7 is executed by CPU 111 reading a program stored in ROM 112 into RAM 113 and executing it. The flow in Fig. 7 starts when MFP 101 is powered on. Note that the flow in Fig. 7 is based on the premise that the service, token information, and channel have been set on button setting registration screen 1701 in Fig. 17.

[0046] In S1001, the CPU 111 determines whether or not the scan-to-chat button 602 has been selected. If it is determined that the scan-to-chat button 602 has been selected, the process proceeds to S1002. If not, the process returns to S1001.

[0047] In S1002, the CPU 111 executes a process of transmitting, to the message application server 300, information indicating a request for channel list information by HTTP communication, using the token information 1503 registered in advance.

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

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

[0050] In S1005, the CPU 111 displays on the operation unit 116 information indicating that the channel list information could not be received.

[0051] In S1006, the CPU 111 determines whether or not the back button has been selected. If it is determined that the back button has been selected, the process returns to S1001. If not, the process returns to S1006.

[0052] In S1007, the CPU 111 requests icon information of other channels in the target workspace from the message application server 300 and acquires it.

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

[0054] In S1009, the CPU 111 determines whether or not a channel has been selected. If it is determined that a channel has been selected, the process proceeds to S1010. If not, the process returns to S1009.

[0055] In S1010, the CPU 111 determines whether the scan to chat operation is in the mention-each-time mode. If it is in the mention-each-time mode, the process proceeds to S1012; if not, the process proceeds to S1011.

[0056] In S1011, the CPU 111 determines from the received channel list information whether or not the user set as the user to be mentioned in the mention user selection field 1721 exists in the channel to which the posting is made. If it is determined that the user to be mentioned exists in the channel, the process proceeds to S1015; otherwise, the process proceeds to S1012.

[0057] In S1012, the CPU 111 acquires, from the message application server 300, icon information of users who belong to the target channel.

[0058] 14 on the touch panel 601 of the operation unit 116. After selecting the user to be mentioned in S1013, a prompt may be displayed to select whether or not to register the selected user as a user to be mentioned in a fixed mention.

[0059] In S1014, the CPU 111 determines whether or not a destination mention has been selected. If it is determined that a destination mention has been selected, the process proceeds to S1015. If not, the process returns to S1014.

[0060] 15 on the operation unit 116. If it is detected in S1015 that all settings of the mention target user to be set in scan to chat and the settings of the comment selection screen have been finalized, the process proceeds to S1016.

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

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

[0063] In S1018, the CPU 111 generates posting parameters. The posting parameters include channel information of the posting destination, a file name, mention information, and a posted comment. The file format is set to the file format set in the transmission settings. The file name is specified as the file name specified in the transmission settings.

[0064] In S1019, the CPU 111 uses the POST method of HTTP communication to transmit the token information 1503 registered in advance, the file generated in S1017 and S1018, and the posting parameters to the message application server 300. Note that the token information 1503 is the token information entered in the token information input field 1711 in FIG. 17.

[0065] By transmitting this data (files converted from image data and posting parameters) to the message app server 300, the message app server 300 executes the following process: This process controls so that the received file is posted to the user indicated by the received mention information on the channel indicated by the received 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. According to this embodiment, the user can easily post a file from the MFP 101 to a channel of the message application server.

[0067] In this embodiment, only one piece of token information is registered, but if multiple pieces of token information are registered, processes related to the token information, such as S1002, S1003, and S1019, are executed for each registered token.

[0068] An example of a screen displayed on the operation panel 201 of the mobile terminal 200 as a result of the file converted from the image data and the posting parameters being sent to the message application server 300 in the process of S1019 will be described later with reference to FIG.

[0069] 14 and 15 are diagrams showing an example of screen transitions during scan-to-chat processing. The screens in Fig. 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 of the button that is displayed varies depending on the settings of the scan-to-chat button. When only the application service information of the destination is registered, a scan-to-chat button 708 is displayed on the home screen 704.

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

[0072] When an organization is selected on the organization selection screen 712 and the OK button is selected, a channel selection screen 713 is displayed for selecting a destination (posting destination) channel from the channels included in the selected organization.

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

[0074] When a mention user is selected on the mention user selection screen 714 and the OK button is selected, a fixed phrase selection screen 715, a destination confirmation screen 716, or a sending screen 717 is displayed. If the user has turned on the fixed phrase selection setting, the fixed phrase selection screen 715 is displayed and accepts the selection of a sentence to be displayed together with image data. When a fixed phrase is selected on the fixed phrase selection screen 715 and the OK button is selected, a destination confirmation screen 716 is displayed. The destination confirmation screen 716 displays the username of the mention user and the fixed phrase to be posted as a destination mention, allowing the user to confirm the posted content. Furthermore, when the user has turned off the fixed phrase selection setting and turned on the destination confirmation setting, the destination confirmation screen 716 is displayed when 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 destination confirmation screen 716, the document is scanned, the image data generated by the scan is sent, and a sending screen 717 is displayed. The sending screen may be displayed while the document is being scanned, or may be displayed after the document has been scanned and the transmission of the image data has begun. Alternatively, the document is scanned when the user sets the template selection setting and destination confirmation setting to OFF, selects a mention user on the mention user selection screen 714, and presses the OK button. The image data generated by the scan is then sent, and the sending screen 717 is displayed. The sending screen 717 may be displayed while the scan is in progress, or after the scan has finished and transmission is in progress.

[0076] If the organization of the destination is also registered in the scan-to-chat button, a scan-to-chat button 709 is displayed on the home screen 705 .

[0077] Selecting the scan to chat button 709 displays a channel selection screen 713. If the organization registered in association with the scan to chat button does not exist on the registered service, an organization selection screen 712 is displayed to accept the selection of an organization.

[0078] If the destination channel is also registered in the scan to chat button, a scan to chat button 710 is displayed on the home screen 706 .

[0079] Selecting the scan to chat button 710 displays a mention user selection screen 714. If the channel registered in association with the scan to chat button does not exist on the registered service, a channel selection screen 713 is displayed to accept channel selection.

[0080] If a mention user is also registered in the scan-to-chat button, a scan-to-chat button 711 is displayed on the home screen 707 .

[0081] Selecting the scan-to-chat button 711 displays a fixed phrase selection screen 715. If a mention user registered in association with the scan-to-chat button does not exist on the registered service or if the mention-each-time mode is set for the scan-to-chat button, a mention user selection screen 714 is displayed to accept the selection of a mention user.

[0082] Furthermore, when the scan-to-chat button is selected, the organization, channel, and mention user registered in the scan-to-chat button acquires the latest information (channel list information, etc.) from the message app server 300, and determines whether the acquired information includes the information registered in association with the button. This realizes the above processing.

[0083] Furthermore, when information registered in association with a button does not exist on the service, that is, when there is information that is not included in the information obtained from the message app server 300, an update screen 718 is displayed. When the YES button is selected on this update screen 718, the information that is not present on the service and therefore the selection by the user is accepted is registered in association with the selected button. When the NO button is selected, the information is not registered in association with the button. When the YES or NO button is selected, a fixed phrase selection screen 715 is displayed.

[0084] In this embodiment, if the destination (posting destination) channel is set in the scan-to-chat button, even if a mention user is not set, it is not necessary to display the mention user selection screen 714, the fixed phrase selection screen 715, or the destination confirmation screen 716. In other words, a configuration may be adopted in which, when the scan-to-chat button is selected, scanning of the document is started and the generated image data is sent.

[0085] Fig. 11 is a diagram showing an example of a message screen of a message app. A message screen 1201 in Fig. 11 is displayed when the message app is launched on the mobile terminal 200 and the processing of S1019 is executed on the MFP 101. The mobile terminal 200 is in communication with the message app server 300.

[0086] When a user starts the message application on the mobile terminal 200 and logs in by entering the ID and password of the user's account, a screen dedicated to that user is displayed.

[0087] Message 1204 is a message that is displayed (posted) by a user with a User 1 account using MFP 101 to send image data generated by scanning and posting parameters to message app server 300. The example in FIG. 11 shows an example in which "Channel 1" is specified as the posting destination channel in the posting parameters, and "User 3" belonging to Channel 1 is specified as the mentioned user. Also, "document.pdf" is specified as the file name in the posting parameters, and "Send." is specified as the comment. The file name and comment are specified by the user on a scan-to-chat advanced settings screen (not shown).

[0088] The message screen 1201 also displays the names and icons of the channels (1208), groups (1209), and users (1210) that the logged-in user is participating in. The icon (1205) of the logged-in message app is also displayed, and for the logged-in workspace (organization), the workspace name and icon are displayed (1206). Also, posting destination information (1202) and message exchanges are displayed (1203). When posting, by adding a comment with "@" before the user name, the poster can indicate that they want to notify a specific user in the channel (1204).

[0089] In the example shown in FIG. 11, the message app notifies User 3's mobile device that the 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 using an icon notification function, vibration, or ringtone. If User 3's mobile device 200 is a desktop device, the user is notified using a desktop notification function or other means. Furthermore, when displaying this screen, the message app server 300 searches for and displays the necessary information from the data structure shown in FIG. 10. For example, the message 1204 post corresponds to "Message 3 + File 1" in the exchange content 505. Attribute information such as the name of File 1 is obtained from 504 and displayed as a file icon on the message. When the user selects this file icon, File 1, which belongs to File 504, can be obtained. Note that although the files posted to this channel are displayed as icons here, a preview image of the file may also be displayed.

[0090] FIG. 10 shows an example of a file structure in the message app server. This file structure is stored in the HDD 305 of the message app server 300, and the screen in FIG. 11 is displayed based on this file structure. The message app server 300 manages data by dividing it into smaller groups, such as channels, groups, users, and files, within the largest group known as a workspace. Channel 501 is a chat room that all members of the workspace can participate in, and all posted content can be searched by anyone. Group 502 is a channel for discussions that should not be open to all members and requires an invitation to view and participate. User 503 is a user participating in this workspace. File 504 stores attached files. Furthermore, content 505 of exchanges between channels, groups, and users is stored in association with each other. For example, Channel 1 stores users participating in Channel 1 in association with each other, and messages and image data exchanged on Channel 1 are also stored in association with Channel 1. This storage allows users corresponding to the specified channel information to be displayed when a channel is selected on the channel selection screen 713. Users participating in that channel can be displayed.

[0091] 17 is a diagram showing an example of a button setting registration screen 1701. The setting registration screen 1701 is a screen displayed on the operation unit 116 of the MFP 101. Note that 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] 17, a button setting registration screen 1701 displays a service 1712, a connection destination input field 1710, and a token information input field 1711, which can be changed by inputting information using a keyboard or the like. When the connection destination and token information are input, 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, an inquiry is made to the service. If the application service does not have an API for providing service information, it is determined that the service is compatible based on the domain name in the URL information registered using the new registration button 1507 in FIG. 12.

[0093] Next, channel list information including information on channels and users existing in the workspace corresponding to the token information input in the token information input field 1711, and icon images that are identification information for each channel are acquired from the message app server 300. At this time, icon images of each user belonging to each channel and an icon image of the workspace corresponding to the token information input in the token information input field 1711 are also acquired. Once acquisition of the channel list information and icon images is complete, it becomes possible to select a channel in the channel selection field 1720 on the button setting registration screen 1701. The user selects a channel to post the scanned image data from the list of channels.

[0094] In this way, on the button setting registration screen 1701, a group (workspace or channel) to which image data is to be sent can be set in association with a button.

[0095] When the CPU 111 detects that the channel set in the channel selection field 1720 has been changed, it acquires from the channel list information a mention user list of users who belong to the channel set in the channel selection field 1720 and who can specify a mention.

[0096] When the mention user list is acquired from the channel list information, it becomes possible to select a user to be mentioned in the mention user selection field 1721. The user selects a user to be mentioned from the list of mention users displayed in the mention user selection field 1721. Note that it is possible to omit setting the mention user selection field 1721, and if no setting is made, scan to chat may be performed according to the "mention each time" screen flow shown in Figures 14 and 15. Alternatively, an option indicating a mention each time may be displayed in the mention user selection field 1721, and scan to chat may be performed according to the "mention each time" screen flow by selecting an option indicating a mention each time.

[0097] Furthermore, if a mention user is set in the mention user selection field 1721, scan to chat may be performed according to the "static mention" screen flow shown in Figures 14 and 15. Furthermore, 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 fixed phrase selection screen 715 is displayed after the scan to chat button 711 is selected.

[0098] In the channel selection field 1720, multiple channels can also be selected. In this case, multiple channel information is sent to the message app server 300, and image data is posted to multiple channels. Furthermore, when 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] An icon image is displayed in the icon image display field 1730 according to the settings. For example, if one channel is set and multiple mention users are set, or if one channel is set and no mention users are set, the icon image of the channel set in the channel selection field 1720 is automatically displayed. In other words, the channel icon image is selected without receiving any user operation. If multiple channels are set, a workspace icon corresponding to the token information entered in the token information input field 1711 is displayed.

[0100] When the workspace cannot be identified, the icon image of the service 1712 is displayed. The icon image displayed in the icon image display field 1730 is displayed as the icon image of the button when a scan-to-chat button is registered on the home screen 608.

[0101] If an icon image is not registered for a channel, a predetermined image may be displayed. The icon to be displayed may be changed within a 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 the service 1712 may be displayed.

[0102] In this way, on the button setting registration screen 1701, the icon image of the button can be set by acquiring the icon image of a workspace, channel, etc., which is identification information of a group such as a workspace or channel, from the message app server 300. Similarly, the icon image of the mentioned user, who is the notification destination user, can also be acquired from the message app server 300 and used as the icon image of the button.

[0103] A character string to be displayed as the name of the button when a scan-to-chat button is added to the home screen 608 is entered in the button name setting field 1731. This character string is automatically set as a name corresponding to the icon image selected by the user as the icon image. For example, in FIG. 17, the icon image of channel 1 is registered as the icon image and is displayed in the icon image display field 1730, so the channel name "Channel 1" corresponding to that icon image is entered. When an icon image corresponding to a user is selected as the icon image, the user name of that user (for example, "User 1") is entered. Here, the names of the channel, user, etc. to be input are information included in the channel list information acquired from the message app server. In this way, on the button setting registration screen 1701, the name of the button can be set by acquiring the workspace name or channel name, which is identification information of a group such as a workspace or channel, from the message app server 300. Similarly, the username of the mentioned user, who is the notification destination user, can also be acquired from the message app server 300 and used as the button name.

[0104] The character string displayed as the name of the button may be automatically set to the name of the channel selected in the channel selection field 1720 without receiving any operation from the user.

[0105] The entered character string can be changed later by the user at will, and character strings can be deleted, added, or changed using a keyboard, etc. The name of the button set here is displayed as "Channel 1" on the button, such as the scan to chat button 602 displayed on the home screen in Figure 13.

[0106] In the fixed phrase mode selection field 1732, it is possible to select the setting of a comment to be sent along with the scanned image data. For example, the fixed phrase mode selection field 1732 displays as an option a "selection mode" that allows a fixed phrase previously set in the fixed phrase setting field 1733 to be selected when executing scan to chat. Also displayed as options are a "fixed mode" that sends a fixed fixed phrase previously set in the fixed phrase setting field 1733, and a "no comment mode" that sends image data without adding a comment.

[0107] Scan settings can also be set on the button setting registration screen 1701. In the double-sided setting field 1740, it is possible to select whether to scan both sides of the document or one side of the document. By selecting the double-sided setting field 1740, the user can select "single-sided" or "double-sided" from a pull-down menu.

[0108] Furthermore, the user can select whether to scan the document in color or monochrome in the color setting field 1741. By selecting the color setting field 1741, the user can select "color" or "monochrome" from the pull-down menu.

[0109] After making settings on the setting registration screen 1701, the user confirms the settings by pressing a setting button 1750. The setting values ​​set here are stored in the storage 114. In a second embodiment described later, the setting values ​​are stored in the HDD 405.

[0110] When a generate button 1506 on the setting registration screen 1501 is pressed, a button for performing scan to chat according to the settings registered on the button setting registration screen 1701 is additionally displayed on the home screen 608 .

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

[0112] The icon image of service A is managed by service A, which is a message service provided by the message application server 300, and the MFP 101 can acquire it from the message application server 300. The icon image of service B is recorded in the MFP 101 device.

[0113] The icon images of organization A and organization B are included in the management information of service A. That is, the MFP 101 transmits token information corresponding to a workspace managed by the message app server to the message app server 300, whereby the icon image of organization A or organization B is acquired from the message app server.

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

[0115] Fig. 19 is a flowchart showing an example of processing in which CPU 111 of MFP 101 acquires an icon image for displaying scan-to-chat button 602 on home screen 608. This flowchart is executed when MFP 101 acquires icon information in S1007 and S1012 of Fig. 7, S1307 and S1312 of Fig. 9, Figs. 17, 14, and 15, and when operation unit 116 starts up and displays home screen 608. The flow in Fig. 19 is implemented by CPU 111 of MFP 101 reading a program stored in ROM 112 into RAM 113 and executing it.

[0116] In step S1901, the CPU 111 acquires the button information registered on the screen of FIG.

[0117] In S1902, the CPU 111 acquires an icon image corresponding to the target X from the message application server 300 and the storage 114. Here, the target X is information registered in the button information and indicates an item that will become a destination. In descending order of concept, the items that can become the target X include an application service, a workspace, a channel, and a user.

[0118] In S1903, the CPU 111 requests the icon image acquisition source shown in Fig. 18 to acquire an icon image corresponding to the target X. If the icon image can be acquired here, the process proceeds to S1904, and if the icon image cannot be acquired, the process proceeds to S1905.

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

[0120] In S1905, the CPU 111 checks whether there is a concept higher than the object X, and if there is, the process proceeds to S1906. If there is no concept higher than the object X, the process proceeds to S1907.

[0121] In S1906, the CPU 111 determines the existing superordinate concept item as object X, and proceeds to the processing of S1902.

[0122] In S1907, the CPU 111 acquires a specific default icon from the storage 114. That is, the process of S1907 is performed when no icon image exists for an application service, workspace, channel, or user.

[0123] According to this embodiment, by selecting a registered object, it is possible to easily identify from the object a group with which image data generated by scanning with an image processing device is shared. [Example]

[0124] In the first embodiment, an example has been described in which the MFP 101 directly transmits image data and posting parameters to the message application server 300. In the present embodiment, an example will be described in which the MFP 101 transmits image data and posting parameters to the message application server 300 via the bot server 400.

[0125] FIG. 8 is a diagram showing an example of a sequence in which the MFP 101 transmits a file generated by scanning to the message application server 300 via the bot server 400. In FIG.

[0126] In S1101, the CPU 111 of the MFP 101 accepts the selection of the scan-to-chat button 602, which is an instruction to start scanning. Note that if the selection of the scan-to-chat button 602 causes a screen to be displayed that accepts the selection of a channel, a mention user, or a fixed phrase, scanning is started by accepting the selection.

[0127] In S1102, the CPU 111 controls the reading unit 118 to read an image of the document based on the scan settings set on the button setting registration screen 1701 in Fig. 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 to transmit various information for posting image data, etc. to the bot server 400. Here, the token information registered on the button setting registration screen 1701 in Fig. 17, the channel information set on the setting registration screen 1701 or the screens in Fig. 14 and Fig. 15, the user information to be mentioned, the comment, etc. are transmitted together with the image data.

[0129] In S1105, the CPU 401 of the bot server transmits the received various information to the message application server 300. The above information is transmitted by executing the command "HTTP POST https: / / message.com / api / files.upload".

[0130] In S1106, the CPU 301 of the message app server 300 searches for registered workspace information and app information using the token information received in S1105, and associates the received image data and channel information with the specified channel and stores them. That is, the CPU 301 controls the posting of the received image data and comment to the specified channel. Furthermore, if a mention user is specified, the CPU 301 also associates the received image data with the channel and the user to whom the post is to be made and stores them. As a result, when the user starts the message app on the mobile terminal 200 and specifies a channel to check the content of the conversation on the channel, a screen on which the received image data has been posted is displayed.

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

[0132] In S1108, CPU 401 of bot server 400 transmits the result received in S1107 to MFP 101. If the posting is successful, CPU 111 of MFP 101 may display a notification that the posting was successful on operation unit 116. If the posting is unsuccessful, CPU 111 of MFP 101 may display a notification that the posting was unsuccessful on operation unit 116. Alternatively, if the posting is successful, no notification may be displayed, and only if the posting is unsuccessful, a notification that the posting was unsuccessful may be displayed.

[0133] FIG. 16 is a diagram showing an example of the correspondence between IDs and token information. In the table of FIG. 16, user IDs or device IDs are registered in correspondence with authentication information (token information). This table is stored in HDD 405 of bot server 400. Here, the user ID and device ID are information stored in MFP 101, and the user ID is user identification information set for each user who uses MFP 101. The device ID is device identification information set for each MFP. The user ID is identification information set by the user when creating a user account for logging in to MFP 101, and the device ID is identification information unique to MFP 101 set at the time of shipment from the factory.

[0134] The token information in FIG. 16 is used when executing scan to chat without selecting the scan to chat button 602.

[0135] 9 is a flowchart showing an example of processing when the scan-to-chat button 602 in this embodiment is selected. Note that each operation (step) in the flowchart of this embodiment is executed by the CPU 111 reading a control program recorded in the ROM 112 or storage 114 into the RAM 113. The explanation of the steps in the flow of FIG. 9 where the same processing as in FIG. 7 is executed will be omitted.

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

[0137] In S1302, the CPU 111 transmits information requesting channel list information to the bot server 400. At this time, the CPU 111 transmits pre-registered token information 1503 to the bot server 400. As a result, the CPU 401 of the bot server 400 transmits the received token information and information requesting channel list information to the message application server 300.

[0138] In S1303, the CPU 111 determines whether or not channel list information has been received from the message application server 300 in response to the request to acquire channel list information sent in S1302. Specifically, the CPU 111 determines whether the bot server 400 has received the channel list information from the message application server 300, and whether the MFP 101 has received the channel list information from the bot server 400. Furthermore, if the status code in the HTTP communication response is an error, or if the body information of the response includes a parameter indicating that the information cannot be acquired, the CPU 111 determines that the channel list information has not been received.

[0139] Steps S1304 to S1306 are the same processes as steps S1004 to S1005 in FIG.

[0140] In S1307, the CPU 111 transmits a request for icon information of other channels of the target workspace to the bot server 400, and the bot server 400 transmits the request to the message app server 300. As a result, the MFP 101 acquires icon information of other channels of the target workspace from the message app server 300 via the bot server 400.

[0141] Steps S1308 to S1311 are similar to steps S1008 to S1011 in FIG.

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

[0143] Steps S1313 to S1318 are similar to steps S1013 to S1018 in FIG.

[0144] In S1319, the CPU 111 transmits the token information 1503 registered in advance to the bot server 400, as well as the file and posting parameters generated in S1317 and S1318. The bot server 400 then transmits the token information 1503, the file and posting parameters generated in S1317 and S1318 to the message app server 300 using the POST method of HTTP communication. By transmitting this data (the file converted from image data and the posting parameters) to the message app server 300, the message app server 300 controls the message app server 300 to post the received file to the user indicated by the received mention information on the channel indicated by the channel information that received the file.

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

[0146] In this embodiment, only one piece of token information is registered, but if multiple pieces of token information are registered, the processes related to the token information, such as S1302, S1303, and S1319, are executed for each registered token.

[0147] According to this embodiment, even if the interface specifications of the message application server 300 are changed, this can be realized by simply updating the program of the bot server without uploading the program of the MFP 101. Furthermore, in a workplace with multiple MFPs, file posting can be performed without having to set a token individually for each MFP.

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

[0149] 101 MFP 300 Message App Server 400 Bot Server 111 CPU 118 Reading unit

Claims

1. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; and a third receiving step of receiving an execution instruction from a user, a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by the scanning device based on a single execution instruction received in the third receiving step while the channel is selected; The program is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

2. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; and a third receiving step of receiving an execution instruction from a user, a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by the scanning device based on a single execution instruction received in the third receiving step; The program is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

3. causing the scanning device to further execute a third display step of displaying a button for receiving the execution instruction on an operation unit of the scanning device; 3. The program according to claim 1, wherein both the scanning process and the transmission process are executed based on a single selection of the displayed button.

4. A first display step of displaying a plurality of groups of a chat service; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; and a third receiving step of receiving an execution instruction from a user, a process from a scanning process of scanning an original to generate image data to a transmission process of transmitting the generated image data is executed by the scanning device in response to a single execution instruction received in the third receiving step with the channel selected; The image data transmitted in the transmission process is stored in association with the selected channel.

5. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; and a third receiving step of receiving an execution instruction from a user, a scanning process of scanning an original to generate image data and a transmission process of transmitting the generated image data are executed by the scanning device in response to a single execution instruction received in the third receiving step; The image data transmitted in the transmission process is stored in association with the selected channel.

6. causing the scanning device to further execute a third display step of displaying a button for receiving the execution instruction on an operation unit of the scanning device; 6. The program according to claim 4, wherein the scanning process through the transmission process are executed by the scanning device in response to a single selection of the displayed button.

7. A program described in any one of claims 1 to 6, characterized in that when the transmission process is executed, the image data and information about the selected channel are transmitted to a server, and the image data is stored in correspondence with the selected channel.

8. The method further causes the scanning device to execute a fourth reception step of receiving scan settings; 8. The program according to claim 1, wherein the scanning process scans an original based on the scan settings, and generates image data.

9. The program described in Claim 8, characterized in that the scan setting is a setting for scanning both sides of the document or scanning one side of the document.

10. The program described in Claim 8, characterized in that the scan setting is a setting for scanning the document in color or in monochrome.

11. A program described in any one of claims 1 to 10, characterized in that the program further causes the scanning device to execute a printing process of printing an image on paper.

12. A receiving step of receiving information on the plurality of channels is further performed by the scanning device, 12. The program according to claim 1, wherein in the second display step, the plurality of channels are displayed based on the received channel information.

13. causing the scanning device to further execute a transmitting step of transmitting token information; 13. The program according to claim 12, wherein said receiving step receives information on said plurality of channels based on said transmitted token information.

14. A program described in any one of claims 1 to 13, characterized in that in the transmission process, the image data is transmitted via HTTP communication.

15. A program described in any one of claims 1 to 14, characterized in that it further causes the scanning device to execute an execution process that executes the scanning process and the transmission process.

16. The method further comprises causing the scanning device to execute a fifth reception step of receiving a file name from a user before receiving the single execution instruction in the third reception step; 16. The program according to claim 1, wherein the image data having the accepted file name is transmitted in the transmission process.

17. further causing the scanning device to perform an acquisition step of acquiring an icon image corresponding to the group; 17. The program according to claim 1, wherein the acquired icon image and the group are displayed in the first display step.

18. The program described in Claim 17, characterized in that the icon image acquired in the first display step is displayed while an object for checking the history of jobs executed by the scanning device is displayed.

19. A program described in any one of claims 1 to 18, characterized in that the first display step displays multiple groups of the chat service when a button for a function other than the scan function is selected, the button being different from a button for a scan function that sends image data generated by scanning by email.

20. A first display means for displaying a plurality of groups of a chat service; a first accepting means for accepting a group selection by a user from the displayed plurality of groups; a second display means for displaying a plurality of channels included in the selected group; a second receiving means for receiving a channel selection by a user from the displayed plurality of channels; a third receiving means for receiving an execution instruction from a user; executes both a scan process for scanning an original to generate image data and a transmission process for transmitting the generated image data based on a single execution instruction received by the third reception means while the channel is selected; The scanning device is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

21. A first display means for displaying a plurality of groups of a chat service; a first accepting means for accepting a group selection by a user from the displayed plurality of groups; a second display means for displaying a plurality of channels included in the selected group; a second receiving means for receiving a channel selection by a user from the displayed plurality of channels; a third receiving means for receiving an execution instruction from a user; executes both a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data based on a single execution instruction received by the third receiving means; The scanning device is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

22. The method further comprises a third display means for displaying a button for receiving the execution instruction on the operation unit of the scanning device, 22. The scanning device according to claim 20, wherein both the scanning process and the transmission process are executed based on a single selection of the displayed button.

23. A first display means for displaying a plurality of groups of a chat service; a first accepting means for accepting a group selection by a user from the displayed plurality of groups; a second display means for displaying a plurality of channels included in the selected group; a second receiving means for receiving a channel selection by a user from the displayed plurality of channels; a third receiving means for receiving an execution instruction from a user; executes a process from a scan process of scanning an original to generate image data to a transmission process of transmitting the generated image data in response to a single execution instruction received by the third receiving means while the channel is selected; The scanning device according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

24. A first display means for displaying a plurality of groups of a chat service; a first accepting means for accepting a group selection by a user from the displayed plurality of groups; a second display means for displaying a plurality of channels included in the selected group; a second receiving means for receiving a channel selection by a user from the displayed plurality of channels; a third receiving means for receiving an execution instruction from a user; executes a process from a scan process of scanning an original to generate image data to a transmission process of transmitting the generated image data in response to a single execution instruction received by the third receiving means; The scanning device according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

25. The method further comprises a third display means for displaying a button for receiving the execution instruction on the operation unit of the scanning device, 25. The scanning device according to claim 23, wherein the processes from the scanning process to the transmission process are executed by a single selection of the displayed button.

26. A scanning device described in any one of claims 20 to 25, characterized in that when the transmission process is executed, the image data and information on the selected channel are transmitted to a server, and the image data is stored in correspondence with the selected channel.

27. ​​Further having a fourth accepting means for accepting scan settings, 27. The scanning device according to claim 20, wherein the scanning process scans an original based on the scan settings, and generates image data.

28. The scanning device according to claim 27, wherein the scan setting is a setting for scanning both sides of a document or one side of a document.

29. The scanning device according to claim 27, wherein the scan setting is a setting for scanning the document in color or in monochrome.

30. A scanning device as claimed in any one of claims 20 to 29, further comprising a printing means for printing an image on paper.

31. Further comprising receiving means for receiving information of the plurality of channels, 31. The scanning device according to claim 20, wherein the second display means displays the plurality of channels based on the received channel information.

32. Further comprising a transmitting means for transmitting token information, 32. The scanning device according to claim 31, wherein said receiving means receives information on said plurality of channels based on said transmitted token information.

33. 33. The scanning device according to claim 20, wherein in the transmission process, the image data is transmitted by HTTP communication.

34. A scanning device as described in any one of claims 20 to 33, further comprising an execution means for executing the scanning process and the transmission process.

35. The method further comprises a fifth receiving means for receiving a file name from a user before the third receiving means receives the single execution instruction; 35. The scanning device according to claim 20, wherein the image data having the accepted file name is transmitted in the transmission process.

36. Further comprising: an acquisition means for acquiring an icon image corresponding to the group; 36. The scanning device according to claim 20, wherein the first display unit displays the acquired icon image and the group.

37. A scanning device as described in Claim 36, characterized in that the first display means displays the acquired icon image while an object for checking the history of jobs executed by the scanning device is displayed.

38. A scanning device as described in any one of claims 20 to 37, characterized in that when a button for a function other than the scan function is selected, which is different from a button for a scan function that sends image data generated by scanning by email, the first display means displays multiple groups of the chat service.

39. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; a third receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by a scanning device based on a single execution instruction received in the third receiving step with the channel selected; The scanning method according to claim 1, wherein the image data transmitted by the transmission process being executed based on the single execution instruction is stored in association with the selected channel.

40. A first display step of displaying a plurality of groups of a chat service; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; a third receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by the scanning device based on a single execution instruction received in the third receiving step; The scanning method according to claim 1, wherein the image data transmitted by the transmission process being executed based on the single execution instruction is stored in association with the selected channel.

41. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; a third receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are executed by the scanning device in response to a single execution instruction received in the third receiving step with the channel selected; The scanning method according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

42. A first display step of displaying a plurality of groups of chat services; a first receiving step of receiving a group selection by a user from the displayed plurality of groups; a second display step of displaying a plurality of channels included in the selected group; a second receiving step of receiving a channel selection by a user from the displayed plurality of channels; a third receiving step of receiving an execution instruction from a user; a scanning process of scanning an original to generate image data and a transmission process of transmitting the generated image data are executed by the scanning device in response to a single execution instruction received in the third receiving step; The scanning method according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

Images