JPH11316780A - Workflow system having hierarchical business process definition - Google Patents

Abstract

PROBLEM TO BE SOLVED: To define hierarchical business process(BP) definitions which are systematic and easy to understand by independently sub-BPs from a high-order main BP and to improve the maintenance. SOLUTION: A process definition program 6 of a client 2 accesses the workflow server 1, registers property information inputted as to respective nodes constituting a sub-BP in a BP definition table 11, and registers the identifier of the sub-BP in a BP library registration table 12. Property information inputted as to a node which is a node in the main BP and also a node as the call source of the sub-BP is registered in the BP definition table 11 and information on a link with the called sub-BP is registered in a sub-BP link table 13. A workflow management program 5 performs flow control from the main BP to the sub-BP by referring to those tables.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow system using an electronic computer, and more particularly to a workflow system that defines a hierarchical business process and controls a workflow in accordance with the business process definition.

[0002]

2. Description of the Related Art In a workflow system using a computer, a series of tasks to be performed in a predetermined task sequence is defined electronically by defining the order of each task, a person in charge, and the content of the task. This is a system that performs work processing in order from one work to the next work according to the definition.
A defined series of work is called a business process.
For example, Nikkei Computer No. 425 (1997.9.
1) As described on pages 206 to 208, a user can easily create business process definition data by using a graphical user interface prepared by a business process definition tool.
The business process definition data defines the work content, the start condition and end condition of the activity, the name of the person in charge, and the like for each work node called an activity. The workflow engine interprets the business process definition data and executes workflow control from one activity to the next activity.

When defining a business process as described above, the business process is often defined in a hierarchical manner. For example, there is a case where a business process is regarded as a macro as a sequence of operations for each section and a detailed sequence of operations performed in each section is developed as a sub-business process. In particular, when defining a large-scale business such as a core business, unless a hierarchical definition is made, the business process becomes extremely complicated, and the business process definition and its maintenance require very large man-hours. By defining a hierarchical business process, the business process definition can be more easily understood.

[0004]

In a conventional workflow system, when a hierarchical business process is defined, a higher-level main business process has definition information of a lower-level sub-business process, and a definition of the main business process is a sub-type. Not independent of the business process definition. For this reason, when the same sub-business process is used repeatedly in multiple activities in the main business process, it is necessary to copy the definition information of the sub-business process defined in one activity and paste it into other activities. There is a problem that maintenance becomes troublesome because the definition information of the sub-business process is duplicated.

Also, when an activity in the main business process calls a sub-business process at a lower level, depending on data generated in business processing, a different sub-business process is called before a corresponding activity (work node) in the main business process. It is necessary to define a hierarchical activity in which a branch condition and a sub-business process called for each branch condition are set, and to write a sub-business process definition for each of a plurality of activities to be branched. Therefore, there is a problem that the definition of the business process becomes complicated, and the maintenance man-hour increases as the number of activities increases.

[0006] An object of the present invention is to provide a workflow system in which a sub-business process is defined independently of a higher-level main business process, thereby enabling a business process definition to be more easily understood and improving maintainability. It is in.

Another object of the present invention is to control the workflow by referring to the business process definition data according to the present invention.

[0008]

SUMMARY OF THE INVENTION The present invention is a program for defining a business process which is embodied on a computer-readable storage medium and which is subject to workflow control. A function for registering attribute information input for each of the constituent nodes in a table, (b) a function for registering a sub-business process identifier as a library so that it can be used from the main business process, and (c) a function included in the main business process A function of registering attribute information input for the node that is a node that is a sub-business process caller in the above table, and (d) stores the correspondence between the identifier of the caller node and the identifier of the called sub-business process. It is characterized by having a function of registering in means.

If the sub-business process is a business process called in accordance with a condition, the identifier of each sub-business process is registered in the storage means for each condition corresponding to the identifier of the calling node.

The program of the present invention is also called (a) when the next node to be transited in a business process is a node that is a caller of a lower-level sub-business process, the identifier of the caller node is called. A function of referring to the first table storing the correspondence with the identifier of the sub-business process and acquiring the identifier of the sub-business process; and (b) a second function of setting attribute information for each node constituting the sub-business process. It has a function of acquiring attribute information of a first node of a sub-business process with reference to a table, and transiting to the first node.

