Application program and image processing device

Abstract

To provide a technique to reduce the time and effort for rewriting of a workflow definition file in an application program and an image processing apparatus that can use the workflow definition file.SOLUTION: An image processing application 22 causes a CPU 11 of a PC 1 to read out a WF file at a predetermined timing. The WF file is a file that defines a workflow indicating a series of processing including image processing, and at least one WF file can be registered in the image processing application 22. When a device defined in the read-out WF file and a default device selected in the image processing application 22 do not match each other, the image processing application 22 causes the CPU to rewrite device information indicating the device in the read-out WF file to information indicating the default device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The technical field disclosed in this specification relates to an application program executable by a computer of an information processing device, and an image processing device. [Background technology]

[0002] Conventionally, there are known application programs or image processing devices that can use a workflow definition file that defines a workflow indicating a series of processes including image processing. Patent Document 1 is an example of a document disclosing a technology related to a workflow. Patent Document 1 discloses a multifunction peripheral that stores a workflow definition file and executes a process according to a workflow described in the workflow definition file, and that accepts change conditions for the workflow definition file and edits the workflow definition file according to the change conditions. [Prior art documents] [Patent documents]

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

[0004] A workflow definition file describes information about an image processing device that is to execute a process, but a user may replace the image processing device described in the workflow definition file with a new image processing device. In that case, to enable the workflow definition file to be used on the new image processing device, it is necessary to rewrite the information about the image processing device described in the workflow definition file. This rewriting of the workflow is troublesome for the user. In particular, when there are multiple workflow definition files, the work of rewriting them one by one is troublesome for the user.

[0005] This specification discloses a technique for reducing the effort required to rewrite a workflow definition file in an application program and an image processing device that can use the workflow definition file. [Means for solving the problem]

[0006] An application program made for the purpose of solving this problem is an application program executable by a computer of an information processing device, and causes the computer to execute a read process to read out a workflow definition file at a predetermined timing, the workflow definition file being a file that defines a workflow indicating a series of processes including image processing, at least one of the workflow definition files can be registered in the application program, and further causes the computer to execute a rewrite process to rewrite information indicating the first image processing device in the workflow definition file read out in the read process to information indicating the second image processing device when a first image processing device, which is an image processing device described in the workflow definition file read out in the read process, does not match a second image processing device, which is an image processing device selected by the application program.

[0007] The application program disclosed in this specification reads an existing workflow definition file, and when a first image processing device, which is an image processing device described in the read workflow definition file, is different from a second image processing device, which is an image processing device selected by the application program, the image processing device described in the read workflow definition file is rewritten from the first image processing device to the second image processing device. In this way, when a user introduces a new image processing device, by selecting the new image processing device through the application program, the information indicating the image processing device is automatically rewritten when the workflow definition file is read. This eliminates the need for the user to edit the workflow definition file in order to use the new image processing device in the workflow.

[0008] An information processing device or image processing device incorporating the application program, a computer-readable storage medium storing the application program, and a control method for implementing the functions of the application program are also novel and useful. Effect of the Invention

[0009] The technology disclosed in this specification realizes a technology for an application program and an image processing device that can use a workflow definition file, which reduces the effort required to rewrite the workflow definition file. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a block diagram showing the electrical configuration of a PC. [Diagram 2] FIG. 1 is an explanatory diagram showing an example of a WF file. [Diagram 3] FIG. 13 is an explanatory diagram showing an example of a management screen. [Figure 4] 13 is a flowchart showing a procedure for a default change process. [Diagram 5] FIG. 11 is an explanatory diagram showing an example of a selection screen. [Figure 6] 13 is a flowchart showing a procedure for a device change process. [Figure 7] FIG. 11 is an explanatory diagram showing an example of a setting selection screen. [Figure 8] FIG. 13 is an explanatory diagram showing an example of a skill selection screen. [Figure 9] 13 is a flowchart showing a procedure for a WF selection process. [Figure 10] 2 is a block diagram showing an example of the electrical configuration of an MFP. [Figure 11] 13 is a flowchart showing a procedure for WF handling processing. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The first embodiment will be described in detail below with reference to the accompanying drawings. In this embodiment, a program executed on a personal computer (hereinafter, referred to as a "PC") will be described.

[0012] As shown in Fig. 1, the PC1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. The PC1 is an example of an information processing device, and the CPU 11 is an example of a computer. The PC1 also includes a user interface (hereinafter referred to as "user IF") 13 and a communication interface (hereinafter referred to as "communication IF") 14, which are electrically connected to the controller 10. Note that the controller 10 in Fig. 1 is a collective term for hardware and software used to control the PC1, and does not necessarily represent a single piece of hardware actually present in the PC1.

[0013] The CPU 11 executes various processes according to the programs read from the memory 12 and based on the user's operation. The memory 12 stores various programs and various data. The memory 12 is also used as a work area when various processes are executed. The buffer provided in the CPU 11 is also an example of a memory. Note that an example of the memory 12 is not limited to a ROM, RAM, HDD, etc. built into the PC 1, but may be a storage medium that can be read and written by the CPU 11, such as a recording medium such as a CD-ROM or DVD-ROM.

