CN114564197A

CN114564197A - Method for distinguishing field authority according to service scene and computer readable storage medium

Info

Publication number: CN114564197A
Application number: CN202210185036.6A
Authority: CN
Inventors: 朱中; 罗义; 甘燎源
Original assignee: Chongqing Yunfeng Technology Co ltd
Current assignee: Chongqing Yunfeng Technology Co ltd
Priority date: 2022-02-28
Filing date: 2022-02-28
Publication date: 2022-05-31

Abstract

The invention relates to a method for distinguishing field authorities according to service scenes, which comprises the following steps: creating a field set of forms of a management system; enumerating a service scene of data application of a form in a management system; respectively setting field permissions of all fields of the form in each service scene; rendering the field authority according to the selected service scene; and when the data of the parameter variables of the function formula change, calculating the function formula again, and dynamically modifying the authority of the corresponding field according to the calculation result. By adopting the method for distinguishing the field authority, a set of universal form system can be established to configure the field authority of the form, so that the service function of the system can be rapidly configured through the form system according to the personalized requirements of enterprises on service scenes, and the refined and personalized authority management can be realized through a function formula, thereby greatly reducing the capital cost and the time cost.

Description

Method for distinguishing field authority according to service scene and computer readable storage medium

Technical Field

The invention belongs to the technical field of industrial internet, and relates to a method for distinguishing field authorities according to service scenes and a computer-readable storage medium.

Background

Along with the development of an industrial internet management platform, more and more enterprises realize cloud service of a production line, and all-round unified management of enterprise factories including production management, material management, storage management, equipment management and the like can be realized through the cloud service. Since the industrial internet management platform serves various industries, and the specific business of each industry is different, if a code is developed separately for each business of each enterprise, it is obviously impractical for the platform service party serving thousands of enterprises or even thousands of enterprises. For this reason, most platform servers are currently dedicated to implement business management through low code or zero code, so as to reduce the development cost of the platform. For example, CN113094037A discloses a form and workflow interaction method, which can automatically acquire data collected by a form from a form engine according to actual situations by using a workflow engine without requiring a developer to write codes to acquire the data, so that the interaction between the form and the workflow can be realized in zero codes.

A field is a basic component of a form, which typically has multiple fields, and different fields can be used to carry different data (which can be defined by type as text, lines of text, numbers, pictures, files, map addresses, people, departments, forms, drop-down boxes, time of day, handwritten signatures, associated form data, etc.). In the prior art, each service function needs to define a set of data pages (add, edit, list, import, export details) separately, the authority of each field is defined on the page, after a form is used, the authority of different scenes is not distinguished, and the authority of the form field is consistent in all the scenes, for example: the field authority cannot be distinguished in addition and edition, and the field authority needs to be customized on the page according to the form.

In a traditional customized development program, each function needs to develop a set of pages independently and determine fields supported by each use scene, if a new field is added or the authority is modified, the program needs to be developed and adjusted, and the development cost and the time cost are brought, so that the efficiency is very low. In addition, different enterprises generally need different systems due to different requirements of different enterprises, and if each enterprise individually customizes and develops a set of individual management systems, huge cost is required and time is consumed.

Disclosure of Invention

In view of the above, the present invention provides a method and a computer-readable storage medium for distinguishing field rights according to a service scenario.

In order to achieve the purpose, the invention provides the following technical scheme:

a method for distinguishing field authority according to service scene includes the following steps:

s100, creating a field set of a form of a management system;

s200, enumerating a service scene of the data application of the form in the management system;

s300, respectively setting field permissions of all fields of the form in each service scene; the setting mode comprises directly appointing field authority and calculating the field authority through a function formula;

s400, rendering the field authority according to the selected service scene;

s500, analyzing the set function formula of the field authority, calculating the function formula again when the data of the parameter variable of the function formula changes, dynamically modifying the authority of the corresponding field according to the calculation result, and returning to execute the step S400.

Further, the step S100 specifically includes the following sub-steps:

s110, establishing a form field, wherein the form field is used for providing a creation template of fields with various attributes;

s120, creating a form engine, wherein the form engine is used for creating fields in the form and realizing the collection, deletion, modification and viewing of data in the form;

