JPH09191319A - Data circulation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To refer to document data at a high speed even under any condition when each client makes request the reference of the document data. SOLUTION: Each LAN is provided with a document server 115 controlling document data and a work flow, and a main server 116 acting like distributing information of new/update information of a work flow to each document server is installed to a WAN. As to document data registered from a client 119 to each document server 115, data processing information of work flows registered simultaneously transferred from the main server 116 to all the document servers 115 via an inter-server database management section 101, synchronized with each other and a work flow check section 103 checks a progressing state of the work flow and only the document server to which clients requiring reference of document data belong acquires the document data from an information acquisition control section 102.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document circulation system for controlling registration, retrieval, circulation, etc. of document data including a large amount of data such as images on a computer network.

[0002]

2. Description of the Related Art In an electronic document circulation system in a computer network, a system for circulating document data based on a predefined circulation route including conditional branching is called a workflow system. Traditional client
As an example of a circulation system using a server system, there is JP-A-5-158828, which has only one server for controlling a workflow and a document file, and all computers related to the workflow have the same LAN. It was supposed to be on the (Local Area Network). When the workflow is executed across multiple LANs, it is necessary to newly take into consideration that the work flow is through a WAN (Wide Area Network), which tends to cause congestion of processing and has a low transfer rate as compared with the LAN, which is efficient. There is a need to build a system.

Further, in the workflow, a system is required that allows the progress status of the workflow at any given time to be easily known. Examples of this type of system include JP-A-4-316243 and JP-A-62-1063.
However, in Japanese Laid-Open Patent Publication No. 4-316243, the progress status can be known only from the sender who started the workflow to the next destination to which the document is sent at that time. However, the progress status and the existence of circulation items will not be communicated to the planned circulation destinations.
Also, all computers involved in the workflow are the same
It is assumed to be on the AN. JP-A-62-1
In the '063 publication, there is no means for knowing the existence of the undelivered document at that time, and the progress of the already arrived document is tracked in a relay manner along the circulation route in response to an inquiry. Therefore, if the workflow is spread over many LANs, it is considered that the transmission of the progress status is delayed.

Further, when it is necessary to circulate a large volume of document data such as image data in a workflow, and when the workflow extends over a plurality of LANs, at least the user who needs to refer to the document data Need to be able to browse at high speed, and WA
It is necessary to reduce the burden on N.

[0005]

In a workflow system that extends over a plurality of LANs, circulation documents are in a plurality of LANs.
In the above transmission, the first issue is that the target document data already exists in the local server at the time when the client of each destination requests the reference of the document data, and it is accessed. As a result, the document data can be referred to at high speed.

As a second problem, a large amount of document data does not require work such as synchronizing with all the LANs related to the workflow, which is a burden on the network, and the third problem is that documents of each LAN are used. It is possible to achieve the first object while effectively using a non-volatile storage medium such as a hard disk of a server.

Further, as a fourth problem, regarding an arbitrary workflow flowing in the network, at least from a client incorporated in the workflow, it is possible to quickly obtain the progress status of the workflow regardless of before and after the document circulation. can give.

A fifth problem is that at least a client incorporated in the workflow can quickly obtain workflow information such as the number of document data scheduled to be circulated in the future from an arbitrary time point. Finally, all of these issues can be achieved without any loss of functionality even when there is a branch within the expected range such as sending back document data in the workflow.

[0009]

In order to solve the above problems, at least one document server that handles document data and workflow information is installed on all LANs, and workflow information is always maintained between all document servers. Synchronize. In order to efficiently distribute workflow information to each document server, at least one main server that handles workflow information is installed to connect with all WANs. When the progress status of the workflow is updated in any of the document servers, the updated progress status is immediately transmitted to the main server, and the updated progress status is distributed to all the document servers.
The fourth and fifth problems are solved.

Further, the minimum necessary document data is sent based on the distributed progress status, thereby solving the first, second and third problems. In addition, if the circulation route is defined in advance including conditional branching, and all the servers can search the context of the circulation order in the circulation route at any time, when there is a branch of the workflow within the planned range such as sending back However, the above problems can be solved.

