Scanning device, scanning method, and program

Abstract

To reduce the time and effort for an approval request on a chat service related to image data generated by a scanning device reading an image of a document.SOLUTION: A scanning device of the present invention has: scanning means that scans an image of a document to generate image data; acquisition means that acquires channel information and information on users from a chat service; receiving means that receives selection of a channel from a plurality of channels indicated by the acquired channel information, and selection of a user to be an approver from users included in the selected channel; and transmission means that transmits, to the chat service, the generated image data and information on the selected user.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a scanning device, a scanning method, and a program. [Background technology]

[0002] Patent Document 1 discloses that an image processing device transmits image data generated by scanning an image of a document to a message application server that provides a chat service. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-078084 Summary of the Invention [Problem to be solved by the invention]

[0004] Chat services provide a function that allows workflows such as various approval requests to be completed within a channel.

[0005] Because the image processing device of Patent Document 1 cannot make an approval request for image data generated by scanning an image of a document, it is necessary to make an approval request on the chat service after the image data has been posted.

[0006] The present invention has been made in consideration of the above problems, and has an object to reduce the effort involved in requesting approval on a chat service for image data generated by a scanning device reading an image of a document. [Means for solving the problem]

[0007] The scanning device of the present invention is characterized by having a scanning means for scanning an image of an original document to generate image data, an acquisition means for acquiring channel information and user information from a chat service, a receiving means for accepting a selection of a channel from a plurality of channels indicated by the acquired channel information and a selection of a user to be an approver from among users included in the selected channel, and a transmitting means for transmitting the generated image data and information of the selected user to the chat service. Effect of the Invention

[0008] It is possible to reduce the effort involved in requesting approval on a chat service for image data generated by a scanning device reading an image of a document. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of the present invention. [Diagram 2] FIG. 1 shows an example of a hardware configuration of an image processing device 101. [Diagram 3] FIG. 3 is a diagram showing an example of a hardware configuration of a mobile terminal 300. [Figure 4] FIG. 4 is a diagram showing an example of a hardware configuration of a message application server 400. [Diagram 5] FIG. 1 shows an example of a hardware configuration of a bot server 500. [Figure 6] FIG. 13 shows an example of a home screen displayed on the operation unit 207 of the image processing device 101. [Figure 7] A sequence diagram showing an example of a process in which the image processing device 101 creates an approval request with a file generated by scanning and attached, and transmits the request to the message application server 400. [Figure 8] 1 is a flowchart showing an example of a scan-to-workflow process executed by the image processing device 101. [Figure 9]FIG. 1 is a sequence diagram showing an example of a process in which an approval request with a file generated by scanning and attached by the image processing device 101 is created and transmitted to the message application server 400 via the bot server 500. [Figure 10] Flowchart showing an example of scan-to-workflow processing [Figure 11] 1 is a flowchart showing an example of a process of the bot server 500. [Figure 12] An example of the screen transition for scan-to-workflow processing [Figure 13] FIG. 13 is a diagram showing an example of a setting registration screen. [Figure 14] A diagram showing an example of a message screen of a message app [Figure 15] FIG. 13 is a diagram showing an example of a file structure in a message application server 400. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] 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. EXAMPLES

[0011] FIG. 1 is a diagram showing an example of a system configuration of the present invention. The image processing system of this embodiment is configured with an image processing device (MFP: Multi Function Peripheral) 101 that can communicate with a mobile terminal 300, which is an example of a terminal device, via a network 100, and a message app server 400. The image processing device may be a scanning device. A bot server 500 is also connected via the network 100 and can communicate with the image processing device 101. The message app server 400 is a chat server that receives messages and image data transmitted from the image processing device 101 and the mobile terminal 300, and manages a chat service that displays the messages and image data on the mobile terminal 300 or a PC (not shown) according to a user operation. The message app server 400 may be configured with a plurality of server devices. The bot server 500 links the image processing device 101 with information (token information) corresponding to a bot app installed in the message app server 400 connected to the image processing device 101, and transfers a request from the image processing device 101 to the message app server 400. The network 100 of this embodiment may be the Internet or a LAN (Local Area Network). Furthermore, the network 100 may be wired or wireless.

[0012] 2 is a diagram showing an example of a hardware configuration of the image processing device 101. The image processing device 101 includes a CPU 202, a ROM 203, a RAM 204, a storage 205, an operation unit I / F 206, an operation unit 207, a reading unit I / F 208, a reading unit 209, a printing unit I / F 210, a printing unit 211, a wireless communication unit I / F 212, and a wireless communication unit 213. The image processing device 101 also includes a FAX unit I / F 214, a FAX communication unit 215, a communication unit I / F 216, and a communication unit 217.

[0013] The control unit 201 including the CPU 202 controls the operation of the entire image processing device 101. The CPU 202 reads out a control program stored in the ROM 203 or the storage 205 to the RAM 204, and performs various controls such as reading control and printing control. The ROM 203 stores a control program executable by the CPU 202. The ROM 203 also stores a boot program and font data. The RAM 204 is a main memory, and is used as a work area and a temporary storage area for developing various control programs stored in the ROM 203 and the storage 205. The storage 205 stores image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 205, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may be used. An eMMC (embedded Multi Media Card) may also be used.

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

[0015] An operation unit I / F 206 connects an operation unit 207 including a display unit such as a touch panel and hard keys to the control unit 201. The operation unit 207 displays information to a user and detects inputs from the user.

