JP2018156596A - Information processing device, information processing program and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently enable the execution of workflow in the case of being able to use a plurality of services to execute the workflow.SOLUTION: An information processing device includes: a first execution part for executing workflow showing a process procedure of one or more processes; a creation part for creating first workflow in which the first execution part executes all processes, and second workflow including external workflow and corresponding to process contents of the first workflow in the case that the first workflow includes a process compatible with the external workflow to be executed by an external second execution part; an acquisition part for acquiring at least a load of the first execution part between a load of the first execution part and the load of the second execution part; and a control part for controlling the execution of the workflow by the execution part. The control part uses the load of the first execution part acquired by the acquisition part to select which is to be executed between the first workflow and the second workflow.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an information processing apparatus, an information processing program, and an information processing system.

  2. Description of the Related Art Conventionally, operations and the like are performed using a workflow that defines a processing procedure using one or more processes. For example, a technique for executing a workflow in an on-premises system completed within an organization or the like is known. Patent Document 1 discloses a technique for executing a workflow in a cloud service provided on the Internet.

  Furthermore, Patent Document 2 discloses a technique for executing a workflow by using an on-premises system and a cloud service together. In Patent Document 2, among the processes included in the workflow, the processes executed by the cloud service and the processes executed by the on-premises system are identified, the order of the processes is rearranged, and the processes executed by the cloud service are summarized. ing. According to the technique of Patent Document 2, communication processing between a cloud service and a device in an on-premises system can be suppressed.

  By the way, for example, a workflow having the same function may be provided by a first service based on an on-premises system and a second service such as a cloud service. In the conventional technology, even in such a case, only the workflow provided by the service selected when the user defines the workflow can be executed between the first service and the second service.

  For example, a user selects a workflow provided by a first service, and a high-load process is executed on a server that executes the workflow process in the system of the first service, while a workflow is executed in the second service. Consider the case where the above process is not performed and the load is low. In the conventional technique, even in such a case, the workflow is executed on the server in the first service system according to the user's selection. For this reason, there is a possibility that problems such as a long time required for completion of the processing by the workflow and a stop of the entire system due to a memory shortage may occur. This problem cannot be solved even in Patent Document 3 described above.

  The present invention has been made in view of the above, and an object of the present invention is to enable efficient execution of a workflow when a plurality of services can be used for execution of the workflow.

  In order to solve the above-described problems and achieve the object, the present invention executes a first execution unit that executes a workflow indicating a processing procedure of one or more processes, and all the processes are executed by the first execution unit. The first workflow, and the first workflow includes a process compatible with the external workflow executed by the external second execution unit, the external workflow is included, and the first workflow corresponds to the processing content A creation unit that creates a second workflow, an acquisition unit that acquires at least a load of the first execution unit among a load of the first execution unit and a load of the second execution unit, and a workflow of the execution unit A control unit that controls execution, and the control unit selects which of the first workflow and the second workflow to execute using the load of the first execution unit acquired by the acquisition unit Do

  According to the present invention, when a plurality of services can be used for executing a workflow, the workflow can be efficiently executed.

