Image processing apparatus, control method, and storage medium

Abstract

To provide a job processor for easily confirming the occurrence of an error together with the history of a job.SOLUTION: An image processing apparatus that displays a home screen including a menu 500 and an integrated history 509 for each user, the image processing apparatus comprising a first execution unit configured to execute a copy job, a second execution unit configured to execute a scan job, and a display control unit configured to display a third object corresponding to a history 510 of a first copy job for which an execution instruction has been received but copying has not been completed, a fourth object corresponding to a history of a second copy job for which copying has been completed, and a fifth object corresponding to a history of a scan job, the display control means displays an icon included in the third object and an icon included in the fourth object in different display modes.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

[0002] 2. Description of the Related Art Conventionally, there are job processing apparatuses that execute jobs and store 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 from which a copy function or a transmission function is selected (see Patent Document 1).

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

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2018-125686 Summary of the Invention [Problem to be solved by the invention]

[0006] With conventional technology, the job execution history is displayed on the home screen, but it is not possible to confirm that an error has occurred. Therefore, if you select the job history without realizing that an error has occurred, the history of the selected job will be set as the settings for a new job, even though an error has occurred.

[0007] In this state, even if an instruction to execute a job is accepted, the execution of the job may be interrupted due to an error.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a job processing device that allows easy confirmation of the occurrence of an error along with the job history on a screen where copy and send functions can be selected. [Means for solving the problem]

[0009] an image processing device that displays a home screen including a first object for displaying a setting screen for a copy function and a second object for displaying a setting screen for a scan function, the image processing device comprising: a first execution means for executing a copy job using setting values ​​set on the setting screen for the copy function that is displayed based on selection of the first object; a second execution means for executing a scan job using setting values ​​set on the setting screen for the scan function that is displayed based on selection of the second object; and a display control means for displaying on the home screen a third object corresponding to a history of a first copy job for which an execution instruction has been received but copying has not been completed, a fourth object corresponding to a history of a second copy job for which copying has been completed, and a fifth object corresponding to a history of a scan job for which scanning has been completed, wherein the display control means displays a screen that allows a copy job to be executed again based on at least one setting value used for the second copy job based on selection of the fourth object displayed on the home screen, and the third object and the fourth object include icons; The icon included in the third object corresponding to the history of the first copy job for which an execution instruction has been received but copying has not been completed and the icon included in the fourth object corresponding to the history of the second copy job for which copying has been completed are displayed in different display modes. [Effects of the Invention]

[0010] The user can easily check the job history and any errors that have occurred on a screen where they can select copy and send functions. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating the configuration of an image processing apparatus according to an embodiment of the present invention. [Figure 2] FIG. 1 is an external view of an operation unit 12 according to the present embodiment. [Figure 3] Flow diagram from starting up the image processing device to displaying the login user's screen [Figure 4] Schematic diagram of the authentication screen [Figure 5] Home screen diagram [Figure 6] Home screen diagram [Figure 7] Home screen diagram [Figure 8] Home screen diagram [Figure 9] Flow diagram from starting an application to completing job execution [Figure 10] Copy screen diagram [Figure 11] Schematic diagram of the error screen [Figure 12] A diagram showing the data table stored in the memory area of ​​the copy function [Figure 13] Flow diagram for generating names for the setting button and status information button displayed in the integrated history [Figure 14] Diagram showing the configuration data table stored for integration history [Figure 15] Diagram showing the configuration data table stored for integration history [Figure 16] Flow diagram for generating text for a setting value [Figure 17] Flow diagram for displaying history on the integrated history side [Figure 18] Flow diagram for calling an application from the integration history [Figure 19] A status explanation table for acquiring a status type and an explanation to be displayed from the status type. [Figure 20] Description ID and display language string correspondence table [Figure 21] Schematic diagram of the error screen [Figure 22] Image processing system diagram [Figure 23] History information data transfer flow chart [Figure 24] Flowchart of integrated history data processing at logout DETAILED DESCRIPTION OF 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 scope of the present invention. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0013] [First embodiment] FIG. 1 is a block diagram illustrating 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 device 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 operation of each unit of the image processing device 1. The control unit 10 includes a CPU 100, a communication unit 101, a RAM 102, a 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 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. The HDD 103 may be configured to be detachable from the image processing device 1 as an external storage device.

[0017] The timer 105 manages a clock and is referenced by the 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 has 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 used as an example of the display unit 120, but other types of displays may also be used. In this embodiment, a touch panel is used as an example of the input unit 121, but operations from the user may also 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 an original image and extracts necessary information from the analysis results. The image generation unit 131 reads an original document using the scanner 120, digitizes the image of the original 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 a copy function, a scan function, and a print function. The copy function is a function for executing a copy job in which an original is read by the scanner 120 and an image is printed on a sheet by the printer 121 based on the image data of the read original. The scan function is a function for executing a transmission job in which the image data generated by reading an original by the scanner 120 is transmitted via the communication unit 101. The print function is a function for executing a print job in which an image is printed on a sheet based on print data received via the communication unit 101 from an information processing device such as an external PC.

