Method for setting approval role according to roles of workflow approval node

Abstract

The invention discloses a method for setting an approval role according to roles of a workflow approval node. The method comprises that role included by a system organization structure are created; candidate roles are displayed when the workflow approval node is set; and one or multiple roles are selected from the candidate roles as the approval role(s) of the node. A system workflow setting staff only needs to select the corresponding roles instead of paying attention to concrete users when setting the approval roles, it is not required to set the approval roles again even if the users associated with the roles are changed, operation is convenient, and it is not likely to make errors. The roles which are independent individuals serve as the main body of a workflow approval operation; new employees are associated to the roles in the approval flow if there is change in the employees / users; or if the approval authority of certain employee is changed, it is only required to adjust the approval authority of the role in a targeted way instead of resetting / adjusting the flow; and setting is convenient, and the workflow reliability is improved greatly.

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 by workflow approval nodes. 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 according to different functi...

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, but the job responsibilities of each person usually change. When the personnel responsibilities are adjusted, a new person in charge needs to be selected, which is prone to errors

Images