Image processing device and setting history deletion control method

Abstract

To provide an image processing device or the like capable of performing deletion control of a setting history after reflecting an operation state and a setting state at the time of requesting deletion of the setting history.SOLUTION: An image processing device includes a storage unit capable of storing the setting history of a job related to image processing, and a control unit that receives a request to delete the setting history, and when receiving the request to delete the setting history, the control unit specifies the setting history to be deleted according to whether a user authentication function is enabled or disabled, and performs deletion control on the specified setting history.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an image processing device and the like. [Background technology]

[0002] 2. Description of the Related Art Some image processing devices, such as multifunction peripherals, store setting values ​​relating to the execution of jobs such as copying, faxing, or image transmission as setting history.

[0003] In recent years, attempts have been made to reduce the user's time and effort required for executing a job by utilizing stored setting history. Specifically, an image processing device displays the setting history on a display unit so that the user can select it. Upon receiving a user's selection of the setting history, the image processing device executes the job based on the setting values ​​associated with the setting history, thereby easily reproducing the job corresponding to the setting history.

[0004] Some of such image processing devices are provided with a delete operation button or the like on a display screen that displays the setting history, which accepts a request to delete the setting history. For example, Patent Document 1 discloses that an authenticated user can specify a specific operation history or all operation histories from among his or her own operation histories and operate a history delete button to control deletion of the specified operation histories from the HDD unit. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-153346 Summary of the Invention [Problem to be solved by the invention]

[0006] However, in conventional technologies such as Patent Document 1, the setting history is deleted from the memory unit all at once by operating the delete operation button, so it is not possible to control deletion while reflecting the operating status or setting state at the time of the request to delete the setting history, such as the enabled status of the user authentication function or the status in which specific settings have been applied to the setting history, such as pinning to fix the display on the display screen.

[0007] An object of the present disclosure is to provide an image processing device or the like that is capable of controlling deletion of setting history by reflecting the operating conditions and setting state at the time of a request to delete the setting history. [Means for solving the problem]

[0008] In order to solve the above problem, the image processing device of the present disclosure includes a memory unit capable of storing the setting history of a job related to image processing, and a control unit that accepts a request to delete the setting history, and when the control unit accepts a request to delete the setting history, it identifies the setting history to be deleted depending on whether a user authentication function is enabled or disabled, and performs deletion control on the identified setting history.

[0009] In addition, the setting history deletion control method according to the present disclosure includes a storage process for storing the setting history of a job related to image processing, and a control process for accepting a request to delete the setting history, and is characterized in that, when a request to delete the setting history is accepted, the control process identifies the setting history to be deleted depending on whether a user authentication function is enabled or disabled, and performs deletion control on the identified setting history. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to provide an image processing device or the like that is capable of controlling deletion of setting history by reflecting the operating status and setting state at the time of a request to delete setting history. [Brief explanation of the drawings]

[0011] [Figure 1]1 is an external perspective view of a multifunction peripheral according to a first embodiment; [Figure 2] FIG. 2 is a functional configuration diagram of the multifunction peripheral according to the first embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a data structure of a setting history according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of the data structure of a job history according to the first embodiment. [Figure 5] 1 is a flowchart illustrating a processing flow according to the first embodiment. [Figure 6] 1 is a flowchart illustrating a processing flow according to the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of operation according to the first embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of operation according to the first embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of operation according to the first embodiment. [Figure 10] FIG. 2 is a diagram illustrating an example of operation according to the first embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of operation according to the first embodiment. [Figure 12] FIG. 10 is a functional configuration diagram of a multifunction peripheral according to a second embodiment. [Figure 13] 10 is a flowchart illustrating a processing flow according to the second embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 15] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 18] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 19] FIG. 10 is a functional configuration diagram of a multifunction peripheral according to a third embodiment. [Figure 20] 10 is a flowchart illustrating a processing flow according to the third embodiment. [Figure 21] FIG. 10 is a diagram illustrating an example of operation according to the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In this disclosure, a multifunction peripheral capable of performing jobs related to copying, faxing, image transmission, etc. in a single housing will be described as one form of an image processing device. Note that the following embodiments are merely examples for explaining the present disclosure, and the technical scope of the description set forth in the claims is not limited to the following description.

[0013] [1 First Embodiment] The first embodiment is a form in which, when a request to delete a setting history is received, the setting history to be deleted is specified depending on whether the authentication function is enabled or disabled.

[0014] [1.1 Functional Configuration] The functional configuration of a multifunction peripheral 10 according to the first embodiment will be described with reference to Figs. 1 and 2. Fig. 1 is an external perspective view that schematically explains the overall configuration of the multifunction peripheral 10. Fig. 2 is a functional configuration diagram of the multifunction peripheral 10. The multifunction peripheral 10 includes a control unit 11, a display unit 13, an operation input unit 15, a communication unit 17, an image forming unit 19, an image reading unit 21, and a storage unit 23.

[0015] The control unit 11 controls the entire multifunction device 10. The control unit 11 is configured, for example, with one or more arithmetic units (CPUs (Central Processing Units) and the like). The control unit 11 realizes its functions by reading and executing various programs stored in the storage unit 23.

[0016] The display unit 13 displays various types of information to the user, etc. The display unit 13 can be configured, for example, by an LCD (Liquid Crystal Display), an organic EL (Electro-luminescence) display, or the like.

[0017] The operation input unit 15 accepts information input by a user or the like. The operation input unit 15 can be configured with hard keys (for example, a numeric keypad), buttons, etc. The operation input unit 15 can be configured as a touch panel that allows input via the display unit 13. In this case, the input method of the touch panel can be, for example, a general method such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitance method.

[0018] The communication unit 17 has a wired / wireless interface or both for communicating with other devices via a network (NW) such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, a telephone line, a fax line, etc.

