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

Abstract

<P>PROBLEM TO BE SOLVED: To associate documents in a document management system with tasks in a workflow management system and manage them while holding document files in the document management system independently from the workflow management system. <P>SOLUTION: The workflow management system manages constructive workflows by a management server provided with a database independently of the document management system provided with a document database for storing a document body and document identification information for identifying the document. The management server includes a document metadata database 116 for storing document metadata including the document identification information stored in the document database and a relative information database 113 for storing a task configuring a workflow and the document metadata by associating them with each other. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a workflow management system, a workflow management method, and a workflow management program for managing a constructive workflow.

  A conventional workflow management system has to determine a workflow model before executing a workflow. However, it is difficult to formulate a prior workflow model in fields where prior information is not completely complete, such as research and development and some services. In view of this, a method called a constructive workflow has been developed that can dynamically construct a model (that can be dynamically changed) during workflow execution.

  In Japanese Patent Application Laid-Open No. 2007-188144 (Patent Document 1) and Japanese Patent Application Laid-Open No. 2007-188145 (Patent Document 2), a more flexible task model, that is, a task hierarchy is used as an alternative to the conventional workflow definition in the constructive workflow. A template has been proposed. By using a task model, it is possible to select a standard method based on past knowledge and refine the task.

In Japanese Patent Laid-Open No. 2008-065714 (Patent Document 3), what is created as a task product is often a document, and when saving it, the task is attached to the workflow system as an attached document, Methods such as creating and managing documents at the same time as task creation have been proposed.
JP 2007-188144 A JP 2007-188145 A JP 2008-0665714 A

  However, the conventional system has a problem that a place where a document is placed is not created until a task is generated on the workflow, and the lifetime of the document is determined depending on the task. Documents that are deliverables may be referenced independently of the workflow, and it is desirable that they can be referenced without logging in to the workflow management system. However, this is not easy because the document is a task attachment. In addition, it is difficult to select a task by paying attention to a document and generate a task.

  Therefore, the present invention has been made in view of the above-described problem. While having a document file on the document management system independent of the workflow management system, the document in the document management system and the tasks in the workflow management system are It is an object to provide a workflow management system, a workflow management method, and a workflow management program that can be managed in association with each other.

  A workflow management system according to one aspect of the present invention manages a constructive workflow by a management server having a database independently of a document management system having a document main body and a document database storing document identification information for identifying the document. The management server includes a document metadata database storing document metadata indicating bibliographic information including document identification information stored in the document database, the task, and the document metadata. And a related information database stored in association with each other.

  The workflow management method according to another aspect of the present invention provides a document identification stored in the document database independently of a document management system including a document main body and a document database storing document identification information for identifying the document. Workflow management for managing constructive workflow by a management server comprising a document metadata database for storing document metadata indicating bibliographic information including information, and a related information database for storing the task and the document metadata in association with each other A workflow management method in a system, wherein a document metadata including the document identification information is retrieved from the document metadata database based on the document identification information, and a task corresponding to the retrieved document metadata is represented by the related information. Search step to search from database When, a display step of displaying the tasks retrieved by the retrieving step.

  The workflow management system and the workflow management method of the present invention can be realized as a computer-readable recording medium on which a program to be executed by a computer and a program are recorded.

  According to the present invention, a document in a document management system and a task in the workflow management system can be associated and managed while having a document file on the document management system independently of the workflow management system.

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

