JP2008310475A - Workflow cooperation method, workflow cooperation program, and workflow connector - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide efficient processing as to a system constructed by cooperating workflows. <P>SOLUTION: This work flow connector 2 stores a called side workflow, work in the called side workflow and a situation of the work, in a notification condition storage part, while correlated therewith as notification conditions, the notification condition is determined to be satisfied when a situation of the work notified from a called side workflow device 3b is consistent with the situation of the work read from the notification condition storage part, and a response notification to calling-out from the called side workflow device 3b is repeated to a calling side workflow device 3a, when the notification condition is satisfied. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a workflow cooperation method, a workflow cooperation program, and a workflow connection apparatus.

  The system within the company is the best choice at the time depending on the company's culture and growth background, such as the history of the company's business expansion, the transition of IT technology, and the fact that the system has been budgeted for each business / department. As a result, there are many cases where the system configuration is complicated.

  Regardless of the status of such systems, business is constantly changing to expand the business and to follow the market. In order to respond to the change, it is a natural requirement that the system in the company is also required to change. The idea of SOA (Service Oriented Architecture) was born as a more flexible method of responding to this requirement.

  SOA is a standardized interface such as a web service for each workflow that bundles a series of work (work processing) executed by each system of a company. It is simple from other systems and end-user web browsers and client software. The workflow can be called via the network through simple procedures.

  The workflow is an instance (execution process) of a business process definition described in BPML (Business Process Modeling Language) by a computer. Further, the interface of the Web service is described in a standardized standard such as WSDL (Web Service Definition Language), and can be used from an external system.

  A system to be linked based on the SOA concept is directly connected to an ESB (Enterprise Service Bus). The system exchanges messages with other systems through the ESB. In other words, the ESB is a way to handle message exchange between the systems to be linked together.

Note that the term ESB is a generic term for technologies aimed at linking systems, and does not indicate a specific specification or standard. Although there are various definitions of the current ESB, the following three functions are required at a minimum, and a system infrastructure having these functions can be said to be an ESB in a narrow sense.
(1) Registry (2) Message routing (3) Protocol and data format conversion

  (1) The registry is a function that centrally manages information of each system to be linked. For example, when requesting the ESB to send a message to another system, the physical location of the destination system stored in the registry can be acquired. Therefore, it is not necessary to specify the physical location of the destination system in each message transmission.

  (2) Message routing is a function for delivering a mediating message to a destination system based on information of each system stored in the registry. When routing, it is possible to set up a simple branching process such as changing the destination according to the argument in the message or a process of delivering the message to one system and then delivering it to another system.

  (3) The protocol and data format conversion is a function for converting the protocol and data format of the ESB according to the destination system. In ESB, protocols and data formats that can be used by each system are managed in the registry, and based on the information, the mediating message is converted into a format that can be interpreted by the destination system.

