Management device and management system

Abstract

Provided are a management device and a management system capable of appropriately managing a workflow. The management device comprises: a creation unit that creates a workflow in which approval processing can be performed by one or a plurality of approvers that have been set; a storage unit that stores the created workflow; an update unit that updates a mode of the workflow in accordance with processing performed with respect to the workflow; a display unit that displays an approval screen for receiving an operation to approve the workflow; and an acquisition unit that acquires identification information of a viewer who is viewing the approval screen. The display unit displays the workflow so that a plurality of users including an applicant who created the workflow and the approvers are able to view the workflow as viewers, and changes a type of a button in an active state that can be operated on the approval screen on the basis of a combination of the current mode of the workflow and the identification information of the viewer.

Description

Management device and management system

[0001] The present disclosure relates to a workflow management device and management system.

[0002] Japanese Patent Application Laid-Open No. 2006-124493 discloses a workflow system in which notifications requesting payment are sent to multiple responsible parties in sequence, enabling electronic documents to be circulated efficiently.

[0003] Japanese Patent Application Publication No. 2004-021415

[0004] However, in the workflow system described in Patent Document 1, there is a risk that only the approver who has been requested to make the payment can check the workflow. On the other hand, if anyone can check the workflow, there is a risk that an inappropriate user may approve the workflow.

[0005] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to provide a management device and a management system that can appropriately manage a workflow.

[0006] The management device according to the present disclosure includes a creation unit that creates a workflow that can be approved by one or more set approvers, a storage unit that stores the created workflow, an update unit that updates the mode of the workflow according to the processing performed on the workflow, a display unit that displays an approval screen that accepts operations to approve the workflow, and an acquisition unit that acquires identification information of a viewer viewing the approval screen, and the display unit displays the workflow so that multiple users, including the applicant who created the workflow and the approver, can view it as viewers, and changes the type of active button that can be operated on the approval screen based on a combination of the current mode of the workflow and the identification information of the viewer.

[0007] The management system according to the present disclosure includes a management device that manages workflows within a network that can be approved by one or more set approvers, and an authentication device that manages the network so that only users whose identification information has been authenticated can access the network. The management device has a creation unit that creates workflows, a storage unit that stores the created workflows, an update unit that updates the workflow mode according to the processing performed on the workflow, a display unit that displays an approval screen that accepts operations to approve the workflow, and an acquisition unit that acquires the identification information of viewers who are viewing the approval screen. The display unit displays the workflow so that multiple users, including the applicant who created the workflow and the approver, can view it as viewers, and changes the type of active button that can be operated on the approval screen based on a combination of the current mode of the workflow and the identification information of the viewer.

[0008] According to the present disclosure, the activation state of the button changes in the workflow depending on the workflow mode and the viewer, which allows for appropriate management of the workflow.

[0009] 1 is a diagram showing an overview of a network of a management system in embodiment 1. FIG. 2 is a functional block diagram of a management system in embodiment 1. FIG. 3 is a mode transition diagram of a workflow created in a management system in embodiment 1. FIG. 4 is an example of an interface screen displayed in a management system in embodiment 1. FIG. 5 is an example of an interface screen displayed in a management system in embodiment 1. FIG. 6 is an example of an interface screen displayed in a management system in embodiment 1. FIG. 7 is an example of an interface screen displayed in a management system in embodiment 1. FIG. 8 is a flowchart of operations when a workflow is created in a management system in embodiment 1. FIG. 9 is a flowchart of notification operations performed by a management system in embodiment 1. FIG. 10 is a flowchart of approval operations performed by a management system in embodiment 1. FIG. 11 is a hardware configuration diagram of a management device of a management system in embodiment 1.

[0010] The embodiments of the present disclosure will be described with reference to the accompanying drawings. In each drawing, the same or corresponding parts are designated by the same reference numerals. Duplicate descriptions of these parts will be appropriately simplified or omitted.

[0011] Embodiment 1 Fig. 1 is a diagram showing an outline of a network of a management system in embodiment 1. Fig. 2 is a functional block diagram of the management system in embodiment 1.

[0012] For example, the management system 1 is applied to the network of a company having an organizational structure as shown in Fig. 1. Specifically, this organizational structure includes a head office H where core functions are located, and a branch office B for the head office H. In addition to the communication network developed by the head office H including the branch office B, there is an independent communication network within the branch office B. Hereinafter, this independent communication network will also be referred to as the management network A.

