JP2007156678A - Workflow system and pending electronic document processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To smoothly process an electronic document by entrusting approval to an optimum proxy authorizing person on a delivery route so as to satisfy the approval due date desired by a drafter even when it is found that the regular person in charge of the authorization on a work flow is absent, etc. <P>SOLUTION: The CPU of a work flow server 200 detects a pending electronic document whose work flow processing for a succeeding approving/authorizing person has not processed for a prescribed suspension period, refers to the schedule of the approving/authorizing person being the superior to the succeeding approving/authorizing person on the delivery route of the detected pending electronic document, and determines the superior as the proxy authorizing person, based on the referred schedule of the approving/authorizing person being the superior and on the suspension limit. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to processing of a staying electronic document which is an unprocessed matter staying in the workflow system due to absence of a person in charge of approval.

  One infrastructure that improves the efficiency of electronic document approval is a workflow system.

  The workflow system sets the distribution unit (distribution order) of the electronic document between the distributors in advance by registering the distribution unit (distribution order) of the electronic document between the distributors in advance by the organization, role, or user. Try to distribute documents.

  In many workflow systems, if the person in charge of distribution of electronic documents is absent, an electronic document that should be distributed to the person in charge of approval is set up in advance as a person in charge of approval. Is received on behalf of the agent, and the business process is avoided by acting on behalf of the business process.

  However, in actual operation, there was a sudden use of a formal official in charge of the workflow, such as illness or an emergency business trip, so there was no agent in charge and no long-term results. It was causing the retention of electronic documents.

  As a proposal for solving such a problem, there is JP-A-11-219393.

  In this case, instead of the person in charge of approval on the workflow, an agent in charge of the person in charge of approval is set in advance, and the electronic document requested to be processed by the person in charge of approval on the workflow is set in advance. An electronic device that determines whether or not the processing is completed within a processing period at a predetermined timing, and when it is determined that the process is staying, an electronic device for requesting the agent in charge of the substitute in charge of processing the electronic document It is to generate and send mail.

Thereby, even when a regular person in charge in the workflow is absent, the system side can request the substitute person in charge for electronic document processing.
JP 11-219393 A

  However, the above-described workflow system sends an electronic document processing request email to a predetermined decision-making agent in charge at the stage where the electronic document has been retained due to the absence of a regular business person on the workflow for a long time. Therefore, if the person in charge of approval and the person in charge of the agency suddenly become absent for a long time at the same time, it will cause the business case to stay for a long period of time. You will lose.

  Further, even if the same electronic document is an important electronic document such as an in-house approval document or a personnel transfer application, inconvenience may occur if it is unconditionally delivered to a preset approval agent.

  In the first place, delivery to the approval agent should be done only when the authorized approval person in the workflow explicitly sets proxy delegation. In the case of electronic document retention due to sudden reasons, In many cases, it is safer to delegate the decision of the case to the senior manager from the viewpoint of security.

  If the substitute approver in the absence of the person in charge of approval is the superior who reports directly to the electronic document delivery route, there may be a problem that the approval of electronic documents will be delayed in the absence of the supervisor.

  In addition, even when all superiors on the delivery route who are not absent for a long time are delegated as approval agents, depending on the schedule of the agent, the approval of the drafter There is a problem that approval cannot be completed by the desired completion date.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to maintain a staying electronic document whose workflow processing of the electronic document by the next approver / authorizer has exceeded a predetermined staying deadline. Detecting and referring to the schedule of the approval / authorizer who is the superior of the next approval / authorizer on the delivery route of the detected electronic document, and the schedule of the approved / authorizer who is the superior is referred to Even if it is found that there is no regular official in charge of the workflow by deciding the superior to be delegated as the decision-making agent based on the stay deadline, the drafter's desired date for completion of the decision is also determined. In order to be satisfied, a mechanism is provided that can delegate proxy decision making to the best substitute decision maker on the delivery route, and facilitate smooth processing of electronic documents.

  The present invention relates to a workflow system that circulates an electronic document according to a predetermined delivery route and performs an approval / decision workflow process, a storage unit that stores organization information of the approval / decisioner, an approval / decisioner schedule, and A stay detection unit for detecting a staying electronic document whose workflow processing of an electronic document by an approval / authorizer has exceeded a predetermined stay deadline, and a next approval on the delivery route of the staying electronic document detected by the stay detection unit -Refers to the approval / authorizer schedule corresponding to the superior of the authorizer, and decides and controls the superior to be delegated as the authorizing agent based on the approval / authorizer schedule referred to by the superior and the retention period And a control means.

  According to the present invention, it is possible to prevent stagnation of a workflow and to promote the efficiency of the workflow work to be processed.

  Therefore, in the workflow system, there is an effect that an unprocessed matter staying due to the absence of the person in charge of approval or the like is notified to the system administrator of the status, and staying for a long time can be avoided.

