Job processing device, method for controlling the job processing device, and program

Abstract

By viewing the history records sorted chronologically, you can check the job execution history and easily see the details of any errors. [Solution] An image processing device comprising: a first execution means for executing a copy function; a second execution means for executing a scan function; and a display control means for displaying a job history list on the display unit, which arranges the job history of jobs executed by the first execution means and the job history of jobs executed by the second execution means in the order of job execution, regardless of the type of function including the copy function and the scan function. The display control means is characterized in that, based on the selection of a job history of a job executed by the first execution means included in the job history list, it displays a setting screen for the copy function that reflects the setting value corresponding to the selected job history, and displays a screen that includes the job history list and information indicating that there is no paper.

Description

Technical Field

[0001] The present invention relates to a job processing apparatus, a control method for the job processing apparatus, and a program.

Background Art

[0002] Conventionally, there has been a job processing apparatus that executes jobs and stores the history of the executed jobs.

[0003] For example, there is a job processing apparatus that displays such a job history on a home screen for selecting a copy function or a transmission function (see Patent Document 1).

[0004] By displaying a list of histories in this way, the user can easily check the history of the most recently executed jobs.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] In the prior art, although the execution history of jobs is displayed on the home screen, it is impossible to confirm until an error has occurred. Therefore, if the job history is selected without noticing that an error has occurred, the selected job history will be set as a new job setting even though an error has occurred.

[0007]

[0008] ​This invention has been made in view of the above-mentioned problems, and aims to provide a job processing device that allows users to easily confirm that an error has occurred along with the job history on a screen where copy and transmission functions can be selected. [Means for solving the problem]

[0009] Image processing apparatus comprising: a first execution means that executes a copy function using settings set by the user on a copy function setting screen displayed on a display unit; a second execution means that executes a scan function using settings set by the user on a scan function setting screen displayed on the display unit; and a job history list that arranges the job history of the jobs executed by the first execution means and the job history of the jobs executed by the second execution means in the order of job execution, regardless of the type of function including the copy function and the scan function, wherein the job history of the jobs executed by the first execution means is added based on the execution of a job by the first execution means, and the job history of the jobs executed by the second execution means is added based on the execution of a job by the second execution means. The system includes a display control means that causes the display unit to display a list of the job history to which the added jobs are located, wherein the display control means, based on the selection of a job history performed by the first execution means included in the job history list, displays a setting screen for the copy function that reflects the setting values ​​corresponding to the selected job history, based on the selection of a job history performed by the second execution means included in the job history list, displays a setting screen for the scan function that reflects the setting values ​​corresponding to the selected job history, and displays a screen that includes a list of the job history, including the job history performed by the first execution means and the job history performed by the second execution means, and information indicating that there is no paper. [Effects of the Invention]

[0010] On a screen where users can select copy and send functions, they can easily see if an error has occurred, along with the job history. [Brief explanation of the drawing]

[0011] [Figure 1] Block diagram for explaining the configuration of the image processing apparatus according to this embodiment [Figure 2] External view of the operation unit 12 according to this embodiment [Figure 3] Flowchart until the image processing apparatus is started and the screen of the logged-in user is displayed [Figure 4] Schematic diagram of the authentication screen [Figure 5] Schematic diagram of the home screen [Figure 6] Schematic diagram of the home screen [Figure 7] Schematic diagram of the home screen [Figure 8] Schematic diagram of the home screen [Figure 9] Flowchart until an application is started and the execution of a job is completed [Figure 10] Schematic diagram of the copy screen [Figure 11] Schematic diagram of the error screen [Figure 12] Diagram showing the data table stored in the memory area of the copy function [Figure 13] Flowchart for generating the names of the setting buttons and status information buttons to be displayed in the integrated history [Figure 14] Diagram showing the setting data table stored for the integrated history [Figure 15] Diagram showing the setting data table stored for the integrated history [Figure 16] Flowchart for generating the text of the setting value [Figure 17] Flowchart until the history is displayed on the integrated history side [Figure 18] Flowchart for calling an application from the integrated history [Figure 19] Situation explanation table for obtaining the state type and the explanatory text to be displayed from the situation type [Figure 20] Correspondence table of explanation ID and display language string [Figure 21] Schematic diagram of the error screen [Figure 22]Relational Diagram of Image Processing System [Figure 23] History Information Data Transfer Flow Diagram [Figure 24] Integrated History Data Processing Flow Diagram at Logout

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the present invention according to the claims. Also, not all combinations of features described in this embodiment are essential for the solution means of the present invention.

[0013] [First Embodiment] FIG. 1 is a block diagram for explaining the configuration of an image processing apparatus 1 which is an example of a job processing apparatus according to an embodiment of the present invention.

[0014] The image processing apparatus 1 includes a control unit 10, a display / operation unit 12, an image processing unit 13, a scanner 120, and a printer 121.

[0015] The control unit 10 controls the operations of each unit of the image processing apparatus 1. The control unit 10 includes a CPU 100, a communication unit 101, a RAM 102, an HDD 103, a ROM 104, a timer 105, a FAX unit 106, a scanner I / F 108, and a printer I / F 109.

[0016] The CPU 100 controls the entire control unit 10. The RAM 102 functions as a work memory for the CPU 100. The HDD 103 stores application programs and image data. The HDD 103 may be, for example, a storage medium such as an optical medium or a flash memory. The ROM 104 stores programs read by the CPU 100, such as a boot program. Also, the HDD 103 may be configured to be detachable from the image processing apparatus 1 as an external storage device.