If the sub-business process is a business process called according to the condition, the sub-business process refers to the storage means and acquires the identifier of the corresponding sub-business process according to the condition.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a configuration diagram of a workflow system according to the embodiment. The workflow system includes a workflow server 1, a client 2 used by an administrator, a client 3 used by an operator, and a network 10 connecting these devices. The workflow server 1 is a computer such as a dedicated server or a personal computer, and stores a business process definition table 11, a business process library registration table 12, and a sub-business process link table 13 on a storage device connected to the processing device. . The business process definition table 11 contains the names of the nodes constituting the business process,
Stores definition information such as start conditions, end conditions, and names of persons in charge. The business process library registration table 12
This is a table for registering, as a library, a business process definition that can be used as a component from another business process among the business process definitions registered in the business process definition table 11. The sub-business process link table 13 is a table that stores the correspondence between the node in the business process of the caller and the sub-business process to be called. The processing device of the workflow server 1 stores and executes the workflow management program 5. The workflow management program 5 receives the business process definition information from the client 2 and registers it in the business process definition table 11, the business process library registration table 12, and the sub business process link table 13. In addition, in response to an inquiry from the client 2, business process information is extracted from the business process definition table 11, the business process library registration table 12, and the sub-business process link table 13 and transmitted to the client 2. When the work of the client 3 is completed, the workflow management program 5 controls the transition from the currently activated node to the next node. The workflow management program 5 transitions to the next node in the same business process, transitions to a sub-business process called from a node in the main business process, and transitions from a sub-business process to the node next to the calling node. Sometimes we do workflow control. In FIG. 1, the illustration of the communication control unit interposed between the workflow management program 5 and the network 10 and the database management program interposed between the workflow management program 5 and the tables 11, 12, and 13 is omitted.

The client 2 is a computer such as a personal computer, and its processing device stores and executes a process definition program 6. The process definition program 6 includes a graphical user interface (GU) (not shown).
A screen for defining a business process is displayed on the display device via I) to assist the administrator in defining the business process. Also, the defined business process definition information is sent to the workflow server 1 via a communication control unit (not shown), and a request is made to register it in the business process definition table 11, the business process library registration table 12, or the sub business process link table 13, The business process information received from the workflow server 1 is displayed on a display device.

The client 3 is a computer such as a personal computer, and its processing device stores and executes a workflow client program 7 and a business program 8. The business program 8 is an application program such as a slip processing executed when a worker is instructed by the workflow management program 5 to perform work. The workflow client program 7 receives a work instruction from the workflow management program 5, starts the business program 8, and
This is a program that monitors the progress of the business program 8 and notifies the workflow server 1 of the completion of the work when the work instructed is completed. Communication control unit between workflow client program 7 and network 10 and GUI between workflow client program 7, business program 8 and display / input device
Are not shown.

The workflow management program 5 is stored in a computer-readable storage medium and is read into a main storage device of the workflow server 1 via a drive unit (not shown) connected to the workflow server 1 or a drive unit of another computer. It can be transmitted to the main storage of the workflow server 1 via the network 10 and executed by the workflow server 1. The same applies to the process definition program 6 and the workflow client program 7. In addition, the workflow management program 5, the process definition program 6, and the workflow client program 7 are collectively stored in one or more storage media.
It can be read into the main storage device of the client 2 and the client 3 or transmitted to each computer by program transmission and executed.

FIG. 2 shows a business process definition table 1
1 is a data configuration diagram. FIG. Each record of the business process definition table 11 has a BP ID 21, a BP name 22,
It is composed of attribute information of each node such as a node name 23, a node type 24, a start condition 25, an end condition 26, a person in charge 27, and a transition destination 28. The BP ID 21 is an identifier assigned by the workflow management program 5 to uniquely identify a business process (BP). The BP name 22 is the name of the business process given when the administrator defines the business process, and corresponds to the BP ID 21. The BPID 21 or the BP name 22 can be referred to as a business process identifier. The node name 23 is a name given to a node (also referred to as an activity or a work node) constituting the business process when the administrator defines the business process, and is an identifier of the node. There are three kinds of node types 24. The node indicates a mere work, a node that is unconditionally a link source to a lower-level sub-business process (sub-BP), or a node that is a link source to a conditional business process. (Condition sub). A conditional sub-business process is a sub-business process in which one of the sub-business processes is selected according to a condition. The start condition 25 sets a condition for starting (activating) the node, and the end condition 26 sets a condition for ending (deactivating) the work by the node. The person in charge 27 is a worker who works on the node, and the transition destination 28 is
Next, the node to be started is shown. "-" Of the transition destination 28 indicates the end of the business process.

