WO2019007261A1 - 表单中的角色性质字段的字段值获取方法 - Google Patents

表单中的角色性质字段的字段值获取方法 Download PDF

Info

Publication number
WO2019007261A1
WO2019007261A1 PCT/CN2018/093450 CN2018093450W WO2019007261A1 WO 2019007261 A1 WO2019007261 A1 WO 2019007261A1 CN 2018093450 W CN2018093450 W CN 2018093450W WO 2019007261 A1 WO2019007261 A1 WO 2019007261A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
user
field value
field
obtaining
Prior art date
Application number
PCT/CN2018/093450
Other languages
English (en)
French (fr)
Inventor
陈达志
Original Assignee
成都牵牛草信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都牵牛草信息技术有限公司 filed Critical 成都牵牛草信息技术有限公司
Publication of WO2019007261A1 publication Critical patent/WO2019007261A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the invention relates to a form generation method for a management software system such as ERP, in particular to a method for obtaining a field value of a character property field in a form.
  • Role-based access control is one of the most researched and matured database rights management mechanisms in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and autonomous 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 indirectly access database resources by being assigned different roles.
  • the role-based permission control mechanism can manage the access rights of the system simply and efficiently, which greatly reduces the burden and cost of the system rights management, and makes the system rights management more in line with the business management specifications of the application system.
  • the traditional role-based user rights management method adopts the "role-to-user one-to-many" association mechanism, and its "role” is group/class nature, that is, one role can simultaneously correspond to/associate multiple users, and the role is similar to the post.
  • the authorization of user rights under this association mechanism is basically divided into the following three forms: 1, as shown in Figure 1, directly authorized to the user, the disadvantage is that the workload is large, the operation is frequent and troublesome; As shown in Figure 2, the role (class/group/post/work type) is authorized (a role can be associated with multiple users), and the user obtains the permission through the role; 3. As shown in Figure 3, the above two methods are combined. .
  • both 2 and 3 need to authorize the role of the class/group nature, and the way of authorization through the role of class/group/post/work type has the following disadvantages: 1.
  • the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
  • a contract form usually contains the contract signer field. If the contract signer is Zhang San, then Zhang San is the field value of the contract signer. In the existing form, only the field of the contract signing party can be filled in as the corresponding employee. For example, in the above example, the field value of the contract signing party is filled in or selected as Zhang San.
  • Zhang San is also responsible for When the sales contract and the sales department are completed, the contract signing party of a contract form is filled in as Zhang San, but when the contract signing department is not marked on the contract form, it is impossible to distinguish whether it belongs to the sales department or the sales department. If there is a problem to be pursued, it is impossible to accurately analyze the sales department, the sales department, the sales department, the second department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the sales department, the
  • the object of the present invention is to overcome the deficiencies of the prior art and to provide a method for obtaining a field value of a character property field in a form.
  • a field value obtaining method of a role property field in a form including: displaying a candidate field value corresponding to a character property field, the candidate field value being a role, and the role is independent Individuals, not groups/classes, a role can only be associated with a unique user at the same time, and a user is associated with one or more roles; obtaining a field value: selecting a role from the candidate field values as the character property field Field value.
  • the field value obtaining method of the character property field in the form includes: displaying candidate field values corresponding to the character property field, the candidate field value is a role, the role is an independent individual, not a group/class, and a role in the same time period Only a unique user can be associated, and one user associates one or more roles; obtain a role field value: select a role from the candidate field values as a role field value in a field value of the role property field; obtain a user field Value: After obtaining the role field value, the user currently associated with the selected role is automatically obtained as the user field value in the field value of the role property field, or the employee corresponding to the user currently associated with the selected role is automatically obtained as the role property. The user field value in the field value of the field.
  • the method for obtaining the field value further includes the step of modifying a user field value: replacing a user currently as a user field value with one of all users associated with the role, or using the current value as a user field value.
  • the employee is replaced with one of all employees corresponding to all users associated with the role.
  • the user determines the authority by its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
  • the user when the user moves across the department, the user is associated with the role in the original department, and the user is associated with the role in the new department.
  • the method for obtaining the field value of the role property field in the form includes: obtaining the user field value: automatically obtaining the current user of the login system or the employee corresponding to the current user as the user field value in the field value of the role property field; acquiring the role Field value: After the user field value is obtained, if the current user has only one role associated with the role, the role is automatically obtained as the role field value in the field value of the role property field; if the current user has two roles or In the above, one of the roles currently associated with the current user is selected as the role field value in the field value of the role property field; the role is an independent individual, not a group/class, and one role can only be associated in the same time period. The only user, and one user is associated with one or more roles.
  • the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the method for obtaining the field value of the role attribute field in the form includes: the employee logs in to the system according to the corresponding user; selects the current role: after the employee logs in to the system, the default role of the user is the current role or the employee selects all the associated users of the employee.
  • a role other than the default role in the role is the current role, the default role has one and only one; the role field value is obtained: the current role is automatically obtained as the role field value in the field value of the role property field,
  • a role is an independent entity, not a group/class.
  • a role can only be associated with a unique user in the same period, and a user is associated with one or more roles.
  • Obtaining a user field value After obtaining the role field value, the current role is automatically obtained. The currently associated user is the user field value in the field value of the role property field, or the employee corresponding to the user currently associated with the current role is automatically obtained as the user field value in the field value of the role property field.
  • the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the beneficial effects of the present invention are: (1)
  • the field value of the character property field in the present invention is composed of a role, or consists of a role and a user, or consists of a role and an employee, since the role in the present invention is an independent individual, not Group/class, so it is possible to judge the corresponding role attribute field by the role in the field value.
  • Which post number/station number is responsible for which is convenient for division of duties, and is more conducive to related matters by post number/station number.
  • a contract form contractor is a salesperson 1, and employee A is responsible for selling one salesperson 1 and sales two salesperson 2 (salesperson 1, salesperson 2 for the role); using traditional The method is that the field value of the contract signator is employee A, and the method of the invention is that the field value of the contract signator is salesperson 1 (employee A); when the contract form has problems to be pursued, the traditional method can only chase Responsible for the employee A, and the method of the present invention can be used to blame the employee A and the sales one (because the role belongs to the department, and can also analyze which job number/role signed contract), thereby being able to perform more accurate More reasonable division of responsibility and disciplinary action.
  • the traditional rights management mechanism defines the role as a group, a job type, a class, etc.
  • the role is a one-to-many relationship with the user. In the actual system use process, it is often necessary to perform the user's authority during the operation process. Adjustments, for example, when the employee permissions are changed, the permissions of an employee associated with the role change. We cannot change the permissions of the entire role because of the change of the individual employee permissions, because the role is also associated with other permissions. Staff. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
  • the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
  • the role since the role is an independent individual, the role permission can be changed to achieve the goal.
  • the method of the present application seems to increase the workload when the system is initialized, it can be made by copying and the like to make the role or authorization more efficient than the traditional group-based role, because the role of the group is not considered.
  • the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
  • the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
  • the traditional group-based role authorization method is error-prone, and the method of the present application greatly reduces the probability of authorization errors, because the method of the present application only needs to consider the role as an independent individual, without considering the traditional method to associate the role of the group. What are the commonalities of multiple users? Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
  • the method of the present application is as follows: the transferred user associates several roles.
  • the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
  • Reason 1 Because the role of this application is equivalent to a station number/post number, different station number/post number The work content/permissions are different. For example, the salesperson 1 role under the sales department and the developer 1 role of the technical department are completely different two station numbers/post numbers, and their permissions are different; Reason 2: If the department (sales department) of the salesperson 1 role is replaced with the technical department, and the role of the salesperson 1 is unchanged, there is a role in the technical department that has the authority of the sales department, which may lead to management confusion and security loopholes.
  • FIG. 1 is a schematic diagram of a manner in which a system directly authorizes a user in the background art
  • FIG. 2 is a schematic diagram of a manner in which a system authorizes a group/class role in the background art
  • FIG. 3 is a schematic diagram of a manner in which a system directly authorizes a user and authorizes a group/class role role in the background art
  • Figure 4 is a flow chart of an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role
  • Figure 6 is a flow chart of still another embodiment of the present invention.
  • Figure 7 is a flow chart of still another embodiment of the present invention.
  • Figure 8 is a flow chart of still another embodiment of the present invention.
  • a field value obtaining method of a character property field in a form includes: displaying a candidate field value corresponding to a character property field, and the candidate field value is a role.
  • the form contains the role attribute field "Contract Signer”, and the candidate field values include Salesperson 1, Salesperson 2, and Salesperson 3.
  • the roles are independent individuals, not groups/classes, and one role can only associate with a unique user at the same time, and one user associates one or more roles.
  • the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
  • Role definition The role does not have the nature of group/class/category/post/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application is equivalent Job number (The job number here is not a post, one post may have multiple employees at the same time, and one job number can only correspond to one employee at the same time).
  • a company system can create the following roles: general manager, deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • general manager deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • Zhang San serves as the company's deputy general manager 2, and also serves as a sales manager in Beijing, then Zhang The three roles to be associated are Deputy General Manager 2 and Beijing Sales Manager. Zhang San has the rights to these two roles.
  • roles are group/class/post/position/work type, and one role can correspond to multiple users.
  • the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
  • the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • Obtaining a field value selecting a role from the candidate field values as a field value of the character property field.
  • the candidate field values include salesperson 1, salesperson 2, and salesperson 3, and when the field value field "contract signer" is set in the form, the salesperson 2 is selected as the character property field from the candidate field values.
  • the field value of the contract signator that is, the contract signator's field value is "salesperson 2".
  • the field value obtaining method of the role property field in the form includes: defining a field value of the role property field, including a role field value and a user field value, that is, a role field value and a user field.
  • the values are each part of the field value.
  • a candidate field value corresponding to the character property field is displayed, and the candidate field value is a role.
  • the form contains the role attribute field "Contract Signer”, and the candidate field values include Salesperson 1, Salesperson 2, and Salesperson 3.
  • the roles are independent individuals, not groups/classes.
  • One role can only be associated with a unique user at a time, and one user is associated with one or more roles.
  • the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
  • the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • Obtaining a role field value selecting a role from the candidate field values as a role field value in a field value of the role property field.
  • the candidate field values include salesperson 1, salesperson 2, and salesperson 3, and when the field value field "contract signer" is set in the form, the salesperson 2 is selected as the character property field from the candidate field values.
  • the role field value in the field value of the contract signer is selected as the character property field from the candidate field values.
  • the user currently associated with the selected role is automatically obtained as the user field value in the field value of the role property field, or the employee corresponding to the currently associated user of the selected role is automatically obtained as the The user field value in the field value of the role property field.
  • the salesperson 2 is currently associated with the user A, and the candidate field values include the salesperson 1, the salesperson 2, and the salesperson 3.
  • the salesperson 2 is When the field value is set in the form including the character property field "contract signer", the salesperson 2 is When the role field value in the field value of the contract signator is selected, the user A is automatically used as the user field value in the field value of the contract signer, that is, the contract signator's field value is "salesperson 2 (user A)". For another example, the salesperson 2 is currently associated with the user A, the user A corresponds to the employee Zhang, and the candidate field values include the salesperson 1, the salesperson 2, and the salesperson 3, and the field of the role attribute field "contract signer" is included in the form.
  • Zhang San is automatically used as the user field value in the field value of the contract signer, that is, the contractor's field value is "sales”. Member 2 (Zhang San)”.
  • the method for obtaining the field value further includes the step of modifying the user field value: replacing the user currently as the user field value with one of all the users associated with the role, or replacing the current user value as the user field value with One of all employees corresponding to all users associated with the role.
  • All users associated with a role here include the user to whom the role is currently associated and the user to whom the role has been associated. For example, the user currently associated with salesperson 2 is user A, and the users who have been associated with salesperson 2 are user B, user C, and user D.
  • the form contains the role attribute field "contract signer"; in salesperson 2 is selected as After the role field value in the contractor's field value, the user A is automatically used as the user field value in the field value of the contract signer, that is, the contract signator's field value is "salesperson 2 (user A)"; If the user field value needs to be changed from user A to user C, then user C can be directly used as the user field value in the field value of the contract signer. At this time, the contract signer's field value is "salesperson 2 (user C)".
  • the user currently associated with the salesperson 2 is the user A
  • the user who has been associated with the salesperson 2 is the user B
  • the user C corresponds to the employee Li Si
  • the user C Corresponding employee Zhang Wu
  • user D ing corresponding employee Li Liu
  • the form contains the role nature field "contract signer”
  • the salesperson 2 is selected as the contractor's field value in the field value
  • Zhang San is automatically used as the contract
  • the user field value in the signer's field value that is, the contract signer's field value is "salesperson 2 (Zhang San)"
  • the user field value needs to be changed from Zhang San to Zhang Wu, then Zhang will be directly
  • the value of the user field in the field value of the contract signator may be five.
  • the field value of the contract signator is “salesperson 2 ( ⁇ )”.
  • the field value obtaining method of the role property field in the form includes: defining a field value of the role property field, including a role field value and a user field value, that is, a role field value and a user field.
  • the values are each part of the field value.
  • the user field value is obtained: the current user of the login system or the employee corresponding to the current user is automatically obtained as the user field value in the field value of the role property field. For example, if the current user of the login system is user A, when the field value is set in the form containing the role property field "contract signer", the user A is automatically used as the user field value in the field value of the contract signer. For another example, the current user of the login system is user A, and the user A corresponds to the employee Zhang San. When the field value is set in the form containing the role property field “contract signer”, Zhang San is automatically used as the contractor’s field value. User field value.
  • Get the role field value After the user field value is obtained, if the current user has only one role associated with the role, the role is automatically obtained as the role field value in the field value of the role property field; if the current user has two roles associated with the current user Or more, select one of the roles associated with the current user as the role field value in the field value of the role property field; the role is an independent individual, not a group/class, and only one role in the same time period A unique user can be associated with one user and one or more roles. For example, the current user of the login system is user A. If user A is associated with salesperson 1, after user A is selected as the user field value of the contractor's field value, then salesperson 1 is automatically used as the contractor's field value.
  • the role field value in the contract signator's field value is "User A (Salesperson 1)".
  • the current user of the login system is User A. If User A is associated with Salesperson 1, Clerk 1 and Cashier 1, after selecting User A as the field value of the contractor's field value, select Salesperson 1
  • the value of the role field in the field value of the contract signator, that is, the contractor's field value is "user A (salesperson 1).
  • the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
  • the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • the field value obtaining method of the character property field in the form includes: defining a field value of the character property field, including a role field value and a user field value, that is, a role field value and a user field.
  • the values are each part of the field value.
  • the default role of the user is the current role or the employee selects one of the roles associated with the user corresponding to the user as the current role.
  • the default role has one and only one. For example, employee Zhang 3 corresponds to user A, user A associate salesperson 1, clerk 1 and cashier 1, salesperson 1 is the default role, then salesperson 1 is the current role, and one of clerk 1 and cashier 1 can also be selected as the current Character.
  • the system displays the default role associated with the user (a user has one and only one default role) and the corresponding role.
  • the employee can select all the roles associated with the user except the default role.
  • a role other than the role and the corresponding permissions of the role are displayed.
  • the system displays the default role to the employee, if the employee no longer selects the role, the default role is the current role. If the employee performs the role selection, the selected role is the current role, and the system performs the current role according to the permissions of the current role. Shows that the user operates according to the permissions of the current role.
  • Obtaining a role field value automatically acquiring the current role as a role field value in a field value of the role property field, the role is an independent individual, not a group/class, and a role can only associate a unique user in the same time period And a user associates one or more roles.
  • the current role is Salesperson 1, and when the field value is set for the role property field "Contract Signer" in the form, Salesperson 1 is automatically used as the role field value in the field value of the contract signer.
  • the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
  • the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
  • the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • the user currently associated with the current role is automatically obtained as the user field value in the field value of the role property field, or the employee corresponding to the user currently associated with the current role is automatically obtained.
  • the user field value in the field value of the role property field For example, the current role is Salesperson 1, and Salesperson 1 is currently associated with User A.
  • the role in the field value of Salesperson 1 is automatically used as the user field value in the field value of the contract signator, that is, the contract signator's field value is "salesperson 1 (user A)".
  • the current role is the salesperson 1
  • the salesperson 1 is currently associated with the user A
  • the user A corresponds to the employee Zhang San.
  • the salesperson 1 is After the value of the role field in the field value of the contract signator, Zhang San is automatically used as the user field value in the field value of the contract signer, that is, the field value of the contract signer is "salesperson 1 (Zhang San)".

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)

