Workflow management device and method

Abstract

To aggregate situations of related workflow.SOLUTION: A transcription unit 505 extracts data and transcribes the data to an aggregated document management unit 503 when generated data is a propagation target in a case where a workflow execution unit 404 executes workflow. The aggregated document management unit 503 holds the transcribed data in association with an aggregated document. An aggregated document generation unit 5032 performs list output in an aggregated document output unit 504 for each check point by including the transcribed data to be aggregated in the aggregated document or the calculation result thereof in the check point time when there is an output request (browsing request) of the aggregated document at the designated one or plurality of check point times.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present invention relates to a workflow management device and method, and is particularly suited to providing an overview of the progress of one or more related workflows. [Background technology]

[0002] It is known that when managing a workflow, each process is displayed over time to display the progress status (JP Patent Publication 2014-96182 A). It has also been proposed that when a workflow includes a sub-workflow, the sub-workflow can also be managed (JP Patent Publication 2018-109889 A).

[0003] When multiple workflows are deployed simultaneously to carry out business, it is desirable to present the progress of the workflows in an optimal manner. It is also desirable to display specific figures along with the progress of the workflows, such as the amount of work related to store management and the cost of fixtures, as the results and burdens. It is also desirable to display the history of specific data in an aggregated manner.

[0004] In project management, there is generally a budget, and it is necessary to manage how the budget is consumed over time. In budget execution, there is an order date, a settlement date, and a payment date for each order unit, and each date has a plan and actual results. In order decision-making, the order date and the planned payment date are entered in each workflow application, so it is not impossible to grasp the budget consumption status and cash flow status at any point in time. However, the data entered into the accounting system is past data that has already occurred, so it is difficult to grasp the situation at any point in time, including in the future. In a workflow system, it is desirable to update documents that are aggregated for the entire project according to the progress of the workflow related to individual orders at the line level, and to retain the history each time the document is updated, so that the "present" as seen from any point in time and the "future" as a forecast at that point in time can be referenced.

[0005] It should be noted that the present invention should not be understood as being limited by the above-mentioned problems, and the contents thereof are defined in the claims and will be described in detail below using examples. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2014-96182 A [Patent Document 2] JP 2018-109889 A Summary of the Invention [Problem to be solved by the invention]

[0007] It is desirable to be able to get an overview of the status of multiple related workflows and, at any given point in time, to be able to grasp the "present" or the "future" as a forecast at that point in time. [Means for solving the problem]

[0008] Before describing the invention in detail, a supplementary explanation will be given regarding the claims.

[0009] According to the present invention, in order to achieve the above object, the configurations as recited in the claims are adopted.

[0010] According to one aspect of the present invention, a workflow management device is provided with: aggregate document management means for managing aggregate documents; associating means for associating a workflow instance with the aggregate document; workflow execution means for executing the workflow instance; propagation means for propagating to the aggregate document specific generation data generated during execution of the workflow instance when specific generation data of the workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated into the aggregate document; and output means for outputting the aggregate document managed by the aggregate document management means, wherein the output of the aggregate document includes a display based on the generation data propagated to the aggregate document, and the output means is configured to have: means for specifying a plurality of checkpoint times; and display means for displaying a list of displays based on the generation data to be aggregated into the aggregate document at each of the specified plurality of checkpoint times, distinguishing them for each checkpoint time.

[0011] According to this configuration, when viewing a workflow at a glance, if there are related workflows, they can be viewed together, specific data can be displayed together, and data for multiple time periods of interest can be compared and understood.

[0012] Here, the aggregate document may be any document that displays contents that should be understood collectively while focusing on a specific aspect, and may be named, for example, "case document," "company document," "report document," or other names that express such contents. The document may also be an electronic document that is generated based on various description rules. The aggregate document may typically be output by viewing it using a browser or printing it using a printer.

[0013] In this configuration, the checkpoint times may be expressed in days.

[0014] Additionally, the checkpoint time may be a time in the past, present, or future.

[0015] Also, a means for designating a manner in which the generated data is displayed on the display means may be further provided.

