Information processing system, image processing apparatus, method for controlling information processing system, method for controlling image processing apparatus, and program

Abstract

To allow an image processing apparatus to instruct deletion of a post made on a chat service from the image processing apparatus.SOLUTION: An information processing system includes a multifunction peripheral (MFP) 110 that is an image processing apparatus comprising a scanner, a chat server 130 that provides a chat service, and an MFP cooperation server 120 that is a cooperation server relaying communication between the MFP 110 and the chat server 130. The MFP 110 transmits a post request for posting a file of a scanned image to the chat service, manages the transmission history of transmission of the post request and identifiers for identifying posts issued by the chat server 130 in association with each other, and when receiving an instruction to delete a post, transmits a request for deleting the post together with an identifier corresponding to the post. The chat server 130 transmits an identifier to the MFP 110 that has transmitted the post request, and deletes the post corresponding to the identifier in response to the deletion request from the MFP.SELECTED DRAWING: Figure 18

Description

[Technical field]

[0001] The present invention relates to an information processing system, an image processing apparatus, a control method for an information processing system, a control method for an image processing apparatus, and a program. [Background technology]

[0002] The use of chat services in business is on the rise to improve the efficiency of telecommuting and teamwork. Chat rooms in chat services are divided into channels for different topics. Users can select a desired channel to post a chat. Patent Document 1 discloses that an image processing device transmits image data generated by scanning an image of a document to a chat server that provides a chat service. By specifying a destination channel from the image processing device and transmitting the scanned image to the chat server, the image data is uploaded to the chat room of the specified channel of the chat service and shared. [Prior art documents] [Patent documents]

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

[0004] However, in Patent Document 1, when a user realizes after transmission that he / she scanned the wrong document or sent to the wrong channel, the data that has been posted to the chat service cannot be deleted from the image processing device.

[0005] It is an object of the present invention to enable an instruction to delete a post made from an image processing device to a chat service from the image processing device. [Means for solving the problem]

[0006] In order to solve the above problem, the information processing system of the present invention is an information processing system including an image processing device equipped with a scanner, a chat server providing a chat service, and an interworking server relaying communication between the image processing device and the chat server, wherein the image processing device is equipped with a first transmission means for transmitting a posting request to post a file of a scanned image generated by scanning with the image processing device to the chat service, a management means for associating and managing a transmission history of the sending of the posting request with an identifier that uniquely identifies the post issued by the chat server, and a second transmission means for transmitting a request to delete the post together with the identifier corresponding to the post when an instruction to delete the post is received, and the chat server is equipped with an issuing means for posting the file based on the posting request from the image processing device and issuing an identifier that uniquely identifies the post, a transmitting means for transmitting the identifier to a source of the posting, and a deletion means for deleting the post corresponding to the identifier in response to the deletion request from the image processing device. Effect of the Invention

[0007] According to the present invention, it is possible to instruct from the image processing device to delete a post made from the image processing device to a chat service. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an overall configuration of an image processing system. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of an MFP. [Diagram 3] 2 is a diagram illustrating the hardware configuration of an MFP collaboration server, a chat server, and a client PC. [Figure 4] FIG. 2 is a diagram illustrating a software configuration of the image processing system. [Diagram 5] FIG. 11 is a sequence diagram showing the flow of a scan image posting process. [Figure 6] FIG. 13 illustrates an example of a login screen. [Figure 7]FIG. 13 is a diagram illustrating an example of a home screen. [Figure 8] FIG. 11 is a diagram illustrating an example of setting information of an application. [Figure 9] FIG. 4 is a diagram illustrating an example of user information. [Figure 10] FIG. 13 is a diagram illustrating an example of a scan screen. [Figure 11] FIG. 13 is a diagram illustrating an example of a chat screen. [Figure 12] FIG. 13 is a diagram illustrating an example of a chat screen. [Figure 13] FIG. 13 is a diagram illustrating an example of a chat screen. [Figure 14] FIG. 4 illustrates an example of a job history. [Figure 15] FIG. 13 is a diagram illustrating an example of an access authorization setting screen. [Figure 16] 13 is a flowchart showing a process of posting a scanned image. [Figure 17] 13 is a flowchart showing a process of posting a scanned image. [Figure 18] FIG. 11 is a sequence diagram showing the flow of a post deletion process. [Figure 19] FIG. 13 illustrates an example of a history screen. [Figure 20] FIG. 13 illustrates an example of a history screen. [Figure 21] FIG. 13 illustrates an example of a history screen. [Figure 22] FIG. 13 illustrates an example of a history screen. [Figure 23] 13 is a flowchart showing a post deletion process. [Figure 24] 13 is a flowchart showing a post deletion process in the MFP 110. [Diagram 25] 13 is a flowchart showing a posting deletion process in MFP linked server 120. [Figure 26] FIG. 11 is a sequence diagram showing the flow of a chatbot account registration process. [Figure 27] FIG. 13 is a diagram illustrating an example of connection information of a chatbot. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) FIG. 1 is a diagram showing an overall configuration of an information processing system according to the present embodiment. The information processing system includes a multifunction peripheral (MFP) 110, an MFP cooperation server 120, and a chat server 130. The information processing system may also include a client PC 111. The MFP 110, the client PC 111, the MFP cooperation server 120, and the chat server 130 are communicatively connected to each other via a network 100. For example, the MFP 110 and the client PC 111 are communicatively connected to various servers that provide various services on the Internet via a local area network (LAN). Note that the network 100 may be configured to transmit and receive data, and may be any communication method. For example, the network 100 may be configured to be a LAN, a WAN, a cellular network such as LTE or 5G, a wireless network, a telephone line, a dedicated digital line, or a combination of these.

[0010] MFP 110 is an example of an image processing device having a scan function and a posting function. MFP 110 has multiple functions such as a print function and a BOX storage function in addition to the scan function. MFP 110 is connected to network 100 and can communicate with external devices on network 100. Note that MFP 110 of the present embodiment communicates with chat server 130 via MFP cooperation server 120. MFP 110 of the present embodiment has an additional application that can send and post a scanned image to a chat service provided by chat server 130. MFP 110 transmits a request to post a file of the scanned image or a message to chat server 130 via MFP cooperation server 120. MFP 110 also transmits a request to delete a post posted from MFP 110 to chat server 130 via MFP cooperation server 120.

[0011] The client PC 111 is an information processing device that can receive cloud services via the network 100. The client PC 111 may be a desktop terminal, or a mobile terminal such as a notebook computer, a tablet, or a smartphone. The client PC 111 uses a chat service provided by the chat server 130 via a web browser, for example, and displays a chat screen (talk room).

[0012] MFP cooperation server 120 is an information processing device that provides an MFP cooperation service. As part of the MFP cooperation service, MFP cooperation server 120 provides a service of transferring information acquired from MFP 110 to a server that provides another service. MFP cooperation server 120 of the present embodiment relays communication between MFP 110 and chat server 130. For example, MFP cooperation server 120 receives a request to post a scanned image file or the like from MFP 110 and transfers it to chat server 130. Furthermore, MFP cooperation server 120 receives a request to delete a post from MFP 110 and transfers it to chat server 130. Furthermore, MFP cooperation server 120 transfers a response received from chat server 130 to MFP 110. The MFP cooperation service is, for example, a cloud service. Note that MFP cooperation server 120 may be realized by one or more information processing devices, a virtual machine (cloud service) using resources provided by a data center including information processing devices, or a combination of these.

[0013] Chat server 130 is an information processing device that provides a chat service. As a chat service, chat server 130 displays file data and character string information transmitted via network 100, and shares information in response to a request from a web browser of client PC 111. In this embodiment, chat server 130 displays images and the like transmitted from MFP 110 via MFP linkage server 120 on a chat screen. The chat service is a cloud service or collaboration service. Chat server 130 may be realized by one or more information processing devices, a virtual machine (cloud service) using resources provided by a data center including information processing devices, or a combination of these.

[0014] The information processing system of this embodiment is configured to include MFP 110, client PC 111, MFP link server 120, and chat server 130, but is not limited to this. For example, MFP 110 may also serve as both client PC 111 and MFP link server 120. Furthermore, MFP link server 120 and chat server 130 may be located on a LAN rather than on the Internet. Furthermore, MFP link server 120 and chat server 130 do not have to be independent services.

[0015] 2 is a diagram showing the hardware configuration of the MFP 110. The MFP 110 has a control unit 210, an operation unit 220, a printer 221, and a scanner 222. The control unit 210 controls the overall operation of the MFP 110. The control unit 210 has a CPU 211, a ROM 212, a RAM 212, a HDD 214, an operation unit I / F 215, a printer I / F 216, a scanner I / F 217, and a network I / F 218.

[0016] The CPU 211 reads out a control program stored in the ROM 212 or the HDD 214 and executes various control processes of the MFP 110. The ROM 212 stores a program executed by the CPU 211. The control by the CPU 211 includes the execution of a program for realizing a flowchart described later. The RAM 212 is used as a temporary storage area such as a main memory or a work area of ​​the CPU 211. The HDD 214 is a storage device that stores image data, various programs, and various setting information. The MFP 110 may include other storage devices such as an SSD (Solid State Drive) as a storage device. In this embodiment, one CPU 211 executes each process shown in a flowchart described later using one memory (RAM 213 or HDD 214), but this is not limited to this. For example, each process may be executed by cooperating multiple CPUs and multiple RAMs or HDDs.

[0017] The operation unit I / F 215 connects the operation unit 220 and the control unit 210. The operation unit 220 includes, for example, a display unit having a touch panel function and various hard keys. By associating input coordinates and display coordinates on the touch panel, it is possible to configure a GUI that makes it appear as if the user can directly operate the screen displayed on the touch panel. Note that touch operations on the touch panel include operations using a human finger and operations using a touch pen. The operation unit 220 functions as a display unit that displays information to the user and a reception unit that receives instructions from the user.

