JP5311136B2 - Workflow management server, workflow management server control method, program, and recording medium - Google Patents

Description

  The present invention relates to a display of a workflow path and progress status in a workflow system.

  2. Description of the Related Art In recent years, a workflow system has been introduced that digitizes various slips and the like in a company, assigns processing of form data to each business person in accordance with predetermined route information, and sequentially advances the business.

  In addition, in order to make it easy to grasp the workflow path and progress at that time, it is generally displayed visually. Japanese Patent Application Laid-Open No. 2004-228561 discloses a system that easily grasps a workflow path and progress status visually.

JP 2002-41744 A

  However, in the workflow system described in Patent Document 1, it is possible to display a simple workflow route and progress, but it is difficult to see when the complicated route or the transition source and the transition destination are separated. There is.

  In particular, it has been difficult for the user to select only the necessary approval personnel while grasping the overall workflow when selecting the subsequent approval personnel. In addition, in the case of a workflow including a loop, there is a problem that it is difficult to see because the number of lines on which a loop that has been passed a plurality of times is displayed increases.

If the present invention has been made to solve the above problems, in the workflow having a path same activity is processed a plurality of times, of the activities that are processed more than once, there is already processed activity, other in the non-processing activity of processing personnel input screen of, for the purpose of Rukoto to display the processing person in charge of the activity that has been processed to該既.

In the workflow management server for managing workflow, and the path information storage means for storing route information having a path same activity of the workflow is processed more than once, the processed and activity progress information currently being processed in the workflow and progress information storage means for storing, and the route information storage means the stored path information, from said progress information storage means stored progress information, the processing of each activity to be treated to the activity after said currently processed personnel and that generates control screen for inputting handlers input screen control means, the activity to input handlers in the input screen control means is an activity to be processed more than once, are processed plurality several times If there are activities that have already been processed, A screen for inputting the handlers of the untreated activity of the activity that is processed, and comprising: the handlers display means Ru display the processing person assigned to the processed activity, the To do.

According to the present invention, in a workflow having a path in which the same activity is processed a plurality of times , if there is an activity that has already been processed among the activities that are processed a plurality of times, the processing person input screen for the other unprocessed activity in, it is possible to Rukoto to display the processing person in charge of the activity that has been processed to該既.

