JP3767666B2 - Workflow management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a workflow management system, a code generator used in the workflow management system, and a method for changing a process of workflow processing.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, a workflow management system is used for efficiently performing information processing consisting of a series of processes and a plurality of processes, that is, workflow processing, in a network system to which a plurality of terminal computers are connected. Data relating to the workflow processing is moved as a package between the computers in a predetermined order, and is processed by each computer. Each processor refers to and rewrites data by operating each of these computers. An example of such a workflow management system is disclosed in Document I (Nikkei Computer, 1997.9.1 pages 204-217).
[0003]
FIG. 9 is a diagram schematically showing the workflow management system disclosed in Document I divided into blocks for each function. In FIG. 9, the data is indicated by a rounded rectangle, and the functional means (application or the like) is indicated by a rectangular rectangle. As shown in FIG. 9, the workflow management system 201 includes a workflow engine A203, a process definition tool A205, a work list handler A207, and a monitoring tool A209. In a widely used client / server system, a workflow engine A203 that controls workflow processing operates on the workflow server 204, and each processor operates a client computer to execute a process (activity) in charge.
[0004]
The process definition tool A 205 is a functional module for defining the processing contents of each process and the order of activities. The process definition tool A205 generates process definition data D211 when a workflow process is newly started. The process definition data D211 includes data relating to processing contents in each activity and the order of the activities as integral data. Further, the process definition data D211 may include data relating to control conditions such as a workflow process end condition. A general process definition tool A205 has a graphical user interface (GUI) environment. Therefore, the processor can easily define the process (the order of the activities and the processing contents in each activity) by using the pointer by operating the mouse.
[0005]
The workflow engine A 203 is a functional module that controls workflow processing. More specifically, the workflow engine A 203 interprets the process definition data D211 and adds a work item indicating the processing content to the work list D213 based on the interpretation. The work list D213 is a data area for storing work items to be processed by each processor, and is provided for each processor.
[0006]
Each processor executes an activity using the client application A 215 or the like according to the work item indicated by the work list handler A 207. For activities that do not require human processing, the activation application A217 activated by the workflow engine A203 executes the activities. As shown in FIG. 9, the client application A215 or the startup application A217 may use application data D219.
[0007]
The work list handler A207 gives each processor an instruction regarding the processing contents by showing the work items to be processed with reference to the work list D213 to each processor. When the processor finishes the work, the work list handler A207 deletes the work item from the work list D213. The workflow engine A 203 recognizes the end of the activity by deleting the work item, and adds the work item to the work list D 213 of the next processor.
[0008]
The monitoring tool A209 is a functional module that confirms the progress of workflow processing by monitoring the workflow engine A203. With the monitoring tool A209, the supervisor or each processor can refer to the progress or end result of the workflow processing as necessary.
[0009]
The workflow control data D221 is used to identify the workflow engines that are responsible for each workflow process when performing a plurality of workflow processes in parallel. The workflow related data D223 includes various information related to the workflow processing. The workflow-related data D223 is, for example, price data of purchased items, and is used when the processor to be in charge changes depending on the price range.
[0010]
As shown in FIG. 9, the workflow engine A 203 controls the processing in each activity based on the process definition data D 211, whereby the workflow processing is performed. Generally speaking, workflow processing is classified into two types of business, repetitive regular business and ad hoc atypical business. The routine work includes a business trip cost slip, equipment purchase slip or budget application, and the non-standard work includes data circulation, technical document creation, or software development. In order to improve the efficiency of work, a workflow management system that can be applied to these various work is required.
[0011]
Typically speaking, in the workflow processing of a routine work, one process definition data is often used because the order of activities and the processing contents in each activity hardly change. On the other hand, in the workflow processing of an atypical business, since the order of activities and the processing contents in each activity are not constant, process definition data is often generated every time workflow processing is performed.
[0012]
[Problems to be solved by the invention]
However, in the conventional workflow management system, it is necessary to modify the entire process definition data in order to change the processing content or processing order of each activity in either a routine business or an atypical business. For example, when changing the approver in the equipment purchase slip, which is a routine work, the process definition data used so far must be corrected. In addition, when it is desired to change the circulation destination of the material in the circulation of materials generated in ad hoc, the process definition data must be corrected before starting the circulation of the material.
[0013]
In order to easily change the processing order of such activities, in the workflow management system 201 of FIG. 9, the workflow engine A 203 refers to the organization / role data D225. The organization / role data D225 is data in which a general destination name indicating a position in the organization such as a section manager or a department manager is associated with a specific destination name such as the name of a processor. In this case, only by defining the general destination name in the process definition data D211, the workflow engine A203 can determine the specific destination name from the general destination name by referring to the organization / role data D225. For this reason, even when a processor in a position along the approval route is changed to another processor due to personnel changes or the like, the destination is dynamically recognized, so there is no need to change the destination name of the approval route.
[0014]
Although the introduction of such organization / role data may make the change unnecessary, in the workflow processing in which the processing order is not defined by the job title, it is still necessary to correct the processing order of the activity from the process definition data.
[0015]
Therefore, in both workflow processing of routine work and non-routine work, when changing the processing contents in one activity or changing the processing order of activities, process definition data is modified or process definition data Create a new. As described above, in the conventional workflow processing, the process-related change involves redefinition of the process definition data, which is inefficient and cannot be easily performed (first problem).
[0016]
Normally, when a new workflow process is started, process definition data is newly created. At this time, if the types of work to which the workflow processing is applied are diverse, the process definition data necessarily has various contents. Since the workflow engine must be able to interpret and execute these process definition data, it needs to have many basic functions for executing various workflow processes in advance. Therefore, the configuration of the workflow engine becomes complicated, and the occupied memory of the workflow engine code that functions as the workflow engine inevitably increases (second problem).
[0017]
Therefore, a workflow management system that can solve at least the first problem and preferably can solve the second problem has been desired.
[0018]
[Means for Solving the Problems]
Therefore, the workflow management system of the invention according to this application is a network system having a plurality of computers, and performs workflow processing consisting of a series of a plurality of steps based on process definition information regarding the processing contents in each step and the order of those steps. In the workflow management system for each process,
Identification means for identifying object definition information related to processing contents in each process and flow definition information related to the order of processes from the process definition information described above,
A program storage unit storing a plurality of programs that provide basic functions used in the above-described workflow processing;
An object definition that interprets the object definition information described above, reads a program corresponding to the interpretation from the program storage unit, and generates an object definition code that is a code related to processing contents in each process based on the read program Code generation means;
A flow definition code generating unit that interprets the flow definition information described above and reads a program corresponding to the interpretation from the program storage unit, and generates a flow definition code that is a code related to the order of each read process;
A workflow engine that controls workflow processing by interpreting the flow definition code and the object definition code.
[0019]
According to this configuration of the workflow management system, when defining a process for workflow processing, the drafter defines the process for starting the workflow processing. The process definition information input by the drafter is separated into a part relating to the flow definition and a part relating to the object definition by the identifying means. After this separation, the former part is encoded by the flow definition code generation means and generated as a flow definition code, and the latter part is encoded by the object definition code generation means and generated as an object definition code. Therefore, when the workflow process is performed, it is not necessary to modify the process definition data itself even if the process (the processing contents and the order of the activities in each activity) is changed. In other words, if you want to change only the processing contents in each activity, you need to modify only the object definition code. If you want to change the order of activities (change of the person who performs the activity), modify only the flow definition code. That's fine.
[0020]
In implementing the present invention, more preferably, the object definition information and the flow definition information described above are interpreted, and a program corresponding to the interpretation is read from the program storage unit, so that the read program is stored. A workflow engine code generation means for generating a workflow engine code based on the workflow engine code may be further provided, and the workflow engine code may function by the workflow engine code.
[0021]
As a result, it is possible to generate a workflow engine code having only the minimum necessary configuration for realizing the functions defined in the flow definition information and the object definition information. Therefore, the memory occupied by the workflow engine code can be reduced. The workflow engine code means program code that, when executed by the CPU, causes the CPU to virtually exist and function in the CPU.
[0022]
In implementing the present invention, it is preferable to further include definition code storage means for storing the object definition code and the flow definition code in the state of a high-level language code. Thereby, when making a correction for the flow definition or the object definition, the person who makes the correction can add, delete or modify the code while understanding each definition code.
[0023]
In carrying out the present invention, preferably, the above-described workflow engine has a hierarchical structure in which functions are inherited from an upper hierarchy to a plurality of lower hierarchies, and the workflow engines of individual lower hierarchies access to each other. It should have a function. Thereby, the lower-level workflow engine can be distributed to the host computers in the network system. As described above, when a hierarchical structure is provided to the workflow engine and a communication function is provided in each lower-level workflow engine, the lower-level workflow engine can exist in a distributed manner in any host computer in the network system. Therefore, the efficiency and stability of the network system by load distribution can be realized.
[0024]
Further, in the workflow management system in which the lower-level workflow engines are distributed as described above, when a general destination name is defined in advance in the above flow definition code, a specific destination name is generated from the general destination name. It is desirable to further include address conversion means, and this address conversion means has a communication function for mutual access to the workflow engine.
[0025]
Conventionally, in order to perform address conversion, the address conversion means has to be provided in the same host computer as the host computer in which the workflow engine exists. However, since the address conversion means is provided with a communication function, the address conversion means can mutually access the lower-level workflow engine even when the lower-level workflow engines are distributed as described above. Therefore, the address conversion means can be provided in a host computer different from the lower-level workflow engine.
[0026]
In addition, the code generator of the invention according to this application is a network system having a plurality of computers, and when performing workflow processing consisting of a series of a plurality of steps, from the process definition information regarding the processing contents in each step and the order of those steps, A code generator that generates code that can be interpreted by the workflow engine,
Identification means for identifying object definition information related to processing contents in each process and flow definition information related to the order of processes from the process definition information described above,
Object definition code generation means for generating an object definition code that can be interpreted by the workflow engine from the object definition information described above,
And a flow definition code generating means for generating a flow definition code that can be interpreted by the workflow engine from the above flow definition information.
[0027]
According to this code generator configuration, the identification means separates the process definition information into object definition information and flow definition information, and then generates an object definition code from the object definition information and generates a flow definition code from the flow definition information. To do. Therefore, the object definition code is corrected when only the processing content in each process is to be changed, and the flow definition code is corrected when only the processing order of the process is to be changed. Therefore, the process can be changed efficiently and easily. The object definition code and the flow definition code are generated as, for example, a Java language or C ++ source program code as a high-level language, that is, an object definition source program code and a flow definition source program code. At this time, when these object definition code and flow definition code are compiled, they become executable program code that can be interpreted by the workflow engine.
[0028]
In addition, in the invention of the method for changing the process of the workflow processing according to this application, before performing the workflow processing consisting of a series of a plurality of steps, from the process definition information regarding the processing contents of each step and the processing order of the steps, Identifying object definition information related to processing contents and flow definition information related to process processing order, generating object definition code that can be interpreted by workflow engine from object definition information, and flow definition that can be interpreted by workflow engine from flow definition information For workflow processing that generates code, when changing the process of the workflow processing, only the object definition code is modified when only the processing content of each process is changed, and the flow is performed when only the processing order of the process is changed. Only the definition code is modified That.
[0029]
According to this process change method, either the object definition code or the flow definition code that exists independently of each other can be modified, regardless of whether you want to change only the processing contents in each step or only change the processing order of the steps. It can respond by doing. Therefore, the process can be changed efficiently and easily.
[0030]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of a workflow management system of the present invention will be described with reference to the drawings. In addition, each block diagram used for this description represents each component in a block to such an extent that these inventions can be understood, and has shown only the schematic functional relationship. In addition, in each figure, the same constituent components are denoted by the same reference numerals and redundant description thereof may be omitted. In each figure, a rectangular rectangle indicates a functional unit, and a rounded rectangle indicates data.
[0031]
(First embodiment)
In the workflow management system, it is necessary to define a workflow process and then execute the workflow process. Therefore, in the first embodiment, a form for defining the process of the workflow management system will be described, then a form for executing the workflow process of the workflow management system will be described, and then a method for changing the process of the workflow process will be described. explain.
[0032]
FIG. 1 is a block diagram schematically showing the interrelationships of main functional units in the workflow management system according to the first embodiment. However, each functional unit in FIG. 1 virtually exists in the central processing unit when the central processing unit as a hardware resource executes a program corresponding to the functional unit. In the following, squares of functional units virtually realized in the central processing unit are shown as squares, and data information formed in the data area of the storage device is shown as rounded rectangles. FIG. 2 is a diagram schematically showing the usage form of hardware resources by each functional unit, taking as an example the case where each functional unit in FIG. 1 is operated by one host computer.
[0033]
Hereinafter, with reference to FIG. 1 and FIG. 2, a form for defining the process of the workflow management system of the embodiment will be described. However, the workflow management system of the embodiment is provided with a workflow engine code generation means.
[0034]
As is well known, a workflow management system executes a workflow process by performing a workflow process including a series of a plurality of activities for each activity in a network system having a plurality of host computers.
[0035]
The workflow management system 11 according to the first embodiment shown in FIG. 1 includes an identification unit F13, an object definition code generation unit F15, a flow definition code generation unit F17, a workflow engine code generation unit F19, and a program storage unit 21. And have. Here, these functional units F13, F15, F17, and F19 are configured to operate as virtual functional means in the central processing unit (CPU) c1 of the host computer h1 in FIG.
[0036]
The host computer h1 shown in FIG. 2 includes a storage device m1, such as a hard disk or an optical disk, a CPU c1, and an input device i1 for man-machine interface. The CPU c1 does not show a control unit for performing necessary control including the timing and start or stop of the operation of the storage device m1, the input device i1, each of the functional units F13, F15, F17, and F19 described above. Contains. The storage device m1 of the host computer h1 has an identification program D13 for realizing the function of the identification means F13, an object definition code generation program D15 for realizing the function of the object definition code generation means F15, and a flow definition code generation means F17. A flow definition code generation program D17 that realizes the above function and a workflow engine code generation program D19 that realizes the function of the workflow engine code generation means F19 are stored.
[0037]
First, in defining the workflow process, the drafter 24 operates the input device i1 of the host computer h1 to store the process definition information D23 in the storage device m1. At this time, the drafter 24 inputs the process definition information D23 from the input device i1 of the host computer h1 by, for example, script input from the keyboard or GUI operation from the pointer device. As a result, the process definition information D23 is stored in the storage device m1 of the host computer h1. However, the process definition information D23 includes data relating to processing contents of each activity, that is, object definition information D23a, and data relating to the order of activities, that is, flow definition information D23b.
[0038]
When the process definition information D23 is input, the identification unit F13 reads the process definition information D23 stored in the storage device m1, and identifies the object definition information D23a and the flow definition information D23b from the process definition information D23. . Thereafter, the identified object definition information D23a and flow definition information D23b are stored in the storage device m1. Note that the identification unit F13 operates on the CPU c1 as a virtual functional unit by the CPU c1 reading and executing the identification program D13 stored in the storage device m1.
[0039]
The program storage unit 21 stores a plurality of basic function providing programs D22 that provide basic functions used for workflow processing. The program storage unit 21 is formed in a data area in the storage device m1 of the host computer h1, for example.
[0040]
For example, the basic function providing program D22 includes a plurality of programs in which basic functions used for workflow processing are classified for each function. In this way, when the basic functions are divided for each function, only necessary functions can be read without reading unnecessary functions. Therefore, the occupied memory of the object definition code D25a, the flow definition code D25b, and the workflow engine code D27 generated from the basic function providing program D22 can be reduced.
[0041]
The object definition code generation unit F15 interprets the object definition information D23a and reads the basic function providing program D22 according to the interpretation from the program storage unit 21, thereby defining the object definition based on the read basic function providing program D22. A code D25a is generated. At this time, specifically, the object definition code generation means F15 functions as follows in the host computer h1.
[0042]
That is, the CPU c1 of the host computer h1 reads and executes the object definition code generation program D15 stored in the storage device m1. As a result, the object definition code generation means F15 is activated. The object definition code generation means F15 reads the object definition information D23a from the storage device m1, and determines whether or not the basic function providing program D22 is necessary for generating the object definition code D25a based on the object definition information D23a. The provided program D22 is read. Thereafter, the object definition code generation means F15 generates the object definition code D25a by combining, for example, the read basic function providing program D22 and the object definition information D23a. For example, at this time, the object definition code generation means F15 may read the plurality of basic function providing programs D22 and generate the object definition code D25a. The generated object definition code D25a is stored in the storage device m1 as a source program including a basic source program that defines at least common processing contents in each activity.
[0043]
The flow definition code generation unit F17 interprets the flow definition information D23b and reads the basic function providing program D22 corresponding to the interpretation from the program storage unit 21, thereby defining the flow definition based on the read basic function providing program D22. A code D25b is generated. At this time, specifically, the flow definition code generation means F17 functions as follows in the host computer h1.
[0044]
That is, the CPU c1 of the host computer h1 reads and executes the flow definition code generation program D17 stored in the storage device m1. As a result, the flow definition code generation means F17 is activated. The flow definition code generation unit F17 reads the flow definition information D23b from the storage device m1, and determines whether the basic function providing program D22 necessary for generating the flow definition code D25b is based on the flow definition information D23b. The provided program D22 is read. Thereafter, the flow definition code generation unit F17 generates the flow definition code D25b by combining, for example, the read basic function providing program D22 and the flow definition information D23b. For example, at this time, the flow definition code generation unit F17 may read the plurality of basic function providing programs D22 and generate the flow definition code D25b. The generated flow definition code D25b is stored in the storage device m1 as a source program including at least a source program that defines the order of activities.
[0045]
The workflow engine code generation means F19 interprets the identified object definition information D23a and flow definition information D23b and reads the basic function providing program D22 according to the interpretation from the program storage unit 21, thereby reading the read basic function. A workflow engine code D27 is generated based on the provided program D22. At this time, specifically, the workflow engine code generation means F19 functions as follows in the host computer h1.
[0046]
That is, when the CPU c1 of the host computer h1 reads and executes the workflow engine code generation program D19 stored in the storage device m1, the workflow engine code generation means F19 is activated. The activated workflow engine code generation means F19 reads the object definition information D23a and the flow definition information D23b from the storage device m1, and also provides a basic function providing program necessary for generating the workflow engine code D27 based on the definition information D23a and D23b. It is determined whether it is D22 or not, and the basic function providing program D22 is read out. Thereafter, the workflow engine code generation means F19 generates the workflow engine code D27 from the read basic function providing program D22. For example, at this time, the workflow engine code generation means F19 generates a workflow engine code D27 by combining a plurality of basic function providing programs D22. The generated workflow engine code D27 interprets the object definition code D15 and the flow definition code D17 (however, includes the meaning of “reference” in Java programming) and controls workflow processing based on this interpretation. Is stored in the storage device m1 as a source program.
[0047]
When actually executing the workflow processing, for example, the CPU c1 of the host computer h1 reads out and executes the workflow engine code D27 stored in the storage device m1, thereby starting the workflow engine as one functional unit. Then, the control operation of the workflow process is performed.
[0048]
The identification unit F13, the object definition code generation unit F15, and the flow definition code generation unit F17 can be recognized as one functional unit called a code generator F28. The code generator F28 is a process that can be interpreted by the workflow engine from the process definition information regarding the processing contents in each activity and the order of the activities when performing workflow processing including a series of activities in a network system having a plurality of host computers. Generate code for. In particular, the code generator F28 distinguishes and generates an object definition code D25a and a flow definition code D25b from the process definition information D23. Therefore, if the workflow engine is configured to be able to interpret the object definition code D25a and the flow definition code D25b for a general workflow management system, only the code generator F28 portion can be applied.
[0049]
Here, the case where a specific workflow process is executed will be described as an example in more detail for each functional unit described above.
[0050]
Here, the workflow management system is constructed using object-oriented programming (OOP). As is well known, Java language, C ++ language, etc. are suitable for OOP. When OOP is used, the above-described workflow engine is defined as a workflow engine having a hierarchical structure including a higher hierarchy (superclass) having only basic functions to a lower hierarchy (subclass) having specific and individual functions. it can. At this time, the object definition code and the flow definition code are objects referenced by the workflow engine.
[0051]
FIG. 3 is a diagram schematically showing a specific functional configuration of the workflow management system of FIG. 1, and a workflow when a workflow engine having a class structure, that is, a hierarchical structure is used instead of the workflow engine shown in FIG. It is a block diagram which shows roughly the mutual relationship of the main functional units about a management system. Each functional unit in FIG. 3 is a functional unit that virtually exists in the CPU when the CPU as the hardware resource executes a program corresponding to the functional unit. However, for the sake of convenience, in FIG. 3, the workflow engine subclasses F27a and F27b are shown as virtual functional units that operate on the CPUs of the host computers h2 and h3, respectively.
[0052]
FIG. 4 is a diagram illustrating an example of a network system that operates each functional unit of the workflow management system of FIG. FIG. 4 shows a network system in which three host computers h1, h2, and h3 are connected. As shown in FIG. 4, each of the host computers h1, h2, and h3 includes CPUs c1, c2, and c3, storage devices m1, m2, and m3 such as hard disks and optical disks, and man-machine interface input devices i1, i2, and i3. With. Although not shown, each host computer h1, h2, and h3 generally has a display device or the like. As already described, the CPUs c1, c2, and c3 have a control unit for driving each functional unit. Further, driver software for driving each hardware resource, general OS software, and the like may be operating on the CPUs c1, c2, and c3. FIG. 4 merely shows an example of a computer in which each component of the workflow management system can exist.
[0053]
Here, as a specific example of the workflow process, a workflow process including two activities is performed. That is, as shown in FIGS. 3 and 4, in this workflow processing, the drafter 24 first operates the host computer h1 to define the workflow processing process, and then the processor 31a operates the host computer h2. The processor 31b then operates the host computer h3 to execute the activity.
[0054]
The workflow engine shown in FIGS. 3 and 4 has a plurality of hierarchical structures from an upper hierarchy to a lower hierarchy. That is, the code for causing the workflow engine to function has a two-level hierarchical structure of a higher-level workflow engine code (workflow engine superclass code) D27s and a lower-level workflow engine code (workflow engine subclass code) D27a and D27b. ing.
[0055]
However, here, the workflow engine code generation means F19 generates the workflow engine subclass codes D27a and D27b which are source program codes. The workflow engine subclass code D27a causes the workflow engine subclass F27a to function, and the workflow engine subclass code D27b allows the workflow engine subclass F27b to function.
[0056]
When a workflow engine having a hierarchical structure is used as described above, it is preferable to generate only a workflow engine code in a lower hierarchy.
[0057]
As is well known, the workflow engine subclasses F27a and F27b can perform functional inheritance (inheritance) from the workflow engine superclass (shown as codes instead of functional units in the drawing) D27s. Therefore, if the basic function is defined in the workflow engine superclass code D27s, the basic function can be inherited in the workflow engine subclasses F27a and F27b. Therefore, in the workflow engine subclass codes D27a and D27b, only functions different from the basic functions need be defined.
[0058]
As described above, the workflow engine code generation means F19 is based on the OOP, and is the lower-level workflow engine code D27a and D27b that functionally inherits from the higher-level workflow engine code D27s that defines the basic function, and It is preferable to generate lower-level workflow engine codes D27a and D27b in which specific specific functions are defined. Thereby, the description of the entire source program code that functions as the workflow engine can be simplified, so that the workflow engine code can be easily generated. At the same time, the occupied memory in the storage device for the workflow engine code can be reduced. As shown in FIG. 3, the class library D52 including the workflow engine super class code D27s is provided in the program storage unit 21, for example.
[0059]
If the workflow engine code having a hierarchical structure extending from the superclass to the subclass can be accessed by setting the communication function to the workflow engine subclass codes D27a and D27b, the workflow engine subclasses D27a and D27b are respectively connected to the network. It can be distributed to any host computer in the system. Therefore, the efficiency and stability of the network system can be improved by load balancing.
[0060]
Here, as shown in FIG. 4, the workflow engine subclass codes D27a and D27b generated by the host computer h1 are distributed to the host computers h2 and h3, respectively. As described above, the workflow engine subclass code D27a shown in FIG. 4 operates on the host computer h2 and functions as the workflow engine subclass F27a shown in FIG. 3, and the workflow engine subclass code D27b shown in FIG. 4 operates on the host computer h3. As a workflow engine subclass F27b. As shown in FIGS. 3 and 4, the processor 31a performs an activity by operating the host computer h2. Thereafter, the processor 31b performs another activity by operating the host computer h3. Thus, when generating the workflow engine code, it is preferable to define different workflow engine subclasses for each processor host computer. As a result, the processor can be easily identified, so that it is easy to define the workflow process.
[0061]
Here, in order to generate a lower-level workflow engine code for each processor as described above, the following process definition information is generated. That is, in FIG. 3, for example, the process definition script D43 is used as the process definition information described above. At this time, the drafter 24 operates the input device i1 of the host computer h1, for example, and inputs the process definition script D43. The process definition script D43 includes an object definition script D43a and a flow definition script D43b.
[0062]
At this time, if OS software or editor software is operated on the CPU c1 of the host computer h1, a process definition script D43 as data is stored in the storage device m1. The process definition script D43 is data in which information related to the process definition of the workflow process is described with a simple internal code. However, the internal code here is a code that can be recognized by the script identifying means F45.
[0063]
FIG. 5 is an example of a process definition script for specific workflow processing. The process definition script shown in FIG. 5 includes an object definition script D43a and a flow definition script D43b.
[0064]
Further, in order to identify these scripts D43a and D43b from each other, different identifiers are added to the scripts D43a and D43b. In the example illustrated in FIG. 5, the identifiers “engines” and “flow” indicate the flow definition script D43b, and the identifier “do” indicates the object definition script D43a.
[0065]
The identifier “engines” specifies the workflow engine subclass name. Here, since different workflow engine subclass codes are generated for the processors 31a and 31b, the processors 31a and 31b that execute the activities are defined by the workflow engine subclass names. For example, as shown in FIG. 5, a workflow engine subclass F27a (loanTeller) is defined for the processor 31a, and a workflow engine subclass F27b (loanDecision) is defined for the processor 31b.
[0066]
The identifier flow defines the processing order of activities by sequentially specifying workflow engine subclass names. That is, in FIG. 3, activities are executed in the order of workflow engine subclasses F27a (loanTeller) and F27b (loanDecision).
[0067]
The identifier do defines the processing content in each activity. That is, as shown in FIG. 5, a process content “method start” is defined in the workflow engine subclass F27a (loanTeller), and a process content “method decideLoan” is defined in the workflow engine subclass F27b (loanDecision).
[0068]
As shown in FIG. 3, such a process definition script D43 is read into the script identification means F45 operating on the CPU c1 of the host computer h1. At this time, the script identification unit F45 separates the process definition script D43 into the object definition script D43a and the flow definition script D43b based on the identifier included in the process definition script D43. Thereafter, the script identification unit F45 stores the object definition script D43a and the flow definition script D43b separated into the host computer h1 in the storage device m1. The script identification means F45 is a virtual functional unit that functions when the CPU c1 reads and executes a script identification program (not shown) stored in the storage device m1 of the host computer h1 shown in FIG. It is.
[0069]
Specifically, the program storage unit 21 has a basic function providing program D22 as follows. That is, the program storage unit 21 is, for example,
(1) A basic function providing program D22 that realizes a function for starting a new workflow process;
(2) A basic function providing program D22 for realizing a function of confirming the progress status of the workflow process being executed,
(3) A basic function providing program D22 that realizes a function of canceling workflow processing;
(4) A basic function providing program D22 that realizes a function of confirming the end of all activities in the workflow processing;
(5) A basic function providing program D22 that realizes a function of discarding information on the canceled or terminated workflow processing;
(6) A basic function providing program D22 for realizing a function of adding a work item to a work list provided for each processor;
(7) A basic function providing program D22 that realizes a function of recognizing the end of an activity by deleting a work item in the work list;
Have
[0070]
As shown in FIG. 4, since the workflow engine classes having a hierarchical structure are distributed in the host computers h1, h2, and h3, the program storage unit 21 has (8) workflow engine subclasses. It is preferable to have a basic function providing program D22 that realizes a communication function for communicating with other workflow engines. In addition, the program storage unit 21 may include a basic function providing program D22 that automatically processes an activity by an activation application for an activity that does not require (9) human processing. As shown in FIG. 4, the program storage unit 21 is provided as a data area of the storage device m1 of the host computer h1, for example.
[0071]
In order to perform OOP in the Java language, it is desirable that the program storage unit 21 has a class library 52 that defines classes that can be used for workflow processing such as a super class of the workflow engine. In FIG. 3, the class library D52 includes a workflow engine superclass code D27s (DWorkflowEngine) and other superclass code D27t (LoanApp2).
[0072]
The workflow engine code generation means F19 receives the basic function providing program D22 (1) to (9) as described above from the program storage unit 21 of the storage device m1, the object definition script D43a and the flow definition script stored in the storage device m1. After reading D43b, the basic function providing program D22 of (1) to (9) that has been read is combined and the workflow engine subclass code D27a (LoanTeller) functions as the workflow engine subclass F27a (LoanTeller) and F27b (LoanDecision) And D27b (LoanDecision) are generated.
[0073]
At this time, the workflow engine code generation means F19 interprets the object definition script D43a and the flow definition script D43b related to the workflow processing, thereby providing workflow engine subclass codes D27a (LoanTeller) and D27b having only basic functions necessary for the workflow processing. (LoanDecision) is generated. That is, the workflow engine code generation unit F19 reads only basic functions necessary for workflow processing defined by the object definition script D43a and the flow definition script D43b, and does not read unnecessary functions. For example, a combination of some of the basic functions (1) to (9) read from the program definition unit F45 and the object definition script D43a read from the program storage unit 21, is combined with the workflow engine subclass code D27a (LoanTeller). And D27b (LoanDecision) are generated. Therefore, the workflow engine subclass codes D27a (loanTeller) and D27b (LoanDecision) have only the minimum necessary configuration, and therefore the occupied memory becomes small. More specifically, for example, a conventional workflow engine must be able to process an activity with an arbitrary number of steps, but the workflow engine of the embodiment only needs to be able to process two activities, so there are extra classes and methods. The code omits the definition.
[0074]
The object definition code generation means F15 reads the basic function providing program D22 as described above and the object definition script D43a accumulated in the storage device m1 from the program storage unit 21 of the storage device m1, and then reads the read basic information. The function providing program D22 and the object definition script D43a are combined to generate the object definition code D47a.
[0075]
The flow definition code generation unit F17 reads the basic function providing program D22 as described above and the flow definition script D43b accumulated in the storage device m1 from the program storage unit 21 of the storage device m1, and then reads the read basic information. The function providing program D22 and the flow definition script D43b are combined to generate the flow definition code D47b.
[0076]
6 and 7 are diagrams showing part of the object definition code D47a and the flow definition code D47b generated as the source program code in the Java language by the object definition code generation means F15 and the flow definition code generation means F17.
[0077]
The code on the first and second lines of the source program code shown in FIG. 6 defines a subclass code D27a (loanDecision) for the superclass code D27s (DWorkflowEngine) of the workflow engine. The code on the third to seventh lines declares exception processing for the workflow engine subclass code D27b (loanDecision). The code on the 8th to 11th lines defines a method decideloan indicating the processing content in the workflow engine subclass code D27b (loanDecision). The code on the 12th to 24th lines defines a method that is executed first when the workflow engine subclass code D27b (loanDecision) is started.
[0078]
The subclass LoanFlow2 of the other super class code D27t (LoanApp2) necessary for the workflow processing is defined by the codes in the first and second lines of the source program code shown in FIG. The codes on the 3rd to 7th lines initialize and define names of other superclass code D27t (LoanFlow2). The code on the 8th to 26th lines registers workflow engine subclass codes D27a (loanTeller) and D27b (loanDecision) used for loanFlow2. The code on the 27th to 31st lines creates a table with the names of workflow engine subclass codes D27a (loanTeller) and D27b (loanDecision). The codes on the 32nd to 34th lines create a table of workflow processing names. The code on the 35th to 37th lines creates a time limit table for workflow processing. The code on the 38th to 40th lines creates a table for determining the end of the workflow process.
[0079]
Further, when actually performing workflow processing, the workflow engine subclasses F27a (loanTeller) and F27b (LoanDecision) shown in FIG. 3 are driven to refer to the classes and methods of the object definition code D47a and the flow definition code D47b. , Control the workflow process.
[0080]
Further, when actually performing the workflow process, the object definition code D47a and the flow definition code D47b must describe a definition related to the process. These definition codes D47a and D47b may be generated in one step or may be generated in a plurality of steps. For example, the code generator F28 may generate only the basic definition code and complete the definition code by adding a specific definition code to the basic definition code. In other words, when the object definition code D47a and the flow definition code D47b are generated in a plurality of steps, first, a code that defines processing contents common to each activity is generated as an object definition basic code, and an object definition extension code is generated. An object definition code may be generated by adding a code that defines processing content unique to each activity to the object definition basic code. Specifically, the object definition code D47a in FIG. 6 is completed as an object definition code when a method specific to each activity is added as an object definition extension code to the blocks in the 8th to 9th lines. Thus, after the object definition code generation means F15 generates the object definition basic code, it is preferable to add the object definition extension code to the object definition basic code. This simplifies the individual object definition code.
[0081]
For convenience of explanation, identification means, workflow engine code generation means, object definition code generation means, and flow definition code generation means, which are virtual functional units, exist in the CPU of a specific same host computer. Each functional unit can exist in the CPU of any host computer. Further, the program storage unit 21, the object definition code D47a, and the flow definition code D47b may exist in the storage device of any host computer.
[0082]
By defining the workflow process by the process definition script in the above procedure, the workflow engine subclass codes D27a (LoanTeller) and D27b (LoanDecision), the object definition code D47a, and the flow definition code D47b can be generated. . However, at the start of workflow processing, the workflow engine subclass codes D27a (LoanTeller) and D27b (LoanDecision) generated by the host computer h1 are distributed to the host computer h2 and the host computer h3, respectively.
[0083]
Similarly to the conventional workflow management system, the work host D53a and D53b and the work list handlers F55a and F55b are provided on the same host computer as the workflow engine subclasses F27a (loanTeller) and F27b (LoanDecision) shown in FIG. It has been. The work lists D53a and D53b are provided for each processor 31a and 31b.
[0084]
Each host computer h2 and h3 performs the following processing. That is, first, each processor 31a refers to the work item shown in the work list D53a by the workflow engine subclass F27a (loanTeller). Thereby, the processor 31a recognizes the activity to be processed. Then, the processor 31a executes the activity using the client application D57 or the like. When the work included in the activity ends, the work list handler F55a deletes the work item from the work list D53a. Thereby, the workflow engine subclass F27a (loanTeller) detects the end of the activity. Thereafter, the workflow engine F27a (loanTeller) sends the data processed in the activity to the next workflow engine F27b (loanDecision).
[0085]
Each processor 31b refers to the work item shown in the work list D53b by the workflow engine subclass F27b (loanDecision). The processor 31b recognizes the activity to be processed. Then, the processor 31b executes the activity using the client application D57 or the like. When the activity ends, the processor 31b operates the work list handler F55b to delete the work item from the work list D53b. Thereby, the workflow engine subclass F27b (loanDecision) detects the end of the activity. At the same time, the workflow engine F27b (loanDecision) detects the end of all activities of the workflow process, and notifies the end of the workflow process and the result to the processor 31a, for example.
[0086]
Next, a method for changing the process of workflow processing will be described using the above-described workflow management system as an application example.
[0087]
The process of the workflow management system according to the embodiment is changed by rewriting the object definition code D25a (D47a) or the flow definition code D25b (D47b). Therefore, it is not necessary to rewrite the process definition data itself as in the conventional workflow management system. That is, according to the workflow management system of the embodiment, only the object definition code D25a is corrected when only the processing content of each activity is changed, and only the flow definition code D25b is changed when only the activity order is changed. You just have to fix it.
[0088]
More specifically, for example, in the workflow processing according to the flow definition code of FIG. 7, if the processor is to be changed, the workflow engine subclass (loanDecision) described in the flow definition code is renamed to another workflow engine subclass. Just do it. Further, for example, in the workflow processing according to the object definition code of FIG. 6, when the processing content of the workflow engine subclass (loanDecision) is to be changed, the method decideLoan indicating the processing content of the object definition code may be modified. In this way, since one modification of the object definition code or the flow definition code does not affect the other modification, the process can be easily changed.
[0089]
In order to correct the object definition code or the flow definition code, the workflow management system described above stores definition code storage means (not shown) that stores the object definition code and the flow definition code in a high-level language code state. ).
[0090]
The object definition code and the flow definition code shown in FIGS. 6 and 7 are generated before starting the workflow process. These definition codes are source programs in this embodiment. These definition codes are compiled into an operable object program. For example, when a Java language source program is compiled, the source program is converted into a byte code that operates independently of the platform, and becomes an executable program. Since it is difficult to rewrite the compiled bytecode data itself, a state before compilation, that is, a source program code in Java language, for example, is stored. Thus, when changing the processing contents or processing order in each activity, a new object definition code or flow definition code can be created by correcting a part of the Java language source program code. If a new definition code is compiled and converted into byte code and then replaced with the byte code data before correction, the process definition can be corrected.
[0091]
(Second Embodiment)
In the following second embodiment, an embodiment in which address conversion means is provided in the workflow management system of the first embodiment will be described. However, here, a mode in which a workflow engine having a hierarchical structure is provided will be described. In the workflow management system described in the first embodiment, the activity processing order is statically defined in the flow definition code. In other words, a specific destination is shown in the code indicating the processor of the activity, and when there is a change in destination due to personnel changes or the like, that is, a change in the order of activities, it is necessary to rewrite the flow definition code.
[0092]
By the way, it is known that when the address conversion means disclosed in Document I or the like is used, the processing order can be dynamically defined, so that the process definition data need not be corrected. However, in the workflow management system disclosed in Document I, the workflow engine operates on a server, and the address conversion unit operates on the same server as the workflow engine. This increases the burden on the server including the address conversion means. Further, when the server is actually down, there is a problem that the workflow processing is interrupted.
[0093]
FIG. 8 is a block diagram schematically and schematically showing each functional unit of the workflow management system that operates the workflow management system according to the second embodiment. However, FIG. 8 does not show the same functional units as those in FIG. 4, and only the differences from FIG. 4, that is, workflow engine subclasses F27a and F27b and address conversion means F67 are shown.
[0094]
As shown in FIG. 8, the workflow management system according to the second embodiment includes address conversion means F63. Here, when the CPU c4 of the host computer h4 reads and executes the address conversion program D63 of the storage device m4, the address conversion means F63 operates on the CPU c4 as a virtual function means.
[0095]
The workflow engine shown in FIG. 8 is programmed by OOP and has a class structure that inherits functions from a superclass to a plurality of subclasses F27a and F27b. Since the individual workflow engine subclasses F27a and F27b exist in a distributed manner for each processor, they have communication functions F67a and F67b for accessing each other.
[0096]
The address conversion means F63 of the second embodiment is particularly characterized in that it includes a communication function F67t. Therefore, the address conversion unit F63 and the plurality of workflow engine subclasses F27a and F27b can access each other by communication.
[0097]
As is well known, the address conversion means F63 is a functional module that converts a general destination name indicating a position in the organization such as a section manager or a department manager into a specific destination name such as a processor name. The address conversion means F63 refers to the organization / role data D65 as in the conventional configuration. For example, when performing workflow processing for approval of equipment purchase, since the approval route is often determined by job title, a destination name is designated by job title in advance. Therefore, even if a processor in a position along the approval route is changed to another processor due to personnel changes or the like, the destination is dynamically determined, so there is no need to change the approval route, that is, the destination name.
[0098]
Here, a flow of determining a specific destination name from a general destination name by the address conversion means 63 will be described with reference to FIG.
[0099]
When the processor of the activity defined in the flow definition code is described with a general destination name, the workflow engine subclass F27a first checks the name of the workflow engine subclass that started the workflow processing, that is, the processor. Next, the workflow engine subclass F27a transmits the general destination name and the initiator name to the address conversion unit F63 by performing network communication with the address conversion unit F63 via the communication functions F67a and F67t.
[0100]
At this time, the address conversion means 63 recognizes the role (belonging department or job title) in the organization of the initiator from the name of the initiator of the workflow process being executed, and the next from the role of the initiator and the general destination name. Find the name of the processor responsible for the activity. Then, the workflow engine subclass name is obtained from the next processor name, and the workflow engine subclass name that should process the next activity is transmitted to the workflow engine subclass F27a. Thereafter, the workflow engine subclass F27b that should process the next activity is activated.
[0101]
As described above, in the second embodiment, the workflow engine is distributed to different host computers h3 and h4 as a plurality of workflow engine subclasses F27a and F27b having a hierarchical structure as shown in FIG. The conversion unit F63 has a communication function. That is, the workflow engine subclass F27a operates on the host computer h2, the workflow engine subclass F27b operates on the host computer h3, and the address conversion means F63 operates on the host computer h4. As described above, even if the address conversion unit F63 and the workflow engine subclasses F27a and F27b exist in different host computers, the address conversion unit F63 has the communication function F67t. Therefore, the address conversion unit F63 includes the workflow engine subclasses F27a and F27b. Can communicate with each other. Therefore, the address conversion means F63 can be moved to an arbitrary host computer. That is, it is not necessary to provide the address conversion means F63 on the same host as the workflow engine as in the prior art.
[0102]
Therefore, the burden on the host computer including the address conversion means can be reduced and the possibility of system down can be reduced. Even when the host computer including the address conversion means goes down, the workflow process can be continued by moving the address conversion means to another host computer.
[0103]
【The invention's effect】
  As is apparent from the above description, according to the workflow management system of the present invention, when defining the process of the workflow processing, the process definition information input by the drafter includes the part related to the flow definition and the object definition by the identification means. Are separated by the flow definition code generation means and the object definition code generation means. Therefore, when the workflow process is performed, it is not necessary to modify the process definition data itself even when the processing content and the order of activities in each activity are changed. In other words, if you want to change only the processing contents in each activity, you need to modify only the object definition code. If you want to change the order of activities (change of the person who performs the activity), modify only the flow definition code. That's fine. Therefore, the process can be changed efficiently and easily.
  Furthermore, according to the workflow management system of the present invention, the program storage unit stores a plurality of programs that provide basic functions used for workflow processing, classified for each function. Therefore, only necessary functions can be read without reading unnecessary functions. Therefore, the memory occupied by the object definition code, flow definition code, and workflow engine code generated from the basic function providing program can be reduced.
