CN108764691B

CN108764691B - Setting method of approval node in approval process based on consultation

Info

Publication number: CN108764691B
Application number: CN201810496667.3A
Authority: CN
Inventors: 陈达志
Original assignee: Chengdu Qianniucao Information Technology Co Ltd
Current assignee: Chengdu Qianniucao Information Technology Co Ltd
Priority date: 2017-05-23
Filing date: 2018-05-22
Publication date: 2023-04-25
Anticipated expiration: 2038-05-22
Also published as: CN108764691A; CN107122921A; WO2018214889A1

Abstract

The invention discloses a method for setting approval nodes in an approval process based on a countersignature, which comprises the following sequential steps: the first step: setting an approval node approval mode as a consultation, and summarizing the consultation opinions of all the approval roles of the nodes by the consultation node to provide a reference for the approval roles of the following approval nodes; and a second step of: one or more approval roles of the countersign node are set. The countersign node gathers the countersign opinions and provides powerful reference for the approval roles of the subsequent approval nodes. The main body of the approval operation in the workflow is a role, and the role is an independent individual, even if staff/user variation occurs, only new staff is required to be re-associated with the role in the approval process; or staff approval authority is changed, the role approval authority is adjusted in a targeted manner, the resetting/adjusting process is not needed, the setting is convenient, errors or omission can be avoided, the normal operation of an enterprise can not be influenced, and the reliability of workflow is greatly improved.

Description

Setting method of approval node in approval process based on consultation

Technical Field

The invention relates to an approval node approval method of an ERP (Enterprise resource planning) and other management software systems, in particular to a setting method of approval nodes based on a consultation in an approval process.

Background

Role-based access control (RBAC) is a database rights management mechanism that has been most studied and thought of in recent years and is considered to be an ideal candidate for replacing traditional Mandatory Access Control (MAC) and autonomous access control (DAC). The traditional autonomous access control has high flexibility but low security, and the forced access control has high security but strong limitation; both role-based access controls are easy to manage and reduce complexity, cost and probability of errors, and have thus been greatly developed in recent years. The basic idea of role-based access control (RBAC) is to divide different roles according to different functional posts in an enterprise organization view, encapsulate access rights of database resources in the roles, and users indirectly access the database resources by being given different roles.

Numerous tables and views are often built into large application systems, which makes management and authorization of database resources very complex. The direct management of access and authorization of database resources by users is very difficult, requires the users to have very thorough knowledge of the database structure and to be familiar with the use of the SQL language, and once the application system structure or security requirements change, a great deal of complex and tedious authorization changes are performed, so that security holes caused by unexpected authorization errors are very easy to occur. Therefore, designing a simple and efficient rights management method for large application systems has become a popular need for systems and system users.

The role-based authority control mechanism can simply and efficiently manage the access authority of the system, greatly reduces the burden and cost of the authority management of the system, and ensures that the authority management of the system more accords with the service management specification of an application system.

However, the traditional role-based user authority management and workflow control methods all adopt a 'role-to-user one-to-many' association mechanism, wherein the 'role' is of group/class nature, namely, one role can simultaneously correspond to/associate a plurality of users, the roles are similar to the concepts of posts/positions/work types and the like, and the authorization of the user authority under the association mechanism is basically divided into the following three forms: 1. as shown in fig. 1, the user is directly authorized, and the disadvantages are large workload, frequent and troublesome operation; the approval operation main body of the approval node in the approval process is a user, the workflow approval node directly selects staff/users as the approval main body, when staff change (such as post adjustment, job departure and the like) occurs, all processes related to the staff have to be correspondingly adjusted, especially for company management staff, the approval processes related to the staff are more, the workload of process adjustment is large and complicated, errors or omission are easy to occur, the normal operation of enterprises is influenced, and even unpredictable losses are caused.

Even if only the approval authority of the employee changes, corresponding adjustment needs to be made to the process related to the employee, and similar problems exist.

2. As shown in fig. 2, the authority is given to the colors (class/group/post/job property) (one character can be associated with a plurality of users), the users obtain the authority through the characters, and the approval operation subject is the group/class property character; 3. as shown in fig. 3, the above two modes are combined.

In the above description, 2 and 3 each need to authorize the roles of class/group property, and the manner of authorizing and workflow controlling by the roles of class/group/post/job property has the following disadvantages: 1. the operation is difficult when the user permission changes: in practical system use, the rights of the user need to be adjusted in the operation process, for example: when dealing with the change of employee rights, the authority of a certain employee related to a role is changed, and we cannot change the authority of the whole role due to the change of the authority of the individual employee, because the role is also related to other employees with unchanged authorities. To cope with this situation, therefore, either a new role is created to satisfy the employee whose authority is changed, or the employee is directly authorized (taken out of role) according to the authority requirements. The two processing modes have the advantages that the time required for the role authorization is long under the condition of more role authorities, the mistakes are easy to make, the operation of a user is tedious and troublesome, and the mistakes are easy to cause the loss of the user of the system.

When the approval authority of the staff/user changes, the staff/user is separated from the role, and the workflow approval node directly selects the staff/user as an approval main body, or the role is newly added to meet the requirement of the approval process. In the first way, when staff changes (such as job adjustment, job departure, etc.) occur, all the processes related to the staff must be correspondingly adjusted, especially for company management staff, the approval processes related to the staff are more, the workload of process adjustment is large and complex, errors or omission are easy to occur, the normal operation of enterprises is affected, and even unpredictable losses are caused. Even if only the approval authority of the employee changes, corresponding adjustment needs to be made to the process related to the employee, and similar problems exist. In the second way, the newly added roles relate to the new, association and authorization work of the roles, and particularly under the conditions that the roles are more and the users associated with the roles are more, the roles are particularly associated with which users are hard to remember.

2. It is difficult to remember the specific rights contained by the roles for a long time: if the authority function points of the roles are more, the specific authority of the roles is difficult to remember after a long time, the authority difference between the roles with similar authorities is more difficult to remember, and the authorities of the similar roles are easy to be confused; if a new user is to be associated, it cannot be accurately determined how the association should be selected.

3. Because the user rights change, more and more roles are created (if no new roles are created, the authorization of the user is greatly increased), and the specific differences of the rights of the roles are more difficult to separate.

4. When the user is on duty, if a plurality of authorities of the user to be on duty are allocated to other users to be born, the authorities of the user to be on duty must be distinguished during processing, roles are respectively re-created to be associated with the other users, and the operation is complex and time-consuming and is easy to generate errors.

Disclosure of Invention