1 is a system configuration diagram illustrating an overall configuration of a system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a workflow management server 103 and a client 112 illustrated in FIG. 1. It is a flowchart which shows an example of the 1st control processing procedure in this invention. It is a flowchart which shows an example of the 2nd control processing procedure in this invention. It is a flowchart which shows an example of the 3rd control processing procedure in this invention. It is a figure which shows an example of the route information data in route information DB110 in this invention. It is a figure which shows an example of the route map screen and person in charge designation | designated screen in this invention. It is a figure which shows an example of the route map screen and person in charge designation | designated screen in this invention. It is a figure which shows an example of the route map screen and person in charge designation | designated screen in this invention. It is a figure which shows an example of the progress information data in progress information DB111 in this invention. It is a figure which shows an example in the middle of the route map screen drawing in this invention. It is a figure which shows an example of the progress information data in progress information DB111 in this invention. It is a figure which shows an example of the route map screen and person in charge designation | designated screen in this invention. It is a figure explaining the memory map of the storage medium which stores the various data processing program which can be read by the workflow management server 103 concerning this invention.

  [First Embodiment]

  Hereinafter, the workflow management server of the present invention will be described with reference to the drawings.

  FIG. 1 is a system configuration diagram showing an overall configuration of a system showing an embodiment of the present invention.

  As shown in FIG. 1, the workflow system of this embodiment includes a workflow management server 103 and a client 112.

  The client 112 includes an output unit 102 that displays an output result from the workflow management server, and an input unit 101 that inputs data to be transmitted to the workflow management server.

  The workflow management server 103 stores the transition order of workflow activities as path information 110 and the progress status of workflow as progress information 111 in an external storage device (HDD).

  The workflow management server 103 also displays path information visualization means 105 for displaying the workflow transition order on the output means 102 of the client, and visualization information for transmitting the data created by the path information visualization means 105 to the client 112. A transmission unit 106, a loop route visualization unit 107 for displaying the loop route of the route information on the output unit 102 of the client, a progress information list generation unit 108 that generates a list of processed activities from the progress information 111, And a processing person selecting means for selecting a processing person candidate for an activity after the workflow that is currently in progress.

  FIG. 2 is a block diagram illustrating an example of a hardware configuration of the workflow management server 103 and the client 112 illustrated in FIG.

  In FIG. 2, the CPU 201 comprehensively controls each device connected to the system bus 204. The ROM 203 or the external memory 211 stores an operating system (OS) that is a control program of the CPU 201 and programs for realizing various functions described later of each server or each client.

  The RAM 202 functions as a main memory, work area, temporary save area, and the like for the CPU 201.

  The input controller 205 controls input from the input unit 209. Examples of the input unit 209 include a pointing device such as a keyboard and a mouse in a terminal such as a server or a client.

  The output controller 206 controls the display of the output unit 210. Examples of the output unit 210 include a CRT display and a liquid crystal display.

  The external memory controller 207 controls access to the external memory 211 that stores a boot program, various applications, font data, user files, edit files, printer drivers, and the like. In addition, the external memory controller 207 stores various tables and parameters for realizing various functions of each server or each client.

  Examples of the external memory 211 include a hard disk (HD), a floppy (registered trademark) disk (FD), a compact flash connected to the PCMCIA card slot via an adapter, and smart media.

  The communication I / F controller 208 executes communication control processing with an external device via the network 212.

  The program of the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary.

  Hereinafter, with reference to the flowchart of FIG. 3, a procedure for the workflow management server 103 to display the workflow path diagram will be described.

  FIG. 3 is executed by the CPU 201 of the workflow management server 103 shown in FIG. In addition, S301-S315 show each step.

  FIG. 3 is a flowchart showing an example of a first control processing procedure in the workflow management server 103 of the present invention, which is activated when an instruction to display a workflow path diagram is received from the input unit 101 of the client 112. In the following description, it is described that the workflow management server executes, but it is also possible for the client to receive data from the path DB and the progress DB and to execute the following flow on the client.

  Upon receiving a command for displaying a workflow route diagram from the input unit 101 of the client 112, the workflow management server 103 acquires route information data and progress information data from the route information DB 110 and the progress information DB 111 (step S301).

  An example of the route information data will be described with reference to FIG.

  FIG. 6 is an example of route information data stored in the route information DB 110.

  6 includes items such as an activity id 601, an activity name 602, an activity type 603, an activity depth 604, a next transition destination candidate 605, and a transition source candidate 606 that makes a transition. Although this data is stored in a database format, it can also be stored using XML or other methods.

  The activity type 603 includes values such as “AWAIT” (waiting state), “CONDITIONAL” (conditional branch), “SPLIT” (parallel branch), “JOIN”, “VOTE” (conference). The activity depth 604 relatively indicates the distance from “START”. Return to description of FIG.

  In step S302, the workflow management server 103 selects activities to be displayed in the order of the activity depth 604 in order to display the activity icon of the route information data on the screen, and repeats the flow from step S316 onward for the number of activities.

  In step S316, the workflow management server 103 stores the id of the display target activity selected in step S302 among the data acquired in step S301.

  In step S303, the workflow management server 103 determines whether the activity to be displayed is branched. In the case of the route information data in FIG. 6, the type of activity corresponding to the branch is “CONDITIONAL” or “SPLIT”. If so, the process proceeds to step S304. If not, the process proceeds to step S309.

  In step S304, the workflow management server 103 repeats steps S305 to S308 for the number of activities to be branched. In the case of the route information data shown in FIG. 6, when id is “conditional branch 1”, there are six candidates with ids of 5, 1, 13, 14, 15, and 16 at least 6 times. Repeats steps S305 to S308.

  In step S305, the workflow management server 103 determines whether a line (transition line) indicating a transition between activities to be displayed crosses or loops. Whether or not the transition line crosses is determined by whether the transition destination activity is another branch destination. Further, whether the activity is a loop target activity is determined by the value of the depth 604 of the next transition destination activity. Specifically, in step S305, the depth of the next transition destination activity is smaller than the depth of the activity of the branch to be displayed due to the relationship between the depth of the activity of the display target branch and the depth of the next transition destination activity. If it is determined that the activity is a loop target activity.

  If it is determined in step S305 that the loop target or the transition line is crossed, the process proceeds to step S306. If it is determined that the loop target is not crossed and the transition line is not crossed, the process proceeds to step S308.

  In step S306, the workflow management server 103 determines that the next transition destination activity is a loop target or a transition line crossing, and the connector icon (activity entity that is the target of the loop target or the transition line crossing is displayed on the route diagram display screen. Instead of an icon that points to, an icon or symbol sign that only indicates where to go to the activity entity is displayed.

  An example of the route diagram will be described with reference to FIG.

  FIG. 7 is an example of a screen image in which the data output from the workflow management server 103 is displayed on the output unit 102 of the client 112, and is a screen for designating an approval person (processing person). FIG. 7 shows an example reflecting the route information data of FIG.

  The conditional branch 3 (704) in FIG. 7 is in the row 609 in FIG. 6, and the next transition destination candidates 605 are four ids [15, 28, 16, 29], and “Conference 1” “ Approval 4 "" Approval 1 "" Approval 5 ". The transition destination candidates of these four ids that correspond to the loop target are “approval 1” (607) whose activity depth 604 is small and id is 16 (608), so “approval 1” is arranged. A connector icon (symbol symbol) (701) is displayed at the next icon arrangement position. Returning to the description of FIG.

  In step S307, the workflow management server 103 draws an auxiliary line (thin wave line) to indicate the link destination to the loop-destination transition destination activity. The auxiliary line may be displayed for the first time when the progress of the workflow reaches the transition source activity, or may be displayed for the first time when the workflow reaches the transition source activity. The auxiliary line may be displayed for the first time when the input means 101 (such as a mouse) of the client points on the screen output to the output means. Further, for example, when the “approval 1” icon 905 in FIG. 9 is pointed by the input means 101 (mouse or the like) of the client, the “approval 1” icon 1301 is scrolled so as to be displayed near the center of the screen as shown in FIG. You may control.

  In this way, the auxiliary line is not initially drawn, and the auxiliary line to the loop destination activity is displayed at the stage where the transition source or destination activity to be looped is focused. It becomes possible to display the line indicating the mark without confusion.

  In the example of FIG. 7, step S307 will be described.

In FIG. 7, “approval 1” is the transition destination of the previous “conditional branch 3” (704).
Since the icon 702 is designated, the path from the connector icon 701 to the “approval 1” icon 702 is displayed with a thin wave line 703. Returning to the description of FIG.

  When step S307 is completed, in step S313, the workflow management server 103 determines whether steps S305 to S308 have been performed for the number of times branched in step S304. If it has not been carried out for the number of branches, the process returns to step S305.

  On the other hand, if steps S305 to S308 have been performed for the number of times branched in step S304, the process proceeds to step S314. The following will be described later.

  In contrast, if the workflow management server 103 determines in step S305 that it is not a loop target, the workflow management server 103 advances the processing to step S308. In step S308, the workflow management server 103 secures a display frame for the icon display position of the next transition destination activity.

  Step S308 will be described with reference to FIG.

  In FIG. 11, “approval 5” (611) with id 29 (610) is shown as the activity of the next transition destination candidate after “condition branch 3” (609) in FIG. A display frame is reserved for the icon display of approval 5 ″. In step S312, which will be described later, an icon indicating the substance of “approval 5” is displayed.

  When step S308 ends, the process proceeds to step S313.

  On the other hand, if the activity to be displayed is not a branch in step S303, the process proceeds to step S315.

  In step S315, the id of the transition source of the display target activity is read from the route information acquired in step S301.

  In step S309, the workflow management server 103 determines whether the activity to be displayed is a loop target or not. If the activity to be displayed is a loop target, the process proceeds to step S310. If the activity is not a loop target, the process proceeds to step S312.

  Whether the display target in step S309 is a loop target or not is the same as in step S305.

to decide. That is, the depth of the transition source activity read out in step S315 if not greater than the depth of the displayed activity, it is determined that the loop target activity.

  If it is determined in step S309 that the activity to be displayed is a loop object, the process proceeds to step S310. In step S310, the workflow management server 103 displays the activity to be displayed as a loop icon on the route diagram display screen. Let

  In step S <b> 311, the workflow management server 103 indicates a link destination by drawing a thin line to the transition target activity to be looped on the route diagram display screen. after that. The process proceeds to step S314.

  On the other hand, if it is determined in step S309 that the display target activity is not a loop target, the process proceeds to step S312. In step S312, the workflow management server 103 displays an icon of the display target activity on the route diagram display screen. .

  Step S312 will be described with reference to FIGS. 11, 7 and 6. FIG.

  In FIG. 11, the icon frame 1101 of the activity secured in step S308 is secured. If the activity to be displayed is “approval 5” (611) with id 29 in FIG. 6, an icon of “approval 5” is displayed in the icon frame of 1101, and is displayed as 705 in FIG.

  The icon display in step S312 may display the progress information by the progress information data (1001 in FIG. 10) in the progress information DB 111. A specific icon display method will be described with reference to FIG.

  FIG. 5 is a flowchart for displaying an icon indicating the substance of an activity.

  FIG. 5 is executed by the CPU 201 of the workflow management server 103 shown in FIG. S501 to S506 indicate each step.

  FIG. 5 is a flowchart showing an example of a third control processing procedure in the workflow management server 103 according to the present invention, which is activated when an icon indicating an activity entity is displayed on the workflow path diagram (S312).

  First, in step S501, the workflow management server 103 acquires progress information data from the progress information DB.

  An example of the progress information data will be described with reference to FIG.

  FIG. 10 is an example of progress information data stored in the progress information DB 111.

  The progress information data in FIG. 10 includes the activity id (defId) 1001 passed by the user in drafting and approval, the activity name 1002, confirmation of whether the activity is currently executed (selected) 1003, the activity status 1004, and the activity It consists of items such as the name of person in charge (name of person in charge of processing) 1005 of the user to be drafted or approved. Although this data is stored in a database format, it can also be stored using XML or other methods. Return to description of FIG.

  In step S502, the workflow management server 103 determines whether the activity to be displayed is currently being executed. Whether it is currently being executed is determined by whether 1003 in FIG. 10 is true or not.

  If it is determined in step S502 that it is currently being executed, the process proceeds to step S503. If it is determined that it is not currently being executed, the process proceeds to step S504.

  In step S503, the workflow management server 103 displays the activity to be displayed by enclosing it with a thick dotted line.

  An example of the route diagram will be described with reference to FIG.

  FIG. 9 is an example of a screen image in which the data output from the workflow management server 103 is displayed on the output unit 102 of the client 112, and is a screen for designating an approval person (processing person). FIG. 9 is an example reflecting the progress information data of FIG.

  The case of displaying “Parallel approval 2_2” (1006) with an activity id of 33 in FIG. 10 corresponds to the processing in step S503.

  In the determination of whether or not the display target activity currently being executed in step S502 is currently being executed, “Parallel approval 2_2” (1006) in FIG. 10 is 1003 “Confirmation of whether or not the activity is currently being executed” (Selected) column. Is true, it is determined that the activity is currently being executed.

  In step S503, the activity to be displayed is surrounded by a thick dotted line as indicated by reference numeral 901 in FIG. 9, and the approval position currently being executed can be grasped at a glance.

  On the other hand, in step S504, the workflow management server 103 determines whether the activity to be displayed is included in the progress information data, that is, whether it has been processed. Whether or not the activity to be displayed is included in the progress information data is determined by whether or not the id of the activity to be displayed is included in “defId” 1001 in FIG.

  If the activity to be displayed is included in the progress data, the process proceeds to step S505, and if not included in the progress data, the process proceeds to step S506.

  In step S505, the workflow management server 103 displays the activity to be displayed with a bold line.

  On the other hand, in step S506, the workflow management server 103 displays the activity to be displayed surrounded by a thin line.

  The case of displaying “approval 1” (1007) with an activity id of 16 in FIG. 10 corresponds to the processing in step S505. An example of a route diagram display screen when the activity id 16 (1007) is the display target activity is 902 in FIG.

  In the situation of the progress information data in FIG. 10, if the id of the activity to be displayed is 16, defId contains 16 (1007), so the icon display of “approval 1” with id 16 in step S504 is in step S505. Proceed with the process. In step S505, as shown at 902 in FIG. 9, the “approval 1” icon is surrounded by a thick line to make it easier to see which route has been taken.

  On the other hand, if it is determined in step S504 that the activity to be displayed is not included in the progress information data, the process proceeds to step S506.

  An example of drawing in step S506 is 903 in FIG.

  When the id of the activity to be displayed is “Parallel approval 2_1”, since 32 is not included in the defId of the progress information data in FIG. 10, the icon display of “Parallel approval 2_1” with id 32 is displayed in step S504. The process proceeds to step S506. In step S506, as indicated by reference numeral 903 in FIG. 9, the “parallel approval 2_1” icon is surrounded by a thin line and differentiated from the route that has passed. Returning to the description of FIG.

  When step S312 ends, the process proceeds to step S315.

  In step S315, the display target activity and its transition source activity are connected by a solid line and displayed. Thereafter, the process proceeds to step S314.

  In step S314, the workflow management server 103 changes the id of the activity to be displayed by the number of activity information designated in step S302, and repeats from step S302.

  When step S316 and subsequent steps are executed for the number of pieces of activity information in step S302, this flow ends.

  As described above, even when a complicated route including a loop is displayed by the route diagram screen display described with reference to FIGS. 3 and 5, the route diagram can be displayed in an easy-to-understand manner while confirming the approved route that has passed.

  Next, a procedure for the workflow management server 103 to display a workflow progress status table will be described with reference to the flowchart of FIG.

  FIG. 4 is executed by the CPU 201 of the workflow management server 103 shown in FIG. S401 to S412 indicate each step.

  FIG. 4 is a flowchart showing an example of a second control processing procedure in the workflow management server 103 according to the present invention, which is activated when an instruction to display a workflow progress status table is received from the input unit 101 of the client 112. . In the following description, it is described that the workflow management server executes, but it is also possible for the client to receive data from the path DB and the progress DB and to execute the following flow on the client.

  When receiving an instruction to display the workflow progress status table from the input unit 101 of the client 112, the workflow management server 103 acquires path information data and progress information data from the path information DB 110 and the progress information DB 111 (step S401).

  Next, in step S402, the workflow management server 103 acquires the number of activity transitions from the path information data, and performs the flow processing from step S403 onward for the number of transitions. The number of transitions is the number of transitions from the transition source activity to the transition destination activity. The flow after step S403 is executed for the number of transitions in the order of transition of activities.

In step S403, the workflow management server 103 determines whether the transition destination (display target) row of the progress status table to be displayed is a loop target activity.
As described above, the depth of the transition source activity (604) of the path information data read out in step S401 is the depth of the transition destination activity (display target).
604) If more has large, it is determined that the loop target activity.

  If the activity to be displayed is a loop target in step S403, the process proceeds to step S404, and if not the loop target, the process proceeds to step S410.

  In step S404, the workflow management server 103 compares the activity depth of the transition destination (display target) with the latest activity depth of the progress information data acquired in step S401. If the latest activity is deeper than the activity at the transition destination (display target), the process proceeds to step S405, and if the latest activity is smaller, the process proceeds to step S412. By this processing, a new row of the progress status table of the loop target that is not currently passing through is not displayed.

  In step S405, the workflow management server 103 advances the process to step S406 if the transition destination (display target) activity has the “completed” status in the progress information data, and if not the “completed” status, step S412. Continue the process. By this process, a new row of the progress status table that is not currently approved is not displayed.

  In step S406, the workflow management server 103 determines from 612 in FIG. 6 whether the approval user of the transition destination (display target) activity can be specified at the time of workflow execution. The activity 612 in FIG. 6 can be designated as an approved user when the workflow is executed. If the approval user can be specified at the time of executing the workflow, the process proceeds to step S407. If the approval user specification cannot be specified, the process proceeds to step S412. By this process, when the approved user cannot be changed, the selection items to be shown to the user can be reduced by not displaying in the progress status table.

  In step S <b> 407, the workflow management server 103 determines whether an approved user of the transition destination (display target) activity is assigned. If the approval user of the transition destination (display target) activity is assigned, the process proceeds to step S408, and if the approval user is not assigned, the process proceeds to step S409.

  In step S408, the workflow management server 103 acquires the approved user to which the transition destination (display target) activity is assigned from the progress information data.

  In step S409, the workflow management server 103 inserts information about the transition destination (display target) activity into the progress table in units of rows. At that time, if there is information on the approved user acquired in step S408, the approved user is also inserted into the corresponding row. In addition, an approval user selection button is inserted in the row of the progress status table so that the approval user can be designated when executing the workflow. When step S409 ends, the process proceeds to step S412.

  In step S412, the workflow management server 103 returns to step S403 for the number of transitions acquired in step S402, and repeats step S403 and subsequent steps.

