Information processing device, information processing method and program

Abstract

To enable a user to easily recognize a processing state about an electronic file.SOLUTION: An information processing device includes update means for updating display information in displaying a file as an icon from first display information before being processed to second display information having different display from the first display information in the case that processing to the file is performed by the image processing device, and display means for displaying the file as an icon according to the display information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an icon control technique for printing electronic files. [Background technology]

[0002] A method of displaying an image icon according to the type of electronic file to make it easier to recognize the electronic file is becoming popular. Patent Document 1 discloses a technology for acquiring the color attribute of an electronic file and displaying an image icon reflecting the color attribute. [Prior art documents] [Patent documents]

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

[0004] Color attributes are not the only information that users want to know about electronic files. For example, when printing multiple electronic files, information about the processing status of the electronic files, such as which electronic files have been printed, is also important to the user. The present invention has been made in consideration of such circumstances, and has an object to enable users to easily recognize the processing status of electronic files. [Means for solving the problem]

[0005] The information processing device of the present invention is characterized in having an update means for updating, when processing of a file is performed on an image processing device, display information for displaying the file as an icon from first display information before the processing is performed to second display information having a different display from the first display information, and a display means for displaying the file as an icon in accordance with the display information. Effect of the Invention

[0006] According to the present invention, it becomes possible for a user to easily recognize the processing status regarding an electronic file. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 illustrates an example of a hardware configuration of an information processing device. [Diagram 2] FIG. 1 illustrates an example of a system configuration constructed on an information processing device. [Diagram 3] FIG. 4 is a diagram showing a program configuration for icon control in the first embodiment. [Figure 4] 11 is a flowchart showing an example of a process for registering an overlay in the first embodiment. [Diagram 5] 11 is a flowchart showing an example of a process for setting a printed overlay in the first embodiment. [Figure 6] FIG. 13 is a diagram showing a display example of a printed overlay in the first embodiment. [Figure 7] 13 is a flowchart showing an example of a process for setting a printed overlay in the second embodiment. [Figure 8] 13 is a flowchart showing an example of a process for setting a printed overlay in the third embodiment. [Figure 9] FIG. 13 is a diagram showing the configuration of an icon control program in the fourth embodiment. [Figure 10] 13 is a flowchart showing an example of a process for creating a workflow ticket according to the fourth embodiment. [Figure 11] 13 is a flowchart showing an example of a process for setting an icon according to the fourth embodiment. [Figure 12] FIG. 13 is a diagram showing an example of an overlay display in the fourth embodiment. [Figure 13] 13 is a flowchart showing an example of a process for setting an overlay in the fourth embodiment. [Figure 14] 13 is a flowchart showing an example of a process for setting an icon according to the fifth embodiment. [Figure 15] FIG. 13 is a diagram showing an example of icon display in the fifth embodiment. [Figure 16] FIG. 23 is a diagram showing the configuration of a file display program in the sixth embodiment. [Figure 17] 23 is a flowchart showing an example of a file display process in the sixth embodiment. [Figure 18] FIG. 23 is a diagram showing an example of file display in the sixth embodiment. [Figure 19] FIG. 23 is a diagram showing an example of a message display in the seventh embodiment. [Figure 20] FIG. 13 is a diagram showing a program configuration in the seventh embodiment. [Figure 21] 23 is a flowchart showing an example of a message update process in the seventh embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the drawings shown below, the same or similar components are designated by the same reference numerals, and duplicated explanations will be omitted.

[0009] <Embodiment 1> The hardware and system configuration according to an embodiment of the present invention will be described below. Fig. 1 is a diagram showing an example of the hardware configuration of an information processing device 100 according to this embodiment. As shown in Fig. 1, the information processing device 100 includes a CPU 11 as a hardware configuration.

[0010] The CPU 11 performs processing based on programs stored in the storage unit 13 and corresponding to applications and program execution environments, which will be described later, to realize each function or process of a flowchart, which will be described later.

[0011] In addition, the CPU 11 is connected to an input unit 12, a storage unit 13, a display unit 14, and an external connection IF 15 via a bus 10. The input unit 12 is a keyboard and a mouse for inputting information. The storage unit 13 includes, for example, a ROM, a RAM, a hard disk drive, and the like, and stores data and the like used in processing based on the programs in addition to the above-mentioned programs. The display unit 14 is a display for displaying a screen, etc. The external connection IF 15 is a network interface and various connection interfaces with external devices.