[0014] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting operations by the user. The user IF 13 may be a combination of a display capable of displaying information and a mouse or keyboard having an input acceptance function, or may be a touch panel having a display function and an input acceptance function.

[0015] The communication IF 14 includes hardware for communicating with an external device. The communication standards of the communication IF 14 are Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The PC 1 may include a plurality of communication IFs 14 corresponding to a plurality of communication standards. The PC 1 of this embodiment may be connectable to the Internet via the communication IFs 14, and may be able to use various cloud services via the Internet.

[0016] 1, the PC 1 of the present embodiment is connected to a multifunction peripheral (hereinafter, referred to as "MFP") 3 via a communication IF 14. The MFP 3 is a device having at least one of an image forming function and an image reading function. The MFP 3 is an example of an image processing device.

[0017] 1, an operating system (hereinafter referred to as "OS") 21 and an image processing application program (hereinafter referred to as "image processing app") 22 are stored in the memory 12 of the PC 1. The image processing app 22 is an example of an application program. The OS 21 is, for example, Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), or Android (registered trademark).

[0018] The image processing application 22 is a program capable of executing various functions such as input, conversion, and output of image data by using a device capable of executing image processing such as the MFP 3. The image processing application 22 of this embodiment is a program compatible with the MFP 3, and can cause the MFP 3 to execute image processing based on a user's instruction.

[0019] Input functions executable by the image processing application 22 include, for example, a scan function for acquiring image data by making the MFP3 or the like execute a scan, and a download function for downloading image data via the Internet. Conversion functions executable by the image processing application 22 include, for example, a format conversion function for converting the format of image data, and an editing function for image data. Output functions executable by the image processing application 22 include, for example, a print function for transmitting image data to the MFP3 or the like and causing it to be printed, an email transmission function for transmitting image data by email, an upload function for transmitting image data to a server or the like on the Internet, and a save function for saving image data in the memory 12.

[0020] The image processing application 22 accepts the selection of a default device for executing image processing by various functions based on a user's instruction, and stores information about the selected default device in the memory 12. The default device registered in the image processing application 22 is an example of a second image processing device. Note that the default device may be selectable for each function. For example, the default device for executing the scan function and the default device for executing the print function may be the same device or different devices.

[0021] The image processing application 22 of the present embodiment can use a workflow. A workflow is a series of processes to be executed by the image processing application 22, and is defined by a workflow definition file (hereinafter, referred to as a "WF file"). At least one WF file can be registered in the image processing application 22 of the present embodiment.

[0022] Each WF file describes a plurality of functions to be executed by the image processing application 22, various setting information used when executing each function, and the execution order of the functions. A series of processes executed by the image processing application 22 according to the workflow includes image processing using a device such as the MFP3. The WF file may also include information specifying a device to execute the function as setting information for the function. The device described in the WF file is an example of a first image processing device.

[0023] In the image processing application 22 of this embodiment, for example, two types of workflows are registered, and in the memory 12 of the PC 1, WF files 23 and 24 that define the respective workflows are stored as shown in Fig. 1. The WF file 23 is a WF file that defines a workflow that executes three types of functions, a scan function 23A, a conversion function 23B, and an upload function 23C, in this order, as shown in Fig. 2. Furthermore, the WF file 23 includes, as setting information for the scan function 23A, device information 231 that specifies the scan setting and the device that will execute the scan, as setting information for the conversion function 23B, information on the data format, and address information 232 of the upload destination as setting information for the upload function 23C.

[0024] The image processing application 22 can receive an instruction to execute each function or an instruction to execute a registered workflow. For example, when an instruction to execute a workflow defined in the WF file 23 is received, the image processing application 22 executes the scan function 23A, the conversion function 23B, and the upload function 23C in this order based on the description of the WF file 23. Specifically, the image processing application 22 transmits a scan command to a device specified in the device information 231, acquires image data of the scan result, converts the acquired image data into a PDF format, and then uploads the image data in the PDF format to an address specified in the address information 232.

[0025] The image processing application 22 can further receive an instruction to manage a workflow. When the image processing application 22 receives an instruction to manage a workflow, the image processing application 22 displays a management screen 50, for example, as shown in Fig. 3 on the user IF 13. The management screen 50 includes a list 51 of registered workflows, an execution instruction button 52 for receiving an instruction to execute a workflow, and a creation instruction button 53 for receiving an instruction to create a workflow.

[0026] The workflow list 51 displays the names of workflows registered in correspondence with each WF file stored in the memory 12. "Scan upload" and "Download print" in FIG. 3 are the names of workflows registered in correspondence with the WF files 23 and 24. The image processing application 22, for example, accepts the selection of a workflow in the list 51 and accepts an instruction to execute the selected workflow. The image processing application 22 also accepts an instruction to create a workflow, stores the created WF file in the memory 12, and registers it as a workflow. The image processing application 22 may also be capable of accepting an instruction to edit a registered workflow.

[0027] Next, a description will be given of the operation of the PC 1 incorporating the image processing application 22. Note that the processes in the following description and each processing step of the flowchart basically indicate the processing of the CPU 11 in accordance with instructions written in a program such as the image processing application 22.

