Department-based approval role setting method for workflow approval nodes

Abstract

The invention discloses a department-based approval role setting method for workflow approval nodes. The method comprises the following steps: departments and roles contained in an organization structure of a system are created; a department manager role of each department is set; candidate departments are displayed when the workflow approval nodes are set; one or more departments are selected from the candidate departments, and the department manager role of the department plays the approval role in the corresponding approval node. A system workflow setting worker is only required to select the corresponding department during approval role setting, then the department manager role of the department plays the approval role, even if the department manager role of the department changes, the current department manager of the department plays the approval role, the approval role is not needed to be set again,, operation is convenient, and proneness to error is avoided. The subject of workflow approval operation is role and the role is an independent individual, so that even during staff / user change, all that is needed is to re-associate new staff to the corresponding role in an approval process, and the setting is convenient.

Description

technical field [0001] The invention relates to a method for setting and managing approval roles of approval nodes in workflows of management software systems such as EPR, in particular to a method for setting approval roles for workflow approval nodes according to departments. Background technique [0002] Role-based access control (RBAC) is the most researched and thoughtful database permission management mechanism in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and discretionary access control (DAC). Traditional discretionary access control has high flexibility but low security, mandatory access control has high security but is too restrictive; role-based access control combines both, which is not only easy to manage but also reduces complexity, cost and error probability , which has been greatly developed in recent years. The basic idea of ​​role-based access control (RBAC) is to divide different roles acc...

AI Technical Summary

Problems solved by technology

[0013] 2. It is difficult to remember the specific permissions contained in the role for a long time: If the role has many permission function points, it is difficult to remember the specific permissions of the role over time, and it is even more difficult to remember the permission differences between roles with similar permissions. The permissions of the role are also easy to confuse; if you want to associate a new user, you cannot accurately determine how to choose the association

[0014] 3. Due to the change of user permissions, more and more roles will be created (if no new roles are created, the direct authorization to users will be greatly increased), and it is more difficult to distinguish the specific differences between the permissions of each role

[0015] 4. When transferring a post, if you want to assign many permissions of the transferred user to several other users, you must distinguish these permissions of the transferred user during processing, and then create roles to associate with the other users. users, such an operation is not only complicated and time-consuming, but also prone to errors

[0016] When setting the approval node of the existing workflow, the corresponding person is usually selected. For a company with a large number of personnel, it is very cumbersome to select a person for approval.

In addition, when personnel duties are adjusted, new responsible personnel need to be selected, which is prone to errors

Images