rdiframework.net━9.3 User Management ━web section

Rdiframework.net━. NET rapid Information System development framework

9.3 User Management-web Section

　　The user Management module mainly manages the users who can log on to the system. Follow-up work such as: User Attribution role, the allocation of rights, the corresponding functional modules owned by the user, the distribution of the rights of each business system, collaborative work, etc. are based on this. The main functions of user management are: adding user, modifying user, deleting user, setting user's default role, setting user's password, setting user's validity, exporting user data, etc. The user management main interface looks like this:

in the user management of the main interface, there are users to manage the appropriate permissions of the login user can add, modify, delete (single or bulk delete), set password, query users. This module is generally assigned to users with the system Administrator role, in case of accidental operation, the Super Admin user is not allowed to be modified and deleted . Of course, the framework core data delete operations are tombstoned rather than physically deleted. The deletion is the deletion flag on the corresponding record. To recover data that has been mistakenly deleted, you can contact a user with an operational database (for example:DBA) for data recovery. This interface only implements the User Management Service interface part of the common functions, the other functions in the service layer has been perfectly implemented, the user can do the corresponding extension, specific reference framework of the service interface Help files.

9.3.1, user add

Add the user interface as shown in:

9.3.2, User modification

Modify the user as shown in:

　　In modifying the user interface, the operator can modify the user's corresponding information, to modify the login user name to be cautious, so as not to modify the user can not log in normally, if you must modify the login user name, you want to tell the corresponding user login user name has changed. Users are not allowed to repeat the user name when modifying the user, if the number is entered, the number is not allowed to repeat, the system will automatically detect whether the data has been duplicated, the user has been set to remove the flag is not repeated verification of the scope of the system, the login user name can also be modified by the administrator.

9.3.3, set User password

Set user password as shown, the user's password can be set individually or in bulk, depending on the operator's choice. When adding a user, you can let the user's password be empty, waiting for all users to add and then batch unified password set, so that not only can save the operation time, but also prevent errors. In the "Set User password" screen, the operator can delete the password, set the default password, and set the new password.

9.3.4, deleting users

For a user who leaves the job, it can be deleted (tombstoned in the frame).

employees are not recommended to remove users directly when they leave, such as employee turnover, many systems of historical real data records should not be deleted, The user should be set to deactivate status (cancel the active state), after the employee leaves, the user deleted, may lead to some data relevance, reference errors, such as the resignation of people, the previous payroll data, log data, project data and so on have been the real data, should not be deleted by this user, The data should be preserved as historical data, leaving traces of history as the right thing to do. Supposedly, all data should not be physically deleted, but the logical deletion, for example, the deletion operation, just to the data hit a delete flag (for example, our framework table of Deletemark field flag set to 1 , indicates that it has been deleted), if you really need to delete the data, the database administrator should do a real physical deletion, Physical deletion of a piece of data is very easy, but because of the mistake of deleting a piece of data, want to get this data back to the cost is often very expensive, remember!

It is necessary for the operator to ask whether or not to delete the selected user before deleting it, as shown in.

9.3.5, exporting user data

　　In the user management interface, we can export to users.

Related articles:

Rdiframework.net-based on. NET rapid Information System development Framework-Series catalogue

Erichu
Source: http://blog.csdn.net/chinahuyong
Email:[email protected]
QQ Communication:406590790
Framework Blog:Http://blog.csdn.net/chinahuyong
Http://www.cnblogs.com/huyong
Rdiframework.net, based on. NET of rapid information system development, integration framework, to users and developers the best. NET Framework deployment scenarios.
about senior engineer, information System Project Manager, DBA. Focused on Microsoft platform Project architecture, management and enterprise solutions, multi-year project development and management experience, has organized and developed several large projects, in the object-oriented, service-oriented and database areas have a certain degree of accomplishment. is now mainly engaged in based onrdiframework.netframework of technical development, consulting work, mainly services in finance, health, railways, telecommunications, logistics, Internet of things, manufacturing, retail and other industries.
If you have any questions or suggestions, please enlighten me!
This article is copyright to the author and Csdn, welcome reprint, but without the author's consent must retain this paragraph, and in the article page obvious location to the original connection, if there is a problem, you can contact me by email or QQ, thank you very much.

rdiframework.net━9.3 User Management ━web section