JPH08153068A - Workflow system - Google Patents

Abstract

PURPOSE: To execute the charge processing for inquiring a folder from another user in the flow to which one's work point belongs without needing the burden on a user by executing update processing of a workflow server and a database management system indivisibly. CONSTITUTION: A workflow desktop 11 starts a database application 14 corresponding to a processing. In accordance with the instruction of the workflow desktop 11, the workflow server 12 executes data management including the storage and input/output processing of workflow data 13 by setting workflow data 13 to be access object. The database application 14 updates a database 17 as one processing in the workflow. A transaction manager 15 is provided with a processing function invisibly executing the data update processing of the workflow server 12 and that of the database management system 16.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow system characterized by a data update processing mechanism of a workflow system which realizes a flow of office processing on a computer. or,
The present invention relates to a workflow system that realizes a flow control mechanism that allows a user to inquire a user outside a flow for a job processed by a user of a work point.

[0002]

2. Description of the Related Art A conventional workflow system is shown in FIG. 8 and its processing procedure is shown in FIG. Conventionally,
As shown in FIG. 8, the workflow system includes a workflow server (WF se that manages workflow data).
rver) 82 and a database management system (DBMS) 84 that manages data for office processing, and a workflow desktop (WF Deskt) for using each
op) 81 and database application (DB App)
(lication) 83 four modules work together.

Workflow Desktop (WF Deskt
op) 81 retrieves the work data from the workflow server (WF server) 82, determines the contents of the work by referring to the work flow defined separately.
Launch the application. Some of these applications update the database (DB) 85, and this application is called a database application here.

In the above conventional workflow system of this type, the workflow desktop (WF Des
ktop) 81 and workflow server (WF server) 8
2. Database application (DB Appplicati
on) 83 and database management system (DBMS) 84
There was no mechanism to execute the two data updates described above as one.