[0016] The reading unit I / F 208 connects the control unit 201 to a reading unit 209 such as a scanner. The reading unit 209 reads an image of an original document, and the CPU 202 converts the image into image data such as binary data. Image data generated based on the image read by the reading unit 209 is transmitted to an external device or printed on recording paper. The reading unit 209 included in the scanning means can scan multiple sheets of original document placed on an ADF (not shown) and generate multiple pieces of image data. At that time, the multiple sheets of original document are transported by the ADF, which is a transport means, and scanned, and image data is generated.

[0017] The printing unit I / F 210 connects a printing unit 211, such as a printer, to the control unit 201. The CPU 202 transfers image data (print data) stored in the RAM 204 to the printing unit 211 via the printing unit I / F 210. The printing unit 211 prints an image based on the transferred image data on recording paper fed from a paper feed cassette.

[0018] The wireless communication unit I / F 212 is an I / F for controlling the wireless communication unit 213, and connects the control unit 201 to an external wireless device (here, the mobile terminal 300) via wireless communication.

[0019] The control unit 201 is connected to the public line network 107 by controlling a FAX communication unit 215 such as a facsimile via a FAX unit I / F 214. The FAX unit I / F 214 is an I / F for controlling the FAX communication unit 215, and is capable of connecting to the public line network and controlling the facsimile communication protocol by controlling a modem and an NCU for facsimile communication.

[0020] The communication unit I / F 216 connects the control unit 201 to the network 100. The communication unit I / F 216 allows the communication unit 217 to transmit image data and various information inside the device to an external device on the network 100, and receives print data and information on the network 100 from an information processing device on the network 100. As a method of transmission and reception via the network 100, transmission and reception using e-mail and file transmission using other protocols (for example, FTP, SMB, WEBDAV, etc.) can be performed. Furthermore, image data and various setting data can be transmitted and received over the network 100 by accessing from the mobile terminal 300, the message application server 400, the bot server 500, and the schedule application server 600 via HTTP communication.

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

[0022] The CPU 307 reads out a control program stored in the ROM 308 and executes various processes for controlling the operation of the mobile terminal 300. The ROM 308 stores the control program. The RAM 309 is used as a temporary storage area such as a main memory and a work area for the CPU 307. The HDD 310 stores various data such as photographs and electronic documents.

[0023] The operation panel 301 has a touch panel function capable of detecting a user's touch operation, and displays various screens provided by the OS and an e-mail sending application. The operation panel 301 is also used to check information stored in the message application server 400 and the schedule application server 600. The user can input a desired operation instruction to the mobile terminal 300 by inputting a touch operation to the operation panel 301. The mobile terminal 300 has a hardware key (not shown), and the user can input an operation instruction to the mobile terminal 300 using this hardware key.

[0024] Camera 304 captures an image in response to an image capture instruction from a user. The photograph captured by camera 304 is stored in a predetermined area of ​​HDD 310. It is also possible to obtain information from a QR code read by camera 304 using a program capable of analyzing QR codes (registered trademark).

[0025] The mobile terminal 300 can transmit and receive data to and from various peripheral devices via an NFC communication unit 305, a Bluetooth (registered trademark) communication unit 306, and a wireless LAN communication unit 311. The Bluetooth communication unit 306 of the mobile terminal 300 may be compatible with Bluetooth (registered trademark) Low Energy.

[0026] FIG. 4 is a diagram showing an example of a hardware configuration of the message application 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 400. 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 transmitted and received to and from various devices such as the mobile terminal 300, the image processing device 101, the bot server 500, and the schedule application server 600 via the communication unit 404. The communication unit 404 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi.

[0027] 5 is a diagram showing an example of the hardware configuration of the bot server 500. The CPU 501 reads out a control program stored in the ROM 502, controls the operation of the bot server 500, and processes requests from the image processing device 101. Some of the requests are directed to the message app server 400, while others are directed to the bot server 500. The ROM 502 stores the control program. The RAM 503 is used as a temporary storage area such as the main memory and work area of ​​the CPU 501. The HDD 505 stores various data such as messages, image data, and channel information. Data can be transmitted and received via the communication unit 504 to and from various models such as the mobile terminal 300, the image processing device 101, and the message app server 400.

[0028] 6 is a diagram showing an example of a home screen displayed on the operation unit 207 of the image processing device 101. The operation unit 207 is made up of a touch panel 601 that displays an operation screen, and LEDs 611 and 612. The touch panel 601 is an instruction means, and also functions as a receiving means that receives instructions from a user, and also functions as a display means that displays a screen. The user directly touches the screen displayed on the touch panel 601 with a finger, a stylus, or other object, and issues an instruction to execute each function based on the displayed screen.

[0029] 6 displays a home screen 602. The home screen 602 is the first screen for instructing the execution of each function of the image processing device 101, and is a screen for selecting a screen display for making various settings for each function executed by the image processing device 101, such as copy, fax, scan, and media print.

[0030] A status check button 603 is an object for displaying a screen (status check screen) for checking the status of the image processing apparatus 101. It is possible to display a transmission history or a job execution history from the status check screen (not shown).

[0031] The scan button 604 is an object for displaying a scan selection screen (not shown) from the image processing apparatus 101. The scan selection screen is a screen for selecting a transmission function such as electronic mail transmission (E-mail), file transmission via SMB, FTP, or HTTP, and Internet fax (I-fax) transmission. By touching the object indicating the displayed transmission function, a setting screen for each transmission function is displayed.