[0019] Image forming unit 19 forms an image based on image data on paper as a recording medium. Image forming unit 19 feeds paper from paper feed unit 25, forms an image on the paper based on the image data, and then discharges the paper to paper discharge unit 27. Image forming unit 19 can be configured, for example, by a laser printer that uses an electrophotographic method. In this case, image forming unit 19 forms an image using toner supplied from toner cartridges (not shown) that correspond to toner colors (e.g., cyan, magenta, yellow, and black).

[0020] The image reading unit 21 generates image data by scanning and reading an original image. The image reading unit 21 can be configured as a scanner device equipped with an image sensor such as a CCD (Charge Coupled Device) or a CIS (Contact Image Sensor). There are no limitations on the configuration of the image reading unit 21, as long as it is configured to generate image data by reading a reflected light image from an original image with an image sensor.

[0021] The storage unit 23 stores various programs and various data necessary for the operation of the multifunction device 10. The storage unit 23 can be configured with a storage device such as a RAM (Random access memory), an HDD (Hard disk drive), an SSD (Solid state drive), or a ROM (Read only memory).

[0022] In the first embodiment, the memory unit 23 stores a job execution program 231, a setting history processing program 232, a user authentication program 233, a deletion target history identification program 234, and a display processing program 235, and reserves a setting value file memory area 236, a setting history memory area 237, and a job history memory area 238.

[0023] The job execution program 231 is a program that is read by the control unit 11 to perform processing for each job associated with the execution of each function, such as copying, faxing, and image data transmission. The control unit 11 that has read the job execution program 231 executes jobs by controlling the display unit 13, operation input unit 15, communication unit 17, image forming unit 19, image reading unit 21, etc., which function as job execution units. The control unit 11 that has read the job execution program 231 can execute various jobs based on the setting values ​​contained in the setting value file of the setting history.

[0024] The setting history processing program 232 is a program that the control unit 11 reads, for example, when acquiring setting values ​​related to job execution, generating a setting history, and performing various processes on the setting history. After loading the setting history processing program 232, the control unit 11 acquires setting values ​​related to job execution and generates a setting value file containing the setting values. The control unit 11 then stores the generated setting value file in the setting value file storage area 236. The control unit 11 also generates the setting history by linking the setting value file to identification information (e.g., a history ID) for identifying which job the file relates to. The control unit 11 then stores the generated setting history in the setting history storage area 237.

[0025] The user authentication program 233 is a program that is loaded by the control unit 11 in order to authenticate a user who logs in to the multifunction device 10. By loading the user authentication program 233, the control unit 11 enables the user authentication function. Note that the user authentication program 233 can be loaded automatically when the device is started up, or by providing an operation button on a system setting screen or the like for switching the user authentication function on and off, and loading the user authentication program 233 when the user operates the operation button. Here, the system setting screen is a setting screen that accepts input settings for the device settings of the multifunction device 10 (for example, operating conditions, environmental conditions, authentication user registration, etc.), and is generally a setting screen that is managed by a user with administrative authority (administrative user).

[0026] The control unit 11, which has loaded the user authentication program 233, displays a user login screen (described later) on the display unit 13. The control unit 11, for example, stores a login user name and a login password in association with each other in advance, and performs login authentication of the user by comparing the login user name and the login password entered via the user login screen. In the present disclosure, a user who has been authenticated for login may be referred to as an authenticated user. Incidentally, user login authentication can be performed not only by knowledge authentication based on the input of a login user name and a login password, but also by possession authentication using a terminal device such as a token, a key, an IC card, or a smartphone, or biometric authentication such as fingerprint authentication, palm print authentication, or face authentication.

[0027] The deletion target history identification program 234 is a program that is loaded by the control unit 11 when a delete all button displayed on a setting history display screen, which will be described later, is pressed. The control unit 11 that has loaded the deletion target history identification program 234 identifies the setting history to be deleted depending on whether the user authentication function is enabled or disabled. In the first embodiment, when the user authentication function is enabled, the control unit 11 identifies the setting history related to the job executed by the user who operated the delete all button as the setting history to be deleted. On the other hand, when the user authentication function is disabled, the control unit 11 identifies the setting history related to the job executed before the delete all button was operated as the setting history to be deleted.

[0028] The display processing program 235 is a program that the control unit 11 reads when displaying on the display unit 13 a display screen that displays a list of setting history, a setting screen that accepts input of various setting values ​​related to job execution, execution instructions, or termination instructions, a basic screen (e.g., a home screen) that displays the setting screen in a switchable manner, or a login screen for user authentication.

[0029] The setting value file storage area 236 is a storage area for storing setting value files generated by the control unit 11 that has read the setting history processing program 232. The setting values ​​include, for example, setting values ​​set by the user, such as color mode, resolution, format, and density, as well as setting values ​​such as device initial values ​​held by the device itself. The control unit 11 that has read the job execution program 231 obtains a setting value file linked to the setting history of the job to be executed from the setting value file storage area 236, and executes the job based on the setting values ​​included in the setting value file.

[0030] The setting history storage area 237 is a storage area that stores the setting history generated by the control unit 11 that has loaded the setting history processing program 232. The setting history stored in the setting history storage area 237 is loaded as needed during display processing and execution of a job based on the setting history. When the control unit 11 receives a request to delete the setting history through operation of the Delete All button, it controls the deletion of the setting history stored in the setting history storage area 237. Here, the setting history storage area 237 can also be configured to store the setting history related to jobs executed by the authenticated user and the setting history related to jobs executed by all users, including the authenticated user, in separate storage areas. In this way, by separately storing and controlling the setting history related to the authenticated user and the setting history related to all users, when the user authentication function is enabled and a command to delete the setting history is input, the setting history related to the user authentication can be directly accessed.

[0031] Here, the setting history according to the present disclosure will be described. Fig. 3(a) is a diagram illustrating an example of the data structure of the setting history stored in the setting history storage area 237. Fig. 3(b) is a diagram illustrating an example of the data structure of a setting value file linked to the setting history in Fig. 3(a).

[0032] The setting history shown in FIG. 3A includes a history ID, an execution date and time, a job type, a display setting value, and a setting value file name.