<About hardware configuration>
First, the hardware configuration of the workflow management server (hereinafter referred to as workflow management SV) according to the first embodiment of the present invention will be described. Since the document management server and the user terminal PC (Personal Computer) have the same hardware configuration as the workflow management SV, description thereof is omitted here. FIG. 1 is a diagram illustrating an example of a hardware configuration of the workflow management SV according to the first embodiment of the present invention.

  As shown in FIG. 1, the workflow management SV includes a control unit 11, a main storage unit 12, an auxiliary storage unit 13, a network I / F 14, an external storage device I / F 15, an external device I / F 16, an output device I / F 17, and And an input device I / F 18.

  A control unit (CPU: Central Processing Unit) 11 is a device that executes a program stored in the main storage unit 12, performs arithmetic processing on data received from an input or storage device, and outputs the data to an output device or storage device.

  A main storage unit (ROM: Read Only Memory, RAM: Random Access Memory) 12 is a device that stores programs and data executed by the control unit 11.

  The auxiliary storage unit (HD: Hard Disk) 13 is a device that stores basic software such as an OS (Operating System) and application software together with related data. In addition, a database (DB: Data Base) is constructed in the auxiliary storage unit 13 to store and manage various information (various data) handled by the workflow management system.

  The network I / F 14 is an interface that exchanges information (data) with peripheral devices connected via the network.

  The external storage device I / F 15 is an interface for exchanging data with an external storage device (for example, a storage media drive) connected via a data transmission path such as USB (Universal Serial Bus).

  The external device I / F 16 is an interface for exchanging data with an external input device (for example, a digital camera or a scanner) connected via a data transmission path.

  The output device I / F 17 is an interface that receives data from an output device (for example, a CRT (Cathode Ray Tube) or a liquid crystal display) connected via a data transmission path.

  The input device I / F 18 is an interface that receives data from an input device (for example, a keyboard or a mouse) connected via a data transmission path.

<About objects>
FIG. 2 is a diagram illustrating an object conceptual diagram according to the first embodiment. As shown in FIG. 2, what is managed on the workflow management system side and the document management system side is different. The workflow management system manages information about tasks, task models, document metadata, document types, and template documents, and the document management system manages information about documents.

  Here, an existing document management system (particularly, a document management DB) is used as the document management system. In the present invention, in order to associate a document in the document management system with a task in the workflow management system, document metadata is generated and managed in the workflow management system. Further, in the present invention, by generating a document type in the workflow management system, a task can be generated based on this document type.

  First, the workflow management system side will be described. The task model is a generalized and abstracted task. Since a task is generated by instantiating the task model, the task model and the task are associated (broken line).

  Also, document metadata indicating bibliographic information of documents in the document management system is managed. A document necessary for executing the task or a document to be referred to is attached to the task model or task, but the document itself is managed in the document management system. Or a task model (solid line).

  In addition, a document type indicating the type of document in the document management system is associated with the task model (dotted line), and is associated with document metadata or a template document (synonymous with document metadata) (one-dot chain line).

  A document in the document management system is associated with document metadata or a template document in the workflow management system (two-dot chain line). With this association, a document attached to a task can be managed in a document management system independent of the workflow management system.