[0016] According to another aspect of the present invention, a workflow management device is provided with: aggregate document management means for managing an aggregate document; associating means for associating a workflow instance with the aggregate document; workflow execution means for executing the workflow instance; propagation means for propagating to the aggregate document specific generation data generated during execution of the workflow instance when specific generation data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated into the aggregate document; and output means for outputting the aggregate document managed by the aggregate document management means, wherein the output of the aggregate document includes a display based on the generation data propagated to the aggregate document, and the output means is configured to include: checkpoint time determination means for determining at least a portion of checkpoint times based on time information included in the specific generation data propagated to the aggregate document; checkpoint time display means for displaying the checkpoint times; checkpoint time designation means for designating one or more checkpoint times among the checkpoint times; and display means for performing a display based on the generation data to be aggregated into the aggregate document at the checkpoint time based on the designated checkpoint time.

[0017] According to this configuration, when viewing workflows at a glance, if there are related workflows, they can be viewed together and specific data can be displayed. Furthermore, multiple candidate times of interest (checkpoint times) can be automatically determined and the user can be prompted to select one, making it easy to present aggregated data for the times of interest.

[0018] In this configuration, the checkpoint time may include the current time as a default checkpoint time.

[0019] Furthermore, the time information for determining at least some of the checkpoint times based on time information included in the predetermined generation data may include scheduled time information and actual time information.

[0020] It goes without saying that the present invention can be realized not only as an apparatus or system invention, but also as a method or program invention.

[0021] Furthermore, to the extent that it is not unreasonable to combine the respective parts of each embodiment, it goes without saying that such combinations also constitute part of the present invention. Effect of the Invention

[0022] According to the present invention, the status of related workflows can be viewed in an integrated manner. [Brief description of the drawings]

[0023] [Figure 1] 1 is a diagram showing an overall hardware configuration that constitutes a workflow management system 10 according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing a functional configuration of a workflow management system 10 according to an embodiment of the present invention. [Diagram 3] 11 is a flowchart illustrating an example of the operation of the aggregate document generating unit 502 of the workflow management system 10 according to the embodiment of the present invention. [Figure 4] 13 is a diagram for explaining an example of a usage screen of the aggregate document generation unit 502. FIG. [Diagram 5] FIG. 13 is a diagram illustrating an example of the use of an aggregate document. [Figure 6] 11 is a flowchart illustrating an example of workflow generation. [Figure 7] 13 is a flowchart illustrating an example of specifying propagation data when a workflow is generated. [Figure 8] FIG. 2 is a diagram illustrating an example of the overall operation of a workflow management system. [Figure 9] FIG. 10 is a diagram illustrating an example of aggregating data of a plurality of workflows. [Figure 10] FIG. 13 is a diagram illustrating an example of aggregating data history of one workflow. [Figure 11] FIG. 5 is a block diagram showing an example of a functional configuration of an aggregate document generation unit 5032 according to an embodiment of the present invention. [Figure 12] 12 is a flowchart illustrating an example of the operation of the aggregate document generating part 5032 in FIG. 11. [Figure 13] 12 is another flowchart illustrating an example of the operation of the aggregate document generating unit 5032 in FIG. [Figure 14] 12 is a schematic diagram illustrating an example of the operation of the aggregate document generator 5032 in FIG. 11. [Figure 15] 12 is another schematic diagram illustrating an example of the operation of the aggregate document generator 5032 in FIG. 11. FIG. [Figure 16] FIG. 12 is a diagram showing an example of an output screen by the aggregate document generating unit 5032 of FIG. [Figure 17] FIG. 12 is a diagram showing another example of an output screen by the aggregate document generating unit 5032 of FIG. [Figure 18] FIG. 12 is a diagram showing another example of an output screen by the aggregate document generating unit 5032 of FIG. [Figure 19] FIG. 12 is a diagram showing another example of an output screen by the aggregate document generating unit 5032 of FIG. [Figure 20] FIG. 13 is a block diagram illustrating a modified example of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] A workflow management system 10 according to an embodiment of the present invention will now be described with reference to the drawings.