[0022] FIG. 2 is a schematic view of the operation unit 12 of FIG.

[0023] Touch panel 200, in this case, is a liquid crystal display with a touch panel sheet attached thereon, and displays an operation screen and soft keys, and when a displayed key is selected, transmits the position information to CPU 100. Therefore, it can be said that touch panel 200 in this case functions not only as display unit 120 in FIG. 1 but also as input unit 121.

[0024] Next, various keys and buttons operated by the user will be described. The start key 201 is used to instruct the scanner 120 to start scanning an original document. In the center of the start key 201 is a two-color LED 202, green and red, whose color indicates whether the start key 201 is ready for use. The stop key 203 is used to stop an operation that is in progress. The numeric keypad 204 is made up of number and symbol keys, and is used to set the number of copies and to instruct screen switching on the touch panel 200. The user mode key 205 is used to call up the user mode. The user mode is a mode for setting the image processing device 1.

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

[0026] In S301, the CPU 100 displays an authentication screen on the operation unit 12. A screen 200 in Fig. 4 is an example of the authentication screen. The screen in Fig. 4 includes a user name input field 401, a password input field 402, and an OK button.

[0027] In S302, CPU 100 accepts a user name and password from the user via operation unit 12. When OK 403 is pressed with a user name entered in user name input field 401 and a password entered in password input field 402, CPU 100 stores the entered user name and password in HDD 103 and proceeds to S303. Note that in addition to or instead of accepting the user name and password entered by the user, the user name and password may be read from a card.

[0028] In S303, the CPU 100 compares the user name and password registered in advance in the HDD 103 for each user with the user name and password received in S302, and determines whether they match.

[0029] If the CPU 100 determines in S304 that there is a match, the CPU 100 determines that the authentication is OK and proceeds to S306, and if it determines that there is no match, the CPU 100 proceeds to S305.

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

[0031] In S306, if the CPU 100 determines that there is a match in S304, the process proceeds to S306.

[0032] In S307, the CPU 100 allows the user to log in to the image processing device 1.

[0033] In S308, the CPU 100 stores the currently logged-in user.

[0034] In S309, the CPU 100 causes the operation unit 12 to display a screen for the logged-in user.

[0035] FIG. 5 shows a home screen for displaying an object for selecting a copy function and an object for selecting a transmission function, which are displayed when a user logs in to the image processing apparatus 1. In FIG.

[0036] The home screen includes a menu 500 and an integrated history 509 for each user.

[0037] Menu 500 displays function selection buttons (copy button 501, send button 502, fax button 503) for selecting each function, and custom buttons for calling up settings preset by the user. The custom buttons include, for example, a contract button 504, a request button 505, and a send to me button 506.

[0038] These buttons are displayed in a layout customized by the user based on information about the user who has logged in to the image processing device 1. The buttons include "my buttons" that are displayed only on the user's personal home screen, and "shared buttons" that are displayed on the home screens of other users as well.

[0039] Slider bar 507 is a bar that is operated to display buttons that cannot be displayed at once, and indicates that this menu 500 can be moved by sliding. When this slider bar is slid, an arrow is pressed, or menu 500 is flicked, CPU 100 receives the operation and calls up and displays application buttons and custom buttons registered in the next area from HDD 103.

[0040] The user name of the user currently logged in to the image processing device 1 is displayed in an area 508 in the upper right corner that displays the user name. Figure 5 shows a state in which "User A" is logged in to the image processing device 1.

[0041] The integrated history 509, which will be described in detail later, is an area in which the execution history of jobs of multiple applications executed by the image processing device 1 is automatically registered along with the job settings, and displayed as a history record in chronological order of job execution. The further down the integrated history 509 is, the older the job execution time, and the further up the job is, the more recent the job execution time. In other words, the further up the history record is displayed, the more recently executed the job is, making it easier for the user to check the history record of recently executed jobs without operating the slider bar 507.

[0042] When a user logs in to the image processing device 1, only the history of jobs previously executed by the logged-in user is displayed in the area of ​​the integrated history 509. If the user has never executed a job, or if the record in the integrated history 509 has been deleted, the display in the area of ​​the integrated history 509 becomes empty, as shown in FIG.

[0043] The subsequent display of integrated history 509 is controlled by CPU 100 based on an application for displaying the integrated history stored in HDD 103 (hereinafter referred to as the integrated history or the integrated history application). Data used in the integrated history is stored in HDD 103.

