JPH08221476A - Work flow system - Google Patents

Abstract

PURPOSE: To efficiently perform the tasks in each domain by retrieving its own organaization management part through each work flow server based on the organization information included in the folder information and then generating and carrying out the flow of the corresponding organization. CONSTITUTION: The work flow servers 16a and 16b of respective domains detect the organizations while executing the flows generated in their own domains and then read the domains including the detected organizations out of a work flow server register part 13. Then, both servers send the folder information including the information on the corresponding organizations added to the folder of the present execution step to the work flow servers 16a and 16b of the domains including the read organizations. Upon receiving the folder information, both servers 16a and 16b retrieve their own organization management parts 18a and 18b based on the organization information included in the received folder information and generate the flows of the organization. When the execution of these flows are finished, the folder information including the folders obtained by the execution of the flows are sent to the servers 16a and 16b of another domain of the transmitter side.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow system for managing a work flow using a computer system, and more particularly to a workflow system for managing a flow across a plurality of domains.

[0002]

2. Description of the Related Art In a company or a government office, in order to efficiently execute a generated job, each job is divided into a plurality of unit jobs common to each job, and each unit job is divided into these unit jobs. It is assigned to a specific person in charge (user) who specializes in it to improve the efficiency of the work as a whole.

The same applies to various jobs using a computer. Then, each job is divided into unit jobs called a plurality of work points, and a person (user) registered in the corresponding work point is referred to as a folder created in the previous stage, such as a document, drawing, program, etc. A system that manages the flow of work for transferring the container for the artifacts and transferring the folder for the artifacts created in the work point to the next work point is called a workflow system.

More specifically, at each work point, the person in charge (user) assigned to the work point
However, the folder is sent to the next work point according to the flow defined in the workflow server when the folder in charge is subjected to predetermined processing such as browsing, editing, adding, etc.

The operation of sending a folder to the next work point is to move the corresponding folder to the "reception tray" of the user assigned to each work point (directory for receiving a folder determined for each person). Means

In such a workflow system, the unit for executing the work in the above-mentioned company or government office is one organization consisting of sections or departments, and this unit is called a domain. Most of the work that occurs in companies, government offices, etc. can be sufficiently processed within the above-mentioned one organization (one domain).

FIG. 15 is a block diagram showing a workflow system having a section or department as one domain. For each domain 1a, 1b, users a ₁ , a ₂ , a
_{3, ..., b 1, b} 2, b 3, a plurality of workpieces point 2a which ... is assigned, 2b are connected transmission lines 3a, through 3b workflow server 4a, the 4b. For example, as shown in FIG. 16, when the workflow server 4a, 4b inputs a work flow 5 composed of a plurality of work points 2a, 2b, the workflow server 4a, 4b manages execution of the flow 5, specifically, Top work point 2a (WP
1) is started, and when the processing at the work point 2a (WP1) ends, this work point 2a (WP1)
The folder created in step 2a (WP
2) and transfer to this work point 2a (WP2)
To start. Further, when the process at the work point 2a (WP2) is completed, the folder is transferred to the next work point 2a (WP3) and the next work point 2a (W3).
Start P3).

In this way, each workflow server 4a, 4
The b manages the execution of the work points 2a and 2b constituting the flow 5 in the self-domains 1a and 1b and the folder management at each execution stage of the flow.

[0009]

However, as shown in FIG.
The workflow system shown in (1) also had the following problems to be solved. That is, each domain 1a,
Each of the work points 2a and 2b managed by the workflow servers 4a and 4b of 1b is the domain 1 to which it belongs.
Since there are only the work points 2a and 2b incorporated in a and 1b, the work points 2 of the other domains 1b and 1a
It was not possible to create a work flow including a and 2b.

In order to eliminate such inconvenience, two domains 1a and 1b shown in FIG. 15 are integrated into one domain, and one work flow server is used to carry out all jobs and all work points 2a and 2b. It is possible to manage it, but if you manage the execution of all the work flows by one, the processing load increases, and the flow waiting for processing occurs frequently,
After all, the processing efficiency of the entire system decreases.