[0025] FIG. 1 shows the system configuration of a workflow management system 10 according to an embodiment of the present invention. In this figure, the workflow management system 10 includes a group of applications 100, such as a document management server 101, a workflow server 102, a database management server 103, a mail server 104, and a web server 105. The group of applications 100, such as the servers 101 to 105, run on an operating system 110 and may be distributed among multiple computers. A computer 120 includes hardware resources such as a processor 121, a main memory 122, and an input / output interface, and the operating system 110 and the group of applications 100 are realized by installing a program 123. In addition to realizing normal workflow processing, the workflow management system 10 allows the progress of one or more selected workflows to be viewed in an integrated manner based on specific data, and its functional blocks will be described later with reference to FIG. 2, FIG. 11, and the like.

[0026] The workflow management system 10 is connected to a user's host terminal 300 via a communication network 200 such as a LAN. The user may use the host terminal 300 to utilize the workflow management system 10 (document management server 101, workflow server 102, database management server 103, mail server 104, web server 105, etc.).

[0027] FIG. 2 shows the functional configuration of the workflow management system 10 of FIG. 1. In FIG. 2, a workflow template holding unit 401, a workflow instance generating unit 402, a workflow instance holding unit 403, and a workflow executing unit 404 constitute a workflow processing unit 400 to realize workflow processing. Here, a workflow instance may be simply called a workflow. A workflow instance may be generated based on a workflow template. The workflow instance generating unit 402 is generated by an input operation by a user through a workflow instance generating screen. For example, as shown in FIG. 6, a template is selected (step S20), and then values ​​are input into the template (step S22) and registered. The workflow template holding unit 401 holds a workflow template for each type of workflow, and this workflow template is composed of various parts such as user activities and conditional branches, and a workflow instance may be generated by inputting values ​​through the form of this template. As will be described later, when a workflow instance is generated from a template, new parts may be added in addition to the parts originally included in the template to perform modification. In addition, the workflow instance may be recursively associated with a lower workflow instance. Although the amount of work increases, a workflow instance may be generated without using a workflow template.

[0028] The registered workflow instance is held in a workflow instance management unit 403 and executed by a workflow execution unit 404. Specifically, the workflow execution unit 404 is realized by the document management server 101, the workflow server 102, the database management server 103, the mail server 104, the web server 105, etc., and executes the workflow instance by using these in a composite manner.

[0029] 2, the workflow management system 10 includes, in addition to the workflow processing unit 400, an aggregate document template storage unit 501, an aggregate document generation unit 502, an aggregate document management unit 503, an aggregate document output unit 504, a transcription unit 505, and the like. The aggregate document generation unit 502 creates an aggregate document from an aggregate document template stored in the aggregate document template storage unit 501 through the screen of the aggregate document template T01 in FIG. 4. Although the name "aggregate document" is used here, it is not limited to a document that associates multiple workflows as described later, and may be a document that associates one workflow. The "aggregate document" may be any document that displays contents that should be understood collectively or in an aggregated manner with a focus on a specific aspect, and may be named, for example, "case document," "collective document," "report document," or any other name that suits such contents.

