Image forming apparatus, print management system, control method therefor, and program

Abstract

To provide an image forming apparatus, a print management system, a control method therefor, and a program, which enable a proxy executor to reduce time and effort for executing a proxy job that requires an access right of a requester.SOLUTION: An image forming apparatus (MFP) connected to a job management server via a network, comprises: a job receiving unit for receiving data of a proxy job requested to be executed by a requester from the job management server; a job display unit for displaying information of a job included in the data of the job; a job execution unit for executing the job on the basis of selecting, by a proxy executor, information of the job displayed on the job display unit; and a user authentication unit. When the information includes authentication information of the requester of the job, the user authentication unit executes authentication of the requester on the basis of the authentication information, and if the requester is authenticated, the job execution unit controls to execute the job.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to an image forming apparatus that executes a proxy job, a print management system, and a control method and program thereof. [Background technology]

[0002] There is a system in which a user submits a print job to an image forming device in advance, and another user executes the print job on behalf of the user (Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] As teleworking becomes more common, collaboration tools that allow for business chat communication are increasingly being used to facilitate communication between telecommuters and those who are in the office. As a result, there are an increasing number of cases where telecommuters (requesters) request that members who are in the office (substitute executors) execute print jobs on their behalf. However, depending on the job settings, there may be cases where resources of the image forming apparatus (such as a personal box or a personal print counter) that require the requester's access rights are referenced when the job is executed. In contrast, the system shown in Patent Document 1 is configured so that users who can access the jobs of the requester are assigned in advance, and a proxy executor selects the requester on the image forming device. Then, upon detecting the selection of the requester, the image forming device provides a mechanism for logging in as the requester based on the authentication information of the requester, displaying a list of executable proxy jobs, and allowing the requester to select and execute the jobs with their authority. However, after selecting a requester, a procedure is required to display and select from a list of proxy jobs, and in addition, the requester remains logged in during that time, which is undesirable from a security standpoint. Therefore, an object of the present invention is to provide a mechanism that reduces the effort required for a proxy executor to execute a proxy job that requires the access right of a requester. [Means for solving the problem]

[0005] The present invention is an image forming apparatus connected to a server via a network, comprising a receiving means for receiving data of a proxy job that a client has requested to be executed from the server, a display means for displaying job information contained in the job data, and an execution means for executing the job based on a proxy executor selecting the job information displayed on the display means, and, if the information includes authentication information of a job requester, an authentication means for authenticating the requester based on the authentication information, and, if the authentication means has authenticated the requester, the execution means controls to execute the job. Effect of the Invention

[0006] According to the present invention, it is possible to reduce the effort required for a proxy executor to execute a proxy job that requires the access right of a requester. [Brief description of the drawings]

[0007] [Figure 1] A diagram showing the configuration of a print management system [Diagram 2] FIG. 1 illustrates a hardware configuration of an information processing device. [Diagram 3] FIG. 2 is a diagram showing a software configuration of the information processing device. [Figure 4] Diagram showing the hardware configuration of the MFP [Diagram 5] MFP software configuration diagram [Figure 6] Diagram showing the hardware configuration of the job management application [Figure 7] Diagram showing the software configuration of the job management application [Figure 8] Workflow ticket creation and transmission process of this embodiment [Figure 9A] Receiving and executing workflow tickets in this embodiment [Figure 9B] Receiving and executing workflow tickets in this embodiment [Figure 10A] The UI displayed on the display unit of the information processing device of this embodiment [Figure 10B] The UI displayed on the display unit of the information processing device of this embodiment [Figure 11A] The UI displayed on the display unit of the information processing device of this embodiment [Figure 11B] The UI displayed on the display unit of the information processing device of this embodiment [Figure 12A] UI displayed on the operation panel of the MFP of this embodiment [Figure 12B] UI displayed on the operation panel of the MFP of this embodiment [Figure 12C] UI displayed on the operation panel of the MFP of this embodiment [Figure 12D] UI displayed on the operation panel of the MFP of this embodiment [Figure 13A] FIG. 2 is a diagram showing a job data configuration according to the present embodiment. [Figure 13B] FIG. 2 is a diagram showing the button data configuration of the present embodiment. [Figure 14A] UI displayed on the operation panel of the MFP of this embodiment [Figure 14B] UI displayed on the operation panel of the MFP of this embodiment DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] [Embodiment 1] Hereinafter, the embodiments of the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0009] - Overall configuration of the printing management system First, the overall configuration of the system according to the present invention is shown in Fig. 1. In the print management system, an information processing device 100, an MFP 110 which is an image forming device, and a job management server 130 are connected via the Internet 10, and communicate information including print jobs between them. Here, MFP is an abbreviation for Multi-Function Peripheral. The information processing device 100 and the MFP 110 may be connected to the Internet 10 via an access point 120.