[0013] The management system 1 includes an authentication device 2, a branch server 3, a core server 4, and a management device 10. The management system 1 is also accessible by individual terminals 5. For example, the individual terminals 5 are terminals individually owned by employees of the company or employees of affiliated companies of the company. The management system 1 may include the individual terminals 5.

[0014] The authentication device 2 is a security device that manages access from outside to inside the management network A. When the authentication device 2 authenticates the individual terminal 5, the individual terminal 5 becomes able to access devices inside the management network A. Unless authenticated, the individual terminal 5 cannot access the inside of the management network A.

[0015] The branch server 3 is installed in the branch B. The branch server 3 is managed within the management network A. For example, the branch server 3 has multiple storage areas set up according to the data stored therein. Each of the multiple storage areas has its own security setting, and can only be accessed by an individual terminal 5 that has been granted access rights.

[0016] The backbone server 4 is installed in the head office H. In this example, the backbone server 4 is managed outside the management network A. Note that at least some of the functions of the backbone server 4 may be managed within the management network A. For example, the backbone server 4 is provided with an information server that stores identification information, contact information, etc. of employees of the company and employees of affiliated companies of the company. In other words, the identification information of all users who may access the network of the management system 1 is stored in the backbone server 4.

[0017] The management device 10 is provided in the branch office B. The management device 10 is managed within the management network A. The management device 10 manages the workflow system operated within the branch office B.

[0018] In the workflow system, a workflow, which is message information, is approved in the system in the order of the approvers that have been set. The order of approvers is set as the workflow path when the workflow is created. When a certain approver approves a workflow, a notification is sent from the management device 10 to the approver set next in order after that approver, i.e., the next approver who is to approve the workflow. When the workflow is approved by all approvers, the workflow is completed. In this way, the workflow system replaces the application procedures within Branch B, which were previously carried out by approvers stamping documents, with message information in a virtual system.

[0019] In the following, as a specific application example of the workflow system, a workflow for granting access rights to one storage area of ​​the branch server 3 to a user of an individual terminal 5 will be described.

[0020] Access rights to the storage area are granted by the operation of an office automation administrator who handles digital-related tasks after obtaining approval from a person in an appropriate position. One or more approvers are set in this workflow. The multiple approvers may include the office automation administrator. The multiple approvers may also include another office automation administrator. For example, an office automation key person who is another office automation administrator is set as the first approver of the workflow and checks whether an appropriate route is set in the workflow.

[0021] An applicant who applies for a workflow and an approver who approves both perform access authentication to the management network A from their own individual terminal 5, and each accesses the workflow system of the management device 10. The applicant and approver view the interface screen of the workflow system provided by the management device 10 and perform operations such as applying for and approving a workflow.

[0022] 2, the authentication device 2 has as its functions a reception unit 21 and an authentication unit 22. The reception unit 21 receives information for authentication from the individual terminal 5. For example, identification information of the individual terminal 5 is transmitted from the individual terminal 5. The identification information includes information for identifying the user who owns the individual terminal 5, such as an employee number. The identification information may also include a password and an identifier of the individual terminal 5 itself.

[0023] Based on the received identification information, the authentication unit 22 authenticates the individual terminal 5 to access the managed network A. The authentication unit 22 manages the history of accesses made by the individual terminal 5 to devices within the managed network A in association with the identification information at the time of authentication. In other words, within the managed network A, the identification information of the user of the individual terminal 5 is always known.

[0024] For example, the branch server 3 has n storage areas set therein, namely, a first storage area 31-1, a second storage area 31-2, . . . , an n-th storage area 31-n.

[0025] The management device 10 includes, as its functions, a first DB unit 11, a second DB unit 12, a storage unit 13, an acquisition unit 14, a display unit 15, a creation unit 16, an update unit 17, a notification unit 18, and a management unit 19.

[0026] The first DB unit 11 is a database that stores identification information of multiple candidates who can become approvers. The first DB unit 11 stores information only about the candidates who can become approvers. The first DB unit 11 stores information about contact points for contacting the candidates in association with the identification information. For example, the contact point information is an email address assigned to the user.

[0027] The second DB unit 12 is a database that stores a list of additional information to be added to a workflow. For example, the additional information is information indicating the first storage area 31-1, the second storage area 31-2, ..., the n-th storage area 31-n of the branch server 3. The additional information may further include objects to be attached to the workflow.

