Workflow management device, workflow management method, and program

Abstract

To allow an approver to efficiently process a plurality of collected applications.SOLUTION: In the present embodiment, a workflow management device is a workflow management device comprising a control unit, and the control unit comprises: acquisition unit that acquires data representing an item set in which a plurality of application items is collected; display control means that controls screen display of the plurality of application items included in the item set represented by the data; and application processing means that collectively approves or rejects the plurality of displayed application items.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a workflow management device, a workflow management method, and a program.

Background Art

[0002] Patent Document 1 describes that a plurality of various applications are grouped into predetermined event units, an applicant selects applications to be performed according to an event from the various applications, and the selected plurality of applications are performed collectively. Patent Document 1 also describes that a plurality of applications applied by an applicant in event units are displayed to an approver, and the approver individually approves the displayed plurality of applications.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the invention disclosed in Patent Document 1, since a plurality of applications are individually displayed and approved, the approval work becomes complicated and burdensome for an approver who performs many approvals.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a workflow management device, a workflow management method, and a program that enable an approver to efficiently process a plurality of grouped applications.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, a workflow management apparatus according to the present invention is a workflow management apparatus including a control unit, wherein the control unit includes: an acquisition unit that acquires data representing a case set obtained by aggregating a plurality of application cases; a display control unit that controls a screen display of the plurality of application cases included in the case set represented by the data; an application processing unit that collectively approves or rejects the plurality of displayed application cases; and a setting unit that sets the application cases to be included in the case set. The application processing unit is characterized in that it advances the approval workflow to the next approver after all the application cases that are collectively approved have been approved.

[0007] Further, in the workflow management apparatus according to the present invention, the acquisition unit acquires data of the case set including at least one application case having a different approval route, the display control unit controls the display of the approval route of each of the application cases included in the case set, the application processing unit approves or rejects the application cases included in the case set, and the setting unit is characterized in that it sets the case set to include at least one application case having a different approval route as the application cases to be included in the case set.

[0008] Further, in the workflow management apparatus according to the present invention, the setting unit is characterized in that it sets an approver who collectively approves or rejects the plurality of application cases included in the case set.

[0009] Further, in the workflow management apparatus according to the present invention, the setting unit is characterized in that it sets, for the plurality of application cases included in the case set, whether to start the approval workflow every time an application is made or to start the approval workflow after all the applications are complete.

[0010] Further, in the workflow management apparatus according to the present invention, the application processing unit is characterized in that the application content of the application case can be corrected until the approval workflow of the application case is started.

[0011] Also, in the workflow management apparatus according to the present invention, when the application processing means advances the approval workflow to an approver who approves a plurality of the application cases to be approved together, each of the application cases to be approved together is approved by an approver who approves the application case before the approver who approves them together, and then the approval workflow is advanced to the approver who approves them together.

[0012] Also, in the workflow management apparatus according to the present invention, the display control means is characterized by controlling the display of the approval status for each of the plurality of application cases.

[0013] Also, in the workflow management apparatus according to the present invention, when the application case is rejected or withdrawn, the application processing means is characterized by changing the approval status of other application cases according to the rejected or withdrawn application case.

[0014] Also, in the workflow management apparatus according to the present invention, when the application processing means retreats the application workflow from an approver who is approving to a previous applicant or approver when the application case is rejected or withdrawn, if the application case is applied or approved together during the retreat to the previous applicant or approver, the range of changing the approval status in the ungrouped application cases is changed according to the application cases included in the grouped application or grouped approval.

[0015] Also, the workflow management method according to the present invention is a workflow management method executed by an information processing apparatus including a control unit, and includes an acquisition step of acquiring data representing a case set obtained by grouping a plurality of application cases, a display control step of controlling the screen display of the plurality of application cases included in the case set represented by the data, an application processing step of collectively approving or rejecting the plurality of displayed application cases, and a setting step of setting the application cases to be included in the case set, and the application processing step is characterized by advancing the approval workflow to the next approver after all of the application cases to be approved together are approved.

[0016] Also, the program according to the present invention is a program for causing an information processing apparatus including a control unit to execute, and includes an acquisition step of acquiring data representing a case set obtained by grouping a plurality of application cases for execution by the control unit, a display control step of controlling the screen display of the plurality of application cases included in the case set represented by the data, an application processing step of collectively approving or rejecting the plurality of displayed application cases, and a setting step of setting the application cases to be included in the case set. The application processing step is characterized in that the approval workflow is advanced to the next approver after all the application cases to be collectively approved are approved.

Effect of the Invention

[0017] According to the present invention, there is an effect that an approver can efficiently process a plurality of grouped applications.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, embodiments of a workflow management apparatus, a workflow management method, and a program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[0020] [1. Overview] In an organization such as a company, a workflow system that supports an application process for receiving applications and an approval process for approving applications is used. In such a workflow system, a workflow including applications and approvals / rejections is executed. In this workflow, an applicant makes not only a particular application but also other applications related to the particular application, and an approver may, when determining approval for a particular application, determine approval not only for the particular application but also for other applications related to the particular application.

[0021] For example, when a business department in a company receives an order for a project, an order application for the project and a budget application for the project are made. Also, for example, regarding the relocation of an employee in a company, an application for address change and an application for changing the commuter pass section are made. When determining approval for the order application, the approver needs to confirm not only the details of the order but also the details of the budget application related to the order and then determine approval. Also, when determining approval for the application for changing the commuter pass section, the approver needs to confirm not only the commuter pass section but also whether the address change application corresponds to the change of the commuter pass section and then determine approval.

[0022] As described above, when the same approver determines related applications, if the approval of each application is determined individually, the work becomes complicated and burdensome for approvers who perform many approvals in a large organization. Therefore, in the present embodiment, a workflow management apparatus, a workflow management method, and a program are provided that enable an approver to efficiently process a plurality of grouped applications. Specific configurations and operations will be described below.

[0023] [2. Configuration] An example of the configuration of the workflow management apparatus 100 according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of the configuration of the workflow management apparatus 100 according to the embodiment.

[0024] The workflow management apparatus 100 is, for example, a commercially available desktop personal computer. However, the workflow management apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, and may be a portable information processing apparatus such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer. Further, the workflow management apparatus 100 may be a server apparatus such as a tower type, rack mount type, or blade type that receives requests and instructions from a client and provides information and processing results to the client.

[0025] The workflow management apparatus 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the workflow management apparatus 100 is communicably connected via an arbitrary communication path.

[0026] The communication interface unit 104 communicably connects the workflow management apparatus 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 is, for example, the Internet or a LAN (Local Area Network), and has a function of communicably connecting the workflow management apparatus 100 and the server 200 to each other and communicably connecting the workflow management apparatus 100 and the terminal devices 400A and 400B to each other. Note that the data stored in the storage unit 106 may be stored in the server 200, for example, and the data processed by the control unit 102 may be acquired from the server 200.

[0027] An input / output interface unit 108 is connected to an input device 112 and an output device 114. As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0028] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records a computer program for giving instructions to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory)·ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used. The storage unit 106 stores, for example, an application set master 106a, an application set member master 106b, an application type master 106c, an application set approval route assignment master 106d, an approval route master 106e, an approval route assignment master 106f, and an approval route step master 106g. In addition, the storage unit 106 stores, for example, case set data 106h, case set member data 106i, case data 106j, case step data 106k, and case step approver data 106l. These data are data representing a case set that summarizes a plurality of application cases. The details of each master and each data will be described in [3. Specific Examples of Processing] described later.

[0029] The control unit 102 is a CPU or the like that comprehensively controls the workflow management apparatus 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processes based on these stored programs. Conceptually in terms of functions, the control unit 102 includes an acquisition unit 102a, a display control unit 102b, an application processing unit 102c, and a setting unit 102d.

[0030] The acquisition unit 102a as an acquisition means acquires the above-described master and data related to the processes performed by the control unit 102. The display control unit 102b as a display control means controls the screens to be displayed on the output device 114 and the terminal devices 400A and 400B based on the master and data acquired by the acquisition unit 102a. By the display control unit 102b, various screens described later are displayed on the output device 114 and the terminal devices 400A and 400B. The application processing unit 102c as an application processing means collectively approves or rejects a plurality of grouped application cases according to the operations performed on the terminal devices 400A and 400B. The setting unit 102d as a setting means performs various settings for the grouped applications according to the operations performed on the input device 112 and the terminal devices 400A and 400B.

[0031] The terminal devices 400A and 400B are, for example, commercially available desktop personal computers. However, the workflow management apparatus 100 is not limited to stationary information processing apparatuses such as desktop personal computers, and may also be portable information processing apparatuses such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers. The terminal devices 400A and 400B are, for example, information processing apparatuses used by applicants who perform various applications within a company and approvers who approve various applications.

[0032] [3. Specific Examples of Processing] Here, specific examples of the processes executed by the workflow management apparatus 100 will be described with reference to FIGS. 2 to 36.

[0033] (Data Structure) Figure 2 is a diagram showing an example of the structure of the master stored in the storage unit 106. The application set master 106a is a master that stores information related to an application set combining a plurality of application cases. The application set master 106a includes a set CD, a set name, an explanation, whether or not there is a consolidated application, whether or not there is an automatic application, and a rejection destination type. Whether or not there is a consolidated application is information indicating whether to start the approval workflow after all of the plurality of applications have been made or to start the approval workflow for each application. Whether or not there is an automatic application is information indicating whether to automatically start the application when the applications are complete when there is a consolidated application. When there is no consolidated application, for each application included in the application set, the approval process proceeds each time an application is made. When there is a consolidated application and there is no automatic application, after all the applications have been made and an operation to confirm the set is performed on the set application screen described later, the applications included in the application set proceed to the approval process. When there is a consolidated application and there is an automatic application, when all the applications have been made, the applications included in the application set automatically proceed to the approval process. The rejection destination type is information specifying the action when the approver rejects the application, and indicates whether to return to the applicant or return to the previous step of the approver who rejected it.

