JP2002157386A - Workflow management method, its device, its processing program and recording medium with its processing program stored - Google Patents

Abstract

PROBLEM TO BE SOLVED: To switch the state transition processing method of a work by a fine unit such as workflow definition, state, and transition. SOLUTION: Workflow definition includes synchronization information being information for designation a processing system corresponding to state transition request API calling. A workflow definition tool is able to set the synchronization information of the workflow definition. A state transmission request synchronization processing program performs state transition processing in a synchronization processing system for performing the state transition processing of a work since the input of the state transition request is accepted until a reply is returned. The state transition request asynchronization processing program performs state transition processing in an asynchronization processing system for operating the state transition processing of a work after the input of the state transition request is accepted, and a reply is returned. Then, whether the state transition processing should be executed by the synchronization processing system or the asynchronization processing system is decided by referring to the synchronization information in the workflow definition.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a control technique for a workflow management system.

[0002]

2. Description of the Related Art A workflow management system is software for managing the state of a work and the assignment of the work to a worker based on a predefined workflow. Hereinafter, information indicating the content of the defined workflow is referred to as a workflow definition. For the workflow management system, for example, WfMC: The Wor
kflow Reference Model (TC0
0-1003 Jan-1995 1.1) and Wf
MC: Workflow ManagementApp
ligation Programming Inte
rface (Interface2 & 3) Specif
ication (WFMC-TC-1009 July
-1998 2.0).

[0003] According to them, the workflow management system provides a programming interface used by a client application program. Hereinafter, this client application program is referred to as a workflow application program.
In the following, the programming interface will be referred to as API (Application Programmable).
ing Interface).

[0004] The API provided by the workflow management system to the workflow application program is an interface for requesting operations on the work, such as inputting, searching, state transition such as start and end, and deletion. When the workflow application program operates using these APIs, the workflow management system manages the state of the work and assigns the work to the user according to the workflow definition. Hereinafter, a request for a work state transition operation to the workflow management system is referred to as a state transition request. An interface for requesting a state transition operation of a work is called a state transition request API.

[0005] The processing system for the state transition request from the workflow application program in the workflow management system is classified into two types: an asynchronous processing system and a synchronous processing system. The asynchronous processing method only performs processing for storing information related to a state transition request in a permanent storage unit, returns a response to the calling workflow application program, and performs actual state transition processing at a later timing with information on the state transition request. Is taken out from the permanent storage means and executed. The synchronous processing method is a method in which an actual state transition process is executed between a state transition request and a response to a workflow application program.

[0006] From the viewpoint of the performance of state transition, the asynchronous processing method has a small number of processes at the time of a state transition request, and therefore, a turnaround time (API response time), which is a time from a state transition request to a response returning to the workflow application program. ) Is small. On the other hand, from the point that there is no guarantee of immediate execution and the point that information relating to the state transition request is stored / retrieved in the permanent storage means, it is the time from the state transition request to the completion of the actual state transition processing. , The state transition time becomes longer.

On the other hand, in the synchronous processing method, since there are many processes at the time of a state transition request, the turnaround time becomes long.
On the other hand, from the point that the operation of storing and retrieving the state transition request to the permanent storage means is not performed, and there is a guarantee of immediate execution,
The state transition time becomes shorter. Generally, the shorter the turnaround time, the better the operability of the workflow application program, and the shorter the state transition time, the earlier the next worker can start work.

Conventionally, the application range of the workflow management system has been an auxiliary business such as an ordering business and a travel expense settlement in a company. Therefore, the state transition time is not so much a problem, but rather, to improve the operability of a workflow application program. Emphasis was placed on reducing API response time. Therefore, the processing method for the API call of the conventional workflow management system has mainly been the asynchronous processing method.

[0009] In recent years, the application range of the workflow management system has been expanded to core business, and it has also been applied to business such as window business that is processed with customers waiting. In such a case, it is important to reduce the state transition time, so a synchronous processing type workflow management system is effective.

One of the major advantages of the introduction of the workflow management system is that the workflow management system controls the flow of a series of operations so that the developer of the workflow application program that executes each operation can execute each operation. In other words, it is possible to concentrate only on the realization of the business logic of the work, and even if the work flow of the work is changed, the source code of the program does not need to be changed. Hereinafter, a program that implements the business logic of each task is referred to as a workflow business processing program. The source code developed by the developer of the workflow application program is called user development code.

[0011]

In the conventional workflow management system, the processing method for calling the state transition request API is fixed for each workflow management system, and thus has a problem in flexibility. The purpose of the present invention is
The purpose is to provide a flexible workflow management system.

[0012]

In order to achieve the object of the present invention, the present invention provides the following processing.

First, a workflow management system according to the present invention includes a workflow definition tool which includes synchronization information, which is information for specifying a processing method for a state transition request API call, in a workflow definition, and which can set synchronization information of the workflow definition. A state transition request synchronous processing program that performs state transition processing of a synchronous processing method, a state transition request asynchronous processing program that performs state transition processing of an asynchronous processing method, and a state transition processing that refers to synchronization information in a workflow definition And a processing method determining program for determining whether to execute by a synchronous processing method or an asynchronous processing method.

Second, the workflow management system of the present invention provides a synchronous state transition request API for designating state transition processing of a synchronous processing method and an asynchronous state transition request API for designating state transition processing of an asynchronous processing method. A state transition request synchronous processing program that performs state transition processing of a synchronous processing method, and a state transition request asynchronous processing program that performs state transition processing of an asynchronous processing method. The state transition of the workflow management system is linked to the workflow application program. A tool for generating a source code of a state transition request issuing program for calling a request API, wherein a synchronous state transition request API is input by inputting synchronization information which is information for specifying a processing method of a state transition request.
Alternatively, there is provided a workflow application program generation tool for generating and separately selecting a source code of a state transition request issuing program that calls an asynchronous state transition request API.

In a third aspect, the workflow management system of the present invention provides a synchronous state transition request API for designating a state transition process of a synchronous processing method and an asynchronous state transition request API for designating a state transition process of an asynchronous processing method. A workflow application which has a state transition request synchronous processing program for performing a state transition processing of a synchronous processing method and a state transition request asynchronous processing program for performing a state transition processing of an asynchronous processing method, and is information accessible from within the workflow application program. The execution environment information includes synchronization information, which is information for specifying a processing method of the state transition request, has a workflow definition tool capable of setting synchronization information of the workflow application execution environment information, is linked to the workflow application program,
A state transition request issuing program that calls a state transition request API of a workflow management system, and switches between calling a synchronous state transition request API with reference to synchronization information of workflow application execution environment information and calling an asynchronous state transition request API. A state transition request issuance program that performs

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below with reference to the drawings. The first example shows one example of the embodiment of the solving means 1. This will be described with reference to FIGS. The workflow management system according to the first embodiment uses one type of state transition request API provided by the workflow management program, refers to synchronization information predefined in the workflow definition data in the workflow management program, and responds to the state transition request. It is characterized in that information on the processing method of the state transition request is excluded from the source code of the workflow business processing program by switching between performing the processing synchronously or asynchronously.

Here, the outline of the basic operation principle of this embodiment will be described. FIG. 3 is used for the description. The user of the workflow management system uses the workflow definition tool 141 to define the possible states of the work and the transition between the states as a workflow definition, and stores the workflow definition data 142. At this time, for each transition of the workflow definition, it is possible to set whether the corresponding transition process is performed synchronously or asynchronously.

The workflow application program 150 has a workflow business processing program 3207 for referring to and updating business data 153, issuing a state transition request API of the workflow management program 140, and implementing business logic.