FIG. 3 is a diagram showing a data structure of the business process library registration table 12. Each record of the business process library registration table 12 is B
It comprises a PID 31, a BP name 32, a registrant 33, a registration date 34, and the like. The BP ID 31 is an identifier assigned by the workflow management program 5 to uniquely identify a business process, and the same BP ID exists as the BP ID 21 in the business process definition table 11. The business process name 32 is the name of the business process corresponding to the BPID 31. The registrant 33 and the registration date 34 indicate the name and registration date of the administrator who registered the business process in the business process library registration table 12, respectively.

FIG. 4 is a data configuration diagram of the sub-business process link table 13. The sub business process link table 13 is a table for setting link information from the main business process to the sub business process, and each record includes a main BP ID 41, a main B
It is composed of a P name 42, a node name 43, a table 44, a condition 45, a sub BP ID 46, and a sub BP name 47.
The main BP ID 41 is the BP ID of the business process immediately above the sub business process, and has the same BP ID.
ID is BP in business process definition table 11
It exists as ID21. Main BP name 42 is Main B
This is the name of the business process corresponding to PID41. The node name 43 is a name given to one of the nodes constituting the main business process, registered in the business process definition table 11, and is the name of a node that is a caller of the sub business process.
The table 44 indicates the name of a table or a file that stores values of data items to be subjected to condition determination such as slip data flowing through the workflow system. The condition 45 is a condition for calling a sub-business process, and includes a name of a target data item and a value of the data item. When the node unconditionally invokes the sub-business process, the table 44 and the condition 45 are not set. Sub BP
The ID 46 is an identifier of the sub business process to be called, and is registered in the business process definition table 11. The sub business process name 47 indicates the name of the sub business process corresponding to the sub BP ID 46.

FIG. 5 is a diagram showing a data example of a business process definition screen displayed on the display device of the client 2. 54 indicates the start of the business process, 55 indicates an icon indicating a normal work node, and 56 indicates the end of the business process. For each work node 55, a node name and a person in charge are set, and a start condition and an end condition of the node are set via a drop-down list (not shown). The registration menu 51 shows a screen for defining and registering a business process. The library registration 52 is an instruction for registering the defined business process in the business process definition table 11 and the business process library registration table 12, and the business process registration 53 is for registering the defined business process in the business process definition table 11. Instructions. In FIG. 5, the library registration 52 is selected.

FIG. 6 is a diagram showing an example of data of a library registration screen displayed on the display device of the client 2.
When the library registration menu 52 is selected on the business process definition screen shown in FIG. 5, a library registration screen is opened. The "business process name" is an area for inputting a business process name given when a defined business process is registered in the business process definition table 11 and the business process library registration table 12. The OK button is a button for instructing that the setting of the business process name has been completed, and the Cancel button is a button for canceling the input of the business process name.

FIG. 7 is a view showing an example of data of another business process definition screen displayed on the display device of the client 2. Reference numeral 55 denotes an icon indicating a normal work node. 57 is an icon of a conditional sub-business process node indicating that a sub-business process is to be called and a sub-business process that differs depending on conditions is called. Reference numeral 58 denotes a sub business process node which is a call source of the sub business process and an icon of the sub business process node indicating that the sub business process is unconditionally called. In the work node 55, the conditional sub-business process node 57, and the sub-business process node 58, a node name and a person in charge are set, respectively, and a start condition and an end condition of the node are set via drop-down lists. . In FIG. 7, the business process registration 53 is selected.