[0033] The history ID is identification information for uniquely identifying the setting history. The history ID is assigned to the generated setting history. The history ID may be a serial number, as shown in the example of Figure 3(a), or may include a specified string of characters, symbols, etc. The execution date and time indicates the date and time when the job was executed. The job type indicates the type of job executed (for example, copy job, fax job, image transmission job (e-mail, scan to SMB, etc.)). The display setting value indicates part of the setting value (content) displayed on the display screen that lists the setting history. The setting value file name is the file name of the setting value file linked to the setting history.

[0034] For example, the setting history associated with history ID "0099" represents the setting history for the job type "copy" executed at 20:20 on February 22, 2020. This job is a copy job executed based on the setting values ​​contained in the setting value file name "0099.config," and is an example in which setting values ​​(items) such as "Color mode: full color, duplex copy: single-sided to single-sided, copy density: automatic, ..." are set as display setting values ​​to be displayed on the display screen. Note that the display setting values ​​set for each history ID are merely examples, and the setting values ​​displayed on the display screen are not limited to those described in FIG. 3.

[0035] FIG. 3B shows an example of the data structure of the setting value file “0098.config” associated with the job ID “0098.” The setting value file shown in FIG. 3B can be configured as a text file or binary data that stores setting values ​​related to job execution, such as “Destination: AAA@sampleA.co.jp, BBB@sampleB.co.jp, Format: Highly Compressed PDF, Resolution: 600 × 600 dpi, Page Combination: Off, Card Scan: Off, Skip Blank Pages: On, Mixed Original: On, Original Count: Off, Test Copy: Off, Concatenated Copy: Off, Bulk Original Mode: Off, Multi-Crop Scan / Photo Crop: Off, ....” When executing a job based on the setting history, the control unit 11 executes the job related to the setting history using the setting values ​​stored in the setting value file. Furthermore, when processing related to the job is completed, the control unit 11 stores the setting values ​​used in executing the job in the setting value file.

[0036] The job history storage area 238 is a storage area that stores job execution records as job histories. Here, the job histories according to the present disclosure will be described. Fig. 4 is a diagram illustrating an example of the data structure of the job histories stored in the job history storage area 238.

[0037] The job history in the example of FIG. 4 includes a job ID, a history ID, an execution date and time, a job type, a user name, and a status.

[0038] A job ID is an identifier for uniquely identifying an executed job. A job ID is generated for each job execution. The job ID may be a serial number, as shown in the example of FIG. 4, or may include a predetermined character string, symbol, etc.

[0039] The history ID, execution date and time, and job type are the same items and have the same content as those included in the setting history described in Figure 3. The user name indicates the name of the user who executed the job. The status indicates the processing status of the job.

[0040] For example, the job history for job ID "0097" represents the job history for the job type "Fax" that was executed at 18:18 on February 22, 2020. The execution instruction for this job was input by the user name "aaaaa," and the status of this job is shown to be "Completed."

[0041] Unlike the setting history, the job history is information that records the execution history of a job, and there are no particular restrictions on when it can be generated. For example, it can be generated at any time, such as before or after the execution of a job or before or after the generation of the setting history.

[0042] [1.2 Processing flow] [1.2.1 Process flow for generating setting history] Next, a process flow according to the first embodiment will be described. Fig. 5 is a flowchart that outlines the process flow for generating a setting history by the multifunction device 10. The control unit 11 generates a setting history by reading the job execution program 231, the setting history processing program 232, etc.

[0043] The control unit 11 accepts input of job execution instructions via setting screens related to copy, fax, image transmission, etc. (Step S10). In this case, the user can input job execution instructions after making necessary settings using the setting history displayed via the home screen and setting screens corresponding to each job type.

[0044] When the control unit 11 receives the job execution instruction input, it executes the job (step S20). Note that "job execution" as used in this specification means a series of processes that are executed under the control of any job mode such as copy, fax, or image transmission, from reading the setting history or inputting setting values ​​to completing the job that started upon receiving the job execution instruction input.

[0045] When a job is executed, the control unit 11 acquires setting values ​​related to the executed job and generates a setting value file containing the setting values. The control unit 11 then stores the generated setting value file in the setting value file storage area 236. The control unit 11 also generates a setting history by linking the setting value file to identification information (history ID) for identifying which job the file relates to. The control unit 11 then stores the generated setting history in the setting history storage area 237 (step S30). Note that the generation and storage of the setting history can also be triggered by, for example, input of an instruction to execute a job, and the execution timing of the generation and storage of the setting history is not limited to the above.

[0046] After generating a job history as a job execution history, control unit 11 stores the job history in job history storage area 238 (step S40), and ends the process. Note that, although Fig. 5 illustrates an example in which the job history is generated after the setting history is generated and stored, it is of course possible to generate the job history after inputting an instruction to execute the job in step S10, simultaneously with the execution of the job in step S20, or before the setting history is generated and stored in step S30.

[0047] [1.2.2 Overall process flow for controlling deletion of setting history] Next, the overall processing flow related to the deletion control of the setting history will be explained using the flowchart in Fig. 6. The control unit 11 executes the processing explained in Fig. 6 by reading the setting history processing program 232, the user authentication program 233, the deletion target history identification program 234, the display processing program 235, etc.

[0048] First, the control unit 11 determines whether or not a display instruction for the setting history has been input by the user (step S100). The user can input the display instruction for the setting history via, for example, a home screen (described later) or an execution screen (not shown) for each job such as copy, fax, or image transmission.

[0049] If the user inputs an instruction to display the setting history, the control unit 11 displays a setting history display screen (described later) on the display unit 13 (step S100; Yes → step S110). On the other hand, if the user does not input an instruction to display the setting history, the control unit 11 continues to display the currently displayed screen (for example, the home screen) (step S100; No).

[0050] Next, the control unit 11 determines whether a request to delete the setting history has been made by operating the Delete All button provided on the setting history display screen (step S120). If it is determined that a request to delete the setting history has been made, the control unit 11 determines whether the user authentication function is enabled (step S120; Yes → step S130).

