JP2017050813A - Information processor, control method for information processor, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform a process using a favorite set value, which has been set for a function provider before alteration, even if the configuration of one of function providers is altered when a specific process is performed by combining the function providers.SOLUTION: An information processor that performs a specific process by combining a plurality of function providers according to a predetermined workflow definition file registers favorite setting, which has been set for each function provider by a user, into storage means as favorite setting with which a function provider ID, the type of a function provider, and a user ID are associated. In accordance with reading of the predetermined workflow definition file, a function provider to be performed, which has been described in the predetermined workflow, is retrieved. Using a function provided ID acquired from the predetermined function provider thus retrieved and a user ID specifying the predetermined workflow definition file, favorite setting registered for the retrieved predetermined function provider is set.SELECTED DRAWING: Figure 15

Description

  The present invention relates to an information processing apparatus, a control method for the information processing apparatus, and a program.

  In recent years, systems capable of expanding the functions of image forming apparatuses have become widespread in image forming apparatuses installed in offices. The function to be expanded (hereinafter referred to as “extended function”) is realized by a software program (hereinafter referred to as “extended software”), and can be added not only at the time of factory shipment but also at the operation stage after installation. An example of this type of system is Canon's MEAP (registered trademark).

  In particular, extension software created for a specific purpose is called application software (hereinafter referred to as an application). The application realizes a target process by using functions such as a facsimile, a scanner, and a printer included in the image forming apparatus. The image forming apparatus is configured so that a plurality of applications can be installed according to the user's purpose.

On the other hand, in a conventional application, a function that saves the setting content of an application that the user likes as “favorite” and can easily call it later when the user operates is known (for example, Patent Document 1). reference).
According to Patent Document 1, first, a custom button for starting processing with setting information currently set in an application that is currently started is registered in a custom menu, and the setting information and custom button that are currently set are registered. Stores button data for.
When the display of the custom menu is instructed by the user, the custom menu including the custom button is displayed. When the custom button is pressed, the application is started with the setting information of the application corresponding to the custom button being read. . As a result, the setting information of the currently activated application, that is, the favorite setting is saved, and the application can be activated in a state where the saved setting information is read later.

JP 2011-124958 A

When a plurality of applications are installed, the user may want to make a common favorite setting for each application.
For example, in the case of an application that performs printing, the page layout may be always “2 in 1”, or the staple may be always “present”.
In the prior art, favorite registration means and calling means for each application are different. For this reason, when the user performs the same favorite setting for a plurality of applications, the user has to register the favorite setting using the favorite registering unit in each application and call the favorite setting using the favorite calling unit of each application. there were.

On the other hand, there may be an application having the same function, for example, a standard pull print application having a standard pull print function, and a bookbinding pull print application having a bookbinding function in addition to the functions of the standard pull print application.
In this case, the administrator of the image forming apparatus may change from a standard pull print application having the same function to a bookbinding pull print application in order to change the system configuration.
In this case, in the prior art, the standard pull print application and the bookbinding pull print application have different favorite setting registration means and calling means, and the setting storage location, setting item, and setting value range often differ depending on the application.
For this reason, even if the user has set a favorite setting for the standard pull print app, if the administrator changes the configuration from the standard pull print app to the bookbinding pull print app, the new app will take over the settings of the old app. I can't.
Therefore, after the configuration change to the bookbinding pull-print application, which is a new application, the user has to take the trouble of performing the same favorite setting set in the old application again on the new application.

  The present invention has been made to solve the above-described problems. The object of the present invention is to change the configuration of one of the function providers when a plurality of function providers are linked to execute specific processing. However, it is to provide a mechanism that can execute processing using the favorite setting value set in the function provider before the change.

The information processing apparatus of the present invention that achieves the above object has the following configuration.
An information processing apparatus that executes a specific process in cooperation with a plurality of function providers according to a predetermined workflow definition file, and sets a favorite setting set by the user for each function provider, a function provider ID, and a function provider type A management unit that registers and manages a favorite setting associated with a user ID in a registration unit, and a function provider to be executed described in the predetermined workflow in response to reading the predetermined workflow definition file Registration with the searched predetermined function provider using the search means for searching for, the function provider ID acquired from the searched predetermined function provider, and the user ID instructing the predetermined workflow definition file Setting means for performing the set favorite setting. And features.

  According to the present invention, when a specific process is executed in cooperation with a plurality of function providers, the favorite setting value set in the function provider before the change is used even if the configuration of any function provider is changed. Can be executed.

1 is a diagram illustrating an example of a system configuration of an image processing system. 2 is a block diagram illustrating a configuration of an MFP. FIG. It is a block diagram which shows the structure of a server. 2 is a software configuration diagram in the MFP. FIG. It is a figure which shows an example of a function provider information table. It is a figure which shows an example of a function provider user information table. It is a figure which shows an example of a function provider favorite setting table. It is a figure which shows the example of a description of a workflow definition file. It is a flowchart explaining the control method of information processing apparatus. It is a figure which shows the flow of a favorite provider's favorite registration process. It is a figure which shows the flow of a favorite call process of a function provider. It is a figure which shows the flow of a favorite list value range check process. It is a flowchart explaining the control method of information processing apparatus. It is a flowchart explaining the control method of information processing apparatus. It is a flowchart explaining the control method of information processing apparatus.

Next, the best mode for carrying out the present invention will be described with reference to the drawings.
<Description of system configuration>
[First Embodiment]

  FIG. 1 is a diagram illustrating an example of a system configuration of an image processing system according to the present embodiment. This system includes an MFP 101 which is an example of an information processing apparatus connected via a LAN 110 and a server 102 connected via a WAN 120. A device on the LAN 110 and a device on the WAN 120 can communicate with each other through each other's network. FIG. 1 shows an example of a typical network configuration, and each device may be in either the LAN 110 or the WAN 120.

In FIG. 1, an MFP 101 is an image forming apparatus having a scanner and a printer. In addition, it has a software platform for adding and executing expansion software that runs on the device. The server 102 is a server that performs various processes in cooperation with the MFP 101.
For example, it may be a file server for storing a file to be printed by the MFP 101, or an application server that executes various processes such as image conversion in response to a request from the MFP 101. The number of servers is not limited to one, and a plurality of servers may exist depending on the purpose. The MFP 101 displays various user I / Fs on the operation unit 219.

