INFORMATION PROCESSING APPARATUS, CONTROL METHOD, STORAGE MEDIUM, AND SYSTEM

A control method for an information processing apparatus, the information processing apparatus being capable of communicating with a server, the server being capable of communicating with an image processing apparatus, the method comprising: receiving setting of information about scanning; transmitting, to the server, scan-job setting information based on the received setting of information about scanning; and acquiring scan data from the server, the scan data being generated through the scanning performed by the image processing apparatus based on the scan-job setting information, wherein the acquired scan data is displayed in a predetermined area on a display unit of the information processing apparatus.

BACKGROUND

Field

The present disclosure relates to an information processing apparatus, a control method, a storage medium, and a system.

Description of the Related Art

Recently, communication using a chat function is known. For example, there is an application program called a collaboration tool which enables collaborative work on a network. In addition, an enhanced application program called a plug-in may be introduced to a collaboration tool. Japanese Patent Laid-Open No. 2021-83019 describes a function related to an enhanced application introduced to a collaboration tool.

It has been demanded that user convenience of a function related to an enhanced application introduced to a collaboration tool be further improved.

SUMMARY

According to an aspect of the present disclosure, a control method for an information processing apparatus, the information processing apparatus being capable of communicating with a server, the server being capable of communicating with an image processing apparatus, the method comprising: receiving setting of information about scanning; transmitting, to the server, scan-job setting information based on the received setting of information about scanning; and acquiring scan data from the server, the scan data being generated through the scanning performed by the image processing apparatus based on the scan-job setting information, wherein the acquired scan data is displayed in a predetermined area on a display unit of the information processing apparatus.

DESCRIPTION OF THE EMBODIMENTS

The present disclosure will be described below in detail by referring to the drawings. Embodiments described below do not limit the present disclosure describing the scope of claims. All combinations of features described in the present embodiments are not necessarily essential for the solution described in the present disclosure. In the attached drawings, the same reference numerals are assigned to the same or similar configurations, and repeated description will be avoided.

First Embodiment

An enhanced application called a plug-in introduced to a collaboration tool may be invoked, for example, from a predetermined area in a chat area of the collaboration tool or an area, in which an enhanced application is selectable, in a menu area for selecting a function or a chat room of the collaboration tool. The predetermined area in a chat area refers, for example, to an object, such as an icon or a button. The area, in which an enhanced application is selectable, in a menu area refers, for example, to an icon button. A chat area and a menu area for selecting a function of the collaboration tool are displayed in the same predetermined screen, or may be displayed on different screens. An enhanced application serves as an information processing system which is capable of submitting a scan job to an external image processing apparatus and posting, to a posting destination specified on the collaboration tool, the scan result (scan data) obtained through scanning on the image processing apparatus.

In such an information processing system, when scanning is performed by the image processing apparatus to generate scan data, the scan data is posted automatically to a predetermined posting destination on the collaboration tool.

However, when the generated scan data is data which is not intended by a user, the unintended scan data may be posted automatically to the predetermined posting destination on the collaboration tool. For example, when an image, which is not intended by a user, is scanned, the unintended scan data may be posted to the predetermined posting destination. In addition, for example, when a setting value, which is not intended by a user, is used in scanning, the unintended scan data may be posted to the predetermined posting destination.

Accordingly, in the present embodiment, before scan data is posted to a predetermined posting destination, a preview image of the scan data is displayed on a collaboration tool. After display of the preview image of the scan data, a posting instruction is allowed to be received. Thus, the scan data is posted to the predetermined posting destination.

Thus, when generated scan data is data which is not intended by a user, occurrence of posting the unintended scan data automatically to a predetermined posting destination on a collaboration tool may be reduced. By usingFIG.1, the configuration of a communication system provided by the present disclosure will be described. The system configuration according to the present embodiment includes an information processing apparatus110, an image processing apparatus120, a collaboration-tool information management server130, a data server140, and a collaboration tool server150. The data server140is a server (an external server of the collaboration-tool information management server130) to which the collaboration-tool information management server130uploads data. For example, in the present embodiment, a scan result file generated by the image processing apparatus120is uploaded to the data server140. The collaboration tool server150is a server (an external server of the collaboration-tool information management server130) which is constructed and managed by an external vendor which provides the collaboration tool. For example, in the present embodiment, the collaboration-tool information management server130transmits, to the collaboration tool server150, an instruction to post data to an enhanced application. The data server140and the collaboration tool server150will not be described in detail.

In the system illustrated inFIG.1, the information processing apparatus110, the MFP120, the collaboration-tool information management server130, the data server140, and the collaboration tool server150perform communication through the Internet100. Examples of a communication system which is used in communication between the apparatuses include a communication standard (Wi-Fi) of IEEE802.11 series and Bluetooth (such as Bluetooth Classic and Bluetooth Low Energy (BLE)). In the system according to the present embodiment, the apparatuses may be connected directly. Alternatively, communication between the apparatuses may be performed through Internet communication by way of a wireless local-area network (LAN) router. Alternatively, the apparatuses may communicate through mobile communication (3rd generation (3G) or 4th generation (4G), 5th generation (5G)).

The information processing apparatus110, the collaboration-tool information management server130, the data server140, and the collaboration tool server150are, for example, personal computers (PCs). However, the configuration is not limited to this, and various devices, such as a smartphone, a tablet terminal, and a digital camera, may be used as the information processing apparatus110, the collaboration-tool information management server130, and the data server140according to the present embodiment. The image processing apparatus120may be, for example, a printing device (printer). The printing device refers to a device having a recording device provided with a print function of recording information on a print medium by using a recording material. In addition, for example, the image processing apparatus120may be a device which further includes a reading device which reads an image on a document and which serves as a copier, or a multi-function peripheral (MFP) having other additional functions. The print system of the image processing apparatus120may be an electrophotographic system, an inkjet system, or another system. For the image processing apparatus120, for example, various devices, such as a PC, a smartphone, a tablet terminal, and a digital camera, may be used as the image processing apparatus120according to the present embodiment. Hereinafter, the image processing apparatus120is referred to as the MFP120.

A collaboration tool application301, which accesses the collaboration tool server150to provide a chat function, is installed in the information processing apparatus110, and is operable in the information processing apparatus110. The collaboration tool application301is capable of performing a Web application (enhanced application)701as a plug-in which enables an enhancement, and is capable of generating information of a scan job which is to be executed by the MFP120. That is, the Web application (enhanced application)701is capable of operating in the information processing apparatus110. The MFP120communicates with the collaboration-tool information management server130to receive/transmit information about the collaboration tool, and performs scanning on the basis of information about a received scan job. The collaboration-tool information management server130provides Web content for use in the collaboration tool application301of the information processing apparatus110. In addition, the collaboration-tool information management server130stores information about a scan job generated by the information processing apparatus, temporarily stores a scan result file obtained through scanning on the MFP120, and stores scan capability values of the MFP120. Further, the collaboration-tool information management server130provides the stored file to the information processing apparatus110or the MFP120, and transmits data to the data server140or the collaboration tool server150. The data server140stores a scan result file obtained through scanning on the MFP120. In addition, the data server140provides the link to a stored file to the chat function of the collaboration tool server150to implement posting of a chat message, which involves the file. The collaboration tool server150provides functions, related to chatting, to the information processing apparatus110or the collaboration-tool information management server130.

In the present embodiment, description will be made by taking, as an example, a form in which scan job information is received/transmitted in communication between the apparatuses in the system inFIG.1. The configuration is not limited to scan job information. Any information may be employed as long as the present embodiment may be carried out by using the information.