[0018] The printer I / F 216 connects the printer 221 and the control unit 210. The printer 221 prints the document read by the reader or the image data stored in the HDD 214 on a recording medium (for example, on a sheet of paper). The printer 221 also prints the image data based on a print job. The image data printed by the printer 221 is transferred from the control unit 210 to the printer 221 via the printer I / F 216. The scanner I / F 217 connects the scanner 222 and the control unit 210. The scanner 222 reads a document set on a document tray or an ADF (Auto Document Feeder) and generates image data. The generated image data is input to the control unit 210 via the scanner I / F 217. The image data generated by the scanner 222 can be printed by the printer 221 (copy output), saved in the HDD 214, or transmitted to an external device such as the MFP linkage server 120 via the network 100 by file transmission, e-mail transmission, or the like. In this embodiment, an example in which the MFP 110 has a printing function and a scanning function has been described, but the MFP 110 only needs to have a scanning function.

[0019] The network I / F 218 is a communication interface that connects the MFP 110 and the network 100. For example, a network cable is connected to the network I / F 218 of the MFP 110, and the MFP 110 can communicate with an external device on the network 100. The MFP 110 uses the network I / F 219 to transmit and receive image data and information to each service on the Internet. Note that, in this embodiment, it is assumed that the network I / F 218 is a communication interface that performs wired communication, but this is not limited to this. For example, the network I / F 218 may be a wireless communication interface. Note that the hardware configuration of the MFP 110 described above is an example, and the MFP 110 may include other configurations as necessary, or may not include some of the configurations.

[0020] 3 is a diagram showing an example of the hardware configuration of MFP collaborative server 120. Chat server 130 and client PC 111 also have the same hardware configuration as MFP collaborative server 120. MFP collaborative server 120 includes control unit 310. Control unit 310 includes CPU 311, ROM 312, RAM 312, HDD 314, and network I / F 315. Client PC 111 may also include operation unit 317. If client PC 111 includes operation unit 317, control unit 310 includes operation unit I / F 316 for connecting to operation unit 317.

[0021] CPU (Central Processing Unit) 311 controls the entire MFP linked server 120. CPU 311 reads out control programs stored in ROM 312 or HDD 314 and executes various control processes. Control by CPU 311 includes execution of programs for implementing flowcharts described below. ROM (Read Only Memory) 312 is a memory dedicated to reading data, and stores, for example, the basic control program of MFP linked server 120. RAM (Random Access Memory) 312 is a memory from / to which data can be read and written, and is used as a temporary storage area such as a work area for CPU 311.

[0022] HDD (Hard Disk Drive) 314 stores various data and programs. In this embodiment, an example in which MFP collaborative server 120 includes HDD 314 as a storage device will be described, but this is not limited thereto, and other storage devices such as an SSD or a disk drive into which external media is loaded may also be included. Network I / F 315 connects MFP collaborative server 120 to network 100. MFP collaborative server 120 transmits and receives various information to and from external devices on network 100 via network I / F 315 and network 100. MFP collaborative server 120 receives various processing requests from external devices via network I / F 315, and returns processing results according to the requests.

[0023] Furthermore, the client PC 111 has an operation unit I / F 316 and an operation unit 317. The operation unit I / F 316 is an interface that connects the operation unit 317 and the control unit 310. The operation unit 317 has, for example, a keyboard, a pointing device, a display, etc. The operation unit 317 functions as a display unit that displays information to the user and a reception unit that receives instructions from the user.

[0024] 4 is a diagram showing the software configuration of the information processing system. In the following, the functions of each device in the information processing system will be described focusing on functions related to the process of sending an image scanned by MFP 110 to chat server 130 via MFP link server 120 and the process of deleting a post from MFP 110.

[0025] First, the function modules of the MFP 110 will be described. The MFP 110 has a native function module 410 and an additional function module 420. The native function module 410 is an application that is provided as standard in the MFP 110. The additional function module 420 is an application (hereinafter, referred to as an additional application) that is additionally installed in the MFP 110. The additional function module 420 is, for example, an application based on Java (registered trademark), and can easily realize the addition of functions to the MFP 110. Note that other additional applications (not shown) may be installed in the MFP 110. The software modules of the MFP 110 are realized by the CPU 211 of the MFP 110 executing a program stored in a memory (ROM 212 or HDD 214).

[0026] The native function module 410 has a scan execution unit 411 and a scan image management unit 412. The scan execution unit 411 executes a scan process by the scanner 222 based on an instruction from the scan execution unit 411, and generates scan image data. The scan image management unit 412 saves the scan image data generated by the scan process by the scan execution unit 411 in the HDD 214 and manages it.

[0027] The additional function module 420 has a display control unit 421, a scan control unit 422, a cooperation service request unit 423, an image processing unit 424, and a data management unit 425. The display control unit 421 controls the display on the operation unit 220. The display control unit 421 displays a user interface screen (UI screen) for accepting various user operations, for example, on the touch panel of the operation unit 220. The various user operations include, for example, input of login authentication information, scan settings, setting of destination information, setting of scan file attribute information, a scan start instruction, a transmission instruction, and the like.

[0028] The scan control unit 422 instructs the scan execution unit 411 of the native function module 410 to execute a scan process together with scan setting information in response to a user operation (e.g., pressing a scan start button) performed on the UI screen. The scan execution unit 411, in accordance with the instruction to execute a scan process from the scan control unit 422, causes the scanner 222 to execute a reading operation of a document or the like via the scanner I / F 217, and generates scan image data. The generated scan image data is stored in the HDD 214 by the scan image management unit 412.

[0029] When saving scanned image data in HDD 214, scanned image management unit 412 issues a scanned image identifier that uniquely identifies the scanned image data to be saved, and saves the scanned image data in association with the scanned image data. Then, scanned image management unit 412 notifies scan control unit 422 of information about the scanned image identifier. The scanned image identifier is a number, symbol, alphabet, or the like for uniquely identifying an image scanned by MFP 110. For example, scan control unit 422 obtains scanned image data to be converted into a file from scanned image management unit 412 using the scanned image identifier, and converts the data into a file in image processing unit 424. Then, it instructs cooperation service request unit 423 to make a request to MFP cooperation server 120 for processing required for file transmission.

[0030] Linked service request unit 423 makes various processing requests to MFP collaboration server 120 and receives the responses. The various processing requests to MFP collaboration server 120 include, for example, a request to obtain settings for additional applications and transmission of scanned image data files. In this embodiment, linked service request unit 423 also transmits a request for posting to a chat service and a request for deleting a post to chat server 130 to MFP collaboration server 120, which relays communication. That is, linked service request unit 423 also functions as a transmission means (first transmission means) that transmits a request for posting to the chat service and a transmission means (second transmission means) that transmits a deletion request to the chat service. For example, a communication protocol such as REST or SOAP is used for communication between MFP 110 and MFP collaboration server 120.

[0031] Image processing unit 424 performs predetermined image processing on scanned image data and generates attributes, including a transmission destination and a file name, used on a UI screen displayed by display control unit 421. Data management unit 425 manages data used within MFP 110, such as acquiring information stored in HDD 214, and storing setting information and transmission result information received from MFP link server 120 via link service request unit 423 in HDD 214. Information managed by data management unit 425 includes, for example, logged-in user information, setting information for additional applications, and job history.

[0032] Next, it will be described how MFP collaborative server 120 has a software configuration. MFP collaborative server 120 has a request control unit 431, an external server access unit 432, a data management unit 433, and a display control unit 434. Request control unit 431 waits in a state in which it can receive a request from an external device such as MFP 110, and instructs external server access unit 432 and data management unit 433 to execute a predetermined process according to the content of the received request.

[0033] External server access unit 432 makes a processing request to chat server 130. In the cloud service, various interfaces are made public for sending data such as files and messages to chat server 130 using protocols such as REST and SOAP, and for acquiring information on the chat service. External server access unit 432 makes a request to chat server 130 using the published interfaces.

[0034] Data management unit 433 holds and manages user information and various setting data managed by MFP linked server 120. Display control unit 434 receives a request from a web browser running on MFP 110 or client PC 111 connected via the Internet, and returns screen configuration information (HTML, CSS, etc.) required for screen display. A user can check user information registered in MFP linked server 120 and change settings related to scan settings and transmission information via a screen displayed by the web browser.

[0035] Next, the software configuration of chat server 130 will be described. Chat server 130 has request control unit 441, data management unit 442, and display control unit 443. Request control unit 441 receives a request from an external device, issues instructions to data management unit 442 according to the request, and returns a response according to the request to the sender of the request. Request control unit 441 of the present embodiment waits in a state in which it can receive a request from MFP linkage server 120, and instructs data management unit 442 to save messages and files and read data managed by chat server 130 according to the request. Then, request control unit 441 returns the result of processing according to the request as a response to the sender of the request. If the request is a post, an identifier that uniquely identifies the post issued by data management unit 442 is included in the response. That is, request control unit 441 also functions as a transmission unit that transmits an identifier that uniquely identifies the post to the sender of the post.

[0036] Based on instructions from request control unit 441, data management unit 442 posts and saves messages and files, and reads and deletes data managed by chat server 130. That is, data management unit 442 functions as a posting unit that posts messages and files and issues an identifier that uniquely identifies the posting. Data management unit 442 also functions as a deleting unit that deletes postings. Display control unit 443 receives a request from a web browser running on MFP 110 or client PC 111 connected via the Internet, and returns screen configuration information (HTML, CSS, etc.) required for screen display. A user can obtain saved files and check messages via a screen displayed on the web browser.