Abstract

本发明公开了一种表单中的角色性质字段的字段值获取方法，包括：显示角色性质字段对应的候选字段值，所述候选字段值为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；获取字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值。本发明中角色性质字段的字段值是由角色构成、或由角色和用户构成、或由角色和员工构成，由于本发明中角色是独立的个体、而非组/类，因此可以通过字段值中的角色来判断出相应的角色性质字段到底是由哪个岗位号负责，便于进行职责划分，有利于以岗位号进行相关事务的统计分析，以及在出现问题时进行追责。

Description

表单中的角色性质字段的字段值获取方法 技术领域
本发明涉及ERP等管理软件系统的表单生成方法，特别是涉及一种表单中的角色性质字段的字段值获取方法。
 背景技术
基于角色的访问控制（RBAC）是近年来研究最多、思想最成熟的一种数据库权限管理机制，它被认为是替代传统的强制访问控制（MAC）和自主访问控制（DAC）的理想候选。基于角色的访问控制（RBAC）的基本思想是根据企业组织视图中不同的职能岗位划分不同的角色，将数据库资源的访问权限封装在角色中，用户通过被赋予不同的角色来间接访问数据库资源。
在大型应用系统中往往都建有大量的表和视图，这使得对数据库资源的管理和授权变得十分复杂。由用户直接管理数据库资源的存取和权限的收授是十分困难的，它需要用户对数据库结构的了解非常透彻，并且熟悉SQL语言的使用，而且一旦应用系统结构或安全需求有所变动，都要进行大量复杂而繁琐的授权变动，非常容易出现一些意想不到的授权失误而引起的安全漏洞。因此，为大型应用系统设计一种简单、高效的权限管理方法已成为系统和系统用户的普遍需求。
基于角色的权限控制机制能够对系统的访问权限进行简单、高效的管理，极大地降低了系统权限管理的负担和代价，而且使得系统权限管理更加符合应用系统的业务管理规范。
然而，传统基于角色的用户权限管理方法均采用“角色对用户一对多”的关联机制，其“角色”为组/类性质，即一个角色可以同时对应/关联多个用户，角色类似于岗位/职位/工种等概念，这种关联机制下对用户权限的授权基本分为以下三种形式：1、如图1所示，直接对用户授权，缺点是工作量大、操作频繁且麻烦；2、如图2所示，对角色（类/组/岗位/工种性质）进行授权（一个角色可以关联多个用户），用户通过角色获得权限；3、如图3所示，以上两种方式结合。
以上的表述中，2、3均需要对类/组性质的角色进行授权，而通过类/组/岗位/工种性质的角色进行授权的方式有以下缺点：1、用户权限变化时的操作难：在实际的系统使用过程中，经常因为在运营过程中需要对用户的权限进行调整，比如：在处理员工权限变化的时候，角色关联的某个员工的权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
2、要长期记住角色包含的具体权限难：若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，若要关联新的用户，无法准确判断应当如何选择关联。
3、因为用户权限变化，则会造成角色创建越来越多（若不创建新角色，则会大幅增加直接对用户的授权），更难分清各角色权限的具体差别。
4、调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
一个合同表单中通常会包含合同签订人这个字段，假如合同签订人为张三，则张三为该合同签订人这个字段的字段值。现有的表单中通常只能合同签订人这个字段填写为相应的员工，如上述例子中将合同签订人的字段值填写或选择为张三。但是，该员工负责多个岗位的事务时，无法清楚地了解到底属于哪个岗位号所从事的事务，导致在出现问题追责时无法追溯具体的责任岗位号或责任部门；例如，张三同时负责了销售一部和销售二部的事务，在将一个合同表单的合同签订人填写为张三，但合同表单上未标注合同签订部门时，无法区分是属于销售一部还是销售二部的事务；假如出现问题进行追责时，无法精准分析除张三以外，销售一部还是销售二部需要负责，更无法分析出是哪个岗位号的责任。
 技术问题