[0034] The application set member master 106b is a master that stores information related to the application types of multiple applications included in the application set. The application set member master 106b includes a set CD, an application type CD, a display order, a mandatory flag, a priority at route determination, and the availability of multiple invoicing. The priority at route determination is information that determines the priorities of multiple applications included in the application set. For example, assume that the approval route for application case (1) is in the order of Mr. A, Mr. B, and Mr. C, the approval route for application case (2) is Mr. C, Mr. B, and Mr. A, and the first and third steps of the approval route are collective approvals where the approver approves the cases together. In this case, if the priority at route determination for case (1) is 1 and the priority at route determination for case (2) is 2, the third step of case (1) and the first step of case (2) are collectively approved; if the priority at route determination for case (2) is 1 and the priority at route determination for case (1) is 2, the third step of case (2) and the first step of case (1) are collectively approved. The availability of multiple invoicing is used when multiple applications of the same type are included in the application set. If there is an automatic collective application, multiple approvals are not allowed. The application set member master 106b includes the same set CD as the set CD included in the application set master 106a. Thereby, the application set master 106a and the application set member master 106b are associated with each other.

[0035] The application type master 106c is a master that stores information related to the types of applications included in the application set. The application type master 106c includes an application type CD, an application type name, an application type group, and a rejection destination type. The application type master 106c includes the same application type CD as the application type CD included in the application set member master 106b. Thereby, the application set member master 106b and the application type master 106c are associated with each other.

[0036] The application set approval route assignment master 106d is a master that maps which approval route to use when a person drafts an application in units of application sets, and stores by associating information related to the affiliation of the applicant of the application set and information on the approval route. The application set approval route assignment master 106d includes a set CD, applicant affiliation, and approval route CD. The application set approval route assignment master 106d includes the same set CD as the set CD included in the application set master 106a. Thereby, the application set master 106a and the application set approval route assignment master 106d are associated with each other.

[0037] The approval route master 106e is a master that stores the approval route name of the application set. The approval route master 106e includes an approval route CD and an approval route name. The approval route master 106e includes the same approval route CD as the approval route CD included in the application set approval route assignment master 106d. Thereby, the application set approval route assignment master 106d and the approval route master 106e are associated with each other.

[0038] The approval route assignment master 106f is a master that maps which approval route to use when a person drafts an application in units of application types, and stores by associating information related to the affiliation of the applicant of the application type and information on the approval route. The approval route assignment master 106f includes an application type CD, applicant affiliation, and approval route CD. The approval route assignment master 106f includes the same application type CD as the application type CD included in the application type master 106c. Thereby, the application type master 106c and the approval route assignment master 106f are associated with each other. Also, the approval route assignment master 106f includes the same approval route CD as the approval route CD included in the approval route master 106e. Thereby, the approval route master 106e and the approval route assignment master 106f are associated with each other.

[0039] The approval route step master 106g is a master that stores information related to each step of the approval route of the applications included in the application set. The approval route step master 106g includes an approval route CD, step order, employee list, summary approval availability, summary approval step name, and conditional expression. For summary approval availability, for multiple applications, if the steps with summary approval are the same and the approvers are the same, it is summary approval. Also, if the summary approval step name is set, it is summary approval only when the summary approval step names are the same. The approval route step master 106g includes the same approval route CD as the approval route CD included in the approval route master 106e. Thereby, the approval route master 106e and the approval route step master 106g are associated. Note that the approval route step master 106g may include a conditional expression so as to have different routes according to the conditions of the application content. For example, as a conditional expression, by setting conditions such as when the application type CD at the time of application is equal to a specific value, different approval routes can be set according to the application type even for the same application set.

[0040] Figure 3 is a diagram showing an example of the structure of the data stored in the storage unit 106. The case set data 106h is data including information related to a case set that combines a plurality of application cases. The case set data 106h includes a set key, a case set name, and a set CD.

[0041] The case set member data 106i is data including information related to the applications included in the case set. The case set member data 106i includes a set key, a case key, display order, application type CD, and status. The case set member data 106i includes the same set key as the set key included in the case set data 106h. Thereby, the case set data 106h and the case set member data 106i are associated.

[0042] Case data 106j is data containing information related to the applications included in the case set. Case data 106j includes a case key, an application date, an applicant, a docket number, a summary of case information, a case image, and a status. Case data 106j includes the same case key as the case key included in case set member data 106i. Thereby, case set member data 106i and case data 106j are associated with each other.

[0043] Case step data 106k is data containing information related to the order of steps in the approval of the applications included in the case set. Case step data 106k includes a case key, a step order, whether there is a summary approval, and a summary approval step name. Case step data 106k includes the same case key as the case key included in case data 106j. Thereby, case data 106j and case step data 106k are associated with each other.

[0044] Case step approver data 106l is data containing information about the approvers at each step of the approval route and the approval status of each step for the applications included in the case set. Case step approver data 1061 includes a case key, a step order, an employee CD, and an approval status. Case step approver data 106l includes the same case key as the case key included in case step data 106k. Thereby, case step data 106k and case step approver data 106l are associated with each other.

[0045] (Maintenance of Approval Route) FIG. 4 is a diagram showing an example of a maintenance screen of an approval route of an application displayed on the workflow management device 100, and an example of an approval route master 106e and an approval route step master 106g created by the maintenance screen of the approval route. As shown in FIG. 4, the maintenance screen 501 of the approval route includes an arrow indicating the progress direction of approval and a box indicating the approver at each step of the approval route. Further, the setting screen of the approval route includes a text box for setting an approval route CD, an approval route name, an approver name, a summary approval step name, and a radio button for setting whether there is a summary approval.

[0046] When the operator inputs the approval route CD and the approval route name on the maintenance screen 501 and clicks the registration button on the maintenance screen 501, as shown in FIG. 4, the input approval route CD and approval route name are stored in the approval route master 106e. Also, for each approval step indicated by a box on the maintenance screen 501, the approver name, the presence or absence of summary approval, and the summary approval step name are input, and by clicking the registration button on the maintenance screen 501, as shown in FIG. 4, for each step, the approval route CD, step order, employee name, presence or absence of summary approval, and summary approval step name are stored in the approval route step master 106g. Note that the input approver name is stored in the column of the employee list in the approval route step master 106g.

[0047] Note that for the setting of summary approval, among the cases included in the application set, if there is a step with summary approval and the approver is the same, it will be summary approval. Also, when the summary approval stage name is specified, it will be summary approval only when the summary approval stage name is the same.

[0048] (Application Set Creation) FIG. 5 is a diagram showing an example of a screen related to the creation of an application set, and an example of the application type master 106c, the application set master 106a, and the application set member master 106b. The application type master 106c is preset prior to the creation of the application set. In the workflow management device 100, on the application set creation screen 502, the already created application sets are displayed in a list associated with the set CD. Here, for example, by clicking any of the buttons "New", "Modify", or "Copy", the screen transitions to the application set editing screen 503.

[0049] On the application set editing screen 503, the set CD of the application set is input in the CD text box, the set name of the application set is input in the name text box, and the description of the application set is input by the operator in the description text box. Also, on the application set editing screen 503, it is set by radio buttons whether to group multiple applications for application or to apply each time.

[0050] By inputting the set CD, inputting the set name, inputting the description of the application set, selecting the radio button, and clicking the registration button, as shown in FIG. 5, the content set on the application set editing screen 503 is stored in the application set master 106a. Note that when "apply each time" is selected by the radio button, the existence of grouped application is "none", and the existence of automatic application is blank. Also, when "grouped application (manual)" is selected by the radio button, the existence of grouped application is "none", and the existence of automatic application is "none". When "grouped application (automatic)" is selected by the radio button, the existence of grouped application is "yes", and the existence of automatic application is "yes".

[0051] Select the applications to be included in the application set from the list of application types, operate on the columns of group, application type, required, multiple invoicing possible, and priority for the selected applications, and click the registration button. As shown in FIG. 5, the set information is stored in the application set member master 106b. Note that the list of application types is displayed based on, for example, the application type master 106c illustrated in FIG. 5. The application type CD included in the application set member master 106b is the application type CD corresponding to the application type name selected from the list.

[0052] (Application Type Route / Application Set Route Assignment) FIG. 6 is a diagram showing an example of an assignment screen for the approval route of an application displayed on the workflow management device 100, and an example of the application type master 106c, the application set master 106a, the approval route master 106e, the approval route assignment master 106f, and the application set approval route assignment master 106d.

[0053] As shown in FIG. 6, on the approval route assignment screen 504, there are provided a column of "applicant's department" for selecting the department to which the applicant who makes the application belongs, a column of "application type / application set" for selecting the application type or application set for setting the route, and a column of "approval route" for selecting the approval route to be assigned to the application type or application set. This screen is displayed based on, for example, the application type master 106c, the application set master 106a, and the approval route master 106e shown in FIG. 6.

[0054] When the operator assigns an approval route to an application type or an application set, first, the operator selects the department to which the applicant who makes the application belongs in the column of "applicant's department" on the approval route assignment screen 504. Next, the operator selects the application type or application set to which the approval route is to be assigned in the column of "application type / application set", and selects the approval route to be assigned to the selected application type or application set in the column of "approval route".

[0055] When the operator assigns an approval route to an application type, the approval route assignment master 106f is set. When the operator assigns an approval route to an application set, the application set approval route assignment master 106d is set. When the applicant of the application case makes a single application without making a set application, the approval route for each application type is determined by referring to the approval route assignment master 106f. Also, when the applicant of the application case makes a set application, first, if the approval route for each application set for making the set application is set by referring to the application set approval route assignment master 106d, this set approval route is adopted. If not, the approval route for each application type included in the application set and for which an application is made is adopted by referring to the approval route assignment master 106f. Thereby, even when the approval route for each application type included in the application set and for which an application is made is adopted, it is possible to cope with a mode in which different approval routes are obtained according to the application content.