[0017] <\ Timer 105 manages the clock and is referenced by CPU 100 to obtain time information.

[0018] The communication unit 101 is connected to the LAN 11 and controls the transmission and reception of data via the LAN 11. The fax unit 106 is connected to the telephone line 14 and controls the transmission and reception of data via the telephone line 14.

[0019] The operation unit 12 includes a display unit 120 to which a touch panel sheet is attached, and an input unit 121 such as hardware keys, and displays a screen and accepts operations from the user. In this embodiment, a liquid crystal display is described as an example of the display unit 120, but other types of displays may be used. In this embodiment, a touch panel is described as an example of the input unit 121, but user operations may be accepted through other interfaces such as a mouse, voice input, or keyboard.

[0020] The image processing unit 13 is controlled by the control unit 10 and includes an image analysis unit 130, an image generation unit 131, and an image output unit 132. The image analysis unit 130 analyzes the structure of the original image and extracts necessary information from the analysis results. The image generation unit 131 reads the original document using the scanner 120, digitizes the image of the document, and generates image data. The generated image data is stored in the HDD 103. The image generation unit 131 can also generate original image data in a different format using the information analyzed by the image analysis unit 130.

[0021] The image processing device 1 has copy, scan, and print functions. The copy function is a function for executing a copy job in which the scanner 120 reads a document and the printer 121 prints an image onto a sheet based on the image data of the scanned document. The scan function is a function for executing a transmission job in which the image data generated by the scanner 120 reads a document is sent via the communication unit 101. The print function is a function for executing a print job in which an image is printed onto a sheet based on print data received from an external information processing device such as a PC via the communication unit 101.

[0022] Figure 2 is an overview view of the operating unit 12 shown in Figure 1.

[0023] In this case, the touch panel 200 has a touch panel sheet attached to the liquid crystal display, and it displays the operation screen and soft keys. When a displayed key is selected, it transmits its position information to the CPU 100. Therefore, in this case, the touch panel 200 can be said to function as both the display unit 120 in Figure 1 and the input unit 121.

[0024] Next, we will explain the various keys and buttons operated by the user. The start key 201 is used to instruct the scanner 120 to start scanning a document. In the center of the start key 201 is a two-color LED 202, green and red, which indicates whether the start key 201 is ready to use. The stop key 203 is used to stop an operation that is currently running. The numeric keypad 204 consists of number and symbol keys and is used to set the number of copies and to switch screens on the touch panel 200. The user mode key 205 is used to access user mode. User mode is a mode for configuring the image processing device 1.

[0025] Figure 3 is a flowchart illustrating the user login process according to this embodiment. The process shown in the flowchart in Figure 3 is realized by the CPU 100 reading a program stored in ROM 104 into RAM 102 and executing it. This flowchart starts when the image processing device 1 is started up. It also starts when the user logs out of the image processing device 1.

[0026] In step S301, the CPU 100 displays an authentication screen on the control unit 12. Screen 200 in Figure 4 is an example of an authentication screen. The screen in Figure 4 includes a username input field 401, a password input field 402, and an OK button.

[0027] In S302, the CPU 100 receives the username and password from the user via the operation unit 12. When the username is entered in the username input field 401 and the password is entered in the password input field 402, and OK 403 is pressed, the CPU 100 stores the entered username and password in the HDD 103 and proceeds to S303. In addition to receiving the username and password entered by the user, or as an alternative, the username and password may be read from a card.

[0028] In S303, CPU100 compares the username and password pre-registered in HDD103 for each user with the username and password received in S302 to determine if they match.

[0029] In S304, if CPU100 determines that there is a match, CPU100 determines that authentication is OK and proceeds to S306. If it determines that there is no match, it proceeds to S305.

[0030] In S305, the CPU 100 causes the operation unit 12 to display an error, and then proceeds to S301.

[0031] In S306, if CPU100 determines that there was a match in S304, it proceeds to process S306.

[0032] In S307, CPU100 logs the user into image processing device 1.

[0033] In S308, CPU100 remembers the currently logged-in user.

[0034] In S309, CPU 100 displays the logged-in user's screen on the control unit 12.

[0035] Figure 5 shows the home screen, which displays objects for selecting the copy function and objects for selecting the send function, depending on when the user logs into the image processing device 1.

[0036] The home screen includes menu 500 and user-specific integrated history 509.

[0037] Menu 500 displays function selection buttons (copy button 501, send button 502, fax button 503) for selecting various functions, and custom buttons for recalling settings pre-configured by the user. Examples of custom buttons include a contract button 504, a request form button 505, and a send to myself button 506.

[0038] These buttons are displayed in a layout customized by the user, based on the user's information after logging into the image processing device 1. Some buttons are "My" buttons, which are only displayed on the user's personal home screen, while others are "Share" buttons, which are displayed on all users' home screens as well.

[0039] The slider bar 507 is a bar that is operated to display buttons that cannot be shown at once, indicating that this menu 500 can be slid and moved. When this slider bar is slid, the arrows are pressed, or the menu 500 is flicked, the CPU 100 receives the operation and retrieves and displays application buttons and custom buttons registered in the next area from the HDD 103.

[0040] Currently, the username of the user logged into the image processing device 1 is displayed in the username display area 508 in the upper right corner. Figure 5 shows the state where "User A" is logged into the image processing device 1.

[0041] The Integrated History 509, which will be explained in detail later, is an area that automatically registers the execution history of jobs of multiple applications executed by this image processing device 1, along with the job settings, and displays them as history records in chronological order of job execution. The further down you go in the Integrated History 509, the older the job execution time, and the further up you go, the more recent the job execution time. In other words, the higher up you go, the more recently executed job history records are displayed, making it easier for the user to check the history records of recently executed jobs without having to operate the slider bar 507.