本发明的目的在于克服现有技术的不足，提供一种表单中的角色性质字段的字段值获取方法。
 技术解决方案
本发明的目的是通过以下技术方案来实现的：表单中的角色性质字段的字段值获取方法，包括：显示角色性质字段对应的候选字段值，所述候选字段值为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；获取字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值。
表单中的角色性质字段的字段值获取方法，包括：显示角色性质字段对应的候选字段值，所述候选字段值为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；获取角色字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值中的角色字段值；获取用户字段值：获取角色字段值后，自动获取所选角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所选角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。
优选的，所述字段值的获取方法还包括修改用户字段值的步骤：将当前作为用户字段值的用户替换为所述角色关联过的所有用户中的一个用户，或将当前作为用户字段值的员工替换为所述角色关联过的所有用户对应的所有员工中的一个员工。
优选的，所述用户通过其与角色的关联确定权限，一个员工对应一个用户，一个用户对应一个员工。
优选的，所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。
优选的，所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。
表单中的角色性质字段的字段值获取方法，包括：获取用户字段值：自动获取登录系统的当前用户或该当前用户对应的员工作为所述角色性质字段的字段值中的用户字段值；获取角色字段值：获取用户字段值后，若当前用户现在关联的角色只有一个，则自动获取该角色作为所述角色性质字段的字段值中的角色字段值；若当前用户现在关联的角色有两个或以上，则从当前用户现在关联的所有角色中选择一个作为所述角色性质字段的字段值中的角色字段值；所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。
优选的，所述用户通过其与角色的关联确定（获得）权限，一个员工对应一个用户，一个用户对应一个员工。
表单中的角色性质字段的字段值获取方法，包括：员工根据其对应的用户登录系统；选择当前角色：在员工登录系统后，用户的默认角色为当前角色或员工选择该员工对应用户关联的所有角色中除默认角色外的一个角色作为当前角色，所述默认角色有且只有一个；获取角色字段值：自动获取所述当前角色作为所述角色性质字段的字段值中的角色字段值，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；获取用户字段值：获取角色字段值后，自动获取所述当前角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所述当前角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。
优选的，所述用户通过其与角色的关联确定（获得）权限，一个员工对应一个用户，一个用户对应一个员工。
 有益效果