By usingFIG.2, the hardware configuration of the information processing apparatus110will be described. The information processing apparatus110according to the present embodiment is assumed to be an apparatus, such as a PC, a smartphone, or a tablet. Any other apparatus may be employed as long as it is an information processing apparatus which is capable of communicating with the Internet100.

A central processing unit (CPU)201reads control programs stored in a read-only memory (ROM)202, and performs various processes for controlling operations of the information processing apparatus110. The ROM202stores control programs. A random-access memory (RAM)203is used as a temporary storage area, such as a main memory and a work area, of the CPU201. A hard disk drive (HDD)204stores various data, such as photographs and electronic documents. The collaboration tool application301described below is also stored in the HDD204. An input unit205receives input on the information processing apparatus110. The input may be performed by using an external terminal, or may be performed by using a unit attached to the information processing apparatus, such as a touch panel. A display unit206displays various screens. The display unit206may have a touch panel function which is capable of detecting a user's touch operation. A communication unit207performs telecommunication by using the Internet100.

By usingFIG.3, the software configuration of the information processing apparatus110will be described.FIG.3is a functional block diagram for describing software implemented by the CPU201reading control programs stored in the ROM202and the HDD204. The collaboration tool application301may use the collaboration tool through communication with the collaboration tool server150, and allows communication with people by using chats. In addition, the collaboration tool application301may read, onto the RAM203, a manifest file, which is stored in the HDD204, to perform the Web application701, described below, as a plug-in which enables an enhancement of the collaboration tool.

The information processing apparatus110may use various applications other than the collaboration tool, which are not described.

By usingFIG.4, the hardware configuration of the MFP120will be described. A controller410including a CPU411controls the operations of the entire apparatus. The CPU411reads control programs, which are stored in a ROM412and an HDD414, to perform various control processes. A RAM413is used as a temporary storage area, such as a main memory and a work area, of the CPU411. The HDD414stores various programs and data. An operation unit I/F415connects an operation unit419to the controller410. The operation unit419includes a liquid-crystal display having a touch panel function. A printer I/F416connects a printer420to the controller410. A scanner I/F417connects a scanner421to the controller410. A network I/F418connects the controller410to the Internet100.

By usingFIG.5, the software configuration of the MFP120will be described. The CPU411reads programs, which are stored in the HDD414of the MFP120, onto the RAM413for analysis and execution. Thus, the processes described below are performed. A login management unit501manages user authentication in the MFP120. A menu display unit502displays menu screens on the operation unit419. The menu display unit502displays buttons (hereinafter referred to application buttons) for invoking applications on the menu screens. The application buttons are buttons for invoking various functions, such as applications installed in the MFP120and Web applications. A device registration application503registers information about the MFP120in the collaboration-tool information management server130. A collaboration-tool cooperative application504accesses the collaboration-tool information management server130to display Web content. A scanner controller505scans documents through operations on the scanner I/F417.

By usingFIG.6, the hardware configuration of the collaboration-tool information management server130will be described.

A CPU601reads control programs, which are stored in a ROM602, to perform various processes for controlling operations of the collaboration-tool information management server130. The ROM602stores control programs. A RAM603is used as a temporary storage area, such as a main memory and a work area, of the CPU601. An HDD604stores various data, such as photographs and electronic documents. A communication unit605performs telecommunication using the Internet100.

By usingFIG.7, the software configuration of the collaboration-tool information management server130will be described.

FIG.7is a functional block diagram for describing software implemented by the CPU601reading control programs stored in the ROM602and the HDD604. The Web application701is an application which is capable of generating scan job settings used in scanning on the MFP120. The Web application701is an application which is read, operated, and performed by the collaboration tool application301. An event processing application702is an application which performs processes for events transmitted to the collaboration-tool information management server130. A database703manages information used by the Web application701and the event processing application702. The information is held in the HDD604.

FIG.8is a flowchart of an exemplary process performed so that, in the MFP120, the device registration application503uploads device capability information of the MFP120to the collaboration-tool information management server130, and registers the MFP120as a device which is to be used by a login user.

Hereinafter, a user who has logged in the MFP120is referred to as a login user.

FIG.15illustrates exemplary data on a collaboration-tool information management server.

FIGS.17A to17Kare diagrams illustrating transitions of screens displayed on the operation unit419of the MFP120.

FIG.21illustrates exemplary data stored in the MFP120.

The process of the flowchart inFIG.8will be described by usingFIGS.15,17A to17K, and21.

The process of the flowchart starts in response to selection (hereinafter referred to as pressing) of a device registration button1714in a top menu screen1710inFIG.17B. In addition, the process starts after completion of a user login process on a login screen1700. A user's name and password are input to a user name input field1701and a password input field1702, and a login button1703is pressed. Then, the login process is completed.

In S801, the device registration application503determines whether a device registration button1716has been pressed. If the determination result in S801is YES, the process proceeds to S802. If the determination result is NO, the process returns to S801.

In S802, the device registration application503obtains a mail address which is address information of the login user. The MFP120has user information2100, as illustrated inFIG.21, for each user, and the user information2100is stored in advance in the HDD414. Thus, a mail address2102associated with a user ID2101may be obtained.

In S803, the device registration application503obtains scan capability information of the MFP120. The scan capability information refers to setting values allowed in various settings. The scan capability information obtained in this step is to be stored in scan capability information1540of the collaboration-tool information management server130. The scan capability information1540will be described. A device ID1541is an identification (ID) unique to an MFP120, and is information with which the MFP120may be identified uniquely. An allowable color setting1542indicates color settings settable in scanning, and has color information, such as color and gray. An allowable resolution setting1543indicates resolution settings settable in scanning, which are, for example, 600×600, 300× 300, and 100×100. An allowable sheet-size setting1544indicates sheet size settings settable in scanning, and has size information, such as A4, A3, B5, and B4. An allowable single/double-sided setting1545indicates single/double-sided settings settable in scanning, and has values of single sided, double sided (horizontal opening), and double sided (vertical opening). An allowable scaling setting1547indicates scaling settings settable in scanning, and has, for example, values of 50%, 100%, and 200%. An allowable file-format setting1546indicates file formats to which files may be converted after scanning, and has, for example, values of JPEG, PDF, and OOXML.

In S804, the device registration application503transmits, to the event processing application702of the collaboration-tool information management server130, the mail address, which is obtained in S802, and the scan capability information, which is obtained in S803. Thus, user information1530and the scan capability information1540, which are illustrated inFIG.15, are generated on the collaboration-tool information management server130, and information indicating the MFP120is registered in device-to-be-used information1532. Multiple devices may be registered in the device-to-be-used information1532. Thus, when S804is performed by an MFP different from the MFP120, the device ID1541of the MFP, which is a different device, is added to the device-to-be-used information1532.

FIGS.9A and9Bare a flowchart of an exemplary process performed so that, in the information processing apparatus110, the collaboration tool application301uses screen information, which is obtained from the Web application701, to register scan-job setting information to the collaboration-tool information management server130.

FIG.11is a diagram illustrating exemplary context information stored in the collaboration tool server150.

FIGS.12A and12Bare diagrams illustrating an exemplary screen (scan-job application screen)1201which includes a scan job setting area and which is displayed on the display unit206of the information processing apparatus110. In the scan-job application screen1201, the scan job setting area (inFIG.12A) may be displayed, and an area for prompting a process on the MFP (inFIG.12B) may be displayed. Setting areas1204to1208,1210to1211, and1213to1218, which are described below, each have a configuration in which a list of setting values, from which a setting value other than an initially displayed setting value may be selected by using a pull-down button provided on the right side of the setting area, is displayed.

FIG.20is a diagram illustrating exemplary screens which are displayed on the display unit206of the information processing apparatus110and which include a chat room area (chat area) from which display of a list of setting values may be invoked.

