JPH09245092A - Workflow definition executing method and system - Google Patents

Abstract

(57) [Abstract] [Problem] When executing a workflow, it is not necessary to predefine all business procedures, and a workflow definition execution method and a workflow definition execution method capable of executing a workflow even if some business procedures remain undefined. Provide the system. According to the present invention, when defining and executing a workflow managed by one workflow management system in a workflow management system, one workflow group is defined as a series of a plurality of workflows, and the workflows within the workflow are configured. And manage the execution order, and inherit information between workflows that make up the workflow group.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow defining method and system, and more particularly to a workflow for defining and executing a workflow in a workflow management system for defining and executing a series of business flows involving a plurality of persons. Definition method and system.

[0002]

2. Description of the Related Art A workflow is a rule that explicitly describes the flow of work (task).
There are the following two types. The first method is to define a workflow as a sequence of tasks, which is the minimum unit of work that constitutes a task. This method is a case where the depth of the hierarchy is set to 1 in the second method described later. FIG.
It is a figure for demonstrating the conventional 1st method. The figure shows an example of definition when a certain work is composed of six works. The workflow 100 shown in the figure has six tasks 101 to 106.
Is described as a series of tasks.

The second method is to first define a general framework (process) of work, and then refine each process into a task, which is the most unit of work, and hierarchically define the process in this process. There is no particular limitation on the depth of the hierarchy. A business can be divided into two processes,
Further, a case where each of these processes is composed of three tasks will be described. FIG. 10 is a diagram for explaining the second conventional method. In the figure, in the workflow 200, there are processes 210 and 220 obtained by dividing the workflow into two. The process 210 is composed of tasks 211 to 213.
It is composed of tasks 221 to 223.

As described above, the method of hierarchically defining a workflow is consistent with the human thinking process of considering the work from a large frame and gradually refining it, and particularly when defining a large-scale workflow. Labor is reduced. next,
How to execute the workflow is explained.

A workflow management system that executes a workflow regards the workflow as a sequence of tasks, which is the minimum unit of work, and executes the tasks sequentially, regardless of the above definition method. That is, when the workflow management system executes the workflow, it simply needs the workflow as a series of tasks regardless of the human thinking process.

For example, the workflow shown in FIG.
The workflow shown in FIG. 10 is regarded as completely equivalent when executing the workflow. At this time,
All tasks of the workflow cannot be executed unless they are defined in advance. FIG. 11 shows the configuration of the workflow management system. The workflow management system 20 shown in the figure has a server computer 21 and client computers 22-24.

The client computers 22-24 are
Each is connected to the server computer 21 via a LAN or the like. The server computer 21 holds the workflow, and executes and manages the workflow. Client computer 22
24 is a function for describing a workflow mainly by a graphic user interface (GUI),
It has a function of executing an activity instructed by the server computer 21.

FIG. 12 shows the structure of the integrated workflow management system. In the integrated workflow management system shown in the figure, the workflow management system 30 has a server computer 31 connected to the client computers 32 to 34, and the workflow management system 40 is
It has a server computer 41 connected to the client computers 42 to 44.

The workflow management system 30 and the workflow management system 40 are workflow management systems of different vendors. Workflow management system 30
Is composed of a server computer 31 and client computers 32-34, and is connected by a LAN or the like. On the other hand, the workflow management system 40 includes a server computer 41 and client computers 42 to 44.
And is connected by a LAN or the like. The server computer 31 and the server computer 41 are connected by the network 50 and can communicate by e-mail. The network 50 is the Internet or the like.

FIG. 13 is a diagram for explaining a conventional workflow executing method. In the figure, the workflow management system 300 includes a workflow management unit 310 and a task execution unit 320. The workflow management unit 310 manages definition information of this workflow, and the task execution unit 320 inquires of the workflow management unit 310 what task is to be executed next in order to execute the workflow. Accordingly, the workflow management unit 310 notifies the task execution unit 320 of the task to be executed next. As a result, the task execution unit 320
Executes a task designated by the workflow management unit 310. After that, this operation is repeated until the final task is executed.

[0011]

However, in the method of defining and executing a work in the above-mentioned conventional technique, all work procedures must be defined in advance before the work is executed, so that the problem occurs during the execution of the work. There is a problem that it is not possible to deal with possible changes in business procedures.

