Method and device for processing and displaying components in form page and storage medium

Abstract

The embodiment of the invention provides a processing and displaying method and device for components in a form page and a storage medium. In the embodiment of the invention, in the process of generating a form page by a low-code development platform, a page description file corresponding to a target form page is generated, the page description file is analyzed into a component tree, component-level permission configuration is carried out through nodes on the component tree, at least one kind of permission information is obtained, and the permission information is displayed on the low-code development platform. Each type of permission information corresponds to one or more components, and corresponding target execution role information is configured for at least one type of permission information, so that component level configuration on the low-code platform is completed. Wherein component level configuration is performed through the component tree, so that a user of the low-code development platform can quickly, efficiently and concisely set, manage and control the components on the form page, and the use cost of the user is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device and storage medium for processing and displaying components in a form page. Background Art

[0002] The existing traditional development platform requires developers to manually write code according to needs, which has the problem of long development time and high programming ability requirements for technicians. So the low-code development platform (LCDP) emerged. A low-code development platform is a development platform that can quickly generate applications without coding (zero code) or with a small amount of code. On the one hand, the low-code development platform has low requirements on the programming ability of developers, and on the other hand, it can shorten the development time. Therefore, it is widely used, especially in the development of form pages. However, in the process of developing form pages on the low-code development platform, it faces the technical difficulty of how to perform configuration management from the component dimension. Summary of the invention

[0003] Multiple aspects of the present application provide a method, device and storage medium for processing and displaying components in a form page, so as to implement component-level configuration management on a low-code development platform.

[0004] An embodiment of the present application provides a method for processing components in a form page, including: in response to an editing operation on multiple components on a form design page of a low-code development platform, generating a page description file corresponding to a target form page according to the description information and hierarchical relationship of the multiple components, the target form page including multiple components; in response to a parsing operation on the target form page, parsing the page description file into a component tree, multiple nodes on the component tree corresponding to multiple components, and the parent-child relationship between the multiple nodes representing the hierarchical relationship between the multiple components; in response to a permission configuration operation initiated on at least some of the nodes on the component tree, generating at least one permission information for at least some of the components corresponding to at least some of the nodes, and components corresponding to different permission information are not exactly the same; and in response to an execution role configuration operation initiated on at least one permission information, respectively configuring corresponding target execution role information for at least one permission information, each permission information corresponding to one or more target execution role information, so as to complete the configuration of multiple components.

[0005] An embodiment of the present application also provides a form page display method, comprising: in response to a display request for a target form page, obtaining a page description file of the target form page, at least one permission information corresponding to at least some components contained in the target form page, and target execution role information corresponding to each permission information; obtaining user role information corresponding to the current terminal, and matching the user role information with the target execution role information; if the target execution role information includes first execution role information matching the user role information, determining first permission information corresponding to the first execution role information and a component corresponding to the first permission information; and rendering at least the component corresponding to the first permission information according to the page description file to obtain a first target form page.

[0006] An embodiment of the present application also provides a processing device for components in a form page, including: a generation module and a parsing module; the generation module is used to respond to an editing operation on multiple components on a form design page of a low-code development platform, and generate a page description file corresponding to a target form page according to the description information and hierarchical relationship of the multiple components, and the target form page includes multiple components; the parsing module is used to respond to the parsing operation on the target form page, parse the page description file into a component tree, multiple nodes on the component tree correspond to multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components; the generation module is also used to respond to a permission configuration operation initiated on at least some of the nodes on the component tree, generate at least one permission information for at least some of the components corresponding to at least some of the nodes, and the components corresponding to different permission information are not exactly the same; and the generation module is also used to respond to an execution role configuration operation initiated on at least one permission information, and configure corresponding target execution role information for at least one permission information, and each permission information corresponds to one or more target execution role information.

[0007] The embodiment of the present application also provides a form page display device, including: an acquisition module, a determination module and a rendering module; the acquisition module is used to respond to a display request for a target form page, obtain a page description file of the target form page, at least one permission information corresponding to at least some components contained in the target form page, and target execution role information corresponding to each permission information; the acquisition module is also used to obtain user role information corresponding to the current terminal, and the matching module is used to match the user role information with the target execution role information; the determination module is used to determine first permission information corresponding to the first execution role information and the component corresponding to the first permission information if the target execution role information includes first execution role information matching the user role information; the rendering module is used to render at least the component corresponding to the first permission information according to the page description file to obtain the first target form page.