本发明的有益效果是：（1）本发明中角色性质字段的字段值是由角色构成、或由角色和用户构成、或由角色和员工构成，由于本发明中角色是独立的个体、而非组/类，因此可以通过字段值中的角色来判断出相应的角色性质字段到底是由哪个岗位号/工位号负责，便于进行职责划分，更有利于以岗位号/工位号进行相关事务的统计分析，以及在出现问题时进行追责。
例如，一个合同表单的合同签订者是销售员1，而员工甲负责销售一部的销售员1和销售二部的销售员2的事务（销售员1、销售员2为角色）；采用传统的方法则合同签订者的字段值为员工甲，而采用本发明的方法则合同签订者的字段值为销售员1（员工甲）；当合同表单出现问题进行追责时，传统方法则只能追责到员工甲，而采用本发明的方法则能够追责到员工甲和销售一部（因为角色归属于部门，且也可分析出是哪个岗位号/角色签订的合同），从而能够进行更准确、更合理的责任划分以及处分。
（2）传统的权限管理机制将角色定义为组、工种、类等性质，角色对用户是一对多的关系，在实际的系统使用过程中，经常因为在运营过程中需要对用户的权限进行调整，比如：在处理员工权限变化的时候，角色关联的某个员工的权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
但在本申请的方法下，因为角色是一个独立的个体，则可以选择改变角色权限即可达到目的。本申请的方法，虽然看起来在系统初始化时会增加工作量，但可以通过复制等方法，使其创建角色或授权的效率高于传统以组为性质的角色，因为不用考虑性质为组的角色在满足关联用户时的共通性，本申请方案会让权限设置清晰，明了；尤其是在系统使用一段时间后（用户/角色权限动态变化），该申请方案能为系统使用方大幅度提高系统使用中的权限管理效率，使动态授权更简单，更方便，更清晰、明了，提高权限设置的效率和可靠性。
（3）传统以组为性质的角色授权方法容易出错，本申请方法大幅降低了授权出错的几率，因为本申请方法只需考虑作为独立个体的角色，而不用考虑传统方法下关联该组性质角色的多个用户有哪些共通性。即使授权出错也只影响关联到该角色的那一个用户，而传统以组性质的角色则会影响关联到该角色的所有用户。即使出现权限授权错误，本申请的修正方法简单、时间短，而传统以组性质的角色在修正错误时需要考虑关联到该角色的所有用户的权限共通性，在功能点多的情况下不仅修改麻烦、复杂，非常容易出错，且很多情况下只能新创建角色才能解决。
（4）在传统以组为性质的角色授权方法下，若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，若要关联新的用户，无法准确判断应当如何选择关联。本申请方法的角色本身就具有岗位号/工位号的性质，选择一目了然。
（5）调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
本申请方法则为：被调岗用户关联了几个角色，在调岗时，首先取消用户与原部门内的角色的关联（被取消的这几个角色可以被重新关联给其他用户），然后将用户与新部门内的角色进行关联即可。操作简单，不会出错。
（6）角色归属于部门，则该角色的部门不能被更换，角色为什么不能更换部门：理由1：因为本申请的角色性质等同于一个工位号/岗位号，不同的工位号/岗位号的工作内容/权限是不一样的，如销售部门下的销售员1角色和技术部门的开发人员1角色是完全不同的两个工位号/岗位号，其权限是不同的；理由2：若将销售员1角色的所属部门（销售部）更换为技术部，其销售人员1这个角色的权限不变，则在技术部存在拥有销售部权限的一个角色，这样会导致管理混乱及安全漏洞。
 附图说明