FIG. 8 is a diagram showing a data example of a sub-business process designation screen displayed on the display device of the client 2. When the sub-business process node 58 is double-clicked on the screen shown in FIG. 7, a sub-business process designation screen is opened. The “sub business process candidate” is the business process library registration table 12
Area for displaying a list of sub-business process names registered in. "Selection sub-business process"
This is an area for displaying a sub-business process name selected from “sub-business process candidates”. >>> is a button that, when selected together with one of “sub-business process candidates”, instructs to input the selected sub-business process name into the “selected sub-business process” area. << is a button for instructing to cancel the sub-business process name of “selected sub-business process” when selected together with the sub-business process name of “selected sub-business process”. The OK button is a button for indicating that the designation of the sub-business process has been completed.

FIG. 9 is a view showing an example of data of a conditional sub-business process setting screen displayed on the display device of the client 2. When the conditional sub-business process node 57 is double-clicked on the screen shown in FIG.
The conditional sub-business process setting screen is opened.
The “sub business process” is an area for selecting one of the sub business process names registered in the business process library registration table 12. “Table” is the name of the table or file that stores the data item to be subjected to the condition determination, and is an area for selecting one of the existing tables or files. "Condition" is a condition when calling the sub business process,
It consists of the target data item name and its value. The “set sub business process” is an area for displaying a list of sub business process names, tables, and conditions for other sub business processes already set. Add button is "sub business process", "table" and "condition"
Button to instruct to add the new sub-business process setting information entered in the "Set up sub-business process" area and the delete button are the selected sub-business process setting information in the "Set up sub-business process" area A button for instructing to delete a sub-business process and an edit button are buttons for instructing to change the condition of the selected sub-business process in the “set sub-business process” area. The OK button is a button for instructing to end the conditional sub-business process setting.

FIG. 10 is a diagram showing an example of data of a business process registration screen displayed on the display device of the client 2. When the business process registration 53 is instructed on the screen shown in FIG. 7, the business process registration screen is opened. The “business process name” is an area for inputting a business process name given when registering the defined business process in the business process definition table 11. The OK button is a button for indicating that the setting of the business process name has been completed, and the Cancel button is a button for canceling the input of the business process name.

FIG. 11 is a flowchart showing the flow of processing centered on the process definition program 6 when defining and registering a sub-business process. After authenticating the operator of the client 2, the process definition program 6 displays a business process definition screen on the display device of the client 2 (step 61). Node name of each node that configures the sub-business process via the display screen,
When the name of the person in charge, the start condition, and the end condition are input, the process definition program 6 receives the input information (step 62). The administrator can paste an icon indicating the work node 55 on the display screen, connect these nodes with arrows to create a visual business process, and input necessary input information. When the library registration 52 on the display screen is instructed (step 63 YES), the process definition program 6 displays the library registration screen on the display device (step 64). The business process name of the defined business process is input (step 6)
5) When the OK button is pressed (step 66O)
K), the process definition program 6 performs a process of registering the defined business process information in the business process definition table 11 (step 67). That is, the process definition program 6 defines the BP name 22 of the defined sub-business process, the node name 23 of each node constituting this sub-business process, the node type 24, the start condition 25,
A registration request is sent to the workflow server 1 to register information on the end condition 26, the person in charge 27, and the transition destination 28 in the business process definition table 11. The workflow management program 5 receives the registration request, generates a BP ID 21 corresponding to the node name, registers the information of each node as one record in the business process definition table 11, and returns the generated BP ID to the client 2. Next, the process definition program 6 performs a process of registering the sub-business process in the business process library registration table 12 (Step 68). That is, the process definition program 6 transmits a registration request to the workflow server 1 to register the BP ID 31 (the received BP ID), the BP name 32, and the registrant 33 of the defined sub-business process in the business process library registration table 12. The workflow management program 5 receives the registration request, and receives the designated sub-business process B
P ID 31, BP name 32, registrant 33 and registration date 34
Is registered in the business process library registration table 12 as information of one record.

When the edit menu is selected on the business process definition screen, the process definition program 6 acquires the business process information registered in the business process definition table 11, performs update, addition, and deletion processing, and executes the workflow. A request for updating the business process definition table 11 and the business process library registration table 12 is issued to the server 1. The workflow management program 5 updates designated records on the business process definition table 11 and the business process library registration table 12.