[0051] If it is determined that the user authentication function is enabled (state), the control unit 11 determines whether the user who requested the deletion of the setting history has administrator authority (step S130; Yes → step S140). If it is determined that the user who requested the deletion of the setting history does not have administrator authority, the control unit 11 identifies the setting history of the job executed by the user as the target for deletion (step S140; No → step S150). Here, the administrator authority according to the present disclosure means the authority given to the device administrator to manage and maintain the device, such as device settings (e.g., operating conditions, environmental conditions, authenticated user registration, etc.) and maintenance of the multifunction device 10 via the system setting screen.

[0052] Next, the control unit 11 displays a deletion confirmation screen on the display unit 13, asking whether or not to delete the setting history (step S170). Then, the control unit 11 controls the deletion of the setting history (step S180), and ends the process. In addition to displaying the deletion confirmation screen, other configurations are possible, such as excluding setting history that you do not want to delete from the deletion targets, or incorporating setting history that you do not want to delete into a job program. Here, the job program according to the present disclosure refers to a technology for permanently and manually storing job-related settings, and refers to a batch setting in which settings related to job processing are registered in a batch. In a use case in which a standard job is repeatedly executed, a user can call up and execute a job program to set setting values ​​related to the job in a batch, thereby reducing the number of setting steps when executing the job.

[0053] On the other hand, if it is determined that the user authentication function is invalid (step S130; No), or if it is determined that the user who made the deletion request has administrator authority (step S140; Yes), the control unit 11 identifies all setting histories of jobs executed up until the deletion request was made as targets for deletion (step S160).Then, the control unit 11 controls the deletion of the setting histories (step S180), and ends the process.

[0054] Meanwhile, when it is determined that a request to delete the setting history has not been made, the control unit 11 determines whether or not a setting history for executing a job has been selected (step S120; No→step S190).

[0055] If it is determined that a setting history for executing a job has been selected, the control unit 11 executes the job based on the selected setting history (step S190; Yes→step S20).

[0056] After executing the job based on the selected setting history, the control unit 11 generates a setting history related to the execution of the job and stores it in the setting history storage area 237 (step S30). Then, the control unit 11 generates a job history, stores it in the job history storage area 238, and ends the process. Note that the generation and storage of the setting history can also be triggered by, for example, input of an instruction to execute the job, and the execution timing of the generation and storage of the setting history is not limited to the above description.

[0057] If it is determined that the setting history for executing the job has not been selected, the control unit 11 returns the process to step S110 (step S190; No→step S110).

[0058] [1.3 Example of operation] Next, an example of operation according to the first embodiment will be described. Fig. 7 is a diagram illustrating an example of the configuration of a user login screen (authentication screen) displayed by the control unit 11 that has enabled the user authentication function by reading the user authentication program 233.

[0059] The user login screen W10 includes a login user name input box Bx10, a login password input box Bx12, an authentication destination selection button B10, an OK button B12, and a cancel button B14.

[0060] The login user name input box Bx10 is an input box that accepts input of the login user name of a user requesting to log in to the multifunction peripheral 10.

[0061] The login password input box Bx12 is an input box that accepts input of a login password associated with the login user name of a user requesting to log in to the multifunction peripheral 10.

[0062] The authentication destination selection button B10 is a button that accepts the selection of the authentication destination of the user. In the example shown in Fig. 7, the device (multifunction device 10) alone is selected as the authentication destination of the user. When the user is managed by another device such as a management server via a network (NW), it is possible to select the name of the other device or location information of the other device on the network (for example, IP address, etc.).

[0063] The OK button B12 is a button for accepting a login authentication operation by the user. The cancel button B14 is a button for accepting a cancellation of the login authentication operation by the user.

[0064] FIG. 8 is a diagram illustrating an example of the configuration of the home screen W20 that the control unit 11 displays when the login authentication by the user is successful.

[0065] The home screen W20 includes a job function etc. display area R10, a login user name display area R12, and a job function etc. display area switching button B16.

[0066] The job function etc. display area R10 is an area that collectively displays job function etc. selection buttons for selecting each job function, accepting instructions to display setting history information, etc. The job function etc. selection buttons are selection buttons having a screen configuration in which each job function and each piece of information is illustrated using shapes, letters, numbers, symbols, etc.

[0067] The job function etc. display area R10 in Figure 8 is an example configured with job function etc. selection buttons that accept selection of each job function such as a simple copy button, simple fax button, simple scan button, email button, history information button B18, external address book button, scan and save button, fax button, etc., as well as input of instructions to display the setting history.

[0068] The login user name display area R12 is a display area that displays the login user name of the user (authenticated user). In addition to the login user name, the login user name display area R12 also displays a logout button so that the user can log out of the multifunction device 10. Note that if the user authentication function is disabled or if an unauthenticated user operates the home screen W20, the login user name display area R12 is not displayed.

[0069] The job function etc. display area switching button B16 accepts an instruction input by the user when switching the display content of the job function etc. display area R10. When the user inputs an instruction to the job function etc. display area switching button B16, the control unit 11 can switch the display content of the job function etc. display area R10 by switching the job function etc. selection button.

[0070] FIG. 9 shows an example of the configuration of a setting history display screen W30 that the control unit 11 displays when the history information button B18 on the home screen W20 is pressed.

[0071] The setting history display screen W30 includes a setting history display area R14. The setting history display area R14 is a display area that displays the setting history corresponding to each job executed by the user. The setting history display area R14 includes a login user name display area R12, an All tab T10, a Copy tab T12, a Send / Save tab T14, a Delete All button B20, a Delete Individual button B22, and a Pin button B24.

[0072] The login user name display area R12 is the same as that displayed on the home screen W20 in Fig. 8. The login user name display area R12 displays the login user name of the user (authenticated user).

[0073] The All tab T10, Copy tab T12, and Send / Save tab T14 are tabs for displaying the setting history after filtering it according to the job type. Fig. 9 shows an example of displaying the setting history (history IDs "0099" to "0096", "0091") for all jobs executed by user "aaaaa" (see Figs. 3 and 4). Note that a thick underline is displayed below the selected tab to indicate that the tab is selected.

