Efficient examination and approval method for workflow examination and approval node

Abstract

The invention discloses an efficient examination and approval method for a workflow examination and approval node. The method comprises the steps of setting the examination and approval role of the examination and approval node and carrying out efficient examination and approval of the examination and approval role. The step of setting the examination and approval role of the examination and approval node comprises three ways of appointing a role, appointing a department (department manager role) and setting the examination and approval role according to a level. The process of carrying out efficient examination and approval of the examination and approval role comprises the following steps that: the examination and approval opinions of the first examination and approval role who submits the examination and approval opinion are taken as the examination and approval result of the examination and approval node; and if any one examination and approval role submits the examination and approval opinions, the examination and approval node finishes examination and approval. For the examination and approval node, when any one examination and approval role submits the examination and approval opinion, the examination and approval result of the examination and approval node is determined, the examination and approval node finishes examination and approval, and the examination and approval tasks of other examination and approval roles are automatically removed so as to realize efficient and quick examination and approval. The method is especially suitable for a situation that any person can give the examination and approval opinions since multiple people have the same examination and approval permission for the same examination and approval task.

Description

technical field [0001] The invention relates to a workflow approval method for management software systems such as ERP, in particular to an efficient approval method for workflow approval nodes. Background technique [0002] Role-based access control (RBAC) is the most researched and thoughtful database permission management mechanism in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and discretionary access control (DAC). Traditional discretionary access control has high flexibility but low security, mandatory access control has high security but is too restrictive; role-based access control combines both, which is not only easy to manage but also reduces complexity, cost and error probability , which 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, encaps...

AI Technical Summary

Problems solved by technology

[0008] In the above statement, both 2 and 3 need to authorize the role of class / group nature, but the method of authorization and workflow control through the role of class / group / position / type of work has the following disadvantages: 1. When user permissions change Difficult to operate: In actual system use, it is often necessary to adjust user permissions during operation. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot 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

[0010] 2. It is difficult to remember the specific permissions contained in the role for a long time: If the role has many permission function points, it is difficult to remember the specific permissions of the role over time, and it is even more difficult to remember the permission differences between roles with similar permissions. The permissions of the role are also easy to confuse; if you want to associate a new user, you cannot accurately determine how to choose the association

[0011] 3. Due to the change of user permissions, more and more roles will be created (if no new roles are created, the direct authorization to users will be greatly increased), and it is more difficult to distinguish the specific differences between the permissions of each role

[0012] 4. When transferring a post, if you want to assign many permissions of the transferred user to several other users, you must distinguish these permissions of the transferred user during processing, and then create roles to associate with the other users. users, such an operation is not only complicated and time-consuming, but also prone to errors

[0013] The workflow approval mechanism of the traditional system has the following defects: (1) The process initiator cannot be selected as the approver in the approval node. Before the end of the approval process, the initiator of the approval process cannot review and confirm the approval result of the application submitted by him, for example : The initiator initiated a reimbursement approval request of 10,000 yuan. Due to errors in the content submitted by the initiator or other reasons, the approved reimbursement amount was revised to 500 yuan after multi-level approval. The final approval result only allows reimbursement of 500 yuan. Approval end of process

If the sponsor has any objection after receiving the approval result, he must invalidate the previous approval process result and submit a new approval application, which increases the internal friction of the system and reduces the approval efficiency

[0014] (2) For inter-provincial and multinational group companies with complex organizational structures, the number of approval processes involved is very large, and the flow conditions and lines of the approval process are also very complicated. For the system process setters, the workload is very heavy. And it is easy to make mistakes when setting up the approval process, the system is very inconvenient to use, and the system reliability is not high

[0015] (3) When setting approval by level, the system cannot realize the approval of the approval request submitted by the highest-level department supervisor. Generally, it is necessary to assign a special approval role to the highest-level department supervisor separately, which increases the workload of the system workflow setup personnel

[0016] (4) The department level can only be judged by the role submitted in the approval process as the judgment standard, and other roles or departments involved in the form cannot be customized as the judgment standard for the department level, and there are certain limitations in use

[0017] Example: For a contract approval process, the signing role of the contract asks for leave and asks his colleague to initiate a contract approval for him, but the system recognizes his colleague as the submitting role of the process, and the judgment of the level is based on his Colleagues shall prevail, which cannot objectively reflect the department and position of the contract signing role

For example, the signing role of the contract is Salesperson 1 of the Marketing Department, and his colleague is the R&D Personnel 1 of the R&D Department. Originally, the contract should be approved by the supervisor of the department where the signing role belongs-the supervisor of the Marketing Department. The approval level of the approval node is set to 1, the system will assign R&D personnel 1 to the supervisor of the department-the supervisor of the R&D department for approval, and there is an error in the assignment of the approval process, which is inconvenient to use

[0018] In addition, the traditional workflow approval node has a single approval method. For multi-person approval, voting is often used. However, 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 actual application process In the middle, the approval efficiency is low, and it is impossible to achieve efficient and fast approval

Images