JP6012504B2 - Workflow management system, workflow management method and program - Google Patents

Description

  The present invention relates to a workflow management system, a workflow management method, and a program. The present invention particularly relates to a workflow system corresponding to a role.

  Many companies have introduced workflows for the purpose of digitizing and improving the efficiency of various applications. In the workflow operation, it is necessary to manage the approval route of the workflow and the access authority of the approved workflow document.

  Conventionally, there is a system that sets an approval route based on role information associated with user information instead of user information (see, for example, Patent Documents 1 to 4).

JP 2007-179251 A JP 2006-79403 A JP 2006-72632 A JP 2000-132625 A

  In the conventional system, if the user information linked to the role information is changed, the approval route can be changed in a batch, but the access authority of the approved workflow document is not set by the role information, so it must be changed individually. However, there was a problem that the load of change work was high. Also, when changing user information associated with role information or deleting role information, there is a problem that it is difficult to grasp the effect of the change / deletion on each workflow.

  An object of the present invention is to utilize a role not only for setting an approval route of a workflow, but also for setting access authority of an approved workflow document.

A workflow management system according to an aspect of the present invention includes:
A workflow data storage unit that stores, in a storage device, data including at least one of a document and information indicating the progress of approval for each workflow in which a user approves a document along an approval path including at least one approval step. When,
A role definition storage unit that stores, in a storage device, a role definition that defines a correspondence relationship between a user and a role that classifies the role of the user;
An approval authority definition storage unit that stores in the storage device an approval authority definition that defines a correspondence relationship between the approval step of the workflow approval route and the role that is authorized to approve the document in the approval step;
An access authority definition storage unit that stores, in a storage device, an access authority definition that defines a correspondence relationship between a workflow and a role that is authorized to access workflow data;
An approval request receiving unit that receives a request from a user terminal that transmits a request for approving a document by specifying an approval step of the workflow approval route;
The role corresponding to the user of the transmission source of the request received by the approval request reception unit is extracted with reference to the role definition stored in the role definition storage unit, and the extracted role is designated by the transmission source. Whether the approval step of the approval route of the corresponding workflow corresponds is determined by referring to the approval authority definition stored in the approval authority definition storage unit. An approval control unit that permits document approval in steps;
An access request receiver that receives a request from a user terminal that transmits a request to access workflow data by specifying a workflow;
The role corresponding to the user of the transmission source of the request received by the access request reception unit is extracted with reference to the role definition stored in the role definition storage unit, and the extracted role is designated by the transmission source. Whether the corresponding workflow is supported is determined by referring to the access authority definition stored in the access authority definition storage unit. If it is determined that the workflow is supported, the user is stored in the workflow data storage unit. And an access control unit that permits access to the data of the workflow.

  According to one aspect of the present invention, a role can be used not only for setting an approval route for a workflow, but also for setting access authority for an approved workflow document.

1 is a block diagram illustrating a configuration of a workflow management system according to a first embodiment. FIG. 3 is a block diagram showing a configuration of a workflow engine, an approval route definition tool, a role definition tool, and a role use status management tool of the workflow management system according to the first embodiment. 4 is a table showing an example of a user / organization database of the workflow management system according to the first embodiment. 4 is a table showing an example of a role database of the workflow management system according to the first embodiment. 4 is a table showing an example of a workflow document database of the workflow management system according to the first embodiment. 6 is a table showing an example of an approval route definition database of the workflow management system according to the first embodiment. 6 is a table showing an example of an approved document authority database of the workflow management system according to the first embodiment. 6 is a table showing an example of a role usage database of the workflow management system according to the first embodiment. 5 is a flowchart showing an example of the operation of the workflow management system according to the first embodiment. 5 is a flowchart showing an example of the operation of the workflow management system according to the first embodiment. 5 is a flowchart showing an example of the operation of the workflow management system according to the first embodiment. 5 is a flowchart showing an example of the operation of the workflow management system according to the first embodiment. 2 is a diagram illustrating an example of a hardware configuration of a workflow management system according to Embodiment 1. FIG.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