[0011]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 shows a device block configuration of a document server according to the present invention. The arrow connecting each component is
The thin arrows show the flow of management data and control information, and the thick arrows show the flow of document data. In the document server 115, an inter-server database management unit 101 that transfers workflow state data to and from the main server 116, and an information collection control unit that transfers document data to and from the information collection control unit 117 of another document server 118. 102, a workflow check unit 10 for verifying various databases related to workflows including workflow status data distributed from the main server and stored in the database unit
3, a data storage unit 105 that stores the document data 104,
A database unit 109 that stores the circulation route definition table 106, the workflow status data table 107, and the new workflow registration data table 108, a data control unit 110 that controls the data storage unit, a table control unit 111 that controls the database unit, and these are operated. An external instruction input device 112 for display, a display device 113 for displaying an operation screen, and processing information for registering and updating document data from each client 119.
Further, it is configured by a client processing control unit 114 for notifying the arrival of the circulation document to the client. The client 119 may have, for example, the image scanner 124 as an input device for registering a document in the document server. It also has an input device 122 for inputting code data and each control command, and has a display device 123 for displaying these control information and the document data obtained by accessing the document server.

FIG. 2 is a block diagram of the main server according to the present invention. In the main server 201, new workflow registration data from a plurality of document servers 202,
Alternatively, when the updated workflow status data is received, and the new and updated workflow status management table 205 is distributed to each document server, the inter-server database management unit 203 and the new workflow registration data transmitted from the document server are processed. A new and changed workflow state management table 20 which is created by processing the circulation route definition table 206 required for processing the new workflow registration data or by registering the updated workflow state data transmitted from the document server.
5, a circulation route definition table 206, a database storage unit 207 that stores the new and changed workflow state management table 205, and a table control unit 204 that controls the database storage unit.

FIG. 3 shows an embodiment of the present invention.
1 shows a network configuration diagram of 1.

First, the networks 302, 308, 3
14, 321 are LANs (Lo
cal Area Network). These are bridges 306,
WAN (Wide Area Netw) by 312, 319, 323
ork) 324. The network 302 has a client A 303, a client B 304, and a document server A 301. The role of the document server is to store the document data, circulation route definition table, and workflow status data table, control the workflow and download the document from other document servers, as well as the workflow and document data newly registered by the client. If there is, the information is transmitted to the main server 325 as a new workflow registration data table. Further, as the workflow progresses, the updated progress status of the workflow is also transmitted to the main server 325 as a workflow status data table. The client performs operations such as document creation, workflow registration, browsing or modification, and annotation. Also inquires about the progress status of the workflow to the document server,
In addition to obtaining the result, it may access a server on a remote LAN via the WAN as needed. Document server B307 and client C309, client D310, client E in network 308
311, the document server C31 in the network 314
3 and the client F315, the client G316, the client H317, the client I318, and the relationship between the document server D320 and the client J322 in the network 321 are the same. The structure of these document servers and the relationship between the document servers and clients are shown in FIG.
As shown in FIG. There is no limit to the number of these document servers and clients. Also network 3
An image scanner 305 is connected to the No. 02 client A 303 as an external input device for image data, which is an example of large-capacity data. Such an input device can be connected to all clients.

The network 308 has a function of accumulating workflow state data newly registered or updated in all document servers, processing the data into a new table form, and redistributing it to all document servers. There is a main server 325. The configuration of the main server and the relationship between the main server and the document server are as shown in FIG.
The main server can share hardware with any one (or more) document server, but can also be a separate server in terms of hardware. Figure 3 in this example
, The main server 325 is the document server B30.
The mode in which the hardware is shared with the No. 7 will be described.

FIG. 4 is a circulation route definition table held by the document server and the main server, and shows the configurations of the circulation route definition table 106 of FIG. 1 and the circulation route definition table 206 of FIG. For all independent workflows that can flow in the network, any workflow always has one circulation route ID 401. There may be workflows that have the same circulation route ID among the workflows that are flowing in the network at a certain point in time. For each circulation route ID 401, the document server 402, the client 403, the role (role) 404, the circulation start 40
5, data areas of approval 406, rejection 407, and hold 408 are provided. Document server 402, client 403,
The roles 404 are collectively called a role setting table 409.
The role setting table 409 and the circulation route ID 401 together represent the state 412. Circulation start 405, approval 40
6, the rejection 407, and the hold 408 are the transfer control table 410.
Call. The transfer control table 410 has the status 412 described above.
The operation 411 is represented with respect to. The circulation route definition table searches for a row in the current state from the role setting table, and the next state transition destination is defined in the item intersecting with the column of the performed operation. In a workflow, a document is circulated from one role to another role with the role as one unit.
The document server to which the client belongs is registered for each role. To determine the role, roll 1, roll 2
・ ・ The word "roll" is used. In FIG. 4, the client assigned to the role of role 1 is client A, and the document server to which the client belongs is document server A. It is possible to assign multiple clients to one role,
In that case, the document will be broadcast, but this section describes an example in which one client is assigned to one role.

