Facsimile apparatus, method of controlling the same, and storage medium

Abstract

To reduce time and effort required when a user transmits data after receiving approval.SOLUTION: According to an aspect of the present disclosure, an image processing apparatus includes an acquisition unit configured to acquire image data, a reception unit configured to receive information corresponding to user information of a user from a chat server that provides a chat service used by the user who has logged in to the image processing apparatus, a posting unit configured to post to a posting destination of the chat service based on the information, and a transmission unit configured to transmit the image data. Wherein the transmission unit transmits the image data based on a fact that there is a reaction to the posted information for requesting the approval.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a facsimile machine, a control method thereof, and a program. [Background technology]

[0002] Image processing devices (multifunction devices) equipped with multiple functions such as facsimile (hereinafter referred to as FAX) and scanner functions are now in use, and are capable of sending and receiving FAXes to and from devices connected via public telephone lines, and sending and receiving data to and from PCs and servers connected via a network. When sending FAXes, various measures have been taken, such as double-checking the recipient's address, to prevent information leaks caused by sending to the wrong recipient.

[0003] In Patent Document 1, a user registers an approver corresponding to a sender of a fax in advance in an image forming device. Also, a system is disclosed in which, when a fax transmission instruction is sent from the sender's terminal to the image forming device, the image forming device sends an approval request for the fax to the approver corresponding to the sender. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-118389 Summary of the Invention [Problem to be solved by the invention]

[0005] In the technology described in Patent Document 1, when a user wants to send a fax after receiving approval, the user needs to register an approver in advance to send an approval request for sending the fax. This problem occurs not only when sending a fax, but also when the user wants to send data after receiving approval.

[0006] The present invention has been made in view of the above-mentioned problems, and aims to reduce the time and effort required when a user transmits data after receiving approval. [Means for solving the problem]

[0007] An image processing device, an acquisition means for acquiring image data; a receiving means for receiving information corresponding to user information of a user who has logged in to the image processing device from a chat server that provides a chat service used by the user; posting means for posting to a posting destination of the chat service based on the information; a transmitting means for transmitting the image data; and the posting means posts information for requesting approval for the transmission means to transmit the image data; The transmitting means transmits the image data based on a response to the posted information for requesting approval. 1. An image processing device comprising: [Effects of the Invention]

[0008] According to the present invention, it is possible to reduce the time and effort required for a user to transmit data after receiving approval. [Brief explanation of the drawings]

[0009] [Figure 1] A diagram showing an example of a system configuration [Figure 2] A diagram showing an example of the configuration of an MFP [Figure 3] FIG. 1 is a diagram illustrating an example of the configuration of a terminal device. [Figure 4] A diagram showing an example of the configuration of a chat server. [Figure 5] An example of user information managed by the chat server. [Figure 6] A sequence diagram showing an example of a process for posting a request for approval of a fax transmission to an approver. [Figure 7] FIG. 10 is a flowchart illustrating an example of a process for sending a fax approval request to a chat server. [Figure 8] Figure showing an example of the screen for setting approvers for fax transmissions [Figure 9] Figure showing an example of a screen for setting default values ​​for a fax job [Figure 10] Figure showing an example of the GUI of a chat application when a request for approval of a fax transmission is posted to the approver [Figure 11] A flowchart showing an example of a process for posting approval requests by grouping threads for each fax destination. [Figure 12] Figure showing an example of the GUI of a chat application when a request for approval of a fax transmission is posted to a channel [Figure 13] A sequence diagram showing an example of a process for posting a request for approval of a fax transmission to a channel. DETAILED DESCRIPTION OF THE INVENTION

[0010] The following describes in detail the embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0011] Example 1 1 is a diagram showing an example of a system configuration of the present invention. In the system configuration of this embodiment, an MFP 200 and a terminal device 300 are connected to a chat server 400 via a network 100 so as to be able to communicate with each other.

[0012] The network 100 of this embodiment may be the Internet or a LAN (Local Area Network), and may be either wired or wireless.

[0013] The MFP (Multi Function Peripheral) 200 has the function of transmitting and receiving image data and is also capable of acquiring image data based on an original document using a reading unit 207. The MFP 200 can receive image data and faxes from, for example, a network 100 such as the Internet or a public line network 110. The MFP 200 in this embodiment refers to an image processing device that also communicates with a chat server 400 via the network 100 and has the function of transmitting and receiving image data. The MFP 200 is also connected to a facsimile device 210 via the public line network 110, and can transmit image data scanned by the MFP 200 to the facsimile device 210 by specifying the telephone number of the facsimile device 210 as the destination. The MFP 200 may also have the function of printing an image based on the image data on a print medium. The MFP 200 can transmit and receive various data and signals. While FIG. 1 shows one MFP 200 connected to the network 100, multiple MFPs 200 may be connected to the network 100.

[0014] Terminal device 300 is a terminal device owned by a fax approver, and is, for example, an electronic device such as a personal computer (PC), a smartphone, or a tablet PC. Terminal device 300 can use a chat service provided by chat server 400, and by displaying information about the chat service on operation unit 305, a user can use the chat service from terminal device 300. Specifically, a user can use the chat service by logging in to the chat service provided by chat server 400 from terminal device 300. In FIG. 1, one terminal device 300 is connected to network 100, but multiple terminal devices 300 may be connected to network 100.

[0015] The chat server 400 is a server that provides a chat service and manages message exchanges (chats) between users who use the terminal devices 300 connected via the network 100. The chat server 400 exchanges information with the terminal devices 300 regarding general processing related to message exchanges, such as sending and receiving processes for messages and displaying messages on a display screen. The chat service is a service that allows users to communicate with each other, and may be, for example, Teams provided by Microsoft or Slack provided by Slack Technologies.

[0016] 2 is a diagram showing an example of the hardware configuration of the MFP 200. The MFP 200 has a CPU 201, ROM 202, RAM 203, storage 204, an operation unit 205, a printing unit 206, a reading unit 207, a communication unit 208, and a FAX communication unit 209. Note that CPU is an abbreviation for Central Processing Unit, ROM is an abbreviation for Read Only Memory, and RAM is an abbreviation for Random Access Memory. Note that each unit is connected to be able to communicate with each other.

[0017] The CPU 201 controls the overall operation of the MFP 200. The CPU 201 loads control programs stored in the ROM 202 or storage 204 into the RAM 203 to perform various types of control, such as reading control and printing control. The ROM 202 stores control programs executable by the CPU 201. The RAM 203 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 202 and storage 204. The storage 204 stores various information, such as an address book, image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 204, but an auxiliary storage device such as an SSD (Solid State Drive) or HDD (Hard Disc Drive) may also be used. An eMMC (Embedded Multi Media Card) may also be used.

[0018] In the MFP 200 of this embodiment, one CPU 201 executes each process shown in the sequence described below using one RAM 203 (memory), but this is not limited to this. For example, multiple CPUs, RAMs, ROMs, and storages can work together to execute each process shown in the flowchart described below. Also, some processes may be executed using hardware circuits such as ASICs and FPGAs.

[0019] The operation unit 205 is, for example, a display unit such as a liquid crystal panel or a touch panel, and an input unit such as buttons or hard keys. The operation unit 205 displays information to the user and detects input from the user. Note that the input from the user detected by the operation unit 205 is transmitted to each unit as an electrical signal.

[0020] A printing unit 206 prints image data (print data) stored in the RAM 203 or storage 204 onto a printing medium (recording paper) fed from a paper feed cassette (not shown).

[0021] The reading unit 207 reads an image of a document, and the CPU 201 converts the image into image data such as binary data. Image data generated based on the image read by the reading unit 207 is sent to an external device or printed on recording paper. The reading unit may have a document table and may be configured to read the document by, for example, a scanner by transporting the document set on the document table. Alternatively, the reading unit may be configured to read the document by photographing it with a camera.