The invention aims to overcome the defects of the prior art, and provides a method for setting approval nodes in an approval process based on a consultation, wherein the approval mode of the approval nodes can be selected (set) as the consultation, and the consultation nodes gather the consultation opinions of all approval roles of the nodes and provide powerful references for the approval roles of the following approval nodes; by adopting the role-based approval process control method, the main body of approval operation in the workflow is a role, and when the staff/users change, the users are only required to be re-associated with the role in the approval process, or the permission of the role is purposefully adjusted, so that the process is not required to be reset, and the configuration is convenient.

The aim of the invention is realized by the following technical scheme: the method for setting the approval node in the approval process based on the consultation comprises the following sequential steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes; the consultation includes agreement/passing (positive property), disagreement/not passing (negative property); and a second step of: one or more approval roles of the countersign node are set.

The approval roles are independent individuals, and are not groups/classes, and one approval role can only be associated with a unique user in the same time period, and one user is associated with one or more approval roles.

Only after all approval roles related to the meeting node submit the meeting comments, the subsequent steps of the approval process can be entered; the countersign node obtains the summary of the countersign opinions of all approval roles of the node, and no matter how the countersign opinions are, the countersign node can not reject the approval flow.

In the approval process, the process cannot be ended by the countersignature node, and at least one non-countersignature approval node exists in the subsequent nodes of the countersignature node.

The method for setting the approval node in the approval process based on the countersignature further comprises the step of setting a responsible role for the countersignature node, wherein the responsible role selects the next-level circulation node of the countersignature node during countersignature, and when the next-level circulation node has a plurality of options, the responsible role selects one of the circulation nodes.

The method for setting the approval node in the approval process based on the countersignature further comprises a step of setting the examination authority of the approval role to the form field content related to the approval process, wherein the examination authority of different approval roles of the same countersignature node to the form field content can be different.

After the approval mode of the approval node is set as the approval, all the approval roles related to the approval node have no modification authority on the form field content of the approval process.

The generation of the approval process comprises the following steps: s1: constructing a three-layer structure model of user-role-authority, wherein: role layer: the operation main body of the flow approval in the workflow is a role, each role is an independent individual, and is not a group/class, one role can only be associated with a unique user in the same period, and one user is associated with one or more roles; rights layer: the method is composed of rights required to be used in workflow execution, and the rights are directly authorized to roles; user layer: the user determines approval tasks in the approval process through the associated roles, and performs approval operation with the authority of the associated roles; s2: generating an approval process based on the three-layer structure model, wherein one approval process comprises a starting node, at least one approval node and an ending node: starting node: the approval process begins; approval node: setting an approval mode of an approval node, selecting an approval role, and authorizing the approval role; end node: ending the approval process; s3: and the user determines the approval task to be processed according to the associated role and performs approval operation according to the authority of the associated role.

The second step adopts an approval role setting method based on form fields and levels, and specifically comprises a step of setting a system organization structure and a step of setting approval roles according to department levels: the step of setting the system organization structure comprises the following substeps: SS1: creating departments and roles contained in the system organization structure; SS2: setting hierarchical relations among all departments, and setting department management roles of all departments; the step of setting approval roles according to department level comprises the following steps: SSS1, selecting to conduct approval role setting in a level mode; SSS2, selecting one of a role property field, a department property field or a submitting role of the approval process in a corresponding form of the approval process as a level main body; SSS3, filling in specific level values N, wherein N is a positive integer greater than or equal to 0 (the value of N can also be replaced by other symbols, such as a, b, c, d, b is one level greater than a, c is two levels greater than a, d is three levels greater than a, and the like): (1) Selecting a role property field in a corresponding form of the approval process as a level main body, and judging the level by taking a role corresponding to the field as a judging standard: (1) when n=0, the role corresponding to the field takes on the approval role of the approval node; (2) when n=1, the department management role of the department where the role corresponding to the field is located takes on the approval role of the approval node; if the role corresponding to the field is a department management role of the department where the field is located, taking the department management role of the higher-level department of the department where the role corresponding to the field is located as an approval role of the approval node; (3) when n=2, the department master role of the department of the superior department of the department where the role corresponding to the field is located takes on the approval role of the approval node; (4) when n=3, the department master role of the department of the upper level department of the department where the role corresponding to the field is located takes on the approval role of the approval node; (5) when n=4, the department master role of the upper level department of the department where the role corresponding to the field is located takes on the approval role of the approval node; (6) and so on; (7) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node; (8) when n is more than or equal to 1, setting a role corresponding to the field as a department master role of a department where the field is located, and when the department has no previous-stage department, approving the approval node by a designated group; (2) Selecting department property fields in the corresponding form of the approval process as a level main body, and judging the level by taking departments corresponding to the fields as judgment standards: (1) when n=0, the department management role of the department corresponding to the field takes on the approval role of the approval node; (2) when n=1, the department master role of the upper level department of the department corresponding to the field takes on the approval role of the approval node; (3) when n=2, the department master role of the department of the upper level of the department corresponding to the field takes on the approval role of the approval node; (4) when n=3, the department master role of the upper level department of the department corresponding to the field takes on the approval role of the approval node; (5) and so on; (6) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node; (7) when n is more than or equal to 1, setting an approval node to be approved by a designated group when a department corresponding to the field has no previous-stage department; (3) Selecting a submitting role of the approval process as a level main body, and judging the level by taking the submitting role as a judging standard: (1) when n=0, the role submitted by the workflow approval process acts as the approval role of the approval node; (2) when n=1, submitting a department management role of a department where the role is located by the workflow approval process to take an approval role of the approval node; if the submitting role is a department management role of the department where the submitting role is located, the department management role of the superior department of the department where the submitting role is located takes on the approval role of the approval node; (3) when n=2, submitting a department master role of a higher-level department of the department where the role is located by the workflow approval process to serve as an approval role of the approval node; (4) when n=3, submitting a department master role of a higher-level department of the department where the role is located by the workflow approval process to take the approval role of the approval node; (5) when n=4, submitting a department master role of a superior department of a department where the role is located by a workflow approval process to take an approval role of the approval node; (6) and so on; (7) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node; (8) when n is more than or equal to 1, setting a submitting role as a department management role of a department where the submitting role is located, and when the department has no previous-stage department, approving the approval node by a designated group; the specified group approval includes one of three cases: (1) a designated group is made up of one or more approving roles; (2) The designated group is determined by department level, only the level main body selected by the approval node can be used when the level main body is selected, and the level value n can be set to 0; (3) The designated group is determined by department level, the level main body can select autonomously, one or more designated nodes are included in the designated group, the designated node of the next stage is required to be set when the level value n of the designated node is not 0, until the designated group setting of the approval node is completed when the level value n of the designated node is 0.

The method for setting the approval node in the approval process based on the consultation comprises the following sequential steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes; and a second step of: setting one or more approval roles of the countersign node; the method also comprises the step of setting the countersign node as an anonymous countersign, wherein after the anonymous countersign, other non-self-approving roles cannot see the countersign opinions submitted by the approving roles except that the approving roles can see the countersign opinions of the self-approving roles.