[0074] The Delete All button B20 is a button that accepts a user request to delete the setting history. When the control unit 11 detects that the user has input on the Delete All button B20, it determines that a request to delete all of the setting history has been made. When the control unit 11 detects that the user has input on the Delete All button B20, it determines whether the user who made the deletion request has administrator authority. Here, if it is determined that the user who made the deletion request does not have administrator authority, the control unit 11 identifies only the setting history of jobs executed by that user as the deletion target. Note that, if it is determined that the user who made the deletion request has administrator authority, the control unit 11 identifies all setting history of jobs executed up until the deletion request was made as the deletion target. Then, the control unit 11 controls the deletion of the setting history.

[0075] The individual deletion button B22 is a button that accepts an instruction to individually delete the displayed setting history. When the control unit 11 receives an input from the individual deletion button B22, it deletes the setting history from the setting history storage area 237.

[0076] The pin button B24 is a button that accepts an instruction input to fix the display of the setting history in the setting history display area R14. In the present disclosure, display control that fixes the display of the setting history in the display area is referred to as pinning. When the control unit 11 receives an input instruction by pressing the pin button B24, it fixes the display of the setting history in the setting history display area R14. In the present disclosure, a pinned setting for a setting history is treated as one aspect of a specific setting imposed on the setting history.

[0077] The setting history display area R14 displays the setting history of each job, including the job type, job execution date and time, and display setting values. For example, the setting history displayed at the top of the display area is an example of the setting history for a copy job executed by user "aaaaa" at 20:20 on February 22, 2020.

[0078] FIG. 10 shows an example of the configuration of the setting history display screen W40 that the control unit 11 displays when the user authentication function is disabled or when a non-authenticated user (including a state before a user to be authenticated is authenticated) presses the history information button B18 on the home screen (not shown).

[0079] The setting history display screen W40 can be configured in approximately the same manner as the setting history display screen W30 illustrated in Figure 9, but differs from the setting history display screen W30 in that the login user name display area R12 is not displayed on the setting history display screen W40.

[0080] The setting history display area R14 of the setting history display screen W40 displays the setting history (history IDs "0099" to "0090") for all executed jobs. Note that in the example of Fig. 10, only the setting history for history IDs "0099" to "0094" is displayed, but by operating the scroll bar on the right side of the screen, the setting history from history ID "0093" onwards can be displayed.

[0081] The Delete All button B20 on the setting history display screen W40 is a button that accepts a user request to delete the setting history. When the control unit 11 detects that the user has pressed the Delete All button B20, it determines that a request to delete all of the setting history has been made. When the control unit 11 detects that the user has pressed the Delete All button B20, it identifies all of the setting history of jobs that have been executed up until the deletion request was made as targets for deletion. Then, the control unit 11 controls the deletion of the setting history.

[0082] FIG. 11 shows an example of the configuration of the deletion confirmation screen W50 that the control unit 11 displays in response to a request to delete the setting history by pressing the Delete All button B20 on the setting history display screen W30. The deletion confirmation screen W50 asks the user whether or not to delete the setting history by displaying a message such as, "Do you want to delete the setting history for user 'aaaaa'?" If the user accepts the message and allows the deletion of the setting history, they press the Delete button B26. When the Delete button B26 is pressed, the control unit 11 controls the deletion of the setting history. On the other hand, if the user does not accept the deletion of the setting history, they press the Cancel button B28. When the Cancel button B28 is pressed, the control unit 11 does not control the deletion of the setting history.

[0083] As described above, according to the first embodiment, the deletion of setting history can be controlled by reflecting the operating status of the multifunction device, such as the enabled / disabled status of the authentication function, thereby enabling more flexible control of the deletion of setting history.

[0084] [2 Second Embodiment] In the second embodiment, when a user requests deletion of a setting history to which a specific setting has been applied, a deletion confirmation screen is displayed or a priority order is set for the setting history to be deleted, thereby preventing the setting history from being deleted immediately after the deletion request.

[0085] Here, the specific setting is a concept including settings, conditions, setting values, etc. that are applied to setting history that would reduce user convenience if it were uniformly deleted when a request to delete setting history is received, such as pinned settings, setting history that is frequently referenced, setting history that is recently referenced and thus attracts a lot of attention from users, setting history that has frequently changed setting values, setting history that includes special processing (for example, stapling processing) as a setting value, etc. In the second embodiment, pinned settings will be described as an example of a specific aspect of the specific setting.

[0086] [2.1 Functional Configuration] 12 is a functional configuration diagram of the multifunction device 30 according to the second embodiment. The functional configuration of the multifunction device 30 according to the second embodiment can be substantially the same as the functional configuration of the multifunction device 10 according to the first embodiment. Therefore, the same components are denoted by the same reference numerals and their description will be omitted.

[0087] The multifunction device 30 includes a control unit 11, a display unit 13, an operation input unit 15, a communication unit 17, an image forming unit 19, an image reading unit 21, and a storage unit 33.

[0088] In the second embodiment, the memory unit 33 stores a job execution program 231, a setting history processing program 232, a user authentication program 233, a deletion target history identification program 234, a display processing program 235, a pinning determination program 331, and a priority determination program 332, and reserves a setting value file memory area 236, a setting history memory area 237, and a job history memory area 238.

[0089] The pinning determination program 331 is a program that the control unit 11 loads when determining a setting history to which a pinned setting is applied as a specific setting. For example, the control unit 11 that has loaded the pinning determination program 331 can identify a setting history to which a pinned setting is applied by referring to a setting history-pinning management table (described later). The pinning determination program 331 is one aspect of a determination program that determines whether a specific setting is applied to a setting history. As described above, the specific setting is not limited to a pinned setting. In addition to pinned settings, setting history that is frequently referenced, setting history that is highly popular with users because the last reference date is recent, setting history that frequently changes setting values, and setting history that includes special processing (e.g., stapling) as a setting value can also be treated as a setting history to which a specific setting is applied. For example, to determine a setting history to which a specific setting is frequently referenced, a determination program corresponding to a specific setting value, such as a "reference count determination program," can be applied.