The process of the flowchart inFIGS.9A and9Bwill be described by usingFIGS.11,12A,12B, and20.

The process of the flowchart starts in response to the state in which, after a user uses the collaboration tool application301to perform a login process by using their user account, the user selects an area for starting the Web application701. For example, the area for starting the Web application701is an MFP-cooperative plug-in application start button2013. In addition, for example, the area for starting the Web application701is an MFP-cooperative plug-in application start button2015included in a predetermined area in a chat area2014. The predetermined area in the chat area2014is, for example, is an area which is indicated by “ . . . ” in the chat area2014inFIG.20and selection of which causes a menu area, from which the Web application701is selectable, to be opened.

In S901, the collaboration tool application301reads, onto the RAM203, a manifest file for a plug-in application stored in the HDD204.

In S902, the collaboration tool application301accesses a uniform resource locator (URL) described in the manifest file. The URL destination is the collaboration-tool information management server130. The Web application701transmits screen information, and the collaboration tool application301thus obtains the screen information.

In S903, the collaboration tool application301obtains pieces of context information from the collaboration tool server150. The pieces of context information describe data illustrated inFIG.11. The pieces of context information are a user ID1101and a user name1102, a team ID1103and a team name1104of a plug-in invocation source, a channel ID1105and a channel name1106of the plug-in invocation source, and a person ID1107and a person name1108of the plug-in invocation source. These are values which change in accordance with how the plug-in application is invoked. For example, as illustrated inFIG.20, when the plug-in application is invoked from the plug-in application start button2015in the state in which a chat room2012is selected, information about the chat screen2014is stored in the pieces of context information1103to1106. Similarly, when the plug-in application is invoked from the plug-in application start button2015in the state in which a personal chat room2016is selected, information about the chat screen2014is stored in the pieces of context information1107and1108. However, when the plug-in application is invoked from the plug-in application start button2013, since the plug-in application is invoked from the outside of the chat screen, chat screen information fails to be detected, and values are not stored in the pieces of context information1103to1108.

In S904, the collaboration tool application301obtains the user information1530, which is registered in the collaboration-tool information management server130, from the user ID1101in the context. Further, the collaboration tool application301obtains the scan capability information1540, which is registered by a user in S804inFIG.8, from the device-in-use1532included in the user information1530.

In S905, the collaboration tool application301obtains, from the collaboration tool server150, team IDs, channel IDs, and user IDs, in or with which the login user may chat, and a list of the names of these.

In S906, the collaboration tool application301determines whether the invocation-source area information, which indicates the source, in the context, from which the application has been invoked, indicates a chat area or an area for invoking a Web application. The chat area refers to the cooperative plug-in application start-button area2015; the area for invoking a Web application refers to the cooperative plug-in application start-button area2013. Specifically, the collaboration tool application301checks the plug-in invocation-source team name1104and the plug-in invocation-source channel name1106, or the plug-in invocation-source person ID1108. When either one of these holds value, it is determined that the invocation source is the chat area. When these do not hold a value, it is determined that the invocation source is an area for invoking a Web application. In S906, if it is determined that the invocation source is a chat area, the process proceeds to S908. If it is determined that the invocation source is an area for invoking a Web application, the process proceeds to S907.

In S907, the collaboration tool application301displays, in the posting-destination team1204and the posting-destination channel1205illustrated inFIG.12Adescribed below, a posting destination which satisfies a preset initial display condition. Then, the process proceeds to S909. The condition (initial display condition) of the posting destination (initial display), which is displayed initially, is the posting destination (most-commonly-posted destination) to which scan data has been posted the most by using the user information of the user who has logged in. The most-commonly-posted destination refers to a team/channel obtained as follows: in S1315and S1811described below, the count of scan result files posted from the MFP120is measured for each team/channel of posting destination, and the team/channel having the most count is the most-commonly-posted destination. That is, when the Web application701is invoked from the area for invoking a Web application, as a posting destination to which scan data is to be posted, the posting destination based on usage information of the user account is displayed in the posting-destination team1204and the posting-destination channel1205as initial values. For example, when the most-commonly-posted destination of a login user is Team A/Channel 1, as illustrated inFIG.12A, “Team A” and “Channel 1” are displayed in the posting-destination team1204and the posting-destination channel1205, respectively. When the pull-down button (posting-destination list display button) on the right side of the posting-destination team1204is selected, information of teams/persons other than “Team A” which is initially displayed in the posting-destination team1204is displayed as a posting-destination list (selection area). For example, information of teams/persons displayed in the posting-destination list is displayed in the descending order of the counts of scan result files posted from the MFP120. When information of a team/person is selected in the posting-destination list, the selected team/person information is displayed in the posting-destination team1204instead of “Team A” which is initially displayed.

In S908, the collaboration tool application301sets setting values, which are to be displayed as a posting destination, from the plug-in invocation source screen information described in the context. For example, the plug-in invocation-source team name1104is displayed in the posting-destination team1204, and the plug-in invocation-source channel name1106is displayed in the posting-destination channel1205. That is, when the Web application701is invoked from a chat area, as a posting destination to which scan data is to be posted, the posting destination based on the chat area, which is the invocation source, is displayed in the posting-destination team1204and the posting-destination channel1205as initial values. For example, when the plug-in is invoked from Team A/Channel 1, as illustrated inFIG.12A, “Team A” and “Channel 1” are displayed in the posting-destination team1204and the posting-destination channel1205, respectively. When the pull-down button on the right side of the posting-destination team1204is selected, information of teams/persons other than “Team A”, which is initially displayed in the posting-destination team1204, is displayed as a posting-destination list. For example, information of teams/persons displayed in the posting-destination list is displayed in the descending order of the counts of scan result files posted from the MFP120. When team/person information is selected in the posting-destination list, the selected information of a team/person is displayed in the posting-destination team1204instead of “Team A” which is initially displayed.

In S909, the collaboration tool application301displays the scan-job application screen1201of the Web application701.

The scan-job application screen1201displays a scan job setting area1202, in which setting values used in execution of scanning, a posting destination of the scanned file, the access permission of the file, and the like are set, and a preview display area1203.

In the scan job setting area1202, user interfaces, such as pull-down menus, a text box, a text area, a checkbox, and a button, are present. The setting values from the posting-destination team/person1204to the scaling1218are stored in the RAM203as the scan-job setting information. The scan-job setting information is data having the same structure as that of the scan-job setting information1500inFIG.15. The posting-destination team/person1204displays a list of team names and user names, which are obtained in S905and in or with which the login user may chat, through the user's pull-down selection.

