System task dispatching method

Abstract

The invention discloses a system task dispatching method. The method comprises determining tasks to be dispatched, namely, determining the tasks requiring dispatching; determining dispatching objects,namely, determining the objects to which the tasks are to be dispatched, wherein the objects are roles which are independent individuals but not groups / classes and one role can only be associated with a unique user in the same time period, and one user can be associated with one or more roles; dispatching, namely, dispatching tasks that require dispatching to the dispatching roles. According to the invention, the tasks are dispatched to the roles, and the user obtains the tasks through the association with the roles. When an employee leaves his / her post, the association between the employee and his / her role is canceled, and a new employee can be directly associated with the role. Re-dispatching for the new employee is not needed, and the operation is convenient and quick. When the employee is transferred to another position, the association with the original role is cancelled, and the tasks dispatched to a new role can be automatically obtained by associating with the new role. The dispatching object needs no action in the event of job termination or post transfer.

Description

technical field [0001] The invention relates to a dispatching method of management software systems such as ERP. 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, encapsulate the access rights of database resources in roles, and users can indirectly a...

AI Technical Summary

Problems solved by technology

[0007] In the above statement, both 2 and 3 need to authorize the roles 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

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

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

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

[0012] As far as the way of dispatching workers is concerned, the traditional system usually assigns work tasks directly to people. Once this person leaves or transfers, he must return all the tasks in his hands. There are the following defects: A: For this person , all tasks must be returned one by one, and the operation is cumbersome, especially for employees who are about to leave, they may not be willing to cooperate in completing the operation of returning tasks; B: For dispatchers, these tasks need to be reassigned to other People need to do repetitive work, which increases internal friction, and the dispatcher has a heavy workload and is prone to errors; C: The process of returning tasks usually needs to be approved, which prolongs the cycle of task execution and increases internal friction in the system; Approval is required, and if the task is not returned in time, it will seriously affect the execution of the task, especially some tasks have urgent time requirements. If it is not returned in time and handed over to a new person, it may cause serious consequences and unpredictable losses; D: When a user transfers a post, the user also needs to return all the previous tasks, and then the dispatcher dispatches tasks for the new post. There are also problems such as troublesome operation and delays in the task execution cycle.

Images