[0028] The storage unit 13 stores information about workflows that have been created in the past. The storage unit 13 stores workflows that have just been created, completed workflows, etc. A completed workflow is one that has been approved by all approvers set on the route.

[0029] The acquisition unit 14 acquires the identification information of the user of the individual terminal 5 that has accessed the workflow system of the management device 10. For example, the acquisition unit 14 acquires the user identification information from the authentication unit 22.

[0030] The display unit 15 generates an interface screen for the workflow system and controls the displayed content. The interface screen includes a display screen that displays a list of workflows stored in the storage unit 13 and an approval screen that accepts operations for creating and approving workflows. The display screen and approval screen for the workflow can be viewed by multiple users, including the workflow applicant and approver. All of these multiple users are users who have been authenticated by the authentication unit 22 to access the inside of the management network A.

[0031] The display unit 15 changes the type of active button that can be operated on the approval screen based on a combination of the current workflow mode and the viewer's identification information. On the approval screen, the "Apply" button, "Approve" button, "Return" button, and "Withdraw" button are displayed in an active or inactive state. When any button is operated, that button is considered to be a process performed on the workflow. For example, when the "Approve" button is operated, the management device 10 considers that an approval process has been performed on the workflow.

[0032] The display unit 15 displays a management screen that can be viewed only by the specified user.

[0033] The creation unit 16 accepts an operation to create a workflow on the approval screen. When the approval screen is opened, the creation unit 16 associates the applicant's identification information acquired by the acquisition unit 14 with the workflow.

[0034] The update unit 17 updates the mode of the workflow in accordance with the process, such as application, approval, return, or withdrawal, performed on the workflow.

[0035] The notification unit 18 sends a notification to the next approver in the workflow path requesting approval. When the workflow is returned, the notification unit 18 notifies the applicant of this fact. When the workflow is completed, the notification unit 18 notifies the applicant of this fact.

[0036] The management unit 19 accepts, on the management screen, an operation to edit the information stored in the first DB unit 11 and the second DB unit 12. The management unit 19 edits the information stored in the first DB unit 11 or the second DB unit 12 based on the accepted editing operation.

[0037] Next, the workflow modes will be described. Fig. 3 is a diagram showing the transition of workflow modes created by the management system in embodiment 1. Figs. 4 to 8 show examples of interface screens displayed by the management system in embodiment 1.

[0038] A workflow includes route information, the applicant's identification information, the applicant's notification destination information, the approver's identification information, and additional information. The route information also includes information about the processes that have been performed up to that point. In other words, the route information is also used as historical information about the processes performed on the workflow. A mode is set for a workflow.

[0039] 3, in this example, "mode 0," "mode a," "mode b-1," "mode b-2," ... "mode b-n," and "mode c" are set in the workflow. For example, the update unit 17 updates the workflow by transitioning the mode based on the last process performed in the process history.

[0040] Mode 0 is the mode in which a workflow is being created and before the "Apply" button is pressed. The creation unit 16 creates a workflow in mode 0, which is the creation mode.

[0041] On the approval screen for a workflow in mode 0, if the identification information of the viewer matches the identification information of the applicant, the "Apply" button is displayed in an active state. In this case, the "Approve" button, "Return" button, and "Withdraw" button are displayed in an inactive state. Also, in this case, input fields for additional information, etc. are displayed in an active state where they can be entered. On the approval screen for a workflow in mode 0, if the identification information of the viewer does not match the identification information of the applicant, all buttons are displayed in an inactive state.

[0042] When the "Apply" button is pressed in mode 0, the system transitions to mode b, which is the approval mode. In mode b, the approver approves the workflow. There are as many modes b as there are approvers. If there are n approvers, n modes are set in mode b: mode b-1, mode b-2, ..., mode b-n. Each mode is associated one-to-one with the approver that has been set.

[0043] On the approval screen for a workflow in mode b, if the identification information of the viewer matches the identification information of the approver corresponding to the mode, the "Approve" button and the "Return" button are displayed in an active state. In this case, the "Apply" button and the "Withdraw" button are displayed in an inactive state. Also, in this case, the input field for "Reason for Return" is displayed in an active state. On the approval screen for a workflow in mode b, if the identification information of the viewer does not match the identification information of the corresponding approver, all buttons are displayed in an inactive state.

