Management device and management system

Abstract

Provided are a management device and a management system that can appropriately manage a workflow. The management device 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 for receiving an operation for approving the workflow, and an acquisition unit that acquires the identification information of a viewer who is viewing the approval screen. The display unit displays the workflow so that a plurality of users including the applicant and approver who created the workflow can view the workflow as viewers, and changes the types of buttons in an active state that can be operated on the approval screen based on the combination of the current mode of the workflow and the identification information of the viewer.

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses a workflow system. In the workflow system, notifications for sequentially requesting settlements are sent to a plurality of persons in charge. Electronic documents can be efficiently circulated.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

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

[0005] The present disclosure has been made to solve the above problems. An object of the present disclosure is to provide a management device and a management system capable of appropriately managing a workflow.

Means for Solving the Problems

[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 for receiving an operation for approving the workflow, and an acquisition unit that acquires identification information of a viewer who is viewing the approval screen. The update unit updates the workflow to the approval mode associated with the next approver after the workflow is created or after the workflow is approved by any of a plurality of approvers, when the approval of the next approver is required. The display unit displays so that a plurality of users including the applicant who created the workflow and One or more the approver can view the workflow as viewers, and based on the combination of the current mode of the workflow and the identification information of the viewer, Displays the approval button for approval in the active state on the approval screen of the workflow only when the mode of one or more workflows is the approval mode and the identification information of the viewer matches the identification information of the next approver. . Further, 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 process performed on the workflow, a display unit that displays an approval screen for receiving an operation for approving the workflow, and an acquisition unit that acquires the identification information of the viewer viewing the approval screen. When the process of rejecting the workflow is performed by any one of one approver or a plurality of approvers, the update unit updates the workflow to the modification mode, and the display unit displays the workflow so that a plurality of users including the applicant who created the workflow and one or more approvers can view the workflow as viewers. Based on the combination of the current mode of the workflow and the identification information of the viewer, the workflow is displayed in a state where the content can be modified on the approval screen of the workflow only when the mode of the workflow is the modification mode and the identification information of the viewer matches the identification information of the applicant.

[0007] The management system according to the present disclosure includes, inside a network, a management device that manages a workflow that can be approved by one or more set approvers, and an authentication device that manages so that only a user who has authenticated identification information can access the inside of the network. The management device has a creation unit that creates a workflow, 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 for receiving an operation for approving the workflow, and an acquisition unit that acquires identification information of a viewer who is viewing the approval screen. The update unit updates the workflow to the approval mode associated with the next approver after the workflow is created or after the workflow is approved by any of a plurality of approvers, when the approval of the next approver is required. The display unit displays so that a plurality of users including the applicant who created the workflow and One or more the approver can view the workflow as viewers, and based on the combination of the current mode of the workflow and the identification information of the viewer, Displays the approval button for approval in the active state on the approval screen of the workflow only when the mode of one or more workflows is the approval mode and the identification information of the viewer matches the identification information of the next approver. . In addition, the management system according to the present disclosure includes a management device that manages a workflow that can be approved by one or more set approvers within a network, and an authentication device that manages access to the inside of the network so that only a user who has authenticated identification information can access it. The management device includes a creation unit that creates a workflow, 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 for receiving an operation for approving the workflow, and an acquisition unit that acquires the identification information of a viewer who is viewing the approval screen. The update unit updates the workflow to a modification mode when a process of rejecting the workflow is performed by any one of one approver or a plurality of approvers. The display unit displays the workflow so that a plurality of users including the applicant who created the workflow and one or more approvers can view the workflow as viewers. Based on the combination of the current mode of the workflow and the identification information of the viewer, only when the mode of the workflow is the modification mode and the identification information of the viewer matches the identification information of the applicant, the workflow is displayed in a state where the content can be modified on the approval screen of the workflow.

Advantages of the Invention

[0008] According to the present disclosure, the active state of the button in the workflow changes depending on the mode of the workflow and the viewer. Therefore, the workflow can be appropriately managed.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Modes for Carrying Out the Invention

[0010] Modes for carrying out the present disclosure will be described with reference to the accompanying drawings. In each figure, the same or corresponding parts are denoted by the same reference numerals. Redundant descriptions of such parts will be appropriately simplified or omitted.

[0011] Embodiment 1. FIG. 1 is a diagram showing an overview of the network of the 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 in the organizational form as shown in FIG. 1. Specifically, the organizational form includes a head office H provided with core functions and branch offices B for the head office H. Separate from the communication network developed by the head office H including the branch offices B, there is a unique communication network within the branch offices B. Hereinafter, the unique communication network is also 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. Further, an individual terminal 5 can access the management system 1. For example, the individual terminal 5 is a terminal individually owned by an employee of the company or an employee of an affiliated company of the company. The management system 1 may include the individual terminal 5.

[0014] The authentication device 2 is a security device that manages access from the outside to the inside of the management network A. By the authentication device 2 authenticating the individual terminal 5, the individual terminal 5 can access the 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 provided in the branch office B. The branch server 3 is managed inside the management network A. For example, a plurality of storage areas are set in the branch server 3 according to the stored data. Each of the plurality of storage areas has a security setting, and can only be accessed by the individual terminal 5 to which the access right is granted.

[0016] The backbone server 4 is installed at the head office H. In this example, the backbone server 4 is managed outside the management network A. Note that at least a part of the functions of the backbone server 4 may be managed inside the management network A. For example, the backbone server 4 is provided with an information server storing identification information, contact information, etc. of the company's employees and the employees of the company's affiliated companies. That is, 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 installed at the branch B. The management device 10 is managed inside the management network A. The management device 10 manages the workflow system operated inside the branch B.

[0018] In the workflow system, a workflow, which is message information, is approved on the system in order from the set approvers. The order of the approvers is set as the route of the workflow when the workflow is created. When a certain approver approves the workflow, a notification is sent from the management device 10 to the approver set in the next order, that is, the next approver who should approve the workflow next. When all approvers have approved, the workflow is completed. In this way, the workflow system conventionally substitutes the application procedures within the branch B, which were advanced by the approvers' stamp on paper, with message information in a virtual system.

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

[0020] The access right to the storage area is granted by the operation of an OA administrator who conducts digital-related operations after obtaining the approval of a person in an appropriate position. One or more approvers are set in this workflow. The multiple approvers may include an OA administrator. The multiple approvers may further include another OA administrator. For example, an OA key person, who is another OA administrator, is set as the first approver of the workflow and checks whether an appropriate path is set in the workflow.

[0021] Both the applicant who applies for the workflow and the approver who conducts the approval perform access authentication from their respective individual terminals 5 to the management network A, and each accesses the workflow system of the management device 10. The applicant and the approver browse the interface screen of the workflow system provided by the management device 10 and perform operations such as applying for and approving the workflow.

[0022] As shown in FIG. 2, the authentication device 2 includes a reception unit 21 and an authentication unit 22 as functions. 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 holds the individual terminal 5, such as an employee number. The identification information may include a password and an identifier of the individual terminal 5 itself.

[0023] Based on the received identification information, the authentication unit 22 authenticates that the individual terminal 5 accesses the management network A. The authentication unit 22 manages the access history of the individual terminal 5 to the devices inside the management network A in association with the identification information at the time of authentication. That is, inside the management network A, the identification information of the user of the individual terminal 5 is always grasped.

[0024] For example, in the branch server 3, n storage areas, namely, the first storage area 31-1, the second storage area 31-2, ···, the nth storage area 31-n, are set.

[0025] The management device 10 includes, as 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 in which identification information of a plurality of candidates who can be approvers is stored. Only information of candidates who can be approvers is stored in the first DB unit 11. In the first DB unit 11, information on a notification destination for contacting the candidate is stored in association with the identification information. For example, the information on the notification destination is the email address assigned to the user.

[0027] The second DB unit 12 is a database in which a list of additional information to be added to the workflow is stored. For example, the additional information is information indicating the first storage area 31-1, the second storage area 31-2, ···, the nth storage area 31-n of the branch server 3. Note that the additional information may further include an object or the like to be attached to the workflow.

[0028] The storage unit 13 stores information on workflows created in the past. The storage unit 13 stores workflows that have just been created, completed workflows, and the like. A completed workflow is one that has been approved by all approvers set in 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 identification information of the user from the authentication unit 22.

[0030] The display unit 15 generates an interface screen of the workflow system and controls the display content thereof. The interface screen includes a display screen on which a list of workflows stored in the storage unit 13 is displayed, and an approval screen that receives operations for creating and approving workflows. The display screen and approval screen of the workflow are viewable by a plurality of users including the applicant and approver of the workflow. The plurality of users are all users who have been authenticated by the authentication unit 22 to access the inside of the management network A.

[0031] In the approval screen, the display unit 15 changes the types of buttons in an active state that can be operated on the approval screen based on the combination of the current mode of the workflow and the identification information of the viewer. On the approval screen, the "application" button, "approval" button, "return" button, and "withdrawal" button are displayed in an active state or an inactive state. When any button is operated, that button is regarded as the process performed on the workflow. For example, when the "approval" button is operated, the management device 10 regards 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 a specific user set.

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

[0034] The update unit 17 updates the mode of the workflow according to processes such as application, approval, return, withdrawal, etc. performed on the workflow.

[0035] The notification unit 18 sends a notification requesting approval to the next approver in the workflow path. When a return process is performed on the workflow, the notification unit 18 notifies the applicant to that effect. When the workflow is completed, the notification unit 18 notifies the applicant to that effect.

[0036] The management unit 19 receives, on the management screen, an editing operation for 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 received editing operation.

[0037] Next, the mode of the workflow will be described. FIG. 3 is a transition diagram of the mode of the workflow created in the management system according to the first embodiment. FIGS. 4 to 8 are examples of the interface screens displayed in the management system according to the first embodiment.

[0038] The workflow includes information on the route, identification information of the applicant, information on the notification destination of the applicant, identification information of the approver, and incidental information. In addition, information on the processes that have been performed so far is added to the information on the route. That is, the information on the route is also used as history information of the processes performed on the workflow. A mode is set for the workflow.

[0039] As shown in FIG. 3, in this example, the workflow is set with "mode 0", "mode a", "mode b-1", "mode b-2", ··· "mode b-n", and "mode c". For example, the update unit 17 transitions and updates the mode of the workflow based on the process that was performed last among the process history.

[0040] Mode 0 is the mode during the creation of the workflow and before "application" is pressed. The creation unit 16 creates the workflow in mode 0 which is the creation mode.

[0041] On the approval screen of the workflow in Mode 0, when 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 "Remove" button are displayed in an inactive state. Also, in this case, the input fields for supplementary information, etc. are displayed in an active state where input is possible. On the approval screen of the workflow in Mode 0, when the identification information of the viewer does not match the identification information of the applicant, all buttons are displayed in an inactive state.

[0042] In Mode 0, when the "Apply" button is pressed, a transition is made to Mode b which is the approval mode. In Mode b, the approver approves the workflow. Mode b is set according to the number of approvers. When there are n approvers, n modes, namely Mode b-1, Mode b-2, ···, Mode b-n, are set in Mode b. Each mode is associated one-to-one with the set approver.

[0043] On the approval screen of the workflow in Mode b, when the identification information of the viewer matches the identification information of the approver corresponding to the mode, the "Approve" button and "Return" button are displayed in an active state. In this case, the "Apply" button and "Remove" button are displayed in an inactive state. Also, in this case, the input field for "Return Reason" is displayed in an active state. On the approval screen of the workflow in Mode b, when 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 the mode associated with the first approver in the path. When the "Approve" button is pressed in Mode b-1, a transition is made to Mode b-2. Mode b-2 is the mode associated with the second approver in the path. Similarly, the mode transitions in the same way for Mode b-3 and later. The mode b-n corresponding to the last approver is also called the final approval mode b-f.

[0045] In the final authentication mode b-f, when the "Application" button is pressed, the mode changes to mode c. Mode c is the completion mode, indicating that the application of the workflow is completed. On the approval screen of the workflow in mode c, all buttons are displayed in an inactive state regardless of the viewer.

[0046] In any of modes b-1 to b-n, when the "Return" button is pressed, the mode changes to mode a. Mode a is the modification mode for modifying the workflow.

[0047] On the approval screen of the workflow in mode a, when the identification information of the viewer matches the identification information of the applicant, the "Application" button and the "Withdrawal" button are displayed in an active state. In this case, the "Approval" button and the "Return" button are displayed in an inactive state. Also, in this case, the input fields for additional information of the workflow, etc. are displayed in an active state where they can be modified. On the approval screen of the workflow in mode a, when the identification information of the viewer does not match the identification information of the applicant, all buttons are displayed in an inactive state.

[0048] Figure 4 is an approval screen on which the workflow of mode 0 is displayed. The creation unit 16 adds the identification information of the applicant who opened this screen to create the workflow, and creates the workflow of mode 0. In this example, the added identification information is the employee number N. The applicant creates the workflow by inputting the content into each block which is additional information and selecting the pull-down on this approval screen.

[0049] In this example, as additional information, a workflow having input fields or selection fields for block K and block L is created. Block K is a field for inputting the identification information of the applicant and the information of the notification destination. The applicant inputs the email address as their own notification destination. In block L, based on the information stored in the second DB unit 12, the storage area for which access rights are desired to be granted can be selected.

[0050] In this example, a workflow having a selection field of block M, which is a field for setting path information, is created. "Application Department OA Key Person" is the first approver. Hereinafter, "Approver 1", "Approver 2", "Approver 3", and "Approver 4" are approvers who can be the second to the fifth approvers, respectively. "Final Approver" is the last approver. Each approver can be selected only from among a plurality of candidates stored in the first DB unit 11.

[0051] Each approver is selected from the candidates displayed in a pull-down format. In the first DB unit 11, it is set which candidate is displayed in which pull-down. Note that not all of the approvers n necessarily have to be selected. For example, only the "Final Approver" may be selected as an approver.

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

[0053] FIG. 5 is an application status screen after the workflow is created. The interface screen includes an "Application Status" screen, which is one of the display screens and sorts and displays the currently incomplete workflows in a list. The interface screen includes a "Completion List" screen, which is one of the display screens and sorts and displays the completed workflows in a list. On the interface screen, an "Application / Approvals" tab, which is an approval screen, an "Application Status" tab, which is a display screen, and a "Completion List" tab, which is a display screen, can be selected. For example, when there is a workflow for which approval processing needs to be performed, a badge indicating that fact is also displayed on the "Application Status" tab.

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

[0055] Figure 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 the buttons and input fields in an inactive state.

[0056] Figure 8 is a management screen for displaying the 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. On the management screen, the "Name" of the candidate, the "Employee Number", which is the identification information of the candidate, and the "Email Address", which is the notification destination of the candidate, are displayed in association. Also, information indicating which approver among the approvers can be set, such as "Approve", "OA", and "Manage", is associated with the candidate's information.

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

[0058] The flowchart in Figure 9 starts when the user begins to create a workflow.

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

[0060] After that, 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 identification information obtained in step S001 to the workflow. The creation unit 16 accepts operations such as input of the applicant's notification destination and selection of an approver on the creation screen.

[0061] After that, in step S003, the applicant operates the "Apply" button to apply for the workflow. The creation unit 16 stores the information of the applied workflow in the storage unit 13.

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

[0063] After that, the operation of the flowchart ends.

[0064] The flowchart of FIG. 10 is an example of the operation when the notification unit 18 performs notification. The flowchart of FIG. 10 starts when the 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 the user to whom the notification is to be sent based on the mode of the workflow. When the workflow is in mode b-n, the notification unit 18 identifies the approver associated with the mode as the user to whom the notification is to be sent. When the workflow is in mode a, the notification unit 18 identifies the applicant as the user to whom the notification is to be sent. When the workflow is in mode c, the notification unit 18 identifies the applicant as the user to whom the notification is to be sent.

[0066] After that, in step S102, the notification unit 18 sends a notification corresponding to the mode to the notification destination of the identified user. When the user who sends the notification is the applicant, the notification unit 18 sends a notification indicating that it has been sent back or completed to the notification destination of the applicant added to the workflow. When the user who sends the notification is the approver, the notification unit 18 extracts the notification destination of the approver from the first DB unit 11 using the identification information of the approver. The notification unit 18 sends a notification requesting approval to the extracted notification destination. If the information of the approver's notification destination is added to the workflow, the notification unit 18 may send a notification to the added notification destination without extracting it from the first DB unit 11.

[0067] After that, the operation of the flowchart ends.

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

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

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

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

[0072] In step S203, the display unit 15 may display an approval screen in which at least part of the workflow information is hidden. Even in this case, in step S203, for the applicant and the approver who is not the next approver included in the route, the display unit 15 may display an approval screen in which all buttons and input fields are inactive. Thus, the content displayed on the approval screen changes according to the combination of the mode and the identification information of the viewer.

[0073] In step S202, when 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 in an active state.

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

[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 there is a next approver in the route.

[0076] If there is a next approver in step S206, the operation of step S207 is performed. In step S207, the update unit 17 changes the mode of the workflow 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 there is no next approver in step S206, the operation of step S208 is performed. In step S208, the update unit 17 changes the mode of the workflow to the completion mode.

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

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

[0080] After that, 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 a creation unit 16, a storage unit 13, an update unit 17, a display unit 15, and an acquisition unit 14 as functions. The display unit 15 displays on the approval screen so that a plurality of users can view the workflow as viewers. The display unit 15 changes the types of buttons in an operable active state based on the combination of the workflow mode and the identification information of the viewer on the approval screen. By displaying the workflow in this way, even a third party who is not an approver or an applicant can confirm the content of the workflow, and the buttons operable on the workflow can be controlled for such a third party. As a result, the management device 10 can appropriately manage the workflow.

[0082] Further, 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 a third party who has been authenticated for access. Therefore, the security can be improved.

[0083] In addition, the management device 10 further includes a first DB unit 11 which is a DB unit. The first DB unit 11 stores identification information of only a plurality of candidates who can be approvers. Although the backbone server 4 stores identification information of all users as well as users who can be approvers, the management device 10 has an individual DB unit. By owning and managing a database with a necessary and sufficient amount of information at branch B and using this, the capacity of the server can be reduced, the comfort of the operation of the management device 10 can be improved, and the security can be improved. For example, by operating the management device 10, the OA administrator at branch B can change the information stored in the DB unit without obtaining approval from head office H. Further, since the DB unit is stored inside management network A, the security can be improved.

[0084] Note that instead of the authentication device 2, the management device 10 may have the function of the authentication unit 22. 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 of the applicant uses the identification information input for access authentication to the management device 10. Among the information associated with the workflow, the identification information of the approver uses the identification information stored in the DB unit. For this reason, it is not necessary to store information of users who can be applicants in the DB information. Further, it is not necessary to have the applicant re-enter the identification information. Furthermore, since the identification information of the applicant is information that has been authenticated, the security on the security side is ensured. In this way, the capacity of the server can be reduced and the security can be improved.

[0085] Next, an example of the 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 in Embodiment 1.

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

[0087] When the processing circuit includes at least one processor 100a and at least one memory 100b, each function of the management device 10 is realized by software, firmware, or a combination of software and firmware. At least one of the software and the firmware is described as a program. At least one of the software and the firmware is stored in at least one memory 100b. The at least one processor 100a reads and executes the program stored in the at least one memory 100b to realize each function of the management device 10. The at least one processor 100a is also referred to as a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a DSP. For example, the at least one memory 100b is a non-volatile or volatile semiconductor memory such as a RAM, a ROM, a flash memory, an EPROM, or an EEPROM, a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, or a DVD.

[0088] When the processing circuit includes at least one dedicated hardware 200, the processing circuit is realized by, for example, 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 is realized by the processing circuit respectively. For example, each function of the management device 10 is realized by the processing circuit collectively.

[0089] Regarding each function of the management device 10, a part may be implemented by dedicated hardware 200, and the other part may be implemented by software or firmware. For example, the function of the notification unit 18 may be implemented by a processing circuit as dedicated hardware 200, and for functions other than the function of the notification unit 18, at least one processor 100a may read and execute a program stored in at least one memory 100b to implement them.

[0090] In this way, the processing circuit realizes each function of the management device 10 with hardware 200, software, firmware, or a combination thereof.

[0091] Although not shown, each function of the authentication device 2, the branch server 3, and the backbone server 4 is also realized by a processing circuit equivalent to the processing circuit that realizes each function of the management device 10.

[0092] Note that at least a part of each function of the management device 10 may be realized on a cloud server. In this case, the processing circuit is composed of a plurality of sub-circuits. The plurality of sub-processing circuits are respectively provided in a plurality of devices constituting the cloud server. The plurality of devices constituting the cloud server may each be provided in a different building.

Industrial Applicability

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

Explanation of Reference Numerals

[0094] 1 Management system, 2 Authentication device, 3 Branch server, 4 Core server, 5 Individual terminal, 10 Management device, 11 First DB section, 12 Second DB section, 13 Storage section, 14 Acquisition section, 15 Display section, 16 Creation section, 17 Update section, 18 Notification section, 19 Management section, 21 Reception section, 22 Authentication section, 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 creation unit that creates a workflow that allows approval processing by one or more designated approvers, A storage unit for storing the created workflow, An update unit updates the mode of the workflow in accordance with the processing performed on the workflow, A display unit that displays an approval screen for accepting operations to approve the aforementioned workflow, An acquisition unit that acquires the identification information of the viewer who is viewing the aforementioned approval screen, Equipped with, The aforementioned display unit is Multiple users, including the applicant who created the workflow and the approver, are made able to view the workflow as viewers. Based on the current mode of the workflow and the viewer's identification information, the types of buttons that are active and operable on the approval screen are changed. Management device.

2. The update unit updates the workflow to an approval mode associated with the next approver if, after the workflow has been created or approved by the approver, approval from the next approver is required. The display unit activates the approval button on the approval screen of the workflow only when the workflow mode is the approval mode and the viewer's identification information matches the next approver's identification information. The control device according to claim 1.

3. The update unit updates the workflow to modification mode when the approver performs the process of returning the workflow. The display unit displays the workflow in a state where its contents can be modified on the approval screen of the workflow only when the workflow mode is the modification mode and the viewer's identification information matches the applicant's identification information. The control device according to claim 1.

4. The display unit activates the withdrawal button for withdrawing the workflow on the approval screen only when the workflow mode is the modification mode and the viewer's identification information matches the applicant's identification information. The control device according to claim 3.

5. A database unit that stores identification information of multiple candidates who may become the approver, Furthermore, The DB unit stores identification information for only the aforementioned group of candidates. The display unit determines whether the viewer's identification information matches the identification information stored in the DB unit, and changes the type of button that is active on the approval screen. A control device according to any one of claims 1 to 4.

6. An authentication unit manages to ensure that only users whose identification information has been authenticated can access the aforementioned approval screen. Furthermore, The acquisition unit acquires the applicant's identification information based on the identification information authenticated by the authentication unit. The creation unit associates the applicant's identification information obtained by the acquisition unit with the workflow. The control device according to claim 5.

7. A management device that manages workflows within the network, where approval can be processed by one or more designated approvers, An authentication device manages to ensure that only users whose identification information has been authenticated can access the inside of the network, Equipped with, The aforementioned control device is A creation unit for creating the aforementioned workflow, A storage unit for storing the created workflow, An update unit updates the mode of the workflow in accordance with the processing performed on the workflow, A display unit that displays an approval screen for accepting operations to approve the aforementioned workflow, An acquisition unit that acquires the identification information of the viewer who is viewing the aforementioned approval screen, It has, The aforementioned display unit is Multiple users, including the applicant who created the workflow and the approver, are made able to view the workflow as viewers. Based on the current mode of the workflow and the viewer's identification information, the types of buttons that are active and operable on the approval screen are changed. Management system.

8. The aforementioned control device is A database unit that stores identification information of multiple candidates who may become the approver, Furthermore, The DB unit stores identification information for only the aforementioned group of candidates. The acquisition unit acquires the applicant's identification information based on the identification information authenticated by the authentication device. The creation unit associates the applicant's identification information obtained by the acquisition unit with the workflow. The display unit determines whether the viewer's identification information matches the identification information stored in the DB unit, and changes the type of button that is active on the approval screen. The management system according to claim 7.

Images