FIG.10is used to describe the relationship between tenant, team channel, and user. Tenant Z1000includes Team A (1001), Team B (1002), user 1 (1003), user 2 (1004), and user 3 (1005). Team A (1001) includes Channel 1 (1006) and Channel 2 (1007), each of which has a chat room. Channel 1 (1006) includes user 1 (1003) and user 2 (1004) who participate in the chat room. For each channel, users who participate in the channel may be managed. For example, user 1 (1003) and user 2 (1004) participate in Channel 1 (1006), while user 1 (1003), user 2 (1004), and user 3 (1005) participate in Channel 2 (1007). The options of the pull-down menu of the posting-destination team/person1204are teams and users included in Tenant Z1000, and are teams/persons1001to1005. The posting-destination channel1205displays a list of selectable channels through a user's pull-down selection. A list of selectable channels will be described below. The file name1206receives a user's input of characters in the text box to determine the name of a file generated in scanning. The file format1207is Portable Document Format (PDF), Office Open XML (OOXML), or Joint Photographic Experts Group (JPEG). However, the file format handled in the present disclosure is not limited to the formats described above. The mentioning setting1208is a pull-down menu for specifying which user is to be notified, which is used in a function, “mentioning”, of notifying a specified user (user information). Users, who may be specified in the pull-down menu, are, for example, inFIG.10, user 1, user 2, and user 3 belonging to Tenant Z1000. The comment1209is a message displayed when a scan result is posted to a chat room. The view permission1210and the edit permission1211are pull-down menus for specifying which permission, view permission or edit permission, of a scan result file posted to a chat room is granted to which user who participates in the chat room. Users, who may be specified in the pull-down menu, are, for example, inFIG.10, user 1, user 2, and user 3 belonging to Tenant Z1000, or a setting, “the same as the mentioning target”, is allowed. The posting-after-preview checkbox1212is a checkbox for setting whether scan data is to be confirmed in the preview area1203before the scan result file is posted to a chat room. The scan device selection1213displays a list of devices, which are registered inFIG.8, through a user's pull-down selection. The color setting1214to the scaling1218are scan setting items used when the MFP120performs scanning. The register1219is a button for registering a job through pressing after completion of job setting. Steps S910to S923, which are subsequent steps, are repeatedly performed until the condition in S925is satisfied.

Back toFIG.9B, the flowchart will be described.

In S910, the collaboration tool application301receives a user operation event. A user operation event occurs by a user operating a user interface in the scan job setting area1202and completing the operation. Specifically, in the case of a pull-down menu, a user operation event occurs when any of options, which are displayed through pressing the pull-down button, is selected. In the case of a text box and a text area, a user operation event occurs when characters are input and the cursor then goes out of the input field. In the case of a checkbox, a user operation event occurs when the checkbox is checked or unchecked. In the case of a button, a user operation event occurs when the button is pressed.

In S911, the collaboration tool application301determines which item has been operated in S910. If it is determined that the scan device selection1213has been operated, the collaboration tool application301proceeds to S912. If it is determined that the register1219has been operated, the collaboration tool application301proceeds to S914. If it is determined that an item other than the two items described above has been operated, the collaboration tool application301proceeds to S918.

In S912, the collaboration tool application301obtains, from the collaboration-tool information management server130, the scan capability information of the device selected in the scan device selection1213, and stores the scan capability information in the RAM203. The scan capability information described above is data having the same structure as that of the scan capability information1540inFIG.15. The collaboration tool application301compares the obtained scan capability information with the setting values of the color setting1214to the scaling1218of the scan-job setting information on the RAM203. When various settings included in the scan-job setting information are not included in the setting values of the scan capability information, the setting values of such setting items are changed to defaults or nulls, and the scan-job setting information is updated. Default values are obtained from the scan capability information (not illustrated).

The reason why nulls are used is, for example, that, even when a device used in scanning does not support scaling setting, scanning is allowed to be performed.

In S913, the collaboration tool application301filters the options, which are to be displayed when pull-down buttons of the color setting1214to the scaling1218are selected, to setting values included in the scan capability information obtained in S912. The collaboration tool application301updates the display of the color setting1214to the scaling1218. When no device is selected in the scan device selection1213, the options of the color setting1214to the scaling1218are all setting values which are settable.

For example, when a device, which supports the sheet sizes of A4, A5, and A6, is selected in the scan device selection1213, the sheet size options are A3, A4, A5, A6, and B4 before the selection, and are A4, A5, and A6 after the selection. When the color setting1214to the scaling1218have been already selected, the values of the color setting1214to the scaling1218are deleted, and blanks are displayed in the color setting1214to the scaling1218.

In S914, the collaboration tool application301checks whether the scan-job setting information on the RAM203has invalid setting values. Specifically, the posting-destination team/person1204and the posting-destination channel having no values cause invalid values (errors) because a chat room to which a scan result image is to be posted is unknown.

In S915, the collaboration tool application301determines whether the result in S914indicates invalid values. If the determination result in S915is YES, the process proceeds to S917. If the determination result in S915is NO, the process proceeds to S916.

In S916, the collaboration tool application301transmits, to the collaboration-tool information management server130, the scan-job setting information on the RAM203, and requests registration of the job. The job registration process by the collaboration-tool information management server130will be described below in the description aboutFIGS.13A and13B.

In S917, the collaboration tool application301displays a pop-up error screen (not illustrated) indicating that setting values of the scan-job setting information are invalid.

In S918, the collaboration tool application301updates the scan-job setting information on the RAM203by using the selected setting value.

In S919, the collaboration tool application301determines what is the setting operation determined in S911. If a team has been set in the posting-destination team/person1204, the process proceeds to S920. If it is determined that a person has been set in the posting-destination team/person1204, the process proceeds to S923. If it is determined that a posting-destination channel has been set, the process proceeds to S921. If it is determined that an item other than those described above has been set, the process proceeds to S925.

In S920, the collaboration tool application301filters the options, which are to be displayed when a pull-down button of the posting-destination channel1205is selected, to those associated with the selected team, and updates the display of the posting-destination channel1205. Specifically, when Team A1001inFIG.10is selected in the posting-destination team/person1204, the options, which are to be displayed when the pull-down button of the posting-destination channel1205is selected, are only Channel 1 and Channel 2, and Channel X and Channel Y are not included in the options. When the posting-destination channel1205has been already selected, the value of the posting-destination channel of the scan-job setting information is deleted, and a blank is displayed in the posting-destination channel1205.

In S921, the collaboration tool application301filters the options, which are to be displayed when the pull-down button of the mentioning1208is selected, to those associated with the selected channel, and updates the display of the mentioning1208. Specifically, when Channel 1 inFIG.10is selected in the posting-destination channel1205, the options, which are to be displayed when the pull-down button of the mentioning1208is selected, are user 1 and user 2, and user 3 is not included in the options. When the mentioning1208has been already selected, the value of the mentioning target of the scan-job setting information is deleted, and a blank is displayed in the mentioning1208.

In S922, the collaboration tool application301filters the options, which are to be displayed in response to selection of the pull-down buttons of the view permission1210and the edit permission1211which indicate access permission settings for setting user information accessible to the scan data, only to those associated with the selected channel. At least when at least one of the pull-down buttons of the view permission1210and the edit permission1211is selected, the collaboration tool application301updates, for display, the options of each permission. Specifically, when Channel 1 inFIG.10is selected in the posting-destination channel1205, the options, which are to be displayed when the pull-down buttons of the view permission1210and the edit permission1211are selected, are user 1, user 2, and “the same as mentioning target”, and user 3 is not included in the options. When “the same as mentioning target” is selected in the options for the pull-down button of the view permission1210, view permission is granted to the same user information as that set in the mentioning1208. The same is true for the edit permission1211. When the view permission1210and the edit permission1211have been already selected before update of the display, the values selected and displayed in the view permission1210and the edit permission1211of the scan-job setting information are deleted, and blanks are displayed in the view permission1210and the edit permission1211. Depending on the file format selected in the file format1207, whether reception of setting of user information, to which edit permission is granted, is allowed may be changed. Specifically, when the file format selected in the file format1207is PDF format or OOXML format, reception of setting of user information, to which edit permission is granted, may be allowed. When the file format selected in the file format1207is a format other than PDF format and OOXML format, reception of setting of user information, to which edit permission is granted, may not be allowed. For example, when the file format selected in the file format1207is a format other than PDF format and OOXML format, the edit permission1211may be displayed in gray out.

In S923, the collaboration tool application301filters the options, which are to be displayed when the pull-down button of the mentioning1208is selected, to those for the selected person, and updates display of the mentioning1208. Specifically, when user 1 inFIG.10is selected in the posting-destination team/person1204, the options, which are to be displayed when the pull-down button of the mentioning1208is selected, are only user 1, and user 2 and user 3 are not included in the options. When the mentioning1208has been already selected, the value of the mentioning target of the scan-job setting information is deleted, and a blank is displayed in the mentioning1208.