[0028] First, the procedure of the default change process will be described with reference to the flowchart of Fig. 4. The default change process is executed by the CPU 11 of the PC 1 when an instruction to select a default device is received by the image processing application 22. The process of receiving the instruction to select a default device is an example of a device selection process. The timing at which the instruction to select a default device is received is an example of a predetermined timing. For example, when a new device is connected to the PC 1, the user can select the new device as the default device.

[0029] In the default change process, the CPU 11 acquires information on a device selected as a default device (hereinafter, referred to as a "selected device") (S101). In S101, the CPU 11 acquires, for example, identification information and capability information of the selected device. The identification information is, for example, a device name, a node name, an IP address, and a serial number, and the capability information is function setting information, for example, values ​​that can be selected as resolution, paper size, and paper type. The CPU 11 may acquire the identification information and capability information by communicating with the selected device, or may acquire them from the OS 21. Then, the CPU 11 stores the information on the selected device acquired in S101 in the memory 12, with the selected device as the default device (S102).

[0030] Next, the CPU 11 reads out all WF files registered in the image processing application 22 (S103). S103 is an example of a read process. Then, the CPU 11 determines whether or not the read WF files include a WF file that includes device information indicating a device other than the selected device (S105). Specifically, the CPU 11 determines whether or not the device information of a WF file that includes device information as setting information for the same function as the selected device indicates the selected device. If it is determined that there is no WF file that includes device information indicating a device other than the selected device (S105: NO), the CPU 11 ends the default change process.

[0031] On the other hand, if it is determined that there is a WF file including device information indicating a device other than the selected device (S105: YES), the CPU 11 displays a list of the names of the corresponding workflows on the user IF 13 (S106) and accepts a user operation. For example, if the selected device is a default device for the scan function, the CPU 11 extracts a WF file including device information other than the selected device as setting information for the scan function, and displays a list of the names of the workflows corresponding to the extracted WF file.

[0032] 5, the CPU 11 displays a selection screen 60 including a list 61 of corresponding workflows, a button 62 for accepting a user operation, and an OK button 63, and accepts a user operation. The buttons 62 include a batch change button 621 for accepting an instruction to collectively change the WF files of all the displayed workflows, an individual change button 622 for accepting an instruction to check the WF files one by one, and an unchanged button 623 for accepting an instruction not to change any of the WF files. The method selected by the batch change button 621 is an example of the first method, and the method selected by the individual change button 622 is an example of the second method. When there are multiple WF files, it is possible to select whether to collectively rewrite the corresponding workflows or to individually rewrite them, which increases the degree of freedom in rewriting and improves convenience.

[0033] The CPU 11 determines the user's selection on the displayed selection screen 60 based on which of the all change button 621, the individual change button 622, and the unchanged button 623 is selected when the operation on the OK button 63 is accepted (S108). Then, when it is determined that the unchanged button 623 is selected (S108: do not change), the CPU 11 ends the default change process.

[0034] When it is determined that the batch change button 621 has been selected (S108: batch change), the CPU 11 executes a device change process with a WF file corresponding to one of the corresponding workflows as the processing execution target (S111). The device change process is a process for rewriting the device information included in the target WF file to information indicating the selected device.

[0035] The procedure of the device change process will be described with reference to the flowchart in Fig. 6. In the device change process, the CPU 11 acquires device information included in the WF file to be executed (S201). Furthermore, the CPU 11 determines whether the acquired device information is changeable based on whether prohibition information that prohibits rewriting is added (S205).

[0036] In addition, the image processing application 22 of this embodiment can accept an instruction to add prohibition information indicating that rewriting is prohibited to each setting information included in the WF file when creating the WF file. For example, in the WF file 23 shown in Fig. 2, the upload destination address information 232 is information to which prohibition information is added and is prohibited from being rewritten. On the other hand, the setting information to which prohibition information is not added is information that is not prohibited from being rewritten.

[0037] The image processing application 22 of this embodiment can also accept instructions to export or import the created WF file. For example, the WF file created by the PC1 can be exported and imported by an image processing application of another PC, etc., so that the same workflow can be executed by a plurality of devices. When a WF file created by another user is imported, a part of the imported WF file may be rewritten and used, but rewriting is prohibited for setting information to which prohibition information was added by the creator of the WF file before exporting. Since prohibition of rewriting of setting information included in the WF file can be set, the security of the WF file is increased. Note that prohibition information that prohibits rewriting of the entire WF file, not just for each setting information, may be added.

[0038] If it is determined that changing the device information is prohibited (S205: NO), the CPU 11 does not rewrite the device information. If it is determined that the device information is changeable (S205: YES), the CPU 11 determines whether the device information indicates a device of the same model as the selected device (S207).

[0039] If it is determined that the models are not the same (S207: NO), the CPU 11 determines whether the setting values ​​described in the WF file are executable on the selected device (S210). Executable setting values ​​may differ for devices of different models. If it is determined that an inexecutable setting value is included (S210: NO), the CPU 11 notifies the user that the setting values ​​of the current WF file cannot be applied to the selected device (S211). S211 is an example of a first notification process. Furthermore, the CPU 11 accepts a user's selection of whether to change the setting values ​​(S212).

