WO2018214889A1 - 基于会签的审批节点在审批流程中的设置方法 - Google Patents

基于会签的审批节点在审批流程中的设置方法 Download PDF

Info

Publication number
WO2018214889A1
WO2018214889A1 PCT/CN2018/087919 CN2018087919W WO2018214889A1 WO 2018214889 A1 WO2018214889 A1 WO 2018214889A1 CN 2018087919 W CN2018087919 W CN 2018087919W WO 2018214889 A1 WO2018214889 A1 WO 2018214889A1
Authority
WO
WIPO (PCT)
Prior art keywords
approval
role
department
node
level
Prior art date
Application number
PCT/CN2018/087919
Other languages
English (en)
French (fr)
Inventor
陈达志
Original Assignee
成都牵牛草信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都牵牛草信息技术有限公司 filed Critical 成都牵牛草信息技术有限公司
Publication of WO2018214889A1 publication Critical patent/WO2018214889A1/zh

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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Definitions

  • the invention relates to an approval node approval method for a management software system such as ERP, in particular to a method for setting an approval node based on a signing in an approval process.
  • 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 and workflow control methods adopt 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.
  • the role is similar to the concept of position/position/work type.
  • the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. As shown in Figure 1, the user is authorized directly. The disadvantage is that the workload is large and the operation is frequent. And trouble; the approval operation subject of the approval node in the approval process is the user, and the workflow approval node directly selects the employee/user as the approval subject.
  • 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 approval operation subject is the group/class nature role; As shown in Figure 3, the above two methods are combined.
  • both 2 and 3 need to authorize the role of the class/group nature, and the way of authorization and workflow control through the role of class/group/post/work type has the following disadvantages: 1.
  • Difficulties in operation In the actual system use process, it is often necessary to adjust the user's authority during the operation process. For example, when dealing with employee permission changes, the employee rights associated with the role change, we cannot because of this Changes in employee permissions change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed. 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 workflow approval node directly selects the employee/user as the approval subject, or the new role is added to meet the requirements of the approval process.
  • employee changes such as transfer, resignation, etc.
  • all the processes involved in the employee must be adjusted accordingly, especially for company management personnel, which involves more approval processes and process adjustments. Large amount, complicated, easy to make mistakes or omissions, affecting the normal operation of the company, and even causing unpredictable losses.
  • 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 object of the present invention is to overcome the deficiencies of the prior art, and to provide a method for setting an approval node based on a signing in an approval process.
  • the approval mode of the approval node can be selected (set) as a signing, and the signing node summarizes all the approval roles of the node.
  • an approval process includes a start node, at least one approval node, and an end node, including the following sequential steps:
  • Step 2 Set one or more approval roles for the signing node.
  • the approval role is an independent individual, not a group/class.
  • One approval role can only be associated with a unique user at the same time, and one user is associated with one or more approval roles.
  • the process cannot be terminated by the signing node, and at least one of the subsequent nodes of the signing node has an unapproved approval node.
  • the setting method of the approval node in the approval process based on the signing process further includes a step of setting a responsible role for the signing node, and the role is responsible for selecting the next-level flow node of the signing node when the signing is performed, and there are multiple next-level flow nodes. When optional, choose one of the responsible roles.
  • the setting method of the approval node in the approval process based on the signing process further includes a step of setting the permission role of the approval role to the content of the form field involved in the approval process, and the different approval roles of the same signing node may have different viewing rights for the form field content.
  • the generation of the approval process includes the following steps: S1: constructing a three-layer structure model of user-role-permission, wherein: role layer: the operation subject of the process approval in the workflow is a role, and each role is an independent individual, instead Group/class, a role can only be associated with a unique user in the same period, and a user is associated with one or more roles; privilege layer: consists of the permissions required for workflow execution, permissions are directly delegated to the role; user layer: user The approval task in the approval process is determined by the associated role, and the approval operation is performed with the permission of the associated role; S2: an approval process is generated based on the three-layer structure model, and an approval process includes a start node, at least one approval node, and an end node.
  • Start node approval process starts; approval node: set approval mode approval mode and select approval role, and authorize approval role; end node: approval process ends; S3: user determines the approval task to be processed according to its associated role And approve the action based on the permissions of the associated role.
  • the second step 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 by department level: the step of setting the system organization structure includes the following substeps. : SS1: Create departments and roles included in the system organization structure; SS2: set the hierarchical relationship between departments, and set the department supervisor role of each department; the steps of setting the approval role by department level include: SSS1: Selection To set the approval role in a hierarchical manner; SSS2: select one of the role nature field, the department property field, or the submission role of the approval process in the approval process corresponding form, as the level body; SSS3: fill in the specific level value n, n is a positive integer ⁇ 0 (the value of N can also be replaced by other symbols, such as a, b, c, d, b is one level larger than a, c is two levels larger than a, and d is three levels larger than a, Analogy): (1)
  • the department head role of the upper-level department is the approval role of the approval node; 6 and so on; 7 when the department level When the highest level department in the system organization structure is exceeded, the department supervisor role of the highest level department acts as the approval role of the approval node; 8 when n ⁇ 1, the “submit role” is required to be the department supervisor role of the department in which it is located, and
  • the approval node is approved by the designated group; the specified group approval includes one of the following three conditions: (1) the designated group consists of one or more approval roles; (2) the designation The group is determined by the department level. When selecting the level body, only the level body selected by the approval node can be used, and the level value n can only be set to 0.
  • the specified group is determined by the department level, and the level body can independently select and specify the group.
  • One or more specified nodes are included. When the level value n of the specified node is non-zero, the next-level designated node must be set. When the level value n of the specified node is 0, the specified group setting of the approval node is completed.
  • an approval process includes a start node, at least one approval node, and an end node, including the following sequential steps: Step 1: Set the approval node approval mode to the signing,
  • the approval node is the signing node, the signing node summarizes the signing opinions of all the node approval roles, and provides reference for the approval role of the subsequent approval node;
  • the second step setting one or more approval roles of the signing node;
  • the signing node is an anonymous signing step. After setting the anonymous signing, except for the approval role, you can see your own signing opinions. Other non-accepting roles cannot see the signing opinions submitted by the approval role.
  • the beneficial effects of the present invention are as follows: 1.
  • the approval mode of the approval node can be selected (set) as the signing, and the signing node summarizes the signing opinions of all the approval roles of the node, and provides a powerful reference for the approval role of the subsequent approval node.
  • the salesperson 5 can initiate a sign-off process (ie, the approval process includes a sign-up node), and the sales department, production department, and finance department can choose to express opinions (ie, choose to represent the roles of the above three departments). , to express the opinions of the respective departments, must submit all the opinions of the meeting before entering the next step.
  • the general manager approves, you can refer to the comments signed by everyone.
  • the sales-related approval role in the sign-up node can be set to view all fields; the production-related approval role can be set to view only the product model field, product quantity field, technical indicator field, Delivery time field; financial related approvers can be set to view only the product model, product unit price, contract amount, billing information, and payment method fields in the contract form.
  • the contract amount is 100,000. If the approval role is selected first, and an approval role A has the right to modify the amount, the contract will be The amount is revised to 80,000, and the contract amount seen by other approval roles will be changed to 80,000. It will be meaningless to conduct the approval of the agreement based on the revised contract content.
  • the traditional level approval method can only use the approval process to submit the role as the judgment standard to judge the department level. It is impossible to customize other roles or departments involved in the form as the criteria for judging the department level, and there are certain usage limitations.
  • the contract signing role is for leave, so that his colleague has initiated a contract approval for him, and the system determines that his colleague is the submitting role of the process, and the level judgment is based on the level approval.
  • Colleagues are the subject, and it is impossible to objectively reflect the department and position in which the contract signing role is located.
  • the signing role of the contract is the salesperson of the marketing department1
  • the colleague role is the R&D personnel of the R&D department.
  • the contract should be approved by the head of the department in which the role is assigned, the head of the marketing department, and the approval level of the approval node is set to At 1 o'clock, the system will be assigned to the supervisor-R&D department supervisor of the department where the R&D staff 1 is located for approval.
  • the allocation process is incorrectly assigned and inconvenient to use.
  • the application can customize the role property field, the department property field or the submission role involved in the form as a criterion for judging the department level. For example, when setting the approval node, the signing role in the contract form can be selected as the level body.
  • the signing role (rather than defaulting to submitting the role) is used as a standard to judge the department level, so as to determine the approval role as the marketing department supervisor role, the use is more flexible, convenient, and versatile.
  • the system provides the approval mechanism for the highest level department heads to avoid the problem that the top level department heads cannot complete the approval process through level approval.
  • the chairman of the company's top leadership submits an approval request
  • the chairman does not have a higher-level department, but sets a designated group to approve the approval request submitted by the chairman.
  • the designated group approval includes one of the following three situations: 1
  • the designated group consists of one or more approval roles.
  • a member of a plurality of supervisory committees constitutes a designated group, and the chairman's approval request is approved by the members of the board of supervisors;
  • the group is determined by the department level.
  • the level body only the level body selected by the approval node can be used, and the level value n can only be set to 0; this case is used to respond to changes in the organizational structure of the enterprise, for example, a company
  • the former top-level supervisor is the general manager, and after the organizational structure changes, the board of directors is added.
  • the highest-level supervisor becomes the chairman.
  • the level of the approval node is 0.
  • the approval role automatically becomes the chairman, instead of being fixed as the general manager.
  • the approval role cannot adapt to the problem of organizational structure change; 3 the specified group is determined by the department level, the level body can choose independently, and the specified group includes one or more designated nodes.
  • the level value n of the specified node is non-zero, it must be set. Specifies the node at the first level until the specified node's level value n is 0, the specified group setting of the approval node Completion; this applies to the approval request submitted by the head of the department in the general department role approval.
  • the finance director of the finance department can review the billing information involved in the contract approval request submitted by the chairman, and ultimately it must be confirmed by the chairman. .
  • the department level n can be set to 0, that is, the submission role itself is selected as the approval role in the approval node. Before the approval process ends, the submission role itself can be approved and confirmed. Return to re-approval, choose to agree to the next step, and submit the review function review procedure to avoid the problem that the approval result is incorrect or the approval result does not match the expected behavior of the submitted role, and the new (resubmission) approval process is required, which reduces the system internal consumption. Improve the efficiency and reliability of the approval process.
  • the submitting role submitted a 10,000 yuan reimbursement approval request.
  • the content submitted by the submitting role is incorrect or other reasons.
  • the approved reimbursement amount is revised to 500 yuan.
  • the submitting role is submitted.
  • the system workflow setting personnel only need to select the level body and input the level value when setting the approval role.
  • Multiple approval processes can be effectively integrated into one approval process, which can effectively reduce The circulation condition and the circulation line reduce the workload of the system workflow setting personnel and improve the system reliability.
  • the expense reimbursement approval process in an approval node setting level approval (choose the submission role as the level body), and set the department level to 1, then all the expense reimbursement in the approval node is automatically submitted by the department of the department where the role is submitted. The supervisor role is approved.
  • the main body of the approval operation in the workflow is the role, and the role is an independent individual rather than a traditional group/class role. Even if employee/user changes occur (such as transfer, resignation, etc.), simply re-enter the new employee. Link to the role in the approval process; or change the employee approval authority, adjust the role approval authority in a targeted manner, no need to reset / adjust the process, easy to set up, no mistakes or omissions, will not affect the normal business Operation greatly improves the reliability of the workflow.
  • the role of the nature of the post number is the approval authority of the approval link node. The user determines which approval tasks are available through the role. The user can approve the operation by associating the role permissions; the understanding is clear and simple, and the nature of each post number/station number
  • the role is the smallest unit of the work subject, and this application can be well satisfied for each role's different requirements for approval.
  • the role of the application is a one-to-one relationship to the user.
  • a role can only be associated with a unique user at the same time.
  • the advantage of this is that the user can obtain the permission by associating the user with the role (ie, the user obtains the associated role). Permissions), and the role's permission changes are much less than the user permissions in the traditional mechanism.
  • the number of roles of the nature of the independent body 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 is simple and convenient, high efficiency, high reliability: the application of the entry/departure/adjustment in the approval process is simple, the operation subject of the approval of the workflow is the role, when the employee/user occurs There is no need to reset the approval process when the change is made (the user only needs to cancel or associate the role: the user who is no longer in the role of the job number/station number cancels the role association and takes over the role of the job number/station number. If the user associates the role of the post number, the user associated with the role automatically obtains the related tasks and permissions of the role in the approval workflow, and does not need to reset the approval workflow or re-authorize the roles in the workflow. Greatly improve the efficiency, security and reliability of process settings.
  • Zhang San is no longer working as a “buyer 3”, Zhang San cancels the association with the role; Li Si took over as “Purchaser 3”
  • Li Si is associated with the role, and Li Si automatically obtains the approval task and approval authority for the role of “Purchase 3” in the approval process.
  • the traditional rights management mechanism defines roles as groups, types of work, classes, etc.
  • the role is a one-to-many relationship with the user. In the actual system use process, it is often necessary to adjust the user's rights 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 and the like to make the role or authorization more efficient than the traditional group-based role, because the role of the group is not considered.
  • the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
  • the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
  • the traditional group-based role authorization method is error-prone.
  • 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 of associating the group of roles. What are the commonalities of multiple users. Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
  • the method of the present application is as follows: the transferred user associates several roles.
  • the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
  • Reason 1 Because the role of this application is equivalent to a station number/post number, different station number/post number The work content/permissions are different. For example, the salesperson 1 role under the sales department and the developer 1 role of the technical department are completely different two station numbers/post numbers, and their permissions are different; reason 2: If the department (sales department) of the salesperson 1 role is replaced with the technical department, and the role of the salesperson 1 is unchanged, there is a role in the technical department that has the authority of the sales department, which may lead to management confusion and security loopholes.
  • a role can exist in different approval nodes in the same approval process. In different approval nodes, the approval role can have different viewing and modification permissions for form fields.
  • a role is Chengdu sales manager 3, in the contract approval workflow, it exists in the Chengdu sales contract approval and Shanghai sales contract approval two approval nodes; for the Chengdu sales contract approval node, the role can be viewed at the time of approval
  • the customer name, contact person, contact information, product quantity, product unit price, contract amount and other fields of the contract, and the unit price and contract amount of the product can be modified; but the approval node of the sales contract in Shanghai cannot view the customer name and contact person.
  • the sensitive field content, such as contact information can not be modified (but can also be set to have viewing rights, no modification rights). In this way, you can customize the permissions of the role in the approval process.
  • FIG. 1 is a schematic diagram of a manner in which a system directly authorizes a user in the background art
  • FIG. 2 is a schematic diagram of a manner in which a system authorizes a group/class role in the background art
  • FIG. 3 is a schematic diagram of a manner in which a system directly authorizes a user and authorizes a group/class role role in the background art
  • Figure 4 is a tree diagram of the organization structure of the embodiment
  • FIG. 5 is a flowchart of a workflow generation method according to the present invention.
  • FIG. 6 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role
  • FIG. 7 is a schematic diagram of a workflow approval process according to the present invention.
  • FIG. 8 is a flowchart of a user-role authorization method according to the present invention.
  • an approval process includes a start node, at least one approval node, and an end node, including the following sequential steps: : Set the approval node approval mode to the signing, saying that the approval node is the signing node, the signing node summarizes the signing opinions of all the node approval roles, and provides reference for the approval role of the subsequent approval node; the second step: setting one of the signing nodes Or multiple approval roles.
  • the approval node approval mode is set to be signed, all the approval roles involved in the approval node do not have the modification permission for the form field content of the approval process.
  • the approval node has only one approval role, you can also choose the signing method. The purpose is to make the approval role only have the right to express opinions, but not the form content.
  • the contract amount is 100,000. If the approval role is selected first, and an approval role A has the right to modify the amount, the contract will be The amount is revised to 80,000, and the contract amount seen by other approval roles will be changed to 80,000. It will be meaningless to conduct the approval of the agreement based on the revised contract content.
  • the approval role is an independent individual, not a group/class.
  • One approval role can only be associated with a unique user at the same time, and one user is associated with one or more approval roles.
  • the setting method of the approval node in the approval process based on the signing process further includes a step of setting a responsible role for the signing node, and the role is responsible for selecting the next-level flow node of the signing node when the signing is performed, and there are multiple next-level flow nodes. When optional, choose one of the responsible roles.
  • Only the approval roles of all the approval roles involved in the sign-up node can enter the subsequent steps of the approval process; the process cannot be terminated by the sign-up node in the approval process, and at least one non-sign-up approval node is included in the subsequent nodes of the sign-up node.
  • the signing node gets a summary of the signing opinions of all the approval roles of the node. No matter what the signing opinions are, the signing node cannot reject the approval process.
  • the approval mode of the approval node can be selected (set) as the signing, and the signing node summarizes the comments of all the approval roles of the node, providing a powerful reference for the approval role of the subsequent approval node.
  • the salesperson 5 can initiate a signing process.
  • the sales department, the production department, and the finance department can choose to express their opinions. All the submissions must be submitted to the next step before the general manager approves. Will sign the opinion.
  • the setting method of the approval node in the approval process based on the signing process further includes a step of setting the permission role of the approval role to the content of the form field involved in the approval process, and viewing the content of the form field by different approval roles of the same signing node. Permissions can be different. It is more convenient to use and has a wide range of applications, which facilitates the hiding of some sensitive fields and avoids information leakage.
  • the sales-related approval role in the sign-up node can be set to view all fields; the production-related approval role can be set to view only the product model field, product quantity field, technical indicator field, Delivery time field; financial related approvers can be set to view only the product model, product unit price, contract amount, billing information, and payment method fields in the contract form.
  • an approval process includes a start node, at least one approval node, and an end node, including the following sequential steps: Step 1: Setting the approval node approval mode
  • the approval node is the signing node, the signing node summarizes the signing opinions of all the approval roles of the node, and provides reference for the approval role of the subsequent approval node; the second step: setting one or more approval roles of the signing node; It also includes a step of setting the signing node as an anonymous signing. After the anonymous signing is set, the non-existing role can not see the signing opinions submitted by the approval role, except that the approval role can see its own signing opinions.
  • An anonymous signing function is provided. After the anonymous signing is set, except for the approval role, the non-existing role can not see the signing opinions submitted by the approval role, and the approval roles are mutually protected. Influence, guarantee the authenticity and credibility of the results of the signing.
  • the second step described is an approval role setting method based on form fields and levels, specifically including a step of setting a system organization structure and a step of setting an approval role by department level: the setting of the system organization structure
  • the department head role a1 of the upper-level department A serves as the approval role of the approval node; 5 and so on; 6 when the department-level setting exceeds the highest-level department in the system organization structure, the department head of the highest-level department
  • the role assumes the approval role of the approval node; for example, for department D, the department level should be
  • the approval role of the approval node; the approval node has the department level n set to 0 when setting the approval role, that is, the submission role d2 itself is selected as the approval role in the approval node, and can be approved by the submission role d2 itself before the approval process ends.
  • Confirm choose to disqualify and return to re-approval, choose to agree to enter the next link, and submit the submitting role review procedure to avoid incorrect approval results or the approval result is inconsistent with the expected role of the submitted role and need to create (resubmit) the approval process.
  • the problem is to reduce the internal friction of the system and improve the efficiency and reliability of the approval process.
  • submit role d2 submitted a 10,000 yuan reimbursement approval request, because the submitted content d2 submitted incorrect content or other reasons, after multiple levels of approval, the approved reimbursement amount was revised to 500 yuan, before the end of the approval process, by Submit the role d2 as an approval role to review and confirm the problem. If you choose to disagree, you can return to re-approval, choose to agree to enter the next link, and do not need to create (resubmit) an approval process.
  • the department supervisor role d1 of the department D where the role d2 is located is submitted to the approval role of the approval node by the workflow approval process; (if the submit role is d1, which is the department supervisor role of the department D in which it is located, then The departmental supervisor role c1 of the upper-level department C of the department D in which the role is submitted serves as the approval role of the approval node.
  • the workflow approval process submits the upper-level department C of the department D where the role d2 is located.
  • the approval node is approved by the specified group; the specified group approval includes the following three cases.
  • this application has another advantage: you can choose roles of different nature, such as contract signing role, contract new role, contract responsibility role on the contract form.
  • the level of the role should not be judged, but the role should be judged by the contract.
  • the first approval node of the reimbursement form (reimbursement approval process) is to submit the superior of the role, and the other approval node is to be approved by the superior of the reimbursement role (the reimbursement role and the submission role may be different roles).
  • the traditional level approval method can only use the approval process to submit the role as the judgment standard to judge the department level. It is impossible to customize other roles or departments involved in the form as the criteria for judging the department level, and there are certain usage limitations.
  • the contract signing role is for leave, so that his colleague has initiated a contract approval for him, and the system determines that his colleague is the submitting role of the process, and the level judgment is based on the level approval.
  • Colleagues are the subject, and it is impossible to objectively reflect the department and position in which the contract signing role is located.
  • the signing role of the contract is the salesperson of the marketing department1
  • the colleague role is the R&D personnel of the R&D department.
  • the contract should be approved by the head of the department in which the role is assigned, the head of the marketing department, and the approval level of the approval node is set to At 1 o'clock, the system will be assigned to the supervisor-R&D department supervisor of the department where the R&D staff 1 is located for approval.
  • the allocation process is incorrectly assigned and inconvenient to use.
  • the application can select the signing role in the contract form as the level subject according to the need, and sign the role (rather than defaulting to submit the role) as the standard judgment department level, thereby determining the approval role as the marketing department supervisor role.
  • the use is more flexible, convenient and versatile.
  • the system provides the approval mechanism for the highest level department heads to avoid the problem that the top level department heads cannot complete the approval process through level approval.
  • the chairman of the company's top leadership submits an approval request
  • the chairman does not have a higher-level department, but sets a designated group to approve the approval request submitted by the chairman.
  • the designated group approval includes one of the following three situations: 1
  • the designated group consists of one or more approval roles.
  • a member of a plurality of supervisory committees constitutes a designated group, and the chairman's approval request is approved by the members of the board of supervisors;
  • the group is determined by the department level.
  • the level body only the level body selected by the approval node can be used, and the level value n can only be set to 0; this case is used to respond to changes in the organizational structure of the enterprise, for example, a company
  • the former top-level supervisor is the general manager, and after the organizational structure changes, the board of directors is added.
  • the highest-level supervisor becomes the chairman.
  • the level of the approval node is 0.
  • the approval role automatically becomes the chairman, instead of being fixed as the general manager.
  • the approval role cannot adapt to the problem of organizational structure change; 3 the specified group is determined by the department level, the level body can choose independently, and the specified group includes one or more designated nodes.
  • the level value n of the specified node is non-zero, it must be set. Specifies the node at the first level until the specified node's level value n is 0, the specified group setting of the approval node Completion; this applies to the approval request submitted by the head of the department in the general department role approval.
  • the finance director of the finance department can review the billing information involved in the contract approval request submitted by the chairman, and ultimately it must be confirmed by the chairman. .
  • the approval authority of the corresponding approval role in the level is authorized, and the approval authority of the corresponding approval role in this level is the same.
  • the generation of the approval process includes the following steps: S1: constructing a three-layer structure model of user-role-permission, wherein: role layer: the operation subject of the process approval in the workflow is a role Each role is an independent individual, not a group/class. A role can only be associated with a unique user at the same time, and a user is associated with one or more roles; the role is composed of: job name + post number; The privilege layer is composed of the privilege that needs to be used in the execution of the workflow. The privilege is directly authorized to the role. The user tier: the user determines the approval task in the approval process through the associated role, and performs the approval operation with the privilege of the associated role. S2: As shown in FIG.
  • an approval process is generated based on a three-layer structure model, and an approval process includes a start node, at least one approval node, and an end node: a start node: initiate a role initiation/application/submission workflow as a start node, or The first approval node acts as the starting node.
  • the system determines the approval process based on the form submitted by the initiating role, and designs one or more approval processes for the form that needs to have a workflow, but a role can only select one of the approval processes under the form (the same role can only exist in the same In one of the processes of a form); for example:
  • Approval node Set the approval node approval mode and select the approval role, and authorize the approval role; End node: When the approval process flow goes to this node, the approval process ends, the end node does not perform the approval operation; or the last approval node is used as the End the node, which needs to be approved.
  • S3 The user determines the approval task to be processed according to the associated role, and performs an approval operation according to the rights of the associated role.
  • a role is Chengdu sales manager 3, in the contract approval workflow, it exists in the Chengdu sales contract approval and Shanghai sales contract approval two approval nodes; for the Chengdu sales contract approval node, the role can be viewed at the time of approval
  • the customer name, contact person, contact information, product quantity, product unit price, contract amount and other fields of the contract, and the unit price and contract amount of the product can be modified; but the approval node of the sales contract in Shanghai cannot view the customer name and contact person.
  • the sensitive field content, such as contact information can not be modified (but can also be set to have viewing rights, no modification rights).
  • the step S1 includes the following sequence of sub-steps: S101: creating a role, each role being an independent individual, not a group/class; S102: creating for S101 The role is separately authorized; S103: associate the user to the role, wherein one role can only associate with the unique user in the same period, and one user associates one or more roles; step S101 is preceded, but step S102 and step S103 have no previous Order relationship.
  • the user determines the privilege through its association with the role. If the privilege of the user is to be modified, the privilege possessed by the role is adjusted to achieve the purpose of changing the privilege of the user associated with the role. Once a user associates a role, that user has all the operational privileges for that role.
  • the role of the role to the user is one-to-one (when the role is associated with a user, other users can no longer associate the role; if the role is not associated with the user, it can be associated with other users).
  • 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/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application is equivalent Job number (The job number here is not a post, one post may have multiple employees at the same time, and one job number can only correspond to one employee at the same time).
  • a company system can create the following roles: general manager, deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • general manager deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • Zhang San serves as the company's deputy general manager 2, and also serves as a sales manager in Beijing, then Zhang The three roles to be associated are Deputy General Manager 2 and Beijing Sales Manager. Zhang San has the rights to these two roles.
  • the system's authorization for a role includes, but is not limited to, authorization of a form, authorization of a menu, or authorization of a function.
  • Authorization for the operation of the form includes but is not limited to additions and deletions.
  • roles are group/class/post/position/work type, and one role can correspond to multiple users.
  • the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
  • Authorization for a role includes, but is not limited to, authorization of a form, authorization of a menu, or authorization of a function.
  • the role belongs to the department, and the role is unique under the department, and the role is authorized according to the work content of the role.
  • the specific operation process includes: (1) canceling the association between the user and the role in the original department; and (2) associating the user with the role in the new department.
  • the role After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • the step S1 described includes the following sequence of sub-steps: S101: establishing a role, each role being an independent individual, not a group/class; S102: associating a user to a role, wherein a role only during the same time period A unique user can be associated, and one user associates one or more roles; S103: Authorize the roles established by S101 separately.
  • the role belongs to the department, and the role is unique under the department, and the role is authorized according to the work content of the role.
  • the workflow control method further includes a user cross-department management step, which includes: (1) canceling the association between the user and the role in the original department; and (2) associating the user with the role in the new department.
  • the composition of the character is: 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/work type.
  • 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 have the authority 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 of the role of “after-sales manager” under the after-sales department.
  • This application authorizes the role of the nature of the post number/station number, and the user associates the role to determine the authority, then the control of the user right is achieved through a simple user-role relationship, allowing the authority Control is simple, easy to operate, clear and clear, and greatly enhances the efficiency of authorization and the reliability of authorization.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本发明公开了一种基于会签的审批节点在审批流程中的设置方法，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；第二步：设置会签节点的一个或多个审批角色。本发明会签节点汇总会签意见，为在后的审批节点的审批角色提供有力参考。工作流中审批操作的主体是角色，而且这个角色是独立的个体，即使发生员工/用户变动，只需将新员工重新关联到审批流程中的角色即可；或者是员工审批权限发生变化，针对性调整该角色审批权限即可，无需重新设置/调整流程，设置方便，不会出错或遗漏，不会影响企业的正常运营，极大提高了工作流的可靠性。

Description

基于会签的审批节点在审批流程中的设置方法 技术领域
本发明涉及一种ERP等管理软件系统的审批节点审批方法，特别是涉及一种基于会签的审批节点在审批流程中的设置方法。
 背景技术
基于角色的访问控制（RBAC）是近年来研究最多、思想最成熟的一种数据库权限管理机制，它被认为是替代传统的强制访问控制（MAC）和自主访问控制（DAC）的理想候选。传统的自主访问控制的灵活性高但是安全性低，强制访问控制安全性高但是限制太强；基于角色的访问控制两者兼具，不仅易于管理而且降低了复杂性、成本和发生错误的概率，因而近年来得到了极大的发展。基于角色的访问控制（RBAC）的基本思想是根据企业组织视图中不同的职能岗位划分不同的角色，将数据库资源的访问权限封装在角色中，用户通过被赋予不同的角色来间接访问数据库资源。
在大型应用系统中往往都建有大量的表和视图，这使得对数据库资源的管理和授权变得十分复杂。由用户直接管理数据库资源的存取和权限的收授是十分困难的，它需要用户对数据库结构的了解非常透彻，并且熟悉SQL语言的使用，而且一旦应用系统结构或安全需求有所变动，都要进行大量复杂而繁琐的授权变动，非常容易出现一些意想不到的授权失误而引起的安全漏洞。因此，为大型应用系统设计一种简单、高效的权限管理方法已成为系统和系统用户的普遍需求。
基于角色的权限控制机制能够对系统的访问权限进行简单、高效的管理，极大地降低了系统权限管理的负担和代价，而且使得系统权限管理更加符合应用系统的业务管理规范。
然而，传统基于角色的用户权限管理和工作流控制方法均采用“角色对用户一对多”的关联机制，其“角色”为组/类性质，即一个角色可以同时对应/关联多个用户，角色类似于岗位/职位/工种等概念，这种关联机制下对用户权限的授权基本分为以下三种形式：1、如图1所示，直接对用户授权，缺点是工作量大、操作频繁且麻烦；审批流程中审批节点的审批操作主体是用户，工作流审批节点直接选择员工/用户作为审批主体，当发生员工变动（如调岗、离职等），该员工涉及到的所有流程必须要作相应调整，特别是对于公司管理人员，其涉及到的审批流程多，流程调整的工作量大、繁杂，容易出错或遗漏，影响企业的正常运营，甚至造成不可预估的损失。
即使只是员工审批权限发生变化，也需要对该员工涉及到的流程作出相应调整，也存在以上类似问题。
2、如图2所示，对角色（类/组/岗位/工种性质）进行授权（一个角色可以关联多个用户），用户通过角色获得权限，审批操作主体是组/类性质角色；3、如图3所示，以上两种方式结合。
以上的表述中，2、3均需要对类/组性质的角色进行授权，而通过类/组/岗位/工种性质的角色进行授权和工作流控制的方式有以下缺点：1、用户权限变化时的操作难：在实际的系统使用过程中，经常因为在运营过程中需要对用户的权限进行调整，比如：在处理员工权限变化时，角色关联的某个员工权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
员工/用户的审批权限发生变化时，要么员工/用户脱离角色，工作流审批节点直接选择员工/用户作为审批主体，要么新增角色来满足审批流程的要求。第一种方式，当发生员工变动（如调岗、离职等），该员工涉及到的所有流程必须要作相应调整，特别是对于公司管理人员，其涉及到的审批流程多，流程调整的工作量大、繁杂，容易出错或遗漏，影响企业的正常运营，甚至造成不可预估的损失。即使只是员工审批权限发生变化，也需要对该员工涉及到的流程作出相应调整，也存在以上类似问题。第二种方式，新增角色便涉及到角色的新建、关联、授权工作，特别在角色多、角色关联的用户也多的情况下，角色具体关联了哪些用户是很难记住的。
2、要长期记住角色包含的具体权限难：若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，相近角色的权限也很容易混淆；若要关联新的用户，无法准确判断应当如何选择关联。
3、因为用户权限变化，则会造成角色创建越来越多（若不创建新角色，则会大幅增加直接对用户的授权），更难分清各角色权限的具体差别。
4、调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
 技术问题
本发明的目的在于克服现有技术的不足，提供一种基于会签的审批节点在审批流程中的设置方法，审批节点的审批方式可选择（设置）为会签，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供有力参考；采用基于角色的审批流程控制方法，工作流中审批操作的主体是角色，当员工/用户发生变化时，只需将用户重新关联到审批流程中的角色，或是针对性调整该角色权限即可，无需重新设置流程，设置方便。
 技术解决方案
本发明的目的是通过以下技术方案来实现的：基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；所述的会签意见包括同意/通过（肯定性质）、不同意/不通过（否定性质）；第二步：设置会签节点的一个或多个审批角色。
所述的审批角色是独立的个体，而非组/类，同一时段一个审批角色只能关联唯一的用户，而一个用户关联一个或多个审批角色。
只有会签节点所涉及到的所有审批角色都提交会签意见后才能进入审批流程的后续步骤；会签节点得到的是该节点所有审批角色的会签意见的汇总，无论会签意见如何，会签节点都不能驳回审批流程。
审批流程中不能以会签节点结束流程，所述会签节点的后续节点中至少有一个非会签的审批节点。
基于会签的审批节点在审批流程中的设置方法，还包括一个为会签节点设置一个负责角色的步骤，负责角色在会签时选择该会签节点的下一级流转节点，当下一级流转节点有多个可选时，由负责角色选择其中一个。
基于会签的审批节点在审批流程中的设置方法，还包括一个设置审批角色对审批流程涉及的表单字段内容查看权限的步骤，同一会签节点的不同审批角色对表单字段内容的查看权限可以不同。
设置审批节点审批方式为会签后，该会签节点所涉及的所有审批角色对审批流程的表单字段内容都不具备修改权限。
所述审批流程的生成包括以下步骤：S1：构建用户-角色-权限的三层结构模型，其中：角色层：工作流中流程审批的操作主体为角色，每个角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；权限层：由工作流执行中所需要使用的权限构成，权限直接授权给角色；用户层：用户通过关联的角色确定审批流程中的审批任务，并以关联角色的权限进行审批操作；S2：基于三层结构模型生成审批流程，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点：开始节点：审批流程开始；审批节点：设置审批节点审批方式并选择审批角色，并对审批角色进行授权；结束节点：审批流程结束；S3：用户根据其关联的角色确定所需处理的审批任务，并根据关联的角色的权限进行审批操作。
所述的第二步采用基于表单字段和级别的审批角色设置方法，具体包括一个设置系统组织结构的步骤和一个按部门级别设置审批角色的步骤：所述设置系统组织结构的步骤包括以下子步骤：SS1：创建系统组织结构中所包含的部门及角色；SS2：设置各部门之间的层级关系，并设置各部门的部门主管角色；所述按部门级别设置审批角色的步骤包括：SSS1:选择以按级别方式进行审批角色的设置；SSS2:选择审批流程对应表单中的角色性质字段、部门性质字段或者该审批流程的提交角色中的一个，作为级别主体；SSS3:填写具体的级别数值n，n为≥0的正整数（N的值也可采用其他符号代替，比如a、b、c、d，b比a大一级，c比a大两级，d比a大三级，以此类推）：（1）选择审批流程对应表单中的角色性质字段作为级别主体，以该字段对应的角色为判断标准判断级别：①当n=0时，由该字段对应的角色担任该审批节点的审批角色；②当n=1时，由该字段对应的角色所在部门的部门主管角色担任该审批节点的审批角色；若该字段对应的角色为其所在部门的部门主管角色，则由该字段对应的角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；③当n=2时，由该字段对应的角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；④当n=3时，由该字段对应的角色所在部门的上上一级部门的部门主管角色担任该审批节点的审批角色；⑤当n=4时，由该字段对应的角色所在部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；⑥以此类推；⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；⑧当n≥1时，需要设置“该字段对应的角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批；（2）选择审批流程对应表单中的部门性质字段作为级别主体，以该字段对应的部门为判断标准判断级别：①当n=0时，由该字段对应的部门的部门主管角色担任该审批节点的审批角色；②当n=1时，由该字段对应的部门的上一级部门的部门主管角色担任该审批节点的审批角色；③当n=2时，由该字段对应的部门的上上一级部门的部门主管角色担任该审批节点的审批角色；④当n=3时，由该字段对应的部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；⑤以此类推；⑥当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；⑦当n≥1时，需要设置“该字段对应的部门无上一级部门时”该审批节点由指定组审批；（3）选择审批流程的提交角色作为级别主体，以该提交角色为判断标准判断级别：①当n=0时，由工作流审批流程提交角色担任该审批节点的审批角色；②当n=1时，由工作流审批流程提交角色所在部门的部门主管角色担任该审批节点的审批角色；若提交角色为其所在部门的部门主管角色，则由提交角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；③当n=2时，由工作流审批流程提交角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；④当n=3时，由工作流审批流程提交角色所在部门的上上一级部门的部门主管角色担任该审批节点的审批角色；⑤当n=4时，由工作流审批流程提交角色所在部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；⑥以此类推；⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；⑧当n≥1时，需要设置“提交角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批；所述指定组审批包括以下三种情况中的一种：（1）指定组由一个或多个审批角色构成；（2）指定组由部门级别确定，选择级别主体时只能沿用该审批节点所选择的级别主体，且级别数值n只能设置为0；（3）指定组由部门级别确定，级别主体能够自主选择，指定组中包括一个或多个指定节点，当指定节点的级别数值n为非0时必须设置下一级指定节点，直到指定节点的级别数值n为0时，该审批节点的指定组设置完成。
基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；第二步：设置会签节点的一个或多个审批角色；还包括一个设置该会签节点为匿名会签的步骤，设置为匿名会签后，除了该审批角色自己能够看到自己的会签意见以外，其他非本审批角色均无法看到该审批角色提交的会签意见。
 有益效果
本发明的有益效果是：1、审批节点的审批方式可选择（设置）为会签，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供有力参考。
例如：合同签订前，销售人员5可发起一个会签流程（即：该审批流程中包括一个会签节点），可选择销售部、生产部、财务部会签表达意见（即选择代表以上三个部门的角色，表达各自部门的会签意见），必须全部提交会签意见后才进入下一步，总经理审批时可参考大家给出的会签意见。
会签与投票的区别是：会签只是征求大家提供意见，只是意见的汇总，为后续审批提供参考，无论会签意见如何，都不能驳回审批流程。而投票时，该审批节点的审批结果由投票者的投票结果确定，会得到一个审批结果：通过/同意或不通过/不同意，可以驳回审批流程。
2、同一会签节点的不同审批角色对表单字段内容的查看权限可以不同，使用更方便，适用范围广，便于实现部分敏感字段的隐藏，避免造成信息泄露。
例如：对于某合同审批流程，会签节点中的销售相关审批角色可以设置为能够查看所有字段；生产相关审批角色可以设置为只能查看合同表单中的产品型号字段、产品数量字段、技术指标字段、交货时间字段；财务相关审批者可以设置为只能查看合同表单中的产品型号、产品单价、合同金额、开票信息、付款方式字段。
3、必须先确定审批方式后选择审批角色，避免先选审批角色时有些审批角色对表单字段内容有修改权限，一旦表单字段内容被修改则无法实现会签审批，因为各个审批角色在并行审批，修改表单数据会影响其他审批角色审批。审批方式确定为会签后，系统则限制所有涉及到的审批角色都无表单修改权限，确保客观体现会签内容。
举例：合同签订前会签是否签订该合同，设定了5个审批角色，合同金额为10万，如果先选审批角色，而审批角色中有某审批角色A具有对金额的修改权限，其将合同金额修改为8万，其他审批角色审批时看到的合同金额则会变为8万，基于修改后的合同内容进行会签审批将无任何意义。
4、当审批节点只有一个审批角色时，也可以选择会签方式，目的是让该审批角色只有意见表达的权利，而不能修改表单内容。
5、提供了匿名会签功能，设置为匿名会签后，除了该审批角色自己能够看到自己的会签意见以外，其他非本审批角色均无法看到该审批角色提交的会签意见，避免审批角色之间受到相互影响，保证会签结果的真实性和可信度。
6、传统级别审批方式只能以审批流程提交角色作为判断标准来判断部门级别，无法自定义以表单中涉及到的其它角色或部门作为判断部门级别的标准，存在一定的使用局限性。
举例：对于一个合同审批流程，合同的签订角色请假了，让其同事替他发起了一个合同的审批，而系统认定其同事为流程的提交角色，在按级别审批时对于级别的判断均以其同事为准，无法客观体现合同签订角色所在的部门及职位。例如，合同的签订角色为市场部的销售人员1，其同事角色为研发部的研发人员1，原本该合同应由签订角色所在部门的主管-市场部主管角色审批，设置审批节点的审批级别为1时，系统会分配给研发人员1所在部门的主管-研发部主管角色进行审批，出现了审批流程的分配错误，使用不方便。
本申请可根据需要自定义以表单中涉及到的角色性质字段、部门性质字段或提交角色作为判断部门级别的标准，例如，在设置审批节点时，可以选择合同表单中的签订角色作为级别主体，以签订角色（而非一味默认为提交角色）作为标准判断部门级别，以此确定审批角色为市场部主管角色，使用更灵活、方便，通用性强。
7、系统提供了最高级别部门主管的审批机制，避免出现最高级别部门主管无法通过级别审批方式完成审批流程的问题。
举例：企业的最高级领导董事长提交审批请求时，在级别审批中，董事长虽没有上级部门，但设置了指定组来审批董事长提交的审批请求。
指定组审批包括以下三种情况中的一种：①指定组由一个或多个审批角色构成，例如，由多个监事会的成员构成指定组，董事长的审批请求由监事会成员进行审批；②指定组由部门级别确定，选择级别主体时只能沿用该审批节点所选择的级别主体，且级别数值n只能设置为0；此种情况用于应对企业组织结构发生变化的情况，例如，某公司原最高级别主管为总经理，而组织结构变化后增设了董事会，最高级别主管变为董事长，审批节点中级别数值为0则审批角色自动变为董事长，而不是固定为总经理，避免出现审批角色不能适配组织结构变化的问题；③指定组由部门级别确定，级别主体能够自主选择，指定组中包括一个或多个指定节点，当指定节点的级别数值n为非0时必须设置下一级指定节点，直到指定节点的级别数值n为0时，该审批节点的指定组设置完成；此种情况适用于普通部门角色审批最高级部门主管所提交的审批请求，例如，财务部门的财务主管可以审核董事长所提交的合同审批请求中涉及的开票信息，最终要由董事长确认。
8、审批节点在设置审批角色时部门级别n可以设置为0，即选择提交角色本身作为审批节点中的审批角色，在审批流程结束前，可以由提交角色本身进行审批确认，选择不同意后可返回重新审批，选择同意进入下一环节，多出了提交角色复核程序，避免出现审批结果不正确或审批结果与提交角色的预期不符而需要新建（重新提交）审批流程的问题，减少了系统内耗，提高了审批流程效率和可靠性。
举例：提交角色提交了一个10000元的报销审批请求，因提交角色所提交的内容有误或其他原因，经过多级审批后核准报销金额被修改为500元，在审批流程结束之前，由提交角色作为审批角色进行复核确认即可发现问题，选择不同意后可返回重新审批，选择同意进入下一环节，无需新建（重新提交）一个审批流程。
9、通过按部门级别设置审批角色的方式，系统工作流设置人员在设置审批角色时只需选择级别主体并输入级别数值即可，多个审批流程能够有效整合在一个审批流程内，能够有效减少流转条件和流转线路，降低了系统工作流设置人员的工作量，提高了系统可靠性。比如：在费用报销审批流程中，在一个审批节点设置级别审批（选择提交角色为级别主体），并设置部门级别为1，则所有的费用报销在该审批节点自动由提交角色所在的部门的部门主管角色进行审批。
10、工作流中审批操作的主体是角色，而且这个角色是独立的个体而不是传统组/类性质的角色，即使发生员工/用户变动（如调岗、离职等），只需将新员工重新关联到审批流程中的角色即可；或者是员工审批权限发生变化，针对性调整该角色审批权限即可，无需重新设置/调整流程，设置方便，不会出错或遗漏，不会影响企业的正常运营，极大提高了工作流的可靠性。以岗位号性质的角色为审批环节节点的审批授权主体，用户通过角色确定其有哪些审批任务，用户通过关联角色的权限进行审批操作即可；理解清晰简单，每个岗位号/工位号性质的角色是工作主体的最小单位，针对每个角色对审批的不同需求，本申请均能够很好满足。
11、本申请角色对用户是一对一的关系，同一时段一个角色只能关联唯一的用户，这样做的好处是，只要将用户关联到角色即可获得权限（即用户获得其关联的角色的权限），而且角色的权限变更比传统机制中的用户权限变更要少得多。独立体性质（岗位号/工位号性质）的角色数量变化小，虽然员工流动大，但岗位号/工位号的变化小（甚至在一定时段内是没有变化的，即角色没有变化），这样将极大简化用户的权限管理，减少系统的开销。
12、动态管理、入职调岗等的操作简单方便，效率高，可靠性高：入职/离职/调岗在审批流程中的应用简单，工作流程的审批的操作主体是角色，当员工/用户发生变化时不用重新设置审批流程（用户只需取消或关联角色即可：不再任职该岗位号/工位号的角色的用户就取消该角色关联，接手任职该岗位号/工位号的角色的用户关联该岗位号的角色，则关联该角色的用户自动就获得了该角色在审批工作流中的相关任务和权限，无需对审批工作流进行重新设置或对工作流中的角色进行重新授权，极大地提高了流程设置的效率、安全性和可靠性。
举例：因张三用户离职或调岗等原因，张三不再做“采购员3”这个角色的工作，则张三取消了与该角色的关联；另外李四接手做“采购员3”这个角色的工作，则将李四关联该角色，则李四自动获得了审批流程中“采购员3”这个角色的审批任务和审批权限。
13、传统的权限管理机制将角色定义为组、工种、类等性质，角色对用户是一对多的关系，在实际的系统使用过程中，经常因为在运营过程中需要对用户的权限进行调整，比如：在处理员工权限变化的时候，角色关联的某个员工的权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
但在本申请的方法下，因为角色是一个独立的个体，则可以选择改变角色权限即可达到目的。本申请的方法，虽然看起来在系统初始化时会增加工作量，但可以通过复制等方法，使其创建角色或授权的效率高于传统以组为性质的角色，因为不用考虑性质为组的角色在满足关联用户时的共通性，本申请方案会让权限设置清晰，明了；尤其是在系统使用一段时间后（用户/角色权限动态变化），该申请方案能为系统使用方大幅度提高系统使用中的权限管理效率，使动态授权更简单，更方便，更清晰、明了，提高权限设置的效率和可靠性。
14、传统以组为性质的角色授权方法容易出错，本申请方法大幅降低了授权出错的几率，因为本申请方法只需考虑作为独立个体的角色，而不用考虑传统方法下关联该组性质角色的多个用户有哪些共通性。即使授权出错也只影响关联到该角色的那一个用户，而传统以组性质的角色则会影响关联到该角色的所有用户。即使出现权限授权错误，本申请的修正方法简单、时间短，而传统以组性质的角色在修正错误时需要考虑关联到该角色的所有用户的权限共通性，在功能点多的情况下不仅修改麻烦、复杂，非常容易出错，且很多情况下只能新创建角色才能解决。
15、在传统以组为性质的角色授权方法下，若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，若要关联新的用户，无法准确判断应当如何选择关联。本申请方法的角色本身就具有岗位号/工位号的性质，选择一目了然。
16、调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
本申请方法则为：被调岗用户关联了几个角色，在调岗时，首先取消用户与原部门内的角色的关联（被取消的这几个角色可以被重新关联给其他用户），然后将用户与新部门内的角色进行关联即可。操作简单，不会出错。
17、角色归属于部门，则该角色的部门不能被更换，角色为什么不能更换部门：理由1：因为本申请的角色性质等同于一个工位号/岗位号，不同的工位号/岗位号的工作内容/权限是不一样的，如销售部门下的销售员1角色和技术部门的开发人员1角色是完全不同的两个工位号/岗位号，其权限是不同的；理由2：若将销售员1角色的所属部门（销售部）更换为技术部，其销售人员1这个角色的权限不变，则在技术部存在拥有销售部权限的一个角色，这样会导致管理混乱及安全漏洞。
18、一个角色在同一个审批流程中能够存在于不同审批节点，不同审批节点中该审批角色对表单字段的查看、修改权限可不同。优势举例：某角色为成都销售经理3，在合同审批工作流中，其存在于成都销售合同审批和上海销售合同审批两个审批节点；对于成都销售合同的审批节点，在审批时该角色可查看该合同的客户名称、联系人、联系方式、产品数量、产品单价、合同金额等全部字段内容，且可修改产品单价、合同金额；但在上海销售合同的审批节点却无法查看客户名称、联系人、联系方式等敏感字段内容，更不能作任何修改（但也可以设为具有查看权限，没有修改权限）。这样一来，能够自定义地设置角色在审批流程中的权限。
在审批节点选择一个或多个审批角色，在审批节点设置审批角色的权限，针对每个审批节点的每个审批角色能够进行独立的权限设置。例如：在一个合同表单的审批流程中，有某个审批节点设置了2个审批角色，分别为角色A、角色B，可设置角色A能够看到该合同表单中的合同金额字段及该字段的值，也可以看到该合同表单中的客户地址字段及该字段的值；设置角色B不能看到合同表单中的合同金额字段，或能看到合同金额字段但看不到该字段的值，看不到值时可用其他符号显示，比如*号，角色B能够看到该合同表单中的客户地址字段及该字段的值。
 附图说明
图1为背景技术中系统直接对用户进行授权的方式示意图；
图2为背景技术中系统对组/类性质角色进行授权的方式示意图；
图3为背景技术中系统对用户直接授权和对组/类性质角色授权相结合的方式示意图；
图4为实施例中系统组织结构树状图；
图5为本发明工作流生成方法流程图；
图6为本发明系统通过独立个体性质角色对用户进行授权的方式示意图；
图7为本发明工作流审批流程示意图；
图8为本发明用户-角色授权方法流程图。
 本发明的实施方式
下面结合附图进一步详细描述本发明的技术方案，但本发明的保护范围不局限于以下所述。
【实施例1】如图7所示，基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；第二步：设置会签节点的一个或多个审批角色。
设置审批节点审批方式为会签后，该会签节点所涉及的所有审批角色对审批流程的表单字段内容都不具备修改权限。当审批节点只有一个审批角色时，也可以选择会签方式，目的是让该审批角色只有意见表达的权利，而不能修改表单内容。
必须先确定审批方式后选择审批角色，避免先选审批角色时有些审批角色对表单字段内容有修改权限，一旦表单字段内容被修改则无法实现会签审批，因为各个审批角色在并行审批，修改表单数据会影响其他审批角色审批。审批方式确定为会签后，系统则限制所有涉及到的审批角色都无表单修改权限，确保客观体现会签内容。
举例：合同签订前会签是否签订该合同，设定了5个审批角色，合同金额为10万，如果先选审批角色，而审批角色中有某审批角色A具有对金额的修改权限，其将合同金额修改为8万，其他审批角色审批时看到的合同金额则会变为8万，基于修改后的合同内容进行会签审批将无任何意义。
所述的审批角色是独立的个体，而非组/类，同一时段一个审批角色只能关联唯一的用户，而一个用户关联一个或多个审批角色。
基于会签的审批节点在审批流程中的设置方法，还包括一个为会签节点设置一个负责角色的步骤，负责角色在会签时选择该会签节点的下一级流转节点，当下一级流转节点有多个可选时，由负责角色选择其中一个。
只有会签节点所涉及到的所有审批角色都提交会签意见后才能进入审批流程的后续步骤；审批流程中不能以会签节点结束流程，所述会签节点的后续节点中至少有一个非会签的审批节点。
会签节点得到的是该节点所有审批角色的会签意见的汇总，无论会签意见如何，会签节点都不能驳回审批流程。
审批节点的审批方式可选择（设置）为会签，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供有力参考。
例如：合同签订前，销售人员5可发起一个会签流程，可选择销售部、生产部、财务部会签表达意见，必须全部提交会签意见后才进入下一步，总经理审批时可参考大家给出的会签意见。
会签与投票的区别是：会签只是征求大家提供意见，只是意见的汇总，为后续审批提供参考，无论会签意见如何，都不能驳回审批流程。而投票时，该审批节点的审批结果由投票者的投票结果确定，会得到一个审批结果：通过/同意或不通过/不同意，可以驳回审批流程。
【实施例2】基于会签的审批节点在审批流程中的设置方法，还包括一个设置审批角色对审批流程涉及的表单字段内容查看权限的步骤，同一会签节点的不同审批角色对表单字段内容的查看权限可以不同。使用更方便，适用范围广，便于实现部分敏感字段的隐藏，避免造成信息泄露。
例如：对于某合同审批流程，会签节点中的销售相关审批角色可以设置为能够查看所有字段；生产相关审批角色可以设置为只能查看合同表单中的产品型号字段、产品数量字段、技术指标字段、交货时间字段；财务相关审批者可以设置为只能查看合同表单中的产品型号、产品单价、合同金额、开票信息、付款方式字段。
【实施例3】基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；第二步：设置会签节点的一个或多个审批角色；还包括一个设置该会签节点为匿名会签的步骤，设置为匿名会签后，除了该审批角色自己能够看到自己的会签意见以外，其他非本审批角色均无法看到该审批角色提交的会签意见。
提供了匿名会签功能，设置为匿名会签后，除了该审批角色自己能够看到自己的会签意见以外，其他非本审批角色均无法看到该审批角色提交的会签意见，避免审批角色之间受到相互影响，保证会签结果的真实性和可信度。
【实施例4】所述的第二步采用基于表单字段和级别的审批角色设置方法，具体包括一个设置系统组织结构的步骤和一个按部门级别设置审批角色的步骤：所述设置系统组织结构的步骤包括以下子步骤：SS1：创建系统组织结构中所包含的部门及角色；SS2：设置各部门之间的层级关系，如图4所示，部门A比部门B高一级，部门A比部门C高两级……；并设置各部门的部门主管角色；所述按部门级别设置审批角色的步骤包括：SSS1:选择以按级别方式进行审批角色的设置；SSS2:选择审批流程对应表单中的角色性质字段、部门性质字段或者该审批流程的提交角色中的一个，作为级别主体；SSS3:填写具体的级别数值n，n为≥0的正整数（N的值也可采用其他符号代替，比如a、b、c、d，b比a大一级，c比a大两级，d比a大三级，以此类推）：（1）选择审批流程对应表单中的角色性质字段作为级别主体，以该选定的角色为判断标准判断级别，例如，流程的提交角色为d2，但选择的表单中的角色性质字段为签订角色，该签订角色为角色d3：①当n=0时，由选定的角色d3担任该审批节点的审批角色；②当n=1时，由选定的角色d3所在部门D的部门主管角色d1担任该审批节点的审批角色；若选定的角色为其所在部门的部门主管角色，则由选定的角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；③当n=2时，由选定的角色d3所在部门D的上一级部门C的部门主管角色c1担任该审批节点的审批角色；④当n=3时，由选定的角色d3所在部门D的上上一级部门B的部门主管角色b1担任该审批节点的审批角色；⑤当n=4时，由选定的角色d3所在部门D的上上上一级部门A的部门主管角色a1担任该审批节点的审批角色；⑥以此类推；⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；例如：对于角色d3而言，部门级别最高应为4，当部门级别设置为6时，由最高级别部门A的部门主管角色a1担任该审批节点的审批角色。
⑧当n≥1时，需要设置“选定的角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批。
（2）选择审批流程对应表单中的部门性质字段作为级别主体，以该选定的部门为判断标准判断级别，例如，选择的表单中的部门性质字段为签订部门，该签订部门为部门D：①当n=0时，由选定部门D的部门主管角色d1担任该审批节点的审批角色；②当n=1时，由选定部门D的上一级部门C的部门主管角色c1担任该审批节点的审批角色；③当n=2时，由选定部门D的上上一级部门B的部门主管角色b1担任该审批节点的审批角色；④当n=3时，由选定部门D的上上上一级部门A的部门主管角色a1担任该审批节点的审批角色；⑤以此类推；⑥当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；例如：对于部门D而言，部门级别最高应为3，当部门级别设置为6时，由最高级别部门A的部门主管角色a1担任该审批节点的审批角色。
⑦当n≥1时，需要设置“选定的部门无上一级部门时”该审批节点由指定组审批。
（3）选择审批流程的提交角色作为级别主体，以该提交角色为判断标准判断级别，例如，若提交角色为角色d2，则：①当n=0时，由工作流审批流程提交角色d2担任该审批节点的审批角色；审批节点在设置审批角色时部门级别n可以设置为0，即选择提交角色d2本身作为审批节点中的审批角色，在审批流程结束前，可以由提交角色d2本身进行审批确认，选择不同意后可返回重新审批，选择同意进入下一环节，多出了提交角色复核程序，避免出现审批结果不正确或审批结果与提交角色的预期不符而需要新建（重新提交）审批流程的问题，减少了系统内耗，提高了审批流程效率和可靠性。
举例：提交角色d2提交了一个10000元的报销审批请求，因提交角色d2所提交的内容有误或其他原因，经过多级审批后核准报销金额被修改为500元，在审批流程结束之前，由提交角色d2作为审批角色进行复核确认即可发现问题，选择不同意后可返回重新审批，选择同意进入下一环节，无需新建（重新提交）一个审批流程。
②当n=1时，由工作流审批流程提交角色d2所在部门D的部门主管角色d1担任该审批节点的审批角色；（若提交角色是d1，他是其所在部门D的部门主管角色，则由提交角色所在部门D的上一级部门C的部门主管角色c1担任该审批节点的审批角色）③当n=2时，由工作流审批流程提交角色d2所在部门D的上一级部门C的部门主管角色c1担任该审批节点的审批角色；④当n=3时，由工作流审批流程提交角色d2所在部门D的上上一级部门B的部门主管角色b1担任该审批节点的审批角色；⑤当n=4时，由工作流审批流程提交角色d2所在部门D的上上上一级部门A的部门主管角色a1担任该审批节点的审批角色；⑥以此类推；⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色。例如：对于角色d2而言，部门级别最高应为4，当部门级别设置为6时，由最高级别部门A的部门主管角色a1担任该审批节点的审批角色。
⑧当n≥1时，需要设置“提交角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批；所述指定组审批包括以下三种情况中的一种：（1）指定组由一个或多个审批角色构成；（2）指定组由部门级别确定，选择级别主体时只能沿用该审批节点所选择的级别主体，且级别数值n只能设置为0；（3）指定组由部门级别确定，级别主体能够自主选择，指定组中包括一个或多个指定节点，当指定节点的级别数值n为非0时必须设置下一级指定节点，直到指定节点的级别数值n为0时，该审批节点的指定组设置完成。
本申请方案在原基于提交角色级别授权方式的优势基础上，还有另一优势：可以选择不同性质的角色，如合同表单上有合同签订角色、合同新增角色、合同负责角色，该审批节点本来不应该以提交角色判定级别，而应以合同签订角色判断级别。比如，报销表单（报销审批流程）的第一个审批节点要以提交角色的上级，另外的一个审批节点要以报销角色的上级审批（报销角色和提交角色可能是不同的角色）。
传统级别审批方式只能以审批流程提交角色作为判断标准来判断部门级别，无法自定义以表单中涉及到的其它角色或部门作为判断部门级别的标准，存在一定的使用局限性。
举例：对于一个合同审批流程，合同的签订角色请假了，让其同事替他发起了一个合同的审批，而系统认定其同事为流程的提交角色，在按级别审批时对于级别的判断均以其同事为准，无法客观体现合同签订角色所在的部门及职位。例如，合同的签订角色为市场部的销售人员1，其同事角色为研发部的研发人员1，原本该合同应由签订角色所在部门的主管-市场部主管角色审批，设置审批节点的审批级别为1时，系统会分配给研发人员1所在部门的主管-研发部主管角色进行审批，出现了审批流程的分配错误，使用不方便。
本申请在设置审批节点时，可以根据需要选择合同表单中的签订角色作为级别主体，以签订角色（而非一味默认为提交角色）作为标准判断部门级别，以此确定审批角色为市场部主管角色，使用更灵活、方便，通用性强。
系统提供了最高级别部门主管的审批机制，避免出现最高级别部门主管无法通过级别审批方式完成审批流程的问题。
举例：企业的最高级领导董事长提交审批请求时，在级别审批中，董事长虽没有上级部门，但设置了指定组来审批董事长提交的审批请求。
指定组审批包括以下三种情况中的一种：①指定组由一个或多个审批角色构成，例如，由多个监事会的成员构成指定组，董事长的审批请求由监事会成员进行审批；②指定组由部门级别确定，选择级别主体时只能沿用该审批节点所选择的级别主体，且级别数值n只能设置为0；此种情况用于应对企业组织结构发生变化的情况，例如，某公司原最高级别主管为总经理，而组织结构变化后增设了董事会，最高级别主管变为董事长，审批节点中级别数值为0则审批角色自动变为董事长，而不是固定为总经理，避免出现审批角色不能适配组织结构变化的问题；③指定组由部门级别确定，级别主体能够自主选择，指定组中包括一个或多个指定节点，当指定节点的级别数值n为非0时必须设置下一级指定节点，直到指定节点的级别数值n为0时，该审批节点的指定组设置完成；此种情况适用于普通部门角色审批最高级部门主管所提交的审批请求，例如，财务部门的财务主管可以审核董事长所提交的合同审批请求中涉及的开票信息，最终要由董事长确认。
当审批节点选择的是级别审批时，对级别中对应的审批角色进行审批权限授权，则此级别中对应的审批角色的审批权限都相同。
举例：n=1时，a3、b3、c3、d3分别提交审批流程时，则对应的审批主管分别为a1、b1、c1、d1，且a1、b1、c1、d1的审批权限都一样。
【实施例5】如图5所示，所述审批流程的生成包括以下步骤：S1：构建用户-角色-权限的三层结构模型，其中：角色层：工作流中流程审批的操作主体为角色，每个角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；所述角色的构成为：岗位名+岗内编号；权限层：由工作流执行中所需要使用的权限构成，权限直接授权给角色；用户层：用户通过关联的角色确定审批流程中的审批任务，并以关联角色的权限进行审批操作；S2：如图7所示，基于三层结构模型生成审批流程，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点：开始节点：发起角色发起/申请/提交工作流作为开始节点，或者由第一个审批节点作为开始节点。
系统根据发起角色所提交的表单确定审批流程，针对需要有工作流的表单设计一个或多个审批流程，但一个角色只能选择该表单下的某一个审批流程（同一个角色只能存在于同一个表单的其中一个流程中）；举例: 采购合同表单有两种流程，分别为P1流程和P2流程，如果在P1流程的开始节点中选择了角色A，那么在P2流程的开始节点就不能再选择角色A，此时角色A新增一个采购合同的审批，提交审批时自动进入P1流程。
审批节点：设置审批节点审批方式并选择审批角色，并对审批角色进行授权；结束节点：审批流程流转到此节点时该审批流程结束，该结束节点不进行审批操作；或者以最后一个审批节点作为结束节点，该结束节点需要进行审批操作。
S3：用户根据其关联的角色确定所需处理的审批任务，并根据关联的角色的权限进行审批操作。
在审批节点选择一个或多个审批角色，一个角色在同一个审批流程中能够存在于不同审批节点，不同审批节点中该审批角色对表单字段的查看、修改权限可不同。优势举例：某角色为成都销售经理3，在合同审批工作流中，其存在于成都销售合同审批和上海销售合同审批两个审批节点；对于成都销售合同的审批节点，在审批时该角色可查看该合同的客户名称、联系人、联系方式、产品数量、产品单价、合同金额等全部字段内容，且可修改产品单价、合同金额；但在上海销售合同的审批节点却无法查看客户名称、联系人、联系方式等敏感字段内容，更不能作任何修改（但也可以设为具有查看权限，没有修改权限）。
在审批节点选择一个或多个审批角色，在审批节点设置审批角色的权限，针对每个审批节点的每个审批角色能够进行独立的权限设置。例如：在一个合同表单的审批流程中，有某个审批节点设置了2个审批角色，分别为角色A、角色B，可设置角色A能够看到该合同表单中的合同金额字段及该字段的值，也可以看到该合同表单中的客户地址字段及该字段的值；设置角色B不能看到合同表单中的合同金额字段，或能看到合同金额字段但看不到该字段的值，看不到值时可用其他符号显示，比如*号，角色B能够看到该合同表单中的客户地址字段及该字段的值。
【实施例6】如图6和图8所示，所述的步骤S1包括以下顺序子步骤：S101：创建角色，每个角色是独立的个体，而非组/类；S102：对S101所创建的角色分别进行授权；S103：将用户关联到角色，其中，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；步骤S101在先，但步骤S102与步骤S103无先后顺序关系。用户通过其与角色的关联确定权限，如果要修改用户的权限，通过调整角色所拥有的权限以达到改变关联了该角色的用户的权限的目的。一旦用户关联角色后，该用户就拥有了该角色的所有操作权限。
角色对用户的关系为一对一（该角色与一个用户关联时，其他用户则不能再关联该角色；若该角色未被用户关联，则可以被其他用户选择关联）。用户对角色的关系为一对多（一个用户可以同时关联多个角色）。
角色的定义：角色不具有组/类/类别/岗位/职位/工种等性质，而是一个非集合的性质，角色具有唯一性，角色是独立存在的独立个体；在企事业单位应用中相当于岗位号（此处的岗位号非岗位，一个岗位同时可能有多个员工，而同一时段一个岗位号只能对应一个员工）。
举例：某个公司系统中可创建如下角色：总经理、副总经理1、副总经理2、北京销售一部经理、北京销售二部经理、北京销售三部经理、上海销售工程师1、上海销售工程师2、上海销售工程师3、上海销售工程师4、上海销售工程师5……用户与角色的关联关系：若该公司员工张三任职该公司副总经理2，同时任职北京销售一部经理，则张三需要关联的角色为副总经理2和北京销售一部经理，张三拥有了这两个角色的权限。
对角色的授权：系统对角色的授权包括但不限于对表单的授权、对菜单的授权或对功能的授权。对表单的操作授权包括但不限于增删查改。
传统角色的概念是组/类/岗位/职位/工种性质，一个角色能够对应多个用户。而本申请“角色”的概念相当于岗位号/工位号，也类同于影视剧中的角色：一个角色在同一时段（童年、少年、中年……）只能由一个演员来饰演，而一个演员可能会分饰多角。
对角色的授权包括但不限于对表单的授权、对菜单的授权或对功能的授权。
所述的角色归属于部门，且该角色在该部门下唯一，根据角色的工作内容对角色进行授权。
如果用户要变换部门则涉及到跨部门调岗，其具体操作过程包括：（1）取消用户与原部门内的角色的关联；（2）将用户与新部门内的角色进行关联。
在创建角色之后，可以在创建用户的过程中关联角色，也可以在用户创建完成后随时进行关联。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
【实施例7】所述的步骤S1包括以下顺序子步骤：S101：建立角色，每个角色是独立的个体，而非组/类；S102：将用户关联到角色，其中，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；S103：对S101所建立的角色分别进行授权。
所述的角色归属于部门，且该角色在该部门下唯一，根据角色的工作内容对角色进行授权。
工作流控制方法，还包括一个用户跨部门调岗管理步骤，具体包括：（1）取消用户与原部门内的角色的关联；（2）将用户与新部门内的角色进行关联。
所述角色的构成为：岗位名+岗内编号。例如：车间生产工人1、车间生产工人2、车间生产工人3……角色是独立个体，相当于岗位号、工位号的概念，不同于传统权限管理体系中的角色，传统体系中角色的概念是岗位/职位/工种等的组/类性质。
【实施例8】以下举例员工张三进入某公司后，员工、用户与角色之间的关系为：1、新入职：员工新入职，直接为该用户（员工）选择相应的岗位号/工位号的角色进行关联即可，例：张三入职公司（公司为张三分配了一个张三用户），工作内容是在销售一部，负责北京区域冰箱产品的销售（对应的角色是销售一部下的“销售工程师5”这个角色），则张三用户直接选择“销售工程师5”这个角色关联即可。
2、增加职位：张三工作一段时间后，公司还安排张三负责北京区域电视产品的销售（对应的角色是销售一部下的“销售工程师8”这个角色）并兼任售后部主管（对应售后部主管1这个角色），则张三用户再增加关联销售一部下的“销售工程师8”和售后部下的“售后部主管1”这两个角色，此时，张三员工关联了三个角色，分别为销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”，张三用户则拥有了这三个角色的权限。
3、减少职位：又过了一段时间，公司决定让张三任职售后部经理（对应售后部下“售后部经理”这个角色），且不再兼任其他工作。则张三用户关联售后部下“售后部经理”这个角色，同时取消此前关联的三个角色（销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”），此时，张三用户只拥有售后部下“售后部经理”这个角色的权限。
4、角色权限的调整（针对角色本身所拥有的权限的调整）：如公司决定增加售后部经理的权限，则只需增加对售后部经理这个角色的授权即可，则张三用户因为售后部经理这个角色的权限增加了，张三用户的权限也增加了。
5、离职：一年后，张三离职了，则取消张三用户与售后部下“售后部经理”这个角色的关联即可。
举例：公司在动态的经营中，职员的入职、离职是经常持续发生的，但岗位号/工位号的变化非常少(甚至在一定时期内是没有变化的)。
传统授权方法：在系统功能点多的情况下，以传统的组/类性质的角色进行授权，不仅授权工作量大，繁杂，而且很容易出错，甚至出错了在短时间内都不容易发现，容易对系统使用方造成损失。
本申请授权方法：本申请是对岗位号/工位号性质的角色进行授权，用户关联角色而确定权限，则对用户权限的控制，只是通过简单的用户-角色的关联关系来实现，让权限控制变得简单、易操作，清晰明了，大幅度提高了授权效率和授权可靠性。
以上所述仅是本发明的优选实施方式，应当理解本发明并非局限于本文所披露的形式，不应看作是对其他实施例的排除，而可用于各种其他组合、修改和环境，并能够在本文所述构想范围内，通过上述教导或相关领域的技术或知识进行改动。而本领域人员所进行的改动和变化不脱离本发明的精神和范围，则都应在本发明所附权利要求的保护范围内。

Claims (10)

  1. 基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，其特征在于，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；
    第二步：设置会签节点的一个或多个审批角色。
  2. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：所述的审批角色是独立的个体，而非组/类，同一时段一个审批角色只能关联唯一的用户，而一个用户关联一个或多个审批角色。
  3. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：只有会签节点所涉及到的所有审批角色都提交会签意见后才能进入审批流程的后续步骤；
    会签节点得到的是该节点所有审批角色的会签意见的汇总，无论会签意见如何，会签节点都不能驳回审批流程。
  4. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：审批流程中不能以会签节点结束流程，所述会签节点的后续节点中至少有一个非会签的审批节点。
  5. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：还包括一个为会签节点设置一个负责角色的步骤，负责角色在会签时选择该会签节点的下一级流转节点，当下一级流转节点有多个可选时，由负责角色选择其中一个。
  6. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：还包括一个设置审批角色对审批流程涉及的表单字段内容查看权限的步骤，同一会签节点的不同审批角色对表单字段内容的查看权限可以不同。
  7. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：设置审批节点审批方式为会签后，该会签节点所涉及的所有审批角色对审批流程的表单字段内容都不具备修改权限。
  8. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：所述审批流程的生成包括以下步骤：S1：构建用户-角色-权限的三层结构模型，其中：角色层：工作流中流程审批的操作主体为角色，每个角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；
    权限层：由工作流执行中所需要使用的权限构成，权限直接授权给角色；
    用户层：用户通过关联的角色确定审批流程中的审批任务，并以关联角色的权限进行审批操作；
    S2：基于三层结构模型生成审批流程，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点：
    开始节点：审批流程开始；
    审批节点：设置审批节点审批方式并选择审批角色，并对审批角色进行授权；
    结束节点：审批流程结束；
    S3：用户根据其关联的角色确定所需处理的审批任务，并根据关联的角色的权限进行审批操作。
  9. 根据权利要求1所述的基于会签的审批节点在审批流程中的设置方法，其特征在于：所述的第二步采用基于表单字段和级别的审批角色设置方法，具体包括一个设置系统组织结构的步骤和一个按部门级别设置审批角色的步骤：所述设置系统组织结构的步骤包括以下子步骤：SS1：创建系统组织结构中所包含的部门及角色；
    SS2：设置各部门之间的层级关系，并设置各部门的部门主管角色；
    所述按部门级别设置审批角色的步骤包括：SSS1:选择以按级别方式进行审批角色的设置；
    SSS2:选择审批流程对应表单中的角色性质字段、部门性质字段或者该审批流程的提交角色中的一个，作为级别主体；
    SSS3:填写具体的级别数值n，n为≥0的正整数：（1）选择审批流程对应表单中的角色性质字段作为级别主体，以该字段对应的角色为判断标准判断级别：
    ①当n=0时，由该字段对应的角色担任该审批节点的审批角色；
    ②当n=1时，由该字段对应的角色所在部门的部门主管角色担任该审批节点的审批角色；若该字段对应的角色为其所在部门的部门主管角色，则由该字段对应的角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；
    ③当n=2时，由该字段对应的角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；
    ④当n=3时，由该字段对应的角色所在部门的上上一级部门的部门主管角色担任该审批节点的审批角色；
    ⑤当n=4时，由该字段对应的角色所在部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；
    ⑥以此类推；
    ⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；
    ⑧当n≥1时，需要设置“该字段对应的角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批；
    （2）选择审批流程对应表单中的部门性质字段作为级别主体，以该字段对应的部门为判断标准判断级别：
    ①当n=0时，由该字段对应的部门的部门主管角色担任该审批节点的审批角色；
    ②当n=1时，由该字段对应的部门的上一级部门的部门主管角色担任该审批节点的审批角色；
    ③当n=2时，由该字段对应的部门的上上一级部门的部门主管角色担任该审批节点的审批角色；
    ④当n=3时，由该字段对应的部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；
    ⑤以此类推；
    ⑥当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；
    ⑦当n≥1时，需要设置“该字段对应的部门无上一级部门时”该审批节点由指定组审批；
    （3）选择审批流程的提交角色作为级别主体，以该提交角色为判断标准判断级别：①当n=0时，由工作流审批流程提交角色担任该审批节点的审批角色；
    ②当n=1时，由工作流审批流程提交角色所在部门的部门主管角色担任该审批节点的审批角色；若提交角色为其所在部门的部门主管角色，则由提交角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；
    ③当n=2时，由工作流审批流程提交角色所在部门的上一级部门的部门主管角色担任该审批节点的审批角色；
    ④当n=3时，由工作流审批流程提交角色所在部门的上上一级部门的部门主管角色担任该审批节点的审批角色；
    ⑤当n=4时，由工作流审批流程提交角色所在部门的上上上一级部门的部门主管角色担任该审批节点的审批角色；
    ⑥以此类推；
    ⑦当部门级别的设置超过系统组织结构中的最高级别部门时，由最高级别部门的部门主管角色担任该审批节点的审批角色；
    ⑧当n≥1时，需要设置“提交角色为其所在部门的部门主管角色，且该部门无上一级部门时”该审批节点由指定组审批；
    所述指定组审批包括以下三种情况中的一种：（1）指定组由一个或多个审批角色构成；
    （2）指定组由部门级别确定，选择级别主体时只能沿用该审批节点所选择的级别主体，且级别数值n只能设置为0；
    （3）指定组由部门级别确定，级别主体能够自主选择，指定组中包括一个或多个指定节点，当指定节点的级别数值n为非0时必须设置下一级指定节点，直到指定节点的级别数值n为0时，该审批节点的指定组设置完成。
  10. 基于会签的审批节点在审批流程中的设置方法，一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点，其特征在于，包括以下顺序步骤：第一步：设置审批节点审批方式为会签，称该审批节点为会签节点，会签节点汇总所有该节点审批角色的会签意见，为在后的审批节点的审批角色提供参考；
    第二步：设置会签节点的一个或多个审批角色；
    还包括一个设置该会签节点为匿名会签的步骤，设置为匿名会签后，除了该审批角色自己能够看到自己的会签意见以外，其他非本审批角色均无法看到该审批角色提交的会签意见。
PCT/CN2018/087919 2017-05-23 2018-05-22 基于会签的审批节点在审批流程中的设置方法 WO2018214889A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710370006.1A CN107122921A (zh) 2017-05-23 2017-05-23 基于会签的审批节点在审批流程中的设置方法
CN201710370006.1 2017-05-23

Publications (1)

Publication Number Publication Date
WO2018214889A1 true WO2018214889A1 (zh) 2018-11-29

Family

ID=59728786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087919 WO2018214889A1 (zh) 2017-05-23 2018-05-22 基于会签的审批节点在审批流程中的设置方法

Country Status (2)

Country Link
CN (2) CN107122921A (zh)
WO (1) WO2018214889A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110288229A (zh) * 2019-06-24 2019-09-27 广州建众互联网科技有限公司 流程处理方法、系统及计算机可读存储介质
CN110992005A (zh) * 2019-12-23 2020-04-10 普元信息技术股份有限公司 大数据应用中实现数据权限控制处理的方法及其系统
CN111210204A (zh) * 2020-01-13 2020-05-29 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN112036824A (zh) * 2020-08-27 2020-12-04 北京新橙科技有限公司 业务审批方法、系统、存储介质及电子设备
CN112966917A (zh) * 2021-02-26 2021-06-15 重庆治略科技有限公司 基于关系网络的智能化流程处理系统、装置及方法
CN113657869A (zh) * 2021-08-31 2021-11-16 上海中通吉网络技术有限公司 流程审批人员的配置方法及装置
CN115526605A (zh) * 2022-10-21 2022-12-27 金恒智控管理咨询集团股份有限公司 基于企业内部控制管理的审批方法及系统
CN117853042A (zh) * 2023-12-25 2024-04-09 东土科技(宜昌)有限公司 电子作业票的生成方法、装置、电子设备及存储介质
CN117993870A (zh) * 2024-04-03 2024-05-07 湖南省交通规划勘察设计院有限公司 一种基于cad的在线审批流程信息交互方法

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107122921A (zh) * 2017-05-23 2017-09-01 成都牵牛草信息技术有限公司 基于会签的审批节点在审批流程中的设置方法
CN107977830B (zh) * 2017-12-18 2021-07-09 东软集团股份有限公司 会签任务创建方法、装置、计算机及存储介质
CN108428109A (zh) * 2018-02-12 2018-08-21 广东绍林科技开发有限公司 一种高效灵活的流程处理系统、方法、终端及介质
CN109146227A (zh) * 2018-06-26 2019-01-04 四川驹马科技有限公司 一种工作流并行审批方法及其系统
CN111008820B (zh) * 2019-11-29 2024-04-05 通号通信信息集团有限公司 铁路无线网络数据系统
CN111027933A (zh) * 2019-12-09 2020-04-17 中国建设银行股份有限公司 审批流转方法、装置、系统及电子设备
CN111340454A (zh) * 2020-03-04 2020-06-26 山信软件股份有限公司 企业作业证安全管理方法
CN111461641A (zh) * 2020-03-12 2020-07-28 北京美住美宿科技有限公司 一种审批流处理方法、系统、设备及可读存储介质
CN112950162B (zh) * 2020-07-09 2022-04-29 北京中百信信息技术股份有限公司 信息系统工程监理工作派发管理信息系统
CN112631579B (zh) * 2020-12-25 2022-08-09 傲普(上海)新能源有限公司 一种基于erp审批流Vue组件复用的方法
CN113269525A (zh) * 2021-05-24 2021-08-17 山东浪潮商用系统有限公司 一种工作流的会签管理方法
CN113554412A (zh) * 2021-06-29 2021-10-26 国网山东省电力公司东营供电公司 一种用于制定审批流程的引擎系统
CN116957487B (zh) * 2023-06-27 2024-05-14 三峡高科信息技术有限责任公司 一种配置式的动态子流程会签方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005135072A (ja) * 2003-10-29 2005-05-26 Ricoh System Kaihatsu Co Ltd セキュア文書交換システム、文書承認方法、文書交換管理方法およびそのプログラム
CN102609834A (zh) * 2012-02-01 2012-07-25 昆山百润科技有限公司 一种会签方法和系统
CN105404952A (zh) * 2015-09-24 2016-03-16 鲁能集团有限公司 基于sap平台的审批工作流动态配置方法及系统
CN107122921A (zh) * 2017-05-23 2017-09-01 成都牵牛草信息技术有限公司 基于会签的审批节点在审批流程中的设置方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007323304A (ja) * 2006-05-31 2007-12-13 Nippon Telegr & Teleph Corp <Ntt> 分担型協調電子データ利用認可判定方法および電子データ共有システム
CN103745283A (zh) * 2012-10-17 2014-04-23 镇江雅迅软件有限责任公司 一种自动判断工作流程流转节点的方法
CN105389674A (zh) * 2015-12-21 2016-03-09 用友网络科技股份有限公司 一种工作流循环审批系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005135072A (ja) * 2003-10-29 2005-05-26 Ricoh System Kaihatsu Co Ltd セキュア文書交換システム、文書承認方法、文書交換管理方法およびそのプログラム
CN102609834A (zh) * 2012-02-01 2012-07-25 昆山百润科技有限公司 一种会签方法和系统
CN105404952A (zh) * 2015-09-24 2016-03-16 鲁能集团有限公司 基于sap平台的审批工作流动态配置方法及系统
CN107122921A (zh) * 2017-05-23 2017-09-01 成都牵牛草信息技术有限公司 基于会签的审批节点在审批流程中的设置方法

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110288229B (zh) * 2019-06-24 2024-05-17 临沂远创科技信息咨询有限公司 流程处理方法、系统及计算机可读存储介质
CN110288229A (zh) * 2019-06-24 2019-09-27 广州建众互联网科技有限公司 流程处理方法、系统及计算机可读存储介质
CN110992005A (zh) * 2019-12-23 2020-04-10 普元信息技术股份有限公司 大数据应用中实现数据权限控制处理的方法及其系统
CN110992005B (zh) * 2019-12-23 2024-02-06 普元信息技术股份有限公司 大数据应用中实现数据权限控制处理的方法及其系统
CN111210204A (zh) * 2020-01-13 2020-05-29 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN111210204B (zh) * 2020-01-13 2023-10-27 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN112036824A (zh) * 2020-08-27 2020-12-04 北京新橙科技有限公司 业务审批方法、系统、存储介质及电子设备
CN112966917A (zh) * 2021-02-26 2021-06-15 重庆治略科技有限公司 基于关系网络的智能化流程处理系统、装置及方法
CN113657869A (zh) * 2021-08-31 2021-11-16 上海中通吉网络技术有限公司 流程审批人员的配置方法及装置
CN115526605A (zh) * 2022-10-21 2022-12-27 金恒智控管理咨询集团股份有限公司 基于企业内部控制管理的审批方法及系统
CN115526605B (zh) * 2022-10-21 2024-03-08 金恒智控管理咨询集团股份有限公司 基于企业内部控制管理的审批方法及系统
CN117853042A (zh) * 2023-12-25 2024-04-09 东土科技(宜昌)有限公司 电子作业票的生成方法、装置、电子设备及存储介质
CN117993870A (zh) * 2024-04-03 2024-05-07 湖南省交通规划勘察设计院有限公司 一种基于cad的在线审批流程信息交互方法

Also Published As

Publication number Publication date
CN108764691B (zh) 2023-04-25
CN107122921A (zh) 2017-09-01
CN108764691A (zh) 2018-11-06

Similar Documents

Publication Publication Date Title
WO2018214889A1 (zh) 基于会签的审批节点在审批流程中的设置方法
WO2018224024A1 (zh) 工作流审批节点高效审批方法
US20230419265A1 (en) Method based on form fields for arranging examination and approval roles at workflow examination and approval nodes
CN108694557B (zh) 工作流及其审批节点的表单字段操作权限的设定方法
CN109086627B (zh) 表单数据操作的审核方法
US11363026B2 (en) Workflow control method and system based on one-to-one correspondence between roles and users
CN108764833B (zh) 工作流审批节点按部门设置审批角色的方法
WO2018214828A1 (zh) 基于投票的审批节点在审批流程中的设置方法
WO2019011220A1 (zh) 基于依据字段设置审批流程的方法
CN108550029B (zh) 工作流审批节点按部门级别设置审批角色的方法
WO2018214890A1 (zh) 工作流审批节点按角色设置审批角色的方法
JP7211593B2 (ja) フォーム関連情報の承認方法
JP7339634B2 (ja) 時間帯に基づいて操作記録を閲覧する権限の設置方法
JP2020520034A (ja) ロール対ユーザーに基づく１対１の権限承認方法とシステム
WO2019015539A1 (zh) 一种表单数据操作权限授权方法
WO2019007291A1 (zh) 根据表单字段值对表单操作权限进行分别授权的方法
WO2018219230A1 (zh) 审批工作流的委托及其再委托方法
JP7429390B2 (ja) 使用者に承認プロセスとその承認ノードの権限を与える方法
WO2019034023A1 (zh) 审批者针对审批任务征询参考意见的方法
JP2020528600A (ja) 第三者フィールドを介してフォームフィールドのフィールド値を承認する方法
WO2019029500A1 (zh) 基于列值对统计列表操作权限进行分别授权的方法
WO2019001322A1 (zh) 基于角色的菜单授权方法

Legal Events

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

Ref document number: 18805292

Country of ref document: EP

Kind code of ref document: A1

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

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18805292

Country of ref document: EP

Kind code of ref document: A1