[0056] For example, as shown in FIG. 6, when “General Affairs Department” is selected in the “Applicant Affiliation” column, “Budget + Order Receipt” is selected in the “Application Type / Application Set” column, “Business Department Route” is selected in the “Approval Route” column, and the “↑ Assignment” part of the setting screen is clicked, the application set approval route assignment master 106d will have the content shown in FIG. 6. Here, in the application set approval route assignment master 106d, in the column of “Set CD”, “S01” of the set CD associated with the “Budget + Order Receipt” application set in the application set master 106a is stored; in the column of “Applicant Affiliation”, “General Affairs Department” selected in the “Applicant Affiliation” column is stored; and in the column of “Approval Route CD”, “R02” of the approval route CD associated with the “Business Department Route” in the approval route master 106e is stored.

[0057] (Pattern (1)) Next, a processing example will be described for the case where the applicant combines budget applications and order registration applications, and the approver approves the applications together. In this processing example, it is assumed that the contents of the application type master 106c, the application set master 106a, and the application set member master 106b before application are as shown in FIG. 7. Also, for the approval route of the budget application, the route is applicant → employee with employee CD “100001” (with collective approval) → employee with employee CD “100002” (with collective approval) → employee with employee CD “100003” (with collective approval); for the approval route of the order registration application, the route is applicant → employee with employee CD “100001” (with collective approval) → employee with employee CD “100003” (with collective approval). Note that in each master shown in FIG. 7, the illustration of records and columns not used in the description of the processing example is omitted.

[0058] FIG. 8 is a diagram showing a screen displayed when a budget application is made and an example of data created based on the screen. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for budget application, on the terminal device 400A, a budget application screen 505 shown in FIG. 8 provided from the workflow management device 100 is displayed. The applicant inputs each item related to the budget application on this budget application screen 505. When the applicant makes a budget application in a set with order registration, the applicant checks the check box of "Make a set application" and clicks the "Register" button. When the applicant clicks the "Register" button, a set selection screen 506 for selecting an application set including the budget application to be applied shown in FIG. 8 as the application type is displayed on the terminal device 400A.

[0059] Here, when the applicant selects "Budget + Order" on the set selection screen 506 and clicks the "Apply" button, the workflow management device 100 creates, as data related to this application, project data 106j, project step data 106k, project step approver data 106l, project set data 106h, and project set member data 106i shown in FIG. 8. Note that since the automatic application flag is "Yes" and the summary application flag is "Yes" in the application set master 106a in FIG. 7, at this point, since the order registration application has not been made, the approval workflow is not started.

[0060] In the project data 106j, a project key that uniquely identifies the applied budget application is stored in the column of the project key. Note that since the application for order registration has not been made here, the information of "Before application" is stored in the status column of the project data 106j.

[0061] In the project step data 106k, since the approval route for the budget application includes three approvers, 1 to 3 are stored in the column of step order. Also, for the approver, since there is a summary approval as described above, "Yes" is stored in the column of summary approval availability.

[0062] In the project step approver data 106l, for each step of the approval route of the budget application, the step order and the employee CD of the employee who approves at each step are stored. At this point, since the order registration application, which is an application grouped in the budget application, has not been submitted and the workflow of the budget application has not started, "unprocessed" is stored in the "approval status" column.

[0063] In the project set data 106h, the set key that uniquely identifies the application set is stored in the set key column, the project set name entered on the set selection screen 506 is stored in the "project set name" column, and the application set CD corresponding to "budget + order" is stored in the set CD column.

[0064] In the project set member data 106i, the set key of the application set, the project key of the budget application included in the application set, and the project key of the order registration are stored. Also, the contents of the application set member master 106b corresponding to the application set are copied to the "display order" and "application type CD" columns of the project set member data 106i. In the "status" column of the project set member data 106i, in the record of the budget application project, since the order registration project, which is a set, has not been applied at this point, it is "before application", and in the record of the order registration project, since the order registration project has not been applied at this point, it is "not invoiced". In the "status" column of the project set member data 106i, if there is no collective approval, it becomes "applied", if there is collective approval and there is an unapplied item, it becomes "before application", if there is collective approval and there is no unapplied item and there is no automatic application, it becomes "before application", and if there is collective approval and there is no unapplied item and there is automatic application, it becomes "applied".

[0065] FIG. 9 is a diagram showing a screen displayed when applying for an order registration that is set with a budget application and an example of data created based on the screen. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for applying for order registration, on the terminal device 400A, an order registration screen 507 shown in FIG. 9 provided by the workflow management device 100 is displayed. The applicant inputs each item related to the order registration on this order registration screen 507. When the applicant applies for order registration in a set with a budget application, the applicant checks the check box of "Apply as a set" and clicks the "Register" button. When the applicant clicks the "Register" button, an application set list screen 508 for selecting an application set including the order registration case to be applied shown in FIG. 9 as the application type is displayed on the terminal device 400A.

[0066] Note that until the approval workflow is started, the content of the application can be modified without withdrawing the application.

[0067] Here, when the applicant selects the "Budget + Order" application set on the application set list screen 508 and clicks the "Apply" button, the application for order registration is completed. Here, since the budget application and the order registration are complete, and the automatic application availability is "Yes" and the summary application availability is "Yes" in the application set master 106a of FIG. 7, the workflow management device 100 automatically starts the approval workflow. Further, when the application for order registration is completed, the workflow management device 100 updates the case data 106j, the case step data 106k, the case step approver data 106l, the case set data 106h, and the case set member data 106i as shown in FIG. 9.

[0068] Regarding the status, if the combined application flag is "Yes" and the automatic application flag is "No", the status column of the second row record in the case data 106j is updated to "Before application", and the status column of the second row record in the case set member data 106i is updated to "Before application". In this case, the approval workflow does not start automatically, and the approver with a step sequence of 1 cannot perform the approval. When the combined application flag is "Yes", the "Route for approval" button is displayed on the application set list screen 508 shown in FIG. 9. When the applicant selects the application set and clicks the "Route for approval" button, the status column of the second row record in the case data 106j is updated to "During application", the status column of the second row record in the case set member data 106i is updated to "Applied", the approval workflow is started, and the approver with a step sequence of 1 can perform the approval. "During application" for the status column indicates that the approval workflow is in progress when viewed on a case-by-case basis after the application has been made, and "Applied" indicates that the application actions for each of the grouped application cases have been completed.

[0069] When the approver operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display the list of applications in charge, for example, the unapproved list screen 509 which is a list of unapproved applications shown in FIG. 10 provided by the workflow management device 100 is displayed. When the approver checks the check boxes of the combined budget application and order registration records on the unapproved list screen 509 and clicks the "Approve" button, the budget application and order registration are approved together. When the "Reject" button is clicked, the budget application and order registration applications are rejected together.

[0070] Note that until all applications subject to batch approval are approved by the approver in the previous step, the applications subject to batch approval are not displayed on the Unapproved List Screen 509 for the next approver. Also, in the case record step data 106k, if there is no batch approval indication in the record with a step order of 1, the first approver can perform approval starting from the timing when an individual case is sent for approval. Further, in the case record step data 106k, if there is no batch approval indication in the records with a step order of 2 or later, the approvers with a step order of 2 or later can perform approval after the approver in the previous step has approved.

[0071] Also, when the approver clicks the "Details" button for a record of budget application or order registration on the Unapproved List Screen 509, as shown in Figure 10, an Application Details Screen 510 that displays the details of the application related to the clicked record is shown. On this Application Details Screen 510, when the part of the character string "Budget Application" is clicked, the details of the budget application are displayed, and when the part of the character string "Order Registration" is clicked, the details of the order registration are displayed. On the Application Details Screen 510, when the "Approval" part is clicked, the applications for budget application and order registration are approved together, and when the "Reject" button is clicked, the applications for budget application and order registration are rejected together.

[0072] Note that when the approver performs an operation to display the approval route of the application, for example, a Route Inquiry Screen 511 illustrated in Figure 10 showing the approval route and the approval status is displayed.

[0073] On the Route Inquiry Screen 511, since all steps of "Start" are completed and for "Budget Application" and "Order Registration", the approval processing by all approvers is unprocessed, it is the step of batch approval, and it is displayed that the current step in the approval process is at the position of "(1)" with a step order of 1, and it is also displayed that it is the step where an employee with an employee CD of "100001" performs approval. Through the Route Inquiry Screen 511, the approver can know the approval route and the approval status of the applications for budget application and order registration.

[0074] In the case step data 106k, for the record with the step order being "1", since the overall approval status is "Yes", on the route inquiry screen 511, at the position of "(1)" where the step order is 1, the backgrounds of the "Budget Application" status and the "Order Registration" status are displayed as the overall approval step which is the overall approval.

[0075] In the case step approver data 106l, for the case key "Y-9A78123F" where the employee CD is "100002" and the step order is "2", although the overall approval status in the case step data 106k is "Yes", in the case step approver data 106l, since there is no record with the same employee CD but a different case key, at the position of "(2)" where the step order is 2, the background of the status is not exceptionally displayed as the overall approval step.

[0076] On the route inquiry screen 511, for the employee with the employee CD being "100003" who is the approver, for "Order Registration", the approval step order is 2, but for "Budget Application", the approval step order is 3. Since the approvals for "Budget Application" and "Order Registration" are consolidated, in accordance with the step of "Budget Application", the approval status of "Order Registration" is displayed at the position of "(3)" where the step order is 3.

[0077] Also, for the case key "Y-9A78123F" where the employee CD is "100003" and the step order is "3" in the case step approver data 106l, since the overall approval status in the case step data 106k is "Yes", at the position of "(3)" where it is displayed together with the case of the case key "J-B34D662C" with the step order of 2, the background of the status is displayed as the overall approval step.

[0078] Also, since the "Overall Application Existence" in the application set master 106a is "Yes" and all the columns of "Status" in the case set member data 106i are "Applied", the "Previous" step and the "Start" step are displayed as processed.