Therefore, as shown in FIG. 9, when a system down such as power-off (see the cross mark (SystemDown) in FIG. 9) occurs, the workflow server (WF
The rollback point of the server is different from the rollback point of the database management system (DBMS), which may cause inconsistency between the contents of the workflow server and the database.

That is, in the case of FIG. 9, when re-executed, the update of the workflow server (WF server) has not been completed (the planned commit point (C) has not been reached).
Therefore, the workflow desktop (WF Desktop) is regarded as having no update, and the process is performed again.

At this time, a database management system (DB
Since the MS has already completed the processing once, the second processing will be performed due to the re-processing of the workflow desktop (WF Desktop).

[0008] To give a simple example, when "100 yen" is deposited in the database in the workflow processing in the above system, the reprocessing described above results in "200 yen" deposit, which is incorrect. It becomes a thing.

As described above, in the conventional system configuration, the workflow desktop (WFDesktop) and the workflow server (WF server), the database application (DB Application) and the database management system (DBMS) are used to update one data item. Therefore, when a system failure such as power-off occurs, the rollback point of the workflow server and the rollback point of the database management system are different, which may lead to incorrect processing. It was

Further, the workflow system defines a case (folder) containing information (documents) to be transferred between work sites (work points) in advance and places it in a work flow. , You can proceed with business reasonably.

At this time, a user registered in the database can be set as the work point, and a flow (workflow) is obtained by connecting the work points. The folder is sent to the work point according to the flow, but at that time, there is a case where it is desired to make an inquiry about the folder to be sent to a user outside the flow.

Regarding this inquiry processing, conventionally, when a folder arrives at a work point and there is an inquiry for the folder, a duplicate of the folder is made and the folder is sent to the user who wants to make an inquiry. , An operation to change the flow is required.
Also, when the user inquiring about the folder performs some processing and sends the folder to the inquiring user, an operation for changing the flow is required.

As described above, conventionally, whenever a folder is to be sent to a work point that is not in the flow,
There is a problem that a troublesome operation for changing the flow is required, and thus the operation load on the user is heavy and the usability is poor.

[0014]

As described above, in the conventional system configuration, there is no mechanism for executing two data updates of the workflow desktop and the workflow server, the database application and the database management system as one. Therefore, when a system failure such as power-off occurs, incorrect processing may be executed due to the time difference between the rollback point of the workflow server and the rollback point of the database management system. There was a problem in keeping the credibility of.

Further, conventionally, when it is desired to send a folder to a work point that is not included in a flow, a troublesome flow changing operation is required each time, so that the operation load on the user is large and the usability is poor. there were.

The present invention has been made in view of the above circumstances,
By synchronizing and inseparably updating the workflow data and the database management system update process, erroneous processing caused by the time difference between the workflow server rollback point and the database management system rollback point can be avoided. It is an object of the present invention to provide a workflow system that can eliminate execution and maintain system reliability.

Further, according to the present invention, when an inquiry about a folder is made to a user outside the flow to which the own work point belongs, the change processing of the flow can be executed without the operation load of the user. The purpose is to provide a workflow system with good operability.

[0018]

The present invention uses a general-purpose transaction manager and incorporates a transaction processing mechanism between a workflow desktop and a database application to simultaneously perform two update processes of a workflow server and a database management system. Provide a workflow system that realizes the function to be executed.

Specifically, a workflow processing mechanism including a workflow desktop and a workflow server,
In a workflow system constructed with a database application and a database mechanism consisting of a database management system, as shown in FIG. 2, a mechanism for enabling a transaction manager on the workflow desktop side and performing interprocess communication with the application is provided. On the built-in side, on the application side, a mechanism for enabling the transaction manager and for performing interprocess communication with the workflow desktop is built in. Further, a mechanism for executing transaction processing under the transaction manager is built in the workflow server. It is characterized in that such a mechanism is incorporated, a transaction manager is interposed between the workflow desktop and the database management mechanism, and the update processing of the workflow server and the database management mechanism is inseparably executed.

Further, according to the present invention, in a workflow system for transferring a folder between a workflow server and a client according to flow information connecting a work point, the flow information is changed to a workflow server managing the flow information. And the process of sending the folder to the work point according to the changed flow information,
And a means for changing the flow information to the original state again, and a work point is temporarily added so that the folder can be delivered to a client not defined by the flow information.

[0021]

[Function] For each processing in the field of paperwork, work is carried out by entering requirements, contents (amount and quantity), etc. in a form, and passing the form to each person in charge, and updating the master ledger. . The present invention relates to a workflow system that realizes such an office process on a computer system, and relates to the update of the flow data corresponding to the above-mentioned form and the database corresponding to the master ledger, and a processing function for executing each update process inseparably. It is characterized by

That is, in the above-described workflow system according to the present invention, the workflow desktop (Workflow Desktop) is transmitted from the database application (DBAplication) to the transaction ID (Tran.
s.ID) (see FIG. 3 [9]), the transaction manager (Transaction Manager) is instructed to commit two transactions simultaneously (see FIG. 3 [10]). According to this instruction, the transaction manager causes the workflow server (WF server) and the database management system (DB
A commit instruction is issued to each MS (Fig. 3 [1
1] [12]). When the transaction manager receives "success" from both the workflow server and the database management mechanism (see [13] [14] in FIG. 3),
Notify that to the workflow desktop (Fig. 3
[15]). When the workflow desktop receives "success" via the transaction manager, the process ends.

As described above, the transaction manager intervenes to perform the update processing of the workflow server and the database management mechanism inseparably, whereby the rollback point of the workflow server and the rollback point of the database management system deviate in time. Execution of erroneous processing caused by can be eliminated, and a highly reliable workflow system can be constructed.

Further, according to the present invention, a means for searching the users registered in the database and a folder to the work point of the other party are sent, and when the processing of the other party is completed, the work point is automatically set to the own work point. And a folder inquiry function having means for returning a folder. As a result, when it is desired to make an inquiry about the folder to be sent to a user outside the flow, this inquiry processing can be performed by a simple operation without imposing an operation burden on the user.

[0025]

Embodiments of the present invention will be described below with reference to the drawings. First, a first embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a block diagram showing the configuration of a workflow system according to the first embodiment of the present invention.

In FIG. 1, reference numeral 11 denotes a workflow desktop for the operator to select a job on the workflow and instruct the processing, and activates a database application 14 according to the processing.

Reference numeral 12 denotes a workflow server (Workflow Server) that stores workflow data and executes delivery processing.
r) and the Workflow Desktop (Workflow Desk
top) Workflow data (WFD) according to 11 instructions
Is updated.

13 is a workflow server (Workflow Se
rver) 12 is workflow data (WFD) to be accessed by the non-volatile memory that is to be accessed by the rver) 12. In this case, data update processing is performed inseparably from the database (DB).

14 is a database application (D
B Application), which is a software module that updates a database (DB) as one process in the workflow.

Reference numeral 15 is a transaction manager which provides a function for executing processing on a plurality of different servers in an inseparable manner. Here, processing on a workflow server (WF server) 12 and a database management system (DBMS) 16 is inseparable. To run.

Reference numeral 16 is a database management system (DBM
S) and the database application (DB A
Under the processing control of the pplication 14 database (D
B) is accessed and updated.

Reference numeral 17 is a database management system (DBM
S) is a database (DB) placed on a non-volatile memory which is an access target of 16 and is composed of data and its management data. Here, data update processing is performed inseparably from the workflow data (WFD) 13.

FIG. 2 shows a coupling mechanism between the modules of the embodiment shown in FIG. 1, wherein the modules are coupled by network communication. In FIG. 2, 11A is a workflow desktop (Workflow Des
ktop) 11 is the main body. 11B is the same body portion 11
A and the transaction manager (Transaction Mana
ger) 15 and database application (DB)
A workflow transaction processing module (WF-Tx) for performing arbitration with the application.

12A is a workflow server (WF serv)
er) 12 is a main body portion, and 12B is the same main body portion 12A.
And Transaction Manager
) 15 and implements the transaction protocol of the workflow, the workflow transaction processing module (WF-Tx).