图1为背景技术中系统直接对用户进行授权的方式示意图；
图2为背景技术中系统对组/类性质角色进行授权的方式示意图；
图3为背景技术中系统对用户直接授权和对组/类性质角色授权相结合的方式示意图；
图4为本发明的一种实施方式的流程图；
图5为本发明系统通过独立个体性质角色对用户进行授权的方式示意图；
图6为本发明的又一种实施方式的流程图；
图7为本发明的又一种实施方式的流程图；
图8为本发明的又一种实施方式的流程图。
 本发明的实施方式
下面结合附图进一步详细描述本发明的技术方案，但本发明的保护范围不局限于以下所述。
【实施例一】如图4所示，表单中的角色性质字段的字段值获取方法，包括：显示角色性质字段对应的候选字段值，所述候选字段值为角色。例如，表单中包含角色性质字段“合同签订人”，候选字段值包括销售员1、销售员2和销售员3。
如图5所示，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。
角色的定义：角色不具有组/类/类别/岗位/职位/工种等性质，而是一个非集合的性质，角色具有唯一性，角色是独立存在的独立个体；在企事业单位应用中相当于岗位号（此处的岗位号非岗位，一个岗位同时可能有多个员工，而同一时段一个岗位号只能对应一个员工）。
举例：某个公司系统中可创建如下角色：总经理、副总经理1、副总经理2、北京销售一部经理、北京销售二部经理、北京销售三部经理、上海销售工程师1、上海销售工程师2、上海销售工程师3、上海销售工程师4、上海销售工程师5……用户与角色的关联关系：若该公司员工张三任职该公司副总经理2，同时任职北京销售一部经理，则张三需要关联的角色为副总经理2和北京销售一部经理，张三拥有了这两个角色的权限。
传统角色的概念是组/类/岗位/职位/工种性质，一个角色能够对应多个用户。而本申请“角色”的概念相当于岗位号/工位号，也类同于影视剧中的角色：一个角色在同一时段（童年、少年、中年……）只能由一个演员来饰演，而一个演员可能会分饰多角。
所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。在创建角色之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
获取字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值。例如，候选字段值包括销售员1、销售员2和销售员3，在为表单中包含角色性质字段“合同签订人”设置字段值时，从候选字段值中选择销售员2作为角色性质字段“合同签订人”的字段值，即合同签订人的字段值为“销售员2”。
【实施例二】如图6所示，表单中的角色性质字段的字段值获取方法，包括：定义所述角色性质字段的字段值包括角色字段值和用户字段值，即角色字段值和用户字段值分别是所述字段值的一部分。
显示角色性质字段对应的候选字段值，所述候选字段值为角色。例如，表单中包含角色性质字段“合同签订人”，候选字段值包括销售员1、销售员2和销售员3。
所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。所述用户通过其与角色的关联确定（获得）权限，一个员工对应一个用户，一个用户对应一个员工。
所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。在创建角色之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
获取角色字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值中的角色字段值。例如，候选字段值包括销售员1、销售员2和销售员3，在为表单中包含角色性质字段“合同签订人”设置字段值时，从候选字段值中选择销售员2作为角色性质字段“合同签订人”的字段值中的角色字段值。
获取用户字段值：获取角色字段值后，自动获取所选角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所选角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。例如，销售员2当前关联着用户甲，候选字段值包括销售员1、销售员2和销售员3，在为表单中包含角色性质字段“合同签订人”设置字段值时，在销售员2被选择为合同签订人的字段值中的角色字段值时，自动将用户甲作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员2（用户甲）”。又例如，销售员2当前关联着用户甲，用户甲对应员工张三，候选字段值包括销售员1、销售员2和销售员3，在为表单中包含角色性质字段“合同签订人”设置字段值时，在销售员2被选择为合同签订人的字段值中的角色字段值后，自动将张三作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员2（张三）”。
所述字段值的获取方法还包括修改用户字段值的步骤：将当前作为用户字段值的用户替换为所述角色关联过的所有用户中的一个用户，或将当前作为用户字段值的员工替换为所述角色关联过的所有用户对应的所有员工中的一个员工。此处角色关联过的所有用户包括角色当前关联的用户和角色曾经关联过的用户。例如，销售员2当前关联的用户为用户甲，销售员2曾经关联过的用户为用户乙、用户丙和用户丁，表单中包含角色性质字段“合同签订人”；在销售员2被选择为合同签订人的字段值中的角色字段值后，自动将用户甲作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员2（用户甲）”；由于工作变动，需要将用户字段值由用户甲变更为用户丙，则直接将用户丙作为合同签订人的字段值中的用户字段值即可，此时合同签订人的字段值为“销售员2（用户丙）”。又例如，例如，销售员2当前关联的用户为用户甲，销售员2曾经关联过的用户为用户乙、用户丙和用户丁，用户甲对应员工张三、用户乙对应员工李四、用户丙对应员工张五、用户丁对应员工李六，表单中包含角色性质字段“合同签订人”；在销售员2被选择为合同签订人的字段值中的角色字段值后，自动将张三作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员2（张三）”；由于工作变动，需要将用户字段值由张三变更为张五，则直接将张五作为合同签订人的字段值中的用户字段值即可，此时合同签订人的字段值为“销售员2（张五）”。
【实施例三】如图7所示，表单中的角色性质字段的字段值获取方法，包括：定义所述角色性质字段的字段值包括角色字段值和用户字段值，即角色字段值和用户字段值分别是所述字段值的一部分。
获取用户字段值：自动获取登录系统的当前用户或该当前用户对应的员工作为所述角色性质字段的字段值中的用户字段值。例如，登录系统的当前用户为用户甲，在为表单中包含角色性质字段“合同签订人”设置字段值时，则自动将用户甲作为合同签订人的字段值中的用户字段值。又例如，登录系统的当前用户为用户甲，用户甲对应员工张三，在为表单中包含角色性质字段“合同签订人”设置字段值时，则自动将张三作为合同签订人的字段值中的用户字段值。
获取角色字段值：获取用户字段值后，若当前用户现在关联的角色只有一个，则自动获取该角色作为所述角色性质字段的字段值中的角色字段值；若当前用户现在关联的角色有两个或以上，则从当前用户现在关联的所有角色中选择一个作为所述角色性质字段的字段值中的角色字段值；所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。例如，登录系统的当前用户为用户甲，若用户甲关联销售员1，在将用户甲选择为合同签订人的字段值的用户字段值后，则自动将销售员1作为合同签订人的字段值中的角色字段值，即合同签订人的字段值为“用户甲（销售员1）”。又例如，例如，登录系统的当前用户为用户甲，若用户甲关联销售员1、文员1和出纳1，在将用户甲选择为合同签订人的字段值的用户字段值后，选择销售员1作为合同签订人的字段值中的角色字段值，即合同签订人的字段值为“用户甲（销售员1）。
所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。所述用户通过其与角色的关联确定（获得）权限，一个员工对应一个用户，一个用户对应一个员工。
所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。在创建角色之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
【实施例四】如图8所示，表单中的角色性质字段的字段值获取方法，包括：定义所述角色性质字段的字段值包括角色字段值和用户字段值，即角色字段值和用户字段值分别是所述字段值的一部分。
员工根据其对应的用户登录系统。
选择当前角色：在员工登录系统后，用户的默认角色为当前角色或员工选择该员工对应用户关联的所有角色中除默认角色外的一个角色作为当前角色，所述默认角色有且只有一个。例如，员工张三对应用户甲，用户甲关联销售员1、文员1和出纳1，销售员1为默认角色，则销售员1为当前角色，也可以从文员1和出纳1中选择一个作为当前角色。
在员工登录系统后，系统向该员工显示所述用户关联的默认角色（一个用户有且只有一个默认角色）和该默认角色对应的权限，员工可以选择其对应用户关联的所有角色中除默认角色外的一个角色及该角色对应的权限进行显示。此处，在系统向员工显示默认角色后，若员工不再进行角色选择则默认角色为当前角色，若员工又进行了角色选择，则所选择的角色为当前角色，系统根据当前角色的权限进行显示，用户根据当前角色的权限进行操作。
获取角色字段值：自动获取所述当前角色作为所述角色性质字段的字段值中的角色字段值，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。例如，当前角色为销售员1，在为表单中的角色性质字段“合同签订人”设置字段值时，自动将销售员1作为合同签订人的字段值中的角色字段值。
所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。所述用户通过其与角色的关联确定（获得）权限，一个员工对应一个用户，一个用户对应一个员工。
所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。在创建角色之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
获取用户字段值：获取角色字段值后，自动获取所述当前角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所述当前角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。例如，当前角色为销售员1，销售员1当前关联用户甲，在为表单中的角色性质字段“合同签订人”设置字段值时，在将销售员1作为合同签订人的字段值中的角色字段值后，自动将用户甲作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员1（用户甲）”。又例如，例如，当前角色为销售员1，销售员1当前关联用户甲，用户甲对应员工张三，在为表单中的角色性质字段“合同签订人”设置字段值时，在将销售员1作为合同签订人的字段值中的角色字段值后，自动将张三作为合同签订人的字段值中的用户字段值，即合同签订人的字段值为“销售员1（张三）”。
以上所述仅是本发明的优选实施方式，应当理解本发明并非局限于本文所披露的形式，不应看作是对其他实施例的排除，而可用于各种其他组合、修改和环境，并能够在本文所述构想范围内，通过上述教导或相关领域的技术或知识进行改动。而本领域人员所进行的改动和变化不脱离本发明的精神和范围，则都应在本发明所附权利要求的保护范围内。