In S924, the collaboration tool application301filters the options, which are to be displayed when the pull-down buttons of the view permission1210and the edit permission1211are selected, to those for the selected person. The collaboration tool application301updates display of the view permission1210and the edit permission1211. Specifically, when user 1 inFIG.10is selected in the posting-destination team/person1204, the options, which are to be displayed when the pull-down buttons of the view permission1210and the edit permission1211are selected, are user 1, and user 2 and user 3 are not included. When the view permission1210and the edit permission1211have been already selected, the values of the view permission1210and the edit permission1211of the scan-job setting information are deleted, and blanks are displayed in the view permission1210and the edit permission1211.

In S925, if it is determined that the operation is pressing of the registration button, the collaboration tool application301proceeds to S926. If it is determined that the operation is not pressing of the registration button, the collaboration tool application301proceeds to S910.

In S926, the collaboration tool application301displays a screen (pop-up screen)1220including a pop-up notification inFIG.12B. A message1221is a message for prompting the MFP120to perform a login process and perform scanning (execution of a scan execution instruction). When a close button1222is pressed, the pop-up screen is closed.FIGS.13A and13Bare a flowchart of an example of the event processing application702of the collaboration-tool information management server130receiving events from the information processing apparatus110and the MFP120to perform various processes.

FIG.15is a diagram illustrating exemplary data stored in the collaboration-tool information management server130.

The flowchart inFIGS.13A and13Bwill be described by usingFIGS.15,19A, and19B.

The flowchart starts by the CPU601reading the event processing application702stored in the HDD604after the collaboration-tool information management server130starts. The event processing application702repeatedly performs S1301to S1323to process various received events, and thus operates as a server.

In S1301, the event processing application702receives an event from the information processing apparatus110or the MFP120.

In S1302, the event processing application702determines which event has been received in S1301. If it is determined that the received event is a job registration request event from the information processing apparatus110, the process proceeds to S1303. If it is determined that the received event is a scan completion event from the MFP120, the process proceeds to S1305. If it is determined that the received event is a posting request event from the information processing apparatus110, the process proceeds to S1318. If it is determined that the received event is a temporarily-stored file acquisition event from the information processing apparatus110, the process proceeds to S1321. If it is determined that the received event is a job-list acquisition event from the MFP120, the process proceeds to S1322.

In S1303, the event processing application702stores (registers), in the database703, the scan-job setting information1500, illustrated inFIG.15, from the received data. A user ID1501is used to uniquely identify a user who uses the system. In the present embodiment, a mail address is used. A job ID1502is information for uniquely identifying the scan-job setting information registered in the collaboration-tool information management server130. In the present embodiment, data obtained through incrementing from “000001” every time scan-job setting information is registered is used. A posting-destination team name1503is the name of a team to which a scan result file (scan data) is posted, and is the team name displayed in2011in a collaboration-tool application screen2010. A posting-destination team ID1504is an ID for uniquely identifying the team of the posting-destination team name1503, and is used in submitting a posting instruction to the collaboration tool server150. A posting-destination channel name1505is the name of a channel to which a scan result file is posted, and is a channel name displayed in2012in the collaboration-tool application screen2010. The posting-destination channel ID1506is an ID for uniquely identifying a channel of the posting-destination channel name1505, and is used in submitting a posting instruction to the collaboration tool server150. The posting-destination user name1507is the name of a user who posts a scan result file, and is a user name displayed in2016in the collaboration-tool application screen2010. The posting-destination user ID1508is an ID for uniquely identifying a chat of the posting-destination user name1507, and is used in submitting a posting instruction to the collaboration tool server150. In the present embodiment, posting to a channel and posting to a user are not allowed to be specified at the same time. When the pieces of posting-destination team/posting-destination channel information1503to1506are specified, the posting-destination user name and the posting-destination user ID are set to null. In contrast, when the pieces of posting-destination user information1507and1508are specified, the pieces of posting-destination team/posting-destination channel information1503to1506are set to null. A main text1510is a text which is to be displayed in2021in an after-posting-message screen2020in posting. The file name1511is the file name of a scan result, and is displayed in2022in the after-posting-message screen2020in posting. A mentioning target name1512is the name of a user to whom the mentioning is set in posting, and is displayed in2023in the after-posting-message screen2020in posting. A mentioning target name ID1513is an ID for uniquely identifying a mentioning target in posting, and is used in submitting a posting instruction to the collaboration tool. The progress state1514indicates the state of the job of the scan-job setting information. As the progress state, “job before execution”, “temporary storage”, “file upload completed”, “posting completed” are present. An execution finish flag1515is a flag indicating whether the job of the scan-job setting information has been executed once. “True” indicates that the job has been completed; “false” indicates that the job has not been performed. After that,1516to1521indicate various settings in execution of a scan job in the MFP120. A view permission setting1522indicates the user ID of a user who have view permission of a posted scan result file. An edit permission setting1523indicates the user ID of a user who has edit permission of a posted scan result file. A scan result file link is a link URL of storage of a scan result file in the data server140.

In S1304, the event processing application702changes (updates) the progress state of the scan-job setting information, which has been stored in the database703in S1303, to “job before execution”, and proceeds to S1323.

In S1323, the event processing application702determines whether a stop instruction to stop the server has been received. If it is determined that a stop instruction has been received, the process of the flowchart ends. If it is determined that a stop instruction has not been received, the process proceeds to S1301.

In S1305, the event processing application702writes, from the database703to the RAM603, scan-job setting information whose job ID matches that included in the scan completion event. The event processing application702determines whether the setting of a posting-after-preview setting1509of the scan-job setting information written in the RAM603is ON. If the determination result in S1305is YES, the process proceeds to S1306. If the determination result is NO, the process proceeds to S1308.

In S1306, the event processing application702stores the scan result file, which is included in the scan completion event, in the HDD604as a temporary file, and proceeds to S1307.

In S1307, the event processing application702updates, for storage, the progress state1514of the scan-job setting information in the database703, whose job ID matches that included in the scan completion event, to the “temporary storage” state, and proceeds to S1323.

In S1308, the event processing application702uploads, to the data server140, the scan result file included in the scan completion event. The event processing application702stores, in the scan result file link1524in the database703, the upload destination link returned as a response of the upload, and proceeds to S1309.

In S1309, the event processing application702determines whether user IDs are set to either one or both of the view permission setting1522and the edit permission setting1523of the scan-job setting information written in the RAM603in S1305. If it is determined that user IDs are set, the process proceeds to S1310. If it is determined that user IDs are not set, the process proceeds to S1313.

In S1310, the event processing application702determines whether or not the file format1520of the scan-job setting information, which is written in the RAM603in S1305, is PDF or OOXML. If the determination result is YES, the process proceeds to S1312. If the determination result is NO, the process proceeds to S1311.

In S1311, the event processing application702transmits, to the data server140, a specific instruction that, when the view permission setting1522of the scan-job setting information stores user IDs, the setting of the view permission of the uploaded file be changed so that the user IDs are allowed to view the file. The event processing application702transmits a specific instruction that, when the edit permission setting1523of the scan-job setting information stores user IDs, the setting of the view permission of the uploaded file be changed so that the user IDs are allowed to view the file.

In S1312, the event processing application702transmits, to the data server140, a predetermined instruction that, when the view permission setting1522of the scan-job setting information stores user IDs, the setting of the view permission of the uploaded file be changed so that the user IDs are allowed to view the file. The event processing application702transmits an instruction that, when the edit permission setting1523of the scan-job setting information stores user IDs, the setting of the edit permission of the uploaded file be changed so that the user IDs are allowed to edit the file.