[0044] Fig. 9 is a flowchart showing the process of executing a job according to this embodiment. The process of the flowchart in Fig. 9 is realized by the CPU 100 reading a 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 S601, the CPU 100 displays a copy screen on the operation unit 12. The user sets the number of copies, monochrome / color setting, single-sided / double-sided reading setting, magnification setting, print paper setting, and the like via the copy screen. The CPU 100 stores the accepted settings in the HDD 103. FIG. 10A 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 includes an other function button 711, a setting history button 712, and a frequently used settings button 713. The color selection button 703 is a button for setting whether the document is to be scanned in color or monochrome. The magnification setting button 704 is a button for setting the magnification for scanning the document and enlarging or reducing the document image for printing. The paper selection button 705 is a button for selecting the printing paper. The finishing button 706 is a button for setting whether to sort and print from the first page in order and output without stapling, or to sort and print from the first page in order and output with stapling. The double-sided button 707 is a button for setting whether to read only one side of the document or both sides of the document. The density button 708 is a button for setting the density of the image to be printed. The document type button 709 is a button for selecting the document type: text, text / photo, or photo. The ID card copy button 710 is a button for setting an ID card copy mode in which images from the front and back of the document are read and printed side by side on the same side of a single sheet of printing paper.

[0046] The other function button 711 is a button for setting functions other than those described above (for example, a punch function, a tint block printing function, etc.). The setting history button 712 is a button for displaying the history of settings for copies executed in the past. The frequently used settings button 713 is a button for displaying a screen for pre-registering, editing, and calling up settings that the user frequently uses. The home button 714 is a button for returning to the home screen.

[0047] The setting confirmation button 702 is a button for displaying the currently set copy setting contents in a list as character strings.

[0048] On the screen of Figure 10(A), the area 701 that displays the setting values ​​and the display on each button indicate that color is set to black and white, magnification is set to 100%, paper size is set to automatic, number of copies is set to 1, and sorting is set.

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

[0050] In S602, the CPU 100 determines whether the start key 201 has been pressed.

[0051] In S603, the CPU 100 reads the settings received via the copy screen of FIG. 10A from the HDD 103, and executes the copy job in accordance with the read settings.

[0052] In S604, CPU 100 stores the settings of the executed copy job as a job execution history in HDD 103. Here, CPU 100 stores time information acquired by referring to timer 105 as the job execution history.

[0053] Fig. 12A shows an example of data stored in the memory area for the copy function of the HDD 103 in S604. As shown in the header 801 of the data table in Fig. 12A, this table records the setting values ​​of the application. The default setting values ​​for the copy function are stored in the first row, default setting 802, and the settings for the job currently executed are additionally stored in the second row, current setting 803.

[0054] Fig. 13 shows a flow for generating, on the application side, the names of buttons to be displayed in the integrated history 509. The processing of the flowchart in Fig. 13 is realized by the CPU 100 reading a program stored in the ROM 104 into the RAM 102 and executing it. This flowchart is executed when job execution is completed in S604 in Fig. 6.

[0055] 6, after the job is completed in S604, in S901, the CPU 100 acquires the data of the integrated history 509 stored in the HDD 103. Fig. 14(A) is a data table saved for the integrated history 509. As shown in the header 1001 of the data table, a button ID, an application ID, and a data type are stored. Also stored is data on setting values ​​set by the application, or the status type of the device itself or an individual job detected by the application, date and time, and setting values ​​or text data on the occurrence status.

[0056] The button ID is an ID for uniquely identifying a history registered in the integrated history 509. The application ID is an ID for identifying by which application the job registered in the integrated history 509 was executed. This application ID is predetermined for each application, such as "100" for the management app of the device itself, "101" for copy, or "201" for send.

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

[0058] The data is the job setting data executed by the application. For example, in a copy application, it contains all the functions and setting values ​​set in the application, such as the number of copies, color, paper size, etc.

[0059] The display text consists of the date and time and setting values. Setting values ​​are information required for the application to manage the settings used in the job and the device status. Device statuses include 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 when there is a problem with the fax line, as in line 1006 of Figure 15(A). The status type of the job is a status type related to a specific job, such as when an error occurs in sending an email, as in line 1007 of Figure 15(B).

[0060] The formats of these various data are stored in a format that can be read by the application that registered the data. The date and time of display text is the date and time when the job was executed or when the application detected the status of the device itself or an individual job, and is text data that is displayed on the button of integrated history 509. The setting value of the display text is text data that highlights characteristic settings from among the settings of the executed job, or a characteristic message that indicates the status of the device itself or an individual job detected by the application, and is also displayed on the button of integrated history 509. The date and time and setting value text allow the user to look at integrated history 509 and recall with what settings each history is the history of a job that was executed.

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

[0062] If it is determined that the situation has not changed, then in S902, the CPU 100 compares the acquired data with the data of the job settings executed this time, and checks whether the integrated history 509 already contains history of the same setting data. The reason for comparing the data in the integrated history 509 with the setting data executed this time is to prevent overlapping of the history. If overlapping exists, the limited display area of ​​the integrated history 509 may be filled with the same settings. For a user who reuses history, a list of more settings variations provides a wider range of choices than a list of the same settings. Because there is no data to compare this time, the CPU 100 determines that the current setting data does not exist in the existing history data. If the integrated history 509 does not contain data of the same history, in S903 the CPU 100 starts processing to generate text for the setting values ​​to be displayed in the history.

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

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