Claims (10)

  1. 表单中的角色性质字段的字段值获取方法，其特征在于，包括：
    显示角色性质字段对应的候选字段值，所述候选字段值为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；
    获取字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值。
  2. 表单中的角色性质字段的字段值获取方法，其特征在于，包括：
    显示角色性质字段对应的候选字段值，所述候选字段值为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；
    获取角色字段值：从所述候选字段值中选择一个角色作为所述角色性质字段的字段值中的角色字段值；
    获取用户字段值：获取角色字段值后，自动获取所选角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所选角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。
  3. 根据权利要求2所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述字段值的获取方法还包括修改用户字段值的步骤：将当前作为用户字段值的用户替换为所述角色关联过的所有用户中的一个用户，或将当前作为用户字段值的员工替换为所述角色关联过的所有用户对应的所有员工中的一个员工。
  4. 根据权利要求2或3所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述用户通过其与角色的关联确定权限，一个员工对应一个用户，一个用户对应一个员工。
  5. 根据权利要求1所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述角色归属于部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在系统中唯一。
  6. 根据权利要求5所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述用户跨部门调岗时，取消用户与原部门内的角色的关联，将用户与新部门内的角色进行关联。
  7. 表单中的角色性质字段的字段值获取方法，其特征在于，包括：
    获取用户字段值：自动获取登录系统的当前用户或该当前用户对应的员工作为所述角色性质字段的字段值中的用户字段值；
    获取角色字段值：获取用户字段值后，若当前用户现在关联的角色只有一个，则自动获取该角色作为所述角色性质字段的字段值中的角色字段值；若当前用户现在关联的角色有两个或以上，则从当前用户现在关联的所有角色中选择一个作为所述角色性质字段的字段值中的角色字段值；所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色。
  8. 根据权利要求7所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述用户通过其与角色的关联确定权限，一个员工对应一个用户，一个用户对应一个员工。
  9. 表单中的角色性质字段的字段值获取方法，其特征在于，包括：
    员工根据其对应的用户登录系统；
    选择当前角色：在员工登录系统后，用户的默认角色为当前角色或员工选择该员工对应用户关联的所有角色中除默认角色外的一个角色作为当前角色，所述默认角色有且只有一个；
    获取角色字段值：自动获取所述当前角色作为所述角色性质字段的字段值中的角色字段值，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；
    获取用户字段值：获取角色字段值后，自动获取所述当前角色当前关联的用户作为所述角色性质字段的字段值中的用户字段值，或自动获取所述当前角色当前关联的用户对应的员工作为所述角色性质字段的字段值中的用户字段值。
  10. 根据权利要求9所述的表单中的角色性质字段的字段值获取方法，其特征在于，所述用户通过其与角色的关联确定权限，一个员工对应一个用户，一个用户对应一个员工。