FIG. 1 is a block diagram illustrating a configuration of an example of an information processing system according to the embodiment. FIG. 2 is a block diagram illustrating a hardware configuration of an example of a server applicable to the embodiment. FIG. 3 is a functional block diagram illustrating an example of functions of the on-premises and cloud servers according to the embodiment. FIG. 4 is a flowchart illustrating an example of workflow creation processing according to the embodiment. FIG. 5 is a flowchart illustrating an example of a process for confirming the existence of a compatible workflow according to the embodiment. FIG. 6 is a flowchart illustrating an example of processing for executing a workflow by the on-premises server according to the embodiment.

  Exemplary embodiments of an information processing apparatus, an information processing program, and an information processing system will be described below in detail with reference to the accompanying drawings. FIG. 1 illustrates an exemplary configuration of an information processing system according to an embodiment. In FIG. 1, the information processing system 1 includes a server 20 connected to a network 2 by, for example, a LAN (Local Area Network), and a server 30 connected from the network 2 via the Internet 3. The information processing system 1 may further include an MFP (Multi Function Printer) 10 and a personal computer (PC) 40 connected to the network 2.

  The network 2 is a so-called on-premises network closed in, for example, one organization, and the server 20 provides services in the on-premises system. The MFP 10 is a multifunction machine that realizes a plurality of functions such as a printer function, a scanner function, a copying function, and a FAX function in a single casing. The PC 40 is a general personal computer, and can log in to the server 20 and use the functions of the server 20. The PC 40 can also transmit a print job to the MFP 10. The server 30 is a server on the cloud network.

  Here, the server 20 provides processing unique to the organization, such as processing for the business of the organization, to the on-premises system. On the other hand, the server 30 provides general-purpose processing for use by a plurality of different on-premises systems (organizations) connected to the cloud network.

  In such a configuration, the information processing system 1 can provide a service based on a workflow that defines a processing procedure based on one or more processes. In the workflow (WF), components for executing processing and the order of components are defined. For example, consider a workflow in which processing for converting image data into PDF (Portable Document Format) data and transferring the converted PDF data to a predetermined destination using an electronic mail is considered. In this case, for example, a PDF conversion component that performs PDF conversion and an e-mail transmission component that transmits data to a predetermined destination by e-mail are defined in the workflow.

  Workflow definitions and components are stored on servers 20 and 30. The workflow may be defined using only components stored in the server 20 or may be defined using only components stored in the server 30. Furthermore, the workflow may be defined by mixing components stored in the server 20 and components stored in the server 30.

  For example, the MFP 10 can request the server 20 or the server 30 to execute a workflow. For example, the above-described workflow in which processing for converting image data into PDF data and transferring it to a predetermined destination by e-mail is applied to the image data acquired by the scanner function of the MFP 10. In this case, the MFP 10 acquires image data by the scan function, accesses the server 20 and requests execution of the workflow. In response to this request, the server 20 calls the workflow, executes the PDF conversion component according to the workflow definition, converts the image data acquired by the scan function into PDF data, and then executes the email transmission component. Then, the PDF data converted by the PDF conversion component is transmitted to a designated destination by electronic mail.

  As described above, various functions can be easily executed by using the workflow.

  In the information processing system 1 according to the embodiment, when a workflow is created in the on-premises server 20, a workflow using only the components stored in the server 20 (referred to as a first workflow) is created. At the same time, in the information processing system 1 according to the embodiment, when creating a workflow in the server 20, components that are compatible with the workflow or components stored in the server 30 on the cloud network among the components included in the workflow. A workflow (referred to as a second workflow) that replaces the workflow or component held by the server 30 is also created. The first workflow is presented to the workflow request source, for example, the MFP 10.

  In addition, when the first workflow is executed, the server 20 acquires at least a load related to the workflow execution in the server 20 and executes the first workflow based on the acquired load, or the server 30 stores the load. Decide whether to execute a second workflow that includes the workflow or component. Thereby, in the information processing system 1 according to the embodiment, when a plurality of services can be used for execution of the workflow, the processing by the workflow can be efficiently executed.

  FIG. 2 shows an exemplary hardware configuration of the server 20 applicable to the embodiment. 2, the server 20 includes a CPU (Central Processing Unit) 2000, a ROM (Read Only Memory) 2001, a RAM (Random Access Memory) 2002, a storage 2003, and a communication I / F 2004. The buses 2010 are communicably connected to each other. The storage 2003 is a storage medium configured by a hard disk drive or a nonvolatile semiconductor memory. The storage 2003 stores various programs and data for the CPU 2000 to operate.

  The CPU 2000 operates using the RAM 2002 as a work area according to a program stored in advance in the storage 2003 or the ROM 2001, and controls the overall operation of the server 20. A communication I / F 2004 controls communication via the network 2 in accordance with an instruction from the CPU 2000.

  In the example of FIG. 2, the storage 2003 is shown as being built in the server 20, but this is not limited to this example. For example, the storage 2003 may be an external storage device connected directly to the server 20 or via the network 2. 1 and 2 show that the server 20 is configured by one computer, this is not limited to this example, and the server 20 includes a plurality of computers distributed. You may comprise by operating.

  Further, the server 30 on the cloud network can also be realized with the same configuration as the server 20 shown in FIG. 2, and thus detailed description thereof is omitted here.

  FIG. 3 is a functional block diagram illustrating an example of the functions of the servers 20 and 30 according to the embodiment. 3, the on-premises server 20 includes a communication unit 200, an acquisition unit 201, a creation unit 202, a management unit 203, an execution unit 204, a WF (workflow) definition storage unit 210, and a component storage unit 220. ,including.

  Among these, the WF definition storage unit 210 and the component storage unit 220 are configured using a predetermined area of the storage 2003, for example. In addition, the communication unit 200, the acquisition unit 201, the creation unit 202, the management unit 203, and the execution unit 204 are formed by executing the information processing program according to the embodiment on the CPU 2000. Not limited to this, a part or all of the communication unit 200, the acquisition unit 201, the creation unit 202, the management unit 203, and the execution unit 204 may be configured by hardware circuits that operate in cooperation with each other.

  An information processing program for realizing each function in the server 20 is a file in an installable format or an executable format, and is read by a computer such as a CD (Compact Disk), a flexible disk (FD), and a DVD (Digital Versatile Disk). It is provided by being recorded on a possible recording medium. However, the present invention is not limited thereto, and the operation program may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. Further, the operation program may be provided or distributed via a network such as the Internet.

  The operation program has a module configuration including the above-described units (communication unit 200, acquisition unit 201, creation unit 202, management unit 203, and execution unit 204). As actual hardware, the CPU 2000 reads the operation program from a storage medium such as the storage 2003 and executes the operation program, whereby the above-described units are loaded onto the main storage device such as the RAM 2002, and the communication unit 200, the acquisition unit 201, A creation unit 202, a management unit 203, and an execution unit 204 are generated on the main storage device.

  In FIG. 3, the WF definition storage unit 210 stores WF (workflow) definitions 211a, 211b,. Each of the WF definitions 211a, 211b,... Included in the WF definition storage unit 210 identifies a combination of one or more components, information indicating the order of processing by each component, preset information, and a workflow. Are included in association with each other.

  The component storage unit 220 stores the components 221a, 221b,... For use in the WF definitions 211a, 211b,. Each component 221a, 221b,... Includes a component ID for identifying the component and component version information in association with each other.

  The communication unit 200 controls the communication I / F 2004 to perform communication with the network 2. Thus, the communication unit 200 can connect to the Internet 3 via the network 2 and communicate with the server 30 via the network 2 and the Internet 3. The acquisition unit 201 acquires a load related to execution of a workflow in the server 20. The acquisition unit 201 can further acquire a load related to the execution of the workflow in the server 30.

  The creation unit 202 creates the WF definitions 211a, 211b,... Using the components 221a, 221b,. The creation unit 202 causes the WF definition storage unit 210 to store the created WF definitions 211a, 211b,. The management unit 203 manages each WF definition 211a, 211b,... Stored in the WF definition storage unit 210 based on, for example, a workflow ID. Further, the management unit 203 manages each component 221a, 221b,... Stored in the component storage unit 220 based on the component ID and version information.

  The execution unit 204 executes a specified workflow based on a user operation or a specific event. For example, the execution unit 204 acquires the WF definition specified from the WF definitions 211a, 211b,... Managed by the management unit 203 in accordance with an instruction from the MFP 10, and acquires each component included in the acquired WF definition. Run.

  In FIG. 3, the server 30 on the cloud network includes a communication unit 300, a management unit 301, an execution unit 302, a WF definition storage unit 310, and a component storage unit 320. Among these, the communication unit 300, the management unit 301, and the execution unit 302 are realized by operating predetermined programs on the CPU included in the server 30. The WF definition storage unit 310 and the component storage unit 320 use a predetermined storage area of the storage provided in the server 30.

  The WF definition storage unit 310 stores WF definitions 311a, 311b,. The configuration of each WF definition 311a, 311b,... Is the same as that of the WF definition 211a, 211b,. The component storage unit 320 stores the components 321a, 321b,... For use in the WF definitions 311a, 311b,. The management unit 301 manages the WF definitions 311a, 311b,... Stored in the WF definition storage unit 310, and the components 321a, 321b,.

  The communication unit 300 controls the communication I / F included in the server 30 and performs communication with the Internet 3. Thus, the communication unit 300 can connect to the network 2 via the Internet 3 and communicate with the server 20 via the Internet 3 and the network 2.

  The execution unit 302 executes a specified workflow based on a specific event. For example, the execution unit 302 acquires the WF definition specified from the WF definitions 311a, 311b,... Managed by the management unit 301 in accordance with an instruction from the server 20, and each component included in the acquired WF definition Execute.

  Here, the component 221 ′ stored in the component storage unit 220 of the server 20 is defined in each WF definition 311a, 311b,... Stored in the WF definition storage unit 310 with respect to the execution unit 302 of the server 30. The execution of the workflow can be instructed. Further, each workflow defined in each WF definition 311a, 311b,... Stored in the WF definition storage unit 310 in the server 30 is, for example, in accordance with an instruction from the component 221 ′ of the server 20, for example, the WF definition 211a of the server 20. , 211b,... Can be executed as components.

  The components 211a, 211b,... Included in the server 20 and the components 311a, 311b,. It can be done.