[0022] The communication unit 208 is connected to the network 100 and can send and receive all kinds of data, such as image data, to and from external devices on the network 100. Specifically, the communication unit 208 receives print data from the terminal device 300 and sends data and signals to the chat server 400. Methods for sending and receiving data via the network 100 include sending and receiving using email and sending files using other protocols (for example, FTP, SMB, WEBDAV, etc.). Furthermore, various types of data can be sent and received via the network 100 by accessing from the terminal device 300 via HTTP communication.

[0023] A FAX communication unit 209 is connected to the public line network 110, and transmits and receives FAXes to and from a facsimile device 210 connected via the public line network 110. The FAX communication unit 209 controls a modem and an NCU for facsimile communication (not shown), thereby enabling connection to the public line network 110 and control of the facsimile communication protocol.

[0024] Fig. 3 is a diagram showing an example of the hardware configuration of the terminal device 300. The terminal device 300 has a CPU 301, a ROM 302, a RAM 303, a storage 304, an operation unit 305, and a communication unit 306. Note that each unit is connected to each other so that they can communicate with each other. Note that the configuration shown in Fig. 3 is merely an example, and it is not essential to include all of these units.

[0025] The CPU 301 controls the overall operation of the terminal device 300. The CPU 301 reads out control programs stored in the ROM 302 or storage 304 into the RAM 303 and executes various processes for controlling the operation of the terminal device 300. The ROM 302 stores control programs executable by the CPU 301. The RAM 303 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 302 and storage 304.

[0026] The storage 304 stores all kinds of information such as application data, various programs, image data, various setting information, etc. The storage 304 may be an auxiliary storage device such as an SSD, HDD, or eMMC.

[0027] The operation unit 305 is, for example, a display unit such as a liquid crystal panel or a touch panel, and an input unit such as buttons or hard keys. The operation unit 305 displays information to the user and detects input from the user. Note that the input from the user detected by the operation unit 305 is transmitted to each unit as an electrical signal.

[0028] The communication unit 306 is connected to the network 100 and can send and receive all kinds of data such as image data to and from external devices on the network 100. For example, the communication unit 306 sends and receives image data and data related to chat services to and from the chat server 400.

[0029] 4 is a diagram showing an example of the hardware configuration of chat server 400. Chat server 400 has a CPU 401, a ROM 402, a RAM 403, a HDD 404, and a communication unit 405. Note that each unit is connected to each other so that they can communicate with each other.

[0030] The CPU 401 reads out a control program stored in the ROM 402 or the HDD 404 and executes various processes for controlling the operation of the chat service provided by the chat 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.

[0031] The HDD 404 stores various data such as chat messages and user information of users who use the chat. The communication unit 405 is connected to the network 100 and can transmit and receive all kinds of data to and from external devices such as the MFP 200 and terminal device 300 on the network 100. The communication unit 405 may perform wired communication using, for example, Ethernet (registered trademark), or may perform wireless communication such as Wi-Fi.

[0032] FIG. 5 shows an example of a user information list 500 stored in the HDD 404 of the chat server 400. The user information list 500 stores information about users registered in the chat service provided by the chat server 400 in a corresponding manner. Specifically, the list stores a user ID, information about the channel to which the user belongs on the chat service, an email address to which electronic data is sent to the user, the user ID of the user's superior, and information about the user's department, each associated with the other information. Other information stored in the user information list 500 includes token information, passwords, and other information. The information stored in the user information list 500 is not limited to the above. It may also store information about the user's department, the user's telephone number, information about the channel to which the user's superior belongs, detailed chat service settings, and other information, each associated with the other information. The information about the channel and the department may be stored using an identifiable ID, for example. The user's superior is the user (approver) who approves fax transmissions. The user ID is a unique name used to identify an individual on the chat and is used to specify the destination when posting a chat message and to identify the user who posted the message to the chat. The user information is information that is registered in advance when using the chat service, and it is not necessary to store all of the above items.

[0033] In this embodiment, a channel is a space where multiple users can communicate with each other, and is a space where messages, files, tools, etc. In this embodiment, a channel is described as having multiple users participating, but this is not limited to this.

[0034] Fig. 6 is a sequence diagram showing an example of a process for posting a request for approval of a fax transmission to an approver when the MFP 200 transmits a fax. The sequence in Fig. 6 is started in response to selection of a fax button 802 displayed on a home screen 801 in Fig. 8 (described later).

[0035] In S601, the user inputs a user ID and password for logging in to the chat service provided by chat server 400 to operation unit 205 of MFP 200, and CPU 201 accepts this. In subsequent steps, information acquisition requests to chat server 400 are sent using token information acquired by CPU 201 controlling communication unit 208 to transmit the user ID and password input in S601 to chat server 400. Note that instead of this token information, the user ID and password input by the user in S601 may be used directly for authentication. Also, login information for MFP 200 and login information for the chat service provided by chat server 400 may be stored in storage 204 in advance. In this case, the login information input by the user in S601 is the login information stored in MFP 200 in advance, and in this case, the user proceeds to step S602 without inputting login information for chat server 400. Note that the login information for the chat service refers to a user ID and password or token information.

[0036] In S602, CPU 201 of MFP 200 controls communication unit 208 to transmit the login information and password entered in S601 to chat server 400, and chat server 400 receives them.

[0037] In S603, the CPU 401 of the chat server 400 performs authentication based on the login information and password received in S602. If the authentication is successful, the CPU 401 issues token information required for sending an information acquisition request to the chat server 400, and controls the communication unit 405 to transmit the token information to the MFP 200. The MFP 200 receives this.

[0038] In S604, the user inputs the telephone number of the facsimile machine 210 to be the destination of the FAX into the operation unit 205 of the MFP 200, and the CPU 201 of the MFP 200 accepts this.

[0039] In S605, when the user presses the approver setting button 810 to display the approver setting screen 812 for setting a fax approver, the CPU 201 of the MFP 200 accepts this as an instruction to display the approver setting screen 812.

[0040] In S606, CPU 201 of MFP 200 controls communication unit 208 to transmit an instruction to chat server 400 via HTTP communication requesting user information, and chat server 400 receives the instruction. Specifically, CPU 201 controls communication unit 208 to transmit an instruction to chat server 400 requesting information about users with whom the user indicated by the token information acquired in S603 can chat. In the user information request, CPU 201 may transmit a request to acquire all users with whom the user logged in in S601 can chat, or may transmit a request to acquire user information corresponding to a user designated by the user. Note that all users with whom the user can chat refer to users corresponding to other user information stored in HDD 404 of chat server 400 in association with the user information of the user logged in to the chat service. The users designated by the user can be designated by specifying conditions, such as limiting the users to only superiors, in approver group field 911 on the button setting screen shown in FIG. 9 . If the user has set the system to limit users to superiors only, the CPU 201 controls the communication unit 208 to send a request to the chat server 400 indicating that information on users registered as superiors of the user who logged in in S606 is to be obtained.

[0041] In S607, the CPU 401 of the chat server 400 checks whether access to the chat service is permitted based on the token information attached to the user information request received in S606 and the user information list 500. If access is permitted, the CPU 401 of the chat server 400 searches for users with whom the user indicated by the token information can chat, based on the user information list 500, in accordance with the user information request. Note that if the request received in S606 is for all users with whom the logged-in user can chat, all users are searched for, and if the request is for a user specified by the user, the specified user is searched for. The CPU 401 controls the communication unit 405 to send the user information of the relevant user obtained by the search to the MFP 200 as response information for the HTTP communication. The MFP 200 receives this.