[0030] The aggregate document generation unit 502 generates an aggregate document, for example, as shown in FIG. 3. In FIG. 3, to generate an aggregate document, a template is selected (S10). Templates may be prepared for various business operations. The template example (aggregate document generation screen) T01 in FIG. 4 can be used for the business of store management, for example. The aggregate document template may be composed of various parts, similar to the workflow template. Typical parts for each business operation may be prepared for the aggregate document template, and various modifications such as adding parts may be made when creating the template (S11). After this, values ​​are input (S12), and one or more workflows are associated with the aggregate document (S13 to S15). The workflow (workflow template) to be associated with the aggregate document may be registered in the aggregate document template, or may be modified to be associated when the aggregate document is generated. In the association of workflows, first, it is determined whether or not there is any workflow to be associated with the aggregate document and aggregated (S13), and if there is a workflow to be associated, the process proceeds to step S14 (always proceeds to step S14 in the first workflow association), and a workflow instance is generated using the workflow instance generating unit 402 (FIG. 2). For example, in the aggregate document template T01 in FIG. 4, the workflow selection option button T02 is operated to select the corresponding workflow template, and values ​​are input using the workflow template ("ordering process"), and then the workflow instance is registered (S14, S15). The workflow template to be associated (for example, the workflow template of "ordering process") may be set in advance in the aggregate document template. In this case, the option button T02 may be operated to omit the selection of the workflow template, and values ​​may be input (and correction processing may be performed if necessary) immediately for the desired workflow template. After this, the process returns to step S13, and the processes of steps S13 to S15 are repeated until all workflow instances to be associated with the aggregate document are registered.In step S13, when all the workflow instances to be associated with the aggregate document have been associated, proceed to step S16, where a formula fx (e.g., a total SUM) for the data propagated from the workflow instances associated in Fig. 4 may be entered in the formula input field T04, and the option button T03 in Fig. 4 may be operated to specify the display format when the aggregated data is displayed in a graph, after which the aggregate document is registered (S17), and the process ends. The formula fx may be a variety of formulas such as a total, an average, etc., and may include a formula that outputs the data as is. The display format may specify numbers, units, chart type, etc.

[0031] In the example of the aggregate document generation flow shown in Fig. 3, the order of the processing steps may be changed as appropriate. For example, the value input (S12) may be performed before the template modification process (S11), before or after the calculation formula and display format specification (S16), or each process may be performed together.

[0032] Incidentally, when a workflow instance is generated from a template, it may be modified by adding new parts in addition to the parts originally included in the template. In addition, the workflow instance may be recursively associated with lower workflow instances. A higher workflow instance may be adopted as an aggregate document for the lower workflow instances. Recursive association may be performed in multiple stages.

[0033] The aggregate document management unit 503 holds the aggregate document generated by the aggregate document generation unit 502 and manages various variables related to the aggregate document. The aggregate document output unit 504 outputs (views and prints) the aggregate document managed by the aggregate document management unit 503 based on a request from a user. The transcription unit 505 propagates data that is generated when a workflow instance is executed and associated with the aggregate document to the aggregate document side. That is, the transcription unit 505 propagates data marked to be propagated to the workflow instance to the aggregate document side, for example, the value of a variable (such as X in FIG. 8) on the workflow instance side as the value of a corresponding variable (such as Y in FIG. 8) of the aggregate document, and may be implemented by inserting an event handler component into the workflow instance. The event handler is not limited to an event handler, and any means for monitoring a specific data input in a workflow instance and propagating data may be used. The data propagation may be an additional write or an update write, and may be selected according to the purpose.

[0034] A workflow template for generating a workflow instance associated with an aggregate document may be configured to mark in advance that the data to be propagated to the aggregate document is a target for propagation in relation to a user's activity of inputting the data. For example, the workflow template may include an event handler component in a predetermined position in advance. However, if the template does not include a component such as an event handler in advance, the user may add an event handler component in a desired position and specify propagation data to aggregate a workflow instance (S23), as shown in FIG. 7.

[0035] Next, the operation of the workflow management system of this embodiment will be described mainly with reference to FIG.

[0036] 8 explains the processing between the aggregate document output unit 504, the aggregate document generation unit 502, the aggregate document management unit 503, the workflow execution unit 404, and the host terminals 300 of user 1 (1001), user 2 (1002),...user m (100m), and user n (100n). Here, the user's host terminals 300 are simply referred to as users. User 1 (1001), user 2 (1002),...user m (100m) are users who process the workflow instance of this example, and user n (100n) is the user who requests aggregate document printing. Each user may have authority according to the operation.

[0037] In Fig. 8, the aggregate document generation unit 502 generates an aggregate document (X30), and at this time generates an associated workflow instance (X31). When multiple workflow instances are associated, those workflow instances are generated and the same process is repeated. This is indicated by the dashed line (X31).