Reference numeral 14A denotes a main body of the database application (DB Application) 14, and 14B
Is the workflow transaction processing module (WF
-Tx) ID information (id- of Transaction Manager) 15 by communication with 11B.
A, id-B, ..., See Trans.ID in FIG. 3) and a database application communication module (DBA Com) for sending and receiving processing instruction commands and the like.

FIG. 3 is a diagram showing the flow of processing between the modules in the first embodiment, and is a flow chart showing the state in which data update is inseparably executed. Here, the workflow desktop (Work
flow Desktop) 11 to WF Desktop, Transaction Manager (Transaction Manager) 15 to Trans.Mgr
Is shown as.

4 to 7 are respectively the workflow transaction processing module (WF-T) shown in FIG.
x) is a flowchart showing the processing operation of 11B, FIG. 4 is a flowchart showing the processing procedure of [1] to [3] of FIG. 3, and FIG. 5 is a flowchart showing the processing procedure of [4] to [7]. 6 and 7 are the same as [10] to [1.
5] is a flowchart showing a processing procedure of [5].

The operation of the first embodiment of the present invention will be described with reference to FIGS. In FIG.
Workflow Desktop 11
Is a software module that executes a process associated with an input / output operation for an operator to select a work on a workflow and instruct the process, and activates a database application (DB Application) 14 according to the process.

Workflow server (WF server) 12
Is a Workflow Desktop 1
In accordance with the instruction of No. 1, the workflow data (WFD) 13 is accessed, and data management including storage and input / output processing of the workflow data is performed.

Database application (DB A
pplication) 14 updates the database (DB) 17 as one process in the workflow. Transaction Manager 15
It has a processing function for inseparably executing the data update processing of the workflow server (WF server) 12 and the data update processing of the database management system (DBMS) 16.