The present invention has been made in view of such circumstances, and even if a flow in which a work to be executed in another domain is incorporated into a part of the work generated in the self domain, the flow is created in each domain. It is an object of the present invention to provide a workflow system capable of efficiently executing a work flow, greatly expanding the types and scales of jobs handled by this system, and efficiently executing each work.

It is another object of the present invention to provide a workflow system which can easily grasp the progress status of a flow sent from its own domain and being executed in another domain.

Further, in addition to the above objects, it is another object of the present invention to provide a workflow system capable of executing a flow as normally as possible even when an abnormality occurs and improving reliability.

[0014]

According to the present invention, each work point belonging to each domain is registered, each work generated in each domain is divided into a plurality of work points, and the execution order of each work point is flowed. And is applied to a workflow system that performs execution management of each flow and folder management at each execution stage by each workflow server provided for each domain.

In order to solve the above problems, in claim 1 of the present invention, each work point is provided for each domain and each domain is composed of each work point belonging to its own domain which is open to other domains. An organization management unit that stores the flow of the organization, a workflow server registration unit that stores a plurality of organization information including the domain to which each organization belongs and designation information that specifies the workflow server of each domain, and a workflow server registration unit provided in each workflow server , When an organization is detected in the process of executing a flow that occurred in its own domain, the domain to which the organization belongs is read from the workflow server registration unit, and the folder information in which the information of the organization is added to the folder at the current execution stage is the domain to which the organization belongs. Folder information sending means for sending to each workflow server and each workflow server When the folder information is received, an organization flow generation executing unit that searches the own organization management unit using the information of the organization included in the corresponding folder information to generate and execute the flow of the corresponding organization, and an end step of executing the flow. And folder information replying means for returning the folder information including the folder to the workflow server that is the transmission source.

According to a second aspect of the present invention, in the workflow system according to the first aspect, a workflow server management unit in which the folder information received by the workflow server that receives the folder information is written, and each workflow server are provided. In response to a folder position tracking command input after transmission of the folder information, a folder position tracking unit for detecting the current folder position from the workflow server of the folder information transmission destination is added via the inter-workflow server management unit.

Further, in the invention of claim 3, in contrast to the workflow system of claim 1, a backup memory which is provided in each workflow server and stores and holds the same storage content of the workflow server registration unit, and the workflow server registration. A transmission backup means for specifying a transmission destination workflow server of folder information based on the stored contents of the backup memory is added when a copy error occurs.

[0018]

In the workflow system configured as described above, the organization management unit of each domain stores the flow of the organization composed of each work point belonging to the self domain that the self domain has made public to other domains. Has been done.

Further, the workflow server registration unit stores a plurality of pieces of organization information including domains belonging to each organization registered in the organization management unit of each domain and specification information for designating a workflow server of each domain.

In such a configuration, the operator is not limited to the normal flow consisting of only the work points belonging to the same domain, and the work flow belonging to the same domain as well as other domains registered in the organization management unit. It is possible to create two types of flows, one that incorporates the published organization.

When the workflow server of each domain detects an organization in the process of executing the flow generated in its own domain, it reads out the domain to which the organization belongs from the workflow server registration unit and stores the information of the organization in the folder at the current execution stage. The folder information marked with is sent to the workflow server of the domain to which the read organization belongs.

The workflow server of the domain to which the organization belongs, which has received the folder information, searches its own organization management section using the information of the organization included in the relevant folder information to generate the flow of the relevant organization. That is, since the flow of the organization opened to the other domain by itself is stored in the own organization management unit, the flow of the relevant organization can be easily reproduced. Then, since the reproduced flow includes only the work points belonging to the own domain, this reproduced flow of the own organization can be easily implemented.

When the execution of this flow is completed, the folder information including the folder obtained by executing the flow is returned to the workflow server of the other domain of the transmission source. In this case, the domain of the reply destination and the specific information of the workflow server can be obtained from the organization delivery file added to the folder.

In the workflow server of the transmission source (reply destination) that has received this folder information, the received folder is transmitted to the next work point of the organization in the first input flow, and the flow execution management is performed from the relevant work point. And the folder management may be restarted.

