Method for arranging examination and approval roles at work flow examination and approval nodes based on form field

Abstract

The present invention discloses a method for arranging examination and approval roles at work flow examination and approval nodes based on a form field. A system organization structure is arranged, one of a role property field, a department property field or the submitted role of an examination and approval process in a form is selected as a rank main body, the rank main body is selected, the selected main body is taken as a judgment criterion to determine the rank; and a concrete rank numerical value is filled out. The method for arranging examination and approval roles at work flow examination and approval nodes based on the form field can take the role property field, the department property field or the submitted role related in the form as a standard for determining the department rank according to the requirements, such as the signed role in a contract form is selected as the rank main body, the signed role is taken as a standard to determine the rank (the submitted role is not the only selection) to determine the examination and approval roles of the examination and approval nodes, and therefore the method for arranging examination and approval roles at work flow examination and approval nodes based on the form field is more flexible and convenient to use and high in versatility. A system provides an assigned set to perform examination and approval of an examination and approval request submitted by a highest level department manager so as to avoid the problem that the highest level department manager cannot complete the examination and approval flow through the rank examination and approval mode.

Description

technical field [0001] The invention relates to a method for setting and managing approval roles of approval nodes in workflows of management software systems such as EPR, in particular to a method for setting approval roles for work flow approval nodes based on form fields. 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 , and thus has been greatly developed in recent years. The basic idea of ​​role-based access control (RBAC) is to divide different roles acc...

AI Technical Summary

Problems solved by technology

[0013] 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

[0014] 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

[0015] 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

[0017] (1) The initiator of the process 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 initiates a 10,000 yuan reimbursement approval Request, due to errors in the content submitted by the initiator or other reasons, the approved reimbursement amount is revised to 500 yuan after multi-level approval, and the final approval result only allows reimbursement of 500 yuan, and the approval process is over

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

[0018] (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

[0019] (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

[0020] (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

[0021] 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

Images