[0010] -Hardware configuration of information processing device 2 shows a hardware configuration of an information processing device 100 in the print management system. Note that the information processing device 100 in this embodiment is assumed to be a device such as a PC, a smartphone, or a tablet, but may be any other device as long as it is an information processing device capable of communicating with the Internet 10. The CPU 201 reads out a control program stored in the ROM 202 or the HDD 204 , and executes various processes for controlling the operation of the information processing device 100 . The ROM 202 stores a control program. The RAM 203 is used as a temporary storage area such as a main memory or a work area for the CPU 201 . The HDD 204 stores various data such as photographs, electronic documents, etc. The HDD 204 also stores an OS (Operating System) 350 and a collaboration application 300, which will be described later. In the case of the information processing device 100, one CPU 201 executes each process shown in the flowcharts described later, but other configurations are also possible. For example, multiple CPUs may cooperate to execute each process shown in the flowcharts described later. The input unit 205 accepts input to the information processing device 100. The input may be made by an external terminal or by an attachment to the information processing device, such as a touch panel. The display unit 206 displays various screens provided by the OS 350 and the collaboration application 300. The display unit 206 may also have a touch panel function capable of detecting a touch operation by a user. The communication unit 207 executes long distance communication using the Internet 10 . The RTC (Real Time Clock) 208 keeps track of time.

[0011] - Software configuration of information processing device 3 shows a software configuration of the information processing device 100. FIG. 3 is a functional block diagram of software implemented by the CPU 201 reading out a control program stored in the ROM 202 or HDD 204. The OS 350 is software that runs on the information processing device 100. Various applications can be installed on the information processing device 100, including a collaboration application 300, which will be described later. The OS 350 exchanges information with these applications, and changes the screen displayed on the display unit 206 according to instructions received from the applications. The OS 350 also includes a group of device drivers for controlling various hardware devices, and provides applications running on the OS with APIs for using various hardware devices. The collaboration application 300 is an application that can be used on the information processing device 100, and enables communication with others using chat. Various applications other than the collaboration application 300 can be used on the information processing device 100, but a description thereof will be omitted. (Collaboration Applications) The software configuration of the collaboration application 300 will now be described in more detail. The screen control unit 301 displays a collaboration application screen on the display unit 206. The screen control unit 301 also determines an operation instruction inputted via the input unit 205 by the user. The communication unit 302 transmits and receives data using the communication unit 207 via the OS 350 . The application storage unit 303 temporarily stores various information. The timer unit 304 measures time. The chat management unit 305 posts and receives chat messages via the communication unit 302, and manages the members participating in the chat. The plug-in management unit 306 performs functional cooperation with plug-ins for expanding the functions of collaboration applications, and displays a screen of a job setting screen display unit 703 (FIG. 7) described later on the display unit 206.

[0012] MFP hardware configuration FIG. 4 shows the hardware configuration of the MFP 110 which is an image forming apparatus in the print management system. The MFP 110 includes a CPU 3020 that executes software stored in a ROM 3030 or a large-scale storage device such as a hard disk 3110 (HD). The CPU 3020 performs overall control of each device connected to the system bus 3010 . The RAM 3040 functions as the main memory, work area, etc. for the CPU 3020 . An external input controller 3060 (PANELC) controls instruction input from various hard keys 3120 (hardkey) or a touch panel 3070 (PANEL) provided in the multifunction peripheral. A display controller 3080 (DISPC) controls the display of a display 3090 (DISPLAY) constituted by, for example, a liquid crystal display. The disk controller 3100 (DKC) controls the hard disk 3110 (HD). A network interface card 3050 (NIC) exchanges data bidirectionally with other network devices or file servers, etc., via the Internet 10 . The printer 3200 (PRINTER) is a section that prints on paper using an electrophotographic method. The printing method does not have to be an electrophotographic method. The scanner 3300 is an image reading unit for reading images printed on paper. In many cases, the scanner 3300 is equipped with an optional ADF (automatic document feeder) (not shown), and can automatically read multiple pages of a document. The hard disk 3110 (HD) may also be used as a temporary storage location for images in some cases.

[0013] MFP software configuration 5 is a block diagram showing the software configuration of the MFP 110. This software is stored in the ROM 3030 and executed by the CPU 3020. The UI processing unit 510 notifies the job control application 520, the home control unit 560, and the application 570 of an input from the external input controller 3060. Alternatively, the UI processing unit 510 controls the display on the display 3090 in response to a screen update request from the job control application 520, the home control unit 560, or the application 570. For example, the job control application 520 analyzes job information received from the job receiving unit 522, and if a screen change is required, the job display unit 523 generates screen data and requests the UI processing unit 510 to update the screen. The UI processing unit 510 displays the request on the display 3090.

