Method for setting an approval process based on a field

Abstract

The invention discloses a method for setting an approval process based on a field, and the steps of creating the approval process are as follows: S1, selecting a form corresponding to the approval process; S2, selecting a basis field for the approval process, wherein one basis field can be selected by one or more approval processes; S3, setting the field value collection of the selected by-field of the approval process, wherein each field value can only exist in the field value collection of one approval process under the by-field. When the approval process is associated, it is judged which approval process belongs to the field value collection of the corresponding basis field according to the field value of the basis field in the approval form. When a form for examination and approval issubmitted, the method can automatically associate the examination and approval process according to the field value of the basis field in the form, and determine the process according to the content of the basis field in the form. The method is simple and clear, is convenient to operate, enables the basis field of the form to be replaced, and can meet different examination and approval requirements in actual management.

Description

technical field [0001] The invention relates to a method for setting an approval flow by a system flow setter of management software such as ERP, in particular to a method for setting an approval flow based on a basis field. 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 ent...

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] In addition, the traditional approval process setting method can only create one approval process for a form (only one approval process can be used at the same time), and all submissions of the form go through this process, although the flow conditions of the process can be set in the process to guide There are different approval lines for process approval, but when faced with complex approval requirements, the flow conditions in the process will be set very complicated, and there are many approval lines for flow. It is necessary to set up a process that fully meets the management requirements. It is difficult, and the setting operation is complicated, error-prone, and it will be troublesome to modify, and the modification may affect the normal use of the relevant personnel of the process

Images