WO2019034023A1 - Method for approver to ask for reference opinion for approval task - Google Patents

Method for approver to ask for reference opinion for approval task Download PDF

Info

Publication number
WO2019034023A1
WO2019034023A1 PCT/CN2018/100311 CN2018100311W WO2019034023A1 WO 2019034023 A1 WO2019034023 A1 WO 2019034023A1 CN 2018100311 W CN2018100311 W CN 2018100311W WO 2019034023 A1 WO2019034023 A1 WO 2019034023A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
approval
approver
user
task
Prior art date
Application number
PCT/CN2018/100311
Other languages
French (fr)
Chinese (zh)
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 WO2019034023A1 publication Critical patent/WO2019034023A1/en

Links

Classifications

    • 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
    • G06Q10/103—Workflow collaboration or project management
    • 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

Definitions

  • the invention relates to a management method for an approval task in a management system such as ERP and CRM, and particularly relates to a method for an approver to consult a reference for an approval task.
  • the approver in the approval node needs to give the approval result for the approval task.
  • the approver often needs to consult other people's opinions as a reference to give more scientific and correct approval results.
  • the traditional management system does not provide the function of consultation. If the approver needs to consult, he can only take face-to-face oral consultation or telephone or instant message consultation. It is impossible to make the approval task and the consultation reference intuitively related in the system.
  • the consultation task is managed in the system in the task mode, and it is impossible to form a valid record in the system, which is not convenient for management.
  • the object of the present invention is to overcome the deficiencies of the prior art, and to provide a method for an approver to consult for an approval task, and the approver initiates a reference request through the management system when approving the approval task, and the reference submitted by the consultant It can assist the approver to make more scientific and correct approval results, and can form an effective consultation record in the system, let the consultation task be managed in the system by task, and make the approval task and the consultation reference form an intuitive relationship. It is also easy to manage.
  • a method for an approver to consult for an approval task including the following steps: an approver obtains an approval task in an approval process; and an approver is consulted for one or more of the approval tasks. A request for a reference was initiated.
  • the approval process includes a start node, at least one approval node, and an end node: a start node: an approval process start; an approval node: an approver approves the approval task; and an end node: the approval process ends.
  • the approver includes one or more of an employee, a user, a group/class nature role, and an independent individual nature role.
  • the inquired person is a user or an employee; one user corresponds to one employee, and one employee corresponds to one user.
  • the subject to be consulted is an independent individual character, and the independent individual nature role is different from the group/class nature role.
  • an independent individual nature role can only be associated with a unique user, and one user is associated with one or more independent individual nature roles.
  • the user obtains the rights of the associated independent individual role; one user corresponds to one employee, one employee corresponds to one user, and the employee obtains the rights of the independent individual role associated with the corresponding user.
  • the method for the approver to consult the approval task for the approval task and further includes an step of setting the permission for the examinee to view the permission, and the approver sets the permission of the consulted person to consult the form field/field value of the approval task corresponding form;
  • the setting scope of the viewing authority is within the scope of viewing permission of the approver for the form field/field value of the corresponding form of the approval task.
  • the method by which the approver consults for the approval task includes the steps for the approver to fill in the remarks when initiating the request for reference.
  • each of the consulted tasks for the approval task is automatically cancelled/end.
  • the subject is given a pass/agree, a disapproval/disagreement conclusion, and/or a reference commentary for the approval task.
  • the method by which the approver consults the approval task includes the steps for the approver to evaluate the concluding comments of the respondent and/or the reference comments filled in.
  • the beneficial effects of the present invention are as follows: 1) When the approver needs to refer to the opinions of others, the reference request for consultation is initiated by the management system, and the reference submitted by the consultant can assist the approver to make a more scientific and correct examination result, and can An effective consultation record is formed in the system, so that the consultation task is managed in the system by the task mode, and the approval task is directly related to the consultation reference, which is convenient for management.
  • the respondent may be a user or employee designated by the approver.
  • the approver may designate a trusted person or a person who believes that it can provide a valid reference to the user for consultation.
  • the operation is simple, easy to use, and meets the requirements of regular use. .
  • Zhang San when Zhang San approved an office furniture procurement contract, Zhang San knew that Li Si and Wang Wu had done furniture sales work, and Zhang San could designate a consultation for Li Si and Wang Wu on the office furniture procurement contract. .
  • the respondent may be an independent individual role designated by the approver, and the employee corresponding to the user currently associated with the role provides approval opinions to the approver.
  • the general manager when the general manager approves the sales contract, the general manager can consult the “Director of Production Department 1” for the delivery time required in the contract. No matter which user is currently associated with the role, it can provide effective Approval comments.
  • the advantages of the independent individual role of the consulted person are as follows: when the employee corresponding to the role of the respondent is resigned or transferred, the original association is simply removed, and the user corresponding to the new employee is associated with the role to automatically obtain the All the currently quested tasks of the role realize the handover of the queried tasks through the association of the roles, the workload is small, the use is convenient, and the seamless docking can be realized, and the lag or omission of the handover of the quested task will not occur, and the consultation is ensured.
  • the reference is given to improve the efficiency of the work; avoiding the delay in the transfer of the task, the employee can still check the approval content and give approval opinions after leaving the company, causing confusion of the company's confidentiality and management confusion.
  • Example of resignation employee Zhang's corresponding user role "production worker 1" (independent individual role), when Zhang San leaves the post, the system administrator (or the corresponding administrator) directly cancels Zhang San's corresponding user and "production worker 1" In connection with this role, Zhang San automatically lost the task of “production worker 1” being consulted, avoiding the lag of the task of being consulted, so that Zhang San can still check the approval content and give approval opinions after leaving the company, resulting in the company. Confidential leakage and management confusion; when the new employee Li Si succeeded Zhang San’s work, directly related to Li Si’s user “production worker 1”, Li Si automatically obtained the role of “production worker 1”.
  • the task of consulting the reference does not need to redistribute the task of consulting for Li Si. The operation is simple and fast, which greatly reduces the workload.
  • Example of transfer The employee Zhang San should be transferred from the production department to the after-sales department.
  • the system administrator (or the corresponding administrator) cancels the association between the user corresponding to Zhang San and the original character “production worker 1”, and then links to the new after-sales department.
  • the role of "after-sales service personnel 3", Zhang San automatically obtained the role of "after-sales service personnel 3" is currently being consulted.
  • the approver can set the view permission of the form field/field value of the respondent's corresponding form for the approval task within the scope of the authority, and can set the form field/field value that each of the respondents can see, so as to be
  • the inquirer can see the form field/field value related to providing the reference opinion, hide the sensitive information that is not related to the reference opinion, and realize the fine management of the authority, which is more in line with the actual operation and management requirements of the enterprise.
  • the general manager approves the sales contract.
  • the form fields in the contract form include the customer name, customer contact information, contract signing time, signer, product name, product unit price, product quantity, contract amount, delivery time, logistics method, etc.
  • the manager can see all the above fields and field values in the approval task.
  • the general manager can ask Zhao Six, the director of the production department, for advice. Zhao Six can only be seen when consulting ( In the task of consulting for reference, only the field values of the three fields "product name”, “product quantity” and “delivery time” can be seen. Zhao Liu cannot see other items that are not related to the reference.
  • Field/field value including customer name, customer contact information, contract amount and other sensitive information; for the logistics method required in the contract, the general manager can consult Liu Qi, the director of the freight department, and can set Liu Qi to see only when consulting. (only visible in the task of consulting for reference) "Product Name”, “Product Quantity”, “Delivery Time”, “ “Logistics” field values of these four fields, Liu Qi can not see other field/field values that are not related to the reference provided by him.
  • the independent individual character of the present application has a one-to-one relationship with the user. In the same period, an independent individual character can only associate with a unique user, and one user associates one or more independent individual characters.
  • the advantage of this is that By associating a user to a role, you gain access (that is, the user gains access to their associated role), and the role (independent individual role) changes in permissions much less than the user permissions in the traditional mechanism.
  • the number of roles of the nature of the independent body (the nature of the post number/station number) is small. Although the employee turnover is large, the change of the post number/station number is small (even if there is no change in a certain period of time, that is, the role does not change), This will greatly simplify the user's rights management and reduce the overhead of the system.
  • the operation of dynamic management, on-the-job adjustment, etc. is simple and convenient, high in efficiency and high in reliability: the application of the entry/departure/adjustment in the authority management is simple, and when the employee/user changes, there is no need to reset the permission, the user only needs Cancel or associate a role: a user who is no longer in the role (independent individual role) cancels the role association, and the user who takes over the role is associated with the role of the role number, and the user associated with the role automatically obtains the role. Roles are consulted for tasks and operational privileges, without the need to re-authorize roles, greatly improving the efficiency, security, and reliability of system setup.
  • Zhang San due to Zhang San’s resignation or transfer, Zhang San will no longer work as a “buyer 3”, and Zhang will cancel the association with “Purchaser 3”; Li Si will take over as “Purchaser”. 3) The role of this role, only need to associate Li Si with the role, then Li Si automatically obtained the task and operation authority of the role of "Purchaser 3" being consulted.
  • 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 to the user.
  • the user's authority is often adjusted during the operation process. For example, when dealing with employee permission changes, 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 employees whose permissions have not changed. . 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 or the like to make the role or authorization more efficient than the traditional group/class nature, because the group/class role 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/class 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, and when the post is adjusted, the user is first de-associated with the role (independent individual role) in the original department (the cancelled roles can be re-associated) For other users, then associate the user with the role in the new department (independent individual role). The operation is simple and will not go wrong.
  • 1 is a schematic diagram of an approval process of the present invention
  • FIG. 2 is a schematic diagram of a manner in which a conventional system directly authorizes a user
  • FIG. 3 is a schematic diagram of a manner in which a legacy system authorizes a group/class role
  • FIG. 4 is a schematic diagram of a manner in which a conventional system directly authorizes a user and authorizes a group/class role role;
  • FIG. 5 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role.
  • the approval process includes a start node, at least one approval node (such as 5 approval nodes in Figure 1), and an end node: Start node: the approval process starts, and the initiation/application/submission workflow is used as the start node. Or the first approval node as the start node; the approval node: the approver approves the approval task; the end node: the approval process ends.
  • the reference opinion may be consulted to others.
  • the method for the approver to consult the approval task for the approval task includes the following steps: the approver obtains the approval task in the approval process, and the The approver includes one or more of an employee, a user, a group/class nature role, and an independent individual nature role; the approver initiates a request for a reference to one or more of the respondents for the approval task.
  • the reference provided by the respondent is only for the reviewer to make the approval of the approval task, and will not determine the approval result, and the approval result will still be made by the approver.
  • the management system initiates (initiating the approval task) reference request, and the reference submitted by the consultant can assist the approver to make more scientific and correct approval results, and can be in the system.
  • Form an effective consultation record let the consultation task be managed in the system in the task mode, and also make the approval task and its corresponding consultation reference form an intuitive relationship, which is convenient for management.
  • the subject is a user or an employee, one user corresponds to one employee, and one employee corresponds to one user.
  • the person being consulted is a user or employee designated by the approver.
  • the approver can designate a person who believes or a person who believes that he can provide a valid reference to the user for consultation.
  • the operation is simple, easy to use, and meets the requirements for routine use.
  • Zhang San when Zhang San approved an office furniture purchase contract, Zhang San knew that Li Si and Wang Wu had done furniture sales work, and Zhang San could designate Li Si and Wang Wu to initiate a purchase contract for the office furniture. consult.
  • the subject is an independent individual role.
  • the independent individual character is different from the group/class role, and an independent individual character can only be associated with a unique user in the same period.
  • a user associates one or more independent individual roles, the user obtains the rights of the associated independent individual nature role; one user corresponds to one employee, one employee corresponds to one user, and the employee obtains the independent individual role of the corresponding user association permission.
  • the person being consulted is an independent individual role designated by the approver, and the employee corresponding to the user currently associated with the role provides approval opinions to the approver.
  • the general manager may consult the “Director of Production Department 1” for the delivery time required in the contract, regardless of which user is currently associated with the role. Approval comments.
  • the advantages of the independent individual role of the consulted person are as follows: when the employee corresponding to the role of the respondent is resigned or transferred, the original association is simply removed, and the user corresponding to the new employee is associated with the role to automatically obtain the All the currently quested tasks of the role realize the handover of the queried tasks through the association of the roles, the workload is small, the use is convenient, and the seamless docking can be realized, and the lag or omission of the handover of the quested task will not occur, and the consultation is ensured.
  • the reference is given to improve the efficiency of the work; avoiding the delay in the transfer of the task, the employee can still check the approval content and give approval opinions after leaving the company, causing confusion of the company's confidentiality and management confusion.
  • Example of resignation employee Zhang's corresponding user role "production worker 1" (independent individual role), when Zhang San leaves the post, the system administrator (or the corresponding administrator) directly cancels Zhang San's corresponding user and "production worker 1" In connection with this role, Zhang San automatically lost the task of “production worker 1” being consulted, avoiding the lag of the task of being consulted, so that Zhang San can still check the approval content and give approval opinions after leaving the company, resulting in the company. Confidential leakage and management confusion; when the new employee Li Si succeeded Zhang San’s work, directly related to Li Si’s user “production worker 1”, Li Si automatically obtained the role of “production worker 1”.
  • the task of consulting the reference does not need to redistribute the task of consulting for Li Si. The operation is simple and fast, which greatly reduces the workload.
  • Example of transfer The employee Zhang San should be transferred from the production department to the after-sales department.
  • the system administrator (or the corresponding administrator) cancels the association between the user corresponding to Zhang San and the original character “production worker 1”, and then links to the new after-sales department.
  • the role of "after-sales service personnel 3", Zhang San automatically obtained the role of "after-sales service personnel 3" (independent individual role) is currently being consulted.
  • 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). Traditional autonomous access control has high flexibility but low security. Forced access control is highly secure but too restrictive. Role-based access control combines both ease of management and reduces the complexity, cost, and probability of errors. Therefore, it 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 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 adopts the "role-to-user one-to-many" association mechanism, and the "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 concept of position/job/type of work the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. As shown in Figure 2, the user is authorized directly, and the disadvantage is that the workload is large, the operation is frequent and troublesome; When employee changes occur (such as transfer, resignation, etc.), all the rights involved in the employee must be adjusted accordingly, especially for company management personnel, which involve many permissions, and the workload adjustment is large, complicated, and easy. Errors or omissions affect the normal operation of the company and even cause unpredictable losses.
  • the role (class/group/post/work type) is authorized (a role can be associated with multiple users), the user obtains the permission through the role, and the system operation subject is the group/class nature role; As shown in Figure 4, 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.
  • the new role involves the creation, association, and authorization of the role. Especially in the case of a large number of roles and a large number of users associated with the role, it is difficult to remember which users are associated with the role.
  • 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 The only one under the department, the number of the role is unique in the system.
  • employee adjustment management step which includes: (1) canceling the association between the employee corresponding to the original role (independent individual role); (2) after the employee corresponding to the user and after the transfer The corresponding new role (independent individual role) is associated, and the employee automatically obtains the task for which the new role is currently being consulted.
  • the following is an analysis of the advantages of authorizing a user through an independent individual role: the user determines (acquires) the right through its association with the role (independent individual role), and if the user's permission is to be modified, by adjusting the role's possession Permission to achieve the purpose of changing the permissions of the user associated with the role. Once a user associates a role, the user has all the operational rights for that role and the task currently being consulted.
  • the relationship of the role (independent individual role) to the user is one-to-one (when the role is associated with one user, other users can no longer associate the role; if the role is not associated with the user, it can be selected by other users; At the same time, a character can and can only be associated with one user).
  • a user's relationship to a role is one-to-many (one user can associate multiple roles at the same time).
  • Role definition The role does not have the nature of group/class/category/post/position/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application Equivalent to the post number (the post number here is not a post, one post may have multiple employees at the same time, and one post 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 and tasks of these two roles.
  • the concept of traditional roles is group/class/post/position/job/work type, and one role can correspond to multiple users.
  • the concept of the "role" (independent individual role) of this application is equivalent to the post number/station number, and is also similar to the role in the film and television drama: a character can only be in the same time period (childhood, juvenile, middle age%) Played by an actor, and an actor may be decorated with multiple angles.
  • the role (independent individual character role) is composed of: post name + post number.
  • workshop production workers 1, workshop production workers 2, workshop production workers 3... roles are independent individuals, equivalent to the concept of job number and station number, different from the role in the traditional authority management system, the concept of role in the traditional system It is the group/class nature of the position/position/job/type of work.
  • the following example shows the relationship between employees, users and roles (independent individual roles) after entering the company: 1.
  • New entry The employee is newly hired, and the corresponding job number/worker is directly selected for the user (employee).
  • the role of the number can be associated, for example: Zhang San joined the company (the company assigned a three-user for Zhang San), the work content is in the sales department, responsible for the sales of refrigerator products in Beijing area (the corresponding role is sales one) Under the role of "Sales Engineer 5", Zhang San users can directly select the role of "Sales Engineer 5".
  • Zhang also arranged for Zhang San to be responsible for the sales of regional TV products in Beijing (the corresponding role is to sell the role of “Sales Engineer 8” under the Ministry of Sales) and concurrently as the head of the after-sales department (corresponding to the after-sales department)
  • the three users added the roles of “sales engineer 8” under the sales department and “sales department supervisor 1” under the after-sales department.
  • Zhang San employees associated three roles, respectively.
  • Zhang San users In order to sell a "Sales Engineer 5", "Sales Engineer 8" and "After Sales Department Supervisor 1" under the after-sales department, Zhang San users have the rights and tasks of these three roles.
  • Zhang San serves as the post-sales manager (corresponding to the role of “after-sales manager” in the after-sales department) and no longer take up other jobs. Then Zhang San user is associated with the role of “after-sales manager” in the after-sales department, and cancels the three roles previously associated (Sales Engineer 5 under Sales, Sales Engineer 8 and “After Sales Manager 1” under the after-sales department) At this time, Zhang San users only have the authority and tasks of the role of “after-sales manager” under the after-sales department.
  • the authorization method of this embodiment in this embodiment, the role of the post number/station number property (independent individual role) is authorized, and the user associates the role to determine (acquire) the right, then the user authority is controlled by the simple user. - The relationship of roles is realized, the permission control is simple, easy to operate, clear and clear, and the authorization efficiency and authorization reliability are greatly improved.
  • the method for the approver to consult the approval task for the approval task further includes a step of setting the permission for the examinee to view the authority, and the approver sets the referenced form for the object to be examined for the subject to be consulted.
  • View permission of the form field/field value; the setting scope of the view permission is within the scope of view permission of the approver for the form field/field value of the corresponding form of the approval task.
  • the approver can set the view authority of the form field/field value of the respondent for the approval task corresponding form within the scope of the authority, and can set the form field/field value that each of the respondents can see, so that the subject is consulted. It can see the form field/field value related to the reference provided by it, hide the sensitive information that is not related to the reference opinion, and realize the fine management of the authority, which is more in line with the actual operation and management needs of the enterprise.
  • the general manager approves the sales contract.
  • the form fields in the contract form include the customer name, customer contact information, contract signing time, signer, product name, product unit price, product quantity, contract amount, delivery time, logistics method, etc.
  • the manager can see all the above fields and field values in the approval task.
  • the general manager can consult Zhao Lu, the director of the production department. When consulting, you can set Zhao Liu to see only (Only in the task of consulting for reference)
  • the field/field value includes sensitive information such as customer name, customer contact information, contract amount, etc.
  • the general manager can consult Liu Qi, the director of the freight department, and can set Liu Qi to see only when consulting.
  • Liu Qi the director of the freight department
  • the field values of the four fields “Logistics”, Liu Qi can not see other field/field values that are not related to the reference provided.
  • the method for the approver to consult the reference task for the approval task may further include an step of the approver filling in the request for comment when initiating the request for consulting the reference, so as to explain the information about the approval task to the consulted person.
  • each of the consulted tasks for the approval task is automatically revoked/closed, thereby avoiding wasting the time of the evaluator and doing nothing.
  • the respondent gives the conclusions and opinions of the approval/consent, disapproval/disagreement for the approval task, and can also fill in the reference comments, and the relevant explanations of the concluding opinions are given in the remarks.
  • the respondent does not give a concluding opinion, but fills in the reference comments, and the comments indicate their opinions and suggestions for the approval task.
  • the approver may evaluate the reference comments filled out by the respondent.
  • the evaluation methods may be: evaluation satisfaction/dissatisfaction, scoring, etc. (the approver may comment on the subject being consulted) And/or the reference comments filled out for evaluation).

