JP2017182572A - Data processing device, information processing device, data processing method of data processing device, data processing method of information processing device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To create a workflow definition file obtained by adding processing of displaying a UI screen in a function provider which is not accompanied with UI display in the case of creating a workflow definition file including the function provider accompanied with UI display and a function provider which is not accompanied with UI display.SOLUTION: A data processing device is configured to add processing for displaying a UI screen showing a state of specific processing to a workflow definition file while a function provider which is not accompanied with UI display executes the specific processing in the case of determining that a function provider defined in a created workflow definition file includes a function provider accompanied with the UI display and the function provider which is not accompanied with the UI display.SELECTED DRAWING: Figure 8

Description

  The present invention relates to a data processing device, an information processing device, a data processing method for the data processing device, a data processing method for the information processing device, 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).

  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.

  The application prescribes the procedure for realizing the target process in the program. Since an app can only execute processing specified in advance by a program, if it is going to realize other things, it is necessary to modify the program of the app or prepare another app, and the extended function can be operated flexibly. There wasn't.

  Therefore, a realization means called workflow application was born. This combines a component called a function provider, which is expansion software having an interface defined for each function type, as a flow as a specific process. By executing this flow, it is a technology that makes it possible to realize an application that combines various functions.

JP 2008-158632 A

  In Patent Document 1, as one example, a plurality of functions of an MFP, which is an image forming apparatus, are used in cooperation with a workflow system provided by a server apparatus while linking the workflows of the image forming apparatus and the server apparatus. An example of realizing the work was shown.

However, Patent Document 1 cannot provide a unified operational feeling of the workflow. There are two types of functional components that make up the workflow.
One is a functional component (hereinafter referred to as a UI possessing function provider) that guides an interactive operation by displaying a user interface (hereinafter referred to as a screen or UI) to the user.
The second is a functional component (hereinafter not referred to as a UI non-owned function provider) processed inside the system (does not display a UI). When these are combined, there is a problem that it is impossible to provide the user with a unified operability.
Specifically, the UI is displayed while processing the UI possessing function provider, and the UI is not displayed while processing the UI non-retaining function provider. Therefore, the user cannot enjoy a unified operational feeling.
That is, in the conventional information processing apparatus, the workflow status cannot be displayed on the UI while the UI non-owning function provider is processing in the workflow. For this reason, there is a problem that the user cannot flexibly respond to a request for confirming the state of a series of workflows through the UI screen.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a workflow definition file including a function provider with UI display and a function provider without UI display in a data processing apparatus. Is to create a workflow definition file in which processing for displaying a UI screen is added to a function provider not accompanied by a UI display.
In a data processing device, when a workflow is started in which a function provider without UI display and a function provider without UI display are started, a system that can display a unified UI screen even when the workflow progresses is provided It is to be.

The data processing apparatus of the present invention that achieves the above object has the following configuration.
A data processing apparatus, a creation unit that creates a workflow definition file in which a plurality of function providers are combined, a function provider that includes a UI display in the function provider defined in the workflow definition file created by the creation unit, and A determination means for determining whether or not a function provider without a UI display is included, and a function provider without a UI display when the determination means determines that a function provider without a UI display is included And adding means for adding a process for displaying a UI screen indicating the state of the specific process to the workflow definition file while the specific process is being executed.
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 described in a created workflow definition file using a plurality of function providers, and causes any one of the function providers selected from the plurality of providers to start a specific process If any function provider executed by the workflow processing means includes a UI screen display process by a specific function provider, the workflow processing means for giving an instruction is associated with the function provider. An instruction to display a UI screen is instructed to the specific function provider.

According to the data processing device, when a workflow definition file including a function provider with UI display and a function provider without UI display is created, the UI screen is displayed on the function provider without UI display. An added workflow definition file can be created.
According to the information processing apparatus, when a workflow in which a function provider without UI display and a function provider without UI display are started, UI screen display with a sense of unity can be performed even when the workflow progresses.