<About main functional configuration>
FIG. 3 is a block diagram illustrating an example of main functional configurations of the workflow management system 100 and the document management system 200 according to the first embodiment. The workflow management system 100 includes a workflow management SV and a user terminal PC, and the document management system 200 includes a document management SV and a user terminal PC. Next, main functional configurations of these management SVs will be described in the order of workflow management SV, document management SV, and user terminal PC.

  As shown in FIG. 3, the workflow management SV includes a GUI providing unit 101 that provides a GUI (graphical user interface) relating to a workflow to a user A who uses the system, and a re-creation from an existing task model and / or task instance. A workflow engine 104 that dynamically generates and executes a workflow model by use and various databases 112 (hereinafter referred to as “DB”) are provided.

  The various DBs 112 include a related information DB 113 that stores the relationship between tasks and documents, a task model DB 114 that stores a task model abstracted in advance by an administrator, a task instance DB 115 that stores past task instances, A document metadata DB 116 that stores document metadata indicating the bibliographic information of the document and a document type DB 117 that stores a document type indicating the document type are provided. The data structure of each DB will be described later with reference to FIG.

  The GUI providing unit 101 includes a rendering engine 102 for drawing a display screen of a user terminal PC (screen displayed on a CRT or a liquid crystal display) and an input / output control unit 103 for exchanging information with the user.

  The workflow engine 104 includes a search unit 105 that performs various searches on the DBs 113 to 117, a task control unit 106 that controls tasks constituting the workflow, a document metadata control unit 109 that controls document metadata, It has.

  The search unit 105 executes various searches for each DB 112 of the related information DB 113, the task model DB 114, the task instance DB 115, the document metadata DB 116, and the document type DB 117.

  Here, the search means 105 will be described with reference to FIG. FIG. 4 is a block diagram showing detailed functions of the search means 105. As shown in FIG. 4, the search unit 105 includes a document metadata search unit 401, a related task search unit 402, a document type search unit 403, and a task model search unit 404.

  The document metadata search unit 401 searches the document metadata DB 116 for document metadata based on document identification information (document ID) for identifying a document in the document management system. The related task search unit 402 searches for a task from the related information DB 113 based on the document metadata ID for identifying the document metadata.

  The document type search unit 403 searches for a document type from the document type DB 117 based on the document metadata ID. The task model search unit 404 searches for the task model from the task model DB 114 based on the document type ID that identifies the document type.

  Returning to FIG. 3, the task control unit 106 includes a task creation unit 107 that creates a task, and a task tree holding unit 108 that holds a tree structure of tasks.

  As an operation overview, the user A operates the workflow engine 104 through the input / output control unit 103 of the GUI providing unit 101 to create and execute a workflow, create a workflow model, related information, register a document, and the workflow instance, Perform work such as linking with the workflow model.

  The task control unit 106 of the workflow engine 104 uses the task model DB 114 and the task instance DB 115 to control tasks based on the user A instruction and the like. The task creation unit 107 of the task control unit 106 performs tasks such as task creation and information linking based on information in each of the DBs 113 to 117 in accordance with an instruction from the user A.

  The document metadata control unit 109 includes a document metadata management unit 110 that manages document metadata and a document creation instruction unit 111 that creates a document.

  The document metadata management unit 110 acquires bibliographic information of a newly created document, assigns a new document metadata ID, and manages the document metadata. When the document creation instruction unit 111 receives a document creation instruction in accordance with an instruction from the user A, the document creation instruction unit 111 outputs a document creation instruction to the document creation unit 205 of the document management system so as to duplicate the document in the document management system.

  Next, the document management SV will be described. Since the GUI providing unit 201 is the same as the GUI providing unit 101 of the workflow management SV, description thereof is omitted.

  The document search unit 204 searches for a document in the document management DB 206 according to the user B instruction. At this time, the document search unit 204 acquires a search key such as a document ID or a document name from the user B via the browser 302, and searches for a document based on the search key.

  The document creation unit 205 creates a document according to the user B instruction. In the first embodiment, a document can be created in accordance with a document creation instruction from the document creation instruction unit 111 according to a user A instruction. The document management DB 206 stores documents. The data structure in the document management DB 206 will be described later with reference to FIG.

  The workflow management system 100 according to the first embodiment includes a multifunction peripheral MFP connected to the system by a communication I / F function provided in the workflow management SV (for example, the network I / F 14 provided in the information processing apparatus illustrated in FIG. 1). User A can log in and out of the system from a device such as a multifunctional MFP, perform task association with scanned images (paper document information is attached to task information), and print task attached information. And so on.

  Next, the user terminal PC displays a display screen for exchanging with the workflow management SV for various types of information related to tasks drawn by the rendering engine 102 of the GUI providing unit 101 provided in the workflow management SV. 301 is provided.

  Also, the browser 302 displays a display screen for exchanging with the document management SV for various information related to the document drawn by the rendering engine 202 of the GUI providing unit 201 provided in the document management SV.

<About the schema of each database>
FIG. 5 is a diagram illustrating a schema example of each database. 5A shows an example schema of the document management DB 206, FIG. 5B shows an example schema of the document metadata DB 116, FIG. 5C shows an example schema of the document type DB 117, and FIG. FIG. 5E shows an example schema of the related information DB 113, FIG. 5E shows an example schema of the task model DB 114, and FIG. 5F shows an example schema of the task instance DB 115.

  As shown in FIG. 5A, the document management DB 206 in the document management system stores an ID that is information for identifying a document, a document body, a title, and the like in association with each other. Here, a URL (Uniform Resource Locator) indicating the storage location of the document is used as the document ID.

  As shown in FIG. 5B, the document metadata DB 116 in the workflow management system identifies a document metadata ID that is information for identifying document metadata, a URL that is a document ID, and a document type. Information associated with the document type ID and the like.

  As shown in FIG. 5C, the document type DB 117 in the workflow management system stores a document type ID, a document type title, and a task model ID that is information for identifying a task model in association with each other. To do.

  As shown in FIG. 5D, the related information DB 113 in the workflow management system stores a task ID, which is information for identifying a task, and a document metadata ID in association with each other.

  As shown in FIG. 5E, the task model DB 114 in the workflow management system includes a task model ID, a template document ID (similar to a document metadata ID) that is information for identifying a template document, and a document type. The ID is stored in association with the ID.

  As shown in FIG. 5F, the task instance DB 115 in the workflow management system stores a task ID, a task title, an executor, and the like in association with each other.