[0042] When a user logs into the image processing device 1, the integrated history 509 area displays only the history of jobs previously performed by the logged-in user. If the user has never performed a job, or if they have deleted a record from the integrated history 509, the display in the integrated history 509 area will be empty, as shown in Figure 5(A).

[0043] From this point forward, the display of the integrated history 509 will be controlled by the CPU 100 based on the application for displaying the integrated history stored in the HDD 103 (hereinafter referred to as the integrated history or integrated history application). Furthermore, the data used in the integrated history will be stored in the HDD 103.

[0044] Figure 9 is a flowchart of the execution of a job according to this embodiment. The processing in the flowchart of Figure 9 is achieved by the CPU 100 reading the program stored in the ROM 104 into the RAM 102 and executing it. This flowchart starts when the copy button 501 of the image processing device 1 is selected.

[0045] In the S601, the CPU 100 displays the copy screen on the operation unit 12. The user can set the number of copies, monochrome / color settings, single-sided / double-sided scanning settings, magnification settings, and paper settings via the copy screen. The CPU 100 stores the received settings in the HDD 103. Figure 10(A) shows the copy screen 200. The copy screen 200 includes a color selection button 703, a magnification setting button 704, a paper selection button 705, a finishing button 706, a double-sided button 707, a density button 708, a document type button 709, and an ID card copy button 710. The copy screen 200 also has other function buttons 711, a setting history button 712, and frequently used setting buttons 713. The color selection button 703 is used to set whether to scan the document in color or monochrome. The magnification setting button 704 is used to set the magnification for scanning the document and enlarging or reducing the image for printing. The paper selection button 705 is used to select the printing paper. The finishing button 706 is used to set whether to print pages in order from the first page and output without stapling, or to print pages in order from the first page and output with stapling. The duplex button 707 is used to set whether to scan only one side of the document or both sides of the document. The density button 708 is used to set the density of the printed image. The document type button 709 is used to select whether the document type is text, text / photo, or photo. The ID card copy button 710 is used to set the ID card copy mode, which scans the images on both sides of the document and prints them side by side on the same side of a single sheet of paper.

[0046] The other function button 711 is for setting functions other than those mentioned above (for example, punch function, watermark printing function, etc.). The setting history button 712 is for displaying the history of settings used in past copying operations. The frequently used settings button 713 is for displaying a screen where the user can register, edit, and recall frequently used settings. The home button 714 is for returning to the home screen.

[0047] The settings confirmation button 702 is a button that displays a list of the currently set copy settings as text.

[0048] In the screen shown in Figure 10(A), the settings are displayed in area 701 and on each button, indicating that the color is set to black and white, the magnification to 100%, the paper size to automatic, the number of copies to 1, and sorting to sort.

[0049] The user sets up the copy settings in this way, places the document on scanner 120, and then presses the start key 201.

[0050] In S602, CPU100 determines whether or not the start key 201 has been pressed.

[0051] In S603, CPU100 reads the settings received via the copy screen in Figure 10(A) from HDD103 and executes the copy job according to the read settings.

[0052] In S604, CPU100 stores the settings of the executed copy job in HDD103 as the job execution history. Here, CPU100 stores the time information obtained by referring to timer105 as part of the job execution history.

[0053] Figure 12(A) shows an example of data stored in the memory area of ​​the copy function of HDD103 in S604. As shown in the header 801 of the data table in Figure 12(A), this table records the application settings. The first row, Default Settings 802, stores the default settings for the copy function, and the second row, Current Settings 803, additionally stores the settings for the job executed this time.

[0054] Figure 13 shows the flow for generating the names of the buttons to be displayed in the integration history 509 on the application side. The processing in the flowchart of Figure 13 is achieved by the CPU 100 reading the program stored in ROM 104 into RAM 102 and executing it. This flowchart is executed in accordance with the completion of job execution in S604 of Figure 6.

[0055] After the job completion in S604 in Figure 6, in S901, the CPU 100 retrieves the integrated history 509 data stored in the HDD 103. Figure 14(A) is the data table stored for the integrated history 509. As shown in the header 1001 of the data table, the button ID, application ID, and data type are stored. In addition, the data of the setting values ​​set by the application, or the status type of the device itself or individual job detected by the application, the date and time, and text data of the setting value or occurrence status are stored.

[0056] The Button ID is an ID used to uniquely identify the history registered in the Integrated History 509. The Application ID is an ID used to identify which application executed the job in the history registered in the Integrated History 509. This Application ID is predetermined for each application, such as "100" for the device's management application, "101" for copy, and "201" for send.

[0057] The data type identifies the type of data body, which will be described later. "Settings" represents job setting data, and "Status" represents status information data for the device itself or for individual jobs.

[0058] The data represents the job settings executed by the application. For example, in a copy application, it contains all the functions and settings that the application configures, such as the number of copies, color, and paper size.

[0059] The displayed text consists of the date and time and the setting value. The setting value is information necessary for the application to manage the settings used in the job and the status of the device. The status of the device can be categorized into the status type of the device itself and the status type of the job. The status type of the device itself is information about the device itself, such as a failure in the fax line, as shown in line 1006 of Figure 15(A). The status type of the job is a status type related to a specific job, such as an error occurring when sending an email, as shown in line 1007 of Figure 15(B).