[0040] For example, if the scan settings of the WF file include a double-sided reading setting and it is determined that double-sided reading cannot be performed on the selected device, the CPU 11 causes the user IF 13 to display a setting selection screen 71 notifying the user that double-sided reading is not possible, as shown in Fig. 7. On the setting selection screen 71, the CPU 11 accepts the user's selection of whether to change the double-sided reading setting to single-sided reading or to cancel the change to the device information. By notifying the user of the setting that cannot be performed, the user can understand that if the device is changed, the processing will not be performed with the previous setting.

[0041] When it is determined that an instruction to change the setting value has been received (S212: YES), the CPU 11 rewrites the device information of the WF file to the selected device, and further rewrites the function setting value to a setting value executable by the selected device (S213). S213 is an example of a rewrite process. In the example of FIG. 7, the CPU 11 rewrites, for example, the scan setting of the WF file from double-sided reading to single-sided reading. Since an unexecutable setting is rewritten to an executable setting, it is possible to avoid an error occurring when executing the workflow defined in the WF file.

[0042] If it is determined that all the setting values ​​described in the WF file are executable (S210: YES), that is, if it is determined that the WF file does not contain any settings that cannot be executed on the selected device, the CPU 11 determines whether the capabilities will be improved by changing the device (S221). In other words, the CPU 11 determines whether there are any settings that are inexecutable on the device in the WF file but are executable on the selected device.

[0043] When it is determined that the capability will be improved (S221: YES), the CPU 11 notifies the user of information on settings that will be selectable by changing the selected device (S222). S222 is an example of a second notification process. Furthermore, the CPU 11 accepts the user's selection of whether or not to change the setting value (S223).

[0044] For example, if the reading resolution of the scan setting of the WF file is the standard resolution setting and it is determined that reading at fine resolution is possible on the selected device, the CPU 11 causes the user IF to display a capability selection screen 72 notifying that reading at fine resolution is possible, as shown in Fig. 8. On the capability selection screen 72, the CPU 11 accepts a user instruction as to whether to change the scan setting to fine resolution or to leave it at standard resolution. By notifying the user of the newly selectable settings due to the change in device, the user can understand that new settings are available.

[0045] When it is determined that an instruction to change the setting value has been received (S223: YES), the CPU 11 rewrites the device information of the WF file to information indicating the selected device, and further rewrites the setting value of the function to an executable setting value (S224). S224 is an example of a rewrite process. In the example of FIG. 8, the CPU 11 rewrites, for example, the scan setting of the WF file from standard resolution to fine resolution. Since the setting can be rewritten to a new setting in conjunction with the rewriting of the device information, the effort of rewriting the setting can be saved.

[0046] If it is determined that the capability will not be improved (S221: NO), or if it is determined that an instruction not to change the setting has been received (S223: NO), the CPU 11 rewrites the device information in the WF file to information indicating the selected device (S225). S225 is an example of a rewrite process. In S225, the CPU 11 rewrites only the device information and does not rewrite the setting.

[0047] After S213, S224, and S225, or when it is determined that changing the device information is prohibited (S205: NO), or when it is determined that the model is the same as the default device (S207: YES), or when it is determined that an instruction to cancel the change of the device information has been received (S212: NO), the CPU 11 does not rewrite the device information. The image processing application 22 of this embodiment does not rewrite the device information if the change is between devices of the same model. When the selected device selected as the default device and the device indicated by the device information in the WF file are the same model, this is an example of a case where the first image processing device and the second image processing device match.

[0048] Then, CPU 11 judges whether the WF file of interest further includes other device information (S231). Since a WF file describes information on a plurality of functions as in the example shown in FIG. 2, device information may be included for each of the plurality of functions. If it is judged that other device information is included (S231: YES), CPU 11 returns to S202 and acquires the device information. If it is judged that the device information is not included (S231: NO), CPU 11 ends the device change process and returns to the default change process.

[0049] Returning to the description of the default change process in Fig. 4, after the device change process in S111, the CPU 11 judges whether or not there is any workflow that has not been processed among the workflows displayed in the list in S106 (S112). If it is judged that there is an unprocessed workflow (S112: YES), the CPU 11 executes the device change process for that workflow. If it is judged that the processing of all the extracted workflows has been completed (S112: NO), the CPU 11 ends the default change process.

[0050] On the other hand, when the CPU 11 determines that an instruction to check the WF files one by one has been received by accepting an operation on the Individual Change button 622 on the selection screen 60 shown in Fig. 5 (S108: Individual Change), the CPU 11 displays a WF file corresponding to one of the corresponding workflows on the user IF 13 (S121). Then, the CPU 11 accepts a user instruction as to whether or not to change the device information included in the displayed WF file (S122). When the CPU 11 determines that an instruction to change the device information has been accepted (S122: YES), the CPU 11 executes the device change process described above (S123).

[0051] If the WF file displayed in S121 contains multiple pieces of device information, in S122, the CPU 11 may accept the selection of the device to be changed. In this case, the CPU 11 executes the device change process for the device selected as the device to be changed. If the WF file contains multiple pieces of device information, the user can select which device information to rewrite, thereby preventing unintended rewriting by the user.