[0008] An embodiment of the present application also provides an electronic device, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to implement the steps in the component processing method in the form page and the form page display method provided in the embodiment of the present application.

[0009] The embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the steps in the component processing method in the form page and the form page display method provided in the embodiment of the present application.

[0010] An embodiment of the present application also provides a computer program product, including a computer program / instruction. When the computer program / instruction is executed by a processor, the processor implements the steps in the component processing method in the form page and the form page display method provided in the embodiment of the present application.

[0011] In an embodiment of the present application, in the process of generating a form page on a low-code development platform, a page description file corresponding to the target form page is generated, the page description file is parsed into a component tree, and component-level permission configuration is performed through the nodes on the component tree to obtain at least one permission information, each permission information corresponds to one or more components, and corresponding target execution role information is configured for at least one permission information to complete the component-level configuration on the low-code platform. Among them, component-level configuration through the component tree enables users of the low-code development platform to quickly, efficiently, and concisely set and control components on the form page, thereby reducing the cost of use for users. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0013] Figure 1 A flowchart of a method for processing components in a form page provided for an exemplary embodiment of the present application;

[0014] Figure 2 A schematic diagram of a permission information configuration provided for an exemplary embodiment of the present application;

[0015] Figure 3 A flowchart of a form page display method provided for an exemplary embodiment of the present application;

[0016] Figure 4 A structural schematic diagram of a component processing device in a form page provided for another exemplary embodiment of the present application;

[0017] Figure 5 A structural schematic diagram of a form page display device provided for another exemplary embodiment of the present application;

[0018] Figure 6 A schematic structural diagram of an electronic device provided as yet another exemplary embodiment of the present application. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0020] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0021] In response to the above technical problems, in an embodiment of the present application, in the process of generating a form page on a low-code development platform, a page description file corresponding to the target form page is generated, the page description file is parsed into a component tree, and component-level permission configuration is performed through the nodes on the component tree to obtain at least one permission information, each type of permission information corresponds to one or more components, and corresponding target execution role information is configured for at least one permission information, so as to complete the component-level permission and execution role configuration on the low-code platform. Among them, the configuration of component-level permissions and execution roles through the component tree enables users of the low-code development platform to quickly, efficiently, and concisely set and manage components on the form page, thereby reducing the cost of use for users.

[0022] A solution provided by an embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0023] Figure 1 The following is a flow chart of a method for processing components in a form page provided by an exemplary embodiment of the present application. Figure 1 As shown, the method includes:

[0024] 101. In response to an editing operation on a plurality of components on a form design page of a low-code development platform, a page description file corresponding to a target form page is generated according to description information and hierarchical relationships of the plurality of components, the target form page including the plurality of components;

[0025] 102. In response to the parsing operation on the target form page, the page description file is parsed into a component tree, where multiple nodes on the component tree correspond to multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components;

[0026] 103. In response to a permission configuration operation initiated on at least some of the nodes on the component tree, generate at least one type of permission information for at least some of the components corresponding to at least some of the nodes, where components corresponding to different permission information are not completely the same; and

[0027] 104. In response to the execution role configuration operation initiated for at least one permission information, corresponding target execution role information is configured for the at least one permission information, each permission information corresponds to one or more target execution role information, so as to complete the configuration of multiple components.

[0028] In this embodiment, a form page can be generated on a terminal device, and permission information of at least some components in the form can be set. For the sake of distinction and description, the terminal device that generates the form page and configures the permission information of at least some components is referred to as the first terminal, and the terminal that requests to display the form page is referred to as the second terminal. The first terminal and the second terminal can interact through the server. Among them, the user corresponding to the first terminal can be a user of the low-code platform, that is, a user who designs and generates the form page. The user of the second terminal can be a viewer of the form page.

[0029] In this embodiment, a form design page is displayed on the first terminal, and the user can perform editing operations on the components on the form design page to generate a page description file corresponding to the form page. For ease of distinction and description, the generation of a page description file corresponding to the target form page is described as an example. The target form page includes the multiple components. A page description file is a file that describes the layout, style, content, etc. of multiple components in a form page, and the page description file can be a Json schema file. A Json schema file is a structured model that defines JSON (JavaScript Object Notation) data, which can describe the format, type, attributes, etc. of JSON data corresponding to multiple components, wherein JSON data is a lightweight data exchange format. It should be noted that a low-code development platform can be run on the first terminal, and the form design page is displayed through the low-code development platform.