[0032] A menu button 605 is an object for displaying a screen for setting the environment such as the language to be used and the settings of each function.

[0033] An address book button 606 is an object for displaying an address book screen of the image processing apparatus 101 when selected by the user.

[0034] The scan-to-chat button 607 is an object for displaying a setting screen for scan-to-chat processing.

[0035] The scan to workflow button 608 is an object for displaying a setting screen for scan to workflow processing. When the scan to workflow button 608 is selected by the user, a scan to workflow screen 1201 in Fig. 12 is displayed on the operation unit 207. The scan to workflow processing will be described in detail with reference to Figs. 7 and 8.

[0036] The HOME button 609 is an object for displaying the home screen 602, and is an object that is always displayed on the operation unit 207.

[0037] The stop button 610 is an object for canceling various operations, and is an object that is always displayed on the operation unit 207.

[0038] The LEDs 611 and 612 notify the user of the status of the image processing device 101. The LED 611 lights up while an e-mail or a print job is being received or executed, and the LED 612 lights up when an error occurs in the image processing device 101.

[0039] Fig. 7 is a diagram showing an example of a sequence in which the image processing device 101 transmits an approval request for a file generated by scanning to the message application server 400. The sequence in Fig. 7 is started in response to selection of the channel selection button 1209 on the scan to workflow screen 1201 in Fig. 12.

[0040] In S701, the CPU 202 of the image processing device 101 requests the message app server 400 for channel list information by HTTP communication via the communication unit 217. Specifically, the image processing device 101 transmits to the message app server 400 token information inputted thereto and information indicating a request for a channel list in a workspace indicated by the token information. Here, an example of the command to be transmitted is "HTTP GET https: / / message.com / api / channels.list". The URL "https: / / message.com / api / channels.list" written in this command is a URL for accessing the message app server 400. By transmitting the token information to this URL, the message app server 400 searches for a workspace and a bot app corresponding to the token information. The token information is inputted by the user via the setting registration screen 1301 of FIG. 13 displayed on the operation unit 207 of the image processing device 101.

[0041] Here, a workspace is like an organization to which multiple users belong in a messaging app. Also, a channel is like a chat room in a workspace. The chat room here is a mechanism for multiple users participating in a chat room to send and receive messages to each other and communicate 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 for multiple users to send and receive messages and communicate like a conversation. For example, it may be something like a group chat, a room, a talk room, or a group.

[0042] Here, the bot application is an application for registering the image processing device 101 as a user in a message application and posting messages and image data, and is installed in the message application server 400. By specifying a bot application and transmitting image data to the message application server 400, the bot application posts the transmitted image data in the message application. In addition, the HDD 405 of the message application server 400 stores the bot application and a token in association with each other, and also associates the bot application with a workspace. Therefore, by receiving token information from the image processing device 101, the message application server 400 can return information on a workspace associated with the bot application associated with the token information. Note that the token information, the bot application, and the workspace may be directly associated with each other. This allows a workspace (a workspace to which the user wants to send image data) corresponding to the token information registered in advance to be selected from a large number of workspaces.

[0043] In S702, the CPU 401 of the message application server 400 checks whether access to the URL is permitted based on the token information received from the image processing device 101 via the communication unit 404. If access is permitted, channel list information included in the workspace corresponding to the token information is generated. The channel list information is array information indicating channel information. The channel information includes a channel ID, the name of the channel, information indicating users participating in the channel, user IDs, and a channel setting value indicating settings such as whether the channel is an archive channel.

[0044] In S703, the CPU 401 of the message application server 400 transmits the channel list information to the image processing device 101 via the communication unit 404 as response information of the HTTP communication.

[0045] In S704, the CPU 202 of the image processing device 101 generates a channel selection screen 1210 based on the channel information included in the received channel list information. Then, when the channel selection button 1209 is selected by the user, the CPU 202 of the image processing device 101 displays the channel selection screen 1210 on the touch panel 601 of the operation unit 207 and waits for a user operation. The channel selection screen 1210 will be described later in the description of FIG. 12.

[0046] In S705, the CPU 202 of the image processing device 101 confirms the information of the channel to which the posting is to be made by selecting at least a channel on the channel selection screen 1210 and selecting the back button 1211.

[0047] In S706, when the approver selection button 1212 is selected by the user, the CPU 202 of the image processing apparatus 101 displays an approver selection screen 1214 on the touch panel 601 of the operation unit 207 and waits for an operation by the user. The approver selection screen 1214 will be described later in the description of Fig. 12. Here, an approver is a user who can execute approval processing for an approval request related to image data generated by scanning a document.

[0048] In S707, the CPU 202 of the image processing apparatus 101 confirms the approver by selecting a user who will be the approver on the approver selection screen 1214 and selecting the back button 1213. In other words, the user who will be the approver is a user who is requested to give approval.

[0049] The user's operations in S706 and S707 may be omitted, and in that case, all users included in the channel to which the posting is to be made may become approvers.

[0050] In S708 , the CPU 202 of the image processing apparatus 101 accepts a scan execution instruction via the operation unit 207 .

[0051] In step S709, the CPU 202 of the image processing apparatus 101 performs scanning with the scan settings set when the scan execution instruction is received.

[0052] In S710, the CPU 202 of the image processing apparatus 101 generates image data of the scanned image in a format set by the scan settings. Note that the scan settings are those designated by the user on a detailed setting screen for the scan-to-workflow (not shown). Note that the scan settings may be displayed and set together with the approval settings on the approval settings screen 1217 in FIG. 12.