[0014] The job control application 520 includes the following modules: a job request unit 521, a job receiving unit 522, a job display unit 523, and a job executing unit 524. The job control application 520 is a software module for cooperating with the job management server . The job request unit 521 communicates with the job management server 130 using the network control unit 500, and requests a workflow ticket. The workflow ticket is job data including job setting values, and may further include information other than the job setting values. The job receiving unit 522 receives a workflow ticket, which is job data, as a response to the job request unit 521 . The job display unit 523 displays job information in the workflow ticket by notifying the UI processing unit 510 of the workflow ticket received by the job receiving unit 522. At this time, if there are multiple received workflow tickets, multiple pieces of job information may be displayed. When the job execution unit 524 is notified that the job information displayed by the job display unit 523 has been selected, the job execution unit 524 notifies the printer control unit 540 that controls the printer 3200 of the job information and executes the job, or notifies the scanner control unit 550 that controls the scanner 3300 of the job information and executes the job. The network control unit 500 is a module for controlling the network I / F 3050 . The user authentication unit 530 is a module that performs user authentication according to the authentication mode. The authentication mode refers to a device authentication method that performs authentication using a user account and password stored in the HD 3110, an account linking method that uses an external authentication provider, and the like. Therefore, when a setting using the account linking method is valid, the user authentication unit 530 can also realize personalization of the MFP 110 using authentication information of the collaboration application 300. 14A and 14B (hereinafter collectively referred to as "FIG. 14"), on UI processing unit 510, and upon detection of selection of the icon, makes a screen transition request to application 570. Note that application button 1410 is a general term for application button 1411, application button 1412, and application button 1413, and the number of buttons is not limited to this. The home control unit 560 causes the UI processing unit 510 to display an icon with settings (custom button 1420) shown in FIG. 14, and provides the setting value to the application 570 when the icon is selected. Furthermore, the home control unit 560 also has a function of making a screen transition request to the application 570. Note that the custom button 1420 is a general term for the custom buttons 1421, 1422, and 1423, and the number of buttons is not limited to this. The home control unit 560 also has a timeline 1430 that causes the UI processing unit 510 to display the execution history of a job and can reproduce the job. The timeline 1430 is a general term for the timeline 1431 and the timeline 1432, and the number of buttons is not limited to this. The timeline 1430 has a notification function that displays jobs that should be executed with priority, such as reserved jobs. The application 570 is a general term for the job control application 520, the home control unit 560, and other applications. There may be a copy application having a copy function, a transmission application having a transmission function, a box application having a box function, and so on. A status line control unit 580 receives requests from the application 570, printer control unit 540, and scanner control unit 550, and requests the UI processing unit 510 to output to the status line 1450 the status of the MFP 110, the status of processing currently being performed, and the like.

[0015] Job management server hardware configuration FIG. 6 shows the hardware configuration of the job management server 130 of the print management system, but each component is similar to that in FIG. 2, so the description will be omitted. Job management server software configuration 7 shows the software configuration of the job management server 130. This is a functional block diagram of software that is realized when the CPU 601 reads out a control program stored in the ROM 602 or HDD 604. The job management application 700 is software that runs on the job management server 130, and controls jobs through communication with the information processing apparatus 100 and communication with the MFP 110. The software configuration of the job management application 700 will be described in more detail below. The communication unit 701 communicates with the information processing device 100 or the MFP 110 via a network adapter 751 . When the job setting screen display unit 703 detects a usage request from the plug-in management unit 306, it transmits information of the job setting screen 1100 (FIGS. 11A and 11B; hereinafter collectively referred to as “FIG. 11”) to be displayed on the display unit 206 via the communication unit 701. The job setting creation unit 704 creates a workflow ticket for execution by the job execution unit 524 in response to an input to the job setting screen 1100 . The job setting management section 705 stores the workflow ticket created by the job setting screen display section 703 . When a job setting transmission unit 706 receives a request for a workflow ticket from the job receiving unit 522 via the communication unit 701 , the job setting transmission unit 706 extracts a workflow ticket according to the conditions from the job setting management unit 705 and transmits it to the job receiving unit 522 . A job execution result receiving unit 707 receives the results of a job executed by the job executing unit 524, and updates the information in the job setting management unit 705 according to the received results. A chat sending unit 708 can send chat messages to the chat management unit 305. The OS 850 and the network adapter 751 are equivalent to the OS 350 and the network adapter 751, respectively, and therefore a description thereof will be omitted.

[0016] Workflow ticket sending process (job management server) Next, a workflow ticket transmission process executed by the job management application 700 will be described. 8 is a flowchart showing a process from when the information processing device 100 connects to the job management server 130 until the job management application 700 of the job management server 130 transmits a workflow ticket to the MFP 110, which is an image forming device. Each step shown in the flowchart in FIG. 8 is processed by the CPU 601 expanding a control program stored in a memory such as the ROM 602 into the RAM 603 and executing it. The client information includes user information, and the user information is set in an application (not shown) before the process starts. In addition, the collaboration application 300 is connected to the job management application 700 via the plug-in management unit 306. In S801, the job management application 700 detects that the start button 1001 for [MFP Cooperation Plug-in] has been pressed on the collaboration tool screen 1000 in FIGS. 10A and 10B (hereinafter collectively referred to as "FIG. 10"). In S802, the job management application 700 launches a job setting screen 1100 shown in FIG. (Job setting screen) The job setting screen 1100 may have setting items such as a job name 1101, a job content 1102, a deadline 1103, a job type 1104, a request destination 1105, and detailed settings 1106. In addition to "print from box", "scan and send by email", "print", "scan and save in box" and the like can be selected as the job type 1104. The request destination 1105 is set only when the job is to be executed by a proxy executor, and it is also possible not to set it when the job is executed by the user. In the detailed settings 1106, a setting value to be used when the job is executed can be set. In FIG. 11(a), the request destination 1105 is not set. On the other hand, when the request destination 1105 is set as in FIG. 11(b), the job management application 700 displays items 1110 to 1112 related to settings related to the job execution user on the job setting screen 1100. The requester authentication setting 1110 is an item for setting the execution user of the proxy job as the requester. A job execution history record setting item 1111 is an item for specifying whether or not the requester himself / herself is to be recorded as the executor of the job execution history. A job billing information update item 1112 is an item for determining whether or not the requester's own billing information is to be updated in conjunction with the execution of a job. When either the job execution history record setting item 1111 or the job accounting information update item 1112 is enabled, the job management application 700 enables the requester authentication setting 1110 in conjunction with the job execution history record setting item 1111. Note that the job execution history record setting item 1111 and the job accounting information update item 1112 are examples of items for which the requester's access rights are required, and items that are linked with the requester authentication setting 1110 are not limited to these. When the requester authentication setting 1110 is enabled, the job management application 700 displays a requester authentication setting screen 1120 (FIG. 11(c)). The requester authentication setting screen 1120 can accept input of the requester's authentication information (account 1121, password 1122). The job management application 700 sets the requester's authentication information in the workflow ticket based on detection of pressing of an [OK] button 1123. Note that if the authentication method used by the user authentication unit 530 is the account linking method and linkage with the collaboration application 300 has already been established, linked authentication information can also be set. The requester authentication setting screen 1120 sets an access token as the requester's authentication information in the workflow ticket based on detection of a linked authentication setting button 1124. In this case, it is not necessary to set the account 1121 and password 1122. When the job management application 700 detects that the workflow ticket [Create] button 1107 has been pressed, it starts the process of generating a workflow ticket.