[0030] For example, the form design page includes a component area and an editing area. The components included in the component area may include but are not limited to: single-line text, multi-line text, date, email, link, table, member or picture, etc. The form page designer can perform a drag operation on multiple components in the component area, drag multiple components required to generate a form page to the editing area, adjust the layout and description information of multiple components in the editing area, and generate a page description file of the target form page.

[0031] In this embodiment, the layout of multiple components on the page and the nested relationship between multiple components can determine the hierarchical relationship of multiple components. For example, a form page may include a header component, a main body component, and a bottom component. The header component, the main body component, and the bottom component may be regarded as a parent component, and the parent component includes child components. For example, the header component may include a navigation menu subcomponent or a search box subcomponent, etc.; the main body component may include a main content subcomponent or a sidebar subcomponent, etc.; the bottom component may include a copyright information subcomponent or a link subcomponent, etc. There is a hierarchical relationship between the parent component and the child component, and there is a hierarchical relationship between the parent component and the entire form page. For another example, there is a nested relationship between the table component and each column component in the table component, that is, there is a hierarchical relationship between the table component and its column component.

[0032] In this embodiment, each component has description information, which includes component name, component type, component content, component style, component size, and the hierarchical relationship between the component and other components. The user edits the description information of each component in the editing area. For example, the description information of the component can be modified in the editing area, such as modifying the component style, component size, or component content.

[0033] In this embodiment, the first terminal may generate a page description file corresponding to the target form page according to the description information of the multiple components and the hierarchical relationship between the multiple components.

[0034] In this embodiment, the user can perform a parsing operation on the target form page, and the first terminal can parse the page description file into a component tree in response to the parsing operation on the target form page. Multiple nodes on the component tree correspond to multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components.

[0035] The implementation method of responding to the parsing operation on the target form page is not limited. For example, the form design page includes: a parsing control, the user can click the parsing control, and the first terminal responds to the triggering operation on the parsing control to parse the page description file into a component tree. For another example, the form design page includes a permission configuration control, the user can click the permission configuration control, and the first terminal responds to the triggering operation on the permission configuration control and jumps to the permission configuration page, the permission configuration page includes a parsing control, the user can click the parsing control, and the first terminal responds to the triggering operation on the parsing control to parse the page description file into a component tree.

[0036] In this embodiment, the user can initiate a permission configuration operation on at least some of the nodes on the component tree, wherein the permission configuration operation can be initiated for some of the nodes on the component tree, or for all of the nodes on the component tree. Accordingly, the first terminal can generate at least one permission information corresponding to the target form page for at least some of the components corresponding to at least some of the nodes in response to the permission configuration operation initiated on at least some of the nodes on the component tree, and the components corresponding to different permission information are not exactly the same. For example, the form design page includes components A, B, C, and D, and the component tree includes: nodes a, b, c, and d. For example, a permission configuration operation can be initiated for all nodes in the component tree, and a permission information E1 is generated for component A corresponding to node a and component B corresponding to node b, another permission information E2 is generated for component C corresponding to node c and component D corresponding to node d, and another permission information E3 is generated for component A corresponding to node a and component D corresponding to node d. For another example, a permission configuration operation can be initiated for some of the nodes in the component tree, for example, a permission information E4 is generated for component C corresponding to node c and component D corresponding to node d. The permission information is mainly used to control the display of components. For example, a permission information G1 is generated for components F1 and F2, and the permission information G1 indicates that components F1 and F2 are allowed to be displayed on the form page.

[0037] In this embodiment, in response to an execution role configuration operation initiated for at least one permission information, corresponding target execution role information is configured for at least one permission information to complete the configuration of multiple components. Each permission information corresponds to one or more target execution role information, and each target execution role information corresponds to one or more permission information. Among them, the target execution role information may include but is not limited to: developer role, operation and maintenance personnel role, employee role, leadership role or team leader role, etc.

[0038] In an embodiment of the present application, in the process of generating a form page on a low-code development platform, a page description file corresponding to the target form page is generated, the page description file is parsed into a component tree, and component-level permission configuration is performed through the nodes on the component tree to obtain at least one permission information, each permission information corresponds to one or more components, and corresponding target execution role information is configured for at least one permission information, so as to complete the component-level permission and execution role configuration on the low-code platform. Among them, the component-level and execution role configuration through the component tree can enable users of the low-code development platform to quickly, efficiently and concisely set and control the components on the form page, thereby reducing the use cost of users.