Furthermore, according to the workflow management system of the present invention, for example, when generating the object definition code and the flow definition code in a plurality of steps, the drafter first inputs the processing content common to each activity, Next, what is necessary is just to input the processing content peculiar to each activity. As a result, the workflow management system generates a code that defines processing content common to each activity as an object definition basic code, and generates a code that defines processing content unique to each activity as an object definition extension code. Then, the workflow management system adds the generated object definition extension code to the object definition basic code. Thereby, the workflow management system can generate the object definition code. Therefore, according to the workflow management system of the present invention, when the object definition code and the flow definition code are generated in a plurality of steps, the drafter has a process content common to each activity and a process content unique to each activity. The object definition code can be generated simply by entering.
[0104]
Further, according to the code generator of the present invention, after the identification means separates the process definition information into the object definition information and the flow definition information, the object definition code is generated from the object definition information, and the flow definition code is generated from the flow definition information. Is generated. Therefore, the object definition code is corrected when only the processing content in each process is to be changed, and the flow definition code is corrected when only the processing order of the process is to be changed. Therefore, the process can be changed efficiently and easily.
[0105]
Further, according to the invention of the method for changing a process of workflow processing, only the processing content of each process is changed to change the process of workflow processing for generating an object definition code and a flow definition code from process definition information. In this case, only the object definition code is modified. When only the process processing order is changed, only the flow definition code is modified. Therefore, according to this process changing method, either of the object definition code or the flow definition code that exists independently of each other, regardless of whether it is desired to change only the processing contents in each step or only the processing order of the steps. This can be dealt with by correcting Therefore, the process can be changed efficiently and easily.
[Brief description of the drawings]
FIG. 1 is a block diagram schematically showing a mutual relationship between functional units of a workflow management system according to a first embodiment.
FIG. 2 is a diagram schematically showing a usage form of hardware resources by each functional unit, taking as an example a case where each functional unit in FIG. 1 is operated by one host computer;
FIG. 3 is a diagram schematically showing a specific functional configuration of the workflow management system of FIG. 1;
4 is a diagram illustrating an example of a network system that operates each functional unit of the workflow management system of FIG. 3;
FIG. 5 is an example of a process definition script for specific workflow processing.
FIG. 6 is a diagram showing a part of object definition code generated as source program code.
FIG. 7 is a diagram showing a part of a flow definition code generated as source program code.
FIG. 8 is a block diagram schematically and schematically showing each functional unit of a network system that operates the workflow management system according to the second embodiment.
FIG. 9 is a block diagram showing a configuration of a conventional workflow management system.
[Explanation of symbols]
11, 41: Workflow management system
F13: Identification means
D13: Identification program
F15: Object definition code generation means
D15: Object definition code generation program
F17: Flow definition code generation means
D17: Flow definition code generation program
F19: Workflow engine code generation means
D19: Workflow engine code generation program
21: Program storage unit
D22: Basic function providing program
D23: Process definition information
D23a: Object definition information
D23b: Flow definition information
24: The drafter
D25a, D47a: Object definition code
D25b, D47b: Flow definition code
D27: Workflow engine code
F27a, F27b: Workflow engine subclass
D27a, D27b: Workflow engine subclass code
D27s: Workflow engine super class code
D27t: Other super class code
F28: Code generator
31a, 31b: processor
D43: Process definition script
D43a: Object definition script
D43b: Flow definition script
F45: Script identification means
D52: Class library
D53a, D53b: Work list
F55a, F55b: Worklist handler
D57: Client application
F63: Address conversion means
D63: Address conversion program
D65: Organization / role data
F67a, F67b, F67t: Communication function