[0037] 5 is a sequence diagram showing the flow of scanned image posting processing in which an image scanned by MFP 110 is converted into a file and sent to a chat service. Here, the description will focus on interactions between each device in the information processing system. Each process executed by MFP 110 is realized by CPU 211 of MFP 110 executing a program stored in memory (ROM 212 or HDD 214). Each process executed by MFP cooperation server 120 is realized by CPU 311 of MFP cooperation server 120 executing a program stored in memory (ROM 312 or HDD 314). Each process executed by chat server 130 is realized by CPU 311 of chat server 130 executing a program stored in memory (ROM 312 or HDD 314).

[0038] In S501, if the MFP 110 is set to require authentication by the user when used, the MFP 110 displays a login screen. Fig. 6 is a diagram showing an example of the login screen. The login screen 600 is a screen for acquiring information for performing user authentication. If a combination of a user name and a password is used for user authentication, the login screen 600 displays a user name input area 601 and a password input area 602 for inputting user information, and a login button 603. The login screen 600 may also display a status history button 604. The status history button 604 is a button for displaying the status and history of jobs being executed or completed by the MFP 110.

[0039] In S502, on login screen 600, user 10 inputs a user name registered in MFP 110 into user name input area 601 and a password into password input area 602, and presses login button 603. As a result, MFP 110 detects the user's pressing of login button 603 in S502. In S503, MFP 110 performs user authentication. MFP 110 verifies whether the combination of user name and password entered by the user matches the combination of user name and password registered in HDD 214 of MFP 110. Note that, although an example of verification using user information registered in MPF ​​110 has been described in this embodiment, the verification process may be executed by MFP linkage server 120. When user authentication is performed by MFP linkage server 120, MFP linkage server 120 verifies the user name and password transmitted from MFP 110 to MFP linkage server 120, and returns the result to MFP 110. User authentication using user information may be performed using other commonly known methods (Basic authentication, Digest authentication, authorization using OAuth, etc.) User authentication using an IC card or biometric authentication may also be performed.

[0040] If the user authentication is successful, in S504, the MFP 110 displays a home screen on which buttons for implementing functions provided by the MFP 110 are arranged. FIG. 7 is a diagram showing an example of the home screen. On the home screen 700, buttons for implementing functions provided by the MFP 110 are displayed. For example, on the home screen 700, a copy button 702, a scan button 706, a setting menu button 707, and a scan-to-chat button 703 are displayed. In addition, on the home screen 700, a user display 701 for displaying the name of a logged-in user, a status history button 604, and buttons corresponding to additional applications (for example, a scan-to-chat button 704 and a scan-to-chat button 705) may be displayed. When the user display 701 is pressed, the MFP 110 displays a menu that allows the selection of editing user information, logout, and the like. The user A displayed on the user display 701 in FIG. 7 corresponds to the user 10 in FIG. 5.

[0041] The copy button 702, the scan button 706, and the setting menu button 707 are buttons for starting the native functions of the MFP 110. The copy button 702 is a button for starting the copy function. The scan button 706 is a button for starting the scan function. The setting menu button 707 is a button for configuring settings of the MFP 110. The scan to chat buttons 703 to 705 are buttons for starting additional applications installed in the MFP 110. The scan to chat button 703 is a button for starting an application for transmitting a scanned image to chat service A. Similarly, the scan to chat button 704 is a button for starting an application for transmitting a scanned image to chat service B. The scan to chat button 705 is a button for starting an application for transmitting a scanned image to chat service C.

[0042] In S505, user 10 presses scan-to-chat button 703 displayed on home screen 700. As a result, in S505, MFP 110 detects that the user has pressed scan-to-chat button 703. In S506, MFP 110 sends to MFP link server 120 a request to acquire application setting information required for use of the additional application corresponding to scan-to-chat button 703. The request to acquire sent from MFP 110 to MFP link server 120 includes logged-in user information, device information, and pressed application information. The application information includes information on the corresponding service. In other words, user information of user A, device information of MFP 110, and application information indicating chat service A are sent to MFP link server 120 together with the request to acquire application setting information.

[0043] Having received the request to obtain application setting information from MFP 110, MFP link server 120 obtains the application setting information from data management unit 433 of MFP link server 120 in S507. Fig. 8 is a diagram showing an example of the application setting information. The application setting information is managed as application setting table 800 by data management unit 433 of MFP link server 120. Application setting table 800 includes, for example, application ID 801, button name 802, scan setting 803, destination 804, message 805, file name 806, file format 807, post deletion 808, and download confirmation 809.

[0044] The application ID 801 is an ID that uniquely identifies an application. For example, an application with application ID 801 S001 corresponds to chat service A, an application with application ID 801 S002 corresponds to chat service B, and an application with application ID 803 corresponds to chat service C. The button name 802 is a button name displayed on the home screen 700 of the MFP 110. The scan setting 803 is an initial value of the scan setting. The scan setting includes, for example, color / black and white, single-sided / double-sided, and the resolution of the scanned image. The transmission destination 804 is an initial value of the chat service and talk room to which the scanned image is to be transmitted.

[0045] Message 805 is the initial value of a message to be sent together with the scanned image when it is sent to the chat service. File name 806 is the initial value of the file name. In the example shown in FIG. 8, "Scan_{year}{month}{day}{minute}" is set as the file name 806. The part enclosed in curly brackets is replaced with specific characters when the application is executed. In the example shown in FIG. 8, the dynamic part of the file name is replaced with the year, month, day, hour, and minute when the application settings are acquired.

[0046] File format 807 is a file format for converting a scanned image. Post deletion 808 indicates whether the chat service supports a chat post deletion function described later. For example, if the chat service supports the post deletion function, a value of True is stored in post deletion 808, and if the chat service does not support the post deletion function, a value of False is stored. Download confirmation 809 indicates whether the chat service supports a function for checking whether a file sent to a chat service described later has been downloaded by someone. For example, if the download confirmation function is supported, a value of True is stored in download confirmation 809, and if the download confirmation function is not supported, a value of False is stored. In this embodiment, since scan to chat button 703 pressed on MFP 110 is a button corresponding to chat service A, MFP linkage server 120 acquires each value corresponding to application ID "S001" in S507.

[0047] In S508, MFP cooperation server 120 acquires user connection information used to check whether connection to the destination chat service acquired from the application setting information is possible. MFP cooperation server 120 acquires the connection information from the user information managed by data management unit 433 of MFP cooperation server 120, based on the user information and application information received from MFP 110 together with the request to acquire the application setting information. The user information manages information that identifies the user, information on services registered by the user, and connection information to the services in association with each other. In this embodiment, MFP cooperation server 120 acquires connection information corresponding to user A currently logged in to MFP 110 and chat service A.

[0048] 9 shows an example of user information managed by MFP linked server 120. The user information is managed as user information table 900 by data management unit 433 of MFP linked server 120. User information table 900 includes, for example, user ID 901, user name 902, password 903, email address 904, connection service 905, and connection information 906.

[0049] User ID 901 is an ID that uniquely identifies a user. User name 902 is the name of the user. Password 903 is the password of the user. Email address 904 is the email address of the user. Email address 904 is used when accessing MFP linked server 120 from client PC 111. Connection service 905 is a service to be connected to (e.g., a chat service). Connection information 906 is information required for connecting to a service, and a value is stored for each service. Connection information 906 stores, for example, an access token and a session ID. Connection information 906 needs to be acquired by allowing a user to connect between MFP linked server 120 and each chat service before using each application. In the example shown in FIG. 9, MFP linked server 120 acquires connection information “8f9adfeggaj290vaa” corresponding to user A and chat A as connection information.

[0050] In S509, MFP collaboration server 120 makes a request to chat server 130, which provides chat service A, to acquire chat information, using the connection information acquired in S508. In S510, chat server 130 acquires chat information based on the connection information and responds to MFP collaboration server 120. The chat information includes, for example, information about talk rooms in which a user can make a chat post on the chat. In this embodiment, MFP collaboration server 120 transmits connection information of user A to chat server 130, and chat server 130 transmits chat information including information about a list of talk rooms in which user A can make a chat post on chat A to MFP collaboration server 120.

[0051] In S511, MFP cooperation server 120 checks, based on the chat information acquired in S510, whether the user can post chat messages to the talk room set as the default value of destination 804 in the setting information table of the application (FIG. 8). If the default value of destination 804 is a talk room to which the user cannot post chat messages, the setting is corrected to match the range accessible by the user. As a correction, for example, MFP cooperation server 120 deletes the information of the talk room set as the default value of destination 804. In S512, MFP cooperation server 120 transmits the setting information of the application (FIG. 8) and chat information including the list of talk rooms acquired in S510 to MFP 110.

[0052] In S513, the MFP 110 displays a scan screen based on the acquired application setting information and chat information. FIG. 10 is a diagram showing an example of the scan screen. FIG. 10(A) shows an example of the scan screen after execution of a scan. The scan screen 1000 includes a preview area 1001, scan settings 1003, transmission information 1004, a scan button 1005, and a send button 1006. A preview image 1002 generated from a scanned image is displayed in the preview area 1001 after execution of a scan. Note that an image or text (both not shown) for encouraging the user to scan may be displayed in the preview area 1001 before execution of a scan.

[0053] Scan setting 1003 displays settings for scanning a document. For example, color mode, double-sided setting, resolution, and the like are displayed in scan setting 1003. MFP 110 displays scan setting 1003 based on scan setting 803 included in setting information of an application acquired from MFP link server 120. Transmission information 1004 displays information related to posting of a scanned image to a chat. For example, information on a chat room to which the image is to be sent, a message to be posted together with the scanned image, and a file name are displayed in transmission information 1004. MFP 110 displays transmission information 1004 based on setting information of an application and chat information acquired from MFP link server 120, and the date, time, and hour when scanning was performed. In scan setting 1003 and transmission information 1004, an edit screen (not shown) can be displayed by a user pressing each setting, and the setting can be changed. Scan button 1005 is a button for instructing execution of a scan. Send button 1006 is a button for instructing transmission of a scanned image to a chat.