<Search processing for tasks related to documents>
FIG. 6 is a sequence diagram illustrating an example of processing for searching for a task related to a document. In step 101, the user designates a document via the browser 302 and makes a search request for a task related to the designated document to the workflow engine 104. The browser may be either the browser 301 on the workflow management system side or the browser 302 on the document management system side.

  Progressing to step 102 following step 101, upon receiving a task search request from the user, the workflow engine 104 searches the document metadata DB 116 for document metadata using the document ID of the designated document as a search key.

  Progressing to step 103 following step 102, the document metadata DB 116 outputs the document metadata ID to the workflow engine 104 as a search result of the document metadata.

  Progressing to step 104 following step 103, the workflow engine 104 searches the related information DB 113 for a task associated with the document metadata ID based on the document metadata ID acquired from the document metadata DB 116.

  In step 105 following step 104, the related information DB 113 outputs a task ID list in which task IDs of all searched tasks are listed to the workflow engine 104 as a task search result.

  Following step 105, the process proceeds to step 106, and the workflow engine 104 sends a task information acquisition request corresponding to the task ID included in the list to the task instance DB 115 based on the task ID list acquired from the related information DB 113. Do.

  Progressing to step 107 following step 106, the task instance DB 115 outputs task information corresponding to the task ID acquired from the workflow engine 104 to the workflow engine 104.

  Progressing to step 108 following step 107, when the workflow engine 104 acquires task information from the task instance DB 115, the workflow engine 104 presents the acquired task information to the user as a search result.

  As described above, by performing the processing shown in FIG. 6, the task related to the designated document can be retrieved and presented to the user by designating the document in an environment where the document and the task are managed independently. Can do.