[0052] After S123, or when it is determined that an instruction not to change the device information has been received (S122: NO), the CPU 11 determines whether or not there is an unprocessed workflow (S124). When it is determined that there is an unprocessed workflow (S124: YES), the CPU 11 returns to S121, displays the WF file, and receives a user instruction. When it is determined that the processing of all workflows has been completed (S124: NO), the CPU 11 ends the default change processing.

[0053] The image processing application 22 of this embodiment rewrites the WF file when the default device is selected, so that the rewriting to the new device can be completed before the workflow is executed. Therefore, when the workflow is executed, the processing can be performed smoothly using the default device. In addition, when there are multiple registered WF files, the image processing application 22 of this embodiment executes the device change processing for each of the multiple WF files, so that the effort of rewriting multiple WF files one by one can be saved.

[0054] Next, the procedure of the WF selection process will be described with reference to the flowchart in Fig. 9. The WF selection process is executed by the CPU 11 of the PC 1 when a management instruction for managing workflows is received, the management screen 50 shown in Fig. 3 is displayed, and then a selection instruction for selecting one of the displayed workflows is received. The process of receiving a workflow selection instruction is an example of a file selection process. The timing at which the selection of a workflow is received on the management screen is an example of a predetermined timing.

[0055] In the WF selection process, the CPU 11 first reads out the selected WF file (S301). S301 is an example of a read process. Then, the CPU 11 judges whether or not device information is described as function setting information in the read WF file (S302). If it is judged that device information is included (S302: YES), it judges whether or not the device information in the WF file is information indicating a default device of the image processing application 22 (S303). Note that if device information is included in all WF files, the judgment in S302 is not necessary, and the CPU 11 may execute the judgment in S303 after S301.

[0056] If it is determined that the device is not the default device (S303: NO), CPU 11 attempts to detect the device indicated by the device information in the WF file (S305). S305 is an example of a detection process. CPU 11 determines, for example, whether communication is possible using an IP address included in the device information. Alternatively, CPU 11 sends a detection signal to detect a device with which communication is possible, and determines whether a response signal has been received from the device indicated by the device information in the WF file. If it is determined that the device cannot be detected (S305: NO), CPU 11 notifies that execution of this workflow is impossible (S306).

[0057] After S306, or when it is determined that the device has been detected (S305: YES), the CPU 11 accepts the user's selection as to whether or not to change the workflow device to the default device (S307). The CPU 11 displays, on the user IF 13, a screen including, for example, a message indicating that the device set in the workflow is not the default device and a button for accepting the selection of whether or not to change, and accepts the user's selection. When it is determined that an instruction to change has been accepted (S307: YES), the CPU 11 acquires information on the default device (S308) and executes the device change process shown in FIG. 6 (S309).

[0058] If the device in the device information included in the WF file is not detected, it is highly likely that the device has been replaced. The image processing application 22 of this embodiment executes a device change process based on a user's instruction and rewrites the device information included in the WF file, making it possible to execute the workflow. If the device cannot be detected, the device change process may be executed without inquiring of the user.

[0059] After the device change process of S309, or if it is determined that the read WF file does not contain device information (S302: NO), or if it is determined that the device of the WF file is the default device (S303: YES), or if it is determined that an instruction not to change the device of the WF file has been received (S307: NO), the CPU 11 determines whether or not an instruction to execute the selected workflow has been received (S311). S311 is an example of an execution reception process.

[0060] When it is determined that an instruction to execute a workflow has not been received (S311: NO), the CPU 11 determines whether an instruction to end the selection of a WF file has been received (S312). When the selection of another workflow has been received or an instruction to end the management process of a workflow has been received, the CPU 11 determines that an instruction to end the selection of a WF file has been received (S312: YES) and ends the WF selection process. When the selection of another workflow has been received, the CPU 11 executes the WF selection process for the selected workflow. By receiving the selection of a WF file and making the selected WF file the target for rewriting, it is possible to eliminate the trouble of editing the WF file selected by the user.

[0061] On the other hand, if it is determined that an instruction to execute a workflow has been received (S311: YES), the CPU 11 determines whether the selected workflow is executable or not (S315). If it is determined that the workflow is executable (S315: YES), the CPU 11 executes the workflow based on the description of the WF file (S316). If it is determined that the workflow is not executable (S315: NO), the CPU 11 notifies an error (S317). For example, if the device of the WF file has not been changed from the device that could not be detected in S305, the CPU 11 determines that the workflow is not executable. After S316 or S317, the CPU 11 ends the WF selection process.

[0062] The image processing application 22 can also receive an execution instruction specifying a registered workflow, not only from the management screen 50, as with an execution instruction for each function. When an execution instruction for a workflow is received, the image processing application 22 reads out a WF file corresponding to the specified workflow, and executes S302 to S309 of the WF selection process for the read WF file. After executing the processes of S302 to S309 of the WF selection process, the image processing application 22 executes the specified workflow. The timing at which an execution instruction for a workflow is received is an example of a predetermined timing. When an execution instruction for a workflow is received, the device information of the WF file is rewritten before execution, so that the effort of editing the WF file for the workflow to be used can be eliminated.