As described above, by providing the workflow server registration unit for storing the information of each function common to each domain and the designation information for designating the work server of each domain, the workflow server of each domain belongs to its own domain. It is possible to incorporate an organization that is composed of not only the work points of other domains but the work points of other domains.

According to the second aspect of the invention, folder information to which the organization information received by the workflow server is added is written in the inter-workflow server management section.
Therefore, when the folder position tracking command for detecting the current position of the folder is input to the workflow server to which the flow is input when the progress status of this flow is transferred to the organization, this workflow server It becomes possible to detect the flow of the organization and the current folder position from the workflow server of the folder information transmission destination via the inter-workflow server management unit.

Further, in the invention of claim 3, a backup memory for storing and holding the same storage content of the workflow server registration unit is provided for each workflow server. As described above, the workflow server registration unit stores a plurality of pieces of organization information including the domain to which each organization is registered in the organization management unit of each domain and specification information that specifies the workflow server of each domain.

Therefore, due to some factor,
Even if an error occurs in the workflow server registration section,
It is possible to specify the destination workflow server of the folder information based on the stored contents of the backup memory. Therefore, the organization flow can be normally executed by the workflow server of another domain.

[0029]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a workflow system of the embodiment. In the workflow system of this embodiment, the two domains 11a and 11b of the domain A and the domain B are the network 1 such as a LAN.
They are connected to each other via 2. Each domain 11a, 1
1b means an organization of a section or department in a company or government office.

Furthermore, a workflow server registration unit 13 and an inter-workflow server management unit 14 are connected to the network 12. An inter-department management server 15 is connected to the workflow server registration unit 13 and the inter-workflow server management unit 14. The inter-department management server 15 manages information exchange between the domains 11a and 11b based on the stored contents of the workflow server registration unit 13 and the inter-workflow server management unit 14.

Further, in each domain 11a, 11b,
Workflow servers 16a and 16b that manage the respective work points 2a and 2b and users that belong to their own domains 11a and 11b, and the execution management of the input flow and the folders obtained at each execution stage of the flow. ,
Flow definition part 1 for the operator to create a work flow
7a and 17b, and organization management units 18a and 18b that store the flow of the "organization" that the self domains 11a and 11b disclose to the other domains 11b and 11a among the flows defined by the flow definition units 17a and 17b. Is provided. In this case, the “organization” indicates one unit made up of work points in one domain such as a section or department.

To the flow definition unit 17a of the domain 11a, a general flow 19 composed of only the work points 2a (WP1, WP2, WP3) belonging to the self domain 11a shown in FIG. 2 is input. Note that each work point 2a has users a1, a2, a3, respectively.
Is input in the assigned state.

In the workflow server 16a, as shown in FIG. 3, a flow definition table 20a for the general flow 19 defined by the flow definition unit 17a is formed. Furthermore, in this flow definition table 20a,
Each work point 2a (WP
1, WP2, WP3) assigned to each user a
A work point user table 21a for storing 1, a2, a3 and a work point order relation table 22a for storing the execution order of each work point 2a (WP1, WP2, WP3) in the relevant flow 19 are formed.

Further, in the workflow server 16a, the name and ID of the folder in the flow currently being executed
(Identification code), folder information table 23a for storing titles, etc., folder memory 24a for storing deliverables stored in the folder, and users a1, a2, a3, ... Registered in the belonging domain 11a. A user table 25a for storing is formed.

In the system of the embodiment, the domain 11a of the organization A composed of one section is shown in FIG.
As shown in (a), in addition to the section manager A, three users a1, a2, and a3 are registered in the user table 25a.

Also in the workflow server 16b of the other domain 11b, in addition to the flow definition table 20b including the work point user table 21b and the work point order relation table 22b, the folder information table 23b, the folder memory 24b and the use A person table 25b is formed.

In the system of this embodiment, in the domain 11b of the organization B, as shown in FIG.
In the user table 25b, in addition to the section manager B, four users b1, b2, b3, b4 are registered.

As shown in FIG. 4, the organization management units 18a and 18b in the workflow servers 16a and 16b have the organization A and organization B flows defined by the operator in the flow definition units 17a and 17b, and their organization information. Memorize Specifically, the organization name, the organization reception tray indicating the directory in which the created folder is stored, and the organization flow are registered.