<About task generation processing after specifying a document>
FIG. 7 is a sequence diagram illustrating an example of task generation processing after a document is specified. In step 201, the user uses the browser 301 to make a document search request for acquiring a document list to the document management SV.

  Progressing to step 202 following step 201, the document management SV presents a document list to the user via the browser 301 upon receiving a document search request in accordance with the user's instruction. Progressing to step 203 following step 202, the user designates a document from the presented document list, and makes a search request for a task model related to the designated document to the workflow engine 104.

  Progressing to step 204 following step 203, the workflow engine 104 searches the document metadata DB 116 for document metadata corresponding to the document ID based on the document ID of the document specified by the user.

  Progressing to step 205 following step 204, the document metadata DB 116 outputs the document metadata ID to the workflow engine 104 as a search result of the document metadata.

  Progressing to step 206 following step 205, the workflow engine 104 requests the document type DB 117 to acquire a document type corresponding to the document metadata ID acquired from the document metadata DB 116.

  Progressing to step 207 following step 206, the document type DB 117 outputs the document type corresponding to the document metadata ID included in the acquisition request to the workflow engine 104.

  Progressing to step 208 following step 207, the workflow engine 104 searches the task model DB 114 for a task model corresponding to the document type acquired from the document type DB 117.

  Progressing to step 209 following step 208, the task model DB 114 outputs a task model list in which task models corresponding to document types are listed to the workflow engine 104 as a search result.

  Progressing to step 210 following step 209, the workflow engine 104 generates a task model list using the task model title and the task model ID in the task model list acquired from the task model DB 114. Next, the workflow engine 104 presents the generated task model list to the user via the GUI providing unit 101 and the browser 301.

  In step 211 following step 210, the user designates a task model from the task model list via the browser 301, and makes a task generation request from the designated task model.

  Progressing to step 212 following step 211, the workflow engine 104 requests the task model DB 114 to acquire a task model corresponding to the task model ID based on the task model ID of the specified task model in accordance with a user instruction. I do.

  Proceeding to step 213 following step 212, the task model DB 114 outputs the requested task model to the workflow engine 104.

  Progressing to step 214 following step 213, the workflow engine 104 instantiates the acquired task model to create a task and stores it in the task instance DB 115.

  Proceeding to step 215 following step 214, when a new task is stored from the workflow engine 104, the task instance DB 115 assigns a task ID to this task, and notifies the assigned task ID to the workflow engine 104.

  In step 216 following step 215, the workflow engine 104 stores the task ID notified from the task instance DB 115 and the document metadata ID acquired from the document metadata DB 116 in step 205 in association with the related information DB 113. .

  Progressing to step 217 following step 216, when the association between the task ID and the document metadata ID is completed (stored in the DB), the related information DB 113 notifies the workflow engine 104 that the association has been completed.

  Progressing to step 218 following step 217, when the workflow engine 104 receives a completion notification from the related information DB 113, the workflow engine 104 notifies the user that task generation has been completed via the browser 302.

  As described above, by performing the processing shown in FIG. 7, when the user designates a document, the task can be generated from the task model corresponding to the designated document. In the process illustrated in FIG. 7, the user performs the above process using the browser 301. However, the user may perform the above process by accessing the document management server using the browser 302.

  In FIG. 7, the document metadata ID corresponding to the designated document is present in the document metadata DB 116. Next, when the corresponding document metadata ID does not exist in the document metadata DB 116, or A case where the document ID of the designated document does not exist in the document metadata DB 116 will be described.

  FIG. 8 is a sequence diagram illustrating an example of processing for generating a task by specifying a document type. In the processing shown in FIG. 8, since the document metadata DB 116 does not have a document ID corresponding to the designated document, the user is allowed to select a document type corresponding to the designated document, and the task is based on the selected document type. Is generated. In the processing shown in FIG. 8, the same reference numerals are given to the same processing as that in FIG.

  In step 301, since the document metadata DB 116 does not have the document ID of the designated document, the document metadata DB 116 records this document ID in the document metadata DB 116, assigns a new document metadata ID, and assigns the assigned document metadata ID. Notify the workflow engine 104.

  In step 302 following step 301, the workflow engine 104 searches the document type DB 117 for the corresponding document type based on the notified document metadata ID.

  In step 303 following step 302, the document type DB 117 outputs a document type list to the workflow engine 104 because the corresponding document type does not exist.

  Progressing to step 304 following step 303, the workflow engine 104 presents the document type list acquired from the document type DB 117 to the user via the browser 301.

  Proceeding to step 305 following step 304, the user selects a document type from the document type list via the browser 301.

  Progressing to step 306 following step 305, the workflow engine 104 stores the selected document type in the document metadata DB 116 in association with the newly created document metadata.

  Progressing to step 307 following step 306, when the association between the document metadata and the document type is completed (stored in the DB), the document metadata DB 116 notifies the workflow engine 104 that the association has been completed.

  Subsequent to step 307, the processing after step 208 is performed in the same manner as the processing shown in FIG. The association in step 216 is performed using the document metadata ID acquired in step 301 and the task ID acquired in step 215.

  As described above, even if the document ID of the specified document does not exist in the document metadata DB 116 by performing the processing shown in FIG. 8, the user can select the document type by presenting the document type list to the user from the system. A task can be generated based on the selected document type.

  In the processing shown in FIG. 8, the case where the document ID corresponding to the document does not exist in the document metadata DB 116 has been described. However, the document corresponding to the document metadata even if the document metadata corresponding to the document ID exists. The type may not exist in the document type DB 117. Even in such a case, the same processing may be performed. At this time, the processing in step 306 is replaced with processing for storing the document metadata ID and the document type ID in association with the document type DB 117.

  Next, transition of each DB when generating a task will be described using a specific example. FIG. 9 is a diagram illustrating a state of each DB before a task is generated. 9A shows an example of data stored in the document type DB 117, FIG. 9B shows an example of data stored in the document metadata DB 116, and FIG. 9C shows a task model. An example of data stored in the DB 114 is shown.

  FIG. 10 is a diagram illustrating a part of each DB after the task is generated. The DB shown in FIG. 10 describes only newly stored portions and omits other data.

  FIG. 10A shows data newly stored in the task instance DB 115, FIG. 10B shows data newly stored in the document metadata DB 116, and FIG. 10C shows related documents. Data newly stored in the DB 113 is shown.

  Here, it is assumed that the user specifies the document ID “http: // docsv / A / business trip application.doc” and instructs task generation. Since the document ID of “http: // docsv / A / business trip application.doc” is not stored in the document metadata DB 116 in FIG. 9B, a document metadata ID “1001” is newly assigned. It is stored in the document metadata DB 116 (see FIG. 10B).

  Next, a document type list is presented to the user via the browser. For example, at least the title of the document type shown in FIG. 9A is presented to the user.

  Next, it is assumed that the user selects “overseas business trip application” from the document type list. The document type ID of the “overseas business application” is “3”, and the task model associated with the document type ID “3” is searched from the task model DB 114. Here, since the task model associated with the document type ID “3” is only “business trip application” with the task model ID “11”, the user selects the task model “business trip application”.

  Next, when the task “business trip application” is generated based on the task model “business trip application”, the task ID “1004” is newly assigned to the task instance DB 115, and the title “business trip application” and the executor “A” And the like are stored (see FIG. 10A).

  Finally, the task ID “1004” and the document metadata ID “1001” are associated and stored in the related document DB 113 (see FIG. 10C).

  As described above, the newly created task ID “1004” is stored in the task instance DB 115 shown in FIG. 10A, and the newly created task ID “1004” is shown in the document metadata DB 116 shown in FIG. The URL “http: // docv / A / business trip application.doc” of the designated document is stored in association with the document metadata ID “1001”, and the related document DB 113 shown in FIG. The task ID “1004” and the document metadata ID “1001” are stored in association with each other.