[0012] The CPU 11 can function as various means by executing a program. A control circuit such as an ASIC that operates in cooperation with the CPU 11 may function as these means. These means may be realized by cooperation between the CPU 11 and a control circuit that controls the operation of the information processing device 100. The CPU 11 does not need to be a single one, and may be multiple. In this case, the multiple CPUs 11 can execute processing in a distributed manner. The multiple CPUs 11 may be located in a single computer, or may be located in multiple physically different computers. The means realized by the CPU 11 executing a program may be realized by a dedicated circuit.

[0013] Next, a system configuration built on the information processing device 100 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the system configuration of the information processing device 100. An operating system 201 (hereinafter referred to as OS201) is software that forms the basis of the entire system. A process 202 is a unit of execution that runs software on the OS201. A program can be run on the process 202.

[0014] In the first embodiment, the program operated on the process 202 is a driver for using the image processing device. The configuration of the program will be described with reference to Fig. 3. In this embodiment, the OS 201 is Windows (registered trademark) as an example. Note that the OS 201 is not limited to Windows, and may be another OS as long as it can realize the operations and functions described below.

[0015] A file 302 held on the OS 201 has an overlay information section 303. The OS 201 also has an icon management section 301 that displays overlays on icons to be displayed. The icon management section 301 displays overlays on icons by referencing the overlay information section 303. An icon for any overlay can be registered in the icon management section 301 from a program. This registration can be performed by the program executing an API of the OS 201.

[0016] The driver 304 has a job transmission unit 305 and a file update unit 306. The job transmission unit 305 transmits data to the image processing device. The data transmitted by the job transmission unit 305 includes data of the file to be printed and print settings. Hereinafter, this data will be referred to as job data. The file update unit 306 updates the overlay information unit 303 of the printed file 302.

[0017] Next, a process in which the driver 304 registers an overlay in the OS 201 will be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of the overlay registration process. The process of registering an overlay can be performed at any time, but Fig. 4 describes the process as being performed when the driver is installed.

[0018] In step S401, the driver 304 determines whether the print overlay has been registered in the OS 201. If the driver 304 determines that the print overlay has been registered (YES in step S401), the driver 304 ends the processing of the flowchart shown in Fig. 4. If the driver 304 determines that the print overlay has not been registered (NO in step S401), the processing of step S402 is executed. In step S402, the driver 304 registers an icon for overlay in the registry of the OS 201. Then, the process of the flowchart shown in FIG.

[0019] Next, a process flow in which the driver 304 transmits job data to the image processing apparatus will be described with reference to Fig. 5. Fig. 5 is a flow chart showing an example of a process for setting a printed overlay.

[0020] When the driver 304 receives an instruction to print a file through a user's instruction operation or the like, in step S501 the driver 304 reads the file to be printed that has been instructed to be printed. In step S502, the driver 304 creates job data for printing the file to be printed that was read in step S501, in accordance with the print settings. In step S503, the driver 304 transmits the job data created in step S502 to the image processing apparatus or the job server.

[0021] In step S504, the driver 304 determines whether the transmission of the job data was successful. If the driver 304 determines that the transmission of the job data was successful (YES in step S504), the process of step S505 is executed. On the other hand, if the driver 304 determines that the transmission of the job data was not successful or that the transmission of the job data failed (NO in step S504), the driver 304 ends the process of the flowchart shown in FIG.

[0022] In step S505, driver 304 sets an overlay icon in overlay information section 303 of the file to be printed. Then, the process of the flowchart shown in Fig. 5 ends. As a result, when the icon of this file is displayed, a printed overlay is displayed on the icon of the file. Here, the file icon is an example of an icon displayed according to the first display information, and the file icon with the printed overlay displayed is an example of an icon displayed according to the first display information.

[0023] In step S504, the driver 304 determines whether the job data has been successfully transmitted, but it may be arranged to determine whether the job data has been printed instead of transmitted. In that case, in step S504, the driver 304 periodically checks the job queue and makes a determination.

[0024] 6(a) and 6(b) show examples of icon overlay display in the first embodiment. In FIG. 6(a), three daily report PDF files are displayed in a file viewing program on the OS 201, and icons 601, 602, and 603 of the respective files are displayed. If the display format of printed files and unprinted files is the same, the user cannot intuitively recognize the printed files. In contrast, according to the present embodiment, when the file "Daily Report_20220523" has been printed, for example, an overlay 611 can be displayed on the icon 601 of the printed "Daily Report_20220523" file as shown in FIG. 6(b).