Combine UI possessing function providers and non-UI possessing function providers. In that case, a means for converting a user interface non-owning function provider into a process having a user interface is provided. Thereby, it is possible to provide the user with a sense of unity.

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 and PC. 2 is a software configuration diagram in the MFP. FIG. It is a software block diagram in PC. It is a figure which shows the screen which the flow creation tool which operate | moves on PC displays. It is a figure which shows an example of a function provider information table. It is a flowchart which shows the data processing method of a data processor. It is a figure which shows the example of a specific description of a workflow definition file. It is a flowchart which shows the data processing method of information processing apparatus. It is a figure which shows UI screen displayed on an operation part. It is a figure which shows UI screen displayed on an operation part. It is a flowchart which shows the control method of a data processor. It is a figure which shows UI screen displayed on an operation part. It is a specific description example of a workflow definition file.

Next, the best mode for carrying out the present invention will be described with reference to the drawings.
<Description of system configuration>
[First Embodiment]
The best mode for carrying out the present invention will be described below with reference to the drawings.
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 that is an information processing apparatus connected via a LAN 110, a PC 103 that is a data processing apparatus, 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 extension software running on the device (details will be described later).
The PC 103 is a terminal device, and software (hereinafter referred to as a flow creation tool) for creating a workflow definition file that runs on the MFP 101 is running.
The server 102 is a server that performs various processes in cooperation with the MFP 101. For example, it may be a file server that receives image data from the MFP 101 or a Web application server that receives a processing request from the MFP 101 and executes OCR (optical character recognition) processing. In the system, the number of servers is not limited to one, and a plurality of servers may exist depending on the purpose.

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 control programs stored in the ROM 212 and the HDD 214 and executes various control processes such as reading control and transmission 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 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 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 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 the configuration of the server 102 and the PC 103 shown in FIG.
In FIG. 3, a control unit 310 including a CPU 311 controls the operation of the entire apparatus. 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 to the LAN 110 or 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 according to the present embodiment. As for the software of this example, the CPU 211 reads out a program (software) stored in the HDD 214 of the MFP 101 to the RAM 213, analyzes and executes the program, and the processing described later 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, seven extension softwares 411 to 417 are installed in the MFP 101 as function providers.

  In this embodiment, the function provider is a kind of extension 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 indicates extended software that provides specific functions such as input for input and output for output. In order to perform a series of complete processing from input to output, multiple function providers must be used. Need to be combined.

For example, in the case of providing a user with a function of “scan and send after preview display”, if an application is used, three functions of “scan”, “preview”, and “send” are realized by one application.
On the other hand, in the case of a function provider, three function providers of “a function provider that realizes a scanning function”, “a function provider that realizes a preview function”, and “a function provider that realizes a transmission function” are required. Furthermore, in order to execute these three function providers as a series of processes, a workflow processing unit 430 described later is required. Here, the workflow processing unit 430 functions as a workflow processing unit that instructs the function provider to start a specific process.

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. In order to execute the workflow, a menu item displayed by the workflow processing unit 430 corresponding to a workflow definition file described later on the menu screen is used.

  Furthermore, the function provider is programmed so as to satisfy the rules defined by the function provider management unit 420 (hereinafter referred to as function provider interface). 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, a function provider that implements a scan function may prepare multiple types of interfaces for different purposes, such as for the purpose of “displaying the scan settings screen” and for the purpose of “executing a scan job”. it can.

  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 function provider interface, extension software can exchange software between the same functions as long as it is a function provider of the same function type.

  Both the standard scan provider 411 and the simple scan provider 412 are function providers (function type = scan) that provide a scan function. Function providers whose function type is “scan” are collectively referred to as a scan provider. The scan provider implements a function provider interface (scan provider interface) defined for a function provider whose function type is “scan”. The standard scan provider 411 has a scan setting screen for general users. On the other hand, the simple scan provider 412 has a scan setting screen for beginners who are unfamiliar with the operation of the MFP 101.