[0053] In S711, the CPU 202 of the image processing device 101 transmits the same token information as in S701, information on the posting destination channel selected in S705, and information on the user selected in S707 to be the approver to the message app server 400 via the communication unit 217. Furthermore, a file in which the image data generated in S709 is converted into an appropriate file format, and the title and comment of the approval request are also transmitted by HTTP communication. Note that the file format, the title and comment of the approval request are specified by the user on the scan-to-workflow approval setting screen 1217.

[0054] In S712, the CPU 401 of the message app server 400 searches for workspace information and app information registered in the token information received in S711. Then, the CPU 401 stores the received approver information, file, title of the approval request, and comment in association with the channel specified in the channel information. If a specific user is specified instead of the entire channel, the CPU 401 further stores the received approver information, file, title of the approval request, and comment in association with the channel and the user to be approved. As a result, when the user starts the message app on the mobile terminal 300 and specifies a channel to check the contents of the conversation in the previous channel, a screen is displayed on which an object of the approval request with the received image data attached is created.

[0055] In S713, the CPU 401 of the message application server 400 transmits a result corresponding to whether the creation of the approval request was successful or not to the image processing device 101 as response information of the HTTP communication. If the creation of the approval request is successful, the CPU 202 of the image processing device 101 may display a notification that the creation of the approval request was successful on the operation unit 207. If the creation of the approval request fails, the CPU 202 of the image processing device 101 may display a notification that the creation of the approval request failed on the operation unit 207. If the creation of the approval request is successful, no notification may be displayed, and only if it fails, a notification that the creation of the approval request failed may be displayed.

[0056] Fig. 8 is a flowchart showing an example of scan-to-workflow processing executed by the image processing device 101. The CPU 202 of the image processing device 101 reads a program stored in the ROM 203 into the RAM 204 and executes it, thereby executing the processing of the flowchart in Fig. 8. The flow in Fig. 8 is started when the image processing device 101 is powered on.

[0057] In S801, the CPU 202 determines whether or not the scan-to-workflow button 608 has been selected. If it is determined that the button has been selected, the process proceeds to S802. If not, the process returns to S801.

[0058] In S802, the CPU 202 displays a scan to workflow screen 1201 on the touch panel 601 of the operation unit 207. Here, the screen transition when the scan to workflow button 608 is selected will be described with reference to FIG.

[0059] 12 is a diagram showing an example of screen transitions in scan-to-workflow processing. When a scan-to-workflow button 608 displayed on the home screen 602 is selected, a scan-to-workflow screen 1201 is displayed on the touch panel 601 of the operation unit 207.

[0060] A destination confirmation button 1202 is displayed on the scan to workflow screen 1201. The destination confirmation button 1202 displays the number of destinations set as destinations for posting image data generated by scanning. In the example of Fig. 12, an example will be described in which one channel is selected as a posting destination. When multiple destinations are selected, the number of set posting destinations is displayed as the number of destinations.

[0061] When the destination confirmation button 1202 is selected, a scan-to-workflow destination confirmation screen 1203 is displayed. The scan-to-workflow destination confirmation screen 1203 displays the posting destination set by selecting the channel selection button 1209 and the approver set by selecting the approver selection button 1212. The posting destination button 1204 displays the posting destination set at that time when the user selects the posting destination on the channel selection screen 1210. The approver button 1205 displays the approver set at that time when the user selects the approver on the approver selection screen 1214. Furthermore, when the posting destination button 1204 and the approver button 1205 are selected, a details screen (not shown) is displayed, and details of the set posting destination and approver are displayed.

[0062] In this embodiment, only one posting destination is displayed on the scan to workflow destination confirmation screen 1203, but this is not limited thereto. For example, the image processing apparatus 101 can set multiple posting destinations from the message app server 400 to display multiple posting destination buttons on the scan to workflow destination confirmation screen 1203. Also, in this embodiment, only one approver is displayed on the scan to workflow destination confirmation screen 1203, but this is not limited thereto. For example, the user may select multiple approvers on the approver selection screen 1214, and if the user does not select an approver on the approver selection screen 1214, everyone may be the approver by default.

[0063] When a reset button 1206 is selected on the scan to workflow screen 1201, the set information is cleared. At this time, the set destination information is cleared. When a black and white start button 1207 and a color start button 1208 are selected on the scan to workflow screen 1201, the scan and send process is started.

[0064] When the channel selection button 1209 is selected, a channel selection screen 1210 is displayed. The channels and users displayed on this channel selection screen 1210 are displayed based on the channel list information received by the image processing device 101 from the message application server 400. On this screen, it is possible to select the channel to post to and which users belonging to that channel to notify. In other words, it is possible to select the channel to post to and the person to mention. When the channel button is selected, the users belonging to that channel are displayed in a pull-down menu. On this screen, both the channel and the user may be selected, or only the channel may be selected to post to all users belonging to that channel. In addition, multiple channels may be selected, or one channel may be selected and multiple users within that channel may be selected. In addition, multiple channels may be selected and different users belonging to each channel may be selected.

[0065] When the back button 1211 is selected, the channel selection is maintained, and the scan-to-workflow screen 1201 is displayed again. At this time, the destination column 1218 displays the selected channel name as the destination and the name of the user to be notified, "Destination: Channel 3 @ User 1." The CPU 202 of the image processing device 101 stores the destination based on the channel and user set at this time in the RAM 204 or storage 205.