[0025] As described above, according to the first embodiment, a printed overlay is displayed on the icon of a printed file. Therefore, printed files and unprinted files can be displayed differently, allowing the user to easily recognize whether a file has been printed or not, and making it easy for the user to check the processing status of the file.

[0026] <Embodiment 2> In the first embodiment, an overlay is set on the icon of a printed file. However, there are cases where an overlay is not desired to be set on a printed file. For example, a user may be confused if a file in a shared folder where files are shared is printed by someone else and a "printed" overlay is set even though the user has not printed the file. In the second embodiment, a method of not setting an overlay on a file in a shared folder is described. The following describes the differences between the second embodiment and the first embodiment. FIG. 8 is a flowchart showing an example of a process for setting a "printed" overlay in the second embodiment.

[0027] The processing in steps S701 to S704 is substantially similar to the processing in steps S501 to S504 in FIG. If the driver 304 determines in step S704 that the job data has been successfully transmitted (YES), the process proceeds to step S705.

[0028] In step S705, the driver 304 determines whether the file to be printed that is instructed to be printed is in the shared folder. If the driver 304 determines that the file to be printed is in the shared folder (NO in step S705), the driver 304 ends the process of the flowchart shown in Fig. 7. In other words, if the driver 304 determines that the file to be printed is in the shared folder, the driver 304 ends the process without setting an overlay icon in the overlay information section 303 of the file to be printed. If the driver 304 determines that the file to be printed is not in the shared folder (YES in step S705), the process of step S706 is executed. The process of step S706 is substantially similar to the process of step S505 in FIG.

[0029] According to the second embodiment, like the first embodiment, it is possible to display printed files and unprinted files differently, so that the user can easily recognize whether a file has been printed or not, and it is possible to easily check the processing status of the file. In addition, for files in a shared folder, it is possible to prevent the user from becoming confused by not setting an overlay icon and not updating the display.

[0030] <Embodiment 3> In the first embodiment, an overlay is set on the icon of a printed file. However, when the image processing device fails to print a file due to running out of paper or toner, the printed overlay should be deleted. In the third embodiment, a method for deleting the printed overlay when the image processing device fails to print a file is described. The following describes the differences between the third embodiment and the first embodiment. FIG. 8 is a flowchart showing an example of a process for setting a printed overlay in the third embodiment.

[0031] The processing in steps S801 to S805 is substantially similar to the processing in steps S501 to S505 in FIG. After the driver 304 sets an overlay icon for the file to be printed in step S805, the driver 304 stores the job sent in step S803 and the file corresponding to the job as a set in step S806. That is, the driver 304 stores the file with the printed overlay icon set and the job related to printing the file as a set.

[0032] In step S806, the driver 304 determines whether the file was successfully printed. There are several methods for this determination, but the simplest is to periodically check the job queue for the image processing device and determine whether the corresponding job has been completed. Alternatively, the driver 304 may receive a notification from the image processing device or make an inquiry to the image processing device. If the driver 304 determines that the file was unsuccessful in printing (NO in step S807), the process of step S808 is executed. On the other hand, if the driver 304 determines that the file was successfully printed (YES in step S807), the process of step S809 is executed.

[0033] In step S808, the driver 304 refers to the set stored in step S806 and deletes the overlay icon indicating that the file corresponding to the failed job has been printed, and then the process proceeds to step S809. In step S809, the driver 304 deletes the set stored in step S806, and ends the process of the flowchart shown in FIG.

[0034] According to the third embodiment, like the first embodiment, it is possible to display printed files and unprinted files in a different way, so that the user can easily recognize whether a file has been printed or not, and it is possible to easily check the processing status of the file. In addition, if printing fails, the printed overlay can be deleted and the original display can be restored.

[0035] <Embodiment 4> In the first to third embodiments, the driver for the image processing device for using the image processing device sets the overlay icon. In recent years, remote work has become widespread, and people who want to use an image processing device are increasingly asking people who are near the image processing device to print or scan files, etc.

[0036] In this type of usage, it is assumed that the requester sets print settings before using the image processing device, creates a workflow ticket including the print settings, and sends it to a person (operator) who is near the image processing device. In remote work, communication between the requester and the operator of the image processing device is generally performed using collaboration tools (communication tools) such as Microsoft Teams (registered trademark) and Slack (registered trademark). Note that collaboration tools are application programs. Therefore, it is natural to process workflow tickets on a program that serves as a plug-in that works with the collaboration tool. The workflow ticket may be created by a plug-in or a driver. The created workflow ticket can be shared in chats or channels on the collaboration tool.