The state transition request receiving program 206 receives a state transition request API call of the workflow application program 150 and calls the processing method determination program 200. The processing method determination program 200
With reference to the workflow definition data 142, it is determined whether the request transition is to be processed synchronously or asynchronously. If the synchronous processing is determined, the state transition request synchronous processing program 2
01 is called, and when it is determined that the processing is asynchronous, the state transition request asynchronous processing program 202 is called. The state transition request synchronization processing program 201 directly calls the state transition processing program 203 and does not return a response to the caller until the state transition of the work is completed. The state transition request asynchronous processing program 202 executes only processing for temporarily holding the state transition processing request in the permanent storage, returns a response to the caller, and in the actual state transition processing, retrieves the state transition request from the persistent storage later. State transition processing program 20
3 is called. The state transition processing program 203 refers to the workflow definition data 142, calls the worker determination program 204, determines the worker of the work, updates the workflow data 143, and executes the state transition processing. The worker determination program 204 refers to the workflow definition data 142 and, if necessary, refers to the business data 153 to determine a worker.

Next, the configuration of the workflow management system of this embodiment will be described with reference to FIG. The workflow management system according to the present embodiment provides the workflow application program 150 with an API for operating the state of a work, such as a state transition request API, and accesses the workflow definition data 142, the workflow data 143, and the business data 153 to access the work. Management program 14 for managing the status of jobs and assignment to workers
0 and workflow definition data 1 that defines the workflow
42, and workflow definition data 1 for storing workflow definitions such as possible states and transitions of a work and rules for determining a worker.
42 and workflow data 1 for storing the state of the work
43 and the workflow management program 1 by accessing the workflow management system application
It comprises a workflow application program 150 that executes while calling an API provided by 40, and business data 153 that stores data depending on the business.

The workflow definition data 142 stores a state definition table 210 that stores definitions of states that can be taken by a work that depends on each workflow definition, and a definition of transition between states that can be taken by a work that depends on each workflow definition. It comprises a transition definition table 211, a worker determination rule definition table 212 for storing the definition of a worker determination rule used for determining the worker in each state, and a worker definition table 213 for storing the definition of the worker. In the present embodiment, a configuration including the definition information of the worker in the workflow management system is shown. However, a configuration in which data is stored in some external database is also possible. It is assumed to be managed by PMDA.

The workflow data 143 includes a work state table 214 for storing work states and a state transition request table 215 for storing state transition requests. The business operation data 153 according to the present embodiment includes a window operation table 216 that stores data depending on the window operation used in the embodiment.

The workflow management program 140 distributes the processing to the state transition request synchronous processing program 201 or the state transition request asynchronous processing program 202 according to the contents of the transition definition table 211. A state transition request synchronous processing program 201 for realizing synchronous processing of a state transition request by calling the state transition request 203 and a state transition request are stored in a state transition request table 215, and the state transition request is executed by a state transition request fixed interval start program 205 at a timing called. A transition request is extracted from the state transition request table 215, and the state transition request program 203 is called to refer to the state transition request asynchronous processing program 202 for realizing the asynchronous processing of the state transition request and the workflow definition data 142. Then, the worker decision program 204 is called, and the work state table 214 is updated. The state transition processing program 203 for realizing the state transition of the work and the worker decision rule definition table 212 are referred to, and the worker decision rules are evaluated. Then, if necessary, the worker definition program 213 accesses the worker definition table 213 and the window work table 216 to determine the worker.
4 and a state transition request fixed interval start-up program 205 that periodically triggers the state transition request asynchronous processing program 202 to trigger the asynchronous execution of the state transition.
And a state transition request reception program 206 that receives a call of the state transition request API and calls the processing method determination program 200.

The workflow definition tool 141 provides a workflow definition user with a GUI for creating a workflow definition, and stores the created workflow definition in the workflow definition data 142.
Having.

Hereinafter, this embodiment will be described in more detail. A table constituting the workflow definition data 142 will be described with reference to FIGS.

FIG. 4 shows the structure of the state definition table 210. The state definition table 210 has the workflow definition name 4
00, state name 401, and worker determination rule name 402. The workflow definition name 400 is
Indicates the workflow definition to which the state belongs. State name 401
Is data that uniquely identifies a state in the same workflow definition. The worker determination rule name 402 is the worker determination rule name 600 in the worker determination rule definition table 212.
See The records of the state definition table 210 are stored in the workflow definition storage procedure 2602 of the workflow definition program 209, and are referred to in the state transition processing procedure 1600 of the state transition processing program 203.

FIG. 5 shows the structure of the transition definition table 211. The transition definition table 211 has the workflow definition name 5
00, a transition ID 501, a transition source state name 502, a transition destination state name 503, and synchronization information 504. The workflow definition name 500 indicates the workflow definition to which the transition belongs. The transition ID 501 is data for uniquely identifying a transition in the same workflow definition. The transition source state name 502 indicates the state name of the state that is the transition source of the transition.
The transition destination state name 503 indicates a state name of a state to be a transition destination of the transition. The synchronization information 504 is a specification of whether to synchronously or asynchronously process the state transition request, and is either “synchronous” or “asynchronous”. Take a value.

The record of the transition definition table 211 is stored in the workflow definition storage procedure 2602 of the workflow definition program 209, and is referred to in the processing method determination procedure 1300 of the processing method determination program 200 and the state transition processing procedure 1600 of the state transition processing program 203. Is done.

FIG. 6 shows an operator determination rule definition table 21.
This is the structure of FIG. Worker determination rule definition table 212
Are the worker determination rule name 600 and the worker determination rule 60
1 is table data. Worker determination rule name 6
00 is data for uniquely identifying the worker determination rule 601. The worker determination rule 601 is character string data interpreted and executed by the worker determination program 204.

The record of the worker decision rule definition table 212 is stored by some method before the record of the state definition table 210 which refers to the worker decision rule name 600 of the record is stored. Reference is made to the operator determination procedure 1700 of 204.

FIG. 7 shows the structure of the worker definition table 213. The worker definition table 213 stores the worker ID 70
The table data is composed of 0 and a role ID 701. The worker ID 700 is data for uniquely identifying the worker. The role ID 701 is an example of an attribute of a worker referred to in the evaluation of the worker determination rule according to the present embodiment.

The record of the worker definition table 213 is
The information is managed in conjunction with a job-dependent worker management mechanism, and is stored, changed, and deleted in some way. In the workflow management system, the worker is referred to in the worker determination procedure 1700 of the worker determination program 204 as necessary.

Next, a table constituting the workflow data 143 will be described with reference to FIGS. FIG. 8 shows the structure of the work state table 214. The work state table 214 is tabular data including a work ID 800, a workflow definition name 801, a state name 802, an operator ID 803, and a state completion flag 804. Work ID
800 is data for uniquely identifying a work. The workflow definition name 801 is the name of the workflow definition to which the work depends. The state name 802 is data indicating the state of the work. The worker ID 803 is identification information of the worker determined as the worker in the state of the state name 802 of the work. The status completion flag 804 is a flag indicating whether or not the status has been completed.

In the workflow management system according to the present embodiment, the state transition processing is performed by the state completion flag 804 of the transition source state.
Is set to TRUE, and the state name of the state of the transition destination is the state name 802.
The state completion flag 804 is realized by inserting a FALSE record into the work state table 214. The record of the work state table 214 is stored in the state transition processing procedure 160 of the state transition processing program 203.
0, stored and updated, and referred to in the processing method determination procedure 1300.

FIG. 9 shows the structure of the state transition request table 215. The state transition request table 215 contains the work ID 9
The table data is composed of 00, a workflow definition name 901, and a transition ID 902. The work ID 900 is an identifier of the work that is the target of the state transition request. The workflow definition name 901 is the name of the workflow definition to which the work for which the state transition request is made depends. The transition ID 902 is an identifier of a transition having the state specified by the state transition request API as the transition source state.

The records of the state transition request table 215 are stored in the state transition request storage procedure 1501 of the state transition request asynchronous processing program 202, and are referenced and deleted by the state transition request fetch procedure 1502 of the state transition request asynchronous processing program 202. .

Next, a table constituting the business data 153 will be described with reference to FIG. Counter business table 2
Reference numeral 16 denotes table data that stores work-dependent data of the window work referred to in the present embodiment and includes a work ID 1000 and a transaction amount 1001. The records in the window business table 216 are stored, referenced, and updated by the workflow business processing program 3207, and are referred to by the worker determination procedure 1700 of the worker determination program 204 as necessary.