[0079] Also, since "Consolidated Application Existence" is "Yes" in the Application Set Master 106a, the background is displayed as the consolidation step in the "Start" step.

[0080] If "Consolidated Application Existence" is "Yes" in the Application Set Master 106a and there is "Not Yet Invoiced" in the "Status" column of the Case Set Member Data 106i, for the already applied applications, the "Previous" step is displayed as processed, the "Start" step is displayed as unprocessed, and for the not yet invoiced applications, the status is not displayed in the "Previous" step and the "Start" step.

[0081] When the budget application and the order registration are approved together by the first approver in the approval route, the case data 106j, the case step data 106k, and the case step approver data 106l become the content shown in FIG. 11. Also, when the approver performs an operation to display the approval route at this time, the status display of each step on the route inquiry screen becomes the route display 512 shown in FIG. 11. The route display 512 shown in FIG. 11 indicates that the budget application is waiting for the judgment of the second approver, and for the order registration, since the budget application has not been approved by the second approver, it shows that it has stopped before the third step.

[0082] Specifically, in the approval step where the step order of the consolidated approval is 1, when the approver with the employee CD "100001" approves the "Budget Application" and the "Order Registration", the status column of the case data 106j is linked to become "Approval In Progress", and in the two records in the case step approver data 106l where the step order is 1 and the employee CD is "100001", the approval status column is linked to become "Approved". In the approval step where the step order is 1, since the "Budget Application" and the "Order Registration" have been approved, at the position of "(1)" where the step order is 1, the status is displayed as processed.

[0083] In the case step approver data 106l, for records containing the case key "Y-9A78123F" of the budget application, the employee CD "100002" is stored in the record where the step order is "2". However, in the records containing the case key "J-B34D662C" of the order registration, since there is no record with the employee CD "100002", the "budget application" is processed as not being a batch approval. Regarding the approval of the "budget application", it is displayed that the current step is at the position of "(2)" where the step order is 2.

[0084] In the case step data 106k, for the record containing the case key "J-B34D662C" of the order registration, the record with the step order "2" has the batch approval status as "yes". However, in the case step approver data 106l, in the record containing the case key "Y-9A78123F" of the budget application, since the approval status of the record with the employee CD "100003" and the step order 2 is "unprocessed", it is determined that the batch approval of the third step order of the budget application and the second step order of the order registration is not possible, and the display of the order registration status shows that the current step is at the position of the arrow on the left side of the step order of "(3)".

[0085] When the budget application is approved by the approver at the second step of the approval route, the case data 106j, the case step data 106k, and the case step approver data 106l will be as shown in Figure 12. Also, when the approver performs an operation to display the approval route at this time, the status display of each step on the route inquiry screen will be the route display 513 shown in Figure 12. The route display 513 in Figure 12 indicates the state where the budget application and the order registration are waiting for the final approver's judgment.

[0086] Specifically, in the approval step where the step order is 2, since the approver with the employee CD "100002" has approved the "budget application", in the record in the case step approver data 106l where the step order is 2 and the employee CD is "100002", the approval status column will be linked and become "approved".

[0087] The approval step where the step order is 2, that is, in the (2) step on the route inquiry screen, since the "budget application" has been approved, the status is displayed as processed at the position of "(2)".

[0088] In the case record step approver data 106l, for the record where the employee CD is "100003", the approval status of all steps one step before the step order is "approved", and for the record where the employee CD is "100003", the approval status is "unprocessed". Therefore, on the route inquiry screen, it is displayed that it is the current step at the position of "(3)".

[0089] (Pattern (2)) Next, a processing example will be described when the applicant makes the same type of application and the approver approves the applications together. In this processing example, it is assumed that the contents of the application type master 106c, application set master 106a, and application set member master 106b before the application are those shown in FIG. 13. Also, regarding the approval route of the order entry registration application, it is assumed to be the route of applicant → employee with employee CD "100001" (with collective approval) → employee with employee CD 100002 (with collective approval). In each master shown in FIG. 13, the illustration of records and columns not used in the description of the processing example is omitted.

[0090] FIG. 14 is a diagram showing a screen displayed when an order registration application is made and an example of data created based on the screen. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for an order registration application, on the terminal device 400A, an order registration screen 514 shown in FIG. 14 provided from the workflow management device 100 is displayed. The applicant inputs each item related to the order registration on this order registration screen 514. When the applicant performs order registration as a set with another order registration, the applicant checks the "Apply as a set" checkbox and clicks the "Register" button. When the applicant clicks the "Register" button, as shown in FIG. 14, a set selection screen 515 for selecting an application set name including the order registration to be applied as the application type is displayed on the terminal device 400A.

[0091] Here, when the applicant selects "Set sales" on the set selection screen 515 and clicks the "Apply" button, the workflow management device 100 creates, as data related to this application, the project data 106j, project step data 106k, project step approver data 106l, project set data 106h, and project set member data 106i shown in FIG. 14.

[0092] In the project data 106j, a project key that uniquely identifies the applied order registration is stored in the project key column. Note that in the status column of the project data 106j, information indicating "under application" is stored because the summary application availability of the application set master 106a is "none" here.

[0093] In the project step data 106k, since the approval route for the budget application includes two approvers, 1 and 2 are stored in the step order column. Also, for the approver, since there is a summary approval as described above, "yes" is stored in the summary approval availability column.

[0094] In the project step approver data 106l, for each step of the approval route for order entry registration, the step order and the employee CD of the employee who approves at each step are stored. At this point, since the summary application flag in the application set master 106a is "none" and the workflow for the first order entry registration has not started, "not processed" is stored in the "approval status" column.

[0095] In the project set data 106h, the set key that uniquely identifies the applied application set is stored in the set key column, the project set name entered on the set selection screen 515 is stored in the "project set name" column, and the application set CD corresponding to "set sales" is stored in the set CD column.

[0096] In the project set member data 106i, the set key of the application set and the project key of the applied order entry registration included in the application set are stored. Also, the contents of the application set member master 106b corresponding to the application set are copied to the "display order" and "application type CD" columns of the project set member data 106i. Since the summary application flag in the application set master 106a is "none", the "status" column of the project set member data 106i becomes "applied".

[0097] FIG. 15 is a diagram showing an example of a screen displayed when an order registration application that is to be set with a previously filed order registration is made. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation to display an application menu, an application menu screen 516 provided from the workflow management device 100 is displayed on the terminal device 400A. On this application menu screen 516, when the applicant clicks on the string "Set Application", an application set list screen 517 shown in FIG. 15 is displayed. On this application set list screen 517, when the applicant clicks on "Set Sale", a set application screen 518 shown in FIG. 15 is displayed. On the set application screen 518, the approval route and the approval status of the previously filed order registration application are displayed. Here, if there are no un-invoiced applications, the applications in progress have their approval steps advancing. On the set application screen 518, when "Order Registration" is selected and the "Add" button is clicked, a new "Order Registration" is added, and a set application screen 519 shown in FIG. 15 is displayed. Here, if there are un-invoiced applications, the applications in progress have their approval steps once reverted. When this added "Order Registration" is clicked, an order registration screen 507 is displayed. When an operation of inputting each item related to the order registration and clicking the "Register" button is performed on the displayed order registration screen 507, a set application screen 520 shown in FIG. 15 is displayed. Here, when there are no un-invoiced applications left, the applications in progress have their approval steps advancing.

[0098] Note that immediately after an application has been made where multiple invoicing possibilities in the application set member master 106b are "possible", even if "Add" is not performed on the set application screen 518 in FIG. 15, data with the same application type and a status of "un-invoiced" may be automatically added as shown in the second row of the set application screen 519. By doing so, it becomes possible to hold off on the workflow going to the approver in the collective approval step until the registration of the necessary order registrations is completed and the set content is finalized. This is suitable in cases where the cases that the approver in the collective approval step should approve are not determined until all the set content is finalized.

[0099] On the set application screen 520, since there is no collective application in the application set master 106a, a "Confirm Set" button is displayed as shown in Fig. 15. Clicking the "Confirm Set" button on the set application screen 520 completes the order registration application. Here, the case data 106j, case step data 106k, case step approver data 106l, case set data 106h, and case set member data 106i will be as shown in Fig. 16.

[0100] In addition, if the required flag of the application set member master 106b in the case set member data 106i is "optional" and the status is "not invoiced", when the "Confirm Set" button is clicked, the status of the data may be automatically changed to "discarded", or a confirmation message such as "There is data that has not been invoiced. Do you want to discard it and confirm the set?" may be displayed to the applicant, and when "Yes" is selected, the status of the data may be automatically changed to "discarded". In this way, when there is no collective application, only when the status of the case data 106j is "applying", and there is no data with the status of "not invoiced" in the case set member data 106i, the set content is considered to be confirmed, and the workflow will also go to the approver in the collective approval step and be displayed as an approval target. The set application screen 519 in Fig. 15 still has data with the status of not invoiced remaining. For the order registration in the first row, it is displayed that the current step is at the position of "→" before the step "(1)", which is a step in the collective approval, indicating that it is stopped in front of the approver of the collective approval.

[0101] When the approver operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display a list of applications to be handled, for example, an unapproved list screen 521 shown in FIG. 17 provided by the workflow management device 100 is displayed. When the approver checks the checkboxes of two order reception registration records summarized on the unapproved list screen 521 and clicks the "Approve" button, the applications for the two order reception registrations are approved together. When the "Reject" button is clicked, the applications for the two order reception registrations are rejected together.