Embodiment 1 FIG.
In this embodiment, a role (an authority group based on role information) is used for setting an approval route for a workflow (WF) and setting an access authority for an approved workflow document. The approval route of a plurality of workflows and the access authority of documents can be changed at once by changing only, and the change load is reduced.

  In addition, by collecting and centralizing information on the usage status of roles used in each workflow and making it available from other systems, the scope of impact when deleting and changing roles is clarified, and the role change load is clarified. This will reduce work and prevent work mistakes.

  FIG. 1 is a block diagram showing a configuration of a workflow management system 100 (WF management system) according to the present embodiment.

  In FIG. 1, a workflow management system 100 includes a user / organization database 101 (user / organization DB), a role database 102 (role DB), a workflow document database 103 (WF document DB), an approval route definition database 104 (approval route definition DB). ), Approved document authority database 105 (approved document authority DB), role usage status database 106 (role usage status DB), workflow engine 110 (WF engine), approval route definition tool 120, role definition tool 130, role usage status. A management tool 140 is provided.

  FIG. 2 is a block diagram showing the configuration of the workflow engine 110, the approval route definition tool 120, the role definition tool 130, and the role usage status management tool 140.

  In FIG. 2, the workflow engine 110 includes an approval request receiving unit 111, an approval control unit 112, an access request receiving unit 113, and an access control unit 114.

  The approval route definition tool 120 includes an approval authority management unit 121, an access authority management unit 122, and a list transmission unit 123.

  The role definition tool 130 includes a role management unit 131 and a list transmission unit 132.

  The role usage status management tool 140 includes a usage status management unit 141 and a list transmission unit 142.

  Although not shown in FIGS. 1 and 2, the workflow management system 100 includes hardware such as a processing device, a storage device, an input device, and an output device. The hardware is used by each database of the workflow management system 100 and each part of the workflow engine 110. For example, the processing device is used to perform calculation, processing, reading, writing, and the like of data and information. The storage device is used to store the data and information. The input device is used for inputting the data and information, and the output device is used for outputting the data and information.

  The user / organization database 101 is an example of a user definition storage unit, and stores a user definition that defines a correspondence relationship between a user and an organization to which the user belongs in a storage device.

  An example of the user / organization database 101 is shown in FIG. In this example, there is a user definition that defines a correspondence relationship between a “user ID” (for example, AA123) that uniquely identifies a user (for example, user A) and an “affiliation organization” (for example, the material department of ABC Company). Are stored in the user / organization database 101.

  The role database 102 is an example of a role definition storage unit, and stores a role definition that defines a correspondence relationship between a user and a role in which the role of the user is classified in a storage device.

  Here, an example of the role database 102 is shown in FIG. In this example, “members registered in the role” (for example, AA123 and BB123) indicated by the user ID and “role ID” (for example, role-abcde12345) that uniquely identifies the role (for example, the material officer role). A role definition that defines a correspondence relationship is stored in the role database 102. In addition, you may classify | categorize the role according to charge, such as a material person role and a purchase person role, and the role according to affiliation, such as the manager of the CC section and the person in charge of the CC section, in the column of “role type”, for example. In that case, when displaying or updating the role, it is possible to perform different processing between the role in charge and the role in affiliation.

  The workflow document database 103 is an example of a workflow data storage unit, and stores data including a document in a storage device for each workflow in which a user approves a document along an approval path including at least one approval step. The workflow data may include information indicating the progress of approval in addition to the document or instead of the document.

  An example of the workflow document database 103 is shown in FIG. In this example, each “workflow ID” (for example, wf-abc-00001) that uniquely identifies a workflow (for example, a parts purchase workflow described later) is uniquely identified by a “workflow document ID” (for example, bunsho123). “Workflow document name” (for example, purchase order.txt) for referring to a document to be stored is stored in the workflow document database 103. Instead of the “workflow document name”, the document itself may be directly stored, or the URL (Uniform / Resource / Locator) of the document may be stored.

  The approval route definition database 104 is an example of an approval authority definition storage unit, and an approval authority definition that defines a correspondence relationship between the approval step of the approval route of the workflow and the role that has the authority to approve the document in the approval step. Store in the storage device.

  Here, FIG. 6 shows an example of the approval route definition database 104. In this example, a “workflow ID” (for example, wf-abc-00001) that uniquely identifies a workflow (for example, part purchase workflow) and an “approval step 1” (for example, role-abcde00001) of the workflow indicated by the role ID. ) To “approval step n (=“ number of approval steps of workflow ”)” (for example, role-abcde12345) is stored in the approval route definition database 104.

  The approved document authority database 105 is an example of an access authority definition storage unit, and stores an access authority definition that defines a correspondence relationship between a workflow and a role that is authorized to access workflow data in a storage device. The authority to access workflow data includes not only the authority to access approved documents, but also the authority to access unapproved documents, documents in the process of approval, information indicating the progress of approval, etc. It may be.

  An example of the approved document authority database 105 is shown in FIG. In this example, a “workflow document ID” (for example, bunsho123) that uniquely identifies a workflow document, and an “authorized document access authority” (for example, role-abcde00001, role-abcde00002, and role) indicated by the role ID. An access authority definition that defines a correspondence relationship with -abcde12345) is stored in the approved document authority database 105.

  The role usage status database 106 is an example of a usage status definition storage unit, and stores the usage status definition created by the role usage status management tool 140 in a storage device.

  The usage status management unit 141 of the role usage status management tool 140 refers to the access authority definition stored in the approved document authority database 105, and associates the workflow with the role that has the authority to access the workflow data. The relationship is extracted by the processing device as the usage status of the role. The role usage status management tool 140 creates a usage status definition that defines the extracted usage status and stores it in the role usage status database 106.

  Here, FIG. 8 shows an example of the role usage database 106. In this example, a “workflow ID” (for example, wf-abc-00001 and wf-abc-00002) for uniquely identifying a workflow (for example, a parts purchase workflow and a lease management workflow) and a role (for example, a material person role) ) Is stored in the role usage database 106 to define a corresponding relationship with a “role ID” (for example, role-abcde12345) that uniquely identifies a role.

  The list sending unit 142 of the role usage status management tool 140 selects a role corresponding to the workflow specified from the user's terminal from the usage status definition stored in the role usage status database 106 (the usage status created by the usage status management unit 141). Extracted by the processing device with reference to the situation definition). The list transmission unit 142 transmits the extracted list of roles to the user terminal via a network or the like.

  In addition, the list transmission unit 142 refers to the usage status definition (the usage status definition created by the usage status management unit 141) stored in the role usage status database 106 for the workflow corresponding to the role specified from the user terminal. And extracted by the processing device. The list transmission unit 142 transmits the extracted workflow list to the user terminal via a network or the like.

  The approval request receiving unit 111 of the workflow engine 110 receives a request via a network or the like from a user terminal that transmits a request for approving a document by specifying an approval step of the approval path of the workflow.

  The approval control unit 112 of the workflow engine 110 extracts a role corresponding to the transmission source user of the request received by the approval request receiving unit 111 with reference to the role definition stored in the role database 102 by the processing device. The approval control unit 112 processes whether the approval step of the approval route of the workflow specified by the transmission source corresponds to the extracted role with reference to the approval authority definition stored in the approval route definition database 104. Judge by device. If it is determined that it is compatible, the approval control unit 112 permits the user to approve the document in the approval step.

  Here, in the examples of FIGS. 3 to 8, it is assumed that the terminal of the user A transmits a request for approving the order form by specifying “workflow ID” wf-abc-00001 and “approval step 2”. To do. When the approval request receiving unit 111 receives the request, the approval control unit 112 extracts the “roll ID” role-abcde 12345 of the user A from the role database 102. The approval control unit 112 confirms that the “role ID” role-abcde12345 of the user A corresponds to the “approval step 2” of the workflow (part purchase workflow) of the “workflow ID” wf-abc-00001. In step 104, the user A is permitted to approve the order form in “approval step 2”.

  The access request reception unit 113 of the workflow engine 110 receives a request via a network or the like from a user terminal that transmits a request for accessing the workflow data by specifying the workflow.

  The access control unit 114 of the workflow engine 110 extracts a role corresponding to the transmission source user of the request received by the access request reception unit 113 with reference to the role definition stored in the role database 102 by the processing device. The access control unit 114 determines whether the workflow specified by the transmission source corresponds to the extracted role with reference to the access authority definition stored in the approved document authority database 105 by the processing device. If it is determined that it is compatible, the access control unit 114 allows the user to access the data of the workflow stored in the workflow document database 103.

  Here, in the example of FIGS. 3 to 8, it is assumed that the terminal of the user A transmits a request for accessing the order form by designating “workflow ID” wf-abc-00001. When the access request receiving unit 113 receives the request, the access control unit 114 extracts the “role ID” role-abcde 12345 of the user A from the role database 102. The access control unit 114 extracts the “workflow document ID” bunsho123 of the document of the workflow (part purchase workflow) of “workflow ID” wf-abc-00001 from the workflow document database 103. The access control unit 114 confirms in the approved document authority database 105 that the “workflow document ID” bunsho123 of the part purchase workflow corresponds to the “role ID” role-abcde12345 of the user A, and the user A Allows access to the order form for ID “bunsho123”.

  The approval authority management unit 121 of the approval route definition tool 120 receives a request via a network or the like from a user terminal that transmits a request for creating an approval authority definition for a new workflow. The approval authority management unit 121 creates an approval authority definition according to the received request and stores it in the approval route definition database 104.

  Further, the approval authority management unit 121 receives a request via a network or the like from a user terminal that transmits a request to update (change or delete) the approval authority definition by designating an (existing) workflow. The approval authority management unit 121 updates the approval authority definition stored in the approval path definition database 104 by the processing device in response to the received request.

  The access authority management unit 122 of the approval route definition tool 120 receives a request via a network or the like from a user terminal that transmits a request for creating an access authority definition for a new workflow. In response to the received request, the access authority management unit 122 creates an access authority definition and stores it in the approved document authority database 105.

  Further, the access authority management unit 122 receives a request via a network or the like from a user terminal that transmits a request for updating (changing or deleting) the access authority definition by designating an (existing) workflow. The access authority management unit 122 updates the access authority definition stored in the approved document authority database 105 by the processing device in response to the received request.

  The list transmission unit 123 of the approval route definition tool 120 uses the role corresponding to the workflow designated from the user's terminal, the usage status definition stored in the role usage status database 106 (the usage status management unit of the role usage status management tool 140). 141 is extracted by the processing device with reference to the usage state definition created in step 141. The list transmission unit 123 transmits the extracted list of roles to the terminal of the user via a network or the like.

  For example, when the request for updating the approval authority definition is received by the approval authority management unit 121, the list transmission unit 123 assigns a role corresponding to the workflow specified by the transmission source of the request to the role usage database 106. Is extracted by the processing device with reference to the usage situation definition stored in the table. The list transmission unit 123 transmits the extracted list of roles to the transmission source via a network or the like and confirms with the user of the transmission source, and then causes the approval authority management unit 121 to update the approval authority definition.

  In the example of FIGS. 3 to 8, the terminal of the user C of the “workflow management department” ABC company / YY system department designates the “workflow ID” wf-abc-00001 and purchases the parts of the approval route definition database 104. Assume that a request for changing the role of “approval step 1” of the workflow to another role is transmitted. When the approval authority management unit 121 receives the request, the list transmission unit 123 sets the “role ID” role-abcde00001, role-abcde00001, and role-abcde12345 corresponding to the “workflow ID” wf-abc-00001 to the role usage situation database 106. Extract from The list transmission unit 123 transmits a list of “role ID” roles-abcde00001, role-abcde00002, and role-abcde12345 to the terminal of user C. For example, it is determined that there is no need to restrict access to the original role even if the user C changes the role of “approval step 1” to another role, and that the terminal of the user C has confirmed the list. Suppose that the response shown is returned. When the approval authority management unit 121 receives the response, the list transmission unit 123 changes the role of “approval step 1” of the workflow of “workflow ID” wf-abc-00001 to another role in the approval route definition database 104. Is permitted to the approval authority management unit 121.

  The role management unit 131 of the role definition tool 130 receives a request from a user terminal that transmits a request for creating a role definition for a new role via a network or the like. In response to the received request, the role management unit 131 creates a role definition and stores it in the role database 102.

  The role management unit 131 receives a request from a user terminal that transmits a request for updating (changing or deleting) a role definition by designating an (existing) role via a network or the like. The role management unit 131 updates the role definition stored in the role database 102 by the processing device in response to the received request.

  The list transmission unit 132 of the role definition tool 130 uses the workflow corresponding to the role specified from the user terminal, the usage status definition stored in the role usage status database 106 (the usage status management unit 141 of the role usage status management tool 140). The processing device is extracted with reference to the usage situation definition created by (1). The list transmitting unit 132 transmits the extracted workflow list to the user terminal via a network or the like.

  For example, when the role management unit 131 receives a request for updating the role definition, the list transmission unit 132 stores the workflow corresponding to the role specified by the transmission source of the request in the role usage state database 106. The extracted usage status definition is extracted by the processing device. The list transmission unit 132 transmits the extracted workflow list to the transmission source via the network or the like and confirms with the user of the transmission source, and then causes the role management unit 131 to update the role definition.

  Here, in the examples of FIGS. 3 to 8, the terminal of the user C of the “role management department” ABC company / YY system department designates the “role ID” role-abcde00002 as the person in charge of the CC section of the role database 102. Suppose that a request for adding a new user is transmitted. When the role management unit 131 receives the request, the list transmission unit 132 extracts “workflow IDs” wf-abc-00001 and wf-abc-00002 corresponding to the “role ID” role-abcde00002 from the role usage state database 106. . The list transmission unit 132 transmits a list of “workflow IDs” wf-abc-00001 and wf-abc-00002 to the terminal of the user C. For example, it is determined that the user C added as the person in charge of the CC section can access any workflow of “workflow ID” wf-abc-00001 and wf-abc-00002, and the terminal of the user C is Assume that a response indicating that the list has been confirmed is returned. When the role management unit 131 receives the response, the list transmission unit 132 instructs the role management unit 131 to add a new user to “member registered in role” of the “role ID” role-abcde00002 in the role database 102. And allow.

  According to the present embodiment, the approved document document database 105 can perform the association process between the approved workflow document and the role, and the management authority of the approved workflow document can be set based on the role. That is, roles can be used not only for setting workflow approval paths but also for setting access rights for approved workflow documents.

  Further, according to the present embodiment, role usage status management tool 140 and role usage status database 106 can collect and centralize role usage status information and provide it to other systems. In providing to other systems, it is desirable to prepare API (Application / Programming / Interface).

  9 to 12 are flowcharts illustrating an example of the operation of the workflow management system 100 (workflow management method according to the present embodiment, program processing procedure according to the present embodiment).

  Here, the user / organization database 101, the role database 102, the workflow document database 103, the approval route definition database 104, the approved document authority database 105, and the role use status database 106 store the data illustrated in FIGS. It shall be.