Hereinafter, the operation of the workflow management program 140 will be described in detail with reference to FIGS. FIG. 11 shows an API provided by the workflow management program 140, and includes a state transition request API 1100. The state transition request API 1100 includes, as an input argument,
A work ID and a state name are taken.

The configuration of each program will be described. The state transition request reception program 206 executes the state transition request API 11
It is composed of a state transition request procedure 1200 that implements the process of 00.

The processing method determining program 200 is composed of a processing method determining procedure 1300 which determines the processing method of the state transition request with reference to the workflow data 143 and the workflow definition data 142.

State transition request synchronous processing program 201
Is composed of a state transition request synchronization processing procedure 1400.

State transition request asynchronous processing program 202
Is a state transition request asynchronous processing procedure 1500, a state transition request storage procedure 1501 for storing a state transition request in permanent storage, a state transition request retrieval procedure 1502 for extracting a state transition request from permanent storage, and A state transition processing start procedure 1503 is called up, takes out the state transition request stored in the permanent storage, and starts the state transition processing program 203.

The state transition processing program 203 executes an actual state transition processing.
It consists of.

The worker decision program 204 is composed of a worker decision procedure 1700 which decides a worker by referring to the workflow definition data 142 and, if necessary, the business data 153.

State transition request fixed interval start program 20
5 is called when the workflow management program 140 is started, and the state transition processing start procedure 150 is executed at regular intervals.
3 comprises a monitoring start procedure 1800.

Next, the operation of each procedure will be described. First, the state transition request procedure 1200 includes a state transition request AP.
This is a procedure that implements I1100, and calls the processing method determination procedure 1300 by passing the argument as it is.

Next, the operation of the processing method decision procedure 1300 will be described with reference to FIG. Processing method determination procedure 13
00 takes a work ID and a state name as input arguments. First, the work state table 214 is searched 1900 using the work ID of the argument and the value of the state name as keys. here,
The record of the work state table 214 does not hit,
Alternatively, if the field value of the status completion flag 804 of the hit record is TRUE 1901, an error is returned to the calling source 1909, and the processing ends. Otherwise, 19
State completion flag 80 of the record that was hit in the search of 00
Update 1902 the field value of 4 to TRUE. Then 19
The search is executed on condition that the workflow definition name 801 field value and the argument state name value of the record hit in the search of 00 match the workflow definition name 500 and the transition source state name 502 of the transition definition table 211, respectively.
903. 1 when a record is hit in the search of 1903
Go to 905, if no hit, go to 1908 1
904. In 1905, the synchronization information 504 field value of the record hit in 1903 is determined. In the case of “synchronization”, the process proceeds to 1906. In the case of "asynchronous", the process proceeds to 1907. In 1906, the value of the work ID of the argument and 1904
Definition name 50 of the record that was hit in the search
The state transition request synchronization processing procedure 1400 is called using the 0 field value and the transition ID 501 field value as arguments.
In step 1907, the state transition request asynchronous processing procedure 1500 is called using the work ID value of the argument, the workflow definition name 500 field value of the record hit in the search in 1904, and the transition ID 501 field value as arguments. End.

Next, the state transition request synchronization processing procedure 140
The operation of 0 will be described. State transition request synchronization processing procedure 14
00 takes a work ID, a workflow definition name, and a transition ID as input arguments. In actual processing, only the value of the argument is passed to the state transition processing procedure 1600 as it is.

Next, the state transition request asynchronous processing procedure 15
00 will be described. The state transition request asynchronous processing procedure 1500 includes a work ID, a workflow definition name, and a transition I.
Take D as an input argument. In the actual processing, only the value of the argument is passed to the state transition request storage procedure 1501 as it is.

Next, the operation of the state transition request storage procedure 1501 will be described. The state transition request storage procedure 1501 is:
A work ID, a workflow definition name, and a transition ID are taken as input arguments, and a record in which the value of each argument is a field value of the work ID 900, the workflow definition name 901, and the transition ID 902 is inserted into the state transition request table 215, and the process ends.

Next, a state transition request fetch procedure 1502
Will be described. Status transition request fetch procedure 1502
Takes a work ID, a workflow definition name, and a transition ID as output arguments and returns a boolean value.

First, from the state transition request table 215,
Select any one record. If not selected, FALSE is returned to the caller, and the processing ends. If a record is selected, the work ID 9 of the selected record
The 00 field value, the workflow definition name 901 field value, and the transition ID 902 field value are set as output arguments, respectively, and the selected record is deleted from the state transition request table 215. Next, call the TRUE
And exit.

Next, the operation of the state transition processing start procedure 1503 will be described. First, a state transition request fetching procedure 15
Call 02. If the answer is FALSE, end. TR
In the case of the UE, the value of the output argument is passed as it is to the state transition processing procedure 1600 and called, and the processing ends.

Next, the operation of the state transition processing procedure 1600 will be described with reference to FIG. State transition processing procedure 16
00 takes a work ID, a workflow definition name, and a transition ID as input arguments.

First, the workflow definition name of the argument and the transition I
A search is performed 2300 based on the condition that the value of D matches the workflow definition name 500 and the transition ID 501 field value of the transition definition table 211. A search is performed on condition that the value of the workflow definition name of the argument and the transition destination state name 503 field value of the record hit in 2300 match the workflow definition name 400 field value and the state name 401 field value of the state definition table 210. Execution 2301.
A worker determination procedure 1700 is called 2302 by passing the worker determination rule name 402 field value of the record hit in 2301 and the work ID of the argument. The values of the work ID and the workflow definition name of the argument, the field value of the transition destination state name 503 of the data retrieved in 2300, and 2
The value of the worker ID acquired in 302 and “FALSE”
The values are Work ID 800 and Workflow Definition Name 8, respectively.
01, state name 802, worker ID 803, and state completion flag 804 are set as field values and inserted into the work state table 2303. End.

Next, the operation of the worker determination procedure 1700 will be described. The worker determination procedure 1700 takes a work ID and a worker determination rule name as input arguments and a worker ID as an output argument.

First, the worker determination rule definition table 212 is searched using the worker determination rule name of the argument as a key, and the work ID of the argument is embedded as needed in the field value of the worker determination rule 601 of the record. Then, the operator definition table 213 is searched. For example, assuming that the embedded variable is “% work ID%” and the value of the work ID of the argument is “80010”, the worker determination rule on the first line in FIG. 6 becomes “IF window business table.work ID = 8001
0 AND Service window table. Transaction amount> = 100
0000 THEN role ID = 60010 ELSE role ID = 60011 ". As a result of evaluating this rule, the role ID
= 60010, and the record of the worker definition table 213 of the worker ID 90020 is obtained. The field value of the worker ID 700 of the record is set in the output argument worker ID, and the processing ends.

Next, the operation of the monitoring start procedure 1800 will be described. The monitoring start procedure 1800 is called when the workflow management program 140 is started. It is assumed that the running flag referred to in the procedure is TRUE at startup and FALSE at termination.

First, the state transition processing start procedure 1503 is called. At regular intervals or when the running flag is FALS
Wait until it becomes E. Determine whether the running flag is TRUE,
If YES, return to the procedure start point. If NO, end.

Hereinafter, the operation of the workflow definition tool 141 will be described in detail with reference to FIG. 2, FIG. 14, and FIG.

The workflow definition program 209 is a workflow definition procedure 2600 which is a main flow of the workflow definition, displays a workflow definition screen, manages each object on the screen, acquires an attribute of the object, and converts it into an internal data structure. And a workflow definition storage procedure 2602 for storing the internal data structure generated by the workflow definition screen display procedure 2601 in the workflow definition data 142.

Next, the operation of each procedure will be described. The operation of the workflow definition procedure 2600 will be described. First, the workflow definition screen display procedure 2601 is called. Next, it is determined whether the return value from the workflow definition screen display procedure 2601 is TRUE. If NO, end. If YES, workflow definition storage procedure 260
Call 2 and end.