The beneficial effects of the invention are as follows: 1. the approval mode of the approval node can be selected (set) as a consultation, and the consultation node gathers the consultation opinions of all the approval roles of the nodes and provides powerful references for the approval roles of the following approval nodes.

For example: before signing a contract, the salesperson 5 can initiate a countersignature process (i.e. the approval process comprises a countersignature node), and can select a sales part, a production part and a financial part to countersignature expression opinions (i.e. select roles representing the three departments and express the countersignature opinions of the respective departments), and the countersignature opinions must be submitted completely before entering the next step, and the countersignature opinions given by the general manager can be referred to during approval.

The difference between the countersign and the vote is: the countersign only solicits people to provide comments, only gathers comments and provides reference for subsequent approval, and the approval process cannot be refused no matter how the countersign comments are. When voting, the approval result of the approval node is determined by the voting result of the voter, and an approval result is obtained: approval procedures may be rejected with/without approval or without approval.

2. The viewing authority of different approval roles of the same countersignature node on the contents of the form fields can be different, so that the method is more convenient to use, has a wide application range, is convenient to hide partial sensitive fields, and avoids information leakage.

For example: for a contract approval process, the sales-related approval roles in the countersign node may be set to be able to view all fields; the production-related approval role may be set to view only the product model field, the product number field, the technical index field, the delivery time field in the contract form; the finance-related approver may be configured to view only the product model, product unit price, contract amount, billing information, and payment method fields in the contract form.

3. The approval roles must be selected after the approval mode is determined, so that when the approval roles are selected first, some approval roles are prevented from having modification permission on the form field content, and once the form field content is modified, the approval cannot be realized, because each approval role is approved in parallel, and modification of form data can influence approval of other approval roles. After the approval mode is determined as the countersign, the system limits all the involved approval roles to have no form modification authority, and ensures objective representation of countersign contents.

Examples: if the contract is signed before signing, 5 approval roles are set, the contract amount is 10 ten thousand, and if the approval roles are selected first, a certain approval role A in the approval roles has modification authority on the amount, the contract amount is modified to 8 ten thousand, the contract amount seen by other approval roles during approval is changed to 8 ten thousand, and the approval is not meaningful based on the modified contract content.

4. When the approval node has only one approval character, a meeting mode can be selected, so that the approval character has only rights for expressing comments and cannot modify the contents of the form.

5. The anonymous countersign function is provided, after the anonymous countersign function is set, besides the approval roles can see the countersign opinions of the approval roles, other non-self approval roles cannot see the countersign opinions submitted by the approval roles, so that the approval roles are prevented from being affected mutually, and the authenticity and the credibility of the countersign result are ensured.

6. The traditional level approval mode only takes approval flow submitting roles as judgment standards to judge department levels, other roles or departments involved in the form cannot be customized to serve as standards for judging department levels, and certain use limitations exist.

Examples: for a contract approval process, the signing role of the contract is called off, so that the colleague initiates approval of the contract for him, and the system considers the colleague as the submitting role of the process, and when the approval is performed according to the level, the judgment of the level is based on the colleague, and the department and the position where the signing role of the contract is located cannot be objectively reflected. For example, when the signing role of the contract is salesperson 1 in the market department, the colleague role is salesperson 1 in the research and development department, and the contract should be approved by the role of the director-market department director in the department where the signing role is located, and the approval level of the approval node is set to be 1, the system can allocate the role of the director-research and development department director in the department where the research and development department 1 is located to carry out approval, and the allocation error of the approval process occurs, so that the system is inconvenient to use.

The method and the system can be used for customizing the role property field, the department property field or the submitting role which are related in the form as the standard for judging the department level according to the requirement, for example, when an approval node is set, the signing role in the contract form can be selected as a level main body, the signing role (instead of the submitting role) is taken as the standard for judging the department level, so that the approval role is determined to be the department management role of the market, and the method and the system are more flexible and convenient to use and have strong universality.

7. The system provides an approval mechanism of the highest-level department director, and avoids the problem that the highest-level department director cannot finish the approval process in a level approval mode.

Examples: when the highest-level leading board of the enterprise submits the approval request, in the level approval, the board owner does not have an upper-level department, but a designated group is set to approve the approval request submitted by the board owner.

The specified group approval includes one of three cases: (1) the appointed group is formed by one or more approval roles, for example, the appointed group is formed by members of a plurality of prison parties, and approval requests of the board owners are approved by the prison party members; (2) the designated group is determined by department level, only the level main body selected by the approval node can be used when the level main body is selected, and the level value n can be set to 0; the method is used for coping with the situation that the organization structure of an enterprise is changed, for example, an original highest-level supervisor of a certain company is a total manager, a board is added after the organization structure is changed, the highest-level supervisor is changed into a board, and an approval role is automatically changed into a board instead of being fixed into the total manager when the level value in the approval node is 0, so that the problem that the approval role cannot adapt to the organization structure change is avoided; (3) the designated group is determined by department level, the level main body can select autonomously, the designated group comprises one or more designated nodes, when the level value n of the designated node is not 0, the designated node of the next stage is required to be set, and when the level value n of the designated node is 0, the designated group setting of the approval node is completed; this is the case for common department roles approving approval requests submitted by the highest level department authorities, e.g., financial authorities of financial departments can review billing information involved in contract approval requests submitted by the board of directors, ultimately to be confirmed by the board of directors.

8. The department level n can be set to 0 when the approval node sets the approval role, namely the submitting role is selected as the approval role in the approval node, approval confirmation can be carried out by the submitting role before the approval process is finished, re-approval can be returned after disagreement is selected, approval is selected to enter the next link, the approval role review program is added, the problem that an approval process needs to be newly built (re-submitted) due to incorrect approval results or mismatching of the approval results and the expectations of the submitting role is avoided, system internal consumption is reduced, and the approval process efficiency and reliability are improved.

Examples: the submitting role submits a 10000-element reimbursement approval request, the approval reimbursement amount is modified to 500 elements after multistage approval due to the fact that the submitted content of the submitting role is wrong or other reasons, before the approval process is finished, the submitting role is used as the approval role to conduct approval confirmation to find out the problem, the approval can be returned after disagreement is selected, approval is selected to enter the next link, and new (resubmission) of an approval process is not needed.

9. By setting the approval roles according to the department level, system workflow setting personnel only need to select the level main body and input the level numerical value when setting the approval roles, a plurality of approval processes can be effectively integrated in one approval process, circulation conditions and circulation lines can be effectively reduced, the workload of the system workflow setting personnel is reduced, and the system reliability is improved. Such as: in the expense reimbursement approval process, a grade approval is set at an approval node (a submitting role is selected as a grade main body), and a department grade is set as 1, so that all expense reimbursements are automatically approved by a department management role of a department where the submitting role is located at the approval node.