[0102] Also, when the approver clicks the "Details" button of an order reception registration record on the unapproved list screen 521, as shown in FIG. 17, an application details screen 522 that displays the details of the application related to the clicked record is displayed. On this application details screen 522, when the upper part of the "Order Reception Registration" character string is clicked, the details of the previously applied order reception registration are displayed. When the lower part of the "Order Reception Registration" character string is clicked, the details of the later applied order reception registration are displayed. On the application details screen 522, when the "Approve" part is clicked, the two "Order Reception Registrations" are approved together. When the "Reject" button is clicked, the two "Order Reception Registrations" are rejected together. Also, when the approver performs an operation to display the approval route of the application, a route inquiry screen 523 illustrated in FIG. 17 showing the approval route and the approval status is displayed. With the route inquiry screen 523, the approver can know the approval route and the approval status of the applications for the two order reception registrations.

[0103] (Pattern (3)) Next, an example of the process when the applicant submits the application for dispatch registration and the application for account registration accompanying the new dispatch registration together, and the route of the combined application is different from the middle will be described. In this example of the process, it is assumed that the contents of the application type master 106c, the application set master 106a, and the application set member master 106b are as shown in FIG. 18 before the application of the application set. Also, regarding the approval route of dispatch registration, the route is applicant → employee with employee CD "100001" (with collective approval) → employee with employee CD "100002" (with collective approval) → employee with employee CD "100003" (without collective approval), and regarding the approval route of account registration, the route is applicant → employee with employee CD "100001" (with collective approval) → employee with employee CD "100002" (with collective approval) → employee with employee CD "100004" (without collective approval). Note that in each master shown in FIG. 18, the illustration of records and columns not used in the description of the example of the process is omitted.

[0104] FIG. 19 is a diagram showing an example of a screen displayed when applying for dispatch registration and data created based on the screen. When the applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for applying for dispatch registration, on the terminal device 400A, the dispatch registration screen 524 shown in FIG. 19 provided by the workflow management device 100 is displayed. The applicant enters each item related to dispatch registration on this dispatch registration screen 524. When the applicant wants to perform dispatch registration in a set with account registration, the applicant checks the "Apply as a set" checkbox and clicks the "Register" button. When the applicant clicks the "Register" button, as shown in FIG. 19, a set selection screen 525 for selecting an application set name including the dispatch registration to be applied as the application type is displayed on the terminal device 400A.

[0105] Here, when the applicant selects "dispatch employment" on the set selection screen 525 and clicks the "apply" button, the workflow management device 100 creates, as data related to this application, the case data 106j, case step data 106k, case step approver data 106l, case set data 106h, and case set member data 106i shown in FIG. 19.

[0106] In the case data 106j, a case key that uniquely identifies the applied dispatch registration is stored in the column of the case key. Note that since no account registration application has been made here, the information "before application" is stored in the status column of the case data 106j.

[0107] In the case step data 106k, since the approval route for dispatch registration includes three approvers, 1 to 3 are stored in the column of step order. Also, since there is a collective approval up to the second step of approval, "yes" is stored in the column of collective approval presence / absence, and for the third step, "no" is stored in the column of collective approval presence / absence.

[0108] In the case step approver data 106l, for each step of the approval route of dispatch registration, the step order and the employee CD of the employee who approves at each step are stored. Note that at this point, since the account registration, which is an application to be aggregated, has not been applied and the dispatch registration workflow has not been started, "untreated" is stored in the column of "approval status".

[0109] In the case set data 106h, a set key that uniquely identifies the applied application set is stored in the column of the set key, the case set name entered on the set selection screen 525 is stored in the column of "case set name", and the application set CD corresponding to "dispatch employment" is stored in the column of set CD.

[0110] In the case set member data 106i, the set key of the application set, the case keys of the dispatch registrations included in the application set, and the case keys of the account registrations are stored. Also, the contents of the application set member master 106b corresponding to the application set are copied to the columns of "display order" and "application type CD" in the case set member data 106i. Note that in the column of "status" in the case set member data 106i, in the record of the "dispatch registration" case, since the account registration case that is the set is not yet applied at this time, it is "before application", and in the record of the account registration case, since the account registration case is not yet applied at this time, it is "not invoiced".

[0111] Figure 20 is a diagram showing an example of a screen displayed when applying for an account registration that is set with a dispatch registration, and data created based on the screen. When the applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for applying for an account registration, on the terminal device 400A, the account registration screen 526 shown in Figure 20 provided by the workflow management device 100 is displayed. The applicant inputs each item related to the account registration on this account registration screen 526. When the applicant applies for an account registration with a set of dispatch registration, the applicant checks the check box of "apply as a set" and clicks the "register" button. When the applicant clicks the "register" button, as shown in Figure 20, an application set list screen 527 including the case of the account registration to be registered is displayed on the terminal device 400A.

[0112] Here, when the applicant selects the application set of "dispatch employment" on the application set list screen 527, the application for the account registration is completed. When the application for the "account registration" is completed, the workflow management device 100 updates the case data 106j, the case step data 106k, the case step approver data 106l, the case set data 106h, and the case set member data 106i as shown in Figure 20.

[0113] Here, since the dispatch registration and account registration are both complete, the "Automatic Application" field in the application set master 106a in FIG. 18 is "Yes", and the "Consolidated Application" field is "Yes", the status column of the case data 106j becomes "Under Application", and the status column of the case set member data 106i becomes "Applied". Since the status column of the case set member data 106i becomes "Applied" and the approval status column of the case step approver data 106l is "Unprocessed", the workflow management device 100 automatically starts the approval workflow, and the workflow is routed to the approver of step (1), which is the first step of the consolidated approval.

[0114] When the approver operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display the list of applications in charge, for example, an unapproved list screen 528 as shown in FIG. 21 provided by the workflow management device 100 is displayed. When the approver checks the checkboxes of the records of the dispatch registration and account registration grouped on the unapproved list screen 528 and clicks the "Approve" button, the applications for dispatch registration and account registration are approved together. When the "Reject" button is clicked, the applications for dispatch registration and account registration are rejected together.

[0115] Also, when the approver clicks the "Details" button of the record of the dispatch registration or account registration on the unapproved list screen 528, an application details screen 529 that displays the details of the application related to the clicked record is displayed as shown in FIG. 21. On this application details screen 529, when the part of the "Dispatch Registration" string is clicked, the details of the dispatch registration application are displayed, and when the part of the "Account Registration" string is clicked, the details of the account registration application are displayed. On the application details screen 529, when the "Approve" part is clicked, the applications for dispatch registration and account registration are approved together. When the "Reject" button is clicked, the applications for dispatch registration and account registration are rejected together.

[0116] When the approver performs an operation to display the approval route of the application, for example, the route inquiry screen 530 illustrated in FIG. 21 showing the approval route and the approval status is displayed. Through the route inquiry screen 530, the approver can know the approval route of the application for dispatch registration and account registration and the approval status.

[0117] On the route inquiry screen 530, since all the columns of the status of the case set member data 106i are "applied" and all the columns of the approval status of the case step approver data 106l are "untreated", the step of "(1)" is displayed as the current step, and as the information of the approver of the step of "(1)" which is the current step, the employee name of the approver and the employee CD of "100001" are displayed.

[0118] Also, on the route inquiry screen 530, since the approval presence / absence is "yes" for the records with step numbers "1" and "2" grouped in the case step data 106k, and the employee CD of the approver is the same for the record with step number "1" and the employee CD of the approver is the same for the record with step number "2" in the case step approver data 106l, the status display for the steps of "(1)" and "(2)" is displayed as a grouped step. Also, since the approval presence / absence is "no" for the record with step number "3" in the case step data 106k, the status display for the step of "(3)" is not displayed as a grouped step.

[0119] (Pattern (4)) Next, a processing example will be described for the case where the applicant makes multiple applications sequentially and approval is given after all the multiple applications are complete. In this processing example, it is assumed that the contents of the application type master 106c, application set master 106a, and application set member master 106b are as shown in Fig. 22 before the multiple applications. Also, regarding the approval route for the application for address change related to the processing example, the route is applicant → employee with employee CD "100001" (with collective approval) → employee 100002 (with collective approval). Regarding the approval route for the application for regular period change, the route is applicant → employee with employee CD "100001" (with collective approval). Regarding the approval route for the application for dormitory entry, the route is applicant → employee with employee CD "100002" (with collective approval). Regarding the approval route for the application for dormitory exit, it is assumed that the route is applicant → employee with employee CD "100002" (with collective approval).

[0120] Fig. 23 is a diagram showing an example of a screen displayed when an application for address change is made and data created based on the screen. When the applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for an application for address change, on the terminal device 400A, the address change screen 531 shown in Fig. 23 provided by the workflow management device 100 is displayed. The applicant inputs each item related to the address change on this address change screen 531. When the applicant makes an application for address change in a set with other applications, the applicant checks the "Make a set application" checkbox and clicks the "Register" button. When the applicant clicks the "Register" button, as shown in Fig. 23, a set selection screen 532 for selecting an application set name including the applied address change as the application type is displayed on the terminal device 400A.

[0121] Here, when the applicant selects "Address change" on the set selection screen 532 and clicks the "Apply" button, the workflow management device 100 creates, as data related to this application, the case data 106j, case step data 106k, case step approver data 106l, case set data 106h, and case set member data 106i shown in Fig. 23.

[0122] In case data 106j, a case key that uniquely identifies the applied address change is stored in the case key column. Note that in the status column of case data 106j, for the application set including the address change, since "no consolidated application" is set to "no" in application set master 106a for "consolidated application availability", information indicating "under application" is stored.

[0123] In case step data 106k, since the approval route for the address change includes two approvers, 1 and 2 are stored in the step order column. Also, since there is a consolidated approval up to the second step of the approval, "yes" is stored in the consolidated approval availability column.

[0124] In case step approver data 106l, for each step of the approval route for the address change, the step order and the employee CD of the employee who performs the approval at each step are stored. Note that at this point, since other applications to be consolidated are unapplied and the workflow of other applications has not been started, "unprocessed" is stored in the "approval status" column.

[0125] In case set data 106h, a set key that uniquely identifies the applied application set is stored in the set key column, the case set name entered on the set selection screen 532 is stored in the "case set name" column, and the application set CD corresponding to "address change" is stored in the set CD column.