FIG. 2 is a block diagram showing the configuration of the MFP 101 shown in FIG.
In FIG. 2, a control unit 210 including a CPU 211 controls the operation of the entire MFP 101. The CPU 211 reads out a control program stored in the ROM 212 or the HDD 214 and executes various control processes such as transmission / reception control and print control. The RAM 213 is used as a temporary storage area such as a main memory or work area for the CPU 211. The HDD 214 stores various programs including image data and installed expansion software. The HDD 214 stores information tables shown in FIGS. 5, 6, and 7 to be described later.
The operation unit I / F 215 connects the operation unit 219 and the control unit 210. The operation unit 219 includes a liquid crystal display unit having a touch panel function, a keyboard, and the like.

  A printer I / F 216 connects the printer 220 and the control unit 210. Image data to be printed by the printer 220 is transferred from the control unit 210 to the printer 220 via the printer I / F 216, and is printed on a recording medium by the printer 220. The printer 220 includes a finishing device that performs processing such as stapling, sorting, automatic folding, and bookbinding.

  The scanner I / F 217 connects the scanner 221 and the control unit 210. The scanner 221 reads an image on a document to generate image data, and inputs the image data to the control unit 210 via the scanner I / F 217.

  The network I / F 218 functions as a communication I / F that connects the control unit 210 (MFP 101) to the LAN 110. The network I / F 218 transmits / receives various information to / from other devices on the LAN 110 or the WAN 120.

FIG. 3 is a block diagram showing a configuration of the server 102 shown in FIG.
In FIG. 3, a control unit 310 including a CPU 311 controls the operation of the entire server 102. The CPU 311 reads out control programs stored in the ROM 312 and the HDD 314 and executes various control processes. The RAM 313 is used as a temporary storage area such as a main memory or work area of the CPU 311. The HDD 314 stores various programs and data.

  The display unit I / F 315 connects the display unit 318 and the control unit 310. A keyboard I / F 316 connects the keyboard 319 and the control unit 310. The CPU 311 recognizes an instruction from the user via the keyboard 319, and changes the screen displayed on the display unit 318 according to the recognized instruction.

  The network I / F 317 connects the control unit 310 (server 102) to the WAN 120. The network I / F 317 transmits / receives various information to / from other devices on the LAN 110 or the WAN 120.

FIG. 4 is a software configuration diagram of the MFP 101 shown in FIG.
In the present embodiment, the program (software) stored in the HDD 214 of the MFP 101 is read by the CPU 211 into the RAM 213, analyzed, and executed, whereby the processing in the flowcharts of FIGS. 9, 10, 11, 12, and 13 is performed. Is executed.

  In FIG. 4, an extended software management unit 410 is a software platform for operating extended software on the MFP 101. In FIG. 4, five function providers 411 to 415 are installed in the MFP 101 as expansion software.

  Here, the function provider is a kind of extended software, but is not an application. The app has a series of complete processes from input to output. On the other hand, a single function provider specializes in specific functions such as input for input and output for output. In order to perform a complete process from input to output, it is necessary to combine multiple function providers. is there.

For example, when providing a user with a function of “printing with standard settings after acquiring an image file from a file server” for an application, two functions of “FTP acquisition” and “standard pull print” are set to 1 for an application. Realize with one app. Here, pull printing is a process of printing image data received from a file server or various information processing apparatuses as servers in an image forming apparatus as a client.
On the other hand, in the case of a function provider, two function providers, “a function provider that realizes an FTP acquisition function” and “a provider that realizes a pull print function with standard settings”, are required. Furthermore, in order to execute these two function providers as a series of processes, a workflow processing unit 430 described later is required.

In addition, the application registers the application itself so as to be displayed side by side with the functions on a menu screen for calling functions originally provided in the MFP 101 (for example, a copy function and a fax transmission function). The application is called from the menu screen according to a user instruction.
On the other hand, the function provider registers the function provider itself in the function provider management unit 420 described later instead of the menu screen. The function provider is called by an instruction from the workflow processing unit 430 via the function provider management unit 420.

  Further, the function provider is programmed so as to satisfy a rule (hereinafter, function provider interface) defined by a function provider management unit 420 described later. The function provider interface is a software interface in which rules for exchanging software are determined. The function provider interface is defined for each type of function (hereinafter, function type) provided by the function provider. The function provider is called from the workflow processing unit 430 based on the function provider interface.

  One function provider may have a plurality of types of interfaces depending on the purpose. For example, in the case of a function provider that implements the pull print function, there are multiple types of interfaces depending on the purpose, such as an interface for the purpose of “display print setting screen” and an interface for the purpose of “execution of print job”. Can be prepared.

  A plurality of types of function providers can be installed in the MFP 101. A plurality of types of function providers of different function types may be installed, or a plurality of types of function providers of the same function type may be installed. Since function providers of the same function type have the same software interface, the extension software can exchange software in the same way as long as it is a function provider of the same function type.

The FTP acquisition provider 411 is a function provider (function type = file acquisition) that provides a function of acquiring a file by FTP reception. The FTP acquisition provider 411 implements a function provider interface (file acquisition provider interface) defined for a function provider whose function type is “file acquisition”. Function providers whose function type is “file acquisition” are collectively referred to as a file acquisition provider.
On the other hand, the UserBox acquisition provider provides a function for acquiring a file from a UserBox (secured in the HDD 214) that is a file storage function for each user provided in the ROM 212 and the HDD 214 of the MFP 101.

The standard pull print provider 413, the standard pull print provider 414, and the bookbinding pull print provider 415 are all function providers (function type = pull print) that provide a pull print function. The function providers whose function type is “pull print” are collectively referred to as a pull print provider.
The pull print provider implements a function provider interface (pull print provider interface) defined for a function provider whose function type is “pull print”.
The regular pull print provider 413 has a print setting screen for a beginner who is not familiar with the operation of the MFP 101 and performs printing with a predetermined setting. On the other hand, the standard pull print provider 414 has a print setting screen for general users. The bookbinding pull print provider 415 has a bookbinding print setting screen for performing advanced finishing.
Each function provider realizes a function provider interface defined for its own function type even if there is no other function provider having the same function type in the MFP 101.
The five function providers 411 to 415 described above are examples, and various function providers can be added to or deleted from the MFP 101 as expansion software.

  The function provider management unit 420 is software that manages function providers installed in the MFP 101. The function provider management unit 420 includes a function provider registration unit 421, a function provider setting unit 422, and a function provider search unit 423. Furthermore, the function provider management unit 420 includes a function provider information table 424, a function provider user information table 425, and a function provider favorite setting table 426.