[0017] In S803, the job management application 700 determines whether the created workflow ticket includes a proxy job. This determination is made based on whether the request destination 1105 was set when the workflow ticket was created. If it is a proxy job (YES in S803), the CPU 601 advances the process to S804, and if it is not a proxy job (NO in S803), the process advances to S807. In S804, the job management application 700 determines whether the job requires a "client login." For example, when printing document data from a storage destination dedicated to the client (box printing), the proxy executor set in the request destination 1105 does not have the access right, so the job is determined to require a "client login." If it is determined to require a "client login" (YES in S804), the CPU 601 proceeds to S805, and if it is determined to require a client login (NO in S804), the CPU 601 proceeds to S807. Note that in the case of a job in which a client login is not required and the client authentication setting 1110 is valid, the requester may be notified that the client authentication setting 1110 is not required. In S805, the job management application 700 checks whether the requester authentication setting 1110 has not been set. If it has not been set (YES in S805), the CPU 601 advances the process to S806, and if it has been set (NO in S805), the CPU 601 advances the process to S807. In S806, the job management application 700 displays a requester authentication setting screen 1120, prompts the requester to input authentication information, and accepts the requester's authentication settings. In S807, the job management application 700 creates a workflow ticket based on the setting values ​​on the job setting screen 1100. In S808, the job management application 700 stores the created workflow ticket in the job setting management unit 705 for each piece of user information. In S809, the job management application 700 determines whether the created workflow ticket includes a proxy job. This determination is made based on whether the request destination 1105 was set when the workflow ticket was created. If it is a proxy job (YES in S809), the CPU 601 proceeds to S810, and if it does not exist (NO in S809), the CPU 601 ends this process. In S810, the job management application 700 notifies the proxy executor of the proxy job by chat using the chat sending unit 708, sending a workflow ticket notification 1002, and then ends this processing.

[0018] Job control application processing (MFP) 9A and 9B (hereinafter collectively referred to as "FIG. 9") are flowcharts showing the processing performed by job control application 520 of MFP 110 from receiving a workflow ticket from job management application 700 running on job management server 130 until the execution of a job. This processing is realized by CPU 3020 of MFP 110 executing job control application 520 and CPU 601 of job management server 130 executing job management application 700. In S901, the user authentication unit 530 detects an authentication operation by the proxy performer, and puts the proxy performer into a logged-in state using the proxy performer's login information. In S902, the user authentication unit 530 notifies the job control application 520 of the change in login status. Upon receiving the notification, the job control application 520 requests a workflow ticket from the job management application 700 of the job management server 130. At this time, the MFP 110 obtains user information from the login information used in S901 and transmits it at the same time as the request. In S903, the job management application 700 of the job management server 130 determines whether a "workflow ticket not in a completed state" (described below) that is assigned to the user exists based on the user information received in S902. If it is determined that a "workflow ticket not in a completed state" exists ("Yes" in S903), the job setting transmission unit 706 transmits the corresponding workflow ticket as a response, and the process proceeds to S904. If a "workflow ticket not in a completed state" does not exist, this process ends. In S904, the job control application 520 receives the workflow ticket sent by the job management application 700 at the job receiving unit 522. When the workflow ticket includes a proxy job, the job control application 520 may request the status line control unit 580 to display a message indicating that a proxy job exists.