[0044] Mode b-1 is a mode associated with the first approver in the path. When the "Approve" button is pressed in mode b-1, the mode transitions to mode b-2. Mode b-2 is a mode associated with the second approver in the path. Modes b-3 and onward transition in the same way, and mode b-n, which corresponds to the last approver, is also called final approval mode b-f.

[0045] When the "Apply" button is pressed in final authentication modes bf, the system transitions to mode c. Mode c is a completion mode that indicates that the workflow application has been completed. On the workflow approval screen in mode c, all buttons are displayed in an inactive state, regardless of the viewer.

[0046] When the "Return" button is pressed in any of modes b-1 to bn, the mode transitions to mode a. Mode a is a correction mode in which the workflow is corrected.

[0047] On the approval screen for a workflow in mode a, if the identification information of the viewer matches the identification information of the applicant, the "Apply" button and "Withdraw" button are displayed in an active state. In this case, the "Approve" button and "Return" button are displayed in an inactive state. Also, in this case, input fields for additional information about the workflow, etc. are displayed in an active state so that they can be modified. On the approval screen for a workflow in mode a, if the identification information of the viewer does not match the identification information of the applicant, all buttons are displayed in an inactive state.

[0048] 4 shows an approval screen displaying a workflow in mode 0. The creation unit 16 creates a workflow in mode 0 by adding to the workflow the identification information of the applicant who opened this screen to create the workflow. In this example, the added identification information is employee number N. The applicant creates a workflow by entering content into each block of supplementary information on the approval screen and selecting from a pull-down menu.

[0049] In this example, a workflow is created that has input or selection fields for Block K and Block L as supplementary information. Block K is a field for entering the applicant's identification information and notification destination information. The applicant enters an email address as their notification destination. Block L allows the applicant to select the storage area to which they wish to grant access rights based on the information stored in the second DB unit 12.

[0050] In this example, a workflow is created that has a selection field for Block M, which is a field for setting route information. The "Application Department OA Key Person" is the first approver. The following "Approver 1," "Approver 2," "Approver 3," and "Approver 4" are the second to fifth possible approvers, respectively. The "Final Approver" is the last approver. Each approver can only be selected from multiple candidates stored in the first DB unit 11.

[0051] Each approver is selected from candidates displayed in a pull-down menu. The first DB unit 11 sets which candidate is displayed in which pull-down menu. Note that not all approvers n need to be selected. For example, only the "final approver" may be selected as the approver.

[0052] In this way, the identification information of the applicant is automatically added to the workflow. The order of approvers is added to the workflow as route information. The creation unit 16 may also add notification destination information for each approver to the workflow.

[0053] Figure 5 shows the application status screen after a workflow has been created. The interface screen includes an "Application Status" screen, which is one of the display screens, that sorts and displays in a list the workflows that are currently incomplete. The interface screen also includes a "Completion List" screen, which is one of the display screens, that sorts and displays in a list the workflows that have been completed. On the interface screen, the "Application / Approval" tab, which is an approval screen, the "Application Status" tab, which is a display screen, and the "Completion List" tab, which is a display screen, are selectable. For example, if there is a workflow that requires approval processing, a badge indicating this is also displayed on the "Application Status" tab.

[0054] 6 shows the approval screen viewed by Approver 1, the next approver. Of the buttons, active buttons are indicated by solid lines, and inactive buttons are indicated by dashed lines. The display unit 15 determines that the identification information of Approver 1, the viewer, matches the identification information of the next approver in the workflow. In this case, the display unit 15 displays the "Approve" button, the "Reject" button, and the input field for the rejection reason in an active state.

[0055] 7 shows an approval screen viewed by a user who is not the next approver. The display unit 15 determines that the identification information of the viewer does not match the identification information of the next approver in the workflow. In this case, the display unit 15 displays all buttons and input fields in an inactive state.

[0056] FIG. 8 is a management screen that displays information stored in the first DB unit 11. The "Candidate Information" tab corresponds to the information stored in the first DB unit 11. The "Additional Information" tab corresponds to the information stored in the second DB unit 12. The management screen displays the candidate's "name," "employee number" which is the candidate's identification information, and "email address" which is the notification destination for the candidate, in association with each other. In addition, information indicating which of the approvers can be set, such as "approval," "OA," or "management," is also associated with the candidate information.

