WO2018224024A1 - Procédé d'approbation efficace pour noeud d'approbation de flux de travail - Google Patents

Procédé d'approbation efficace pour noeud d'approbation de flux de travail Download PDF

Info

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

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management

Definitions

  • the invention relates to a workflow approval method for a management software system such as ERP, in particular to an efficient approval method for a workflow approval node.
  • 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 workflow approval mechanism of the traditional system has the following defects: (1) The process initiator cannot select the process initiator itself as the approval personnel. Before the approval process ends, the initiator of the approval process cannot review the approval result of the application submitted, for example.
  • the sponsor initiated a request for reimbursement of 10,000 yuan. Due to the wrong content submitted by the sponsor or other reasons, the approved reimbursement amount was revised to 500 yuan after multi-level approval, and the final approval result was only allowed to reimburse 500 yuan. The process ends. If the sponsor has objection after receiving the approval result, the result of the previous approval process must be invalidated, and then an application for approval is resubmitted, which increases the internal consumption of the system and reduces the efficiency of examination and approval.
  • 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 traditional workflow approval node has a single approval method.
  • voting is often used.
  • the voting method usually requires each approval role to submit the voting result before the approval result of the approval node can be obtained. In the case of low efficiency, it is impossible to achieve efficient and rapid approval.
  • the object of the present invention is to overcome the deficiencies of the prior art and provide an efficient approval method for a workflow approval node. As long as any approval role submits an approval opinion, the approval result of the approval node is determined, and the approval of the approval node ends.
  • the approval task of the approval role is automatically removed to achieve efficient and rapid approval. It is especially suitable for multiple people to have the same approval authority for the same approval task. Any approval opinion given by one person can determine the result of the approval.
  • a workflow approval node efficient approval method including a step of setting an approval node approval role and an approval role efficient approval step: the steps of setting an approval node approval role include the following A combination of any one or more of the modes: (1) directly designating one or more roles as an approval role; (2) directly designating one or more departments, and acting as an approval role for the department's departmental role; (3) The approval role is set by level; the approval role is efficiently approved: one approval node contains one or more approval roles, and the approval opinion of the first approval role that submits the approval opinion is used as the approval result of the approval node, as long as there is any An approval role submits an approval opinion, and the approval node approval ends.
  • the workflow approval node efficient approval method also includes a step of setting the approval role to view the content of the form field involved in the approval process, and the different approval roles of the same approval node have the same view/modification permission for the form field content.
  • the workflow approval node efficient approval method further includes a step of setting a lower-level flow node of the approval node, and the next-level flow node includes two types: (1) one or more when the approval result of the approval node is “pass” Passing the node; (2) one or more rejecting nodes when the approval result of the approval node is "rejected"; when there are multiple passing nodes/refusing nodes when passing/refusing, the first one submits the approval opinion
  • the approval role selects a pass node/reject node; when there is only one pass/reject node when passing/rejecting, the approval role of the first submitting approval opinion selects the pass/reject node, or the system automatically enters the Pass node/reject node.
  • the roles are independent individuals, not groups/classes. One role can only associate unique users at the same time, and one user associates one or more roles.
  • the approval process is based on 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, not a group/class, one at the same time. A role can only be associated with a unique user, and a user is associated with one or more roles.
  • the privilege layer consists of the privilege required for workflow execution, and the privilege is directly delegated to the role.
  • the user tier the user determines the approval process through the associated role. The approval task in the middle, and the approval operation is performed with the permission of the associated role.
  • the user-role-authority three-tier structure model includes the following steps: establishing roles, each role is an independent individual, not a group/class; the role belongs to a department, and the role is performed according to the work content of the role.
  • Authorization and the name of the role is unique under the department, the number of the role is unique in the system; when the account is transferred across departments, the relationship between the account and the role in the original department is cancelled, and the account (user) and the new department are The roles within the association are associated; the authorized roles are authorized separately; the users are associated with the roles, wherein one role can only be associated with a unique user and one user is associated with one or more roles.
  • the approval process includes a start node, at least one approval node, and an end node: a start node: an approval process starts; an approval node: selects an approval role, and authorizes the approval role; and ends the node: the approval process ends.
  • the step of setting the approval role by level 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: Creating a system organization structure included Department and role; SS2: Set the hierarchical relationship between departments, and set the department supervisor role of each department; the steps to set the approval role by department level include: SSS1: Select (or set) to approve by level Role setting; SSS2: Select one of the role nature field, department nature field or 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 ⁇ 0 positive Integer (N value 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, d is greater than a third level, and so on): (1) Select the role nature field in the approval process corresponding form as the level body,
  • the role property field and the department property field in the form are mandatory single options.
  • the step of setting the approval role by level 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: Creating a system organization structure included Department and role; SS2: Set the hierarchical relationship between departments, and set the department supervisor role of each department; the steps to set the approval role by department level include: SSS1: Select (or set) to approve by level Role setting; SSS2: Select one of the role nature field, department nature field or 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 ⁇ 0 positive Integer (N value 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, d is greater than a third level, and so on): (1) Select the role nature field in the approval process corresponding form as the level body,
  • the department head role serves as the approval role for the approval node; 6 and so on; 7 when the department level setting exceeds the system organization structure In the highest level department, the department head 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 head role of the department in which it is located, and the department has no previous level.
  • Department time The approval node is approved by the specified 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 designated group is determined by the department level.
  • the level value n can only be set to 0; (3) the specified group is determined by the department level, the level body can select independently, and the specified group includes one or more Specifies the node. When the level value n of the specified node is non-zero, the specified node of the next level must be set. When the level value n of the specified node is 0, the specified group setting of the approval node is completed.
  • the beneficial effects of the present invention are as follows: (1) As long as any approval role submits an approval opinion, the approval result of the approval node is determined, the approval of the approval node is completed, and the approval tasks of other approval roles are automatically removed, thereby achieving high efficiency. Quick approval. It is especially suitable for multiple people to have the same approval authority for the same approval task, and any one can decide the situation of the node approval result.
  • the sales manager 1, the sales manager 2, and the personnel supervisor 2 have the authority to directly determine the result of the approval, and the approval role in the approval node is the sales manager 1 and the sales manager 2
  • the personnel supervisor 2 is composed of any one person (role) who gives the approval opinion to determine the approval result of the node.
  • the approval task is assigned to the sales manager 1, the sales manager 2, the personnel supervisor 2, and the sales manager 2 first sees the approval task and submits the approval opinion as “pass”, then the approval of the node is approved by “pass”.
  • the sales manager 1 and the personnel supervisor 2 are no longer required to give approval opinions, and the approval tasks of the sales manager 1 and the personnel supervisor 2 are automatically removed.
  • the administrative department of the company has role A and role B. If role A is the department supervisor role of the administrative department, when performing the workflow approval setting for leave, simply select role A as the approval role instead of selecting role A. The user, even if the user associated with role A is changed from Zhang San to Li Si, does not need to re-approve the role setting.
  • Benefits of the designated department The system workflow setting personnel only need to select the corresponding department when setting the approval role, then the department supervisor role of the department is the approval role, even if the department supervisor role of the department changes, the current department head of the department The role is an approval role, and there is no need to reset the approval role. It is easy to operate and not easy to make mistakes.
  • the employee of the company when the employee of the company takes time off, it needs the approval of the administrative department.
  • the department supervisor role of the administrative department is the approval role
  • the employee corresponding to the department's supervisor role is obtained through the supervisor role of the department. Approve the task and approve it according to the relevant authority of the department's supervisor role. It is not necessary to select a specific employee for approval setting.
  • the operation is simple and convenient.
  • the department head of the administrative department changes from role A to role B, the role B corresponds.
  • the staff approves and does not need to re-set the approval role.
  • the advantage of setting the approval role by level By setting the approval role by department level, the system workflow setting personnel only need to input the corresponding department level when setting the approval role, and multiple approval processes can be effectively integrated in one approval process. It can effectively reduce the flow conditions and flow lines, reduce the workload of system workflow set personnel, and improve system reliability.
  • the expense reimbursement approval process in an approval node setting level approval, and submitting the role as the level body, and setting the level to 1, all the expense reimbursement is automatically supervised by the department head of the department where the submitting role is located in the approval node. The role is approved.
  • 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.
  • the submission role itself can be approved and confirmed. Can return to re-approval, choose to agree to enter the next link, and more to submit the role review process, to avoid the problem of incorrect approval results or the approval results are not in line with the expectations of the submitted role and need to create (resubmit) the approval process, reducing the system Internal friction increases 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 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.), or employee approval authority If there is a change, simply re-associate the employee to the new role, or adjust the role approval authority accordingly. There is no need to reset/adjust the process. It is easy to set up, no mistakes or omissions, and will not affect the normal operation of the enterprise. Greatly improved 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 (acquires) the approval tasks through the role. The user can approve the operation by associating the role. The understanding is clear and simple, and each post number/work The role of the nature of the tag is the smallest unit of the work subject, and this application is 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 associated role 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 (the nature of the post number/station number) is small. Although the employee turnover is large, the change of the post number/station number is small (even if there is no change in a certain period of time, that is, the role does not change), This will greatly simplify the user's rights management and reduce the overhead of the system.
  • the operation of dynamic management, on-the-job adjustment, etc. is simple and convenient, high in efficiency and high in reliability: the application of the entry/departure/adjustment in the approval process is simple, and the operation subject of the approval of the workflow is the role, when the employee/user There is no need to reset the approval process when the change occurs (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 is associated with the role of the job number, the user associated with the role automatically obtains the related tasks and permissions of the role in the approval workflow, without resetting the approval workflow or reauthorizing the roles in the workflow. , greatly improving 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 authority management mechanism defines the role as a group, a job type, a class, etc.
  • the role is a one-to-many relationship with the user. In the actual system use process, it is often necessary to perform the user's authority in the operation process. Adjustments, for example, when the employee permissions are changed, the permissions of an employee associated with the role change. We cannot change the permissions of the entire role because of the change of the individual employee permissions, because the role is also associated with other permissions. Staff. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
  • the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
  • the role since the role is an independent individual, the role permission can be changed to achieve the goal.
  • the method of the present application seems to increase the workload when the system is initialized, it can be made by copying and the like to make the role or authorization more efficient than the traditional group-based role, because the role of the group is not considered.
  • the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
  • the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
  • the traditional group-based role authorization method is error-prone, and the method of the present application greatly reduces the probability of authorization errors, because the method of the present application only needs to consider the role as an independent individual, without considering the traditional method to associate the role of the group. What are the commonalities of multiple users? Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
  • the method of the present application is as follows: the transferred user associates several roles.
  • the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
  • 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.
  • the customer name, contact person, contact information, product quantity, product unit price, contract amount and other fields of the contract, and the product unit price and contract amount can be modified; however, the customer sales name approval node cannot view the customer name, contact person, or contact.
  • the sensitive field content, such as the mode can't be modified (but can also be set to have view permission, no modify permission). 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 schematic diagram of a manner in which a system authorizes a user through an independent individual role
  • FIG. 6 is a schematic diagram of a workflow approval process according to the present invention.
  • FIG. 7 is a flowchart of a user-role authorization method according to the present invention.
  • a workflow approval node efficient approval method includes a step of setting an approval node approval role and an approval role efficient approval step: the step of setting an approval node approval role includes any one or more of the following methods Kind of combination: (1) directly assign one or more roles as the approval role; (2) directly designate one or more departments, and take the department's departmental supervisor role as the approval role; (3) set the approval role by level;
  • the roles are as follows: specify the role, specify the department, and set the approval role by level: the benefit of the specified role: the system workflow setting personnel only need to select the corresponding role as the approval role when setting the approval role, without selecting a specific user. Even if the user associated with the role changes, there is no need to reset the approval role, and the operation is convenient and error-prone.
  • the administrative department of the company has role A and role B. If role A is the department supervisor role of the administrative department, when performing the workflow approval setting for leave, simply select role A as the approval role instead of selecting role A. The user, even if the user associated with role A is changed from Zhang San to Li Si, does not need to re-approve the role setting.
  • Benefits of the designated department The system workflow setting personnel only need to select the corresponding department when setting the approval role, then the department supervisor role of the department is the approval role, even if the department supervisor role of the department changes, the current department head of the department The role is an approval role, and there is no need to reset the approval role. It is easy to operate and not easy to make mistakes.
  • the employee of the company when the employee of the company takes time off, it needs the approval of the administrative department.
  • the department supervisor role of the administrative department is the approval role
  • the employee corresponding to the department's supervisor role is obtained through the supervisor role of the department. Approve the task and approve it according to the relevant authority of the department's supervisor role. It is not necessary to select a specific employee for approval setting.
  • the operation is simple and convenient.
  • the department head of the administrative department changes from role A to role B, the role B corresponds.
  • the staff approves and does not need to re-set the approval role.
  • the advantage of setting the approval role by level By setting the approval role by department level, the system workflow setting personnel only need to input the corresponding department level when setting the approval role, and multiple approval processes can be effectively integrated in one approval process. It can effectively reduce the flow conditions and flow lines, reduce the workload of system workflow set personnel, and improve system reliability.
  • an approval node contains one or more approval roles, select one to indicate that the role is approved, and select multiple representations to be approved by any of the multiple roles, 5
  • the type of approval role is optional.
  • the approval opinion of the first approval role for submitting the approval opinion is used as the approval result of the approval node, and the approval node approval is completed as long as any approval role submits the approval opinion.
  • the approval result of the approval node is determined, the approval node approval is completed, and the approval tasks of other approval roles are automatically removed, achieving efficient and rapid approval. It is especially suitable for multi-person (multi-approval role).
  • the approval authority for the same approval task is the same. Any approval opinion given by one person (role) can determine the approval result of the node.
  • the sales manager 1, the sales manager 2, and the personnel supervisor 2 have the authority to directly determine the result of the approval, and the approval role in the approval node is the sales manager 1 and the sales manager 2
  • the personnel supervisor 2 is composed of any one person (role) who gives the approval opinion to determine the approval result of the node.
  • the approval task is assigned to the sales manager 1, the sales manager 2, the personnel supervisor 2, and the sales manager 2 first sees the approval task and submits the approval opinion as “pass”, then the approval of the node is approved by “pass”.
  • the sales manager 1 and the personnel supervisor 2 are no longer required to give approval opinions, and the approval tasks of the sales manager 1 and the personnel supervisor 2 are automatically removed.
  • the workflow approval node efficient approval method further includes a step of setting the approval authority to view the content of the form field involved in the approval process, and the different approval roles of the same approval node must have the same viewing authority for the form field content.
  • the View Fields view and modify permissions are also a uniform permission set for all approval roles, rather than setting permissions for each approval role. Because the approval permissions are the same for each approval role, any approval role can determine the approval results for the node, so you must ensure that the form fields seen by each approval role are the same.
  • the approval role can view all the fields of the form (field content) by default. By default, all fields of the form (field content) are prohibited from being modified.
  • the user can set the forbidden approval role to view certain fields (field contents) in the current step, or the authorization can modify some Field (field content).
  • the workflow approval node efficient approval method further includes a step of setting the next-level flow node of the approval node, and the next-level flow node includes two types: (1) when the approval result of the approval node is "pass” One or more passing nodes; (2) one or more rejecting nodes when the approval result of the approval node is "rejected"; when there are multiple passing nodes/refusing nodes when passing/refusing, the first An approval role for submitting an approval opinion selects a pass node/refuse node; when there is only one pass node/refute node when passing/rejecting, the approval role of the first submission approval opinion selects the pass node/reject node, or The pass node/reject node is automatically entered by the system.
  • the steps of setting the approval role by level include a step of setting the system organization structure and a step of setting the approval role by level: the step of setting the system organization structure includes the following substeps: SS1: Creating a system organization structure Departments and roles included; SS2: Set the hierarchical relationship between departments. As shown in Figure 4, department A is one level higher than department B, department A is two levels higher than department C... and departments of each department are set.
  • Supervisor role the steps of setting the approval role by department level include: SSS1: selecting (or setting) to set the approval role by level; SSS2: selecting the role nature field, department attribute field in the approval process corresponding form or the One of the submission roles of the approval process is used as the level body; when the level body is selected, only one can be selected; the form can have multiple roles and departmental fields (such as signing roles, responsible roles, signing departments, and responsible Department, etc.), but only one process submits a role in a process; SSS3: fill in the specific level value n, n is ⁇ 0 Integer (N value 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, d is greater than a third level, and so on): (1) Select the role attribute field in the approval process corresponding form as the level body, and judge the level by the role corresponding to the field.
  • SSS1 selecting (or setting) to set the approval
  • the submit role of the process is d2, but the role nature field in the selected form is the signing role.
  • 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.
  • 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 steps of setting the approval role by level include a step of setting the system organization structure and a step of setting the approval role by level: the step of setting the system organization structure includes the following substeps: SS1: Creating a system organization structure Departments and roles included; SS2: Set the hierarchical relationship between departments and set the department supervisor role of each department. As shown in Figure 4, department A is one level higher than department B, and department A is two levels higher than department C.
  • the steps of setting the approval role by department level include: SSS1: selecting (or setting) to set the approval role by level; SSS2: selecting the role property field, the department property field in the approval process corresponding form, or the One of the submission roles of the approval process 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 A level larger than a, c is two levels larger than a, d is greater than a level three, and so on): (1) select the role nature field in the approval process corresponding to the form as the level body, The determined role is to judge the standard judgment level.
  • 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.
  • 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 roles are independent individuals, not groups/classes, and one role can only associate with a unique user at the same time, and one user associates one or more roles.
  • the approval process is based on 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, not a group/class, one at the same time.
  • a role can only be associated with a unique user, and a user is associated with one or more roles; the role consists of: the post name + the post number; the privilege layer: consists of the permissions required to be used in the workflow execution, and the rights are directly authorized.
  • user layer The user determines (acquires) the approval task in the approval process through the associated role, and performs the approval operation with the permission of the associated role.
  • the approval process includes a start node, at least one approval node, and an end node: a start node: initiate/apply/submit a workflow, and further, initiate a role initiation/application/submission workflow as a start The node, or the first approval node as the start node; the approval node: select the approval role and authorize the approval role; the system determines the approval process based on the form submitted by the originating role, and designs one or more forms for the form that needs to have a workflow.
  • a role can only select one of the approval processes under the form (the same role can only exist in one of the processes in the same form); for example: the procurement contract form has two processes, respectively P1 process And the P2 process, if the role A is selected in the start node of the P1 process, then the role A can no longer be selected at the beginning node of the P2 process. At this time, the role A adds a purchase contract approval, and automatically enters the P1 process when submitting the approval. .
  • End node When the approval process flow goes to this node, the approval node approval ends, the end node does not perform the approval operation; or the last approval node is used as the end node, and the end node needs to perform the approval operation.
  • the user-role-privilege three-tier structure model includes the following steps: establishing roles, each role being an independent individual, not a group/class; the role belongs to a department, according to the role
  • the work content authorizes the role, and the name of the role is unique under the department, the number of the role is unique in the system; when the account is transferred across departments, the account is unlinked from the role in the original department, and the account is (user) associates with the role in the new department; authorizes the established roles separately; associates the user to the role, wherein one role can only associate with the unique user at the same time, and one user associates one or more roles .
  • the following is an analysis of the advantages of the method of authorizing a user through an independent individual role: the user determines the authority through its association with the role. If the user's permission is to be modified, the role is changed to adjust the role. The purpose of the user's permissions. 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.
  • roles are group/class/post/position/work type, and one role can correspond to multiple users.
  • the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
  • the 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 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 determines the (acquired) authority by associating the role, and the control of the user authority is realized by a simple user-role relationship. It makes the permission control simple, easy to operate, clear and clear, and greatly improves the authorization efficiency and authorization reliability.