[0042] In S608, the CPU 201 of the MFP 200 displays an approver setting screen 812 on the operation unit 205 based on the user information received in S607, and waits for a user operation. The approver setting screen 812 will be described later with reference to FIG.

[0043] In S609, when the user selects a user (approver) to be the approver on the approver setting screen 812 displayed on the operation unit 205, the CPU 201 of the MFP 200 accepts this and determines the user to whom the approval request is to be sent.

[0044] In S610, when the user presses the start button 811, the CPU 201 of the MFP 200 receives an instruction to start FAX transmission via the operation unit 205.

[0045] In S611, the CPU 201 of the MFP 200 controls the reading unit 207 to scan the document and generate image data. It is assumed that the user has placed the document on the reading unit 207 and completed the settings used for general FAX transmission before executing this step. General settings include, for example, destination settings, density settings, image quality mode settings, and scan mode settings.

[0046] In S612, CPU 201 of MFP 200 controls communication unit 208 to transmit information to chat server 400 instructing the user to post an approval request message to the approver selected by the user in S609. That is, CPU 201 posts the approval request message to the approver selected by the user in S609. The approval request message includes a message requesting approval for the FAX transmission, the telephone number of facsimile device 210 as the transmission destination entered in S604, and the image data generated in S611. Note that it is not essential that the approval request message include the image data generated in S611. Note that the approval request message is an example of information for requesting approval to send image data.

[0047] In S613, CPU 401 of chat server 400 posts the message received in S612 to a chat room of the chat service. The chat room to which the message is posted is the chat room corresponding to the user information of the approver selected by the user in S609. CPU 401 controls communication unit 405 to send the thread ID of the posted thread to MFP 200, and MFP 200 receives it.

[0048] In S614, CPU 201 of MFP 200 controls communication unit 208 to check the approval status of the approval request posted in S612. Specifically, CPU 201 controls communication unit 208 to send to chat server 400 a message acquisition request instructing acquisition of a message posted in the thread corresponding to the thread ID received in S613, along with the thread ID. Chat server 400 receives this. Note that this process may be performed multiple times by CPU 201. For example, it may be repeated until a message is posted in the thread posted by CPU 401 in S612. Alternatively, the process of this step may be performed every time a fixed time elapses, or a fixed number of times.

[0049] In S615, the CPU 401 of the chat server 400 checks whether there is a message (response) posted to the thread indicated by the thread ID attached to the message acquisition request received in S614. If there is a message posted to the thread indicated by the received thread ID, the CPU 401 controls the communication unit 405 to transmit the message posted to the thread indicated by the received thread ID to the MFP 200. The MFP 200 receives this.

[0050] In S616, the CPU 201 of the MFP 200 analyzes the message received in S615 and determines whether or not the message is a message approving the FAX transmission. The determination of whether or not the message is a message approving the FAX transmission will be described in the description of FIG.

[0051] In S617, the CPU 201 of the MFP 200 controls the FAX communication unit 209 to send the image data scanned in S611 by FAX to the facsimile device 210 corresponding to the telephone number entered by the user in S604. Note that this process is performed if it is determined that the message received in S616 is a message approving the FAX transmission, and is not performed if it is determined that the message is not a message approving the FAX transmission.

[0052] Fig. 7 is a flowchart showing an example of a process in which MFP 200 posts a request for approval of a fax transmission to an approver when the MFP 200 sends a fax. The process of this flowchart is executed by CPU 201 of MFP 200 reading a program stored in ROM 202 into RAM 203. The flow of Fig. 7 is started when the power of MFP 200 is turned on.

[0053] In S701, the CPU 201 determines whether or not the user has selected the fax button 802. If the CPU 201 determines that the fax button 802 has been selected, the process proceeds to S702. If not, the CPU 201 waits until it determines that the fax button 802 has been selected.

[0054] In step S702, the CPU 201 causes the operation unit 205 to display the fax screen 803.

[0055] In S703, the user inputs a destination address to which the fax is to be sent on the fax screen 803, and when the CPU 201 detects that the destination address has been input, it displays the destination address information in the destination address display field 804. The destination address may be set, for example, by inputting a telephone number using the numeric keypad 807 displayed on the fax screen 803, or by selecting the destination address from an address book that is displayed when the address book button 809 is selected.

[0056] In step S704, the CPU 201 detects that the user has selected the approver setting button 810 to display the approver setting screen 812 for selecting an approver for the FAX transmission.

[0057] In S705, CPU 201 logs in to the chat service provided by chat server 400 using login information for the chat service stored in advance in MFP 200. Specifically, CPU 201 controls communication unit 208 to transmit the login information for the chat service to chat server 400. Upon receiving the login information, chat server 400 performs authentication based on the login information transmitted by CPU 201, and if the authentication is successful, CPU 201 can log in to the chat service. Note that CPU 401 of chat server 400 performs this authentication based on user information list 500. If login to chat server 400 is successful, CPU 201 receives token information transmitted from chat server 400. Note that if login information is not stored in advance in MFP 200, CPU 201 causes operation unit 205 to display a login screen in S705, and logs in to chat server 400 using the user ID and password input by the user.

[0058] In S706, CPU 201 determines whether login to the chat service was successful. Specifically, CPU 201 determines that login was successful if it receives token information from chat server 400 in response to the login information sent in S705. On the other hand, CPU 201 determines that login was not successful if the status code in the HTTP communication response is an error or if the body information of the response contains a parameter indicating that information cannot be acquired. If CPU 201 determines that login was successful, it proceeds to S705; otherwise, it proceeds to S720.

[0059] In S720, the CPU 201 causes the operation unit 205 to display the fax screen 803, and causes the fax screen 803 to display information indicating that login to the chat service has failed, and then returns to S705.

[0060] In S707, CPU 201 controls communication unit 208 to use the token information received in S705 to send information to chat server 400 indicating a request for user information via HTTP communication. At this time, chat server 400 searches for users with whom the user indicated by the token information can chat in accordance with the user information request, and sends the user information of the relevant users obtained by the search to MFP 200. MFP 200 receives this. At this time, CPU 401 of chat server 400 performs the search based on user information list 500.

[0061] If an approver is designated by the user, chat server 400 transmits user information corresponding to the designated approver to MFP 200. Therefore, in this step, MFP 200 receives the user information transmitted from chat server 400. Note that all users available for chatting refer to users corresponding to other user information stored in HDD 404 of chat server 400 in association with the user information of the user who has logged in to the chat service.

[0062] In S708, CPU 201 determines whether or not user information has been received from chat server 400 in response to the user information request sent in S707. Specifically, CPU 201 determines that user information has been received if it has been received from chat server 400. On the other hand, CPU 201 determines that user 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 user information cannot be acquired. If CPU 201 determines that user information has been received, the process proceeds to S709; otherwise, the process proceeds to S721.

[0063] In step S721, the CPU 201 causes the operation unit 205 to display the approver setting screen 812, and causes information indicating that the user information could not be received to be displayed on the approver setting screen 812. At this time, the approver setting screen 812 does not display options for users who will become approvers.

[0064] In S722, the CPU 201 determines whether or not the back button 813 has been selected. If the CPU 201 determines that the back button 813 has been selected, the process returns to S705, and if not, the CPU 201 waits until it determines that the back button 813 has been selected.

[0065] In S709, CPU 201 displays user list 814 based on the user information received from chat server 400 on approver setting screen 812 displayed on operation unit 205, waits for a user selection, and detects and accepts the selection when a selection is made. That is, CPU 201 accepts the posting destination to which the approval request message is to be posted.

[0066] In S710, the CPU 201 determines whether or not the user has selected a user to be the approver on the approver setting screen 812. If the CPU 201 determines that a user to be the approver has been selected, the process proceeds to S711; otherwise, the process waits until a user to be the approver is selected.