FIGS. 12A and 12B are flowcharts showing the flow of processing centered on the process definition program 6 when defining and registering a main business process. After authenticating the operator of the client 2, the process definition program 6 displays a business process definition screen on the display device (step 71). When the node name, person in charge, start condition, and end condition of each node constituting the main business process are input via the display screen, the process definition program 6 receives the input information (step 72). The administrator sets the work node 55,
Icons indicating the conditional sub-business process node 57 and the sub-business process node 58 can be pasted on the display screen, and these nodes can be connected by arrows to create a visual business process, and necessary input information can be input. . When the sub-business process node 58 is double-clicked (step 74 YES), a sub-business process designation screen is displayed (step 75), and a sub-business process candidate is acquired from the workflow server 1 and displayed (step 76). That is, the process definition program 6 queries the workflow server 1 for the sub-business process name registered in the business process library registration table 12. The workflow management program 5 sends the registered BP ID 31 and the corresponding BP name 32 to the client 2 with reference to the business process library registration table 12. The process definition program 6 displays the received BP name 32. If the OK button is pressed while the sub-business process name of any unconditional sub-business process is selected (step 77YE)
S), BP ID3 of selected sub-business process
1 is stored in association with the node name of the calling main business process (step 78), and the process returns to step 71. If the conditional sub-business process node 57 is double-clicked (step 79 YES), a conditional sub-business process setting screen is displayed (step 8).
0), obtain and display the sub-business process candidates, tables, and conditions from the workflow server 1 (step 81). That is, the process definition program 6 queries the workflow server 1 for the business process name, table, and condition of the sub-business process candidate. The workflow management program 5 checks the BP ID3 of each record obtained by referring to the business process library registration table 12.
1 and BP name 32, the name of the table or file storing the data item values that can be targets registered in the workflow server 1, and the sub BP name 47 of each record obtained by referring to the sub business process link table 13, the table 44 and the condition 45 are transmitted to the client 2.
The process definition program 6 displays the received BP name 32 of the sub-business process in the business process library registration table 12 in the “sub-business process” area, and changes the name of the table or file that stores the data item value to the “table” area. And all the sub BP names 47, tables 44, and conditions 45 obtained from the sub business process link table 13 are displayed in the “set sub business process” area. The administrator can confirm the already set sub business process information by referring to the information in the “set sub business process” area. One of the BP names 32 in the “sub business process” area is selected, one of the table names in the “table” area is selected, a condition is input in the “condition” area, and an additional instruction is given.
If the K button is pressed (YES in step 82), the added sub-business process information is stored in association with the node name of the main business process of the caller (step 83), and the process returns to step 71.

When "business process registration" is instructed on the business process definition screen (step 73YE)
S), the process proceeds to the process shown in FIG. 12B, and a business process registration screen is displayed (step 84). The business process name of the main business process is entered (Step 8)
5) When the OK button is pressed (step 86O)
K), the process definition program 6 performs a process of registering the business process information of the defined main business process in the business process definition table 11 (step 87). That is, the process definition program 6 defines the BP name 22 of the defined main business process, the node name 23 of each node constituting the business process, the node type 24, the start condition 25, the end condition 26, the person in charge 27, and the transition destination 28. Information to business process definition table 11
A registration request is transmitted to the workflow server 1 so as to be registered in the workflow server 1. The workflow management program 5 receives the registration request, generates a BP ID 21 corresponding to the node name, registers the information of each node as one record in the business process definition table 11, and sets the generated BPID to the client 2 as the BP name. Return it in association. Next, the process definition program 6 performs a process of registering the link information of the sub business process in the sub business process link table 13 (step 88). That is, the process definition program 6 stores the BP ID 21 and BP of the main business process corresponding to the sub-business process node 58.
A registration request is transmitted to the workflow server 1 to register the BP ID 31 and the BP name 32 of the called sub-business process with the name 22, the node name 23, and the sub-business process link table 13. Further, the process definition program 6 stores the main BP ID 4 of the main business process corresponding to the conditional sub-business process node 57.
1. A registration request is transmitted to the workflow server 1 to register the BP ID 31, the BP name 32, the table name, and the condition of the sub business process called the main BP name 42, the node name 43, and the sub business process in the sub business process link table 13. Generally, since there are a plurality of sub-business processes called from the conditional sub-business process node 57, each sub-business process information is transmitted. The workflow management program 5 receives these registration requests and, for each sub-business process, the main B
P ID 41, main BP name 42, node name 43, table 44, condition 45, sub BP ID 46, and sub BP
One record including the name 47 is created and registered in the sub-business process link table 13.