The built-in OCR provider 413 and the Web OCR provider 414 are both function providers (function type = OCR) that provide the OCR function. The function providers whose function type is “OCR” are collectively referred to as an OCR provider. The OCR provider implements a function provider interface (OCR provider interface) defined for a function provider whose function type is “OCR”. The built-in OCR provider 413 provides an OCR function by performing character recognition processing on the MFP 101.
On the other hand, the Web OCR provider 414 provides an OCR function by calling a character recognition process provided by an external Web server (for example, the server 102) via the Web browser 450.

  The FTP transmission provider 415 is a function provider (function type = file transmission) that provides a transmission function. The transmission provider implements a function provider interface (file transmission provider interface) defined for a function provider whose function type is “file transmission”. Reference numeral 416 denotes a preview provider.

A UI display conversion system provider 417, which is a UI display provider, is a provider for converting UI display processing during execution of processing of a UI non-owning function provider. In the present embodiment, the description will be made in a form included in the extended software management unit 410, but of course, it may be arranged in a form included in the workflow processing unit 430. The UI display conversion system provider 417 is a provider responsible for UI screen display processing for a UI non-owning function provider. Here, the OCR provider is included in the UI non-owning function provider.
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 seven function providers 411 to 417 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, a function provider search unit 423, a function provider information table 424, a function provider setting table 425, and a function provider interface definition 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 registers itself with the function provider registration unit 421 when installed in the MFP 101 and in an execution state.

  The function provider search unit 423 receives a function provider search condition from the workflow processing unit 430, which will be described later, and identifies the function provider based on the information in the function provider information table 423. 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 function provider interface definition 426 defines a function provider interface.

  The workflow processing unit 430 executes a series of processes by combining a plurality of function providers according to a workflow definition file 440 described later. In the present embodiment, the workflow indicates 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, one workflow definition file is defined as an example, but the number is not limited to one, and a plurality of workflow definition files may exist on the MFP 101.

  “ShowSettingUI” is an interface for displaying a scan setting screen, receives a parameter, and returns a result as a boolean. When the user confirms the scan setting, true (true) is returned, and when the user cancels the scan setting, false (false) is returned. Parameter is a setting value for calling the interface, and is defined in the workflow definition file 440. “DoScan” is an interface for executing a scan, receives a parameter, and returns the result in a data format of “Document”. “DoScan” scans with a value set by the user using “ShowSettingUI” or a set value specified by Parameter.

FIG. 5 is a software configuration diagram of the PC 103 shown in FIG.
Note that the software (program) stored in the HDD 314 of the PC 103 is read by the CPU 311 into the RAM 313, analyzed, and executed, so that the processing described later is executed.

  In FIG. 5, the screen control unit 510 controls the screen display of the flow creation tool. A workflow definition file creation unit 520 creates a workflow definition file used by the MFP 101. The function provider I / F information table 530 is a table that stores information related to the function provider interface possessed by each function provider, and is stored in the HDD 314. The function provider interface definition 540 is the same definition as the function provider interface definition 426 of the MFP 101.

FIG. 6 is a diagram showing a screen displayed by the flow creation tool operating on the PC 102 shown in FIG.
In FIG. 6, an area 610 is an area for displaying a workflow component of a function provider (function type) defined in the function provider I / F information table 530. In FIG. 6, each function provider is represented as a button, but may be represented in another format.

  An area 620 is an area for defining a workflow flow. The workflow flow is defined by arranging the function providers necessary for the workflow from the buttons displayed in the area 610. In FIG. 6, a workflow for “OCR” and “send” after “scan” is defined.

An area 630 is an area for setting individual function providers. Among the function providers arranged in the area 620, the setting screen of the function provider being selected is displayed. In FIG. 6, a transmission provider setting screen is displayed as an example. A check box 631 exists in the area 630. The check box 631 is a setting for preventing the setting screen from being displayed on the MFP 101 when the target function provider is executed by the MFP 101. The function provider whose check box 631 is ON executes the workflow with the setting value set in the area 630 without displaying the setting screen. Note that the check box 631 is displayed only when the function provider has a setting interface.
A text field 641 is an area for inputting a workflow name. A button 642 is a button for instructing generation of a workflow definition file.

