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

Abstract

<P>PROBLEM TO BE SOLVED: To relate and manage documents in a document management system and tasks in a workflow management system while holding document files on the document management system independently of the workflow management system, and to easily generate a task starting at a document in the document management system. <P>SOLUTION: In a workflow management system, a management server includes a task storage means 114 of storing task information, a document metadata storage means 116 of storing document metadata, a relation information storage means 113 of relating and storing tasks constituting a workflow and document metadata, an accepting means 103 of accepting specification of a document, a retrieval means 105 of retrieving a task related to document metadata from the task storage means on the basis of document metadata corresponding to the same document or a document similar to the document, and a generation means 107 of generating a task corresponding to the accepted document on the basis of the retrieved task. <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 created 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 create 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 of the present invention to provide a workflow management system, a workflow management method, and a workflow management program that can be managed in association with each other and easily create a task starting from a document in the document management system.

  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 task storage unit that stores task information including bibliographic information of tasks and a hierarchical structure between tasks, and a document meta that includes document identification information stored in the document database. Document metadata storage means for storing data, related information storage means for storing the tasks constituting the workflow and the document metadata in association with each other, a reception means for receiving a document specification, and a document received by the reception means Based on document metadata corresponding to the same or similar document Search means for searching for a task associated with the document metadata from the task storage means, and creation means for creating a task corresponding to the accepted document based on the task searched by the search means; .

  In addition, the workflow management method according to another aspect of the present invention provides a bibliographic information of tasks and a hierarchy between tasks independently of a document management system including a document main body and a document database storing document identification information for identifying the document. Task storage means for storing task information including a structure, document metadata storage means for storing document metadata including document identification information stored in the document database, tasks constituting a workflow, and the document metadata, And a related information storage means for storing the information in association with each other, and a workflow management method in a workflow management system for managing a constructive workflow by a management server comprising: a reception step for receiving a document specification; Document meta that corresponds to a document that is the same or similar to the document Based on the data, a search step that searches the task storage means for a task associated with the document metadata, and a task corresponding to the accepted document is created based on the task searched by the search step And a creation 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, while having a document file on the document management system independently of the workflow management system, the document in the document management system and the tasks in the workflow management system are associated with each other and managed. It is possible to provide a workflow management system, a workflow management method, and a workflow management program that can easily create a task starting from a document.

  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 concept in 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, and document metadata, 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.

  First, the workflow management system side will be described. The task model is a generalized and abstracted task. In order to create a task by instantiating this task model, this task model is associated with the task (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 referenced is attached to the task model or task. Since the document itself is managed in the document management system, in this system, document metadata, Tasks and task models are associated (solid line).

  The document in the document management system is associated with the document metadata in the workflow management system (dashed 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 reconfiguration from an existing task model and / or task instance. It includes a workflow engine 104 that dynamically creates and executes a workflow model by use, and various databases 112 (hereinafter referred to as “DB”).

  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, Document metadata DB 116 for storing document metadata indicating bibliographic information of the document, task access information DB 117 for storing access information including browsing information and / or update history information for tasks, and information on the organization to which the user belongs The organization information DB 118 is provided. Note that the organization information DB 118 is not necessarily provided in the workflow management system 100, and may be provided outside so that the organization information can be acquired when necessary. 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 118, a task control unit 106 that controls tasks constituting the workflow, a document metadata control unit 110 that controls document metadata, It has.

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

  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, and a task model search unit 403.

  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 task model search means 403 searches for the task model from the task model DB 114 based on the task ID for identifying the task.

  Returning to FIG. 3, the task control unit 106 includes a task creation unit 107 that creates a task, a task tree retention unit 108 that retains a tree structure of tasks, and a task that records access information that is a task record and update history. And an access recording unit 109.

  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 118 in accordance with an instruction from the user A.

  The document metadata control unit 110 includes a document metadata management unit 111 that manages document metadata. The document metadata management unit 111 acquires bibliographic information of a newly created document, and manages document metadata by newly assigning a document metadata ID.

  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 and a document name from the user B via the browser 302, and performs the same or similar document search based on the search key. The document search unit 204 also searches for a document when a document search request is received from the workflow management system 100 side.

  The document management DB 205 stores documents. The data structure in the document management DB 205 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.

  FIG. 5 is a block diagram showing an example of functions according to the present invention. As shown in FIG. 5, the workflow management system includes a reception unit 501, a search unit 502, a display unit 503, a selection unit 504, a duplication unit 505, and a creation unit 506.

  The accepting unit 501 (corresponding to the input / output control unit 103) accepts designation of a document. Specifically, a document ID for identifying a document is specified and / or input by the user via the browser 301, and the document ID is received.

  The search unit 502 (corresponding to the search unit 105) searches the document metadata DB 116 for document metadata corresponding to the document ID based on the document ID received by the receiving unit 501. Next, based on the retrieved document metadata, a task corresponding to this document metadata is retrieved from the related information DB 113.

  The display unit 503 (GUI providing unit 101) displays a list of tasks searched by the search unit on the display screen. A selection unit 504 (corresponding to a selection function included in the GUI providing unit 101) allows a user to select a task from the task list displayed by the display unit 503.

  The duplicating unit 505 (corresponding to the task creation unit 107) duplicates the task selected by the selecting unit 504. At this time, only the selected task may be duplicated, or a subtask (child task) of the selected task may be duplicated.

  The creation unit 506 (corresponding to the task creation unit 107) creates a task and a subtask based on the task and subtask duplicated by the duplication unit 505 (here, the subtask is also duplicated). Specifically, with respect to the duplicated task, a task that needs to be corrected (hereinafter referred to as “necessary item”) is corrected and created. Necessary items are task ID, subtask, and parent task information.

  In the example shown in FIG. 5, the configuration shown in FIG. 5 is divided for easy understanding, but the configuration shown in FIG. 5 is not necessarily required, and the duplication unit 505 and the creation unit 506 are combined. Any configuration may be used as long as it has the functions described above, such as a single configuration.

  The accepting unit 501 may accept the designation of a document designated on the document management system 200 side, and each terminal PC and each management SV are assumed to be connected via a network.

<About the schema of each database>
FIG. 6 is a diagram illustrating a schema example of each database. 6A is a schema example of the document management DB 206, FIG. 6B is a schema example of the document metadata DB 116, FIG. 6C is a schema example of the related information DB 113, and FIG. An example schema of the task model DB 114 and FIG. 6E are diagrams showing an example schema of the task instance DB 115.

  As shown in FIG. 6A, 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. 6B, the document metadata DB 116 in the workflow management system stores a document metadata ID, which is information for identifying document metadata, and a URL, which is a document ID, in association with each other. .

  As shown in FIG. 6C, 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. 6D, the task model DB 114 in the workflow management system stores a task model ID, a subtask (child task) ID, a task ID, and the like in association with each other.

  As shown in FIG. 6E, 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.

  Although not shown in FIG. 6, the task access information DB 117 includes, for each task ID, browsing information such as a user who browsed this task, date, and number of times, and update history information such as date and number of times of updating this task. Are stored in association with each other.

  Further, the organization information DB 118 stores organization information indicating an organization to which the user belongs, using a user ID for identifying the user. For example, the organization information is stored using a tree structure that becomes a lower layer in the order of group, team, and user so that the proximity of the users in the organization can be obtained.

  Organizational proximity is the order in which the organization is in order, in the same team, different teams but in the same group, different teams and groups, but the same center (office), different teams, groups, and centers. . As a result, the proximity of the organization can be determined using the organization information.

<About task creation processing (part 1)>
FIG. 7 is a sequence diagram illustrating an example (part 1) of task creation processing after a document is designated. As shown in FIG. 7, in step 101, the user instructs the workflow management system 100 to create a task by specifying a document via the browser 301.

  In the following description, the task creation instruction is issued using the browser 301. However, the task creation instruction may be issued from the document management system 200 side to the workflow management system 100 side using the browser 302.

  In step 102 following step 101, the workflow engine 104 makes a search request to the document management system 200 in order to acquire a document that is the same and / or similar to the specified document in accordance with the task creation instruction of the user.

  In step 103 following step 102, the document management system 200 searches for the same and / or similar documents based on the document ID of the document specified from the document management DB 205, and uses the document list as a search result as a workflow. Output to engine 104.

  At this time, the means for searching for similar documents is provided on the document management system 200 side, but means for searching for similar documents on the workflow management system side may be provided. In addition, when both systems do not have a means for searching for similar documents, only the same document may be returned as a search result.

  In the case where a means for searching for similar documents is provided on the document management system 200 side, it can be implemented using existing techniques such as a vector space model and a TF / IDF model. In addition, when a means for searching for similar documents is provided on the workflow management system 100 side, it becomes a format having a search index outside the document management system, and can be implemented using existing technology such as Google Desktop (registered trademark). It is.

  Progressing to step 104 following step 103, 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 list acquired from the document management system 200.

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

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

  Progressing to step 107 following step 106, the related information DB 113 outputs a task ID to the workflow engine 104 as a search result.

  Progressing to step 108 following step 107, the workflow engine 104 searches the task instance DB 115 for a task corresponding to the task ID based on the task ID acquired from the related information DB 113.

  Progressing to step 109 following step 108, the task instance DB 115 outputs a list of tasks to the workflow engine 104 as a search result.

  In step 110 following step 109, the workflow engine 104 searches the task access information DB 117 for task browsing information and update history information acquired from the task instance DB 115.

  Progressing to step 111 following step 110, the task access information DB 117 outputs task browsing information and update history information to the workflow engine 104 as search results.

  Progressing to step 112 following step 111, the workflow engine 104 sorts the tasks based on the acquired browsing information and update history information, and presents the sorted tasks to the user as a task template list. As for sorting, sorting is performed so that tasks with a large number of browsing times and / or tasks updated to the latest are displayed at the top.

  In step 113 following step 112, the user selects a task from the task template list via the browser 301, and the selected task is notified to the workflow management system 100 side.

  Progressing to step 114 following step 113, the workflow engine 104 duplicates the notified task and its subtask, corrects necessary items, creates a task, and stores the task in the task instance DB 115.

  Progressing to step 115 following step 114, the task instance DB 115 notifies the workflow engine 104 of the completion of storage (storage) of the created task and subtask.

  Progressing to step 116 following step 115, the workflow engine 104 accesses the task access information DB 117 to update the creation history of the created task, the browsing history information of the copy source, and the like.

  Progressing to step 117 following step 116, the workflow engine 104 stores the created task and document metadata in association with each other in the related information DB 113.

  In step 118 following step 117, the related information DB 113 notifies the workflow engine 104 of the completion of storing the task and document metadata. Progressing to step 119 following step 118, the workflow engine 104 notifies the user through the browser 301 that the creation of the task has been completed.

  As described above, when creating a task by designating a document by performing the process shown in FIG. 7, the tasks are sorted based on the access information including the task browsing information and the update history information, and the sorted task is presented to the user. Then, by selecting a task as a template, it is possible to easily create a task based on the latest updated task or a task with a large number of browsing.

<About task creation processing (part 2)>
FIG. 8 is a sequence diagram illustrating an example (part 2) of task creation processing after a document is designated. In the processing shown in FIG. 8, the same processing as that shown in FIG. 7 is denoted by the same reference numeral and description thereof is omitted. In the process shown in FIG. 8, tasks are sorted based on organization information.

  In step 201, the workflow engine 104 searches the organization information DB 118 for the proximity of the organization. Specifically, the organization information between the user who designated the document and instructed the task creation and the user who created the task in the task list in step 109 is searched.

  Progressing to step 202 following step 201, the organization information DB 118 outputs the organization information to the workflow engine 104 as a search result.

  Following step 202, the process proceeds to step 203, where the workflow engine 104 sorts the tasks in the order in which the users who are instructed to create are sorted based on the acquired organization information, and after sorting the tasks. Are presented to the user as a task template list.

  The subsequent processing is the same as the processing shown in FIG. As described above, by performing the process shown in FIG. 8, when creating a task by designating a document, the task is sorted based on the organization information, and the sorted task is presented to the user to select a template task. Thus, task creation can be performed based on a task created by a user who is organizationally close to the user who creates the task.

  The task rearrangement (sorting) shown in FIGS. 7 and 8 is not necessarily required, and the searched tasks may be displayed without sorting. Further, sorting may be performed by allowing the user to select which one to use for sorting.

<Specific examples of task creation>
Next, a specific example of task creation in the present invention will be described with reference to FIGS. In a scenario for creating a task, a request for “inventory of fixed assets” is distributed to all groups from a user “AAA” by e-mail. FIG. 9 is a diagram illustrating an example of an electronic mail. As shown in FIG. 9, inventory of fixed assets is requested in the text of the mail.

  Next, the member “BBB” receiving the mail as shown in FIG. 9 creates a “fixed asset inventory” task and stores it in the related information DB 113 in association with the mail ID (URL). The mail is stored in the mail DB (corresponding to the document management DB 205). In addition, the member “BBB” creates a link to the fixed asset inventory format and a link to the inventory procedure manual in the task.

  FIG. 10 is a diagram illustrating an example of a task created by “BBB”. As shown in FIG. 10, the task “Fixed asset inventory” includes related documents “2007-2.xls” (fixed asset inventory format), “workflow.doc” (inventory procedure manual), “Request for fixed asset inventory”. ”(Email). The association of related documents is performed using document metadata. The document body of the related document is stored in the DB of the document management system independent of the workflow management system.

  In addition, a subtask “send reminder to unexecuted person” is created in the task “inventory of fixed assets”.

  Next, the member “CCC” who received the mail from “AAA” in the same manner as “BBB” tries to create a task based on this request mail. At this time, “CCC” acquires the document metadata based on the document ID of this mail, and searches the related information DB 113 for a task corresponding to this document metadata.

  As a result of the search, “CCC” finds that the task created by “BBB” is associated with this document metadata. Next, when “CCC” instructs the workflow management system 100 to create a task, the task created by “BBB” is duplicated, necessary items are corrected, and a task “CCC” is created.

  FIG. 11 is a diagram illustrating an example of a task created by duplicating “CCC”. As shown in FIG. 11, link information and subtasks created by “BBB” are copied as they are, and items such as the creator and creation date are corrected.

  FIG. 12 is a diagram illustrating an example of each DB after “BBB” has created a task. 12A shows an example of the data structure in the document metadata DB 116, FIG. 12B shows an example of the data structure in the task instance DB 115, and FIG. 12C shows in the related document DB 113. It is a figure which shows an example of this data structure.

  As shown in FIG. 12A, the document metadata DB 116 includes a document ID “1001”, a title “2007-2.xls”, and a URL “http: //xxx/inventory/2007-2.xls”. Etc. are stored in association with each other.

  As shown in FIG. 12B, the task instance DB 115 stores a task ID “2001”, a title “fixed asset inventory”, an executor “BBB”, and the like associated with each other.

  As shown in FIG. 12C, the related document DB 113 stores a task ID “2001” and a document metadata ID “1001” in association with each other.

  FIG. 13 is a diagram illustrating an example of each DB after “CCC” has created a task. FIG. 13A shows an example of the data structure in the task instance DB 115, and FIG. 13B shows an example of the data structure in the related document DB 113.

  As shown in FIG. 13A, a task “CCC” is added to the task instance DB 115 from the state shown in FIG. For example, a title “inventory for fixed assets” associated with the task ID “2003” is added.

  As shown in FIG. 13B, the related information DB 113 is added with document metadata of a document related to the task added to the task instance DB 115 from the state shown in FIG. 12C. For example, a task ID “2003” and a document metadata ID “1001” are added.

  Here, the task ID “2003” is a duplicate of the task ID “2001”, and the link information of the task with the task ID “2001” is duplicated as it is, so even after the task is duplicated The document metadata DB 116 is the same as that shown in FIG.

  As described above, when a workflow is started from an information medium managed independently from the workflow management system such as an e-mail or an electronic bulletin board, the task can be easily created based on the task associated with the information medium. It can be carried out.

<About task creation processing (part 3)>
FIG. 14 is a sequence diagram illustrating an example (part 3) of the task creation process after the document is designated. In the processing shown in FIG. 14, the same reference numerals are assigned to the same processing as that in FIG. 7, and description thereof is omitted.

  In step 301, the workflow engine 104 searches the task model DB 114 for a task model associated with this task based on the task acquired from the task instance DB 115.

  Progressing to step 302 following step 301, the task model DB 114 outputs a task model list to the workflow engine 104 as a search result.

  Progressing to step 303 following step 302, the workflow engine 104 presents the task model list acquired from the task model DB 114 to the user via the browser 301 as a task model template list.

  In step 304 following step 303, the user selects a task model via the browser 301, and the selected task model is notified to the workflow management system 100.

  Proceeding to step 305 following step 304, the workflow engine 104 makes a request to acquire the selected task model to the task model DB 114.

  Proceeding to step 306 following step 305, the task model DB 114 outputs the task model for which an acquisition request has been made to the workflow engine 104. At this time, if the task model has a subtask model (child task model), the subtask model is also output to the workflow engine 104.

  Progressing to step 307 following step 306, the workflow engine 104 instantiates these based on the task model and subtask model acquired from the task model DB 114, thereby creating a task and subtask. The workflow engine 104 outputs the created task and subtask for storage in the task instance DB 115.

  Progressing to step 308 following step 307, the task instance DB 115 notifies the workflow engine 104 to that effect when storing the created task and subtask.

  Step 117 and subsequent steps are the same as the processing shown in FIG. As described above, by performing the process shown in FIG. 14, when creating a task by designating a document, by presenting a task model as a template instead of presenting a task associated with the document as a template, the user can Tasks can be easily created by instantiating a task model.

  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 content described in the embodiment can be a program, and the program can be executed by a computer to cause the task management system and the task management device to execute the above-described processing. 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 cause the task management system and the task management apparatus to execute the processing described above.

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 concept in Embodiment 1. 1 is a block diagram illustrating an example of main functional configurations of a workflow management system 100 and a document management system 200 according to Embodiment 1. FIG. The block diagram which shows the detailed function of a search means. The block diagram which shows an example of the function which concerns on this invention. The figure which shows the example of a schema of each database. The sequence diagram which shows an example (the 1) of the task generation process after designating a document. The sequence diagram which shows an example (the 2) of a task generation process after designating a document. The figure which shows an example of an email. The figure which shows an example of the task which BBB created. The figure which shows an example of the task which CCC duplicated and created. The figure which shows an example of each DB after BBB creates a task. The figure which shows an example of each DB after CCC created the task. The sequence diagram which shows an example (the 3) of a task production | generation process after designating a document.

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
DESCRIPTION OF SYMBOLS 100 Workflow management system 101, 201 GUI provision part 102, 202 Rendering engine 103, 203 Input / output control part 104 Workflow engine 105 Search engine 106 Task control part 107 Task creation part 108 Task tree holding part 109 Task access recording part 110 Document metadata Control unit 111 Document metadata management means 112 Database 113 Related information DB
114 Task model DB
115 Task instance DB
116 Document metadata DB
117 Task access information DB
118 Organization Information DB
200 Document Management System 204 Document Retrieval Means 205 Document Management DB
301, 302 Browser 401 Document metadata search means 402 Related task search means 403 Task model search means 501 Acceptance means 502 Search means 503 Display means 504 Select means 505 Duplicate means 506 Create 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
Task storage means for storing task information including bibliographic information of tasks and a hierarchical structure between tasks;
Document metadata storage means for storing document metadata including document identification information stored in the document database;
Related information storage means for storing the tasks constituting the workflow and the document metadata in association with each other;
Accepting means for accepting specification of a document;
A search unit that searches the task storage unit for a task associated with the document metadata based on document metadata corresponding to a document that is the same as or similar to the document received by the receiving unit;
Creating means for creating a task corresponding to the accepted document based on the task searched by the searching means;
A workflow management system comprising: The management server
Display means for displaying the task searched by the search means;
Selecting means for selecting a task displayed by the display means;
Duplicating means for duplicating the task selected by the selecting means,
The creating means includes
2. The workflow management system according to claim 1, wherein a task corresponding to the accepted document is created based on the task copied by the copying unit. The management server
Access information storage means for storing access information including task browsing information and / or update history information;
The display means includes
The workflow management system according to claim 2, wherein the searched task is displayed based on access information stored in the access information storage unit. The display means includes
The workflow management system according to claim 2, wherein the searched task is displayed based on organization information indicating organization information to which the user belongs, stored in the organization information storage unit. The display means includes
The workflow management system according to claim 4, wherein an organization to which the user who created the searched task belongs belongs is displayed in an order closer to the organization to which the user who specified the document belongs. The management server
It further comprises a task model storage means for associating and managing task identification information for identifying a task and a task model,
The search means includes
Based on the task identification information of the retrieved task, a task model corresponding to the task identification information is retrieved from the task model storage means,
The creating means includes
6. The workflow management system according to claim 1, wherein a task corresponding to the accepted document is created based on a task model searched by the search unit. The creating means includes
The workflow management system according to any one of claims 1 to 5, wherein when a task to be created includes a subtask, a task and a subtask corresponding to the accepted document are created based on the task and the subtask. . The creating means includes
7. The workflow management according to claim 6, wherein when a task model searched by the search means includes a subtask model, a task and a subtask corresponding to the accepted document are created based on the task model and the subtask model. system. A task storage means for storing task information including bibliographic information of tasks and a hierarchical structure between tasks, independent of a document management system comprising a document main body and a document database for storing document identification information for identifying the document; Document metadata storage means for storing document metadata including document identification information stored in the document database, and related information storage means for storing a task constituting a workflow and the document metadata in association with each other. A workflow management method in a workflow management system for managing a constructive workflow by a management server,
A reception step for accepting specification of a document;
A retrieval step for retrieving a task associated with the document metadata from the task storage unit based on document metadata corresponding to a document that is the same as or similar to the document accepted by the acceptance step;
A creation step for creating a task corresponding to the accepted document based on the task searched in the search step;
A workflow management method.   A workflow management program for causing a computer to execute the workflow management method according to claim 9.

Images