Database management system (DBMS) 1
6 manages a database (DB) 17. Based on the function of each module described above, the operation of the first embodiment will be described with reference to the flowcharts shown in FIGS.

[Workflow Desktop]
By the operator's operation on the ktop) 11, the workflow desktop (Workflow Desktop) 11 retrieves the workflow data from the workflow server (WF server) 12 via the transaction manager (Transaction Manager) 15, and the workflow server (W
The transaction is started for the F server) 12 ([1], [2] in FIG. 3, step A1 in FIG. 4).

Transaction manager (Transactio
n Manager 15 is a workflow desktop (Work
transaction ID (Tr
ans.ID) to notify the start of the transaction (Fig. 3 [3]).

[Workflow Desktop]
ktop) 11 is a transaction manager (Transact
Ion Manager 15) Transaction ID (Trans.
When the ID; id-A) is received, the received transaction ID (Trans.ID; id-A) is recorded in the data area of the workflow transaction processing module (WF-Tx) 11B (steps A2 and A3 in FIG. 4).

[Workflow Desktop]
ktop) 11 is a transaction ID (Trans.ID; id-
After receiving A), the database application (D
B Application 14 is started (FIG. 3 [4], FIG. 5).
Step B1). At this time, the data related to the processing that is flowing through the workflow is passed (for example, "the number of delivery").

Database application (DB A
pplication) 14 is a transaction manager (Tr
anssaction Manager) 15 to initiate a transaction, where a database management system (DBM)
S) 16 reads data from the database (DB) 17 and transfers the data (for example, “stock quantity”) to the database application (DB Application) 14 (FIGS. 3 [5], [6], and [7]).

Database application (DB A
pplication) 14 processes the received data (for example, "stock quantity"-"delivery quantity"), and writes the result (for example, new "stock quantity") in database (DB) 17 (Fig. 3 [8]). .

At this point, the commit (Commit)
Since the operation is not performed, even if the system goes down, it can be returned at the start of the transaction and the reprocessing can be correctly executed.

Database application (DB A
After updating the database (DB) 17, the pplication 14 returns the transaction ID (Trans.ID; id-B) to the workflow desktop 11 ([9] in FIG. 3).

[Workflow Desktop]
ktop) 11 is a database application (DB A
When the database update processing is completed, the transaction ID (Trans.ID; id-B) is recorded in the data area of the workflow transaction processing module (WF-Tx) 11B (Fig. 5 steps B2, B3).

After that, the workflow desktop (Work
The flow desktop) 11 sends two transaction IDs (Trans.ID; id-A, id-B) to the transaction manager (Transaction Manager) 15 and instructs the transaction manager 15 to commit the two transactions at the same time (see FIG. 10], step C1 in FIG. 6).

Transaction manager (Transactio
n Manager) 15 has two transaction IDs (id
-A, id-B), when it receives a commit instruction, it communicates with the workflow server (WF server) 12 and the database management system (DBMS) 16 and issues a commit instruction to both of them to execute the transaction atomically. Is guaranteed ([11] and [12] in FIG. 3).

Then, the transaction manager (Tr
ansaction Manager) 15 is a workflow server (W
F server) 12 and database management system (DB)
After confirming that both MS and 16 have returned "success", the fact is returned to the workflow desktop (Workfl
ow Desktop) 11 (Fig. 3 [13], [1]
4], [15]).

Workflow Desktop
ktop) 11 is a transaction manager (Transactio
Upon receiving the notification of the transaction "success" from the n Manager 15), the transaction processing is terminated, and in some cases, the database application (DB App)
(lication) 14 gives an end instruction (step C2 in FIG. 6,
C3).