[0057] Next, the operation of the management system will be described with reference to Figures 9 to 11. Figure 9 is a flowchart of the operation when a workflow is created in the management system in embodiment 1. Figure 10 is a flowchart of the notification operation performed by the management system in embodiment 1. Figure 11 is a flowchart of the approval operation performed by the management system in embodiment 1.

[0058] The flowchart of FIG. 9 begins when a user begins creating a workflow.

[0059] In step S001, the acquisition unit 14 acquires identification information of the applicant who is the user who will create the document.

[0060] Then, in step S002, the display unit 15 displays a workflow creation screen. The creation screen may be an approval screen for the workflow in mode 0. The creation unit 16 automatically adds the applicant's identification information acquired in step S001 to the workflow. The creation unit 16 accepts operations on the creation screen, such as input of the applicant's notification destination and selection of the approver.

[0061] Thereafter, in step S003, the applicant operates the "Apply" button to apply for the workflow. The creating unit 16 stores information about the applied workflow in the storage unit 13.

[0062] Thereafter, in step S004, the notification unit 18 notifies the first approver, who is the next approver.

[0063] Then, the operation of the flowchart ends.

[0064] The flowchart in Fig. 10 is an example of the operation when the notification unit 18 performs a notification. The flowchart in Fig. 10 starts when a flowchart is stored in the storage unit 13 or when the mode of the flowchart stored in the storage unit 13 is updated.

[0065] In step S101, the notification unit 18 identifies a user to send the notification to based on the mode of the workflow. If the workflow is mode b to n, the notification unit 18 identifies an approver associated with the mode as the user to send the notification. If the workflow is mode a, the notification unit 18 identifies the applicant as the user to send the notification. If the workflow is mode c, the notification unit 18 identifies the applicant as the user to send the notification.

[0066] Then, in step S102, the notification unit 18 sends a notification corresponding to the mode to the notification destination of the identified user. If the user sending the notification is the applicant, the notification unit 18 sends a notification that the work has been returned or completed to the notification destination of the applicant added to the workflow. If the user sending the notification is the approver, the notification unit 18 uses the identification information of the approver to extract the notification destination of the approver from the first DB unit 11. The notification unit 18 sends a notification requesting approval to the extracted notification destination. Note that if information about the approver's notification destination is added to the workflow, the notification unit 18 may send the notification to the added notification destination without extracting it from the first DB unit 11.

[0067] Then, the operation of the flowchart ends.

[0068] The flowchart in FIG. 11 starts when the approval screen of a workflow in approval mode is viewed by a viewer.

[0069] In step S201, the acquisition unit 14 acquires identification information of the viewer of the approval screen.

[0070] Thereafter, in step S202, the display unit 15 determines whether the identification information of the viewer matches the identification information of the next approver.

[0071] If the identification information of the viewer does not match the identification information of the next approver in step S202, the operation of step S203 is performed. In step S203, the display unit 15 displays an approval screen in which all buttons and input fields are inactive. Then, the operation of the flowchart ends.

[0072] In step S203, the display unit 15 may display an approval screen in which at least a portion of the workflow information is hidden. Even in this case, in step S203, the display unit 15 may display an approval screen in which all buttons and input fields are inactive for approvers other than the applicant and the next approver included in the route. In this way, the content displayed on the approval screen changes depending on the combination of the mode and the viewer's identification information.

[0073] In step S202, if the identification information of the viewer matches the identification information of the next approver, the operation of step S204 is performed. In step S204, the display unit 15 displays an approval screen in which the "Approve" button, the "Reject" button, and the input field for the reason for rejection are active.

[0074] Thereafter, in step S205, the display unit 15 determines whether the button operated on the approval screen of the workflow is "Approve" or "Return."

[0075] If it is determined in step S205 that the "Approve" button has been operated, the operation of step S206 is performed. In step S206, the update unit 17 determines whether or not the next approver exists in the route.

[0076] If it is determined in step S206 that a next approver exists, the operation of step S207 is performed. In step S207, the update unit 17 changes the workflow mode to the approval mode corresponding to the next approver. For example, if the next approver is the second approver, the update unit 17 updates the workflow to mode b-2.

[0077] If it is determined in step S206 that there is no next approver, the operation of step S208 is performed. In step S208, the update unit 17 changes the workflow mode to the completion mode.