[0090] The priority determination program 332 is a program that the control unit 11 reads when determining the priority of setting history to be excluded from deletion targets among setting history to which pinning settings have been applied. The control unit 11 reads the priority determination program 333 and determines the priority according to settings by the user or predetermined setting conditions, and excludes setting history from deletion targets based on the determined priority.

[0091] [2.2 Processing flow] Next, the flow of processing according to the second embodiment will be described with reference to the flowchart in Fig. 13. The control unit 11 executes the processing described in Fig. 13 by reading a setting history processing program 232, a user authentication program 233, a deletion target history identification program 234, a display processing program 235, a pinning determination program 331, a priority determination program 332, etc.

[0092] Note that the processes from step S100 to step S120 explained in Fig. 6 can be the same, and therefore the explanation will be omitted here. Also, the same processes as those explained in Fig. 6 will be assigned the same step numbers, and the explanation thereof will be omitted.

[0093] The control unit 11 determines whether the user authentication function is enabled (step S130). If it is determined that the user authentication function is enabled (state), the control unit 11 determines whether the user who requested the deletion of the setting history has administrator authority (step S130; Yes → step S140). If it is determined that the user who requested the deletion of the setting history does not have administrator authority, the control unit 11 determines whether there is a setting history of a pinned user (step S140; No → step S200).

[0094] When it is determined that there is a setting history of a pinned user, the control unit 11 determines the priority of the setting history of the pinned user (step S200; Yes→step S210).

[0095] Next, if the user has set a deletion priority for a setting history other than the pinned setting history, the control unit 11 determines the deletion priority (step S220).

[0096] The control unit 11 displays a deletion execution confirmation screen on the display unit 13, asking whether or not to delete the setting history (step S170). Then, the control unit 11 controls the deletion of the setting history (step S180), and ends the process. In this case, the control unit 11 first performs the deletion process of the setting history other than the setting history to which the pinned setting has been applied, and then, based on the deletion priority, can delete the setting history determined to be deleted from the setting history to which the pinned setting has been applied (for example, the setting history to which the pinned setting has been applied, which has been referenced few times or has an old reference history, etc.).

[0097] On the other hand, if it is determined that there is no setting history of the pinned user, the control unit 11 specifies the setting history of the job executed by that user as the deletion target (step S200; No→step S150).

[0098] Next, the control unit 11 displays a deletion execution confirmation screen on the display unit 13 (step S170).Then, the control unit 11 controls the deletion of the setting history (step S180), and ends the process.

[0099] Meanwhile, if it is determined that the user authentication function is disabled (step S130; No), or if it is determined that the user who requested the deletion is a user with administrator authority (step S140; Yes), the control unit 11 determines whether there is a setting history with pinned settings (step S230).

[0100] If it is determined that there is a pinned setting history, the control unit 11 determines the priority order of the pinned setting history (step S230; Yes→step S240).

[0101] Next, if the user has set a deletion priority for a setting history other than the pinned setting history, the control unit 11 determines the deletion priority (step S260).

[0102] The control unit 11 displays a deletion execution confirmation screen on the display unit 13, asking whether or not to delete the setting history (step S170). Then, the control unit 11 controls the deletion of the setting history (step S180), and ends the process. In this case, the control unit 11 first performs the deletion process of the setting history other than the setting history to which the pinned setting has been applied, and then, based on the deletion priority, can delete the setting history determined to be deleted from the setting history to which the pinned setting has been applied (for example, the setting history to which the pinned setting has been applied, which has been referenced few times or has an old reference history, etc.).

[0103] On the other hand, if it is determined that there is no pinned setting history, all setting histories of jobs executed up until the deletion request is made are identified as deletion targets (step S230; No → step S160).Then, the control unit 11 controls the deletion of the setting history (step S180) and ends the process.

[0104] [2.3 Example of operation] Next, an operation example according to the second embodiment will be described. Fig. 14 shows a setting history display screen W30 displayed by the control unit 11 in response to pressing of the history information button B18 on the home screen W20 illustrated in Fig. 8, which is an example of a display of the setting history to which the pinned setting has been applied.

[0105] The setting history display screen W30 illustrated in Fig. 14 is an example of a display that displays the setting history related to jobs executed by a user (authenticated user) with the login user name "aaaaa." Fig. 14 shows an example in which the pinned setting has been applied to all of the setting history (history IDs "0099" to "0096" and "0091") of jobs executed by the login user name "aaaaa." When the pinned setting is applied, the pin button B24 is displayed in a darkened state.

[0106] On the other hand, Figure 15 shows an example of the configuration of the setting history display screen W40 that the control unit 11 displays when the user authentication function is disabled or when an unauthenticated user (including the state before a user to be authenticated is authenticated) presses the history information display button provided on the home screen (not shown) operated by the unauthenticated user.

[0107] The setting history display screen W40 illustrated in FIG. 15 is an example of a display that displays the setting history (history IDs "0099" to "0090") related to all executed jobs. In FIG. 15, the pinned setting is applied to the setting history (history IDs "0099" to "0096") of jobs executed by the login user name "aaaaa," and the pinned setting is not applied to other setting history. As illustrated in FIGS. 14 and 15, except when all jobs are executed by the same user, the setting history display screen results in the number of displayed items in the setting history to which specific settings, i.e., pinned settings, are applied differing before and after user authentication, in addition to the enabled / disabled state of the authentication function.

[0108] Fig. 16(a) is a diagram illustrating an example of the data structure of a setting history-pinning management table, and Fig. 16(b) is a diagram illustrating an example of the data structure of a setting value file to which pinned settings are applied.

[0109] The setting history-pinning management table is a table referenced by the control unit 11 that has read the pinning determination program 331. Fig. 16(a) shows an example in which pinning settings are applied to the setting history (history IDs "0099" to "0096", "0091") of the login user name "aaaaa." The setting history-pinning management table includes, as management items, a history ID, a setting value file, a pinning flag, and a pinning priority.