10. The main body of the approval operation in the workflow is a role, and the role is an independent individual rather than the role of the traditional group/class property, even if staff/user changes (such as post adjustment, job departure and the like) occur, only new staff needs to be re-associated with the role in the approval process; or staff approval authority is changed, the role approval authority is adjusted in a targeted manner, the resetting/adjusting process is not needed, the setting is convenient, errors or omission can be avoided, the normal operation of an enterprise can not be influenced, and the reliability of workflow is greatly improved. Taking a role with the post property as an approval authority body of an approval link node, determining which approval tasks are possessed by a user through the role, and performing approval operation by the user through the authority of the associated role; understanding clearly simply, the role of every post number/station number nature is the minimum unit of work main part, and to every role to the different demands of approval, this application all can satisfy well.

11. The roles are in one-to-one relation to the users, and only one role can be associated with a unique user in the same period, so that the user can obtain the authority (namely, the user obtains the authority of the associated role) by associating the user with the role, and the authority change of the role is much less than that of the user in the traditional mechanism. The number of roles of the independent body property (station number/station number property) is small, and the change of the station number/station number is small (even the role is unchanged within a certain period of time) although staff flows greatly, so that the authority management of a user is greatly simplified, and the overhead of a system is reduced.

12. The operation of dynamic management, job entering and post adjusting and the like is simple and convenient, the efficiency is high, and the reliability is high: the application of the job entering/leaving/job adjusting in the approval process is simple, the approval operation main body of the workflow is a role, when the staff/user changes, the approval process is not required to be reset (the user only needs to cancel or associate the role, the user who does not have the role of the job number/job position number any longer can cancel the role association, the user who takes the role of the job number/job position number at the hand can associate the role of the job number, the user who associates the role can automatically acquire the related task and authority of the role in the approval workflow, and the approval workflow is not required to be reset or the roles in the workflow are required to be re-authorized, so that the efficiency, the safety and the reliability of the flow setting are greatly improved.

Examples: because Zhang Sanyong users leave the job or adjust the job, etc., the person 3 does not work for the role of "buyer 3" any more, the person three cancels the association with the role; in addition, when the plum four catcher works for the role of 'buyer 3', the plum four is related to the role, and then the plum four automatically obtains the approval task and approval authority of the role of 'buyer 3' in the approval process.

13. The traditional authority management mechanism defines roles as properties of groups, industry types, classes and the like, the roles are in one-to-many relation to users, and in the actual system use process, the authority of the users needs to be adjusted in the operation process, for example: when dealing with the change of employee rights, the rights of a certain employee associated with a role are changed, and we cannot change the rights of the whole role due to the change of the rights of the individual employees, because the role is also associated with other employees with unchanged rights. To cope with this situation, therefore, either a new role is created to satisfy the employee whose authority is changed, or the employee is directly authorized (taken out of role) according to the authority requirements. The two processing modes have the advantages that the time required for the role authorization is long under the condition of more role authorities, the mistakes are easy to make, the operation of a user is tedious and troublesome, and the mistakes are easy to cause the loss of the user of the system.

However, under the method of the application, because the role is an independent individual, the purpose can be achieved by selectively changing the authority of the role. Although the method of the application can increase the workload when the system is initialized, the efficiency of creating the roles or authorizing the roles can be higher than that of the roles taking the groups as the properties by copying and other methods, and the scheme of the application can make the setting of the rights clear and clear because the commonality of the roles taking the properties as the groups when the roles meet the associated users is not considered; especially after the system is used for a period of time (the user/role authority dynamically changes), the application scheme can greatly improve the authority management efficiency in the use of the system for the system user, so that the dynamic authority is simpler, more convenient, clearer and more clear, and the authority setting efficiency and reliability are improved.

14. The traditional character authorization method taking the group as the property is easy to make mistakes, and the probability of authorization mistakes is greatly reduced by the method, because the method only needs to consider the characters as independent individuals, and does not need to consider which common characters are shared by a plurality of users which are related to the character of the group under the traditional method. Even an authorization error affects only the user associated with that role, whereas a traditional role in group nature affects all users associated with that role. Even if authority authorization errors occur, the method for correcting the authority authorization errors is simple and short in time, and the authority commonality of all users related to the roles needs to be considered when the roles with group properties are corrected in the prior art, so that the method is troublesome and complex to modify under the condition of more functional points, is quite easy to make mistakes, and can only be solved by newly creating the roles in many cases.

15. Under the traditional role authorization method taking the group as a property, if the role has more authority function points and long time, the specific authority of the role is hard to remember, the authority difference between roles with similar authorities is hard to remember, and if a new user is required to be associated, how to select the association cannot be accurately judged. The role of the method has the property of post number/station number, and the selection is clear at a glance.

16. When the user is on duty, if a plurality of authorities of the user to be on duty are allocated to other users to be born, the authorities of the user to be on duty must be distinguished during processing, roles are respectively re-created to be associated with the other users, and the operation is complex and time-consuming and is easy to generate errors.

The method comprises the following steps: the user who is on Shift associates several roles, and when on Shift, the user first cancels the association of the user with the roles in the original department (the cancelled roles can be re-associated to other users), and then associates the user with the roles in the new department. The operation is simple, and no error occurs.

17. A character belongs to a department, the department of the character cannot be changed, and why the character cannot change the department: reason 1: because the character property of the application is equal to one station number/post number, the working contents/authorities of different station numbers/post numbers are different, for example, the role of salesman 1 under the sales department and the role of developer 1 of the technical department are completely different, and the authorities of the two station numbers/post numbers are different; reason 2: if the department (sales department) to which the role of sales person 1 belongs is replaced with a technical department, and the authority of the role of sales person 1 is unchanged, there is one role having the authority of the sales department in the technical department, which causes confusion and security holes.

18. One role can exist in different approval nodes in the same approval process, and the approval role in different approval nodes has different viewing and modifying rights on form fields. Examples of advantages: a role is a capital sales manager 3, which exists in two approval nodes of capital sales contract approval and Shanghai sales contract approval in a contract approval workflow; for the approval node of the adult sales contract, the role can check all field contents such as the customer name, the contact person, the contact way, the product quantity, the product unit price, the contract amount and the like of the contract during approval, and can modify the product unit price and the contract amount; however, the approval node of the Shanghai sales contract cannot view the contents of sensitive fields such as customer names, contacts, contact ways and the like, and cannot be modified (but can also be set to have viewing rights and have no modification rights). In this way, the authority of the role in the approval process can be set in a self-defined manner.

One or more approval roles are selected at the approval node, the authority of the approval roles is set at the approval node, and independent authority setting can be carried out on each approval role of each approval node. For example: in the approval process of a contract form, 2 approval roles are set by a certain approval node, namely a role A and a role B respectively, wherein the role A can be set to see a contract amount field and a value of the field in the contract form and also can see a client address field and a value of the field in the contract form; the setting role B cannot see the contract amount field in the contract form, or can see the contract amount field but cannot see the value of the field, and can display other symbols such as a number when the value is not seen, and the role B can see the client address field and the value of the field in the contract form.

Drawings

FIG. 1 is a schematic diagram of a system for directly authorizing a user in the background art;

FIG. 2 is a schematic diagram of a system authorizing group/class property roles in the background;

FIG. 3 is a schematic diagram of a system combining direct authorization of a user with authorization of a group/class property role in the background art;

FIG. 4 is a tree diagram of a system organization structure according to an embodiment;

FIG. 5 is a flow chart of a workflow generation method of the present invention;

FIG. 6 is a schematic diagram of the manner in which the system of the present invention authorizes a user by an independent individual character;

FIG. 7 is a schematic diagram of a workflow approval process according to the present invention;

fig. 8 is a flow chart of a user-character authorization method of the present invention.

Detailed Description

The technical solution of the present invention will be described in further detail with reference to the accompanying drawings, but the scope of the present invention is not limited to the following description.

As shown in fig. 7, a method for setting approval nodes based on a consultation in an approval process, wherein an approval process includes a start node, at least one approval node, and an end node, includes the following sequential steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes; and a second step of: one or more approval roles of the countersign node are set.

After the approval mode of the approval node is set as the approval, all the approval roles related to the approval node have no modification authority on the form field content of the approval process. When the approval node has only one approval character, a meeting mode can be selected, so that the approval character has only rights for expressing comments and cannot modify the contents of the form.

The approval roles must be selected after the approval mode is determined, so that when the approval roles are selected first, some approval roles are prevented from having modification permission on the form field content, and once the form field content is modified, the approval cannot be realized, because each approval role is approved in parallel, and modification of form data can influence approval of other approval roles. After the approval mode is determined as the countersign, the system limits all the involved approval roles to have no form modification authority, and ensures objective representation of countersign contents.

Only after all approval roles related to the meeting node submit the meeting comments, the subsequent steps of the approval process can be entered; in the approval process, the process cannot be ended by the countersignature node, and at least one non-countersignature approval node exists in the subsequent nodes of the countersignature node.

The countersign node obtains the summary of the countersign opinions of all approval roles of the node, and no matter how the countersign opinions are, the countersign node can not reject the approval flow.

The approval mode of the approval node can be selected (set) as a consultation, and the consultation node gathers the consultation opinions of all the approval roles of the nodes and provides powerful references for the approval roles of the following approval nodes.

For example: before signing a contract, the salesperson 5 can initiate a countersignature flow, and can select the countersignature expression comments of the sales department, the production department and the finance department, and the countersignature comments must be submitted completely before the next step is carried out, and the countersignature comments given by a manager can be referred to during approval.

The method for setting approval nodes in an approval process based on a countersignature further comprises a step of setting the approval role to view the contents of the form fields related to the approval process, wherein the viewing authority of different approval roles of the same countersignature node to view the contents of the form fields can be different. The method is more convenient to use, wide in application range, convenient to hide partial sensitive fields and capable of avoiding information leakage.

Embodiment 3. Method for setting approval nodes in an approval process based on a countersignature, wherein one approval process comprises a start node, at least one approval node and an end node, and the method comprises the following steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes; and a second step of: setting one or more approval roles of the countersign node; the method also comprises the step of setting the countersign node as an anonymous countersign, wherein after the anonymous countersign, other non-self-approving roles cannot see the countersign opinions submitted by the approving roles except that the approving roles can see the countersign opinions of the self-approving roles.

The anonymous countersign function is provided, after the anonymous countersign function is set, besides the approval roles can see the countersign opinions of the approval roles, other non-self approval roles cannot see the countersign opinions submitted by the approval roles, so that the approval roles are prevented from being affected mutually, and the authenticity and the credibility of the countersign result are ensured.

The second step of the embodiment 4 adopts an approval role setting method based on form fields and levels, and specifically includes a step of setting a system organization structure and a step of setting an approval role according to department levels: the step of setting the system organization structure comprises the following substeps: SS1: creating departments and roles contained in the system organization structure; SS2: setting hierarchical relations among all departments, as shown in fig. 4, department a is one level higher than department B, and department a is two levels higher than department C … …; setting department management roles of all departments; the step of setting approval roles according to department level comprises the following steps: SSS1, selecting to conduct approval role setting in a level mode; SSS2, selecting one of a role property field, a department property field or a submitting role of the approval process in a corresponding form of the approval process as a level main body; SSS3, filling in specific level values N, wherein N is a positive integer greater than or equal to 0 (the value of N can also be replaced by other symbols, such as a, b, c, d, b is one level greater than a, c is two levels greater than a, d is three levels greater than a, and the like): (1) Selecting a role property field in a corresponding form of an approval process as a level main body, and judging the level by taking the selected role as a judging standard, for example, the submitting role of the process is d2, but the role property field in the selected form is an signing role, and the signing role is a role d3: (1) when n=0, the selected role d3 plays an approval role of the approval node; (2) when n=1, the department manager role D1 of the department D where the selected role D3 is located takes on the approval role of the approval node; if the selected role is a department management role of the department where the selected role is located, the department management role of the superior department of the department where the selected role is located is used as an approval role of the approval node; (3) when n=2, the department master role C1 of the department C of the upper level of the department D where the selected role D3 is located takes on the approval role of the approval node; (4) when n=3, the department master role B1 of the department B of the upper level of the department D where the selected role D3 is located takes on the approval role of the approval node; (5) when n=4, the department master role a1 of the department a of the upper level of the department D where the selected role D3 is located takes on the approval role of the approval node; (6) and so on; (7) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node; for example: for the role d3, the department level should be at most 4, and when the department level is set to 6, the department administration role a1 of the highest level department a takes on the approval role of the approval node.

(8) When n is more than or equal to 1, setting the selected role as a department management role of a department where the selected role is located, and when the department has no previous-stage department, the approval node is approved by a designated group.

(2) Selecting department property fields in a corresponding form of the approval process as a level main body, and judging the level by taking the selected department as a judging standard, for example, selecting the department property fields in the form as an signing department, wherein the signing department is department D: (1) when n=0, the department master role D1 of the selected department D plays an approval role of the approval node; (2) when n=1, the department master role C1 of the upper level department C of the selected department D takes on the approval role of the approval node; (3) when n=2, the department master role B1 of the department B of the upper level of the selected department D plays an approval role of the approval node; (4) when n=3, the department master role a1 of the department a of the upper level above the selected department D takes on the approval role of the approval node; (5) and so on; (6) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node; for example: for department D, the department level should be at most 3, and when the department level is set to 6, the department authority role a1 of the highest level department a takes on the approval role of the approval node.

(7) When n is more than or equal to 1, the approval node is approved by the appointed group, wherein the selected department has no previous department.

(3) Selecting a submitting role of the approval process as a level main body, and judging the level by taking the submitting role as a judging standard, for example, if the submitting role is a role d2, then: (1) when n=0, the workflow approval process submitting role d2 plays an approval role of the approval node; the department level n of the approval node can be set to 0 when the approval role is set, namely the approval role d2 is selected as the approval role in the approval node, approval confirmation can be carried out by the approval role d2 before the approval process is finished, re-approval can be returned after approval is not chosen, approval is chosen to enter the next link, the approval role review program is added, the problem that a new (re-approval) approval process is needed due to incorrect approval results or mismatching of the approval results and the approval roles is avoided, the internal consumption of a system is reduced, and the efficiency and reliability of the approval process are improved.

Examples: the submitting role d2 submits a 10000-yuan cancel-and-cancel approval request, the cancel-and-cancel amount is modified to 500 yuan after multistage approval due to the fact that the submitted content of the submitting role d2 is wrong or other reasons, before the approval process is finished, the submitting role d2 is taken as the approval role to carry out rechecking confirmation, the problem can be found, the re-approval can be returned after the disagreement is selected, the next link is selected to be approved, and a new (re-submitting) approval process is not needed.

(2) When n=1, submitting a department master role D1 of a department D where the role D2 is located by the workflow approval process to take an approval role of the approval node; (if the submitting role is D1, which is the department master role of the department D where the submitting role is located, the department master role C1 of the department C at the upper level of the department D where the submitting role is located acts as the approval role of the approval node) (3) when n=2, the department master role C1 of the department C at the upper level of the department D where the workflow approval process submitting role D2 acts as the approval role of the approval node; (4) when n=3, submitting a department master role B1 of the department B of the upper level of the department D where the role D2 is located by the workflow approval process to act as an approval role of the approval node; (5) when n=4, submitting a department master role a1 of the department a of the upper level of the department D where the role D2 is located by the workflow approval process to act as an approval role of the approval node; (6) and so on; (7) when the department level setting exceeds the highest level department in the system organization structure, the department manager role of the highest level department takes on the approval role of the approval node. For example: for the role d2, the department level should be at most 4, and when the department level is set to 6, the department administration role a1 of the highest-level department a takes on the approval role of the approval node.

(8) When n is more than or equal to 1, setting a submitting role as a department management role of a department where the submitting role is located, and when the department has no previous-stage department, approving the approval node by a designated group; the specified group approval includes one of three cases: (1) a designated group is made up of one or more approving roles; (2) The designated group is determined by department level, only the level main body selected by the approval node can be used when the level main body is selected, and the level value n can be set to 0; (3) The designated group is determined by department level, the level main body can select autonomously, one or more designated nodes are included in the designated group, the designated node of the next stage is required to be set when the level value n of the designated node is not 0, until the designated group setting of the approval node is completed when the level value n of the designated node is 0.

The scheme of the application has another advantage based on the original advantage of submitting role level authorization mode: roles of different properties can be selected, such as a contract signing role, a contract adding role and a contract responsibility role on a contract form, and the approval node should not submit a role judgment level, but rather contract a role judgment level. For example, the first approving node of the reimbursement form (reimbursement approval process) is to be at the upper level of the submitting role, and the other approving node is to be at the upper level of the reimbursement role (the reimbursement role and the submitting role may be different roles).

The traditional level approval mode only takes approval flow submitting roles as judgment standards to judge department levels, other roles or departments involved in the form cannot be customized to serve as standards for judging department levels, and certain use limitations exist.

When the approval node is set, the signing roles in the contract form can be selected as the level main body according to the requirement, the signing roles (instead of the submitting roles) are used as the standard judgment department level, the approval roles are determined to be market part management roles, and the method is flexible and convenient to use and high in universality.

The system provides an approval mechanism of the highest-level department director, and avoids the problem that the highest-level department director cannot finish the approval process in a level approval mode.

When the approval node selects the level approval, approval authority authorization is carried out on the corresponding approval roles in the level, and the approval authorities of the corresponding approval roles in the level are the same.

Examples: when n=1, a3, b3, c3, d3 submit the approval process respectively, the corresponding approval authorities are a1, b1, c1, d1 respectively, and the approval authorities of a1, b1, c1, d1 are the same.

As shown in fig. 5, the generation of the approval process includes the following steps: s1: constructing a three-layer structure model of user-role-authority, wherein: role layer: the operation main body of the flow approval in the workflow is a role, each role is an independent individual, and is not a group/class, one role can only be associated with a unique user in the same period, and one user is associated with one or more roles; the role is constituted as follows: post name + post number; rights layer: the method is composed of rights required to be used in workflow execution, and the rights are directly authorized to roles; user layer: the user determines approval tasks in the approval process through the associated roles, and performs approval operation with the authority of the associated roles; s2: as shown in fig. 7, an approval process is generated based on the three-layer structure model, wherein one approval process includes a start node, at least one approval node, and an end node: starting node: the initiating role initiates/applies/submits the workflow as a starting node or by the first approving node as a starting node.

The system determines approval flows according to the forms submitted by the initiating roles, and designs one or more approval flows aiming at the forms needing workflow, but one role can only select one approval flow under the form (the same role can only exist in one flow of the same form); for example, the purchase contract form has two processes, namely a P1 process and a P2 process, if the role A is selected in the beginning node of the P1 process, the role A can not be selected any more in the beginning node of the P2 process, and the role A is newly added with an approval of the purchase contract and automatically enters the P1 process when submitting the approval.

Approval node: setting an approval mode of an approval node, selecting an approval role, and authorizing the approval role; end node: when the approval process flows to the node, the approval process is ended, and the ending node does not perform approval operation; or the last approval node is used as an end node, and the end node needs to carry out approval operation.

S3: and the user determines the approval task to be processed according to the associated role and performs approval operation according to the authority of the associated role.

One or more approval roles are selected at the approval node, one role can exist in different approval nodes in the same approval process, and the approval roles in different approval nodes can have different permission for viewing and modifying the form fields. Examples of advantages: a role is a capital sales manager 3, which exists in two approval nodes of capital sales contract approval and Shanghai sales contract approval in a contract approval workflow; for the approval node of the adult sales contract, the role can check all field contents such as the customer name, the contact person, the contact way, the product quantity, the product unit price, the contract amount and the like of the contract during approval, and can modify the product unit price and the contract amount; however, the approval node of the Shanghai sales contract cannot view the contents of sensitive fields such as customer names, contacts, contact ways and the like, and cannot be modified (but can also be set to have viewing rights and have no modification rights).

As shown in fig. 6 and 8, the step S1 includes the following sequential sub-steps: s101: creating roles, each role being an independent individual, not a group/class; s102: respectively authorizing the roles created in the step S101; s103: associating users to roles, wherein one role can only be associated with a unique user during the same period, and one user is associated with one or more roles; step S101 is prior, but step S102 and step S103 are not in sequential relationship. The user determines the authority through the association with the role, and if the authority of the user is to be modified, the purpose of changing the authority of the user associated with the role is achieved by adjusting the authority possessed by the role. Once a user associates a role, the user has all the operating rights of that role.

The relationship of the character to the user is one-to-one (when the character is associated with one user, other users can not associate the character any more, and if the character is not associated by the user, the association can be selected by other users). The relationship of users to roles is one-to-many (one user can associate multiple roles at the same time).

Definition of roles: the characters do not have the properties of group/class/category/post/position/work class and the like, but have the property of non-aggregation, the characters have uniqueness, and the characters are independent individuals which exist independently; in enterprise applications, this corresponds to a post (here, a post is not a post, there may be multiple employees at the same time, and a post can only correspond to one employee in the same period).

Examples: the following roles may be created in a corporate system: the main manager, the auxiliary main manager 1, the auxiliary main manager 2, the Beijing sales one manager, the Beijing sales two managers, the Beijing sales three managers, the Shanghai sales engineer 1, the Shanghai sales engineer 2, the Shanghai sales engineer 3, the Shanghai sales engineer 4 and the Shanghai sales engineer 5 … … are related to roles: if the staff member of the company opens three to leave the company subsidiary manager 2 and leaves Beijing to sell one manager, the roles that the company needs to be associated with open three are the subsidiary manager 2 and the Beijing to sell one manager, and the staff member has the rights of the two roles.

Authorization of a character: the authorization of the system for the character includes, but is not limited to, authorization of the form, authorization of the menu, or authorization of the function. The authorization of the manipulation of the form includes, but is not limited to, adding or deleting changes.

The concept of a traditional character is a group/class/post/job/work nature, one character being able to correspond to multiple users. The concept of the role is equivalent to the post number/station number, and is also similar to the role in movie drama: one character can only be played by one actor during the same period (childhood, teenager, middle-aged … …), and one actor may be multi-faceted.

Authorization for a character includes, but is not limited to, authorization for a form, authorization for a menu, or authorization for a function.

The role belongs to a department, the role is unique under the department, and the role is authorized according to the working content of the role.

If the user wants to change departments, the cross-department sentry is involved, and the specific operation process comprises the following steps: (1) disassociating the user from the role in the original department; (2) associating the user with a role in the new department.

After the roles are created, the roles can be associated in the process of creating the users, and the roles can be associated at any time after the users are created. After the user associates the roles, the association relationship with the roles can be released at any time, and the association relationship with other roles can be established at any time.

Step S1 described in example 7 comprises the following sequential sub-steps: s101: establishing roles, each role being an independent individual, not a group/class; s102: associating users to roles, wherein one role can only be associated with a unique user during the same period, and one user is associated with one or more roles; s103: the roles established in S101 are individually authorized.

The workflow control method further comprises a step of user inter-department post adjustment management, and specifically comprises the following steps: (1) disassociating the user from the role in the original department; (2) associating the user with a role in the new department.

The role is constituted as follows: post name + post number. For example: the roles of the workshop producer 1, the workshop producer 2 and the workshop producer 3 and … … are independent individuals, are equivalent to the concepts of a post number and a station number, and are different from the roles in the traditional authority management system, and the concepts of the roles in the traditional system are group/class properties of the post/position/work variety and the like.

Example 8 the relationship between staff, user and roles after the following example staff entered a company: 1. new job entry: the employee is newly engaged, and the role of the corresponding post number/station number is directly selected for the user (employee) to be associated, for example: the three-in-office company (the company distributes one three users for three) has one selling part and is responsible for selling the refrigerator products in the Beijing area (the corresponding role is the role of sales engineer 5 below the selling part), and Zhang Sanyong users directly select the role of sales engineer 5 to be associated.

2. Increasing positions: after a period of time of the third party, the company also arranges that the third party is responsible for selling television products in Beijing area (the corresponding role is the role of 'sales engineer 8' under the part of sales) and also serves as an after-sales manager (the role of 'after-sales manager 1'), and then the third party adds two roles of 'sales engineer 8' under the part of sales and 'after-sales manager 1' under the part of after-sales in association with each other, at this time, the third party associates three roles, namely 'sales engineer 5', 'sales engineer 8' under the part of sales and 'after-sales manager 1' under the part of sales, and the third party has the authority of the three roles.

3. The positions are reduced: over time, the company decided to leave open three after-market manager (corresponding to the role of "after-market manager" under-market), and no longer doubles as other work. Zhang Sanyong users associate this role of "after-market manager" under the sales, while canceling the three roles previously associated (sales engineer 5, sales engineer 8, and "after-market manager 1" under the sales), at which point Zhang Sanyong users only have the right of this role of "after-market manager" under the sales.

4. Adjustment of rights of a character (adjustment of rights possessed by the character itself): if the company decides to increase the authority of the after-sales manager, only the authority of the role of the after-sales manager needs to be increased, and Zhang Sanyong users have increased the authority of the three users because the authority of the role of the after-sales manager is increased.

5. Leaving: after one year, the user can cancel the association of the user with the role of the after-sales manager under the after-sales part after leaving the office.

Examples: in dynamic business, staff's job entry and job departure are frequent and continuous, but the change in the station number/station number is very small (even unchanged for a certain period of time).

The traditional authorization method comprises the following steps: under the condition of multiple system function points, the traditional role of group/class property is used for authorization, so that the authorization workload is large, complex and easy to make mistakes, even the mistakes are not easy to find in a short time, and the loss to the system user is easy to cause.

The application authorization method comprises the following steps: the authority control method and the authority control system authorize the role with the position number/position number property, and control the user authority by associating the role to determine the authority only through a simple association relationship between the user and the role, so that the authority control becomes simple and easy to operate, the authority control is clear, and the authority efficiency and the authority reliability are greatly improved.

The foregoing is merely a preferred embodiment of the invention, and it is to be understood that the invention is not limited to the form disclosed herein but is not to be construed as excluding other embodiments, but is capable of numerous other combinations, modifications and environments and is capable of modifications within the scope of the inventive concept, either as taught or as a matter of routine skill or knowledge in the relevant art. And that modifications and variations which do not depart from the spirit and scope of the invention are intended to be within the scope of the appended claims.

Claims

1. The method for setting the approval node in the approval process based on the consultation is characterized by comprising the following sequential steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes;

and a second step of: setting one or more approval roles of the countersign node;

the approval roles are independent individuals and are not groups/classes, one approval role can only be associated with a unique user in the same time period, and one user is associated with one or more approval roles;

The method also comprises the step of setting the examination authority of the examination roles for the form field contents related to the examination flow, wherein the examination authority of different examination roles of the same countersignature node for the form field contents can be different, but the form field contents have no modification authority.

2. The method for setting up a consultation-based approval node in an approval process according to claim 1, wherein: only after all approval roles related to the meeting node submit the meeting comments, the subsequent steps of the approval process can be entered;

3. The method for setting up a consultation-based approval node in an approval process according to claim 1, wherein: in the approval process, the process cannot be ended by the countersignature node, and at least one non-countersignature approval node exists in the subsequent nodes of the countersignature node.

4. The method for setting up a consultation-based approval node in an approval process according to claim 1, wherein: the method also comprises the step of setting a responsible role for the countersign node, wherein the responsible role selects the next-level circulation node of the countersign node during countersign, and when the next-level circulation node has a plurality of options, the responsible role selects one of the circulation nodes.

5. The method for setting up a consultation-based approval node in an approval process according to claim 1, wherein: the generation of the approval process comprises the following steps: s1: constructing a three-layer structure model of user-role-authority, wherein: role layer: the operation main body of the flow approval in the workflow is a role, each role is an independent individual, and is not a group/class, one role can only be associated with a unique user in the same period, and one user is associated with one or more roles;

rights layer: the method is composed of rights required to be used in workflow execution, and the rights are directly authorized to roles;

user layer: the user determines approval tasks in the approval process through the associated roles, and performs approval operation with the authority of the associated roles;

s2: generating an approval process based on the three-layer structure model, wherein one approval process comprises a starting node, at least one approval node and an ending node:

starting node: the approval process begins;

approval node: setting an approval mode of an approval node, selecting an approval role, and authorizing the approval role;

end node: ending the approval process;

6. The method for setting up a consultation-based approval node in an approval process according to claim 1, wherein: the second step adopts an approval role setting method based on form fields and levels, and specifically comprises a step of setting a system organization structure and a step of setting approval roles according to department levels: the step of setting the system organization structure comprises the following substeps: SS1: creating departments and roles contained in the system organization structure;

SS2: setting hierarchical relations among all departments, and setting department management roles of all departments;

the step of setting approval roles according to department level comprises the following steps: SSS1, selecting to conduct approval role setting in a level mode;

SSS2, selecting one of a role property field, a department property field or a submitting role of the approval process in a corresponding form of the approval process as a level main body;

SSS3, filling in a specific level value n which is a positive integer more than or equal to 0: (1) Selecting a role property field in a corresponding form of the approval process as a level main body, and judging the level by taking a role corresponding to the field as a judging standard:

(1) when n=0, the role corresponding to the field takes on the approval role of the approval node;

(2) When n=1, the department management role of the department where the role corresponding to the field is located takes on the approval role of the approval node; if the role corresponding to the field is a department management role of the department where the field is located, taking the department management role of the higher-level department of the department where the role corresponding to the field is located as an approval role of the approval node;

(3) when n=2, the department master role of the department of the superior department of the department where the role corresponding to the field is located takes on the approval role of the approval node;

(4) when n=3, the department master role of the department of the upper level department of the department where the role corresponding to the field is located takes on the approval role of the approval node;

(5) when n=4, the department master role of the upper level department of the department where the role corresponding to the field is located takes on the approval role of the approval node;

(6) and so on;

(7) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node;

(8) when n is more than or equal to 1, setting a role corresponding to the field as a department master role of a department where the field is located, and when the department has no previous-stage department, approving the approval node by a designated group;

(2) Selecting department property fields in the corresponding form of the approval process as a level main body, and judging the level by taking departments corresponding to the fields as judgment standards:

(1) when n=0, the department management role of the department corresponding to the field takes on the approval role of the approval node;

(2) when n=1, the department master role of the upper level department of the department corresponding to the field takes on the approval role of the approval node;

(3) when n=2, the department master role of the department of the upper level of the department corresponding to the field takes on the approval role of the approval node;

(4) when n=3, the department master role of the upper level department of the department corresponding to the field takes on the approval role of the approval node;

(5) and so on;

(6) when the setting of the department level exceeds the highest-level department in the system organization structure, taking the role of department management of the highest-level department as the approval role of the approval node;

(7) when n is more than or equal to 1, setting an approval node to be approved by a designated group when a department corresponding to the field has no previous-stage department;

(3) Selecting a submitting role of the approval process as a level main body, and judging the level by taking the submitting role as a judging standard: (1) when n=0, the role submitted by the workflow approval process acts as the approval role of the approval node;

(2) When n=1, submitting the department role of the department in which the role is located by the workflow approval process to act as the approval node

Approving the roles; if the submitting role is a department management role of the department where the submitting role is located, the department management role of the superior department of the department where the submitting role is located takes on the approval role of the approval node;

(3) when n=2, submitting a department master role of a higher-level department of the department where the role is located by the workflow approval process to serve as an approval role of the approval node;

(4) when n=3, submitting a department master role of a higher-level department of the department where the role is located by the workflow approval process to take the approval role of the approval node;

(5) when n=4, submitting a department master role of a superior department of a department where the role is located by a workflow approval process to take an approval role of the approval node;

(6) and so on;

(8) when n is more than or equal to 1, setting a submitting role as a department management role of a department where the submitting role is located, and when the department has no previous-stage department, approving the approval node by a designated group;

The specified group approval includes one of three cases: (1) a designated group is made up of one or more approving roles;

(2) The designated group is determined by department level, only the level main body selected by the approval node can be used when the level main body is selected, and the level value n can be set to 0;

(3) The designated group is determined by department level, the level main body can select autonomously, one or more designated nodes are included in the designated group, the designated node of the next stage is required to be set when the level value n of the designated node is not 0, until the designated group setting of the approval node is completed when the level value n of the designated node is 0.

7. The method for setting the approval node in the approval process based on the consultation is characterized by comprising the following sequential steps: the first step: setting an approval mode of an approval node as a consultation node, and calling the approval node as the consultation node, wherein the consultation node gathers the consultation opinions of all approval roles of the nodes and provides a reference for the approval roles of the later approval nodes;

The method also comprises the step of setting the countersign node as an anonymous countersign, wherein after the anonymous countersign, other non-self-approving roles cannot see the countersign opinions submitted by the approving roles except that the approving roles can see the countersign opinions of the self-approving roles;