In step S1 of FIG. 9, for example, a role used for setting access authority for a workflow document can be created by the following procedure.
(1) A role administrator accesses the role definition tool 130.
(2) The role management unit 131 of the role definition tool 130 refers to the user / organization database 101 and displays user / organization information on the terminal of the role manager.
(3) The role manager inputs the definition of the material person role with the role definition tool 130.
(4) The role management unit 131 of the role definition tool 130 registers input data in the role database 102.

In step S2 of FIG. 9, for example, the workflow approval path and the access authority of the approved workflow document can be set by role in the following procedure.
(1) A workflow administrator (developer) accesses the approval route definition tool 120.
(2) The approval authority management unit 121 of the approval route definition tool 120 refers to the role database 102 and displays a list of roles on the terminal of the workflow administrator.
(3) The workflow administrator inputs the definition of the part purchase workflow using the approval route definition tool 120.
(4) The approval authority management unit 121 of the approval path definition tool 120 registers input data in the approval path definition database 104, the workflow document database 103, and the approved document authority database 105.
(5) The usage status management unit 141 of the role usage status management tool 140 registers the association information between each role and the part purchase workflow in the role usage status database 106.

In step S3 of FIG. 10, for example, the workflow can be used in the following procedure.
(1) The workflow administrator accesses the parts purchase workflow.
(2) The approval control unit 112 of the workflow engine 110 refers to the approval path definition database 104 and identifies a role associated with “approval step 2” of the component purchase workflow.
(3) The approval control unit 112 of the workflow engine 110 refers to the role database 102 and displays a list of users associated with the role on the terminal of the workflow administrator.
(4) The workflow administrator selects A as the approver of “Approval Step 2” of the parts purchase workflow.
(5) The approval control unit 112 of the workflow engine 110 transmits an approval request mail of “approval step 2” of the parts purchase workflow to the terminal A.
(6) A accesses the parts purchase workflow.
(7) The approval control unit 112 of the workflow engine 110 refers to the role database 102 and identifies the role associated with A.
(8) The approval control unit 112 of the workflow engine 110 refers to the approval path definition database 104 and confirms that the role is a role associated with “approval step 2” of the component purchase workflow.
(9) A approves the order form.
(10) The approval control unit 112 of the workflow engine 110 transmits an approval completion mail of “approval step 2” (or the whole) of the parts purchase workflow to a terminal such as C. Note that (1) to (10) are also executed in the same manner for the “approval step 1” of the component purchase workflow.
(11) C accesses the parts purchase workflow.
(12) The access control unit 114 of the workflow engine 110 refers to the role database 102 and identifies the role associated with C.
(13) The access control unit 114 of the workflow engine 110 refers to the approved document authority database 105 and confirms that the role is a role associated with the component purchase workflow.
(14) C refers to the order form.