Next, for each role, a role that can start the workflow is set. The workflow is circulated in order from the role that can be started according to the circulation route definition table, and when the client approval assigned to the role that can be ended is issued, the document is returned to the role that can be started, and the notification of the end of circulation is issued to the main server. Each document server refers to the workflow state data table redistributed from the main server, deletes the workflow data from each document server, and the circulation is completed.

Further, when the document circulated in each roll is approved, the roll for circulating the document next is set.
In addition, when the document circulated in each role is not approved, a role for returning the document is set. Then, set a role to hold the circulated document. In FIG. 4, the roll that can start circulation is roll 1, and when the circulation starts, the document is sequentially circulated as roll 2, roll 3, roll 4, roll 5 as long as the document is continuously approved in each roll. When the approval is given in the role 5, the document is returned to the role 1, the same contents are circulated to the roles 6 and 7, and the end notice is transmitted to the main server. In this case, operations such as approval and rejection of the document are not permitted by the rolls 6 and 7, and only browsing is possible. When the document is not approved by each roll, the rollback destination is roll 1 for roll 2, roll 2 for roll 3, and roll 4 for roll 5. When the document is not approved by the roll 4, the rollback destination is the roll 1. In this case, the hold destination of the document when the hold is issued in each role is
It is set to be the same as the role that issued the hold, but it is possible to assign the hold destination to another role. In this way, the flow of the document can be set freely.

FIG. 5 is a table of workflow status data held in each document server, and shows the contents of the workflow status data table 107 in FIG. When the document data and the circulation route ID are registered by the client in an arbitrary document server, the new workflow registration data table 108 in which the document data name 601 and the circulation route ID 602 are described as shown in FIG. Sent to. In FIG. 1, when the new workflow registration data table 108 is transmitted to the main server, the new workflow registration data table is deleted from the database unit 109. Next, based on the transmitted new workflow registration data table, for all workflows and document data newly registered in the network, independent workflow NO. 701 and document data ID 703 are set by the main server as shown in FIG. Is set. The transmitted circulation route ID 602 is directly substituted for the circulation route ID 702. The main server uses this new / updated workflow status data table 2
After creating 05 (FIG. 7), the new / updated workflow status data table 205 is transmitted to each document server, and the new / updated workflow status data table 205 in the main server is deleted. Each document server receives new
The update workflow status table is added to the workflow status data table 107 as shown in FIG. The first half of the workflow status data table, that is, workflow N
The O.501, the circulation route ID 502, and the document data ID 503 remain unchanged until the workflow ends, but the other elements change at any time depending on the workflow state. Location 504 indicates to which role the workflow and the latest document is currently arriving. A state 505 shows what kind of instructions are given to the document and the workflow in the role. Ie approval, hold, reject,
And that's it. When each document server detects that the end is written in this column, it deletes the line from the workflow state table. That is, the workflow ends and is deleted from the network. As an example of these, in FIG.
In the circulation of 001, the circulation route ID is 1 and the document data ID is 0.
The document 001 is circulated, and it can be seen that the workflow has progressed to roll 3 at this point. Here, assuming that the circulation route ID corresponds to that in FIG. 4, it can be seen from the status section that the approval operation has been performed in roll 3, and this document should be circulated to roll 4 next. It is derived from FIG. 4 that