[0078] If it is determined in step S205 that the "Return" button has been operated, the operation of step S209 is performed. In step S209, the update unit 17 updates the workflow to the correction mode.

[0079] After the operation of step S207, S208, or S209, in step S210, the notification unit 18 sends a notification corresponding to the current mode of the workflow.

[0080] Then, the operation of the flowchart ends.

[0081] According to the first embodiment described above, the management system 1 includes a management device 10. The management device 10 includes, as its functions, a creation unit 16, a storage unit 13, an update unit 17, a display unit 15, and an acquisition unit 14. The display unit 15 displays a workflow on an approval screen so that multiple users can view it as viewers. The display unit 15 changes the type of active, operable buttons on the approval screen based on a combination of the workflow mode and the viewer's identification information. Displaying the workflow in this manner allows even third parties other than the approver or applicant to confirm the content of the workflow, and enables control of the buttons that can be operated on the workflow for such third parties. As a result, the management device 10 can appropriately manage the workflow.

[0082] The management system 1 further includes an authentication device 2. The authentication device 2 manages users who can access the workflow system managed by the management device 10. The workflow can be viewed by third parties whose access has been authenticated. This improves security.

[0083] The management device 10 also includes a first DB unit 11, which is a database unit. The first DB unit 11 stores identification information for only multiple potential approver candidates. While the core server 4 stores identification information for all users, not just those who could potentially become approvers, the management device 10 has its own DB unit. By owning and managing a database with a sufficient amount of information at branch B and utilizing this database, server capacity can be reduced, the ease of operation of the management device 10 can be improved, and security can be enhanced. For example, by operating the management device 10, an office automation administrator at branch B can change information stored in the DB unit without obtaining approval from head office H. Furthermore, because the DB unit is stored within the management network A, security can be improved.

[0084] Note that the management device 10 may have the functionality of the authentication unit 22, rather than the authentication device 2. In the management device 10, the acquisition unit 14 acquires the identification information authenticated by the authentication unit 22. The creation unit 16 associates the identification information authenticated by the authentication unit 22 with the workflow as the applicant's identification information. That is, among the information associated with the workflow, the identification information entered to receive access authentication into the management device 10 is used as the applicant's identification information. Among the information associated with the workflow, the identification information stored in the DB unit is used as the approver's identification information. Therefore, there is no need to store information about users who could potentially become applicants in the DB information. Furthermore, there is no need for applicants to re-enter their identification information. Furthermore, because the applicant's identification information is authenticated information, security is guaranteed. In this way, server capacity can be reduced and security can be improved.

[0085] Next, an example of hardware constituting the management device 10 will be described with reference to Fig. 12. Fig. 12 is a hardware configuration diagram of the management device of the management system according to the first embodiment.

[0086] Each function of the management device 10 may be realized by a processing circuit. For example, the processing circuit may include at least one processor 100 a and at least one memory 100 b. For example, the processing circuit may include at least one dedicated hardware 200.

[0087] When the processing circuit includes at least one processor 100a and at least one memory 100b, the functions of the management device 10 are implemented by software, firmware, or a combination of software and firmware. At least one of the software and firmware is written as a program. At least one of the software and firmware is stored in the at least one memory 100b. The at least one processor 100a implements the functions of the management device 10 by reading and executing the program stored in the at least one memory 100b. The at least one processor 100a is also referred to as a central processing unit, processing unit, arithmetic unit, microprocessor, microcomputer, or DSP. For example, the at least one memory 100b may be a non-volatile or volatile semiconductor memory such as RAM, ROM, flash memory, EPROM, or EEPROM, a magnetic disk, a flexible disk, an optical disk, a compact disk, a minidisk, or a DVD.

[0088] When the processing circuit includes at least one dedicated hardware 200, the processing circuit may be realized, for example, as a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof. For example, each function of the management device 10 may be realized by a processing circuit. For example, each function of the management device 10 may be realized collectively by a processing circuit.

[0089] Some of the functions of the management device 10 may be implemented by dedicated hardware 200, and other functions may be implemented by software or firmware. For example, the function of the notification unit 18 may be implemented by a processing circuit as the dedicated hardware 200, and functions other than the function of the notification unit 18 may be implemented by at least one processor 100a reading and executing a program stored in at least one memory 100b.

[0090] In this way, the processing circuitry realizes the functions of the management device 10 using hardware 200, software, firmware, or a combination of these.