[0037] Specifically, an example will be described in which a requester who is not in the office where the image processing device is installed and a executor who is in the office are taken. For example, first, a requester who wants to print a file specifies the setting "A3 color double-sided printing" and creates a workflow ticket for printing the file "Daily report.pdf". Then, the requester attaches the created workflow ticket to a chat in a collaboration tool and asks the executor to print. Then, when the executor executes the workflow ticket from a plug-in, printing is performed with the print settings included in the workflow ticket. In this way, problems such as print setting errors can be prevented by the requester who wants to use an image processing device and the executor communicating via a workflow ticket.

[0038] In the fourth embodiment, a method in which a plug-in that runs on a collaboration tool sets an overlay icon will be described. The following describes the differences between the fourth embodiment and the above-described embodiments.

[0039] FIG. 9 is a diagram showing the configuration of an icon control program in the fourth embodiment. The driver 901 includes a job transmission unit 302 that transmits jobs to an image processing device 910. The image processing device 910 includes a job management unit 911 that accepts and manages jobs.

[0040] A workflow ticket execution program 903, which is a plug-in that runs on the collaboration tool, has a ticket processing unit 904 and a file updating unit 905. The ticket processing unit 904 has a function of reading a workflow ticket 906 and transmitting job data related to the workflow ticket 906 to an image processing device 910. The file updating unit 905 has a function similar to that of the file updating unit 306 shown in FIG.

[0041] The workflow ticket 906 has a workflow information section 907 that includes print settings and folder information to save after scanning. The workflow ticket 906 also has a document information section 908 that is file information to be printed. The document information section 908 may be the file itself to be printed, or may be the file path of a document stored on a server. The workflow ticket 906 itself is a file handled on the OS 201, so it also has an overlay information section 909. The overlay information section 909 is the same as the overlay information section 303 shown in FIG. 3.

[0042] The process in which the workflow ticket execution program 903 creates a workflow ticket 906 will be described with reference to Fig. 10. Fig. 10 is a flow chart showing an example of the process of creating a workflow ticket.

[0043] In step S1001, the workflow ticket execution program 903 acquires information about the file to be processed. In step S1002, the workflow ticket execution program 903 acquires workflow settings for the file to be processed. Examples of workflow settings include "print three copies in color on one side of A3 paper," "send a fax to B Corporation," and "scan documents mailed from C Office."

[0044] In step S1003, the workflow ticket execution program 903 creates a workflow ticket that includes the file information acquired in step S1001 and the workflow settings acquired in step S1002. In step S 1004 , the workflow ticket execution program 903 sets an icon for the file of the workflow ticket 906 .

[0045] Details of the icon setting process in step S1004 in Fig. 10 will be described with reference to Fig. 11. Fig. 11 is a flowchart showing an example of the icon setting process.

[0046] In step S1101, the workflow ticket execution program 903 checks the type of the set workflow. In step S1102, the workflow ticket execution program 903 determines whether the next workflow for the file to be processed is printing. If the workflow ticket execution program 903 determines that the next workflow is printing (YES in step S1102), the process of step S1103 is executed. If the workflow ticket execution program 903 determines that the next workflow is not printing (NO in step S1102), the process of step S1104 is executed.

[0047] In step S1103, the workflow ticket execution program 903 sets a print icon as an overlay for the file to be processed, and ends the processing of the flowchart shown in Fig. 11. Fig. 12(a) shows an example of the display of an overlay icon of the workflow ticket 1004 when a print icon is set as an overlay in step S1103.

[0048] In step S1104, the workflow ticket execution program 903 determines whether the next workflow for the file to be processed is fax transmission. If the workflow ticket execution program 903 determines that the next workflow is fax transmission (YES in step S1104), the process proceeds to step S1105. If the workflow ticket execution program 903 determines that the next workflow is not fax transmission (NO in step S1104), the process proceeds to step S1106.

[0049] In step S1105, the workflow ticket execution program 903 sets a FAX icon as an overlay for the file to be processed, and ends the processing of the flowchart shown in Fig. 11. Fig. 12(b) shows an example of the display of an overlay icon of the workflow ticket 1004 when a FAX icon is set as an overlay in step S1105.