FIG. 7 is a diagram showing an example of the function provider information table 424 shown in FIG.
In FIG. 7, a function provider information table 424 holds a function provider ID that uniquely identifies a function provider, a name of the function provider, and a function type. Furthermore, the function provider information table 424 holds information related to the function provider, such as a function provider interface, an execution interface, a cancel interface, a UI possession presence / absence, and a value that can be set in the function provider. When the above-mentioned UI possession status is “Y” is a user interface possession function provider and the UI possession status is “N”, it means a user interface non-retention function provider. In this embodiment, it is shown that the embedded OCR provider 413 and the Web OCR provider 414 are UI non-owning function providers. Further, the standard scan provider 411, the easy scan provider 412, the FTP transmission provider 415, and the preview provider 416 are UI holding function providers. The cancel interface is an interface for canceling the process. As an example, the embedded OCR provider 413 indicates that the embedded OCR provider 413 has a process called “Stop” for canceling the process.

FIG. 8 is a flowchart showing a data processing method of the data processing apparatus showing this embodiment. This example is a processing example in which the workflow definition file 440 is created by the flow creation tool in the PC 103. In this process, the CPU 311 reads out the program stored in the HDD 314 of the PC 103 to the RAM 313, analyzes, and executes the program, thereby executing each step of the flowchart of FIG.
In step S801, the screen control unit 510 receives an instruction to create a workflow definition file. In step S <b> 802, the workflow definition file creation unit 520 outputs basic information such as a workflow ID and name to the workflow definition file 440.

  In step S803, the workflow definition file creation unit 520 acquires one piece of function provider information in the order in which the workflow generation file area 620 is arranged as a workflow. In step S804, the workflow definition file creation unit 520 determines whether function provider information has been acquired in step S803 and branches the process. If the workflow definition file creation unit 520 determines that there is a function provider to be acquired and information has been acquired, the process proceeds to S805. If there is no more function provider to be acquired and information cannot be acquired, the process proceeds to S808.

  In step S805, the workflow definition file creation unit 520 determines whether the information about the UI possessing function provider has been acquired in step S804, and branches the process. If the workflow definition file creation unit 520 determines that it is a UI possessing function provider, the process proceeds to S806, and if it is not a UI possessing function provider, that is, if it is a UI non-retaining function provider, the process returns to S803.

In step S <b> 806, the workflow definition file creation unit 520 determines whether information on the presence or absence of the UI possessing function provider exists in the RAM 313. If the workflow definition file creation unit 520 determines that the information on the presence / absence of the UI possession function provider still exists in the RAM 313, the process proceeds to S807. If YES is determined, the process returns to S803.
In step S <b> 807, the workflow definition file creation unit 520 stores information indicating whether the UI possession function provider is present in the RAM 313 as “Yes”, and the process returns to step S <b> 803.
In step S808, the workflow definition file creation unit 520 returns the function provider whose information is to be acquired to the function provider at the head of the workflow. In step S809, the workflow definition file creation unit 520 acquires one piece of function provider information in the order in which the workflow generation file area 620 is arranged as a workflow.

  In step S810, the workflow definition file creation unit 520 determines whether function provider information has been acquired in step S809 and branches the process. If there is a function provider to be acquired and the workflow definition file creation unit 520 determines that information has been acquired, the process advances to step S811, and if there is no more function provider to be acquired and information cannot be acquired, the workflow definition If the file creation unit 520 determines, this process is terminated.

  In step S811, the workflow definition file creation unit 520 determines whether there is UI possession function provider presence / absence information. If the workflow definition file creation unit 520 determines that the UI possession function provider presence / absence information exists, the process proceeds to S812. If the UI does not exist, the workflow definition file creation unit 520 proceeds to S813.

  In step S812, the workflow definition file creation unit 520 proceeds to step S813 when the workflow definition file creation unit 520 determines that the information acquired in step S810 is a UI possessing function provider. If the workflow definition file creation unit 520 determines that the provider is not a UI possessing function provider, that is, if it is a UI non-retaining function provider, the process proceeds to S814.