[0066] When the approver selection button 1212 is selected, an approver selection screen 1214 is displayed. The channels and users displayed on this approver selection screen 1214 are displayed based on the channel selected on the channel selection screen 1210. On this screen, it is possible to select an approver, that is, to which user in the destination channel an approval request is to be issued. On this screen, one user or multiple users may be selected as the approver. Also, when multiple channels are selected on the channel selection screen 1210, it may be possible to select an approver for each channel. Also, if the user does not select an approver on the approver selection screen 1214, everyone may be the approver by default, or the user selected on the channel selection screen 1210 may be the approver.

[0067] When the back button 1213 is selected, the approver selection is saved, and the scan-to-workflow screen 1201 is displayed again. The CPU 202 of the image processing apparatus 101 stores the approver set at this time in the RAM 204 or the storage 205.

[0068] When the approval setting button 1215 is selected, an approval setting screen 1217 is displayed. On this screen, approval settings such as the setting of the transmission file, the title and comments of the approval request, and the priority can be changed and confirmed. The title of the approval request may be input by the user. The priority of the approval request can be selected from "important", "high", "medium", and "low", and the selected priority information is transmitted to the message app server 400. The message app server 400 generates an approval request based on the transmitted information. In other words, the priority set here can be confirmed in the approval request posted to the channel.

[0069] When a back button 1216 is selected, the approval setting contents are saved, and the scan to workflow screen 1201 is displayed again. In addition, the CPU 202 of the image processing apparatus 101 stores the approver set at this time in the RAM 204 or the storage 205.

[0070] Here, the description will return to the flow of Fig. 8. In S802, the CPU 202 displays the scan-to-workflow screen 1201 of Fig. 12 on the operation unit 207. In S803, the CPU 202 detects that the channel selection button 1209 has been selected.

[0071] In S804, in response to the selection of the channel selection button, the CPU 202 executes a process of transmitting information indicating a request for channel information by HTTP communication to the message application server 400, using the token information 1303 registered in advance.

[0072] Here, the setting registration screen in Fig. 13 will be described. Fig. 13 is a diagram showing an example of the setting registration screen. The setting registration screen 1301 is a screen displayed on the operation unit 207 of the image processing device 101. Note that the setting registration screen 1301 may also be displayed as a Web page on the operation unit of an information processing device such as a PC connected to the image processing device 101 via a network. The contents registered on the setting registration screen 1301 are recorded in the storage 205 in the first embodiment, and in the HDD 505 in the second embodiment.

[0073] Connection destination 1302 is a column showing organization information of the connection destination. Token information 1303 is a column of registered token information. Operation buttons 1304 is a column of operation buttons. In this item, an edit button 1305 and a generate button 1306 are displayed.

[0074] When an edit button 1305 is selected, character strings such as token information and connection destination information can be input and changed using a keyboard or the like. When a generate button 1306 is selected, a scan to workflow button 608 is set to be displayed on the home screen 602. The contents registered on the setting registration screen 1301 are stored in the storage 205 in the first embodiment, and in the HDD 505 in the second embodiment.

[0075] By clicking a new registration button 1307, it is possible to accept input of a character string by the user and to add and register connection destination and token information.

[0076] Now, returning to the explanation of the flow in Fig. 8, in S805, the CPU 202 determines whether or not channel information has been received from the message application server 400 in response to the channel acquisition request sent in S804. Specifically, 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, it is determined that the channel list information has not been received. If it is determined that the information has been received, the process proceeds to S808. If not, the process proceeds to S806.

[0077] In S806, the CPU 202 displays information indicating that the channel list information could not be received on the channel selection screen 1210. At this time, the channel selection screen 1210 does not display any channel or user options.

[0078] In S807, the CPU 202 judges whether or not the back button 1211 has been selected. If it is judged that the back button 1211 has been selected, the process returns to S802. If not, the process returns to S807.

[0079] In S808, the CPU 202 displays, on the touch panel 601 of the operation unit 207, a channel selection screen 1210 on which the channel information and the like received from the message application server 400 are displayed.

[0080] In S809, the CPU 202 detects whether the posting destination (channel, or channel and user) selected on the channel selection screen 1210 has been confirmed via the touch panel 601 of the operation unit 207. If it has been confirmed, the process transitions to S810, and the posting channel list information is updated. If it has not been confirmed, the process transitions to S808. The method for detecting confirmation is whether the back button 1211 has been selected. Note that, in the case of a screen configuration in which the Confirm button is displayed on the screen of the operation unit 207, a similar transition is made when the Confirm button is selected.

[0081] 12 on the operation unit 207, and updates the display of the posting destination field 1218 with the posting destination confirmed in S809. At this time, information on the user to be notified is also displayed together with the posting destination channel.

[0082] In S811, the CPU 202 detects that the approver selection button 1212 has been selected. By detecting that the approver selection button 1212 has been selected, an approver selection screen 1214 is displayed on the touch panel 601 of the operation unit 207, showing the destination channel and user confirmed in S809.

[0083] In S812, the CPU 202 detects whether the approver selected on the approver selection screen 1214 has been confirmed via the touch panel 601 of the operation unit 207. If the approver has been confirmed, the process transitions to S813. If the approver has not been confirmed, the process transitions to S812. The method for detecting confirmation is whether the back button 1213 has been selected. Note that in the case of a screen configuration in which the Confirm button is displayed on the screen of the operation unit 207, a similar transition is made when the Confirm button is selected.