The tables and document data are transferred between the main server and each document server while referring to the above tables. The operation of this system will be described below using an actual document flow. The network system configuration is as shown in FIG. 3, and the circulation route definition table is shown in FIG.
Use those. First, each of the document servers 115 (FIG. 1) and the main server 201 (FIG. 2) has a preset circulation route definition table 106 (FIG. 1) and FIG.
Owns 06 (FIG. 2). Circular route definition table 10
The contents of 6 (FIG. 1) and 206 (FIG. 2) are the same in all servers. Although this table can be physically changed by any server or client, it is practical to make a change on condition that the user has a certain authority in order to prevent confusion. In any server, by the command from the client,
Alternatively, if the circulation route definition table is changed by a direct operation to the server, and if the circulation route definition table is on the document server, the updated circulation route definition table 106 (FIG. 1) is transferred to the main server. , The main server redistributes the updated circulation route definition table 206 (FIG. 2) to all the document servers, and always uses the same circulation route definition tables 106 (FIG. 1) and 206 (FIG. 2) in all the document servers. To be able to hold. Immediately when the table on the main server is changed, the main server distributes the updated circulation route definition table 206 (FIG. 2) to all the document servers, and the same circulation route definition table 106 is always distributed to all the document servers. (FIG. 1) and 206 (FIG. 2) can be held. When the main server shares the hardware with any document server, the circulation route definition tables 106 (FIG. 1) and 206 (FIG. 2) may be physically the same on the hardware. it can. In this example, as shown in FIG. 3, the main server 32
5 shares the hardware with the document server B307.

Next, the start of the workflow will be described. In this example, it is assumed that the document data is circulated from the client A 303 to the circulation route with the circulation route ID 1 in FIG. 4 in the network of FIG. First, for image registration, from the client A303 to the document server A3
The image is registered in 01. Referring to FIG. 1, first, in the client 119, an input is made from the input device 122 so as to register the document data, and the main control unit 125
From the image control unit 120 to the image scanner 1
An instruction is given from 24 to capture an image. A document data name is set for the acquired image data by inputting from the input device 122 to the document control unit 120 of the client 119. Next, the document data is transferred from the client 119 to the document server 115, and the client processing control unit 114 of the document server is notified that there is new document data. Upon receiving the request for new document registration from the client, the client control unit 114 in the document server instructs the data control unit 110 to register the document data in the data storage unit 105 from the client. At the same time as registering this series of document data, the circulation route ID for this document data is input from the input device 122.
It circulates according to or accepts the circulation instruction from the user. As a procedure, a reference request for the circulation route definition table is issued from the input device 122 of the client to the document server, and the document server makes the client processing control unit 11
After receiving the reference request at 4, the table control unit 11
The circulation route definition table in the database unit 109 is referenced via 1 to obtain a list of circulation routes, and the client processing control unit 114 notifies the client 119. The client 119 displays the contents of the received circulation route definition table. When the user selects the circulation route ID 1 from the input device 122, the circulation route ID is notified to the document server 115. When the document server 115 acquires the circulation route ID by the client processing control unit 114, it creates the new workflow registration data table 108 as shown in FIG. 6 via the table control unit 111. That is,
The document data name 601 and the circulation route ID 602 in FIG. 6 set by the client 119.

By the operation up to this point, new document data 104 in the data storage unit 105 in the document server 115,
Further, the new workflow registration data table 108 is created in the database unit 109. The workflow check unit 103 independently monitors each table, and when detecting that a new workflow is registered in the new workflow registration data table 108, the workflow check unit 103 notifies the inter-server database management unit 101 of the main server. To the main server 116, the inter-server database management unit 101 sends information about the newly registered workflow to the main server 116 based on the registration request. That is, the new workflow registration data table 108 is acquired via the table control unit 111, and the inter-server database management unit 101 transmits the new workflow registration data table 108 to the main server 116. If the transmission is successful, the table control unit deletes the new workflow registration data table.

Next, the operation of the main server that receives the new workflow registration data table will be described. FIG.
In the new workflow registration data table transmitted from a certain document server 202,
It is received via the inter-server database management unit 203. Next, the new workflow registration data table is stored in the control storage area 207, processed as described below, and then added to the new and updated workflow state management table 205. That is, the workflow registered first is an independent workflow NO.701 as shown in FIG.
Is set, and an independent document data ID 703 is set corresponding to the document data. Further, the place 704 and the state 705 are set by referring to the circulation route definition table 206.

In this example, workflow No. 701 is 00
01, circulation route ID 702 is 1, document data ID 703 is 0001, place 704 is roll 1 from FIG. 4, state 705
Since circulation has started, it means that circulation has started.

