Approval task transfer method based on improved rbac authority control mechanism

Abstract

The invention discloses an approval task transfer method based on an improved RBAC authority control mechanism, including: creating a role in the system, the role is an independent individual role, and an independent individual role can only be associated with a unique user at the same time period. Associate one or more independent individual roles; the transferer obtains the approval tasks in the approval process; the transferer transfers the approval tasks to the transferee, and the transferee is an independent individual role. In the present invention, the transferee adopts an independent individual character role. When the employee corresponding to the user associated with the transferee's role leaves or transfers, he only needs to cancel the original association and associate the user corresponding to the new employee with the role to automatically obtain the current status of the role. All transferred approval tasks are handed over through role association, with a small workload and seamless connection, without delay or omission in the transfer of approval tasks, ensuring that urgent tasks are processed in a timely manner.

Description

technical field [0001] The invention relates to a method for managing approval tasks in management systems such as ERP and CRM, in particular to a method for transferring approval tasks based on an improved RBAC authority control mechanism. 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 functional positio...

AI Technical Summary

Problems solved by technology

[0007] In the above statement, both 2 and 3 need to authorize the role of class / group nature, but the way of authorization through the role of class / group / post / work type has the following disadvantages: 1. The operation is difficult when the user authority changes: In actual system use, it is often necessary to adjust user permissions during enterprise operations. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot change the permissions of an individual employee. Instead, change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

[0009] 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

[0010] 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

[0011] 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

[0012] Traditional management systems usually have the function of transferring approval tasks. However, the approval tasks are directly transferred to a specific user / employee. When the transferred user / employee leaves or is transferred, the approval task needs to be returned and reapproved. The transfer of tasks has a large workload and is prone to delays or omissions in task processing, which may bring unpredictable losses to the enterprise

Images