When the edit menu is selected on the business process definition screen, the process definition program 6 acquires the business process information registered in the business process definition table 11, performs update and additional processing, and executes the process. Business process definition table 11
Issue an update request. Workflow management program 5
Updates the specified record on the business process definition table 11. Further, it adds, updates, and deletes the link information already registered in the sub business process link table 13 via the conditional sub business process setting screen.

With the above processing, the sub-business process link table 13 can be set so that different nodes on the same main business process call the same sub-business process, and a plurality of business processes registered in the business process library registration table 12 can be set. Nodes can share.

The main business process defined and registered as described above may be further registered in the business process library registration table 12. That is, when the library registration 52 is instructed after performing the processing of steps 87 and 88, the process definition program 6 performs only the processing of step 68 without performing the processing of steps 64-67. The main business process thus defined and registered can be used as a sub-business process of a higher-level main business process.

FIGS. 13A and 13B are flowcharts showing the processing flow of the workflow management program 5 for performing workflow control. The work flow management program 5 communicates with the work flow client program 7 of the client 3 to execute the work for the work node to be currently executed (step 91). The business program 8 of the client 3 performs the processing related to the business, and the workflow client program 7 monitors the progress and notifies the workflow management program 5. When the condition of the termination condition 26 is satisfied for the currently activated work node (step 92 YES), the workflow management program 5 determines that the next node is set in the transition destination 28 of the node, that is, the process is not terminated ( (Step 93NO), the business process definition table 11 is searched to acquire the definition record of the next node, and the node type 24 is referred to (Step 94). If the node type 24 of the next node is “work” (step 95YE)
S), a work instruction message is issued to the person in charge indicated by the person in charge 27 of the node (step 96), and the process ends. If the next node is not set in the transition destination 28 of the node and the process ends (YES in step 93),
The sub BP ID 46 of the sub business process link table 13 is searched by the BP ID 21 of the node (step 97). If there is no matching record with the BP ID 21 (step 98 NO), the process ends because the main business process has ended. BP ID
If there are 21 matching records (step 98YE
S), since this node is the last node of the sub business process, the main BP ID of the calling node is acquired by referring to the BP ID 41 of the same record (step 99), and the business process definition table 11 is searched and called. The transition destination 28 of the definition record relating to the source node is acquired (step 100), and the process returns to step 94 to search the business process definition table 11 to acquire the definition record of the next node, and refers to the node type 24 (step 94). ).

If the node type 24 of the next node is not "work" (NO in step 95), the process moves to FIG. 13B, and the workflow management program 5 determines that the node type is "condition sub".
It is determined whether or not it is (step 101). If "condition sub" (step 101 YES), the sub business process link table 13 is searched by the BP ID 21 in the definition record of the next node, and the table 44, condition 45, and sub BP ID 46 in the corresponding record are obtained. (Step 102). Next, the obtained table is accessed to obtain the data item value specified by the condition (step 103), the sub BP ID 46 of the sub business process corresponding to the condition is obtained (step 104), and the process returns to step 94 to return to the business process. The first definition record corresponding to the sub BP ID 46 obtained by searching the definition table 11 is obtained, and the node type 24 is referred to (step 94). If the node type is not “condition sub” (NO in step 101), since it is “sub BP”, the sub business process link table 13 is searched by the BP ID 21 in the definition record of the next node, and the sub BP ID 46 of the corresponding record is searched. (Step 1
05), returning to step 94, and similarly, sub-BP ID 46
Is obtained, and the node type 24 is referred to (step 94).

[0035]

As described above, according to the present invention, in defining a hierarchical business process, a sub-business process is defined independently of a higher-level main business process. It is possible to further simplify and systematically define, and one sub-business process definition can be shared by a plurality of activities in the main business process, and the maintainability of the business process definition can be improved.