In response to a request from each function provider, the function provider registration unit 421 registers information such as a function type and a settable value of each function provider in the function provider information table 424. Each function provider 411 to 415 registers itself with the function provider registration unit 421 when installed in the MFP 101 and in an execution state.
In response to a request from the user, the function provider setting unit 422 sets a function provider setting such as a function provider favorite setting in the function provider user information table 425.

  The function provider search unit 423 receives a function provider search condition from the workflow processing unit 430 described later, and identifies a function provider that matches the condition based on information in the function provider information table 424. Since the function provider search unit 423 specifies one function provider as the search result, when there are a plurality of function providers that match the search condition, the function provider with the highest priority is set as the search result.

  The workflow processing unit 430 executes a series of processes by combining a plurality of function providers in accordance with a predetermined workflow definition file 440 described later. In this embodiment, the workflow refers to a series of processes in which a plurality of function providers are combined.

The workflow definition file 440 defines information related to function provider invocation, such as a function provider search condition that the workflow processing unit 430 invokes, a calling order, and a setting value applied to the function provider that has been invoked.
In FIG. 4, two examples of workflow definition files are defined, but the number is not limited.

FIG. 5 is a diagram illustrating an example of the function provider information table 424 illustrated in FIG.
In FIG. 5, the function provider information table 424 holds information related to a function provider, such as a function provider ID that uniquely identifies the function provider, a function provider name, a function type (type), and a function provider interface.

FIG. 6 is a diagram illustrating an example of the function provider user information table 425 illustrated in FIG.
In FIG. 6, the function provider user information table 425 holds information related to a user who uses the function provider, such as a user ID that uniquely identifies a user who uses the function provider.

FIG. 7 is a diagram showing an example of the function provider favorite setting table 426 shown in FIG.
In FIG. 7, a function provider favorite setting table 426 holds a user ID indicating a user who has registered a function provider favorite, a function type of the function provider, and a function provider ID. The function provider favorite setting table 426 holds information related to the function provider favorite setting such as a setting ID for specifying a favorite setting item and a setting value for the favorite setting item.

FIG. 8 is a diagram showing a specific description example of the workflow definition file 440 shown in FIG. In this embodiment, the workflow definition file is expressed as an XML format file, but is not limited to the XML format, and may be a file of another format.
In FIG. 8, a Workflow tag 801 indicates that the following description is a workflow definition.

The FP tag 802 is a child element of the Workflow tag 801 and defines information related to the function provider executed in the workflow. The no attribute of the FP tag 802 defines the execution order of function providers in the workflow, and “no =“ 1 ”” indicates that the function provider is executed first. The id attribute of the FP tag 808 defines that the first function provider to be executed is the FTP acquisition provider.
A Condition tag 803 is a child element of the FP tag 802 and is used to define a search condition for the file acquisition provider.

  The Action tag 804 is a child element of the FP tag 802, and defines information about the function provider call. The no attribute and method attribute of the Action tag define the execution order and the interface to be called in the function provider defined by the FP tag. The Action tag 804 defines that “showSettingUI” is called first in the execution of the file acquisition provider.

  A Parameter tag 805 is a child element of the Action tag 804, and defines a setting value to be passed when an interface (showSettingUI) defined in the Action tag 804 is called.

  The Action tag 806 is a child element of the FP tag 802, and defines information about the function provider call. The Action tag 806 defines that “doGet” is called second in the execution of the file acquisition provider.

  A Parameter tag 807 is a child element of the Action tag 806, and defines a setting value to be passed when an interface (doGet) defined in the Action tag 806 is called. The Action tag 806 includes an Output tag that defines an output as a result of executing “doGet”.

The FP tag 808 has a no attribute and defines that the second function provider to be executed is a pull print provider. The type attribute of the FP tag 808 defines the function type of the function provider to be executed, and “type =“ PULL_PRINT ”” indicates that it is a pull print provider. As for the FP tag, the function provider can be uniquely specified using the id attribute as in the FP tag 802, or can be specified in the function type using the type attribute as in the FP tag 808.
A Condition tag 809 is a child element of the FP tag 808 and is used to define a search condition for the pull print provider.

  The Action tag 810 is a child element of the FP tag 808, and defines information about the function provider call. The Action tag 810 defines that “showSettingUI” is called first in the execution of the pull print provider. In addition to this, the Action tag 810 includes an Input tag representing a definition related to an input of a “showSettingUI” call of the pull print provider.

  A Parameter tag 811 is a child element of the Action tag 810, and defines a setting value to be passed when an interface (showSettingUI) defined in the Action tag 810 is called. In addition to this, the Action tag 810 includes an Output tag that defines an output as a result of executing the “showSettingUI”.

  The Action tag 812 defines that “doPullPrint” is called second in the execution of the pull print provider. In addition, the Action tag 812 includes an Input tag representing a definition related to an input of a pull print provider's “doPullPrint” call.

  A Parameter tag 813 is a child element of the Action tag 812, and defines a setting value to be passed when an interface (doPullPrint) defined in the Action tag 812 is called.

  FIG. 9 is a flowchart illustrating a method for controlling the information processing apparatus according to the present embodiment. This example corresponds to the workflow execution flow on the MFP 101. Each step is realized by the CPU 211 executing a control program stored therein.

  In step S901, the workflow processing unit 430 receives a workflow execution instruction from the user. In step S902, the workflow processing unit 430 reads the workflow definition file 440 corresponding to the execution instruction. Here, it is assumed that the workflow definition file 440 is defined so that “function provider whose function provider ID is FTP_GET” and “function provider whose function type is pull print” are executed in order.

  In step S <b> 903, the workflow processing unit 430 instructs the function provider management unit 420 to search for a function provider “function provider whose function provider ID is FTP_GET” described in the workflow definition file 440.

In step S904, the function provider management unit 420 extracts function providers that match the search conditions based on the function provider information table 424. In this example, it is assumed that the FTP acquisition provider 411 is extracted.
In step S905, the function provider management unit 420 notifies the search result of the FTP acquisition provider to the workflow processing unit 430. In step S <b> 906, the workflow processing unit 430 that has received the search result issues a file acquisition instruction to the FTP acquisition provider 411 of the search result.
In S907 to S913, the FTP acquisition provider 411 performs FTP file acquisition processing based on the instruction received from the workflow processing unit 430.

  First, in S907, the FTP acquisition provider 411 checks whether a favorite registration instruction has been received from the user. Here, the FTP acquisition provider 411 displays a setting screen for the user to perform settings necessary for the FTP acquisition process on the operation unit 219 of the MFP 101, and whether to perform favorite registration from the user when acquiring the setting contents. Accept instructions for no.