Landscapes

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

Abstract

A method for an approver to ask for a reference opinion for an approval task, comprising: an approver acquiring an approval task in an approval flow; and the approver initiating, to one or more consulted persons for the approval task, a request for asking for a reference opinion. A consulted person is an independent individual character; one independent individual character can only be associated with a unique user in the same time period; and one user is associated with one or more independent individual characters. An approver initiates a request for asking for a reference opinion via a management system, and the reference opinion can assist the approver in making a more scientific and more accurate approval result and can form an effective query record in the system. The consulted person uses an independent individual character, and when an employee leaves the office or transfers positions, seamless joint can be realised, and the lag or omission of the handover of a consulted task cannot occur, thereby ensuring that the consulted person gives a reference opinion in a timely manner, and avoiding the leakage of secrets and chaos when managing a company.

Description

审批者针对审批任务征询参考意见的方法Method for reviewers to consult for approval tasks 技术领域Technical field
本发明涉及一种ERP、CRM等管理***中审批任务的管理方法，特别是涉及一种审批者针对审批任务征询参考意见的方法。The invention relates to a management method for an approval task in a management system such as ERP and CRM, and particularly relates to a method for an approver to consult a reference for an approval task.
背景技术Background technique
在企业运营过程中，审批流程繁多，审批节点中审批者需要针对审批任务给出其审批结果，然而审批者往往需要征询他人的意见作为参考，才能给出更科学、更正确的审批结果。传统管理***未提供征询意见功能，审批者若需征询意见只能采取面对面口头征询或电话、即时通讯征询等方式，无法在***中让审批任务与征询参考意见形成直观的关联性、也无法让征询任务以任务方式在***中进行管理、也无法在***中形成有效记录，不便于管理。In the process of enterprise operation, there are many approval processes. The approver in the approval node needs to give the approval result for the approval task. However, the approver often needs to consult other people's opinions as a reference to give more scientific and correct approval results. The traditional management system does not provide the function of consultation. If the approver needs to consult, he can only take face-to-face oral consultation or telephone or instant message consultation. It is impossible to make the approval task and the consultation reference intuitively related in the system. The consultation task is managed in the system in the task mode, and it is impossible to form a valid record in the system, which is not convenient for management.
技术问题technical problem
本发明的目的在于克服现有技术的不足，提供一种审批者针对审批任务征询参考意见的方法，审批者在审批其审批任务时通过管理***发起参考意见征询请求，被征询者提交的参考意见能协助审批者作出更科学、更正确的审批结果，且能在***中形成有效的征询记录，让征询任务以任务方式在***中进行管理，也让审批任务与征询参考意见形成直观的关联性，也便于管理。The object of the present invention is to overcome the deficiencies of the prior art, and to provide a method for an approver to consult for an approval task, and the approver initiates a reference request through the management system when approving the approval task, and the reference submitted by the consultant It can assist the approver to make more scientific and correct approval results, and can form an effective consultation record in the system, let the consultation task be managed in the system by task, and make the approval task and the consultation reference form an intuitive relationship. It is also easy to manage.
技术解决方案Technical solution
本发明的目的是通过以下技术方案来实现的：审批者针对审批任务征询参考意见的方法，包括以下步骤：审批者获取审批流程中的审批任务；审批者针对审批任务向一个或多个被征询者发起征询参考意见的请求。The object of the present invention is achieved by the following technical solutions: a method for an approver to consult for an approval task, including the following steps: an approver obtains an approval task in an approval process; and an approver is consulted for one or more of the approval tasks. A request for a reference was initiated.
所述的审批流程包括一个开始节点、至少一个审批节点、一个结束节点：开始节点：审批流程开始；审批节点：审批者对审批任务进行审批；结束节点：审批流程结束。The approval process includes a start node, at least one approval node, and an end node: a start node: an approval process start; an approval node: an approver approves the approval task; and an end node: the approval process ends.
所述的审批者包括员工、用户、组/类性质角色、独立个体性质角色中的一种或多种。The approver includes one or more of an employee, a user, a group/class nature role, and an independent individual nature role.
所述的被征询者为用户或员工；一个用户对应一个员工，一个员工对应一个用户。The inquired person is a user or an employee; one user corresponds to one employee, and one employee corresponds to one user.
所述的被征询者为独立个体性质角色，独立个体性质角色与组/类性质角色不同，同一时段一个独立个体性质角色只能关联唯一的用户，而一个用户关联一个或多个独立个体性质角色，用户获得其关联的独立个体性质角色的权限；一个用户对应一个员工，一个员工对应一个用户，员工获得其对应的用户关联的独立个体性质角色的权限。The subject to be consulted is an independent individual character, and the independent individual nature role is different from the group/class nature role. In the same period, an independent individual nature role can only be associated with a unique user, and one user is associated with one or more independent individual nature roles. The user obtains the rights of the associated independent individual role; one user corresponds to one employee, one employee corresponds to one user, and the employee obtains the rights of the independent individual role associated with the corresponding user.
审批者针对审批任务征询参考意见的方法，还包括一个审批者设置被征询者查看权限的步骤，审批者设置其所征询的被征询者针对审批任务对应表单的表单字段/字段值的查看权限；所述查看权限的设置范围在该审批者针对该审批任务对应表单的表单字段/字段值的查看权限范围之内。The method for the approver to consult the approval task for the approval task, and further includes an step of setting the permission for the examinee to view the permission, and the approver sets the permission of the consulted person to consult the form field/field value of the approval task corresponding form; The setting scope of the viewing authority is within the scope of viewing permission of the approver for the form field/field value of the corresponding form of the approval task.
审批者针对审批任务征询参考意见的方法，还包括一个审批者在发起征询参考意见的请求时填写征询备注的步骤。The method by which the approver consults for the approval task, and also includes the steps for the approver to fill in the remarks when initiating the request for reference.
当审批者给出针对审批任务的审批结果后，各被征询者关于该审批任务的被征询任务自动撤销/结束。After the approver gives the approval result for the approval task, each of the consulted tasks for the approval task is automatically cancelled/end.
所述的被征询者针对审批任务给出通过/同意、不通过/不同意的结论意见和/或填写参考意见备注。The subject is given a pass/agree, a disapproval/disagreement conclusion, and/or a reference commentary for the approval task.
审批者针对审批任务征询参考意见的方法，还包括一个审批者对被征询者的结论意见和/或所填写的参考意见备注进行评价的步骤。The method by which the approver consults the approval task, and also includes the steps for the approver to evaluate the concluding comments of the respondent and/or the reference comments filled in.
有益效果Beneficial effect
本发明的有益效果是：1）审批者需要参考他人意见时，通过管理***发起参考意见征询请求，被征询者提交的参考意见能协助审批者作出更科学、更正确的审批结果，且能在***中形成有效的征询记录，让征询任务以任务方式在***中进行管理，也让审批任务与征询参考意见形成直观的关联性，便于管理。The beneficial effects of the present invention are as follows: 1) When the approver needs to refer to the opinions of others, the reference request for consultation is initiated by the management system, and the reference submitted by the consultant can assist the approver to make a more scientific and correct examination result, and can An effective consultation record is formed in the system, so that the consultation task is managed in the system by the task mode, and the approval task is directly related to the consultation reference, which is convenient for management.
2）被征询者可以是由审批者指定的用户或员工，审批者可以指定信任的人或其认为能向其提供有效参考意见的人进行意见的征询，操作简单，使用方便，符合常规使用需求。2) The respondent may be a user or employee designated by the approver. The approver may designate a trusted person or a person who believes that it can provide a valid reference to the user for consultation. The operation is simple, easy to use, and meets the requirements of regular use. .
例如：张三在审批一个办公家具采购合同时，张三知道员工中李四和王五都曾做过家具销售工作，张三可指定向李四和王五发起针对办公家具采购合同的意见征询。For example, when Zhang San approved an office furniture procurement contract, Zhang San knew that Li Si and Wang Wu had done furniture sales work, and Zhang San could designate a consultation for Li Si and Wang Wu on the office furniture procurement contract. .
3）被征询者可以是由审批者指定的独立个体性质角色，由角色当前所关联的用户对应的员工向审批者提供审批意见。3) The respondent may be an independent individual role designated by the approver, and the employee corresponding to the user currently associated with the role provides approval opinions to the approver.
例如：总经理在审批销售合同时，针对合同中要求的交货时间，总经理可向“生产部主任1”这一角色征询意见，无论该角色当前关联的是哪个用户，都能提供有效的审批意见。For example, when the general manager approves the sales contract, the general manager can consult the “Director of Production Department 1” for the delivery time required in the contract. No matter which user is currently associated with the role, it can provide effective Approval comments.
被征询者采用独立个体性质角色的优势如下：被征询者的角色关联的用户对应的员工离职、调岗时，只需解除原关联，将新任员工对应的用户关联到该角色即可自动获得该角色当前所有被征询任务，通过角色的关联顺带就实现了被征询任务的交接，工作量小，使用方便，而且能够实现无缝对接，不会出现被征询任务交接的滞后或遗漏，确保被征询者及时给出参考意见，提高工作效率；避免被征询任务交接滞后使得员工离职后仍能查看审批内容并给出审批意见，造成公司机密的泄露和管理的混乱。The advantages of the independent individual role of the consulted person are as follows: when the employee corresponding to the role of the respondent is resigned or transferred, the original association is simply removed, and the user corresponding to the new employee is associated with the role to automatically obtain the All the currently quested tasks of the role realize the handover of the queried tasks through the association of the roles, the workload is small, the use is convenient, and the seamless docking can be realized, and the lag or omission of the handover of the quested task will not occur, and the consultation is ensured. In a timely manner, the reference is given to improve the efficiency of the work; avoiding the delay in the transfer of the task, the employee can still check the approval content and give approval opinions after leaving the company, causing confusion of the company's confidentiality and management confusion.
离职举例：员工张三对应的用户关联角色“生产工人1”（独立个体性质角色），张三离职时，***管理员（或相应管理员）直接取消张三对应的用户与“生产工人1”这一角色的关联，则张三自动失去“生产工人1”被征询参考意见的任务，避免被征询参考意见的任务交接滞后使得张三离职后仍能查看审批内容并给出审批意见，造成公司机密的泄露和管理的混乱；新入职员工李四接替张三的工作时，直接让李四对应的用户关联“生产工人1”，则李四自动获得了“生产工人1”这一角色当前被征询参考意见的任务，无需再为李四重新分配征询参考意见的任务，操作简单快捷，大大减少了工作量。Example of resignation: employee Zhang's corresponding user role "production worker 1" (independent individual role), when Zhang San leaves the post, the system administrator (or the corresponding administrator) directly cancels Zhang San's corresponding user and "production worker 1" In connection with this role, Zhang San automatically lost the task of “production worker 1” being consulted, avoiding the lag of the task of being consulted, so that Zhang San can still check the approval content and give approval opinions after leaving the company, resulting in the company. Confidential leakage and management confusion; when the new employee Li Si succeeded Zhang San’s work, directly related to Li Si’s user “production worker 1”, Li Si automatically obtained the role of “production worker 1”. The task of consulting the reference does not need to redistribute the task of consulting for Li Si. The operation is simple and fast, which greatly reduces the workload.
调岗举例：员工张三要从生产部调岗到售后部，***管理员（或相应管理员）取消张三对应的用户与原角色“生产工人1”的关联，再关联到售后部的新角色“售后服务人员3”，张三则自动获得了“售后服务人员3”这一角色当前被征询参考意见的任务。Example of transfer: The employee Zhang San should be transferred from the production department to the after-sales department. The system administrator (or the corresponding administrator) cancels the association between the user corresponding to Zhang San and the original character “production worker 1”, and then links to the new after-sales department. The role of "after-sales service personnel 3", Zhang San automatically obtained the role of "after-sales service personnel 3" is currently being consulted.
4）审批者可在其权限范围内设置被征询者针对审批任务对应表单的表单字段/字段值的查看权限，可针对性设置每个被征询者能够看到的表单字段/字段值，使被征询者能够看到与其提供参考意见相关的表单字段/字段值，隐藏与其提供参考意见不相关的敏感信息，实现了权限精细化管理，更符合企业实际运营管理需求。4) The approver can set the view permission of the form field/field value of the respondent's corresponding form for the approval task within the scope of the authority, and can set the form field/field value that each of the respondents can see, so as to be The inquirer can see the form field/field value related to providing the reference opinion, hide the sensitive information that is not related to the reference opinion, and realize the fine management of the authority, which is more in line with the actual operation and management requirements of the enterprise.
例如：总经理审批销售合同，合同表单中的表单字段包括客户名称、客户联系方式、合同签订时间、签单人、产品名称、产品单价、产品数量、合同金额、交货时间、物流方式等（总经理在该审批任务中能够看到以上所有字段及字段值），针对合同中要求的交货时间，总经理可向生产部主任赵六征询意见，征询意见时可设置赵六仅能看到（在该次征询参考意见的任务中仅能看到）“产品名称”、“产品数量”和“交货时间”这三个字段的字段值，赵六无法看到其它与其提供参考意见不相关的字段/字段值，包括客户名称、客户联系方式、合同金额等敏感信息；针对合同中要求的物流方式，总经理可向货运部主任刘七征询意见，征询意见时可设置刘七仅能看到（在该次征询参考意见的任务中仅能看到）“产品名称”、“产品数量”、“交货时间”、“物流方式”这四个字段的字段值，刘七无法看到其它与其提供参考意见不相关的字段/字段值。For example, the general manager approves the sales contract. The form fields in the contract form include the customer name, customer contact information, contract signing time, signer, product name, product unit price, product quantity, contract amount, delivery time, logistics method, etc. The manager can see all the above fields and field values in the approval task. For the delivery time required in the contract, the general manager can ask Zhao Six, the director of the production department, for advice. Zhao Six can only be seen when consulting ( In the task of consulting for reference, only the field values of the three fields "product name", "product quantity" and "delivery time" can be seen. Zhao Liu cannot see other items that are not related to the reference. Field/field value, including customer name, customer contact information, contract amount and other sensitive information; for the logistics method required in the contract, the general manager can consult Liu Qi, the director of the freight department, and can set Liu Qi to see only when consulting. (only visible in the task of consulting for reference) "Product Name", "Product Quantity", "Delivery Time", " "Logistics" field values of these four fields, Liu Qi can not see other field/field values that are not related to the reference provided by him.
5）本申请独立个体性质角色对用户是一对一的关系，同一时段一个独立个体性质角色只能关联唯一的用户，一个用户关联一个或多个独立个体性质角色，这样做的好处是，只要将用户关联到角色即可获得权限（即用户获得其关联的角色的权限），而且角色（独立个体性质角色）的权限变更比传统机制中的用户权限变更要少得多。独立体性质（岗位号/工位号性质）的角色数量变化小，虽然员工流动大，但岗位号/工位号的变化小（甚至在一定时段内是没有变化的，即角色没有变化），这样将极大简化用户的权限管理，减少***的开销。5) The independent individual character of the present application has a one-to-one relationship with the user. In the same period, an independent individual character can only associate with a unique user, and one user associates one or more independent individual characters. The advantage of this is that By associating a user to a role, you gain access (that is, the user gains access to their associated role), and the role (independent individual role) changes in permissions much less than the user permissions in the traditional mechanism. The number of roles of the nature of the independent body (the nature of the post number/station number) is small. Although the employee turnover is large, the change of the post number/station number is small (even if there is no change in a certain period of time, that is, the role does not change), This will greatly simplify the user's rights management and reduce the overhead of the system.
6）动态管理、入职调岗等的操作简单方便，效率高，可靠性高：入职/离职/调岗在权限管理中的应用简单，当员工/用户发生变化时不用重新设置权限，用户只需取消或关联角色即可：不再任职该角色（独立个体性质角色）的用户就取消该角色关联，接手任职该角色的用户关联该岗位号性质的角色，关联该角色的用户自动就获得了该角色被征询意见的任务和操作权限，无需对角色进行重新授权，极大地提高了***设置的效率、安全性和可靠性。6) The operation of dynamic management, on-the-job adjustment, etc. is simple and convenient, high in efficiency and high in reliability: the application of the entry/departure/adjustment in the authority management is simple, and when the employee/user changes, there is no need to reset the permission, the user only needs Cancel or associate a role: a user who is no longer in the role (independent individual role) cancels the role association, and the user who takes over the role is associated with the role of the role number, and the user associated with the role automatically obtains the role. Roles are consulted for tasks and operational privileges, without the need to re-authorize roles, greatly improving the efficiency, security, and reliability of system setup.
举例：因张三用户离职或调岗等原因，张三不再做“采购员3”这个角色的工作，则将张三取消与“采购员3”的关联；另外李四接手做“采购员3”这个角色的工作，只需将李四关联该角色，则李四自动获得了“采购员3”这个角色被征询意见的任务和操作权限。For example: due to Zhang San’s resignation or transfer, Zhang San will no longer work as a “buyer 3”, and Zhang will cancel the association with “Purchaser 3”; Li Si will take over as “Purchaser”. 3) The role of this role, only need to associate Li Si with the role, then Li Si automatically obtained the task and operation authority of the role of "Purchaser 3" being consulted.
7）传统的权限管理机制将角色定义为组、工种、类等性质，角色对用户是一对多的关系，在实际的***使用过程中，因为在运营过程中经常需要对用户的权限进行调整，比如：在处理员工权限变化的时候，角色关联的某个员工的权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对***使用方的损失。7) 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 to the user. In the actual system use process, the user's authority is often adjusted during the operation process. For example, when dealing with employee permission changes, 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 employees whose permissions have not changed. . 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.
但在本申请的方法下，因为角色是一个独立的个体，则可以选择改变角色权限即可达到目的。本申请的方法，虽然看起来在***初始化时会增加工作量，但可以通过复制等方法，使其创建角色或授权的效率高于传统组/类性质的角色，因为不用考虑组/类性质角色在满足关联用户时的共通性，本申请方案会让权限设置清晰，明了；尤其是在***使用一段时间后（用户/角色权限动态变化），该申请方案能为***使用方大幅度提高***使用中的权限管理效率，使动态授权更简单，更方便，更清晰、明了，提高权限设置的效率和可靠性。However, under the method of the present application, since the role is an independent individual, the role permission can be changed to achieve the goal. Although the method of the present application seems to increase the workload when the system is initialized, it can be made by copying or the like to make the role or authorization more efficient than the traditional group/class nature, because the group/class role is not considered. In the commonality of the related users, 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.
8）传统组/类性质的角色授权方法容易出错，本申请方法大幅降低了授权出错的几率，因为本申请方法只需考虑作为独立个体的角色，而不用考虑传统方法下关联该组性质角色的多个用户有哪些共通性。即使授权出错也只影响关联到该角色的那一个用户，而传统以组性质的角色则会影响关联到该角色的所有用户。即使出现权限授权错误，本申请的修正方法简单、时间短，而传统以组性质的角色在修正错误时需要考虑关联到该角色的所有用户的权限共通性，在功能点多的情况下不仅修改麻烦、复杂，非常容易出错，且很多情况下只能新创建角色才能解决。8) The traditional group/class 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.
9）在传统以组为性质的角色授权方法下，若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，若要关联新的用户，无法准确判断应当如何选择关联。本申请方法的角色本身就具有岗位号/工位号的性质（独立个体性质角色），选择一目了然。9) Under the traditional group-based role authorization method, if the role has more privilege function points, it takes a long time to remember the specific privilege of the role, and it is more difficult to remember the privilege difference between the roles with similar privilege. To associate a new user, you cannot accurately determine how the association should be selected. The role of the method of the present application itself has the nature of the post number/station number (independent individual role), and the choice is clear at a glance.
10）调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。10) When adjusting the post, if you want to assign a lot of rights of the transferred users to other users, you must separate the rights of the transferred users and create roles to associate with others. Users, such an operation is not only complicated and time consuming, but also prone to errors.
本申请方法则为：被调岗用户关联了几个角色，在调岗时，首先取消用户与原部门内的角色（独立个体性质角色）的关联（被取消的这几个角色可以被重新关联给其他用户），然后将用户与新部门内的角色（独立个体性质角色）进行关联即可。操作简单，不会出错。The method of the present application is as follows: the transferred user associates several roles, and when the post is adjusted, the user is first de-associated with the role (independent individual role) in the original department (the cancelled roles can be re-associated) For other users, then associate the user with the role in the new department (independent individual role). The operation is simple and will not go wrong.
附图说明DRAWINGS
图1为本发明审批流程示意图；1 is a schematic diagram of an approval process of the present invention;
图2为传统***直接对用户进行授权的方式示意图；2 is a schematic diagram of a manner in which a conventional system directly authorizes a user;
图3为传统***对组/类性质角色进行授权的方式示意图；3 is a schematic diagram of a manner in which a legacy system authorizes a group/class role;
图4为传统***对用户直接授权和对组/类性质角色授权相结合的方式示意图；4 is a schematic diagram of a manner in which a conventional system directly authorizes a user and authorizes a group/class role role;
图5为本发明***通过独立个体性质角色对用户进行授权的方式示意图。FIG. 5 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role.
本发明的最佳实施方式BEST MODE FOR CARRYING OUT THE INVENTION
下面结合附图进一步详细描述本发明的技术方案，但本发明的保护范围不局限于以下所述。The technical solution of the present invention will be described in further detail below with reference to the accompanying drawings, but the scope of protection of the present invention is not limited to the following.
如图1所示，审批流程包括一个开始节点、至少一个审批节点（如图1中审批节点有5个）、一个结束节点：开始节点：审批流程开始，发起/申请/提交工作流作为开始节点，或者由第一个审批节点作为开始节点；审批节点：审批者对审批任务进行审批；结束节点：审批流程结束。As shown in Figure 1, the approval process includes a start node, at least one approval node (such as 5 approval nodes in Figure 1), and an end node: Start node: the approval process starts, and the initiation/application/submission workflow is used as the start node. Or the first approval node as the start node; the approval node: the approver approves the approval task; the end node: the approval process ends.
在审批节点审批者对审批任务进行审批时，可以向他人征询参考意见，具体的，审批者针对审批任务征询参考意见的方法，包括以下步骤：审批者获取审批流程中的审批任务，所述的审批者包括员工、用户、组/类性质角色、独立个体性质角色中的一种或多种；审批者针对审批任务向一个或多个被征询者发起征询参考意见的请求。When the approval node approver approves the approval task, the reference opinion may be consulted to others. Specifically, the method for the approver to consult the approval task for the approval task includes the following steps: the approver obtains the approval task in the approval process, and the The approver includes one or more of an employee, a user, a group/class nature role, and an independent individual nature role; the approver initiates a request for a reference to one or more of the respondents for the approval task.
被征询者提供的参考意见只是供审批者进行审批任务审批时参考，不会由此决定审批结果，审批结果仍由审批者作出。The reference provided by the respondent is only for the reviewer to make the approval of the approval task, and will not determine the approval result, and the approval result will still be made by the approver.
审批者需要参考他人意见时，通过管理***发起（对该审批任务发起）参考意见征询请求，被征询者提交的参考意见能协助审批者作出更科学、更正确的审批结果，且能在***中形成有效的征询记录，让征询任务以任务方式在***中进行管理，也让该审批任务与其对应的征询参考意见形成直观的关联性，便于管理。When the approver needs to refer to other people's opinions, the management system initiates (initiating the approval task) reference request, and the reference submitted by the consultant can assist the approver to make more scientific and correct approval results, and can be in the system. Form an effective consultation record, let the consultation task be managed in the system in the task mode, and also make the approval task and its corresponding consultation reference form an intuitive relationship, which is convenient for management.
【实施例1】本实施例中，被征询者为用户或员工，一个用户对应一个员工，一个员工对应一个用户。[Embodiment 1] In this embodiment, the subject is a user or an employee, one user corresponds to one employee, and one employee corresponds to one user.
被征询者是由审批者指定的用户或员工，审批者可以指定信任的人或其认为能向其提供有效参考意见的人进行意见的征询，操作简单，使用方便，符合常规使用需求。The person being consulted is a user or employee designated by the approver. The approver can designate a person who believes or a person who believes that he can provide a valid reference to the user for consultation. The operation is simple, easy to use, and meets the requirements for routine use.
例如：张三在审批一个办公家具采购合同时，张三知道员工中李四和王五都曾做过家具销售工作，张三可指定向李四和王五发起针对该办公家具采购合同的意见征询。For example, when Zhang San approved an office furniture purchase contract, Zhang San knew that Li Si and Wang Wu had done furniture sales work, and Zhang San could designate Li Si and Wang Wu to initiate a purchase contract for the office furniture. consult.
【实施例2】本实施例中，被征询者为独立个体性质角色，如图5所示，独立个体性质角色与组/类性质角色不同，同一时段一个独立个体性质角色只能关联唯一的用户，而一个用户关联一个或多个独立个体性质角色，用户获得其关联的独立个体性质角色的权限；一个用户对应一个员工，一个员工对应一个用户，员工获得其对应的用户关联的独立个体性质角色的权限。[Embodiment 2] In this embodiment, the subject is an independent individual role. As shown in FIG. 5, the independent individual character is different from the group/class role, and an independent individual character can only be associated with a unique user in the same period. And a user associates one or more independent individual roles, the user obtains the rights of the associated independent individual nature role; one user corresponds to one employee, one employee corresponds to one user, and the employee obtains the independent individual role of the corresponding user association permission.
被征询者是由审批者指定的独立个体性质角色，由角色当前所关联的用户对应的员工向审批者提供审批意见。The person being consulted is an independent individual role designated by the approver, and the employee corresponding to the user currently associated with the role provides approval opinions to the approver.
例如：总经理在审批销售合同时，针对该合同中要求的交货时间，总经理可向“生产部主任1”这一角色征询意见，无论该角色当前关联的是哪个用户，都能提供有效的审批意见。For example, when the general manager approves the sales contract, the general manager may consult the “Director of Production Department 1” for the delivery time required in the contract, regardless of which user is currently associated with the role. Approval comments.
被征询者采用独立个体性质角色的优势如下：被征询者的角色关联的用户对应的员工离职、调岗时，只需解除原关联，将新任员工对应的用户关联到该角色即可自动获得该角色当前所有被征询任务，通过角色的关联顺带就实现了被征询任务的交接，工作量小，使用方便，而且能够实现无缝对接，不会出现被征询任务交接的滞后或遗漏，确保被征询者及时给出参考意见，提高工作效率；避免被征询任务交接滞后使得员工离职后仍能查看审批内容并给出审批意见，造成公司机密的泄露和管理的混乱。The advantages of the independent individual role of the consulted person are as follows: when the employee corresponding to the role of the respondent is resigned or transferred, the original association is simply removed, and the user corresponding to the new employee is associated with the role to automatically obtain the All the currently quested tasks of the role realize the handover of the queried tasks through the association of the roles, the workload is small, the use is convenient, and the seamless docking can be realized, and the lag or omission of the handover of the quested task will not occur, and the consultation is ensured. In a timely manner, the reference is given to improve the efficiency of the work; avoiding the delay in the transfer of the task, the employee can still check the approval content and give approval opinions after leaving the company, causing confusion of the company's confidentiality and management confusion.
离职举例：员工张三对应的用户关联角色“生产工人1”（独立个体性质角色），张三离职时，***管理员（或相应管理员）直接取消张三对应的用户与“生产工人1”这一角色的关联，则张三自动失去“生产工人1”被征询参考意见的任务，避免被征询参考意见的任务交接滞后使得张三离职后仍能查看审批内容并给出审批意见，造成公司机密的泄露和管理的混乱；新入职员工李四接替张三的工作时，直接让李四对应的用户关联“生产工人1”，则李四自动获得了“生产工人1”这一角色当前被征询参考意见的任务，无需再为李四重新分配征询参考意见的任务，操作简单快捷，大大减少了工作量。Example of resignation: employee Zhang's corresponding user role "production worker 1" (independent individual role), when Zhang San leaves the post, the system administrator (or the corresponding administrator) directly cancels Zhang San's corresponding user and "production worker 1" In connection with this role, Zhang San automatically lost the task of “production worker 1” being consulted, avoiding the lag of the task of being consulted, so that Zhang San can still check the approval content and give approval opinions after leaving the company, resulting in the company. Confidential leakage and management confusion; when the new employee Li Si succeeded Zhang San’s work, directly related to Li Si’s user “production worker 1”, Li Si automatically obtained the role of “production worker 1”. The task of consulting the reference does not need to redistribute the task of consulting for Li Si. The operation is simple and fast, which greatly reduces the workload.
调岗举例：员工张三要从生产部调岗到售后部，***管理员（或相应管理员）取消张三对应的用户与原角色“生产工人1”的关联，再关联到售后部的新角色“售后服务人员3”，张三则自动获得了“售后服务人员3” （独立个体性质角色）这一角色当前被征询参考意见的任务。Example of transfer: The employee Zhang San should be transferred from the production department to the after-sales department. The system administrator (or the corresponding administrator) cancels the association between the user corresponding to Zhang San and the original character “production worker 1”, and then links to the new after-sales department. The role of "after-sales service personnel 3", Zhang San automatically obtained the role of "after-sales service personnel 3" (independent individual role) is currently being consulted.
基于角色的访问控制（RBAC）是近年来研究最多、思想最成熟的一种数据库权限管理机制，它被认为是替代传统的强制访问控制（MAC）和自主访问控制（DAC）的理想候选。传统的自主访问控制的灵活性高但是安全性低，强制访问控制安全性高但是限制太强；基于角色的访问控制两者兼具，不仅易于管理而且降低了复杂性、成本和发生错误的概率，因而近年来得到了极大的发展。基于角色的访问控制（RBAC）的基本思想是根据企业组织视图中不同的职能岗位划分不同的角色，将数据库资源的访问权限封装在角色中，用户通过被赋予不同的角色来间接访问数据库资源。Role-based access control (RBAC) 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). Traditional autonomous access control has high flexibility but low security. Forced access control is highly secure but too restrictive. Role-based access control combines both ease of management and reduces the complexity, cost, and probability of errors. Therefore, it 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 enterprise organization view, encapsulate the access rights of database resources in roles, and indirectly access database resources by being assigned different roles.
在大型应用***中往往都建有大量的表和视图，这使得对数据库资源的管理和授权变得十分复杂。由用户直接管理数据库资源的存取和权限的收授是十分困难的，它需要用户对数据库结构的了解非常透彻，并且熟悉SQL语言的使用，而且一旦应用***结构或安全需求有所变动，都要进行大量复杂而繁琐的授权变动，非常容易出现一些意想不到的授权失误而引起的安全漏洞。因此，为大型应用***设计一种简单、高效的权限管理方法已成为***和***用户的普遍需求。A large number of tables and views are often built in large application systems, which makes the management and authorization of database resources very complicated. It is very difficult for the user to directly manage the access and permissions of the database resources. It requires the user to have a very thorough understanding of the database structure and is familiar with the use of the SQL language, and once the application system structure or security requirements have changed, To carry out a large number of complex and cumbersome authorization changes, it is very easy to have some security vulnerabilities caused by unexpected authorization errors. Therefore, designing a simple and efficient rights management method for large-scale application systems has become a common requirement for system and system users.
基于角色的权限控制机制能够对***的访问权限进行简单、高效的管理，极大地降低了***权限管理的负担和代价，而且使得***权限管理更加符合应用***的业务管理规范。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.
然而，传统基于角色的用户权限管理均采用“角色对用户一对多”的关联机制，其“角色”为组/类性质，即一个角色可以同时对应/关联多个用户，角色类似于岗位/职位/职务/工种等概念，这种关联机制下对用户权限的授权基本分为以下三种形式：1、如图2所示，直接对用户授权，缺点是工作量大、操作频繁且麻烦；当发生员工变动（如调岗、离职等），该员工涉及到的所有权限必须要作相应调整，特别是对于公司管理人员，其涉及到的权限多，权限调整的工作量大、繁杂，容易出错或遗漏，影响企业的正常运营，甚至造成不可预估的损失。However, the traditional role-based user rights management adopts the "role-to-user one-to-many" association mechanism, and the "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 concept of position/job/type of work, the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. As shown in Figure 2, the user is authorized directly, and the disadvantage is that the workload is large, the operation is frequent and troublesome; When employee changes occur (such as transfer, resignation, etc.), all the rights involved in the employee must be adjusted accordingly, especially for company management personnel, which involve many permissions, and the workload adjustment is large, complicated, and easy. Errors or omissions affect the normal operation of the company and even cause unpredictable losses.
2、如图3所示，对角色（类/组/岗位/工种性质）进行授权（一个角色可以关联多个用户），用户通过角色获得权限，***操作主体是组/类性质角色；3、如图4所示，以上两种方式结合。2. As shown in Figure 3, the role (class/group/post/work type) is authorized (a role can be associated with multiple users), the user obtains the permission through the role, and the system operation subject is the group/class nature role; As shown in Figure 4, the above two methods are combined.
以上的表述中，2、3均需要对类/组性质的角色进行授权，而通过类/组/岗位/工种性质的角色进行授权的方式有以下缺点：1、用户权限变化时的操作难：在实际的***使用过程中，在企业运营过程中经常需要对用户的权限进行调整，比如：在处理员工权限变化时，角色关联的某个员工权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对***使用方的损失。In the above expressions, 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 operation when the user rights change is difficult: In the actual system use process, the user's authority is often adjusted during the operation of the enterprise. For example, when the employee's authority changes, the employee's authority associated with the role changes. We cannot change the individual employee's authority. And change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed. 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.
员工/用户的权限发生变化时，要么员工/用户脱离角色，要么新增角色来满足工作要求。第一种方式的缺陷同上述“直接对用户授权”方式的缺陷。第二种方式，新增角色便涉及到角色的新建、关联、授权工作，特别在角色多、角色关联的用户也多的情况下，角色具体关联了哪些用户是很难记住的。When the employee/user's permissions change, either the employee/user leaves the role or the role is added to meet the job requirements. The defect of the first method is the same as the above-mentioned "direct authorization to the user" method. In the second way, the new role involves the creation, association, and authorization of the role. Especially in the case of a large number of roles and a large number of users associated with the role, it is difficult to remember which users are associated with the role.
2、要长期记住角色（传统角色）包含的具体权限难：若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，相近角色的权限也很容易混淆；若要关联新的用户，无法准确判断应当如何选择关联。2. It is difficult to remember the specific permissions of the role (traditional role) for a long time: if the role has more permission function points, it is difficult to remember the specific permissions of the role, and it is more difficult to remember the roles between the roles with similar permissions. Permission differences, permissions of similar roles are also very confusing; if you want to associate new users, you can't accurately determine how to choose associations.
3、因为用户权限变化，则会造成角色（传统角色）创建越来越多（若不创建新角色，则会大幅增加直接对用户的授权），更难分清各角色权限的具体差别。3, because the user permissions change, it will cause more and more roles (traditional roles) to be created (if you do not create a new role, it will greatly increase the authorization directly to the user), it is more difficult to distinguish the specific differences of the roles of each role.
4、调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色（传统角色）来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。4. When adjusting the post, if you want to assign a lot of permissions of the transferred users to other users, you must separate the permissions of the transferred users and create roles (traditional roles). Associated with several other users, such an operation is not only complicated and time consuming, but also prone to errors.
本实施例中，在角色（独立个体性质角色）创建时或角色创建后为该角色选择一个部门，则该角色归属于该部门，根据角色的工作内容对角色进行授权，且该角色的名称在该部门下唯一，该角色的编号在***中唯一。In this embodiment, when a role (independent individual role) is created or a role is selected for the role after the role is created, 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 The only one under the department, the number of the role is unique in the system.
如果员工需要调岗，还包括一个员工调岗管理步骤，具体包括：（1）取消员工对应的用户与原角色（独立个体性质角色）的关联；（2）将员工对应的用户与调岗后相应的新角色（独立个体性质角色）进行关联，员工自动获得该新角色当前被征询参考意见的任务。If the employee needs to be transferred, it also includes an employee adjustment management step, which includes: (1) canceling the association between the employee corresponding to the original role (independent individual role); (2) after the employee corresponding to the user and after the transfer The corresponding new role (independent individual role) is associated, and the employee automatically obtains the task for which the new role is currently being consulted.
以下对通过独立个体性质角色对用户进行授权所具备的优势进行分析：用户通过其与角色（独立个体性质角色）的关联确定（获得）权限，如果要修改用户的权限，通过调整角色所拥有的权限以达到改变关联了该角色的用户的权限的目的。一旦用户关联角色后，该用户就拥有了该角色的所有操作权限和当前被征询参考意见的任务。The following is an analysis of the advantages of authorizing a user through an independent individual role: the user determines (acquires) the right through its association with the role (independent individual role), and if the user's permission is to be modified, by adjusting the role's possession Permission to achieve the purpose of changing the permissions of the user associated with the role. Once a user associates a role, the user has all the operational rights for that role and the task currently being consulted.
角色（独立个体性质角色）对用户的关系为一对一（该角色与一个用户关联时，其他用户则不能再关联该角色；若该角色未被用户关联，则可以被其他用户选择关联；即同一时段，一个角色能且只能被一个用户关联）。用户对角色的关系为一对多（一个用户可以同时关联多个角色）。The relationship of the role (independent individual role) to the user is one-to-one (when the role is associated with one user, other users can no longer associate the role; if the role is not associated with the user, it can be selected by other users; At the same time, a character can and can only be associated with one user). A user's relationship to a role is one-to-many (one user can associate multiple roles at the same time).
角色的定义：角色不具有组/类/类别/岗位/职位/职务/工种等性质，而是一个非集合的性质，角色具有唯一性，角色是独立存在的独立个体；在企事业单位应用中相当于岗位号（此处的岗位号非岗位，一个岗位同时可能有多个员工，而同一时段一个岗位号只能对应一个员工）。Role definition: The role does not have the nature of group/class/category/post/position/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application Equivalent to the post number (the post number here is not a post, one post may have multiple employees at the same time, and one post number can only correspond to one employee at the same time).
举例：某个公司***中可创建如下角色：总经理、副总经理1、副总经理2、北京销售一部经理、北京销售二部经理、北京销售三部经理、上海销售工程师1、上海销售工程师2、上海销售工程师3、上海销售工程师4、上海销售工程师5……用户与角色的关联关系：若该公司员工张三任职该公司副总经理2，同时任职北京销售一部经理，则张三需要关联的角色为副总经理2和北京销售一部经理，张三拥有了这两个角色的权限和任务。For example: 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... User-role relationship: If the company employee 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 and tasks of these two roles.
传统角色的概念是组/类/岗位/职位/职务/工种性质，一个角色能够对应多个用户。而本申请“角色”（独立个体性质角色）的概念相当于岗位号/工位号，也类同于影视剧中的角色：一个角色在同一时段（童年、少年、中年……）只能由一个演员来饰演，而一个演员可能会分饰多角。The concept of traditional roles is group/class/post/position/job/work type, and one role can correspond to multiple users. The concept of the "role" (independent individual role) of this application is equivalent to the post number/station number, and is also similar to the role in the film and television drama: a character can only be in the same time period (childhood, juvenile, middle age...) Played by an actor, and an actor may be decorated with multiple angles.
在创建角色（独立个体性质角色）之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。After creating a role (independent individual role), 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.
所述角色（独立个体性质角色）的构成为：岗位名+岗内编号。例如：车间生产工人1、车间生产工人2、车间生产工人3……角色是独立个体，相当于岗位号、工位号的概念，不同于传统权限管理体系中的角色，传统体系中角色的概念是岗位/职位/职务/工种等的组/类性质。The role (independent individual character role) is composed of: post name + post number. For example: workshop production workers 1, workshop production workers 2, workshop production workers 3... roles are independent individuals, equivalent to the concept of job number and station number, different from the role in the traditional authority management system, the concept of role in the traditional system It is the group/class nature of the position/position/job/type of work.
以下举例员工张三进入某公司后，员工、用户与角色（独立个体性质角色）之间的关系为：1、新入职：员工新入职，直接为该用户（员工）选择相应的岗位号/工位号的角色进行关联即可，例：张三入职公司（公司为张三分配了一个张三用户），工作内容是在销售一部，负责北京区域冰箱产品的销售（对应的角色是销售一部下的“销售工程师5”这个角色），则张三用户直接选择“销售工程师5”这个角色关联即可。The following example shows the relationship between employees, users and roles (independent individual roles) after entering the company: 1. New entry: The employee is newly hired, and the corresponding job number/worker is directly selected for the user (employee). The role of the number can be associated, for example: Zhang San joined the company (the company assigned a three-user for Zhang San), the work content is in the sales department, responsible for the sales of refrigerator products in Beijing area (the corresponding role is sales one) Under the role of "Sales Engineer 5", Zhang San users can directly select the role of "Sales Engineer 5".
2、增加职位：张三工作一段时间后，公司还安排张三负责北京区域电视产品的销售（对应的角色是销售一部下的“销售工程师8”这个角色）并兼任售后部主管（对应售后部主管1这个角色），则张三用户再增加关联销售一部下的“销售工程师8”和售后部下的“售后部主管1”这两个角色，此时，张三员工关联了三个角色，分别为销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”，张三用户则拥有了这三个角色的权限和任务。2. Adding positions: After working for a period of time, Zhang also arranged for Zhang San to be responsible for the sales of regional TV products in Beijing (the corresponding role is to sell the role of “Sales Engineer 8” under the Ministry of Sales) and concurrently as the head of the after-sales department (corresponding to the after-sales department) In the role of supervisor 1, the three users added the roles of “sales engineer 8” under the sales department and “sales department supervisor 1” under the after-sales department. At this time, Zhang San employees associated three roles, respectively. In order to sell a "Sales Engineer 5", "Sales Engineer 8" and "After Sales Department Supervisor 1" under the after-sales department, Zhang San users have the rights and tasks of these three roles.
3、减少职位：又过了一段时间，公司决定让张三任职售后部经理（对应售后部下“售后部经理”这个角色），且不再兼任其他工作。则张三用户关联售后部下“售后部经理”这个角色，同时取消此前关联的三个角色（销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”），此时，张三用户只拥有售后部下“售后部经理”这个角色的权限和任务。3. Reducing the position: After a while, the company decided to let Zhang San serve as the post-sales manager (corresponding to the role of “after-sales manager” in the after-sales department) and no longer take up other jobs. Then Zhang San user is associated with the role of “after-sales manager” in the after-sales department, and cancels the three roles previously associated (Sales Engineer 5 under Sales, Sales Engineer 8 and “After Sales Manager 1” under the after-sales department) At this time, Zhang San users only have the authority and tasks of the role of “after-sales manager” under the after-sales department.
4、角色权限的调整（针对角色本身所拥有的权限的调整）：如公司决定增加售后部经理的权限，则只需增加对售后部经理这个角色的授权即可，则张三用户因为售后部经理这个角色的权限增加了，张三用户的权限也增加了。4, the adjustment of the role permissions (for the adjustment of the permissions of the role itself): If the company decides to increase the authority of the after-sales manager, then only need to increase the authorization of the role of the after-sales manager, then Zhang San users because of the after-sales department The authority of the manager has increased, and the permissions of Zhang San users have also increased.
5、离职：一年后，张三离职了，则取消张三用户与售后部下“售后部经理”这个角色的关联即可。5. Resignation: After one year, Zhang San resigned, and the relationship between Zhang San users and the post-sales department manager of the after-sales department can be cancelled.
举例：公司在动态的经营中，职员的入职、离职是经常持续发生的，但岗位号/工位号的变化非常少(甚至在一定时期内是没有变化的)。For example: in the dynamic operation of the company, the entry and exit of the staff are often continued, but the change of the post number/station number is very small (even within a certain period of time).
传统授权方法：在***功能点多的情况下，以传统的组/类性质的角色进行授权，不仅授权工作量大，繁杂，而且很容易出错，甚至出错了在短时间内都不容易发现，容易对***使用方造成损失。Traditional authorization method: In the case of a large number of system functions, authorization in the traditional group/class role, not only the authorization workload is large, complicated, but also easy to make mistakes, even if it is wrong, it is not easy to find in a short time. It is easy to cause damage to the system user.
本实施例授权方法：本实施例是对岗位号/工位号性质的角色（独立个体性质角色）进行授权，用户关联角色而确定（获得）权限，则对用户权限的控制，通过简单的用户-角色的关联关系来实现，让权限控制变得简单、易操作，清晰明了，大幅度提高了授权效率和授权可靠性。The authorization method of this embodiment: in this embodiment, the role of the post number/station number property (independent individual role) is authorized, and the user associates the role to determine (acquire) the right, then the user authority is controlled by the simple user. - The relationship of roles is realized, the permission control is simple, easy to operate, clear and clear, and the authorization efficiency and authorization reliability are greatly improved.
【实施例3】本实施例中，审批者针对审批任务征询参考意见的方法，还包括一个审批者设置被征询者查看权限的步骤，审批者设置其所征询的被征询者针对审批任务对应表单的表单字段/字段值的查看权限；所述查看权限的设置范围在该审批者针对该审批任务对应表单的表单字段/字段值的查看权限范围之内。[Embodiment 3] In the embodiment, the method for the approver to consult the approval task for the approval task further includes a step of setting the permission for the examinee to view the authority, and the approver sets the referenced form for the object to be examined for the subject to be consulted. View permission of the form field/field value; the setting scope of the view permission is within the scope of view permission of the approver for the form field/field value of the corresponding form of the approval task.
审批者可在其权限范围内设置被征询者针对审批任务对应表单的表单字段/字段值的查看权限，可针对性设置每个被征询者能够看到的表单字段/字段值，使被征询者能够看到与其提供参考意见相关的表单字段/字段值，隐藏与其提供参考意见不相关的敏感信息，实现了权限精细化管理，更符合企业实际运营管理需求。The approver can set the view authority of the form field/field value of the respondent for the approval task corresponding form within the scope of the authority, and can set the form field/field value that each of the respondents can see, so that the subject is consulted. It can see the form field/field value related to the reference provided by it, hide the sensitive information that is not related to the reference opinion, and realize the fine management of the authority, which is more in line with the actual operation and management needs of the enterprise.
例如：总经理审批销售合同，合同表单中的表单字段包括客户名称、客户联系方式、合同签订时间、签单人、产品名称、产品单价、产品数量、合同金额、交货时间、物流方式等（总经理在该审批任务中能够看到以上所有字段及字段值），针对该合同中要求的交货时间，总经理可向生产部主任赵六征询意见，征询意见时可设置赵六仅能看到（在该次征询参考意见的任务中仅能看到）“产品名称”、“产品数量”和“交货时间”这三个字段的字段值，赵六无法看到其它与其提供参考意见不相关的字段/字段值，包括客户名称、客户联系方式、合同金额等敏感信息；针对合同中要求的物流方式，总经理可向货运部主任刘七征询意见，征询意见时可设置刘七仅能看到（在该次征询参考意见的任务中仅能看到）“产品名称”、“产品数量”、“交货时间”、“物流方式”这四个字段的字段值，刘七无法看到其它与其提供参考意见不相关的字段/字段值。For example, the general manager approves the sales contract. The form fields in the contract form include the customer name, customer contact information, contract signing time, signer, product name, product unit price, product quantity, contract amount, delivery time, logistics method, etc. The manager can see all the above fields and field values in the approval task. For the delivery time required in the contract, the general manager can consult Zhao Lu, the director of the production department. When consulting, you can set Zhao Liu to see only (Only in the task of consulting for reference) The field values of the three fields "product name", "product quantity" and "delivery time", Zhao Liu can not see other irrelevant reference The field/field value includes sensitive information such as customer name, customer contact information, contract amount, etc. For the logistics method required in the contract, the general manager can consult Liu Qi, the director of the freight department, and can set Liu Qi to see only when consulting. To (only in the task of consulting for reference) "product name", "product quantity", "delivery time", The field values of the four fields "Logistics", Liu Qi can not see other field/field values that are not related to the reference provided.
本实施例中，审批者针对审批任务征询参考意见的方法，还可以包括一个审批者在发起征询参考意见的请求时填写征询备注的步骤，以便向被征询者说明审批任务相关信息等。In this embodiment, the method for the approver to consult the reference task for the approval task may further include an step of the approver filling in the request for comment when initiating the request for consulting the reference, so as to explain the information about the approval task to the consulted person.
作为优选，当审批者给出针对审批任务的审批结果后，各被征询者关于该审批任务的被征询任务自动撤销/结束，避免浪费被征询者时间做无用功。Preferably, when the approver gives the approval result for the approval task, each of the consulted tasks for the approval task is automatically revoked/closed, thereby avoiding wasting the time of the evaluator and doing nothing.
进一步的，被征询者针对审批任务给出通过/同意、不通过/不同意的结论意见，可同时填写参考意见备注，备注中给出其结论意见的相关说明。Further, the respondent gives the conclusions and opinions of the approval/consent, disapproval/disagreement for the approval task, and can also fill in the reference comments, and the relevant explanations of the concluding opinions are given in the remarks.
或者是，被征询者不给出结论意见，但填写参考意见备注，备注中说明其针对该审批任务的意见和建议等。Or, the respondent does not give a concluding opinion, but fills in the reference comments, and the comments indicate their opinions and suggestions for the approval task.
如果被征询者填写了参考意见备注，审批者可对被征询者所填写的参考意见备注进行评价，评价方式可以是：评价满意/不满意、打分等（审批者可对被征询者的结论意见和/或所填写的参考意见备注进行评价）。If the respondent fills in the reference comments, the approver may evaluate the reference comments filled out by the respondent. The evaluation methods may be: evaluation satisfaction/dissatisfaction, scoring, etc. (the approver may comment on the subject being consulted) And/or the reference comments filled out for evaluation).
以上所述仅是本发明的优选实施方式，应当理解本发明并非局限于本文所披露的形式，不应看作是对其他实施例的排除，而可用于各种其他组合、修改和环境，并能够在本文所述构想范围内，通过上述教导或相关领域的技术或知识进行改动。而本领域人员所进行的改动和变化不脱离本发明的精神和范围，则都应在本发明所附权利要求的保护范围内。The above is only a preferred embodiment of the present invention, and it should be understood that the present invention is not limited to the forms disclosed herein, and is not to be construed as being limited to the other embodiments, but may be used in various other combinations, modifications and environments. Modifications can be made by the techniques or knowledge of the above teachings or related art within the scope of the teachings herein. All changes and modifications made by those skilled in the art are intended to be within the scope of the appended claims.