In step S813, the workflow definition file creation unit 520 adds a definition related to the execution interface of the function provider to the workflow definition file, and the process returns to step S809.
On the other hand, in S814, the workflow definition file creation unit 520 performs a process of adding the definition of the UI non-owned function provider to the workflow definition file. In S815, a description for conversion to temporarily display the screen during processing of the UI non-owning function provider is added to the workflow definition file, and the process proceeds to S813. By executing the above steps, the flow creation tool creates the workflow definition file 440.

  FIG. 9 is a diagram showing a specific description example of the workflow definition file in the present embodiment. 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. 9, a Workflow tag 910 indicates that the following description is a workflow definition. The FP tag 920 is a child element of the Workflow tag 910 and defines information related to a function provider executed in the workflow. The no attribute of the FP tag 920 defines the execution order of the function providers in the workflow, and “no =“ 1 ”” indicates that the function provider is executed first. The type attribute of the FP tag 920 defines the function type of the function provider to be executed, and “type =“ SCAN ”” indicates that it is a scan provider.

The Condition tag 921 is a child element of the FP tag 920, and the scan provider search conditions are defined by the Required tag 922 and the Optional tag 923, which are child elements. The Required tag 922 defines an indispensable condition of the scan provider to be searched, and indicates that a scan provider that can set “PDF” as a setting value of “DUCUMENT_FORMAT (file format)” is indispensable.
The Optional tag 923 defines an optional condition of the scan provider to be searched, and indicates that a scan provider that can set “TEXT” as a setting value of “ORIGINAL_TYPE (original type)” is used preferentially.

  Here, the difference between the mandatory condition and the optional condition will be described. In the function provider search process, the indispensable condition is a condition that must be satisfied. If there is no function provider that satisfies the indispensable condition, the search result is “none”. On the other hand, the option condition is a condition that preferentially uses a function provider that satisfies the option condition. If there is no function provider that satisfies the option condition, the option condition is excluded from the search condition.

The Action tag 924 is a child element of the FP tag 920, 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 924 defines that “showSettingUI” is called first in the execution of the scan provider.
A Parameter tag 925 is a child element of the Action tag 924, and defines a setting value to be passed when an interface (showSettingUI) defined in the Action tag 924 is called. The Action tag 926 is a child element of the FP tag 920 and defines that “doScan” is called second in the execution of the scan provider.
The Output tag 927 is a child element of the Action tag 926, and defines an output as a result of executing “doScan”. The Output tag 927 defines that the output format is “Document” with the type attribute and that the ID that uniquely identifies the output data is “foo” with the id attribute. The FP 930 tag defines that the second function provider to be executed is an OCR provider with a no attribute and a type attribute.
The ReqUIred tag 931 defines an indispensable condition for the OCR provider, and indicates that an OCR provider that can set “JA (Japanese)” as a setting value of “LANG (recognition language)” is essential.
The DiSpray tag 943 defines whether the function provider has a UI and does not have a UI with a mode attribute. In this embodiment, it is defined as “false” and defines that the function provider of the FP930 tag does not have a UI. In this example, it is defined that the function provider does not have a UI only when this tag appears.

  The Action tag 932 is a child element of the FP tag 930, and defines that “doOCR” is called first in the execution of the OCR provider. The Input tag 933 is a definition related to the input of “doScan” and indicates that data in “Document” format is received from data with an ID “foo”. Data whose ID is “foo” is output data of “doScan” defined by the Output tag 927. That is, the OCR provider defines that the scan data of the scan provider is received in the Document format. The output tag 934 is a definition related to the output of “doOCR”. The output attribute is “string (character string)” in the type attribute, and the ID that uniquely identifies the output data is “bar” in the id attribute. Is defined.

  The FP tag 944 is a function provider that is executed third by a no attribute, an id attribute, and a kind attribute. As the definition contents, the kind attribute is a UI conversion function provider (SuppliDisplay) that converts a process so that a UI non-owning provider can display a UI.

  The Supply 945 tag has a class attribute and a type attribute, and defines that the destination of the UI conversion processing is a function provider and the type is OCR, that is, the function provider defined by the FP tag 930.

  The FP tag 940 defines that the fourth function provider to be executed is the FTP transmission provider by the no attribute and the id attribute. The FP tag can specify the function provider by the function type using the type attribute as in the FP tags 920 and 930, or can uniquely specify the function provider using the id attribute as in the FP tag 940.

  The input tag 941 is a definition related to the input of the “doSend” call of the FTP transmission provider, and indicates that “Document” is received from the data whose ID is “foo”, that is, the output of “doScan”. Similarly, the Parameter tag 942 is a definition related to the input of the “doScan” call of the FTP transmission provider, and indicates that “String” is received from the data whose ID is “bar”, that is, the output of “doOCR”.