[0067] Selection detection is performed based on whether or not any of the lists displayed on the approver setting screen 812 is selected. Note that in the case of a screen configuration in which a Confirm button is displayed on the screen of the operation unit 205, the same transition occurs even when the Confirm button is pressed with any of the lists selected.

[0068] In S711, the CPU 201 determines whether or not the start button 811 displayed on the operation unit 205 has been selected. If the CPU 201 determines that the start button 811 has been selected, the process proceeds to S712; otherwise, the CPU 201 waits until the start button 811 is selected. Note that the start button is not limited to the start button 811 displayed on the fax screen 803, and may be, for example, a start button displayed on the approver setting screen 812, or a hard key provided on the operation unit 205.

[0069] In S712, the CPU 201 controls the reading unit 207 to read the original document and generate image data. It is assumed that the user has placed the original document on the reading unit 207 and completed general fax settings before executing this step. General fax settings include, for example, destination settings, density settings, image quality mode settings, and scan mode settings. It is also possible to use image data stored in the storage 204, in which case this step is unnecessary.

[0070] In S713, CPU 201 transmits a message posting request to chat server 400, instructing the user selected by the user in S710 to post an approval request message. The approval request message includes a message requesting approval for the FAX transmission, the destination information entered in S703, and the image data generated in S712. Note that the approval request message does not necessarily include the image data generated in S611. At this time, if chat server 400 succeeds in posting the message, CPU 201 receives information indicating the result of the message posting transmitted from chat server 400. Specifically, if chat server 400 succeeds in posting the message, CPU 201 receives information indicating the success of the message posting.

[0071] In this process, one thread is created for each fax job, but if a thread already exists in which a message has been posted regarding approval of a fax transmission to the same destination as the destination entered in S703, the message may be posted in addition to the existing thread.

[0072] In S714, CPU 201 determines whether or not it has received information from chat server 400 indicating that the message posting was successful in response to the message posting request sent in S713. Specifically, CPU 201 determines that the message posting was successful if it has received the thread ID of the thread to which the message was posted or if the status code in the HTTP communication response indicates success. On the other hand, CPU 201 determines that the message posting failed if the received status code is an error or if the body information of the response contains a parameter indicating that the message posting failed. If CPU 201 determines that the message posting was successful, it proceeds to S715; otherwise, it proceeds to S723.

[0073] In S723, the CPU 201 causes the operation unit 205 to display on the fax screen 803 information indicating that the approval request message could not be posted to the designated approver, and then returns to S713.

[0074] In S715, CPU 201 controls communication unit 208 to use the thread ID received in S714 to send information indicating a request for messages posted to the thread posted via HTTP communication to chat server 400. Note that CPU 201 may also use the token information received in S706 to send information to chat server 400 via HTTP communication indicating a request for only messages posted by the approver's user account, among the messages posted to the chat room.

[0075] At this time, in accordance with the request from CPU 200 of MFP 200, CPU 401 of chat server 400 controls communication unit 405 to transmit the corresponding message to MFP 200. MFP 200 receives this message.

[0076] In S716, the CPU 201 determines whether the message received in S715 contains a keyword related to approving or denying the fax transmission. Keywords related to approval are, for example, character strings such as "I approve," "No problem," or "OK." Keywords related to denial are, for example, character strings such as "I deny," "There is a problem," or "NG." The keywords are set in advance by the user. Note that these examples are examples of character strings indicating approval and character strings indicating denial. These keywords related to approval or denial are stored, for example, in the storage 204 of the MFP 200. The CPU 201 determines whether the message received in S715 contains a keyword related to approving or denial of the fax transmission based on the keyword set by the user. If the CPU 201 determines that the message contains a keyword related to approval or denial, the process proceeds to S717; otherwise, the process returns to S715.

[0077] In S717, CPU 201 determines whether the message received in S715 contains a keyword related to approval. This determination is made by CPU 201 based on a keyword set by the user, similar to S716, to determine whether the message contains a keyword related to approval of the fax transmission. It is clear from the processing of the previous step, S716, that the message contains either a keyword related to approval or denial, and that if the message does not contain a keyword related to approval, it contains a keyword related to denial. In other words, if the message contains a keyword related to denial, CPU 201 determines "denial" in this step. If CPU 201 determines that the message contains a keyword related to approval, the process proceeds to S718; if it determines that the message does not contain a keyword related to approval, the process proceeds to S724.

[0078] In step S724, the CPU 201 cancels the FAX transmission and deletes the FAX job.

[0079] In S718, the CPU 201 controls the FAX communication unit 209 to send the image data generated by reading the document in S712 by FAX via the public line network 110 to the facsimile machine 210 corresponding to the telephone number entered by the user in S703.

[0080] In S719, CPU 201 displays the fax transmission result on operation unit 205. At this time, CPU 201 transmits to chat server 400 a message posting request instructing the chat server 400 to post a message regarding the fax transmission result in S718 or S724. The content of the message to be posted may be, for example, "Fax transmission successful" or "Fax transmission failed."

[0081] Fig. 11 is a flowchart showing an example of processing for grouping approval threads by fax destination. The processing of this flowchart is executed by CPU 201 of MFP 200 reading a program stored in ROM 202 into RAM 203. The flow of Fig. 11 is started when step S712 in Fig. 7 ends. In other words, this processing is processing for the second or subsequent times when a fax is sent to the same destination two or more times.

[0082] In S1101, the CPU 201 determines whether a thread for approving a fax to be sent to the fax destination input by the user in S703 already exists. That is, the CPU 201 determines whether a thread requesting approval for the same fax transmission destination already exists. Specifically, the CPU 201 acquires thread information for the posting destination received in S709 from the chat server 400 and determines whether a message in each thread includes an approval request for the same destination as the destination input in S703. Note that the thread information includes not only the thread ID but also the contents of the messages that make up the thread, and at least the thread ID and the message contents correspond to each other. Note that this determination may be performed in another manner, such as by storing the thread ID and the destination received in S715 based on the posting request sent in S713 in association with each other in the storage 204, and determining whether a thread ID corresponding to the fax transmission destination is stored.

[0083] If CPU 201 determines that a thread requesting approval for the same fax transmission destination exists, the process proceeds to step S1102; on the other hand, if CPU 201 determines that a thread requesting approval for the same fax transmission destination does not exist, the process proceeds to step S1105.

[0084] In S1102, the CPU 201 identifies the thread ID of a thread requesting approval for the same destination acquired in S1101. Specifically, the CPU 201 compares the fax transmission destination input in S703 with the thread information acquired in S1101, searches for messages containing the same phone number, and identifies the thread ID corresponding to the message.

[0085] In S1103, CPU 201 controls communication unit 208 to send a message reply request to chat server 400, using the token information acquired in S705, instructing the reply of a message to the thread having the thread ID identified in S1102. Similar to the message reply request sent in S713, the message reply request includes a message requesting approval for the FAX transmission, the destination information entered in S703, and the image data generated in S712. At this time, if the message reply based on the message reply request to chat server 400 is successful, CPU 201 receives information indicating the success of the message reply request sent by chat server 400.

[0086] In S1105, CPU 201 controls communication unit 208 to send a message posting request to chat server 400, instructing the message to be posted to the posting destination accepted in S709, requesting approval for the FAX transmission. The message posting request includes a message requesting approval for the FAX transmission, the destination information entered in S703, and the image data generated in S712. If the message posting is successful, CPU 201 receives information indicating the success of the message posting sent by chat server 400, and the thread ID.