The present invention has been made in view of the above points. It is not necessary to predefine all business procedures when executing a workflow in a workflow management system, and even if some business procedures remain undefined. It is an object of the present invention to provide a workflow definition execution method and system that can execute a workflow and can change the definition of the business procedure of the workflow that is being executed.

[0013]

FIG. 1 is a diagram for explaining the principle of the present invention. According to the present invention, when defining and executing a workflow managed by one workflow management system in the workflow management system, one workflow group is defined as a series of a plurality of workflows (step 1), and the workflows in the workflow are configured. And the execution order are managed (step 2), and the information between the workflows forming the workflow group is inherited (step 3).

Further, according to the present invention, during execution of a workflow in a workflow group, a workflow is newly defined after the workflow being executed in the workflow group. Further, according to the present invention, while a workflow in a workflow group is being executed, the definition of the workflow after the workflow being executed in the workflow group is changed.

FIG. 2 is a block diagram showing the principle of the present invention. According to the present invention, in a workflow management system, a workflow definition execution system managed by one workflow management system manages a group definition unit 410 that defines one workflow group as a series of a plurality of workflows, and the configuration of workflows in the workflows. A configuration management unit 411 for managing the workflow, an execution order management unit 420 for managing the execution order of the workflows in the workflow,
The information transfer unit 412 has an information transfer unit 412 that transfers information between workflows included in the workflow group 500, and an execution unit 430 that executes a task of the workflow of the workflow group based on the information managed by each unit.

The execution means 430 also refers to the workflow configuration information of the configuration management means 411, and the execution order management means 420 is based on the workflow configuration information.
And a means for sequentially executing the tasks of the workflows in the workflow group in accordance with the execution order of the workflows, and a means for activating the information inheriting means 412 when the execution of all the tasks in the workflow is completed.

Further, the group definition means 410 described above is
An additional definition unit is included that allows a new workflow to be defined after the workflow being executed in the workflow group during execution of the workflow in the workflow group. The execution means 430 includes means for executing the task in the workflow defined by the additional definition means.

The group definition means 410 described above is
When the workflow in the workflow group 500 is being executed, a change definition unit is included which can change the definition of the workflow after the workflow in execution in the workflow group. The executing means 430 includes means for executing the task in the workflow defined by the change defining means.

Accordingly, in the present invention, one workflow is defined as a series of a plurality of workflows (workflow group), and thus one workflow to be executed at a certain time point is defined among the workflows in the workflow group. If so, this workflow group can be executed even if no other workflow is defined. Moreover, the definition of an unexecuted workflow can be modified at any time.

Further, by inheriting information between the workflows in the workflow group, each workflow can be executed without contradiction, which is different from simply activating a plurality of workflows in order. Therefore, it is possible to execute the workflow even if some of the business procedures are undefined, and in addition, it is possible to change the definition of the business procedure of the workflow that is being executed.

[0021]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 3 shows the configuration of the workflow management system of the present invention. The workflow definition execution system shown in the figure comprises a workflow management system 400, a workflow 510, and a workflow group 500 having a workflow 520.

The workflow management system 400 comprises a workflow management section 410 having a configuration management section 411, an information transfer section 412, a workflow management section 420 and a task execution section 430. The configuration management unit 411 of the workflow group management unit 410 has workflow configuration information for each workflow group, and manages information in which the workflow group 500 includes workflows 510 and 520 and the workflow execution order.

The information transfer section 412 of the workflow group management section 410 manages transfer information between workflows. The workflow management unit 420 manages the execution order of individual tasks of the workflows that make up the workflow group.

The task execution unit 430 actually executes the task. Next, the operation of the above configuration will be described. FIG. 4 is a flowchart of the workflow definition executing method of the present invention. Step 101) The task execution unit 430 of the workflow management system 400 inquires of the configuration management unit 411 about the first task to be executed in the workflow group 500.

Step 102) As a result, the configuration management unit 411 extracts the workflow to be executed first from the workflows forming the managed workflow group, and inquires about the task to be executed first by the workflow. Step 103) The workflow management unit 420 determines the task name to be executed first in the first workflow based on the task execution order information in response to the inquiry from the configuration management unit 411, and returns it to the configuration management unit 411.

Step 104) The configuration management section 411
The workflow name and the task name in the workflow notified from the workflow management unit 420 are notified to the task execution unit 430. Step 105) The task execution unit 430 that has received the notification from the configuration management unit 411 executes the task with the task name in the workflow with the notified workflow name.