[0054] In S514, the user 10 issues a scan instruction by pressing the scan button 1005. As a result, in S514, the MFP 110 detects that the user has pressed the scan button 1005. In S515, the MFP 110 scans the document and generates a scanned image. In S516, the MFP 110 displays a preview image 1002 generated from the scanned image in the preview area 1001.

[0055] In S517, the user 10 issues a transmission instruction to the chat by pressing the send button 1006. As a result, in S517, the MFP 110 detects that the user has pressed the send button 1006. In S518, the MFP 110 generates a file from the scanned image. The MFP 110 assigns the file name set in the transmission information 1004 to the file name of the generated file.

[0056] In S519, MFP 110 sends a posting request to chat server 130 to MPF linkage server 120. The posting request includes the destination set in transmission information 1004, the message to be posted, and the created file. In S520, MFP linkage server 120 sends the posting request acquired from MFP 110 to chat server 130. Note that the user connection information acquired in S508 is used for access from MFP linkage server 120 to the talk room that is the posting destination on chat server 130. In S521, chat server 130 posts the scanned image by adding the specified message and file to the destination talk room specified in transmission information 1004.

[0057] 11 to 13 are diagrams showing examples of chat screens. Chat screen 1100 is displayed on operation unit 317 of client PC 111, for example. Fig. 11(A) shows the chat screen on which posting of a file scanned by MFP 110 and transmitted from MFP 110 has been completed. Chat screen 1100 includes, for example, a chat room selection area 1101, a chat room 1102, a chat input field 1104, and a chat send button 1105.

[0058] Chat room selection area 1101 is an area for selecting a chat room. Chat room names are displayed in a list in chat room selection area 1101. Chat room 1102 displays messages posted to the chat room selected in chat room selection area 1101. Posted message 1103 in chat room 1102 indicates a message posted with a file attached from MFP 110 via MFP linkage server 120. In this manner, an image scanned by MFP 110 can be sent from MFP 110 to chat server 130 and posted. Chat input field 1104 is an area for a user of PC 111 to input a chat. Chat send button 1105 is a button for sending the content entered in chat input field 1104 to chat server 130 and posting it.

[0059] In S522, chat server 130 sends the result of posting the scanned image to the chat to MFP cooperation server 120. If the posting is successful, upon completion of the posting, chat server 130 sends to MFP cooperation server 120 a posting ID that uniquely indicates the success of the chat posting and the posting. In S523, MFP cooperation server 120 transfers the posting result received from chat server 130 to MFP 110.

[0060] In S524, the MFP 110 adds the acquired posting result to the job history as a transmission history. Fig. 14 is a diagram showing an example of the job history. Fig. 14 is divided into Fig. 14(A) and Fig. 14(B), but Fig. 14(A) and Fig. 14(B) together constitute one job history. The job history is managed by the data management unit 433 of the MFP 110. The job history includes, for example, a job ID 1201, a date and time 1202, an application ID 1203, a job type 1204, a status 1205, and a transmission destination 1206. The job history further includes a message 1207, a file name 1208, a preview image 1209, a posting ID 1210, and a user 1211.

[0061] Job ID 1201 is an ID that uniquely identifies each job. Date and time 1202 is the date and time when the job was executed. Application ID 1203 is the application ID of the native or additional application that executed the job, and is the same as application ID 801 in FIG. 8. Job type 1204 indicates the type of job. The type of job indicates the type of function provided by the MFP 110, such as printing (including copy, print, etc.) and transmission (including chat, e-mail, shared folder, fax, etc.).

[0062] Status 1205 indicates the status of the job. Examples of the status include sending, sent, deleted, and error. Destination 1206 is the destination to which the scanned image is sent. Destination 1206 includes, for example, a destination address, a service, and a chat room. Message 1207 is a message sent via chat or email together with the scanned image file. File name 1208 indicates the file name of the sent file. Preview image 1209 is a preview image of the sent file. If the file has multiple pages, preview image 1209 holds multiple preview images.

[0063] Posting ID 1210 is a posting ID issued by chat server 130. Posting ID is an ID that uniquely identifies a posting of a file or a message issued by chat server 130. User 1211 is information that identifies a user who executed a job. For example, user 1211 may be information that uniquely identifies a user, such as a user name, a user ID, or a user's email address.

[0064] In this way, the job history stores, as a transmission history, the file sent to chat server 130 in S519, destination information, the transmission result obtained from chat server 130 in S523, and the posting ID, all linked to the job ID. After pressing the send button in S517, MFP 110 adds the transmission history to the job history, and updates the status, posting ID, and the like in response to the results of the file generation in S518 and the file posting request in S523. The transmission history of job ID "J20230621103311" shown in Fig. 14 corresponds to the posting of a scanned image displayed on the screens of Figs. 10 and 11.

[0065] In S525, the MFP 110 displays a transmission completion message on the scan screen 1000. FIG. 10B is a diagram showing an example of the transmission completion message. If the posting of the scanned image to the chat is successful, a completion message 1007, a history display button 1008, and a close button 1009 are displayed on the scan screen 1000. When the history display button 1008 is pressed by the user, the MFP 110 displays a screen that displays the job status and history of the MFP 110, which will be described later. When the close button 1009 is pressed by the user, the MFP 110 returns the displayed screen to the home screen 700.

[0066] Here, a method for permitting a connection between MFP collaborative server 120 and chat server 130 will be described. A user logs in to MFP collaborative server 120 via client PC 111, for example, and is able to display an access authorization setting screen by screen transition from a main screen (not shown) that is displayed after logging in. FIG. 15 is a diagram showing an example of the access authorization setting screen. Access authorization setting screen 1300 is a screen for making settings to permit MFP collaborative server 120 to access chat server 130. Access authorization setting screen 1300 is provided by MFP collaborative server 120, and is displayed on operation unit 317 of client PC 111 via a Web browser.

[0067] The access authorization setting screen 1300 includes a service name display area 1301, a service connection button 1302, and a service connection status display area 1303. The service name display area 1301 displays the name of a chat service to which the MFP linkage service can be connected. When the service connection button 1302 is pressed, a target service authentication and authorization screen (not shown) is displayed, and the user can grant authorization for the target service to MFP linkage server 120 by performing authentication and authorization settings for the target service. The authorization setting is performed, for example, by using the OAuth mechanism. The service connection status display area 1303 indicates whether or not a connection to the service is authorized. For example, the service connection status display area 1303 displays "not connected" when a connection to the service is not authorized, and displays "connected" when a connection to the service is authorized. When the authorization setting is completed, the display in the service connection status display area 1303 switches from "not connected" to "connected". When the authorization setting is completed, information on the authorized service is registered in the connection service 905 of the user information table 900 corresponding to the login user. Furthermore, information used to connect to the service, such as an access token acquired at the time of authorization setting, is stored in the connection information 906 of the user information table 900 by the data management unit 433 .

[0068] Next, the process of posting a scanned image by MFP 110 will be described with reference to Fig. 16 and Fig. 17. Fig. 16 and Fig. 17 are flowcharts showing the process of posting a scanned image. The process shown in the flowcharts of Fig. 16 and Fig. 17 is the process in MFP 110 after detecting the user's press of scan to chat button 703 in S505 of Fig. 5. Note that each process shown in Fig. 16 and Fig. 17 is realized by CPU 211 of MFP 110 reading a program stored in memory (ROM 212 or HDD 214) into RAM 213 and executing it.

[0069] In S1401, the display control unit 421 displays a message (not shown) indicating that the app (app of chat service A) corresponding to the scan to chat button 703 pressed on the home screen 700 is running on the operation unit 220 of the MFP 110. In S1402, the data management unit 425 acquires the user ID of the logged-in user and the app ID corresponding to the button pressed on the home screen 700. In this embodiment, the data management unit 425 acquires the user ID of the logged-in user A (user 10) and the app ID of the chat service A app corresponding to the scan to chat button 703.

[0070] In S1403, linked service request unit 423 sends a request to MFP link server 120 to obtain application setting information, including a user ID, an application ID, the MFP serial number, and the like. The processing of S1403 corresponds to the processing of S506 in FIG. 5. In S1404, linked service request unit 423 receives a response to the request to obtain the application setting information from MFP link server 120. Linked service request unit 423 obtains, as the response, the application setting information (FIG. 8), a list of talk rooms accessible on chat server 130, and information on whether the user can connect to chat service A. Then, data management unit 425 stores the information received from MFP link server 120 in HDD 214.

[0071] In S1405, display control unit 421 determines whether or not connection to chat service A provided by chat server 130 is possible, based on the connection availability information to chat service A received from MFP linkage server 120 in S1404. If connection to chat service A is not possible, processing of S1406 is performed. In S1406, display control unit 421 displays an error screen indicating that connection to chat service A is not possible. Furthermore, a message according to the cause of the inability to connect may be displayed on the error screen. For example, if authorization settings have not been made, a message is displayed prompting the user to separately access MFP linkage server 120 and grant authorization to chat server 130. On the other hand, if connection to chat service A is possible, processing of S1407 is performed.

[0072] In S1407, the display control unit 421 displays the scan screen 1000 reflecting the information received in S1404. The application settings and the like received in S1404 are reflected in the scan settings 1003 and the transmission information 1004. The processing of S1407 corresponds to the processing of S513 in FIG. 5. In S1408, the display control unit 421 determines whether or not a scan instruction has been accepted on the scan screen 1000. If the scan button 1005 has been selected, it is determined that a scan instruction has been accepted, and the processing of S1409 is performed. On the other hand, it is determined that a scan instruction has not been accepted until the scan button 1005 is selected, and the processing of S1408 is repeated.

[0073] In S1409, the scan control unit 422 instructs the scan execution unit 411 to start scanning. The scan execution unit 411 performs scanning processing and generates scanned image data. The scanned image data generated by scanning is stored in the scanned image management unit 412, and the corresponding scanned image identifier is notified to the scan control unit 422. During the scanning processing, the display control unit 421 may display a message (not shown) indicating that scanning is in progress.