<Regarding the process of generating a document and task by specifying the document type>
FIG. 11 is a sequence diagram illustrating an example of processing for generating a document and a task by designating a document type. In the processing shown in FIG. 11, the same reference numerals are assigned to the same processing as that in FIG. 7, and description thereof is omitted.

  In step 401, the user requests the workflow management server side for a list of document types via the browser 301.

  Progressing to step 402 following step 401, when the workflow engine 104 receives a request for a document type list from the user via the browser 301 or the GUI providing unit 101, the workflow engine 104 searches the document type DB 117 for the document type list.

  Progressing to step 403 following step 402, the document type DB 117 outputs a document type list to the workflow engine 104 as a search result.

  In step 404 following step 403, the workflow engine 104 presents a document type list to the user via the GUI providing unit 101 and the browser 301.

  Proceeding to step 405 following step 404, the user designates a document type or document name from the document type list and instructs the workflow management server side to create a document via the browser 301.

  Progressing to step 406 following step 405, the workflow engine 104 makes an acquisition request for the designated document type to the document type DB 117. Progressing to step 407 following step 406, the document type DB 117 outputs the requested document type to the workflow engine 104.

  Next, a task model list is presented to the user by performing the processing from step 208 to step 210. In step 408, the user selects a task model via the browser 301. By performing the processing from step 212 to step 213, the workflow engine 104 can acquire the task model specified by the user.

  In step 409, the workflow engine 104 searches the document metadata DB 116 for a document ID corresponding to the template document ID using the template document ID (document metadata ID) associated with the acquired task model.

  In step 410 following step 409, the document metadata DB 116 outputs the retrieved document ID to the workflow engine 104.

  Progressing to step 411 following step 410, the workflow engine 104 instructs the document management system to copy the document based on the document ID.

  Progressing to step 412 following step 411, the document management system copies the instructed document and outputs the document ID of the copied document to the workflow engine 104.

  Progressing to step 413 following step 412, the workflow engine 104 registers the acquired document ID in the document metadata DB 116. At this time, a new document metadata ID is assigned to the document ID to be registered.

  In step 414 following step 413, the document metadata DB 116, when the association between the newly created (duplicated) document ID and the document metadata ID is completed, the workflow metadata together with the document metadata ID assigned to that effect. 104 is notified.

  Progressing to step 415 following step 414, the workflow engine 104 instantiates the task model acquired in step 213 to generate a task and stores it in the task instance DB 115. At this time, if the task model has a tree structure and lower-level task models exist, these task models are also instantiated to generate a task. Therefore, it is possible to generate a task group having a plurality of tasks based on a tree-structured task model.

  In step 416 following step 415, the task instance DB 115 assigns a task ID to the newly created task, and when these storages are completed, the task engine DB 115 informs the workflow engine 104 that the storage is completed along with the assigned task ID. Notice.

  Progressing to step 417 following step 416, the workflow engine 104 associates the document metadata ID notified in step 414 with the task ID notified in step 416 and registers it in the related information DB 113.

  Progressing to step 418 following step 417, the related information DB 113 notifies the workflow engine 104 of the completion of storing the task ID and the document metadata ID.

  Progressing to step 419 following step 418, the workflow engine 109 notifies the user that the creation of the task and the document has been completed via the browser 301.

  As described above, by performing the processing shown in FIG. 11, by specifying the document type, the task model associated with this document type is specified, the document associated with this task model is duplicated, and the task model Tasks can be generated based on Furthermore, it is possible to associate the duplicated document with the generated task. When the task model has a tree structure, a task group similar to this tree structure can be generated.

  FIG. 12 is a diagram illustrating a part of data of each DB when a document and a task are generated. The example shown in FIG. 12 shows a specific example of each DB after the processing shown in FIG. 11 is performed from the state of each DB shown in FIG. The process up to the state of each DB shown in FIG. 12 will be described.

  First, the user selects “international conference paper” from the document type list, and the task model ID associated with “international conference paper” is found from the document type DB shown in FIG. Present “International Conference Paper Submission” with ID “1” to the user.

  Next, when the user selects the task model “Conference paper submission” and instructs the system to create tasks and documents, the task model related to the task model “International conference paper submission” (hereinafter referred to as the related task model). ) To get. The related task model means all the task models in the lower hierarchy of the target task model among the task models represented by a tree structure.

  In the example shown in FIG. 9 (c), all the task models with task model IDs “2” to “13” are the lower-level task models of the task model “Submission of International Conference Papers”. Is the related task model.

  Next, template document IDs (document metadata IDs) associated with all acquired task models are acquired. In the example shown in FIG. 9C, the template document IDs “1” and “2” associated with the task model “Conference submission” and the template document ID “3” associated with the task model “external presentation application” are used. Here, the template document IDs “1” to “6” are acquired.

  Note that two template documents are associated with the task model “international conference paper submission”, and the user may select one. Here, it is assumed that “ACM paper template.tex” having the template document ID “1” is selected.

  Next, a document ID (URL) is specified from the acquired template document ID, a document based on this document ID is copied, and necessary information is corrected. For example, the document ID is corrected from “http: //docsv/xxx/acm.tex” to “http: //docsv/A/acm.tex”. This duplicated document is stored on the document management system side. FIG. 12D shows an example of data in the document management DB 206 at this time. Here, only newly created data is shown for ease of explanation.

  Next, the workflow management system side acquires newly created document IDs (URLs), assigns document metadata IDs to them, and stores them in the document metadata DB 116. FIG. 12B shows an example of data in the document metadata DB 116 at this time.

  Next, a task is generated by instantiating a task model (including a related task model) acquired on the workflow management system side, and stored in the task instance DB 115. FIG. 12A shows an example of data in the task instance DB 115 at this time. Here, a case has been described in which a task is generated as a task group while maintaining a tree structure.

  Finally, the task ID of the generated task and the document metadata ID are associated with each other and stored in the related document DB 113. FIG. 12C shows an example of data in the related document DB 113 at this time. The relationship between the task and the document metadata can be determined by examining the relationship between the task model that is the basis of the task and the document metadata that is the document copy source from the task model DB 114.

  As described above, according to the workflow management system according to the first embodiment, the document in the document management system is associated with the task in the workflow management system while holding the document file on the document management system independently of the workflow management system. Can be managed.

  Also, in the present invention, assuming that a document management server is set up at the head office and a workflow management server is set up at each department, each department generates tasks with reference to documents stored at the head office, You can duplicate the document in and associate it with the task of your department.

  Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. It can be changed.

  Note that the processing contents described in the embodiments can be used as a program, and the above-described processing can be executed as a workflow management system and a workflow management method by causing the computer to execute the program. It is also possible to record the program on a recording medium, cause the computer to read the recording medium on which the program is recorded, and execute the above-described processing as a workflow management system and a workflow management method.