[0019] In S905, the job control application 520 checks the setting value of the home registration setting 1206 (FIG. 12C). The home registration setting 1206 is a setting for whether or not to register the workflow ticket of the logged-in user owned by the job control application 520 to the home. The home registration setting 1206 can be set from a setting screen 1205 that the job control application 520 displays when it detects that the setting screen display button has been pressed. The setting screen 1205 allows registration to the custom button 1420 and the timeline 1430 (FIG. 14). These are called the custom button registration setting 1207 and the timeline registration setting 1208, respectively, and the home registration setting 1206 is a general term for both. If either the custom button registration setting 1207 or the timeline registration setting 1208 is valid (if "Yes" in S905), the CPU 3020 advances the process to S906, and if neither is valid (if "No" in S905), the CPU 3020 advances the process to S907. In S906, the job control application 520 registers the workflow ticket in the home, and sends a registration request to the home control unit 560 based on the registration destination setting 1209 of its own job and the registration destination setting 1210 of the proxy job. The button data of the home control unit 560 has the configuration shown in button data 1320 in FIG. The button ID 1321 is an identifier for the button. The application ID 1322 is an identifier of the application 570 to be displayed on the home control unit 560 . The button positions 1323 are the order of the buttons on the home control unit 560. The button type 1324 includes an application button 1410, a custom button 1420, and a timeline 1430 shown in FIG. The button setting value 1325 is a valid item when the button type 1324 is the custom button 1420 or the timeline 1430, and is data that the home control unit 560 provides to the application indicated by the application ID when it detects pressing of a button. When the job control application 520 registers a workflow ticket in the home control unit 560 , the job control application 520 sets the job ID 1301 that uniquely identifies the workflow ticket in the button setting value 1325 . The icon setting 1326 indicates an icon setting to be displayed on the home control unit 560, and is registered by the application indicated by the application ID 1322. The home control unit 560 applies the same icon to the application button 1410 and the custom button 1420 of the same application 570. On the other hand, when the application 570 wants to change the state of the icon by the button setting value 1325, an alternative icon can be specified in the icon setting 1326. At this time, the home control unit 560 displays the button of the application 570 using the alternative icon registered in advance by the application 570. Note that the alternative icon managed by the home control unit 560 is not limited to one, and the application 570 may be able to select from a plurality of icons registered in advance. The job control application 520 may specify an alternative icon for a proxy job. In S907, the UI processing unit 510 displays the personalized home screen 1400. (Home screen) FIG. 14 shows an example of a form of a home screen 1400. The home screen 1400 has an application button 1410, a custom button 1420, and a timeline 1430. The application buttons 1411 to 1413 correspond to the button IDs 001 to 003. Custom button 1421 corresponds to button ID 004, and custom buttons 1422-1423 correspond to button IDs 006-007. Timeline 1431 and timeline 1432 correspond to button ID 005 and button ID 008. An alternative icon is specified for button ID 005 by job control application 520. For this reason, home control unit 560 sets an icon (substitute job icon 1435) different from button ID 006 and button ID 007, to which normal icons of job control application 520 are set, to timeline 1431 of button ID 005. Note that status line control unit 580 outputs a message indicating that a substitute job exists to status 1450 at the bottom of the screen upon receiving a request from job control application 520 in S904. Note that a configuration in which home control unit 560 makes an output request in conjunction with a notification function of timeline 1430 may be adopted. The authenticated user 1440 has the user information authenticated by the user authentication unit 530 in S901 outputted to it. The display of the authenticated user 1440 may be controlled by either the home control unit 560 or the user authentication unit 530.