In step S908, the FTP acquisition provider 411 determines whether an instruction for performing favorite registration is received from the user in step S907. If the FTP acquisition provider 411 determines that an instruction to perform favorite registration is received from the user in S907, the process proceeds to S909. If the FTP acquisition provider 411 determines in S907 that it has not received an instruction to perform favorite registration from the user, the process proceeds to S910.
In step S909, the FTP acquisition provider 411 performs favorite registration processing. Details of the processing are shown in FIG.

  In step S910, the FTP acquisition provider 411 checks whether a favorite call instruction has been received from the user. Here, the FTP acquisition provider 411 displays a setting screen for the user to perform settings necessary for the FTP acquisition process on the operation unit 219 of the MFP 101, and performs a favorite call from the user when acquiring the setting contents. Accept instructions for no.

In step S911, the FTP acquisition provider 411 determines whether an instruction for performing a favorite call is received from the user in step S910. If the FTP acquisition provider 411 determines that an instruction for performing a favorite call is received from the user in S910, the process proceeds to S912. If the FTP acquisition provider 411 determines in S910 that it has not received an instruction to make a favorite call from the user, the process proceeds to S913.
In S912, the FTP acquisition provider 411 performs favorite call processing. Details of the processing are shown in FIG. In step S913, the FTP acquisition provider 411 executes FTP file acquisition processing according to the instruction.
In step S <b> 914, the FTP acquisition provider 411 transmits the acquired file as a result of the FTP file acquisition process to the workflow processing unit 430.

  In step S <b> 915, the workflow processing unit 430 instructs the function provider management unit 420 to search for a function provider whose “function type is pull print function” described in the workflow definition file 440.

In step S <b> 916, the function provider management unit 420 extracts a function provider that matches the search condition based on the function provider information table 424. In this example, it is assumed that the standard pull print provider 414 is extracted.
In step S917, the function provider management unit 420 notifies the search result of the pull print provider to the workflow processing unit 430.
In step S918, the workflow processing unit 430 that has received the search result issues a pull print instruction to the standard pull print provider 414 of the search result. In S919 to S923, the standard pull print provider 414 performs standard pull print processing based on the instruction received from the workflow processing unit 430.

  First, in step S919, the standard pull print provider 414 determines whether a favorite registration instruction has been received from the user. Here, the standard pull print provider 414 displays a setting screen for the user to perform settings necessary for the standard pull print process on the operation unit 219 of the MFP 101, and when the setting content is acquired, the user can register a favorite. An instruction to perform or not is accepted.

  In step S920, the standard pull print provider 414 determines whether an instruction to perform favorite registration is received from the user in step S919. If the standard pull print provider 414 determines in S919 that it has received an instruction to perform favorite registration from the user, the process proceeds to S909. If the standard pull print provider 414 determines in S919 that it has not received an instruction to perform favorite registration from the user, the process proceeds to S921.

  In step S921, the standard pull print provider 414 determines whether a favorite call instruction has been received from the user. Here, the standard pull print provider 414 displays a setting screen for the user to perform settings necessary for the standard pull print processing on the operation unit 219 of the MFP 101, and when the setting content is acquired, the user pulls a favorite call. An instruction to perform or not is accepted.

In step S922, the standard pull print provider 414 determines whether an instruction for performing a favorite call is received from the user in step S919. If the standard pull print provider 414 determines in S921 that it has received an instruction to perform a favorite call from the user, the process proceeds to S912. If the standard pull print provider 414 determines in S921 that it has not received an instruction to make a favorite call from the user, the process proceeds to S923.
In step S923, the standard pull print provider 414 executes standard pull print processing according to the instruction. In step S <b> 924, the standard pull print provider 414 transmits the result of performing the standard pull print process to the workflow processing unit 430. Then, the process ends.

(Function provider favorite registration process)
FIG. 10 is a diagram showing the flow of function provider favorite registration processing on the MFP 101 shown in FIG.
The process shown in FIG. 10 is the details of the process shown in S909 of FIG. Here, the processing is described on the assumption that the user is instructed to register favorites in the standard pull print provider 414. However, these processing are not performed by the function provider, and similar processing is performed by other function providers. I do.

  In step S <b> 1001, the standard pull print provider 414 sends a function provider ID, a user ID, and a favorite setting value list [setting ID, setting value] to the function provider management unit 420 to request favorite setting registration. Here, the function provider ID is “NORMAL_PULL_PRINT”, which is its own function provider ID, and the user ID is the user ID of the user who instructed the workflow processing unit 430 to perform the process. The favorite setting value list is a list of a set of setting IDs representing setting items and setting values representing setting contents for the setting items.

In step S1002, the function provider management unit 420 extracts from the function provider information table 424 the function type of the function provider that matches the search condition based on the function provider ID received in step S1001. In this example, it is assumed that the function type “PULL_PRINT” is extracted as a result of the search condition “function provider ID = NORMAL_PULL_PRINT”.
In step S1003, the function provider management unit 420 performs the loop processing in step S1004 for the number of favorite setting value lists received in step S1001.

  In step S1004, the function provider management unit 420 acquires the function type acquired in step S1002, the function provider ID received in step S1001, and the user ID. Then, the function provider management unit 420 stores the elements of the list of favorite setting values [setting ID, setting value] in the function provider favorite setting table 426 one by one in association with the function type, function provider ID, and user ID. . In this example, the favorite setting value list is stored as shown in the second to fourth lines of the function provider favorite setting table 426 in FIG. That is, the function provider favorite setting table 426 stores a favorite setting value list in association with “user ID = tanaka”, “function type = PULL_PRINT”, and “function provider ID = NORMAL_PULL_PRINT”. At this time, the list of favorite setting values is stored in order of [number of copies = 1], [page layout = 2 in 1], and [imposition = double-sided] one by one.

  In step S1005, the function provider management unit 420 returns the result of saving the favorite setting in step S1004 to the standard pull print provider 414 as a registration result. Then, the process ends.