[0074] In S1410, the image processing unit 424 generates a preview image of the scanned image. Then, the display control unit 421 displays the generated preview image 1002 on the scan screen 1000. In S1411, the display control unit 421 determines whether or not a transmission instruction has been accepted on the scan screen 1000. If the send button 1006 is selected, it is determined that a transmission instruction has been accepted, and the process of S1412 is performed. On the other hand, until the send button 1006 is selected, it is determined that a transmission instruction has not been accepted, and the process of S1411 is repeated.

[0075] In S1412, the display control unit 421 displays a message (not shown) on the scan screen 1000 to the effect that the scanned image is being sent to the chat service. In S1413, the data management unit 425 issues a job ID that uniquely represents the sent job, and saves information related to the sending as a sending history in the job history (FIG. 14) in the HDD 214. At this time, the status 1205 in the job history becomes "sending", and the posting ID 1210 remains empty until the sending result is obtained.

[0076] In S1414, image processing unit 424 converts the scanned image with the file format and file name specified in transmission information 1004 to generate a file, and saves the file in the job history of HDD 214. In S1415, cooperation service request unit 423 transmits a file posting request to MFP cooperation server 120 to send the file generated in S1414 to the destination specified in transmission information 1004. A message to be posted together with the file is also transmitted together with the file. The processing of S1415 corresponds to the processing of S519 in FIG. 5. Having received the file posting request from MFP 110, MFP cooperation server 120 instructs chat server 130 to post the file to the destination specified in chat service A. Chat server 130 posts the file to the specified destination, and returns the posting result including the generated posting ID to MFP 110 via MFP cooperation server 120. In S1416, cooperation service request unit 423 receives the file posting result from chat server 130 via MFP cooperation server 120.

[0077] In S1417, data management unit 425 reflects the file posting result received by cooperation service request unit 423 in the job history (FIG. 14). At this time, status 1205 becomes "sent", and the posting ID received in the file posting result is saved in posting ID 1210. In S1418, display control unit 421 displays a message of transmission completion on scan screen 1000, and ends this process. FIG. 10B is a diagram showing an example of the transmission completion message. Display control unit 421 displays completion message 1007, history display button 1008, and close button 1009 on scan screen 1000. In this way, in this embodiment, when a scanned image generated by MFP 110 is transmitted to chat server 130 and posted, the posting ID uniquely indicating the posting on chat server 130 and the transmission content can be associated with each other and managed as a job history by MFP 110.

[0078] Next, a process flow between each device when a file or message posting transmitted from MFP 110 to chat server 130 via MFP link server 120 is deleted by operating MFP 110. FIG. 18 is a sequence diagram showing the flow of a posting deletion process. Here, the description focuses on the exchange between each device. Each process executed by MFP 110 in the posting deletion process is realized by CPU 211 of MFP 110 executing a program stored in memory (ROM 212 or HDD 214). Each process executed by MFP link server 120 is realized by CPU 311 of MFP link server 120 executing a program stored in memory (ROM 312 or HDD 314). Each process executed by chat server 130 is realized by CPU 311 of chat server 130 executing a program stored in memory (ROM 312 or HDD 314).

[0079] In S1501, the user 10 presses the history display button 1008 or the status history button 604. As a result, in S1501, the MFP 110 detects that the history display button 1008 or the status history button 604 has been pressed. In S1502, the MFP 110 acquires information on the job history (FIG. 14) corresponding to the logged-in user from the HDD 214. In S1503, the MFP 110 displays a history screen based on the acquired job history.

[0080] 19 to 22 are diagrams showing an example of a history screen 1600. Fig. 19 is an example in which a list of jobs of a logged-in user is displayed on the history screen 1600. The history screen 1600 displays a list of job histories of logged-in user A. The history screen 1600 that displays the list of jobs includes a list 1601, a switch button 1602, a delete post button 1608, a detailed information button 1609, and a close button 1610.

[0081] The switching button 1602 is a button for switching the type of function (job) displayed in the list 1601. The switching button 1602 is, for example, a pull-down menu from which the user selects the type of function. The pull-down menu of the switching button 1602 displays a list of functions such as "Print" and "Send". The MFP 110 displays in the list 1601 the job history corresponding to the function selected with the switching button 1602.

[0082] A list 1601 displays a list of jobs executed by the user. A list of job histories corresponding to a function selected with a switching button 1602 is displayed in the list 1601. In the example shown in Fig. 19, "Send", which indicates a job for scanning and sending, is selected with the switching button 1602, and a list screen of the sending history is displayed in the list 1601.

[0083] The list of transmission jobs 1601 includes items such as a status 1603, a transmission date and time 1604, a transmission destination 1605, a message 1606, and a file name 1607. The status 1603 displays the status of the job. The status 1603 is information corresponding to the status 1205 in the job history shown in FIG. 14. The transmission date and time 1604 displays the execution date and time of the job. The transmission date and time 1604 is information corresponding to the date and time 1202 in the job history shown in FIG. 14. The transmission destination 1605 displays the transmission destination of the job. The transmission destination 1605 is information corresponding to the transmission destination 1206 in the job history shown in FIG. 14. The message 1606 displays the contents of a message transmitted via the chat server 130, e-mail, or the like. The message 1606 is information corresponding to the message 1207 in the job history shown in FIG. 14. The file name 1607 displays the file name of the transmitted file. The file name 1607 corresponds to the file name 1208 in the job history shown in FIG.

[0084] The delete post button 1608 is a button for deleting a post corresponding to the history of a transmission job selected in the list 1601. The delete post button 1608 is displayed in a pressable state when a post deletion function is available for the history of a transmission job selected in the list 1601. In this embodiment, this button is displayed in a pressable state when the job history selected in the list 1601 is a job for the chat server 130 and the post deletion function is available. The close button 1610 is a button for closing the history screen 1600.

[0085] Detailed information button 1609 is a button for displaying detailed information about a selected job. When it is detected that detailed information button 1609 is pressed, MFP 110 displays a detailed job information screen on history screen 1600. FIG. 20 is a diagram showing an example of the detailed information screen of a transmission job. On the detailed information screen, a preview image 1611 and detailed job information 1612 are displayed. Preview image 1611 is a preview image of a file transmitted in a transmission job. An image held in preview image 1209 of the job history shown in FIG. 14 is displayed on preview image 1611. In addition to the information displayed on list 1601, detailed job information 1612 displays information included in the job history of the job history shown in FIG. 14, such as sender information.

[0086] Furthermore, the job details screen displays a delete post button 1608 and a back button 1613. The delete post button 1608 is displayed as selectable only when the job history displayed on the job details screen is a job history corresponding to deleting a post. The back button 1613 is a button for closing the job details screen and returning to the history screen 1600. In this way, information that cannot be displayed on the history screen 1600 can be displayed on the details screen, improving the convenience for the user when checking whether or not the post is correct. If the user determines that the post should be deleted, for example because the post is incorrect, the user presses the delete post button 1608.

[0087] FIG. 19 shows an example in which the job history of the user A who is currently logged in is displayed, but the present invention is not limited to this. As shown in FIG. 21, even if the user A is currently logged in, the job history of other users (for example, user B and user C) may also be displayed. FIG. 21 shows an example in which a list of jobs of multiple users is displayed on the history screen 1600. When the history of users other than the currently logged in user is also displayed, the list 1601 also displays user 1614, which is an item indicating the name of the user who instructed the execution of the job. User 1614 is information corresponding to user 1211 in the job history shown in FIG. 14. In addition, in the job history of users other than the currently logged in user, the destination 1605, message 1606, file name 1607, and the like are not displayed. In addition, when the job history of a user other than the currently logged in user is selected and the detailed information button 1609 is pressed, the preview image 1611 on the detailed information screen is also not displayed. Furthermore, jobs that a logged-in user can delete are limited to their own jobs, and when another user's job history is selected, the delete post button 1608 cannot be selected, even if the job history is one for which the delete post function is available. When the delete post button 1608 cannot be selected, it is displayed as grayed out. Note that when the delete post button 1608 cannot be selected, it may be hidden.

[0088] Returning to the description of FIG. 18, in S1504, the user selects one job history from the list 1601. As a result, the MFP 110 detects the selection of the job history by the user in S1504. In S1505, the MFP 110 updates the display of the delete post button 1608 on the history screen 1600 in accordance with the selected job history. Specifically, the MFP 110 first refers to the status 1205 and the destination 1206 corresponding to the selected job history. If the destination 1206 is not a chat service, for example, an address that cannot be deleted such as an email address or a fax, the delete post button 1608 is disabled and is displayed on the history screen 1600 in a state in which it cannot be pressed (for example, grayed out). If the status 1205 is "sent" and the destination 1206 is a chat service, the MFP 110 further acquires the application ID 1203. The MFP 110 then references the setting information (Delete Post 808) of the application setting information (FIG. 8) that was previously acquired in response to a setting acquisition request such as in step S506 and stored in the HDD 214, and determines whether the application ID corresponding to the job history supports post deletion. If Delete Post 808 is "True," the MFP 110 enables the Delete Post button 1608 and displays it on the history screen 1600 in a pressable state. On the other hand, if Delete Post 808 is "False," the MFP 110 disables the Delete Post button 1608 and displays it on the history screen 1600 in an unselectable state.

[0089] When the user wishes to delete the post corresponding to the job history selected in S1504, the user presses delete post button 1608 in S1506. As a result, MFP 110 detects the pressing of delete post button 1608 in S1506. In S1507, MFP 110 transmits a delete post request to MFP cooperation server 120 together with information about post ID 1210 corresponding to the selected job history.