In step S4 in FIG. 11, for example, it is possible to confirm in which workflow the role is used in the following procedure.
(1) The administrator of the workflow (or role) accesses the role usage status management tool 140.
(2) The list transmission unit 142 of the role usage status management tool 140 displays a menu screen on which the following a to c can be selected on the terminal of the workflow manager.
a. List workflow names associated with roles b. Display a list of role names associated with the workflow c. Display usage details (workflow approval step number, document name, etc.) (3) The workflow administrator selects “a. List workflow names associated with roles” from the menu.
(4) The list transmission unit 142 of the role usage status management tool 140 refers to the role usage status database 106 and the role database 102 and displays a list of role names on the terminal of the workflow manager.
(5) The workflow administrator selects a role whose usage status is to be confirmed.
(6) The list transmission unit 142 of the role usage status management tool 140 acquires the workflow ID from the role usage status database 106 using the role ID as a key.
(7) The list transmission unit 142 of the role usage status management tool 140 acquires the workflow name from the approval path definition database 104 using the workflow ID as a key, and displays the workflow name list on the terminal of the workflow manager.
(8) The workflow administrator selects “c. Display usage details” from the menu.
(9) The list sending unit 142 of the role usage status management tool 140 acquires approval route information from the approval route definition database 104 and workflow document name information from the workflow document database 103 using the workflow ID as a key, and manages the workflow. On the screen of the terminal.