In the system of this embodiment, in the organization A of the domain 11a, the name of the organization is [organization A], and the flow of the organization is shown in the order of users [a1 → a].
2 → a3]. In the organization B of the domain 11b, the name of the organization is [B section ** in charge], and the flow of the organization is [b1 → B section manager] in the order of the users.

Further, in the work server registration unit 13 which can be freely accessed by the workflow servers 16a and 16b of the domains 11a and 11b, as shown in FIG. 4, the workflows used when the folder information is transmitted. The addresses of the servers 16a and 16b on the network 12 are registered in advance. Further, in the work server registration unit 13, each organization name for identifying the organization A and the organization B registered in each organization management unit 18a, 18b. The organization information such as the name of each work server and each reception tray is registered.

Similarly, the work server management unit 14 which can be freely accessed by the workflow servers 16a and 16b of the domains 11a and 11b includes an organization currently extending over both domains 11a and 11b. The information of the original flow 26 in the case where the flow 26 shown in (1) is being executed and the flow 28 of the organization is being executed is temporarily stored. Specifically, as shown in FIGS. 11 and 12, the workflow server 16 on the execution side of the flow of the organization
a, 16b, the folder memory 24a, 24
The storage contents of the organization sending files 29a and 29b set in b are set.

Then, the organization sending file 29a,
In 29b, the sender workflow server name, the flow name, the return tray (the directory that receives the folder when the folder information is returned), the inbox (the directory that receives the folder information when the organizational flow ends normally), etc. Is memorized.

The storage information of the inter-workserver management unit 14 is such that the workflow servers 16a and 16b that are the senders of the folder information are the domain 11 that is the recipient of the folder information.
This is used when searching the current position of the folder in b and 11a.

In the workflow system configured as described above, the operator preliminarily uses the flow definition units 17a, 17
When the flow of the organization A and the organization B and the organization information are input using b, the information is stored in the respective organization management units 18a and 18b, and a part of the information is registered in the common workflow server registration unit 13. .

Then, for example, one workflow server 16a registers the flow input from the flow definition unit 17a in the flow definition table 20a, and initializes the various information related to this flow described above in the folder information table 23a and the folder memory 24a. Set.

In the case of the general flow 19 in which the set work flow is composed only of the work points 2a belonging to the own domain 11a shown in FIG. 2, for example, the work flow server 4a in the conventional work flow system shown in FIG. Similarly to the above, the respective work points 2a (WP1, WP2,
WP3) is started and one work point 2a
When the processing in (WP1, WP2, WP3) is completed, the folder storing the deliverables obtained at that time is transferred to the next work point 2a (WP1, WP2, WP3), and the contents of the forter memory 24a can be obtained. Update to the folder. Further, the current position of the folder information table 23a is set to the next work point 2a (WP1,
Update to WP2, WP3).

The set work flow is shown in FIG. 6, for example.
As shown in FIG. 8, in the case of the flow 26 including the work point 2a belonging to the self domain 11a and the organization 27 published by another domain 11b, use of the work point of the flow definition table 21a of the work flow server 16a as shown in FIG. The name of the organization [B section ** charge] is set in the third work point WP3 in the person table 21a.

As shown in FIG. 7, the actual flow 28 of the organization having the name [section B ** in charge] is preset in the organization management unit 18b of the domain 11b, as shown in FIG. Means to circulate the folder from section B to section manager.

In this case, the workflow server 16a sequentially executes the flow 26 in the order set in the work point order relation table 22a. And
The flow definition table 20a, the folder information table 23a, and the folder memory 24a immediately before sending a folder from the user a2 assigned to the work point WP2.
The contents stored in the table are in the state shown in FIG. The current position of the folder information table 23a is the work point WP2.