PCT/CN2018/093450 2017-07-07 2018-06-28 表单中的角色性质字段的字段值获取方法 WO2019007261A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710553309.7 2017-07-07
CN201710553309.7A CN107292144A (zh) 2017-07-07 2017-07-07 表单中的角色性质字段的字段值获取方法

Publications (1)

Publication Number Publication Date
WO2019007261A1 true WO2019007261A1 (zh) 2019-01-10

Family

ID=60100954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093450 WO2019007261A1 (zh) 2017-07-07 2018-06-28 表单中的角色性质字段的字段值获取方法

Country Status (2)

Country Link
CN (2) CN107292144A (zh)
WO (1) WO2019007261A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107292144A (zh) * 2017-07-07 2017-10-24 成都牵牛草信息技术有限公司 表单中的角色性质字段的字段值获取方法
CN112632391A (zh) * 2020-12-30 2021-04-09 深圳市华傲数据技术有限公司 数据处理方法、设备及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299694A (zh) * 2007-04-30 2008-11-05 华为技术有限公司 家庭网络中访客管理的方法及系统、家庭网关
CN102004868A (zh) * 2009-09-01 2011-04-06 上海杉达学院 一种基于角色访问控制的信息系统数据存储层及组建方法
CN102930226A (zh) * 2012-10-25 2013-02-13 无锡中科泛在信息技术研发中心有限公司 细粒度客户端使用权限控制方法
CN103632082A (zh) * 2013-12-10 2014-03-12 惠州华阳通用电子有限公司 一种通用权限管理系统及方法
KR20160084997A (ko) * 2015-01-07 2016-07-15 충북대학교 산학협력단 비밀번호 기반 역할 및 권한 부여 장치 및 방법
CN106488789A (zh) * 2014-07-11 2017-03-08 科乐美数码娱乐株式会社 游戏系统、游戏控制装置、程序以及信息存储介质
CN107292144A (zh) * 2017-07-07 2017-10-24 成都牵牛草信息技术有限公司 表单中的角色性质字段的字段值获取方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7284000B2 (en) * 2003-12-19 2007-10-16 International Business Machines Corporation Automatic policy generation based on role entitlements and identity attributes
US8271527B2 (en) * 2004-08-26 2012-09-18 Illinois Institute Of Technology Refined permission constraints using internal and external data extraction in a role-based access control system
CN102053969A (zh) * 2009-10-28 2011-05-11 上海宝信软件股份有限公司 webERP用户权限管理系统
CN104462888A (zh) * 2014-12-25 2015-03-25 遵义国正科技有限责任公司 客运管理信息系统中的用户权限管理系统
CN106790060A (zh) * 2016-12-20 2017-05-31 微梦创科网络科技（中国）有限公司 一种基于角色访问控制的权限管理方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299694A (zh) * 2007-04-30 2008-11-05 华为技术有限公司 家庭网络中访客管理的方法及系统、家庭网关
CN102004868A (zh) * 2009-09-01 2011-04-06 上海杉达学院 一种基于角色访问控制的信息系统数据存储层及组建方法
CN102930226A (zh) * 2012-10-25 2013-02-13 无锡中科泛在信息技术研发中心有限公司 细粒度客户端使用权限控制方法
CN103632082A (zh) * 2013-12-10 2014-03-12 惠州华阳通用电子有限公司 一种通用权限管理系统及方法
CN106488789A (zh) * 2014-07-11 2017-03-08 科乐美数码娱乐株式会社 游戏系统、游戏控制装置、程序以及信息存储介质
KR20160084997A (ko) * 2015-01-07 2016-07-15 충북대학교 산학협력단 비밀번호 기반 역할 및 권한 부여 장치 및 방법
CN107292144A (zh) * 2017-07-07 2017-10-24 成都牵牛草信息技术有限公司 表单中的角色性质字段的字段值获取方法