Claims (10)

  1. 审批者针对审批任务征询参考意见的方法，其特征在于，包括以下步骤：审批者获取审批流程中的审批任务；The method for the approver to consult the approval task for the approval task, characterized in that the method includes the following steps: the approver obtains the approval task in the approval process;
    审批者针对审批任务向一个或多个被征询者发起征询参考意见的请求。The approver initiates a request for a reference to one or more of the respondents for the approval task.
  2. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：所述的审批流程包括一个开始节点、至少一个审批节点、一个结束节点：开始节点：审批流程开始；The method according to claim 1, wherein the approval process includes a start node, at least one approval node, and an end node: a start node: an approval process starts;
    审批节点：审批者对审批任务进行审批；Approval node: The approver approves the approval task;
    结束节点：审批流程结束。End node: The approval process ends.
  3. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：所述的审批者包括员工、用户、组/类性质角色、独立个体性质角色中的一种或多种。The method according to claim 1, wherein the approver includes one or more of an employee, a user, a group/class nature role, and an independent individual nature role.
  4. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：所述的被征询者为用户或员工；一个用户对应一个员工，一个员工对应一个用户。The method for requesting an appraisal for an approval task according to claim 1, wherein the subject is a user or an employee; one user corresponds to one employee, and one employee corresponds to one user.
  5. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：所述的被征询者为独立个体性质角色，独立个体性质角色与组/类性质角色不同，同一时段一个独立个体性质角色只能关联唯一的用户，而一个用户关联一个或多个独立个体性质角色，用户获得其关联的独立个体性质角色的权限；一个用户对应一个员工，一个员工对应一个用户，员工获得其对应的用户关联的独立个体性质角色的权限。The method according to claim 1, wherein the subject is an independent individual character, and the independent individual character is different from the group/class role, and is independent during the same period. An individual-type role can only be associated with a unique user, and a user is associated with one or more independent individual-type roles, and the user obtains the rights of his or her associated independent individual-type role; one user corresponds to one employee, one employee corresponds to one user, and the employee obtains The permissions of the corresponding individual nature roles associated with the user.
  6. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：还包括一个审批者设置被征询者查看权限的步骤，审批者设置其所征询的被征询者针对审批任务对应表单的表单字段/字段值的查看权限；所述查看权限的设置范围在该审批者针对该审批任务对应表单的表单字段/字段值的查看权限范围之内。The method for claiming a reference for an approval task according to claim 1, further comprising: a step of setting an access authority to view the permission of the consultee, and the approver sets the respondent to be consulted for the approval task. The view permission of the form field/field value of the form; the setting range of the view permission is within the scope of the view authority of the form field/field value of the corresponding form of the approver for the approval task.
  7. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：还包括一个审批者在发起征询参考意见的请求时填写征询备注的步骤。The method according to claim 1, wherein the approver requests the reference for the approval task, and further comprises the step of filling in the remarks by an approver when initiating the request for the reference.
  8. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：当审批者给出针对审批任务的审批结果后，各被征询者关于该审批任务的被征询任务自动撤销/结束。The method for claiming a reference for an approval task according to claim 1, wherein when the approver gives an approval result for the approval task, each of the consulted tasks for the approval task is automatically revoked/ End.
  9. 根据权利要求1所述的审批者针对审批任务征询参考意见的方法，其特征在于：所述的被征询者针对审批任务给出通过/同意、不通过/不同意的结论意见和/或填写参考意见备注。The method according to claim 1, wherein the subject is given a pass/consent, a disapproval/disagree conclusion, and/or a reference for the approval task. Comments note.
  10. 根据权利要求9所述的审批者针对审批任务征询参考意见的方法，其特征在于：还包括一个审批者对被征询者的结论意见和/或所填写的参考意见备注进行评价的步骤。The method of claim 9, wherein the approver consults the approval task, and further comprises the step of evaluating, by the approver, the commented opinion of the consulted person and/or the commentary comment filled in.
