Workflow management device and workflow management method

Abstract

To manage multiple kinds of interlocks, in workflow within an organization.SOLUTION: A workflow management device of the present invention comprises: an input / output processing unit which receives workflow information which is workflow from proposal to approval of a document, and interlock information which previously sets whether or not to interlock operation to the document; and a workflow management unit which accepts the operation to the document, during progress of the workflow based on the workflow information, refers to the interlock information, and determines whether or not to interlock the accepted operation.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a workflow management device and a workflow management method. [Background technology]

[0002] Recently, it has become common for documents to be approved by computers within an organization. The workflow device of Patent Document 1 circulates a document proposed by an applicant to multiple approvers according to a preset approval path. The device sets a certain point on the approval path as a stop point. When the workflow has progressed to the stop point, the device temporarily stops the workflow at the stop point. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2023-28542 Summary of the Invention [Problem to be solved by the invention]

[0004] In reality, many people involved in a document are involved in the document until it is finally approved within an organization. Naturally, not all people involved in the document can be equally involved. The types of operations that can be performed on a document (modification, viewing, etc.) vary depending on the content of the document and the roles of the people involved. This necessitates a mechanism (interlock) that sets in advance the operations that a certain person cannot perform, and prohibits that person from performing those operations when that person attempts to perform them. Without this mechanism, business slowdowns and accidents often occur as unexpected people view and modify the document before it is finally approved.

[0005] The workflow device of Patent Document 1 stops the workflow immediately after a predetermined approver approves a document, so that, for example, a contract is not inadvertently leaked to an external organization. However, the workflow device of Patent Document 1 focuses on stopping the workflow and does not take interlocks into consideration. Therefore, an object of the present invention is to manage multiple types of interlocks in a workflow within an organization. [Means for solving the problem]

[0006] The workflow management device of the present invention is characterized in that it comprises an input / output processing unit that receives workflow information, which is a workflow from drafting a document to its approval, and interlock information that sets in advance whether or not to interlock operations on the document, and a workflow management unit that receives operations on the document while the workflow based on the workflow information is in progress, refers to the interlock information, and determines whether or not to interlock the received operations. Effect of the Invention