[0065] Furthermore, when the process proceeds from S1107 to S1101, CPU 100 compares the setting values ​​of the currently executed job with the setting values ​​of the default settings. Specifically, CPU 100 compares the setting value items in FIG. 12A in order from left to right. In this example, CPU 100 compares the number of copies first. If the comparison reveals one or more differences, CPU 100 acquires the text of those setting values ​​in S1102. The reason for picking out differences from the default settings is that it is assumed that items whose setting values ​​the user intentionally changed are more memorable. In this case, since there is a difference in the number of copies, the setting value text that CPU 100 acquires first is two copies. Next, in S1103, CPU 100 acquires the length of the text. Because there is a limit to the number of characters that can be displayed on the buttons displayed in integrated history 509, CPU 100 checks in S1104 whether the display limit has been reached. If the CPU 100 determines that the display limit will be exceeded, no text data is added and the display text generation process ends. If the limit has not been reached, in S1105 the CPU 100 adds the read text data as text data of the setting values ​​to be displayed in the integrated history 509. If there are still setting differences, the process proceeds from S1106 to S1102, and the CPU 100 repeats the processes of S1102 to S1105. The generation of text data also ends if there are no more setting data differences before the display limit is reached. In this case, the difference is up to the double-sided setting, so text data up to "2 copies, color, double-sided" is generated. Since there are no further differences, the data up to that point becomes the setting value text data. Finally, the application ID of the application executed by the CPU 100 and the current setting data saved to the HDD 103 in S604 of FIG. 6 are saved as data1.xml. Additionally, the generated setting value text, job execution date and time text, and whether or not there is existing data are stored in the HDD 103, and in S904 the CPU 100 transmits these contents to the integrated history 509. Whether or not there is existing data is the result of the comparison in S902.

[0066] In this way, the objects that appear in the integrated history are registered.

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

[0068] In S901, the CPU 100 acquires the data of the integrated history 509 stored in the HDD 103. The data table stored for the integrated history 509 is in the state shown in FIG.

[0069] If the CPU 100 determines in S906 that the status of the image processing device 1 has changed, then 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 acquires the status type and the explanation to be displayed from the detected status type in accordance with the status explanation table shown in FIG. 19(A). The CPU 100 acquires the status type="line" (1402), status="disconnection" (1403), status type="warning" (1404) and explanation ID="MSG_ID_FAX_LINEOFF" (1405). The status type="warning" indicates that the use of the device or an application affected by it is to be stopped.

[0070] Next, the CPU 100 executes the status monitoring application, and references the correspondence table between explanation IDs and display language character strings shown in FIG. 20. Then, in step S908, the CPU 100 acquires the status TXT (1503) "Please check the fax line" according to the acquired explanation ID ("MSG_ID_FAX_LINEOFF"), in accordance with the display language of the operation unit 12. Finally, in step S909, the CPU 100 sends the acquired status type (1402) "Warning" and display character string (1503) as status TXT to the integrated history. The CPU 100 then sends these, along with the application ID, data type, status TXT, date and time TXT, and no existing data, to the integrated history as status information data "FAXLINE_ERROR.xml." As a result, the data table stored for the integrated history 509 becomes the state shown in FIG. 15A, and the screen becomes the one shown in FIG. 8A. 8A, the error record 517 is displayed above the other history records 514 to 516, with priority over them. The error record 517 also includes an icon on the left side that calls attention to the error.

[0071] Furthermore, if it is detected that the fax line is no longer disconnected, the CPU 100 generates "line" as the status type and "normal" as the status. Because the status type="line" is already in the integrated history 509, the status monitoring application determines that this is not a newly occurring situation, and in S910 the CPU 100 requests the integrated history 509 to delete the information. Then, in S911, it determines whether the situation has been resolved. If, in determination S911, a situation other than the status type="normal" has not been resolved, processing is performed in S908 similar to that for the occurrence of a new situation described above. As a result, status information for the new situation is displayed in the integrated history 509. Because the status type corresponding to the current status type="line" and status="normal" is "normal," the CPU 100 determines in S911 that the situation has been resolved, and terminates the processing. As a result, the status display in the integrated history 509 disappears.

[0072] The above description has been given of the case where the CPU 100 detects a disconnection of the line, but the same operation also applies when an application that submits a job detects a state that requires notification to the user.

[0073] For example, suppose a copy application is instructed to execute a job with staple settings that will exceed the maximum number of sheets that can be stapled by the device. Since the operation when a user executes a copy job has already been described, here we will only explain the operation when a situation arises that requires the user to be notified regarding the execution of the copy job.