(Function provider favorite call processing)
FIG. 11 is a flowchart showing the function provider favorite call processing on the MFP 101 shown in FIG.
The process shown in FIG. 11 is the details of the process shown in S912 of FIG. Here, the processing is described on the assumption that a favorite call is instructed by the user in the standard pull print provider 414, but these processing are not performed by the function provider, and similar processing is performed even by other function providers. I do.

  In step S1101, the standard pull print provider 414 transmits a function provider ID, a user ID, a positive setting value list, and a negative setting value list to the function provider management unit 420, and requests a favorite setting call. Here, the function provider ID is “NORMAL_PULL_PRINT”, which is its own function provider ID, and the user ID is the user ID of the user who instructed the workflow processing unit 430 to perform the process. The positive setting value list is a set of setting items and setting values that are permitted by the function provider itself among all setting values that do not depend on the MFP 101. The negative setting value list is a set of setting items and setting values that the function provider itself rejects from among all setting values that do not depend on the MFP 101. Each of the positive setting value list and the negative setting value list is a list of a set of a setting ID representing a setting item and a setting value representing a setting content for the setting item.

  In step S1102, the function provider management unit 420 extracts the function type of the function provider that matches the search condition from the function provider information table 424 based on the function provider ID received in step S1101. In this example, it is assumed that the function type “PULL_PRINT” is extracted as a result of the search condition “function provider ID = NORMAL_PULL_PRINT”.

  In step S1103, the function provider management unit 420 extracts the function provider favorite setting that matches the search condition from the function provider favorite setting table 426 based on the function provider ID and the user ID received in step S1101. In this example, as in the second to fourth lines of the function provider favorite setting table 426 in FIG. 7, the search conditions “function provider ID = NORMAL_PULL_PRINT” and “user ID = tanaka” are extracted. As a result, three favorite setting value lists of [number of copies = 1] [page layout = 2 in 1] and [imposition = double side] are extracted.

  In step S1104, the function provider management unit 420 determines whether the number of favorite setting lists obtained as a result of searching the function provider favorite setting table 426 in step S1103 is zero. If the function provider management unit 420 determines that the number of favorite setting lists as a result of searching the function provider favorite setting table 426 is 0, the process proceeds to S1105. If the function provider management unit 420 determines that the number of favorite setting lists as a result of searching the function provider favorite setting table 426 is not zero, the process proceeds to S1106.

  In step S1105, the function provider management unit 420 searches the function provider favorite setting table 426 for the function type acquired in step S1102 and the user ID received in step S1101. The function provider management unit 420 extracts function provider favorite settings that match the search conditions for the function type and user ID from the function provider favorite setting table 426. In this example, the results of the search conditions “function type = PULL_PRINT” and “user ID = tanaka” are extracted as in the second to fourth lines of the function provider favorite setting table 426 in FIG. As a result, it is assumed that one favorite setting value list of [number of copies = 50] that is a favorite setting corresponding to “function provider ID = FORM_PULL_PRINT” is extracted. Furthermore, it is assumed that three favorite setting value lists of [number of copies = 1] [page layout = 2 in 1] and [imposition = duplex] corresponding to “function provider ID = NORMAL_PULL_PRINT” are extracted. As described above, the function provider management unit 420 acquires the search result of the function provider favorite setting table 426 as a favorite setting list for each function provider ID. As described above, the function provider management unit 420 may acquire a plurality of extraction results of the favorite setting list for the function type.

  In step S1106, the function provider management unit 420 performs a range check process on the favorite setting list acquired in step S1103 or S1105. Details of the processing are shown in FIG.

  In step S1107, the function provider management unit 420 returns the favorite setting list extracted in step S1106 to the standard pull print provider 414 as a favorite setting acquisition result. Then, the process ends.

(Favorite setting list range check process)
FIG. 12 is a diagram showing a flow of a favorite list range check process in the function provider management unit 420 on the MFP 101 shown in FIG. More specifically, it is the details of the processing shown in S1106 of FIG.

In step S1201, the function provider management unit 420 determines whether the number of favorite setting lists obtained as a result is greater than zero. If the function provider management unit 420 determines that the number of favorite setting lists is not greater than “0”, the process proceeds to S1202. If the function provider management unit 420 determines that the number of favorite setting lists is greater than “0”, the process proceeds to S1203.
In step S1202, the function provider management unit 420 returns that there is no corresponding favorite setting. Then, the process ends. In step S1203, the function provider management unit 420 performs a settable value list creation process. Details of the processing will be described with reference to FIG.

  In step S1204, the function provider management unit 420 initializes the value of the variable i to “1”. In step S1205, the function provider management unit 420 determines whether or not the value of the variable i is equal to or less than the number of acquired favorite setting lists. If the value of the variable i is equal to or less than the number of acquired favorite setting lists, processing is performed. Loop. That is, when the function provider management unit 420 determines that the value of the variable i is equal to or less than the number of acquired favorite setting lists, the process proceeds to S1206. If the function provider management unit 420 determines that the value of the variable i is not less than the number of acquired favorite setting lists, the process proceeds to S1213.

  In step S1206, the function provider management unit 420 initializes the value of the variable j to 1. In step S1207, the function provider management unit 420 determines whether or not the value of the variable j is equal to or less than the number of elements in the acquired i-th favorite setting list, and the i-th favorite setting list acquired as the value of the variable j. If it is less than the number of elements, the process is looped. That is, if the function provider management unit 420 determines that the value of the variable j is equal to or less than the number of elements in the acquired i-th favorite setting list, the process proceeds to S1208. If the function provider management unit 420 determines that the value of the variable j is not less than or equal to the number of elements in the acquired i-th favorite setting list, the process proceeds to S1212.

In step S1208, the function provider management unit 420 determines whether the j-th favorite setting value of the i-th favorite list is included in the settable value list. If the function provider management unit 420 determines that the j-th favorite setting value of the i-th favorite list is included in the settable value list, the process proceeds to S1209. If the function provider management unit 420 determines that the j-th favorite setting value of the i-th favorite list is not included in the settable value list, the process proceeds to S1210.
In step S1209, the function provider management unit 420 sets the j-th favorite setting ID and the setting value of the i-th favorite setting list in the i-th result list.

  In step S1210, the function provider management unit 420 sets the initial value of the function provider in the i-th result list as the setting value corresponding to the j-th favorite setting ID in the i-th favorite setting list. In S1211, the function provider management unit 420 sets the value of the variable j to j + 1. Then, the process returns to S1207.

  In step S1212, the function provider management unit 420 sets the value of the variable i to i + 1. Then, the process returns to S1205. In step S1213, the function provider management unit 420 returns a result list having the largest number of lists among all the result lists. As a result, the favorite setting list having the most setting items that match the settable value list in the favorite setting list is returned as a result list. Then, the process ends.