[0126] In case set member data 106i, the set key of the application set, the case key of the regular interval change included in the application set, the case key of the move-in application included in the application set, and the case key of the move-out application are stored. Also, the contents of application set member master 106b corresponding to the application set are copied to the "display order" and "application type CD" columns of case set member data 106i. Note that in the "status" column of case set member data 106i, it becomes "applied" in the record of the "address change" case, and in the records of other cases, since other cases are unapplied, it becomes "not invoiced".

[0127] FIG. 24 is a diagram showing an example of a screen displayed when an application that is to be set with a previously applied address change is made. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation to display an application menu, an application menu screen 516 provided from the workflow management device 100 is displayed on the terminal device 400A. On this application menu screen 516, when the applicant clicks on the string "Set Application", an application set list screen 533 shown in FIG. 24 is displayed. On this application set list screen 533, when the applicant clicks on "Address Change", a set application screen 534 shown in FIG. 24 is displayed. On the set application screen 534, the approval route and the approval status of the previously applied address change application are displayed. Also, on the set application screen 534, since the presence or absence of grouped application in the application set master 106a is "none", a "Confirm Set" button is displayed. On the set application screen 534, when "Dormitory Application" is selected and the "Discard" button is clicked, as shown in the set application screen 535, "Dormitory Application" is discarded from the set application. Note that also on the set application screen 535, since the presence or absence of grouped application in the application set master 106a is "none", a "Confirm Set" button is displayed. Also, on the set application screen 535, when "Regular Interval Change" is selected and the "Issue Ticket" button is clicked, a screen (not shown) for making an application for "Regular Interval Change" is displayed. When an operation of inputting each item related to "Regular Interval Change" on the displayed screen and clicking the "Register" button is performed, the case data 106j, the case step data 106k, the case step approver data 106l, the case set data 106h, and the case set member data 106i become the content shown in FIG. 25.

[0128] Note that on the set application screen 534 and the set application screen 535, since there are remaining applications with the status of "not yet issued", for the address change that is being applied, the current step is displayed at the position of "→" in front of the position of "(1)", which is the step of grouped approval, indicating that the workflow is stopped in front of the approver of the grouped approval.

[0129] Similarly, when "Check-out Application" is selected on the set application screen 535 and the "Issue Ticket" button is clicked, a screen (not shown) for making a "Check-out Application" will be displayed. When each item related to the "Check-out Application" is input on the displayed screen and the "Register" button is clicked, the case data 106j, case step data 106k, case step approver data 106l, case set data 106h, and case set member data 106i will be as shown in FIG. 26.

[0130] Here, all columns of the status in the case data 106j become "Pending Application", and the columns of the status in the case set member data 106i become "Applied" or "Discarded" and there is no "Not Yet Issued Ticket". In this way, since the approvers for all steps of the summary approval have been determined, the approval workflow that was stopped for the approver of the step with step sequence 1, which is a step of summary approval, is released, and the approval workflow will proceed for the approver of the summary approval.

[0131] In addition, if there are items in the case set member data 106i where the required flag in the application set member master 106b is "Optional" and the status is "Not Yet Issued Ticket", when the "Confirm the Set" button is clicked, the status of the data may be automatically changed to "Discarded", or a confirmation message such as "There is unissued ticket data. Do you want to discard it and confirm the set?" may be displayed to the applicant, and when "Yes" is selected, the status of the data may be automatically changed to "Discarded". In this way, when there is no summary application, when only the status of the case data 106j is "Pending Application" and there is no data with the status of "Not Yet Issued Ticket" in the case set member data 106i, the set content is considered to be determined, and the approval workflow will also proceed for the approver of the summary approval step and be displayed as an approval target. By doing this, it is possible to stop the approval workflow from proceeding for the approver of the summary approval step until the required applications in the set content are determined, which is suitable when the applications that the approver of the summary approval step should approve are not determined until the set content is determined.

[0132] In addition, when the case set member data 106i includes those with the required flag of the application set member master 106b being "required" and the status being "not invoiced", an error message indicating that the required application has not been made may be displayed when the "confirm the set" button is clicked.

[0133] In addition, on the set application screen 535, by selecting the application type and clicking the "Modify" button, the content of the application of the selected application type can be modified. For example, when "address change" is selected on the set application screen 535 and the "Modify" button is clicked, the address change screen 531 is displayed, and the content of the address change application can be modified.

[0134] When the approver who approves "address change" and "regular interval change" with the employee CD being "100001" operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display the list of applications in charge, for example, the unapproved list screen 536 shown in FIG. 27 provided by the workflow management device 100 is displayed. When the approver checks the checkboxes of the application records of the address change and regular interval change summarized on the unapproved list screen 536 and clicks the "Approve" button, the two applications are approved together, and when the "Reject" button is clicked, the two applications are rejected together.

[0135] Also, when an approver with an employee CD of "100001" clicks the "Details" button for the address change record on the Unapproved List Screen 536, as shown in Figure 27, an Application Details Screen 537 that displays the details of the application related to the clicked record is displayed. On the Application Details Screen 537, when the part of the "Regular Interval Change" character string is clicked, the details of the regular interval change application are displayed, and when the part of the "Check-Out Application" character string is clicked, the details of the check-out application are displayed. On the Application Details Screen 537, when the "Approve" part is clicked, the applications for address change and regular interval change are approved together, and when the "Reject" button is clicked, the applications for address change and regular interval change are rejected together. Also, when the approver performs an operation to display the approval route of the application, a Route Inquiry Screen 538 illustrated in Figure 27 showing the approval route and the approval status is displayed. With the Route Inquiry Screen 538, the approver can know the approval route of the application and the approval status.

[0136] On the Route Inquiry Screen 538, for the "Address Change" and "Regular Interval Change" which are batch approvals, at the position of "(1)", it is displayed that it is a batch approval with the background of the status and that it is the current step. Also, for the "Address Change" and "Check-Out Application" which are batch approvals, at the position of "(2)", the approver with an employee CD of "100002" is the approver with a step order of 2 for the address change, but is the approver with a step order of 1 for the check-out application. Regarding the address change, since the approver with a step order of 1 is in the approval process, at the position of "→" before the step of "(2)" for the check-out application, it is displayed that it is the current step. Also, regarding the approval status of the check-out application, it is displayed at the position of the step of "(2)" in accordance with the address change which is a batch approval.

[0137] After the approver with employee CD "100001" approves the applications for address change and regular period change, the approver who is the next approver for "address change" and has employee CD "100002" operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display the list of applications in charge. For example, the unapproved list screen 539 shown in FIG. 28 provided by the workflow management device 100 is displayed. When the approver checks the checkboxes of the records of the address change application and the move-out application summarized on the unapproved list screen 539 and clicks the "Approve" button, the two applications are approved together. When the "Reject" button is clicked, the two applications are rejected together.

[0138] Also, when the approver clicks the "Details" button of the address change record on the unapproved list screen 539, as shown in FIG. 28, the application details screen 540 that displays the details of the application related to the clicked record is displayed. On the application details screen 540, when the part of the "Move-out application" string is clicked, the details of the "Move-out application" are displayed. When the part of the "Regular period change" string is clicked, the details of the "Regular period change" application are displayed. On the application details screen 540, when the "Approve" part is clicked, the address change application and the move-out application are approved together. When the "Reject" button is clicked, the address change application and the move-out application are rejected together. Also, when the approver performs an operation to display the approval route of the application, the route inquiry screen 541 illustrated in FIG. 28 showing the approval route and the approval status is displayed. From the route inquiry screen 541, the approver can know the approval route of the application and the approval status.

[0139] On the route inquiry screen 541, the approver of "address change" and "move-out application" with employee CD "100002" for batch approval is the approver with step order 2 for address change, but the approver with step order 1 for the move-out application. Since the approver with step order 1 for the address change has approved, it is displayed that the current step is at the position of "(2)" for both the address change and the move-out application.

[0140] (Pattern (5)) Next, a processing example will be described for the case where the routes of a plurality of grouped applications differ halfway through and the same approver makes the approval decision at the end. In this processing example, it is assumed that the contents of the application type master 106c, the application set master 106a, and the application set member master 106b are as shown in FIG. 29 before the application of the application set. Also, regarding the approval route of the budget application according to this processing example, the route is applicant → employee with employee CD "100001" (no collective approval) → employee with employee CD "100002" (no collective approval) → employee with employee CD "100003" (with collective approval). Regarding the approval route of the purchase application, the route is assumed to be applicant → employee with employee CD "100004" (no collective approval) → employee with employee CD "100003" (with collective approval). Note that in each master shown in FIG. 29, illustrations of records and columns not used in the description of the processing example are omitted.

[0141] FIG. 30 is a diagram showing an example of a screen displayed when a budget application is made and data created based on the screen. When an applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for a budget application, the budget application screen 542 shown in FIG. 30 provided by the workflow management device 100 is displayed on the terminal device 400A. The applicant inputs each item related to the budget application on this budget application screen 542. When the applicant makes a budget application as a set with a purchase application, the applicant checks the "Apply as a set" checkbox and clicks the "Register" button. When the applicant clicks the "Register" button, as shown in FIG. 30, a set selection screen 543 for selecting an application set name including the budget application to be applied as the application type is displayed on the terminal device 400A.

[0142] Here, when the applicant selects "Budget + Purchase" on the set selection screen 543 and clicks the "Apply" button, the workflow management device 100 creates, as data related to this application, the project data 106j, project step data 106k, project step approver data 106l, project set data 106h, and project set member data 106i shown in FIG. 30. Here, since the summary application availability of the application set master 106a is "none", in the project set member data 106i, the "Status" column of the record corresponding to the budget application becomes "Applied". In the project set data 106h, a set key for uniquely identifying the application set is stored in the set key column, the project set name entered on the set selection screen 543 is stored in the "Project Set Name" column, and the application set CD corresponding to "Budget + Purchase" is stored in the set CD column.

