CN113204790A

CN113204790A - View permission processing method, device, equipment and medium

Info

Publication number: CN113204790A
Application number: CN202110570938.7A
Authority: CN
Inventors: 熊小文; 李佳仕
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2021-05-25
Filing date: 2021-05-25
Publication date: 2021-08-03
Anticipated expiration: 2041-05-25
Also published as: CN113204790B

Abstract

The embodiment of the disclosure relates to a view permission processing method, a device, equipment and a medium, wherein the method comprises the following steps: in response to the creation operation of the view permission, showing a permission identification configuration item, wherein the permission identification configuration item comprises: a rights object configuration item and a group list configuration item; acquiring configuration information of the permission identification configuration item; and sending an authority creating request to a server, wherein the authority creating request carries the configuration information of the authority identifier configuration item, so that the server generates the authority identifier based on the configuration information of the authority identifier configuration item. The embodiment of the disclosure realizes the group-based view permission management, improves the convenience of view permission setting, improves the response speed of the client and relieves the pressure of the server.

Description

View permission processing method, device, equipment and medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for processing view permissions.

Background

With the development of networks, online forms gradually come into life of users, and the online forms store data of electronic forms in a cloud server, perform data interaction with the cloud server through network communication, and display contents of the forms through a display interface.

Currently, online forms incorporate online collaboration, information management, and visualization capabilities. In using an online form, multiple collaborators may collaboratively view and edit the same online form. Meanwhile, the online form can visually display the data to the user in a view mode, and can present the same data source by using various views. All data input into the online form can be converted into different display forms in real time, different views can be switched by one key, and the looking-up requirements of all users are met. In order to improve the visualization capability of the online form and meet more consulting requirements of users, the types of views are inevitably more and more, and at present, common views are as follows: a form view, a billboard view, a gantt chart, an album view, etc. However, the management scheme of view rights still needs to be perfected.

Disclosure of Invention

To solve the technical problem or at least partially solve the technical problem, the present disclosure provides a view permission processing method, apparatus, device, and medium.

The embodiment of the disclosure provides a view permission processing method, which is applied to a client, and the method comprises the following steps:

in response to the creation operation of the view permission, showing a permission identification configuration item, wherein the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

acquiring configuration information of the permission identification configuration item;

and sending an authority creating request to a server, wherein the authority creating request carries the configuration information of the authority identifier configuration item, so that the server generates the authority identifier based on the configuration information of the authority identifier configuration item.

responding to a table loading operation, sending a table loading request to a server, wherein the table loading request carries a table identifier and a user identifier, so that the server determines a group list to which the user identifier belongs and determines authority data hit by the group list;

acquiring form data corresponding to the form identification and authority data hit by the group list fed back by the server end in response to the form loading request, and loading the form data; the authority data comprises at least one authority identifier, and an authority object and authority information corresponding to the authority identifier;

and responding to the modification operation of the view attribute, judging whether to execute the modification operation based on the permission data, and modifying the permission type of the corresponding view if the execution is judged.

The embodiment of the disclosure provides a view permission processing method, which is applied to a server side and comprises the following steps:

receiving an authority creating request sent by a client, wherein the authority creating request carries configuration information of an authority identification configuration item; the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

generating an authority identifier based on the configuration information of the authority identifier configuration item;

and pushing the generated authority object and the authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list corresponding to the authority identifier.

receiving a form loading request sent by a client, wherein the form loading request carries a form identifier and a user identifier;

determining a group list to which the user identifier belongs and determining authority data hit by the group list; the authority data comprises at least one authority identifier, and an authority object and authority information corresponding to the authority identifier;

and feeding back table data corresponding to the table identification and the authority data hit by the group list to the client in response to the table loading request.

The embodiment of the present disclosure further provides a view permission processing apparatus, which is applied to a client, and the apparatus includes:

the display unit is used for responding to the creation operation of the view permission and displaying a permission identification configuration item, wherein the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

the acquisition unit is used for acquiring the configuration information of the authority identification configuration item;

a sending unit, configured to send an authority creation request to a server, where the authority creation request carries configuration information of the authority identifier configuration item, so that the server generates an authority identifier based on the configuration information of the authority identifier configuration item.

the sending unit is used for responding to a table loading operation and sending a table loading request to a server, wherein the table loading request carries a table identifier and a user identifier, so that the server determines a group list to which the user identifier belongs and determines authority data hit by the group list;

an obtaining unit, configured to obtain table data corresponding to the table identifier and authority data hit by the group list, where the table data corresponds to the table identifier and is fed back by the server in response to the table loading request, and load the table data; the authority data comprises at least one authority identifier, and an authority object and authority information corresponding to the authority identifier;

and the modifying unit is used for responding to the modifying operation of the view attribute, judging whether to execute the modifying operation based on the permission data, and modifying the permission type of the corresponding view if the modifying operation is judged to be executed.

The embodiment of the present disclosure further provides a view permission processing apparatus, which is applied to a server, and the apparatus includes:

the system comprises a receiving unit, a sending unit and a receiving unit, wherein the receiving unit is used for receiving an authority creating request sent by a client, and the authority creating request carries configuration information of an authority identification configuration item; the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

the generating unit is used for generating the authority identification based on the configuration information of the authority identification configuration item;

and the pushing unit is used for pushing the generated authority object and the authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list corresponding to the authority identifier.

the receiving unit is used for receiving a form loading request sent by a client, wherein the form loading request carries a form identifier and a user identifier;

the determining unit is used for determining a group list to which the user identifier belongs and determining authority data hit by the group list; the authority data comprises at least one authority identifier, and an authority object and authority information corresponding to the authority identifier;

and the sending unit is used for feeding back the table data corresponding to the table identification and the authority data hit by the group list to the client in response to the table loading request.

An embodiment of the present disclosure further provides an electronic device, including: a processor and a memory;

the processor is used for executing the view permission processing method provided by the embodiment of the disclosure by calling the program or the instruction stored in the memory.

The disclosed embodiments also provide a non-transitory computer-readable storage medium storing a program or instructions that cause a computer to perform the view permission processing method provided by the disclosed embodiments.

Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages:

when the view authority is created, the client sends the acquired configuration information of the authority object configuration item and the group list configuration item to the server, so that the server can generate the authority identifier based on the configuration information of the authority object configuration item and the group list configuration item, and therefore, the authority object is associated with the group list through the authority identifier, one or more groups in the group list corresponding to the authority identifier can perform authority operation on the associated authority object (view), the group-based view authority management is realized, and the convenience of view authority setting is improved.

Secondly, when table data is loaded for the first time, a client sends a table loading request carrying a table identifier and a user identifier to a server, so that the server can feed back corresponding table data based on the table identifier, determine a corresponding group list based on the user identifier, further feed back at least one authority identifier hit by the group list to which the user identifier belongs and authority objects and authority information corresponding to the authority identifiers based on the corresponding relation among the authority identifiers, the authority objects and the group list when the view attributes are created, and when the client responds to the modification operation of the view attributes, judge whether the view attributes have modification authority or not based on the authority data. Therefore, after the form data is loaded, the client can determine the permission information of the user to which the client belongs to the view in the form, and under the condition that the view permission of the user is not changed, when the user modifies the view attribute subsequently, the client does not need to inquire whether the view modification permission exists or not from the server, so that the response speed of the client is improved, and the pressure of the server is relieved. In addition, when the view attribute can be modified, the permission category of the corresponding view is modified, so that the flexible adjustment of the permission category of the view is realized.

And thirdly, the server creates configuration information of the permission object configuration item and the group list configuration item carried by the request based on the permission of the client, generates a permission identifier, and pushes the permission object and the permission information corresponding to the permission identifier to the client corresponding to each user identifier in the group list corresponding to the permission identifier, so that when the permission operation is performed on the view on the client corresponding to each user identifier in the group list corresponding to the permission identifier, the corresponding client does not need to send a query request for whether the permission to operate to the server, and particularly when a plurality of collaborators collaborate to operate the table, the number of concurrent requests of permission interfaces is greatly reduced, and the pressure of the server is greatly reduced.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

Fig. 1 is a schematic flowchart of a view permission processing method according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a view permission updating method according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a group adding or deleting method of view permissions according to an embodiment of the present disclosure;

fig. 4 is a schematic flowchart of a view permission deletion method according to an embodiment of the present disclosure;

fig. 5 is a schematic flowchart of another view permission processing method according to an embodiment of the present disclosure;

fig. 6 is a schematic flowchart of another view permission processing method according to an embodiment of the present disclosure;

fig. 7 is a flowchart illustrating another view permission processing method according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of a view authority processing apparatus according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of another view authority processing apparatus according to an embodiment of the present disclosure;

fig. 10 is a schematic structural diagram of another view authority processing apparatus according to an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of another view authority processing apparatus according to an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

At present, the management of view permissions of online forms in existing schemes is based on roles, that is, when creating and setting permission information of users to views, permission information needs to be configured for each user one by one, so that the management of view permissions is complicated. Moreover, the modification of the view permission related attributes is limited to locking the view and cannot meet the requirements of users. In addition, in order to manage the group view authority, authority information and group information are written in the data structure of the view. Therefore, in order to implement authentication, the client needs to request the server to query the current operation permission of the user on the view permission in real time when executing view permission operation each time, and at this time, when a plurality of collaborators cooperatively operate an online form, a high concurrent request is brought, and great pressure is brought to the server.

In order to solve the above problem, an embodiment of the present disclosure provides a view permission processing method, which is described below with reference to specific embodiments.

Fig. 1 is a flowchart illustrating a method for processing view permission according to an embodiment of the present disclosure, where the method may be performed by a view permission processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 1, the method is applied to a client, and includes:

step 101, responding to the creation operation of the view authority, and displaying the authority identification configuration item.

In some embodiments, the rights identification configuration item includes: a rights object configuration item and a group list configuration item. Wherein the rights object configuration item is used to configure the rights object, e.g. view; the group list configuration item is used for configuring the group list. In some embodiments, the online form may be associated with a social software, and accordingly, the group list may enter group information divided on the corresponding social software.

In an implementation manner of the embodiment of the present disclosure, after a user creates an online form, enters form data, and realizes view display of the form data (at this time, a view authority is empty, that is, authority information of each user to each view is not set), when a function item of a certain view is clicked, a view authority creation button that is displayed can be selected to trigger creation operation of the view authority of the view; or, each view can be displayed by clicking a view authority creating button on the online form, and then the creation operation of the view authority of the view is triggered by selecting a certain view; alternatively, the creation operation of the view authority of each view may be triggered by directly clicking a view authority creation button on the online form. At this time, the client responds to the creation operation of the view permission, and can display the permission identification configuration item in a popup window form, so that the user can input the configuration information of the permission identification configuration item in the permission identification configuration item. It can be understood that, for the triggering manner of the creation operation of the various view permissions described above, when the client responds to the creation operation of the view permission of a certain view, only the permission identification configuration item for the view is presented. When the client side responds to the creation operation of the view permission of each view, permission identification configuration items aiming at each view can be displayed at the same time, and the permission identification configuration items aiming at each view can be selectively displayed one by one in a pull-down option mode.

In some embodiments, the rights object configuration item includes: the table identifies the configuration sub-item and the view identifies the configuration sub-item. The table identifier configuration sub-item is used for configuring a table identifier, and the table identifier is a unique identifier used for characterizing the table, that is, the table identifiers of different tables are different, and the table identifier may be a character string. In addition, the view identifier configuration sub-item is used for configuring a view identifier, and similar to the table identifier, the view identifier is a unique identifier for characterizing the view, and even though the view identifiers of different types of views representing the same data source may be different, the view identifier may be a character string. The disclosed embodiments do not limit the composition of the form identifier and the view identifier.

In some embodiments, the group list configuration item comprises: the group identification configures the sub-item, the group type configures the sub-item and the authority information configures the sub-item. The group id configuration sub-item is used to configure a group id, where the group id is a unique id used to characterize a group, that is, the group ids of different groups are different, and the group id may be a character string. The group type configuration sub-item is used for configuring a group type, and the group type is used for limiting group members. For example, when the group type is 0, the group member is the corresponding group, and when the group type is other values, the group member is the specific person in the corresponding group. For example, a group type may include a plurality of values (which may be separated by a symbol, such as a comma, between values in a corresponding data structure) when the group type is other values, each value corresponding to one person in the group, for example, when the group type includes 1, the group member includes the first person in the corresponding group list, when the group type includes 2, the group member includes the second person in the corresponding group list, and so on. In addition, the authority information configuration sub-item is used for configuring authority information, and the authority information is used for representing the operation authority of the group members on the view authority. For example, when the rights information is 1 or true, it indicates that the corresponding group member is operable to the view rights; and when the authority information is 0 or false, the view authority is not operable by the corresponding group member.

And 102, acquiring configuration information of the authority identification configuration item.

In an implementation of the embodiment of the present disclosure, after displaying the permission identifier configuration item, the user may input corresponding configuration information according to the indicated permission identifier configuration item, and after confirming the configuration information, the client may obtain the configuration information of the permission identifier configuration item. In another implementation of the embodiment of the present disclosure, after displaying the permission identifier configuration items, the client may automatically display corresponding configuration information in each permission identifier configuration item, and after the user confirms the displayed configuration information, the client may obtain the configuration information of the permission identifier configuration item.

Illustratively, based on the above technical solution, for the form identifier, the form identifier may be automatically generated when the user creates an online form, and at this time, when the form identifier configuration sub-item is displayed, the form identifier may be automatically entered by the system and confirmed by the user; the form identifier can also be customized by the user, and at this time, when the form identifier configuration sub-item is displayed, the form identifier is input by the user in a customized manner and confirmed. For the view identifier, the view identifier can be automatically generated when the view is generated based on the entered form data, and at the moment, when the view identifier configuration sub-item is displayed, the view identifier can be automatically entered by the system and confirmed by the user; the view identifier can also be customized by the user, and at this time, when the view identifier configuration sub-item is displayed, the user customizes and inputs the view identifier and confirms the view identifier. In addition, the group identifier, the group type and the authority information can be preset by a user, when the group list configuration item is displayed, the group identifier, the group type and the authority information can be displayed in the corresponding group list configuration item in a pull-down option mode, and the user confirms the configuration information in a pull-down selection or adding mode.

103, sending an authority creating request to the server, wherein the authority creating request carries the configuration information of the authority identification configuration item, so that the server generates the authority identification based on the configuration information of the authority identification configuration item.

In some embodiments, the client may send an authority creation request to the server in an HTTP request manner, where the authority creation request carries configuration information of an authority identifier configuration item, so that the server may generate an authority identifier based on the configuration information of the authority identifier configuration item after receiving the authority creation request, where the authority identifier may be a character string randomly generated by the server, and the authority identifier corresponds to the view one to one. In this way, the rights object is associated with the group list, that is, the table identifier and the view identifier are associated with the group identifier, the group type and the rights information, so that the rights information of the group members (groups or persons in the groups) of the corresponding group to the view in the table can be accurately determined based on the rights identifiers.

According to the view permission processing scheme provided by the embodiment of the disclosure, when the view permission is created, the client sends the acquired configuration information of the permission object configuration item and the group list configuration item to the server, so that the server can generate the permission identifier based on the configuration information of the permission object configuration item and the group list configuration item, and therefore the permission object is associated with the group list through the permission identifier, one or more groups in the group list corresponding to the permission identifier can perform permission operation on the associated permission object (view), thereby realizing group-based view permission management and improving convenience in view permission setting.

Based on the above technical solution, in some embodiments, fig. 2 is a schematic flow chart of a view permission updating method provided by the embodiments of the present disclosure. As shown in fig. 2, the method includes:

step 201, responding to the updating operation of the view permission, and displaying the permission updating configuration item.

Wherein, the permission updating configuration item comprises: the rights identify the entry and the group list configuration item.

In some embodiments, after the client sends the permission creation request to the server, the server sends the generated permission identifier to the client in response to the permission creation request, and the permission identifier is stored in the client. When the view permission of a certain view needs to be updated, a user can select an update option of the view permission by clicking a function item of the view to trigger the update operation of the view permission; and the client responds to the updating operation of the view permission and shows the permission updating configuration item.

Step 202, obtaining the configuration information of the permission updating configuration item.

In some embodiments, the client associates the permission identifier with the corresponding view after receiving the permission identifier, and further displays the corresponding permission identifier in the permission identifier entry when displaying the permission update configuration item, and displays the configuration information of the created or previously updated group list in the group list configuration item. As such, the user may modify based on the configuration information in the group list configuration item: specifically, the user selects a group to be updated based on the group identifier, that is, selects the group identifier (the group identifier does not need to be modified), modifies the permission information or modifies the group type and the permission information simultaneously according to actual requirements under the group identifier, and after the modification is completed, the user confirms the configuration information of the permission update configuration item, so that the client can obtain the configuration information of the permission update configuration item.

Step 203, sending an authority updating request to the server, where the authority updating request carries configuration information of the authority updating configuration item, so that the server updates the group list corresponding to the authority identifier based on the configuration information of the authority updating configuration item.

In some embodiments, the client may send an authority updating request to the server in an HTTP request manner, where the authority updating request carries configuration information of an authority updating configuration item, so that the server may update the group list corresponding to the authority identifier based on the configuration information of the authority updating configuration item after receiving the authority updating request, thereby implementing updating of the authority information of the group or the group staff.

Based on the above technical solutions, in some embodiments, fig. 3 is a schematic flow diagram of a method for adding or deleting a group of view permissions provided by an embodiment of the present disclosure. As shown in fig. 3, the method includes:

step 301, responding to the group adding or deleting operation of the view authority, and displaying the group adding or deleting configuration items.

Wherein, the group adding or deleting configuration items comprises: the rights identify the entry and the group list configuration item.

In some embodiments, after the client sends the permission creation request to the server, the server sends the generated permission identifier to the client in response to the permission creation request, and the permission identifier is stored in the client. When the group of the view permission of a certain view needs to be added or deleted, a user can select a group adding or deleting option of the view permission by clicking a function item of the view to trigger the group adding or deleting operation of the view permission; and the client responds to the group adding or deleting operation of the view permission and shows the group adding or deleting configuration items.

Step 302, obtaining the configuration information of the group adding or deleting configuration items.

In some embodiments, the client associates the authority identifier with the corresponding view after receiving the authority identifier, and further displays the corresponding authority identifier in the authority identifier input item when displaying the authority update configuration item, and respectively and correspondingly inputs the group identifier, the group type and the authority information in the group list configuration item when a group needs to be added, so as to configure the authority information for the added group or group personnel; when a group needs to be deleted, only the group identifier or the group type corresponding to the group needing to be deleted needs to be input in the group list configuration item, and after the user confirms the configuration information of the group addition or deletion configuration item, the client can acquire the configuration information of the group addition or deletion configuration item.

Step 303, sending a group adding or deleting request to the server, where the group adding or deleting request carries configuration information of the group adding or deleting configuration item, so that the server adds or deletes the group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration item.

In some embodiments, the client may send a group addition or deletion request to the server in an HTTP request manner, where the group addition or deletion request carries configuration information of a group addition or deletion configuration item, so that after receiving the group addition or deletion request, the server may add or delete a group list corresponding to the permission identifier based on the configuration information of the group addition or deletion configuration item, thereby implementing addition or deletion of a group or group personnel operating on view permission.

Based on the above technical solution, in some embodiments, fig. 4 is a schematic flow chart of a method for deleting view permissions provided by the embodiments of the present disclosure. As shown in fig. 4, the method includes:

and step 401, responding to the deletion operation of the view permission, and displaying a permission deletion configuration item.

Wherein, the permission deleting configuration item comprises: the rights identify the entry.

In some embodiments, after the client sends the permission creation request to the server, the server sends the generated permission identifier to the client in response to the permission creation request, and the permission identifier is stored in the client. When the view permission of a certain view needs to be deleted, a user can select a deletion option of the view permission by clicking a function item of the view to trigger the deletion operation of the view permission; and the client responds to the deletion operation of the view permission and displays the permission deletion configuration item.

And 402, acquiring the configuration information of the permission deletion configuration item.

In some embodiments, the client associates the permission identifier with the corresponding view after receiving the permission identifier, and then displays the corresponding permission identifier in the permission identifier entry when displaying the permission deletion configuration item, and then the client can obtain the configuration information of the permission deletion configuration item after the user confirms the permission identifier.

Step 403, sending an authority deletion request to the server, where the authority deletion request carries configuration information of the authority deletion configuration item, so that the server deletes the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deletion configuration item.

In some embodiments, the client may send an authority deletion request to the server in an HTTP request manner, where the authority deletion request carries configuration information of an authority deletion configuration item, so that after receiving the authority deletion request, the server may delete the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deletion configuration item, thereby deleting the view authority of a certain view, that is, the view authority is empty.

Fig. 5 is a flowchart of another view permission processing method provided by the embodiment of the present disclosure, which may be executed by a view permission processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 5, the method is applied to a client, and includes:

step 501, responding to a table loading operation, sending a table loading request to a server, where the table loading request carries a table identifier and a user identifier, so that the server determines a group list to which the user identifier belongs and determines authority data hit by the group list.

In some embodiments, the clients may include a host client, which is a client that creates a form (an online form), and a collaboration client, which is a client held by a collaborator that can view and edit the form. After a user creates a table, a main client uploads table data to a server, and when the table is checked through a collaborative client for the first time, the table data of the server needs to be loaded to the local. In an embodiment, when a user inputs a web page address of a form through a browser of a collaborative client, a form loading operation may be triggered, and at this time, the collaborative client sends a form loading request to a server in response to the form loading operation. The table loading request carries a table identifier and a user identifier, so that the server determines corresponding table data based on the table identifier, determines a group list to which a user requesting to load the table belongs based on the user identifier, and further determines hit authority data based on the group list.

Step 502, obtaining table data corresponding to the table identifier fed back by the server in response to the table loading request and authority data hit by the group list, and loading the table data.

The authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information. Since one view corresponds to one rights identifier when creating view rights, one view may correspond to multiple group lists, and different views may correspond to the same group list, the rights data corresponding to one group list may include one or more rights identifiers.

It can be understood that, in the technical scheme of the present disclosure, for the processing of the view permission, all collaboration clients can normally load the form data and display the view, and all collaborators can view and edit the view.

Step 503, responding to the modification operation of the view attribute, judging whether to execute the modification operation based on the permission data, and if the execution is judged, modifying the permission type of the corresponding view.

In some embodiments, the view attribute is an attribute related to the view permission, and therefore, whether the view attribute has permission to modify the operation can be determined based on the permission data. Specifically, when a view attribute of a certain view needs to be modified, a user can select a modification option of the view attribute by clicking a function item of the view to trigger the modification operation of the view attribute; the client responds to the modification operation of the view attribute, inquires the authority objects, namely the table identification and the view identification, in the authority data, and matches the table identification and the view identification corresponding to the view attribute with the table identification and the view identification in the authority data respectively; if the matching is successful, further checking the authority information corresponding to the successfully matched authority object; if the authority information is true, for example 1 or true, then the modification operation is determined to be executed; if the authority information is false, for example, 0 or false, it is determined that the modification operation is not performed. In addition, if the matching fails, it is determined that the modification operation is not performed.

In some embodiments, modifying the permission category of the corresponding view includes:

and modifying the permission field in the data structure of the corresponding view, wherein the permission field is a field which is added in the data structure of the view in advance, and the permission field is used for describing the permission type of the view.

In some embodiments, the permission category is a public view, a locked view, or a personal view. Wherein the public view indicates that all people can view and edit, the locked view indicates that view properties cannot be modified, and the individual view indicates that only individuals or parts of individuals can view and edit.

For example, when determining not to perform a modification operation, the client may not perform any operation or the popup hint view attribute may not be modified. And when the modification operation is judged to be executed, the client displays the options of the permission types, and after the user determines the permission types, the client modifies the permission types of the corresponding views.

According to the view permission processing scheme provided by the embodiment of the disclosure, when table data is loaded for the first time, a client sends a table loading request carrying a table identifier and a user identifier to a server, so that the server can feed back corresponding table data based on the table identifier, determine a corresponding group list based on the user identifier, and further feed back at least one permission identifier hit by the group list to which the user identifier belongs and permission objects and permission information corresponding to the permission identifiers based on the corresponding relation among the permission identifiers, the permission objects and the group list when the view permission is created, and when the client responds to the view attribute modification operation, the client can judge whether the view attribute has modification permission based on the permission data. Therefore, after the form data is loaded, the client can determine the permission information of the user to which the client belongs to the view in the form, and under the condition that the view permission of the user is not changed, when the user modifies the view attribute subsequently, the client does not need to inquire whether the view modification permission exists or not from the server, so that the response speed of the client is improved, and the pressure of the server is relieved. In addition, when the view attribute can be modified, the permission category of the corresponding view is modified, so that the flexible adjustment of the permission category of the view is realized.

Fig. 6 is a flowchart of another view permission processing method provided by the embodiment of the present disclosure, which may be executed by a view permission processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 6, the method is applied to a server, and includes:

step 601, receiving an authority creating request sent by a client, wherein the authority creating request carries configuration information of an authority identification configuration item.

Wherein, the authority identification configuration item comprises: a rights object configuration item and a group list configuration item. The rights object configuration item includes: the table identifies the configuration sub-item and the view identifies the configuration sub-item. The group list configuration item includes: the group identification configures the sub-item, the group type configures the sub-item and the authority information configures the sub-item.

Step 602, generating an authority identifier based on the configuration information of the authority identifier configuration item.

And the server generates the authority identification based on the configuration information of the authority identification configuration item, the authority identification can be a character string randomly generated by the server, and the authority identification corresponds to the view one by one. In this way, the rights object is associated with the group list, that is, the table identifier and the view identifier are associated with the group identifier, the group type and the rights information, so that the rights information of the group members (groups or persons in the groups) of the corresponding group to the view in the table can be accurately determined based on the rights identifiers.

Step 603, pushing the generated authority object and authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list corresponding to the authority identifier.

In some embodiments, each user in the group list is provided with a corresponding user identifier, and the user identifier is bound with a corresponding client. After the server generates the authority identifier, a group list corresponding to the authority identifier and each user identifier in the group list are determined, a client corresponding to the user identifier is further determined, and finally, the authority object and the authority information corresponding to the authority identifier are pushed to the corresponding client. Therefore, after the corresponding client renders the received rights object and the rights information, the rights information of the corresponding client to the rights object can be determined, so that an inquiry request for whether the operation rights exist or not is not required to be sent to the server, and the pressure of the server is relieved. In an embodiment, the server may push information to the client through the Websocket interface.

According to the view permission processing scheme provided by the embodiment of the disclosure, the server generates the permission identifier based on the configuration information of the permission object configuration item and the group list configuration item carried by the permission creation request of the client, and pushes the permission object and the permission information corresponding to the permission identifier to the client corresponding to each user identifier in the group list corresponding to the permission identifier, so that when the permission operation is performed on the view on the client corresponding to each user identifier in the group list corresponding to the permission identifier, the corresponding client does not need to send a query request for whether the permission to operate to the server, especially when a plurality of collaborators cooperatively operate the form, the number of concurrent requests of the permission interface is greatly reduced, and the pressure of the server is greatly reduced.

Based on the above technical solution, in some embodiments, the method further includes: and sending the generated permission identification to the client in response to the permission creation request. Therefore, the client can complete the operations of permission updating, group adding or deleting, permission deleting and the like based on the permission identification and matching with the server.

Based on the above technical solution, in some embodiments, the method further includes:

step 701, receiving an authority updating request sent by a client, wherein the authority updating request carries configuration information of an authority updating configuration item.

And step 702, updating the group list corresponding to the authority identification based on the configuration information of the authority updating configuration item.

Step 703, pushing the rights object and the rights information corresponding to the updated rights identifier to the client corresponding to each user identifier updated in the group list corresponding to the rights identifier.

And the server side pushes the authority object and the authority information corresponding to the updated authority identifier to the client side corresponding to each updated user identifier in the group list corresponding to the authority identifier, so that the corresponding client side completes the coordination of the view authority.

step 801, receiving a group adding or deleting request sent by a client, where the group adding or deleting request carries configuration information of a group adding or deleting configuration item.

Wherein, the group adding or deleting configuration items comprises: the authority identification input item and the group list configuration item;

step 802, adding or deleting the group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration item.

Step 803, pushing the rights object and the rights information corresponding to the rights identifier to the client corresponding to each user identifier in the group list added or deleted by the rights identifier.

And the client pushes the authority object and the authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list added or deleted by the authority identifier, so that the corresponding client completes the coordination of the view authority.

step 901, receiving an authority deletion request sent by a client, where the authority deletion request carries configuration information of an authority deletion configuration item.

The permission deletion configuration item comprises: the rights identify the entry.

And 902, deleting the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deletion configuration item.

And step 903, pushing the authority object and the authority information corresponding to the deleted authority identifier to the client corresponding to each user identifier in the group list corresponding to the authority identifier.

And the server side pushes the authority object and the authority information corresponding to the deleted authority identification to the client side corresponding to each user identification in the group list corresponding to the authority identification, so that the corresponding client side completes the coordination of the view authority.

Fig. 7 is a flowchart of another view permission processing method provided by the embodiment of the present disclosure, which may be executed by a view permission processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 7, the method is applied to a server, and includes:

step 1001, receiving a form loading request sent by a client, where the form loading request carries a form identifier and a user identifier.

Step 1002, determine the group list to which the user identifier belongs and determine the authority data hit by the group list.

The authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information.

In some embodiments, the server pre-maintains a corresponding relationship among the authority identifier, the authority object corresponding to the authority identifier, and the group list corresponding to the authority identifier; and based on the corresponding relation, determining a group list to which the user identifier belongs and determining authority data hit by the group list.

Step 1003, feeding back the table data corresponding to the table identifier and the authority data hit by the group list to the client in response to the table loading request.

According to the view permission processing scheme provided by the embodiment of the disclosure, after receiving a form loading request sent by a client, a server can feed back corresponding form data based on form identification, determine a corresponding group list based on user identification, and further feed back at least one permission identification hit by the group list to which the user identification belongs, and permission objects and permission information corresponding to the permission identification based on correspondence of the permission identification, the permission object and the group list when creating view permission, so that when the client responds to a modification operation of a view attribute, whether the view attribute has modification permission can be judged based on the permission data. Therefore, after the form data is loaded, the client can determine the permission information of the user to which the client belongs to the view in the form, and under the condition that the view permission of the user is not changed, when the user modifies the view attribute subsequently, the client does not need to inquire whether the view modification permission exists or not from the server, so that the response speed of the client is improved, and the pressure of the server is relieved. In addition, when the view attribute can be modified, the permission category of the corresponding view is modified, so that the flexible adjustment of the permission category of the view is realized.

Fig. 8 is a schematic structural diagram of a view permission processing apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 8, the apparatus is applied to a client, and includes:

the presentation unit 10 is configured to present, in response to the creation operation of the view permission, a permission identification configuration item, where the permission identification configuration item includes: a rights object configuration item and a group list configuration item;

an obtaining unit 11, configured to obtain configuration information of the permission identifier configuration item;

the sending unit 12 is configured to send an authority creating request to the server, where the authority creating request carries configuration information of the authority identifier configuration item, so that the server generates the authority identifier based on the configuration information of the authority identifier configuration item.

In some embodiments, the rights object configuration item includes: the table identifies the configuration sub-item and the view identifies the configuration sub-item.

In some embodiments, the group list configuration item comprises: the group identification configures the sub-item, the group type configures the sub-item and the authority information configures the sub-item.

In some embodiments, the presentation unit 10 is further configured to present, in response to the update operation of the view permission, a permission update configuration item, where the permission update configuration item includes: the authority identification input item and the group list configuration item;

the obtaining unit 11 is further configured to obtain configuration information of the permission updating configuration item;

the sending unit 12 is further configured to send an authority updating request to the server, where the authority updating request carries configuration information of an authority updating configuration item, so that the server updates the group list corresponding to the authority identifier based on the configuration information of the authority updating configuration item.

In some embodiments, the presentation unit 10 is further configured to present a group addition or deletion configuration item in response to a group addition or deletion operation of the view permission, where the group addition or deletion configuration item includes: the authority identification input item and the group list configuration item;

the obtaining unit 11 is further configured to obtain configuration information of the group addition or deletion configuration item;

the sending unit 12 is further configured to send a group adding or deleting request to the server, where the group adding or deleting request carries configuration information of the group adding or deleting configuration items, so that the server adds or deletes a group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration items.

In some embodiments, the presentation unit 10 is further configured to present, in response to the deletion operation of the view permission, a permission deletion configuration item, where the permission deletion configuration item includes: an authority identification entry;

the obtaining unit 11 is further configured to obtain configuration information of the permission deletion configuration item;

the sending unit 12 is further configured to send an authority deletion request to the server, where the authority deletion request carries configuration information of an authority deletion configuration item, so that the server deletes the authority identifier and the group list corresponding to the authority identifier based on the configuration information of the authority deletion configuration item.

The view permission processing device provided by the embodiment of the disclosure can execute the view permission processing method provided by the corresponding embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.

Fig. 9 is a schematic structural diagram of another view authority processing apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 9, the apparatus is applied to a client, and includes:

a sending unit 20, configured to send a table loading request to the server in response to a table loading operation, where the table loading request carries a table identifier and a user identifier, so that the server determines a group list to which the user identifier belongs and determines authority data hit by the group list;

the acquiring unit 21 is configured to acquire table data corresponding to a table identifier and authority data hit by a group list, which are fed back by a server in response to a table loading request, and load the table data; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

and the modifying unit 22 is configured to respond to the modifying operation of the view attribute, determine whether to execute the modifying operation based on the permission data, and modify the permission type of the corresponding view if the executing is determined.

In some embodiments, the modifying unit 22 is specifically configured to modify a permission field in the data structure of the corresponding view, where the permission field is a field that is added in advance in the data structure of the view, and the permission field is used to describe a permission category of the view.

In some embodiments, the permission category is a public view, a locked view, or a personal view.

Fig. 10 is a schematic structural diagram of another view authority processing apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 10, the apparatus is applied to a server, and includes:

a receiving unit 30, configured to receive an authority creation request sent by a client, where the authority creation request carries configuration information of an authority identifier configuration item; the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

a generating unit 31 for generating an authority identifier based on the configuration information of the authority identifier configuration item;

and the pushing unit 32 is configured to push the generated rights object and rights information corresponding to the rights identifier to the client corresponding to each user identifier in the group list corresponding to the rights identifier.

In some embodiments, the apparatus further includes a response unit, configured to send the generated permission identifier to the client in response to the permission creation request.

In some embodiments, the receiving unit 30 is further configured to receive an authority updating request sent by the client, where the authority updating request carries configuration information of an authority updating configuration item; the authority update configuration item includes: the authority identification input item and the group list configuration item;

the generating unit 31 is further configured to update the group list corresponding to the authority identifier based on the configuration information of the authority update configuration item;

the pushing unit 32 is further configured to push the rights object and the rights information corresponding to the updated rights identifier to the client corresponding to each updated user identifier in the group list corresponding to the rights identifier.

In some embodiments, the receiving unit 30 is further configured to receive a group addition or deletion request sent by the client, where the group addition or deletion request carries configuration information of a group addition or deletion configuration item, and the group addition or deletion configuration item includes: the authority identification input item and the group list configuration item;

the generating unit 31 is further configured to add or delete a group list corresponding to the authority identifier based on the configuration information of the group addition or deletion configuration item;

the pushing unit 32 is further configured to push the rights object and the rights information corresponding to the rights identifier to the client corresponding to each user identifier in the group list added or deleted by the rights identifier.

In some embodiments, the receiving unit 30 is further configured to receive an authority deletion request sent by the client, where the authority deletion request carries configuration information of an authority deletion configuration item, and the authority deletion configuration item includes: an authority identification entry;

the generating unit 31 is further configured to delete the authority identifier and the group list corresponding to the authority identifier based on the configuration information of the authority deletion configuration item;

the pushing unit 32 is further configured to push the rights object and the rights information corresponding to the deleted rights identifier to the client corresponding to each user identifier in the group list corresponding to the rights identifier.

Fig. 11 is a schematic structural diagram of another view authority processing apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 11, the apparatus is applied to a server, and includes:

the receiving unit 40 is configured to receive a table loading request sent by a client, where the table loading request carries a table identifier and a user identifier;

a determining unit 41, configured to determine a group list to which the user identifier belongs and determine authority data in which the group list hits; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

and a sending unit 42, configured to feed back, to the client, the table data corresponding to the table identifier and the authority data hit by the group list in response to the table loading request.

In some embodiments, the above apparatus further comprises: the maintenance unit is used for maintaining the corresponding relation among the authority identification, the authority object corresponding to the authority identification and the group list corresponding to the authority identification in advance;

the determining unit 41 is specifically configured to determine, based on the correspondence, a group list to which the user identifier belongs and determine authority data in which the group list hits.

The disclosed embodiments also provide a computer program product comprising a computer program/instruction, which when executed by a processor implements the view permission processing method provided by the disclosed embodiments.

Referring now specifically to FIG. 12, a schematic diagram of a structure suitable for use in implementing the electronic device 1100 in embodiments of the present disclosure is shown. The electronic device 1100 in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle-mounted terminal (e.g., a car navigation terminal), etc., and a stationary terminal such as a digital TV, a desktop computer, etc. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 12, the electronic device 1100 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 1101 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)1102 or a program loaded from a storage means 1108 into a Random Access Memory (RAM) 1103. In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are also stored. The processing device 1101, the ROM 1102, and the RAM 1103 are connected to each other by a bus 1104. An input/output (I/O) interface 1105 is also connected to bus 1104.

Generally, the following devices may be connected to the I/O interface 1105: input devices 1106 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1107 including, for example, Liquid Crystal Displays (LCDs), speakers, vibrators, and the like; storage devices 1108, including, for example, magnetic tape, hard disk, etc.; and a communication device 1109. The communication means 1109 may allow the electronic device 1100 to communicate wirelessly or wiredly with other devices to exchange data. While fig. 12 illustrates an electronic device 1100 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via the communication device 1109, or installed from the storage device 1108, or installed from the ROM 1102. The computer program, when executed by the processing apparatus 1101, performs the above-described functions defined in the view authority processing method of the embodiment of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to the creation operation of the view permission, and showing a permission identification configuration item, wherein the permission identification configuration item comprises: a rights object configuration item and a group list configuration item; acquiring configuration information of the authority identification configuration item; and sending an authority creating request to the server, wherein the authority creating request carries the configuration information of the authority identification configuration item, so that the server generates the authority identification based on the configuration information of the authority identification configuration item.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to a table loading operation, sending a table loading request to a server, wherein the table loading request carries a table identifier and a user identifier, so that the server determines a group list to which the user identifier belongs and determines authority data hit by the group list; acquiring form data corresponding to a form identifier fed back by a server end in response to a form loading request and authority data hit by a group list, and loading the form data; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information; and responding to the modification operation of the view attribute, judging whether to execute the modification operation based on the permission data, and modifying the permission type of the corresponding view if the execution is judged.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving an authority creating request sent by a client, wherein the authority creating request carries configuration information of an authority identification configuration item; the permission identification configuration item comprises: a rights object configuration item and a group list configuration item; generating an authority identifier based on the configuration information of the authority identifier configuration item; and pushing the generated authority object and the authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list corresponding to the authority identifier.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a form loading request sent by a client, wherein the form loading request carries a form identifier and a user identifier; determining a group list to which the user identifier belongs and determining authority data hit by the group list; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information; and feeding back the table data corresponding to the table identification and the authority data in the group list hit to the client in response to the table loading request.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, the present disclosure provides a view permission processing method, applied to a client, including:

responding to the creation operation of the view permission, and showing a permission identification configuration item, wherein the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

acquiring configuration information of the authority identification configuration item;

and sending an authority creating request to the server, wherein the authority creating request carries the configuration information of the authority identification configuration item, so that the server generates the authority identification based on the configuration information of the authority identification configuration item.

According to one or more embodiments of the present disclosure, in a view permission processing method provided by the present disclosure, a permission object configuration item includes: the table identifies the configuration sub-item and the view identifies the configuration sub-item.

According to one or more embodiments of the present disclosure, in a view permission processing method provided by the present disclosure, a group identifier configuration sub-item, a group type configuration sub-item, and a permission information configuration sub-item.

According to one or more embodiments of the present disclosure, the view permission processing method provided by the present disclosure further includes:

responding to the updating operation of the view permission, and showing a permission updating configuration item, wherein the permission updating configuration item comprises: the authority identification input item and the group list configuration item;

acquiring configuration information of a permission updating configuration item;

and sending an authority updating request to the server, wherein the authority updating request carries the configuration information of the authority updating configuration item, so that the server updates the group list corresponding to the authority identifier based on the configuration information of the authority updating configuration item.

responding to the group adding or deleting operation of the view authority, showing the group adding or deleting configuration items, wherein the group adding or deleting configuration items comprise: the authority identification input item and the group list configuration item;

acquiring configuration information of adding or deleting configuration items of the group;

and sending a group adding or deleting request to the server, wherein the group adding or deleting request carries the configuration information of the group adding or deleting configuration items, so that the server adds or deletes the group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration items.

responding to the deletion operation of the view permission, and showing a permission deletion configuration item, wherein the permission deletion configuration item comprises the following steps: an authority identification entry;

acquiring configuration information of the permission deletion configuration item;

and sending an authority deleting request to the server, wherein the authority deleting request carries the configuration information of the authority deleting configuration item, so that the server deletes the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deleting configuration item.

acquiring form data corresponding to a form identifier fed back by a server end in response to a form loading request and authority data hit by a group list, and loading the form data; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

According to one or more embodiments of the present disclosure, in a view permission processing method provided by the present disclosure, modifying a permission category of a corresponding view includes:

According to one or more embodiments of the present disclosure, in a view permission processing method provided by the present disclosure, a permission category is an open view, a locked view, or a personal view.

According to one or more embodiments of the present disclosure, the present disclosure provides a view permission processing method, applied to a server, including:

and sending the generated permission identification to the client in response to the permission creation request.

receiving an authority updating request sent by a client, wherein the authority updating request carries configuration information of an authority updating configuration item; the authority update configuration item includes: the authority identification input item and the group list configuration item;

updating the group list corresponding to the authority identification based on the configuration information of the authority updating configuration item;

and pushing the authority object and the authority information corresponding to the updated authority identifier to the client corresponding to each updated user identifier in the group list corresponding to the authority identifier.

receiving a group adding or deleting request sent by a client, wherein the group adding or deleting request carries configuration information of a group adding or deleting configuration item, and the group adding or deleting configuration item comprises: the authority identification input item and the group list configuration item;

adding or deleting the group list corresponding to the authority identification based on the configuration information of the group addition or deletion configuration item;

and pushing the authority object and the authority information corresponding to the authority identifier to the client corresponding to each user identifier in the group list added or deleted by the authority identifier.

receiving an authority deletion request sent by a client, wherein the authority deletion request carries configuration information of an authority deletion configuration item, and the authority deletion configuration item comprises: an authority identification entry;

deleting the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deletion configuration item;

and pushing the authority object and the authority information corresponding to the deleted authority identification to the client corresponding to each user identification in the group list corresponding to the authority identification.

determining a group list to which the user identifier belongs and determining authority data hit by the group list; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

and feeding back the table data corresponding to the table identification and the authority data in the group list hit to the client in response to the table loading request.

maintaining the corresponding relation among the authority identification, the authority object corresponding to the authority identification and the group list corresponding to the authority identification in advance;

and determining a group list to which the user identifier belongs and determining authority data in the hit of the group list based on the corresponding relation.

According to one or more embodiments of the present disclosure, the present disclosure provides a view permission processing apparatus, applied to a client, including:

the display unit is used for responding to the creation operation of the view permission and displaying a permission identification configuration item, and the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

and the sending unit is used for sending an authority creating request to the server, wherein the authority creating request carries the configuration information of the authority identification configuration item, so that the server generates the authority identification based on the configuration information of the authority identification configuration item.

According to one or more embodiments of the present disclosure, in a view rights processing apparatus provided by the present disclosure, a rights object configuration item includes: the table identifies the configuration sub-item and the view identifies the configuration sub-item.

According to one or more embodiments of the present disclosure, in a view authority processing apparatus provided by the present disclosure, a group list configuration item includes: the group identification configures the sub-item, the group type configures the sub-item and the authority information configures the sub-item.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the presentation unit is further configured to present a permission update configuration item in response to an update operation of the view permission, where the permission update configuration item includes: the authority identification input item and the group list configuration item;

the acquisition unit is also used for acquiring the configuration information of the permission updating configuration item;

the sending unit is further configured to send an authority updating request to the server, where the authority updating request carries configuration information of the authority updating configuration item, so that the server updates the group list corresponding to the authority identifier based on the configuration information of the authority updating configuration item.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the display unit is further configured to display a group addition or deletion configuration item in response to a group addition or deletion operation of the view permission, where the group addition or deletion configuration item includes: the authority identification input item and the group list configuration item;

the acquisition unit is also used for acquiring the configuration information of the group addition or deletion configuration items;

the sending unit is further configured to send a group adding or deleting request to the server, where the group adding or deleting request carries configuration information of the group adding or deleting configuration items, so that the server adds or deletes the group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration items.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the presentation unit is further configured to present a permission deletion configuration item in response to a deletion operation of the view permission, where the permission deletion configuration item includes: an authority identification entry;

the acquisition unit is also used for acquiring the configuration information of the permission deletion configuration item;

the sending unit is further configured to send an authority deletion request to the server, where the authority deletion request carries configuration information of the authority deletion configuration item, so that the server deletes the authority identifier and the group list corresponding to the authority identifier based on the configuration information of the authority deletion configuration item.

the sending unit is used for responding to the table loading operation and sending a table loading request to the server, wherein the table loading request carries the table identification and the user identification, so that the server determines the group list to which the user identification belongs and determines the authority data hit by the group list;

the acquisition unit is used for acquiring table data corresponding to the table identifier fed back by the server end in response to the table loading request and authority data hit by the group list, and loading the table data; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the modifying unit is specifically configured to modify a permission field in a data structure of a corresponding view, where the permission field is a field that is added in advance in the data structure of the view, and the permission field is used to describe a permission type of the view.

According to one or more embodiments of the present disclosure, in a view authority processing apparatus provided by the present disclosure, an authority category is an open view, a locked view, or a personal view.

According to one or more embodiments of the present disclosure, the present disclosure provides a view permission processing apparatus, applied to a server, including:

the receiving unit is used for receiving an authority creating request sent by a client, wherein the authority creating request carries the configuration information of the authority identification configuration item; the permission identification configuration item comprises: a rights object configuration item and a group list configuration item;

According to one or more embodiments of the present disclosure, the view permission processing apparatus further includes a response unit, configured to send the generated permission identifier to the client in response to the permission creation request.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the receiving unit is further configured to receive a permission update request sent by the client, where the permission update request carries configuration information of a permission update configuration item; the authority update configuration item includes: the authority identification input item and the group list configuration item;

the generating unit is also used for updating the group list corresponding to the authority identification based on the configuration information of the authority updating configuration item;

the pushing unit is further configured to push the rights object and the rights information corresponding to the updated rights identifier to the client corresponding to each updated user identifier in the group list corresponding to the rights identifier.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the receiving unit is further configured to receive a group addition or deletion request sent by the client, where the group addition or deletion request carries configuration information of a group addition or deletion configuration item, and the group addition or deletion configuration item includes: the authority identification input item and the group list configuration item;

the generating unit is also used for adding or deleting the group list corresponding to the authority identification based on the configuration information of the group adding or deleting configuration items;

the pushing unit is further configured to push the rights object and the rights information corresponding to the rights identifier to the client corresponding to each user identifier in the group list added or deleted by the rights identifier.

According to one or more embodiments of the present disclosure, in the view permission processing apparatus provided by the present disclosure, the receiving unit is further configured to receive a permission deletion request sent by the client, where the permission deletion request carries configuration information of a permission deletion configuration item, and the permission deletion configuration item includes: an authority identification entry;

the generating unit is also used for deleting the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deletion configuration item;

the pushing unit is further configured to push the rights object and the rights information corresponding to the deleted rights identifier to the client corresponding to each user identifier in the group list corresponding to the rights identifier.

the determining unit is used for determining a group list to which the user identifier belongs and determining authority data hit by the group list; the authority data comprises at least one authority identifier, an authority object corresponding to the authority identifier and authority information;

and the sending unit is used for responding to the table loading request and feeding back the table data corresponding to the table identification and the authority data in the group list hit to the client.

According to one or more embodiments of the present disclosure, in a view authority processing apparatus provided by the present disclosure, the apparatus further includes: the maintenance unit is used for maintaining the corresponding relation among the authority identification, the authority object corresponding to the authority identification and the group list corresponding to the authority identification in advance;

the determining unit is specifically configured to determine, based on the correspondence, a group list to which the user identifier belongs and determine authority data in which the group list hits.

In accordance with one or more embodiments of the present disclosure, there is provided an electronic device including: a processor and a memory;

According to one or more embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium storing a program or instructions for causing a computer to execute a view permission processing method provided as an embodiment of the present disclosure.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A view permission processing method is applied to a client, and comprises the following steps:

2. The method of claim 1, wherein the rights object configuration item comprises: the table identifies the configuration sub-item and the view identifies the configuration sub-item.

3. The method of claim 1, wherein the group list configuration item comprises: the group identification configures the sub-item, the group type configures the sub-item and the authority information configures the sub-item.

4. The method of claim 1, wherein the method further comprises:

acquiring the configuration information of the permission updating configuration item;

and sending an authority updating request to a server, wherein the authority updating request carries the configuration information of the authority updating configuration item, so that the server updates the group list corresponding to the authority identification based on the configuration information of the authority updating configuration item.

5. The method of claim 1, wherein the method further comprises:

responding to group adding or deleting operation of view authority, showing a group adding or deleting configuration item, wherein the group adding or deleting configuration item comprises: the authority identification input item and the group list configuration item;

acquiring configuration information of the group addition or deletion configuration items;

sending a group adding or deleting request to a server, wherein the group adding or deleting request carries the configuration information of the group adding or deleting configuration items, so that the server adds or deletes the group list corresponding to the authority identifier based on the configuration information of the group adding or deleting configuration items.

6. The method of claim 1, wherein the method further comprises:

responding to the deletion operation of the view permission, and showing a permission deletion configuration item, wherein the permission deletion configuration item comprises: an authority identification entry;

and sending an authority deleting request to a server, wherein the authority deleting request carries the configuration information of the authority deleting configuration item, so that the server deletes the authority identification and the group list corresponding to the authority identification based on the configuration information of the authority deleting configuration item.

7. A view permission processing method is applied to a client, and comprises the following steps:

8. The method of claim 7, wherein the modifying the permission category of the corresponding view comprises:

and modifying a permission field in a data structure of the corresponding view, wherein the permission field is a field which is added in advance in the data structure of the view, and the permission field is used for describing the permission type of the view.

9. The method of claim 7, wherein the permission category is a public view, a locked view, or a personal view.

10. A view permission processing method is applied to a server side and comprises the following steps:

11. The method of claim 10, wherein the method further comprises:

12. The method of claim 10, wherein the method further comprises:

receiving an authority updating request sent by a client, wherein the authority updating request carries configuration information of an authority updating configuration item; the permission update configuration item comprises: the authority identification input item and the group list configuration item;

updating a group list corresponding to the authority identification based on the configuration information of the authority updating configuration item;

13. The method of claim 10, wherein the method further comprises:

adding or deleting a group list corresponding to the authority identification based on the configuration information of the group addition or deletion configuration item;

14. The method of claim 10, wherein the method further comprises:

15. A view permission processing method is applied to a server side and comprises the following steps:

16. The method of claim 15, wherein the method further comprises:

maintaining a corresponding relation among an authority identifier, an authority object corresponding to the authority identifier and a group list corresponding to the authority identifier in advance;

and determining a group list to which the user identifier belongs and determining authority data hit by the group list based on the corresponding relation.

17. A view permission processing apparatus applied to a client, the apparatus comprising:

18. A view permission processing apparatus applied to a client, the apparatus comprising:

19. A view permission processing device is applied to a server side and comprises:

20. A view permission processing device is applied to a server side and comprises:

21. An electronic device, comprising: a processor and a memory;

the processor is configured to perform the steps of the method of any one of claims 1 to 16 by calling a program or instructions stored in the memory.

22. A non-transitory computer-readable storage medium storing a program or instructions for causing a computer to perform the steps of the method according to any one of claims 1 to 16.