In addition, the workflow desktop (Workflow
Desktop 11 is a transaction manager (Tran
saction Manager) 15 to transaction "failure"
Notification of the transaction manager (Tran
saction Manager) 15 the transaction (Tran
s.ID = id-A, id-B) is instructed to abort the transaction processing from the beginning (from FIG. 3 [1]).
Start over (step D1 in Fig. 7).

In this way, the workflow system has a transaction manager 15
Is provided, and the update processing of the workflow server (WF server) 12 and the database management system (DBMS) 16 is inseparably executed, so that the rollback point of the workflow server (WF server) 12 and the database management system (DBMS) 16 High reliability can be realized by eliminating erroneous execution of processing that occurs due to the time lag of the rollback point, and it can be applied with high reliability to a workflow system called core business.

Next, a second embodiment of the present invention will be described with reference to FIGS. The second embodiment relates to a flexible flow control so that the user can easily inquire of a user outside the flow about a job processed by the user of the work point of the workflow system.

FIG. 10 is a block diagram showing the configuration of the second embodiment of the present invention. In FIG. 10, reference numeral 21 is a workflow server, and various management information regarding the workflow is stored in a database (DB).

Reference numeral 22 is flow information stored in a database (DB), which stores information about the route through which the folder flows, the state of the folder, the position of the folder, and the like.

Reference numeral 23 is user information also stored in the database DB, which is table information in which the user of the workflow system is registered. Reference numeral 24 is a work point included in the flow information, which indicates a point at which a folder is processed.

Reference numerals 25A, 25B and 25C are clients, each of which has a desktop screen and is connected to the workflow server 21 via the network 30.

26 is a client 25A, 25B, 25
This is a folder that C has as a target for sending, and each contains a document. Reference numeral 27 is a receiving tray for loading and unloading the folder 26.

FIG. 11 is a flow chart showing the flow of a folder inquiry in the second embodiment. The workflow server 21 and the clients 25A, 25B, 2 are shown in FIG.
It is realized under the communication control between each processor with 5C.

In FIG. 11, S1 is a step for searching for a user, searching the user registered in the database (DB) and selecting the destination user of the folder 26.

S2 is a step for changing the flow, and the work point and route of the selected user are added to the existing flow. S3 is a step of sending the folder 26, and sends the folder to the work point of the selected user.

S4 is a step of returning the folder 26, and the folder 26 is sent to the work point of the user who sent it. S5 is a step of changing the flow, and the added work point and route (step S2
Delete).

FIG. 12 is a diagram showing a transition state example of the flow information in the second embodiment. Here, the work point (WP) number 5 is added as the work point information, and the route from the work point (WP) number 5 to the work point (WP) number 3 and the work point (WP) number are added as the route information. 3 shows an example in which a route from 3 to a work point (WP) number 5 is added.

Now, the operation of the second embodiment of the present invention will be described with reference to FIGS. The client 25A belongs to the work point 24 (a) included in the flow information 22 of the database (DB) provided in the work flow server 21, and the folder 26 has arrived at this work point.

The client 25A searches for the user registered in the user information 23 of the database (DB) provided in the workflow server 21 to obtain the user who wants to make an inquiry (step S1 in FIG. 11).

In this example, a user who is not defined in the flow is searched. Next, the user who makes the inquiry is selected. The user of this inquiry destination is the client 25C in this example.

The flow is changed so that the folder 26 existing in the work point of the client 25A can be sent to the work point of the client 25C (FIG. 11).
Step S2).

In this example, the route indicated by the broken line arrow and the work point 24 (c) of the client 25C are added from the work point 24 (a) of the flow information shown in FIG.

The client 25A is the client 25C
The folder 26 is sent to the work point (step S3 in FIG. 11). Client 25C is client 25
The folder 26 received from A is subjected to some processing.

The client 25C then proceeds to the folder 26
The processed folder 26 is sent to and returned to the client 25A by using the remand function of (FIG. 11 step S).
Four ).

The client 25A is the client 25
When the folder 26 is returned from C, the client 25
The flow is changed to delete the flow connecting the work point of A and the work point of the client 25C (step S5 in FIG. 11).

As described above, since the work point is temporarily added and the folder can be transferred to the client which is not defined by the flow information, the user outside the flow to which the work point belongs can be sent to the user. When making an inquiry about a folder, the flow changing process can be executed without the user's operation burden.