[0050] In step S1106, the workflow ticket execution program 903 determines whether the next workflow for the file to be processed is a scan. If the workflow ticket execution program 903 determines that the next workflow is a scan (YES in step S1106), the process proceeds to step S1107. If the workflow ticket execution program 903 determines that the next workflow is not a scan (NO in step S1106), the process proceeds to step S1108.

[0051] In step S1107, the workflow ticket execution program 903 sets a scan icon as an overlay for the file to be processed, and ends the processing of the flowchart shown in Fig. 11. Fig. 12(c) shows an example of the display of an overlay icon of the workflow ticket 1004 when a scan icon is set as an overlay in step S1107.

[0052] In step S1108, the workflow ticket execution program 903 determines whether or not there is a next workflow for the file to be processed. Since the progress status of each workflow is held by the ticket processing unit that cooperates with the image processing apparatus, the presence or absence of the next workflow can be confirmed by referring to the ticket processing unit 904. If the workflow ticket execution program 903 determines that there is no next workflow (YES in step S1108), the process of step S1109 is executed. If the workflow ticket execution program 903 determines that there is a next workflow (NO in step S1108), the process of the flowchart shown in FIG. 11 is terminated.

[0053] In step S1109, the workflow ticket execution program 903 sets an executed icon in the overlay for the file to be processed, and ends the processing of the flowchart shown in Fig. 11. In this step S1109, in order to display the file as having already been executed, for example, a checked icon 611 as shown in Fig. 6(b) is set in the overlay.

[0054] Next, a flow in which the workflow ticket execution program 903 processes the workflow ticket 904 and transmits a job will be described with reference to Fig. 13. Fig. 13 is a flowchart showing an example of a process for setting an overlay. The workflow in the description is printing.

[0055] In step S 1301 , the workflow ticket execution program 903 reads the workflow ticket 906 . In step S1302, the workflow ticket execution program 903 creates job data for executing a workflow by referencing the workflow information section 907 and the document information section 908. Note that the job data may be created in step S1302 by executing the driver 901 from the workflow ticket execution program 903 instead of using the workflow ticket execution program 903 itself.

[0056] In step S1303, the workflow ticket execution program 903 transmits the job data created in step S1302 to the image processing device 910. Note that the job data may be transmitted to a job reception server linked to the image processing device 910, instead of being transmitted directly to the image processing device 910.

[0057] In step S1304, the workflow ticket execution program 903 determines whether or not the job data has been successfully sent. If the workflow ticket execution program 903 determines that the job data has been successfully sent (YES in step S1304), the process proceeds to step S1305. On the other hand, if the workflow ticket execution program 903 determines that the job data has not been successfully sent or has failed to be sent (NO in step S1304), the process of the flowchart shown in FIG. 13 ends.

[0058] In step S1305, the workflow ticket execution program 903 sets an icon for the workflow ticket file in the same manner as in step S1004 in FIG. 11, and ends the process of the flowchart shown in FIG.

[0059] 5 in the first embodiment, it is also possible to determine whether the job data has been executed or not, rather than whether the job data has been successfully transmitted. In that case, in step S1304, the job queue is periodically checked for determination, or the job status is periodically checked with the image processing device for determination.

[0060] According to the fourth embodiment, by setting and displaying an overlay icon according to the type of workflow, the user can easily recognize the next task to be performed.

[0061] <Embodiment 5> In the above-described embodiments, an overlay icon for a file is set. The OS 201 can display an icon according to the file extension. Therefore, by changing the icon display itself, rather than an overlay icon, it is possible to display the icon in an easy-to-read manner even on a small screen.

[0062] A method for setting an icon for a printed file will be described with reference to Fig. 14. Fig. 14 is a flowchart showing an example of a process for setting an icon in the fifth embodiment. Note that, in the following, the workflow ticket execution program 903 will be described as performing the process as in the fourth embodiment described above, but when a workflow ticket is not used as in the first to third embodiments, the driver 304 performs the process.

[0063] The processing in steps S1401 to S1404 is substantially similar to the processing in steps S501 to S504 in FIG. If the workflow ticket execution program 903 determines in step S1404 that the job data has been successfully sent (YES), the process proceeds to step S1405.

[0064] In step S1405, the file update unit 905 of the workflow ticket execution program 903 changes the file extension of the workflow ticket. Then, the workflow ticket execution program 903 ends the processing of the flowchart shown in Fig. 14. By changing the file extension in this way, the file will thereafter be displayed with an icon corresponding to the changed extension.