FIG. 3 is a diagram illustrating an example of a hardware configuration of a workflow management SV according to the first embodiment. FIG. 3 is a diagram illustrating an object conceptual diagram according to Embodiment 1. 1 is a block diagram illustrating an example of main functional configurations of a workflow management system and a document management system according to Embodiment 1. FIG. The block diagram which shows the detailed function of a search means. The figure which shows the example of a schema of each database. The sequence diagram which shows an example of the process which searches the task relevant to a document. The sequence diagram which shows an example of the task production | generation process after designating a document. The sequence diagram which shows an example of the process which designates a document type and produces | generates a task. The figure which shows the state of each DB before a task is produced | generated. The figure which shows a part of each DB after the task was generated. The sequence diagram which shows an example of the process which designates a document type and produces | generates a document and a task. The figure which shows a part of data of each DB when a document and a task are produced | generated.

Explanation of symbols

11 Control unit 12 Main storage unit 13 Auxiliary storage unit 14 Network I / F
15 External storage device I / F
16 External device I / F
17 Output device I / F
18 Input device I / F
100 Workflow management system 101, 201 GUI
102, 202 Rendering engine 103, 203 Input / output control unit 104 Workflow engine 105 Search unit 106 Task control unit 107 Task creation unit 108 Task tree holding unit 109 Document metadata control unit 110 Document metadata management unit 111 Document creation instruction unit 112 Database 113 Related Information DB
114 Task model DB
115 Task instance DB
116 Document metadata DB
117 Document type DB
200 Document management system 204 Document search means 205 Document creation means 206 Document management DB
301, 302 Browser 401 Document metadata search means 402 Related task search means 403 Document type search means 404 Task model search means

