Role and user one-to-one correspondence-based workflow control method and system

Abstract

The invention discloses a role and user one-to-one correspondence-based workflow control method and system. The method comprises the following steps of: constructing a three-layer structure model of users, roles and authorities, wherein each role is an independent individual, and at a same time period, one role only can be associated with a unique user but one user can be associated with one or more roles; controlling a workflow by utilizing the three-layer structure model, selecting an approval role and authorizing the approval role; and determining to-be-processed approval tasks by the usersaccording to the associated roles, and carrying out approval operations according to the authorities of the associated roles. According to the method and system, subjects of the approval operations in workflows are roles, and even employee / user change (such as position transfer, demission and the like) or employee approval authority change occurs, employees are re-associated with the roles or role approval authorities are adjusted without resetting / adjusting the process, so that the setting is convenient, errors or omissions are not easy to occur, normal operation of enterprises is not influenced, and the reliability of the workflows is greatly improved.

Description

technical field [0001] The invention relates to a workflow control method of management software systems such as ERP, in particular to a role-based one-to-one workflow control method and system for users. 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 , and thus 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 positions in the enterprise organization...

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

Images