Next, workflow definition screen display procedure 2
The operation of 601 will be described. First, FIG. 14 shows an image displayed on the screen of the display 123 in the workflow definition screen display procedure 2601. Also,
The workflow definition tool 141 can receive input of characters and symbols from a keyboard, and can operate a mouse pointer 2906 indicating a point on the screen using a mouse. The user can define a workflow by dragging and dropping the state object 2907 and the transition object 2908 from the tool box 2901 to the layout box 2900. The workflow definition name is set in a text box 2911. State object 2 attached to layout box 2900
By double-clicking the mouse 909 or the transition object 2910 with a mouse, a state attribute setting dialog 2903 and a transition attribute setting dialog 2902 can be opened, respectively, and attributes can be set. In particular, in the transition attribute setting dialog 2902, the setting of the attribute linked to the transition processing method is performed by the transition method radio box 29.
12 is possible.

When the created workflow definition is stored in the workflow definition data 142, an OK button 290 is displayed.
4 is canceled by clicking the CANCEL button 2905. Layout box 2
The attributes of each object 900 can be referred to from the workflow definition screen display procedure 2601.

An OK button 2904 or a CANCEL button 2905 is clicked, and control returns to the workflow definition screen display procedure 2601 to determine whether or not the pressed button is OK. If no, layout box 2
900 and the tool box 2901 are erased, FALSE is returned to the caller, and the process ends. If YES, the attributes of each object other than the transitions arranged on the layout box 2900 are copied to the workflow definition tool 1
41, stored in a workflow definition structure variable accessible. The structure of the workflow definition structure variable is a workflow definition structure 3000 shown in FIG. The state structure 3001 and the transition structure 3002 are managed in a variable-length list. Next, a unique ID in the corresponding workflow definition is assigned to each transition object 2910 arranged on the layout box 2900. The attribute of each transition object 2910 is stored in a workflow structure variable. At this time, “asynchronous” is set in the synchronization information 3003 when the selection in the transition method radio box 2912 is focused on the response, and “synchronous” is set in the transition time radio box 2912 when the transition time is emphasized. Layout box 2900 and tool box 2
901 is deleted, TRUE is returned to the caller, and the processing is ended.

Next, a workflow definition storage procedure 2602
Will be described. Workflow definition storage procedure 260
2 stores the respective attributes of the workflow definition structural variables in the state definition table 210 and the transition definition table 211, respectively, and ends. Next, FIG. 1 is a block diagram of an example in which a workflow management system to which the present invention is applied is realized as an apparatus.
Shown in A server computer 100 and a plurality of client computers 101 are connected by a network 102.

The server computer 100 has a CPU 120, a keyboard 121, a mouse 122, a display 123, a communication device 124, an auxiliary storage device 125, and a main storage device 126.
And the bus 127, and the workflow definition data 142 and the workflow data 14 on the auxiliary storage device 125.
3 is loaded, and the workflow management program 140 and the workflow definition tool 141 are loaded on the main storage device 126 and executed. The workflow definition data 142 and the workflow data 143 are created when the workflow management program 140 is installed. The workflow definition data 142 is updated when the workflow definition tool 141 creates a workflow definition, and is referred to when the workflow management program 140 operates a work.
The workflow data 143 is referred to and updated when a work is operated by the workflow management program 140.

The client computer 101 has a CPU
130, a keyboard 131, a mouse 132, a display 133, a communication device 134, an auxiliary storage device 135, a main storage device 136, and a bus 137. The auxiliary storage device 135 stores business data 153 and workflow application execution environment information 154. , Main storage device 136
Workflow application program 150 and workflow application program generation tool 1
51 and the workflow application execution environment information setting tool 152 are loaded and executed. The business data 153 can be accessed from the server computer 100 via the network 102. The workflow application execution environment information 154 is created when the workflow application program 150 is installed, and is referred to when the workflow application program 150 is executed. The workflow application execution environment information 154 can be referred to and updated by the workflow application execution environment information setting tool 152. The business data needs to be created before the execution of the workflow application program 150, is referred / updated when the workflow application program 150 is executed, and is referred to by the workflow management program 140 as needed.

In the same manner as in the present embodiment, it is possible to realize the case where the synchronization information is provided for each state, the case where the synchronization information is provided for each workflow, and the case where the synchronization information is included in the environment information of the workflow management program.

The second example shows an example of the embodiment of the solving means 2. This will be described with reference to FIGS. In the workflow management system according to the second embodiment, the workflow management program includes a synchronous state transition request A
A workflow application program that provides two types of state transition request APIs, a PI and an asynchronous state transition request API, but receives synchronization information and provides one type of state transition request interface. A workflow application program generation tool that determines whether to generate a code for issuing a synchronous state transition request API of a workflow management program or a code for issuing an asynchronous state transition request API based on input synchronization information. And provide a workflow business processing program 3
The source code 207 is characterized in that a state transition request is issued using the interface of the state transition request issuing program, thereby excluding information on the state transition processing method from the user development code. The block diagram of the workflow management system of the present embodiment is the same as FIG.

The configuration of the workflow management system of this embodiment will be described with reference to FIG. This system includes an execution system 3210 and a development system 3220. The execution system 3210 provides the workflow application program 150 with an API for operating the state of the work including the state transition request API, and the workflow definition data 142 and the workflow data 143.
Management program 140 that manages the state of work and assignment to workers while accessing the work data and the work data 153, and workflow definition data that stores workflow definitions such as possible states and transitions of work and rules for determining workers 142, a workflow data 143 that stores the state of the work, and a workflow application program 150 that accesses the business data 153 of the workflow management system application business and calls and executes an API provided by the workflow management program 140, and depends on the business. It is composed of business data 153 for storing data. The development system 3220 includes a workflow application program generation tool 151.

The workflow definition data 142 stores a state definition table 210 that stores definitions of states that can be taken by a work that depends on each workflow definition, and a definition of transition between states that can be taken by a work that depends on each workflow definition. It is composed of a transition definition table 3211, a worker determination rule definition table 212 for storing the definition of a worker determination rule used for determining the worker in each state, and a worker definition table 213 for storing the definition of the worker. The workflow data 143 includes a work state table 214 for storing a state of a work and a state transition request table 3215 for storing a state transition request. The business operation data 153 according to the present embodiment includes a window operation table 216 that stores data depending on the window operation used in the embodiment.

The workflow management program 140 stores the state transition request in the state transition request table 3215 and the state transition request synchronous processing program 3201 for realizing the synchronous processing of the state transition request by calling the state transition processing program 3203. A state transition request is extracted from the state transition request table 3215 at a timing called by the transition request fixed interval start program 205, and the state transition request asynchronous processing program 3202 that implements the asynchronous processing of the state transition request by calling the state transition processing program 3203. And workflow definition data 1
A state transition processing program 32 that implements the state transition of the work by calling the worker determination program 204 and updating the work state table 214 with reference to the program 42.
03 and the worker determination rule definition table 212 to evaluate the worker determination rule, and access the worker definition table 213 and the window work table 216 as necessary to determine the worker. Decision program 20
4 and the state transition request asynchronous processing program 3202 which is periodically invoked to trigger the state transition asynchronous execution at regular intervals.
5, synchronous state transition request API and asynchronous state transition request A
A state transition request receiving program 3 that accepts a call to a PI and calls the state transition request synchronous processing program 3201 or the state transition request asynchronous processing program 3202
206.

The table constituting the workflow definition data 142 will be described with reference to FIG. FIG. 17 shows the structure of the transition definition table 3211. The transition definition table 3211 includes a workflow definition name 3300, a transition ID
3301, transition source state name 3302, transition destination state name 330
3 is tabular data. The workflow definition name 3300 indicates the workflow definition to which the transition belongs. The transition ID 3301 is data that uniquely identifies a transition within the same workflow definition. The transition source state name 3302 indicates the state name of the state that is the transition source of the transition.
03 indicates a state name of a state to be a transition destination of the transition.