New workflow status management table 205
When the document is created, the main server immediately sets the new workflow status management table 205 in each document server 202.
To the server via the inter-server database management unit 203. In each document server, the inter-server database management unit 1
01 receives it, updates the workflow status data table 107, that is, after adding the information of FIG. 7 to FIG. 5, and then reports the change to the workflow check unit 103. When the distribution is completed, the main server deletes the row of the workflow from the workflow status management table 205.

Next, each document server starts the process of checking the workflow status table. In FIG. 1, when the new or updated workflow status management table is transmitted from the main server 116, the document server 115 acquires it by the inter-server database management unit 101 as described above, and the workflow status data table of the database unit 109 is acquired. Add to 107 and report the change to the workflow check unit 103. Thereby, the workflow checking unit 103 checks whether or not any of the clients belonging to the workflow checking table 103 should refer to the circulation document for the changed row of the workflow status table. That is, in the workflow status table of FIG. 5, the circulation route ID 502, the place 504, and the status 505.
Further, referring to the columns of the role 404, the document server 402, and the operation 411 from the circulation route definition table 106 (FIG. 4) using the circulation route ID 502 as a key, the client that next refers to the circulation document belongs to the role. To investigate. In the case of this case, circulation route ID 40
1 is 1, role 404 has reached role 1, and operation 411 is set in FIG. 4 based on state 505 in the figure. Therefore, referring to the column of operation 411, state 505 indicates circulation start. It can be seen from the column of the circulation start 405 of No. 4 that the document data is circulated next to the roll 2. Therefore, the role 404 and the document server 40
By referring to the column 2 of the table, it is recognized that the role 2 is assigned to the client belonging to the document server B (client C in this case). With the operations up to this point, the servers other than the document server B do not perform any particular processing because the client that next refers to the document data in the newly created workflow does not belong to itself. With regard to (2), since the client (client C) who should refer to the document data next belongs to itself, it is possible to perform high-speed reference when there is a request to refer to the document data from the client C, which is one of the objects of the present invention. Therefore, the document data must be owned in the own data storage unit 105. That is, the workflow status data table 10 of the workflow check unit 103.
The document server B, which recognizes that the client who needs to refer to the document data next time belongs to itself by the check of 7, further adds the workflow state data table 1
Location 504 of 07 (FIG. 5), circulation route definition table 1
By referring to the role 404 of 06 (FIG. 4) and the column of the document server 402, it is obtained in which role the required document data is, and therefore in which document server. In the case of this example, the workflow status table 10
The role 1 is acquired from the location 504 of No. 7, and the document server 402 corresponding to the role 1 of the role 404 of the circulation route definition table 106 is acquired as the document server A. As a result, the document server B sends the document data required by the document server A 118 from the information collection control unit 102 to the document data.
The data is downloaded by designating the ID 503 and stored in the data storage unit 105. Then, when an inquiry is made from the client C 119 via the client processing control unit, the server B stores the document data ID 503 with the workflow No. 501 of 0001 in the data storage unit 105.
Enables the reply that there is a circulation document of 0001 and needs to be referenced.

Through the above processing, the client C makes an inquiry to the document server B to know that there is a circulation document to be referred to. If the client C needs to refer to the document data thereafter,
At any time during the circulation order of the client C, the document data 104 can be referred to at high speed simply by accessing the local server. This is superior in that the response speed and the load on the WAN are reduced as compared to remote access to the document server A that is the source of the creation and reference of the document each time the client C requests the reference of the document data. Produce the effect.

Next, it is assumed that the operation (change, attachment of various data, etc.) on the content of the document data in the client C is completed, and the approval is issued for the document data. That is, in FIG. 1, the input device 12 of the client 119
From 2, the document data 104 in the data storage unit 105 is operated, and then the roll 2 is written in the column of the location 504 and the approval is written in the column of the state 505 of the workflow state table via the table control unit 111. Therefore, at this time, both the document data and the workflow status data are updated. In FIG. 1, the document server B uses the inter-server database management unit 1 for the updated row in the workflow status table 107.
From 01, it transmits to the main server 116. In this example, for the workflow of workflow No. 0001 in the workflow status data table 107, role 2 is assigned to the column of location 704 and approval is assigned to the column of status 705 as the updated workflow status data table, and the workflow is sent to the main server.