[0038] When a workflow instance is generated in X31, an exchange (activity) X32 occurs between the workflow execution unit 404 and users 1001, 1002, ... 100m. 1 , X32 2 ,...X32 m For example, activity X32 m In the example, user m generates data to be propagated. This data to be propagated is propagated (X33) to aggregate document management unit 503 by transcription unit 505 (FIG. 2). After that, the data to be propagated is similarly propagated to aggregate document management unit 503 for the remaining workflow instances (workflows W1 to Wk in FIG. 9).

[0039] Thereafter, when an output request is supplied from user n to aggregate document output unit 504 (X34), aggregate document output unit 504 requests document data from aggregate document management unit 503 (X35), aggregate document management unit 503 returns the document data to aggregate document output unit 504 (X36), and aggregate document output unit 504 outputs the aggregate document based on the aggregate document data (X37). The aggregate document data also includes the data propagated to aggregate document management unit 503 by transcription unit 505, and is displayed including this data.

[0040] FIG. 5 shows a schematic example of how to use an aggregate document. As shown in FIG. 5, when an aggregate document is generated, a workflow, for example, a "fixture ordering process" is associated with it and generated as shown in A01. This workflow executes the operations shown in the illustrated flowchart process, and data is updated as the workflow progresses (A02). This update triggers input data of all workflow related documents linked to the aggregate document to be propagated to the aggregate document, and data on the aggregate document side is updated (A03). In this way, the status of the workflows linked to the aggregate document is aggregated in the aggregate document and output. Note that, although the example in FIG. 5 is based on an example of updating and writing data, it is of course also applicable to an example of appending data.

[0041] 9 shows a manner in which each data is propagated from a plurality of workflow instances to the aggregate document management unit 503. In the example shown in the figure, the workflow W1 generates data D1 and holds it in a variable X1, which is propagated to a variable Y1 of the aggregate document management unit 503 by the transcription unit 505 (FIG. 2). Similarly, the workflow W2 generates data D2 and holds it in a variable X2, which is propagated to a variable Y2 of the aggregate document management unit 503 by the transcription unit 505 (FIG. 2). Finally, the workflow Wk generates data Dk and holds it in a variable Xk, which is propagated to a variable Yk of the aggregate document management unit 503 by the transcription unit 505 (FIG. 2).

[0042] These propagated data D1, D2, ... Dk are returned to aggregate document output unit 504 as aggregate document data, and aggregate document output data is generated and output (viewed and printed) based on the formulas and display methods contained in the aggregate document data. Data D1, D2, ... Dk represent, for example, numerical values ​​for each resource required for one project (e.g., fixtures, rent, etc.), allowing the progress of the project to be grasped in an aggregate manner.

[0043] FIG. 10 shows an example in which the generated data of a single workflow instance is additionally written on the aggregate document management unit 503 side and the history of the data is held. In the example shown in the figure, the workflow W1 generates data D11 and holds it in the variable X11, which is propagated to the variable Y11 of the aggregate document management unit 503 by the transcription unit 505 (FIG. 2). The workflow W1 updates this data. When the data is updated, the data is held in the variable X12, which is propagated to the variable Y12 of the aggregate document management unit 503 by the transcription unit 505. Similarly, the history of the generated data is propagated sequentially to the aggregate document management unit 503 side. Finally, when the workflow W1 updates the data, it is held in the variable X1j, which is propagated to the variable Y1j of the aggregate document management unit 503 by the transcription unit 505.

[0044] The multiple propagated data are processed as a data history, making it possible to grasp the temporal changes of the data in an aggregate manner.

[0045] FIG. 11 illustrates an example of an aggregate document generation unit 5032 that generates an aggregate document. In this figure, the aggregate document generation unit 5032 generates an aggregate document that aggregately displays the results of each workflow (project results) at a point in time that the user is interested in (hereinafter also referred to as the checkpoint time).

[0046] The checkpoint time is typically the current time, but may be a future or past time, which can be uniquely determined by the time information entered in the workflow.