[0007] According to the present invention, a plurality of types of interlocks can be managed in the workflow within an organization. [Brief description of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating a configuration of a workflow management device. [Diagram 2] 1 is an example of workflow information. [Diagram 3] 11 is an example of interlock information. [Figure 4] 13 is an example of progress information. [Diagram 5] 13 is an example of affiliation information. [Figure 6] 13 is a flowchart of a document circulation process. [Figure 7] 13 is a flowchart of an interlock process procedure. [Figure 8]13 is a flowchart of a workflow participation process; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention (referred to as "the present embodiment") will be described in detail with reference to the drawings and the like. The present embodiment is an example of document approval in a general company. However, the present invention is also applicable to cases where a document is finally approved with the involvement of multiple people in non-company government offices, schools, medical institutions, etc. Furthermore, the present invention is generally applicable to cases where records of business activities by multiple people are stored in a computer area, even if nothing specifically named a "document" is created.

[0010] (term) A user is a person who is permitted to access the workflow management device. In many cases, users belong to the same organization and have a hierarchical relationship (superior-subordinate relationship) with other users.

[0011] A workflow is a set of predefined rules for the order in which multiple users perform tasks. In the case of office work, tasks are realized through a flow of document drafting and approval. In this case, the workflow is the order in which documents are circulated among multiple users. The term "circulating" refers to sending the document to the next approver by attaching it to an e-mail or the like. Alternatively, the term "circulating" may refer to storing the document in a specific storage area of ​​the workflow management device and sending an e-mail to the next approver with an instruction to access the document via a network or the like.

[0012] A document is, for example, a file in which a business document such as a request for approval, minutes, contract, specification, design document, etc. is digitized. A document includes any one of character strings, numerical values, voice, music, and images, or a combination of these. For the sake of simplicity, in this embodiment, documents and workflows correspond one-to-one.

[0013] An operation is an action that a user takes on a document. Types of operations include, for example, modifying a document, copying a document, viewing a document, etc. (described in detail below). Other types of operations include filtering of voice and music (removing high frequency parts, etc.), changing pixel values ​​of an image (changing brightness), etc. In this manner, operations correspond to general computer functions. In this embodiment, operations are a separate concept from each workflow process, such as proposal and approval, which will be described later.

[0014] Drafting is when a user creates a document from scratch. Such a user is also called an originator. There is usually one originator for a document. Approval is when a user approves the contents of a document. Such a user is also called an approver. Approvers for a document are preset from among users other than the document's originator. Usually, there are multiple approvers for one document. When all preset approvers have approved a document, the document is considered to have been approved organizationally.

[0015] The approver can also forward the document to the next approver after adding instructions, comments, etc. that do not contradict the contents of the document. The approver can also modify the contents of the document himself / herself and forward the modified document to the next approver, unless specifically prohibited. The processes for approval include return and rejection.

[0016] A return is when an approver instructs an originator to revise a document, and the approver decides to which approver (the same approver or another approver) the revised document will be sent again. The originator who is instructed to revise the document may be someone other than the originator of the document. A rejection occurs when an approver stops the workflow related to a document.

[0017] An interlock is the prohibition of operations by a user. Interlocks are set in advance for each period, type of operation, and user. A typical example of a period is "before the document is approved." A typical example of a type of prohibited operation is "modifying the document."

[0018] (Workflow management device) 1 is a diagram showing the configuration of a workflow management device 1. The workflow management device 1 is a general computer, and includes a central control device 11, an input device 12 such as a mouse and a keyboard, an output device 13 such as a display, a main memory device 14, an auxiliary memory device 15, and a communication device 16.

[0019] The input / output processing unit 21 and workflow management unit 22 in the main memory device 14 are programs. In the following explanation, when an entity is described as "XX unit", it means that the central control device 11 reads the program from the auxiliary memory device 15 to the main memory device 14 and realizes the function of the program. The auxiliary memory device 15 stores workflow information 31, interlock information 32, progress information 33, and affiliation information 34 (described in detail later). The auxiliary memory device 15 may be configured independently as a separate housing.

[0020] There are multiple tenants 2. A tenant 2 is an organization such as a business entity that can access one workflow management device 1. Each tenant 2 exclusively uses an area of ​​the workflow management device 1 having a different physical address or logical address. In other words, security is maintained between the tenants 2.

[0021] Each of the tenants 2 has a plurality of user terminal devices 3. Each of the user terminal devices 3 is operated by an employee (user) belonging to the tenant 2. Each of the user terminal devices 3 is connected to the workflow management device 1 via a network 4. The auxiliary storage device 15 stores documents 5. The users access the workflow management device 1 via the user terminal devices 3 and perform operations such as viewing and modifying the documents 5.

[0022] (Workflow information) 2 is an example of the workflow information 31. In the workflow information 31, a drafter ID is stored in a drafter column 102, an approver ID is stored in an approver column 103, and an activation ID is stored in an activation ID 104 in association with a flow ID stored in a flow ID column 101.

[0023] The flow ID in the flow ID column 101 is an identifier that uniquely identifies a workflow. In this embodiment, the flow ID also uniquely identifies the document 5 that is drafted and approved in that workflow. The drafter ID in the drafter column 102 is an identifier that uniquely identifies the drafter.

[0024] The approver ID in the approver column 103 is an identifier that uniquely identifies an approver. "1st", "2nd", "3rd", "4th", ... are the approval order. There are multiple approvers for one workflow, and each approver is assigned an approval order. Multiple approver IDs may correspond to one approval order. "[ ]" here indicates that multiple approvers are overlapping in the approval order, that is, approval by all approvers is required. "( )" here indicates that multiple approvers are selective in the approval order, that is, approval by any one approver is sufficient. A thick frame surrounding an initiator ID or approver ID indicates that the initiator or approver is currently in the process of drafting or approving document 5.

[0025] The activation ID in the activation ID column 104 will be described later.

[0026] From record 105 in FIG. · Draft author P001 drafts document 5. There are four approvers for Document 5. The document 5 is circulated in the following order of approval: Approver P002 → Approver P003 → Approver P004 → Approver P005, and then approved. · Currently, Document 5 is being approved by Approver P004.

[0027] From record 106 in FIG. · Draft author P011 drafts document 5. There are four approvers for Document 5. The document 5 is circulated to Approver P012, Approver P013, Approver P014, and Approver P015 in this order and approved. Of these, Document 5 is circulated to Approver P012 and Approver P013 at the same time. After both approve, Document 5 is circulated to Approver P014. Currently, Document 5 is being drafted by drafter P011.

[0028] From record 107 in FIG. 2, the following can be seen. · Drafter P021 drafts Document 5. There are four approvers for Document 5. The document 5 is circulated in the approval order of Approver P022 → Approver P023 or Approver P024 → Approver P025 and approved. Of these, Document 5 is circulated to Approver P023 and Approver P024 at the same time. After either of them approves Document 5, Document 5 is circulated to Approver P025. · Currently, Document 5 is being approved by Approver P023. A notice that “no approval required” is sent to approver 024.

[0029] (Interlock information) 3 is an example of the interlock information 32. In the interlock information 32, a period is stored in a period column 112, an operation is stored in an operation column 113, and an applicable user ID is stored in an applicable user column, in association with a flow ID stored in a flow ID column 111.

[0030] The flow IDs in the flow ID column 111 are the same as those in FIG. The period in the period column 112 is the timing for performing the interlock. The operations in the operation column 113 are operations that may be subject to interlock. Examples of the operations include the following:

[0031] View: View Document 5. · Modification: Changing the contents of Document 5 without special instructions (including partial deletion and addition). ·Copying: Copying a document 5 · Distributing to others: Distributing Document 5 to users other than those set in the flowchart. ·Comment: Add a note without changing the content of Document 5. · Linking: Pasting the URL of reference information on the Internet into Document 5. · Upload: Uploading Document 5 onto the Internet.

[0032] The applicable user ID in the applicable user column 114 is an identifier that uniquely identifies the user to whom the interlock is applied.

[0033] For example, the following can be seen from record 115 in FIG. In Workflow W01, approver P002 and approver P003 are prohibited from modifying document 5 during the period before approval (before approver P005 approves). In workflow W01, approver P003 is prohibited from viewing document 5 during the period before approver P002 approves it.

[0034] As is clear from the above, the interlock information 32 presets whether or not operations on the document 5 are to be interlocked.

[0035] (Progress information) 4 is an example of the progress information 33. In the progress information 33, a time is stored in a time column 122, a user ID is stored in a user column 123, a process is stored in a process column 124, and an interlock flag is stored in an interlock column 125 in association with a flow ID stored in a flow ID column 121.

[0036] The flow ID in the flow ID column 121 is the same as the flow ID in FIG. The time in the time column 122 is the time when the user executed each process of the workflow or the time when the user performed an interlocked operation. The user in the user column 123 is an identifier that uniquely identifies the initiator or approver. Here, "( )" indicates that the operation by that user is interlocked. The processes in the process column 124 are each workflow process by the user. In Fig. 4, "draft", "approval", "modification", "return" and "approval (decision)" are shown as examples of processes, but other processes may be used. Note that "modification" here refers to a process (re-draft) performed by another user based on instructions from a user, and is different from "modification" as an operation performed by a user without such special instructions. The interlock flag in the interlock column 125 indicates an operation that is subject to an interlock.

[0037] From record 126 in FIG. On August 10, 2023, in Workflow W01, after Proposer P001 had proposed a document, but before Approver P002 had approved it, Approver P003 attempted to view Document 5. However, the approval by P003 was interlocked. The gist of the interlock is that "P003 is not allowed to view Document 5 except when he / she approves it." The basis for this interlock is record 115 in Figure 3. After approver P005 returns document 5 to originator P001, originator P001 modifies document 5.

[0038] From record 127 in FIG. On August 20, 2023, in Workflow W01, after Proposer P001 had proposed the document, Approver P003 attempted to modify Document 5 before Approver P005 approved it. However, the modifications made by approver P003 were interlocked. The basis for this interlock is record 115 in Figure 3. After approver P005 returns document 5 to approver P004, approver P004 modifies document 5.

[0039] (Affiliation information) 5 is an example of the affiliation information 34. In the affiliation information 34, a tenant name is stored in a tenant name field 132, a user ID is stored in a user field 133, an email address is stored in an email address field 134, and a flow ID is stored in a flow ID field 135 in association with a tenant ID stored in a tenant ID field 131.

[0040] The tenant ID in the tenant ID column 131 is an identifier that uniquely identifies the tenant 2 (the organization to which the user belongs). The tenant name in the tenant name column 132 is the name of the tenant 2. The user ID in the user column 133 is the same as the user ID in FIG. The email address in the email address column 134 is the email address of the user terminal device 3 operated by the user. The flow ID in the flow ID column 135 is the same as the flow ID in FIG.

[0041] The following can be seen from Figure 5: The workflow management device 1 is used by at least Tenant A, Tenant B, and Tenant C. Each tenant has multiple users. · The workflows that need to be managed differ for each tenant.

[0042] (Document Circulation Processing Procedure) FIG. 6 is a flowchart of a document circulation process. In step S201, the input / output processing unit 21 of the workflow management device 1 accepts the affiliation information 34 (FIG. 5). Specifically, first, the input / output processing unit 21 accepts a tenant name, a user name, and an email address from any user terminal device 3 belonging to a certain tenant 2. Secondly, the input / output processing unit 21 assigns a tenant ID and a user ID, and then creates a record of the affiliation information 34. At this stage, the flow ID column 135 of the affiliation information 34 is blank.

[0043] In step S202, the input / output processing unit 21 receives workflow information 31 (FIG. 2). Specifically, first, the input / output processing unit 21 receives a workflow from any user terminal device 3 belonging to the tenant 2. The workflow may be in any form as long as it describes, for each document 5 to be drafted, the name of a drafter, the names of multiple approvers, the approval order, and the relationship between superimposition and selection. Secondly, the input / output processing unit 21 creates a record of the workflow information 31 based on the accepted workflow. At this time, the input / output processing unit 21 assigns a flow ID and an activation ID (described in detail later) and stores them in the record. The input / output processing unit 21 stores the flow ID in the affiliation information 34. The input / output processing unit 21 may receive, from the user terminal device 3, already completed workflow information 31 having a format shown in FIG.

[0044] In step S203, the input / output processing unit 21 accepts the interlock information 32 (FIG. 3). Specifically, first, the input / output processing unit 21 accepts a flow ID, an interlock period related to the workflow, an operation, and an applicable user name from any user terminal device 3 belonging to the tenant 2. Secondly, the input / output processor 21 creates a record of the interlock information 32 based on these pieces of information. The input / output processing unit 21 may receive, from the user terminal device 3, already completed interlock information 32 having a format shown in FIG.

[0045] In step S204, the workflow management unit 22 of the workflow management device 1 accepts the drafting of the document 5. Specifically, first, the workflow management unit 22 accepts any document 5 from the user terminal device 3 of the drafter of the tenant 2. The document 5 here is, for example, a written proposal with contents already filled in (drafted). In accordance with the workflow, multiple approvers will approve the document 5 in a predetermined approval order.

[0046] In step S205, the workflow management unit 22 records this in the progress information 33 (FIG. 4). Specifically, the workflow management unit 22 records in the progress information 33 that, for example, in workflow "W01", the initiator "P001" has "proposed" the workflow. The workflow management unit 22 surrounds "P001" in the initiator column 102 in the record 105 of the workflow information 31 (FIG. 2) with a thick frame during the period when the initiator P001 is in the proposal state.

[0047] In step S206, the workflow management unit 22 routes the document 5 to the approver. Specifically, the workflow management unit 22 routes the document 5 to the user terminal device 3 of the first approver based on the workflow information 31. During the period when the document is being approved by the first drafter, the workflow management unit 22 surrounds, for example, "P002" in the approver column 103 of the record 105 of the workflow information 31 (FIG. 2) with a thick line frame. During this period, the workflow management unit 22 removes the thick line frame surrounding "P001."

[0048] In step S207, the input / output processing unit 21 prompts the next approver to approve the document 5. Specifically, the input / output processing unit 21 displays, on the user terminal device 3 of the next approver, a message prompting the next approver to approve the forwarded document 5.

[0049] In step S208, the workflow management unit 22 judges whether the approver has approved the document 5. To simplify the explanation, it is assumed that the approver inputs either "approval" or "rejection" as the result to his / her user terminal device 3. If the result is "approval" (step S208 "YES"), the workflow management unit 22 proceeds to step S211, and if the result is "rejection" (step S208 "NO"), the workflow management unit 22 proceeds to step S209.

[0050] In step S209, the input / output processor 21 accepts a destination for return. Specifically, the input / output processor 21 accepts an instruction from the user terminal device 3 of the approver who instructed "return", as to which user the document 5 should be returned to be revised. In principle, the document 5 is returned to the drafter.

[0051] In step S210, the workflow management unit 22 records in the progress information 33 (FIG. 4). Specifically, first, the workflow management unit 22 records in the progress information 33, for example, that in the workflow "W01", the approver PXXX has sent the workflow back to the initiator P001. Second, the workflow management unit 22 routes the document 5 to be revised to the user terminal device 3 of the drafter who is to revise the document 5. After that, the workflow management unit 22 returns to step S204. In step S204, the workflow management unit 22 receives the revised document 5 from the user terminal device 3 of the drafter.

[0052] Although not shown in Fig. 6, the workflow management unit 22 may also send the document 5 to be revised to the approver who initially approved the document. In this case, the approver who instructs the revision is different from the approver who initially approved the revision.

[0053] In step S211, the workflow management unit 22 routes the document 5 to the next approver. During the period when the document is being approved by the next drafter, the workflow management unit 22 surrounds, for example, "P003" in the approver column 103 of the record 105 of the workflow information 31 (FIG. 2) with a thick frame. During this period, the workflow management unit 22 removes the thick frame surrounding "P002".

[0054] In step S212, the workflow management unit 22 repeats the processes of steps S204 to S211 as many times as necessary (for the next number of approvers).

[0055] In step S213, the workflow management unit 22 judges whether the final approver has approved the request. If the final approver has approved the request (step S213 "YES"), the workflow management unit 22 proceeds to step S214, and otherwise (step S213 "NO"), the workflow management unit 22 returns to step S212.

[0056] In step S214, the workflow management unit 22 records in the progress information 33 (FIG. 4). Specifically, the workflow management unit 22 records in the progress information 33 that the last approver "P005" has "approved (decided)" in the workflow "W01", for example. Thereafter, the document circulation processing procedure is terminated.

[0057] (Interlock procedure) FIG. 7 is a flowchart of the interlock process procedure. In step S301, the workflow management unit 22 of the workflow management device 1 starts a workflow. Specifically, the workflow management unit 22 accepts a proposal of a document 5 from the user terminal device 3 of a drafter in an arbitrary workflow.

[0058] In step S302, the workflow management unit 22 judges whether an operation has been accepted. The workflow management unit 22 constantly monitors whether the users perform operations such as viewing and editing on the document 5 from their respective positions via the user terminal device 3. If the workflow management unit 22 accepts such an operation (step S302 "YES"), it proceeds to step S303, and otherwise (step S302 "NO") it remains in standby.

[0059] In step S303, the workflow management unit 22 refers to the interlock information 32 (FIG. 3). If the workflow management unit 22 receives an operation of "correction" for document 5 from approver "P003" in the workflow "W01" during the period before approval, the operation should be interlocked.

[0060] In step S304, the workflow management unit 22 judges whether or not interlocking is required. Specifically, if the accepted operation should be interlocked (step S304 "YES"), the workflow management unit 22 proceeds to step S305, and otherwise (step S304 "NO"), the workflow management unit 22 returns to step S302.

[0061] In step S305, the workflow management unit 22 executes an interlock. Specifically, the workflow management unit 22 invalidates the operation accepted in step S302, and displays a message that "the accepted operation has been interlocked" on the user terminal device 3 of the user who performed the operation.

[0062] In step S306, the workflow management unit 22 records in the progress information 33 (FIG. 4). Specifically, the workflow management unit 22 records in the progress information 33 that, for example, in the workflow "W01", the user "PXXX" has been interlocked from "modifying" the document 5.

[0063] In step S307, the workflow management unit 22 ends the workflow. Specifically, the workflow management unit 22 accepts the last approver's approval (decision) of the document 5 from the last approver's user terminal device 3. Then, the interlock processing procedure ends.

[0064] (Tenant Management and Activation ID) The workflow management unit 22 divides the workflow information 31 (Fig. 2), interlock information 32 (Fig. 3), progress information 33 (Fig. 4), and documents 5 for each tenant 2 (organization to which the user belongs). The auxiliary storage device 15 is divided, for example, into area A that stores such information related to tenant "Company A," area B that stores such information related to tenant "Company B," ... Areas A, B, ... are mutually exclusive areas with different physical addresses or logical addresses. The workflow management unit 22 assigns an activation ID to each tenant 2. The activation ID is an identifier that uniquely identifies such an exclusive area.

[0065] Usually, there is a one-to-one correspondence between a tenant 2 and an exclusive area for that tenant. In other words, in most cases, the tenant ID and the activation ID are synonymous. However, since there are cases (cloud) where multiple exclusive areas correspond to one tenant 2, the two are distinguished.

[0066] This activation ID is assigned to all operations performed on the workflow management device 1 from a user terminal device 3 belonging to a certain tenant 2. The input / output processing unit 21 and workflow management unit 22 of the workflow management device 1 allow access only to the exclusive area specified by the activation ID, and ignore, reject, or invalidate access to other exclusive areas. In this way, the activation ID creates a sense of use as if a workflow management device 1 exists for each tenant 2, and guarantees security between multiple tenants 2.

[0067] The workflow management unit 22 may further divide an exclusive area for a certain tenant 2 for each workflow, assign an activation ID to a combination of the tenant 2 and the workflow, and associate the activation ID with the further divided exclusive area. The activation ID of the workflow information 31 (FIG. 2) is such an example.

[0068] (Workflow participation processing procedure) FIG. 8 is a flowchart of a workflow participation process. In step S401, the workflow management unit 22 of the workflow management device 1 receives a request for issuing an activation ID. Specifically, the workflow management unit 22 receives an issuance request for issuing an activation ID from any user terminal device 3. At this stage, it is assumed that the workflow management unit 22 already knows the tenant ID of the tenant 2 to which the user terminal device 3 belongs, and the flow ID of the workflow registered by the tenant 2.

[0069] In step S402, the workflow management unit 22 issues an activation ID. Specifically, the workflow management unit 22 issues an activation ID for a combination of a tenant ID and a flow ID, and transmits the activation ID to the user terminal device 3 of the proposer. The activation ID may be encrypted, may have an expiration date, or may have a password that can be changed at any time. After that, the user terminal device 3 of the tenant 2 to which the proposer belongs will share the issued one or more activation IDs.

[0070] The workflow management unit 22 sets an exclusive area of ​​the workflow management device 1 for each activation ID. From the viewpoint of effective use of resources, handling of increasing data, etc., the workflow management unit 22 may sever the association between an activation ID and a certain exclusive area and associate the activation ID with another exclusive area.

[0071] In step S403, the workflow management unit 22 registers the activation ID. Specifically, the workflow management unit 22 stores the issued activation ID in the workflow information 31 (FIG. 2).

[0072] In step S404, the workflow management unit 22 judges whether or not an access request has been received from a user. Specifically, when the workflow management unit 22 receives an access request from any user terminal device 3 to access the workflow management device 1 (step S404 "YES"), the workflow management unit 22 proceeds to step S405. In other cases (step S404 "NO"), the workflow management unit 22 waits as is.

[0073] In step S405, the workflow management unit 22 accepts an activation ID. Specifically, the workflow management unit 22 prompts the user terminal device 3 that has transmitted the access request to input an activation ID, and accepts this from the user terminal device 3.

[0074] In step S406, the workflow management unit 22 determines whether or not the access should be permitted. Specifically, the workflow management unit 22 determines whether or not all of the following conditions are satisfied:

[0075] The combination of the tenant ID and flow ID specified by the received activation ID is registered in the same record of the affiliation information 34 (Figure 5). The accepted activation ID and the flow ID that the activation ID identifies are registered in the same record of the workflow information 31 (FIG. 2). A record including the flow ID specified by the accepted activation ID is registered in the interlock information 32 (Figure 3). The record of the workflow information 31 including the accepted activation ID includes the initiator ID or approver ID of the user who sent the access request.

[0076] If all the conditions are satisfied (step S406 "YES"), the workflow management unit 22 proceeds to step S407, otherwise (step S406 "NO"), the workflow management unit 22 proceeds to step S408.

[0077] In step S407, the workflow management unit 22 permits access. Specifically, the workflow management unit 22 permits the user terminal device 3 that sent the access request to access the exclusive area specified by the activation ID accepted in step S405. Thereafter, the workflow participation processing procedure ends. "Access" means performing an operation on the document 5 stored in the exclusive area, or performing each process of the workflow in the exclusive area.

[0078] In step S408, the workflow management unit 22 denies the access. Specifically, the workflow management unit 22 denies the user terminal device 3 that sent the access request from accessing any of the exclusive areas. Then, the workflow participation processing procedure is terminated.

[0079] (Effects of the embodiment) The workflow management device of this embodiment provides the following effects. (1) The workflow management device can determine whether or not to interlock an operation on a document. (2) The workflow management device can set whether or not to enable interlock for each type of operation and for each user. (3) The workflow management device can set whether or not to perform interlock for each period. (4) The workflow management device can interlock viewing or modification of a document. (5) The workflow management device can inform the user that the interlock has occurred. (6) The workflow management device can be used by multiple organizations while ensuring security.

[0080] The present invention is not limited to the above-described embodiment, but includes various modified examples. For example, the above-described embodiment has been described in detail to easily explain the present invention, and is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0081] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD. In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0082] 1 Workflow management device 2 Tenant 3. User terminal equipment 4. Network 5 Documents 11 Central control unit 12 Input Devices 13 Output Devices 14 Main memory 15 Auxiliary storage 16 Communication Equipment 21 Input / Output Processing Unit 22 Workflow Management Department 31 Workflow Information 32 Interlock Information 33 Progress information 34 Affiliation Information