[0074] First, the copy application reads the document placed by the user under set conditions and calculates the total number of sheets to be output. In this example, it is assumed that the copy application determines that the total number of output sheets has exceeded the upper limit of the number of sheets that can be stapled. According to this situation, the copy application generates a status type="execute", a status="number of staples exceeded", and a status type="warning". The status type="warning" does not stop execution but is a status type that alerts the user. As a result, in S906, the copy application executed by CPU 100 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 the status type="execute" is a newly occurred situation, the copy application obtains the status type and the explanation to be displayed from the situation type detected by the copy application according to the situation explanation table shown in FIG. 19(B). The copy application acquires the explanation ID = "MSG_ID_COPY_STAPLEOVER" (1407) with the status type = "Executed" (1409) and the state = "Number of Staples Exceeded" (1406). Next, based on the correspondence table of explanation IDs and display language strings shown in FIG. 20, the copy application acquires the status TXT = "Number of Staples Exceeded" (1505) in accordance with the acquired explanation ID = "MSG_ID_COPY_STAPLEOVER" (1504) and the display language of the operation panel (S908). Finally, in S909, the copy application sends the acquired status type = "Warning" and display string = "Number of Staples Exceeded" (1505) as the status TXT to the integrated history. Here, the copy application sends the status type and the status to the integrated history as the status information data = "STAPLEOVER.xml" together with the application ID, data type, status TXT, date and time TXT, and information that there is no existing data (S909). As a result, the data table saved for integrated history 509 becomes the state shown in Fig. 15(B), and the screen becomes as shown in Fig. 8(B). In Fig. 8(B), error record 518 has priority over the other history records 514 to 516 and is displayed above them. Also, error record 517 includes an icon indicating an error on the left side.

[0075] FIG. 17 shows a flow until the integrated history 509 receives the setting information data or the situation information data and displays the history.

[0076] In S1201, the integrated history 509 executed by the CPU 100 receives the value saved in the HDD 103 in S904 of FIG. 9 from the application executed by the CPU 100. Next, in S1202, the CPU 100 determines whether the received data is setting data. If it is determined to be setting data, then in S1203 the CPU 100 checks whether or not there is existing data. Since there is no existing data this time, in S1204 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 FIG. 14(B). If there is existing data, in S1205 the CPU 100 updates only the date.

[0077] If it is determined that the received data is not setting data, then in S1206 the CPU 100 checks whether or not there is existing data. If it is determined that there is no existing data, in S1207 the CPU 100 adds the data received from the application side to the data table of the integrated history 509. The data received from the application side is added to the data table as shown by button ID 1003 in FIG. 14(E). If there is existing data, in S1208 the CPU 100 updates only the date.

[0078] Since the screen of the operation unit 12 is still the copy screen, when the home button 714 is selected, the CPU 100 displays the home screen of FIG. 5B. As shown in FIG. 5B, the home screen of user A is displayed with the current history button 510 displayed in the integrated history 509. The current history 510 displays an application icon 511 identified from the application ID, a job execution date and time 512, and text 513 indicating the difference from the default settings. The application icon 511 is an icon for a copy job. Note that an icon for a transmission job is displayed like the history record icon 515 in FIG. 6B. This information is important information that helps the user remember what the settings were when looking at the current history 510. If the user wants to execute a job with the same settings, the user can press this history 510, and the CPU 100 will perform processing to call the application with the same settings reflected.

[0079] The flow of calling an application from the integrated history 509 will be described with reference to Fig. 18. The flowchart in Fig. 18 is implemented by the CPU 100 reading a program stored in the ROM 104 into the RAM 102 and executing it.

[0080] When the user selects a history record 510 (also called a history record or an object) in the integrated history 509 in FIG. 5B, in S1301, the history data for the selected button ID is read 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 setting data to that application. Since this 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 ​​for various settings from the received data, and displays the application screen on the operation unit 12 with the settings reflected. FIG. 10B shows the copy screen displayed with the settings of the history 510 reflected.

[0081] In this way, by using the integrated history 509, the user can call up and use the settings that have been executed once with one touch.

[0082] Next, a case where a part of the settings called from the integrated history 509 is changed and a job is executed will be described.

[0083] This time, assume that in S602, the user changes only the number of copies to five and presses the start key 201. In S603, the application running on the CPU 100 executes the job according to the settings. In S604, the CPU 100 overwrites and saves the job execution settings as shown in the second row of FIG. 12B, the current settings, as indicated by row 804. As described above, the flow in FIG. 13 then compares the data already in the integrated history 509 with the current settings. Since the current settings are not included in the existing data, a text description of the setting differences is generated in the flow in FIG. 16, and various data is sent to the integrated history 509. Then, the new settings are added in the flow in FIG. 17. FIG. 14C shows the history in which row 1003 has been newly added to the data table. FIG. 6A shows the screen in which history 514 is newly displayed in the home integrated history 509. The integrated history 509 is sorted and displayed in descending order by job execution date and time, so the history of the newly added job is added to the top of the list as shown in FIG. 6(A).

[0084] In this way, by reusing job settings that the user has used once, the user's time and effort in setting up jobs can be reduced.

[0085] If the history 510 of the first copy executed in FIG. 6A is selected and the job is executed without changing the settings, it is determined that the determination in S902 of FIG. 13 is to determine whether existing data exists in the integrated history 509. Therefore, the process of S903 for generating text is not executed. Therefore, in S905, the date and time text, information indicating the existence of an existing ID, and data indicating which button ID in the integrated history 509 it was for are sent from the application side to the integrated history 509. Since an existing ID exists, it is determined that an existing ID exists in the process of determining whether an existing ID exists in the process of saving data in the integrated history 509 in S1202 of FIG. 17, and in S1204, the CPU 100 updates and saves only the date of the data that matches the button ID in FIG. 14D.