[0060] The format of these various data is stored in a format that can be read by the application that registered the data. The date and time in the displayed text is the date and time when the job was executed, or when the application detected the status of the device itself or individual jobs, and is the text data displayed on the button in the integrated history 509. The setting value in the displayed text is text data that picks out characteristic settings from the settings of the executed job, or a characteristic message that represents the status of the device itself or individual jobs detected by the application, and this is also displayed on the button in the integrated history 509. This date and time and setting value text allows the user to look at the integrated history 509 and recall what settings each history entry represents for the job that was executed.

[0061] When data from the integrated history 509 is obtained in S901, in S906 the CPU 100 determines whether the situation in the image processing device 1 has changed.

[0062] If the situation has not changed, then in S902, CPU100 compares the acquired data with the data of the job settings executed this time to check if there is already a history of the same setting data in the integrated history 509. The reason for comparing the data in integrated history 509 with the setting data executed this time is to eliminate duplication of history. If there is duplication, the limited display area of ​​integrated history 509 may be filled with the same settings. For users who reuse the history, having a variety of settings displayed rather than a list of the same settings gives them more choices. In this case, there is no data to compare, so CPU100 determines that the current setting data is not in the existing history data. If there is no history data of the same setting in integrated history 509, in S903, CPU100 starts the process of generating the text of the setting value to be displayed in the history.

[0063] Figure 16 shows the flow for generating setting value text. The processing in the flowchart of Figure 16 is achieved by the CPU 100 reading the program stored in ROM 104 into RAM 102 and executing it.

[0064] First, in S1107, CPU100 determines whether the custom button name 1802 has been notified to the application from menu 500. The name is one of the pieces of information notified to the application when one of the custom buttons (504-506) is selected in menu 500 and a job is executed, as explained in the operation of the custom buttons. If CPU100 determines that the name 1802 has been notified, CPU100 compares the custom setting value with the current setting value in S1109. If it determines that there is no difference, in S1108 CPU100 replaces the TXT data with the notified name 1802 and terminates the flow. If it determines in S1107 that the name has not been notified, or if it determines in S1109 that the name has been notified but the job settings have been changed from the custom settings, the process proceeds to S1109.

[0065] Furthermore, if the process proceeds from S1107 to S1101, CPU100 compares the settings of the job executed this time with the default settings. Specifically, CPU100 compares the settings items in Figure 12(A) from left to right. In this example, CPU100 starts the comparison with the number of copies. If there is one or more differences as a result of the comparison, CPU100 retrieves the text of the setting in S1102. The reason for picking out the differences from the default settings is that it can be assumed that the items that the user intentionally changed are more likely to leave a lasting impression. In this case, first there is a difference in the number of copies, so the setting text that CPU100 first retrieves is "2 copies". Next, in S1103, CPU100 retrieves the length of the text. Since there is a limit to the number of characters that can be displayed on the buttons displayed in the integration history 509, CPU100 checks in S1104 whether the display limit has been reached. If CPU100 determines at this point that the display limit has been exceeded, the text data will not be added and the display text generation process will end. If the limit has not been reached, in S1105, CPU100 adds the read text data as the setting value text data to be displayed in the integrated history 509. If there are still setting differences, the process proceeds from S1106 to S1102, and CPU100 repeats the process from S1102 to S1105. If there are no more setting data differences before the display limit is reached, the text data generation will also end. In this case, the difference is up to the double-sided setting, so "2 copies, color, double-sided" is generated as text data, and since there are no further differences, that is the end of the setting value text data. Finally, CPU100 saves the application ID of the application it executes and the setting data saved in HDD103 in S604 of Figure 6 as data1.xml. In addition, the generated configuration text, the job execution date and time text, and whether or not existing data exists are saved to HDD103, and CPU100 in S904 sends these contents to integrated history 509. Whether or not existing data exists is the result of comparison in S902.

[0066] In this way, the objects that will be displayed in the integration history are registered.

[0067] Next, we will explain the case where the process proceeds to S907 based on the judgment in S906. For example, if a fax line failure is detected, the process proceeds from S906 to S907. The image processing device 1 has a "status monitoring application" for monitoring the status of its own device. The status monitoring application is stored in the HDD 103, read into the RAM 102 by the CPU 100, and executed.

[0068] In S901, CPU100 retrieves the data for the integrated history 509 stored on HDD103. The data table stored for the integrated history 509 is in the state shown in Figure 14(E).

[0069] In S906, if the CPU 100 determines that the status of the image processing device 1 has changed, in S907 the CPU 100 determines whether a new status has occurred. If it determines that a new line disconnection has occurred, the CPU 100 obtains the status type and the description to be displayed from the detected status type according to the status description table shown in Figure 19(A). The CPU 100 obtains status type = "Line" (1402), status = "Disconnected" (1403), status type = "Warning" (1404), and description ID = "MSG_ID_FAX_LINEOFF" (1405). Status type = "Warning" indicates a state in which the use of the device or the application affected by it is stopped.

[0070] Next, CPU 100 runs the status monitoring application and refers to the correspondence table between the description ID and the display language string shown in Figure 20. Then, according to the acquired description ID = "MSG_ID_FAX_LINEOFF", CPU 100, in S908, acquires the status TXT = "Please check the fax line." (1503) in accordance with the display language of the operation unit 12. Finally, in S909, CPU 100 sends the acquired status type = "Warning" (1402) and display string = "Please check the fax line." (1503) as a status TXT to the integrated history. Here, CPU 100 sends these, along with the application ID, data type, status TXT, date and time TXT, and no existing data, as status type and status to the integrated history as status information data = "FAXLINE_ERROR.xml". As a result, the data table stored for the integrated history 509 becomes as shown in Figure 15(A), and the screen becomes as shown in Figure 8(A). In Figure 8(A), error record 517 is displayed above the other history records 514-516, taking precedence over them. Error record 517 also includes a warning icon on its left side.