Next, the main server redistributes the received update workflow status data table to each document server. In FIG. 2, the main server 201 receives the update workflow state management table from the document server 202 via the inter-server database management unit 204. Unlike the new case, the received update workflow state management table is not processed as it is and redistributed to each document server 202 via the inter-server database management unit 204. Here, each document server again checks the received workflow status table. In this example, the circulation order is roll 3, but from FIGS. 3 and 4,
The client D assigned to the role 3 is on the same LAN as the document server B that is the same as the client C assigned to the role 2 that has performed the preceding process. Since the document server B obtains the above information by the workflow check process, the process of downloading document data from another document server is not performed. The above is the same when, for example, the document is rejected in roll 3 and a remand order to roll 2 is issued.
Also in this case, the document data is not downloaded, and the client C assigned to the previously returned role 2 refers to the document data in the document server B that has been changed by the role 3 to change the data. Will be added.

When the document data operation in the roll 3 is completed and the approval is issued, the roll 4 which needs to refer to the document data next is the roll 4. The client to which the role 4 is assigned is the client F in this case from FIGS. 3 and 4, and the document server to which it belongs is the document server C. Therefore, after the updated workflow status data table is transmitted from the document server B to the main server again and the updated workflow status data table is distributed from the main server to each document server, the above workflow check is performed, and the client belonging to the client next It is the document server C that recognizes that it is necessary to refer to the document data. Then, the document server C downloads the document data from the document server B via the information collection control unit 102, and then notifies the client F to which the role 4 is assigned that the circulation document exists.

Here, it is assumed that the document data is not approved in the roll 4 and is sent back. When the document is rejected by roll 4, according to the circulation route definition table of FIG. 4, it is roll-back destination roll 1 at the time of rejection 407. After the workflow status table including these pieces of information is distributed to each document server, each document server again checks the workflow status data table 107 by the workflow checking unit 103. At this time, the client assigned to the role 1 ( It is the document server A that recognizes that the client A) belongs to itself. The document server A is the information collection control unit 102.
The document is downloaded from the document server C via the, and the client A to which the role 1 is assigned is notified of the existence of the returned document. Even if the document data goes backward in the workflow as described above, when the client requests the local server to browse the document data, the necessary document data always exists on the local server.

If the document data is approved by the client assigned to the role 4, and the document data is approved by the client assigned to the transfer destination role 5, the document data is obtained according to the circulation route definition table of FIG. Is roll 1, roll 6, roll 7
Will be sent to. At the same time, the document server C to which the role 5 belongs sends information indicating that the workflow has ended to the main server. The main server substitutes end into the column of status 705 of the workflow status data table,
Distribute to each document server. Each document server refers to the distributed workflow status table 108 and deletes the workflow row in which the end is written in the column of status 505. As a result, the workflow is deleted from the network, and in this case, the latest images are in roll 1, roll 5, roll 6, and roll 7. In other words, the circulation started from roll 1 is finally approved by roll 5,
It means that the approved data is returned to the role 1, and it remains in the role of the role 6 and the role 6 which needs the document data as a reference material.

Next, in the above-mentioned workflow, means for knowing the number of document data or workflows that can be circulated to the client at a certain time from the client to which an arbitrary role is assigned, and the progress status of the workflow at that time. I will describe. Roll 3 for example
When the above-mentioned inquiry is made from the client G316 to which the role 5 is assigned at the stage when the workflow has progressed to, the client G316 searches the workflow state data table 107 in the local server C313, and the client G316 does Among the circulation route IDs assigned to the roles, the circulation route ID 50 in the workflow state data table of FIG. 5 is used as the workflow currently executed.
2 is acquired from 1, 5, 3, ... And the circulation route ID 401 in the circulation route definition table of FIG. 4 is 1, 5, 3 ,.
.. is searched for the client 403 in the data, and the circulation route is set as the circulation route in which the client G exists.
Since ID 1 is obtained, the workflow No. 0001, the document data ID 0001, the location is role 3, and the status is approved from the workflow status table at that point in time. According to the circulation route definition table, the circulation order of the client G is one after another. You can immediately get the information that there is.

Further, in this example, the information that the number of workflows having the document data to be circulated to the client G in the future from this time point is 1 and the circulation route is the circulation route ID 0001 can also be obtained.
These pieces of information can be searched from the client assigned to any role any time after the workflow is registered in the role 1 and after the workflow is completed. Further, even in the case of a client that is not assigned to any role, the same search can be performed by giving access authority to the circulation route definition table 106 and the workflow status data table 107. If necessary, it is possible to access and browse the document data existing on one of the document servers from the document data ID, but in this case, the client F actually requests the browsing and then the client F actually makes a request.
The client F needs to wait until the document data corresponding to the document server C to which it belongs is downloaded.