[0086] 14(E) shows the data 1005 with the updated date. The integrated history 509 displays the history in descending order by date, so the history 516 of the copy that was just executed, as shown in FIG. 7(A), is the first in the setting history.

[0087] Next, we will explain the case where the settings of the corresponding job are called up by selecting transmission history 515 in Fig. 7(A), and the job is not executed, and the user returns to the home screen. In this case, since the job is not executed, the process of saving the settings in S604 in Fig. 9 and subsequent steps are not performed. Therefore, no particular process of updating the history data is performed, and the display remains as it is in Fig. 7(A).

[0088] Next, the flow of calling an application from the integrated history 509 will be described with reference to FIG.

[0089] It is assumed that the screen is as shown in FIG. 8(A) and the data of the integrated history 509 is as shown in FIG. 15(A).

[0090] When a user presses error record 517 in integrated history 509, integrated history 509 running on CPU 100 reads the history data for the pressed button ID=1004 from the data table of integrated history 509 stored on HDD 103, as shown in FIG. 15(A). Based on application ID=100 in the read history data, integrated history 509 determines that the target application is a status monitoring application, and in S1302, transmits status information data=“FAXLINE_ERROR.xml” to the status monitoring application. The status monitoring application running on CPU 100 then 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 touch panel 200 showing guidance for resolving the status. FIG. 21 shows the status monitoring application screen displayed to reflect the status of error record 517.

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

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

[0093] When the user presses error record 518 in integrated history 509, integrated history 509 running on CPU 100 reads the history data of the pressed button ID=1004 from the data table of integrated history 509 stored on HDD 103 and shown in FIG. 15(B). Based on application ID=101 in the read history data, integrated history 509 determines that the target application is a copy application, and in S1302 transmits status information data=“STAPLEOVER.xml” to the copy application. The copy application running on CPU 100 reads the status type and status from the received status information data=“STAPLEOVER.xml,” and in S1303 displays a screen appropriate for the status type=“execute” and status=“number of sheets to staple” on operation unit 12. FIG. 21 shows the status monitoring application screen displayed reflecting the status of error record 518.

[0094] If the copy job is suspended due to paper out, the copy application generates a status type of "running," a status of "out of paper," and a status type of "suspended" (1408), and the integrated history data becomes as shown in FIG. 15C, resulting in the display shown in FIG. 8C. In FIG. 8C, error record 519 is displayed above the other history records 514 to 516, taking priority over them. Error record 519 also includes an icon indicating an error on the left side. When the user selects this error record 519, the copy application displays a paper feed tray selection screen as shown in FIG. 11B. If the user selects a paper feed tray containing paper or refills the specified paper feed tray, the copy application determines that the paper out state has been resolved and resumes the suspended copy job. At the same time, as described above, the paper out state is resolved, and the copy application detects this change in step S907 and requests the integrated history 509 to delete the status information. Since the state has been resolved, the copy application then terminates the processing. As a result, the integrated history data becomes as shown in FIG. 14(E), the home screen becomes as shown in FIG. 7(A), and the user can see that there is no situation to be processed.

[0095] Next, registration and deletion in the menu of the integrated history 509 will be described.

[0096] When the user presses and holds a button displayed in integrated history 509, a context menu 580 for operations on the button itself is displayed, as shown in Fig. 7(B). While a long press has been used as an example of a user operation that displays context menu 580, the way to call context menu 580 is not limited to a long press, and can also be a double tap or by providing a call button. Context menu 580 includes context menus for operations on buttons in integrated history 509, such as Execute 581, Add to menu 582, and Delete 583.

[0097] If Execute 581 is selected in Fig. 7(B), CPU 100 performs the process of calling the application, as already explained using Fig. 18. If Register in Menu 582 is selected in Fig. 7(B), CPU 100 performs the process of registering the custom button as a new button in menu 500 on the left. The position of the button to be registered here may be blank in menu 500, or may be selected by the user.

[0098] When the user presses Delete 583 in Fig. 7(B), a process for deleting the selected history is executed by the CPU 100. The CPU 100 deletes the target from the data table of history order and the data table of integrated history 509 in Fig. 14, and sorts the remaining history by date and time.

[0099] If the CPU 100 determines that the selected button for history 509 is not a setting button but a status information button, then registration 582 is not displayed in the menu, and only execution 581 and deletion 583 are displayed.

[0100] Next, a case where the number of history records or error records on the integrated history 509 reaches the upper limit will be described.

[0101] When jobs with different settings are repeatedly executed and the limit on the number of records stored in the integrated history 509 is reached, the CPU 100 performs a process of deleting the oldest records in the data table. This limit is the limit of the storage area and is not necessarily the same as the limit of the display area. This is because the limit of the display area can vary depending on settings such as button size and layout, and whether scrolling is enabled using a slider bar or flick.