Non-Patent Document 1 proposes an adapter as means for connecting two different interfaces. The adapter performs data conversion and character code conversion from the legacy system to the service platform. As a result, the workflow can be called from both sides.
Hitachi, Ltd., “Hitachi middleware / platform software general site / Cosminexus service configuration”, [online], [Search April 27, 2007], Internet <URL: http://www.hitachi.co.jp/ Prod / comp / soft1 / cosminexus / products / lineup / sa / index.html>

  FIG. 9 is an explanatory diagram showing a workflow cooperation method in the synchronous method and the asynchronous method. Here, a description will be given of a procedure performed by a resident at a government office when moving, taking as an example a one-stop service that combines a plurality of government office procedures into one place. The caller workflow links the callee workflows by sequentially calling a plurality of callee workflows. Note that it is preferable to use a legacy system that is already in operation rather than newly developing a call destination workflow from the viewpoint of reducing development costs.

  The call destination workflow is configured by connecting one or more works (work processes executed by a computer). For example, the callee workflow in FIG. 9A is configured by sequentially connecting three works (a reception process, a section manager examination process, and a department manager examination process).

  FIG. 9A shows workflow cooperation by a synchronous method. Consider a case of creating a caller workflow (moving procedure) that links two existing callee workflows (moving procedure, moving procedure). In the synchronous method, when a workflow is called, the process waits for a response before proceeding to the next process. In the figure, communication such as calling and answering is indicated by dotted arrows. Therefore, the transfer procedure is executed after the transfer procedure is completed. Thereby, the transfer procedure can utilize the processing result of the transfer procedure.

  FIG. 9B shows workflow cooperation by an asynchronous method. In the asynchronous method, when a workflow call is made, it is possible to proceed to the next process without waiting for a response. Therefore, the transfer procedure is executed even if the transfer procedure is not completed. Thereby, since the transfer-in procedure and the transfer-out procedure are executed in parallel, both processes can be completed in an early time.

  As a feature common to both the synchronous method of FIG. 9A and the asynchronous method of FIG. 9B, the response of the callee workflow is the completion of the last work among the works constituting the callee workflow. Sometimes it is notified only once. This specification is defined by the fact that ESB does not manage the status of each work constituting the workflow to be called.

  However, depending on the contents of the workflow, there is a case where a wasteful waiting time occurs when the workflow is linked. For example, it is assumed that a “transfer certificate” is issued as a processing result of the “section manager examination process” of the transfer procedure, and rewriting to the resident's card database is executed as a process result of the “manager inspection process” of the transfer procedure. It is assumed that a “transfer certificate” is required in advance in the “acceptance process” of the transfer procedure.

  If a response is issued when the transfer manager's section manager review process is completed, the transfer procedure's reception process must be started without waiting for the transfer manager's department manager review process to end. Can be efficient.

  However, in the synchronous method of FIG. 9A, no response is notified in the “section manager review process” of the transfer procedure in the middle of the workflow, so the response notification is waited until the end of the “department manager review process” of the transfer procedure. It is inefficient.

  In the asynchronous method of FIG. 9B, the “acceptance process” of the transfer procedure is started without waiting for the completion of the “section manager examination process” of the transfer procedure, and the “transfer certificate” is issued. Because there is not, transfer procedure stops.

  As described above, when the callee workflow calls the callee workflow, the timing for notifying the response to the call from the callee workflow to the callee workflow is one time when the process of the callee workflow is completed. If it is only, it may be difficult to construct an efficient workflow linkage system.

  In particular, when there is at least one interactive work for a work constituting the workflow, the execution time of the work flow becomes long as a whole, and the response is delayed. The interactive work is a work that waits for input from the user. As a result, the caller workflow falls into a process stagnation.

  Therefore, the main object of the present invention is to realize efficient processing for a system constructed by linking workflows.

  In order to solve the above-described problem, the present invention provides a caller workflow apparatus that executes a caller workflow for a workflow that sequentially executes a work in which a business process definition for realizing a service based on SOA is instantiated, and the caller Communication is possible between a callee workflow device that executes a callee workflow started by being called from a workflow, and a workflow connection device that relays a response notification to the call from the callee workflow device to the caller workflow device. A workflow linkage method executed by a connected workflow system, wherein the workflow connection device associates the call destination workflow, the work in the call destination workflow, and the state of the work as notification conditions. Notification condition memory When the state of the work notified from the call destination workflow device matches the state of the work of the notification condition read from the notification condition storage unit, it is determined that the notification condition is satisfied. When the notification condition is satisfied, the response notification to the call from the callee workflow device is relayed to the caller workflow device. Other means will be described later.

  According to the present invention, it has become possible to realize efficient processing for a system constructed by linking workflows.

  FIG. 1 is an explanatory diagram showing a workflow cooperation method. Each workflow in FIG. 1 and the work that is a component thereof are the same as those described in FIG.

  The caller workflow (moving procedure) 102 includes a workflow call 102a that calls the callee workflow (transfer procedure) 101, a workflow response reception 102b that receives the response, and a workflow call 102c that calls the callee workflow (transfer procedure) 103 and the workflow call 102c. Workflow response reception 102d for receiving a response is executed in order.

  The callee workflow (transfer procedure) 101 is executed in the order of reception processing 101a → section manager examination processing 101b → department manager examination processing 101c. A “transfer certificate” is issued as a processing result of the section manager examination process 101b, and rewriting to the “resident card database” is executed as a process result of the department manager examination process 101c.

  The callee workflow (transfer procedure) 103 is executed in the order of the reception process 103a → the section manager examination process 103b → the department manager examination process 103c. It should be noted that processing result data such as “transfer certificate” and “resident card database” is exchanged in a separate route from the response in a shared database (not shown) in each call destination workflow.

  The workflow connection device 2 enables a response notification from each call destination workflow to the call source workflow 102 at an arbitrary timing. In addition, although two workflow connection apparatuses 2 are illustrated in the drawing, any number may be used as long as the number is one or more.

  First, a notification condition for executing a response notification is registered in advance with respect to the workflow connection apparatus 2. Next, for each work of each call destination workflow, every time a state transition such as the start of execution, during execution, or the end of execution occurs, the workflow connection device 2 is notified every time that the state transition has occurred. Then, the workflow connection apparatus 2 selects a notification that matches the notification condition from the state transitions notified each time, and notifies the caller workflow 102 of the notification. It can be said that the notification condition defines a correlation between workflows.

  FIG. 2 is a configuration diagram showing the workflow cooperation system of this embodiment. The workflow cooperation system includes a caller workflow device 3a, a plurality of callee workflow devices 3b, a workflow connection device 2, a setting device 5, and an operation device 6 that are connected to a network 9.

  The caller workflow device 3a links the workflows by calling the workflows respectively executed by the plurality of callee workflow devices 3b. The called destination workflow device 3b notifies the workflow connection device 2 of a response to the call. The workflow connection device 2 transfers a response that satisfies a preset notification condition to the caller workflow device 3a. The setting device 5 sets setting information such as a notification condition of the workflow connection device 2. The operation device 6 instructs the start of control for notifying a response.

  A shared database 8 for exchanging workflow processing results (for example, the “transfer certificate” described in FIG. 1) between a plurality of call destination workflow devices 3b is accessible from the plurality of call destination workflow devices 3b. It is configured. The shared database 8 may be one, or may be configured by preparing a plurality of databases and sharing access rights.

  FIG. 3 is an explanatory diagram showing details of each device constituting the workflow cooperation system of the present embodiment.

  FIG. 3A is a configuration diagram of the caller workflow device 3a.

  The caller workflow device 3a includes a CPU 31a, a main storage device 32a, and a database 33a. The main storage device 32a stores a program for configuring a work state monitoring unit 321a for monitoring a state during execution of a work every predetermined time, and a work execution unit 322a for executing and controlling the deployed work. The work state monitoring unit 321a starts state monitoring for the work constituting the workflow when the workflow is generated.

  The database 33a stores a business process definition storage unit 331a that defines the contents of a workflow that is executed by the own apparatus, and a work state table 332a that stores the state of each work constituting the workflow executed by the own apparatus. .

  FIG. 3B is a configuration diagram of the callee workflow device 3b. There may be three or more call destination workflow devices 3b linked to each other. The call destination workflow device 3b has the same configuration as that of the call source workflow device 3a, and the suffixes [a] and “b” of the reference numerals indicate the correspondence between the components. The reason for adopting the same configuration is that the roles of the call destination and the call source are not fixed, focusing only on a predetermined workflow, and if another workflow is focused, another role may be assigned. .

  FIG. 3C is a configuration diagram of the workflow connection device 2. The workflow connection device 2 may reduce the load by being activated in a plurality of ways.

  The workflow connection device 2 includes a CPU 21, a main storage device 22, and a database 23. The main storage device 22 includes a data conversion unit 221, a notification condition determination unit 222, and a program for configuring the message transmission unit 223.

  The database 23 is a notification condition table 231 that stores notification conditions for response messages, a work state integration table 232 that integrates and manages work states notified from each call destination workflow device 3b, and is referred to when communicating with each device. The communication management table 233 to be stored is stored.

  When the state update information written in the work state table 332b is sent from the work state monitoring unit 321b, the notification condition determination unit 222 associates the information with the host name of the called workflow device 3b, Write to integrated table 232.

  The notification condition determination unit 222 evaluates whether or not the state update information written in the work state integration table 232 satisfies the notification condition of the notification condition table 231. When the notification condition is satisfied, the data conversion unit 221 identifies the call destination workflow device 3a as the notification destination from the communication management table 233, and creates a response message converted into a format that can be processed by the notification destination.

  The message transmission unit 223 notifies the response message created by the data conversion unit 221 to the caller workflow device 3a. Further, the message sending unit 223 notifies the callee workflow device 3b that the response is returned to the callee workflow device 3b in which the notification condition is satisfied and the response of the subsequent workflow is not defined in another notification condition. The work state monitoring unit 321b state monitoring is terminated by sending the work state monitoring unit 321b of 3b.

  FIG. 4 is an explanatory diagram showing details of each device constituting the workflow cooperation system of the present embodiment. It should be noted that the processing units of each device may be distributed and arranged in independent devices, or may be concentrated on the same device.

  FIG. 4A is a configuration diagram of the setting device 5.

  The setting device 5 includes a CPU 51, a main storage device 52, and a magnetic disk device 53. The main storage device 52 stores a program for configuring the setting unit 521. The magnetic disk device 53 includes a communication destination definition file 531 that defines communication information for linking workflows, and a notification condition definition that defines under what conditions and what control is applied to the workflow state transition. A file 532 is stored.

  The setting unit 521 sets the created communication destination definition file 531 and notification condition definition file 532 in the magnetic disk device 53. The setting unit 521 registers each file set in the magnetic disk device 53 in the notification condition table 231, the work state integration table 232, and the communication management table 233 of the workflow connection device 2.

  FIG. 4B is a configuration diagram of the operation apparatus 6.

  The operation device 6 includes a CPU 61 and a main storage device 62. The main storage device 62 stores a program for configuring the operation operation unit 621 for starting and operating the workflow connection device 2 and the work state monitoring unit 321b.

  FIG. 5 is an explanatory diagram showing an outline of processing of the workpiece state monitoring unit 321b and the workpiece execution unit 322b.

  First, when the work execution unit 322b receives a workflow execution request from the workflow connection device 2 or the like, the work execution unit 322b instantiates the business process definition stored in the business process definition storage unit 331b and calls the call destination workflow (transfer procedure) 101 or the like. Run the workflow.

  Next, when the execution of the workflow is started, the work state monitoring unit 321b monitors the state transition between the works constituting the executed workflow, and when the state transition is detected as a change, the result is displayed in the work state table. Write to 332b. Note that the monitoring timing is, for example, at regular intervals.

  FIG. 6A shows an example of the communication management table 233. The communication management table 233 includes, for each called workflow device, the “host name” of the device and the “IP address” of the device. The “host name” stores a name that uniquely identifies the called workflow device. The “IP address” stores an IP address that uniquely identifies the location of the device on the network. That is, the communication management table 233 is a table for realizing name resolution (DNS: Domain Name System).

  FIG. 6B shows an example of the work state integration table 232. The work state integration table 232 includes a “host name” of each machine used for a call, a “call destination workflow ID” for specifying a call destination workflow, and a “call destination work ID” for specifying a work constituting the call destination workflow. The “call destination work state” indicating the work state specified by the work ID is stored in association with each other. The “host name” has the same contents in FIG. 6A and FIG.

  FIG. 6C shows an example of the notification condition table 231. The notification condition table 231 includes a “notification condition name” that represents a notification condition name, a “caller workflow ID” that identifies the caller workflow, and a “caller response return state” that represents the caller state when a response is returned. ”, Information on the call destination described in FIG. 6B (“ call destination workflow ID ”,“ call destination work ID ”,“ call destination work state ”), and“ calculation ”indicating the relationship between a plurality of notification conditions “Child” is stored in association with each other.

  In the notification condition table 231, one notification condition is registered per line. When defining an AND condition or an OR condition that extends over a plurality of notification conditions, the “notification condition name” has the same name in the plurality of notification conditions, and the “operator” has a relationship (AND, OR) between the notification conditions of each other. ) In the case of AND, the condition is indispensable in a plurality of conditions, and in the case of OR, one of the conditions satisfies the condition.

  The “caller response return state” indicates the state of the caller workflow. When it is not “waiting for response”, the notification is temporarily suspended until it becomes “waiting for response” without notifying the response.

  The processing for determining whether or not the notification condition is satisfied includes information on the call destination (“call destination workflow ID”, “call destination work ID”, “call” described in FIGS. 6B and 6C). This is realized by collating the previous work state ") with each other. It is determined that the notification condition is satisfied when the combination of the information on the call destinations matches each other in FIGS. 6B and 6C.

  For example, for information on the call destination, two pieces of information (transfer workflow, section manager examination work) match each other, but one piece of information ("execution start" and "complete" in the call destination work state) does not match. Therefore, the notification condition is not satisfied at this time.

  However, when the section manager examination work transitions from “at the start of execution” to “complete” and the transition is reflected in the work state integration table 232, the three pieces of information regarding the call destination completely match each other. At this time, it is determined that the notification condition is satisfied, and a response notification of “transfer workflow” is returned to the caller workflow device 3a.

  FIG. 7 is a flowchart showing processing performed by the work state monitoring unit 321b.

  First, a notification to start workflow cooperation is received from the workflow connection device 2 (S11). Next, the workflow is read from the business process definition storage unit 331b, and the workflow for monitoring the work state is held on the main storage device 32b (S12). Then, the workpiece status monitoring target is changed from the already monitored workpiece to the next monitoring workpiece, and the workpiece status monitoring target is determined (S13). If no workpiece has been monitored yet, the first workpiece is the monitoring target.

  Here, when the monitoring end notification is received from the workflow connection device 2 (Yes in S14), the processing is ended because the monitoring is not necessary. Thereby, when monitoring is unnecessary, the amount of wasteful processing can be reduced by interrupting monitoring. On the other hand, when the notification of the monitoring end is not received (S14, No), the process proceeds to S15.

  Then, the state of the work to be monitored is checked with reference to the work state table 332b at regular intervals. If the state has been updated due to the transition of the work state since the previous check (S15, Yes), the process proceeds to S16. . On the other hand, when the update has not been performed (S15, No), the process returns to S14.

  If the answer is Yes in S15, the workflow connection device 2 is notified of the update of the work status to be monitored detected in S15 (S16). Here, when processing of all the works constituting the workflow is completed (S17, Yes), a workflow completion notification is sent to the workflow connection apparatus 2 (S18). On the other hand, when there is an unfinished workpiece (S17, No), the process returns to S13.

  FIG. 8 is a flowchart showing processing performed by the workflow connection device 2 when the work state monitoring unit 321b is notified of the update of the work state.

  First, a work state update notification (S18) to be monitored is received from the work state monitoring unit 321b (S21). Next, the work state received in S21 is written to the work state integration table 232 (S22).

  Here, with reference to the notification condition table 231, it is determined whether or not the notification condition is satisfied (S23). First, when the condition is not satisfied (S23, No), the information wait state from the work state monitoring unit 321b is entered, and the process returns to S21 again. On the other hand, if the condition is satisfied, the process proceeds to S24.

  Then, the response message received in S21 is transmitted to the caller (S24). Note that the processing of S24 may be executed whenever the workflow is completed even if the notification condition is not satisfied. The purpose of this is to maintain compatibility with the specification in which a response is always returned at the end of the workflow in the synchronous and asynchronous linkage methods shown in FIG.

  According to the present embodiment described above, the workflow connection device 2 notifies the caller workflow as a response of the state transition of the callee workflow that satisfies the notification condition. As a result, since the call source workflow can receive a response at an appropriate timing, the call destination workflow can be started one after another at an appropriate timing without causing unnecessary waiting time. Therefore, the response timing in service cooperation can be changed flexibly.

  As described above, the method in which the workflow connection apparatus 2 exclusively executes the function for notifying the response is configured so that each call destination workflow directly notifies the call source workflow of the response. Compared to the direct correction method, there are the following advantages. In the direct correction method, after the callee workflows are executed, when the number of callee workflows to which new responses are notified increases, the callee workflows are stopped and a new response destination is newly set for the callee workflows. Registration will result in a system outage period.

  On the other hand, in the system in which the workflow connection device 2 is provided, it is not necessary to stop the call destination workflow only by newly adding response destinations to the notification conditions of the workflow connection device 2, so that the system operation stop period does not occur.