[0090] In S1508, MFP cooperation server 120 sends a post deletion instruction to chat server 130 together with the post ID received from MFP 110. In S1509, chat server 130 deletes the messages and files related to the received post ID. Fig. 11(B) is a diagram showing an example of a chat screen where a post has been deleted. On chat screen 1100, posted message 1103 shown in Fig. 11(A) has been deleted, and message 1106 indicating that the post has been deleted is displayed.

[0091] In S1510, chat server 130 transmits the result of the post deletion to MFP cooperation server 120. In S1511, MFP cooperation server 120 transmits the result of the post deletion received from chat server 130 to MFP 110. MFP 110 receives the result of the post deletion from chat server 130 via MFP cooperation server 120. In this embodiment, it is assumed that the post deletion is successful and MFP 110 receives a result indicating that the post deletion was successful. If the post deletion is successful, in S1512, MFP 110 updates the status of the history corresponding to the job history in which the post deletion was executed to “deleted”. That is, status 1205 corresponding to the job ID in which the post was deleted in the job history ( FIG. 14 ) is changed to “deleted”. The change in status 1205 of the job history is reflected in status 1603 of list 1601 displayed on history screen 1600. FIG. 22 is a diagram showing an example of the history screen after deletion is executed. Comparing FIG. 19 with FIG. 22, it can be seen that the status 1603 of the job selected in FIG. 19 has been changed from "Submitted" to "Deleted."

[0092] Next, details of the post deletion process performed by MFP 110 described in Fig. 18 will be described with reference to Fig. 23. Fig. 23 is a flowchart showing the post deletion process. The process shown in the flowchart in Fig. 23 is the process performed by MFP 110 after history display in S1503 in Fig. 18. Note that each process shown in Fig. 23 is realized by CPU 211 of MFP 110 reading a program stored in memory (ROM 212 or HDD 214) into RAM 213 and executing it.

[0093] In S1701, the display control unit 421 determines whether or not a job history has been selected in the list 1601. If it is determined that a job history has been selected, the MFP 110 performs processing in S1702. On the other hand, until it is determined that a job history has been selected, the MFP 110 repeats the processing in S1701.

[0094] In the processing of S1702 to S1707, the MFP 110 determines whether to enable or disable the display of the delete post button 1608 on the history screen 1600. If a post cannot be deleted, the MFP 110 disables the display of the delete post button 1608 on the history screen 1600, and enables the display of the delete post button 1608 only if a post can be deleted. The MFP 110 determines whether a post can be deleted, that is, whether to enable the display of the delete post button 1608 on the history screen 1600, based on the job history information and the application setting information.

[0095] In S1702, the data management unit 425 acquires, from the job history (FIG. 14), information corresponding to the job history selected in the list 1601. In S1702, the data management unit 425 acquires information including at least the application ID 1203, the status 1205, and the transmission destination 1206 as information corresponding to the selected job history.

[0096] In S1703, the display control unit 421 refers to the job history information acquired in S1702 and determines whether the destination 1206 is a chat service. If the destination 1206 is a chat service, the MFP 110 performs processing in S1705. On the other hand, if the destination 1206 is not a chat service, the MFP 110 performs processing in S1704 since the post cannot be deleted. In S1704, the display control unit 421 disables the post delete button 1608 on the history screen 1600 and ends this processing. For example, the display control unit 421 disables the post delete button 1608 by graying out the post delete button 1608 so that it cannot be pressed.

[0097] In S1705, the display control unit 421 refers to the job history information acquired by the data management unit 425 and determines whether the status 1205 is "sent". If the status 1205 is "sent", the MFP 110 performs the process of S1706. On the other hand, if the status 1205 is not "sent", the MFP 110 performs the process of S1704 because the post deletion cannot be used due to a status such as sending, deleted, or an error. In S1704, the display control unit 421 disables the post deletion button 1608 and ends this process.

[0098] In S1706, data management unit 425 acquires application information corresponding to application ID 1203 in the job history from HDD 214. Here, the application information held in HDD 214 is the same as the application setting information (FIG. 8) held by MFP link server 120. The application information can be acquired from MFP link server 120 in the processing of S512, but the application information may also be kept up to date by periodically synchronizing MFP 110 and MFP link server 120. In S1706, data management unit 425 acquires information including at least post deletion 808 as the application information.

[0099] In S1707, display control unit 421 determines whether or not a post can be deleted. Whether or not a post can be deleted is determined based on whether or not the chat service has a post deletion function, i.e., based on whether Delete Post 808 in the application information acquired by data management unit 425 is "True" or "False." If Delete Post 808 is "True," it is determined that post deletion is possible, and MFP 110 performs processing of S1708. On the other hand, if Delete Post 808 is "False," post deletion is not available, and MFP 110 performs processing of S1704. In S1704, display control unit 421 disables the Delete Post button 1608 and ends this processing.

[0100] In S1708, the display control unit 421 enables the display of the delete post button 1608 on the history screen 1600. In S1709, the display control unit 421 determines whether or not the delete post button 1608 has been selected. If it is determined that the delete post button 1608 has been selected, the MFP 110 performs the process of S1710. On the other hand, the MFP 110 repeats the process of S1709 until the delete post button 1608 is selected. Note that if it is detected that a button other than the delete post button 1608 has been selected, the MFP 110 performs the process corresponding to the selected button.

[0101] In S1710, data management unit 425 acquires posting ID 1210 of the job for which the posting deletion has been instructed, from the job history ( FIG. 14 ). In S1711, cooperation service request unit 423 sends to MFP cooperation server 120 a request to delete files and messages associated with the posting ID, together with posting ID 1210 acquired by data management unit 425. MFP cooperation server 120 that has received the posting deletion request from MFP 110 sends to chat server 130 a request to delete files and messages associated with the posting ID, together with the received posting ID 1210. Chat server 130 that has received the posting deletion request from MFP 110 via MFP cooperation server 120 deletes the files and messages associated with the posting ID based on the received posting ID 1210. Then, chat server 130 sends a result of the posting deletion to MFP 110 via MFP cooperation server 120.

[0102] In S1712, linked service request unit 423 receives the post deletion result from chat server 130 via MFP linked server 120. In S1713, data management unit 425 updates status 1205 in the job history ( FIG. 14 ) based on the post deletion result received by linked service request unit 423. For example, if the post deletion was successful, data management unit 425 changes status 1205 from “Sent” to “Deleted.” Then, display control unit 421 updates the display of status 1603 in list 1601 on history screen 1600 in accordance with the job history updated by data management unit 425.

[0103] In this way, by managing the posting ID uniquely indicating the posting on the chat server 130 and the job history in association with each other in the MFP 110, it is possible to delete the file and the message on the chat server 130 related to the job selected in the list 1601. This allows a file that the user has mistakenly sent to the chat server 130 to be deleted by an operation from the operation unit 220 of the MFP 110. Examples of erroneous sending by the user include a mistake in the scanned document such as an incomplete entry in the document or an excess or shortage of pages, an error in sending information such as an error in selecting the destination talk room, and an error in the scan setting. In the case of chat, it is highly likely that a member of the talk room that sent the file will view or obtain the file immediately after receiving a notification of a new posting. Therefore, the more important the document, the more likely it is that the file will be deleted or the error will be corrected immediately when a mistake is made. Therefore, making it possible to delete a post sent to the chat server 130 from the MFP 110, which is the terminal that executed the sending process, enables the post to be deleted in the shortest time compared to the case of moving to another terminal to delete the post, improving the convenience of the user.

[0104] In the post deletion process shown in FIG. 23, the determinations in S1703, S1705, and S1707 have been described as the conditions for switching the enable / disable display of the post deletion button 1608. However, the time that has passed since the job execution time may also be added to the determination. When the time that has passed since the job execution time is used as the condition for switching the enable / disable display of the post deletion button 1608, the date and time 1202 is also acquired when acquiring the job history in S1702. For example, when it is determined in S1705 that the message is “sent”, the display control unit 421 performs a process of determining whether or not an arbitrary time has passed since the date and time 1202 of transmission. The arbitrary time can be set by the MFP 110 or the MFP cooperation server 120. If the arbitrary time has passed, the display control unit 421 performs the process of S1704 and displays the post deletion button 1608 as invalid. On the other hand, if the arbitrary time has not passed, the MFP 110 performs the process of S1706. In this embodiment, the main case in which a user wants to delete a post by operating the MFP 110 is when the user realizes an error immediately after a sending operation. Therefore, it is unlikely that the user would take the trouble to delete an old post from the MFP 110. By displaying the delete post button 1608 as inactive after a given time has elapsed, it is possible to prevent the user from accidentally deleting posts from old job history.

[0105] Next, a process for when a post cannot be deleted will be described. Even if the post deletion process (FIG. 23) is performed, the post cannot be deleted in the case of a chat service that does not support a post deletion function. In this embodiment, when a post cannot be deleted, a correction message is posted to inform other users of the chat that the file sent to the chat room was sent by mistake, thereby informing them that the file sent to the chat room was sent by mistake. By posting a message to inform them that the file sent to the chat room was sent by mistake, it is possible to urge other users to stop viewing and obtaining the incorrect file.

[0106] Even in chat services that support posting deletion, there are cases where other users download the file to be deleted before the posting is deleted. In this embodiment, when other users have already downloaded the file to be deleted, a correction message is posted to inform other users of the chat that the file sent to the chat room was sent by mistake. By posting a message informing other users that the file sent to the chat room was sent by mistake, it is possible to urge other users to stop viewing the already downloaded file and delete it.

[0107] Fig. 24 is a flowchart showing a posting deletion process in MFP 110. The process shown in the flowchart in Fig. 24 is a process in MFP 110 after history display in S1503 in Fig. 18. Note that each process shown in Fig. 24 is realized by CPU 211 of MFP 110 reading a program stored in memory (ROM 212 or HDD 214) into RAM 213 and executing it.