[0102] According to this embodiment, on a screen where a user can select a copy function or a send function, the user can check the job history in the history record and easily confirm that an error has occurred by checking the error record. Also, because the error record is given priority over the history record and is displayed above the history record, the user can easily notice an error when it occurs. Also, because the error record is displayed together with the date and time the error occurred, the user can easily check from the error record when the error occurred.

[0103] [Second embodiment] In the second embodiment, a process will be described in which the integrated history data is shared between image processing devices.

[0104] FIG. 22 shows a schematic diagram of the relationship between image processing devices.

[0105] Image processing device 1, image processing device 2, and image processing device 3 are image processing devices each having the functions explained above, and are interconnected via a LAN as shown in the figure.

[0106] 3 are also mutually linked, and a user who can be authenticated by image processing device 1 can also be authenticated as the same user by image processing device 2 and image processing device 3. Assume that image processing device 1 also functions as an authentication server.

[0107] Assume that user A is viewing FIG. 8(A) on the image processing device 1, and the integrated history data is in the state shown in FIG. 15(A). When user A logs in to the image processing device 2 in this state, if the setting for identifying users is ON in the image processing device 2, the CPU 100 of the image processing device 2 displays an authentication screen on the touch panel 200 after the main body of the image processing device 2 starts up (S301). FIG. 4 shows the authentication screen displayed on the image processing device 2. The authentication screen has areas for inputting a user name 401 and a password 402. After displaying the authentication screen, the image processing device 2 waits for input of the user name and password (S302). When the user inputs a previously registered user name and password and presses the OK button 403, the CPU 100 transmits this information to the image processing device 1. The image processing device 1 compares the user name and password stored in the HDD 103 to determine whether they match the input user name and password (S303). If the user name and password do not match, the image processing device 1 returns an authentication error to the 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 user name and password match, the CPU 100 of the image processing device 1 retrieves information associated with the user stored in the HDD 103 and transmits it to the image processing device 2 (S306). At this time, when transmitting history information data to another device, the transmission data is generated according to the flow shown in FIG. 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 confirmed whether data [i] of the history information data exists (S1802). If data [i] exists, data [i] is read (S1803) and it is confirmed whether its data type is "setting" (S1804). If the data type is "settings", the read data [i] is set to the transfer data [j] (S1805), and the read position [i] of the history information data and the write position [j] of the transmission data are advanced by one (S1806). If the data type is not "settings", the read position [i] of the history information data is advanced by one (S1807).Thereafter, it is confirmed whether data [i] corresponding to the read position [i] of the updated history information data exists (S1802), and if it is determined that data [i] to be read does not exist, it transmits the transmission data (S1808). When the image processing device 2 completes the call of the information linked to the user, the CPU 100 permits the user to log in (S307) and saves the information as the currently logged-in user in the HDD 103 of the image processing device 2 (S308). Thereafter, the CPU 100 of the image processing device 2 displays a home screen reflecting the information of the called-up logged-in user on the touch panel 200 (S309). At this point, the history information data related to user A of the image processing device 2 is as shown in FIG. 14(E), and the home screen of user A is displayed as shown in FIG. 7(A).

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

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

[0110] [Third embodiment] In the above-described embodiments, the setting data and the situation information data are managed in the same way, and are distinguished from each other by data type. In the third embodiment, an example will be shown in which all situation information data is deleted when the user logs out.

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

[0112] When a logout instruction is received, the CPU 100 first initializes the reading position [i] of the history information data and the writing position [j] of the saved data to 0 (S1901). Next, it checks whether data [i] of the history information data exists (S1902). If data [i] exists, it reads the data [i] (S1903) and checks whether its data type is "settings" (S1904). If the data type is "settings", it sets the read data [i] to saved data [j] (S1905), and advances the reading position [i] of the history information data and the writing position [j] of the saved data by one position each (S1906). If the data type is not "settings", it advances the reading position [i] of the history information data by one position each (S1907). Thereafter, it is checked whether data [i] corresponding to the read position [i] of the updated history information data exists (S1902), and if it is determined that the 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 of Figure 15(B) or Figure 15(C), data 1006 whose data type is other than setting will not be saved, and as a result, the history information data will be saved in the state of Figure 14(E).

[0113] When the user logs in again, the status managed by each application is registered in the integrated history 509. If the history information data before logout is as shown in FIG. 15(A) and the status has not changed, the application for monitoring the status of the entire device registers data similar to data 1006 as a new status that has occurred at that time, in the same way as described in the first embodiment. However, the date and time is the date and time when the new status was detected.

[0114] Also, if the history information data before logging out is as shown in Figure 15(B), the copy job has not exceeded the number of sheets to be stapled, so the copy application does not register the situation, and the history information data starts in the state shown in Figure 15(B).

[0115] According to this embodiment, all situation information data is deleted when the user logs out, so situations that the user has already confirmed do not need to be displayed again.