[0047] For example, consider the tasks of planning, executing, and paying a project budget. Each of these has a workflow of application and approval, and an order is placed after the budget has been approved, and payment occurs after delivery and inspection. When managing a project's budget and performance, how much of the budget has been consumed over time compared to the total budget at the project planning stage can be calculated by tallying up the approved amount, the amount being applied for, and the scheduled payment date at the time of budget application and approval, as a cumulative scheduled payment amount, and linking it to time (checkpoint time) and recording it, or it can be tallied at that point in time, and with this data it is possible to check the budget consumption status and scheduled payment status at any point during the project period.

[0048] When the input data for a workflow contains time information, for example, based on the planned expense date, the actual expense date, the planned and actual resource purchase dates, and the planned and actual dates in personnel planning, candidate checkpoint times can be determined in addition to the current time, which is the default checkpoint time, and these can be displayed in a pull-down menu or the like (see Figure 15), allowing you to check the results at the checkpoint times.

[0049] In FIG. 11, the aggregate document management unit 503 includes a history data database 5031 and an aggregate document generation unit 5032. The data generated by the workflow execution unit 404 is stored in, for example, the history data database 5031 via the transcription unit 505. The aggregate document generation unit 5032 has a checkpoint time determination unit 5033, a checkpoint time display unit 5034, a checkpoint time selection unit 5035, and a display format selection unit 5036. The checkpoint time determination unit 5033 refers to the history data database 5031 and determines checkpoint time candidates based on history data including time information such as a scheduled date and an actual date. In addition to checkpoint candidates determined based on variable times such as a scheduled date and an actual date, a "current" time and a time after a certain interval has elapsed (for example, a point halfway through the scheduled period of the project, a point one month after the start of the project, etc.) may be adopted as default checkpoint candidates. By presenting checkpoint candidates that are likely to interest the user, the user can easily check the progress of the project.

[0050] A checkpoint time display unit 5034 presents the checkpoint candidates determined by the checkpoint time determination unit 5033 to the user, for example, by a pull-down menu, so that the user can select a desired checkpoint from the checkpoint candidates using a checkpoint time determination unit 5035. A display format selection unit 5036 allows the user to select a display format for the aggregate document, for example, a table format (FIG. 14), a hierarchical format (FIG. 18), a graph (FIGS. 16 and 17), a Kanban card, etc. Also, multiple checkpoints, typically two checkpoints, may be selected so that the results between the checkpoints can be compared (FIG. 19).

[0051] FIG. 14 displays confirmed information at the "current" time, and aggregates results, etc. based on data related to scheduled dates and actual dates prior to the present time. Results, etc. may also be aggregated based only on data related to actual dates. Note that in FIG. 14, the "current" time is "2023 / 02 / 28", and payment is settled on "2023 / 01 / 30", which is reflected in the aggregated results.

[0052] In Fig. 15, future or past checkpoint candidates for the "current" time are displayed in a pull-down menu, and the results, etc., forecast and actual results at the time of the selected future or past (or "current") checkpoint are included in the aggregation. In this example, in addition to the current date ("2023 / 02 / 28"), the actual dates included in the entered data ("2023 / 01 / 18", "2023 / 01 / 13", "2023 / 01 / 10") are displayed as checkpoints in the pull-down menu, and further, based on the application for a payment schedule for "2023 / 03 / 31", "2023 / 03 / 31" is presented in the pull-down menu as a future checkpoint and can be selected.

[0053] Fig. 12 shows an example of the operation of selecting the display format of an aggregate document and displaying it (see Fig. 13 for comparison formats), in which the checkpoint time determination unit 5033 determines the checkpoint time (step S30), the checkpoint time display unit 5034 displays the checkpoint time, for example, in a pull-down menu (S31), the checkpoint time selection unit 5036 selects the checkpoint time based on the user's specification (S22), and then the display format selection unit 5036 selects the display format based on the user's selection and generates the aggregate document (S34). Note that the checkpoint selection step and the display format selection step may be performed in tandem.