[0108] The processes of S1801 to S1805 in Fig. 24 are the same as the processes of S1701 to S1705 in Fig. 23. If it is determined in S1805 that the status of the job history selected in S1801 is "Sent", the MFP 110 performs the process of S1806. In S1806, the display control unit 421 enables the display of the delete post button 1608 on the history screen 1600. That is, in this process, the delete post button 1608 is enabled regardless of whether the selected job history corresponds to deleting a post.

[0109] In S1807, the display control unit 421 determines whether or not the delete post button 1608 has been selected. If it is determined that the delete post button 1608 has been selected, the MFP 110 performs the process of S1808. Meanwhile, the MFP 110 repeats the process of S1807 until the delete post button 1608 is selected. In S1808, the data management unit 425 acquires information about the job for which the post deletion has been instructed from the job history (FIG. 14). The job information acquired by the data management unit 425 in S1808 includes at least the post ID 1210, the application ID 1203, and the file name 1208.

[0110] In S1809, linkage service request unit 423 sends to MFP linkage server 120 a request to delete the file and message associated with the posting ID, together with posting ID 1210 acquired by data management unit 425. Having received the post deletion request from MFP 110, MFP linkage server 120 performs the processing shown in FIG. 25. FIG. 25 is a flowchart showing the post deletion processing in MFP linkage server 120. MFP linkage server 120 sends a post deletion request to chat server 130 if the post can be deleted, and sends a request to post a correction message if the post cannot be deleted. Each process shown in FIG. 25 is realized by CPU 311 of MFP linkage server 120 reading a program stored in memory (ROM 312 or HDD 314) into RAM 213 and executing it.

[0111] In S1821, data management unit 433 acquires application information corresponding to application ID 1203 received from MFP 110 from application setting information (FIG. 8) stored in HDD 314. In S1821, data management unit 433 acquires information including at least post deletion 808 and download confirmation 809 as application information.

[0112] In S1822, external server access unit 432 determines whether the post deletion function is available in the application based on post deletion 808 acquired in S1821. If post deletion 808 is "True", it is determined that the post deletion function of the application is available, and MFP linkage server 120 performs processing of S1823. On the other hand, if post deletion 808 is "False", it is determined that the post deletion function of the application is not available, and MFP linkage server 120 performs processing of S1829.

[0113] In S1823, external server access unit 432 sends a request to delete the posted file and message associated with the posting ID to chat server 130. Having received the post deletion request from MFP cooperation server 120, chat server 130 deletes the posted file and message corresponding to the posting ID. At this time, chat screen 1100 displays as shown in FIG. 11(B) above. Then, chat server 130 sends the result of the post deletion process to MFP cooperation server 120. In S1824, external server access unit 432 receives the deletion result from chat server 130.

[0114] In S1825, external server access unit 432 determines, based on download confirmation 809 acquired in S1821, whether it is possible to confirm whether the file corresponding to the posting ID received from MFP 110 has already been downloaded from the chat. If download confirmation 809 is "True", it is determined that download confirmation is possible, and MFP linkage server 120 performs processing of S1826. On the other hand, if download confirmation 809 is "False", it is determined that download confirmation is not possible, and MFP linkage server 120 performs processing of S1829.

[0115] In S1826, external server access unit 432 sends a request to chat server 130 to confirm whether a file corresponding to the posting ID has been downloaded. In the case of a chat service that can obtain information on whether a user has downloaded a file, the download confirmation request is sent to determine whether any user has already downloaded the file. Chat server 130 that has received the download confirmation request checks whether any user has already downloaded the file corresponding to the posting ID, and returns the confirmation result to MFP linkage server 120.

[0116] In S1827, external server access unit 432 receives the download confirmation result from chat server 130. In S1828, external server access unit 432 determines whether or not any users have already downloaded the data, based on the download confirmation result received from chat server 130. If any users have already downloaded the data, MFP linkage server 120 performs the process of S1829. On the other hand, if no users have already downloaded the data, MFP linkage server 120 performs the process of S1831.

[0117] In S1829, external server access unit 432 sends a correction message posting request together with the posting ID to chat server 130. Chat server 130, which has received the correction message posting request from MFP linkage server 120, performs processing to post the correction message to the chat room in which the posting corresponding to the posting ID was made. The correction message is a message indicating that the posting was sent in error. The correction message may also include a message requesting that the file be deleted if it has already been downloaded. FIG. 12 is a diagram showing an example of a chat screen on which a correction message has been posted. Correction message 1107 displays, for example, a message to members of the chat room informing them that the posting was sent in error and urging them to delete the file that they have already downloaded.

[0118] FIG. 12(A) is an example of a chat screen 1100 in which the selected posting is not deleted and a correction message is posted. If it is determined in S1822 that the posting cannot be deleted (S1822-NO), the chat screen 1100 shown in FIG. 12(A) is displayed. FIG. 12(B) is an example of a chat screen 1100 in which the selected posting is deleted and a correction message is posted. If it is determined in S1822 that the posting is cannot be deleted (S1822-YES) and if it is not determined that there is no user who has downloaded the file (S1828-YES), the chat screen 1100 shown in FIG. 12(B) is displayed. That is, if the posting is deleted and download confirmation is not possible, or if the posting is deleted and download confirmation is possible and it is confirmed that the user has already downloaded the posted file, the chat screen 1100 shown in FIG. 12(B) is displayed. If the posting is deleted and there is no user who has already downloaded it, there is no need to prompt the user to delete it, so a correction message is not sent (S1829).

[0119] Then, upon completing the processing of posting the correction message, chat server 130 transmits the result of posting the correction message to MFP cooperation server 120. At S1830, external server access unit 432 receives the result of posting the correction message from chat server 130. At S1830, external server access unit 432 receives the result of posting the correction message from chat server 130. At S1831, request control unit 431 transmits to MFP 110 the execution result of the deletion instruction from MFP 110. The execution result includes information indicating whether "delete post" or "post correction message" was executed.

[0120] Returning to the explanation of the flow in Fig. 24, in S1810, linked service request unit 423 of MFP 110 receives an execution result for the deletion request from MFP linked server 120. The execution result received in S1810 is the execution result sent by MFP linked server 120 in S1831. In S1811, data management unit 425 updates status 1205 of the job history (Fig. 14) based on the result received in S1810. For example, if only a message prompting deletion has been sent, status 1205 becomes "correction message sent." Then, display control unit 421 changes the display of status 1603 in list 1601 on history screen 1600 in response to the update of status 1205, and displays it.

[0121] As described above, even in chat services where posting deletion is not possible or where there is a possibility that a user has already downloaded the file, it is possible to prevent the wrong file from being viewed or acquired by sending a correction message urging the user to delete the file. Even in cases where posting deletion is possible, if the file that has already been instructed to be deleted has been downloaded by another user, it is possible to prevent the wrong file from being viewed by sending a correction message urging the user to delete the file.

[0122] As described above, according to this embodiment, a file or message posted on a chat service corresponding to a job history selected on the transmission history screen of the image processing device can be deleted by operating the image processing device. As a result, if a message is sent to the chat service by mistake from the image processing device, it is possible to instruct the deletion of the post from the image processing device on the spot without using another terminal.

[0123] Second embodiment In the first embodiment, an example is described in which an account of a user who uses chat server 130 is used to send a file or a message from MFP linked server 120 to chat server 130. In the second embodiment, an example is described in which an account for a chatbot linked to MFP 110 is used. The account for the chatbot is created on chat server 130 by a provider of an additional application for MFP 110 or an administrator of chat server 130. In this embodiment, it is assumed that settings required for communication between MFP linked server 120 and chat server 130 using an account dedicated to the chatbot have been set in advance by the provider of the additional application or the administrator. Note that, in the second embodiment, only differences from the first embodiment are described, and parts that are not specifically stated have the same configuration and procedure as those in the first embodiment.

[0124] Fig. 26 is a sequence diagram showing the flow of chatbot account registration processing. Fig. 26 shows the flow of processing between each device up to the point where settings are made so that an image scanned by MFP 110 can be sent to chat server 130 using the chatbot account. Each process executed by MFP 110 is realized by CPU 211 of MFP 110 executing a program stored in memory (ROM 212 or HDD 214). Each process executed by MFP linkage server 120 is realized by CPU 311 of MFP linkage server 120 executing a program stored in memory (ROM 312 or HDD 314). Each process executed by chat server 130 is realized by CPU 311 of chat server 130 executing a program stored in memory (ROM 312 or HDD 314).

[0125] A user logs in to chat server 130 in advance via client PC 111 or the like. In S1901, the user issues an instruction to add a chatbot account created by an additional application provider or administrator to a talk room in which the user wishes to use scan-to-chat on MFP 110. As a result, chat server 130 accepts an instruction from the user to add the chatbot account to the talk room. In S1902, chat server 130 executes a process to add the chatbot to the talk room. In S1903, chat server 130 notifies MFP cooperation server 120 that the chatbot has been added, along with information about the added talk room.

[0126] At S1904, MFP collaboration server 120 transmits a message indicating the steps required to start using the talk room received from chat server 130. At S1905, chat server 130 posts the message received from MFP collaboration server 120 to the chat room. FIG. 13 is an example of a posting screen displaying the message transmitted by MFP collaboration server 120 indicating the steps required to start using the talk room. Chat screen 1100 displays message 1108 transmitted by MFP collaboration server 120 indicating the steps required to start using the talk room. Message 1108 displays, for example, a message indicating that it is necessary to enter a registration code displayed on MFP 110 in this talk room to start using the talk room.

[0127] S1906 to S1910 are processes for acquiring the registration code supported in S1905. In S1906, the user operates MFP 110 to press a registration code display button (not shown) of the application that the user is going to use. As a result, MFP 110 detects the pressing of the registration code display button. In S1907, MFP 110 transmits a registration code issuance request to MFP linkage server 120 together with a serial number that uniquely identifies MFP 110 and the application ID of the application that the user is going to use. In S1908, MFP linkage server 120 issues a registration code in response to the registration code issuance request, and stores the registration code in association with the serial number and application ID of MFP 110. In S1909, MFP linkage server 120 transmits the issued registration code to MFP 110. In S1910, MFP 110 displays the registration code on operation unit 220.