[0063] Furthermore, the image processing application 22 may detect the device in the device information included in each WF file not only when the selection of a workflow is accepted, but also, for example, when the image processing application 22 is started, periodically, when an instruction is input from the user, etc. If the device is not detected, the image processing application 22 may execute a device change process.

[0064] As described above in detail, the image processing application 22 of this embodiment reads out the WF file of a registered workflow, and if the device indicated by the device information included in the read WF file does not match the default device selected in the image processing application 22, the device information included in the WF file is rewritten to information indicating the default device. In this way, when a user introduces a new device, the device information is automatically rewritten when the WF file is read out by selecting the new device as the default device for the image processing application 22. This can save the user the trouble of editing the WF file in order to use a new device in the workflow.

[0065] Next, the second embodiment will be described in detail with reference to the accompanying drawings. In this embodiment, a program executed in the MFP will be described.

[0066] As shown in Fig. 10, the MFP 100 of this embodiment includes a controller 110 including a CPU 111 and a memory 112. The MFP 100 is an example of an image processing device, and the CPU 111 is an example of a controller. The MFP 100 also includes a user IF 113, a communication IF 114, a printing unit 115, and a scanner 116, which are electrically connected to the controller 110. The MFP 100 can execute printing based on image data using the printing unit 115, and can also execute image reading to read an image of an original document using the scanner 116. The printing unit 115 and the scanner 116 are examples of image processing units.

[0067] The CPU 111 executes various processes according to a program read from the memory 112 and based on a user's operation. The memory 112 stores various programs and various data. The memory 112 is also used as a work area when various processes are executed. The user IF 113 includes hardware for displaying a screen for notifying the user of information, and hardware for accepting operations by the user. The communication IF 114 includes hardware for communicating with an external device. The communication IF 114 is compatible with a communication standard such as Ethernet (registered trademark), Wi-Fi (registered trademark), or USB.

[0068] 10, an OS 121 and an image processing application 122 are stored in the memory 112 of the MFP 100. The image processing application 122 is a program capable of executing a workflow. The MFP 100 can import a WF file via the communication IF 114, for example, and stores the imported WF file in the memory 112.

[0069] Memory 112 of MFP 100 in this embodiment stores WF files 123 and 124 that define a workflow including processing by image processing application 122. Similar to WF files 23 and 24 in the first embodiment described above, WF files 123 and 124 are files that define a workflow indicating a series of processes including image processing such as printing and image reading.

[0070] Next, the procedure of the WF compatible processing will be described with reference to the flowchart in Fig. 11. The WF compatible processing is executed by CPU 111 of MFP 100 upon receipt of a user instruction to select a workflow, for example, an instruction to import a WF file or an instruction to execute a registered workflow. The timing at which a user instruction to select a workflow is received is an example of a predetermined timing.

[0071] In the WF compatible processing, CPU 111 reads a target WF file (S401), and determines whether the read WF file includes device information (S402). S401 is an example of a reading process. If it is determined that device information is included (S402: YES), CPU 111 determines whether the device information indicates MFP 100 itself (S405). If it is determined that the device information does not indicate MFP 100 itself (S405: NO), CPU 111 determines whether MFP 100 itself can execute the function set in the device information (S406).

[0072] If it is determined that the command is executable (S406: YES), CPU 111 causes user IF 113 to display a message inquiring whether or not to change the device information of the WF file to information indicating MFP 100 itself (S407), and accepts a user instruction. If an instruction to change the device information is accepted (S407: YES), CPU 111 rewrites the device information of the WF file to information indicating MFP 100 itself (S411). S411 is an example of a rewrite process.

[0073] In S411, the image processing application 122 may determine whether or not the function settings are applicable, and may accept an instruction to change the settings, similar to the image processing application 22 of the PC 1. That is, in S411, the CPU 111 may inquire of the user whether or not to change the settings if the settings are not executable or the capabilities would be improved, similar to the device change process shown in Fig. 6. Then, when an instruction to change the settings is accepted, the CPU 111 may change the settings to executable settings.

[0074] In addition, in a WF file registered in a device such as the MFP 100, device information may not be added as setting information for a function to be executed by the device itself. In this case, the CPU 111 may delete the corresponding device information from the WF file in S411.

[0075] After S411, or if it is determined that the device information indicates MFP 100 itself (S405: YES), or if it is determined that the MFP 100 itself is not executable (S406: NO), or if an instruction not to change is received (S407: NO), CPU 111 determines whether or not other device information is included in the selected WF file (S413). If it is determined that it is included (S413: YES), CPU 111 returns to S405 and makes a similar determination. On the other hand, if it is determined that it is not included (S413: NO) or if it is determined that the selected WF file does not include device information (S402: NO), CPU 111 ends the WF handling process.

[0076] As described above in detail, with the image processing application 122 of the second embodiment, like the first embodiment, when a WF file is read, information indicating the device is automatically rewritten to information indicating the device itself, thereby saving the user the trouble of editing the WF file.

[0077] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can be naturally improved and modified in various ways without departing from the scope of the present invention. For example, instead of the PC1, a tablet computer or a smartphone may be used. In addition, the present invention is not limited to the MFP3, and any device capable of processing image data may be used, such as a printer dedicated to printing, a copier, a FAX machine, a scanner, a digital camera, etc. In addition, a plurality of devices may be connected to the PC1.

