Workflow and method for setting form field operation authority of approval nodes thereof

Abstract

The invention discloses a workflow and a method for setting form field operation authority of approval nodes thereof. The workflow comprises a start node and an approval node; the setting modes of form field operation authority of the start node and the approval node are different. In addition, a method for setting form field operation authority of approval nodes is also disclosed; the approval node comprises one or more approvers; the form field operation authority of each approver in the approval node is customized. The method comprises following steps: selecting approvers from the approval node; obtaining default settings of the form field operation authority; modifying the default settings of the form field operation authority according to the approval items of the selected approvers in the workflow. By means of the method of the invention, the approval cycle is shortened, the approval workload is reduced and information security is enhanced.

Description

technical field [0001] The invention relates to a method for setting authority in workflow of management software systems such as ERP, in particular to a method for setting operation authority of form fields of workflow and approval nodes thereof. 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 ...

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

Example 2, the sales contract of a Shanghai branch needs to be approved by the personnel of the Chengdu branch, but the approvers of the Chengdu branch do not have the authority to view the sales contract of the Shanghai branch in the system. The company's approval personnel cannot view the relevant content of the sales contract, resulting in the inability to complete the normal approval process

[0018] When the same permissions are set for all nodes, some approvers can view sensitive information that they do not need for approval, which will expand the scope of dissemination of these information, easily lead to information leakage, and threaten information security, such as approval before the contract is signed: financial approval The approver mainly examines whether the contract should be signed from the financial point of view, and does not need to know the customer's contact information. If the financial approver is set to view the customer's contact information, it may lead to the disclosure of the customer's contact information.

Images