[0087] In S1104, CPU 201 determines whether the message reply or posting from chat server 400 was successful in response to the message reply request sent in S1103 or the message posting request sent in S1105. Specifically, CPU 201 determines that the message reply or posting was successful if the status code in the HTTP communication response indicates success or if a thread ID is received. On the other hand, CPU 201 determines that the message reply or posting failed if the received status code is an error or if the body information of the response contains a parameter indicating that the message reply or posting failed. If CPU 201 determines that the message reply or posting was successful, proceed to S1107; otherwise, proceed to S1106.

[0088] In S1106, the CPU 201 causes the operation unit 205 to display on the fax screen 803 information indicating that the approval request message could not be replied to or posted, and then returns to S1101.

[0089] In S1107, CPU 201 controls communication unit 208 to send to chat server 400, using the thread ID received in S714, information indicating a request for messages posted to the thread posted via HTTP communication. Note that CPU 201 may also use the token information received in S706 to send to chat server 400, via HTTP communication, information indicating a request for only messages posted by the approver's user account, of the messages posted to the chat room. At this time, in accordance with the request from CPU 200 of MFP 200, CPU 401 of chat server 400 controls communication unit 405 to send the relevant messages to MFP 200. MFP 200 receives this.

[0090] In S1108, the CPU 201 determines whether the message received in S1107 includes a keyword related to approval or denial of the fax transmission. Keywords related to approval are, for example, character strings such as "I approve," "There's no problem," or "OK," while keywords related to denial are, for example, character strings such as "I deny," "There's a problem," or "NG," and the keywords are set in advance by the user. These keywords related to approval or denial are stored, for example, in the storage 204 of the MFP 200. The CPU 201 determines whether the message received in S715 includes a keyword related to approval or denial of the fax transmission based on the keyword set by the user.

[0091] Note that when an approver posts a message containing a keyword related to approval or denial, the approver may be configured to specify the fax job to be approved or denied by attaching an identifier for identifying the fax job, such as the job ID of the fax job, to the message. If CPU 201 determines that the message contains a keyword related to approval or denial, it proceeds to step S1109; otherwise, it returns to step S1107.

[0092] In S1109, CPU 201 determines whether the message received in S1107 contains a keyword related to approval. As in S716, CPU 201 determines whether the message contains a keyword related to approval of the fax transmission based on a keyword set by the user. It is clear from the processing of the previous step, S1108, that the message contains either an approval or denial keyword, and that if the message does not contain an approval keyword, it contains a denial keyword. In other words, if the message contains a denial keyword, CPU 201 determines "denial" in this step. If CPU 201 determines that the message contains an approval keyword, the process proceeds to S1110; if it determines that the message does not contain an approval keyword, the process proceeds to S1112.

[0093] In step S1112, the CPU 201 cancels the FAX transmission and deletes the FAX job.

[0094] In S1110, the CPU 201 controls the FAX communication unit 209 to send the image data generated by reading the document in S712 via the public line network 110 by FAX to the facsimile machine 210 corresponding to the telephone number entered by the user in S703.

[0095] In S1111, CPU 201 displays the fax transmission result on operation unit 205. At this time, CPU 201 transmits to chat server 400 a message posting request instructing chat server 400 to post a message regarding the fax transmission result in S1110 or S1112. The content of the message to be posted may be, for example, "Fax transmission successful" or "Fax transmission failed."

[0096] FIG. 8 shows an example of screen transitions displayed on the operation unit 205 when the user selects an approver for FAX transmission.

[0097] Home screen 801 is a general screen for the user to select a function to be executed on MFP 200, and is an example of a screen that is displayed on operation unit 205 when power is turned on to MFP 200. When fax button 802 displayed on home screen 801 is selected, fax screen 803 is displayed on operation unit 205.

[0098] The fax screen 803 is a screen for the user to input a fax destination when sending a fax, and to call up a screen for making various settings, which will be described later.

[0099] The destination display field 804 displays destination information such as the telephone number entered as the fax destination and the registered name registered in the address book. The number of destinations field 808 displays the number of destinations set.

[0100] When the numeric keypad button 805 is selected, a numeric keypad 807 for inputting a telephone number is displayed. The user can set the destination by inputting the telephone number corresponding to the facsimile device 210 to which the FAX is to be sent using the displayed numeric keypad (software keys).

[0101] When the transmission setting button 806 is selected, the screen transitions and a transmission setting screen 819 is displayed on the operation unit 205. On the transmission setting screen 819, it is possible to set the resolution and density of image data to be transmitted by FAX, double-sided scanning settings of the document, and the like.

[0102] When the address book button 809 is selected, telephone numbers registered in the address book of the MFP 200 are displayed so that they can be selected. The user can set a destination for fax transmission by selecting a displayed telephone number.

[0103] When the approver setting button 810 is selected, the screen transitions, and an approver setting screen 812 is displayed on the operation unit 205. A user list 814 is displayed on the approver setting screen 812. The user list 814 is displayed based on user information received by the MFP 200 from the chat server 400. For example, if User A logs in to the chat server 400 and specifies a condition in the approver group field 911 to limit approvers to only superiors, the user list 814 displays the user IDs registered on the chat server 400 as User A's superiors. Here, User X and User Y indicate the user accounts of the users who are superiors of User A. On the approver setting screen 812, the user can select users to be approvers for the fax transmission from the displayed user list 814. A check mark or the like indicating this is displayed in the list of users who have been selected as approvers, making the selected users identifiable. If a user who is an approver is selected again, the user is removed from the approver list, and the check mark indicating the approver is hidden. At this time, a mark other than a check mark may be displayed, or the selected users may be made identifiable by changing the color of the list. The number of users currently selected as approvers is displayed in the approver count field 816. When the back button 813 is selected, the screen transitions and the fax screen 803 is displayed on the operation unit 205. During this screen transition, the approver selection at the time the back button 813 was selected is retained. When the back button 813 is selected, a message such as "Do you want to keep your selection?" may be displayed along with options, and the approver selection may not be retained depending on the user's selection.

[0104] When start button 811 is selected, CPU 201 of MFP 200 starts scanning the document and transmits the generated (acquired) image data and the destination information displayed in destination display field 804 to chat server 400. Note that the same processing is executed regardless of whether start button 811 is selected (pressed) on fax screen 803, transmission setting screen 819, or approver setting screen 812. Note that start button 811 may be controlled so that it cannot be pressed unless at least one approver has been selected, or it may be possible to select an approver without selecting an approver. If start button 811 is pressed without selecting an approver, the configuration may be such that fax transmission is immediately executed without sending an approval request to the chat server, or an error message may be displayed.

[0105] 13, a channel can be selected as the destination of the approval request, and an approval request can be posted to the channel. In this case, user list 814 is displayed based on the channel information that MFP 200 receives from chat server 400. For example, user list 814 displays the channels in which the user participates, such as ChA, ChB, etc. Also, approver number column 816 displays the number of channels currently selected as approvers.

[0106] 9 is a diagram showing an example of a button setting screen for setting default values ​​for a FAX job executed by the FAX button 802. The button setting screen can be used by accessing a button setting page provided by the MFP 200 from the browser 901. Note that a configuration may also be adopted in which a user who has authority to set buttons logs in to the MFP 200, and the CPU 201 causes the operation unit 205 to display the button setting screen, thereby allowing the user to set the buttons.

[0107] The login user field 902 displays the user ID of the user who is logged in to the MFP 200 to configure button settings from a browser. To configure button settings, a user with administrator privileges for the MFP 200 or a general user with authority to configure button settings logs in to the MFP 200.

[0108] When the logout button 903 is selected, a process for logging out the user who is logged in to the MFP 200 is performed, and a screen indicating that the user has been logged out from the MFP 200 is displayed on the browser 901 .