That is, when the definition of the sub-business process is changed, only the definition of the sub-business process registered in the library needs to be modified. All activities (work nodes) in the main business process to be used are identified, and the number of maintenance steps can be significantly reduced compared to the method of modifying all the sub business processes defined in the identified activities. it can.

In particular, when a different sub-business process is called according to data generated during business processing, the description of the conditional branch and the sub-business process to be called for each branch condition is made independent from the definition of the main business process. Since the definition of the process is expressed simply, the number of steps for defining and maintaining the business process can be reduced.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a workflow system according to an embodiment.

FIG. 2 is a business process definition table 11 according to the embodiment.
FIG. 4 is a data configuration diagram of FIG.

FIG. 3 is a data configuration diagram of a business process library registration table 12 of the embodiment.

FIG. 4 is a data configuration diagram of a sub-business process link table 13 according to the embodiment.

FIG. 5 is a diagram illustrating a data example of a business process definition screen for defining a lower-level business process.

FIG. 6 is a diagram showing an example of data on a library registration screen.

FIG. 7 is a diagram illustrating a data example of a business process definition screen for defining a business process of an upper hierarchy.

FIG. 8 is a diagram showing a data example of a sub-business process designation screen.

FIG. 9 is a diagram illustrating a data example of a conditional sub-business process setting screen.

FIG. 10 is a diagram illustrating a data example of a business process registration screen.

FIG. 11 is a flowchart illustrating a processing flow of a process definition program 6 when a sub-business process is defined and registered according to the embodiment.

FIG. 12A is a flowchart illustrating a process flow of a process definition program 6 when defining and registering a main business process according to the embodiment.

FIG. 12B is a flowchart (continued) showing the processing flow of the process definition program 6 when defining and registering the main business process of the embodiment.

FIG. 13A is a flowchart illustrating a processing flow of a workflow management program 5 that performs workflow control according to the embodiment.

FIG. 13B is a flowchart (continued) showing a processing flow of the workflow management program 5 for performing workflow control according to the embodiment.

[Explanation of symbols]

1: Workflow server, 2, 3: Client, 5:
Workflow management program, 6: Process definition program, 7: Workflow client program, 1
1: Business process definition table, 12: Business process library registration table, 13: Sub business process link table

Claims (5)

[Claims] 1. A program for defining a business process which is embodied on a computer-readable storage medium and which is subject to workflow control, the program including the following functions: (a) Each node constituting a sub-business process Function to register the attribute information entered for
(B) a function of registering the identifier of the sub-business process as a library so that it can be used from the main business process; (c) inputting a node included in the main business process and serving as a caller of the sub-business process (D) registering the correspondence between the identifier of the calling node and the identifier of the called sub-business process in the storage means. 2. The sub-business process is a business process called according to a condition, and the identifier of each sub-business process is registered in the storage means for each condition corresponding to the identifier of the node of the calling source. The storage medium for storing the program according to claim 1, further comprising a function. 3. Data relating to a business process which is embodied on a computer-readable storage medium and which is subject to workflow control, and has the following data structure: (a) For each node constituting each business process A first table storing attribute information of the node, and (b) an identifier of one node constituting a higher-level business process stored in the first table, and a higher-order identifier stored in the first table. A second table that stores correspondences with identifiers of lower-level business processes called by the business process. 4. A program that is embodied on a computer-readable storage medium and controls a workflow.
The program includes the following functions: (a) When a node to be transitioned to next in a business process is a node that calls a lower-level sub-business process, the identifier of the calling node and the sub-business to be called A function of referring to the first table storing the correspondence with the process identifier and acquiring the identifier of the sub-business process, and (b) a second function of setting attribute information for each node constituting the sub-business process
A function of acquiring attribute information of the first node of the sub-business process by referring to the table of the sub-business process and transiting to the first node. 5. The first table stores identifiers of a plurality of sub-business processes selected by a condition corresponding to an identifier of a node of a calling source, and stores identifiers of the corresponding sub-business processes according to the condition. The storage medium for storing the program according to claim 4, wherein