Code-free authority management method based on graphical programming

Abstract

A code-free authority management method based on graphical programming is based on a graphical programming platform, the graphical programming platform is connected with a user side and a technical background through a network, the graphical programming platform integrates a user authority system and is provided with a sandbox environment, a developer carries out software development on the graphical programming platform, and the graphical programming platform is connected with the user side and the technical background through a network. The method comprises the following steps: dragging an authority component and an authority control component on a billboard workbench, drawing a graphical logic code, translating the graphical logic code, and compiling the graphical logic code into an executable program to obtain an application software system; the application software system is automatically integrated with a user permission system and runs in a sandbox; a user side enters an application software system homepage by logging in, an authority control component on the application software system homepage is an entrance of a user authority system, and the user authority system displays corresponding operation options on an operation page of the user authority system according to a user identity. The method has the advantages that the user permission can be rapidly set and changed in a graphical programming mode.

Description

Technical Field

[0001] The present invention relates to the technical field of graphical programming, and in particular to a code-free permission management method based on graphical programming. Background Art

[0002] With the development of computer technology, more and more business systems have emerged to realize various business functions and meet different business needs. In order to better serve different users and provide richer and multi-level business functions, different permissions can be configured for different users in a business system, so that users with different permissions have differences in the pages they can access, the data they can obtain, the operations they can perform, etc. Generally speaking, this permission configuration can be achieved with the help of the permission management module in the business system. However, with the increasing complexity and number of business systems, as well as the increasing requirements of the public for system security, how to more efficiently and reliably implement the permission management of business systems has become a highly concerned issue.

[0003] Traditional permission management methods usually use text codes to individually encode the permissions of each user. The setting process is cumbersome and complicated, and requires a lot of time and energy. If the verification is not careful, it is easy to make mistakes.

[0004] The flexibility of permission allocation is enhanced, thereby effectively realizing the management requirements of multi-role permissions of the system. Summary of the invention

[0005] The present invention provides a code-free permission management method based on graphical programming, which can realize the rapid setting and modification of user permissions through graphical programming.

[0006] To achieve the above object, the present invention provides a codeless permission management method based on graphical programming, which includes the following steps:

[0007] Step 1: Build a graphical programming platform, which connects the user end and the technical background through the network. The graphical programming platform integrates the user authority system and is provided with a sandbox environment. Developers log in to the graphical programming platform to develop software. They only need to drag and drop the authority component and the authority control component to the Kanban workbench, draw the graphical logic code that meets the use requirements, and then translate and compile the graphical logic code into an executable program to obtain an application software system; the application software system automatically integrates the user authority system and runs in the sandbox;

[0008] Step 2: The user sends an application system access request to the sandbox through a browser and enters the login page;

[0009] Step 3: After the login page obtains the user account and password information, it initiates a login request to the user permission system microservice to query the user data element. If the account and password match, the login is successful and the application software system homepage is entered; otherwise, the account and password information is obtained again;

[0010] Step 4: The user authority system determines the user role according to the user data primitive, and initiates an authority data request to the user authority system microservice according to the role;

[0011] Step 5: The user permission system microservice queries the user permission data, and the permission component and the permission control component determine the current user permission according to the user permission data;

[0012] Step 6: When the role is an administrator, enter the user permission system through the permission control component. The administrator selects the role in the role list and enters the permission configuration page to configure the user permission data. After the configuration is completed, it is stored in the database through the user permission system microservice;

[0013] Through the above design, the graphical programming platform provides the use rights of the corresponding permission components in the Kanban workbench according to the user permission data of the current user. When the user is an administrator, he can also enter the user permission system through the permission control component to set or change the user permission data of the subordinate role. And the setting process is a code-free permission setting. You only need to click and check the permission setting element of the corresponding permission in the corresponding permission setting unit graphical page to complete the corresponding permission setting.

[0014] Each of the permission components contains three types of permission information, including hidden, visible, and editable. The three types of permission information correspond to three types of permission setting graphics. According to the user role positioning, the permission setting of each permission component can be performed on the permission configuration page of the user, and then the corresponding user permission data is generated. Code-free permission setting operation is realized, which is simple and fast. Personalized permission settings for different user roles can be quickly realized.