[0071] Furthermore, if the CPU 100 detects that the fax line connection has been restored, it generates "Line" as the status type and "Normal" as the status. Since "Line" as the status type is already present in the integrated history 509, the status monitoring application determines that this is not a newly occurring situation. In S910, the CPU 100 requests the integrated history 509 to delete this information, and in S911, it determines whether the situation has been resolved. If the determination in S911 does not indicate that any situation other than "Normal" as the status type has been resolved, then in S908, it performs the same processing as when a new situation occurs. As a result, the status information for the new status is displayed in the integrated history 509. In this case, the status type corresponding to "Line" and "Normal" is "Normal," so the CPU 100 determines in S911 that the situation has been resolved and terminates processing. As a result, the status display that was shown in the integrated history 509 disappears.

[0072] The above explanation describes the situation when CPU100 detects a network disconnection, but it operates similarly when the application submitting the job detects a situation that should notify the user.

[0073] For example, suppose a copy application is instructed to execute a job with stapling settings that exceeds the maximum number of pages that can be stapled on the device. As already described, the behavior when a user executes a copy job, here we will only describe the behavior that occurs when some situation arises that requires notification to the user regarding the execution of a copy job.

[0074] First, the copy application reads the document placed by the user according to the set conditions and calculates the total number of sheets to be printed. In this example, the copy application determines that the total number of printed sheets exceeds the maximum number of sheets that can be stapled. Accordingly, the copy application generates status type = "Execute", state = "Number of stapled sheets exceeded", and status type = "Warning". Status type = "Warning" does not stop execution, but it is a status type that alerts the user. As a result, in S906, the copy application executed by CPU100 determines that the situation has changed. Next, in S907, the copy application determines whether a new situation has occurred. If the status monitoring application determines that status type = "Execute" is a newly occurring situation, the copy application obtains the status type and the explanatory text to be displayed from the status type detected by the copy application, according to the status explanation table shown in Figure 19(B). The copy application obtains a status type = "Executing" (1409), a status = "Number of staples exceeded" (1406), and a description ID = "MSG_ID_COPY_STAPLEOVER" (1407). Next, based on the correspondence table between description IDs and display language strings shown in Figure 20, the copy application obtains a status TXT = "Number of staples exceeded." (1505) according to the obtained description ID = "MSG_ID_COPY_STAPLEOVER" (1504) and the display language of the operation panel (S908). Finally, in S909, the copy application sends the obtained status type = "Caution" and display string = "Number of staples exceeded." (1505) as a status TXT to the integrated history. Here, the copy application sends the status type and status, along with information such as application ID, data type, status TXT, date and time TXT, and no existing data, to the integrated history as status information data = "STAPLEOVER.xml" (S909). As a result, the data table saved for the integrated history 509 will be in the state shown in Figure 15(B), and the screen will look like Figure 8(B). In Figure 8(B), error record 518 is displayed above the other history records 514-516, taking precedence over them. Also, error record 517 includes an error icon on the left side.

[0075] Figure 17 shows the flow from when the integrated history 509 receives the above-mentioned configuration information data or status information data until it displays the history.

[0076] In S1201, the integrated history 509, which is executed by CPU100, receives the value stored in HDD103 in S904 (Figure 9) from the application side executed by CPU100. Next, in S1202, CPU100 determines whether the received data is configuration data. If it is determined to be configuration data, in S1203, CPU100 checks whether there is existing data or not. In this case, there is no existing data, so in S1204, CPU100 adds the data received from the application side to the data table of integrated history 509. The data received from the application side is added to the data table as shown in Figure 14(B). If there was existing data, in S1205, CPU100 updates only the date.

[0077] If the CPU determines that the received data is not configuration data, in S1206, the CPU 100 checks whether existing data exists. If it determines that there is no existing data, in S1207, the CPU 100 adds the data received from the application to the data table of the integrated history 509. The data received from the application is added to the data table as shown in Figure 14(E) for button ID 1003. If existing data exists, in S1208, the CPU 100 updates only the date.

[0078] The screen on the control unit 12 is still the copy screen, so when the home button 714 is selected, the CPU 100 displays the home screen shown in Figure 5(B). As shown in Figure 5(B), the home screen for user A is displayed with the button 510 for the current history displayed in the integrated history 509. The current history 510 displays the application icon 511 identified by the application ID, the job execution date and time 512, and text 513 representing the difference from the default settings. The application icon 511 is the icon for the copy job. The icon for the send job is displayed as the icon in the history record 515 in Figure 6(B). This information is important for helping the user remember what the settings were when they look at the current history 510. When the user wants to run a job with the same settings, pressing this history 510 will cause the CPU 100 to call the application with the same settings reflected.

[0079] Figure 18 illustrates the flow for calling an application from the integration history 509. The flowchart in Figure 18 is realized when the CPU 100 reads the program stored in the ROM 104 into the RAM 102 and executes it.

[0080] When the user selects a history record 510 (also called a history record or object) in the integrated history 509 shown in Figure 5(B), S1301 reads the history data for the selected button ID from the data table of the integrated history 509 stored in the HDD 103. The integrated history 509 determines the target application from the application ID of the read history data, and in S1302 sends the configuration data to that application. In this case, since it is a copy, the copy application is called by the CPU 100. In S1303, the copy application running on the CPU 100 reads the setting values ​​of various settings from the received data and displays the application screen on the operation unit 12 with the settings reflected. Figure 10(B) shows the copy screen displayed with the settings of history 510 reflected.