[0143] FIG. 31 is a diagram showing an example of a screen displayed when making a purchase application that is set with a budget application and data created based on the screen. When the applicant operates the terminal device 400A to access the workflow management device 100 and performs an operation for a purchase application, on the terminal device 400A, the purchase application screen 544 shown in FIG. 31 provided by the workflow management device 100 is displayed. The applicant enters each item related to the purchase application on this purchase application screen 544. When the applicant makes a purchase application in combination with a budget application, the applicant checks the "Make a set application" checkbox and clicks the "Register" button. When the applicant clicks the "Register" button, as shown in FIG. 31, an application set list screen 545 including the projects of the purchase application to be registered is displayed on the terminal device 400A.

[0144] Here, when the applicant selects the "Budget + Purchase" application set on the application set list screen 545, the purchase application is completed. Here, the budget application and the purchase application are complete, and the workflow management device 100 also starts the workflow of the purchase application. Also, when the application of the purchase application is completed, the workflow management device 100 updates the project data 106j, the project step data 106k, the project step approver data 106l, the project set data 106h, and the project set member data 106i as shown in FIG. 31.

[0145] When an approver with an employee CD of "100001" operates the terminal device 100B to log in to the workflow management device 100 and performs an operation to display a list of applications in charge, for example, an unapproved list screen 546 which is a list of unapproved applications shown in FIG. 32 provided by the workflow management device 100 is displayed. Here, when the approver checks the checkbox of the record of the budget application and clicks the "Approve" button, the budget application is approved, and when the "Reject" button is clicked, the budget application is rejected.

[0146] Also, when an approver with an employee CD of "100001" clicks the "Details" button of the budget application record on the unapproved list screen 546, an application details screen 547 that displays the details of the application related to the clicked record is displayed as shown in FIG. 32. On this application details screen 547, when the part of the "Purchase Application" character string is clicked, the details of the purchase application are displayed. On the application details screen 547, when the "Approve" part is clicked, the budget application is approved, and when the "Reject" button is clicked, the budget application is rejected.

[0147] In addition, when the approver performs an operation to display the approval route of the application, for example, a route inquiry screen 548 illustrated in FIG. 32 showing the approval route and the approval status is displayed. With the route inquiry screen 548, the approver can know the approval route of the application and the approval status.

[0148] On the route inquiry screen 548, the step order of "budget application" step 1 and the step order of "purchase application" step 1 are not collective approvals. The approver with step order 1 in the "budget application" has an employee CD of "100001", and the approver with step order 1 in the "purchase application" has an employee CD of "100004", which is different. Therefore, at the step position of "(1)", the current step is displayed separately for "budget application" and "purchase application".

[0149] Also, after the approver with an employee CD of "100001" approves the budget application and performs an operation to display the approval route, for example, the route inquiry screen 549 illustrated in FIG. 32 is displayed. According to the route inquiry screen 549, it can be known that the budget application is at the second step and the purchase application is at the first step.

[0150] On the route inquiry screen 549, the step order of "budget application" step 2 and the step order of "purchase application" step 1 are not collective approvals. The approver with step order 2 in the "budget application" has an employee CD of "100002", and the approver with step order 1 in the "purchase application" has an employee CD of "100004", which is different. Therefore, for the "budget application", the current step is displayed at the step position of "(2)", and the approval status of the purchase application with step order 2 is not displayed at the position of "(2)". On the other hand, the final steps of the approvals for "budget application" and "purchase application" are collective approvals, and the employee CD of the approver is the same as "100003". Therefore, the approval status of the purchase application with step order 2 is displayed at the position of "(3)".

[0151] (Conditions for the workflow to proceed to the approver) Supplementing the conditions for the workflow to proceed to the approver of the application workflow, when the collective approval availability of the case step data 106k is "none", the state of the "start" step of the application satisfies the conditions described above as processed, and for the steps before the approver's step, when the approval status of the case step approver data 106l is all "approved", the workflow proceeds.

[0152] Also, when the approval status of the summary approval of the case step data 106k is "Yes", all applications in the case set meet the condition that the status of the "start" step is the above-mentioned processed status, the application set is finalized, and the approval status of the case step approver data 206l of the steps before the summary approval step for all applications with the status of "applied" included in the case set member data 106i is all "approved", the workflow proceeds.

[0153] ("Set to Finalize" button, conditions for the "Route for Approval" button to be clickable) To supplement the conditions for the "Set to Finalize" button and the "Route for Approval" button displayed on the screen to be clickable, when the status of all case set member data 106i with the mandatory flag of the application set member master 106b being "mandatory" is all "applied" or "before application", and before the application set is finalized, these buttons are clickable. When the summary application flag of the application set master 106a is "Yes", regardless of the automatic application flag, the button text is "Route for Approval", and for the rest, the button text is "Set to Finalize".

[0154] (Conditions for the application set to be finalized) To supplement the conditions for the application set to be finalized, the application set is finalized in any of the following cases. Specifically, when the summary application flag of the application set master 106a is "Yes", the automatic application flag is "Yes", and the status of all case set member data 106i in the set where the multiple ticket issuance availability of the application set member master 106b is all "not available" is all "applied", the application set is finalized. Also, when the above-mentioned "Set to Finalize" button or "Route for Approval" button is clicked, the application set is finalized.

[0155] After the application set is finalized, if any application is withdrawn by the applicant or rejected by the approver, the finalized application set will be cleared. Note that when the application set is finalized, the status column of the case data 106j is updated from "Before Application" to "During Application". Also, when the application set is finalized, the status column of the case set member data is updated from "Before Application" to "Applied", and from "Unprocessed" to "Discarded".

[0156] (Supplementary Explanation of Status Display) Regarding the display of the approval route and approval status, for supplementary information, in the "Previous" step of the approval route, the status display becomes "Processed" when there is a consolidated application in the application set master 106a and the "Status" of the case set member data 106i is "Before Application" or "Applied".

[0157] In the "Start" step of the approval route, the status display becomes "Unprocessed" when there is a consolidated application in the application set master 106a, the application set has not been finalized after the application is registered, or when the "Status" of the case data 106j is "Before Application" and the "Status" of the case set member data 106i is "Applied".

[0158] In the "Start" step of the approval route, the status display becomes "Processed" when there is no consolidated application in the application set master 106a when the application is registered, when there is a consolidated application in the application set master 106a and the application set is finalized after the application is registered, or when the "Status" of the case data 106j is "During Application" and the "Status" of the case set member data 106i is "Applied".

[0159] It is possible to determine whether the application set is finalized by checking the "Status" column of the case set member data 106i. If all "Status" values are "Applied", it is determined that the application set is finalized.

[0160] (Reference to Application Set Master and Application Set Member Master) When referring to the application set master 106a, refer to the application set master 106a on the condition of the set CD included in the case set data 106h, and refer to the set name, whether there is a consolidated application, whether there is an automatic application, etc. as necessary. Also, when referring to the application set member master 106b, refer to the application set member master 106b on the condition of the set CD included in the case set data 106h, and refer to the mandatory flag, whether multiple invoicing is possible, etc.

[0161] (Application Rejection) Next, a processing example when an application is rejected will be described. FIG. 33 is a diagram for explaining the processing when an application is rejected. In FIG. 33, A to F represent approvers. FIG. 33(a) shows the state before approver E rejects cases (1) to (3) which are the cases included in the case set combining cases (1) to (5).

[0162] If approver E rejects the applications for cases (1) to (3) and the rejection destination type in the application set master 106a is pre-approval, the workflow management device 100 changes the approval state to the state shown in FIG. 33(b). Specifically, the approval steps for cases (1) to (3) return to the step one step before the step of the person who rejected them. Note that if the returned destination is consolidated approval, the cases included in that consolidated approval also return to the consolidated approval step together. For example, since case (2) returns to approver B, case (3) also returns to approver B.

[0163] Also, for case (4) for which approver E does not perform consolidated approval, since the approval steps of cases (2) and (3) included together with case (4) in the consolidated approval while the approval step returns to approver B due to the application rejection have the same approver B and have been processed by approver B, case (4) will also be dragged by the rejection of cases (2) and (3) and the approver will change from approver F to approver B.

[0164] When the approver E rejects the applications of cases (1) to (3) and the rejection destination type in the application set master 106a is the applicant, the workflow management device 100 sets the approval status to the state shown in FIG. 33(c). For the cases in the case set that are before the final approval, the steps of the workflow all return to the applicant. Note that for case (5) approved by the final approver, it does not return to the applicant. When the applicant resubmits the returned application, in the route inquiry screen displayed by the operation of the approver in the step of collective approval, the cases that have been finally approved are displayed as related cases.

[0165] Note that when the rejection destination type in the application set master 106a is rejection destination selection, the approval workflow returns to one step before the step of the person who rejected it or returns to the applicant, and the approver who rejected it selects.

[0166] FIG. 34 is a diagram for explaining the processing when a pull-up rejection is performed to replace the approver of the current step during the approval process by the authority of the subsequent approver of the approver of the current step. In FIG. 34, A to G represent approvers. FIG. 34(a) shows the state before the subsequent approver G of the approvers D, E, and F, who are the approvers of the current step, performs a pull-up rejection on cases (2) to (4) that are the targets of collective approval for a case set including cases (1) to (5).

[0167] When the approver G performs a pull-up rejection on the application and the rejection destination type in the application set master 106a is pre-approval, the workflow management device 100 sets the approval status to the state shown in FIG. 34(b). Specifically, the workflows of cases (2) to (4) do not return to the approver G who performed the pull-up rejection, but return to one step before the current step approvers D, E, and F. Note that if the returned destination is collective approval, the cases included in that collective approval also return to the step of collective approval together. For example, since case (4) returns to approver A, the workflows of cases (1) to (3) also return to the step of approver A.