[0109] In the approval setting function field 906, it is possible to select whether to enable or disable the function of requesting approval for fax transmission using chat. For example, if the user sets this to "enabled," the start button 811 cannot be selected unless at least one approver is set on the approver setting screen 812. On the other hand, if the user sets this to "disabled," the start button 811 may be selectable without setting an approver, or the approver setting button 810 may be hidden so that the start button 811 can be selected without setting an approver. This function is an example of a setting acceptance that accepts from the user a setting as to whether or not to request approval.

[0110] In the linked service selection field 907, a chat service for posting a message requesting user information and approval of a FAX transmission by the MFP 200 can be selected. The linked service selection field 907 displays a list of chat services that support the MFP 200's processes for obtaining user information and posting a message, and the user can post an approval request to the desired chat service by selecting one of them.

[0111] In the login ID field 908 and login password field 909, the user can enter a login ID and password for logging in to the chat service selected in the linked service selection field 907.

[0112] In the message body field 910, a standard message to be used when posting an approval request to the chat service can be set. In the approver group field 911, extraction conditions for users to be displayed on the approver setting screen 812 are set. For example, if "Superior" is set, only users who are the superiors of the fax sender are displayed in the user list 814 on the approver setting screen 812 from the user information acquired from the chat server 400. In addition, the user may set the approver group field 911 to extract only users who belong to a specified department or to extract only users who belong to a specified channel. Note that only when the approval setting function field 906 before sending is set to "Enabled", the fields 907 to 911 for setting the sending of the approval request are displayed as configurable fields.

[0113] The resolution field 912, density field 913, and double-sided original field 914 are fax transmission settings, and it is possible to set values ​​that are initially displayed on the transmission setting screen 819. In addition to these, it is also possible to set general parameters used in fax transmission, and the set parameters are similarly reflected as values ​​that are initially displayed on the transmission setting screen 819.

[0114] When the OK button 904 is selected, the setting values ​​set on this button setting screen at that time are stored in the storage 204. When the cancel button 905 is selected, the settings set on this button setting screen are cleared and the button setting is terminated.

[0115] 10 is a diagram showing an example of a screen in which chat server 400 receives an approval request sent from MFP 200 and the posted message is displayed in a chat application running on terminal device 300. That is, Fig. 10 is a diagram showing an example of the GUI of the chat application when a request for approval of a FAX transmission is posted to the approver.

[0116] A chat application screen 1001 is displayed on the operation unit 305 of the terminal device 300. A login user ID field 1002 displays the user ID of the user who has logged in to the chat server. A user selection field 1003 displays a list of user IDs of users with whom messages and files can be exchanged via chat, and the user can select a desired user to start exchanging messages and files via chat with the selected user. Specifically, a chat room with the user selected by the user is displayed, and the user can post messages and files there to exchange chat messages with the selected user.

[0117] The destination user display field 1004 displays the user ID selected in the user selection field 1003. In other words, this indicates that the chat room with that person is displayed. The chat field 1005 displays chat exchanges between the user (UserX) displayed in the destination user display field 1004 and the user (UserA) currently logged in to the chat application.

[0118] Thread 1006 is a thread that compiles message exchanges on a specific topic. In this embodiment, one thread is created for each FAX job, but threads may also be compiled for each FAX destination.

[0119] Thread 1006 in Fig. 10 is an example of approval exchange when UserX is selected as the approver. Thread 1006 contains approval request body 1007 posted from MFP 200, image data preview 1009, and link 1008 to the image data file. Thread 1006 also contains a message exchange consisting of a reply message 1010 from the approver (UserX) in response to the approval request message, and a message 1011 of the fax transmission result. The link to the image data file indicates the location of the file (image data).

[0120] The main text 1007 is an affiliate message set by the user in the main text field 910 on the button setting screen. In the main text 1007, "@" indicates that the user listed after this mark is being mentioned. By adding this, the approver will be able to easily notice the message, for example, even if the approver has some chat service notifications turned off. In this embodiment, a mention of the user selected by the user on the approver setting screen 812 is automatically incorporated into the main text. Note that mentioning is not essential.

[0121] The link 1008 to the image data file is a link to the image data file based on the image data acquired by the scan executed by selecting the start button 811. The image data preview 1009 is a preview image based on the image data acquired by the scan executed by selecting the start button 811.

[0122] The reply message 1010 is a message posted in the chat room by the approver user in response to the approval request message, and is a message indicating approval such as "I approve," "OK," or "No problem." If there is a problem with the fax content, the approver posts a message indicating denial such as "I reject," "NG," or "There is a problem" as reply message 1010.

[0123] The FAX transmission result message 1011 is a message indicating the result of the FAX transmission carried out in accordance with the contents of the reply message 1010, and if successful, a message such as "FAX transmission successful" is posted, and if unsuccessful, a message such as "FAX transmission failed" is posted.

[0124] A message input field 1012 is an input field for inputting a message when sending a message to the thread 1006. A new post button 1013 is a button selected when creating a new thread.

[0125] Instead of the user ID, a display name corresponding to the user ID, such as a nickname registered by the user, may be displayed.

[0126] <Example 2> In the first embodiment, a method for posting an approval request message in the approver's chat room is described. In the second embodiment, a method for posting an approval request message in a channel is described.

[0127] FIG. 13 is a sequence diagram showing an example of a process in which a user selects a channel for exchanging messages on a specific topic as a destination of an approval request, and posts an approval request for sending a fax to the channel.

[0128] In S1301, the user inputs a user ID and password for logging in to the chat service provided by chat server 400 to operation unit 205 of MFP 200, and CPU 201 accepts this. In subsequent steps, information acquisition requests to chat server 400 are made using token information acquired by CPU 201 controlling communication unit 208 to transmit the user ID and password input in S1301 to chat server 400. Note that instead of this token information, the user ID and password input by the user in S1301 may be used directly for authentication. Also, login information for MFP 200 and login information for the chat service provided by chat server 400 may be stored in storage 204 in advance. In this case, the login information input by the user in S1301 uses login information previously stored in MFP 200, and in this case, the user proceeds to step S1302 without inputting login information for chat server 400.

[0129] In S1302, CPU 201 of MFP 200 controls communication unit 208 to transmit the login information and password entered in S1301 to chat server 400, and chat server 400 receives them.

[0130] In S1303, CPU 401 of chat server 400 performs authentication based on the login information and password received in S1302. If authentication is successful, CPU 401 issues token information required for making an information acquisition request to chat server 400, and controls communication unit 405 to transmit the token information to MFP 200. MFP 200 receives this. In S1304, the user inputs the telephone number of facsimile machine 210 to be the fax destination into operation unit 205 of MFP 200, and CPU 201 of MFP 200 accepts this.

[0131] In S1305, when the user presses the approver setting button 810 to display the approver setting screen 812 for setting a fax approver, the CPU 201 of the MFP 200 accepts this as an instruction to display the approver setting screen 812.

[0132] In S1306, CPU 201 of MFP 200 controls communication unit 208 to transmit an instruction to chat server 400 via HTTP communication requesting channel information, which is received by chat server 400. Specifically, CPU 201 causes chat server 400 to transmit an instruction requesting information on the channel in which the user indicated by the token information acquired in S1303 is participating.

[0133] In S1307, CPU 401 of chat server 400 checks whether access to the chat service is permitted based on the token information attached to the channel information request received in S1306. If access is permitted, CPU 401 of chat server 400 searches for a channel in which the user indicated by the token information is participating, in accordance with the channel information request. CPU 401 controls communication unit 405 to transmit channel information of the corresponding channel obtained by the search to MFP 200 as response information of the HTTP communication. MFP 200 receives this.

[0134] In S1308, the CPU 201 of the MFP 200 displays the approver setting screen 812 on the operation unit 205 based on the channel information received in S1307, and waits for a user operation.