[0084] Furthermore, in S811, if the CPU 202 does not detect that the approver selection button 1212 is selected, it may execute the process of S813 with all users on the default state channel or the user of the posting destination selected in S809 as the approver, and in that case, skip the processes of S811 and S812.

[0085] In S813, the CPU 202 determines whether or not the black and white start button 1207 or the color start button 1208 displayed on the operation unit 207 has been selected. If it is determined that the button has been selected, the process proceeds to S814. If not, the process returns to S813.

[0086] In step S814, the CPU 202 controls the reading unit 209 based on the scan settings to read the image of the document and generate image data. The scan settings used are those designated by the user on a detailed setting screen of the scan-to-workflow (not shown).

[0087] In step S815, the CPU 202 converts the image data generated in step S814 into the file format set on the approval setting screen 1217.

[0088] In S816, the CPU 202 generates approval parameters. The approval parameters include the destination channel, approver, file format, file name, approval title, and approval comment. The approver selected in S812 is set as the approver. The file format is set to the file format set in the approval settings. The file name is specified as the file name specified in the approval settings. The approval title is specified as the approval title specified in the approval settings. The approval comment is specified as the approval comment specified in the approval settings.

[0089] In S817, the CPU 202 uses the token information 1303 registered in advance to send the file generated in S815 and the approval parameters generated in S816 to the message application server 400 by the POST method of HTTP communication. By sending this data (the file converted from image data and the approval parameters) to the message application server 400, the message application server 400 controls to create an object of an approval request for the received file. Then, the object is posted to the channel indicated by the received channel information. The approval request will be described later with reference to FIG. 14.

[0090] In S818, the CPU 202 receives the result of the approval request creation from the message application server 400, and displays it on the touch panel 601 of the operation unit 207. According to this embodiment, the user can easily create an approval request with a file attached from the image processing device 101 to a channel of the message application server 400.

[0091] An example of a screen displayed on the operation panel 301 of the mobile terminal 300 by sending the file converted from the image data in the processing of S815 and the approval parameters to the message application server 400 in the processing of S817 will be described with reference to FIG.

[0092] Fig. 14 is a diagram showing an example of a message screen of a message application. A message screen 1401 in Fig. 14 is displayed when the message application is started on the mobile terminal 300 and the process of S815 is executed in the image processing device 101. In addition, the mobile terminal 300 is in communication with the message application server 400.

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

[0094] A message 1403 is an object of an approval request posted by a user having an account of User 3, who has used the image processing apparatus 101 to transmit image data generated by scanning in S815 of FIG. 8 and approval parameters. In the example of FIG. 14, "Channel 1" is specified as the channel 1402 of the posting, and "User 1" belonging to Channel 1 is specified as the approver. The channel 1402 and a message 1403 are also displayed. "Approval of **" is specified as the title 1404 of the approval request of the approval parameters, and "Please approve" is specified as the comment 1405 of the approval request. When a file button 1406 is selected, an image of the transmitted image file is displayed. The file name, the title of the approval, and the comment of the approval request are set by the user on a detailed setting screen of the scan-to-workflow (not shown).

[0095] In the message 1403, the user who has requested approval is displayed as a requester 1407 in order to clearly indicate the user, and the approver before approval is displayed as pending reply 1408 in order to clearly indicate the approver.

[0096] A user designated as an approver can select an approve button 1409, a reject button 1410, or a display details button 1411 from the message application.

[0097] By selecting the Approve button 1409, the approver can execute the approval process. Then, the message 1403 is changed to the message 1412. Specifically, the message "Requested", which indicates that approval is being requested, is changed to "Approved", and the message "Response pending", which indicates that approval has not yet been given, is changed to "Approver", which indicates that approval has been given, and the Approve button 1409 and Reject button 1410 are no longer displayed.

[0098] Similarly, when the reject button 1410 is selected, the approval request is canceled, and the message "Requested" indicating that approval is being requested is changed to "Rejected." Then, "Response pending," indicating that the approver has not yet approved, is changed to "Rejected user," indicating that approval has been granted, and the approve button 1409 and reject button 1410 are no longer displayed.

[0099] When the Show Details button 1411 is selected, details of the current approval status (not shown) are displayed. Specifically, the priority of the approval request, the date and time when approval was requested, etc. are displayed.

[0100] Furthermore, when displaying this screen, the message application server 400 searches for and displays necessary information from the data structure shown in Fig. 15. For example, the posting of the message 1403 corresponds to "approval 1 + user 1 + file g + user 3" in the content of the exchange 1505.

[0101] FIG. 15 is a diagram showing an example of a file structure in the message app server 400. This file structure is stored in the HDD 405 of the message app server 400, and the screen in FIG. 14 is displayed based on this file structure. The message app server 400 has smaller groups such as channels, groups, and user files in the largest group called workspace, and manages data. The channel 1501 is a type of chat room in which all members of the workspace can participate and all posted content can be searched by anyone. The group 1502 is a channel for discussion that should not be made public to all members, and requires an invitation to view and participate. The user 1503 is a user participating in this workspace. The file 1504 stores an attached file. Furthermore, the contents 1505 of the exchange between the channel, group, and user are stored in association with each other. For example, the users participating in the channel 1 are stored in association with the channel 1, and messages and image data exchanged in the channel 1 are also stored in association with the channel 1. By storing the information in this way, when a channel is selected on the channel selection screen 1210, the user corresponding to the specified channel information can be displayed. You can view the users who are participating in that channel.