Step 106) It is judged whether or not all the tasks in the first workflow have been executed, and if they have been executed, the procedure proceeds to step 108, and if there are unexecuted tasks in the workflow, the step is executed. Move to 107. Step 107) The task execution unit 430 sequentially executes the tasks in the workflow, and proceeds to step 106.

Step 108) When the execution of the task of the workflow 510 is completed, the information transfer unit 412 of the workflow management system 400 inquires of the configuration management unit 411 whether there is a workflow to be executed next. Step 109) The configuration management unit 411 uses the information transfer unit 4
It is determined whether or not there is a workflow to be executed next in response to the 12 queries, and if there is, a step 11
If it does not exist, the process ends.

Step 110) The configuration management unit 411
The information transfer unit 412 is notified of the workflow name to be executed next. (Step 111) The information takeover unit 412 makes the configuration management unit 41
When the workflow name (n) to be executed next is acquired from 1, the takeover information is acquired from the previously processed workflow (n-1).

Step 112) When the task execution unit 430 next executes, when the information takeover unit 412 acquires the workflow name (n), the execution order information of the workflow name (n) is managed from the task execution unit 430 by the workflow management unit 430. The part 420 is queried for the first execution order task name in the workflow (n).

Step 113) Workflow management unit 4
20 notifies the task execution unit 430 of the first execution order task name in the workflow (n). As a result, the task execution unit 430 performs the processing from step 105 onward.

[0032]

Embodiments of the present invention will now be described with reference to the drawings.
The following description will be given based on the above-described FIGS. 3 and 4. [First Embodiment] The following first embodiment shows an example in which information for executing the next workflow 520 is already defined when the first workflow 510 is executed.

In the following description, the workgroup 50
There are two workflows 510 and 520 as workflows included in 0, and the workflow 510 includes tasks 511, 512, and 513.
Exists, and the tasks are executed sequentially from the task 511. The workflow 520 includes tasks 521 and 5
22 and 523 exist, and the tasks 521 are sequentially executed.

As shown in FIG. 5, the configuration management unit 411 of the workflow management system 400 manages the group name and the workflow name belonging to the group having the group name. In the example of the figure, the workflow 510 and the workflow 520 are registered in the group name 500.

The workflow management unit 420 manages the task to be executed and the execution order of the task for each workflow. FIG. 6 shows an example of information managed by the workflow management unit according to the first embodiment of this invention. In the figure, the workflow management unit 420 manages the workflow name and the task name to be executed first in the workflow.

A workflow definition execution method will be described below with reference to the flowchart of FIG. The task execution unit 430 of the workflow management system 400 inquires of the configuration management unit 411 about the first task to be executed in the workflow group 500 (step 101).

As a result, the configuration management unit 411 extracts the workflow name (workflow 510) that should be executed first from the workflows 510 and 520 that make up the managed workflow group 500, and the workflow 510 first performs the extraction. The workflow management unit 420 is inquired about the task to be performed (step 102).

In response to the inquiry from the configuration management unit 411, the workflow management unit 420 determines the task name (task 511) to be executed first in the first workflow 510 based on the task execution order information, and the configuration management unit 4
It returns to 11 (step 103).

The configuration management unit 411 uses the workflow name (workflow 510) and the task name (task 51) in the workflow 510 notified from the workflow management unit 420.
1) is notified to the task execution unit 430 (step 10).
4). The task execution unit 430, which has received the notification from the configuration management unit 411, receives the notified workflow name (workflow 5
10) Task name in the workflow 510 (task 51
The task 511 of 1) is executed (step 105).

It is determined whether all the tasks in the first workflow 510 have been executed (step 106). In this case, since only task 511 is being executed,
Task 512 and task 513 are unprocessed. Therefore,
The tasks 512 and 513 in the workflow 510 are sequentially executed. This completes the processing of all tasks in the workflow 510.

When the execution of the task of the workflow 510 is completed, the information transfer unit 412 of the workflow management system 400 inquires of the configuration management unit 411 whether there is a workflow to be executed next (step 108).
The configuration management unit 411 determines whether or not there is a workflow to be executed next in response to the inquiry from the information transfer unit 412 (step 109), and notifies the name of the workflow to be executed next (workflow 520) (step 110).

The workflow name to be executed next by the information transfer unit 412 from the configuration management unit 411 (workflow 520)
Is acquired, the takeover information is acquired from the previously processed workflow (workflow 510) (step 11).
1). The name of the first execution task of the workflow 520 to be executed next by the task execution unit 430 is set to the workflow management unit 420.
(Step 112).