The record of the transition definition table 3211 is
It is stored in the workflow definition storage procedure 2602 of the workflow definition program 209, and is referred to by the state transition processing procedure 3900 of the state transition processing program 3203. The state definition table 210, the worker determination rule definition table 212, and the worker definition table 213 are the same as in the first embodiment.

Next, a table constituting the workflow data 143 will be described with reference to FIG. FIG. 18 shows the structure of the state transition request table 3215. The state transition request table 3215 is tabular data including a work ID 3400, a workflow definition name 3401, and a state name 3402. The work ID 3400 is the identifier of the work that is the target of the state transition request. The workflow definition name 3401 is the name of the workflow definition to which the work that is the target of the state transition request depends. State name 34
02 is the state name specified by the state transition request API.

The record of the state transition request table 3215 is stored in the state transition request storage procedure 3801 of the state transition request asynchronous processing program 3202, and is referred / deleted by the state transition request fetch procedure 3802 of the state transition request asynchronous processing program 3202. . The work state table 214 is the same as in the first embodiment. The structure of the table constituting the business data 153 is the same as in the first embodiment.

Hereinafter, the operation of the workflow management program 140 will be described in detail with reference to FIGS. 19 to 22. FIG. 19 shows an API provided by the workflow management program 140, which includes a synchronous state transition request API 3500 and an asynchronous state transition request API 3501. Synchronous state transition request API3500 and asynchronous state transition request API3
Reference numeral 501 denotes a work ID and a state name as input arguments.

The configuration of each program will be described. The state transition request receiving program 3206 executes the synchronization state transition request AP
Synchronous state transition request procedure 3 that implements I3500 processing
600, and an asynchronous state transition request procedure 3601 that implements the processing of the asynchronous state transition request API 3501.

State transition request synchronous processing program 3201
Is composed of a state transition request synchronization processing procedure 3700.

State transition request asynchronous processing program 320
2 is a state transition request asynchronous processing procedure 3800, a state transition request is stored in a permanent storage, a state transition request storage procedure 3801, and a state transition request is extracted from a permanent storage.
A state transition request fetch procedure 3802, which is called at regular intervals, fetches a state transition request stored in the persistent storage, and starts a state transition processing program 3203;
It comprises a state transition processing start procedure 3803.

The state transition processing program 3203 executes the actual state transition processing.
0.

The worker determination program 204 and the state transition request fixed interval activation program 205 are the same as in the first embodiment.

Next, the operation of each procedure will be described. First, the operation of the synchronization state transition request procedure 3600 will be described with reference to FIG.
This will be described with reference to FIG. The synchronous state transition request procedure 3600 takes a work ID and a state name as input arguments.

First, the work state table 214 is searched using the work ID of the argument and the value of the state name as keys 43.
00. Here, when the record of the work state table 214 does not hit, or when the field value of the state completion flag 804 of the hit record is TRUE 430
1. An error is returned to the caller 4304, and the processing ends. In other cases, the field value of the status completion flag 804 of the record hit in the search of 4300 is updated to TRUE.
302. Next, the workflow definition name 801 field value of the record hit in the search of 4300 and the work I of the argument
State transition request synchronization processing procedure 3 by passing D and the value of the state name
Call 700. End.

Next, the asynchronous state transition request procedure 3601
Will be described with reference to FIG. The asynchronous state transition request procedure 3601 takes a work ID and a state name as input arguments. First, the work state table 214 is searched 440 using the work ID of the argument and the value of the state name as keys.
0. Here, when the record of the work state table 214 does not hit, or when the field value of the state completion flag 804 of the hit record is TRUE 4401,
An error is returned to the caller, and 4404 ends. Otherwise, the field value of the status completion flag 804 of the record hit in the search of 4400 is updated to TRUE 440.
2. Next, the workflow definition name 801 field value of the record hit in the search in 4400, the work ID of the argument, and the value of the state name are passed, and the state transition request asynchronous processing procedure 38
Call 00. End.

Next, the state transition request synchronization processing procedure 370
0 takes a work ID, a workflow definition name, and a state name as input arguments. In actual processing, only the value of the argument is passed to the state transition processing procedure 3900 as it is.

Next, the state transition request asynchronous processing procedure 38
00 takes a work ID, a workflow definition name, and a state name as input arguments. In actual processing, only the value of the argument is passed to the state transition request storage procedure 3801 as it is.

Next, the operation of the state transition request storage procedure 3801 will be described. The state transition request storage procedure 3801 is:
A work ID, a workflow definition name, and a state name are taken as input arguments, and a record in which the values of the work ID, the workflow definition name, and the state name of the arguments are field values is inserted into the state transition request table 3215, and the processing ends.

Next, a state transition request fetch procedure 3802
Will be described. State transition request fetch procedure 3802
Takes a work ID, a workflow definition name, and a state name as output arguments and returns a boolean value. First, an arbitrary record is selected from the state transition request table 3215. Determine if a record was selected, and if not,
Returns FALSE to the caller and ends. When the selected record is selected, the work ID 3400 field value, the workflow definition name 3401 field value, and the state name 3402 field value of the selected record are set as output arguments, and the selected record is stored in the state transition request table 32.
15 to delete. Returns TRUE to the caller and ends.

Next, the operation of the state transition processing start procedure 3803 will be described. First, a state transition request fetch procedure 38
Call 02. If the answer is FALSE, end. TR
In the case of the UE, the value of the output argument is passed to the state transition processing procedure 3900 as it is and called. End.

Next, the operation of the state transition procedure 3900 will be described with reference to FIG. State transition processing procedure 39
00 takes a work ID, a workflow definition name, and a state name as input arguments.

First, a search is performed 4500 on condition that the values of the workflow definition name and the state name of the argument match the workflow definition name 3300 and the transition source state name 3302 field value of the transition definition table 3211. Next, it is confirmed that the value of the workflow definition name of the argument and the transition destination state name 3303 field value of the record hit in 4500 match the workflow definition name 400 field value and the state name 401 field value of the state definition table 210. Search execution 4501 as a condition.Worker determination procedure 1700 is called by passing the worker determination rule name 402 field value of the record hit in 4501 and the work ID of the argument 4
502. The work ID of the argument, the value of the workflow definition name, and the transition destination state name 3303 of the data retrieved by 4500
, The value of the worker ID acquired in 4502, and the “FALSE” value are respectively assigned to the work ID 800, the workflow definition name 801, the state name 802, and the worker ID.
450 which is set as the field value of the state completion flag 803 and the state completion flag 804 and inserted into the work state table 214
3. End.

Hereinafter, the workflow management program 140
Details of the operation of the workflow application program generation tool 151 according to the present embodiment, which can select a processing method for the state transition request, will be described with reference to FIGS.

The workflow application program generation tool 151 allows the user to select a processing method of the workflow management program 140 for a state transition request, a transition method selection procedure 4600, generates a state transition request issuing program, and generates a state transition request issuing program. It has a procedure 4601 and a main processing procedure 4602 for controlling the main flow of the workflow application program 150.

The state transition request issuing program 3208 generated by the workflow application program generation tool 151 is a workflow business processing program 320.
7 that can be called from the server 7.

The state transition request issuing procedure 4700 is called by passing the work ID and the state name as input arguments to the synchronous state transition request API 3500 or the asynchronous state transition request API 3501 of the workflow management program 140.

Hereinafter, each procedure of the workflow application program generation tool 151 will be described with reference to FIG. First, the main processing procedure 460
Operation 2 will be described. The main processing procedure 4602 calls the transition method selection procedure 4600 at some timing. After that, the state transition request issuing program generation procedure 4601 is called at some timing.
End.

Next, the operation of the transition method selection procedure 4600 will be described with reference to FIG.

First, the transition method selection procedure 4600 displays a transition method selection screen 5000 on the screen of the display 133 and waits for a user selection. The user selects an item in the transition method list box 5001 with the mouse 132 and clicks the selection button 5002 to select the item.
A transition method can be selected.