[0015] The development steps of the permission component are also included, as follows:

[0016] Step A1: The technical background performs the graphic element information definition, icon construction and text code compilation operations of the permission component on the graphic element construction workbench according to the usage requirements, and obtains the graphic element information file, icon and text code of the corresponding permission component;

[0017] Step A2: importing the graphic element information file into the business database through the graphic element information import module in the graphic element import publisher, and importing the icon and text code into the text library through the text import module in the graphic element import publisher;

[0018] Step A3: The technical backend loads the permission component graphic element onto the Kanban workbench of the graphical programming platform by dragging the icon according to the usage requirements, and loads the graphic element information file and text code of the corresponding permission component into the browser cache;

[0019] Step A4: the technical backend performs a graphic element logical connection on the authority component and the authority control component according to the use requirements on the kanban workbench, generates a corresponding application software system logic program graphical code, and then passes it to the translator;

[0020] Step A5: the translator translates the graphical code of the application software system logic program into text data, and generates permission data of all permission components on the kanban workbench according to the permission declaration in the graphic element information, and passes it to the compiler;

[0021] Step A6: The user authority system is built into the compiler, and the compiler compiles the text data into machine code data and passes it to the sandbox for execution.

[0022] Through the above design, the development and operation of the permission component is realized. By declaring the permission of the permission component during the definition of the graphic element information, it is convenient to set the permission for each permission component separately later.

[0023] Preferably: in step 1, each permission component has different permission values ​​assigned, and different permission values ​​correspond to different permission levels; each user corresponds to at least one role, and each role can only have any one of the three permissions of "hide", "visible only" and "editable" for each permission component.

[0024] Through the above design, by matching different permission levels to different user roles, permission settings can be quickly implemented, and then fine-tuned according to the user's specific usage needs to complete personalized permission settings.

[0025] Preferably: the graphical programming platform is integrated with a graphic element construction workbench, the graphic element construction workbench is connected to the technical background and the graphic element import publisher, the graphic element import publisher is connected to the business database and the text library; the graphical programming platform reads the data in the business database and the text library through the browser cache module.

[0026] The graphic element construction workbench is used to construct the permission component and complete the graphic element information definition, icon production and text code editing of the permission component.

[0027] The graphic element import publisher is used to import the graphic element information into the business database, and import the icon and text code into the text library.

[0028] As a preferred embodiment: the graphical programming platform is further provided with a database and a user authority system microservice, the database is bidirectionally connected with the user authority system microservice, and the user authority system microservice is bidirectionally connected with the browser;

[0029] The database stores user authority data and user data primitives;

[0030] The user authority system microservice is used to query user data primitives or user authority data from a database and feed it back to the browser, while storing the user authority data in the database.

[0031] Preferably, the graphical programming platform is further provided with a translator and a compiler, wherein the translator obtains the graphical code of the application software system logic program of the permission component and the permission control component in the kanban workbench, and translates it into text code and passes it to the compiler; the compiler has a built-in user permission system, compiles the text code into machine code data, and sends it to the sandbox for execution.

[0032] The sandbox provides a running environment for the compiled executable file, i.e., the machine code data.

[0033] Preferably, in step 5, the permissions corresponding to the permission component and the permission control component include three permissions: "hidden", "visible only", and "editable".

[0034] Each permission component contains three types of permissions: hidden, visible, and editable. You can quickly complete the personalized settings of user permission data based on user role positioning requirements.

[0035] When the upper-level permission component is in hidden state, the lower-level pages or permission components linked to it are also in hidden state and no separate settings are required.

[0036] Preferably, in step 6, the permission configuration page includes permission setting units of the permission component, each unit includes three permission setting icons: "Hidden", "Visible Only", and "Editable", and click to check the corresponding icon to complete the permission configuration.

[0037] Through the above design, user permission settings can be completed quickly, and code-free permission settings can be realized. The permission setting page is simple and easy to understand, the operation is convenient and fast, and it is not easy to make mistakes. It can save a lot of time and energy, and completely realize code-free operation. The operator does not need to have a code knowledge background.