On the other hand, if it is determined in step S403 that the transition destination (display target) activity is not a loop target, that is, the transition source activity depth (604) of the path information data read in step S401 is the display target. Transition destination activity depth (60
4) When than not small, the process proceeds to step S410.

  In step S410, the workflow management server 103 determines whether the transition destination (display target) activity is a conditional branch, parallel branch, or combination. If it is a conditional branch, parallel branch, or combination, the display line creation flow in step S407 does not pass, and the process proceeds to step S412. If it is not a conditional branch, parallel branch, or combination, the process proceeds to step S407. The reason why the display line is not created at the time of branching or joining is that the activity does not require the approval user to be determined.

  In step S412, when the processes after step S403 for the number of transitions acquired in step S402 are performed, this flow is ended.

  Specifically, an example of route information data will be described with reference to FIG. 6, and an example of progress information data will be described with reference to FIGS. 12 and 10.

  FIG. 12 shows progress information data when Hidekazu Onodera “drafts” and asks Mr. Masahisa Isogai for “approval 1”. FIG. 10 shows progress information data in a state where “approval 1” is completed and “parallel approval 2_2” is waiting to be processed.

  In step S401, the route information data in FIG. 6 and the progress information data in FIGS. 12 and 10 are acquired.

  In step S402, the number of activity transitions is acquired from the route information data of FIG. In the case of “conditional branch 3” of 609, the number of transitions is four times of 15, 28, 16, 29 described in nextIds. The number of transitions of each id is summed to determine the number of transitions, and the number of subsequent flow processes is determined. In this example, the processing order is the transition order.

  The flow after step S403 is executed the number of times determined in step S402. By executing the flow from S403 onward for the number of transitions, even if a loop target activity is passed a plurality of times, it is possible to display only the latest person in charge of approval, instead of displaying the number of times passed through the loop target.

  In step S403, it is determined whether or not it is a loop target along the order of transition based on the route information data of FIG. In the case of “conditional branch 3” 609 in FIG. 6, the nextIds 16 (608) is smaller than the depth 604 (604) and is smaller than the depth 604 (604). In the following, the story proceeds when the transition destination (display target) activity is 607 described above.

  In step S404, the depth of the transition destination (display target) activity 607 is compared with the depth of the latest activity in the progress information data. In the case of the progress information data shown in FIGS. 12 and 10, the latest activity depth is “approval 1” 15 in FIG. 12, “parallel approval 2_2” 17 in FIG. 10, and the transition destination (display target) activity 607. Since the depth is 15 or more, the process proceeds to step S405 in both cases.

  In step S405, it is determined from the status (1204, 1004) of the progress information data of the transition destination (display target) activity 607 whether or not 607 has been completed. In the case of FIG. 12, since the status 1207 of “approval 1” is “waiting for processing” and not “completed”, the process proceeds to step S412. On the other hand, in the case of FIG. 10, since the status 1008 of “approval 1” is “completed”, the process proceeds to step S406.

  In step S406, a determination is made as to whether or not an authorized user can be specified at the time of workflow execution of the path information data of the transition destination (display target) activity 607, from 612 (assignable enabled). Since the approved user specifiable column 612 of the transition destination (display target) activity 607 is TRUE, it is determined that an approved user can be specified, and the process proceeds to step S407.

  In step S407, it is confirmed whether the person in charge of approving the transition destination (display target) activity 607 is assigned. Since the name of the person in charge 1005 in the “approval 1” row 1007 of the progress information data has a name of “Masahisa Kamagai” and the person in charge of the approval is assigned, the process proceeds to step S408.

  In step S408, the person in charge name “Masahisa Isogai” in the person in charge column confirmed in step S407 is acquired.

  In step S409, a display line such as 904 in FIG. 9 is created. In order to create the display line 904, the information of “Masahisa Kaigai” acquired in step S408 is acquired from the progress information data of FIG. 10 and displayed. A selection button is arranged at 904 so that the person in charge of approval can be changed. At this time, information such as the department to which the person in charge belongs and the title of the position may be brought not from the progress information data but from personnel information data not shown this time.

  On the other hand, in step S405, when the status of the progress information data of the transition destination (display target) activity 607 is not completed as shown in FIG. 12 (1204), the next of “conditional branch 3” 609 as shown in FIG. The row 801 of the activity “Approval 1” 607 is not displayed.

  In addition, although there is a line with an expression mark (!) In 905 in FIG. 9, the line with the expression mark, that is, the activity indicates an activity for which an approval person candidate has not yet been determined. Yes.

  Further, when the status 1004 is completed (1008), the person in charge of approval may be input as indicated by 904 in FIG. 9, or the person in charge of approval is determined as shown in the column 1 of approval in FIG. Although not shown, the person in charge of approval may be displayed in 801 having a loop route.

  Furthermore, when the status is completed, an activity for displaying an approval person in the loop route (for example, 904), and an approval person in the loop route at the stage where the approval person is determined even if the status is not completed ( The activity displaying the position 801 (not shown) may be determined by data (not shown) in the route information data.

  As described above, according to the flow of FIG. 4, the user can display and select only selectable approval user items while checking the workflow flow when specifying the approval user. In addition, only the latest approval result can be displayed in the approval flow of the loop target, and it is possible to prevent the progress table data from increasing according to the number of loops and make the table easier to see.

  It should be noted that history information for the number of times the same activity has been passed a plurality of times may be expanded and displayed in the progress status table by clicking each activity in the progress status table or each activity in the route diagram.

  As described above, according to this embodiment, when the person in charge of approval is determined in the workflow management server, a person who has previously approved in a loop is input to the person in charge of approval in advance while displaying a route diagram. This makes it easy to select only the necessary approvers while grasping the flow of the entire workflow, and the latest approver is also responsible for loops that have been passed multiple times in a workflow that includes loops. It is possible to provide a method for displaying the progress status table in an easy-to-understand manner.

  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.

  In the above embodiment, a case has been described in which a configuration in which the person in charge of the workflow data to be circulated can be displayed and selected in each step of the workflow is applied to the workflow management server. Instead, it is possible for the client to have the above configuration.

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

  FIG. 14 is a diagram for explaining a memory map of a recording medium (storage medium) for storing various data processing programs readable by the workflow management server 103 according to the present invention.

  Although not specifically illustrated, 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. An icon to be displayed 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. 3, 4, and 5 in this embodiment may be performed by the 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 that records the program code of software that implements the functions of the above-described embodiments is supplied to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus It goes without saying that the object of the present invention can also be achieved by reading and executing the program code stored in the recording medium.

  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.

  Examples of the recording medium for supplying the program code include a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a DVD-ROM, a magnetic tape, and a non-volatile memory card. ROM, EEPROM, silicon disk, etc. can be used.

  Further, by executing the program code read out by the computer, not only the functions of the above-described embodiments are realized, but also the computer is operated on the basis of the instruction of the program code. It goes without saying that the OS (operating system) or the like performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Furthermore, after the program code read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the program code is read out. -A case where the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instruction of the function and the functions of the above-described embodiments are realized by the processing. Needless to say.

  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 reading and reading 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 possible to do.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

DESCRIPTION OF SYMBOLS 101 Input part 102 Output part 103 Workflow management server 104 External storage device 105 Path information visualization part 106 Visualization information transmission part 107 Loop path visualization part 108 Progress information list generation part 109 Processing person selection part 110 Path information 111 Progress information 112 clients

Claims (7)

In the workflow management server that manages the workflow,
Route information storage means for storing route information having a route in which the same activity of the workflow is processed a plurality of times;
Progress information storage means for storing progress information of processed and currently processed activities of the workflow;
Based on the route information stored in the route information storage means and the progress information stored in the progress information storage means, a screen for inputting a person in charge of each activity processed after the activity currently being processed is generated. Processing person input screen control means to control;
The activity that causes the person in charge of processing to be input by the input screen control means is an activity that is processed a plurality of times. If there is an activity that has already been processed among the activities that are processed a plurality of times, the activity that is processed a plurality of times A processing person display means for displaying a processing person assigned to the processed activity on the screen for inputting a processing person of the unprocessed activity of
A workflow management server characterized by comprising:   If the activity to be processed a plurality of times is an activity to be processed later on the route than the activity currently being processed, the processing person input screen control means is responsible for processing the activity to be processed later on the route. The workflow management server according to claim 1, wherein a screen for inputting a person is not displayed.   3. The workflow management server according to claim 1, further comprising route information visualization means for visually displaying and controlling an activity and route information stored in the route information storage means. The processing person input screen control means is means for generating and controlling a screen for displaying a processing person of the processed activity,
The handlers display means, wherein the processing personnel processed activity, the unprocessed of activity that is the multiple processing before SL activity since the activity currently being processed activity to be processed a plurality of times 4. The workflow management server according to claim 1, wherein the person in charge of processing the activity is displayed. A workflow having route information storage means for storing route information having a route for processing the same activity of the workflow a plurality of times, and progress information storage means for storing progress information of processed and currently processed activities of the workflow In the management server control method,
Based on the route information stored in the route information storage means and the progress information stored in the progress information storage means, a screen for inputting a person in charge of each activity processed after the activity currently being processed is generated. Processing person input screen control process to control,
The activity that causes the person in charge of processing to be input in the input screen control step is an activity that is processed a plurality of times, and if there is an activity that has already been processed among the activities that are processed a plurality of times, the activity that is processed a plurality of times A processing person display step of displaying a processing person assigned to the processed activity on a screen for inputting a processing person of an unprocessed activity of
A method for controlling a workflow management server, comprising:   A program for executing the control method of the workflow management server according to claim 5.   A storage medium storing a computer-readable program for executing the control method of the workflow management server according to claim 5.

Images