s130, creating each field of the form of the management system one by one through the form engine and the form field to form a field set of the form.

Further, creating fields of the form through the form engine and the form field includes the steps of:

s131, selecting field attributes to be created in the form field;

s132, adding a blank field of the attribute in the form by the form engine;

and S133, editing each parameter of the blank field according to requirements to obtain the required field.

Further, the service scenario includes: newly adding and editing; the field authority of the service scenario includes: "read only", "hidden", and "must fill"; wherein the content of the first and second substances,

the 'read-only' permission is that the field can not be manually modified under the page of the corresponding service scene;

the 'hidden' permission is that the field is not displayed under the page of the corresponding service scene;

the "must fill" right is that a field must be filled with data at the time of commit, otherwise it cannot be committed.

Further, the service scenario further includes listing, viewing, exporting and printing, and the field authority when the service scenario is a listing includes "retrieving" and "listing hiding"; the field authority of the service scene during viewing comprises 'hiding'; the field authority of the business scene during export comprises 'list hiding'; the service scene is that the field authority during printing comprises 'hidden';

the 'retrieval' authority is to provide a retrieval function for the field under the list page, and the data of the field can be used as an index for retrieval;

the "list hide" permission is that the field is not displayed on the list page.

Further, the service scenario also includes import, and the field authority of the service scenario when the service scenario is imported includes "hide" and "keep original value";

the 'original value preserving' authority is used for editing the existing data of the form by importing data by a user, the 'original value preserving' field does not allow the field to be modified by the imported data, and the data of the field before the importing operation is preserved.

Further, when the field authority is directly specified, whether the field authority is opened or not is directly specified during setting; when the field authority is calculated through the function formula, the calculation result of the function formula comprises "true" and "false", the field authority is opened when the calculation result of the function formula is "true", and the field authority is closed when the calculation result of the function formula is "false".

Further, in the step S100, when creating a field set of a form of the management system, default permissions of each field are also set; the setting mode of the field permission of the field of the setting form in each service scene comprises default setting, and the default setting is used for taking the default permission of each field as the permission of the field in the corresponding service scene.

Further, the step S400 specifically includes the following sub-steps:

s410, calling a corresponding interface of a server according to a service scene when a user enters a management system;

s420, the service end returns the field authority of the service scene; if the field authority is calculated through the function formula, the field authority is obtained according to the calculation result of the function formula, and then the field authority is returned;

s430, rendering and loading the field of the current business scene, and displaying the rendered effect on the display page of the current business scene;

s440, enumerating all the service scenes, and respectively rendering the display modes of all the fields in each service scene.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a method of distinguishing field rights according to a traffic scenario as set forth above.

In the invention, the permission control of the fields in the specific service scene is realized by creating the field set of the form and the enumerated data service scene and respectively setting the field permission of all the fields in each service scene; based on the authority control method, a set of universal form system can be established to configure the field authority of the form in the management system of the enterprise user, so that the form system can be configured according to the personalized requirements of the enterprise on the service scene of data application, a set of service functions can be rapidly configured, the refined and personalized authority management can be realized through a function formula according to the different authority requirements of the data in different service scenes, and the method is far superior to a customized system function development mode in the aspects of capital cost and time cost.

Drawings

For the purposes of promoting a better understanding of the objects, aspects and advantages of the invention, reference will now be made to the following detailed description taken in conjunction with the accompanying drawings in which:

fig. 1 is a flowchart of a method for distinguishing field rights according to a service scenario according to a preferred embodiment of the present invention.

FIG. 2 is a diagram illustrating a create form page in one embodiment.

FIG. 3 is a diagram of a list page in one embodiment.

Fig. 4 is a schematic diagram of a field permission setting page of an editing scenario in a specific example.

Fig. 5 is a schematic diagram of a field permission setting page of an import scene in a specific example.

Fig. 6 is a diagram illustrating a function formula setting page of field rights in a specific example.

FIG. 7 is a diagram illustrating the effect of an edit page rendered in one embodiment.

Detailed Description

The embodiments of the invention are explained below by means of specific examples, the illustrations provided in the following examples are merely illustrative of the basic idea of the invention, and features in the following examples and examples can be combined with one another without conflict.

In the invention, the permission control of the fields in the specific service scene is realized by creating the field set of the form and the enumerated data service scene and respectively setting the field permission of all the fields in each service scene; based on the authority control method, a set of universal form system can be established to configure the field authority of the management system form of the enterprise user, so that a set of management system meeting the personalized requirements of enterprises on the service scene of data application can be rapidly configured, and refined and personalized field authority management can be realized through a function formula.

As shown in fig. 1, a preferred embodiment of the method for distinguishing field rights according to a service scenario of the present invention comprises the following steps:

s100, creating a field set of the form of the management system. The fields and sets are defined as follows:

field: a field is a basic component element of a form, and a form has a plurality of fields, such as: the input box of the name, sex, age, etc. of the user information page for the user to enter data on the mobile phone or the computer is called a field. Different fields may have different attributes, and fields of different attributes may be used to carry data of different attributes. The attributes of the fields can include text, multiple lines of text, numbers, pictures, files, map addresses, personnel, departments, forms, drop-down boxes, dates and times, handwritten signatures, associated attributes and the like, and the fields with different attributes respectively bear corresponding data. For example: fields of numeric attributes are used to store numbers, fields of drop-down box attributes are used to store the structure of a drop-down menu, fields of form attributes are used to store a form (i.e., a sub-form) in a form as fields, and so on.

And (3) gathering: is a set in mathematical meaning, and can store numbers, texts, computer objects and the like in the field of computers, and is represented by symbols [ ]'.

The step may specifically include the following substeps:

s110, establishing a form field, wherein the form field is used for providing a creation template of form fields with various attributes.

As shown in FIG. 2, to create a page of the "book information" form, the form field consists of the "base field" area, "advanced field" area, "enterprise field" area on the left side of FIG. 2.

And S120, creating a form engine, wherein the form engine is used for creating fields in the form and realizing the collection, deletion, modification and viewing of data in the form. The form engine may be created without repeated development and different management systems may be common.

S130, creating each field of the form of the management system one by one through the form engine and the form field to form a field set of the form. As shown in fig. 2, the "form field" area in the middle is used to show fields that have been created, in which five fields of book number (ISBN), book name, pricing, borrowing status, and estimated borrowable time have been created. Creating fields of a form through a form engine and form fields includes the steps of:

s131, selecting the field attribute to be created in the form field. For example, if a field of a text attribute needs to be added in a form, the field of the text attribute is clicked in the form field.

S132, adding a blank field of the attribute in the form by the form engine. For example, after clicking a field of a text attribute in a form field, a blank text field is added to the form, the name of the field is text, and other parameters are all null.

And S133, editing each parameter of the blank field according to requirements to obtain the required field. As shown in fig. 2, the right area is a parameter setting area of the blank field, the parameters of the blank field generally include a name, a number, guidance information, default permissions (field control options in the figure), default values, and the like, and there may be specific parameters for fields with different attributes. For example: for the fields of the attributes of the drop-down box, the parameters of the drop-down box also comprise options of the drop-down box; for fields associated with attributes, its parameters also include associated forms, associated fields, and the like.

An example of a field set after creation of a book information form for a book management system is completed as follows:

[

book Number (ISBN)

Name of book

Pricing

Borrowing state

Predicted borrowable time

The current borrower

Status of state

Source

Purchasing links

Applicant

Borrow the book

Procurement status

]

Of course, more fields may be added to the field set as desired.

S200, enumerating the service scene of the data application of the form in the management system. The service scenario is a presentation and use scenario of data, and generally includes a list, an addition, and an edition. The list is data in a form displayed on a page of the management system in a list mode; as shown in FIG. 3, a diagram of a list page of the book management system is shown. The field authority when the service scene is a list includes "retrieve" and "list hide".

The 'retrieval' authority is to provide a retrieval function for the field under the list page, so that the data of the field can be used as an index for retrieval, and the required data can be conveniently retrieved under the list page. For example, the authority of the book name field of the book information form in the business scene of the list can be set as "retrieve", so that the user can search the book name to find the book to be borrowed under the page of the list.