[First Embodiment]
Hereinafter, details of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of a workflow system to which this embodiment is applied.

  The workflow system according to this embodiment includes a workflow and slip design computer terminal (workflow and slip design terminal) 400, and a workflow operation computer terminal (workflow operation) provided corresponding to a processor (person in charge) who performs a task. Terminal 300), various tables for executing workflows, and a workflow server 200 for storing various programs.

  The workflow and slip design terminal 400, the workflow operation terminal 300, and the workflow server 200 are each connected to a network 500 and operated.

  The workflow and slip design terminal 400 includes a slip designer program 401 and a system management program 402. The workflow and slip design terminal 400 communicates with a management program (not shown) on the workflow server 200 to create a slip definition and a workflow to be used in the workflow system. Create various definition information used in the system. For example, the workflow and slip design terminal 400 can register an organization table, role table, user table, user role table, delivery definition information, various slip information, and the like in the workflow server 200. In order to perform these operations, the workflow and slip design terminal 400 can connect to the workflow server 200 by inputting its own identification information.

  The workflow operation terminal 300 uses the Web browser 301 executed on the workflow operation terminal 300 to transmit access information regarding the slip to the workflow server 200 by HTTP, and receives the result. At this time, the generated display / calculation processing is executed by using a Java (registered trademark) applet 302 or the like. The workflow operation terminal 300 is arranged for a person in charge (for example, a drafter, a section manager, a department manager, etc.) who performs a predetermined job specified in advance.

  The workflow server 200 stores information related to the workflow system (organization table, role table, user table, user role table, delivery definition information, delivery information table, schedule data of the person in charge of approval, system administrator table, etc.). DataBaSe Management System) 205, an HTTP server 201 for receiving a request from a computer terminal for workflow operation and executing the request, a servlet engine 202, a workflow program 204, and an SMTP server 203 for realizing a workflow notification function. .

  The workflow server 200 can acquire predetermined schedule information (schedule information of each user input using general schedule management software) stored in the external DB.

  Hereinafter, a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and the slip design terminal 400 illustrated in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a block diagram showing an example of a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and slip design terminal 400 shown in FIG.

  In FIG. 2, reference numeral 101 denotes a CPU, which is stored in a ROM 103 or a hard disk (HD) 104 (any other storage device such as a flexible disk, CD-ROM, DVD-ROM, etc.) 104. The entire computer is controlled by loading the program onto the RAM 102 and executing it. The RAM 102 is used as a work area for the CPU 101.

  A communication interface 107 enables connection to the network 500. An input device 105 corresponds to a pointing device such as a keyboard or a mouse. Reference numeral 106 denotes a display device, which includes a CRT, LCD, or the like.

  Note that the RDBMS 205 of the workflow server 200 illustrated in FIG. 1 is built in the HD 104 of the workflow server 200. Further, the HTTP server 201, the servlet engine 202, the workflow program 204, and the SMTP server 203 of the workflow server 200 are realized by the CPU 101 of the workflow server 200 loading and executing a program stored in the HD 104 on the RAM 102. The

  Further, the Web browser 301 of the workflow operation terminal 300 shown in FIG. 1 is realized by the CPU 101 of the workflow operation terminal 300 loading and executing a program stored in the HD 104 on the RAM 102.

  Further, the Java (registered trademark) applet 302 of the workflow operation terminal 300 shown in FIG. 1 is executed by the CPU 101 of the workflow operation terminal 300 executing the program downloaded from the workflow server 200 on the Web browser 301. Realized.

  The slip designer program 401 and the system management program 402 of the workflow and slip design terminal 400 shown in FIG. 1 are loaded into the RAM 102 by the CPU 101 of the workflow and slip design terminal 400 by loading a program stored in the HD 104. This is realized by executing.

  FIG. 3 is a schematic diagram showing the flow of slips in the workflow system shown in FIG.

  In the workflow system according to the present embodiment, as shown in FIG. 3, using the workflow operation terminal 300, the person in charge defined by an organization and a role called a node for issuing a slip and approving / rejecting the slip. Do. A business process is defined as a group of nodes to which a slip is delivered.

  FIG. 4 is a data configuration diagram showing an example of the data structure of the organization table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This organization table is for storing information related to the organization for realizing the workflow.

  In the organization table shown in FIG. 4, the organization ID is an arbitrary organization name written as a code, and always covers the upper organization ID. The organization name indicates the name on the display of the organization ID. Furthermore, the parent organization ID indicates a higher organization ID.

  FIG. 5 is a data configuration diagram showing an example of the data structure of the role table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This role table is for storing information related to roles for realizing the workflow.

  In the role table shown in FIG. 5, the role ID is an arbitrary role name written as a code. The role name indicates a name on the display of the role ID.

  FIG. 6 is a data configuration diagram showing an example of the data structure of the user table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This user table is for storing user information for using the workflow.

  In the user table shown in FIG. 6, the user ID displays the user as an arbitrary code. The password is used for authentication together with the user ID when logging into the workflow system. Furthermore, the user name indicates the name on the display of the user ID.

  FIG. 7 is a data configuration diagram showing an example of the data structure of the post table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This post table is used to store post information for using the workflow.

  As shown in FIG. 7, each record in the post table includes “user ID” defined in the user table, “role ID” defined in the role table, and “organization” defined in the organization table. ID ”.

  FIG. 8 is a data configuration diagram showing an example of the data structure of the delivery definition information stored in the RDBMS 205 of the workflow server 200 shown in FIG. The delivery definition information is for storing information defining a route through which the slip is delivered.

  Here, as an example, an example is shown in which the roles are delivered in the order of “employee” → “department manager” → “department manager” → “department manager” → “president”. When the delivery route of the slip is defined in this way, the delivery definition information of this delivery route is created as information of five records as shown in FIG.

  Hereinafter, a method for creating the delivery definition information will be described.

  For example, when the voucher name is “account expense”, the user first sets “account expense” as the voucher name from the workflow and voucher design terminal 400 using the system management program, and then sets each node. To do. Taking node 1 as an example, by setting a code “004” indicating a department manager in node 1 and selecting a target organization (here, “A company” with organization ID “80” is selected), Role ID “004”, “Route organization ID” indicating “Voucher name” as “Account expense”, “Organization ID” as “80”, “Node number” as “1”, “Route role ID” as “Department manager” Is set as an organization ID that plays a role. Here, “company A” with the organization ID “80” is selected as the target organization, and the delivery target person with the role ID “department manager” is not determined. Therefore, the route organization ID is “NULL” (indicated by a blank in the figure).

  FIG. 9 is a data configuration diagram showing an example of the data structure of the delivery information table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This delivery information table is generated based on the delivery definition information shown in FIG. 8 during delivery processing in the workflow system shown in FIG. 10, which will be described later, and stores the route, status, etc. of the workflow. It is. The delivery information table corresponds to a case where a user with the user ID “U0012” has started. In this case, the slip is delivered as user IDs “U0012”, “U0007”, “U0003”, “U0002”, “U0001”.

  As shown in FIG. 9, the delivery information table includes a “slip name” item 501, a “slip number” item 502, a “node number” item 503, a “processing user” item 504, a “status” item 505, and a “last processing date”. “Addition” item 506, “Payment completion desired” item 507, “Payment completion desired date” item 508, “Substituted” item 509, and the like.

  The “slip name” item 501 stores the slip name itself such as “account expense” at the time of drafting. In the “slip number” item 502, an identifier for identifying a slip is stored in the draft. The “processing user” item 504 stores the user ID of the processor corresponding to the “node number” item 503. The “state” item 505 stores information indicating a state such as “waiting for processing” or “processed”. The “date of last processing” item 505 stores the date and time when the node corresponding to the “node number” item 503 is processed.

  The “Payment completion desired” item 507, the “Payment completion desired date” item 508, and the “Substituted” item 509 will be described later.

  Hereinafter, the overall flow of the delivery processing procedure in the workflow system of the present invention will be described with reference to FIG.

  FIG. 10 is a flowchart showing an example of a first control processing procedure in the workflow system of the present invention, and corresponds to the delivery processing by the workflow program 204 of the workflow server 200 shown in FIG. In the figure, S5000 to S5013 indicate each step.

  First, when the CPU of the workflow server 200 that executes the workflow program 204 (hereinafter referred to as the CPU of the workflow server 200) receives a slip processing request from the workflow operation terminal 300 (step S5000), it starts delivery processing.

  The CPU of the workflow server 200 switches the delivery process based on the “draft”, “approval”, and “denial” request categories of the slip processing request received in step S5000 (step S5001).

  If the CPU of the workflow server 200 determines in step S5001 that the request category of the slip processing request received in step S5000 is “draft”, the CPU of the workflow server 200 in step S5002 As the information, node number “0” is set in the delivery information table. In the “processing user”, the user ID of the user who issued the draft is set.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, as shown in FIG. 8, a record with the node number “0” in the delivery information table includes “accompaniment cost” in the slip name, slip The slip number issued at the time of drafting (here, “00001”), the node number “0”, the processing user user ID “U0012”, and the status “processed” are set.

  Next, in step S5003, the CPU of the workflow server 200 sets the current node number to “1” and refers to the delivery definition information (FIG. 8) corresponding to the slip name of the slip processing request received in step S5000. Information of the number “1” (route role ID, route organization ID) is acquired, and the process proceeds to step S5008.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, the route role ID “004” and the route organization ID “NULL” are acquired.

  On the other hand, if the CPU of the workflow server 200 determines in step S5001 that the request category of the slip processing request received in step S5000 is “approved” or “denied”, the CPU of the workflow server 200 in step S5004. Acquires the current node number with reference to the delivery information table (FIG. 9).

  Next, in step S5005, the CPU of the workflow server 200 determines whether the request category of the slip processing request received in step S5000 is “approval” or “denied”, and determines that it is “approval”. In this case, in step S5006, after incrementing the current node number acquired in step S5004, the delivery definition information (FIG. 8) having the incremented current node number is referred to, and information on the current node number ( (Route role ID, route organization ID) is acquired, and the process proceeds to step S5008.

  On the other hand, if the CPU of the workflow server 200 determines in step S5005 that the request category of the slip processing request received in step S5000 is “denied”, the current node number acquired in step S5004 in step S5007. Is decremented, the current node number information (route role ID, route organization ID) is acquired with reference to the delivery definition information (FIG. 8) having the decremented current node number, and the process proceeds to step S5008.

  In step S5008, the CPU of the workflow server 200 uses the route role ID and route organization ID acquired in step S5003, S5006, or S5007 to refer to the user post information (FIG. 7) to determine the next delivery target user. The ID is determined (from the post table (FIG. 7), the role ID is the route role ID and the organization ID is the user ID of the route organization ID). When the acquired route organization ID is “NULL” (in the case of blank in FIG. 8), the organization ID to which the user ID corresponding to the node number one smaller than the current node number belongs is set as “route organization ID”. The next delivery target user ID is determined. Furthermore, when the next delivery target user ID cannot be determined even after this (when the role ID is the route role ID and the organization ID is not the route organization ID record in the user post information (FIG. 7)). The next delivery target user ID is determined with the parent organization ID of the organization ID as the “route organization ID”, and this process is repeated until the next delivery target user ID is determined.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, as shown in FIG. 9, the route role ID “004” of the node number “1” and the route organization ID “NULL” are shown in step S5003. ”Is acquired, and the user ID to be delivered is determined based on the acquired route role ID“ 004 ”and route organization ID“ NULL ”. Here, since the acquired route organization ID is “NULL”, the organization ID “8010101010” to which the user ID “U0012” corresponding to the node number “0” that is one smaller than the current node number “1” belongs is “route”. The next delivery target user ID is determined as the “organization ID”. At this time, since there is no record of the role ID “004” and the organization ID “8010101010” in the user post information (FIG. 7), the parent organization ID “80101010” of the organization ID “8010101010” is set as the “route organization ID”. The next delivery target user ID is determined. Here, referring to the user post information (FIG. 7), the role ID “004”, the user ID of the organization ID “8010101010” is “U0007”, and this user ID “U0007” is determined as the next delivery target user ID. Is done.

  Next, in step S5009, the CPU of the workflow server 200 determines whether or not the slip processing request received in step S5000 is from the final approver. The final approver determines whether the approval is from the approver of the role ID corresponding to the record of the maximum value of the node number in FIG. 8, and when the original final approver is delegated (proxy), Furthermore, it shall be the upper manager.

  When the CPU of the workflow server 200 determines in step S5009 that the slip processing request received in step S5000 is not from the final approver, in step S5011, the CPU of the workflow server 200 receives the request in step S5000. It is determined whether the request classification of the slip processing request is “approval” or “draft” or “denial”, and if it is determined that it is “approval” or “draft”, in step S5012, the delivery Information on the next node number is set in the information table (FIG. 9). At this time, the current node number is set in the “node number” item 503, the next delivery target user ID determined in step S 5009 is set in the “processing user” item 504, and the “status” item 505 is set in the “status” item 505. “Waiting for processing” is set, and the current date and time is set in the “last processing date” item 506. Then, the CPU of the workflow server 200 notifies the delivery target person of the workflow by the SMTP server 203 and ends the process.

  On the other hand, if the CPU of the workflow server 200 determines in step S5011 that the request category of the slip processing request received in step S5000 is “denied”, in step S5013, the above-described processing is performed from the delivery information table (FIG. 9). In addition to deleting the current node number, the SMTP server 203 notifies the delivery target person that the delivery target has been denied, and the process ends.

  On the other hand, if the CPU of the workflow server 200 determines in step S5009 that the voucher processing request received in step S5000 is from the final approver, in step S5010, the distribution information table (FIG. 9) In addition to deleting the delivery information, the SMTP server 203 notifies the drafter that all the approval has been approved, and the process ends.

  Hereinafter, the process at the time of long-term residence in this embodiment is demonstrated using FIGS.

  FIG. 11 is a diagram showing an example of an electronic document (slip) with a final decision completion deadline according to the present embodiment, which is displayed on the display device of the workflow operation terminal 300 at the time of voting and input to the workflow operation terminal 300. An input instruction can be given by the device.

  As shown in FIG. 11, for an electronic document with an approval completion deadline, a check box 601 for no approval completion desired and a check box 602 for approval completion desired are arranged in a normal electronic document. The check box 601 with no approval completion desired and the check box 602 with approval completed desired can be exclusively checked “ON”.

  If the desired check box is “ON”, the desired date of completion of approval is entered in the desired date of approval completion input field 603.

  When the voucher is issued, the CPU of the workflow server 200 stores the information in the check box 601 indicating that approval is not desired in a normal electronic document and the check box 602 indicating that approval is desired in the delivery information table shown in FIG. Is stored in the item “whether or not payment completion is desired”. Further, the CPU of the workflow server 200 stores the information in the approval completion desired date input field 603 in the “approval completion desired date” item 508 of the delivery information table shown in FIG. This process is executed in step S5002 in FIG.

  FIG. 12 is a diagram showing schedule data of a person in charge of approval on the electronic document delivery route in the present embodiment.

  The schedule data of the person in charge of approval is obtained by processing the schedule information of the person in charge input using general schedule management software as external data for the agency approval work, and processing the workflow server 200. Stored in the RDBMS 205.

  The schedule data of the person in charge of approval is created by the workflow server 200 for each issued slip based on the delivery information table of the slip when a slip desired to be settled is issued. is there.

  In FIG. 12, the schedule data of the person in charge of approval is composed of a person in charge column 701, a schedule column 702, and the like.

  The person-in-charge column 701 stores information (user name, user ID, etc.) that identifies the person in charge of approval on the delivery route. The schedule column 702 stores a schedule from the drafting date (draft date) to the desired date of completion of approval. If there is no desired date for completion of approval, a schedule for a predetermined period (for example, two weeks) is stored.

  The CPU of the workflow server 200 determines each person in charge of approval on the delivery route based on the delivery information table of the issued slip, and specifies information (user name, user ID, etc.) for identifying each person in charge of approval. Acquired and stored in the person-in-charge column 701. Further, the CPU of the workflow server 200 acquires the schedule of each person in charge of approval stored in the person-in-charge column 701 from general schedule management software and stores it in the schedule column 702. At that time, the data are classified into three types, that is, the day of going out all day, the day of going out for half a day, the day having a meeting for more than half a day, and the day other than the above. If the schedule is undecided, Null is stored.

  In the present embodiment, the day of going out all day is indicated by “x” marks such as 703. In addition, a day that goes out for half a day or has a meeting that lasts for more than half a day is indicated by “Δ” as in 704. Days other than the above are indicated by “◯” as in 705. If the schedule is undecided, it is blank as shown at 706.

  FIG. 13 shows a screen for displaying a list of addresses of a system administrator notifying that when approval / approval processing of an electronic document exceeds a predetermined stay period and proxy approval cannot be set for the superior It is. This screen is displayed on the display screen of the workflow operation terminal 300 by logging in to the workflow server 200 in the administrator mode and instructing display of the system administrator destination list.

  In this system administrator destination list, information in the system administrator table registered in the RDBMS 205 of the workflow server 200 is displayed.

  In this system administrator destination list, an administrator name 801, an administrator mail address 802, a management target organization 803, and a residence period 804 indicating a period during which residence in the organization is permitted are displayed.

  If the information in the system administrator table registered in the system administrator destination list is to be changed, an edit button 805, a new button 806 to add a new information, a delete button 807 to delete, a system administrator registration To end the function, the close button 808 is pressed. As a result, the CPU of the workflow server 200 controls to perform the corresponding process.

  When the edit button 805 or the new button 806 is pressed, the CPU of the workflow server 200 displays the system administrator setting screen of FIG. 9 on the display device of the workflow operation terminal 300.

  As an example of the system administrator list screen, as shown in FIG. 8, a configuration is shown in which a residence period 804 is set for each system administrator. However, the residence period 804 may be set for each type of slip. The system administrator table edited on the system administrator list screen is registered in the RDBMS 205 of the workflow server 200.

  FIG. 14 is a diagram showing an example of a system administrator setting screen in the present embodiment.

  This system administrator setting screen has input fields for an administrator name 901, an administrator mail address 902, a stay period 903, and a target organization 904. When editing registered information, the registered information is already registered in each input field. The information is displayed, and each input field is displayed blank when newly registering.

  When each information is input to each of the input fields 901 to 904 and the registration button 905 is pressed, the CPU of the workflow server 200 registers the information in the system administrator table in the RDBMS 205, and the system shown in FIG. Return the screen to the administrator address list. Note that the target organization 904 can select the corresponding organization from the list box.

  When the cancel button 906 is pressed, the CPU of the workflow server 200 cancels input information in the input fields 901 to 904 and returns the screen to the system administrator destination list shown in FIG.

  Further, the system administrator can designate one person in all the organizations, or designate one person for each or a plurality of departments and designate a plurality of persons in all the organizations.

  Hereinafter, the flow of processing for detecting stay of undecided electronic documents in the workflow system of the present invention will be described with reference to FIGS.

  FIG. 15 is a flowchart showing an example of a second control processing procedure in the workflow system of the present invention, and corresponds to the stay detection processing of an unprocessed electronic document by the workflow program 204 of the workflow server 200 shown in FIG. In the figure, S1001 to S1013 indicate steps.

  First, the CPU of the workflow server 200 that executes the workflow program 204 (hereinafter, the CPU of the workflow server 200) searches (checks) the delivery information table in step S1001 when a predetermined period has elapsed (periodically).

  In step S1002, the CPU of the workflow server 200 checks the “status” item 505 of the delivery information table. If the status is “processed”, the CPU ends the processing. Further, although not shown in the flowchart, the processing is also ended in the case of “substituted” item 509 “completed”.

  On the other hand, if it is determined in step S1002 that the “status” item 505 of the delivery information table is “waiting for processing”, the process proceeds to step S1003 and the slip is based on the user ID in the “processing user” item 504. Search the post table and get the organization code. Further, the information of the “last processing date” item 506 of the slip is also acquired.

  In step S <b> 1004, the CPU of the workflow server 200 determines whether the slip is an electronic document with an approval completion desired date from information in the “Payment completion desired” item 506 of the delivery information table.

  If it is determined that the slip is not an electronic document with a desired date for completion of approval, in step S1005, the CPU of the workflow server 200 obtains information on the stay period in the system administrator table based on the organization code acquired in step S1003. get. Furthermore, the CPU of the workflow server 200 sets the difference between the current date and time and the processing wait start date and time (final processing date) as the stay grace period, and proceeds to step S1007.

  On the other hand, if it is determined in step S1004 that the slip is an electronic document with an approval completion desired date, in step S1006, the CPU of the workflow server 200 determines the required number of days until the approval completion desired date and the number of days passing through all nodes. The difference is set as a grace period, and the process proceeds to step S1007. Details will be described below. First, the required number of days until the approval completion date is “approval completion date-current date”. Assuming that it takes “1 + α” days to pass through one decision node (α is a correction value and is appropriately determined according to the state of the organization), the total number of days passing through all nodes is “(total number of nodes−current node) × (1 + α) ”. Therefore, the stay grace period is calculated as “(approval completion completion date−current date / time) − (total number of nodes−current node) × (1 + α)”.

  Next, in step S1007, the CPU of the workflow server 200 compares the stay grace period calculated in step S1005 or S1006 with the stay period in the administrator table to determine whether or not the stay is over.

  If it is determined in step S1007 that the stay is not over (the stay grace period calculated in step S1005 or S1006 does not exceed the stay period in the administrator table), the CPU of the workflow server 200 ends the process as it is. .

  On the other hand, if it is determined in step S1007 that the stay is over (the stay grace period calculated in step S1005 or S1006 exceeds the stay period in the administrator table), the CPU of the workflow server 200 determines in step S1008. An upper length capable of proxy approval on the delivery route is selected (details are shown in FIG. 16).

  Next, in step S1009, the CPU of the workflow server 200 determines whether or not there is a superior who can be authorized on the delivery route in the process of step S1008. The process proceeds to S1011.

  In step S <b> 1011, the CPU of the workflow server 200 acquires the upper mail address from the user table.

  Next, in step S1012, the CPU of the workflow server 200 generates and transmits an e-mail notifying the approval proxy request to the mail address acquired in step S1011 and sends the superior selected in step S1008 to the approval proxy. Set as a person. That is, the upper user ID selected in step S1008 is set in the “processing user” item 504 of the node number currently staying in the delivery information table, and “done” is set in the “substituted” item 509. To do. And the process of this flowchart is complete | finished.

  On the other hand, in step S1012, the CPU of the workflow server 200 determines in step S1008 that there is no superior that can be approved on behalf of the delivery route in step S1008. In step S1010, the organization code acquired in step S1003. The system administrator table is searched based on the above, and the mail address of the system administrator is acquired.

  Next, in step S1013, the CPU of the workflow server 200 generates an e-mail notifying that the approval / settlement process for the electronic document is retained for the e-mail address of the system administrator acquired in step S1010. To send. Further, the CPU of the workflow server 200 includes a “target organization” item 1701, a “slip number” item 1702, a “node number” item 1703, and “node number” item 1703 in the RDBMS 205 of the workflow server 200. In the “stay time” item 1704, the organization code acquired in step S1003, the slip number of the stay slip, the stay node number, and the stay grace period calculated in step S1005 or S1006 are stored, respectively. Update. And the process of this flowchart is complete | finished.

  FIG. 16 is a flowchart showing an example of a third control processing procedure in the workflow system of the present invention, and corresponds to the process of selecting an upper length capable of proxy approval on the delivery route in step S1008 of FIG. In the figure, S1101 to S1107 indicate each step.

  First, in step S1101, the CPU of the workflow server 200 selects the immediate superior of the approver from the delivery route of the slip.

  Next, in step S1102, the CPU of the workflow server 200 sets the cost for the all-day outing (x mark) for the superior approval schedule selected in step S1101 as “one day” and goes out for half a day or more than half a day. On the day of meeting (△ mark), the cost is set to “0.5 days”. On the other day (○ mark), the cost is set to “0 day”, and the correction value taking into account the organization environment is set to “α”. And add this to each cost, the total sum of the above costs added until the date (△ mark) or a day other than the above (○ mark) that goes out for half a day or for more than half a day of continuous meeting appears. Is the scheduled date for approval processing (scheduled approval cost).

  Next, in step S1103, the CPU of the workflow server 200 determines whether or not the planned cost for approval processing calculated in step S1102 is within the scheduled stay grace date calculated in step S1105 or S1006 in FIG. If it is determined that it is within the range, the process proceeds to step S1107.

  In step S <b> 1107, the CPU of the workflow server 200 selects the superior as an approval agent (a superior capable of proxy approval), and ends the process.

  On the other hand, in step S1103, the CPU of the workflow server 200 determines that the approval process scheduled cost calculated in step S1102 is not within the scheduled stay grace date calculated in step S1105 or S1006 in FIG. 15 (exceeds the scheduled stay grace date). If it is determined, the process proceeds to step S1104.

  Next, in step S1104, the CPU of the workflow server 200 determines whether or not all superiors on the delivery route of the slip have been inspected, and if it is determined that there are superiors that have not yet been inspected. In step S1105, the next superior is selected, and the process returns to step S1102.

  On the other hand, if the CPU of the workflow server 200 determines in step S1104 that all the superiors on the delivery route of the slip have been inspected, in step S1106, it is determined that the corresponding slip is absent as a superior that can be approved as a proxy. The process ends.

  Note that the correction value “α” used in step S1102 may be configured to be changeable depending on the environment of the organization, the type of slip, and the like.

  FIG. 17 is a diagram illustrating an example of a staying slip information table in the present embodiment.

  This staying slip information table is stored in the RDBMS 205 of the workflow server 200.

  The staying slip information table includes a “target organization” item 1701, a “slip number” item 1702, a “node number” item 1703, and a “staying time” item 1704.

  Hereinafter, with reference to FIG. 18 and FIG. 19, a flow of processing in which the system administrator sets a substitute for a slip in which processing in the workflow system of the present invention is retained will be described.

  FIG. 18 is a diagram showing a screen displayed in the approval / approval staying slip list in the present embodiment.

  When the system administrator logs in to the workflow server 200 from the workflow operation terminal 300, the workflow server 200 searches the staying slip information table shown in FIG. 17 based on the organization code corresponding to the system administrator. The corresponding staying slip information is acquired. Then, the workflow server 200 generates an approval / approval stay slip list screen based on the acquired stay slip information and transmits it to the workflow operation terminal 300 of the system administrator. Accordingly, the workflow operation terminal 300 of the system administrator displays the approval / approval staying slip list screen on the display device.

  On this approval / approval staying slip list screen, the slip number 1302, the node number 1303, the processing user 1304, the status 1305, and the staying time 1306 of the slips in which the approval or approval processing is staying are displayed. Each voucher has an approval check field 1301 and an agent setting field 1307.

  The system administrator uses this approval / approval staying slip list screen to set a user who performs the staying process. First, a check is made in an approval check column 1301 for a slip for setting a substitute, and a mail address of a user who performs the processing is input in a substitute setting column 1307.

  It is possible to set a substitute for a plurality of slips at a time. When all the settings are completed, the execution button 1308 is pressed. Further, when closing the approval / approval staying slip list screen, a close button 1309 is pressed.

  When the execute button 1308 is pressed, information on this screen is transmitted from the workflow operation terminal 300 to the workflow server 200. And the workflow server 200 which received this starts the process shown in FIG.

  FIG. 19 is a flowchart showing an example of a fourth control processing procedure in the workflow system of the present invention. The system administrator substitutes a slip in which processing by the workflow program 204 of the workflow server 200 shown in FIG. This corresponds to the process of setting a person. In the figure, S1401 to S1410 indicate each step.

  When the processing administrator is set on the approval / approval stay slip list screen shown in FIG. 18 on the workflow operation terminal 300 by the system administrator and the execution button 1308 is pressed, the stay matter information (information in FIG. 18) is displayed. It is transmitted to the workflow server 200. In step S1401, the CPU of the workflow server 200 that executes the workflow program 204 (hereinafter referred to as the CPU of the workflow server 200) acquires information on the staying matter from the workflow operation terminal 300.

  Next, in step S1402, the CPU of the workflow server 200 first determines whether or not there is a case in which the approval check is input in the approval check column 1301 in the staying case information, and the approval check is input. If it is determined that there is no case, the process ends.

  On the other hand, if the CPU of the workflow server 200 determines that there is a case for which an approval check has been input, the process proceeds to step S14003.

  In step S <b> 1403, the CPU of the workflow server 200 determines whether there is a case in which the agent's email address is input in the agent setting field 1307 of the case in which the approval check is input in the approval check field 1301 of the staying case information. Determine whether or not.

  In step S1403, when the CPU of the workflow server 200 determines that there is no case in which the e-mail address of the agent is input in the agent setting field 1307, the process proceeds to step S1407, and the agent address is set. A message is sent to the workflow operation terminal 300 to be input and displayed on the screen, and the process ends.

  On the other hand, in step S1403, the CPU of the workflow server 200 determines that the case in which the email address of the agent is input in the agent setting column 1307 of the item in which the approval check is input in the approval check column 1301 of the staying case information. If it is determined that there is, the process proceeds to step S1404.

  In step S <b> 1404, the CPU of the workflow server 200 creates and transmits a mail requesting the agent to process. The email to be sent includes proxy processing information such as a slip number, a node number, a processing user, and a residence time.

  After sending the proxy processing request mail, in step S1405, the CPU of the workflow server 200 transmits a slip processing request to the proxy. The CPU of the workflow server 200 sets the substitute in the “processing user” item 504 of the staying node number, and further sets “done” in the “substituted” item 509.

  In step S1406, the CPU of the workflow server 200 deletes the row of the corresponding slip number and node number from the approval / approval stay slip information table (FIG. 17) and updates the stay slip list screen to the workflow operation terminal 300. To update the screen. And this flowchart is complete | finished.

  Through the above process, even if it is found that there is no official decision-maker in charge of the workflow, delegate decision-making is delegated to the best substitute decision-maker on the delivery route so that the drafter's decision-making date can be satisfied And smooth processing of electronic documents can be promoted.

  Therefore, it is possible to prevent the stagnation of the workflow and to promote the efficiency of the workflow work to be processed.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The configuration of a data processing program that can be read by the workflow server 200 according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 20 is a diagram for explaining a memory map of a recording medium (storage medium) that stores various data processing programs readable by the workflow server 200 according to the present invention.

  Although not specifically shown, information for managing a program group stored in the recording medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, when a program or data to be installed is compressed, a program to be decompressed may be stored.

  The functions shown in FIGS. 10, 15, 16, and 19 in the present embodiment may be performed by a host computer by a program installed from the outside. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a recording medium such as a CD-ROM, a flash memory, or an FD, or from an external recording medium via a network. Is.

  As described above, a recording medium in which a program code of software for realizing the functions of the above-described embodiments is recorded is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus is stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the program code.

  In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program code constitutes the present invention.

  As a recording medium for supplying the program code, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, A silicon disk or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program represented by software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading out a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. It becomes.

  In addition, all the structures which combined any or all of each modification shown in the said embodiment are also contained in this invention.

  As described above, in the workflow system, the status of the unprocessed matter staying due to the absence of the person in charge of approval, etc. is notified to the system administrator, and the long-term stay of the unprocessed matter can be avoided. There is an effect.

It is a figure which shows schematic structure of the workflow system to which this embodiment is applied. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a computer applicable to the workflow server, the workflow operation terminal, the workflow, and the slip design terminal illustrated in FIG. 1. It is a schematic diagram which shows the flow of the slip in the workflow system shown in FIG. FIG. 2 is a data configuration diagram illustrating an example of a data structure of an organization table stored in an RDBMS of the workflow server illustrated in FIG. 1. It is a data block diagram which shows an example of the data structure of the role table memorize | stored in RDBMS of the workflow server shown in FIG. It is a data block diagram which shows an example of the data structure of the user table memorize | stored in RDBMS of the workflow server shown in FIG. FIG. 2 is a data configuration diagram illustrating an example of a data structure of a post table stored in an RDBMS of the workflow server illustrated in FIG. 1. FIG. 2 is a data configuration diagram illustrating an example of a data structure of delivery definition information stored in an RDBMS of the workflow server illustrated in FIG. 1. FIG. 2 is a data configuration diagram illustrating an example of a data structure of a delivery information table stored in an RDBMS of the workflow server illustrated in FIG. 1. It is a flowchart which shows an example of the 1st control processing procedure in the workflow system of this invention. It is a figure which shows an example of the electronic document (slip) with an approval completion desired time limit in this embodiment. It is the figure which showed the schedule data of the person in charge of decision on the delivery route of the electronic document in this embodiment. When the approval / approval processing of an electronic document exceeds a predetermined residence time limit and the proxy approval for the superior cannot be set, this is a screen for displaying a list of destinations of a system administrator notifying that. It is a figure which shows an example of the system administrator setting screen in this embodiment. It is a flowchart which shows an example of the 2nd control processing procedure in the workflow system of this invention. It is a flowchart which shows an example of the 3rd control processing procedure in the workflow system of this invention. It is a figure which shows an example of the staying slip information table in this embodiment. It is a figure which shows the screen displayed by the approval / approval staying slip list | wrist in this embodiment. It is a flowchart which shows an example of the 4th control processing procedure in the workflow system of this invention. It is a figure explaining the memory map of the recording medium (storage medium) which stores the various data processing program which can be read by the workflow server 200 concerning this invention.

Explanation of symbols

200 Workflow server 204 Workflow program 205 RDBMS
300 Workflow operation terminal 101 CPU
102 RAM
103 ROM
104 HD

Claims (8)

In a workflow system that circulates electronic documents according to a predetermined delivery route and performs workflow processing for approval and approval,
Storage means for storing the organization information of the approval / authorizer and the schedule of the approval / authorizer;
A stay detection means for detecting a staying electronic document in which the workflow processing of the electronic document by the next approval / decision person exceeds a predetermined staying deadline;
Refers to the schedule of the approval / authorizer who is the superior of the next approval / authorizer on the delivery route of the staying electronic document detected by the residence detection means, and refers to the schedule of the approval / authorizer who is referred to as the superior; Control means for determining and controlling the superior to be delegated as a decision-making agent based on the stay deadline;
A workflow system characterized by comprising:   The control means refers to the schedule for all the superiors / authorizers on the delivery route with reference to the schedule when the next superior schedule of the next approval / decision person does not satisfy the stay deadline, The workflow system according to claim 1, wherein an upper manager having a schedule that satisfies the stay deadline is delegated as an approval agent. A system administrator setting means for setting at least one system administrator;
The control means informs the system administrator that the approval / approval processing of the electronic document has exceeded the stay deadline when a superior having a schedule that satisfies the stay deadline does not exist on the delivery route. The workflow system according to claim 2, wherein notification is performed.   A setting unit capable of setting an approval agent by the system administrator for an electronic document notified by the control unit that the electronic document approval / approval process has exceeded the stay deadline; The workflow system according to claim 3, wherein: It has an approval request deadline setting means that can set an approval completion deadline for an electronic document,
5. The workflow system according to claim 1, wherein the detection unit determines the stay deadline based on a desired settlement completion deadline set by the final settlement desired deadline setting unit. In a staying electronic document processing method of a workflow system that circulates an electronic document according to a predetermined delivery route and performs workflow processing for approval and approval,
A registration step for registering the organization information of the approval / authorizer and the schedule of the approval / authorizer in the storage means;
A stay detection step for detecting a staying electronic document in which the workflow processing of the electronic document by the next approval / decision person has exceeded a predetermined staying deadline;
Refers to the schedule of the approval / authorizer who is the superior of the next approval / authorizer on the delivery route of the detected electronic document, and refers to the schedule of the approval / authorizer who is the superior, and the residence time limit. A determination step for determining a superior to be delegated as an approval agent based on
A method for processing a stagnant electronic document characterized by comprising:   A program for causing a computer to execute the staying electronic document processing method according to claim 6.   A recording medium storing a computer-readable program for causing a computer to execute the staying electronic document processing method according to claim 6.

Images