Also Published As

Publication number Publication date
CN107292144A (zh) 2017-10-24
CN108875054A (zh) 2018-11-23
CN108875054B (zh) 2021-04-09

Similar Documents

Publication Publication Date Title
CN108764833B (zh) 工作流审批节点按部门设置审批角色的方法
WO2019011304A1 (zh) 基于角色获取的表单数据的授权方法
CN109214150B (zh) 基于角色的表单操作权限授权方法
WO2018214890A1 (zh) 工作流审批节点按角色设置审批角色的方法
WO2019007260A1 (zh) 表单字段值操作权限授权方法
CN107103228B (zh) 基于角色对用户的一对一的权限授权方法和系统
CN109104425B (zh) 基于时间段的操作记录查看权限的设置方法
AU2018299512A1 (en) Method for setting approval procedure based on base fields
WO2019007210A1 (zh) 一种表单的关联信息授权方法
US20200202023A1 (en) Authorization method for displaying current permissions status of all system users
WO2019019981A1 (zh) 系统中用户在信息交流单元的权限的设置方法
CN108875391B (zh) 系统中员工登录其账户后的权限显示方法
WO2019015657A1 (zh) 一种系统的考勤设置方法
WO2018205940A1 (zh) 基于角色对用户的一对一的组织结构图生成及应用方法
US11750616B2 (en) Method for authorizing approval processes and approval nodes thereof for user
WO2019011162A1 (zh) 快捷功能设置方法
WO2019011255A1 (zh) 通过第三方字段对表单字段的字段值进行授权的方法
WO2019001322A1 (zh) 基于角色的菜单授权方法
CN109033861B (zh) 系统中对授权操作者进行授权的方法
WO2019007261A1 (zh) 表单中的角色性质字段的字段值获取方法
WO2019029647A1 (zh) 系统中仓库的设置方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18827962

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18827962

Country of ref document: EP

Kind code of ref document: A1