[0020] In S908, the home control unit 560 detects a button press event notified from the UI processing unit 510. In S909, the home control unit 560 identifies the button ID 1321 from the detected button, and checks the button type 1324. If the button type 1324 is the application button 1410, the home control unit 560 advances the process to S910, and if the button type is the custom button 1420 or the timeline 1430, the process advances to S912. In S910, the home control unit 560 requests the UI processing unit 510 to perform a screen transition to a corresponding application based on the application ID 1322 linked to the button ID 1321. In this flowchart, it is assumed that the home control unit 560 detects the selection of the job control application 520 with the button ID 003. The UI processing unit 510 requests the job control application 520 to display a screen. The job control application 520 generates a job list screen 1200 (FIG. 12A) based on the acquired workflow ticket, and requests the UI processing unit 510 to update the screen. Here, the job list screen 1200 displays the job name 1303, job type 1304, requester 1305, and data name 1306 among the items described in the data configuration 1300 (FIG. 13A) of the job. In addition, the job ID 1301, the button ID 1321, and the job setting value 1307 may be displayed. It should be noted that items 1303 to 1308 refer to data temporarily stored in the RAM 3040 or HD 3110 based on the workflow ticket received by the job control application 520. In S911, the job control application 520 detects the selection of the job 1201, identifies the corresponding job ID 1301, makes a request for confirmation of execution of the job based on the job setting values ​​1307, and advances the process to S914. In S912, the home control unit 560 provides the button setting value 1325 to the application 570 corresponding to the application ID 1322, and requests the UI processing unit 510 to transition to that application. In this flowchart, it is assumed that the home control unit 560 selects and detects the timeline 1431 of the job control application 520. In S913, the job control application 520 acquires the job ID 1301 from the provided button setting value 1325. The job control application 520 requests confirmation of job execution with the job setting value 1307 corresponding to the job ID 1301, and advances the process to S914. In S914, the job control application 520 generates the job details screen 1202 based on the job setting values ​​1307, and sends a screen update request to the UI processing unit 510. Note that the job details screen 1202 displays some of the job information of the received workflow ticket. In S915, when the job control application 520 detects that the start button 1201 has been pressed, the job control application 520 starts job execution processing based on the job setting values ​​1307. Note that displaying the job details screen 1202 (FIG. 12B) is not essential, and the job setting values ​​1307 may include information on whether or not to display a confirmation screen, and the job control application 520 may omit this step based on that information. In S916, the job control application 520 determines whether it is a proxy job based on the requester 1305. If it is determined that it is a proxy job because the requester 1305 is other than the user (YES in S916), the process proceeds to S917. If it is determined that it is not a proxy job because the requester 1305 is the user (NO in S916), the process proceeds to S921. In S917, the job control application 520 checks whether there is any problem with the setting contents from the job setting value 1307, the requester authentication setting 1308, and the proxy job authentication setting 1211. The proxy job authentication setting 1211 is an item that can be set from the setting screen 1205, and can determine the method of controlling the requester login in the case of a proxy job. For example, if the administrator of the MFP 110 selects "make requester login mandatory", in the case of a proxy job, only jobs for which the requester authentication setting 1308 is valid can be executed, and the job execution history and billing information can be recorded and managed as the requester. On the other hand, if "follow the requester authentication setting" is selected, the requester login is executed based on the requester authentication setting 1308. Also, if "do not perform requester login for jobs not requiring requester login" is selected, and in the case of a job that does not require requester access rights, the requester login is not executed even if the requester authentication setting 1308 is valid. Therefore, if the requester authentication setting 1308 does not exist but the proxy job authentication setting 1211 is "required requester login" or the job requires requester access rights, the job control application 520 determines that there is a setting error. If this is the case ("No" in S917), the process proceeds to S930. Otherwise, it is determined that there is no setting error ("Yes" in S917), and the process proceeds to S918. In S918, the job control application 520 determines whether a requester login is required. If the requester authentication setting 1308 exists and the proxy job authentication setting is set to "require requester login" or "follow requester authentication setting" (if "Yes" in S918), it is determined that a requester login is required, and the process proceeds to S919. On the other hand, if the job does not require a requester access right, the proxy job authentication setting 1211 is set to "follow requester authentication setting", and there is no requester authentication setting 1308, it is determined that a requester login is not required. Similarly, if the job does not require a requester access right and the proxy job authentication setting 1211 is set to "do not perform requester login for jobs that do not require a requester login", it is also determined that a requester login is not required. If it is determined that a requester login is not required in this way (if "No" in S918), the process proceeds to S921. In S919, the job control application 520 provides the authentication information included in the requester authentication setting 1308 to the user authentication unit 530 and requests authentication. The user authentication unit 530 authenticates (logs in) the requester based on the authentication information and returns the authentication result to the job control application 520. In S920, the job control application 520 checks whether the authentication (login) of the requester has been successful. If the authentication (login) of the requester has been successful (YES in S920), the process proceeds to S921. If the authentication (login) of the requester has not been successful (NO in S920), the process proceeds to S930.

[0021] In S921, the job settings in the workflow ticket are notified to the printer control unit 540 that controls the printer 3200 and the scanner control unit 550 that controls the scanner 3300, and the job is executed. In S922, the job control application 520 inquires of the user authentication unit 530 as to whether the requester is currently logged in, and determines from the inquiry result whether the requester is currently logged in. If the requester is currently logged in (YES in S922), the process proceeds to S923. If the requester is not currently logged in (NO in S922), the process proceeds to S927. In S923, job control application 520 requests status line control unit 580 to display that the job being executed is a proxy job. Note that this may be displayed on the screen of job control application 520 via job display unit 523 without using status line control unit 580. In S924, the job control application 520 requests the user authentication unit 530 to cancel authentication (log out) of the requester. In S925, the user authentication unit 530 returns the state to the state immediately before the login state in response to the cancellation of authentication (logout) of the requester. In S926, the job execution unit 524 transmits an execution completion notification of the target workflow ticket to the job execution result receiving unit 707, and the job execution result receiving unit 707 changes the target workflow ticket to a completed state, and the process proceeds to S928. On the other hand, if the requester is not logged in, in S927, the job control application 520 requests the status line control unit 580 to display that a job of the authenticated user is being executed, and the process proceeds to S928.

[0022] In S928, if the home registration setting 1206 is valid (YES in S928), the job control application 520 advances the process to S929, and if it is invalid (NO in S928), the job control application 520 ends this process. In S929, the job control application 520 requests the home control unit 560 to delete the button linked to the button ID 1321 corresponding to the completed job ID 1301. The home control unit 560 deletes the custom button 1420 and timeline 1430 linked to the button ID 1321, and ends this process. A home screen 1401 is a screen after a proxy job has been executed in response to the selection and detection of a timeline 1431 from the state of the home screen 1400. The home screen 1401 is in a state where the timeline 1431 has disappeared and the status line control unit 580 is displaying a message in the status 1450 indicating that a job is being executed. On the other hand, if there is a problem with the settings or if the requester fails to log in ("No" in S917), the process proceeds to S930. In S930, the job control application 520 generates the error screen 1220 (FIG. 12D) due to an error in the requester authentication setting 1308, and sends a screen update request to the UI processing unit 510. In S931, if the job control application 520 detects that the [Notify requester] button 1222 has been pressed (if "Yes" in S931), the process proceeds to S932. If the job control application 520 detects that the [Close] button 1221 has been pressed (if "No" in S931), the process ends. In S932, the job control application 520 notifies the requester of an error due to insufficient authentication information via the collaboration application 300 (chat 1003: FIG. 10(c)). At this time, the job control application 520 requests the collaboration application 300 to attach the workflow ticket 1004 of the requester, and ends this process.