In S1313, the event processing application702refers to the scan-job setting information in the database703, whose job ID matches that included in the scan-job setting information on the RAM603. The event processing application702updates, for storage, the progress state1514of the scan-job setting information in the database703with “file upload completed”, and proceeds to S1314.

In S1314, the event processing application702obtains a file link indicating the access destination to the file uploaded in S1308, and proceeds to S1315.

In S1315, the event processing application702instructs the collaboration tool server150to post a chat message. The chat message to be posted is created with the posting destination and the posting description determined by the scan-job setting information in the database703, and includes a file link indicating the access destination to the file. Thus, as illustrated in the after-posting-message screen2020inFIG.20, the scan result file is posted to the user-desired posting destination.

In S1317, the event processing application702updates, for storage, the progress state1514of the scan-job setting information in the database703with “posting completed”, and proceeds to S1323.

In S1318, the event processing application702uploads, to the data server140, the scan result file stored as a temporary file in the HDD604in S1306, and proceeds to S1319.

In S1319, the event processing application702deletes the scan result file stored as a temporary file in the HDD604in S1306, and proceeds to S1320.

In S1320, the event processing application702updates the scan-job setting information in the database703on the basis of the received data received in S1301, and proceeds to S1309. The scan-job setting information is updated to reflect the data, which has been set by a user in1901to1906inFIG.19A, on a chat message that is to be posted. The posting-destination team setting1901is an item for setting a posting-destination team or a person as a posting destination. The data which is set in the posting-destination team1204is displayed, and the displayed data may be changed by a user. The posting-destination channel setting1902is an item for setting a posting-destination channel. The data which is set in the posting-destination channel1205is displayed, and the displayed data may be changed by a user. The mentioning target setting1903is an item for setting a mentioning target used in posting. The data which is set in the mentioning target1208is displayed, and the displayed data may be changed by a user. The comment setting1904is an item for setting a comment used in posting. The data which is set in the comment1209is displayed, and the displayed data may be changed by a user. The view permission setting1905is an item for setting the user IDs of users who have view permission of the scan result file that is to be posted. The data which is set in the view permission setting1210is displayed, and the displayed data may be changed by a user. The edit permission setting1906is an item for setting the user IDs of users who have edit permission of the scan result file that is to be posted. The data which is set in the edit permission setting1211is displayed, and the displayed data may be changed by a user. When a scan result file button1907is pressed, a preview screen1909is displayed. The preview display area (hereinafter, preview screen)1909includes a preview1910of the scan result file. Pressing a close button1911may cause a return to the previous page (for example, a job detail screen1900). When a post button1908is pressed, the set items are reflected, and a request to post a chat message is transmitted to the collaboration-tool information management server130.

In S1321, the event processing application702transmits, to the connection source (information processing apparatus110), the scan result file stored as a temporary file in the HDD604in S1306, and proceeds to S1323.

In S1322, the event processing application702transmits, to the connection source (information processing apparatus110), the scan-job setting information1500, in the database703, which includes the user ID included in the received data received in S1301, and proceeds to S1323.

FIG.14is a flowchart of a process performed so that the collaboration-tool cooperative application504of the MFP120establishes a connection with the collaboration-tool information management server130to display the waiting-for-scan job list screen1720and the scan-completed job list screen1730inFIGS.17D and17E. The flowchart starts in response to pressing a “scan and transmit to collaboration tool” button1712after a login to the MFP120.

In S1401, the collaboration-tool cooperative application504obtains a mail address of the login user. The mail address is the same as that obtained in S802inFIG.8, and is associated with a user ID1531of the collaboration-tool information management server130.

In S1402, the collaboration-tool cooperative application504obtains a scan-job setting information list from the collaboration-tool information management server130by using the mail address obtained in S1401.

In S1403, the collaboration-tool cooperative application504displays the waiting-for-scan job list screen1720. The jobs, which are included in the scan-job setting information list obtained in S1402and whose job execution finish flags1515are not true, are displayed on a job list display unit1722. In S1404, the collaboration-tool cooperative application504determines whether a display job selection button1721has been changed. If the display job selection button1721has not been changed, the process proceeds to S1408. If the display job selection button1721has been changed, the process proceeds to S1405.

In S1405, the collaboration-tool cooperative application504determines whether the changed selection item is “scanned”. If the item is “scanned”, the process proceeds to S1406. If the item is “not scanned”, the process proceeds to S1407.

In S1406, the collaboration-tool cooperative application504displays the scan-completed job list screen1730. The jobs, which are included in the scan-job setting information list obtained in S1402and whose job execution finish flags1515are true, are displayed on a job list display unit1732. In S1407, like S1403, the collaboration-tool cooperative application504displays the jobs, which are included in the scan-job setting information list and whose job execution finish flags1515are not true, in the job list display unit1722.

In S1408, the collaboration-tool cooperative application504determines whether a job displayed on the operation unit419has been selected. If a job has not been selected, the process returns to S1404. If a job has been selected, the collaboration-tool cooperative application504stores the scan-job setting information of the selected job in the RAM413, and displays the scan setting screen1740.

FIGS.16A and16Bare a flowchart of a process performed so that the collaboration-tool cooperative application504of the MFP120establishes a connection with the collaboration-tool information management server130; a scan setting screen1740inFIG.17Fis displayed; and scanning is performed. The trigger for starting the flowchart is selection of a job displayed on the job list display units1722and1732.

In S1601, the collaboration-tool cooperative application504displays the scan setting screen1740inFIG.17Fon the basis of the scan-job setting information stored in the RAM413in S1408. The scan-job setting information described above is data having the same structure as that of the scan-job setting information1500inFIG.15. The scan setting screen1740displays a back-to-list button1741, a transmission destination1742, a color setting button1743, an image quality setting button1744, a sheet size button1745, a double-sided setting button1746, a detail setting button1747, and a delete button1748. The back-to-list button1741makes a screen transition to the waiting-for-scan job list screen1720through pressing. The transmission destination1742displays the posting-destination channel name and the posting-destination team name of the scan-job setting information. The color setting button1743, the image quality setting button1744, the sheet size button1745, and the double-sided setting button1746display, on the respective buttons, the setting values of the setting items from the scan-job setting information. For example, pressing the color setting button1743causes a color setting screen1770to be displayed. Pressing the detail setting1747causes setting items, which are not displayed in the scan setting screen1740, to be displayed in a screen (not illustrated). Pressing the delete button1748causes transmission, to the collaboration-tool information management server130, of an instruction to delete data related to the job ID1502of the scan-job setting information. Thus, a process (not illustrated) of deleting the scan-job setting information, on the collaboration-tool information management server130, of the job ID is performed. After that, S1602to S1606are repeatedly performed until the condition in S1607is satisfied.

In S1602, the collaboration-tool cooperative application504receives a user operation event.

In S1603, the collaboration-tool cooperative application504determines which button has been pressed in S1602. If the pressed button is one for various settings related to scanning, such as the color setting button1743, the process proceeds to S1604. If the pressed button is a start key, the process proceeds to S1607. The process, which is performed in the case in which the pressed button is the detail setting button1747or the delete button1748, is not important in the present disclosure, and will not be described.

In S1604, the collaboration-tool cooperative application504displays a setting change screen for changing the setting. For example, pressing the color setting button1743causes the collaboration-tool cooperative application504to display a color setting pop-up screen1771in the color setting screen1770. The color setting pop-up screen1771displays setting buttons, such as an automatic color button1772, a color button1773, and a monochrome button1774.

In S1605, the collaboration-tool cooperative application504receives pressing of a displayed setting button.

