Acquisition method for field value of role property field in form

Abstract

The invention discloses an acquisition method for a field value of a role property field in a form, which comprises the steps of: displaying a candidate field value corresponding to the role propertyfield, wherein the candidate field value is a role and the role is a separate individual rather than a group / class, and one role in a same time can only be associated with a unique user and one user can be associated with one or more roles; and obtaining field values, that is, selecting a role from the candidate field value as a field value of the role property field. The field value of the role property field in the present invention is composed of a role, or composed of a role and a user, or composed of a role and an employee, since the role in the present invention is a separate individualrather than a group / classe, therefore, it can be judged by the role in the field value that which post number is responsible for the corresponding role property field, facilitate the division of responsibility, and it is conducive to statistical analysis of related matters by post number and responsibility when problems arise.

Description

technical field [0001] The invention relates to a method for generating a form of a management software system such as ERP, in particular to a method for obtaining a field value of a role property field in a form. 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). The basic idea of ​​role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and users can indirectly access database resources by being assigned different roles. [0003] There are often a large number of tables and views in large-scale application systems, which makes the management and authorization of database resources very c...

AI Technical Summary

Problems solved by technology

[0005] However, the traditional role-based user rights management methods all adopt the "role-to-user one-to-many" association mechanism. / Position / Type of work and other concepts, the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. figure 1 As shown, directly authorizing users has the disadvantages of heavy workload, frequent and cumbersome operations; 2. figure 2 As shown, authorize the role (category / group / position / type of work) (a role can be associated with multiple users), and the user obtains the authority through the role; 3. For example image 3 As shown, the combination of the above two methods

[0006] 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 the actual system use, it is often necessary to adjust the user's permissions during the operation process. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot Changes to change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

The above two processing methods not only take a long time to authorize the role in the case of many role permissions, but also are prone to mistakes. The operation of the user is cumbersome and troublesome, and it is also easy to make mistakes and cause losses to the system user.

[0007] 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. To associate a new user, it is impossible to accurately determine how to choose the association

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

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

However, when the employee is responsible for multiple positions, he cannot clearly understand which position number he is engaged in, which makes it impossible to trace the specific responsible position number or responsible department when a problem occurs; for example, Zhang San is also responsible for For the affairs of Sales Department 1 and Sales Department 2, when the contract signer of a contract form is filled in as Zhang San, but the contract signing department is not marked on the contract form, it is impossible to distinguish whether it belongs to Sales Department 1 or Sales Department 2; If there is a problem and the responsibility is pursued, it is impossible to accurately analyze whether the first sales department or the second sales department is responsible except for Zhang San, and it is impossible to analyze which post number is responsible

Images