[0039] In an optional embodiment, in response to a parsing operation on a target form page, an implementation method of parsing a page description file into a component tree includes: obtaining description information and hierarchical relationships of multiple components from the page description file, the description information including identification information of the component, the identification information of the component may be any information that can identify the component, for example, the identification information may be the component's identity ID (Identity), component name or component content, etc.; taking the identification information of the multiple components as multiple nodes, since the hierarchical relationship of the multiple components can reflect the parent-child relationship between the multiple components, the hierarchical relationship of the multiple components can be converted into the parent-child relationship between the multiple nodes, and generating a component tree based on the multiple nodes and the parent-child relationship between the multiple nodes.

[0040] In an optional embodiment, after the page description file is parsed into a component tree, the component tree can also be displayed on the permission management page so that users of the low-code development platform can select nodes from the component tree.

[0041] In an optional embodiment, in response to a permission configuration operation initiated on at least some nodes on a component tree, in the process of generating at least one kind of permission information for components corresponding to at least some of the nodes, at least one kind of permission information can be created in response to at least one permission creation operation on a permission management page; for each kind of permission information, in response to an operation of selecting a node from the component tree, the permission information is associated with the component corresponding to the selected node.

[0042] The execution order of displaying the component tree and creating the permission information is not limited. For example, the component tree may be displayed first and then the permission information may be created, or the permission information may be created first and then the component tree may be displayed.

[0043] exist Figure 2, which shows an implementation method of first creating permission information and then displaying a component tree. The example of the created permission information being named "View Privacy Information", the component tree including a "Name" node and a "Privacy Information" node, and the child node "Father" of the "Privacy Information" node is used to illustrate an exemplary method of generating permission information for a component corresponding to a node in the component tree, but is not limited thereto.

[0044] In an optional embodiment, in the process of configuring corresponding target execution role information for at least one kind of permission information, at least one target execution role information can be determined in response to an execution role management operation; for each target execution role information, in response to an operation of selecting permission information, the target execution role information is associated with the selected permission information.

[0045] Optionally, the method of determining at least one target execution role information is not limited. For example, in response to a role management operation, a role management page is displayed, and the role management page includes at least one existing execution role information; in response to a selection operation for the existing execution role information, the target execution role information is selected from the at least one existing execution role information. For another example, in response to an execution role creation operation, the created role information is obtained as the target execution role information. For another example, in response to a role management operation, a role management page is displayed, and the role management page includes at least one existing execution role information; first execution role information is selected from at least one existing execution role information; in response to the execution role creation operation, the created role information is obtained as the second execution role information, and the first execution role information and the second execution role information are used as the target execution role information.

[0046] In an optional embodiment, the first terminal may provide the page description file corresponding to the target form page, at least one kind of permission information corresponding to at least some components, and the target execution role information corresponding to each kind of permission information to the server, so that the server can provide it to the terminal requesting to display the target form page, i.e., the second terminal. The first terminal or the server may publish the page description file corresponding to the target form page. The second terminal may send a display request to the server for the published page description file corresponding to the target form page.

[0047] In addition to the above method embodiments, the present application embodiment also provides a form page display method, such as Figure 3 As shown, the method includes:

[0048] 301. In response to a display request for a target form page, obtain a page description file of the target form page, at least one type of permission information corresponding to at least some components included in the target form page, and target execution role information corresponding to each type of permission information;

[0049] 302. Obtain user role information corresponding to the current terminal, and match the user role information with target execution role information;

[0050] 303. If the target execution role information includes first execution role information matching the user role information, determine first permission information corresponding to the first execution role information and a component corresponding to the first permission information;

[0051] 304. Render at least a component corresponding to the first permission information according to the page description file to obtain a first target form page.

[0052] In this embodiment, the second terminal can obtain the link information published by the server, and the user can click on the link information to initiate a display request for the target form page to the server through the second terminal. The server device provides the page description file of the target form page, at least one permission information corresponding to at least some components contained in the target form page, and the target execution role information corresponding to each permission information to the second terminal. The second terminal can receive the page description file provided by the server, at least one permission information corresponding to at least some components contained in the target form page, and the target execution role information corresponding to each permission information.

[0053] In this embodiment, the user of the second terminal corresponds to one kind of user role information, for example, the user role information is an operation and maintenance personnel role; or the user of the second terminal corresponds to multiple kinds of user role information, for example, the user role information corresponding to the second terminal may be a leadership role and a team leader role. Among them, the user role information can be matched with the target execution role information. The matching process refers to determining which one or which ones of the target execution role information are the same as the user role information. For the convenience of distinction and description, the target execution role information that matches the user role information is referred to as the first execution role information. If the user role information matches the first execution role information, the first permission information corresponding to the first execution role information and the component corresponding to the first permission information are determined; according to the page description file, at least the component corresponding to the first permission information is rendered to obtain the first target form page. The first target form page includes at least the component corresponding to the first permission information.