In S1606, the collaboration-tool cooperative application504updates the scan-job setting information on the RAM413with the setting value of the pressed setting button.

In S1607, the collaboration-tool cooperative application504determines whether the start key has been pressed. If it is determined that the start key has been pressed, the process proceeds to S1608.

If it is determined that the start key has not been pressed, the process proceeds to S1602.

In S1608, the collaboration-tool cooperative application504determines whether the setting values of the settings included in the scan-job setting information include a setting value which is not supported by the MFP120. For example, the setting values of the sheet size, which are supported by the MFP120, are A4, A5, and A6, while the setting value of the sheet size of the scan-job setting information is A3. In this case, since the MFP120does not support A3, the process proceeds to S1609. For example, the MFP120, which does not support scaling, performs scanning with a scaling of 100%. However, when the setting of scaling is set to 100% in the scan-job setting information, the MFP120, which does not support scaling, determines that there is an unsupported setting value, and the process proceeds to S1609. When the MFP120supports all the setting values of the scan-job setting information, the process proceeds to S1622.

In S1609, the collaboration-tool cooperative application504determines whether all the setting values determined not to be supported by the MFP120in S1608are equivalent to the default values of the settings. As in the example of scaling described above, in the MFP120which does not support scaling, when the setting of scaling of the scan-job setting information is 100%, it is determined that this is equivalent to the default value. If it is determined that all the setting values, which are not supported by the MFP120, are equivalent to the default values, the process proceeds to S1610. If it is determined that not all the setting values are equivalent to the default values, the process proceeds to S1611.

In S1610, the collaboration-tool cooperative application504updates the scan-job setting information by changing the setting values, which are not supported by the MFP120, to nulls. As described above, when scaling is set, it is determined that an unsupported setting value is set. Thus, scanning fails to be performed. Therefore, to perform scanning, such settings of the scan-job setting information are updated with nulls.

In S1611, the collaboration-tool cooperative application504stores, in the form of array, manually-changeable setting items in the RAM413. The manually-changeable setting items refer to setting items whose setting values, which are not supported by the MFP120, are set in the scan-job setting information and which have selectable values other than the set setting values. For example, the setting values of the sheet size supported by the MFP120are A4, A5, and A6, while the setting value of the sheet size of the scan-job setting information is A3 size. In this case, a user may manually change the setting to any of A4, A5, and A6 to perform scanning. Such a setting item is defined as a manually-changeable setting item.

In S1612, the collaboration-tool cooperative application504determines whether one or more pieces of data are present in the array of the manually-changeable setting items. If it is determined that one or more pieces of data are present, the process proceeds to S1614. If it is determined that one or more pieces of data are not present, the process proceeds to S1613.

In S1613, the collaboration-tool cooperative application504displays an automatic replacement screen1750inFIG.17G. The automatic replacement screen1750displays a pop-up screen1751on the scan setting screen1740. The pop-up screen1751has a message1752, a cancel button1754, and an execution-with-replacement button1753. The message1752is a message for confirming that settings, which are not supported by the MFP120, are set in the scan-job setting information and whether the setting values are to be replaced to perform scanning.

In S1614, the collaboration-tool cooperative application504displays a manual replacement screen1760inFIG.17H. The manual replacement screen1760displays a pop-up screen1761on the scan setting screen1740. The pop-up screen1761has a message1762, an execution-with-replacement button1765, a manual change button1764, and a cancel button1763. The message1762is a message for confirming that settings, which are not supported by the MFP120, are set in the scan-job setting information and whether the setting values are to be replaced to perform scanning.

In S1615, the collaboration-tool cooperative application504determines which button, which is displayed in the pop-up screen in S1613or S1614, has been pressed. If the OK button1753or1765has been pressed, the process proceeds to S1616. If the manual change button1764has been pressed, the process proceeds to S1617. If the cancel button1754or1763has been pressed, the process of the flowchart ends.

In S1616, the collaboration-tool cooperative application504changes the setting values, which are not supported by the MFP120, to the defaults or nulls, and updates the scan-job setting information. Steps S1617to S1620are repeatedly performed until the condition of S1621is satisfied. Thus, the setting values of the setting items, which are not supported by the MFP120, may be changed by a user.

In S1617, the collaboration-tool cooperative application504retrieves a piece of setting item data from the array of the manually-changeable setting items on the RAM413.

In S1618, the collaboration-tool cooperative application504displays a pop-up screen1781for changing the setting of the setting item data retrieved in S1617. The pop-up screen1781is an exemplary screen for changing the setting value of the sheet size, and is displayed on the scan setting screen1740. The pop-up screen1781includes an A4 button1782, an A5 button1783, and an A6 button1784.

In S1619, the collaboration-tool cooperative application504determines whether a button1782,1783, or1784for the various setting values in the pop-up screen displayed in S1618has been pressed. It is determined that a button has been pressed, the process proceeds to S1620. If it is determined that a button has not been pressed, the process proceeds to S1618.

In S1620, the collaboration-tool cooperative application504updates the scan-job setting information, which is stored in the RAM413, with the pressed setting value.

In S1621, the collaboration-tool cooperative application504determines whether the array of the manually-changeable setting items is null. If it is determined that the array is null, the process proceeds to S1622. If it is determined that the array is not null, the process proceeds to S1617.

In S1622, the collaboration-tool cooperative application504displays a scan-in-progress screen1790. The scan-in-progress screen1790displays a pop-up screen1791on the scan setting screen1740.

In S1623, the collaboration-tool cooperative application504instructs the scanner controller505to perform scanning. The scanner controller505performs scanning and stores the scan result file in the HDD414.

In S1624, the collaboration-tool cooperative application504obtains the scan result file stored in the HDD414in S1623. The collaboration-tool cooperative application504converts the obtained scan result file to the file format1520included in the scan-job setting information, and stores the resulting file in the HDD414.

In S1625, the collaboration-tool cooperative application504transmits the scan result file, which is obtained through the conversion in S1624, as a scan completion event to the event processing application702of the collaboration-tool information management server130.

FIGS.18A and18Bare a flowchart of an exemplary process performed so that the collaboration tool application301of the information processing apparatus110opens a posting-destination chat on the Web application701. The flowchart starts in response to completion of the process in S926.

In S1801, the collaboration tool application301determines whether the pop-up screen1220, which includes the message1221for prompting scanning using the MFP120, has been closed. The pop-up screen1220is illustrated inFIG.12B, and is displayed in S926inFIG.9B. If the determination result in S1801is NO, the process proceeds to S1802. If the determination result is YES, the process of the flowchart ends.

In S1802, the collaboration tool application301obtains job list information from the collaboration-tool information management server130, and proceeds to S1803.

In S1803, the collaboration tool application301obtains, from the job list obtained in S1802, scan-job setting information, whose job ID matches that received when the job is registered in the collaboration-tool information management server130in S916, and stores the scan-job setting information in the RAM203. The collaboration tool application301checks (monitors) a change of the progress state1514of the scan-job setting information, and determines in which state the scan-job setting information is.

Specifically, when the process in S1803is the first process after start of the flowchart, the collaboration tool application301determines that the progress state1514is information indicating “no change”, and proceeds to S1801.

In S1803, when the process in S1803is the second or subsequent process after start of the flowchart, and when the progress state1514has changed from information indicating “job before execution” to information indicating “file upload completed”, it is determined that the progress state1514has changed to information indicating “file upload completed”, and the process proceeds to S1804. In S1803, when the process in S1803is the second or subsequent process after start of the flowchart, and when the progress state1514has changed from information indicating “job before execution” to information indicating “posting completed”, it is determined that the progress state1514has changed to information indicating “posting completed”, and the process proceeds to S1814. Information indicating “posting completed” is information indicating the state in which scan data has been posted to the predetermined posting destination.