[0023] As explained above, in the present invention, the workflow ticket is displayed as a button and is selectable. Then, when the workflow ticket turned into a button is executed, the requester logs in based on the requester authentication setting 1308 provided by the collaboration application 300, and executes the proxy job. This allows the proxy executor to operate in the same procedure as other buttons, even if the job setting value requires the requester's access rights, without having to select the requester. This makes it possible to easily execute a proxy job that requires the requester's access rights, improving convenience. Furthermore, in a configuration in which a workflow ticket is registered on the home screen 1400, a proxy job can be executed immediately after authentication in the same manner as with other buttons, thereby reducing the number of operation steps. Furthermore, in the present invention, a workflow ticket can be registered as a custom button 1420 or a timeline 1430. For example, since many proxy jobs are highly important, it is possible to register them in the timeline 1430 so as not to overlook them. Furthermore, in the present invention, the appearance of the proxy job can be changed, which similarly reduces the risk of overlooking it.

[0024] Furthermore, in the present invention, it is possible to display information about the requester while a proxy job is being executed, providing an opportunity to realize after the job has been executed that a job other than the proxy job has been executed by mistake. In addition, in the present invention, the authentication setting for the proxy job can be selected. For example, in an environment where it is desired to link the job execution history and billing information to the requester, it is effective to make the requester authentication mandatory using the proxy job authentication setting. Furthermore, in the present invention, the requester's own authentication information can be easily set when creating a workflow ticket, which reduces the risk of forgetting to enter authentication information or entering the wrong information. Furthermore, in the present invention, when a job setting requires the requester's access rights when creating a workflow ticket, the requester is notified of this, thereby reducing the risk of missing an input of the requester authentication settings. In addition, in the present invention, when settings that require the requester's access rights are made, the requester authentication settings can be automatically enabled, thereby reducing the risk of missing an entry of the requester authentication settings. Furthermore, the present invention is configured to be able to notify the requester if there is a problem with the requester authentication settings. This allows the proxy executor to immediately request an immediate response from the requester even if the proxy job execution fails.

[0025] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) An image forming apparatus connected to a server via a network, a receiving means for receiving data of a proxy job requested to be executed by a requester from the server; A display means for displaying job information included in the job data; an execution means for executing the job based on a selection by an agent of the job information displayed on the display means; if said information includes authentication information of a requester of the job, authentication means for performing authentication of the requester based on said authentication information; If the authentication means is able to authenticate the requester, the execution means controls to execute the job. 1. An image forming apparatus comprising: (Configuration 2) When the authentication means has authenticated the client and the execution means has completed execution of the job, the authentication means cancels the authentication of the client. 2. The image forming apparatus according to claim 1, (Configuration 3) The display means is Display the job information either as a timeline or as custom buttons 3. The image forming apparatus according to claim 1, wherein the first and second components are arranged in a same plane. (Configuration 4) The icon of the custom button can be set 4. The image forming apparatus according to claim 3, (Configuration 5) The display means displays the status of the job. 5. The image forming apparatus according to any one of configurations 1 to 4. (Configuration 6) If the job does not require a requester access right, the requester is not authenticated. 6. The image forming apparatus according to any one of configurations 1 to 5. (Configuration 7) and a notification means for notifying the requester of an error that the authentication information is incomplete via a collaboration application when authentication of the requester is set as mandatory in the job information and authentication information of the requester does not exist. 7. The image forming apparatus according to any one of configurations 1 to 6. (Configuration 8) A print management system in which an information processing device, a server, and an image forming device are communicatively connected via a network, The server, a setting unit for setting data of a proxy job that is requested to be executed by a user of the image forming apparatus from a requester; a transmission means for transmitting job data requested by an image forming apparatus to the image forming apparatus; The image forming apparatus includes: A receiving means for receiving data of a proxy job requested to be executed by a requester from the server; A display means for displaying job information included in the job data; an execution means for executing the job based on a selection made by an agent by the job information displayed on the display means; if said information includes authentication information of a requester of the job, authentication means for performing authentication of the requester based on said authentication information; If the authentication means is able to authenticate the requester, the execution means executes the job. A print management system comprising: (Configuration 9) The setting means cooperates with the client's information processing device through a collaboration application. 9. The print management system according to configuration 8. (Configuration 10) The server, Prompt the requester for authentication information if the job requires authentication 10. The print management system according to configuration 8 or 9. (Configuration 11) The image forming apparatus includes: and a notification means for notifying the requester of an error via a collaboration application when the requester cannot be authenticated by the authentication means due to a defect in the authentication information. 11. The print management system according to any one of configurations 8 to 10. (Method 1) A method for controlling an image forming apparatus connected to a server via a network, comprising: a receiving step of receiving data of a proxy job requested to be executed by a client from the server; a display step of displaying job information included in the job data on a display means; an execution step of executing the job based on a selection by an agent of the job information displayed on the display means; if said information includes authentication information of a requester of the job, an authentication step of performing authentication of the requester based on said authentication information; If the requester is authenticated in the authentication step, the job is executed in the execution step. 2 is a control method for an image forming apparatus according to claim 1 . (Method 2) A control method for a print management system in which an information processing device, a server, and an image forming device are communicatively connected via a network, comprising: The server, a setting step of setting data of a proxy job to be executed by a requester to a user of the image forming apparatus; A transmission step is performed to transmit job data requested by the image forming apparatus to the image forming apparatus; The image forming apparatus includes: a receiving step of receiving data of a proxy job requested to be executed by a requester from the server; a display step of displaying job information included in the job data; an execution step of executing the job based on a selection made by a proxy executor of the job information displayed in the display step; if said information includes authentication information of a requester of the job, an authentication step of performing authentication of the requester based on said authentication information; If the requester is authenticated in the authentication step, the job is controlled to be executed in the execution step. A control method for a print management system. (Program 1) A program for causing a computer to execute the control method for an image forming apparatus according to the first method. [Explanation of symbols]