Landscapes

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

Abstract

L'invention concerne un procédé d'approbation efficace pour un nœud d'approbation de flux de travail. Le procédé comprend : une étape de réglage d'un rôle d'approbation d'un nœud d'approbation, et une étape d'approbation efficace au moyen du rôle d'approbation, il existe trois manières selon lesquelles le rôle d'approbation du nœud d'approbation est défini : la spécification d'un rôle, la spécification d'un service (un rôle de responsable de département), et la définition du rôle d'approbation sur la base de niveaux. Le processus d'approbation efficace au moyen du rôle d'approbation consiste à : utiliser une opinion d'approbation d'un premier rôle d'approbation soumettant une opinion d'approbation en tant que résultat d'approbation du nœud d'approbation, et tant que l'un quelconque des rôles d'approbation soumet une opinion d'approbation, l'approbation du nœud d'approbation se terminant. Dans le procédé, tant que l'un quelconque des rôles d'approbation soumet une opinion d'approbation, un nœud d'approbation détermine un résultat d'approbation du nœud d'approbation, et l'approbation des extrémités de nœud d'approbation, et des tâches d'approbation des autres rôles d'approbation sont automatiquement annulées, ce qui permet d'obtenir une approbation efficace et rapide. Ce procédé est particulièrement approprié pour des situations où de multiples personnes ont une autorité d'approbation pour la même tâche d'approbation, et toute personne peut donner des opinions d'approbation.
PCT/CN2018/090319 2017-06-08 2018-06-07 Procédé d'approbation efficace pour noeud d'approbation de flux de travail WO2018224024A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710428786.0A CN107180339A (zh) 2017-06-08 2017-06-08 工作流审批节点高效审批方法
CN201710428786.0 2017-06-08