[0091] Although not shown, the functions of the authentication device 2, branch server 3, and backbone server 4 are also realized by processing circuits equivalent to the processing circuits that realize the functions of the management device 10.

[0092] At least some of the functions of the management device 10 may be implemented on a cloud server. In this case, the processing circuit is composed of multiple partial circuits. The multiple partial processing circuits are provided in multiple devices that make up the cloud server. The multiple devices that make up the cloud server may each be provided in a different building.

[0093] As described above, the management system according to the present disclosure can be used to manage a workflow system.

[0094] DESCRIPTION OF SYMBOLS 1 Management system, 2 Authentication device, 3 Branch server, 4 Core server, 5 Individual terminal, 10 Management device, 11 First DB unit, 12 Second DB unit, 13 Storage unit, 14 Acquisition unit, 15 Display unit, 16 Creation unit, 17 Update unit, 18 Notification unit, 19 Management unit, 21 Reception unit, 22 Authentication unit, 31-1 First storage area, 31-2 Second storage area, 31-n nth storage area, 100a Processor, 100b Memory, 200 Hardware, A Management network, B Branch, H Head office, N Employee number

Claims

1. A management device comprising: a creation unit that creates a workflow that can be approved by one or more set approvers; a storage unit that stores the created workflow; an update unit that updates the mode of the workflow in accordance with processing performed on the workflow; a display unit that displays an approval screen that accepts operations to approve the workflow; and an acquisition unit that acquires identification information of a viewer viewing the approval screen, wherein the display unit displays the workflow so that multiple users, including the applicant who created the workflow and the approver, can view it as the viewers, and changes the type of active button that can be operated on the approval screen based on a combination of the current mode of the workflow and the identification information of the viewer.

2. The management device of claim 1, wherein the update unit updates the workflow to an approval mode associated with the next approver when approval from the next approver is required after the workflow has been created or after the workflow has been approved by the approver, and the display unit displays an approval button for approval in an active state on the approval screen for the workflow only when the mode of the workflow is the approval mode and the identification information of the viewer matches the identification information of the next approver.

3. The management device described in claim 1 or claim 2, wherein the update unit updates the workflow to edit mode when the approver performs a process to return the workflow, and the display unit displays the workflow in a state where the content can be edited on the approval screen of the workflow only when the workflow mode is the edit mode and the viewer's identification information matches the applicant's identification information.

4. The management device according to claim 3, wherein the display unit displays a withdraw button for withdrawing the workflow on the approval screen in an active state only when the workflow mode is the correction mode and the identification information of the viewer matches the identification information of the applicant.

5. A management device as described in any one of claims 1 to 4, further comprising a DB unit that stores identification information of multiple candidates who can become the approver, wherein the DB unit stores identification information of only the multiple candidates, and the display unit changes the type of button that is active on the approval screen by determining whether the identification information of the viewer matches the identification information stored in the DB unit.

6. The management device of claim 5, further comprising an authentication unit that manages the approval screen so that only users whose identification information has been authenticated can access the approval screen, wherein the acquisition unit acquires the applicant's identification information based on the identification information authenticated by the authentication unit, and the creation unit associates the applicant's identification information acquired by the acquisition unit with the workflow.

7. A management system comprising: a management device that manages workflows within a network that can be approved by one or more set approvers; and an authentication device that manages the network so that only users whose identification information has been authenticated can access the network, wherein the management device has: a creation unit that creates the workflow; a storage unit that stores the created workflow; an update unit that updates the mode of the workflow in accordance with processing performed on the workflow; a display unit that displays an approval screen that accepts operations to approve the workflow; and an acquisition unit that acquires identification information of viewers viewing the approval screen, wherein the display unit displays the workflow so that multiple users including the applicant who created the workflow and the approver can view it as the viewers, and changes the type of active button that can be operated on the approval screen based on a combination of the current mode of the workflow and the identification information of the viewer.

8. The management system of claim 7, further comprising: a DB unit that stores identification information of multiple candidates who can become the approver; the DB unit stores identification information of only the multiple candidates; the acquisition unit acquires identification information of the applicant based on identification information authenticated by the authentication device; the creation unit associates the identification information of the applicant acquired by the acquisition unit with the workflow; and the display unit changes the type of button that is active on the approval screen by determining whether the identification information of the viewer matches the identification information stored in the DB unit.

Images