The "list hide" permission is that the field is not displayed on the list page. The list page does not necessarily need to show all the data, so the authority of fields which are not concerned by the user (i.e. fields which are not required to be shown on the list page) in the business scene of the list can be set as 'list hiding', so that the list page only shows the necessary data for being convenient to view. For example: the authority of the fields of the book information form, such as the borrowing state, pricing, purchasing state and the like, in the business scene of the list can be set as 'list hiding'.

Newly adding a new data in a form of the management system; editing to modify the existing data in the form of the management system; when the service scene is newly added or edited, the field authority comprises: "read only", "hidden", and "must fill". As shown in fig. 4, a page is set for the field authority of the editing scene of the "book information" form (since the page can only display 10 fields, two fields of borrowing and purchasing status are not shown in fig. 4, and can be displayed by dragging the progress bar on the right side in actual operation).

The "read-only" right is that the field cannot be modified manually under the page of the corresponding service scene, and the value of the field can only be modified in the modes of system cascade, filling and the like. For example, when a book in the book management system is in a borrowing state, when the data of the book is edited, the "current borrower" field of the book automatically fills the field with the name of the borrower stored in the system, and the data of the field is not allowed to be manually modified.

The 'hidden' permission is that the field is not displayed under the page of the corresponding service scene so as to avoid displaying the field irrelevant to the service scene; the "hidden" permissions are typically used for data preservation of page form calculation formulas and traffic flows.

The 'must fill' authority is that data must be filled in the field when the field is submitted, otherwise, the field is prompted to have the must fill field not filled, and the field cannot be submitted.

For example, when a system administrator enters a new book, the number, name, pricing, etc. of the book need to be filled in, so the authority of the field of the "book information" form in the new service scene is set as "must be filled in", and some data are input after the purchase is completed, so the entry is not needed in the new service scene, for example: the authority of the fields of the book information form, such as the borrowing state, the predicted borrowing time, the current borrower, the purchasing state and the like, under the newly added service scene can be set to be hidden, so that the fields cannot be displayed during the newly added process. A system administrator needs to perfect book information after purchasing is finished, so that information such as book numbers, names, pricing, borrowing states, predicted borrowable time, purchasing states, sources, purchasing links and the like needs to be perfected during editing, and the authority of the fields in an edited service scene can be set to be 'must fill in'; since no information is yet borrowed, the current permissions of the borrower, status, applicant, etc. fields under the edited business scenario may be set to "hidden".

When the fields of the form include form fields, the field permissions of the form fields may further include: add "table row", "delete table row", and "existing data table data not editable".

The "add table row" authority is to allow the user to add a new row of data when adding table data to the table field.

The "delete table row" permission is to allow the user to delete existing data of the table when editing the data of the table field.

The 'non-editable existing data table data' right is to set a row of data of the table field to be in a non-editable state (namely, not modified and not deleted).

Of course, the business scenario also includes import, view, export, and print. The import is to import data in batches through the existing data table files in formats such as excel and the like; the field authority when the service scene is import includes 'hidden' and 'original value reserved'. As shown in FIG. 5, a page is set for the field permissions of the import scenario of the "book information" form. As can be seen from fig. 5, all fields do not have "hidden" rights and "original value retention" rights opened in the import scene, nor have field rights calculated by a function formula set.

The 'original value preservation' right is that when a user edits the existing data of the form through the excel imported data, the field of the 'original value preservation' does not allow the field to be modified through the imported data, and the data of the field before the import operation is preserved.

For example, when importing data, it is certainly not desirable to modify the data of the borrower and the predicted borrowable time, so the authority of the above fields at the time of importing can be set as "hidden" and importing cannot be performed; of course, the authority of the field may also be set to "keep original value", so that the data of the field in the imported data may be viewed, but the existing data of the field in the system may not be modified.

The viewing is to generate detailed information of a certain piece of data under a new page viewing list page, and the field authority during viewing comprises 'hiding' in a service scene. The export scene is used for exporting the table data of the list page, the field authority of the export scene is 'list hiding', and the 'list hiding' authority of the field under the export scene is the same as the 'list hiding' authority of the field under the list scene, so that the field authority of the export scene does not need to be set, and the field authority of the export scene can be directly generated according to the field authority of the list scene. The printing scene is used for printing the data of the form, the field authority of the printing service scene comprises 'hiding', and the field with the field authority of 'hiding' cannot be printed under the printing service scene.

S300, respectively setting field permissions of all fields of the form in each service scene; the setting mode comprises directly specifying field authority and calculating the field authority through a function formula. When directly appointing the field authority, whether the field authority is opened or not is directly appointed during setting. When the field authority is calculated through the function formula, the calculation result of the function formula comprises "true" and "false", the field authority is opened when the calculation result of the function formula is "true", and the field authority is closed when the calculation result of the function formula is "false". Therefore, the authority of the field can be associated with the data of other fields, the field authority setting mode is more flexible, and a user can flexibly configure the field authority in a universal mode through a function formula without respectively appointing the authority of the field under different conditions.

As shown in fig. 4 and 5, the method for setting the field authority is preferably: respectively generating an authority setting table corresponding to each scene, taking the field name as a row title and taking the authority name as a column title, enabling each cell to respectively represent an authority of the field, setting a state setting icon and a function formula setting icon in each cell, and directly setting the field authority through the state icon or setting a function formula for calculating the field authority through the function formula icon. The state setting icon may be a state box, and the function formula setting icon may be a function formula box; in a default state, the color in the state box is displayed as light color without marks; after the state box is clicked, the color in the state box is displayed as dark color, and a mark "√" is displayed to indicate that the field authority is opened; clicking the status box again changes the color in the status box from dark to light, and the mark "√" disappears, indicating that the field permission is not opened. Clicking the function formula box to generate a function setting page, and selecting a function and a parameter variable of the function to form a function formula; as shown in fig. 6, the service scenario is an example of a function formula setting page of the book name field authority when editing, where: the elementary () is a function defined in advance in a function library and used for judging whether the field content is empty, the meaning of a function formula in the figure is that whether the content of the current borrower field is empty is judged firstly, if so, the value of true is returned, and if not, the value of false is returned; therefore, the 'read only' permission of the book name field in the editing scene is associated with the content of the current borrower field, so that the permission of the book name field is 'read only' after the book is borrowed, the book name is not allowed to be modified, but the book name of the data obtained from the system is automatically filled in the book name field. When a function formula is set, displaying a mark "fx" in the function formula frame to indicate that the function formula is set, wherein the color in the function formula frame is light color in a default state; if the function formula box is clicked, the color in the function formula box is displayed as dark color, and the setting method for expressing the field authority is to calculate the field authority according to the set function formula; if the function formula box is clicked again, the color in the function formula box is changed from dark color to light color, and the setting mode of the field authority is directly appointed; at this time, the function formula is invalid and is not calculated. As can be seen from fig. 4, in the editing scene, the "fill-necessary" authority and the "read-only" authority of the three fields of the book name, the borrowing state and the preset borrowable time are determined by the calculation result of the function formula, and the field authorities of the other fields are directly specified.

When the field set of the form of the management system is created, the default authority of each field is also set; therefore, the setting mode of the field permission of the field of the setting form in each service scene can also comprise default setting, and when the setting mode of the field permission of a certain service scene selects the default setting, the default permission of each field is directly used as the permission of the field in the service scene, so that single setting is not needed.

S400, rendering field authority of the service scene; when entering a certain service scenario, a corresponding page is generated according to the field authority specified in step S300. For example, for a field of "hidden" permissions, no display is made when the page is generated, a field of "must fill" permissions is prompted by a "+" sign and made available for filling, and a check is made at commit to see if the field is empty, etc. The step may specifically include the following substeps:

and S410, calling a corresponding interface of the server according to the service scene when the user enters the management system. For example, the service scenario that is entered first when entering the system is generally a list, and therefore, when the user enters the system, the list interface of the server is called.

And S420, the server returns the header data and the field authority displayed by the service scene. If the field authority is directly specified in the step S300, directly returning the authority specified by the field; if the field authority is not directly specified in the step S300, but the field authority is calculated by using the function formula, the field authority is obtained according to the calculation result of the function formula, and then the field authority calculated according to the function formula is returned. For example, when the function formula of the field authority of the book name field in the edited service scene is set as shown in fig. 6, it is detected whether the current borrower field of the data in the form is empty, and then it is determined whether the "read only" authority of the book name field is turned on according to whether the borrower field has data.

S430, rendering and loading the field of the current business scene, and displaying the rendered effect on the display page of the current business scene.

S440, enumerating all the service scenes, and respectively rendering the display modes of all the fields in each service scene; and then, the rendered effect can be directly displayed after the service scene is changed.

For example, after setting the field authority of the editing scene according to fig. 4, assuming that the returned calculation result of the function formula of the three fields "must fill" authority of the book name, the borrowing state and the preset borrowable time is "false", and the returned calculation result of the function formula of the "read only" authority is "true", the rendered effect schematic diagram of the editing page is shown in fig. 7.

S500, analyzing the set function formula of the field authority, calculating the function formula again when page loading or data of parameter variables of the function formula change, dynamically modifying the authority of the corresponding field according to the calculation result, and returning to execute the step S400. Therefore, the authorities of form fields, such as filling, reading only, hiding and the like, can be dynamically modified through the function formula, and the aim of dynamically controlling the field authorities according to the requirements of users is fulfilled.

In the embodiment, the authority control of the fields in the specific service scene is realized by respectively setting the field authority of all the fields in the form field set in each service scene; based on the authority control method, a set of universal form system can be established to configure and manage the field authority of the system form, so that the form system can be configured according to the personalized requirements of enterprises on the service scenes of data application, a set of service functions can be rapidly configured, the refined and personalized authority management can be realized through a function formula according to the different authority requirements of data in different service scenes, and the capital cost and the time cost are far less than those of a customized system function development mode.

The present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a computer, the computer program performs some or all of the actual operations of the method for distinguishing field permissions according to service scenarios, so as to implement the functions of any one of the above embodiments.

Finally, the above embodiments are only intended to illustrate the technical solutions of the present invention and not to limit the present invention, and although the present invention has been described in detail with reference to the preferred embodiments, it will be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions, and all of them should be covered by the claims of the present invention.

Claims

1. A method for distinguishing field permissions according to service scenarios, comprising the steps of:

s100, creating a field set of a form of a management system;

s400, rendering the field authority according to the selected service scene;

2. The method according to claim 1, wherein the step S100 specifically comprises the following sub-steps:

3. The method of claim 2, wherein the creating of the form fields through the form engine and the form field comprises the following steps:

s131, selecting field attributes to be created in the form field;

s132, adding a blank field of the attribute in the form by the form engine;

4. The method of claim 1, wherein the service scenario comprises: newly adding and editing; the field authority of the service scenario includes: "read only", "hidden", and "must fill"; wherein the content of the first and second substances,

the 'must fill' right is that a field must be filled with data at the time of submission, otherwise it cannot be submitted.

5. The method of claim 4, wherein the service scenario further comprises listing, viewing, exporting and printing, and the field permissions when the service scenario is a listing comprise "retrieve" and "list hide"; the field authority of the service scene during viewing comprises 'hiding'; the field authority of the business scene during export comprises 'list hiding'; the service scene is that the field authority during printing comprises 'hidden';

the 'retrieval' authority is to provide a retrieval function for the field under the list page and can take the data of the field as an index for retrieval;

the "list hide" permission is that the field is not displayed on the list page.

6. The method of claim 4, wherein the service scenario further comprises import, and the field permission of the service scenario when being imported comprises "hide" and "keep original value";

7. The method for distinguishing field permissions according to service scenario of claim 1, wherein when directly specifying field permissions, directly specifying whether field permissions are on or not at setup; when the field authority is calculated through the function formula, the calculation result of the function formula comprises "true" and "false", the field authority is opened when the calculation result of the function formula is "true", and the field authority is closed when the calculation result of the function formula is "false".

8. The method for distinguishing the field authority according to the service scenario as claimed in claim 1, wherein in the step S100, when creating the field set of the form of the management system, a default authority for each field is further set; the setting mode of the field permission of the field of the setting form in each service scene comprises default setting, and the default setting is used for taking the default permission of each field as the permission of the field in the corresponding service scene.

9. The method according to claim 1, wherein the step S400 specifically comprises the following sub-steps:

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of distinguishing field rights according to a traffic scenario, as claimed in any one of claims 1 to 9.