[0168] When the approver G rejects the application and the rejection destination type in the application set master 106a is the applicant, the workflow management device 100 sets the approval status to the state shown in FIG. 34(c), and all the workflow steps of the cases before the final approval in the cases included in the case set return to the applicant. Note that for the cases approved by the final approver, the workflow steps do not return to the applicant. When the applicant resubmits the returned application, in the route inquiry screen displayed by the operation of the approver in the collective approval step, the cases that have been finally approved are displayed as related cases.

[0169] (Return to Applicant) Next, a processing example when returning the application to the applicant will be described. FIG. 35 is a diagram for explaining the processing when the applicant returns the application. In FIG. 35, A to E represent approvers. FIG. 35(a) shows the state before the applicant returns the application for the case set combining cases (1) to (4). When the applicant returns the application, the workflow management device 100 returns the workflow steps of cases (1) to (3) being approved by approver D to the applicant for resubmission or abandonment. Note that case (4) that has been approved by the final approver A will not return to the applicant because it has been approved.

[0170] (Return to Approver) Next, a processing example when the approver withdraws the application will be described. FIG. 36 is a diagram for explaining the process when the approver withdraws the application. In FIG. 36, A to E represent approvers. FIG. 36(a) shows the state before approvers A to C withdraw the application for the case set combining cases (1) to (4). For case (1) being approved by approver D, when approver C withdraws the application, as shown in FIG. 36(b), the workflow management device 100 returns the steps of the workflow of case (1) to approver C. Also, for the workflows of case (1) and case (2) of approver D grouped in the collective approval step until returning to the withdrawal destination, with case (1) being withdrawn, it is set to the state of waiting for approval by approver C and waits at the position of "→" in front of approver D. Also, for case (2) or (3), when approver B withdraws the application, as shown in FIG. 36(c), the workflow management device 100 returns the steps of the workflows of case (2) and case (3) to approver B. Also, for the workflow of case (1), with case (2) grouped with case (1) in the collective approval step until returning to the withdrawal destination being withdrawn, it is set to the state of waiting for approval by approver B and waits at the position of "→" in front of approver D. Also, for cases (1) to (3), when approver A withdraws the application, as shown in FIG. 36(d), the workflow management device 100 returns the steps of the workflows of cases (1) to (3) to approver A.

[0171] Note that for an application where the "collective application flag" in the application set master 106a is "yes" and the status column in the case set member data 106i is "before application", the application can be modified without withdrawing the application.

[0172] [4. Effects of the Embodiment] According to the workflow management device 100 of the embodiment, a plurality of grouped applications are displayed to the approver, and the approver can collectively approve or reject them. Therefore, the approver can efficiently process a plurality of grouped applications, reducing the human burden.

[0173] In addition, according to the workflow management device 100, since it is possible to set the cases to be grouped and the approvers who will approve them collectively, it is possible to efficiently advance the approval workflow according to the application.

[0174] Also, in a plurality of grouped applications, the approval route may differ depending on the application. However, according to the workflow management device 100, since a plurality of applications are grouped and the approver can perform approval / rejection after the approval steps are aligned, it is possible to efficiently advance the approval workflow.

[0175] In addition, according to the workflow management device 100, the approver can confirm the approval status of a plurality of grouped application cases through the route inquiry screen.

[0176] Also, when a plurality of related application cases with different contents and the same approver are not grouped, if the application cases are sent to the approver through individual workflows, the approver may not know which application cases are related, and there is a risk that the approver cannot make a correct judgment on the application. However, according to the workflow management device 100, since the workflows of a plurality of related application cases with different contents and the same approver are collectively advanced to the approver, the approver can correctly judge the application cases.

[0177] Also, when a plurality of related application cases with different contents and the same approver are not grouped, if some of the application cases are withdrawn, other related application cases may not be withdrawn. However, when an application case is withdrawn, other application cases are also withdrawn, so that the approver can correctly judge the application cases for the withdrawn application cases.

[0178] [5. Contribution to the United Nations' Sustainable Development Goals (SDGs)] According to the present embodiment, since it is possible to contribute to improving business efficiency and making appropriate management decisions for the enterprise, it is possible to contribute to Goals 8 and 9 of the SDGs.

[0179] In addition, according to the present embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitalization, and thus it is possible to contribute to SDGs Goals 12, 13, and 15.

[0180] In addition, according to the present embodiment, it is possible to contribute to strengthening control and governance, and thus it is possible to contribute to SDGs Goal 16.

[0181] [6. Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the embodiments described above.

[0182] For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0183] In addition, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings can be arbitrarily changed unless otherwise specified.

[0184] In addition, regarding the workflow management device 100, each illustrated component is a functional concept, and it is not necessarily physically configured as illustrated.

[0185] For example, regarding the processing functions provided by the workflow management device 100, particularly each processing function performed by the control unit 102, all or any part thereof may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the workflow management device 100 to execute the processing described in the present embodiment, and is mechanically read by the workflow management device 100 as necessary. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes the control unit 102 in cooperation with the CPU.

[0186] Further, this computer program may be stored in an application program server connected to the workflow management device 100 via an arbitrary network, and all or part of it can be downloaded as necessary.

[0187] Also, a program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0188] Also, the "program" is a data processing method described in any language or description method, and is not limited to a form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributedly configured as a plurality of modules or libraries, or those that achieve their functions in cooperation with other separate programs typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0189] The various databases and the like stored in the storage unit 106 are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0190] Further, the workflow management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the workflow management device 100 may be realized by installing software (including programs or data, etc.) that realizes the processing described in this embodiment in the information processing device.

[0191] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or function additions. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0192] The present invention is useful in a workflow system used within an organization such as a company.

Explanation of Signs

[0193] 100 Workflow management device 102 Control unit 102a Acquisition unit 102b Display control unit 102c Application processing unit 102d Setting unit 104 Communication interface unit 106 Storage unit 106a Application set master 106b Application set member master 106c Application type master 106d Application set approval route assignment master 106e Approval route master 106f Approval route assignment master 106g Approval route step master 106h Project set data 106i Project set member data 106j Project data 106k case step data 106l case step approver data 108 input / output interface section 112 input device (keyboard) 114 output device (monitor) 200 server 300 network 400A, 400B terminal devices 501 maintenance screen 502 application set creation screen 503 application set editing screen 504 approval route assignment screen 505, 542 budget application screen 506, 515, 525, 532, 543 set selection screen 507, 514 order registration screen 508, 517, 527, 533, 545 application set list screen 509, 521, 528, 536, 539, 546 unapproved list screen 510, 522, 529, 537, 540, 547 application details screen 511, 523, 530, 538, 541, 548, 549 route inquiry screen 512, 513 route display 516 application menu screen 518, 519, 520, 534, 535 set application screen 524 dispatch registration screen 526 account registration screen 531 address change screen 544 purchase application screen

Claims

1. A workflow management device including a control unit, wherein the control unit has an acquisition means for acquiring data representing a case set obtained by grouping a plurality of application cases, a display control means for controlling the screen display of the plurality of application cases included in the case set represented by the data, an application processing means for collectively approving or rejecting the plurality of displayed application cases, a setting means for setting the application cases to be included in the case set, and is characterized in that the application processing means advances the approval workflow to the next approver after all the application cases to be collectively approved have been approved. A workflow management device.

2. The acquisition means acquires data of the case set including at least one application case having a different approval route, the display control means controls the display of the approval route of each of the application cases included in the case set, the application processing means approves or rejects the application cases included in the case set, and the setting means sets the application cases to be included in the case set to include at least one application case having a different approval route. The workflow management device according to claim 1.

3. The setting means sets an approver who collectively approves or rejects the plurality of application cases included in the case set. The workflow management device according to claim 1 or 2.

4. The setting means sets, for the plurality of application cases included in the case set, whether to start the approval workflow every time an application is made or to start the approval workflow after all applications are complete. The workflow management device according to any one of claims 1 to 3.

5. The application processing means can modify the application content of the application case until the approval workflow of the application case is started. The workflow management device according to any one of claims 1 to 4.

6. When the application processing means advances the approval workflow to the approver who collectively approves the plurality of application cases to be collectively approved, each of the application cases to be collectively approved is approved by the approver who approves the application case before the said approver, and then the approval workflow is advanced to the approver who collectively approves. The workflow management device according to any one of claims 1 to 5.

7. The display control means controls the display of the approval status for each of the plurality of application cases. ​ ​ ​ ​ ​ The workflow management device according to any one of claims 1 to 6.

8. When the application processing means rejects or returns the application case, according to the rejected or returned application case, it changes the approval status of other application cases. The workflow management device according to any one of claims 1 to 7.

9. When the application processing means retreats the approval workflow of the application from the approver in approval due to rejection or return of the application case, if the application case is collectively applied or approved while retreating to the applicant or approver at the retreat destination, according to the application case included in the collectively applied or collectively approved application case, it changes the scope of changing the approval status in the uncollected application cases. The workflow management device according to claim 8.

10. A workflow management method executed by an information processing device including a control unit, executed by the control unit, an acquisition step of acquiring data representing a case set obtained by aggregating a plurality of application cases, a display control step of controlling the screen display of the plurality of application cases included in the case set represented by the data, an application processing step of collectively approving or rejecting the plurality of displayed application cases, a setting step of setting the application cases to be included in the case set, comprising, wherein the application processing step is characterized in that the approval workflow proceeds to the next approver after all of the application cases approved collectively are approved.

11. A program for causing an information processing device including a control unit to execute, for execution by the control unit, an acquisition step of acquiring data representing a case set obtained by aggregating a plurality of application cases, a display control step of controlling the screen display of the plurality of application cases included in the case set represented by the data, an application processing step of collectively approving or rejecting the plurality of displayed application cases, a setting step of setting the application cases to be included in the case set, including, wherein the application processing step is a program for proceeding the approval workflow to the next approver after all of the application cases approved collectively are approved.

Images