[Settable value list creation process]
FIG. 13 is a flowchart illustrating a method for controlling the information processing apparatus according to the present embodiment. This example corresponds to the settable value list creation processing procedure in the function provider management unit 420 on the MFP 101 shown in FIG. More specifically, this is a detailed procedure of the process shown in S1203 of FIG. Each step is realized by the CPU 211 executing a control program stored therein.

In step S1301, the function provider management unit 420 acquires the capability value of the MFP 101 and sets it in the settable value list. Here, the function provider management unit 420 uses the printer I / F 216 of the MFP 101 to perform printing functions such as paper size, color mode, and image processing provided in the device, for example, the printer 220, and finishing such as staple, automatic folding, and bookbinding. Get the presence or absence of the function. Further, the function provider management unit 420 acquires the presence / absence of a scan function such as scan resolution, color mode, and image processing through the scanner I / F 217 of the MFP 101.
Furthermore, the function provider management unit 420 acquires the presence / absence of network functions such as the network connection state and the presence / absence of a response of the network connection destination through the network I / F 218 of the MFP 101. Further, the function provider management unit 420 acquires the presence / absence of a control program stored in the ROM 212 or the HDD 214 of the MFP 101 and the presence / absence of installed extension software stored in the HDD 214. The function provider management unit 420 sets (determines) the presence / absence of these various functions as the capability value of the MFP 101 and the set of setting ID and setting value as a settable value list.

In S1302, the function provider management unit 420 initializes the value of the variable i to “1”. In S1303, the function provider management unit 420 determines whether or not the value of the variable i is equal to or smaller than the number of items in the settable value list, and determines that the value of the variable i is equal to or smaller than the number of items in the settable value list Loops the process. That is, if the function provider management unit 420 determines that the value of the variable i is equal to or less than the number of items in the settable value list, the process proceeds to S1304.
On the other hand, if the function provider management unit 420 determines that the value of the variable i is not less than or equal to the number of items in the settable value list, the process proceeds to S1310. In S1304, the function provider management unit 420 initializes the value of the variable j to “1”.

In step S1305, the function provider management unit 420 determines whether the value of the variable j is equal to or less than the number of negative setting value lists received in step S1101 of FIG. 11, and the value of the variable i is a negative setting value. If it is less than the number of items in the list, the process is looped.
That is, when the function provider management unit 420 determines that the value of the variable j is equal to or less than the number of cases in the negative set value list, the process proceeds to S1306. If the function provider management unit 420 determines that the value of the variable j is not less than or equal to the number of cases in the negative set value list, the process proceeds to S1309.

  If the function provider management unit 420 determines in step S1306 that the i-th setting item in the settable value list matches the j-th setting item in the negative setting value list, the process advances to step S1307. If the function provider management unit 420 determines that the i-th setting item in the settable value list does not match the j-th setting item in the negative setting value list, the process proceeds to S1308. In step S1307, the function provider management unit 420 deletes the i-th set value from the settable value list. In S1308, the function provider management unit 420 sets the value of the variable j to j + 1. Then, the process returns to S1305.

  In step S1309, the function provider management unit 420 sets the value of the variable i to i + 1. Then, the process returns to S1303. Through the processes of S1302 to S1309 so far, the function provider management unit 420 deletes the setting value included in the negative setting value list from the setting value list. In step S1310, the function provider management unit 420 initializes the value of the variable p to “1”.

In S1311, the function provider management unit 420 determines whether or not the value of the variable p is equal to or smaller than the number of items in the settable value list. Loop.
That is, when the function provider management unit 420 determines that the value of the variable p is equal to or less than the number of items in the settable value list, the process proceeds to S1312. If the function provider management unit 420 determines that the value of the variable p is not less than or equal to the number of items in the settable value list, the process proceeds to S1318. In S1312, the function provider management unit 420 initializes the value of the variable q to “1”.

  In S1313, the function provider management unit 420 determines whether the value of the variable q is equal to or less than the number of cases in the positive setting value list received in S1101 of FIG. 11, and the value of the variable q is the positive setting value. If it is less than the number of items in the list, the process is looped. In other words, if the function provider management unit 420 determines that the value of the variable q is equal to or less than the number of cases in the positive setting value list, the process proceeds to S1314. If the function provider management unit 420 determines that the value of the variable q is not less than or equal to the number of cases in the positive set value list, the process proceeds to S1316.

  If the function provider management unit 420 determines in step S1314 that the p-th setting item in the settable value list matches the q-th setting item in the positive setting value list, the process advances to step S1317. If the function provider management unit 420 determines that the p-th setting item in the settable value list does not match the q-th setting item in the positive setting value list, the process proceeds to S1315. In S1315, the function provider management unit 420 sets the value of the variable q to q + 1. Then, the process returns to S1313. In step S1316, the function provider management unit 420 deletes the p-th set value from the settable value list.

  In step S1317, the function provider management unit 420 sets the value of the variable p to p + 1. Then, the process returns to S1311. Through the processing of S1310 to S1317 so far, the function provider management unit 420 deletes the setting value not included in the positive setting value list from the setting value list. In step S1318, the function provider management unit 420 returns a settable value list for specifying the set value range. Then, the process ends.

[Workflow execution processing]
FIG. 14 is a flowchart illustrating a method for controlling the information processing apparatus according to the present embodiment. More specifically, this corresponds to the workflow execution processing procedure in the MFP 101 shown in FIG. Each step is realized by the CPU 211 reading, analyzing, and executing the stored control program.
In step S1401, the workflow processing unit 430 first receives a workflow execution instruction from the user. In step S1402, the workflow processing unit 430 reads the workflow definition file 440 corresponding to the execution instruction.

  In step S1403, the workflow processing unit 430 extracts one function provider definition defined by the FP tag from the workflow definition file 440 in the execution order. Here, the execution order means the order of younger numbers defined in the no element of the FP tag.