FIG. 10 is a flowchart illustrating a data processing method of the information processing apparatus according to the present exemplary embodiment. This example is a series of processing examples on the MFP 101 shown in FIG. Note that the CPU 311 reads out the program stored in the HDD 314 of the PC 103 to the RAM 313, analyzes, and executes the program, thereby executing each step of the flowchart of FIG.
In step S1001, the workflow processing unit 430 receives a workflow execution instruction from the user. In step S1002, the workflow definition file 440 corresponding to the execution instruction is read.
In step S <b> 1003, the workflow processing unit 430 instructs the function provider management unit 420 to search for a function provider described in the workflow definition file 440. The workflow definition file 440 includes the three search conditions for “function provider whose function type is scan”, “function provider whose function type is OCR”, and “function provider whose function provider ID is SEND_FTP”. Specify and indicate.

In step S1004, the function provider management unit 420 extracts function providers that match the search conditions based on the function provider information table 423. If there are a plurality of scan providers that match the search condition, the scan provider with the highest priority is set as the search result. In this example, it is assumed that the standard scan provider 411, the embedded OCR provider 414, and the FTP transmission provider 4110 are extracted. In step S1005, the function provider management unit 420 notifies the workflow processing unit 430 of the search result of the function provider.
In step S1006, the workflow processing unit 430 issues a scan instruction to the standard scan provider 411 of the search result.
In step S1007, the standard scan provider 411 that has received the scan instruction in step S1006 from the workflow processing unit 430 executes a scan according to the instruction. In step S <b> 1008, the workflow processing unit 430 issues an OCR instruction to the search result embedded OCR provider 413. In step S1009, the embedded OCR provider 413 that has received the OCR instruction in step S1008 from the workflow processing unit 430 executes OCR in accordance with the instruction.

  In step S1012, the workflow processing unit 430 issues a UI display instruction to the UI display conversion system provider 417. Then, the UI display conversion system provider 417 that has received the UI display instruction in S1013 converts the process to display the UI during the process of the embedded OCR provider 413 according to the instruction. In step S1011, the FTP transmission provider 4110 that has received the transmission instruction in step S1010 from the workflow processing unit 430 performs transmission execution processing in accordance with the instruction.

FIG. 11 is a diagram showing a UI screen displayed on the operation unit 219 shown in FIG. This example is an example of a UI displayed on the operation unit 219 by the workflow processing unit 430 during the UI non-owning function provider processing defined in the workflow definition file 440. The timing at which the UI screen is displayed will be described with reference to FIG.
In FIG. 11, the execution process display screen 1101 is displayed on the operation unit 219 during the OCR process, that is, the UI non-owner function provider process. Reference numeral 1102 denotes a button for hiding the screen. When the button for hiding this screen 1102 is pressed, the display of the execution processing display screen 1101 can be temporarily hidden.