Publications (1)

Publication Number Publication Date
WO2018224024A1 true WO2018224024A1 (fr) 2018-12-13

Family

ID=59836517

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090319 WO2018224024A1 (fr) 2017-06-08 2018-06-07 Procédé d'approbation efficace pour noeud d'approbation de flux de travail

Country Status (2)

Country Link
CN (2) CN107180339A (fr)
WO (1) WO2018224024A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109816331A (zh) * 2018-12-20 2019-05-28 平安国际融资租赁有限公司 审核任务处理方法、装置、计算机设备和存储介质
CN111126930A (zh) * 2019-10-12 2020-05-08 中国平安财产保险股份有限公司 节点数据处理方法、装置、计算机设备和存储介质
CN111210204A (zh) * 2020-01-13 2020-05-29 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN111382989A (zh) * 2018-12-28 2020-07-07 上海汽车集团股份有限公司 数据处理方法及装置
CN112184077A (zh) * 2020-10-30 2021-01-05 平安数字信息科技(深圳)有限公司 可配置的流程审批方法、装置、计算机设备及存储介质
CN112446689A (zh) * 2020-12-15 2021-03-05 中煤能源研究院有限责任公司 一种防突措施实施过程管控的方法
CN112712452A (zh) * 2020-12-02 2021-04-27 杭州趣链科技有限公司 基于区块链的审批信息处理方法和装置
CN113469517A (zh) * 2021-06-28 2021-10-01 北京喜沃思咨询有限公司 基于excel服务器的信息管理方法及系统
CN117649210A (zh) * 2024-01-29 2024-03-05 国网浙江省电力有限公司宁海县供电公司 一种项目数据管理方法以及管理系统

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107180339A (zh) * 2017-06-08 2017-09-19 成都牵牛草信息技术有限公司 工作流审批节点高效审批方法
CN107886306B (zh) * 2017-11-24 2021-01-29 网易（杭州）网络有限公司 文件审批方法、介质、装置和计算设备
CN108428109A (zh) * 2018-02-12 2018-08-21 广东绍林科技开发有限公司 一种高效灵活的流程处理系统、方法、终端及介质
CN109284907A (zh) * 2018-09-03 2019-01-29 山东浪潮通软信息科技有限公司 一种基于复合活动实现指定后续审批活动参与者的方法
CN109345122A (zh) * 2018-10-11 2019-02-15 郑州云海信息技术有限公司 云计算系统中申请流程的管理方法和装置
CN109754175B (zh) * 2018-12-28 2023-04-07 广州明动软件股份有限公司 用于对行政审批事项的办结时限进行压缩预测的计算模型及其应用
CN109784859B (zh) * 2019-01-17 2023-09-01 四川驹马科技有限公司 一种无需配置驳回节点的工作流流程配置方法
CN111818090B (zh) * 2020-08-04 2022-09-23 蝉鸣科技(西安)有限公司 一种SaaS平台上的权限管理方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102354356A (zh) * 2011-09-29 2012-02-15 用友软件股份有限公司 数据权限管理装置和方法
WO2017021154A1 (fr) * 2015-07-31 2017-02-09 British Telecommunications Public Limited Company Commande d'accès
CN106503969A (zh) * 2016-11-03 2017-03-15 东软集团股份有限公司 业务流程审批方法及装置
CN106779613A (zh) * 2016-12-28 2017-05-31 北京奇鱼时代科技有限公司 一种用于审批配置的方法与装置
CN107180339A (zh) * 2017-06-08 2017-09-19 成都牵牛草信息技术有限公司 工作流审批节点高效审批方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009054047A (ja) * 2007-08-28 2009-03-12 Ricoh Co Ltd 承認審査システム及び承認審査方法
CN106485390A (zh) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 审批流的生成方法和装置
CN105389674A (zh) * 2015-12-21 2016-03-09 用友网络科技股份有限公司 一种工作流循环审批系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102354356A (zh) * 2011-09-29 2012-02-15 用友软件股份有限公司 数据权限管理装置和方法
WO2017021154A1 (fr) * 2015-07-31 2017-02-09 British Telecommunications Public Limited Company Commande d'accès
CN106503969A (zh) * 2016-11-03 2017-03-15 东软集团股份有限公司 业务流程审批方法及装置
CN106779613A (zh) * 2016-12-28 2017-05-31 北京奇鱼时代科技有限公司 一种用于审批配置的方法与装置
CN107180339A (zh) * 2017-06-08 2017-09-19 成都牵牛草信息技术有限公司 工作流审批节点高效审批方法

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109816331A (zh) * 2018-12-20 2019-05-28 平安国际融资租赁有限公司 审核任务处理方法、装置、计算机设备和存储介质
CN111382989A (zh) * 2018-12-28 2020-07-07 上海汽车集团股份有限公司 数据处理方法及装置
CN111382989B (zh) * 2018-12-28 2024-01-26 上海汽车集团股份有限公司 数据处理方法及装置
CN111126930A (zh) * 2019-10-12 2020-05-08 中国平安财产保险股份有限公司 节点数据处理方法、装置、计算机设备和存储介质
CN111126930B (zh) * 2019-10-12 2024-04-09 中国平安财产保险股份有限公司 节点数据处理方法、装置、计算机设备和存储介质
CN111210204B (zh) * 2020-01-13 2023-10-27 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN111210204A (zh) * 2020-01-13 2020-05-29 普元信息技术股份有限公司 云平台流程应用业务审批环节中实现通用核查项配置与展现处理的系统及其方法
CN112184077A (zh) * 2020-10-30 2021-01-05 平安数字信息科技(深圳)有限公司 可配置的流程审批方法、装置、计算机设备及存储介质
CN112712452A (zh) * 2020-12-02 2021-04-27 杭州趣链科技有限公司 基于区块链的审批信息处理方法和装置
CN112446689A (zh) * 2020-12-15 2021-03-05 中煤能源研究院有限责任公司 一种防突措施实施过程管控的方法
CN113469517B (zh) * 2021-06-28 2024-01-05 北京喜沃思咨询有限公司 基于excel服务器的信息管理方法及系统
CN113469517A (zh) * 2021-06-28 2021-10-01 北京喜沃思咨询有限公司 基于excel服务器的信息管理方法及系统
CN117649210A (zh) * 2024-01-29 2024-03-05 国网浙江省电力有限公司宁海县供电公司 一种项目数据管理方法以及管理系统
CN117649210B (zh) * 2024-01-29 2024-04-19 国网浙江省电力有限公司宁海县供电公司 一种项目数据管理方法以及管理系统