[0110] The history ID is identification information for uniquely identifying the setting history. The setting value file is the file name of the setting value file linked to the setting history. The pinned flag is a flag indicating whether or not a pinned setting has been applied to the setting history. The pinned priority indicates the priority of the setting history to be excluded from deletion targets, and is a management item referenced by the control unit 11 that has loaded the priority determination program 332. The pinned priority will be explained in the next figure.

[0111] Fig. 16(b) is the same as the setting value file "0098.config" illustrated in Fig. 3(b). Fig. 16(b) is an example in which pinned settings are applied as specific settings (values). The control unit 11 manages and updates the setting history-pinned management table illustrated in Fig. 16(a) by referring to the setting value file illustrated in Fig. 16(b).

[0112] 17 shows an example of the configuration of a pinning priority confirmation screen W60 for setting the priority of setting history to be excluded from deletion. The pinning priority confirmation screen W60 is a display screen for checking the pinning priority applied to the setting history. The pinning priority confirmation screen W60 includes a pinning priority display area R16 that displays the currently applied pinning priority, an apply button B30, a change button B32, and a cancel button B34.

[0113] The pinning priority display area R16 is a display area that displays the currently applied pinning priority. The pinning priority is displayed in descending order, starting with the setting history with the highest priority. Note that setting history with a low priority (not very useful) can be set as a deletion target by a deletion request from the user. Fig. 17 shows an example in which setting history with a priority of 5 or lower is set as a deletion target.

[0114] The apply button B30 is a button that accepts input to apply the pinning priority settings displayed in the pinning priority display area R16. The change button B32 is a button that accepts input to change the pinning priority. The cancel button B34 is a button that accepts cancellation of the application of the pinning priority settings displayed in the pinning priority display area R16.

[0115] Fig. 18 shows an example of the configuration of a pinning priority change screen W70 that the control unit 11 displays in response to pressing of the Change button B32 on the pinning priority confirmation screen W60 of Fig. 17. The pinning priority change screen W70 includes a priority change display area R18, a Reflect Reference Count button B36, a Reflect Last Reference Date button B38, an Apply button B40, and a Cancel button B42.

[0116] The priority change display area R18 displays the current priority and a pull-down button for changing the current priority. When changing the current priority, the user can change the priority of the setting history to be excluded from deletion by operating the pull-down button and specifying the changed priority that is displayed.

[0117] The Reflect Reference Count button B36 is a button for sorting the current priority based on the number of references to the setting history. The Reflect Last Reference Date button B38 is a button for sorting the current priority based on the last reference date when the setting history was referenced. The Apply button B40 is a button for accepting input for applying the changed priority. The Cancel button B42 is a button for canceling the application of the changed priority.

[0118] The changes and settings made via the pinning priority change screen W70 are reflected in the pinning priorities in the setting history-pinning priority management table illustrated in FIG. 16(a) and are referenced in the priority determination process such as steps S210 and S240 in FIG. 13.

[0119] As described above, according to the second embodiment, it is possible to control the deletion of setting history after reflecting the state in which a specific setting such as a pinned setting has been applied, thereby enabling more flexible control of the deletion of setting history.

[0120] [3 Third embodiment] The third embodiment is a form in which all stored setting histories are identified as targets for deletion when a global setting that applies to all users is enabled. Here, the global setting that applies to all users is assumed to be, for example, a setting related to restrictions on the use of setting histories (prohibiting viewing, use, or storage of setting histories, etc.) or a setting related to the application of setting histories imported from an external device (to prevent, for example, the possibility of mistakenly importing setting histories of another user), and refers to a setting in which a change in the setting affects all users who use the multifunction peripheral.

[0121] [3.1 Functional Configuration] 19 is a functional configuration diagram of the multifunction device 50 according to the third embodiment. The functional configuration of the multifunction device 50 according to the third embodiment can be substantially the same as the functional configuration of the multifunction device 10 according to the first embodiment. Therefore, the same components are denoted by the same reference numerals and their description will be omitted.

[0122] The multifunction device 50 includes a control unit 11, a display unit 13, an operation input unit 15, a communication unit 17, an image forming unit 19, an image reading unit 21, and a storage unit 53.

[0123] In the third embodiment, the memory unit 53 stores a job execution program 231, a setting history processing program 232, a user authentication program 233, a deletion target history identification program 234, a display processing program 235, and an overall setting determination program 531, and reserves a setting value file memory area 236, a setting history memory area 237, and a job history memory area 238.

[0124] The overall setting determination program 531 is a program that the control unit 11 reads when determining whether the overall settings that are applied to all users for the setting history are enabled. After reading the overall setting determination program 531, the control unit 11 determines whether the settings related to restrictions on the use of the setting history, such as prohibiting viewing, use, and storage of the setting history, and the settings related to the application of setting history imported from an external device, are enabled.

[0125] [3.2 Processing flow] Next, the flow of processing according to the third embodiment will be described with reference to the flowchart in Fig. 20. Fig. 20 is a flowchart illustrating processing for identifying all stored setting histories as targets for deletion. The control unit 11 executes the processing described in Fig. 20 by reading the overall setting determination program 531.

[0126] The processes from step S100 to step S120 described in FIG. 6 can be common, so the description thereof will be omitted here.

[0127] The control unit 11 determines whether the setting history is a change to the setting relating to the restriction of use of the setting history, such as prohibition of viewing or prohibition of use (step S300).

[0128] If the control unit 11 determines that the setting history is a change to a setting regarding restrictions on the use of the setting history, such as prohibiting viewing or use, it identifies all stored setting history as setting history to be deleted (step S300; Yes → step S160).

[0129] If the control unit 11 determines that the setting history is not a change to a setting related to restrictions on the use of the setting history, such as prohibiting viewing or use, it determines whether the change is a change to a setting related to the application of the setting history imported from an external device (step S300; No → step S310).

[0130] If the control unit 11 determines that the change is a setting change related to the application of the setting history imported from an external device, it identifies all stored setting histories as setting histories to be deleted (step S310; Yes → step S160). On the other hand, if the control unit 11 determines that the change is not a setting change related to the application of the setting history imported from an external device (step S310; No), it ends the process.