In step S1404, if there is a function provider to be executed next, the workflow processing unit 430 proceeds to step S1405. If there is no function provider to be executed next (after obtaining the last function provider), the workflow processing unit 430 ends the execution of the workflow. To do.
In step S <b> 1405, the workflow processing unit 430 acquires the function provider search condition from the FP tag, and searches the function provider information table 424 for the function provider information. In step S1406, the workflow processing unit 430 receives the function provider search result and checks whether there is a function provider that matches the search condition.

  In S1406, when the workflow processing unit 430 determines that there is a function provider that matches the search result, the workflow processing unit 430 advances the processing to S1407. On the other hand, if the workflow processing unit 430 determines that there is no function provider that matches the search, the process proceeds to S1413. In step S <b> 1413, the workflow processing unit 430 notifies the error and ends the workflow execution processing.

  In step S <b> 1407, the workflow processing unit 430 extracts one Action tag that is a child element of the FP tag to be processed from the workflow definition file 440 in the execution order. Here, the execution order means the order of younger numbers defined in the no element of the Action tag.

  In step S1408, the workflow processing unit proceeds to step S1409 if there is an action tag to be processed next, and returns to step S1403 if there is no action tag to be processed next (after obtaining the last action tag).

In step S1409, the workflow processing unit 430 calls the function provider acquired as the search result in step S1405 according to the definition of the action tag. At this time, if a Parameter tag or an Input tag is defined as a child element of the Action tag, the workflow processing unit 430 gives an input to the function provider according to the definition.
For example, in the workflow definition file 440 shown in FIG. 8, the Input tag of the Parameter tag 813 is a definition related to the input of the “doPullPrint” call of the pull print provider, and indicates that “Document” is received from the data whose ID is “foo”. ing. Data whose ID is “foo” is output data of “doGet” of the file acquisition provider defined by the Output tag of the Action tag 812.
Therefore, the workflow processing unit 430 provides the output data of “doGet” held by itself as input data when calling “doPullPrint”.
In step S1410, the function provider called by the workflow processing unit 430 executes processing according to the instruction. Details of the processing will be described with reference to FIG. In step S1411, the workflow processing unit 430 waits for completion of execution of the called function provider.

  In step S1412, the workflow processing unit 430 stores the output of the function provider in the HDD 214 or the RAM 213 so that it can be used as an input of another function provider. For example, the Output tag of the Parameter tag 807 is a definition related to the output of the “doGet” call of the file acquisition provider, and the “Document” data that is the output of “doGet” is stored with the ID “foo”. After saving the output of the function provider, the workflow processing unit 430 advances the processing to S1407 in order to acquire the definition of the next function provider.

[Function provider execution processing]
FIG. 15 is a flowchart illustrating a method for controlling the information processing apparatus according to the present embodiment. More specifically, the execution order of the function providers on the MFP 101 is the order. This process corresponds to the detailed procedure of the process shown in S1410 of FIG. Each step is realized by causing the CPU 211 to read the program stored in the HDD 214 of the MFP 101 into the RAM 213, and analyze and execute the program.

  In step S1501, the workflow processing unit 430 instructs the function provider to execute. In step S1502, whether the function provider needs to request a new setting input from the workflow processing unit 430 based on whether or not all the setting input values necessary for its processing have been input from the workflow processing unit 430. Judging. If the function provider determines that all setting input values necessary for its own processing are not given and setting input is necessary, the process proceeds to S1503. If the function provider determines that all setting input values necessary for its own processing have been given and there is no need for setting input, the process proceeds to S1521.

  In step S1503, the function provider receives a setting input from the user. When the function provider receives the input from the user, the process proceeds to step S1504. Here, the function provider displays a setting screen for the user to make settings necessary for the function provider process on the operation unit 219 of the MFP 101. On this setting screen, it is possible to receive an instruction from the user as to whether or not to perform favorite setting registration, favorite calling, function provider execution, and cancellation.

  In step S1504, the function provider determines whether the content input by the user in step S1503 is favorite setting registration. If the function provider determines that the content input by the user in S1503 is favorite setting registration, the process proceeds to S1505. If the function provider determines in step S1503 that the content input by the user is not favorite setting registration, the process proceeds to step S1512.

  In step S <b> 1505, the function provider transmits a function provider ID, a user ID, and a favorite setting value list [setting ID, setting value] to the function provider management unit 420 to request favorite setting registration. Here, the function provider ID is its own function provider ID, and the user ID is the user ID of the user who instructed the workflow processing unit 430 to perform processing. The favorite setting value list is a list of a set of setting IDs representing setting items and setting values representing setting contents for the setting items.

  In step S1506, the function provider management unit 420 extracts from the function provider information table 424 the function type of the function provider that matches the search condition based on the function provider ID received in step S1505. In S1507, the function provider management unit 420 initializes the value of the variable i to 1.

  In step S1508, the function provider management unit 420 determines whether the value of the variable i is equal to or less than the number of favorite setting lists received from the function provider in step S1505. When the function provider management unit 420 determines that the value of the variable i is equal to or less than the number of items in the favorite setting value list, the process is looped. That is, if the function provider determines that the value of the variable i is equal to or less than the number of items in the favorite setting list, the process proceeds to S1509. On the other hand, if the function provider determines that the value of the variable i is not less than or equal to the number of favorites setting list, the process proceeds to S1511.

  In step S1509, the function provider acquires the function type acquired in step S1506, the function provider ID received in step S1505, and the user ID by the function provider management unit 420. Then, the function provider management unit 420 stores the elements of the list of favorite setting values [setting ID, setting value] in the function provider favorite setting table 426 one by one in association with the function type, function provider ID, and user ID. . In this example, the favorite setting value list is stored as shown in the second to fourth lines of the function provider favorite setting table 426 in FIG.

  In step S1510, the function provider management unit 420 sets the value of the variable i to i + 1. Then, the process returns to S1508. In step S1511, the function provider management unit 420 returns the result of saving the favorite setting in step S1509 as a registration result to the function provider. Then, the process returns to S1502.

  In step S1512, the function provider determines whether the content input by the user in step S1503 is a favorite setting call. If the function provider determines that the content input by the user in S1503 is a favorite setting call, the process proceeds to S1513. If the function provider determines that the content input from the user in S1503 is not a favorite setting call, the process proceeds to S1520.