[0081] In this way, using the integrated history 509, users can recall and use settings they have previously implemented with a single touch.

[0082] Next, we will explain what happens when you change some settings from the configuration retrieved from integration history 509 and then run the job.

[0083] In this case, let's assume that, with the previous settings, S602 changes only the number of copies to 5, and the user presses the start key 201. In S603, the application running on CPU100 executes the job according to the settings. In S604, CPU100 overwrites and saves the job execution settings as shown in line 804 of the current settings in the second line of Figure 12(B). After that, as described above, in the flow of Figure 13, the data already in the integrated history 509 is compared with the current setting data. Since the current setting is not in the existing data, in the flow of Figure 16, a text of the setting difference is generated, and various data is sent to the integrated history 509. After that, in the flow of Figure 17, the history of the new setting is added. Figure 14(C) shows the history where line 1003 has been newly added to the data table. Figure 6(A) shows the screen where history 514 is newly displayed in the integrated history 509 on the home. The integrated history 509 is sorted in descending order by job execution date and time and displayed in order, so as shown in Figure 6(A), the history of the newly added job is added to the top of the list.

[0084] In this way, by reusing job settings that a user has used before, the effort required for the user to configure jobs can be reduced.

[0085] If you select the history 510 of the copy that was executed first in Figure 6(A) and run the job without changing any settings, the system will determine in S902 of Figure 13 whether there is existing data in the integrated history 509 and that there is. Therefore, the process in S903 that generates the text is not executed. Consequently, in S905, the date and time text, the information that there is an existing ID, and the data of which button ID in the integrated history 509 it corresponds to are sent from the application to the integrated history 509. Since there is an existing ID, the process in S1202 of the process to determine whether there is an existing ID or not in the process of saving the data in the integrated history 509 in Figure 17 will determine that there is an existing ID, and in S1204, the CPU 100 updates and saves only the date of the data with a matching button ID in Figure 14(D).

[0086] Figure 14(E) shows data 1005 with an updated date. Since the integrated history 509 displays the history in descending order by date, the history 516 of the copy that was just executed, as shown in Figure 7(A), becomes the first entry in the settings history.

[0087] Next, we will explain the case where, by selecting the transmission history 515 in Figure 7(A), the corresponding job settings are retrieved, but the user returns to the home screen without executing the job. In this case, since the job was not executed, the process from saving the settings in S604 in Figure 9 onwards is not performed. Therefore, no particular history data update process is performed, and the display remains as in Figure 7(A).

[0088] Next, Figure 18 illustrates the flow of calling an application from integration history 509.

[0089] The screen is shown in Figure 8(A), and the data for integrated history 509 is shown in Figure 15(A).

[0090] When the user presses error record 517 in the integrated history 509, the integrated history 509, which operates on the CPU 100, reads the history data for the pressed button ID=1004 from the data table shown in Figure 15(A) of the integrated history 509 stored on the HDD 103. The integrated history 509 determines from the application ID=100 of the read history data that the target application is a status monitoring application, and in S1302, sends status information data=“FAXLINE_ERROR.xml” to that status monitoring application. The status monitoring application, which operates on the CPU 100, reads the status type and status from the received status information data=“FAXLINE_ERROR.xml”. Then, it checks the current status of this status type=“Line”, and in S1303, displays a screen on the touch panel 200 showing guidance on how to resolve the situation. Figure 21 shows the status monitoring application screen displayed reflecting the status of error record 517.

[0091] In this way, the integrated history 509 allows the user to view their desired status with a single touch of a button.

[0092] Similarly, the user can display information about the copy application in the state shown in Figure 8(B) and Figure 15(B) with a single button click. This will be explained below.

[0093] When the user presses error record 518 in the integrated history 509, the integrated history 509, which operates on the CPU 100, reads the history data for the pressed button ID=1004 from the data table shown in Figure 15(B) of the integrated history 509 stored on the HDD 103. The integrated history 509 determines from the application ID=101 of the read history data that the target application is a copy application, and in S1302, sends status information data=“STAPLEOVER.xml” to the copy application. The copy application, which operates on the CPU 100, reads the status type and state from the received status information data=“STAPLEOVER.xml”, and in S1303, displays a screen on the operation unit 12 that matches the status type=“Execution”, state=“Staple count overflow”. Figure 21 shows the status monitoring application screen displayed reflecting the status of error record 518.

[0094] If a copy job is interrupted due to lack of paper, the copy application generates a status type = "Executing", status = "No paper", status type = "Interrupted" (1408), and the integrated history data becomes as shown in Figure 15(C), resulting in the display shown in Figure 8(C). In Figure 8(C), error record 519 takes precedence over other history records 514-516 and is displayed above them. Error record 519 also includes an error icon on the left. When the user selects this error record 519, the copy application displays a paper feed tray selection screen as shown in Figure 11(B). If the user specifies a paper feed tray with paper, or replenishes paper in the specified paper feed tray, the copy application determines that the "no paper" status has been resolved and starts the interrupted copy job. At the same time, as already explained, since the "no paper" status has been resolved, the copy application, which detected this change in S907, requests the deletion of the status information from the integrated history 509, and since the status has been resolved, the process ends there. As a result, the integrated history data is shown in Figure 14(E), the home screen is shown in Figure 7(A), and it is clear that there is nothing for the user to do.