It is explanatory drawing which shows the cooperation system of the workflow regarding one Embodiment of this invention. It is a block diagram which shows the workflow cooperation system of this embodiment regarding one Embodiment of this invention. It is explanatory drawing which shows the detail of each apparatus which comprises the workflow cooperation system of this embodiment regarding one Embodiment of this invention. It is explanatory drawing which shows the detail of each apparatus which comprises the workflow cooperation system of this embodiment regarding one Embodiment of this invention. It is explanatory drawing which shows the process outline | summary of the workpiece | work state monitoring part and workpiece | work execution part regarding one Embodiment of this invention. It is a block diagram which shows an example of each table regarding one Embodiment of this invention. It is a flowchart which shows the process which the workpiece | work state monitoring part regarding one Embodiment of this invention performs. It is a flowchart which shows the process which a workflow connection apparatus performs when the update of a workpiece | work state is notified from the workpiece | work state monitoring part regarding one Embodiment of this invention. It is explanatory drawing which shows the cooperation system of the workflow in a synchronous system and an asynchronous system.

Explanation of symbols

2 Workflow connection device 221 Data conversion unit 222 Notification condition determination unit 223 Message transmission unit 231 Notification condition table 232 Work state integration table 233 Communication management table 3a Caller workflow device 321a Work state monitoring unit 322a Work execution unit 331a Business process definition storage unit 332a Work state table 3b Called workflow device 321b Work state monitoring unit 322b Work execution unit 331b Business process definition storage unit 332b Work state table 5 Setting device 6 Operation device 9 Network