PCT/CN2018/100311 2017-08-14 2018-08-13 Method for approver to ask for reference opinion for approval task WO2019034023A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710694054.6A CN107480948A (en) 2017-08-14 2017-08-14 Approver is directed to the method that examination ＆ approval task seeks the opinion of advisory opinion
CN201710694054.6 2017-08-14

Publications (1)

Publication Number Publication Date
WO2019034023A1 true WO2019034023A1 (en) 2019-02-21

Family

ID=60600345

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/100311 WO2019034023A1 (en) 2017-08-14 2018-08-13 Method for approver to ask for reference opinion for approval task

Country Status (2)

Country Link
CN (2) CN107480948A (en)
WO (1) WO2019034023A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110363497A (en) * 2019-07-02 2019-10-22 北京启迪区块链科技发展有限公司 A kind of checking method, device, equipment and storage medium

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107480948A (en) * 2017-08-14 2017-12-15 成都牵牛草信息技术有限公司 Approver is directed to the method that examination ＆ approval task seeks the opinion of advisory opinion
CN110991901A (en) * 2019-12-05 2020-04-10 上海凯京信达科技集团有限公司 Task allocation method, computer storage medium and electronic device
CN111178842A (en) * 2019-12-27 2020-05-19 中国航空工业集团公司沈阳飞机设计研究所 Product examination system
CN112446682A (en) * 2020-11-30 2021-03-05 泰康保险集团股份有限公司 Contract approval method and device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104484617A (en) * 2014-12-05 2015-04-01 中国航空工业集团公司第六三一研究所 Database access control method on basis of multi-strategy integration
CN106485388A (en) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 The right management method of business approval system and device
CN106779619A (en) * 2016-12-30 2017-05-31 全民互联科技（天津）有限公司 A kind of examination ＆ verification for improving business approval is endorsed method and system
CN106779430A (en) * 2016-12-23 2017-05-31 重庆足下科技有限公司 The method and management equipment of a kind of Work Process Management
CN107480948A (en) * 2017-08-14 2017-12-15 成都牵牛草信息技术有限公司 Approver is directed to the method that examination ＆ approval task seeks the opinion of advisory opinion

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101699480A (en) * 2009-11-05 2010-04-28 金蝶软件（中国）有限公司 Hierarchical relationship-based approval flow establishing method, hierarchical relationship-based service flow processing method, hierarchical relationship-based approval flow establishing device, and hierarchical relationship-based service processing device
CN103093289A (en) * 2011-10-27 2013-05-08 镇江雅迅软件有限责任公司 Method for implementing approval process by multiple people
KR20140115764A (en) * 2013-03-22 2014-10-01 박영우 Electronic approval method and system and computer readable medium storing an electronic approval program

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104484617A (en) * 2014-12-05 2015-04-01 中国航空工业集团公司第六三一研究所 Database access control method on basis of multi-strategy integration
CN106485388A (en) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 The right management method of business approval system and device
CN106779430A (en) * 2016-12-23 2017-05-31 重庆足下科技有限公司 The method and management equipment of a kind of Work Process Management
CN106779619A (en) * 2016-12-30 2017-05-31 全民互联科技（天津）有限公司 A kind of examination ＆ verification for improving business approval is endorsed method and system
CN107480948A (en) * 2017-08-14 2017-12-15 成都牵牛草信息技术有限公司 Approver is directed to the method that examination ＆ approval task seeks the opinion of advisory opinion

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110363497A (en) * 2019-07-02 2019-10-22 北京启迪区块链科技发展有限公司 A kind of checking method, device, equipment and storage medium