[0054] FIG. 13 shows the operation when the comparison format is selected. In this figure, when the comparison format is selected (S40), list columns are displayed as the number of items to be compared (S41), the checkpoint time determination unit 5033 determines the checkpoint time (step S42), the checkpoint time display unit 5034 displays the checkpoint time in each list column, for example in a pull-down menu (S43), the checkpoint time selection unit 5036 selects a checkpoint time based on the user's specification in each list column (S44), and then the display format selection unit 5036 selects a display format based on the user's selection (S45), and an aggregate document is generated (S46).

[0055] 20 shows a modified example of the embodiment described above, in which workflow management system 10A has aggregated workflow instance generation unit 511 instead of aggregated document generation unit 502 in Fig. 2, aggregated workflow template holding unit 510 instead of aggregated document template holding unit 501, and aggregated workflow instance management unit 512 instead of aggregated document management unit 503. In this embodiment, a workflow template for processing aggregated documents is prepared, aggregated documents are generated using this workflow, and aggregated documents are prepared as aggregated workflow-related documents for each case or other situation through workflow processing, and the user may be prompted to output the aggregated document (activity) as appropriate. 20, the aggregated workflow template holding unit 510, the aggregated workflow instance generating unit 511, and the aggregated workflow instance management unit 512 are shown separately from the workflow template holding unit 401, the workflow instance generating unit 402, and the workflow instance management unit 403 of the workflow processing unit 400, but the aggregated workflow template holding unit 510, the aggregated workflow instance generating unit 511, and the aggregated workflow instance management unit 512 may be included in the workflow template holding unit 401, the workflow instance generating unit 402, and the workflow instance management unit 403 of the workflow processing unit 400, respectively. That is, the former may be a subset of the latter. In this case, the transcription unit 506 may propagate (transcribe) data inside the workflow instance management unit 403 including the aggregated workflow instance management unit 512.

[0056] 20, a workflow instance may be recursively associated with a lower workflow instance. A higher workflow instance may be used as an aggregate document for the lower workflow instance. Recursive association may be performed in multiple stages.

[0057] This is the end of the description of the embodiment.

[0058] Incidentally, the present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit and scope of the present invention. [Explanation of symbols]