[0026] 100 Information processing device 110 MFP 130 Job Management Server

Claims

1. An image forming apparatus connected to a server via a network, a receiving means for receiving data of a proxy job requested to be executed by a requester from the server; A display means for displaying job information included in the job data; an execution means for executing the job based on a selection by an agent of the job information displayed on the display means; if said information includes authentication information of a requester of the job, an authentication means for performing authentication of the requester based on said authentication information; If the authentication means is able to authenticate the requester, the execution means controls to execute the job.

1. An image forming apparatus comprising:

2. When the authentication means has authenticated the client and the execution means has completed execution of the job, the authentication means cancels the authentication of the client.

2. The image forming apparatus according to claim 1,

3. The display means is Display the job information either as a timeline or as custom buttons 3. The image forming apparatus according to claim 1, wherein the first and second electrodes are arranged in a first direction.

4. The icon of the custom button can be set 4. The image forming apparatus according to claim 3.

5. The display means displays the status of the job.

3. The image forming apparatus according to claim 1, wherein the first and second electrodes are arranged in a first direction.

6. If the job does not require a requester access right, the requester is not authenticated.

3. The image forming apparatus according to claim 1, wherein the first and second ink cartridges are arranged on a first surface side.

7. and a notification means for notifying the requester of an error that the authentication information is incomplete via a collaboration application when authentication of the requester is set as mandatory in the job information and authentication information of the requester does not exist.

3. The image forming apparatus according to claim 1, wherein the first and second electrodes are arranged in a first direction.

8. A print management system in which an information processing device, a server, and an image forming device are communicatively connected via a network, The server, a setting unit for setting data of a proxy job that is requested to be executed by a user of the image forming apparatus from a requester; a transmission means for transmitting job data requested by an image forming apparatus to the image forming apparatus; The image forming apparatus includes: A receiving means for receiving data of a proxy job requested to be executed by a requester from the server; A display means for displaying job information included in the job data; an execution means for executing the job based on a selection made by an agent by the job information displayed on the display means; if said information includes authentication information of a requester of the job, an authentication means for performing authentication of the requester based on said authentication information; If the authentication means is able to authenticate the requester, the execution means executes the job. A print management system comprising:

9. The setting means cooperates with the client's information processing device through a collaboration application.

9. The print management system according to claim 8.

10. The server, Prompt the requester for authentication information if the job requires authentication 10. The print management system according to claim 8, wherein the print management system is a system for managing a print job.

11. The image forming apparatus includes: and a notification means for notifying the requester of an error via a collaboration application when the requester cannot be authenticated by the authentication means due to a defect in the authentication information.

10. The print management system according to claim 8,

12. A method for controlling an image forming apparatus connected to a server via a network, comprising: a receiving step of receiving data of a proxy job requested to be executed by a client from the server; a display step of displaying job information included in the job data on a display means; an execution step of executing the job based on a selection by an agent of the job information displayed on the display means; if said information includes authentication information of a requester of the job, an authentication step of performing authentication of the requester based on said authentication information; If the requester is authenticated in the authentication step, the job is executed in the execution step. 2 is a control method for an image forming apparatus according to claim 1 .

13. A control method for a print management system in which an information processing device, a server, and an image forming device are communicatively connected via a network, comprising: The server, a setting step of setting data of a proxy job to be executed by a requester to a user of the image forming apparatus; A transmission step is performed to transmit job data requested by the image forming apparatus to the image forming apparatus; The image forming apparatus includes: a receiving step of receiving data of a proxy job requested to be executed by a requester from the server; a display step of displaying job information included in the job data; an execution step of executing the job based on a selection made by a proxy executor of the job information displayed in the display step; if said information includes authentication information of a requester of the job, an authentication step of performing authentication of the requester based on said authentication information; If the requester is authenticated in the authentication step, the job is controlled to be executed in the execution step. A control method for a print management system.

14. A program for causing a computer to execute the method for controlling an image forming apparatus according to claim 12.

Images