JPH10326314A - Workflow management system for outsourcing - Google Patents

Abstract

PROBLEM TO BE SOLVED: To ensure the security of the processing contents and a processing flow by using an identifier to identify the documents for every document data base. SOLUTION: A client 100, a document management server 101 and a workflow management server 102 are connected to a network 103. The documents, i.e., the user data and the flow control information, i.e., the system data are separately stored in the data bases of different computers. Then, the user data and the system data are separately stored in its own in-house data base and a data base of the outsourcing destination respectively. Then, a workflow engine refers to the system data and controls only the access right of the user data. Meanwhile, the system data are described by means of only an identifier that is insignificant by itself to ensure the security of a processing flow. The information on correspondence between the identifier and a display name is managed as the user data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a workflow management system that controls a document flow in accordance with a process definition that defines a processing flow. In particular, it relates to technologies related to effective security, billing, and services required for outsourcing of workflow management.

[0002]

2. Description of the Related Art Regarding a workflow management system, Nikkei Computer, No. 2, May 2, 1994. P of 336
p. 57-67. The workflow management system can be classified into a mail type and a database type according to the base. Patents relating to the mail type include "electronic mail circulation processing system" disclosed in JP-A-4-178046 and "electronic circulation system using a computer network" disclosed in JP-A-5-158828. on the other hand,
Patents relating to database types include Japanese Patent Application Laid-Open No. 57-116.
No. 48, “Document circulation system” and JP-A-6-231
No. 059, “Document Circulation Route Definition Method” and the like.

[0003] However, in both types of workflow management systems, conventionally, it has been assumed that the system user and the administrator belong to the same organization.

[0004]

Generally, in order to operate a database type workflow management system, complicated operations such as database maintenance are required. for that reason,
If a small business has no system department, it is not economical to operate a workflow management system on its own.

[0005] Outsourcing of workflow management is
This is one correct solution to the above problem. However,
The following issues must be solved for outsourcing workflow management.

[0006] ● Confidentiality of processing contents and processing flow ● Calculation method of usage fee of workflow management service ● Various services provided by vendors and its realization method It is an object of the present invention to solve the above problems.

[0007]

In order to solve the above-mentioned problem of confidentiality of the contents of a document to be circulated, the present invention provides a method in which a document as user data and a flow control information as system data are stored in a database on different computers. Separate and store in. Then, the user data and the system data are separately stored in the database in the own company and the database at the outsourcing destination, respectively. The workflow engine controls only the access right of the user data with reference to the system data. Further, in order to maintain the confidentiality of the processing flow, the system data is described using only an identifier that has no meaning. Then, the correspondence information between the identifier and the display name is managed as user data.

Next, in order to calculate the usage fee of the workflow management service, a value to be counted up every time flow control is performed is held in system data. Then, the service usage fee is calculated based on the value.

Finally, as a service provided by the above-mentioned vendor, a service for periodically notifying a process definition manager of workflow statistical information by e-mail is realized.

[0010]

BEST MODE FOR CARRYING OUT THE INVENTION

(Embodiment 1) FIG. 1 is a simplified system configuration diagram used for explaining one embodiment of the present invention. for that reason,
FIG. 1 shows a client (100), a server (101) for document management, and a server (102) for workflow management.
Are connected to the network (103) one by one. However, in practice, at least a plurality of clients (100) and a server (101) for document management are connected to the network (103). The client (100) includes a WF client (110) that provides a user interface for a user to perform a workflow process.

The document management server (101) includes a document database (150) and a document server (120) for providing an access interface therefor. In the document database (150), there are documents (151) that are electronically circulated among the processing personnel.

The workflow management server (102) has a WF database (160), a WF server (130) for providing an access interface to the WF database (160), and a document server (102) based on information in the WF database (160). 120), there is a WF engine (140) for controlling the access right of the document (151), and a notification agent (170) for notifying the workflow management administrator of the statistical information of the workflow.

The WF database (160) includes a process definition (161) that describes the contents, order, persons in charge, and rules for determining the processing of the document (151), a document (15).
Flow control information (162) for managing the circulation status and processing status of 1), and flow statistical information (163) for storing statistical data that can be acquired during the circulation control of the document (151).
Exists.

FIG. 2 shows a document (151) used in this embodiment.
FIG. 5 is a diagram conceptually showing an example of the above.

The document (151) includes a document content (220).
In addition, a document property (210) exists as a combination of a property name (211) and a value (212). In this embodiment, the document ID (230), the editable user name (24
0), process definition name (250), processing node name (26
0), WF server name (270), reference flag (280)
Property exists.