[0078] Furthermore, for example, the various screens shown in the figures are all examples, and the display formats, such as the wording of messages and the positions, shapes, and numbers of buttons, are not limited to the examples shown in the figures.

[0079] Furthermore, the WF file to be read is not limited to one stored in the memory 12, but may be any file that can be read by the image processing application 22. For example, there may be a WF file stored in a device other than the PC 1, such as a cloud server.

[0080] In addition, in this embodiment, the user's selection is accepted before rewriting the device information, but it may not be accepted. For example, in the default change process, the CPU 11 may proceed to S111 or S121 after S106 without accepting the selection in S108. Also, for example, in the WF selection process, the CPU 11 may not accept the selection in S307, and may not rewrite the device information if the device detection is successful, and may rewrite the device information if the device detection is unsuccessful. Also, for example, in the WF support process, the CPU 111 may not accept the selection in S407, and may rewrite the device information if the device is executable, and may not rewrite the device information if the device is not executable.

[0081] In addition, in this embodiment, when there is a difference in capability between the device of the WF file and the selected device, the user's selection as to whether or not to change the settings is accepted, but the settings may not be changed. For example, if the selected device cannot execute the settings of the WF file, the device change may be canceled. Specifically, for example, S211 to S213 of the device change process may be deleted, and if the CPU 11 determines NO in S210, the CPU 11 may proceed to S231. Also, even if the capability is improved, the settings may not be changed. Specifically, for example, S221 to S224 of the device change process may be deleted, and if the CPU 11 determines YES in S210, the CPU 11 may proceed to S225.

[0082] Also, for example, in the present embodiment, a list of WF files including device information is displayed, and a selection is accepted as to whether to change all WF files at once or to accept instructions for each WF file individually, but this is not limited thereto. For example, all device information included in each WF file may be displayed in a list, and a selection is accepted as to whether to change all devices at once or to accept instructions for each device individually. Alternatively, a selection is accepted as to whether to change all WF files including device information for each device at once or to accept instructions for each WF file.

[0083] Also, for example, if the device in the WF file and the device selected as the default device are the same model, the WF file is not rewritten, but it may be rewritten. In other words, if the device indicated by the device information in the read WF file and the device selected by the image processing application 22 are different devices of the same model, it may be determined that they do not match.

[0084] Also, for example, the MFP 100 of the second embodiment may determine whether or not rewriting of information in the WF file is prohibited. Furthermore, if the device information is not the MFP 100 itself, the MFP 100 may detect the device indicated by the device information. Then, if rewriting is prohibited or if the device is detected, the MFP 100 may not rewrite the WF file.

[0085] In addition, in any of the flowcharts disclosed in the embodiments, the order of execution of multiple processes in any of the steps can be arbitrarily changed or the processes can be executed in parallel as long as no contradiction occurs in the process content.

[0086] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]

[0087] 1 PC 11 CPU 100 MFP 111 CPU 115 Printing Unit 116 Scanner

Claims

1. An application program executable by a computer of an information processing device, The computer includes: a read process is executed at a predetermined timing to read a workflow definition file, the workflow definition file being a file that defines a workflow indicating a series of processes including image processing, and at least one workflow definition file is capable of being registered in the application program; The computer further comprises: When a first image processing device, which is an image processing device described in the workflow definition file read in the read process, does not match a second image processing device, which is an image processing device selected by the application program, executing a rewriting process for rewriting information indicating the first image processing device, in the workflow definition file read in the reading process, to information indicating the second image processing device; 1. An application program comprising:

2. 2. The application program according to claim 1, The computer includes: executing a device selection process for receiving a selection of an image processing device using a user interface of the information processing device; The computer further comprises: the timing at which the image processing device is selected by executing the device selection process is regarded as the predetermined timing, and the read process is executed; The computer further comprises: executing the rewriting process when the first image processing device described in the workflow definition file read in the reading process does not match the second image processing device selected by the application program in the device selection process.

1. An application program comprising:

3. 3. The application program according to claim 2, The computer includes: when a plurality of workflow definition files are read in the read process, it is determined for each of the read workflow definition files whether or not the first image processing device described in the workflow definition file matches the second image processing device selected by the application program in the device selection process, and the workflow definition file for which the first image processing device and the second image processing device do not match is subject to the execution of the rewrite process.

1. An application program comprising:

4. 4. The application program according to claim 3, The computer includes: when a plurality of the workflow definition files are read in the read process, it is determined for each of the read workflow definition files whether or not the first image processing device described in the workflow definition file matches the second image processing device selected by the application program by the device selection process, and when there is a workflow definition file for which the first image processing device and the second image processing device do not match, a selection is accepted, using the user interface, between a first method of collectively rewriting the plurality of the workflow definition files and a second method of individually rewriting the plurality of the workflow definition files; When the first method is selected, all of the workflow definition files read in the read process, which are not identical between the first image processing device and the second image processing device, are subject to the rewriting process; when the second method is selected, a selection of whether or not to execute the rewrite process on each of the workflow definition files for which the first image processing device and the second image processing device do not match among the plurality of workflow definition files read out in the read process is accepted using the user interface, and the workflow definition file for which the rewrite process has been selected to be executed is executed as a target for the rewrite process, and the workflow definition file for which the rewrite process has not been selected to be executed as a target for the rewrite process is not executed as a target for the rewrite process.