Next, the transition method selected on the transition method selection screen 5000 is stored in a transition method variable accessible in the workflow application program generation tool 151, and the processing ends.

Next, the operation of the state transition request issuing program generation procedure 4601 will be described. First, the value stored in the transition method variable accessible in the workflow application program generation tool 151 is determined.
In the present embodiment, if the value indicates that the transition time is important, the synchronization state transition request A of the workflow management program 140 is executed.
A code for calling the PI 3500 is generated, and if the value indicates that importance is placed on the response, the asynchronous state transition request API 35
Generate code to call 01.

When the workflow application program generation tool 151 generates the state transition request issuance program 3208 for calling the synchronous state transition request API 3500, the state transition request issuance procedure 4700 uses the values of the work ID and the state name passed as arguments as arguments. As the synchronous state transition request API 35 of the workflow management program 140
00, returns the received reply as it is, and ends.

When the workflow application program generation tool 151 executes the asynchronous state transition request API 3501
The state transition request issuance procedure 4700 in the case of generating the state transition request issuance program 3208 that calls the asynchronous state transition request API of the workflow management program 140 using the values of the work ID and the state name passed as arguments as arguments
Call 3501 and return the received reply as it is,
finish.

The workflow operation processing program 3207 of the workflow application program 150
A task process is performed for the work ID to be processed, and the state transition request issuance procedure 4700 of the state transition request issuance program 3208 is called with the work ID and the state name to be processed as arguments. In the same manner as in the present embodiment, it is also possible to realize a case where a workflow definition is input to a workflow application program generation tool.

The third example shows an example of the embodiment of the solving means 3. This will be described with reference to FIGS. In the workflow management system according to the third embodiment, the workflow management program includes a synchronous state transition request A
Two types of state transition request APIs, PI and asynchronous state transition request API, are provided. A workflow application execution environment information setting tool that holds synchronization information in the execution environment information of the workflow application program and can set the synchronization information Setting is possible, and the state transition request issuance program refers to the synchronization information,
Perform synchronous / asynchronous calls at runtime.

In the source code of the workflow business processing program 3207, which is a user development code, a state transition request is issued using the interface of the state transition request issuing program, so that the state transition processing method can be performed from the user development code. Eliminate information. The block diagram of the workflow management system of the present embodiment is the same as FIG.

The configuration of the workflow management system of this embodiment will be described with reference to FIG. The present system provides the workflow application program 150 with an API for operating a state of a work including a state transition request API.
A workflow management program 140 that manages the state of the work and the assignment to the worker while accessing the workflow definition data 142, the workflow data 143, and the business data 153; An AP provided by a workflow management program 140 that accesses workflow definition data 142 for storing workflow definitions such as decision rules, workflow data 143 for storing the state of a work, and business data 153 for a workflow management system application business.
It consists of a workflow application program 150 that executes while calling I, and business data 153 that stores data dependent on the business.

The workflow management program 140, the workflow definition data 142, and the workflow data 143
And the business data 153 are the same as those in the second embodiment. The differences from the second embodiment are a state transition request issuing program 5500, workflow application execution environment information 154, and a workflow application execution environment information setting tool 152. The state transition request issuance program 5500 includes a state transition request issuance procedure 5505.
It consists of.

First, the contents of the workflow application execution environment information 154 will be described with reference to FIG. The workflow application execution environment information 154 is data that can be referenced from the workflow application program 150, and is data in which a name and a value are associated. For example, in FIG. 25, “asynchronous” is set as the synchronization information 5600 in the workflow application execution environment information 154.

Next, the state transition request issuing program 550
The processing contents of the 0 state transition request issuing procedure 5505 will be described. The state transition request issuance procedure 5505 includes the work ID
And the state name as input arguments. First, it is determined whether the synchronization information 5600 of the workflow application execution environment information 154 is present. If the data indicating the designation of the synchronous processing is set, the synchronous state transition request API 3500 is called by passing the work ID and the state name of the arguments. If the data indicating the designation of the asynchronous process is set, the asynchronous state transition request A is passed by passing the work ID and the state name of the arguments.
Call PI3501. Return the response received as a result of the API call and exit.

Hereinafter, the operation of the workflow application execution environment information setting tool 152 capable of setting the synchronization information 5600 in the workflow application execution environment information 154 will be described in detail with reference to FIGS. 24 to 26.

The workflow application execution environment information setting tool 152 allows the user to select the processing method of the workflow management program 140 for the state transition request, and sets the transition method selection procedure 5800 and the workflow application execution environment information 154. Execution environment information setting procedure 58
01 and a main processing procedure 5802 for controlling the main flow of the workflow application execution environment information setting tool 152.

Hereinafter, the procedures of the workflow application execution environment information setting tool 152 will be described. First, the operation of the main processing procedure 5802 will be described. The main processing procedure 5802 calls the transition method selection procedure 5800 at some timing. After that, the workflow application execution environment information setting procedure 5801 is called at some timing.
Then end.

Next, the operation of the transition method selection procedure 5800 will be described with reference to FIG. First, the transition method selection procedure 5800 displays the transition method selection screen 6100 of FIG. 26 on the screen of the display 133, and waits for a user selection. The user can select a transition method by selecting an item in the transition method list box 6101 with the mouse 132 and clicking a selection button 6102.

Next, the transition method selected on the transition method selection screen 6100 is stored in a transition method variable accessible in the workflow application execution environment information setting tool 152, and the process ends. Next, the operation of the workflow application execution environment information setting procedure 5801 will be described with reference to FIG.

First, the value stored in the transition method variable accessible in the workflow application execution environment information setting tool 152 is determined. In this embodiment, if the value indicates that the transition time is important, the data indicating the designation of the synchronization processing is set in the synchronization information 5600 of the workflow application execution environment information 154. If the value indicates that the response is important, the workflow is used. Data indicating the designation of asynchronous processing is set in the synchronous information 5600 of the application execution environment information 154.

In the same manner as in this embodiment, it is possible to realize a case where a workflow definition is input to a workflow application program. The workflow management system according to the first to third embodiments controls the processing performance by switching between the synchronous processing method and the asynchronous processing method based on the predefined information, for the processing method for the work state transition request. .

In the following embodiment, a workflow for relatively controlling the processing performance by setting priorities and restricting the available computer resources based on the predefined information for the processing for the work state transition request. The management system is described. Such relative processing performance control is particularly effective in a system shared by a plurality of users in an environment where computer resources are limited.