[0095] Next, we will explain how to register and delete entries in the integrated history 509 menu.

[0096] The buttons displayed in the integrated history 509 will display a context menu 580 for the operation of the button itself when the user long-presses the history button, as shown in Figure 7(B). Although long-pressing is given as an example of a user operation to display the context menu 580, the method of calling up the context menu 580 is not limited to long-pressing, and double-tapping or a dedicated call button may be provided. The context menu 580 includes context menus such as Execute 581, Register to Menu 582, and Delete 583 as operations for the buttons in the integrated history 509.

[0097] If you select Execute 581 in Figure 7(B), the CPU 100 will perform the application call process, as already explained using Figure 18. If you select Register to Menu 582 in Figure 7(B), the CPU 100 will perform the process of registering the custom button as a new button in the left-hand menu 500. The position of the registered button can be either a blank space in menu 500 or a position selected by the user.

[0098] If the user presses Delete 583 in Figure 7(B), the CPU 100 executes the process of deleting the selected history. The CPU 100 deletes the item from the data table of the history order and the data table of the integrated history 509 in Figure 14, and then performs sorting of the remaining history by date and time.

[0099] If the CPU 100 determines that the selected history button 509 is a status information button and not a setting button, it will not display "Register" 582 in the menu, and will only display "Execute" 581 and "Delete" 583.

[0100] Next, we will explain what happens when the number of history records or error records in the integrated history 509 reaches its limit.

[0101] When jobs with different settings are repeatedly executed and the maximum number of entries in the integrated history (509) is reached, CPU 100 deletes the oldest entries from the data table in order. This limit is the storage limit and is not necessarily the same as the display area limit. This is because the display area limit is variable depending on settings such as button size and layout, and whether or not scrolling is enabled using slider bars or flick gestures.

[0102] According to this embodiment, on a screen where users can select copy and send functions, they can easily check the job history in history records and confirm that errors have occurred using error records. Furthermore, since error records are displayed above history records, users are more likely to notice errors when they occur. Additionally, by displaying error records along with the date and time the error occurred, users can easily confirm when the error occurred using the error records.

[0103] [Second Embodiment] In the second embodiment, the process for sharing the integrated history data described above between image processing devices will be described.

[0104] Figure 22 schematically illustrates the relationships between image processing devices.

[0105] Image processing device 1, image processing device 2, and image processing device 3 are image processing devices that each have the functions described above, and are interconnected by a LAN as shown in the diagram.

[0106] The authentication process described in Figure 3 is interconnected, and a user authenticated by image processing device 1 can also be authenticated as the same user by image processing device 2 and image processing device 3. Let's assume that image processing device 1 also functions as an authentication server.

[0107] Assume that user A is viewing Figure 8(A) on image processing device 1, and the integrated history data is in the state shown in Figure 15(A). When user A logs into image processing device 2 in this state, if the setting for user identification is ON, after image processing device 2 starts up, the CPU 100 displays an authentication screen on the touch panel 200 (S301). Figure 4 is the authentication screen displayed on image processing device 2. The authentication screen has fields for entering a username 401 and a password 402. After displaying the authentication screen, image processing device 2 waits for the user to enter a username and password (S302). When the user enters a username and password that they have registered in advance and presses the OK button 403, the CPU 100 sends this information to image processing device 1. Image processing device 1 compares the username and password stored on HDD 103 with the entered username and password to see if they match (S303). If the username and password do not match, image processing device 1 returns an authentication error to image processing device 2 (S304). When the CPU 100 of the image processing device 2 receives an authentication error, it displays an error message on the touch panel 200 and displays the authentication screen again (S305). If the image processing device 1 determines that the username and password match, the CPU 100 of the image processing device 1 retrieves the user-related information stored in the HDD 103 and sends it to the image processing device 2 (S306). When sending history information data to another device, the transmission data is generated according to the flow shown in Figure 18. First, the reading position [i] of the history information data and the writing position [j] of the transmission data are initialized to 0 (S1801). Next, it is checked whether the history information data [i] exists (S1802). If the data [i] exists, the data [i] is read (S1803) and it is checked whether the data type is "setting" (S1804). If the data type is "setting", the read data [i] is set in the transfer data [j] (S1805), and the reading position [i] of the history information data and the writing position [j] of the transmission data are advanced by one (S1806). If the data type is not "setting", the reading position [i] of the history information data is advanced by one (S1807).Subsequently, the system checks if data [i] corresponding to the read position [i] of the updated history information data exists (S1802). If it determines that data [i] to be read does not exist, it sends the data to be transmitted (S1808). Once the image processing device 2 has finished retrieving the information associated with the user, the CPU 100 allows the user to log in (S307) and saves the user as the currently logged-in user on the HDD 103 of the image processing device 2 (S308). After that, the CPU 100 of the image processing device 2 displays a home screen on the touch panel 200 that reflects the information of the retrieved logged-in user (S309). At this point, the history information data for user A in the image processing device 2 is as shown in Figure 14(E), and the home screen for user A is shown in Figure 7(A).

[0108] When user A logs out, image processing device 2 sends user information to image processing device 1 and updates the user information.

[0109] According to this embodiment, the integrated history data described above can be shared between image processing devices, so that history records and error records can be checked even when using a different image processing device.

[0110] [Third Embodiment] In the embodiment described above, both configuration data and status information data were managed similarly, and distinguished by their data types. The third embodiment shows an example in which all status information data is deleted when the user logs out.

[0111] Only the differences from the first embodiment will be described.