[0065] FIG. 15(a) shows an example of the icon display when the extension is changed. In FIG. 15(a), an icon 1501 of "Daily Report_20220523" and an icon 1502 of "Daily Report_20220524" are displayed. "Daily Report_20220524" is a file of the workflow ticket 906 immediately after creation. The file name including the extension is "Daily Report_20220524.wf1", and the icon of the extension wf1 is set in the OS 201 as the "Daily Report_20220524" icon 1502 in FIG. 12(a). In addition, for the extension wf2, an icon that indicates that it has been printed is registered in the OS 201, like the "Daily Report_20220523" icon 1501 in FIG. 12(a). Therefore, by changing the extension wf1 to the extension wf2 in step S1405, it is possible to display an icon that is easy for the user to recognize. The extension may be changed according to the next workflow of the workflow ticket, and the icon displayed may be changed as shown in Fig. 15(b) as an example. For example, if the next workflow of the "Daily Report_20220523" file is printing, the extension will be changed accordingly and icon 1511 will be displayed. Also, if the next workflow of the "Daily Report_20220524" file is fax transmission, the extension will be changed accordingly and icon 1512 will be displayed.

[0066] According to the fifth embodiment, an icon is set and displayed according to the type of workflow, so that the user can easily recognize the processing status of a file in the workflow.

[0067] <Embodiment 6> In each of the above-described embodiments, an example was shown in which the information processing device 100 was assumed to be a general personal computer (PC), but in recent years, printing from smartphones and tablets has also become widespread. In the sixth embodiment, a method for displaying printed files to a user in an easy-to-understand manner when the information processing device 100 is a mobile terminal such as a smartphone or tablet will be described.

[0068] In the sixth embodiment, the program operated on the process 202 is an application for using the image processing device. The configuration of the program will be described with reference to FIG. 14. In this embodiment, the OS 201 is, for example, Android (registered trademark) or iOS (registered trademark). The application 1601 has a print request sending unit 1602 that sends a print request to the image processing device. The application 1601 also has a file management unit 1603 that manages files held on the OS 201, and a file display unit 1604 that displays the files.

[0069] The process in which the application 1601 changes the display of a file will now be described with reference to Fig. 17. Fig. 17 is a flow chart showing an example of the display process of a file.

[0070] In step S1701, the application 1601 reads a folder that the application 1601 can access.

[0071] In step S1702, the application 1601 displays the files in the folder loaded in step S1701. An example of the file display in step S1702 is shown in FIG. 18(a). FIG. 18(a) shows an example of a plurality of music score files displayed on the screen of an application for using a general image processing device. Conventionally, even after printing a file specified on this screen, the display of each file remains the same. For this reason, for example, when printing a plurality of music scores in sequence, the user may lose track of how far the file has been printed, and may forget the music score that he or she wanted to print, or may print the same music score twice.

[0072] In step S1703, the application 1601 transmits the file designated by the user as a job to the image processing apparatus and prints it.

[0073] In step S1704, the application 1601 determines whether or not the file transmission was successful. If the application 1601 determines that the file transmission was successful (YES in step S1704), the process of step S1705 is executed. On the other hand, if the application 1601 determines that the file transmission was not successful or failed (NO in step S1704), the application 1601 ends the process of the flowchart shown in FIG.

[0074] In step S1705, the application 1601 stores the file transmitted in step S1703 as having been transmitted. In step S1706, the application 1601 changes the display of the file stored as having been sent in step S1705, and ends the process of the flowchart shown in FIG.

[0075] An example of the display changed by the processing in step S1706 is shown in Fig. 18(b). In Fig. 18(b), the display of the portion indicated by frame 1801 has been changed. By displaying in this manner, it is possible to prevent the above-mentioned problems from occurring when printing multiple files. Also, since the operation of scrolling the display on a mobile terminal such as a smartphone when there are a large number of files is cumbersome, for example, a filter display may be provided by selecting from menu 1802 as shown in Fig. 18(c).

[0076] <Embodiment 7> In the fourth embodiment, a workflow ticket mechanism is assumed that allows the image processing device to be used smoothly even if the requester and the executor of printing are different. Chat is a natural way to exchange workflow tickets on a collaboration tool. FIG. 19(a) shows an example of workflow ticket exchange on a collaboration tool. In this example, user Yamada Taro creates a workflow ticket and requests printing, and user Okawa Hanako prints using the workflow ticket and replies to that effect. Note that on the collaboration tool, multiple users participating in a certain group can each send a message within the group, and the sent messages can be viewed by multiple users in the group.