In S1804, the collaboration tool application301determines whether the posting-after-preview setting1509of the scan-job setting information is ON. If the determination result in S1804is YES, the process proceeds to S1805. If the determination result is NO, the process proceeds to S1801.

In S1805, the collaboration tool application301requests the collaboration-tool information management server130to obtain the scan result file, and proceeds to S1806.

In S1806, the collaboration tool application301displays the job detail screen1900, and proceeds to S1807. Steps S1807to S1812after that are repeatedly performed until the condition in S1813is satisfied. A user may confirm and change various settings about posting of a chat message, which are displayed in the job detail screen. Pressing a scan result button1907enables the scan result file to be previewed.

In S1807, the collaboration tool application301receives a user operation on the job detail screen1900or the preview screen1909, and proceeds to S1808.

In S1808, the collaboration tool application301determines which input has been received in S1807. If the input is for updating various settings for posting a chat message, the process proceeds to S1809. If the input is pressing the scan result button, the process proceeds to S1810. If the input is pressing a close button, the process proceeds to S1811. If the input is pressing the posting button, the process proceeds to S1812.

In S1809, the collaboration tool application301updates the scan-job setting information with the setting for posting a chat message, which is input by the user, and proceeds to S1813.

In S1810, the collaboration tool application301displays the preview screen1909to display the scan result obtained in S1805, and proceeds to S1813.

In S1811, the collaboration tool application301displays the job detail screen1900, and proceeds to S1813.

In S1812, the collaboration tool application301uses the scan-job setting information, which is stored in the RAM203in S1803, to request the collaboration-tool information management server130to post a message, and proceeds to S1813.

In S1813, the collaboration tool application301determines whether the user input in S1808is pressing the posting button. If the input is pressing the posting button, the process proceeds to S1814. If not, the process proceeds to S1807.

In S1814, the collaboration tool application301performs display control for displaying a screen (the after-posting-message screen2020) including the predetermined posting destination to which the scan data has been posted, on the basis of the posting-destination channel ID or the posting-destination user ID included in the scan-job setting information. Then, the collaboration tool application301ends the process of the flowchart. In the embodiment described above, before scan data is posted to a predetermined posting destination, a preview image of the scan data is displayed on the collaboration tool. After display of the preview image of the scan data, a posting instruction is received. Thus, the scan data is posted to the predetermined posting destination.

Thus, when scan data which is not intended by a user is generated, occurrence of posting the unintended scan data automatically to a predetermined posting destination on the collaboration tool may be reduced.

Second Embodiment

In the first embodiment, the initial display condition of the posting-destination team1204and the posting-destination channel1205which are displayed as a posting destination in the scan job setting area inFIG.12Ais the most-commonly-posted destination of a login user. However, the most-commonly-posted destination may be a posting destination different from one desired by a user, and the user may have a desired posting destination other than the initial posting destination. Further, a user may want to sort, for display, a posting-destination list, from which a setting value is selectable, on the basis of a predetermined condition. Accordingly, in the second embodiment, the initial display condition of the posting-destination team1204and the posting-destination channel1205is made changeable. In addition, the posting-destination list may be sorted, for display, on the basis of a predetermined condition.

FIGS.22A and22Bare a flowchart obtained by changing a part of the process, inFIGS.9A and9B, performed so as to display job settings.

Steps S901to S926inFIGS.22A and22Bare substantially the same as steps S901to S926inFIGS.9A and9B. The processes different from those inFIGS.9A and9Bare a posting-destination candidate sorting process S2201, which is added between S907/S908and S909, an initial-display-condition changing process S2202, which is an additional process, and a posting-destination candidate sorting process S2203, which is an additional process.

FIGS.23A and23Bare diagrams illustrating an exemplary scan-job application screen2301displayed on the display unit206of the information processing apparatus110. The scan-job application screen2301, a scan job setting area2302, and a posting-destination team2304inFIG.23Aare substantially the same as the scan-job application screen1201, the scan job setting area1202, and the posting-destination team1204, respectively, inFIG.12A. InFIG.23A, selection of a posting-destination list display button2305causes information about teams/persons other than “Sales”, which is initially displayed in the posting-destination team2304, to be displayed as a posting-destination list2306. For example, when a given posting destination is selected from the posting destinations displayed in the posting-destination list2306, information about the team/person selected in the posting-destination list2306is displayed in the posting-destination team2304instead of “Sales” which is initially displayed. When an initial-display setting change2303inFIG.23Bis selected, an area (FIG.23B) including an initial-display-condition change button2307and a sort-condition change button2308is displayed. The initial-display-condition change button2307and the sort-display-condition change button2308are radio buttons.

Therefore, user events received in S910inFIG.23Ainclude, in addition to the user events received in S910inFIG.9B, pressing of the initial-display-condition change button2307and pressing of the sort-condition change button2308.

A specific process is illustrated in the flowchart inFIGS.22A and22B. The flowchart starts when predetermined user information is used to log in the collaboration tool application301on the information processing apparatus110, and the plug-in application start button2013or2015is then pressed. The configurations and processes, which are not described in the description below, are equivalent to those in the first embodiment, and will not be described.

In S2201, the collaboration tool application301sorts, for display, the posting-destination list2306in accordance with a sort condition (predetermined condition) described below. The posting-destination list displayed in the posting-destination list2306inFIG.23Ais the same as that obtained in S905.

In S911inFIG.22B, if the collaboration tool application301receives an initial-display-condition change event, the process proceeds to S2202. If the collaboration tool application301receives a sort-condition change event, the process proceeds to S2203.

In S2202, the collaboration tool application301obtains information about the login user's usage of the collaboration tool application301from the collaboration-tool information management server130. Then, on the basis of the obtained usage information, the collaboration tool application301updates, for display, the posting-destination team2304with a posting destination which satisfies the condition selected by using the initial-display-condition change button2307. Options selectable by using the initial-display-condition change button2307may be, but not limited to these, for example, a chat of most-commonly-posted destination, a latest-displayed chat, and a chat with the user themselves. The latest-displayed chat is a chat displayed the latest before display of the scan-job application screen2301. The chat with the user themselves is a chat in which user information, which indicates a user who has logged in the collaboration tool application301, may post a message to the user themselves (that is, the logged-in user information).

In S2203, the collaboration tool application301obtains information of the login user's usage of the collaboration tool application301from the collaboration-tool information management server130. Then, the collaboration tool application301updates, for display, the order of the posting destinations in the posting-destination list on the basis of the obtained usage information and the condition selected by using the sort-condition change button2308. Order options selectable by using the sort-condition change button2308may be, but not limited to these, for example, the order of posting count and the order of latest display. Display in the order of posting count refers to display in the descending order starting from the posting destination (most-commonly-posted destination) whose count of the logged-in user's posts of scan data is the most. Display in the order of latest display refers to display in the order starting from the posting destination displayed the latest before display of the scan-job application screen2301.

As described above, in the present embodiment, the initial display condition of the posting-destination team1204and the posting-destination channel1205displayed as an initial posting destination in the scan job setting area inFIG.12Ais changeable. In addition, the posting-destination list may be sorted, for display, on the basis of a predetermined condition. Thus, a user may select a more desirable posting destination. Even with a large number of posting destination options, trouble in selecting a posting destination may be mitigated, achieving improvement of user convenience.

OTHER EMBODIMENTS

This application claims the benefit of Japanese Patent Application No. 2023-165667, filed Sep. 27, 2023 and No. 2023-165668, filed Sep. 27, 2023, which are hereby incorporated by reference herein in their entirety.