[0054] For example, the user role information is H, the target form page corresponds to two kinds of permission information and two kinds of target execution role information, the permission information J1 includes component K1, the permission information J2 includes component K2 and component K3, the target execution role information L1 has permission information J1, and the target execution role information L2 has permission information J1 and permission information J2. If the user role information H matches the target execution role information L1, the permission information J1 corresponding to the target execution role information L1 and the component K1 corresponding to the permission information J1 are determined, and according to the page description file, at least the component K1 is rendered to obtain the first target form page.

[0055] In an optional embodiment, the page description file includes components that need to configure permission information and components that do not need to configure permission information. Among them, for the components that need to configure permission information, at least one permission information can be configured for some or all components, and the components that need to configure permission information can be any one or more components in the target form page. The components that do not need to configure permission information can be components that can be displayed on the target form page by default. Based on this, according to the page description file, the components corresponding to the first permission information and the components that do not need to configure permission information can be rendered to obtain the first target form page, and the components corresponding to the first permission information and the components that do not need to configure permission information can be displayed on the first target form page. Among them, the components that need to configure permission information include the components corresponding to the first permission information, that is, the components corresponding to the first permission information can be less than or equal to the components that need to configure permission information. When the components corresponding to the first permission information are less than the components that need to configure permission information, the components that need to configure permission information can also include components that need to configure permission information and have not configured permission information, and components that need to configure permission information and have configured permission information but the target execution role information does not match the user role information. In this case, in the process of obtaining the first target form page, other components other than the components corresponding to the first permission information in the components that need to configure permission information can be rendered.

[0056] Optionally, if the target execution role information does not include the first execution role information that matches the user role information, it means that the user corresponding to the second terminal does not have the permission to view the component corresponding to the permission information. According to the page description file, the component that does not need to be configured with permission information is rendered to obtain a second target form page. The second target form page displays the component that does not need to be configured with permission information.

[0057] Regarding the embodiments of the present application Figure 1 and Figure 3 The detailed implementation and beneficial effects of each step in the method have been described in detail in the aforementioned embodiments and will not be elaborated here.

[0058] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 101 to 103 can be a device; for another example, the execution subject of steps 101 and 102 can be a device, and the execution subject of step 103 can be device B; and so on.

[0059] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 101, 102, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0060] Figure 4 A structural diagram of a processing device for components in a form page provided by an exemplary embodiment of the present application, such as Figure 4 As shown, the device includes: a generating module 41 and a parsing module 42;

[0061] A generation module 41 is used to generate a page description file corresponding to a target form page in response to an editing operation on a plurality of components on a form design page of a low-code development platform, according to description information and hierarchical relationships of the plurality of components, wherein the target form page includes the plurality of components;

[0062] A parsing module 42, for parsing the page description file into a component tree in response to a parsing operation on the target form page, wherein multiple nodes on the component tree correspond to multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components;

[0063] A generating module 41, configured to generate at least one type of permission information for at least some components corresponding to at least some nodes in response to a permission configuration operation initiated on at least some nodes on the component tree, wherein components corresponding to different permission information are not completely the same; and

[0064] The generation module 41 is used to respond to the execution role configuration operation initiated for at least one permission information, configure corresponding target execution role information for at least one permission information, each permission information corresponds to one or more target execution role information, so as to complete the configuration of multiple components.

[0065] In an optional embodiment, the parsing module is specifically used to: obtain description information and hierarchical relationships of multiple components from a page description file, the description information including identification information of the components; use the identification information of the multiple components as multiple nodes, and convert the hierarchical relationships of the multiple components into parent-child relationships between the multiple nodes, and generate a component tree based on the multiple nodes and the parent-child relationships between the multiple nodes.

[0066] In an optional embodiment, the device also includes: a display module; after parsing the page description file into a component tree, the display module is used to display the component tree on the permission management page; the generation module is specifically used to: create at least one permission information in response to at least one permission creation operation on the permission management page; for each type of permission information, in response to the operation of selecting a node from the component tree, associate the permission information with the component corresponding to the selected node.

[0067] In an optional embodiment, the generation module is specifically used to: determine at least one target execution role information in response to an execution role management operation; and for each target execution role information, associate the target execution role information with the selected permission information in response to an operation of selecting permission information.

