JP2004287575A - Task management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a task management system capable of managing a task by using a combination of basic instruction systems based on a task module. <P>SOLUTION: This task management system is provided with: a task module having an instructing means for designating a person who processes a task, a reporting means for executing a task report to the instructor and an approving means for approving the task report; a system storing means for storing information associated with an instruction system including the instructor, reporter or approver on the basis of the execution result of the task module; and a management means for managing a task by combining the information associated with the instruction system based on the task module. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to managing information transmission such as in-company instruction and reporting.
[0002]
[Prior art]
In recent years, workflow has been a core software supporting business reform. The workflow means the flow of business, and is also called an electronic approval system.
[0003]
Currently, various tasks in a company are processed using a workflow. The workflow is effective for business such as approval / decision business and decision making business in a company. In such a job, a person different from the drafter performs confirmation / approval of the content applied by the drafter sequentially or partially at the same time. Then, the process is repeated until the final decision is approved.
[0004]
Here, a conventional workflow is shown in FIG.
[0005]
FIG. 27A shows an approval type workflow. In the approval type workflow, the content applied for by the drafter is continuously approved one by one. FIG. 27B shows a workflow of a Decision-making type. In the approval type workflow, the content applied by the drafter is approved by a plurality of persons at the same time during the approval.
[0006]
By the way, such business often flows through a round-trip type approval route. FIG. 28 shows the conventional workflow shown in FIG. 27 represented by a reciprocating approval route.
[0007]
Here, the flow of the instruction / reporting operation will be described with reference to FIG.
[0008]
The manager A first instructs the section manager B on the work contents (1). The section manager B transmits the instructed work contents to the section staff C (2). The section C executes the designated task (3). Then, the section C reports the end of the work to the section manager B. Section manager B receives the report from section C and reports it to the section manager (4). Manager A makes final approval (5).
[0009]
In addition, as such a workflow system, an operation computer terminal connected to a network for executing a workflow between persons in charge and a plurality of paths for a node which is a unit of processing to be handled are multiplexed. A design computer terminal for designing a workflow by designating a project variable of the same, and a workflow server for managing the designed workflow and accessing the operation computer terminal in accordance with the activity that is the process assigned to the node. A system provided with the same has been proposed (see Patent Document 1).
[0010]
However, this method has the following problems.
[0011]
In a reciprocating workflow as shown in FIG. 28, the route is long and management is complicated. For example, a workflow of three people is managed by five nodes. That is, when three persons, the section manager A, the section manager B, and the section C, process the workflow, it is necessary to manage five processes of instruction, transmission, execution, report, and approval. Therefore, an intermediate person (section manager B) performs the process twice on the outward route and the return route. In such a case, if a return or the like occurs in the middle, the status management becomes complicated.
[0012]
Further, in a reciprocating workflow, it is difficult to define a workflow such as a case of branching in the middle. For example, in FIG. 28, when a plurality of persons communicate (2), the workflow becomes the approval type workflow shown in FIG. 27 (B). However, in FIG. 28, when there are a plurality of communicators, there are also a plurality of execution nodes (3). In such a case, it has been difficult to cope with the conventional workflow.
[0013]
Further, in the reciprocating workflow, there is a case where the section manager B is determined when the manager A instructs, but the section C to be executed is not determined. In such a case, the forwarding route of the workflow is not determined.
[0014]
In addition, as shown in FIG. 28, if only one person executes a task, a conventional workflow can sufficiently cope with the task. However, it is difficult to cope with the conventional workflow when there is a person who further executes a task below the section C in FIG. That is, it is difficult to cope with a workflow when the number of instruction systems increases.
[0015]
[Patent Document 1]
JP-A-2002-99686 (abstract).
[0016]
[Problems to be solved by the invention]
The present invention has been made in view of such problems of the related art. That is, the problem to be solved by the present invention is to provide a task management system capable of managing tasks by combining basic instruction systems by task modules.
[0017]
[Means for Solving the Problems]
The present invention employs the following means in order to solve the above problems.
[0018]
A business management system according to the present invention includes: a business module having instruction means for designating a person who processes a business, a report means for executing a business report for the instructor, and an approval means for approving the business report; Based on the execution result, a system storage unit that records information related to the instruction system including the instructor, reporter, or approver, and a management unit that manages a business by combining information related to the instruction system by the business module It is characterized by having.
[0019]
With such a configuration, the business can be managed by a combination of basic instruction systems by the business module, including the case of branching on the way. Therefore, it is possible to manage the work in accordance with an arbitrary instruction system, or to designate the instruction systems one by one. Therefore, it is possible to flexibly respond to a change in the instruction system. In addition, the instruction systems by the business modules can be combined via, for example, a network. This makes it possible to easily manage business processes, for example, between the parent company and the subsidiary company or between the ordering company and the order receiving company.
[0020]
The management unit may further include a system-related storage unit that stores information related to a system indicated by a plurality of business modules in association with each other.
[0021]
With such a configuration, a higher order person in the instruction system can designate a plurality of instruction systems collectively.
[0022]
Further, the business management system according to the present invention may further include a status recording unit that records the status of the instruction, report, or approval.
[0023]
In the business management system according to the present invention, the business module may further include a plurality of instruction units that specify a plurality of persons who process the business, or may further include a group instruction unit that specifies a group that performs the business. Is also good.
[0024]
Further, the present invention may store the above-mentioned program in a readable storage medium.
[0025]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[0026]
FIG. 1 is a diagram illustrating a workflow based on a ring-structured information chain, and FIG. 2 is a diagram illustrating a branched workflow based on a ring-structured information chain. FIG. 3 is a diagram showing an embodiment based on the broadcast unit WF, and FIG. 4 is a diagram showing an embodiment based on the group unit WF.
[0027]
FIG. 5 is a diagram showing a system configuration using WWW, and FIG. 6 is a diagram showing a module configuration.
[0028]
FIG. 7 to FIG. 13 are diagrams showing a configuration of a table included in the DB server. 7 shows a user management table, FIG. 8 shows a group management table, FIG. 9 shows a flow management table, and FIG. 10 shows a forwarding management table (unit WF). FIG. 11 is a diagram showing a forwarding management table (broadcast unit WF), FIG. 12 is a diagram showing a document management table, and FIG. 13 is a diagram showing the relationship between the tables.
[0029]
14 to 23 show the processing flow of the system. 14 is a diagram showing the overall work, FIG. 15 is a diagram showing the creation of a new workflow, FIG. 16 is a diagram showing a processing flow when creating a new workflow, and FIG. 17 is a diagram showing the execution of the work. FIG. 18 is a diagram showing a process flow of approval / return of child WF, FIG. 19 is a diagram showing a process flow of child WF creation, FIG. 20 is a diagram showing a process flow of completion report, and FIG. FIG. 22 is a diagram showing execution of approval, and FIG. 22 is a diagram showing a processing flow of approval / return of a workflow. FIG. 23 is a diagram showing a processing flow of dunning and discontinuation by the scheduled processing.
[0030]
FIG. 24 is a conceptual diagram of an unprocessed search at the time of cooperation with another server, and FIG. 25 is a diagram showing query contents at the time of an unprocessed search.
<Basic principle>
According to the present invention, information transmission is managed by a combination of unit WFs (also referred to as a chain of WFs) in an instruction / reporting operation over a plurality of layers. Here, one round trip from the instructor to the reporter and back from the reporter to the instructor (approver) is a basic component of the workflow (hereinafter, referred to as a unit WF). Further, information transmission in which an instruction from the instructor circulates and returns to the instructor again is referred to as ring-structure information transmission.
[0031]
Hereinafter, the basic principle of the workflow of the present invention will be described with reference to FIGS.
[0032]
FIG. 1 shows an embodiment of a workflow using a ring structure type information chain. The implementation procedure in this case is as follows.
[0033]
First, the manager A creates the WF1 by appointing the manager B and gives an instruction to the manager B. Then, the section manager B who has received the instruction creates the WF2 by designating the section C, and gives the instruction to the section C.
[0034]
Further, the section C receiving the instruction implements the content of the instruction. Then, the section C reports to the section manager B that the instruction content has been completed by the WF2. Then, based on the report from section C, section manager B reports to section manager A by WF1.
[0035]
Next, with reference to FIG. 2, an embodiment of a workflow having a branch by a ring structure type information chain will be described.
[0036]
As described above, even in the case where there is a branch from the section manager B in FIG. 2 to the preceding instruction system by the combination of the unit WFs, information transmission can be managed in the same manner as in the workflow using the ring structure type information chain in FIG. In other words, even if the workflow has a branch, the instruction / reporting operation can be managed by a combination of the unit WFs. The implementation procedure in this case is as follows.
[0037]
First, the manager A creates the WF1 by appointing the manager B, and gives an instruction to the manager B.
[0038]
Then, the section manager B who has received the instruction creates the WF2 by designating the section 1 and gives the instruction to the section 1. Similarly, section manager B designates section 2 to create WF 3 and gives section 2 an instruction.
[0039]
Then, the section 1 implements the instruction contents and reports the completion to the section manager B by the WF2. Similarly, the section 2 implements the instruction content and reports the completion to the section manager B by the WF3. Section manager B reports to section manager A by WF1 based on the reports from section 1 and section 2.
[0040]
As described above, in the present invention, since a workflow is configured by a combination of unit WFs, the entire workflow can be managed by grasping the parent-child relationship of each component.
[0041]
In addition, one instructor may specify only the instructed person (reporter) directly. Therefore, the indicating system ahead of the reporter can respond arbitrarily. In other words, in the above-described embodiment, the section manager merely gives an instruction to the section manager, and the section manager who receives the instruction can arbitrarily determine whether the instruction content is to be performed by one section member or by two or more section members.
[0042]
In the above-described embodiment, the entire workflow can be managed by grasping the parent-child relationship such as the manager and the section manager, and the section manager and the section staff.
[0043]
Next, the types of workflows will be described with reference to FIGS.
[0044]
FIGS. 1 and 2 show a workflow in which the instructor issues an instruction to one reporter. That is, a unit WF is shown in FIGS.
[0045]
FIG. 3 is a diagram showing a broadcast unit WF. The broadcast unit WF refers to a type of workflow in which a plurality of reporters are designated and instructed simultaneously. In the broadcast unit WF, the response type can be specified when giving the instruction.
[0046]
The answer type includes "all persons must answer" and "one person needs answer". "Everyone must answer" means that all reporters need to respond. "One person is required" means that the workflow is completed when any one of the reporters answers.
[0047]
FIG. 4 is a diagram showing a group unit WF. The group unit WF refers to a type of workflow for instructing a reporter of a predefined group of users.
[0048]
Even in the group WF, the answer type can be specified when giving an instruction. Here, "all members must answer" is a case where all members of the group need to respond. “One-person answer required” is a case where this workflow is completed when any one of the members of the group answers.
<System configuration>
With reference to FIG. 5, a system configuration in an embodiment using WWW will be described. The business management system according to the present embodiment includes a plurality of user terminals 501, a workflow server 502, and a DB server 503.
[0049]
The user uses the workflow of the business management system using the terminal 501. The terminal 501 uses a browser (browsing software) 511 to display a menu for using this workflow on a screen.
[0050]
The workflow server 502 includes a workflow engine 512 for realizing a workflow function, and a WWW server 513 for displaying a screen on a browser 511 of the terminal 501.
[0051]
The DB server 503 is a server for storing data required for this workflow. The DB server 503 includes DBs for user management 514, group management 515, flow management 517, and document management 518. The management table of the DB server 503 will be described later in detail. This DB may be a general RDB or a DB configured by XML. That is, the type of DB is not particularly limited.
[0052]
Further, the business management system may be provided with an authentication server 504 for executing authentication using an ID / password when a user logs in to the business management system. However, when the independent authentication server 504 is not installed, the authentication can be executed by providing a table storing the ID / password on the DB server.
[0053]
Further, the work management system may cooperate with the mail server 505 to use an e-mail to notify the user of the forwarding destination when the workflow is forwarded.
[0054]
Further, it may cooperate with another workflow server or another DB server via a network 506 such as the Internet. For example, the DB server 503 and the workflow server 502 may be linked via a network between the parent company and the subsidiary company or between the ordering company and the order receiving company. In this way, it is possible to easily manage a workflow that spans the parent company and the subsidiary company or the ordering company and the order receiving company.
<Module configuration>
With reference to FIG. 6, a module configuration of the task management system according to the present embodiment will be described. FIG. 6 is a module configuration diagram of the embodiment of the present invention. In this module, operations performed by a user accessing a WF server in the system and executed are shown in processing units.
[0055]
Hereinafter, processing executed in each module will be described.
[0056]
The login 601 executes authentication using an ID / password when the user logs in from the terminal 501 to the workflow server 502 in the system.
[0057]
Then, when the user logs in to the workflow server 502, the system displays a workflow menu 602. That is, the workflow menu 602 is a menu screen displayed first after the user logs in 601. When the user logs out of the system, the process ends 603.
[0058]
Next, processing that can be executed by the user on the workflow menu 602 will be described.
[0059]
The processes that can be executed in the workflow menu 602 include a new creation 604, a created list 605, an unprocessed list 609, an unapproved list 612, a free search 614, a proxy registration 616, and a proxy process 617.
[0060]
New creation 604 creates a new workflow. Here, the user creates a new workflow. This user is the instructor.
[0061]
The created list 605 displays a list of workflows created by the user. Here, the user can browse workflows including unprocessed and processed.
[0062]
The content / processing status reference 606 displays the content of the selected workflow and the processing status at that time.
[0063]
The stop 607 executes the stop of the process in the selected workflow. Here, when child workflows are defined, processing of all child workflows is stopped in a chain.
[0064]
The chain reference 608 displays a workflow related to the selected workflow, such as a parent workflow and a child workflow of the selected workflow, in a chain in a tree shape.
[0065]
The unprocessed list 609 displays a list of workflows to be processed by the logged-in user. That is, the unprocessed list 609 displays all unprocessed work.
[0066]
Then, the progress setting 610 sets the progress of the selected workflow. At this time, the user gives a completion report if all the processes have been completed.
[0067]
Then, the child WF creation 611 creates a new child workflow. Here, the user who has received the instruction instructs the subordinate to execute the task. This user becomes the instructor of the created child workflow. A chain reference 608 displays a parent workflow, a child workflow, and the like of the selected workflow in a chain in a tree shape.
[0068]
The unapproved list 612 displays a list to be approved among the workflows created by the user. That is, the unapproved list 612 displays a list of reports from subordinates designated by the user.
[0069]
Then, the approval 613 approves the selected workflow. Here, the user approves the report from the subordinate.
[0070]
The free search 614 searches for any one of the workflows created in the past. Here, the user can refer to the workflow created in the past. At this time, for the workflow referred to, the reference authority may be given to restrict the reference person. It is desirable to manage the reference authority according to the position of the user and the department to which the user belongs.
[0071]
Then, the search result list 615 displays a list of the search results described above.
[0072]
The search result list 615 includes a content / processing state reference 606 and a chain reference 608. The content / processing status reference 606 displays the content of the selected workflow and the processing status at that time. The chain reference 608 displays workflows related to the selected workflow, such as a parent workflow and a child workflow of the selected workflow, in a chain in a tree shape.
[0073]
The agent registration 616 registers the person who processes the work on behalf of the user. For example, when a task that requires immediate processing occurs when a worker is absent, a person who can process the task is required instead of the worker. In such a case, an agent registered in advance on behalf of the absent user performs the job on behalf of the user.
[0074]
In the proxy process 617, the user registered in advance by the proxy registration 616 executes the process on behalf of the registrant.
<Table configuration>
The table relating to the module structure will be described with reference to FIGS. These tables are stored in the DB server 303 shown in FIG.
<User management table>
The user management table 700 will be described with reference to FIG. FIG. 7 is a diagram illustrating an example of the user management table 700.
[0075]
The items in this table are WFE identification 701, user ID 702, name 703, e-mail address 704, job title 705, affiliation 706, and table 707. The WFE identification 701 and the user ID 702 are items that are primary keys of the table. The primary key is a field for identifying a record one line at a time, and the primary key always has a unique value. Also, by specifying the primary key, only necessary records are extracted from a huge amount of data.
[0076]
Hereinafter, each item will be described.
[0077]
The WFE identification 701 stores information (such as the URL of the workflow server) for identifying the workflow engine 512 for managing each workflow.
[0078]
Information for uniquely identifying each user in the workflow engine 512 is stored in the user ID 702.
[0079]
The name 703 stores the name of each user. The name 703 may be stored with a first and last name separately, or may be stored in a plurality of notations such as kanji, kana, and romaji.
[0080]
The mail address 704 stores the mail address of each user. The e-mail address 704 is used when a WF-related work instruction, report, reminder, or the like is performed by e-mail.
[0081]
The position 705 stores the position of each user in the organization. The position 705 is used when managing access authority and the like according to the position.
[0082]
The affiliation 706 stores the affiliation of each user. The affiliation 706 is used when the instructor specifies a reporter to perform a search by an organization. The affiliation 706 may store a plurality of levels of affiliations (company, headquarters, business department, department, section, section, group), and the like.
[0083]
Further, if there is an item to be managed for each user other than the above, it can be stored in the item 707.
<Group management table>
The group management table 800 will be described with reference to FIG. FIG. 8 is a diagram illustrating an example of the group management table 800.
[0084]
The main items of this table are a WFE identification 801, a group ID 802, a member ID 803, and a table 804. These items are the items that will be the primary keys of the table.
[0085]
Hereinafter, each item will be described.
[0086]
The WFE identification 801 stores information (such as the URL of the workflow server) for identifying the workflow engine 512 that manages each workflow, similarly to the WFE identification 701.
[0087]
The group ID 802 stores information for uniquely identifying each group in the workflow engine 512.
[0088]
The member ID 803 stores the user ID of a user belonging to each group.
[0089]
Furthermore, if there is an item to be managed for the members of each group other than the above, the item can be stored in the item 804.
<Flow management table>
The flow management table 900 will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of the flow management table 900 when the unit WF illustrated in FIG. 2 is created.
[0090]
This table manages the parent workflow (WF1) shown in FIG. 2 and its child workflows (WF2, WF3) in association with three records. Items in this table include WFE identification 901, WFID 902, parent WFE identification 903, parent WFID 904, parent WF process ID 905, WF type 906, answer type 907, creator ID 908, creator name 909, creation date and time 910, processing time limit 911, The processing at the time limit 912, the reference restriction 913, and the stop flag 914. The WFE identification 901 and WFID 902 are items that are primary keys of the table.
[0091]
Hereinafter, each item will be described.
[0092]
The WFE identification 901 stores information (such as the URL of the workflow server) for identifying the workflow engine 512 that manages each workflow, similarly to the WFE identification 701.
[0093]
The WFID 902 stores information for uniquely identifying a workflow in the workflow engine 512.
[0094]
When the workflow is a child WF, information for identifying a management engine of the parent WF is stored in the parent WFE identification 903. When the workflow is a parent WF, NULL is stored in the parent WFE identification 903.
[0095]
When the workflow is a child WF, the WFID 902 on the management engine of the parent WF is stored in the parent WFID 904. If the workflow is a parent WF, NULL is stored in the parent WFID904.
[0096]
When the workflow is a child WF, the parent WF processor ID 905 stores the processor ID 905 of the parent WF. If the workflow is a parent WF, NULL is stored in the parent WF processor ID 905.
[0097]
The WF type 906 stores a symbol for distinguishing the unit WF, the broadcast unit WF, and the group unit WF. Since WF1, WF2, and WF3 are unit WF as shown in FIG. 2, the unit WF is stored here.
[0098]
The answer type 907 stores the condition of the person who reports to the instructor. In the case of the unit WF, NULL is stored in the answer type 907. In the case of a broadcast unit WF or a group unit WF, the response type 907 stores information for distinguishing between “all members need to answer” and “one person needs answer”.
[0099]
The creator ID 908 stores the ID of the user who created each workflow.
[0100]
The creator name 909 stores the name of the creator. The creator's name 909 may store the first and last names separately, or may store them in a plurality of notations such as kanji, kana, and romaji.
[0101]
The creation date and time 910 stores the date and time when each workflow was created.
[0102]
The processing time limit 911 stores the processing time limit set for each workflow. If the processing time limit is not specified, NULL is stored in the processing time limit 911.
[0103]
In the time limit processing 912, information for distinguishing the processing content (for example, discontinuation) when the time limit is reached is stored when there is a processing time limit. On the other hand, if the processing time limit is not set, NULL is stored in the process 912 when the time limit arrives.
[0104]
The reference restriction 913 stores information for distinguishing a range in which each workflow is disclosed (for example, unrestricted, only a superior, or within a department).
[0105]
The stop flag 914 stores a stop flag (information for each cause) when the workflow process is stopped due to cancellation by the creator or termination due to expiration of the deadline.
[0106]
Further, if there is an item to be managed for each workflow other than the above, the item may be added.
<Forwarding management table>
The forwarding management table 1000 will be described with reference to FIG. FIG. 10 is a diagram illustrating an example of the forwarding management table of the WF1 illustrated in FIG.
[0107]
This table manages the entry contents of the instructor, reporter, and approver of the WF1 with three records. This approver is the same person as the instructor.
[0108]
Items in this table include WFE identification 1001, WFID 1002, forwarding order 1003, forwarding destination WFE 1004, forwarding destination group ID 1005, processor ID 1006, processor name 1007, processing date and time 1008, processing state 1009, processor ID 1010, proxy processor name 1011, presence / absence of attached document 1012, instruction / report content 1013, reporter progress 1014, report status 1015, and table 1016. Also, the WFE identification 1001, WFID 1002, forwarding order 1003, forwarding destination WFE 1004, and processor ID 1006 are items that become primary keys of the table.
[0109]
Hereinafter, each item will be described.
[0110]
The WFE identification 1001 stores information (such as the URL of the workflow server) for identifying the workflow engine 512 that manages each workflow, similarly to the WFE identification 701.
[0111]
The WFID 1002 stores information for uniquely identifying a workflow in the workflow engine 512.
[0112]
The forwarding order 1003 stores the order in which the workflow is forwarded. In the hierarchical order 1003, “1” indicates the instructor, “2” indicates the reporter, and “3” indicates the approver. The approver is the same person as the instructor.
[0113]
Information for identifying the WFE to which the reporter belongs is stored in the forwarding destination WFE 1004.
[0114]
The forwarding destination group ID 1005 stores information for identifying a group to which the workflow is forwarded. In the case of the unit WF and the broadcast unit WF, NULL is stored in the forwarding destination group ID 1005. When the forwarding destination group ID 1005 is a group-based WF, the reporter's record stores the group ID. Here, the reporter record is a record whose forwarding order 1003 is “2”.
[0115]
The processor ID 1006 stores the IDs of the instructor, reporter, and approver. When the work is performed on behalf of the business, the processor ID 1006 stores the ID of the substitute. When the business is processed by the reporter, NULL is stored in the processor ID 1006.
[0116]
The processor name 1007 stores the name corresponding to the processor ID.
[0117]
The processing date and time 1008 stores the date and time at which the instruction, report, and approval were performed. If the user has performed a temporary save, the processing date and time 1008 stores that date and time. Thereafter, when the user completes the processing, the completed date and time is overwritten in the processing date and time 1008.
[0118]
The processing status 1009 stores the status of each record. For example, the record of the instructor whose forwarding order is “1” stores “draft”. In the record of the reporter whose forwarding order is “2”, “unprocessed”, “temporary storage”, “processed”, or “return” is stored. The record of the approver whose forwarding order is “3” stores “unprocessed” or “completed”.
[0119]
The proxy processor ID 1010 stores the ID of a proxy when an instruction, a report, or an approval is processed on behalf of the proxy. If the work is not performed on behalf of the job, NULL is stored in the proxy processor ID 1010.
[0120]
The proxy processor name 1011 stores the name corresponding to the proxy processor ID.
[0121]
The attachment presence / absence 1012 stores an instruction at the time of creating a workflow, or the presence or absence of an attachment related to a report at the time of processing. Individual attachments are managed in a document management table described later.
[0122]
The instruction / report content 1013 stores an instruction at the time of creating a workflow or a text related to a report at the time of processing. That is, comments of the instructor / reporter and the like are stored here.
[0123]
In the reporter progress status 1014, the progress status is stored in the record of the reporter whose forwarding order is “2”. The progress status refers to, for example, a processing status such as a job being processed 50%.
[0124]
In the report status 1015, information indicating the report status is stored in the record of the reporter whose forwarding order is “2”. This status includes completion, cancellation, and reconsideration.
[0125]
Further, for each workflow, if there are other items to be individually managed in the records of the instructor, the reporter, and the approver, the items can be stored in the item 1016.
[0126]
Next, the forwarding management table 1100 will be described with reference to FIG. 10 shows an example of the forwarding management table of the unit WF shown in FIG. 2, while FIG. 11 shows an example of the forwarding management table of the broadcasting unit WF shown in FIG.
[0127]
In this table, similarly to FIG. 10, the contents of the instructor, reporter, and approver are managed in each record.
[0128]
FIG. 11 differs from FIG. 10 in the number of reporters. Since one reporter manages one record, it has a plurality of records.
[0129]
The items in this table are the same as those in FIG.
<Document management table>
FIG. 12 is a diagram illustrating an example of the document management table. This table manages the attached documents at the time of instruction / report with one record per document.
[0130]
The items in this table are WFE identification 1201, each WFID 1202, forwarding order 1203, forwarding destination WFE 1204, processor ID 1205, INDEX 1206, document name 1207, and document 1208 on the server.
[0131]
Hereinafter, each item will be described.
[0132]
The WFE identification 1201 stores information (such as a URL of a workflow server) for identifying a workflow engine 512 that manages each workflow.
[0133]
The WFID 1202 stores information for uniquely identifying a workflow in the workflow engine 512, similarly to the WFE identification 701.
[0134]
The forwarding order 1203 stores the order in which the workflow is forwarded. In the hierarchical order 1003, “1” indicates the instructor, “2” indicates the reporter, and “3” indicates the approver (the same person as the instructor).
[0135]
The forwarding destination WFE 1204 stores a symbol for identifying the WFE to which the reporter belongs.
[0136]
The processor ID 1205 stores IDs of an instructor, a reporter, and an approver. In the case where the job is performed on behalf of the business, the processor ID 1006 indicates the ID of the agent. Further, when the business is processed by the reporter, the processor ID 1006 stores NULL.
[0137]
The INDEX 1206 stores a unique number of the attached document for each creator / processor.
[0138]
The document name 1207 stores a document name to be displayed on the screen.
[0139]
The server document 1208 stores the physical storage location of the document on the server.
[0140]
Furthermore, if there is an item to be managed for each attached document other than the above, an additional table may be stored.
<Related to each table>
With reference to FIG. 13, the relationship between the flow management table 900, the forwarding management table 1000 (1100), and the document management table 1200 will be described. FIG. 13 is a diagram illustrating the relationship between the tables.
[0141]
The flow management table 900 manages a workflow with one record. That is, in the workflow, the instruction, the report, and the approval are performed, and therefore, the flow management table 900 is associated with the instructor forwarding management table, the reporter forwarding management table, and the approver forwarding management table.
[0142]
The forwarding management table 1000 (1100) manages the entry status for each instructor, reporter, and approver of each workflow in one record. The forwarding management table 1000 (1100) can be broadly classified into one for the instructor, one for the reporter, and one for the approver.
[0143]
This reporter record is one record in the case of the unit WF. On the other hand, in the case of the broadcast unit WF, the reporter record has a plurality of records because one broadcaster manages one record. Further, in the case of the group unit WF and the answer type “one person answer required”, the reporter record is one record. On the other hand, in the case of group-based WF and "all members must answer", the reporter record is managed by one record for each member of the group, and therefore has as many records as the number of members in the designated group. .
[0144]
The forwarding management table 1000 (1100) is associated with a document management table 1200 that manages documents attached by the instructor or reporter.
[0145]
The document management table 1200 has a plurality of records in order to manage each record of the instructor or the reporter of the forwarding management table 1000 (1100) with a record for each attached document. Further, the document management table 1200 may attach a plurality of documents to one instruction or report.
<Process flow of overall work procedure>
With reference to FIG. 14, a processing procedure of the overall work will be described. FIG. 14 is a diagram showing the processing of the entire work.
[0146]
In the business management system according to the present embodiment, the system creates a new workflow based on the input of the creator of the workflow (S1401). The creator of this workflow is both the instructor and the approver.
[0147]
Then, the system instructs the reporter indicated in the created workflow to execute the work (S1402). The reporter then performs the work. Here, the processing executed by the system includes creation of a child WF, approval of a report result from the child WF, and reporting to the instructor.
[0148]
Then, the system instructs the creator to approve (S1403). That is, the system causes the workflow creator to confirm the report result from the reporter. The creator then approves.
[0149]
Thereafter, the system ends the processing of the entire operation.
<New workflow creation process>
The new workflow creation process (S1401) shown in FIG. 14 will be described in detail with reference to FIG. FIG. 15 is a diagram illustrating a process of creating a new workflow.
[0150]
A user who creates a new workflow first logs in to the system (S1501). This user is the instructor.
[0151]
Next, the user selects the new creation 604 from the workflow menu 602 shown in FIG. 6 (S1502).
[0152]
Then, the system instructs the user to input the instruction content (S1503). Then, the user inputs the instruction content. Here, the user specifies an attached file as needed.
[0153]
The system instructs the user to input a processing time limit (S1504). Then, the user inputs a processing time limit 911 shown in FIG. Here, the user specifies the processing method 912 at the time of expiration as necessary.
[0154]
The system instructs the user to input a reference restriction (S1505). Then, the user inputs the reference restriction 913.
[0155]
The system instructs the user to input a forwarding method and a reporter (S1506). Then, the user inputs the forwarding method and the reporter. Here, the forwarding method is a WF type 906, and there are a unit WF, a broadcast unit WF, and a group unit WF. The reporter is also the forwarding address. When the WF type 906 is a broadcast unit WF or a group unit WF, the user further specifies “all members must answer” or “one person needs answer”.
[0156]
The system changes the processing state 909 shown in FIG. 9 to the “draft state” and saves the input contents (S1507).
[0157]
The system notifies the reporter of the workflow by e-mail (S1508).
Thereafter, the system ends the process of creating a new workflow.
[0158]
Next, the table processing at the time of creating a new workflow will be described with reference to FIG. FIG. 16 is a processing flow of the system when a new workflow is created. The system executes processing on the WF engine 512 to which the pointer belongs as shown in FIG. 5 according to the input from the pointer.
[0159]
The system starts this processing in response to the user selecting new creation 604 from the workflow menu 602 shown in FIG.
[0160]
First, the system adds a new record to the flow management table 900 shown in FIG. 13 (S1601). Then, a WFID, which is unique identification information, is assigned to the workflow. The system stores the numbered WFID in the WFID 1002 of the flow management table 900 shown in FIG.
[0161]
At this time, the workflow management table 900 sets the parent WF related information to NULL. The parent WF related information is a parent WFE identification 903, a parent WFID 904, and a parent WF processor ID 905 shown in FIG.
[0162]
When the input WF type 906 is the broadcast unit WF or the group unit WF, the system sets the answer type 907. In FIG. 9, since the WF type 906 is a unit WF, NULL is set as the answer type 907.
[0163]
Further, the system sets a processing time limit setting 911, a process when the processing time limit is reached 912, and a reference restriction 913 in accordance with the input from the user.
[0164]
Next, the system newly adds a record to the forwarding management table 1000 shown in FIG. 13 (S1602).
[0165]
The system adds an indicator record whose forwarding order 1003 shown in FIG. 10 is “1”.
[0166]
Then, the system sets the instruction content according to the input from the user. At this time, if there is an attached document, the system sets the attached file presence / absence 1012 to “1”. At this time, the system sets the processing state 1009 to “Draft”.
[0167]
Then, the system adds a reporter record whose forwarding order 1003 is “2”. At this time, the system sets the processing state 1009 to “unprocessed”.
[0168]
If the input WF type 906 is a unit WF, the system generates only one record. Then, the system sets the WFE 1001 and the WFID 1002 to which the reporter belongs to the forwarding destination WFE 1004 and the processor ID 1006.
[0169]
When the input WF type 906 is a broadcast unit WF, the system generates records for the number of broadcast persons. Then, the system sets the WFE 1001 and ID 1002 to which each reporter belongs to the forwarding destination WFE 1004 and the processor ID 1006.
[0170]
If the input WF type 806 is a group-based WF, the system generates a record. At this time, the system generates only one record if "one-person required", and generates records for all the groups if "all-member required". Then, the system sets the forwarding WFE 1004 and the group ID 1006.
[0171]
In FIG. 10, since the WF type 806 is a unit WF, the system generates only one record.
[0172]
The system adds an approver record whose transmission order is “3”. At this time, the system sets the processing state 1009 to unprocessed.
[0173]
Next, the system determines whether there is an attached document (S1603). The system determines the presence or absence of the attached document based on the attached document presence / absence 1012 shown in FIG.
[0174]
If the system determines in S1303 that there is no attached document, the process ends.
[0175]
On the other hand, if the system determines in S1303 that there is an attached document, it adds a new record to the document management table 900 shown in FIG. At this time, the system adds new records by the number of attached documents. Then, the system sets “1” to the forwarding order 1101 shown in FIG. 11 (S1604). Thereafter, the system ends the processing.
<Work execution processing>
The work execution process (S1402) shown in FIG. 14 will be described in detail with reference to FIG. FIG. 17 is a diagram showing a process of executing a task.
[0176]
First, the system approves the ID / password by the login 601 shown in FIG. Here, the user logs in to the system (S1701). The user executing this process is the reporter.
[0177]
Next, the system causes the user to select the unprocessed list 609 from the workflow menu 602 (S1702). The search contents when displaying the unprocessed list 609 are shown in FIG. 24 and FIG.
[0178]
Then, the system instructs the user to select a workflow for executing the process from the list (S1703). Here, the user selects one workflow for executing the process.
[0179]
If a child workflow (hereinafter, also referred to as a child WF) exists in the selected workflow, the system displays a summary of the completion status of the child workflow and the following (S1704). In other words, the system collectively displays the workflows whose report status 1015 shown in FIG. 10 is “completed”.
[0180]
Then, the system causes the user to execute approval or return of the workflow for which the child workflow has received the completion report (S1705). FIG. 18 shows a processing flow of the system when the child workflow is approved or sent back.
[0181]
Further, the system causes the user to select whether to create a child WF (S1706).
[0182]
If the system determines in step S1706 to create a child WF, the system executes registration processing for creating a child WF (S1707 to S1712). The system determines whether to create a child WF based on whether the user has selected the child WF creation 611 shown in FIG.
[0183]
The system instructs the user to input the instruction (S1707). Here, the user specifies an attached file as needed. When the user specifies an attached file, INDEX is set in the attached file presence / absence 1012.
[0184]
Then, the system instructs input of the processing time limit 911 (S1708). This processing time limit 911 can be set within the time limit of the parent WF. In addition, the user inputs the processing at the time limit 912 as necessary.
[0185]
Then, the system instructs input of the reference restriction 913 (S1709).
[0186]
Then, the system instructs the user to input the WF type 906 and the reporter shown in FIG. 9 (S1710).
[0187]
The WF type 906 is a unit WF, a broadcast unit WF, or a group unit WF. This reporter is also a forwarding destination and a processor of the reporter record shown in FIG.
[0188]
When the WF type 906 is the broadcast unit WF or the group unit WF, the system causes the user to select the answer type 907. The answer type 907 is “all members must answer” or “one person needs answer”.
[0189]
Then, the system changes the processing state 1009 shown in FIG. 10 to “Draft” and saves the input contents (S1711). FIG. 23 shows a processing flow of the system when the child WF is generated.
[0190]
The system notifies the reporter that the child WF has been created by e-mail (S1712). The system instructs the user to execute the work by this mail.
[0191]
Then, the system returns to S1706 and prompts the user to select whether to create a child workflow again.
[0192]
If the system determines in step S1706 that a child WF is not created, the system determines whether the report is a completion report (S1713).
[0193]
If the system determines in S1713 that the report is a completion report, the system instructs the user to input report contents (S1714). The user specifies the attached file as needed.
[0194]
Then, the system changes the processing state 1009 shown in FIG. 10 to “processed” and saves the input contents (S1715). FIG. 25 shows a processing flow when reporting completion. Here, if there is a child WF whose processing state 1009 is not “processed”, all processing states 1009 and below that child WF are set to “cancel”.
[0195]
Then, the system notifies the instructor of the completion report by e-mail (S1717). Thereafter, the system ends the processing.
[0196]
On the other hand, if the system determines in step S1713 that the notification is not a completion report, the system instructs the user to input a progress status 1014 illustrated in FIG. 10 (S1718). The progress status 814 is displayed at a completed rate such as 50%.
[0197]
Then, the system instructs the user to input the contents of the interim report (S1719). Here, the user specifies an attached file as needed.
[0198]
Then, the system sets the processing state 1009 shown in FIG. 10 to the “temporary storage state” and saves the input contents. Thereafter, the system ends the processing.
[0199]
Next, the table processing at the time of approving / returning a child workflow will be described with reference to FIG. FIG. 18 is a processing flow of the system when approving / returning a child workflow. The system executes a process on the WF engine 512 to which the approver belongs according to the input from the approver.
[0200]
The system starts this processing in response to the user selecting the approval list 612 from the workflow menu 602 shown in FIG.
[0201]
First, the system determines whether the approver has selected approval (S1501).
[0202]
If the system determines in S1801 that the approver has selected approval, the system updates the forwarding management table 1000 shown in FIG. 10 (S1802).
[0203]
The system instructs the user to update the approver record in the forwarding management table 1000 shown in FIG. This approver record is a record whose forwarding order 1003 is “3”.
[0204]
Then, the system sets the processing state 1009 to “completed”, and sets the processing date and time 1008, the processor name 1007, the processor ID 1006, and the like according to the input from the user. Thereafter, the system ends the processing.
[0205]
On the other hand, if the system determines in S1801 that the approver does not select approval, the system updates the forwarding management table 1000 shown in FIG. 10 (S1503).
[0206]
The system instructs the user to update the reporter record and the approver record in the forwarding management table 1000 shown in FIG. This reporter record is a record whose forwarding order 1003 is “2”, and this approver record is a record whose forwarding order 1003 is “3”.
[0207]
Then, the system sets the processing state 1009 to “completed”, and sets the processing date and time 1008, the processor name 1007, the processor ID 1006, and the like according to the input from the user.
[0208]
The system sets the processing state 1009 of the reporter record to “return”.
[0209]
Further, the system sets the processing status 1009 of the approver record to "return", and sets the processing date and time 808, the processor name 807, the processor ID 806, and the like for recording. Thereafter, the system ends the processing.
[0210]
Next, with reference to FIG. 19, a table process when a child WF is created will be described. FIG. 19 is a processing flow of the system when a child workflow is registered. The system executes processing on the WF engine 512 to which the instructor belongs according to the input from the instructor.
[0211]
The system starts this processing in response to the user selecting new creation 604 from the workflow menu 602 shown in FIG.
[0212]
First, the system adds a new record to the flow management table 900 shown in FIG. 13 (S1901). Then, a WFID, which is unique identification information, is assigned to the workflow. The system stores the numbered WFID in the WFID 902 of the flow management table 900 shown in FIG.
[0213]
At this time, the workflow management table 900 sets parent WF related information. The parent WF related information is a parent WFE identification 903, a parent WFID 904, and a parent WF processor ID 905 shown in FIG.
[0214]
When the input WF type 906 is the broadcast unit WF or the group unit WF, the system sets the answer type 907. In FIG. 9, since the WF type 906 is a unit WF, the system sets NULL to the answer type 907.
[0215]
Further, the system sets a processing time limit setting 911, a process when the processing time limit is reached 912, and a reference restriction 913 in accordance with the input from the user. The system sets the processing time limit setting 911 within the processing time limit of the parent WF.
[0216]
Next, the system newly adds a record to the forwarding management table 1000 shown in FIG. 13 (S1902).
[0219]
The system adds an indicator record whose forwarding order 1003 shown in FIG. 10 is “1”.
[0218]
Then, the system sets the instruction content according to the input from the user. At this time, if there is an attached document, the system sets “1” in the column of attached document presence 1012. At this time, the system sets the processing state 1009 to “Draft”.
[0219]
Then, the system adds a reporter record whose forwarding order 1003 is “2”. At this time, the system sets the processing state 1009 to “unprocessed”.
[0220]
If the input WF type 906 is a unit WF, the system generates only one record. Then, the system sets the WFE to which the reporter belongs and the ID to the forwarding destination WFE 1004 and the processor ID 1006.
[0221]
When the input WF type 906 is a broadcast unit WF, the system generates records for the number of broadcast persons. Then, the system sets the WFE to which each reporter belongs and the ID to the forwarding destination WFE 81004 and the processor ID 1006.
[0222]
If the input WF type 906 is a group-based WF, the system generates a record. At this time, the system generates only one record if “one-person answer is required”, and generates records for all the groups if “all-members are required”. Then, the system sets the forwarding destination WFE 1004 and the group ID 1006.
[0223]
In FIG. 10, since the WF type 906 is a unit WF, the system generates only one record.
[0224]
The system adds an approver record whose sending order is “3”. At this time, the system changes the processing state 1009 to “unprocessed”.
[0225]
Next, the system determines whether there is an attached document (S1903).
[0226]
If the system determines in step S1903 that there is no attached document, the process ends.
[0227]
On the other hand, if the system determines in S1903 that there is an attached document, it adds a new record to the document management table 1200 shown in FIG. 13 (S1904). At this time, the system adds new records by the number of attached documents. Then, the system sets “1” to the forwarding order 1201 shown in FIG. Thereafter, the system ends the processing.
[0228]
Referring to FIG. 20, the table processing at the time of reporting the completion of the workflow will be described. FIG. 20 is a processing flow of the system at the time of the completion report. The system executes processing on the WF engine 512 to which the reporter belongs according to the input from the reporter.
[0229]
The system starts this processing in response to the input of the report content (S1714) shown in FIG.
[0230]
First, the system determines whether the processing state 1009 of the reporter record of the input person is “processed” (S2001). This reporter record is a record in which the forwarding order 1003 is “2”. If the system determines in step S2001 that the processing status 1009 of the reporter record is "processed", the process ends.
[0231]
On the other hand, in S2001, when the system determines that the processing state 1009 of the reporter record is not “processed”, the system updates the reporter record in the forwarding management table 1000 shown in FIG. 10 (S2002). This forwarding management table 1000 is updated based on the WF type 906 and the answer type 907 shown in FIG.
[0232]
First, when the WF type 906 is a unit WF, the system determines the reporter record instruction / report contents 1013, the reporter progress status 1014, the report status 1015, the processor name 1007, and the processing date and time in accordance with the input of the reporter. 1008 is set. Then, the system sets the processing state 1009 to “processed”. When the WF type 906 is the unit WF, there is only one reporter record as shown in FIG.
[0233]
Next, when the WF type 906 is the broadcast unit WF, the system adds the instruction / report contents 1013, the reporter progress status 1014, the report status 1015, the processor name 1007, and the processing date and time 1008 to the report record of the input person. Set. Further, the system sets the processing state 1009 to “processed”.
[0234]
If the WF type 906 is a broadcast unit WF and the answer type 907 is “Answer required”, the system displays the processing status 1009 of other reporter records in addition to the reporter's report record. Set to “Processed”.
[0235]
If the WF type 906 is a group-based WF and the answer type 907 is “all respondents are required”, the system adds instructions / report contents 1013 and reporter progress 1014 to the reporter record according to the input of the reporter. , A report status 1015, a processor name 1007, and a processing date and time 1008. Here, only the report record of the input person is changed. Then, the system sets the processing state 1009 to “processed”.
[0236]
If the WF type 906 is a group-based WF and the answer type 907 is “one-person required”, the system sets the processor ID 1006 in the reporter record according to the input of the reporter. Further, the system sets an instruction / report content 1013, a reporter progress status 1014, a report status 1015, a processor name 1007, and a processing date and time 1008. Then, the system sets the processing state 1009 to “processed”.
[0237]
Next, the system determines whether there is an attached document (S2003). If the system determines in S2003 that there is no attached document, the process ends.
[0238]
On the other hand, if the system determines in S2003 that there is an attached document, it adds a new record to the document management table 1200 shown in FIG. At this time, the system adds new records by the number of attached documents. Then, the system sets “2” to the forwarding order 1003 shown in FIG. 10 (S2004). Then, the system ends the processing.
<Approval execution process>
With reference to FIG. 21, the processing of the system when the user executes the approval will be described. FIG. 21 is a processing flow of executing the approval. The system executes processing on the WF engine 512 to which the instructor belongs according to the input from the instructor.
[0239]
The user who executes the approval first logs in to the system (S2101). This user is both the approver and the instructor.
[0240]
Next, the user selects the unapproved list 612 from the workflow menu 602 shown in FIG. 6 (S2102).
[0241]
The system causes the workflow to execute approval from the unapproved list 612 to be selected (S2103). Here, the user selects one workflow for executing approval.
[0242]
The system displays the selected workflow and prompts the user to confirm the report (S2104). Here, the user confirms the report content of the selected workflow.
[0243]
The system determines whether the user has selected to execute the approval (S2105). Here, the user approves or returns the report content. If the system determines in S2105 to approve, the system instructs the user to input a comment (S2106). The user enters a comment on the report as needed. This comment is stored in the instruction / report content 1013 shown in FIG.
[0244]
The system changes the processing state to the completed state and stores the input contents (S2107). That is, the system changes the processing state 1009 shown in FIG. 10 to “completed”. The processing flow at this time is shown in FIG. Thereafter, the system ends the approval execution process.
[0245]
On the other hand, if the system determines in S2105 that approval is not to be given, it instructs the user to input a comment (S2108). The user inputs a comment such as a correction request for the report content in the instruction / report content 1013 as necessary.
[0246]
The system returns the processing and saves the input contents (S2109). That is, the system changes the processing state 1009 shown in FIG. 10 to “return”. FIG. 22 shows a processing flow in this case.
[0247]
The system notifies the reporter of the return of the report content by e-mail, and instructs re-execution of the process (S2110). Thereafter, the system ends the processing.
[0248]
Next, with reference to FIG. 22, the table processing at the time of approval / return of the workflow will be described. FIG. 22 is a processing flow of the system when the workflow is approved / returned. The system executes a process on the WF engine 512 to which the approver belongs according to the input from the approver. This processing flow is basically the same as the approval / return processing in the case of the child workflow shown in FIG.
[0249]
The system starts this processing in response to the user selecting the approval list 612 from the workflow menu 602 shown in FIG.
[0250]
First, the system determines whether the approver has selected approval (S2201). If the system determines in S2201 that the approver has selected approval, the system updates the forwarding management table 1000 shown in FIG. 13 (S2202).
[0251]
The system instructs the user to update the approver record in the forwarding management table 1000 shown in FIG. This approver record is a record whose forwarding order 1003 is “3”.
[0252]
Then, the system sets the processing state 1009 to “completed”, and sets the processing date and time 1008, the processor name 1007, the processor ID 1006, and the like according to the input from the user. Thereafter, the system ends the processing.
You.
[0253]
On the other hand, if the system determines in S2201 that the approver does not select approval, the system updates the forwarding management table 1000 shown in FIG. 10 (S2203).
[0254]
The system instructs the user to update the reporter record and the approver record in the forwarding management table 1000 shown in FIG. This reporter record is a record whose forwarding order 1003 is “2”, and this approver record is a record whose forwarding order 1003 is “3”.
[0255]
Then, the system sets the processing state 1009 to “completed”, and sets the processing date and time 1008, the processor name 1007, the processor ID 1006, and the like according to the input from the user. The system sets the processing state of the reporter record to "Send Back".
[0256]
Further, the system sets the processing state 1009 of the approver record to “return” for recording, and sets the processing date and time 1008, the processor name 1007, the processor ID 1006, and the like. Thereafter, the system ends the processing.
<Other processing flow>
Next, with reference to FIG. 23, a description will be given of a dunning and aborting process executed in the scheduled process. FIG. 23 is a processing flow of the dunning and discontinuation by the regular processing. Preferably, the system automatically performs this process once a day.
[0257]
The user sets a time (N) at which the dunning is started in the WF engine 512 in advance. For example, the user sets the dunning start time (N) to “7” when setting to warn the worker that one week before the processing deadline has come. The dunning date can be calculated by subtracting the dunning start time (N) from the processing deadline date.
[0258]
Then, the system searches for the unprocessed workflow, and notifies the worker of a reminder mail. However, if the processing deadline has been exceeded and the processing at the deadline is “discontinued”, a reminder email is not notified, and the corresponding WF and all lower WFs are set as “discontinued” to complete the processing. .
[0259]
First, the system extracts, on the WF engine 512, a workflow in which the stop flag 914 of the flow management table 900 is set to “NULL”. The system also extracts a workflow whose processing status of the reporter in the forwarding management table 1000 related to the workflow is not “processed” (S2301).
[0260]
Then, the system determines whether the date has reached the dunning date (processing deadline -N) or whether the processing deadline 911 is "NULL" (S2302). Here, when the system determines that the date has not reached the dunning date (treatment deadline-N) or that the processing deadline 911 is “NULL”, the processing ends.
[0261]
On the other hand, in S2302, when the system determines that the date has reached the dunning date (treatment deadline -N), the system determines whether the date has not reached the processing deadline 911 (S2303). Here, if the system determines that the date has not reached the processing deadline 911, the system acquires the reporter's mail address 704 from the user management table 700. Then, the system sends a reminder email to the reporter (S2304). Thereafter, the system ends the processing.
[0262]
In S2303, when the system determines that the date has reached the processing deadline 911, the system determines whether the deadline processing 912 is "discontinued" (S2305). Here, when the system determines that the process 912 at the time limit has expired is “discontinuation”, the system extracts the corresponding WF and all lower WFs. Then, the system changes the stop flag 914 of the workflow management table 900 to “discontinue” and transmits a notification mail to the instructor (S2306). Thereafter, the system ends the processing.
[0263]
Next, a search process on the unprocessed list screen will be described with reference to FIGS.
[0264]
FIG. 24 is a conceptual diagram of an unprocessed search at the time of cooperation with another server. This conceptual diagram is a simplified diagram of the system configuration diagram shown in FIG. The terminal 2401, the company WFE 2402, and the cooperation destination WFE 2403 are connected via a network. The in-house WFE 2402 is a workflow engine 513 of the workflow server 502 shown in FIG. 5, and the cooperating WFE 2403 is a workflow engine 513 of the cooperating workflow server 502.
[0265]
When the user's terminal 2401 selects the unprocessed list, the system executes an unprocessed WF search on the in-house WFE 2402 (S2401).
[0266]
At the same time, the system inquires of the cooperation destination FWE 2403 whether or not there is an unprocessed workflow set as the forwarding destination for itself (S2402). Upon receiving this inquiry, the cooperation destination WFE 2403 searches for an unprocessed workflow whose forwarding destination is set as the inquiry source.
[0267]
The cooperation destination WFE 2403 answers the search result to the company WFE 2402 (S2403).
[0268]
The system merges the search result of the in-house WFE 2402 with the answer of the cooperation destination WFE 2403 and displays an unprocessed list on the terminal 2401 (S2404).
[0269]
FIG. 25 shows query contents at the time of search in the in-house WFE 2402 and the cooperation destination WFE 2403.
[0270]
The system searches for an unprocessed workflow from the flow management table 900 and the forwarding management table 1000 shown in FIG. 9 under the following conditions.
[0271]
In the flow management table 900, the stop flag 914 is “NULL”.
The WEF identification 901 is the search target WFE. The WFE identification 901 is the WFE identification of the forwarding management table 1000. The WFID 902 is the WFID of the forwarding management table 1000.
[0272]
On the other hand, in the forwarding management table 1000, the forwarding destination WFE 1004 is its own WFE. The processor ID 1006 is its own processor ID, or the forwarding destination group is the group ID 1005 of the group ID, the WFE identification 1001 is its own WFE, and the processor ID 1006 is its user ID. The processing state 1009 is “unprocessed”, “temporary storage”, or “return”.
[0273]
The system extracts a workflow satisfying the above conditions as an unprocessed workflow.
<Effects of Embodiment>
The business management system according to the present embodiment manages business by a combination of basic workflows (unit WF), including a case where the operation branches in the middle. Therefore, the entire workflow can be managed in accordance with an arbitrary instruction system.
[0274]
The instruction system can be specified one by one. Therefore, it is possible to flexibly respond to a change in the instruction system.
[0275]
By the broadcast unit WF and the group unit WF, a superior can collectively designate a plurality of instruction systems. Also, in the broadcast unit WF and the group unit WF, by setting "all members must answer", all of the plurality of target persons can be answered at once. In the broadcast unit WF and the group unit WF, the instructor can designate a plurality of target persons without specifying the respondents by setting “one person required answer”, and have one arbitrary person answer.
[0276]
The management engine for each unit WF that constitutes the entire workflow can be linked even with physically separate engines. This makes it possible to easily manage a workflow that extends between the parent company and the subsidiary company, or between the ordering company and the order receiving company.
[0277]
The reporter can set an intermediate state even before the completion report. Thereby, the instructor can grasp the progress of the work.
[0278]
The reporter can specify the status when reporting completion. The status is, for example, completed, aborted, and needs to be reviewed. By reporting the status of “review required” to the instructor, the instructor who has received the report can also instruct the specific forwarding destination on the second lap. The reporter of the child WF can cascade-reference instructions and the like higher than the direct instructor. The instructor of the parent WF can sequentially refer to the processing (progress) status of the child WF and the grandchild WF. Reference from the child to the parent and the instruction content / processing (progress) status from the parent to the child can be permitted or prohibited according to the setting of authority or the like. A chain sequence of WF can be illustrated. When all of the child WFs are completed, the completion status (completion date, person in charge, completion status, comment, etc.) of each child WF can be automatically compiled for reporting to the parent WF. When the parent WF is stopped, the child WF and grandchild WF can also be stopped in a chain. A time limit can be set such that a time limit is set at the time of WF creation and a dunning is automatically performed when approaching the time limit set in advance, or automatically stopped when the time limit is exceeded. By enabling the deadline of the child WF to be set within the deadline of the parent WF, deadline management in a chain of instruction systems can be realized with consistency. At this time, if the parent WF is overdue and terminated, the child WF is also terminated.
<Modification>
In the above-described embodiment, the system configuration using WWW has been described with reference to FIG. However, a system configuration that does not use WWW may be used. Therefore, a modified example of a system configuration using a client / server will be described with reference to FIG.
[0279]
In a system using WWW, the workflow server 502 includes a workflow engine 512 and a WWW server 513, and the terminal 501 includes a browser.
[0280]
However, in a system using a client / server, the workflow server includes a server application, and the terminal includes a client application.
[0281]
Each terminal communicates with the server application on the workflow server using the client application. In this way, the business management system can display the menu on the screen as in FIG. As a result, the user can create and process a workflow using the client application. The rest of the system configuration is the same as that of the system using WWW, and the description is omitted.
[0282]
Note that, in the present modification, cooperation with another server is not performed, but cooperation with another workflow server or another DB server may be performed via a network such as the Internet as shown in FIG.
<Computer-readable storage medium>
A program that causes a computer to execute any of the processes of the above-described embodiments can be recorded on a computer-readable storage medium. The system described in the above embodiment can be provided by causing a computer to read and execute the program in the storage medium.
[0283]
Here, a computer-readable storage medium refers to a storage medium that stores information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read from a computer. . Among such storage media, those removable from a computer include, for example, a flexible disk, a magneto-optical disk, a CD-ROM, a CD-R / W, a DVD, a DAT, an 8 mm tape, a memory card, and the like.
[0284]
Further, as a recording medium fixed to the computer, there is a hard disk, a ROM (Read Only Memory), or the like.
[0285]
The above embodiment does not limit the scope of the present invention in any way, and various modifications may be appropriately made within a range that can be understood by those skilled in the art.
<Others>
Further, this embodiment discloses the following invention.
(Supplementary Note 1) a business module including: an instruction unit for designating a person who processes a business; a report unit for executing a business report to the instructor;
A system storage unit that records information related to an instruction system including an instructor designated by the instructing unit, a reporter executed by the reporting unit, or an approver approved by the approval unit, based on an execution result by the business module; ,
A business management system comprising: a management unit that manages a business by combining information relating to an instruction system by the business module.
(Supplementary Note 2) The business management system according to Supplementary Note 1, wherein the management unit further includes a system-related storage unit that stores information related to the instruction system by a plurality of business modules in an associated manner.
(Supplementary note 3) The business management system according to supplementary note 1 or 2, further comprising a state storage unit that stores a state of the instruction, the report, or the approval.
(Supplementary Note 4) The business management system according to any one of Supplementary notes 1 to 3, wherein the business module further includes a plurality of instruction units for specifying a plurality of persons who process the business.
(Supplementary note 5) The job management system according to any one of supplementary notes 1 to 4, wherein the task module further includes a group designating unit that specifies a group that processes the task.
(Supplementary Note 6) An operation module for executing an instruction step of designating a person who processes the operation, a reporting step of executing an operation report to the instructor, and an approval step of approving the operation report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
A step of managing a task by combining information relating to the instruction system by the task module.
(Supplementary note 7) The program according to supplementary note 6, further comprising the step of storing information related to the instruction system of the plurality of business modules in association with each other.
(Supplementary note 8) The program according to supplementary note 6 or 7, further comprising a step of storing the status of the instruction, the report, or the approval.
(Supplementary note 9) The program according to any one of supplementary notes 6 to 8, wherein the business module further executes a step of designating a plurality of persons who process the business.
(Supplementary note 10) The program according to any one of Supplementary notes 6 to 9, wherein the business module further executes a step of specifying a group that processes the business.
(Supplementary Note 11) A task module for executing an instruction step of designating a person who processes a task, a reporting step of executing a task report to the instructor, and an approval step of approving the task report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
A computer-readable storage medium storing a program for executing a step of managing a business by combining information relating to an instruction system by the business module.
(Supplementary note 12) The storage medium according to supplementary note 11, which further executes a step of storing information relating to the instruction system by the plurality of business modules in association with each other.
(Supplementary note 13) The storage medium according to supplementary note 11 or 12, further comprising a step of storing the status of the instruction, the report, or the approval.
(Supplementary note 14) The storage medium according to any one of Supplementary notes 11 to 13, wherein the business module further executes a step of specifying a plurality of persons who process the business.
(Supplementary note 15) The storage medium according to any one of Supplementary notes 11 to 14, wherein the business module further executes a step of specifying a group for processing the business.
(Supplementary Note 16) A task module for executing an instruction step of designating a person who processes a task, a reporting step of executing a task report to the instructor, and an approval step of approving the task report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
And a step of managing a business by combining information relating to the instruction system by the business module.
[0286]
【The invention's effect】
As described above, the present invention can provide a task management system capable of managing tasks by combining basic instruction systems using task modules.
[Brief description of the drawings]
FIG. 1 is a diagram showing an embodiment of a workflow based on a ring structure type information chain.
FIG. 2 is a diagram showing an embodiment of a workflow having a branch by a ring structure type information chain.
FIG. 3 is a diagram showing an embodiment using a broadcast unit WF.
FIG. 4 is a diagram showing an embodiment using a group unit WF.
FIG. 5 is a diagram showing a system configuration using WWW.
FIG. 6 is a diagram showing a module configuration.
FIG. 7 is a diagram showing a user management table.
FIG. 8 is a diagram showing a group management table.
FIG. 9 is a diagram showing a flow management table.
FIG. 10 is a diagram showing a forwarding management table (unit WF).
FIG. 11 is a diagram showing a forwarding management table (broadcast unit WF).
FIG. 12 is a diagram showing a document management table.
FIG. 13 is a relationship diagram of each table.
FIG. 14 is a diagram showing an overall operation.
FIG. 15 is a diagram illustrating creation of a new workflow.
FIG. 16 is a diagram showing a processing flow at the time of new creation.
FIG. 17 is a diagram showing execution of work.
FIG. 18 is a diagram showing a processing flow of approval / return of child WF.
FIG. 19 is a diagram showing a processing flow of child WF creation.
FIG. 20 is a diagram showing a processing flow of a completion report.
FIG. 21 is a diagram showing execution of approval.
FIG. 22 is a diagram showing a processing flow of workflow approval / return.
FIG. 23 is a diagram showing a processing flow of dunning and discontinuation by a regular processing.
FIG. 24 is a conceptual diagram of an unprocessed search at the time of cooperation with another server.
FIG. 25 is a diagram showing query contents at the time of unprocessed search.
FIG. 26 is a diagram showing a system configuration using a client / server.
FIG. 27 is a diagram showing a conventional workflow.
FIG. 28 is a diagram illustrating an example of an instruction / reporting task using a conventional workflow.
[Explanation of symbols]
501 ... terminal
502: Workflow server
503 ... DB server
504 ... Authentication server
505 ... Mail server
511 ... Browser
512: Workflow engine
513: WWW server
514: User management
515: Group management
516: Flow management
517: Forwarding management
518: Document management
601… Login
602: Workflow menu
603 ... End
604… New creation
605: Created list
606: Content / processing state reference
607 ... Cancel
608: Chain reference
609: Unprocessed list
610: Progress status setting
611: Child WF creation
612: Unapproved list
613: Approval
614… Free search
615 ... List of search results
616: Agent registration
617: Proxy processing
900: Flow management table
1000 ... forwarding management table (unit WF)
1100: Forwarding management table (broadcast unit WF)
1200: Document management table