[0116] The object of the present invention can also be achieved by performing the following process: a storage medium storing program code for software that realizes the functions of the above-described embodiments is supplied to a system or device, and a computer (or a CPU, MPU, etc.) of the system or device reads 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 embodiments, and the program code and the storage medium storing the program code constitute the present invention. [Explanation of symbols]

[0117] 100 CPU 102 RAM 103 HDD

Claims

1. 1. An image processing apparatus that displays a home screen including a first object for displaying a setting screen for a copy function and a second object for displaying a setting screen for a scan function, a first execution means for executing a copy job using a setting value set on the setting screen of the copy function, which is displayed based on the selection of the first object; a second execution means for executing a scan job using a setting value set on the setting screen of the scan function, which is displayed based on the selection of the second object; a display control means for displaying on the home screen a third object corresponding to a history of a first copy job for which an execution instruction has been received but copying has not been completed, a fourth object corresponding to a history of a second copy job for which copying has been completed, and a fifth object corresponding to a history of a scan job for which scanning has been completed; The display control means displaying a screen on which a copy job can be executed again based on at least one setting value used in the second copy job, based on the fourth object displayed on the home screen being selected; the third object and the fourth object include icons; An image processing device characterized in that an icon included in a third object corresponding to the history of the first copy job for which an execution instruction has been received but copying has not been completed and an icon included in a fourth object corresponding to the history of the second copy job for which copying has been completed are displayed in different display modes.

2. 2. The image processing device according to claim 1, wherein the display control means displays the at least one setting value used in the second copy job based on the selection of the fourth object displayed on the home screen.

3. 2. The image processing apparatus according to claim 1, wherein the first copy job is a job that has been interrupted due to a shortage of printing paper.

4. 4. The image processing apparatus according to claim 3, wherein the display control means displays a screen relating to the feeding of paper to be used in the first copy job based on the selection of the third object.

5. 2. The image processing device according to claim 1, wherein the display control means changes the display mode by making the icons included in the third object and the icons included in the fourth object differ in whether or not they include a predetermined image.

6. The image processing device according to claim 1 , wherein the display control means displays the third object, the fourth object, and the fifth object vertically aligned in a predetermined area of ​​the home screen.

7. 2. The image processing apparatus according to claim 1, wherein the display control means displays the fourth object and the fifth object in order of job execution.

8. 2. The image processing device according to claim 1, wherein the display control means displays the third object on the home screen based on the acceptance of an instruction to execute the first copy job, and displays the fourth object on the home screen based on the acceptance of an instruction to execute the second copy job.

9. The image processing device according to claim 1 , wherein the fifth object includes an icon different from the icons included in the third object and the fourth object.

10. 2. The image processing apparatus according to claim 1, wherein the at least one setting value is a setting value for a color mode of copying.

11. 2. The image processing apparatus according to claim 1, wherein the home screen is a screen that is displayed when a predetermined object is selected on the setting screen for the copy function.

12. 1. An image processing apparatus that displays a home screen including a first object for displaying a setting screen for a copy function and a second object for displaying a setting screen for a scan function, an execution unit that executes a copy job using a setting value set on the setting screen of the copy function that is displayed based on the selection of the first object; a display control means for displaying on the home screen a third object corresponding to a history of a first copy job for which an execution instruction has been received but copying has not been completed, and a fourth object corresponding to a history of a second copy job for which copying has been completed; The display control means displaying a screen on which a copy job can be executed again based on at least one setting value used in the second copy job, based on the fourth object displayed on the home screen being selected; the third object and the fourth object include icons; An image processing device characterized in that an icon included in a third object corresponding to the history of the first copy job for which an execution instruction has been received but copying has not been completed and an icon included in a fourth object corresponding to the history of the second copy job for which copying has been completed are displayed in different display modes.

13. 1. A control method for an image processing apparatus having a display unit that displays a home screen including a first object for displaying a setting screen for a copy function and a second object for displaying a setting screen for a scan function, comprising: a first execution step of executing a copy job using setting values ​​set on the setting screen of the copy function, which is displayed based on the selection of the first object; a second execution step of executing a scan job using setting values ​​set on the setting screen of the scan function, which is displayed based on the selection of the second object; a first display control step of displaying on the home screen a third object corresponding to a history of a first copy job for which an execution instruction has been received but copying has not been completed, a fourth object corresponding to a history of a second copy job for which copying has been completed, and a fifth object corresponding to a history of a scan job for which scanning has been completed; a second display control step of displaying a screen that allows a user to execute a copy job again based on at least one setting value used in the second copy job, based on the fourth object displayed on the home screen being selected; the third object and the fourth object include icons; A control method for an image processing apparatus, characterized in that an icon included in a third object corresponding to the history of the first copy job for which an execution instruction has been received but copying has not been completed and an icon included in a fourth object corresponding to the history of the second copy job for which copying has been completed are displayed in different display modes.

14. A program for causing a computer to execute each of the means according to any one of claims 1 to 11.

Images