Claims

1. an input / output processing unit that receives workflow information, which is a workflow from document drafting to approval, and interlock information that pre-sets whether or not operations on the document are to be interlocked; accepting an operation on the document during the progress of the workflow based on the workflow information; a workflow management unit that refers to the interlock information and determines whether or not to interlock the received operation; A workflow management device comprising:

2. The interlock information includes: Whether or not to interlock is set for each type of operation and for each user.

2. The workflow management device according to claim 1,

3. The interlock information includes: Whether or not to interlock is set for each period.

3. The workflow management device according to claim 2.

4. The interlock information includes: The interlocking operation is set to view or modify the document.

4. The workflow management device according to claim 3.

5. The workflow management unit When the operation is interlocked, a message is displayed to a user who has requested the operation that the operation has been interlocked; 5. The workflow management device according to claim 4.

6. a storage unit for storing the workflow information, the interlock information, and the document in different areas divided for each organization to which a user belongs; The workflow management unit issuing to said user an identifier that allows access only to an area partitioned for the organization to which said user belongs; 2. The workflow management device according to claim 1,

7. The input / output processing unit of the workflow management device includes: receiving workflow information, which is a workflow from document drafting to approval, and interlock information, which pre-sets whether or not operations on the document are to be interlocked; The workflow management unit of the workflow management device includes: accepting an operation on the document during the progress of the workflow based on the workflow information; referring to the interlock information to determine whether or not to interlock the accepted operation; A workflow management method comprising:

Images