[0135] In step S1309, when the user selects a channel to which the user wants to post on the approver setting screen 812 displayed on the operation unit 205, the CPU 201 of the MFP 200 accepts this and determines the user to whom the approval request is to be sent. Typically, the channel selected by the user here is a channel in which the approver participates in addition to the user.

[0136] In S1310, when the user presses the start button 811, the CPU 201 of the MFP 200 receives an instruction to start FAX transmission via the operation unit 205.

[0137] In S1311, the CPU 201 of the MFP 200 controls the reading unit 207 to scan the document and generate image data. It is assumed that the user has placed the document on the reading unit 207 and completed general fax settings before executing this step. General fax settings include, for example, destination settings, density settings, image quality mode settings, and scan mode settings.

[0138] In S1312, CPU 201 of MFP 200 controls communication unit 208 to send information to chat server 400 instructing the user to post a message requesting approval to the channel selected by the user in S1309. The message includes a message requesting approval for the FAX transmission, the telephone number of facsimile device 210 as the destination input in S1304, and the image data generated in S1311. Note that it is not essential that the message include the image data generated in S1311.

[0139] In S1313, CPU 401 of chat server 400 posts the message received in S1312 to a channel of the chat service. The channel to which the message is posted is the channel selected by the user in S1309. CPU 401 controls communication unit 405 to transmit the thread ID of the posted thread to MFP 200, and MFP 200 receives it.

[0140] In S1314, CPU 201 of MFP 200 controls communication unit 208 to check the approval status of the approval request posted in S1312. Specifically, CPU 201 controls communication unit 208 to send to chat server 400 a message acquisition request instructing acquisition of a message posted in the thread corresponding to the thread ID received in S1313, along with the thread ID. Chat server 400 receives this. Note that this process may be performed multiple times by CPU 201. For example, it may be repeated until a message is posted in the thread posted by CPU 401 in S1312. Alternatively, the process of this step may be performed every time a fixed time elapses, or a fixed number of times.

[0141] In S1315, CPU 401 of chat server 400 checks whether there is a message (response) posted to the thread indicated by the thread ID attached to the message acquisition request received in S1314. If there is a message posted to the thread indicated by the received thread ID, CPU 401 controls communication unit 405 to transmit the message posted to the thread indicated by the received thread ID to MFP 200. MFP 200 receives this.

[0142] In step S1316, the CPU 201 of the MFP 200 analyzes the message received in step S1315 and determines whether or not the message is a message approving fax transmission. The determination of whether or not the message is a message approving fax transmission will be described in connection with FIG.

[0143] In S1317, CPU 201 of MFP 200 controls FAX communication unit 209 to send the image data scanned in S1311 by FAX to facsimile device 210 corresponding to the telephone number entered by the user in S1304. Note that this process is performed if it is determined that the message received in S1316 is a message approving the FAX transmission, and is not performed if it is determined that the message is not a message approving the FAX transmission.

[0144] FIG. 7 is a flowchart showing an example of a process in which the MFP 200 posts a request for approval of a FAX transmission to an approver when the MFP 200 transmits a FAX.

[0145] The processing of this flowchart is executed by the CPU 201 of the MFP 200 reading a program stored in the ROM 202 into the RAM 203. The flow of Fig. 7 is started when the power of the MFP 200 is turned on.

[0146] In the second embodiment, the approval request message is posted to a channel, unlike the first embodiment in which the approval request message is posted to the approver's chat room. The following describes the differences from the first embodiment.

[0147] S701 to S706 and S720 in the second embodiment are the same as those in the first embodiment, and therefore the description thereof will be omitted.

[0148] In S707, CPU 201 controls communication unit 208 to use the token information received in S705 to send information indicating a request for channel information via HTTP communication to chat server 400. At this time, chat server 400 searches for channels in which the user indicated by the token information is participating in accordance with the request for channel information, and sends the channel information of the channels obtained by the search to MFP 200. MFP 200 receives this. At this time, CPU 401 of chat server 400 performs the search based on user information list 500.

[0149] If a channel is specified by the user, chat server 400 transmits channel information corresponding to the specified channel to MFP 200. Therefore, in this step, MFP 200 receives the channel information transmitted from chat server 400. Note that MFP 200 may be configured to receive both user information and channel information.

[0150] In S708, CPU 201 determines whether or not channel information has been received from chat server 400 in response to the request for channel information sent in S707. Specifically, CPU 201 determines that channel information has been received if it has been received from chat server 400. On the other hand, CPU 201 determines that channel 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 contains a parameter indicating that channel information cannot be obtained. If CPU 201 determines that channel information has been received, the process proceeds to S709; otherwise, the process proceeds to S721.

[0151] In S721, the CPU 201 causes the operation unit 205 to display the approver setting screen 812, and causes information indicating that the channel information could not be received to be displayed on the approver setting screen 812. At this time, the approver setting screen 812 does not display options for users who will become approvers.

[0152] S722 in the second embodiment is the same as in the first embodiment, and therefore the explanation will be omitted.

[0153] In S709, CPU 201 displays user list 814 based on the channel information received from chat server 400 on approver setting screen 812 displayed on operation unit 205, waits for a user selection, and detects and accepts the selection when a selection is made. That is, CPU 201 accepts the posting destination to which the approval request message is to be posted.

[0154] In S710, the CPU 201 determines whether or not the user has selected a channel to which the approval request message is to be posted on the approver setting screen 812. If the CPU 201 determines that a channel has been selected, the process proceeds to S711; otherwise, the process waits until a channel is selected.

[0155] Selection detection is performed based on whether or not any of the lists displayed on the approver setting screen 812 is selected. Note that in the case of a screen configuration in which a Confirm button is displayed on the screen of the operation unit 205, the same transition occurs even when the Confirm button is pressed with any of the lists selected.

[0156] S711 and S712 in the second embodiment are the same as those in the first embodiment, and therefore the description thereof will be omitted.

[0157] In S713, CPU 201 transmits a message posting request to chat server 400, instructing the chat server 400 to post an approval request message to the channel selected by the user in S710. The approval request message includes a message requesting approval for the FAX transmission, the destination information entered in S703, and the image data generated in S712. Note that the approval request message does not necessarily include the image data generated in S611. At this time, if chat server 400 successfully posts the message, CPU 201 receives information indicating the result of the message posting transmitted from chat server 400. Specifically, if chat server 400 successfully posts the message, CPU 201 receives information indicating the success of the message posting.

[0158] In this process, one thread is created for each fax job, but if a thread already exists in which a message has been posted regarding approval of a fax transmission to the same destination as the destination entered in S703, the message may be posted in addition to the existing thread.

[0159] S714 in the second embodiment is the same as in the first embodiment, and therefore the explanation will be omitted.

[0160] In S723, the CPU 201 causes the operation unit 205 to display on the fax screen 803 information indicating that the approval request message could not be posted to the specified channel or to the specified channel, and then returns to S713.

[0161] The processing from S715 onward in the second embodiment is the same as that in the first embodiment, and therefore a description thereof will be omitted.

[0162] FIG. 12 shows an example of a screen in which the chat server 400 receives an approval request sent from the MFP 200 and a message posted to a channel, not to a user, is displayed in a chat application running on the terminal device 300.

[0163] A chat application screen 1201 is displayed on the operation unit 305 of the terminal device 300. A login user ID field 1202 displays the user ID of the user who has logged in to the chat server. A user selection field 1203 displays a list of user IDs of users with whom messages and files can be exchanged via chat, and by selecting a desired user, the user can start exchanging messages and files via chat with the selected user. Specifically, a chat room with the user selected by the user is displayed, and by posting messages and files there, the user can exchange chat messages with the other user.

[0164] The channel selection field 1214 displays a list of channel names for channels that allow messages and files to be exchanged via chat. When a user selects a desired channel, exchange of messages and files via chat begins between members participating in the selected channel. Specifically, a chat room for the channel selected by the user is displayed, and by posting messages and files there, the user can exchange chat messages with other users participating in the channel.

[0165] The destination channel display field 1204 displays the name of the channel selected in the channel selection field 1214. In other words, this indicates that the chat room of that channel is being displayed. The participating members field 1215 displays the number of users participating in the channel displayed in the destination channel display field 1204. The chat field 1205 displays chat exchanges that have taken place in the channel (ChA) displayed in the destination channel display field 1204.

[0166] Thread 1206 is a thread that compiles message exchanges on a specific topic. In this embodiment, one thread is created for each FAX job, but threads may also be compiled for each FAX destination.

[0167] Thread 1206 in Fig. 12 is an example of approval exchange taking place on ChA. Thread 1206 contains approval request body 1207 posted from MFP 200, image data preview 1209, and link 1208 to the image data file. Thread 1206 also contains a message exchange consisting of a reply message 1210 from a member (UserX) participating in ChA in response to the approval request message, and a FAX transmission result message 1211.

[0168] The body 1207 is an affiliate message set by the user in the body field 910 of the button setting screen. In the body 1207, "@" indicates that the user listed after this mark is being mentioned. By adding this, the approver will be able to receive notifications even if they have turned off some of the chat service notifications, making it easier for the approver to notice the message. In this embodiment, mentions of all users belonging to the channel selected by the user on the approver setting screen 812 are automatically incorporated into the body. Note that mentioning is not required. Furthermore, the approver may be able to specify a channel and specific users participating in that channel on the approver setting screen 812, and mention those users individually.

[0169] The link 1208 to the image data file is a link to the image data file based on the image data acquired by the scan executed by selecting the start button 811. The image data preview 1209 is a preview image based on the image data acquired by the scan executed by selecting the start button 811.

[0170] The reply message 1210 is a message posted in the chat room by the approver user in response to the approval request message, and is a message indicating approval such as "I approve," "OK," or "No problem." If there is a problem with the fax content, the approver posts a message indicating denial such as "I reject," "NG," or "There is a problem" as reply message 1210.

[0171] The FAX transmission result message 1211 is a message indicating the result of the FAX transmission carried out according to the contents of the reply message 1210, and if successful, a message such as "FAX transmission successful" is posted, and if unsuccessful, a message such as "FAX transmission failed" is posted.

[0172] A message input field 1212 is an input field for inputting a message when sending a message to the thread 1206. A new post button 1213 is a button selected when creating a new thread.

[0173] With the configuration described above, it is possible to reduce the effort required to send a fax based on approval of the fax transmission.

[0174] The approver's message (reply message 1010) described in this embodiment may be replaced with a specific reaction function. For example, a thumbs-up reaction, an OK stamp, or the like may be set in the same way as keywords related to approval, and if such a reaction is received in response to the approval request message, it is determined to be approval, and a fax transmission may be executed. These reactions are symbols that give the impression of approval, and may be a thumbs-up symbol, an OK stamp, a circular symbol, a smiling symbol, a green symbol, or the like. The approval request message may also be in the form of an object such as a button, and the CPU 201 may post a button labeled "Approve" or "Deny," and the approver may specify the object to determine whether to approve or deny, and a fax transmission may be executed.

[0175] In this embodiment, a method for acquiring user information of a specific user has been described using Fig. 6, and a method for acquiring channel information of a channel to which the user belongs has been described using Fig. 13, but a configuration in which both user information and channel information are acquired is also possible. With such a configuration, users and channels are displayed in user list 814 based on the acquired information, increasing the number of targets from which the user can select as destinations for posting approval request messages, making it easier for the user to select an arbitrary posting destination.

[0176] In this embodiment, an example in which an approval request message is posted to one chat room is shown. However, a configuration in which a user can select multiple posting destinations and the approval request message is posted to multiple chat rooms by selecting multiple posting destinations may be used. In this case, the approval or denial of the approver who responded first may be used as the basis for the fax transmission. Alternatively, the decision may be made after all approvers have responded, or based on the collected approvals and denials. Determining based on the collected approvals and denials means, for example, setting a condition in advance, such as when a majority of approvers have responded, and determining approval when the majority of replies indicate approval when that condition is met.

[0177] In this embodiment, the fax transmission is executed by determining "approval" based on the content of the message returned in response to the approval request message, but the present invention is not limited to this. For example, if a reply is received in response to a posted approval request message, the reply may be determined to be approval regardless of the content of the reply, and a fax may be transmitted.

[0178] The method of transmission is not limited to fax, and the present invention can also be used in other cases, such as sending image data by email.

[0179] <Other Examples> The present invention can also 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 having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

Claims

1. An image processing device, an acquisition means for acquiring image data; a receiving means for receiving information corresponding to user information of a user who has logged in to the image processing device from a chat server that provides a chat service used by the user; posting means for posting to a posting destination of the chat service based on the information; a transmitting means for transmitting the image data; and the posting means posts information for requesting approval for the transmission means to transmit the image data; The transmitting means transmits the image data based on a response to the posted information for requesting approval.

1. An image processing device comprising:

2. 2. The image processing device according to claim 1, wherein the transmitting means transmits the image data based on a response to the posted information requesting approval being an indication of approval.

3. 3. The image processing device according to claim 2, wherein the indication of approval is a character string registered in the image processing device by the user, and the reply is a character string including the character string indicating approval.

4. 3. The image processing device according to claim 2, wherein the indication of approval is a symbol that uses a function of the chat service and gives an impression of approval.

5. 5. The image processing device according to claim 4, wherein the symbol giving the impression of approval is a thumbs-up symbol.

6. 5. The image processing apparatus according to claim 4, wherein the symbol that gives the impression of approval is a symbol that includes a character string of "OK."

7. 2. The image processing device according to claim 1, wherein the transmitting means does not transmit the image data if the response to the posted information requesting approval is a denial.

8. Further comprising a receiving means, the accepting means accepts from the user a designation of a posting destination based on the information received by the receiving means, the designation being a posting destination of the information for which approval is to be requested; 2. The image processing apparatus according to claim 1, wherein the posting means posts the information for requesting approval to the designated posting destination.

9. 2. The image processing apparatus according to claim 1, wherein the information is user information corresponding to an approver.

10. 2. The image processing apparatus according to claim 1, wherein the information is channel information of a channel in which the user participates.

11. The image processing device according to claim 1 , wherein the information for requesting approval includes a message.

12. 2. The image processing device according to claim 1, wherein the information for requesting approval includes image data.

13. 2. The image processing apparatus according to claim 1, wherein the information for requesting approval includes information indicating the location of the image data.

14. The image processing device according to claim 11 , wherein the information for requesting approval further includes an object for reacting to the message.

15. 2. The image processing apparatus according to claim 1, wherein the information for requesting approval includes information on a destination of the image data.

16. The method further includes a setting receiving means for receiving a setting from the user as to whether or not to request approval, 2. The image processing apparatus according to claim 1, wherein, when the setting accepting means accepts a setting that does not request approval, the sending means sends the image data without the posting means making the post.

17. 17. A program for causing a computer to execute each of the means of the image processing apparatus according to claim 1.

18. A method for transmitting image data, comprising: an acquisition step of acquiring the image data; a receiving step of receiving information corresponding to user information of a user logged in to the image processing device from a chat server that provides a chat service used by the user; a posting step of posting to a posting destination of the chat service based on the information; a transmitting step of transmitting the image data; and the posting step posts information for requesting approval to transmit the image data in the transmitting step, The transmitting step transmits the image data based on a response to the posted information for requesting approval.

10. A method for transmitting image data, comprising:

Images