[0038] Preferably, in step 6, the permission control component on the homepage of the application software system is the entrance to the user permission system, and the user permission system displays corresponding operation options on the operation page of the user permission system according to the user identity.

[0039] As a preferred embodiment, a new user registration step is also included, which is as follows:

[0040] Step B1: The browser obtains the access address of the application software system, and the browser initiates an access request to the sandbox according to the access address to enter the login page of the application software system;

[0041] Step B2: The login page obtains user registration information, generates a user information graphic element according to the user registration information, and then sends it to the user authority system microservice;

[0042] Step B3: the user authority system microservice completes the new user registration according to the user information element, and grants the ordinary user identity level authority to the user information element, obtains the user data element, and then stores the user data element in the database, and returns to the login page;

[0043] Step B4: The login page obtains the user account and password information to complete the login.

[0044] Through the above design, the registration of new users can be completed quickly, and the identity level of ordinary users can meet the usage needs of most ordinary users, and can also be adjusted according to the specific needs of users later.

[0045] Preferably, the user information element corresponding to each user is unique, and the user information contained in the user information element includes but is not limited to the user's name, telephone number, ID number, age, gender, and avatar.

[0046] Each user has a unique user information element.

[0047] The beneficial effects of the present invention are as follows: through graphical programming design, code-free permission management settings are realized, the setting operation is simple and fast, clear and easy to make mistakes, and a lot of time and energy costs can be saved. At the same time, the present invention can be widely used in the permission management settings of various graphical systems and platforms, and has strong practicality. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 It is a structural block diagram of the present invention;

[0049] Figure 2 It is a schematic diagram of the process of the present invention;

[0050] Figure 3 Schematic diagram of the development process of the permission component in the embodiment. DETAILED DESCRIPTION

[0051] The present invention is further described in detail below in conjunction with the accompanying drawings and specific examples. The following examples or drawings are used to illustrate the present invention, but are not used to limit the scope of the present invention.

[0052] like Figure 1 As shown: a codeless permission management method based on graphical programming, based on a graphical programming platform, and a user end and a technical background connected to the graphical programming platform through a network, the graphical programming platform integrates a user permission system, and is provided with a sandbox environment, developers log in to the graphical programming platform to develop software, and only need to drag and drop permission components and permission control components onto a kanban workbench, draw graphical logic codes that meet the use requirements, and then translate and compile the graphical logic codes into executable programs to obtain an application software system; the application software system automatically integrates a user permission system and runs in a sandbox;

[0053] The user terminal enters the application software system homepage by logging in. The authority control component on the application software system homepage is the entrance to the user authority system. The user authority system displays corresponding operation options on the operation page of the user authority system according to the user identity.

[0054] Each of the permission components has different permission values, and different permission values ​​correspond to different permission levels; each user corresponds to at least one role, and each role can only have any one of the three permissions of "hide", "visible only" and "editable" for each permission component.

[0055] The graphical programming platform is integrated with a graphic element construction workbench, which is connected to the technical background and the graphic element import publisher, and the graphic element import publisher is connected to the business database and the text library; the graphical programming platform reads data in the business database and the text library through the browser cache module.

[0056] The graphical programming platform is also provided with a database and a user authority system microservice, the database is bidirectionally connected to the user authority system microservice, and the user authority system microservice is bidirectionally connected to the browser;

[0057] The database stores user authority data and user data primitives;

[0058] The user authority system microservice is used to query user data primitives or user authority data from a database and feed it back to the browser, while storing the user authority data in the database.

[0059] The graphical programming platform is also provided with a translator and a compiler. The translator obtains the graphical code of the application software system logic program of the permission component and the permission control component in the Kanban workbench, and translates it into text code and passes it to the compiler; the compiler has a built-in user permission system, compiles the text code into machine code data, and sends it to the sandbox for execution.

[0060] like Figure 2 As shown: A codeless permission management method based on graphical programming, comprising the following steps:

[0061] Step 1: Building a graphical programming platform, wherein the graphical programming platform is connected to a user terminal and a technical backend via a network;

[0062] Step 2: The user sends an application system access request to the sandbox through a browser and enters the login page;

[0063] Step 3: After the login page obtains the user account and password information, it initiates a login request to the user permission system microservice to query the user data element. If the account and password match, the login is successful and the application software system homepage is entered; otherwise, the account and password information is obtained again;

[0064] Step 4: The user authority system determines the user role according to the user data primitive, and initiates an authority data request to the user authority system microservice according to the role;

[0065] Step 5: The user permission system microservice queries the user permission data, and the permission component and the permission control component determine the current user permission according to the user permission data;

[0066] Step 6: When the role is an administrator, enter the user permission system through the permission control component. The administrator selects the role in the role list and enters the permission configuration page to configure the user permission data. After the configuration is completed, it is stored in the database through the user permission system microservice.

[0067] like Figure 3 As shown: It also includes the development steps of the permission component, which are as follows:

[0068] Step A1: The technical background performs the graphic element information definition, icon construction and text code compilation operations of the permission component on the graphic element construction workbench according to the usage requirements, and obtains the graphic element information file, icon and text code of the corresponding permission component;

[0069] Step A2: importing the graphic element information file into the business database through the graphic element information import module in the graphic element import publisher, and importing the icon and text code into the text library through the text import module in the graphic element import publisher;

[0070] Step A3: The technical backend loads the permission component graphic element onto the Kanban workbench of the graphical programming platform by dragging the icon according to the usage requirements, and loads the graphic element information file and text code of the corresponding permission component into the browser cache;

[0071] Step A4: the technical backend performs a graphic element logical connection on the authority component and the authority control component according to the use requirements on the kanban workbench, generates a corresponding application software system logic program graphical code, and then passes it to the translator;

[0072] Step A5: the translator translates the graphical code of the application software system logic program into text data, and generates permission data of all permission components on the kanban workbench according to the permission declaration in the graphic element information, and passes it to the compiler;

[0073] Step A6: The user authority system is built into the compiler, and the compiler compiles the text data into machine code data and passes it to the sandbox for execution.

[0074] In step 5, the permissions corresponding to the permission component and the permission control component include three permissions: "hidden", "visible only", and "editable".

[0075] In step 6, the permission configuration page includes permission setting units of the permission component. Each unit includes three permission setting icons: "Hide", "Visible Only", and "Editable". Click and check the corresponding icon to complete the permission configuration.

[0076] It also includes new user registration steps, as follows:

[0077] Step B1: The browser obtains the access address of the application software system, and the browser initiates an access request to the sandbox according to the access address to enter the login page of the application software system;

[0078] Step B2: The login page obtains user registration information, generates a user information graphic element according to the user registration information, and then sends it to the user authority system microservice;

[0079] Step B3: the user authority system microservice completes the new user registration according to the user information element, and grants the ordinary user identity level authority to the user information element, obtains the user data element, and then stores the user data element in the database, and returns to the login page;

[0080] Step B4: The login page obtains the user account and password information to complete the login.

[0081] The user information element corresponding to each user is unique, and the user information contained in the user information element includes but is not limited to the user's name, telephone number, ID number, age, gender, and avatar.