[0077] However, for user Hanako Ohkawa, typing a reply message after printing a requested document is a burden. However, if she does not type a reply, when multiple print requests are made, she will not know which requests have already been completed. Even if she types a reply, the behavior of a typical collaboration tool is that after a certain period of time, chat messages will be collapsed with all replies except for the first heading, making it difficult to confirm which requests have already been completed.

[0078] To solve this problem, after a workflow ticket is executed, the message of the requester is updated instead of replying to the message of the requester. In the seventh embodiment, a method of updating a message of the requester by adding a record of the execution of the workflow ticket to the message of the requester will be described.

[0079] 20 is a diagram showing the configuration of a program that cooperates with a collaboration tool in the seventh embodiment. A workflow ticket execution program 2001 has a workflow ticket processing unit 2002 and a collaboration tool cooperation unit 2003. The workflow ticket processing unit 2002 has a function of reading a workflow ticket and transmitting job data related to the workflow ticket. The collaboration tool cooperation unit 2003 is implemented to operate the API of the collaboration tool for posting and editing messages. In addition, the collaboration tool 2004 has a message management unit 2005 that manages messages.

[0080] 21 is a flowchart showing an example of the process of the workflow ticket execution program 2001 in the embodiment 7. It is assumed that the workflow ticket execution program 2001 is running in each of the collaboration tools of the requester and the executor.

[0081] The processing in steps S2101 to S2103 is substantially similar to the processing in steps S1301 to S1305 in FIG.

[0082] In step S2104, the workflow ticket execution program 2001 determines whether or not the job data has been successfully sent. If the workflow ticket execution program 2001 determines that the job data has been successfully sent (YES in step S2104), the process of step S2305 is executed. On the other hand, if the workflow ticket execution program 2001 determines that the job data has not been successfully sent or has failed to be sent (NO in step S2104), the process of the flowchart shown in FIG. 21 is terminated.

[0083] In step S2105, the workflow ticket execution program 2001 judges whether the creator of the workflow ticket is the user himself / herself. If the workflow ticket execution program 2001 judges that the creator is the user himself / herself (YES in step S2105), the process of step S2106 is executed. If the workflow ticket execution program 2001 judges that the creator is not the user himself / herself (NO in step S2105), the process of step S2107 is executed.

[0084] If the creator is the user, then the message on the collaboration tool requesting execution of the workflow ticket is also posted by the user, and therefore the workflow ticket execution program 2001 running in the user's environment has the authority to update the message. Therefore, in step S2106, which is executed when it is determined that the creator is the user, the workflow ticket execution program 2001 updates the message.

[0085] On the other hand, in step S2107, the workflow ticket execution program 2001 notifies the workflow ticket execution program 2001 operating in the environment of the poster of the message on the collaboration tool requesting the execution of the workflow ticket.

[0086] In step S2108, the workflow ticket execution program 2001 of the requester that has received the notification in step S2107 updates the message. An example of the message update in step S2108 is shown in FIG. 19(b). By automatically performing an additional update as shown in the part indicated by the frame 1901, instead of a simple reply, a highly visible display can be realized. Specifically, for example, an update is performed to add a message indicating which user executed the printing. The content added by the update is not limited to the above, and a message simply indicating that the printing was executed may be added. In addition, for example, a message indicating the date and time when the printing was executed may be added. As described above, the sent message can be viewed by multiple users in the group on the collaboration tool. Therefore, the updated message can also be viewed by multiple users in the group on the collaboration tool. This makes it possible for other users in the group to check the message added by the update in this process.

[0087] <Other embodiments of the present invention> 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 embodiment 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) for implementing one or more of the functions.

[0088] It should be noted that the above-mentioned embodiments are merely examples of the implementation of the present invention, and the technical scope of the present invention should not be interpreted as being limited by these. In other words, the present invention can be implemented in various forms without departing from its technical concept or main features.