Claims (4)

In a workflow management system that performs workflow processing consisting of a series of processes in a network system having a plurality of computers for each process based on process definition information in each process and the order of those processes,
Identification means for identifying object definition information related to processing contents in each step and flow definition information related to the order of steps from the process definition information;
A program storage unit that stores a plurality of programs that provide basic functions used in the workflow processing, divided for each function ;
By interpreting the identified object definition information and reading out the program corresponding to the interpretation from the program storage unit, an object definition code which is a code related to processing contents in each step based on the read program An object definition code generation means for generating;
A flow definition that interprets the flow definition information and reads the program according to the interpretation from the program storage unit to generate a flow definition code that is a code related to the order of each process based on the read program Code generation means;
Definition code storage means for storing the object definition code generated by the object definition code generation means and the flow definition code generated by the flow definition code generation means in a high-level language code;
Reading the object definition code and the flow definition code stored in the high-level language code from the definition code storage means and interpreting them, and reading the program according to the interpretation from the program storage unit, Workflow engine code generation means for generating a workflow engine code based on the issued program;
A workflow management system comprising: a workflow engine that controls the workflow processing based on the workflow engine code generated by the workflow engine code generation means . The workflow management system according to claim 1,
  The workflow engine code generation means includes
  Converting the generated workflow engine code into byte code, storing the converted byte code as a source program in the definition code storage means,
  When the object definition code or the flow definition code stored in the high-level language code is modified in the definition code storage unit, the modified definition code is read from the definition code storage unit and the modification is performed. A new object definition code or flow definition code is created based on the defined definition code, the created new object definition code or flow definition code is converted into a byte code, and the converted byte code is converted into the definition code. Replace with the source code bytecode stored in the storage before modification
A workflow management system characterized by this. In the workflow management system according to claim 1 or 2 ,
A workflow management system, wherein the workflow engine has a hierarchical structure in which functions are inherited from an upper hierarchy to a plurality of lower hierarchies, and each of the workflow engines in the lower hierarchy has a communication function for accessing each other. The workflow management system according to claim 3 ,
In the case where a general destination name is defined in advance in the flow definition code, further comprising address conversion means for generating a specific destination name from the general destination name, and
The workflow management system, wherein the address conversion means has a communication function for mutual access to the workflow engine in the lower hierarchy.

Images