[0082] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A codeless permission management method based on graphical programming, characterized in that: The following steps are involved: Step 1: Build a graphical programming platform, which connects the user end and the technical background through the network. The graphical programming platform integrates the user authority system and is provided with a sandbox environment. Developers log in to the graphical programming platform to develop software. They only need to drag and drop the authority component and the authority control component to the Kanban workbench, draw the graphical logic code that meets the use requirements, and then translate and compile the graphical logic code into an executable program to obtain an application software system; the application software system automatically integrates the user authority system and runs in the sandbox; Step 2: The user sends an application system access request to the sandbox through a browser and enters the login page; Step 3: After the login page obtains the user account and password information, it initiates a login request to the user permission system microservice to query the user data element. If the account and password match, the login is successful and the application software system homepage is entered; Otherwise, re-obtain the account and password information; Step 4: The user authority system determines the user role according to the user data primitive, and initiates an authority data request to the user authority system microservice according to the role; Step 5: The user permission system microservice queries the user permission data, and the permission component and the permission control component determine the current user permission according to the user permission data; Step 6: When the role is an administrator, enter the user permission system through the permission control component. The administrator selects the role in the role list and enters the permission configuration page to configure the user permission data. After the configuration is completed, it is stored in the database through the user permission system microservice; The development steps of the permission component are also included, as follows: Step A1: The technical background performs the graphic element information definition, icon construction and text code compilation operations of the permission component on the graphic element construction workbench according to the usage requirements, and obtains the graphic element information file, icon and text code of the corresponding permission component; Step A2: importing the graphic element information file into the business database through the graphic element information import module in the graphic element import publisher, and importing the icon and text code into the text library through the text import module in the graphic element import publisher; Step A3: The technical backend loads the permission component graphic element onto the Kanban workbench of the graphical programming platform by dragging the icon according to the usage requirements, and loads the graphic element information file and text code of the corresponding permission component into the browser cache; Step A4: the technical backend performs a graphic element logical connection on the authority component and the authority control component according to the use requirements on the kanban workbench, generates a corresponding application software system logic program graphical code, and then passes it to the translator; Step A5: the translator translates the graphical code of the application software system logic program into text data, and generates permission data of all permission components on the kanban workbench according to the permission declaration in the graphic element information, and passes it to the compiler; Step A6: The user authority system is built into the compiler, and the compiler compiles the text data into machine code data and passes it to the sandbox for execution.

2. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: In step 1, each permission component has different permission values, and different permission values ​​correspond to different permission levels; each user corresponds to at least one role, and each role can only have any one of the three permissions of "hide", "visible only" and "editable" for each permission component.

3. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: The graphical programming platform is integrated with a graphic element construction workbench, which is connected to the technical background and the graphic element import publisher, and the graphic element import publisher is connected to the business database and the text library; the graphical programming platform reads data in the business database and the text library through the browser cache module.

4. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: The graphical programming platform is also provided with a database and a user authority system microservice, the database is bidirectionally connected to the user authority system microservice, and the user authority system microservice is bidirectionally connected to the browser; The database stores user authority data and user data primitives; The user authority system microservice is used to query user data primitives or user authority data from a database and feed it back to the browser, while storing the user authority data in the database.

5. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: The graphical programming platform is also provided with a translator and a compiler. The translator obtains the graphical code of the application software system logic program of the permission component and the permission control component in the Kanban workbench, and translates it into text code and passes it to the compiler; the compiler has a built-in user permission system, compiles the text code into machine code data, and sends it to the sandbox for execution.

6. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: In step 5, the permissions corresponding to the permission component and the permission control component include three permissions: "hidden", "visible only", and "editable".

7. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: In step 6, the permission configuration page includes permission setting units of the permission component. Each unit includes three permission setting icons: "Hidden", "Visible Only", and "Editable". Click and check the corresponding icon to complete the permission configuration.

8. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: In step 6, the permission control component on the homepage of the application software system is the entrance to the user permission system, and the user permission system displays corresponding operation options on the operation page of the user permission system according to the user identity.

9. The codeless permission management method based on graphical programming according to claim 1 is characterized in that: It also includes new user registration steps, as follows: Step B1: The browser obtains the access address of the application software system, and the browser initiates an access request to the sandbox according to the access address to enter the login page of the application software system; Step B2: The login page obtains user registration information, generates a user information graphic element according to the user registration information, and then sends it to the user authority system microservice; Step B3: the user authority system microservice completes the new user registration according to the user information element, and grants the ordinary user identity level authority to the user information element, obtains the user data element, and then stores the user data element in the database, and returns to the login page; Step B4: The login page obtains the user account and password information to complete the login.

10. The codeless permission management method based on graphical programming according to claim 9 is characterized in that: The user information element corresponding to each user is unique, and the user information contained in the user information element includes but is not limited to the user's name, telephone number, ID number, age, gender, and avatar.

Images