[0102] In addition, the message application server 400 has a dedicated folder for storing files for each user. A folder may be created in the dedicated folder for each user as folder a 1506, and files such as file a and file b may be stored in a lower level, or files such as file c 1507 may be stored directly in a lower level of the dedicated folder for each user. By appropriately granting access rights to each user's files, other users can access the files by accessing the links to the files.

[0103] By executing the above-mentioned process, it is possible to reduce the effort involved in requesting approval via a chat service for image data generated by a scanning device reading an image of a document. EXAMPLES

[0104] In the first embodiment, an example has been described in which the image processing device 101 directly transmits image data and approval parameters to the message application server 400. In the present embodiment, an example will be described in which the image processing device 101 transmits image data and approval parameters to the message application server 400 via the bot server 500.

[0105] FIG. 9 is a diagram showing an example of a sequence in which the image processing device 101 creates an approval request with a file generated by scanning attached, and transmits the request to the message application server 400 via the bot server 500. In FIG.

[0106] In step S901, the CPU 202 of the image processing device 101 requests the bot server 500 for channel list information by HTTP communication using a device ID or a user ID as a parameter.

[0107] In S902, the CPU 501 of the bot server 500 transmits information indicating a request for channel list information by HTTP communication using token information corresponding to the received device ID or user ID to the message application server 400. This token information is obtained according to the device ID or user ID received in S901.

[0108] In S903, the CPU 401 of the message application server 400 checks whether access to the URL is permitted based on the token information. If access is permitted, channel list information is generated that is included in the workspace corresponding to the token information. The channel list information is array information that indicates channel information. The channel information includes a channel ID, a channel name, information indicating users participating in the channel, and a channel setting value that indicates settings such as whether the channel is an archive channel.

[0109] In S904, the CPU 401 of the message application server 400 controls the communication unit 404 to transmit the channel list information to the bot server 500 as response information of the HTTP communication.

[0110] In S905, the CPU 501 of the bot server 500 transmits the channel list information received in S905 to the image processing device 101 as a response to the HTTP communication.

[0111] The processing in S906 to S912 is similar to the processing in S704 to S710 in FIG. 7, and therefore a description thereof will be omitted.

[0112] In S913, the CPU 202 of the image processing device 101 transmits the device ID or user ID, destination channel information, approval parameters such as the approver, the title of the approval request, and comments on the approval request, and image data to the bot server 500 by HTTP communication.

[0113] In S914, the CPU 501 of the bot server 500 executes a process of transmitting the received destination channel information, approval parameters, image data, and token information corresponding to the received device ID or user ID to the message app server 400. Here, the CPU 501 refers to a table stored in the HDD 505 in which the device ID or user ID is associated with the token information, and determines the token information to be transmitted.

[0114] The process of S915 is similar to that of S712, and therefore the description thereof will be omitted.

[0115] In S916, the CPU 401 of the message application server 400 transmits a result indicating whether the creation of the approval request was successful or not to the bot server 500 as response information of the HTTP communication.

[0116] In S917, the CPU 501 of the bot server 500 transmits a result corresponding to whether the creation of the approval request was successful or not to the image processing device 101 as response information of the HTTP communication. If the creation of the approval request is successful, the CPU 202 of the image processing device 101 may display a notification that the creation of the approval request was successful on the operation unit 207. If the creation of the approval request fails, the CPU 202 of the image processing device 101 may display a notification that the creation of the approval request failed on the operation unit 207. Alternatively, if the creation of the approval request is successful, no notification may be displayed, and only if the creation of the approval request fails, a notification that the creation of the approval request failed may be displayed.

[0117] Fig. 10 is a flowchart showing an example of scan-to-workflow processing. The CPU 202 reads a program stored in the ROM 203 into the RAM 204 and executes it to execute the processing of the flowchart in Fig. 10. The flow in Fig. 10 is started when the image processing device 101 is powered on.

[0118] The processing in S1001 to S1003 is similar to the processing in S801 to S803, and therefore the description thereof will be omitted.

[0119] In S1004, the CPU 202 acquires the user ID of the user logged in to the image processing device 101 or the device ID of the image processing device 101, and transmits a channel information acquisition request and the user ID or device ID to the bot server 500 by HTTP communication.

[0120] The processing in S1005 to S1016 is similar to the processing in S805 to S816, and therefore the description thereof will be omitted.

[0121] In S1017, the CPU 202 transmits to the bot server 500 the user ID of the user logged in to the image processing device 101 or the device ID of the image processing device 101, the file generated in S1015, and the approval parameters generated in S1016.

[0122] The process of S1018 is similar to the process of S818, and therefore the explanation thereof will be omitted.

[0123] Fig. 11(a) is a flowchart showing an example of the process when the bot server 500 obtains ID and channel information from the message application server 400. Fig. 11(b) is a flowchart showing an example of the process when the bot server 500 creates an approval request to the message application server 400. The processes in Fig. 11(a) and (b) are executed by the CPU 501 reading a program stored in the ROM 502 into the RAM 503 and executing it. The flows in Fig. 11(a) and (b) are started when the power of the bot server 500 is turned on.

[0124] First, an example of a process in which the bot server 500 acquires an ID and channel information from the message application server 400 will be described with reference to FIG. 11(a).

[0125] In S1101, the CPU 501 determines whether or not an information acquisition request for acquiring a device ID or a user ID and channel information has been received from the image processing device 101. If it is determined that the request has been received, the process proceeds to S1102. If not, the process returns to S1101.