Claims (10)

A workflow management system that manages a constructive workflow by a management server that includes a database, independent of a document management system that includes a document main body and a document database that stores document identification information for identifying the document,
The management server
A document metadata database for storing document metadata including document identification information stored in the document database;
A workflow management system comprising a related information database that stores a task constituting a workflow and the document metadata in association with each other. The management server
Search means for searching document metadata including the document identification information from the document metadata database based on the document identification information, and searching the related information database for a task corresponding to the searched document metadata. The workflow management system according to claim 1. The management server
A document type database for storing the document metadata in association with a document type indicating the document type;
A task model database storing the document type and the task model in association with each other;
The workflow management system according to claim 2, wherein the search unit searches the document type database for a document type corresponding to the searched document metadata, and searches the task model database for a task model corresponding to the searched document type. . The management server
The workflow management system according to claim 3, further comprising task generation means for instantiating the task model searched by the search means to generate the task. The management server
The workflow management system according to claim 4, further comprising a document creation instruction unit that issues an instruction to copy a document in the document database based on document metadata attached to the task model searched by the search unit. A document storing document metadata indicating bibliographic information including document identification information stored in the document database independently of a document management system including a document main body and a document database storing document identification information for identifying the document A workflow management method in a workflow management system for managing a constructive workflow by a management server comprising a metadata database and a related information database for storing the task and the document metadata in association with each other,
A first search step for searching document metadata including the document identification information from the document metadata database based on the document identification information;
A second search step of searching a task corresponding to the document metadata from the related information database based on the document metadata searched by the first search step;
A workflow management method. The management server
A document type database for storing the document metadata in association with a document type indicating the document type;
A task model database storing the document type and the task model in association with each other;
A third search step of searching the document type database for a document type corresponding to the document metadata searched by the first search step;
The workflow management method according to claim 6, further comprising a fourth search step of searching the task model database for a task model corresponding to the document type searched in the third search step.   The workflow management method according to claim 8, further comprising a task generation step of generating the task by instantiating the task model searched in the fourth search step.   9. The workflow management method according to claim 8, further comprising a document creation instruction step of issuing an instruction to copy a document in the document database based on document metadata attached to the task model searched in the fourth search step.   A workflow management program for causing a computer to execute the workflow management method according to claim 6.

Images