Also Published As

Publication number Publication date
CN109102253A (en) 2018-12-28
CN107480948A (en) 2017-12-15
CN109102253B (en) 2021-04-27

Similar Documents

Publication Publication Date Title
WO2019034023A1 (en) Method for approver to ask for reference opinion for approval task
WO2019029650A1 (en) Form data operation auditing method
US20230419265A1 (en) Method based on form fields for arranging examination and approval roles at workflow examination and approval nodes
CN108764833B (en) Method for setting approval roles according to departments by workflow approval nodes
CN108694557B (en) Workflow and method for setting form field operation authority of approval node thereof
WO2018224024A1 (en) Efficient approval method for workflow approval node
WO2018196876A1 (en) Workflow control method and system based on one-to-one correspondence between roles and users
WO2018214889A1 (en) Countersign-based method for setting up approval node in approval process
WO2019011220A1 (en) Method for setting approval procedure based on base fields
WO2018214890A1 (en) Role-based method for setting approval role for workflow approval node
WO2018205942A1 (en) Method for setting approval roles according to department levels on workflow approval nodes
WO2019007292A1 (en) Role-based form operation authority granting method
WO2019007260A1 (en) Method for authorizing operation permissions of form field values
JP7318894B2 (en) How to authorize the operation privileges for the statistics column table
WO2018214828A1 (en) Voting-based method for setting approval node in approval process
WO2019029648A1 (en) Improved rbac right mechanism-based approval task transfer method
WO2019015539A1 (en) Method for authorizing form data operation authority
WO2019015656A1 (en) System dispatching method
WO2018219230A1 (en) Approval workflow entrusting and re-entrusting method
WO2018192557A1 (en) Permission granting method and system based on one-to-one correspondence between roles and users
WO2019011162A1 (en) Shortcut function setting method
CN108985648B (en) Management method for transaction processing in management system
WO2018224023A1 (en) Method for displaying permission after employee logs into account thereof in system
WO2019019980A1 (en) Forum management method
WO2019029500A1 (en) Column value-based separate authorization method for statistical list operations

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: 18846570

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18846570

Country of ref document: EP

Kind code of ref document: A1