1. An application program comprising:

5. 2. The application program according to claim 1, The computer includes: executing an execution reception process for receiving an execution instruction of the workflow defined in the registered workflow definition file, using a user interface of the information processing device; The computer further comprises: executing the read process with the timing at which the execution instruction is received in the execution receiving process as the predetermined timing, and with the workflow definition file that defines the workflow for which the execution instruction is received in the execution receiving process as an execution target; The computer further comprises: before executing the workflow for which the execution instruction has been accepted in the execution receiving process, it is determined whether or not the first image processing device described in the workflow definition file read in the reading process matches the second image processing device selected by the application program, and if the first image processing device and the second image processing device do not match, the rewriting process is executed, and after the rewriting process is executed, the workflow is executed.

1. An application program comprising:

6. 2. The application program according to claim 1, The computer includes: executing a file selection process for accepting selection of the workflow definition file using a user interface of the information processing device; The computer further comprises: the timing when the workflow definition file is selected by executing the file selection process is regarded as the predetermined timing, and the read process is executed with the workflow definition file selected in the file selection process as the execution target; The computer further comprises: executing the rewriting process when the first image processing device described in the workflow definition file selected in the file selection process does not match the second image processing device selected by the application program.

1. An application program comprising:

7. 2. The application program according to claim 1, The computer includes: executing a detection process for attempting to detect the first image processing device described in the workflow definition file read in the read process; The computer further comprises: when the first image processing device is not detected in the detection process, it is determined whether or not the first image processing device described in the workflow definition file read in the read process matches the second image processing device selected by the application program, and when the first image processing device and the second image processing device do not match, the rewriting process is executed.

1. An application program comprising:

8. 8. The application program according to claim 1, The computer includes: when the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program, a selection of whether or not to rewrite the workflow definition file is accepted using a user interface of the information processing device, and when the selection of rewriting the workflow definition file is accepted, the rewriting process is executed, and when the selection of not rewriting the workflow definition file is accepted, the rewriting process is not executed.

1. An application program comprising:

9. 9. The application program according to claim 1, The computer includes: When the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program, The rewriting process; a first notification process for notifying, by using a user interface of the information processing device, of a setting value that becomes unexecutable by rewriting the setting value in the workflow definition file read in the read process to information that indicates the second image processing device by the rewrite process; Execute the 1. An application program comprising:

10. 10. The application program according to claim 9, The computer includes: When the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program, a rewriting process for rewriting information indicating the first image processing device in the workflow definition file read in the reading process to information indicating the second image processing device, and further rewriting the setting value that becomes inexecutable by the rewriting to information indicating the second image processing device to a setting value that is executable by the second image processing device; The first notification process; Execute the 1. An application program comprising:

11. 11. The application program according to claim 1, The computer includes: executes the rewrite process when the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program and rewriting of information indicating the image processing device is not prohibited in the workflow definition file read in the read process, and does not execute the rewrite process when rewriting of information indicating the image processing device is prohibited in the workflow definition file read in the read process.

1. An application program comprising:

12. 12. The application program according to claim 1, The computer includes: When the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program, The rewriting process; a second notification process for notifying, by using a user interface of the information processing device, of a setting value that becomes selectable by rewriting the setting value in the workflow definition file read in the read process to information indicating the second image processing device by the rewriting process; Execute the 1. An application program comprising:

13. 13. The application program according to claim 12, The computer includes: When the first image processing device described in the workflow definition file read in the read process does not match the second image processing device selected by the application program, the rewriting process comprising: rewriting information indicating the first image processing device in the workflow definition file read in the read process to information indicating the second image processing device; and, if there is a setting value that can be selected by further rewriting the information to information indicating the second image processing device, receiving a selection of whether or not to rewrite the information to the setting value using a user interface of the information processing device, and, if a selection of rewriting the information to the setting value is received, rewriting the information to the setting value; The second notification process; Execute the 1. An application program comprising:

14. 14. The application program according to claim 1, The computer includes: when there are a plurality of first image processing devices described in the workflow definition file read in the read process, it is determined whether each of the first image processing devices matches the second image processing device selected by the application program, and when there are a plurality of first image processing devices that do not match the second image processing device, a selection of information indicating the first image processing device that is to be the target of the rewrite process is accepted using a user interface of the information processing device, and the rewrite process is executed using the information indicating the selected first image processing device as the target of execution.

1. An application program comprising:

15. An image processing unit; A controller; An image processing device comprising: The controller: a read process is executed at a predetermined timing to read a workflow definition file, the workflow definition file being a file that defines a workflow indicating a series of processes including image processing, and at least one workflow definition file is capable of being registered in the image processing device; The controller further comprises: When the device described in the workflow definition file read in the read process is different from the image processing device, executing a rewrite process for rewriting information indicating the device in the workflow definition file read in the read process to information indicating the image processing device; 13. An image processing device comprising:

Images