[0077]

As described above in detail, according to the workflow system of the present invention, the workflow data update and the database management system update process are synchronously and inseparably executed. It is possible to construct a highly reliable system by eliminating erroneous processing that occurs due to a time lag between the rollback point and the rollback point of the database management system.

Further, according to the present invention, by adopting a structure having a function of inquiring about a folder to users outside the flow to which the own work point belongs, folder processing including users outside the flow can be performed. In that case, the working time can be greatly reduced and the management can be facilitated because the mail system outside the system is not used.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a workflow system according to a first embodiment of the present invention.

FIG. 2 is a block diagram showing a coupling mechanism between each module of the embodiment shown in FIG.

FIG. 3 is a flowchart showing the flow of processing between modules in the first embodiment.

FIG. 4 is a flow transaction processing module (WF-Tx) processing shown in FIG.
-A flowchart showing the processing procedure of [3].

5 is a flowchart showing the process of the workflow transaction processing module (WF-Tx) shown in FIG.
7 is a flowchart showing a processing procedure of [7].

6 is a flowchart illustrating a process of the workflow transaction processing module (WF-Tx) shown in FIG.
The flowchart which shows the processing procedure of 0]-[15].

7 is a flow chart showing a process of the workflow transaction processing module (WF-Tx) shown in FIG.
The flowchart which shows the processing procedure of 0]-[15].

FIG. 8 is a block diagram showing the configuration of a conventional workflow system.

9 is a flowchart showing the flow of processing between modules of the system shown in FIG.

FIG. 10 is a block diagram showing the configuration of a second embodiment of the present invention.

FIG. 11 is a flowchart showing the processing procedure of the second embodiment.

FIG. 12 is a diagram showing a transition of flow information in the second embodiment.

[Explanation of symbols]

11 ... Workflow Deskto
p), 11B ... Workflow transaction processing module (WF-Tx), 12 ... Workflow server (W
orkflow Server), 12B ... Workflow transaction processing module (WF-Tx), 13 ... Workflow data (WFD), 14 ... Base application (DB Application), 14B ... Database application communication module (DBA Com), 15 ... Transaction manager (Transaction) Manager), 16 ...
Database management system (DBMS), 17 ... Database (DB), 21 ... Workflow server, 22 ... Flow information, 23 ... User information, 24 ... Work point,
25A, 25B, 25C ... Client, 26 ... Folder, 27 ... Reception tray, DB ... Database.

Claims (6)

[Claims] 1. A workflow system constructed by a workflow processing mechanism comprising a workflow desktop and a workflow server, and a database mechanism comprising a database application and a database management system, wherein a workflow processing mechanism and a database mechanism are provided between the workflow processing mechanism and the database mechanism. A workflow system characterized by having a transaction manager and executing update processing of a workflow server and a database management mechanism inseparably. 2. A workflow desktop for performing workflow processing procedures, a workflow server for managing workflow data, and a database application for updating a database in the workflow processing.
And a database management mechanism for managing the database,
A workflow system comprising: a transaction manager that inseparably executes update processing between the workflow server and the database management mechanism. 3. The workflow system according to claim 1, wherein the workflow desktop is provided with a workflow transaction module for arbitrating between a database application and a transaction manager. 4. The workflow system according to claim 1, 2 or 3, wherein the database application is provided with a communication module for performing interface processing of a transaction manager. 5. The workflow system according to claim 1, wherein the workflow server is provided with a workflow transaction module that realizes a transaction protocol of a workflow. 6. A workflow system that transfers a folder between a workflow server and a client according to flow information connecting a work point, and means for changing the flow information to a workflow server that manages the flow information, After the process of sending the folder to the work point according to the changed flow information, it has means to change the flow information to the original state again, and the work point is added temporarily to the folder not defined in the flow information for the client. A workflow system characterized by being able to deliver and receive.