For example, the service of the workflow management system is provided by an ASP (Applicati
When providing in the form of an application hosting service such as on service provider, management of the amount of computer resources used for processing and management of the processing schedule for each customer or business are performed appropriately, and quality services according to the contract contents are provided. Must provide.
Even in such a case, the processing performance control method of the present invention can be applied.

The fourth embodiment is an embodiment of a workflow management system for controlling the processing priority of a state transition request based on previously defined transition processing definition information. An example is shown in which the processing priority is defined and the processing priority is controlled for each workflow definition to which the work to be subjected to the state transition request belongs. This will be described with reference to FIGS.

The block diagram of the workflow management system of this embodiment is the same as that of FIG. FIG. 27 shows a system configuration in this embodiment. In this system configuration, in the system configuration shown in FIG. 2, a workflow definition table 6201 for storing the definition of various attributes of the workflow definition is added as the workflow definition data 142. In this embodiment, the state transition request fetch procedure 1502 and the workflow definition screen display procedure 26
01, the process of the workflow definition storage procedure 2602 is changed. FIG. 27 shows only differences from the first embodiment, and does not describe details of the entire system configuration. Hereinafter, this embodiment will be described in detail. In order to avoid redundant description, only the differences from the first embodiment are shown here.

FIG. 28 shows a workflow definition table 620.
This is the structure of FIG. Workflow definition table 6201
Is table data including a workflow definition name 6311 and a priority 6312. Workflow definition name 6311
Is data that uniquely identifies the workflow definition.
The priority 6312 is a designation of a priority when processing a state transition request, and takes an arbitrary numerical value.

The record of the workflow definition table 6201 is stored in the workflow definition storage procedure 2602 of the workflow definition program 209, and is referred to by the state transition request fetch procedure 1502 of the state transition request asynchronous processing program 202.

Next, the operation of the state transition request fetch procedure 1502 in this embodiment will be described. In this embodiment, the state transition request fetch procedure 1502 is a work ID
And a workflow definition name and a transition ID as output arguments, and return a boolean value.

First, the workflow definition name 901 and the workflow definition table 62 in the state transition request table 215
01 using the workflow definition name 6311 as a key and the state transition request table 215 and the workflow definition table 6
201 are combined, and the first record of the result of sorting in the descending order of the priority 6312 value of the workflow definition table 6201 is selected. If not selected, FALSE is returned to the caller, and the processing ends. When a record is selected, the work ID 900 field value of the selected record, the workflow definition name 901 field value, and the transition I
The D902 field value is set in each output argument, and the selected record is deleted from the state transition request table 215. Next, return TRUE to the caller and end.

Next, the operation of the workflow definition screen display procedure 2601 in this embodiment will be described. First, FIG. 29 is a diagram showing an image displayed on the screen of the display 123 in the workflow definition screen display procedure 2601 according to the present embodiment. The difference from the first embodiment is the state transition processing for each workflow definition. Is that a text box 6411 for designating the priority of is added.

FIG. 30 is a flowchart showing a workflow definition screen display procedure 2601 in this embodiment.
FIG. 35 is a diagram showing a workflow definition structure 6511 for storing information related to the workflow definition defined on the screen of FIG.
The difference from the first embodiment is that a priority field 6512 for storing the priority input in the text box 6411 is added.

Next, the operation of the workflow definition storage procedure 2602 in this embodiment will be described. In this embodiment, the workflow definition storage procedure 2602 stores the attributes of the workflow definition structure 6511 in the workflow definition table 6201, the state definition table 210, and the transition definition table 211, respectively, and ends.

In the same manner as in this embodiment, it is also possible to realize a case where the priority is set for each state, each transition, and each workflow application program.

As described above, in the workflow management system according to the present embodiment, the processing priority of the state transition request is determined for each workflow, for each workflow definition, each state, each transition, and each workflow application program. It can be easily set with tools in small units.

The fifth embodiment is an example of a workflow management system that controls the amount of computer resources used in processing a state transition request based on predefined transition process definition information. The maximum main storage capacity that can be used for processing a request and the main storage capacity that is required for processing one state transition request are defined. 5 shows an example of controlling the storage capacity. This will be described with reference to FIGS.

The block diagram of the workflow management system of this embodiment is the same as that of FIG. FIG. 31 shows a system configuration in this embodiment. In this system configuration, in the system configuration shown in FIG. 2, a workflow definition table 6601 for storing the definition of various attributes of the workflow definition is added as the workflow definition data 142. Further, in the present embodiment, the state transition request asynchronous processing program 202 includes variables for holding the current main storage capacity, the main storage capacity used for one state transition processing, and the maximum usable main storage capacity for each workflow definition. An initialization procedure 6611 for securing and initializing an area is added. Further, in the present embodiment, changes are made to the processing of the state transition request fetch procedure 1502, the state transition processing activation procedure 1503, the workflow definition screen display procedure 2601, and the workflow definition storage procedure 2602. FIG.
Only the differences from the first embodiment are described therein, and details of the entire system configuration are not described.

FIG. 32 shows the structure of the workflow definition table 6601 in this embodiment. In this embodiment, the workflow definition table 6201 is tabular data including a workflow definition name 6711, a main storage usage 6712, and a maximum main storage usage 6713. The workflow definition name 6711 is data for uniquely identifying the workflow definition. The main storage usage 6712 is data representing a main storage capacity required when processing a state transition request related to a work of the corresponding workflow definition. The maximum main storage use amount 6713 is data representing the maximum main storage capacity that can be used for processing a state transition request related to the work of the corresponding workflow definition.

In the present embodiment, the record of the workflow definition table 6601 is stored in the workflow definition storage procedure 2602 of the workflow definition program 209, and is referred to in the initialization procedure 6611 of the state transition request asynchronous processing program 202. Next, initialization procedure 6
The operation of 611 will be described. The initialization procedure 6611 is executed only once when the workflow management program 140 is started.

In the initialization procedure 6611, first, the workflow definition table 6601 is searched to obtain a list of workflow definitions. Next, for each workflow definition, a variable area (“sum of current usage”) holding the current main storage capacity used, and a constant area (“processing usage amount”) holding the main storage capacity used for one-state transition processing )), A constant area (“Usage limit”) that holds the maximum seed storage capacity that can be used for state transition processing is secured, and 0 and main memory usage are 6 respectively.
It is initialized to a value of 712 and a value of a maximum main memory usage of 6713.

Next, the operation of the state transition request fetch procedure 1502 in this embodiment will be described with reference to FIG. State transition request fetching procedure 15 in this embodiment
02 takes a work ID, a workflow definition name, and a transition ID as output arguments and returns a boolean value.

(Step 6811) The workflow definition table 6601 is searched to obtain a list of workflow definitions. (Step 6812) One unchecked workflow definition is selected from the list of workflow definitions acquired in Step 6811. (Step 6813)
A state transition request related to the work of the workflow definition selected in step 6812 is searched from the state transition request table 215 and one is selected. (Step 6814) If the search result in Step 6813 is not empty, Step 68
The process branches to step 6819 if it is empty.
(Step 6815) If the sum of “sum of current usage” and “usage for each process” regarding the workflow definition selected in step 6812 is not more than “usage upper limit”, step 6
If it is larger than the “Usage limit”, the process branches to step 6819. (Step 6816) Step 6
The “usage for each process” is added to the “sum of current usage” related to the workflow definition selected in 812. (Step 6
817) The corresponding attribute of the state transition request selected in step 6813 is substituted for the output argument work ID, workflow definition name, and transition ID, and the corresponding record of the state transition request table 215 is deleted. (Step 68
18) Return TRUE to the caller and end. (Step 6819) The workflow definition selected in Step 6812 is marked as checked. (Step 68
20) If there is an unchecked workflow definition, go to step 6812; otherwise, go to step 682.
Branch to 1. (Step 6821) FA is called
Returns LSE and ends.

Next, the operation of the state transition processing start procedure 1503 in this embodiment will be described. First, a state transition request fetch procedure 1502 is called. The answer is FALSE
If, end. In the case of TRUE, the value of the output argument is passed as it is to the state transition processing procedure 1600 and called. Subtract "amount" and finish.

Next, the operation of the workflow definition screen display procedure 2601 in this embodiment will be described. First, FIG. 34 is a diagram showing an image displayed on the screen of the display 123 in the workflow definition screen display procedure 2601 in this embodiment. The difference from the first embodiment is that Text box 691 for designating the main storage capacity required for each transition process
1 and a text box 6912 for designating the upper limit of the amount of main storage that can be used for the state transition processing.

FIG. 35 is a diagram showing a workflow definition structure 7011 for storing information relating to the workflow definition defined on the screen of FIG. 34 in the workflow definition screen display procedure 2601 according to the present embodiment. The main storage usage field 70 for storing the main storage usage entered in the text box 6911
12 and a maximum main memory usage field 70 for storing the main memory usage entered in the text box 6912
13 is added.

Next, the operation of the workflow definition storage procedure 2602 in this embodiment will be described. In this embodiment, the workflow definition storage procedure 2602 stores the attributes of the workflow definition structure 7011 in the workflow definition table 6601, the state definition table 210, and the transition definition table 211, respectively, and ends. In the same manner as in the present embodiment, it is also possible to realize a case where the unit for controlling the computer resource amount is set for each state, each transition, and each workflow application program.

Further, in the same manner as in the present embodiment, it is possible to realize the case where the computer resources to be controlled are the number of processing threads, the auxiliary storage capacity, and the like.