[0089] The disclosure of the present embodiment includes the following configurations, methods, etc. (Configuration 1) an update means for updating, when a file is processed by an image processing device, display information for displaying the file as an icon from first display information before the processing is performed to second display information that is different from the first display information; and display means for displaying the files as icons in accordance with the display information. (Configuration 2) 2. The information processing device according to configuration 1, wherein the second display information overlays information indicating that the second display information has been processed on an icon corresponding to the first display information. (Configuration 3) 2. The information processing device according to configuration 1, wherein an icon displayed according to the first display information and an icon displayed according to the second display information are different from each other. (Configuration 4) a transmission unit for transmitting job data relating to the file to be processed by the image processing device; The information processing device according to any one of configurations 1 to 3, characterized in that the update means updates the display information of the file from the first display information to the second display information when the transmission of the job data by the transmission means is completed. (Configuration 5) 5. The information processing apparatus according to configuration 4, wherein the update means, if processing on the file fails, returns the display information of the file to the first display information. (Configuration 6) 6. The information processing device according to any one of configurations 1 to 5, wherein the update means does not update the display information when the file is in a shared folder. (Configuration 7) 7. The information processing device according to any one of configurations 1 to 6, wherein when the file is a workflow ticket, the update means updates the display information of the file based on the workflow of the workflow ticket. (Configuration 8) 8. The information processing device according to configuration 7, wherein the update means updates the display information of the file by updating the extension of the file in accordance with the workflow of the workflow ticket. (Configuration 9) 9. The information processing device according to any one of configurations 1 to 8, wherein the process performed by the image processing device includes at least one of printing, FAX transmission, and scanning. (Configuration 10) a display means for displaying the file; A management means for managing the file; a sending means for sending a print request for the file; When the print request is transmitted, the information processing apparatus updates a display of the file for which the print request is transmitted. (Configuration 11) A linking means for linking with a collaboration tool operated on an information processing device; A management means for managing messages in the collaboration tool; a processing means for transmitting job data based on a workflow ticket for processing a file; When the job data is transmitted, the information processing apparatus updates the message related to the file corresponding to the job data. (Method 1) An information processing method executed by an information processing device, an updating step of updating, when a file is processed by an image processing device, display information for displaying the file as an icon from first display information before the processing to second display information that is different from the first display information; and displaying the file as an icon in accordance with the display information. (Program 1) The computer of the information processing device an updating step of updating, when a process on a file is performed by an image processing device, display information for displaying the file as an icon from first display information before the process is performed to second display information having a display different from the first display information; and a display step of displaying the file as an icon in accordance with the display information. [Explanation of symbols]

[0090] 100: Information processing device 11: CPU 13: Memory unit 14: Display unit

Claims

1. an update means for updating, when a file is processed by an image processing device, display information for displaying the file as an icon from first display information before the processing is performed to second display information that is different from the first display information; and display means for displaying the files as icons in accordance with the display information.

2. The information processing apparatus according to claim 1 , wherein the second display information overlays information indicating that the second display information has been processed on an icon corresponding to the first display information.

3. 2 . The information processing apparatus according to claim 1 , wherein an icon displayed according to the first display information is different from an icon displayed according to the second display information.

4. a transmission unit for transmitting job data relating to the file to be processed by the image processing device; 2 . The information processing apparatus according to claim 1 , wherein the update unit updates the display information of the file from the first display information to the second display information when the transmission unit has completed transmission of the job data.

5. 5. The information processing apparatus according to claim 4, wherein said update means, when the processing on said file has failed, returns the display information of said file to said first display information.

6. 2. The information processing apparatus according to claim 1, wherein said update means does not update said display information when said file is in a shared folder.

7. 2 . The information processing apparatus according to claim 1 , wherein, when the file is a workflow ticket, the update means updates the display information of the file based on a workflow of the workflow ticket.

8. 8. The information processing apparatus according to claim 7, wherein the update unit updates the display information of the file by updating the extension of the file in accordance with the workflow of the workflow ticket.

9. 2. The information processing apparatus according to claim 1, wherein the process performed by the image processing apparatus includes at least one of printing, fax transmission, and scanning.

10. a display means for displaying the file; A management means for managing the file; a sending means for sending a print request for the file; When the print request is transmitted, the information processing apparatus updates a display of the file for which the print request is transmitted.

11. A linking means for linking with a collaboration tool operated on an information processing device; A management means for managing messages in the collaboration tool; a processing means for transmitting job data based on a workflow ticket for processing a file; When the job data is transmitted, the information processing apparatus updates the message related to the file corresponding to the job data.

12. An information processing method executed by an information processing device, an updating step of updating, when a file is processed by an image processing device, display information for displaying the file as an icon from first display information before the processing to second display information having a different display from the first display information; and displaying the file as an icon in accordance with the display information.

13. The computer of the information processing device an updating step of updating, when a process on a file is performed by the image processing device, display information for displaying the file as an icon from first display information before the process is performed to second display information having a display different from the first display information; and a display step of displaying the file as an icon in accordance with the display information.

Images