[0131] Note that the setting changes in steps S300 and S310 may not be intended to delete the setting history, and in this case, a deletion confirmation screen may be displayed on the display unit 13 to ask whether or not to delete the setting history.

[0132] Furthermore, for example, if the setting change is to return the setting history to the factory default settings, it is highly likely that the change is not intended to delete the setting history, so in this case too, it is preferable to display a deletion confirmation screen on the display unit 13 asking whether or not to delete the setting history.

[0133] As described above, according to the third embodiment, the deletion of setting history can be controlled after reflecting the state in which the global settings applied to all users are enabled, thereby enabling more flexible control of the deletion of setting history.

[0134] [4 Fourth embodiment] The fourth embodiment is an embodiment in which the timing for deleting the setting history can be set in the first to third embodiments.

[0135] It should be noted that the function settings and processing flow according to the fourth embodiment can be implemented in the same manner as in the first to third embodiments, and therefore a description thereof will be omitted here.

[0136] [4.1 Example of operation] 21(a) shows an example of the configuration of the setting history deletion timing setting screen W80. The setting history deletion timing setting screen W80 includes a selection button B44 for setting the timing for deleting the setting history, an OK button B46, and a cancel button B48.

[0137] The selection button B44 is a button that accepts selection input for the timing of deleting the setting history. Fig. 21(a) shows an example where the timing of deleting the setting history can be selected, such as "delete immediately after inputting a command to delete all," "delete when the next command to delete all is input," "delete when the setting history display screen is closed," and "delete at a set date and time."

[0138] The OK button B46 is a button that accepts an instruction to input the selection result of the selection button B44. The cancel button B48 is a button that accepts an instruction to cancel the selection result of the selection button B44.

[0139] Figure 21(b) shows an example of the configuration of a deletion confirmation screen W90 that is displayed on the home screen W20 when the timing for deleting the setting history selected in Figure 21(a) arrives, asking whether or not to delete the setting history. If the user approves the deletion of the setting history based on the confirmation message displayed on the deletion confirmation screen W90 shown in Figure 21(b), the user presses the OK button B50. On the other hand, if the user does not approve the deletion of the setting history, the user can cancel the deletion control of the setting history by pressing the Cancel button B52.

[0140] As described above, according to the fourth embodiment, it is possible to set the timing for deleting the setting history to any timing, and therefore in addition to the effects of the first to third embodiments, it is possible to perform more flexible control over the deletion of the setting history.

[0141] The present invention is not limited to the above-described embodiments, and various modifications are possible. In other words, embodiments obtained by combining technical means that are appropriately modified within the scope of the gist of the present invention are also included in the technical scope of the present invention.

[0142] Furthermore, although the above-described embodiments are described separately for the sake of convenience, they may of course be combined and executed within the scope of technical feasibility.

[0143] In addition, the programs that run on each device in the embodiments are programs that control the CPU, etc. (programs that make a computer function) so as to realize the functions of the above-described embodiments. Information handled by these devices is temporarily stored in a temporary storage device (e.g., RAM) during processing, and then stored in various storage devices such as ROMs (Read Only Memories) and HDDs, and is read, modified, and written by the CPU as needed.

[0144] Here, the recording medium for storing the program may be any of semiconductor media (e.g., ROM, non-volatile memory card, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray (registered trademark) Disc, etc.)), magnetic recording media (e.g., magnetic tape, flexible disk, etc.). Furthermore, not only are the functions of the above-described embodiments realized by executing the loaded program, but the functions of the present invention may also be realized by processing in cooperation with an operating system or other application programs, etc., based on instructions from the program.

[0145] Furthermore, when distributing the program on the market, the program can be stored on a portable recording medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the storage device of the server computer is of course included in the present invention. [Explanation of symbols]

[0146] 10, 30, 50 multifunction devices 11 Control section 13 Display section 15 Operation input section 17 Communications Department 19 Image forming unit 21 Image reading unit 23, 33, 53 storage section 25 Paper feed section 27 Paper output section 231 Job Execution Program 232 Setting history processing program 233 User Authentication Program 234 Program for identifying history to be deleted 235 Display Processing Program 236 Setting value file storage area 237 Setting history storage area 238 Job History Storage Area 331 Pinning Judgment Program 332 Priority Determination Program 531 Overall setting judgment program

Claims

1. a storage unit capable of storing job setting history; a control unit; The control unit When a request to delete the setting history is received, the image processing device identifies the setting history to be deleted based on user information linked to user authentication, and performs deletion control on the identified setting history.

2. The control unit 2. The image processing apparatus according to claim 1, wherein, when a user who has made a request to delete the setting history has administrator authority, all of the stored setting histories are specified as the deletion target.

3. The control unit 2. The image processing apparatus according to claim 1, wherein, when a specific setting is applied to the setting history, the image processing apparatus inquires of a user whether or not the setting history can be deleted before performing deletion control of the setting history.

4. 4. The image processing apparatus according to claim 3, wherein the specific settings applied to the setting history are settings set by a user.

5. further comprising a display unit capable of displaying the setting history, 5. The image processing apparatus according to claim 4, wherein the specific setting is a setting for fixing the display of the setting history on the display unit.

6. 6. The image processing apparatus according to claim 5, wherein the number of display items of the setting history for which the display of the setting history on the display unit is fixed is different before and after user authentication.

7. The control unit 6. The image processing apparatus according to claim 5, wherein, when a setting for fixing the display of the setting history on the display unit is applied to the setting history, a priority order is set for the setting history to be excluded from deletion.

8. 8. The image processing apparatus according to claim 7, wherein the priority is determined based on the number of times the setting history is referenced or the last reference date and time.

9. a storage step of storing a job setting history; a control step, In the control step, A setting history deletion control method characterized in that, when a request to delete the setting history is received, the setting history to be deleted is identified based on user information linked to user authentication, and deletion control is performed on the identified setting history.

Images