As described above, in the workflow management system according to the present embodiment, the amount of computer resources available for processing a state transition request is determined for each workflow, for each workflow definition, each state, each transition, and each workflow. It can be easily set using tools in small units, such as for each application program.

[0145]

According to the present invention, a flexible workflow management system can be provided.

[Brief description of the drawings]

FIG. 1 is a block diagram of a workflow management system according to a first embodiment.

FIG. 2 is a configuration diagram of a workflow management system according to the first embodiment.

FIG. 3 is a schematic diagram of the first embodiment.

FIG. 4 shows the structure of a state definition table according to the first embodiment.

FIG. 5 shows the structure of a transition definition table according to the first embodiment.

FIG. 6 shows a structure of an operator determination rule definition table according to the first embodiment.

FIG. 7 is a structure of an operator definition table according to the first embodiment;

FIG. 8 shows a structure of a work state table according to the first embodiment.

FIG. 9 shows the structure of a state transition request table according to the first embodiment.

FIG. 10 shows the structure of a counter operation table according to the first embodiment.

FIG. 11 illustrates an API of a workflow management program according to the first embodiment.

FIG. 12 is a flowchart showing a processing procedure of a processing method determination procedure according to the first embodiment;

FIG. 13 is a flowchart illustrating a processing procedure of a state transition processing procedure according to the first embodiment;

FIG. 14 is a workflow definition screen according to the first embodiment.

FIG. 15 shows a structure of a workflow definition structure according to the first embodiment.

FIG. 16 is a configuration diagram of a workflow management system according to a second embodiment.

FIG. 17 shows the structure of a transition definition table according to the second embodiment.

FIG. 18 shows the structure of a state transition request table according to the second embodiment.

FIG. 19 illustrates an API of a workflow management program according to the second embodiment.

FIG. 20 is a flowchart illustrating a processing procedure of a synchronization state transition request procedure according to the second embodiment;

FIG. 21 is a flowchart illustrating a processing procedure of an asynchronous state transition request procedure according to the second embodiment;

FIG. 22 is a flowchart illustrating a processing procedure of a state transition processing procedure according to the second embodiment;

FIG. 23 is a transition method selection screen according to the second embodiment.

FIG. 24 is a configuration diagram of a workflow management system according to the third embodiment.

FIG. 25 shows the structure of workflow application execution environment information according to the third embodiment.

FIG. 26 is a transition method selection screen according to the third embodiment.

FIG. 27 is a configuration diagram of a workflow management system according to a fourth embodiment.

FIG. 28 shows the structure of a workflow definition table according to the fourth embodiment.

FIG. 29 is a workflow definition screen according to the fourth embodiment.

FIG. 30 shows the structure of a workflow definition structure according to the fourth embodiment.

FIG. 31 is a configuration diagram of a workflow management system according to a fifth embodiment.

FIG. 32 shows the structure of a workflow definition table according to the fifth embodiment.

FIG. 33 is a flowchart showing a procedure of a state transition request fetching procedure according to the fifth embodiment;

FIG. 34 is a workflow definition screen according to the fifth embodiment.

FIG. 35 shows the structure of a workflow definition structure according to the fifth embodiment.

[Explanation of symbols]

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Yoshiki Matsuda 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa Prefecture, within the Business Solutions Division of Hitachi, Ltd.

Claims (25)

[Claims] 1. A workflow management method in which a plurality of states and transitions between states are defined in advance as a workflow definition, and a state transition request is input to perform a state transition process of a work. A synchronous processing step of performing a state transition process of a work before returning a response, an asynchronous processing step of performing a state transition process of a work after receiving a response to the input of the state transition request and returning a response, A workflow management method, comprising: a selection step of selecting and executing the synchronous processing step and the asynchronous processing step based on input selection information as a work state transition processing for an input. 2. The workflow management method according to claim 1, wherein the selecting step generates a program for calling one of the asynchronous processing step and the synchronous processing step corresponding to the input selection information. Workflow management method. 3. The workflow management method according to claim 1, wherein the selection information is synchronization information defined in advance. 4. The workflow management method according to claim 3, wherein the workflow definition includes the synchronization information. 5. The workflow management method according to claim 4, wherein environment information of an execution environment of the workflow application program includes the synchronization information. 6. The workflow management method according to claim 3, wherein the environment information of the execution environment of the workflow management program is:
A workflow management method comprising the synchronization information. 7. The workflow management method according to claim 4, wherein the synchronization information is provided for each transition definition between states. 8. The workflow management method according to claim 4, wherein the synchronization information is provided for each state. 9. The workflow management method according to claim 5, wherein said synchronization information is provided for each workflow definition. 10. A workflow management device which preliminarily defines a plurality of states that a work can take and transitions between the states as a workflow definition, and performs a state transition process of the work by inputting a state transition request. A synchronous processing means for performing a state transition process of the work between receiving an input of the input and returning a response; and an asynchronous processing means for performing a state transition process of the work after receiving the input of the state transition request and returning a response. A workflow management apparatus for selecting and executing the synchronous processing means and the asynchronous processing means for performing a work state transition process in response to the input of the state transition request based on the input selection information. 11. A computer-readable recording in which a plurality of states that can be taken by a work and transitions between the states are defined in advance as a workflow definition, and a workflow management program for performing a state transition process of the work by inputting a state transition request is stored. In the medium, the program is a synchronous processing step of performing a state transition process of a work between receiving the input of the state transition request and returning a response, and receiving a response after receiving the input of the state transition request and returning a response. An asynchronous processing step of performing a state transition process of a work; and a state transition process of the work in response to the input of the state transition request, based on the input selection information, selecting the synchronous processing step and the asynchronous processing step. A recording medium storing a workflow management program having an execution step to be executed. 12. A workflow management program for preliminarily defining a plurality of states that a work can take and transitions between the states as a workflow definition, and performing a state transition process of the work by inputting a state transition request. A synchronous processing step of performing a work state transition process between receiving a transition request input and returning a response, and an asynchronous process of performing a work state transition process after receiving the state transition request input and returning a response A workflow management program comprising: a step of executing a state transition process of a work in response to an input of the state transition request based on the input selection information by selecting the synchronous processing step and the asynchronous processing step . 13. A plurality of states that can be taken by a work and transitions between the states are defined in advance as a workflow definition, a state transition request is input, and a work for the input of the state transition request is input based on the input transition processing control information. A workflow management method, characterized by controlling execution of a state transition process. 14. The workflow management method according to claim 13, wherein the state transition processing control information includes priority information, and when there are a plurality of state transition requests to be processed, the state transition request to be processed is determined by the priority information. A workflow management method, wherein the selection is made based on the following. 15. The workflow management method according to claim 13, wherein the state transition processing control information includes usable computer resource amount information, and is used for a state transition request that has already been processed and a processing for the state transition request. A workflow management method comprising: comparing a sum of computer resource amounts with a value defined by the available computer resource amount information, and determining whether to execute a process for the state transition request or not. . 16. The workflow management method according to claim 14, wherein the computer resource amount is a main storage capacity used for processing for the state transition request. 17. The workflow management method according to claim 15, wherein the computer resource amount is an auxiliary storage capacity used for processing for the state transition request. 18. The workflow management method according to claim 15, wherein the computer resource amount is the number of threads used for processing for the state transition request. 19. The workflow management method according to claim 13, wherein the transition process control information is predefined transition process definition information. 20. The workflow management method according to claim 19, wherein said workflow definition includes said transition process definition information. 21. The workflow management method according to claim 19, wherein environment information of an execution environment of the workflow application program includes the transition processing definition information. 22. The workflow management method according to claim 19, wherein the environment information of the execution environment of the workflow management program is:
A workflow management method comprising the transition process definition information. 23. The workflow management method according to claim 20, wherein said transition process definition information is provided for each transition definition between states. 24. The workflow management method according to claim 20, wherein the transition processing definition information is provided for each state. 25. The workflow management method according to claim 20, wherein said transition process definition information is provided for each workflow definition.