Also Published As

Publication number Publication date
CN107180339A (zh) 2017-09-19
CN108805532B (zh) 2023-04-07
CN108805532A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
WO2018224024A1 (fr) Procédé d'approbation efficace pour noeud d'approbation de flux de travail
WO2018210248A1 (fr) Procédé basé sur des champs de formulaire permettant d'organiser des rôles d'examen et d'approbation sur des nœuds d'examen et d'approbation de flux de travail
WO2018214889A1 (fr) Procédé basé sur une contresignature permettant de configurer un nœud d'approbation dans un processus d'approbation
US20200151670A1 (en) Method for setting form field operation authority of workflow, and method for setting form field operation authority of approval node
CN108764833B (zh) 工作流审批节点按部门设置审批角色的方法
WO2018196876A1 (fr) Système et procédé de commande de flux de travaux basés sur une correspondance biunivoque entre des rôles et des utilisateurs
CN108984715B (zh) 基于依据字段设置审批流程的方法
WO2018205942A1 (fr) Procédé de configuration de rôles d'approbation en fonction de niveaux de services sur des nœuds d'approbation de flux de travail
WO2018214890A1 (fr) Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail
WO2019029650A1 (fr) Procédé de vérification d'opération de données de formulaire
WO2018214828A1 (fr) Procédé à base de vote permettant de configurer un nœud d'approbation dans un processus d'approbation
CN108711037B (zh) 审批工作流的委托及其再委托方法
JP2020520034A (ja) ロール対ユーザーに基づく１対１の権限承認方法とシステム
WO2019015539A1 (fr) Procédé d'autorisation d'une autorité d'exploitation de données de formulaire
JP7429390B2 (ja) 使用者に承認プロセスとその承認ノードの権限を与える方法
WO2019034023A1 (fr) Procédé permettant à un approbateur de demander une opinion de référence pour une tâche d'approbation
WO2019011162A1 (fr) Procédé de définition de fonction de raccourci
WO2019029500A1 (fr) Procédé d'autorisation séparée basé sur une valeur de colonne pour opération de liste statistique
OA19306A (en) Workflow control method and system based on one-to-one correspondence between roles and users.

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

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

Country of ref document: EP

Kind code of ref document: A1