As described above, when creating a workflow in which a plurality of extension softwares are combined according to the procedure described above, a function provider that has a UI may be combined with a provider that does not have a UI. Specifically, this corresponds to the case where the button 1502 of the Scan & OCR & FTP transmission application in FIG. 12 is designated.
At that time, the user who creates the workflow simply creates the workflow and provides a unified flow definition operation feeling to the user who expects a unified UI display when the flow is executed with a unified workflow definition operation. It becomes possible to do.
In other words, when the UI possessing function provider is defined, the UI display is displayed on the UI non possessing function provider, thereby unifying the operability of execution of the flow application. On the other hand, when the UI possessing function provider is not defined, the UI display is not performed for the UI non-retaining function provider. For this reason, it becomes possible to provide the user with a unified operability in the execution of the flow application.

FIG. 12 is a diagram showing a UI screen displayed on the operation unit 219 shown in FIG. In this example, a description will be given of a difference in screen transitions for showing a difference in effect when the invention is not applied and when the invention is applied.
[First UI screen transition]
First, when the present embodiment is not applied, how the UI screen display changes as the workflow progresses will be described.
In FIG. 12, the screen transition when the invention is not applied is a TOP menu screen 1501, a scan setting screen 1510, and an FTP transmission screen 1520. First, the user presses a Scan & OCR & FTP transmission application button 1502 on the TOP menu screen 1501. The operation of this button 1502 corresponds to the workflow execution instruction in S1001. Then, the screen transits to a scan setting screen 1510. Since the contents that can be set on this screen are not related to the effects of the present invention, the description is omitted. When the next button 1511 on the scan setting screen 1510 is pressed, a scan execution instruction in S1007 is performed.
Subsequently, an OCR execution instruction in S1008 is performed. At this time, since the operation unit 219 displays the TOP menu screen 1501, the status of the OCR execution instruction in S1008 is not displayed. For this reason, the user cannot grasp what is happening and feels uncomfortable in the operability. Next, when the OCR execution process of S1009 is completed, a transmission instruction of S1010 is performed, and the operation unit 219 displays an FTP transmission screen 1520. Here, reference numeral 1521 denotes a cancel button which is pressed when canceling the FTP transmission processing.

[Second UI screen transition]
Next, how the UI screen display transitions with the progress of the workflow according to the present embodiment will be described.
The TOP menu screen 1530 is the same as the TOP menu screen 1501, the scan setting screen 1540 is the same as the scan setting screen 1510, and the FTP transmission screen 1560 and the FTP transmission screen 1520 are the same.

First, the user presses a Scan & OCR & FTP transmission application button 1502 on the TOP menu screen 1530. The operation of this button 1502 corresponds to the workflow execution instruction in S1001. Then, the screen transits to a scan setting screen 1540. Since the contents that can be set on this screen are not related to the effects of the present invention, the description is omitted.
When the next button 1541 on the scan setting screen 1540 is pressed, a scan execution instruction in S1007 is performed. Subsequently, an OCR execution instruction in S1008 is performed. At that time, the operation unit 219 displays an execution process display screen 1550. The execution process display screen 1550 is the same as the execution process display screen 1101 of FIG.
Therefore, the status of the OCR execution instruction in S1008 is displayed, the user can grasp what is happening, and feel unity in operability.
Next, when the OCR execution process of S1009 is completed, a transmission instruction of S1010 is performed, and the operation unit 219 displays an FTP transmission screen 1560. As shown in FIG. 12, by applying the present invention, the processing status is displayed in the processing that the user expects to display, so that a sense of unity in operability can be provided.