In this state, when the user a2 sends the folder to the next work point WP3, the current position of the folder information table 23a is updated to the work point WP3, as shown in FIG. Then, it is necessary to send the updated folder to the user of the work point WP3. However, in this work point WP3, in the work point user table 21a, the organization [section B **
[Responsible] is assigned, so the organization [B Section ** In charge]
Send the folder to.

The workflow server 16a sends the folder to the organization of another domain by the following procedure. First, as shown in FIG. 10, in the folder memory 24a, the flow name [Flow A] of the folder information table 23a, the workflow server name of the sender (self), the network address of the own workflow server 16a, and the sender Information on the flow ID, "return tray", and "reception tray" is incorporated as a file 29a for organization delivery.

Next, the reception tray of the organization [section B **] is acquired from the workflow server registration unit 13 of the inter-division management server 15, and as shown in FIG. 11, the workflow server 16b which is the transmission destination of the domain 11b. Organization [section B *
Copy the folder information stored in the folder memory 24a to the [in charge] reception tray. Therefore, as shown in FIG. 11, the contents stored in the forter memory 24b of the workflow server 16b of the domain 11b are as shown in the figure, the workflow server 16 of the domain 11a shown in FIG.
When the content of the folder memory 24a is equal to the content stored in the folder memory 24a, the content stored in the folder memory 24a of the workflow server 16a is deleted.

Workflow server 16 of domain 11b
In step b, a flow executed in this domain 11b is generated from the received folder information. Specifically, the flow of the organization stored in the organization registration unit 18b is specified from the reception tray of the received folder information, and the flow of this organization and the information related to this organization are defined in the flow definition table 21b and the work point order tree relationship. The name of the flow A is set in the table 22b. Further, the initial work point WP1 of the organizational flow is set in the folder information table 22b. Therefore, this flow is a normal flow composed of only the work points belonging to its own domain 11b.

When the workflow generation processing is completed, the workflow server 16b, as shown in FIG. 12, has the sender workflow server name included in the reception folder information stored in the organization delivery file 29b of the folder memory 24b,
The sender flow ID, the return tray, the acceptance tray, the destination workflow server, and the destination flow ID are registered in the inter-workflow server management unit 14.

When the workflow server 16b completes the flow initial setting process of the organization [B manager ** charge], the workflow server 16b performs a normal execution process for this flow set in the flow definition table 20b.

When the flow set in the flow definition table 20b ends normally, the work flow server 16b stores the work flow source server 16a of the sending work flow server 16a stored in the organization sending file 29b of the folder memory 24b as shown in FIG. Acquire the sender's workflow server name and acceptance tray from the information. Then, the folder information in the folder memory 24b is copied (replied) to the acceptance tray of the workflow server 16a of the sender of the domain 11a. In this case, the organization sending file 29b is not sent and only the substance of the folder such as the product file is returned.

Therefore, the folder memory 24a of the workflow server 16a of the domain 11a stores the folder after the flow of the organization of the domain 11b is completed. Further, the workflow server 16a having received the folder information erases the storage information of the inter-workflow server management unit 14 of the inter-department management server 15.

Then, the workflow server 16a sets the current position of the folder information table 23a as the organization [section B **.
In charge] to the next work point WP4 from the work point WP3 corresponding to.

After that, the normal flow execution processing is restarted in accordance with the setting order of the work point order related table 22a of the flow definition table 20a. Therefore, the work flow 26 including the organizational flow 28 of the other domain 11b shown in FIG. 6 input from the flow definition unit 17a of the domain 11a is normally executed and ends.

At the first work point WP1 of the flow of the organization executed in the domain 11b, when the folder is returned to the previous work point WP due to an internal defect, etc., the workflow server 11b copies (sends) the folder to the workflow server 11a of the sender domain 11a by the same process. At that time, the workflow server 11a copies the folder to the return tray instead of the acceptance tray.

When the workflow server 11a receives the folder in the return tray, it deletes the information registered in the inter-workflow server management unit 14 of the inter-department management server 15 and then the folder information table 23 as described above.
The current position of the folder stored in a is returned to the previous state, the folder received from the other workflow server 11b is sent to the user set in the previous work point WP, and the flow operation is performed. To resume.

Furthermore, while the flow is being executed, while the folder is being sent to another workflow server, the execution of the flow on the own workflow server is in a stopped state. During this period, by using the information stored in the inter-workflow management unit 14 of the inter-department management server 15, it is possible to trace which position of which organization the folder is currently located.

For example, when the flow 26 shown in FIG. 6 is input from the flow definition unit 17a of the domain 11a,
From the workflow server 16a to the workflow server 16
When a folder is being sent to b, the following process is performed to retrieve the current folder position from the workflow server 16a that is the sender. During this period, the inter-workflow server management unit 14 stores the organization delivery file 29 sent to the workflow server 16b.
The information of b is stored.

First, the workflow server 16a requests the inter-department management server 15 for the information of the workflow server name of the sender and the recipient of the flow ID. The inter-department management server 15 searches the inter-workflow server management unit 14 with the workflow server name and flow ID of the transmission source, and obtains the workflow server name and flow ID of the transmission destination. Then, the inter-department management server 15 obtains the information of the flow designated by the flow ID from the destination workflow server 16b, and transfers the obtained information to the request source workflow server 16a.

As a result, the sender workflow server 16
In a, the current folder position can be grasped by obtaining the flow information of the destination workflow server 16b obtained from the inter-department management server 15.

In the workflow system configured as described above, in each domain 11a, 11b, the flow of the organization composed of the respective work points of the self domain opened to the other domains 11b, 11a is defined to define the respective organization. In addition to storing the information in the management units 18a and 18b, a part of the workflow server storage unit 13 commonly provided for the domains 11a and 11b and designated addresses such as addresses on the network 12 of the workflow servers 16a and 16b. Have registered.

Accordingly, at the time of creating a flow for the work generated by the operator in the flow definition units 17a and 17b of the domains 11a and 11b, not only the work points 2a and 2b belonging to their own domains 11a and 11b, but also the work points 2a and 2b, respectively. By incorporating the organizations of the other domains 11b and 11a into this work flow, it is possible to easily assign the work to the work points 2b and 2a belonging to the other domains 11b and 11a.

As a result, without increasing the work points 2a and the persons in charge registered in the workflow servers 16a and 16b of the domains 11a and 11b, and in the domains 11a and 11b, the self domains 11a and 11b are registered.
The types and scales of jobs handled by the domains 11a and 11b can be expanded while maintaining the state in which each flow configured only with the work points 2a and 2b belonging to b can be independently executed.

Further, since the workflow server-to-workflow server management unit 14 that can be accessed in common is provided, even when the work point of the flow being executed is moved to the other domain 11b by the function of "organization", the folder You can easily grasp the current position and surely grasp the progress status of the flow when necessary.

FIG. 14 is a block diagram showing the schematic arrangement of a workflow system according to another embodiment of the present invention.
The same parts as those of the embodiment system shown in FIG. 1 are designated by the same reference numerals. Therefore, detailed description of the overlapping portions will be omitted.

In the system of this embodiment, the workflow servers 16a and 16b of the domains 11a and 11b, respectively.
The flow definition tables 20a and 20b, the folder information tables 23a and 23b, the folder memory 24a,
In addition to 24b and user files 25a and 25b, backup memories 30a and 30b are provided.

Each of the backup memories 30a, 30
In b, the same storage content as the workflow server registration unit 13 is stored for backup. Then, if the workflow server registration unit 13 does not operate normally due to some reason and it becomes necessary to transmit the folder information from the workflow server 16a to the other workflow server 16b, instead of the workflow server registration unit 13 , The workflow server 16b for transmitting folder information from the backup memory 30a
The folder information can be transmitted by reading the reception tray on the side and copying the folder information to this reception tray. Therefore, even if the inter-department management server 15 does not operate normally, the flow can be normally executed by using the "organization" between the domains 11a and 11b.

[0073]

As described above, in the workflow system of the present invention, the flow of the organization defined only by the work points of its own domain, which is open to other domains, is defined. There is a management server that manages flows that span each domain. Therefore, even if you create a flow that incorporates a work to be executed in another domain into a part of the work generated in your own domain, you can efficiently execute the work flow in each domain, and the type of work handled by this system And the scale can be greatly expanded, and each task can be performed efficiently.

Further, even if the flow is being executed in another domain, the progress status of this flow can be easily grasped. Furthermore, since the storage contents of the workflow server registration unit are stored and held in the backup memory, the flow can be executed as normally as possible even when an abnormality occurs, and the reliability of the entire system can be improved.

[Brief description of drawings]

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

FIG. 2 is a diagram showing a general flow composed only of work points in the same domain input to the system of the embodiment.

FIG. 3 is a diagram showing stored contents of a workflow server in the system of the embodiment.

FIG. 4 is a diagram showing an organization flow definition procedure and a registration procedure in the system of the embodiment.

FIG. 5 is a diagram showing a user table formed in each workflow server in the system of the embodiment.

FIG. 6 is a diagram showing a flow in which an organizational flow input to the system of the embodiment is incorporated.

FIG. 7 is a diagram showing an execution order of flows including an organizational flow in the system of the embodiment.

FIG. 8 is a diagram showing the stored contents of one workflow server immediately after the start of the flow (WP1) in the system of the embodiment.

FIG. 9 is a diagram showing the stored contents of one workflow server when the flow has progressed to a fixed position (WP2).

FIG. 10 is a diagram showing a state in which an organization delivery file has been created in the workflow server when the flow proceeds to the next position (WP3).

FIG. 11 is a diagram showing a state in which the organization sending file is sent to the other workflow server.

FIG. 12 is a diagram showing a state in which the contents of the reception folder in the other domain are set in the inter-workflow server management unit.

FIG. 13 is a diagram showing a state in which the flow of the organization ends in the other domain and the folder is returned to the original domain.

FIG. 14 is a block diagram showing a schematic configuration of a workflow system according to another embodiment of the present invention.

FIG. 15 is a schematic configuration diagram of a conventional workflow system.

FIG. 16 is a diagram showing a flow composed only of work points belonging to the same domain.

[Explanation of symbols]

11a, 11b ... Domain, 12 ... Network, 13
... workflow server management unit, 14 ... workflow server management unit, 15 ... division management server, 16a, 16b
... Workflow server, 17, 17b ... Flow definition unit,
18a, 18b ... Organization management section, 19, 26 ... Flow, 2
0a, 20b ... Flow definition table, 21a, 21b ...
Work point user table, 22a. 22b ... Workpoint order relation table, 23a, 23b ... Folder information table, 24a, 24b ... Folder memory,
25a, 25b ... User table, 28 ... Organization flow, 29a, 29b ... Organization sending file, 30a, 3
0b ... Memory for backup

Claims (3)

[Claims] 1. Each work point belonging to each domain is registered, each work generated in each domain is divided into a plurality of work points, and the execution order of each work point is defined by a flow, so that each domain is defined. In a workflow system that performs execution management of each flow and folder management of each execution stage in each workflow server provided in, each domain is provided in each domain, and each domain is a self-domain published to another domain. An organization management unit that stores the flow of an organization configured by each work point to which it belongs, a workflow server that stores a plurality of organization information including the domain to which each organization belongs and specification information that specifies a workflow server of each domain The registration unit and the workflow server that is provided in each of the workflow servers described above When the organization is detected, the domain to which the relevant organization belongs is read from the workflow server registration unit, and folder information in which the information of the relevant organization is added to the folder at the current execution stage is transmitted to the workflow server of the read belonging domain. An information transmitting unit, which is provided in each of the workflow servers and, when receiving the folder information, searches its own organization management unit using the information of the organization included in the corresponding folder information to generate and execute the flow of the corresponding organization. A workflow system comprising: an organization flow generation and execution unit that performs the above; and a folder information reply unit that returns folder information including a folder at the stage of ending execution of the flow to the workflow server that is the transmission source. 2. A workflow server that receives the folder information, an inter-workflow server management unit in which the received folder information is written, and a folder position tracking provided in each of the workflow servers and input after the folder information is transmitted. 3. A folder position tracking means for detecting the current folder position from the workflow server of the folder information transmission destination via the inter-workflow server management unit in response to a command.
The described workflow system. 3. Each of the workflow servers is provided,
A backup memory that stores and retains the same storage content of the workflow server registration unit, and a transmission backup unit that specifies the destination workflow server of the folder information based on the storage content of the backup memory when the workflow server registration unit is abnormal The workflow system according to claim 1, further comprising: