1. Technical Field
The embodiments of the present disclosure relate to information processing technology, and particularly to a webpage permission control system and method.
2. Description of Related Art
A website may control access privilege for different people. For example, an employee may be restricted from accessing a specific webpage of the Website, and another employee may access the specific webpage of the website without any restriction. However, at present, most website establishes an independent page for each employee with a specific permission, which may result in difficulty of maintaining the website. Therefore, there is room for improvement in the art.
The disclosure is illustrated by way of examples and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.”
In general, the word “module”, as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, JAVA, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as in an EPROM. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable median include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives.
The database 5 may store a permission control list 600 as shown in
The first data field of the permission control list 600 is a primary key of the permission control list 600. The first data field of the permission control list 600 may be, but is not limited to, a unique identification number. For example, the unique identification number may be “3b92d506-5105-4c4b-b03f-cf802d599f5c” as shown in
The second data field of the permission control list 600 determines an authority of a user who accesses the data list 601. If the second data field of the permission control list 600 is associated with a table name of the data list 601, then the user is capable of accessing the data list 601, who is associated with the second data field of the permission control list 600. For example, if the role of the permission control list 600 is associated with five data lists 601, the user who is associated with the second data field is capable of accessing the five data lists 601. As shown in
The third data field of the permission control list 600 includes a table name of the data list 601. In other words, the permission control list 600 is associated with the data list 601 using the third data field.
The fourth data field of the permission control list 600 determines an authority for the user to access the data fields of the data list 601. The fourth data field of the permission control list 600 includes names of the data fields of the data list 601. For example, as shown in
The data list 601 may include, one or more data fields. As shown in
In addition, each GUI widget also includes four statuses, namely a visible status, a written-read status, a read-only status, and an invisible status. The visible status indicates that data in the GUI widget is visible to the user when the webpage 602 is displayed. The written-read status indicates that the data in the GUI widget can be read and/or amended. The read-only status indicates that the data in the GUI widget is restricted to read only. The invisible status indicates that the GUI widget is invisible to the user. The status of each GUI widget is the visible status as default. The user can amend the status of the each GUI widget. For example, the user may amend the status of the GUI widget from the visible status to the read-only status.
The generation module 210 generates the permission control list 600 and saves the permission control list 600 into the database 5.
The obtaining module 220 loads the webpage 602 from the database 5 and obtains a name of each GUI widget in the webpage 602. For example, as shown in
The assignment module 230 searches for the data list 601 from the database 5 and assigns data from the data list 601 to each GUI widget in the webpage 602. In one embodiment, the assignment module 230 assigns the data of each data field of the data list 601 to the GUI widget corresponding to the data field of the data list 601. For example, as shown in
The parsing module 240 searches for the permission control list 600 from the database 5, parses configuration information of the permission control list 600 and assigns the data of one or more data fields of the data list 601 to the configuration information of the permission control list 600. In one embodiment, the configuration information corresponds to one or more data fields of the data list 601 upon the condition that the configuration information includes names of the one or more data fields of the data list 601. The parsing module 240 searches for the fourth data field of the permission control list 600 and obtains configuration information from the fourth data field of the permission control list 600. As shown in
The amendment module 250 amends a status of each GUI widget corresponding to the configuration information. After amending the status of each GUI widget corresponding to the configuration information, the permission control of the webpage 602 is finished.
In step S10, the generation module 210 generates a permission control list 600 and saves the permission control list 600 into the database 5. The permission control list 600 is generated as shown in
In step S20, the obtaining module 220 loads a webpage 602 from the database 5 and obtains a name of each GUI widget in the webpage 602. For example, as shown in
In step S30, the assignment module 230 searches for a data list 601 from the database 5 and assigns data from the data list 601 to each GUI widget in the webpage 602.
In step S40, the parsing module 240 searches for the permission control list 600 from the database 5, parses configuration information of the permission control list 600 and assigns the data of one or more data fields of the data list 601 to the configuration information of the permission control list 600. For example, the parsing module 240 assigns the data of the data fields T1, T3 and T5 to the configuration information, changes the configuration information to “<Company><T1>A-F11111</T1><T3>cb</T3><T5>rb</T5></Company>.”
In step S50, the amendment module 250 amends a status of each GUI widget corresponding to the configuration information.
Although certain inventive embodiments of the present disclosure have been specifically described, the present disclosure is not to be construed as being limited thereto. Various changes or modifications may be made to the present disclosure without departing from the scope and spirit of the present disclosure.
Number | Date | Country | Kind |
---|---|---|---|
2013100310747 | Jan 2013 | CN | national |