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

Abstract

The invention discloses a method for setting an approval role of an approval node of a workflow according to roles. The method comprises the following steps of creating roles included in a system organization structure; displaying candidate roles when the approval node of the workflow is set; and selecting one or more roles from the candidate roles as the approval role / roles of the node. When thesystem workflow setting personnel set the approval role, the system workflow setting personnel only need to select the corresponding role instead of paying attention to a specific user, and even if the user associated with the role is changed, the approval role does not need to be reset, so that the method is easy to operate and less error-prone. A main body of approval operation in the workflow is the role, and the role is an independent individual, even if an employee / user change occurs, a new employee is associated to the role in the approval process again; or when the approval authority ofthe employee is changed, the approval authority of the role is adjusted in a targeted way instead of resetting / adjusting the process; and the setting is convenient, and the reliability of the workflow 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 ERP, in particular to a method for setting approval roles by workflow approval nodes according to roles. 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 accordi...

AI Technical Summary

Problems solved by technology

[0008] In the above statement, both 2 and 3 need to authorize the role of class / group nature, but the method of authorization and workflow control through the role of class / group / position / type of work has the following disadvantages: 1. When user permissions change Difficult to operate: In actual system use, it is often necessary to adjust user permissions during operation. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot Changes in employee permissions change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

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

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

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

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