The document ID (230) is an identifier for identifying the document (151) in units of the document database (150).

The editable user name (240) is stored in the document (1
51) holds the name of the user who can edit. The document server (120) permits only the user specified by the editable user name (240) to refer to and edit the document (151).

The process definition name (250), WF server name (270), and processing node name (260)
The circulation position of 1) is stored. That is, they are a process definition (161) used to control the circulation of the document (151), and a WF management server (10) storing the process definition (161).
2) and identify the location in the process definition (161).

The reference flag (280) indicates that the document server (1)
20) is a flag managed by the editable user name (2
Editable user name (240) after 40) is updated
Indicates ON / OFF whether the user designated by the user has referred to the document (151).

In another embodiment, the document properties (21
0) includes an editable user name list and a referenceable user name list, and the users described in the editable user name list have access rights to reference and edit the document (151), and are described in the referenceable user name list. In some cases, a user who has access is given a read-only access right.

FIG. 3 is a diagram conceptually showing an example of the process definition (161) used in this embodiment, using a data flow model.

In the process definition (161), in addition to the name for identifying the process definition and the mail address of the administrator, the contents of the processing, the execution order, the person in charge, and rules for determining them are described.

The process definition in FIG. 3 includes a process definition name (301) of “travel expense settlement” and “satoh@xyz.ab”.
c. co. jp ”e-mail address of the administrator (302)
And processes called “creation” (310), “examination” (320), “approval” (330), and “accounting” (340) are performed in this order. For processes other than “creation” (310), , "Suzuki" (321), "Tanaka" (331),
It is described that "Yamada" (341) is in charge of each process.

Regarding the process of "creation" (310), the person in charge is described as "-" (311), indicating that anyone can process it.

FIG. 4 shows an example of the flow control information (162) used in this embodiment. It contains the following information:

A document ID for identifying the document (151)
(420).

The document server name (410) for storing the circulation position of the document (151), the process definition name (43)
0), processing node name (440).

A person in charge (450) for storing the person in charge of processing the document (151).

A processing state (460) and a flow request (470) for storing the processing state of the workflow.

A processing start date and time (480) for storing the date and time when the processing of the document was started.

In the present embodiment, the processing state (460) is described by a processing code and a transition code. In the flow control information (162) shown in FIG. 4, act and sup are process codes, and wait and move are status codes. The processing state (460) is changed by the WF server (130) called from the WF client (110) or the WF engine (140). For example, when the user suspends the flow of the document (151), the processing code is changed from act to sup. When the user finishes editing the document (151) and instructs the next person to flow, the transition code is wa
It is changed from it to move. WF engine (14
If (0) flows the document (151) to the next person in charge of processing, the transition code is changed from move to wait.

The type of the flow request (470) depends on the type of the flow control function provided in the workflow management system. In FIG. 4, “Create” requesting to flow a newly created document (151), “Move” requesting to flow an existing document (151) next,
A NULL indicating that there is no immediate flow request is shown.

The processing start date and time (480) is set when the new entry of the flow control information (162) is created.
The date and time at that time are set by the server (480).

FIG. 5 is a diagram conceptually showing an example of the flow statistical information (163) used in this embodiment.

The flow statistics information (163) includes the following information.

A document server name (510) for storing a document to be circulated according to the process definition (161).

A process definition name (520) for identifying the process definition (161).

A counter (530) for storing the number of times the WF server (130) has circulated the document (151) based on the user's flow request (470). Counter (5
The value of 30) is counted up by the WF server (130) called from the WF engine (140). For example, if the user requests that the circulated document (151) be returned to the previous processor, the WF server (130) is called from the WF engine (110) to change the value of the counter (530). Increase by one. When the user requests that the processed document (151) be circulated to the next user, when the WF engine (140) electronically flows the document (151) to the next processing person, The server (130) is called from the WF engine (140) and increases the value of the counter (530) by one.

● The number of documents that have been circulated and processed according to the respective process definitions (161) (540).

In accordance with the respective process definitions (161), all documents (15
Regarding 1), the total processing time (55) representing the time taken from the start of processing to the end of all processing
0).

FIG. 6 is a flowchart of a process performed by the WF client (110) until the user selects an existing document (151) or creates a new document and edits the document.

When a new document (151) is created (6)
01), the WF client (110) creates a new document (1
51) to allow the user to edit (60)
2).