[0128] In S1911, the user enters the registration code displayed on MFP 110 in the previous talk room. As a result, chat server 130 displays the registration code entered by the user on chat screen 1100. Message 1109 shown in FIG. 13 is an example of a registration code entered by the user. In S1912, chat server 130 transmits the entered registration code to MFP linkage server 120.

[0129] In S1913, MFP cooperation server 120 confirms that the serial number and application ID of MFP 110 match the registration code received from chat server 130. Then, in S1914, the destination talk room and the serial number of MFP 110 to which the posting can be made are associated with the chatbot of the chat service related to the application ID as chatbot connection information, and saved. At this time, a room ID that uniquely identifies the talk room and the like are saved as the destination talk room.

[0130] FIG. 27 is a diagram showing an example of the connection information of a chatbot. The connection information of the chatbot is stored in HDD 314 of MFP cooperation server 120. The connection information of the chatbot includes, for example, chat service name 2001, bot ID 2002, bot name 2003, serial number 2004, talk room name 2005, and room ID 2006. Chat service name 2001 is the name of the chat service. Bot ID 2002 is a chatbot ID that uniquely indicates a bot added to the chat service indicated by chat service name 2001. Bot name 2003 is the name of the chatbot when posting to chat server 130. Serial number 2004 is the serial number of MFP 110 that can post files and messages to the chat server using the chatbot account. Talk room name 2005 is the name of a talk room to which MFP 110 can post files and messages using the chatbot account. The room ID 2006 is an ID that uniquely identifies a talk room to which a file or a message can be posted by the MFP 110 using a chatbot account. In other words, the room ID 2006 is an ID that corresponds to the talk room name 2005.

[0131] In S1915, MFP cooperation server 120 transmits a message of completion of chatbot registration to chat server 130. In S1916, the chat server displays a message of completion of chatbot registration in the talk room. Message 1110 shown in FIG. 13 is a message indicating that the MFP has been registered as a chatbot in the talk room. The above chatbot registration process makes it possible to transmit files and messages from MFP 110 using the chatbot to chat server 130, and to delete posted files and messages. File posting 1111 shown in FIG. 13 is an example of a case where a scanned image file and a message are posted to chat server 130 from MFP 110 using the chatbot account by the process shown in FIG. 5. As shown in file posting 1111, when a file is posted using the chatbot account, it is displayed as if it was posted from the chatbot. Files and messages posted from MFP 110 using the chatbot cannot be deleted even if chat server 130 is accessed via client PC 111 using a user account. In this way, when deleting a file or the like posted from the MFP 110 using a chatbot linked to the MFP 110, the deletion of the posting from the MFP 110 described in the first embodiment is useful.

[0132] As described above, according to this embodiment, it is possible to register a chatbot account linked to the MFP 110. For a post from a chatbot account linked to the MFP 110, it is possible to instruct deletion of the post by operating the MFP 110 through the process described in the first embodiment.

[0133] The disclosure of this embodiment includes the following information processing system configuration. (Configuration 1) An information processing system including an image processing device having a scanner, a chat server providing a chat service, and a linking server relaying communication between the image processing device and the chat server, The image processing device includes: a first transmission means for transmitting a posting request to post a scanned image file generated by scanning with the image processing device to the chat service; a management means for managing a transmission history of the transmission of the posting request and an identifier that uniquely identifies the posting issued by the chat server in association with each other; a second transmission means for transmitting a request to delete the post together with an identifier corresponding to the post to the chat service when an instruction to delete the post is received; The chat server, an issuing means for posting the file based on the posting request from the image processing device and issuing an identifier that uniquely identifies the posting; A transmission means for transmitting the identifier to a source requesting the posting; a deletion means for deleting the post corresponding to the identifier in response to a deletion request from the image processing device. (Configuration 2) The image processing device further includes a display unit for displaying a list screen of a transmission history for receiving an instruction to delete a post, The information processing system according to configuration 1, wherein on the list screen, a post delete button is displayed in a selectable state when a post corresponding to a selected transmission history can be deleted. (Configuration 3) The information processing system according to configuration 2, wherein a post can be deleted when the chat service in which the post was made supports a function for deleting posts. (Configuration 4) The information processing system according to configuration 2 or 3, characterized in that when a sending history not associated with the currently logged-in user is selected on the list screen, the post deletion button is displayed in an unselectable state or is hidden. (Configuration 5) An information processing system according to any one of configurations 2 to 4, characterized in that if a given amount of time has elapsed since the posting request was sent, the post deletion button is displayed or hidden in an unselectable state. (Configuration 6) The list screen displays, as a transmission history, at least one of a status, a file name of a transmitted file, a message transmitted together with the file, a transmission destination, and a user name that instructed the transmission; The information processing system according to any one of configurations 2 to 5, characterized in that when an instruction is given to display detailed information of a transmission history selected on the list screen, a preview image of the transmitted file is displayed. (Configuration 7) The information processing system described in configuration 6, characterized in that when the image processing device receives a result of the deletion of a post executed on the chat server, the status of the transmission history is updated from Sent to Deleted. (Configuration 8) The information processing system described in any one of configurations 1 to 7, characterized in that when the linking server receives a request from the image processing device to delete a post to be sent to the chat service, if it is impossible to delete the post, it sends a request to the chat service to post a correction message indicating that the post was sent in error. (Configuration 9) The information processing system described in any one of configurations 1 to 8, characterized in that when the linked server receives from the image processing device a request to delete a post to be sent to the chat service, if the post can be deleted and the file of the post has already been downloaded to the chat service, the linked server sends a request to the chat service to post a correction message indicating that the post was sent in error.

[0134] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a 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 implements one or more of the functions.

[0135] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

Claims

1. An information processing system including an image processing device having a scanner, a chat server providing a chat service, and a linking server relaying communication between the image processing device and the chat server, The image processing device includes: a first transmission means for transmitting a posting request for posting a scanned image file generated by scanning with the image processing device to the chat service; a management means for managing a transmission history of the transmission of the posting request and an identifier that uniquely identifies the posting issued by the chat server in association with each other; a second transmission means for transmitting a request to delete the post together with an identifier corresponding to the post to the chat service when an instruction to delete the post is received; The chat server, an issuing means for posting the file based on the posting request from the image processing device and issuing an identifier that uniquely identifies the posting; A transmission means for transmitting the identifier to a source requesting the posting; a deletion means for deleting the post corresponding to the identifier in response to a deletion request from the image processing device.

2. The image processing device further includes a display unit for displaying a list screen of a transmission history for receiving an instruction to delete a post, The information processing system according to claim 1 , wherein a post delete button is displayed in a selectable state on the list screen when a post corresponding to a selected transmission history can be deleted.

3. 3. The information processing system according to claim 2, wherein a post can be deleted when the chat service in which the post is made supports a function for deleting posts.

4. The information processing system according to claim 2, characterized in that when a sending history not linked to the currently logged-in user is selected on the list screen, the post deletion button is displayed in an unselectable state or is hidden.

5. 3. The information processing system according to claim 2, wherein, when a given time has elapsed since the transmission of the posting request, the posting deletion button is displayed in an unselectable state or is hidden.

6. The list screen displays, as a transmission history, at least one of a status, a file name of a transmitted file, a message transmitted together with the file, a transmission destination, and a user name that instructed the transmission; 3. The information processing system according to claim 2, wherein when an instruction is given to display detailed information of a transmission history selected on the list screen, a preview image of the transmitted file is displayed.

7. The information processing system according to claim 6, characterized in that when the image processing device receives a result of the deletion of a post executed on the chat server, the status of the transmission history is updated from "sent" to "deleted."

8. The information processing system described in claim 1, characterized in that when the linking server receives a request from the image processing device to delete a post to be sent to the chat service, if it is not possible to delete the post, it sends a request to the chat service to post a correction message indicating that the post was sent in error.

9. The information processing system described in claim 1, characterized in that when the linking server receives a request from the image processing device to delete a post to be sent to the chat service, if the post can be deleted and the file of the post has already been downloaded to the chat service, it sends a request to the chat service to post a correction message indicating that the post was sent in error.

10. An image processing device including a scanner, a first transmission means for transmitting a posting request for posting a scanned image file generated by scanning to a chat service; a management means for managing a transmission history of the transmission of the posting request and an identifier that uniquely identifies a posting issued in the chat service based on the posting request in association with each other; and a second sending means for, when an instruction to delete a post is received, sending a request to delete the post together with an identifier corresponding to the post to the chat service.

11. A method for controlling an information processing system including an image processing device having a scanner, a chat server providing a chat service, and a linking server relaying communication between the image processing device and the chat server, comprising: a step of transmitting a posting request to post a scanned image file generated by scanning the image processing device to the chat service; posting the file in the chat server based on the posting request from the image processing device and issuing an identifier that uniquely identifies the posting; transmitting the identifier to a requester of the posting in the chat server; managing, in the image processing device, a transmission history of the transmission of the posting request and an identifier that uniquely identifies the posting issued by the chat server in association with each other; When an instruction to delete a post is received in the image processing device, a request to delete the post together with an identifier corresponding to the post is transmitted to the chat service; and deleting the posting corresponding to the identifier in the chat server in response to a deletion request from the image processing device.

12. A method for controlling an image processing device including a scanner, comprising: A step of transmitting a posting request to post the scanned image file generated by scanning to a chat service; managing a transmission history of the transmission of the posting request and an identifier that uniquely identifies a posting issued in the chat service that was posted based on the posting request in association with each other; when an instruction to delete a post is received, transmitting a request to delete the post together with an identifier corresponding to the post to the chat service.

13. A program for causing a computer of an image processing apparatus to execute each step according to claim 12.

Images