As a result, the workflow management unit 420
Is the name of the first execution task of the workflow 520 (task 5
21) is notified to the task execution unit 430 (step 11).
3). The task execution unit 430 is a workflow management unit 420.
The task 521 acquired from the above is set as the head task of the workflow 520, and the tasks 522 and 523 are sequentially executed (step 107).

The information transfer unit 412 inquires of the configuration management unit 411 about the name of the workflow to be executed next (step 108). In this example, the workflow name to be executed next is not defined in the configuration management unit 411, so the process ends. [Second Embodiment] In the following second embodiment, the workflow 510 and the workflow 520 are considered as independent workflows in the system using the conventional technique. Therefore, when the workflow 510 is executed, the workflow 520 is executed. The definition of the workflow 520 is not required to be performed, so an example of defining the workflow 520 during execution of the workflow 510 will be described.

FIG. 7 shows an example (part 1) of the contents of the configuration management section of the second embodiment of the present invention. The example in the figure shows the contents of the configuration management unit before the workflow 510 is executed, and only the workflow 510 is currently designated as the group 500. FIG. 8 is a flowchart of the workflow definition executing method according to the second embodiment of this invention.

The task execution unit 430 of the workflow management system 400 inquires of the configuration management unit 411 about the first task to be executed in the workflow group 500 (step 201). As a result, the configuration management unit 4
11 extracts the workflow name (workflow 510) to be executed first from the workflows 510 that compose the managed workflow group 500. At present, as shown in FIG. 7, only the workflow 510 is defined as the workflow name in the configuration management unit 411. Therefore, the configuration management unit 411 determines the task that the workflow 510 should perform first as the workflow management unit 4
20 is inquired (step 202).

In response to the inquiry from the configuration management unit 411, the workflow management unit 420 determines the task name (task 511) to be executed first in the first workflow 510 based on the task execution order information, and the configuration management unit 4
It returns to 11 (step 203).

The configuration management unit 411 uses the workflow name (workflow 510) and the task name (task 51) in the workflow 510 notified from the workflow management unit 420.
1) is notified to the task execution unit 430 (step 20)
4). The task execution unit 430, which has received the notification from the configuration management unit 411, receives the notified workflow name (workflow 5
10) Task name in the workflow 510 (task 51
The task 511 of 1) is executed (step 205).

As shown in FIG. 5 during execution of the task execution unit 430, the workflow 520 is additionally defined as the workflow group 500 in the configuration management unit 411 (step 206). It is determined whether all the tasks in the first workflow 510 have been executed (step 2
07). In this case, since only the task 511 is being executed, the tasks 512 and 513 are unprocessed. Therefore, the task 51 in the workflow 510 is
2, 513 are sequentially executed. Workflow 5
Processing of all tasks in 10 is completed.

When the execution of the task of the workflow 510 is completed, the information transfer unit 412 of the workflow management system 400 inquires of the configuration management unit 411 whether there is a workflow to be executed next (step 209).
The configuration management unit 411 determines whether or not there is a workflow to be executed next in response to the inquiry of the information transfer unit 412 (step 210). In this example, step 2 above
Since the workflow 520 is additionally defined in the configuration management unit 411 in 06, the workflow name (workflow 520) to be executed next is notified (step 211).

The workflow name to be executed next by the information transfer unit 412 from the configuration management unit 411 (workflow 520)
Is acquired, the takeover information is acquired from the previously processed workflow (workflow 510) (step 21).
2). The name of the first execution task of the workflow 520 to be executed next by the task execution unit 430 is set to the workflow management unit 420.
(Step 213).

As a result, the workflow management unit 420
Is the name of the first execution task of the workflow 520 (task 5
21) is notified to the task execution unit 430 (step 21).
4). The task execution unit 430 is a workflow management unit 420.
The task 521 acquired from the above is set as the head task of the workflow 520, and the tasks 522 and 523 are sequentially executed (step 208).

The information transfer unit 412 inquires of the configuration management unit 411 about the name of the next workflow to be executed (step 209). In this example, the workflow name to be executed next is not defined in the configuration management unit 411, so the process ends. Further, in the first and second embodiments described above, when the task execution unit 430 executes a task in the workflow after the first workflow, the information takeover unit 412 is used.
Asks the configuration management unit 411 if there is a workflow to be executed next.
Although the takeover information, which is the information between the workflows, is acquired from the workflow executed immediately before, the invention is not limited to this example, and when the configuration management unit 411 is defined,
The configuration may be such that the takeover information to be stored in the information takeover unit 412 is defined at the same time. As a result, the processing of step 111 of the first embodiment and step 212 of the second embodiment becomes unnecessary. In addition, in this example, other than information between workflows as transfer information, information related to the result of task execution cannot be transferred, so that the transfer information is acquired from the previously executed workflow.