In step S5 of FIG. 12, for example, it is possible to confirm which role the workflow uses by the following procedure.
(1) The administrator of the workflow (or role) accesses the role usage status management tool 140.
(2) The list transmission unit 142 of the role usage status management tool 140 displays a menu screen on which the following a to c can be selected on the terminal of the workflow manager.
a. List workflow names associated with roles b. Display a list of role names associated with the workflow c. Display usage details (workflow approval step number, document name, etc.) (3) The workflow administrator selects “b. List role names linked to workflow” from the menu.
(4) The list transmission unit 142 of the role usage status management tool 140 refers to the role usage status database 106 and the approval route definition database 104 and displays a list of workflow names.
(5) The workflow administrator selects a workflow whose usage status is to be confirmed.
(6) The list transmission unit 142 of the role usage status management tool 140 acquires the role ID from the role usage status database 106 using the workflow ID as a key.
(7) The list transmission unit 142 of the role usage management tool 140 acquires the role name from the role database 102 using the role ID as a key, and displays the list of role names on the terminal of the workflow manager.
(8) The workflow administrator selects “c. Display usage details” from the menu.
(9) The list sending unit 142 of the role usage status management tool 140 acquires approval route information from the approval route definition database 104 and workflow document name information from the workflow document database 103 using the workflow ID as a key, and manages the workflow. On the screen of the terminal.

  FIG. 13 is a diagram illustrating an example of a hardware configuration of the workflow management system 100.

  In FIG. 13, the workflow management system 100 includes an arbitrary number of computers, and includes an LCD 901 (Liquid / Crystal / Display), a keyboard 902 (K / B), a mouse 903, an FDD 904 (Flexible Disk / Drive), and a CDD 905 (Compact). (Disc / Drive) and a printer 906 are provided. These hardware devices are connected by cables and signal lines. Instead of the LCD 901, a CRT (Cathode / Ray / Tube) or other display device may be used. Instead of the mouse 903, a touch panel, a touch pad, a trackball, a pen tablet, or other pointing devices may be used.

  The workflow management system 100 includes a CPU 911 (Central Processing Unit) that executes a program. The CPU 911 is an example of a processing device. The CPU 911 includes a ROM 913 (Read / Only / Memory), a RAM 914 (Random / Access / Memory), a communication board 915, an LCD 901, a keyboard 902, a mouse 903, an FDD 904, a CDD 905, a printer 906, and an HDD 920 (Hard / Disk) via a bus 912. Connected with Drive) to control these hardware devices. Instead of the HDD 920, a flash memory, an optical disk device, a memory card reader / writer, or other recording medium may be used.

  The RAM 914 is an example of a volatile memory. The ROM 913, the FDD 904, the CDD 905, and the HDD 920 are examples of nonvolatile memories. These are examples of the storage device. The communication board 915, the keyboard 902, the mouse 903, the FDD 904, and the CDD 905 are examples of input devices. The communication board 915, the LCD 901, and the printer 906 are examples of output devices.

  The communication board 915 is connected to a LAN (Local / Area / Network) or the like. The communication board 915 is not limited to a LAN, but is an IP-VPN (Internet, Protocol, Private, Network), a wide area LAN, an ATM (Asynchronous / Transfer / Mode) network, a WAN (Wide / Area / Network), or the Internet. It does not matter if it is connected to. LAN, WAN, and the Internet are examples of networks.

  The HDD 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922. The program group 923 includes programs that execute the functions described as “˜units” in the description of the present embodiment. The program is read and executed by the CPU 911. The file group 924 includes data, information, and signal values described as “˜data”, “˜information”, “˜ID (identifier)”, “˜flag”, and “˜result” in the description of this embodiment. And variable values and parameters are included as items of “˜file”, “˜database”, and “˜table”. The “˜file”, “˜database”, and “˜table” are stored in a recording medium such as the RAM 914 or the HDD 920. Data, information, signal values, variable values, and parameters stored in a recording medium such as the RAM 914 and the HDD 920 are read out to the main memory and the cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. It is used for processing (operation) of the CPU 911 such as calculation, control, output, printing, and display. During the processing of the CPU 911 such as extraction, search, reference, comparison, calculation, calculation, control, output, printing, and display, data, information, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory. Remembered.

  The arrows in the block diagrams and flowcharts used in the description of this embodiment mainly indicate input / output of data and signals. Data and signals are recorded in memory such as RAM 914, FDD904 flexible disk (FD), CDD905 compact disk (CD), HDD920 magnetic disk, optical disk, DVD (Digital Versatile Disc), or other recording media Is done. Data and signals are transmitted by a bus 912, a signal line, a cable, or other transmission media.

  In the description of the present embodiment, what is described as “to part” may be “to circuit”, “to device”, “to device”, and “to step”, “to process”, “to”. ~ Procedure "," ~ process ". That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, what is described as “˜unit” may be realized only by software or only by hardware such as an element, a device, a board, and wiring. Alternatively, what is described as “to part” may be realized by a combination of software and hardware, or a combination of software, hardware and firmware. Firmware and software are stored as programs in a recording medium such as a flexible disk, a compact disk, a magnetic disk, an optical disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” described in the description of the present embodiment. Or a program makes a computer perform the procedure and method of "-part" described by description of this Embodiment.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to this embodiment, A various change is possible as needed.

  100 Workflow Management System 101 User / Organization Database 102 Role Database 103 Workflow Document Database 104 Approval Path Definition Database 105 Approved Document Authority Database 106 Role Usage Database 110 Workflow Engine 111 Approval Request Receiving Unit 112 Approval control unit, 113 access request reception unit, 114 access control unit, 120 approval route definition tool, 121 approval authority management unit, 122 access authority management unit, 123 list transmission unit, 130 role definition tool, 131 role management unit, 132 list Transmission unit, 140 role usage status management tool, 141 usage status management unit, 142 list transmission unit, 901 LCD, 902 keyboard, 903 mouse, 904 FDD, 9 05 CDD, 906 printer, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 HDD, 921 operating system, 922 window system, 923 program group, 924 file group.