When editing an existing document (601), WF
First, the client (110) first sends the document server (12)
0), the name of the user currently being processed is included in the editable user name (240), and the reference flag (28)
A list of documents (151) for which (0) is OFF is obtained (603). Next, the document (1) acquired in the process (603)
The list of 51) is displayed on the display of the client (100), and the user can select a document (151) to be processed from the list (604). When the user selects the document (151) to be processed, the WF client (110) transmits the document (151) via the document server (120).
Document content (220) of the document (151) specified by the user
Is acquired (605). After that, the document content (220) acquired in the process (605) is displayed on the display of the client (100), and the user inputs the document content (22).
0) can be edited (606).

FIG. 7 is a flowchart of a process performed by the WF client (110) until the user receives a process on the document (151) and executes the process.
The WF client (110) first receives a processing request for the document (151) issued by the user (70).
1). Next, it is determined whether the received processing request is of a type including storage of edited document contents (70).
2). Only when the received processing request is of a type including storage of the edited document content, the edited document content is stored in the document content (220) in the document (151) via the document server (120) (703). ).

Next, it is determined whether the received processing request is of a type including flow control (704). If the received processing request does not include the flow control, the processing ends.

If the received processing request is of a type including flow control, the following processing is performed. It is determined whether the received processing request is flow control of a new document (70).
5). In the case of flow control for an existing document, an entry having the same document server name, document ID, and process definition name included in the received processing request is retrieved from the flow control information (162) via the WF server (130). (7
06). Via the WF server (130), the flow request type, the processing node name, and the person in charge included in the received processing request are entered into the flow control information (1) retrieved in the processing (706).
62) the flow request (470), the processing node name (440), and the person in charge (450) in the entry are set (70).
9). Further, via the WF server (130), the processing state (460) in the flow control information (162) is changed to act
/ Move (710). Finally, the reference flag (280) in the document (151) is turned ON via the document server (120) (711), and the process ends.

If the received processing request is flow control of a new document, the following processing is performed. Next, via the WF server (130), new (162) is added to the flow control information.
An entry is created (707). And WF server (7
Through 10), the processing start date and time (480) in the entry created in the processing (707) is set (708). After that, the processing after the processing (709) is continuously executed.

FIG. 8 is a flowchart of a process performed by the WF engine (140) for controlling the flow of the document (151).

First, the WF engine (140) creates a list of entries whose flow request is other than NULL from the flow control information (162) via the WF server (130) (801). Next, an unprocessed entry is extracted from the list of entries acquired in the process (801) (802). If there is no unprocessed entry, the process ends. If there is an unprocessed entry, the following process is performed (803). It is checked whether the type of the flow request (470) in the entry extracted in the process (802) is an indirect transition or a direct transition (804). The indirect transition type flow request refers to requesting a transition to the document for the next processing according to the process definition.

On the other hand, the direct transition type flow request is
This means that the user designates the processing node and the name of the person in charge, and requests the document (151) to make a transition to perform the processing. Returning the document (151) when the previous process has a defect and executing the process again is an example of a direct transition type flow request.

If the flow request (470) in the entry is a direct transition (804), the WF engine (140)
Performs the process (808) next.

If the entry flow request (470) is an indirect transition (804), the WF engine (140)
From the process definition (161) specified by the process definition name (430) in the entry via the WF server (130), the processing node to be processed next to the processing node specified by the processing node name (440) in the entry And the name of the person in charge is obtained (805). If the next processing node can be acquired in the processing (805) (806), the WF engine (140) sends the processing node name (440) and the person in charge (45) in the entry via the WF server (130).
0) is updated with the processing node and the name of the person in charge acquired in the processing (805) (807). Further, the document ID in the entry is entered via the document server (120) of the server (101) designated by the document server name (430) in the entry.
The editable user name (240) of the document (151) designated by (420) is updated with the value of the person in charge (450) in the entry (808). Then, the processing state (460) and the flow request (470) in the entry are updated to act / wait and NULL via the WF server (130) (809). Via the WF server (130), the same value as the process definition name (430) in the entry obtained in the process (801) is set to the process definition name (520) in the entry in the flow statistical information (163). The entry in the flow statistical information (163) is searched (810). The value of the counter (530) of the entry in the flow statistical information (163) retrieved in the process (810) is incremented by 1 (811). Finally, the document ID (420) in the entry is entered via the document server (120) of the server (101) designated by the document server name (410) in the entry.
Sets the reference flag (280) of the document (151) specified by
FF is set (816), and the process (802) is executed again.