[0068] Optionally, the generation module is specifically used to: in response to a role management operation, display a role management page, the role management page including at least one existing execution role information; in response to a selection operation on the existing execution role information, select target execution role information from at least one type of existing execution role information, and / or, in response to an execution role creation operation, obtain the created role information as the target execution role information.

[0069] In an optional embodiment, the device also includes a providing module; the providing module is used to provide a page description file, at least one permission information corresponding to at least some components, and target execution role information corresponding to each permission information to the server, so that the server provides it to the terminal requesting to display the target form page.

[0070] Figure 5 A structural diagram of a form page display device provided for an exemplary embodiment of the present application, such as Figure 5 As shown, the device includes: an acquisition module 51, a matching module 52, a determination module 53 and a rendering module 54.

[0071] The acquisition module 51 is used to respond to the display request for the target form page, acquire the page description file of the target form page, at least one kind of permission information corresponding to at least part of the components included in the target form page, and the target execution role information corresponding to each kind of permission information;

[0072] The acquisition module 51 is also used to acquire the user role information corresponding to the current terminal, and the matching module 52 is used to match the user role information with the target execution role information;

[0073] The determination module 53 is used to determine the first permission information corresponding to the first execution role information and the component corresponding to the first permission information if the target execution role information includes the first execution role information matching the user role information;

[0074] The rendering module 54 is used to render at least the component corresponding to the first permission information according to the page description file to obtain a first target form page.

[0075] In an optional embodiment, the page description file includes components that need to be configured with permission information and components that do not need to be configured with permission information; the rendering module is specifically used to: render the components corresponding to the first permission information and the components that do not need to be configured with permission information according to the page description file to obtain the first target form page.

[0076] Optionally, the rendering module is further used to: if the target execution role information does not include first execution role information matching the user role information, render components that do not require configuration of permission information according to the page description file to obtain a second target form page.

[0077] Regarding the embodiments of the present application Figure 4 and Figure 5 The detailed implementation and beneficial effects of each step in the illustrated device have been described in detail in the aforementioned embodiments and will not be elaborated on here.

[0078] Figure 6 A schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application is shown in FIG. Figure 6 As shown, the device includes: a memory 64 and a processor 65.

[0079] The memory 64 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method used to operate on the electronic device.

[0080] The processor 65 is coupled to the memory 64 and is used to execute the computer program in the memory 64, so as to: in response to an editing operation on multiple components on a form design page of a low-code development platform, generate a page description file corresponding to a target form page according to the description information and hierarchical relationship of the multiple components, and the target form page includes multiple components; in response to a parsing operation on the target form page, parse the page description file into a component tree, multiple nodes on the component tree correspond to multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components; in response to a permission configuration operation initiated on at least some of the nodes on the component tree, generate at least one permission information for at least some of the components corresponding to at least some of the nodes, and the components corresponding to different permission information are not exactly the same; and in response to an execution role configuration operation initiated on at least one permission information, respectively configure corresponding target execution role information for at least one permission information, and each permission information corresponds to one or more target execution role information, so as to complete the configuration of multiple components.

[0081] In an optional embodiment, when the processor 65 parses the page description file into a component tree in response to a parsing operation on a target form page, it is specifically used to: obtain description information and hierarchical relationships of multiple components from the page description file, the description information including identification information of the components; use the identification information of the multiple components as multiple nodes, and convert the hierarchical relationships of the multiple components into parent-child relationships between the multiple nodes, and generate a component tree based on the multiple nodes and the parent-child relationships between the multiple nodes.

[0082] In an optional embodiment, after parsing the page description file into a component tree, the processor 65 is further used to: display the component tree on the permission management page; when the processor 65 generates at least one permission information for the components corresponding to at least some of the nodes in response to a permission configuration operation initiated on at least some of the nodes on the component tree, the processor 65 is specifically used to: create at least one permission information in response to at least one permission creation operation on the permission management page; for each type of permission information, in response to an operation of selecting a node from the component tree, associate the permission information with the component corresponding to the selected node.

[0083] In an optional embodiment, when the processor 65 configures corresponding target execution role information for at least one permission information in response to an execution role configuration operation initiated for at least one permission information, it is specifically used to: respond to the execution role management operation to determine at least one target execution role information; for each target execution role information, respond to the operation of selecting permission information to associate the target execution role information with the selected permission information.

[0084] Optionally, when the processor 65 determines at least one execution role information in response to an execution role management operation, it is specifically used to: display a role management page in response to the role management operation, the role management page including at least one existing execution role information; select target execution role information from at least one existing execution role information, and / or, in response to an execution role creation operation, obtain the created role information as the target execution role information.