Claims (10)

For workflows that execute work in which business process definitions for instantiating services based on SOA (Service Oriented Architecture) are instantiated,
A caller workflow device that executes a caller workflow, a callee workflow device that executes a callee workflow that is called and started from the caller workflow, and a call response notification from the callee workflow device to the caller A workflow linkage method executed by a workflow system configured by connecting a workflow connection device that relays to a workflow device in a communicable manner,
The workflow connection device is
The call destination workflow, the work in the call destination workflow, and the state of the work are associated with each other as a notification condition and stored in a notification condition storage unit,
When the work state notified from the callee workflow device matches the work state of the notification condition read from the notification condition storage unit, it is determined that the notification condition is satisfied,
A workflow cooperation method comprising: relaying the response notification to a call from the callee workflow device to the caller workflow device when the notification condition is satisfied. The workflow connection device further converts the response notification into a data format that can be processed by the caller workflow device in a step of relaying the response notification to the caller workflow device. The workflow linkage method described in 1. The workflow cooperation method according to claim 1, wherein the call destination workflow device further outputs the execution result of the call destination workflow to a shared database accessible from other call destination workflow devices. The workflow connection apparatus further ends the work state notification process for the caller workflow apparatus that satisfies all the notification conditions after the step of relaying the response notification to the caller workflow apparatus. The workflow cooperation method according to claim 1, wherein control is performed so that The workflow system is further configured by connecting operation devices to be communicable,
The operation device instructs the callee workflow device to start the work state notification step, and whether or not the notification condition is satisfied for the work state notified to the workflow connection device. 2. The workflow cooperation method according to claim 1, further comprising: instructing start of a step of relaying the response notification satisfying the notification condition to the caller workflow device. The workflow connection apparatus further stores, for the notification condition stored in the notification condition storage unit, the AND condition of the plurality of notification conditions or the operator indicating the OR condition in association with the plurality of notification conditions. The workflow cooperation method according to claim 1, wherein a plurality of the notification conditions are individually determined, and the determination result is comprehensively determined based on the condition indicated by the operator. In the step of relaying the response notification to the caller workflow device, the workflow connection device further waits for a response until the status of the caller workflow executed by the caller workflow device is not waiting for a response. The workflow cooperation method according to claim 1, wherein the response notification is suspended. The said workflow connection apparatus further notifies the said notification of a response to the said call origin workflow apparatus, when the completion notification of the said call destination workflow is received from the said call destination workflow apparatus. Workflow linkage method. A workflow cooperation program for causing each computer constituting the workflow system to execute the workflow cooperation method according to claim 1. For workflows that execute work in which business process definitions for instantiating services based on SOA (Service Oriented Architecture) are instantiated,
A caller workflow device that executes a caller workflow that is a workflow that sequentially executes workpieces, a callee workflow device that executes a callee workflow that is called from the caller workflow, and a response notification to the call. A workflow connection device used in a workflow system configured by connecting a workflow connection device that relays from a call destination workflow device to the call source workflow device so that they can communicate with each other,
A notification condition storage unit that stores the call destination workflow, the work in the call destination workflow, and the state of the work in association with each other as a notification condition;
The notification condition determination unit that determines that the notification condition is satisfied when the state of the work notified from the call destination workflow device matches the state of the work of the notification condition read from the notification condition storage unit When,
And a message transmission unit that relays the response notification to the call from the callee workflow device to the caller workflow device when the notification condition is satisfied.

Images