(Processing according to the embodiment)
Next, processing according to the embodiment will be described. FIG. 4 is a flowchart illustrating an example of workflow creation processing according to the embodiment. The process according to the flowchart shown in FIG. 4 is executed by, for example, the creation unit 202 in the on-premises server 20.

  In step S100, the creation unit 202 creates a workflow definition of an on-premises workflow (WF) in response to an instruction from the PC 40, for example. The on-premises workflow is a workflow executed in the server 20 connected to the on-premises network 2. The creation unit 202 creates a workflow definition of an on-premises workflow using, for example, the components 221a, 221b,... Stored in the component storage unit 220 of the server 20.

  At this time, the creation unit 202 can perform a setting for prohibiting execution of the created workflow in the server 30 on the cloud network outside the on-premises network 2. For example, when a workflow to be created includes processing for handling confidential information, an application that prohibits execution of the workflow in the server 30 can be considered. For example, the creation unit 202 sets a prohibition flag indicating prohibition of execution outside the on-premises network 2 in the WF definition of the created workflow.

  In the next step S101, the creation unit 202 saves the on-premises workflow (WF definition) created in step S100 in the WF definition storage unit 210. In the next step S102, the creation unit 202 analyzes the on-premises workflow (hereinafter, target workflow) saved in step S101.

  In the next step S103, the creation unit 202 determines whether the target workflow can be executed by the server 30 on the cloud network based on the analysis result in step S102. For example, when the prohibition flag is included in the target workflow, the creation unit 202 determines that the target workflow is not executable in the server 30 (step S103, “No”), and ends the series of processes according to the flowchart of FIG. Let On the other hand, if the creation unit 202 determines in step S103 that the target workflow can be executed by the server 30 (step S103, “Yes”), the process proceeds to step S104.

  In step S104, the creation unit 202 acquires one of the components included in the target workflow as the target component, and analyzes the acquired target component. In the next step S105, the creation unit 202 confirms whether there is a workflow compatible with the target component in the WF definition storage unit 310 of the server 30 on the cloud network based on the analysis result of the target component. Details of the processing in step S105 will be described later.

  In the next step S106, as a result of the confirmation in step S105, the creation unit 202 stores the workflow definition of the workflow compatible with the target component (hereinafter, compatible workflow) in the WF definition storage unit 310 of the server 30. It is determined whether or not. If it is determined that it has not been saved (step S106, “No”), the process proceeds to step S108. On the other hand, if the creation unit 202 determines in step S106 that the data has been saved (step S106, "Yes"), the process proceeds to step S107.

  In step S107, the creation unit 202 creates a replacement workflow in which the target component is replaced with a compatible workflow on the server 30 that is compatible with the target workflow in the target workflow, and the workflow definition of the created replacement workflow is Save in the WF definition storage unit 210. That is, the WF definition storage unit 210 stores the WF definition of the target workflow and the WF definition of the replacement workflow corresponding to the target workflow.

  In step S107, if a replacement workflow corresponding to the target workflow already exists, the workflow definition of the replacement workflow is updated with the workflow definition of the compatible workflow.

  In the next step S108, the creation unit 202 determines whether or not the processing in steps S104 to S107 has been completed for all components included in the target workflow. When it determines with not having completed (step S108, "No"), the preparation part 202 returns a process to step S104, and performs the process after step S104 about the next component contained in an object workflow.

  On the other hand, when the creation unit 202 determines that the processing in steps S104 to S107 has been completed for all components included in the target workflow (step S108, “Yes”), the series of processing in the flowchart of FIG. .

  FIG. 5 is a flowchart illustrating an example of a process for confirming the existence of a compatible workflow according to the embodiment. The process according to the flowchart of FIG. 5 is a process executed in step S105 of the flowchart of FIG. 4 described above.

  In step S200 and step S201, the creation unit 202 acquires the component ID and version information of the target component. In step S202, the creation unit 202 refers to the compatible component check table based on the acquired component ID and version information.

  The compatible component check table includes components 221a, 221b,... Stored in the component storage unit 220 of the on-premises server 20, and WF definitions 311a, 311b, stored in the WF storage unit 310 of the server 30 on the cloud network. In each workflow by..., An entry indicating a pair of compatible component and workflow is stored.

  More specifically, the compatible component check table stores an entry associated with the workflow ID of the workflow on the cloud network that is compatible with the component, using the component ID and version information of the on-premises component as a key. . This compatible component check table is created in advance and stored in the server 30 on the cloud network, for example.

  In the next step S203, the creation unit 202 determines whether or not an entry corresponding to the component ID and version information acquired in steps S200 and S201 exists in the compatible component check table. When it determines with existing (step S203, "Yes"), the preparation part 202 makes a process transfer to step S205.

  In step S205, the creation unit 202 acquires the workflow ID of the workflow on the cloud network stored in the entry determined to exist as the workflow ID of the compatible workflow. When the creation unit 202 acquires the workflow ID of the compatible workflow, the creation unit 202 ends the process according to the flowchart of FIG. 5 and shifts the process to step S106 in the flowchart of FIG.

  On the other hand, when it is determined in step S203 that the corresponding entry does not exist (step S203, “No”), the creation unit 202 shifts the process to step S204.

  In step S204, the creation unit 202 refers to the on-premises compatible component check table based on the component ID and version information acquired in steps S200 and S201. The on-premises compatible component check table is a table having the same configuration as the above-described compatible component check table, and is stored in the on-premises server 20.

  For example, in the on-premises workflow service, when there is a custom-made component on-premises, a combination of workflows on the cloud network corresponding to the custom-made component is registered in the on-premises compatible component check table. For the custom component, for example, a custom plug-in for adding a function to the MFP 10 can be applied. As a result, this custom plug-in process may also be executed on-premises.

  When the reference to the on-premises compatible component check table is completed in step S204, the creating unit 202 shifts the processing to step S205 described above.

  FIG. 6 is a flowchart illustrating an example of processing executed by the execution unit 204 in the server 20 according to the embodiment. The workflow executed here is a workflow created as a target workflow in the flowchart of FIG. 4 described above, and a corresponding replacement workflow is also created and saved.

  In step S300, the execution unit 204 determines whether the server 30 on the cloud network can execute a process based on the target workflow that is an on-premises workflow (for example, a process based on a replacement workflow). If the prohibition flag is included in the workflow definition of the target workflow, the execution unit 204 determines that the server 30 cannot execute the process based on the target workflow (step S300, “No”), and the process is stepped. The process proceeds to S307.

  In step S307, the execution unit 204 executes an on-premises workflow, that is, a target workflow, and ends a series of processes according to the flowchart of FIG.

  On the other hand, when the execution unit 204 determines that the process based on the target workflow is executable in the server 30 (step S300, “Yes”), the execution unit 204 shifts the process to step S301. In step S301, the execution unit 204 requests the acquisition unit 201 to acquire a load related to the workflow execution of the server 20. In the next step S302, the acquisition unit 201 determines whether or not the load comparison target is the server 30 on the cloud network in response to the request. If the acquisition unit 201 determines that the load comparison target is not the server 30 (step S302, “No”), the process proceeds to step S304.

  On the other hand, if the acquisition unit 201 determines that the comparison target is the server 30 (step S302, “Yes”), the acquisition unit 201 moves the process to step S303, and acquires the load related to the workflow execution of the server 30. When acquiring the load related to the workflow execution of the server 30, the acquiring unit 201 shifts the processing to step S304.

  In the process of step S302, it is assumed that whether the load comparison target is the server 30 on the cloud network is determined in advance.

  In step S304, the acquisition unit 201 compares the acquired server 20 or the load related to workflow execution of the servers 20 and 30. In the next step S305, the acquisition unit 201 determines whether to execute the workflow on the server 30 on the cloud network according to the load comparison result by the acquisition unit 201 in step S304.

  If the acquisition unit 201 determines that the workflow is to be executed by the server 30 (step S305, “Yes”), the acquisition unit 201 shifts the processing to step S306. In step S306, the execution unit 204 executes a cloud workflow, that is, a replacement workflow. On the other hand, when determining that the workflow is not executed on the server 30 (step S305, “No”), the acquisition unit 201 shifts the processing to step S307. In step S307, the execution unit 204 executes the on-premises workflow, that is, the target workflow.

  The comparison process in step S304 and the determination process in step S305 will be described more specifically. When the acquisition unit 201 determines in step S302 that the load comparison target is not the server 30, and the process directly proceeds from step S302 to step S304, the acquisition unit 201 compares the load related to workflow execution in the server 20 with a threshold value. For example, the acquisition unit 201 determines in step S305 that the cloud workflow is to be executed in step S305 when the number of jobs waiting to be processed in the server 20 is greater than or equal to a threshold (for example, 100 or more), and the process proceeds to step S306. Transition.

  Further, if the load comparison target is the server 30 in step S302 and the load of the server 30 is acquired in step S303, the acquisition unit 201 acquires the load of the server 20 acquired in step S301 and the load of the server 20 in step S303. The acquired load of the server 30 is compared. As a result of the comparison in step S304, the acquisition unit 201 causes the server 20 and the server 30 having the smaller load to execute the workflow corresponding to the server in step S305.

  That is, if the acquisition unit 201 obtains a comparison result indicating that the load on the server 30 is smaller than that on the server 20 in step S304, the acquisition unit 201 determines in step S305 that the cloud workflow is to be executed, and the process is performed in step S306. To migrate. On the other hand, if the acquisition unit 201 obtains a comparison result indicating that the load on the server 20 is smaller than that on the server 30 in step S304, the acquisition unit 201 determines in step S305 that the on-premises workflow is executed, and the process is performed in step S307. To migrate.

  As described above, in the information processing system 1 according to the embodiment, when creating a workflow definition, a target workflow using only an on-premises component as a component and a replacement workflow in which a part of the component is replaced with a cloud workflow. create. Then, the information processing system 1 executes the target workflow based on the load related to the workflow execution in the on-premises server 20 or the load related to the workflow execution in each of the server 20 and the cloud server 30 or executes a replacement workflow. Select whether to execute. Therefore, in the information processing system 1 according to the embodiment, when a plurality of services (for example, the on-premises server 20 and the cloud server 30) can be used to execute the workflow, the processing by the workflow is efficiently performed. It becomes executable.

  Each of the above-described embodiments is a preferred embodiment of the present invention, but is not limited thereto, and various modifications can be made without departing from the gist of the present invention.