[0112] When a logout command is received, the CPU 100 first initializes the read position [i] of the history information data and the write position [j] of the saved data to 0 (S1901). Next, it checks whether the data [i] of the history information data exists (S1902). If the data [i] exists, it reads the data [i] (S1903) and checks if its data type is "setting" (S1904). If the data type is "setting", it sets the read data [i] into the saved data [j] (S1905) and advances the read position [i] of the history information data and the write position [j] of the saved data by one (S1906). If the data type is not "setting", it advances the read position [i] of the history information data by one (S1907). Subsequently, it is checked whether data [i] corresponding to the read position [i] of the updated history information data exists (S1902). If it is determined that data [i] to be read does not exist, the data is overwritten with the saved data and saved (S1908). As a result, if the integrated history data processing at logout is performed when the history information data is in the state shown in Figure 15(B) or Figure 15(C), data 1006, whose data type is other than setting, will not be saved, and consequently, the history information data will be saved in the state shown in Figure 14(E).

[0113] Upon logging in again, the status managed by each application is registered in the integrated history 509. If the history information data before logging out is as shown in Figure 15(A) and the status has not changed, the overall device status monitoring application registers data similar to data 1006 as a newly occurring status, as described in the first embodiment. However, the date and time of this registration will be the date and time when the new status was detected.

[0114] Furthermore, if the history data before logging out was as shown in Figure 15(B), the copy job did not exceed the number of staples, so the copy application does not register the status, and the history data starts in the state shown in Figure 15(B).

[0115] According to this embodiment, all status information data is deleted when the user logs out, so there is no need to redisplay status information that the user has already viewed.

[0116] Furthermore, the object of the present invention can also be achieved by performing the following process: supplying a storage medium containing program code for software that realizes the functions of the above-described embodiment to a system or device, and having the computer (or CPU, MPU, etc.) of the system or device read the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the above-described embodiment, and the program code and the storage medium containing the program code constitute the present invention. [Explanation of symbols]

[0117] 100 CPU 102 RAM 103 HDD

Claims

1. An image processing device, A first execution means that executes the copy function using the settings set by the user on the copy function screen displayed on the display unit, A second execution means that executes the scan function using the settings set by the user on the scan function screen displayed on the display unit, The system includes a display control means that causes the display unit to display a job history list which is a list of jobs executed by the first execution means and a list of jobs executed by the second execution means, arranged in the order of job execution regardless of the type of function including the copy function and the scan function, wherein the job history of jobs executed by the first execution means is added when the first execution means executes a job, and the job history of jobs executed by the second execution means is added when the second execution means executes a job, and the job history of jobs executed by the second execution means is added when the second execution means executes a job, The display control means is Based on the selection of a job history executed by the first execution means included in the job history list, the copy function screen is displayed with the setting values ​​corresponding to the selected job history reflected. Based on the selection of a job history executed by the second execution means included in the job history list, the scan function screen is displayed with the setting values ​​corresponding to the selected job history reflected. An image processing apparatus characterized by displaying information about jobs that have been interrupted due to lack of paper in the job history list, which includes the job history of jobs executed by the first execution means and the job history of jobs executed by the second execution means.

2. The image processing apparatus is an image processing apparatus having a plurality of paper feeding units, The image processing apparatus according to claim 1, characterized in that the display control means displays a screen for selecting a paper feed unit from the plurality of paper feed units to feed paper to be used for printing, based on the selection of information of the job that has been interrupted due to the lack of paper.

3. The image processing apparatus according to claim 1 or 2, characterized in that the display control means displays a screen related to paper feeding based on the selection of information about the job that has been interrupted due to the lack of paper.

4. The image processing apparatus according to any one of claims 1 to 3, characterized in that the display control means displays information regarding the execution date and time of the job which has been interrupted due to lack of paper as information about the job.

5. The job that is interrupted due to lack of paper is a copy function job, The image processing apparatus according to any one of claims 1 to 4, characterized in that the display control means displays at least one of the setting values ​​of the copy setting items set for the job that has been interrupted due to lack of paper as information for the job.

6. The image processing apparatus according to any one of claims 1 to 5, characterized in that the display control means displays the list of jobs on the home screen.

7. The image processing apparatus according to claim 6, wherein the home screen is a screen that includes a button for displaying the copy function screen, and is a screen that is displayed based on the selection of a predetermined button on the copy function screen.

8. A method for controlling an image processing apparatus, A first execution step involves executing the copy function using the settings set by the user on the copy function screen displayed on the display unit, A second execution step involves executing the scan function using the settings set by the user on the scan function screen displayed on the aforementioned display unit, A first display control step causes the display unit to display a job history list which is a list of jobs executed in the first execution step and a list of jobs executed in the second execution step, arranged in the order of job execution regardless of the type of function including the copy function and the scan function, wherein the job history of jobs executed in the first execution step is added based on the execution of a job in the first execution step, and the job history of jobs executed in the second execution step is added based on the execution of a job in the second execution step. A second display control step, based on the selection of a job history from the first execution step included in the job history list, displays the copy function screen with the setting values ​​corresponding to the selected job history reflected; The third display control step includes, based on the selection of a job history from the second execution step included in the job history list, a third display control step that displays a screen for the scan function that reflects the setting values ​​corresponding to the selected job history, A control method for an image processing apparatus, characterized in that, in the first display control step, information of jobs that have been interrupted due to lack of paper is displayed in the job history list, which includes the history of jobs executed in the first execution step and the history of jobs executed in the second execution step.

9. A computer program that causes a computer to execute each means of the image processing apparatus described in any one of claims 1 to 7.

Images