[0126] In step S1102 , the CPU 501 acquires token information corresponding to the device ID or user ID received from the image processing apparatus 101 .

[0127] In S1103, the CPU 501 determines whether or not there is token information corresponding to the received device ID or user ID. If it is determined that there is token information, the process proceeds to S1104. If not, the process proceeds to S1105. If it is determined that there is token information, the RAM 503 stores token information corresponding to the received device ID or user ID.

[0128] In S1104, the CPU 501 transmits the information acquisition request received from the image processing device 101 in S1101 to the message application server 400 by using the token information identified in S1103. The CPU 501 transmits the information returned from the message application server 400 in response to the transmission to the image processing device 101.

[0129] In S1105, the CPU 501 transmits information indicating an execution error to the image processing apparatus 101 as a response to the request received in S1101.

[0130] Next, an example of a process in which the bot server 500 creates an approval request to the message application server 400, as shown in FIG. 11(b), will be described.

[0131] In S1106, the CPU 501 determines whether or not the device ID or user ID, approval parameters, information indicating the file format, etc., image data, and the creation of an approval request have been received from the image processing device 101. If it is determined that such information has been received, the process proceeds to S1107. If not, the process returns to S1106.

[0132] In step S1107, the CPU 501 executes a process of transmitting to the message application server 400 the received approval parameters, information indicating the file format and the like, image data, and token information corresponding to the received device ID or user ID.

[0133] In S1108, response information to the transmission in S1107 from the message application server 400 is received, and the response information is transmitted to the image processing apparatus 101.

[0134] According to this embodiment, even if the interface specification of the message application server 400 is changed, it is possible to realize this by simply updating the program of the bot server 500 without uploading the program of the image processing device 101. Also, in a workplace with multiple image processing devices, an approval request can be created without setting a token for each image processing device individually.

[0135] In this embodiment, the image processing device 101 performs various communications with the message application server 400 via the bot server 500, but the present invention is not limited to this. For example, all the processes of the bot server 500 in the sequence of FIG. 9 may be performed by an intermediate server that interprets a WebAPI. In this case, the image processing device 101 performs HTTP communication by specifying the URL of the WebAPI in order to transmit an approval request or image data. This intermediate server is also a server related to the chat server. In addition, a general-purpose server that is not dedicated to linking with a chat service may perform all the processes of the bot server 500 in the sequence of FIG. 9.

[0136] <Other embodiments> The present invention can be realized by supplying a program that realizes one or more functions of the above-mentioned embodiments to a system or device via a network or a storage medium. Then, one or more processors in the computer of the system or device can 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]

[0137] 101 Image processing device 400 Message App Server 500 Bot Server 202 CPU 209 Reading unit

Claims

1. A scanning means for scanning an image of an original to generate image data; An acquisition means for acquiring channel information and user information from a chat service; a receiving means for receiving a selection of a channel from the plurality of channels indicated by the acquired channel information and a selection of a user to be an approver from users included in the selected channel; A scanning device comprising a transmitting means for transmitting the generated image data and information of the selected user.

2. 2. The scanning device according to claim 1, wherein the approver is a user who can execute approval processing for an approval request regarding the image data.

3. The receiving means further receives a setting of a priority of the approval request, 3. The scanning device according to claim 2, wherein said transmission means transmits the generated image data, information on the selected user, and information on the set priority.

4. The scanning device according to claim 1, characterized in that the transmitting means transmits the generated image data and information of the selected user to a server related to the chat service, thereby posting an object for performing approval processing to the selected channel.

5. 5. The scanning device according to claim 4, wherein the object includes a button for executing the approval process.

6. 5. The scanning device according to claim 4, wherein the object includes a button for displaying the generated image data.

7. 2. The scanning device according to claim 1, wherein said transmitting means transmits the generated image data, information on the selected user, and information on the selected channel.

8. Further comprising a conveying means, 2. The scanning device according to claim 1, wherein the scanning means reads an image of the document conveyed by the conveying means to generate the image data.

9. a scanning step of scanning an image of an original document to generate image data; an acquisition step of acquiring channel information and user information from a chat service; a receiving step of receiving a selection of a channel from the plurality of channels indicated by the acquired channel information and a selection of a user to be an approver from users included in the selected channel; A scanning method comprising the step of transmitting the generated image data and information of the selected user.

10. a scanning step of scanning an image of an original document to generate image data; an acquisition step of acquiring channel information and user information from a chat service; a receiving step of receiving a selection of a channel from the plurality of channels indicated by the acquired channel information and a selection of a user to be an approver from users included in the selected channel; A program for causing a computer to execute a scanning method, comprising a transmitting step of transmitting the generated image data and information of the selected user.

11. 11. The program according to claim 10, wherein the approver is a user who can execute approval processing for an approval request regarding the image data.

12. The receiving step further includes receiving a setting of a priority of the approval request; 12. The program according to claim 11, wherein said transmission step transmits the generated image data, information about the selected user, and information about the set priority.

13. The program according to claim 10, characterized in that an object for performing approval processing is posted to the selected channel by sending the generated image data and information of the selected user to a server related to the chat service in the transmission process.

14. 14. The program according to claim 13, wherein the object includes a button for executing the approval process.

15. 14. The program according to claim 13, wherein the object includes a button for displaying the generated image data.

16. 11. The program according to claim 10, wherein said transmitting step transmits said generated image data, information about said selected user, and information about said selected channel.

Images