[0036]

As described above, according to the present invention,
In a workflow system that spans multiple LANs,
By constantly synchronizing a small amount of workflow status data with the document server of each LAN, the transfer of a large amount of document data between LANs can be minimized, reducing the load on the network and in principle Information about an arbitrary workflow at that time can be acquired at high speed from the computer by simply accessing the local server. With regard to the document data, the client can access the document data at high speed simply by accessing the local server at all times.
Further, even when there is a branch within a predictable range such as the sending back of the Circular 2 document, it is possible to use the function retaining the above features without any limitation.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a document server according to an embodiment of the present invention.

FIG. 2 is a configuration diagram of a main server according to an embodiment of the present invention.

FIG. 3 is a configuration diagram of a multiple network system according to an embodiment of the present invention.

FIG. 4 is a circulation route definition table according to an embodiment of the present invention.

FIG. 5 is an example of a workflow status data table according to an embodiment of the present invention.

FIG. 6 is a new workflow registration data table according to the embodiment of the present invention.

FIG. 7 is a new / updated workflow status data table according to an embodiment of the present invention.

[Explanation of symbols]

101 server-to-server database management unit 102 information collection control unit 103 workflow check unit 104 document data 105 data storage unit 106 circulation route definition table 107 workflow status data table 108 new workflow registration data table 109 database unit 110 data control unit 111 table control unit 112 External instruction input device 113 Display device 114 Client processing control unit 115 Document server 116 Main server 117 Information collection control unit 118 of other document server 118 Other document server 119 Client 120 Document control unit 121 Workflow control unit 122 Input device 123 Display device 124 Image scanner 125 Main control unit 201 Main server 202 Document server 203 Inter-server database administration unit 204 table control unit 205 new and updated workflow state management table 206 circulation route definition table 207 control storage area 208 database unit 301 document server A 302 LAN 303 client A 304 client B 305 image scanner 306 bridge 307 document server B 308 LAN 309 client C 310 Client D 311 Client E 312 Bridge 313 Document Server C 314 LAN 315 Client F 316 Client G 317 Client H 318 Client I 319 Bridge 320 Document Server D 321 LAN 322 Client J 323 Bridge 324 WAN 325 Main Server 401 Circulation Route ID 402 Document server 403 Client 404 Role 405 Circulation start document transfer destination 406 Approval document transfer destination 407 Rejection document transfer destination 408 Hold document transfer destination 409 Role setting table 410 Transfer control table 411 Operation 412 Status 501 Workflow NO. 502 Circulation route ID 503 Document data ID 504 Place 505 State 601 Document Data Name 602 Circulation Route ID 701 Workflow No. 702 Circulation Route ID 703 Document Data ID 704 Place 705 State

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Jun Nishiyama 2880 Kokuzu, Odawara City, Kanagawa Stock Company Hitachi Storage Systems Division

Claims (4)

[Claims] 1. A system for managing a large amount of data such as an image using a plurality of servers, and referring to or updating arbitrary data across a plurality of servers by a circulation function, relates to a document circulated for all the servers. Only information that manages data such as circulation order is always synchronized,
The actual data is circulated, and when it is viewed by a user registered on another local server, it is copied to the local server and displayed at high speed simply by accessing the data on the local server. A system that makes it possible and makes it possible to efficiently use a nonvolatile storage medium such as a hard disk because only the necessary server has the latest data, and to reduce the load on the network. 2. When the data circulated from another server or the additional information has a defect by the circulation function, the data indicating the defect is added, the data is changed, and the user of the other server of the transfer source is made. Even if you send it back
The system according to claim 1, wherein even the returned user can refer to the changed data only by accessing the local server to which the user is registered. 3. The system according to claim 1, wherein when the circulation is performed across the servers, even if the circulation data is on different servers, the state of the circulation data can be referred to only by accessing the local server. 4. A user of another local server regardless of which local server has information such as which user of each circulation route and how much data is accumulated when performing a circulation between servers. The system according to claim 1, which can be accessed at high speed from.