If the next processing node cannot be obtained in the processing (805) (806), the WF engine (140)
Updates the processing status (460) and the flow request (470) of the entry in the flow control information (162) to sink / wait and NULL via the WF server (130) (812). Next, the same value as the process definition name (430) in the entry obtained in the process (801) is entered into the entry in the flow statistical information (163) via the WF server (130). (520)
(813). The value of the counter (530) of the entry in the flow statistical information (163) searched in the process (813) is incremented by 1 (814). The difference between the current date and time and the processing start date and time (480) in the entry obtained in the process (801) is calculated by summing the processing time (55) of the entry in the flow statistical information (163) searched in the process (813).
(814) and the process (816) are executed for the (0).

FIG. 9 shows that the notification agent (170)
It is a flowchart of the process performed by driving a timer.

The notification agent (170) creates a list of entries of the flow statistical information (163) via the WF server (130) (901). Processing (901)
An unprocessed list is obtained from the list of entries created in (902). When there is no unprocessed entry (9
03), end the processing.

If there is an unprocessed entry (903),
The following processing is performed. The notification agent (170) searches for a process definition (161) having the same name as the process definition name (520) of the entry in the process definition name (301) (904). The administrator mail address (30) in the process definition (161) searched in the process (904)
In (2), the content obtained in the process (902) is transmitted by mail (905). The process (902) is performed again.

(Embodiment 2) In Embodiment 1, the process definition (161) stored in the WF database (160),
Flow control information (162), flow statistical information (163)
There is a name that realizes the real world. Therefore, in order to maintain the confidentiality of the processing flow, first, a mapping table (1000) as shown in FIG. 9 is necessary for the server (101) that requests outsourcing. The mapping table (1000) holds an identifier (1010) meaningless by itself and a name (1020) representing the real world in association with each other. Then, the process definition (16
1), flow control information (162), flow statistical information (1)
63) are in the mapping table (100
0) in the identifier (101) corresponding to the name (1020).
0). The WF client (110) and the WF engine (140) send the mapping table (10
Using the value of the identifier (1010) described in (00),
The document server (120) and the WF server (130) are called. The document server (120) sends the mapping table (1
000), a process of converting an identifier into a name is added.

[0058]

According to the present invention, the services of confidentiality of processing contents and processing flows, accounting for workflow management, and workflow management services, which are issues when outsourcing workflow management, are solved. As a result, the field in which outsourcing of workflow management becomes possible can be expanded.

[Brief description of the drawings]

FIG. 1 is an embodiment of a configuration diagram of a workflow management system according to the present invention.

FIG. 2 is a diagram conceptually representing a document according to the present invention.

FIG. 3 is a diagram conceptually expressing a process definition in the present invention.

FIG. 4 is a diagram conceptually expressing flow control information according to the present invention.

FIG. 5 is a diagram conceptually expressing flow statistical information in the present invention.

FIG. 6 is a flowchart illustrating a process flow of a WF client until a user displays a list of documents to be processed and edits the documents according to the present invention.

FIG. 7 is a flowchart illustrating a flow of a WF client when executing a processing request issued by a user according to the present invention.

FIG. 8 is a flowchart illustrating a flow of a document transition process performed by the WF engine according to the present invention.

FIG. 9 is a flowchart illustrating a flow of a process performed by a notification agent according to the present invention.

FIG. 10 is a diagram conceptually showing a mapping table in the present invention.

[Explanation of symbols]

100: Client, 101: Server including a document database, 102: Server including a WF database, 103: Network, 110: W
F client, 120 ... document server, 1
30 ... WF server, 140 ... WF engine,
150: Document database, 160: WF database, 170: Notification agent.

Claims (3)

[Claims] 1. A document to be processed is electronically circulated between processing persons based on flow control information in accordance with a process definition that describes processing contents, procedures, persons in charge, or rules for determining them. Means for separately storing the document and the flow control information in databases on different computers, and referring to the process definition and the flow control information,
Means for sequentially updating and controlling the access right of the document. 2. A document to be processed is electronically circulated between processing persons based on flow control information in accordance with a process definition that describes processing contents, procedures, persons in charge, or rules for determining them. A workflow management system for outsourcing, comprising: means for counting the number of times flow control has been performed; and means for calculating a usage fee for the workflow management system based on the number of times of flow control. 3. A document to be processed is electronically circulated between processing persons based on flow control information in accordance with a process definition that describes processing contents, procedures, persons in charge, or rules for determining them. A workflow management system for outsourcing, comprising: means for acquiring statistical information related to circulation of the document; and means for periodically notifying the designated administrator of the statistical information.