[0085] In an optional embodiment, the processor 65 is also used to provide the page description file, at least one permission information corresponding to at least some components, and the target execution role information corresponding to each permission information to the server, so that the server can provide it to the terminal requesting to display the target form page.

[0086] Regarding the embodiments of the present application Figure 6 The detailed implementation and beneficial effects of each step in the illustrated device have been described in detail in the aforementioned embodiments and will not be elaborated on here.

[0087] Further, if Figure 6 As shown, the electronic device also includes: a communication component 66, a display 67, a power component 68, an audio component 69 and other components. Figure 6 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 6 In addition, Figure 6 The components in the dotted box are optional components, not mandatory components, and may depend on the product form of the electronic device. The electronic device of this embodiment may be implemented as a terminal device such as a desktop computer, a laptop computer, a smart phone or an IOT device.

[0088] The embodiment of the present application also provides an electronic device, the implementation structure of the electronic device is Figure 6 The implementation structure of the electronic device shown is the same or similar, and can refer to Figure 6 The electronic device provided in this embodiment is implemented as follows: Figure 6The difference between the electronic devices in the illustrated embodiments mainly lies in that the functions implemented by the processor executing the computer program stored in the memory are different. For the electronic device provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: in response to a display request for a target form page, obtain a page description file of the target form page, at least one permission information corresponding to at least part of the components contained in the target form page, and target execution role information corresponding to each permission information; obtain user role information corresponding to the current terminal, and match the user role information with the target execution role information; if the target execution role information includes the first execution role information that matches the user role information, determine the first permission information corresponding to the first execution role information and the component corresponding to the first permission information; according to the page description file, render at least the component corresponding to the first permission information to obtain the first target form page.

[0089] In an optional embodiment, the page description file includes components that need to be configured with permission information and components that do not need to be configured with permission information; when the processor renders at least the components corresponding to the first permission information according to the page description file to obtain the first target form page, it is specifically used to: render the components corresponding to the first permission information and the components that do not need to be configured with permission information according to the page description file to obtain the first target form page.

[0090] In an optional embodiment, the processor is further configured to: if the target execution role information does not include first execution role information matching the user role information, render components that do not require configuration of permission information according to the page description file to obtain a second target form page.

[0091] The detailed implementation and beneficial effects of the electronic device provided in the embodiments of the present application have been described in detail in the aforementioned embodiments and will not be elaborated here.

[0092] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figure 1 and Figure 3 The steps in the method embodiment shown may be executed by an electronic device.

[0093] Accordingly, the embodiment of the present application further provides a computer program product, including a computer program / instruction, which, when executed by a processor, enables the processor to implement the above-mentioned Figure 1 and Figure 3 The steps in the method embodiment shown may be executed by an electronic device.

[0094] The above-mentioned memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0095] The above-mentioned communication component is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

[0096] The above-mentioned display includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0097] The power supply assembly provides power to various components of the device where the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply assembly is located.

[0098] The above-mentioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (Microphone, MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal.

[0099] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-readable storage media (including but not limited to disk storage, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage, etc.) containing computer-usable program code.

[0100] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0101] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0102] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0103] In a typical configuration, a computing device includes one or more processors (Central Processing Unit, CPU), input / output interface, network interface and memory.

[0104] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0105] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0106] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0107] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for processing components in a form page, characterized in that: include: In response to an editing operation on a plurality of components on a form design page of a low-code development platform, a page description file corresponding to a target form page is generated according to description information and hierarchical relationships of the plurality of components, the target form page including the plurality of components; In response to a parsing operation on the target form page, the page description file is parsed into a component tree, where a plurality of nodes on the component tree correspond to the plurality of components, and a parent-child relationship between the plurality of nodes represents a hierarchical relationship between the plurality of components; In response to a permission configuration operation initiated on at least some of the nodes on the component tree, generating at least one type of permission information for at least some of the components corresponding to the at least some of the nodes, wherein components corresponding to different permission information are not completely the same; as well as In response to an execution role configuration operation initiated for at least one permission information, corresponding target execution role information is configured for the at least one permission information, each permission information corresponds to one or more target execution role information, so as to complete the configuration of the multiple components.