Claims (5)

A workflow data storage unit that stores, in a storage device, data including at least one of a document and information indicating the progress of approval for each workflow in which a user approves a document along an approval path including at least one approval step. When,
A role definition storage unit that stores, in a storage device, a role definition that defines a correspondence relationship between a user and a role that classifies the role of the user;
An approval authority definition storage unit that stores in the storage device an approval authority definition that defines a correspondence relationship between the approval step of the workflow approval route and the role that is authorized to approve the document in the approval step;
An access authority definition storage unit that stores, in a storage device, an access authority definition that defines a correspondence relationship between a workflow and a role that is authorized to access workflow data;
An approval request receiving unit that receives a request from a user terminal that transmits a request for approving a document by specifying an approval step of the workflow approval route;
The role corresponding to the user of the transmission source of the request received by the approval request reception unit is extracted with reference to the role definition stored in the role definition storage unit, and the extracted role is designated by the transmission source. Whether the approval step of the approval route of the corresponding workflow corresponds is determined by referring to the approval authority definition stored in the approval authority definition storage unit. An approval control unit that permits document approval in steps;
An access request receiver that receives a request from a user terminal that transmits a request to access workflow data by specifying a workflow;
The role corresponding to the user of the transmission source of the request received by the access request reception unit is extracted with reference to the role definition stored in the role definition storage unit, and the extracted role is designated by the transmission source. Whether the corresponding workflow is supported is determined by referring to the access authority definition stored in the access authority definition storage unit. If it is determined that the workflow is supported, the user is stored in the workflow data storage unit. An access control unit that permits access to the workflow data ;
Referring to the access authority definition stored in the access authority definition storage unit, the correspondence relationship between the workflow and the role to which the authority to access the workflow data is extracted as the role usage status, and the extracted usage status A usage status management unit that creates a usage status definition that defines
A request is received from a user terminal that transmits a request for updating the approval authority definition by specifying a workflow, and the approval authority definition stored in the approval authority definition storage unit is updated according to the received request. Approval authority management department,
The role corresponding to the workflow specified from the transmission source of the request received by the approval authority management unit is extracted with reference to the usage status definition created by the usage status management unit, and the extracted list of roles is Ruwa Kufuro management system includes a <br/> after confirming to the transmission source user and the transmission source, and the list transmitting section for updating the approval authority defined above approval authority management unit. The list transmission unit extracts a workflow corresponding to a role designated from a user terminal with reference to the usage situation definition created by the usage situation management unit, and the extracted workflow list is stored in the user terminal. workflow management system according to 請 Motomeko 1 that sends. Role management unit that receives a request from a user terminal that transmits a request for updating the role definition by specifying a role, and updates the role definition stored in the role definition storage unit in response to the received request Further comprising
The list transmission unit extracts the workflow corresponding to the role specified from the transmission source of the request received by the role management unit with reference to the usage status definition created by the usage status management unit, and extracted a list of workflow from sending to the sender to confirm to the sender of the user, the workflow management system according to 請 Motomeko 2 Ru to update the role definition to the role management unit. For each workflow in which a user approves a document along an approval path including at least one approval step, data including at least one of a document and information indicating the progress of approval is stored in a storage device, and Role definition that defines the correspondence with roles that classify user roles, and approval authority definition that defines the correspondence between the approval step of the workflow approval route and the role authorized to approve documents in the approval step And an access authority definition that defines a correspondence relationship between the workflow and a role that is authorized to access the workflow data in a storage device,
A request is received from a terminal of a user who transmits a request for approving a document by specifying an approval step of a workflow approval route, and a role corresponding to the user who transmitted the received request is stored in the storage device. Refer to the approval authority definition stored in the storage device to see whether the approval step of the approval route of the workflow specified by the sender corresponds to the extracted role. If it is determined that the document is supported, the user is allowed to approve the document in the approval step,
The role corresponding to the user who sent the request is received from the user terminal that sends the request to access the workflow data by specifying the workflow, and the role definition stored in the storage device is defined. It is determined by referring to the access authority definition stored in the storage device whether or not the workflow specified by the sender corresponds to the extracted role. The user is allowed to access the workflow data stored in the storage device ,
Usage that refers to the access authority definition stored in the storage device, extracts the correspondence between the workflow and the role authorized to access the workflow data as the role usage, and defines the extracted usage Create a status definition
The usage definition that created the role corresponding to the workflow specified by the sender of the received request is received from the terminal of the user who sends the request to update the approval authority definition by specifying the workflow The workflow management is characterized in that the approval authority definition stored in the storage device is updated after the extracted list of roles is transmitted to the transmission source and confirmed with the user of the transmission source. Method. A program for causing a computer to function as the workflow management system according to any one of claims 1 to 3 .

Images