[Second Embodiment]
Hereinafter, a second embodiment for carrying out the present invention will be described with reference to the drawings.
FIG. 13 is a flowchart showing a control method of the data processing apparatus according to the present embodiment. In this process, the CPU 311 reads out the program stored in the HDD 314 of the PC 103 to the RAM 313, analyzes, and executes the program, thereby executing each step of the flowchart of FIG. The difference from the first embodiment is S1216 and S1217.

  FIG. 14 is a diagram showing a UI screen displayed on the operation unit 219 shown in FIG. This example is an example of a UI displayed on the operation unit 219 by the workflow processing unit 430 during the UI non-owning function provider processing defined in the workflow definition file 440. The basic behavior of the UI 1301 is the same as that of the UI 1101.

  In FIG. 14, as a difference, 1304 is a button for canceling the processing. Specifically, when this button 1304 is pressed with respect to the embedded OCR provider 413 of the currently embedded OCR function provider, “stop” in the Available tag 1450 described in FIG. The process is called and the OCR process can be stopped.

  In the present embodiment, the example in which the OCR process is stopped has been described. If the UI non-owning function provider defines only the I / F, it is possible to define not only stop processing but also processing related to execution processing such as suspension, suspension, and resumption, and display the UI. Needless to say, it can be converted.

  FIG. 15 is a specific description example of the workflow definition file in the present embodiment. 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. The description other than 1450 is the same as the description of FIG.

  In FIG. 15, an Available tag 1450 means that a process that can be operated from the screen is defined in the OCR function provider 413 as a provider having no UI possession function being processed. This example indicates that a process “stop” is defined as a process for canceling the OCR process.

As described above, the user who creates the workflow can create the workflow without knowing information related to the processing of the UI non-owning function provider (for example, the existence of the cancellation processing).
As a result, it is possible to define a workflow that allows the user to cancel the process of the non-UI function provider without being aware of the UI display of the function provider. Thus, as an effect, when a UI non-owning function provider is incorporated into a workflow, the system provides a UI to suspend the UI non-owning function provider. As a result, the user can enjoy a unified operational feeling.

  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.

100 MFP
102 Server 103 PC

Claims (11)

A data processing device,
A creation means for creating a workflow definition file that combines multiple function providers;
A determination means for determining whether the function provider defined in the workflow definition file created by the creation means includes a function provider with UI display and a function provider without UI display;
When the determination unit determines that a function provider without a UI display is included, a UI screen indicating the state of the specific process while the function provider without the UI display is executing a specific process Additional means to add the process to display the workflow definition file,
A data processing apparatus comprising:   When the determining unit determines that a function provider that does not include a UI display is not included, the adding unit does not add a process for displaying a UI screen indicating a state of a specific process to the workflow definition file. The data processing apparatus according to claim 1.   When the determination means determines that a function provider without UI display is included, if the specific process by the function provider without UI display is a process that can be stopped, the additional means The data processing apparatus according to claim 1, wherein a process for displaying a button for accepting cancellation of the specific process is added to a UI screen indicating a process state.   The data processing apparatus according to claim 1, wherein the plurality of function providers include a scan provider, an OCR provider, a transmission provider, a preview provider, and a UI display provider.   The data processing apparatus according to claim 4, wherein the OCR provider is a function provider not accompanied by a UI display. An information processing apparatus that executes a specific process described in a created workflow definition file using a plurality of function providers,
Workflow processing means for instructing one of function providers selected from the plurality of providers to start a specific process;
If any function provider executed by the workflow processing means includes UI screen display processing by a specific function provider, the instruction to display a UI screen associated with the function provider is specified. An information processing apparatus characterized by instructing a function provider.   The specific function provider is a UI display provider that displays a UI screen associated with the specific process while a specific process is being executed by the function provider without UI display. Item 7. The information processing device according to Item 6. A data processing device,
A creation process to create a workflow definition file that combines multiple function providers,
A determination step of determining whether the function provider defined in the workflow definition file created in the creation step includes a function provider with UI display and a function provider without UI display;
When it is determined in the determination step that a function provider without a UI display is included, a UI indicating a state of the specific process while the function provider without the UI display is executing a specific process An additional process to add a process to display the screen to the workflow definition file,
A data processing method for a data processing apparatus, comprising: A data processing method for an information processing apparatus that executes a specific process described in a created workflow definition file using a plurality of function providers,
A workflow processing step of instructing any one of the function providers selected from the plurality of providers to start a specific process;
If any of the function providers executed in the workflow processing step includes a UI screen display process by a specific function provider, an instruction to display a UI screen associated with the function provider is given. A data processing method of an information processing apparatus, characterized by instructing a specific function provider.   A program causing a computer to execute the data processing method of the data processing apparatus according to claim 8.   A program causing a computer to execute the data processing method of the information processing apparatus according to claim 9.

Images