1 Information processing system 2 Network 3 Internet 10 MFP
20, 30 Server 40 PC
200, 300 Communication unit 201 Acquisition unit 202 Creation unit 203, 301 Management unit 204, 302 Execution unit 210, 310 WF definition storage unit 220, 320 Component storage unit

Japanese Patent Laying-Open No. 2015-032043 JP 2014-056488 A

Claims (8)

A first execution unit that executes a workflow indicating a processing procedure of one or more processes;
A first workflow in which all processing is executed by the first execution unit;
When the first workflow includes a process compatible with an external workflow executed by an external second execution unit, the second workflow includes the external workflow and corresponds to the processing content of the first workflow When,
A creation section for creating
An acquisition unit that acquires at least the load of the first execution unit among the load of the first execution unit and the load of the second execution unit;
A control unit that controls execution of the workflow by the execution unit;
With
The controller is
An information processing apparatus that selects which of the first workflow and the second workflow to execute using the load of the first execution unit acquired by the acquisition unit. The controller is
The information processing apparatus according to claim 1, wherein the second workflow is selected when the load of the first execution unit is equal to or greater than a threshold value. The controller is
The information processing apparatus according to claim 1, wherein the second workflow is selected when a load on the second execution unit is smaller than a load on the first execution unit. The creating unit
4. The information processing apparatus according to claim 1, wherein one or more external workflows are associated with one of the processes included in the first workflow. 5. The creating unit
The information processing apparatus according to any one of claims 1 to 4, wherein one external workflow is associated with one or more processes included in the first workflow. The creating unit
The information processing apparatus according to claim 1, wherein the processing setting value included in the first workflow is associated with the setting value of the external workflow compatible with the processing. . An execution step for executing a workflow indicating a processing procedure of one or more processes;
A first workflow including one or more processes, wherein all the processes are executed by the execution step;
When the first workflow includes a process compatible with an external workflow executed by an external execution unit, the second workflow including the external workflow and corresponding to the processing content of the first workflow;
A creation step to create a
An acquisition step of acquiring at least a load due to the first execution step among the load due to the first execution step and the load of the external execution unit;
A control step for controlling execution of the workflow by the execution step;
An information processing program for causing a computer to execute
The control step includes
An information processing program that selects which of the first workflow and the second workflow to execute using the load of the first execution step acquired in the acquisition step. An information processing system including a first information processing device and a second information processing device,
The first information processing apparatus includes:
A first execution unit that executes a workflow indicating a processing procedure of one or more processes;
The second information processing apparatus
A second execution unit for executing the workflow;
A first workflow in which all processes are executed by the second execution unit;
When the first workflow includes a process compatible with the external workflow executed by the first execution unit, the second workflow includes the external workflow, and the first workflow corresponds to the processing content. ,
A creation section for creating
An acquisition unit that acquires at least the load of the first execution unit among the load of the first execution unit and the load of the second execution unit;
A control unit that controls execution of the workflow by the execution unit;
With
The controller is
An information processing system that selects which of the first workflow and the second workflow to execute using the load of the first execution unit acquired by the acquisition unit.

Images