Claims (12)

A business module having instruction means for designating a person who processes the business, a report means for executing a business report for the instructor, and an approval means for approving the business report;
A system storage unit that records information related to an instruction system including an instructor designated by the instructing unit, a reporter executed by the reporting unit, or an approver approved by the approval unit, based on an execution result by the business module; ,
A business management system comprising: a management unit that manages a business by combining information relating to an instruction system by the business module. The business management system according to claim 1, wherein the management unit further includes a system-related storage unit configured to store information related to an instruction system by a plurality of business modules in a related manner. The business management system according to claim 1, further comprising a status storage unit configured to store a status of the instruction, the report, or the approval. 4. The business management system according to claim 1, wherein the business module further includes a plurality of instruction units for specifying a plurality of persons who process the business. The business management system according to claim 1, wherein the business module further includes a group instruction unit that specifies a group that processes the business. Including a task module for executing an instruction step to specify a person who processes a task, a reporting step to execute a task report for the instructor, and an approval step to approve the task report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
A step of managing a task by combining information relating to the instruction system by the task module. The program according to claim 6, further comprising the step of storing information related to the instruction system by a plurality of business modules in association with each other. 8. The program according to claim 6, further comprising the step of storing the status of the instruction, the report, or the approval. The program according to claim 6, wherein the business module further executes a step of designating a plurality of persons who process the business. The program according to claim 6, wherein the business module further executes a step of specifying a group that processes the business. Including a task module for executing an instruction step to specify a person who processes a task, a reporting step to execute a task report for the instructor, and an approval step to approve the task report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
A computer-readable storage medium storing a program for executing a step of managing a business by combining information relating to an instruction system by the business module. Including a task module for executing an instruction step to specify a person who processes a task, a reporting step to execute a task report for the instructor, and an approval step to approve the task report,
Based on the execution result by the business module, a step of recording information related to the instruction system including the instructor designated in the instructing step, the instructor executed in the reporting step, or the approver approved in the approval step,
And a step of managing a business by combining information relating to the instruction system by the business module.

Images