2. The method according to claim 1, characterized in that In response to the parsing operation on the target form page, the page description file is parsed into a component tree, including: Acquire description information and hierarchical relationships of the multiple components from the page description file, wherein the description information includes identification information of the components; The identification information of the multiple components is used as multiple nodes, and the hierarchical relationship of the multiple components is converted into a parent-child relationship between the multiple nodes, and the component tree is generated according to the parent-child relationship between the multiple nodes.

3. The method according to claim 1, characterized in that After parsing the page description file into a component tree, the method further includes: displaying the component tree on a permission management page; In response to a permission configuration operation initiated on at least some of the nodes on the component tree, generating at least one type of permission information for the components corresponding to the at least some of the nodes, including: In response to at least one permission creation operation on the permission management page, create at least one permission information; For each type of permission information, in response to an operation of selecting a node from the component tree, the permission information is associated with a component corresponding to the selected node.

4. The method according to any one of claims 1 to 3, characterized in that: In response to an execution role configuration operation initiated for at least one permission information, corresponding target execution role information is configured for the at least one permission information, including: In response to the execution role management operation, determining at least one target execution role information; For each target execution role information, in response to an operation of selecting permission information, the target execution role information is associated with the selected permission information.

5. The method according to claim 4, characterized in that In response to the execution role management operation, at least one execution role information is determined, including: In response to the role management operation, displaying a role management page, the role management page including at least one existing execution role information; In response to a selection operation on existing execution role information, target execution role information is selected from the at least one existing execution role information, and / or, in response to an execution role creation operation, the created role information is acquired as the target execution role information.

6. The method according to any one of claims 1 to 3, characterized in that: Also includes: The page description file, at least one permission information corresponding to at least part of the components, and target execution role information corresponding to each permission information are provided to the server, so that the server provides them to the terminal requesting to display the target form page.

7. A form page display method, characterized in that: include: In response to a display request for a target form page, obtaining a page description file of the target form page, at least one type of permission information corresponding to at least some components included in the target form page, and target execution role information corresponding to each type of permission information; Obtaining user role information corresponding to the current terminal, and matching the user role information with the target execution role information; If the target execution role information includes first execution role information matching the user role information, determining first permission information corresponding to the first execution role information and a component corresponding to the first permission information; According to the page description file, at least the component corresponding to the first permission information is rendered to obtain a first target form page.

8. The method according to claim 7, characterized in that The page description file includes components that need to be configured with permission information and components that do not need to be configured with permission information; According to the page description file, at least a component corresponding to the first permission information is rendered to obtain a first target form page, including: According to the page description file, components corresponding to the first permission information and components that do not need to be configured with permission information are rendered to obtain a first target form page.

9. The method according to claim 8, characterized in that Also includes: If the target execution role information does not include the first execution role information matching the user role information, the components that do not need to be configured with permission information are rendered according to the page description file to obtain a second target form page.

10. A processing device for components in a form page, characterized in that: include: Generate modules and parse modules; The generating module is configured to generate, in response to an editing operation on a plurality of components on a form design page of a low-code development platform, a page description file corresponding to a target form page according to description information and hierarchical relationships of the plurality of components, wherein the target form page includes the plurality of components; The parsing module is used to parse the page description file into a component tree in response to a parsing operation on the target form page, wherein the multiple nodes on the component tree correspond to the multiple components, and the parent-child relationship between the multiple nodes represents the hierarchical relationship between the multiple components; The generating module is further configured to generate at least one type of permission information for at least some components corresponding to at least some nodes in response to a permission configuration operation initiated on at least some nodes on the component tree, wherein components corresponding to different permission information are not completely the same; and The generation module is also used to respond to an execution role configuration operation initiated for at least one permission information, and configure corresponding target execution role information for the at least one permission information, each permission information corresponds to one or more target execution role information, so as to complete the configuration of the multiple components.

11. A form page display device, characterized in that: include: Get module, match module, determine module and render module; The acquisition module is used to, in response to a display request for a target form page, acquire a page description file of the target form page, at least one type of permission information corresponding to at least some components included in the target form page, and target execution role information corresponding to each type of permission information; The acquisition module is further used to acquire user role information corresponding to the current terminal, and the matching module is used to match the user role information with the target execution role information; The determination module is configured to determine first permission information corresponding to the first execution role information and a component corresponding to the first permission information if the target execution role information includes first execution role information matching the user role information; The rendering module is used to render at least the component corresponding to the first permission information according to the page description file to obtain a first target form page.

12. An electronic device, characterized in that: include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to implement the steps in the method of any one of claims 1 to 6 and claims 7 to 9.

13. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is caused to implement the steps in the method according to any one of claims 1 to 6 and claims 7 to 9.

Images