[0059] 10. Workflow Management Systems 100 Applications 101 Document Management Server 102 Workflow Server 103 Database Management Server 104 Mail Server 105 Web Server 110 Operating Systems 120 Computer 121 processors 122 Main Memory 123 Programs 200 Communication Network 300 Host terminal 400 Workflow Processing Unit 401 Workflow template storage unit 402 Workflow instance generation unit 403 Workflow Instance Management Unit 404 Workflow Execution Unit 501 Aggregate Document Template Storage Unit 502 Aggregate Document Generation Unit 503 Document Management Department 5031 Database for historical data 5032 Aggregated Document Generation Unit 5033 Checkpoint Time Determination Unit 5034 Checkpoint Time Display Unit 5035 Checkpoint Time Selection Unit 5036 Display format selection section 504 Aggregated Document Output Unit 505 Transcription Department 510 Aggregation workflow template storage unit 511 Aggregation Workflow Instance Generation Unit 512 Aggregated Workflow Instance Management Unit 1001, 1002... User (user's host terminal)

Claims

1. an aggregate document management means for managing the aggregate document; an associating means for associating a workflow instance with said aggregate document; A workflow execution means for executing the workflow instance; a propagation means for propagating to the aggregate document, when predetermined generated data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generated data generated during execution of the workflow instance; an output means for outputting the aggregate document managed by the aggregate document management means; an output of the aggregate document including a display based on the generated data propagated to the aggregate document; The output means is A means for specifying multiple checkpoint times; a display means for displaying a list of the generated data to be aggregated into the aggregate document at each of the specified multiple checkpoint times, distinguishing the display based on the generated data for each checkpoint time.

2. 2. The workflow management device according to claim 1, wherein the plurality of checkpoint times are defined in units of days.

3. 2. The workflow management device according to claim 1, wherein the checkpoint time is a past, present, or future time.

4. 2. The workflow management device according to claim 1, further comprising a means for designating a manner in which said generated data is displayed on said display means.

5. An aggregate document management means manages the aggregate document; an associating means for associating a workflow instance generated based on the workflow definition held in a workflow holding means with the aggregate document; A step in which a workflow execution means executes the workflow instance; A propagation means propagates, when predetermined generation data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generation data generated during execution of the workflow instance to the aggregate document; an output means for outputting the aggregate document managed by the aggregate document management means; an output of the aggregate document including a display based on the generated data propagated to the aggregate document; a workflow management method comprising: the output means, based on the specification of a plurality of checkpoint times, displaying a list of the generated data to be aggregated at each of the plurality of checkpoint times, distinguishing the display by the checkpoint time.

6. Computer, A workflow definition storage means for storing a workflow definition; an aggregate document management means for managing the aggregate document; an associating means for associating a workflow instance generated based on the workflow definition with the aggregate document; a workflow execution means for executing the workflow instance; a propagation means for propagating to the aggregate document, when predetermined generated data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generated data generated during execution of the workflow instance; and The document management means is used to realize the output means for outputting the aggregate document managed by the aggregate document management means, an output of the aggregate document including a display based on the generated data propagated to the aggregate document; The output means is A means for specifying multiple checkpoint times; and a display means for displaying a list of displays based on the generated data to be aggregated into the aggregate document at each of the specified multiple checkpoint times, distinguishing the displays by checkpoint time.

7. an aggregate document management means for managing the aggregate document; an associating means for associating a workflow instance with said aggregate document; A workflow execution means for executing the workflow instance; a propagation means for propagating to the aggregate document, when predetermined generated data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generated data generated during execution of the workflow instance; an output means for outputting the aggregate document managed by the aggregate document management means; an output of the aggregate document including a display based on the generated data propagated to the aggregate document; The output means is a checkpoint time determination means for determining at least a part of a checkpoint time based on time information included in the predetermined generated data that is propagated to the aggregate document; a checkpoint time display means for displaying the checkpoint time; a checkpoint time designation means for designating one or more of the checkpoint times; a display unit that performs display based on the generated data to be aggregated into the aggregate document at a specified checkpoint time based on the specified checkpoint time.

8. 8. The workflow management apparatus according to claim 7, wherein the checkpoint times include a current time as a default checkpoint time.

9. 8. The workflow management device according to claim 7, wherein said time information for determining at least some of said checkpoint times based on time information included in said predetermined generated data includes scheduled time information and actual time information.

10. An aggregate document management means manages the aggregate document; an associating means for associating a workflow instance with the aggregate document; A step in which a workflow execution means executes the workflow instance; A propagation means propagates, when predetermined generation data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generation data generated during execution of the workflow instance to the aggregate document; an output means for outputting the aggregate document managed by the aggregate document management means; an output of the aggregate document including a display based on the generated data propagated to the aggregate document; Furthermore, a step in which a checkpoint time determination means determines at least a part of the checkpoint time based on time information included in the predetermined generated data transmitted to the aggregate document management means; a step of displaying the checkpoint time by a checkpoint time display means; a step of a checkpoint time designation means designating one or more checkpoint times among the checkpoint times; a display step of displaying, based on the generated data to be aggregated into the aggregate document at the specified checkpoint time, the generated data being displayed based on the specified checkpoint time by a display means.

11. Computer, an aggregate document management means for managing the aggregate document; associating means for associating a workflow instance with said aggregate document; a workflow execution means for executing the workflow instance; a propagation means for propagating to the aggregate document, when predetermined generated data of a workflow instance associated with the aggregate document is defined as an aggregation target to be aggregated in the aggregate document, the predetermined generated data generated during execution of the workflow instance; and The document management means is used to realize the output means for outputting the aggregate document managed by the aggregate document management means, an output of the aggregate document including a display based on the generated data propagated to the aggregate document; The output means is a checkpoint time determination means for determining at least a part of a checkpoint time based on time information included in the predetermined generated data that is propagated to the aggregate document; a checkpoint time display means for displaying the checkpoint time; a checkpoint time designation means for designating one or more of the checkpoint times; a display unit that performs a display based on the generated data to be aggregated into the aggregate document at a specified checkpoint time based on the specified checkpoint time.

Images