In step S1513, the function provider transmits the function provider ID, user ID, positive setting value list [setting ID, setting value], and negative setting value list [setting ID, setting value] to the function provider management unit 420. And request a favorite setting call.
Here, the function provider ID is its own function provider ID, and the user ID is the user ID of the user who instructed the workflow processing unit 430 to perform processing. The positive setting value list is a set of setting items and setting values that are permitted by the function provider itself among all setting values that do not depend on the MFP 101.
The negative setting value list is a set of setting items and setting values that the function provider itself rejects from among all setting values that do not depend on the MFP 101. Each of the positive setting value list and the negative setting value list is a list of a set of a setting ID representing a setting item and a setting value representing a setting content for the setting item.

  In step S1514, the function provider management unit 420 extracts the function type of the function provider that matches the search condition from the function provider information table 424 based on the function provider ID received in step S1513.

  In step S1515, the function provider management unit 420 extracts function provider favorite settings that match the search condition from the function provider favorite setting table 426 based on the function provider ID and user ID received in step S1101. Then, the function provider management unit 420 creates a favorite setting value list by using a set of the setting ID and setting value as a list.

  In step S1516, the function provider management unit 420 determines whether the number of favorite setting lists obtained as a result of searching the function provider favorite setting table 426 in step S1515 is zero. When the function provider management unit 420 determines that the number of favorite setting lists as a result of searching the function provider favorite setting table 426 is 0, the process proceeds to S1517. On the other hand, if the function provider management unit 420 determines that the number of favorite setting lists as a result of searching the function provider favorite setting table 426 is not zero, the process advances to step S1518.

In step S1517, the function provider management unit 420 searches the function provider favorite setting table 426 for the function type acquired in step S1514 and the user ID received in step S1513.
The function provider management unit 420 extracts function provider favorite settings that match the search conditions for the function type and user ID from the function provider favorite setting table 426. Then, the function provider management unit 420 creates a favorite setting value list by using a set of the setting ID and setting value as a list. The function provider management unit 420 may acquire a plurality of extraction results of the favorite setting list for the function type.

  In step S1518, the function provider management unit 420 performs a range check process on the favorite setting list acquired in step S1515 or S1517. Details of this process have already been described with reference to FIG.

  In S1519, the function provider management unit 420 returns the favorite setting list extracted in S1518 as a favorite setting acquisition result to the function provider. Then, the process returns to S1503.

In step S1520, the function provider determines whether the content input from the user in step S1503 is execution of the function provider. If the function provider determines that the content input by the user in step S1503 is execution of the function provider, the process proceeds to step S1521. On the other hand, if the function provider determines that the content input by the user in S1503 is not function provider execution, the process proceeds to S1523.
In step S1521, the function provider executes function provider processing according to the instruction. In step S1522, the function provider transmits the result of the function provider process to the workflow processing unit 430. Then, the process ends. On the other hand, in S1523, the function provider executes cancel processing in accordance with the instruction. Then, the process proceeds to S1522.

According to the present embodiment, the function provider management unit provides the favorite registration unit and the favorite calling unit among the unit that executes a series of processes by combining a plurality of function providers and the series of processes.
Further, when a workflow that configures an application is changed and a function provider having the same function type is executed, the favorite setting registered from the function provider can be inherited and called by a newly executed function provider. Thereby, even when the configuration of the application is changed, it is possible to reduce the trouble of the user performing the favorite setting again.

  In addition, the function provider management unit creates a list of settable values from the positive setting value, the negative setting value of the function provider to be called, and the capability value of the MFP for each setting value of the favorite setting read from the function provider favorite setting table. Create and determine whether it is within that range. As a result, even if the setting value of the function provider that registered the favorite setting differs from the setting value of the function provider that calls the favorite setting, only the setting values that can be set by the function provider that calls the favorite setting are recalled. Can do. Even if the capability values of the MFP at the time of favorite registration and when calling favorite are different, it is possible to call the favorite setting by narrowing down to only the setting values that can be used by the function provider at the time of calling the favorite setting.

  In the present embodiment, the workflow processing unit has been described as a configuration that calls a function provider as a component of the workflow. However, an application that is an extension software serves as the workflow processing unit and calls other extension software. It may be. For example, when any app performs processing, when calling another app or function provider in the middle of processing, the design definition is retained for each processing, and the design designation is called when calling It may be configured to be passed to the extended software.

  The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

101 MFP

Claims (10)

An information processing apparatus that executes a specific process in cooperation with a plurality of function providers according to a predetermined workflow definition file,
Management means for registering and managing the favorite setting set by the user for each function provider, by registering the favorite setting in which the function provider ID, the function provider type, and the user ID are associated with each other in the registration means;
Search means for searching for a function provider to be executed described in the predetermined workflow in response to reading the predetermined workflow definition file;
Setting for performing a favorite setting registered for the searched predetermined function provider, using the function provider ID acquired from the searched predetermined function provider and the user ID instructing the predetermined workflow definition file Setting means to
An information processing apparatus comprising: A determination means for determining a setting value range to be favorite set for a function provider to be executed from the set value of the favorite setting acquired and a setting value specified by the device;
The information processing apparatus according to claim 1, wherein the setting unit sets a determined setting value for a function provider to be executed.   The determination means obtains a positive setting value list and a negative setting value list preset by the function provider from the searched function provider, and sets a setting value that should not be set from the favorite setting value range. The information processing apparatus according to claim 2, wherein the information processing apparatus is deleted.   The information processing apparatus according to claim 1, wherein the specific process is specified by a combination of specific function providers.   The information processing apparatus according to claim 1, comprising: a scanner, a printer, a communication I / F, and a user I / F.   The information processing apparatus according to claim 1, wherein the predetermined workflow definition file includes a tag that specifies an execution order of the registered function providers.   The information processing apparatus according to claim 1, wherein the predetermined workflow definition file includes a tag that specifies a search condition for a registered function provider.   The information processing apparatus according to claim 1, wherein the predetermined workflow definition file includes a tag that specifies an interface for calling a registered function provider. A method of controlling an information processing apparatus that executes a specific process in cooperation with a plurality of function providers according to a predetermined workflow definition file,
A management process for registering and managing a favorite setting set by a user for each function provider by registering a favorite setting in which a function provider ID, a function provider type, and a user ID are associated with each other;
A search step of searching for a function provider to be executed described in the predetermined workflow in response to reading the predetermined workflow definition file;
Setting for performing a favorite setting registered for the searched predetermined function provider, using the function provider ID acquired from the searched predetermined function provider and the user ID instructing the predetermined workflow definition file Process,
An information processing apparatus control method comprising:   A program for causing a computer to execute the control method of the information processing apparatus according to claim 9.

Images