The present invention is not limited to the above embodiments, but various modifications and applications are possible within the scope of the claims.

[0055]

As described above, according to the workflow definition executing method and system of the present invention, in the workflow management system, it is not necessary to predefine all business procedures when executing a workflow, Even if the business procedure is undefined, the workflow can be executed, and the business procedure of the workflow that is being executed can be changed.

[Brief description of drawings]

FIG. 1 is a diagram for explaining the principle of the present invention.

FIG. 2 is a principle configuration diagram of the present invention.

FIG. 3 is a configuration diagram of a workflow management system of the present invention.

FIG. 4 is a flowchart of a workflow definition executing method of the present invention.

FIG. 5 is a diagram showing an example of contents of a configuration management unit according to the first embodiment of this invention.

FIG. 6 is a diagram showing an example of information managed by a workflow management unit according to the first embodiment of this invention.

FIG. 7 is a diagram showing an example of contents of a configuration management unit according to a second embodiment of this invention.

FIG. 8 is a flowchart of a workflow definition executing method according to the second embodiment of this invention.

FIG. 9 is a diagram illustrating a first conventional method.

FIG. 10 is a diagram for explaining a second conventional method.

FIG. 11 is a configuration diagram of a workflow management system.

FIG. 12 is a configuration diagram of an integrated workflow management system.

FIG. 13 is a diagram for explaining a conventional workflow execution method.

[Explanation of symbols]

410 group management means, workflow group management part 411 configuration management means, configuration management part 412 information transfer means, information transfer part 420 execution order management means, workflow management part 430 execution means, task execution part 500 workflow group 510, 520 workflow 511 513, 521-523 tasks

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kazaku Asano 3-19-2 Nishishinjuku, Shinjuku-ku, Tokyo Inside Nippon Telegraph and Telephone Corporation (72) Inventor Keiji Obayashi 3-19 Nishishinjuku, Shinjuku-ku, Tokyo No. 2 Nippon Telegraph and Telephone Corporation

Claims (9)

[Claims] 1. When defining and executing a workflow managed by one workflow management system in a workflow management system, one workflow group is defined as a sequence of a plurality of workflows, and the workflows in the workflow are configured and executed. A workflow definition executing method, characterized in that the order is managed and the information between the workflows constituting the workflow group is inherited. 2. The workflow definition executing method according to claim 1, wherein a workflow is newly defined after the workflow being executed in the workflow group while the workflow is being executed in the workflow group. 3. The workflow definition executing method according to claim 1, wherein during the execution of the workflow in the workflow group, the definition of the workflow subsequent to the workflow in execution in the workflow group is changed. 4. In the workflow management system, in a workflow definition execution system managed by one workflow management system, a group definition means for defining one workflow group as a series of a plurality of workflows, and a configuration of the workflows in the workflows. A configuration management unit that manages, an execution order management unit that manages the execution order of workflows in the workflow, an information transfer unit that transfers information between the workflows that form the workflow group, and information managed by each unit. And a executing unit that executes a task of the workflow of the workflow group based on the above. 5. The execution unit refers to the workflow configuration information of the configuration management unit,
Means for sequentially executing the tasks of the workflows of the workflow group in accordance with the execution order of the workflows, referring to the execution order management means based on the configuration information of the workflows; and The workflow definition execution system according to claim 4, further comprising means for activating information transfer means. 6. The group defining means, during execution of a workflow in the workflow group,
5. The workflow definition execution system according to claim 4, further comprising additional definition means for newly defining a workflow after the workflow being executed in the workflow group. 7. The workflow definition execution system according to claim 4, wherein the execution unit includes a unit that executes a task in the workflow defined by the additional definition unit. 8. The group defining means, during execution of a workflow in the workflow group,
5. The workflow definition execution system according to claim 4, further comprising change definition means for changing the definition of a workflow after the workflow being executed in the workflow group. 9. The workflow definition execution system according to claim 4, wherein the execution unit includes a unit that executes a task in the workflow defined by the change definition unit.