Access control methods, devices, electronic devices and storage media

By responding to permission configuration requests in a low-code platform and configuring business flow permissions for workflow dashboards using business forms and user role attributes, the problem of poor flexibility in configuring user operation permissions for workflow dashboards is solved, and the efficiency and granularity of permission configuration are improved.

CN115470505BActive Publication Date: 2026-11-10CCB FINTECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202211203123.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-29
Publication Date
2026-11-10
Estimated Expiration
2042-09-29

AI Technical Summary

Technical Problem

The user configuration of operation permissions in the existing low-code platform's process dashboard is inflexible, resulting in low permission configuration efficiency and low granularity, which cannot meet the flexible and ever-changing market demands.

Method used

By responding to permission configuration requests, the target node of the target process dashboard is determined, the relevant business forms are retrieved from the data warehouse, the operation user is determined based on the business forms and target fields, and the business flow permissions are configured according to the business type and user role attributes of the process dashboard.

Benefits of technology

It improves the efficiency and granularity of permission configuration, and can automatically redirect to the user bound in the target field, meeting the user's flexible configuration needs and solving the problem of poor flexibility in the traditional method.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115470505B_ABST
    Figure CN115470505B_ABST
Patent Text Reader

Abstract

This disclosure provides a permission management method, apparatus, electronic device, and storage medium, which can be applied to the field of computer technology. The method includes: in response to a permission configuration request, determining the target node of the target process dashboard, wherein the permission configuration request carries a target field; retrieving a business form associated with the target process dashboard from a data warehouse; assigning tasks to the target process dashboard based on the business form and the target field to determine a target operation user, wherein the target operation user has a user role attribute; and configuring the business flow permissions of the target operation user based on the business type and user role attribute of the target process dashboard.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, electronic device, and storage medium for access control. Background Technology

[0002] With the development of internet computing such as big data and cloud computing, digital transformation has become a new opportunity for enterprise development. Major companies are leveraging this wave of information technology construction to build their own application systems. Low-code architecture allows for the rapid construction of various application systems with minimal code writing, through visual component drag-and-drop methods.

[0003] The process of building application systems using low-code platforms can generally be implemented through workflow dashboards. Workflow dashboards not only flow along with the building tasks but also visualize the application system building process, making it easier for users to intuitively understand the current stage of each building task and related detailed information. In realizing this disclosed concept, the inventors discovered at least the following problems in related technologies: the configuration method for configuring user operation permissions for workflow dashboards based on low-code platforms lacks flexibility, resulting in low efficiency and low granularity in permission configuration. Summary of the Invention

[0004] In view of this, the present disclosure provides a method, apparatus, electronic device, storage medium, and computer program product for managing access rights.

[0005] One aspect of this disclosure provides a permission management method, comprising: responding to a permission configuration request, determining the target node where the target process dashboard is located, wherein the permission configuration request carries a target field; obtaining a business form associated with the target process dashboard from a data warehouse; assigning tasks to the target process dashboard based on the business form and the target field to determine a target operation user, wherein the target operation user has a user role attribute; and configuring the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attribute.

[0006] According to embodiments of this disclosure, configuring the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attributes includes: obtaining a process form associated with the target process dashboard from the data warehouse; determining at least one flow node associated with the target node based on the process form; determining a target flow node from at least one of the flow nodes based on the business type to which the target process dashboard belongs and the user role attributes; and configuring the business flow permissions of the target operation user based on the target flow node.

[0007] According to embodiments of this disclosure, determining at least one flow node associated with the target node based on the above-mentioned process form includes: determining multiple associated nodes associated with the target node from the above-mentioned process form; and determining at least one of the above-mentioned flow nodes located after the process represented by the target node from the multiple associated nodes based on business logic relationships.

[0008] According to embodiments of this disclosure, the aforementioned flow nodes have node role attributes; wherein, determining a target flow node from at least one of the aforementioned flow nodes based on the business type to which the target flow dashboard belongs and the aforementioned user role attributes includes: modifying the aforementioned user role attributes based on the business type to which the target flow dashboard belongs to obtain a target operation user role attribute; matching the aforementioned target operation user role attribute with the node role attributes of at least one of the aforementioned flow nodes respectively to obtain at least one matching result; and determining the aforementioned target flow node from at least one of the aforementioned flow nodes based on at least one of the aforementioned matching results.

[0009] According to embodiments of this disclosure, the above-mentioned modification of the user role attributes based on the business type to which the target process dashboard belongs to obtain the target operation user role attributes includes: determining the target operation user role attributes as preset user role attributes when the business type to which the target process dashboard belongs is a preset business type; obtaining the historical operation records of the target operation user when the business type to which the target process dashboard belongs is not a preset business type; performing statistical analysis on the historical operation records to obtain analysis results; and modifying the user role attributes based on the analysis results and the business type to which the target process dashboard belongs to obtain the target operation user role attributes.

[0010] According to embodiments of this disclosure, the above-mentioned task allocation to the target process dashboard based on the above-mentioned business form and the above-mentioned target field to determine the target operation user includes: extracting form data associated with the above-mentioned target field from the above-mentioned business form based on the above-mentioned target field, wherein the above-mentioned form data includes at least one user identification information; determining at least one operation user based on at least one of the above-mentioned user identification information; and allocating the tasks generated based on the above-mentioned target process dashboard among the at least one of the above-mentioned operation users to determine the target operation user who has been assigned the task.

[0011] According to an embodiment of this disclosure, the method further includes: when the target user has finished processing the target flow dashboard, in response to the target user's drag operation, transferring the target flow dashboard from the target node to the target transfer node.

[0012] Another aspect of this disclosure provides a permission management device, comprising: a first determining module, configured to determine the target node of the target process dashboard in response to a permission configuration request, wherein the permission configuration request carries a target field; an obtaining module, configured to obtain a business form associated with the target process dashboard from a data warehouse; an allocation module, configured to allocate tasks to the target process dashboard based on the business form and the target field to determine a target operation user, wherein the target operation user has a user role attribute; and a configuration module, configured to configure the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attribute.

[0013] Another aspect of this disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more instructions, wherein when the one or more instructions are executed by the one or more processors, the one or more processors cause the one or more processors to implement the above-described permission management method.

[0014] Another aspect of this disclosure provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to implement the aforementioned permission management method.

[0015] Another aspect of this disclosure provides a computer program product including computer-executable instructions that, when executed, implement the aforementioned access control method.

[0016] According to embodiments of this disclosure, a permission management method, apparatus, electronic device, storage medium, and product determine the target node of a target process dashboard in response to a permission configuration request; retrieve related business forms from a data warehouse; determine the operating user based on the target fields carried in the business forms and the permission configuration request; and configure business flow permissions according to the business type of the target process dashboard and the role attributes of the operating user. Because the operating user is determined using the target fields and business forms, and the business flow permissions are determined using the attributes of the target process dashboard and the user's role, the information carried in the permission configuration request and the target process dashboard itself can be fully utilized to automatically redirect the target process dashboard to the user bound in the target fields and configure the permissions that the operating user can possess. This at least partially overcomes the problem of poor flexibility in configuring operating permissions for users of process dashboards in related technologies, thereby achieving the technical effect of improving the efficiency and granularity of permission configuration. Attached Figure Description

[0017] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0018] Figure 1 This schematic diagram illustrates a system architecture of a permission management method and apparatus according to embodiments of the present disclosure;

[0019] Figure 2 A flowchart illustrating a permission management method according to an embodiment of the present disclosure is shown schematically.

[0020] Figure 3 The diagram illustrates the configuration of operating permissions according to an embodiment of the present disclosure.

[0021] Figure 4 This illustration shows a schematic diagram of the configuration of business flow permissions according to an embodiment of the present disclosure;

[0022] Figure 5 A block diagram schematically illustrates a permission management apparatus according to embodiments of the present disclosure; and

[0023] Figure 6 A block diagram of an electronic device suitable for implementing a permission management method according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0024] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0026] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0027] When using expressions such as "at least one of A, B, and C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). When using expressions such as "at least one of A, B, or C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).

[0028] As business demands continue to emerge, the construction of application systems also needs to meet diverse business requirements. The process of building application systems using traditional software development involves professional technicians writing code based on user needs to create various application systems. This process includes requirements analysis, system design, development, and testing. Therefore, traditional software development models suffer from drawbacks such as long development cycles, high development costs, poor flexibility and scalability, and the need for a large number of developers. Traditional software development models are increasingly unable to meet the flexible and ever-changing market demands. In this context, a development model that enables the rapid construction of various application systems through a visual approach—low-code development—has emerged.

[0029] Low-code development refers to the rapid construction of various application systems through drag-and-drop visual components, requiring little or no coding. Low-code platforms aim to simplify the process, time, and cost of building enterprise management systems, lowering the barrier to entry for enterprise application system development and achieving rapid system deployment. Low-code platforms can save developers a significant amount of coding work, while also enabling non-technical personnel to quickly generate applications through a visual interface. After the application system is built, the one-click automated deployment capability of the low-code platform allows for rapid deployment to the specified environment. Simultaneously, the low-code platform can manage, modify, and update relationships between different applications. Furthermore, after the application system is built, the low-code platform helps users implement full lifecycle management of the application, displaying detailed application runtime data, generating application performance reports, and providing intelligent suggestions based on historical data.

[0030] As forms are increasingly used on low-code platforms, the above configuration methods can no longer meet the growing user demands. For example, traditional low-code platforms typically configure user permissions for workflow dashboards using direct selection. Direct selection means configuring the operator for a specific node in the workflow directly through a personnel selector. Only the configured user has the permission to operate at that node. This method may limit the personnel handling a workflow node to a fixed set of people, potentially reducing processing efficiency under high workloads. Of course, configuring more people with the same permissions to solve the problem of low processing efficiency under high workloads is also undesirable, as some people do not need these permissions, and this method may also introduce security risks. Furthermore, in a business workflow, users may want workflow nodes to automatically flow to the personnel bound to the executor field in the form, rather than to fixed personnel. Obviously, the above direct selection method cannot meet this requirement. Current permission configuration methods suffer from low flexibility and low configuration efficiency. In addition, traditional low-code platform workflow dashboards can generally only configure workflow transition nodes. For example, if node A is configured with transition nodes B and C, any user with operation permissions for node A can drag the dashboard from node A to node B or node C. It is impossible to finely control the operation permissions of transition nodes and achieve fine-grained management of node operation permissions.

[0031] In view of this, embodiments of the present disclosure provide a method to improve the efficiency of configuring operation permissions for users and enhance the granularity of permission configuration. Specifically, embodiments of the present disclosure provide a permission management method, a permission management device, an electronic device, a storage medium, and a program product. The permission management method includes: in response to a permission configuration request, determining the target node where the target process dashboard is located, wherein the permission configuration request carries a target field; obtaining a business form associated with the target process dashboard from a data warehouse; assigning tasks to the target process dashboard based on the business form and the target field to determine the target operation user, wherein the target operation user has a user role attribute; and configuring the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attribute.

[0032] In the technical solution disclosed herein, the acquisition, storage, and application of user personal information comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals. In the technical solution disclosed herein, user authorization or consent has been obtained before acquiring or collecting user personal information.

[0033] Figure 1 A schematic diagram illustrating the system architecture of a permission management method and apparatus according to embodiments of the present disclosure is provided. It should be noted that... Figure 1The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0034] like Figure 1 As shown, the system architecture 100 according to this embodiment may include a target process dashboard 101 and multiple target nodes 102-106.

[0035] The target process dashboard 101 can be a transmission medium that displays business information, approval information, executor information, current stage, operating permissions, and transfer permissions during the approval and execution processes.

[0036] Each target node may include an electronic device. Any one of the target nodes may serve as the starting node, which may be used to respond to permission configuration requests, trigger business flow, and begin transmitting process dashboard 101.

[0037] Any one of the target nodes can be used as the end node. The end node can be a node that indicates that the business has been completed or that a certain stage of the business has ended.

[0038] Other nodes in the target node, besides the start and end nodes, can also serve as approval nodes, execution nodes, etc., required by the business during the approval and execution processes. For example... Figure 1 As shown, during the permission management process, the starting node can respond to the permission configuration request and determine the target node where the process dashboard 101 is located; retrieve the business forms associated with the target process dashboard from the data warehouse; assign tasks to the target process dashboard based on the business forms and the target fields carried in the permission configuration request to determine the target operation user; and configure the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attributes of the target operation user.

[0039] It should be noted that the permission management method provided in this disclosure embodiment can generally be executed by the target node. Correspondingly, the permission management device provided in this disclosure embodiment can generally be set in the target node. The permission management method provided in this disclosure embodiment can also be executed by a node different from the target node but capable of interacting with it. Correspondingly, the permission management device provided in this disclosure embodiment can also be set in a node different from the target node but capable of interacting with it.

[0040] It should be understood that Figure 1 The number of target process dashboards and target nodes shown is merely illustrative. Depending on implementation needs, there can be any number of target process dashboards and target nodes.

[0041] The following will be based on Figure 1 The described system architecture, through Figures 2-4 The permission management method of the disclosed embodiments is described in detail.

[0042] Figure 2 A flowchart illustrating a permission management method according to an embodiment of the present disclosure is shown schematically.

[0043] like Figure 2 As shown, the method includes operations S201 to S204.

[0044] In operation S201, in response to the permission configuration request, the target node of the target process dashboard is determined, wherein the permission configuration request carries the target field.

[0045] In operation S202, retrieve the business forms associated with the target process dashboard from the data warehouse.

[0046] In operation S203, tasks are assigned to the target process dashboard based on the business form and target fields to determine the target operation users, where the target operation users have user role attributes.

[0047] In operation S204, based on the business type and user role attributes of the target process dashboard, configure the business flow permissions for the target operation user.

[0048] According to embodiments of this disclosure, a permission configuration request can be a request to configure workflow permissions for personnel handling workflow processes. Workflow processes can involve the verification, testing, and deployment of newly developed models or systems. These workflows typically require approval from reviewers. If the approval is successful, the workflow can proceed to the next node or end. If the approval fails, the reviewer can transfer the workflow node back to the developer for further modifications. Therefore, reviewers need to possess workflow permissions.

[0049] According to embodiments of this disclosure, the target workflow dashboard can be a transmission medium that displays information such as business identifiers, business information, approval information, executor information, current stage, operating permissions, and transfer permissions, such as a workflow card. The target workflow dashboard can move along with a specific task.

[0050] According to embodiments of this disclosure, the target node can be at least one flow node in the process, and the flow node can include nodes such as pending, processing, pending verification, and completed.

[0051] According to embodiments of this disclosure, by displaying process business information in the form of a process dashboard and performing process operations in a visual manner, users can more intuitively understand the stage of each task in the process, the operator performing the task, and other detailed information about the task execution.

[0052] According to embodiments of this disclosure, a data warehouse can be used to store business forms. Specifically, based on a business identifier displayed in the target process dashboard, such as a business number, a business form corresponding to that business number can be retrieved from the data warehouse, and that business form can be associated with the target process dashboard.

[0053] According to embodiments of this disclosure, the target field may refer to a name field, an executor field, an approver field, etc. The target user can be one or more users appearing in the name field, executor field, and approver field.

[0054] According to embodiments of this disclosure, user role attributes may include the target user's basic information, operating permissions, and relationships with other users.

[0055] According to embodiments of this disclosure, the service type can be determined based on the importance of the service, the frequency of the service occurrence, the sensitivity of the service, or the confidentiality of the service, etc.

[0056] According to embodiments of this disclosure, business flow permissions can be permissions that allow a business to flow to a specified target node. Business flow permissions can include permissions for nodes to be processed, nodes in process, nodes to be verified, and nodes that have been completed. They can also include permissions to add business processes, delete business processes, and skip the current business process.

[0057] According to embodiments of this disclosure, a permission management method, apparatus, electronic device, storage medium, and product determine the target node of a target process dashboard in response to a permission configuration request; retrieve related business forms from a data warehouse; determine the operating user based on the target fields carried in the business forms and the permission configuration request; and configure business flow permissions according to the business type of the target process dashboard and the role attributes of the operating user. Because the operating user is determined using the target fields and business forms, and the business flow permissions are determined using the attributes of the target process dashboard and the user's role, the information carried in the permission configuration request and the target process dashboard itself can be fully utilized to automatically redirect the target process dashboard to the user bound in the target fields and configure the permissions that the operating user can possess. This at least partially overcomes the problem of poor flexibility in configuring operating permissions for users of process dashboards in related technologies, thereby achieving the technical effect of improving the efficiency and granularity of permission configuration.

[0058] According to embodiments of this disclosure, operation S203 may further include the following operations: extracting form data associated with the target field from the business form based on the target field, wherein the form data includes at least one user identification information; determining at least one operation user based on the at least one user identification information; and allocating tasks generated based on the target process dashboard among the at least one operation user to determine the target operation user to whom the task is allocated.

[0059] According to embodiments of this disclosure, user identification information may include user name, user number, etc. Each user name and each user number may correspond to one operator. Based on the process task type generated by the target net process dashboard, the required flow nodes, or the business logic relationship of the tasks, the target operator can be assigned among at least one operator to obtain the target operator at the target node.

[0060] Figure 3 The diagram illustrates the configuration of operating permissions according to an embodiment of the present disclosure.

[0061] like Figure 3 As shown, in addition to direct selection and selection by rules, a new configuration option is added for automatic allocation based on form field selection in the permission configuration. For example, when a business flow event is detected, the allocation rule can be selected to allocate based on form field selection. The field can be the name field. The process engine can automatically set the user bound to the "name" field in the form as the person to be assigned to the flow node, thereby realizing this flexible automatic allocation method of selecting the person to be assigned based on form field selection.

[0062] According to embodiments of this disclosure, the target user for a given operation node is determined based on preset fields such as name, executor, and approver in the business form, enabling flexible configuration of process nodes. If a rule-based configuration method is used to pre-bind users based on the executor and approver fields, it may be necessary to configure a separate process rule for each user when there are many users or business processes. This not only leads to a large workload and is time-consuming, but also wastes resources as some users may not need to perform execution or approval operations. However, embodiments of this disclosure provide a solution that eliminates the need for pre-setting rules and pre-binding users. Upon responding to a business flow event, it can automatically assign one or more users appearing in the name, executor, and approver fields of the business form. This not only saves time and effort but also conserves resources and improves the efficiency of permission configuration.

[0063] According to an embodiment of this disclosure, operation S204 may further include the following operations: obtaining a process form associated with the target process dashboard from the data warehouse; determining at least one flow node associated with the target node based on the process form; determining a target flow node from at least one flow node based on the business type and user role attributes of the target process dashboard; and configuring business flow permissions for the target operation user based on the target flow node.

[0064] According to embodiments of this disclosure, the process form may include flow nodes that are to be processed or have already been processed, and the target node may be one or more flow nodes. The data warehouse may also store process forms. Specifically, based on the business identifier displayed on the target process dashboard, such as a business number, the process form corresponding to that business number can be found in the data warehouse, and that process form can be used as the process form associated with the target process dashboard.

[0065] According to embodiments of this disclosure, determining at least one flow node associated with a target node based on a process form may include the following operations: determining multiple associated nodes associated with the target node from the process form; and determining at least one flow node located after the process represented by the target node from the multiple associated nodes based on business logic relationships.

[0066] According to embodiments of this disclosure, a process form may contain multiple flow nodes that are to be processed or have already been processed. Based on the identification information of the target node, such as its number, fields, or sequence number, multiple flow nodes associated with the target node can be determined from among these multiple flow nodes. These multiple associated flow nodes are, for example, a collection of all nodes belonging to the same process business as the target node.

[0067] According to embodiments of this disclosure, business logic relationships can be related to the order in which business processes are completed. For example, the logical relationship of a business process flow can be pending, processing, pending verification, completed, etc. Based on the business logic relationships, one or more process nodes following the target node can be determined from the set of all nodes.

[0068] According to embodiments of this disclosure, a flow node may have a node role attribute. Determining a target flow node from at least one flow node based on the business type and user role attribute of the target flow dashboard may further include the following operations: modifying the user role attribute based on the business type of the target flow dashboard to obtain a target operation user role attribute; matching the target operation user role attribute with the node role attribute of at least one flow node to obtain at least one matching result; and determining the target flow node from at least one flow node based on the at least one matching result.

[0069] According to embodiments of this disclosure, modifying user role attributes may include the following operations: when the business type to which the target process dashboard belongs is a preset business type, determining the target operation user role attribute as a preset user role attribute; when the business type to which the target process dashboard belongs is not a preset business type, obtaining the target operation user's historical operation records; performing statistical analysis on the historical operation records to obtain analysis results; and modifying the user role attributes based on the analysis results and the business type to which the target process dashboard belongs to obtain the target operation user role attributes.

[0070] According to embodiments of this disclosure, the preset service type can be a type determined based on the importance of the service, a type determined based on the frequency of occurrence of the service, a type determined based on the sensitivity of the service, a type determined based on the confidentiality of the service, etc. The preset service type can be one or more service types.

[0071] According to embodiments of this disclosure, the preset user role attributes may include the user's basic information, operating permissions, and relationships with other users.

[0072] According to embodiments of this disclosure, historical operation records can be operations performed by the user in previous approval processes, such as initiating, reviewing, and verifying operations.

[0073] According to embodiments of this disclosure, the analysis results can be a table file generated after statistical analysis of the operations performed by the user. The table file may include all performed operations, the number of times each operation was performed, and the sorting results of each operation based on the number of times it was performed.

[0074] According to the embodiments of this disclosure, based on the analysis results and the business type to which the target workflow dashboard belongs, the user role attributes can be modified. After obtaining the target operation user role attributes, the target operation user role attributes can be matched with the node role attributes of at least one workflow node to obtain at least one matching result. If the matching result shows that the target operation user role attributes are consistent with the node role attributes of the workflow node, the target workflow node can be determined from at least one workflow node based on the at least one matching result. After determining the target workflow node, the business workflow permissions of the target operation user can be configured.

[0075] According to embodiments of this disclosure, by modifying user role attributes to obtain target operation user role attributes, it is possible to configure user role attributes for process dashboards that are not preset business types (such as newly developed business types, or business types that have never been processed before, and for which there are no corresponding processing flows). In this way, the business flow permissions of the target user can be determined based on the role attributes, thereby improving the flexibility of permission configuration.

[0076] Figure 4 The illustration shows a schematic diagram of the configuration of business flow permissions according to an embodiment of the present disclosure.

[0077] like Figure 4 As shown, if the first user, the second user, and the third user all have operation permissions for node A, and the role attribute of the first user is set to 'a', the role attribute of the second user is set to 'b', the role attribute of the third user is set to 'c', the role attribute of node B is set to 'a', the role attribute of node C is set to 'b', and the role attribute of node D is set to 'c', then the first user can only transfer the business process from node A to node B with the same role attribute, but cannot transfer it from node A to node C or node D. Specifically, the first user can transfer nodes by dragging, pulling, or dropping. The second user can only transfer the business process from node A to node C with the same role attribute, but cannot transfer it from node A to node B or node D. The third user can only transfer the business process from node A to node D with the same role attribute, but cannot transfer it from node A to node B or node C. In this way, further control over the target transfer nodes can be achieved, meeting users' needs for precise control over business flow permissions and improving the granularity of permission configuration.

[0078] According to embodiments of this disclosure, when the workflow nodes include nodes to be issued, nodes to be processed, nodes in the processing stage, nodes to be verified, and completed nodes, the personnel permissions corresponding to the workflow nodes can be configured as groups to be issued, processed, processed, verified, and completed, respectively. When a user has business that needs to be processed, the workflow engine can determine whether the user can process the business to be processed to the specified workflow node based on the configured workflow nodes and the personnel permissions corresponding to the workflow nodes. For example, if the first user belongs to the processing group, the first user can only drag the business to be processed from the node to be issued to the node to be processed, and cannot drag it to other workflow nodes, thereby achieving precise control over business workflow permissions and improving the granularity of permission configuration.

[0079] According to embodiments of this disclosure, when a target user completes processing a target workflow dashboard, the target workflow dashboard can be transferred from a target node to a target transfer node in response to the target user's drag-and-drop operation.

[0080] According to embodiments of this disclosure, a visual application building method is achieved through drag-and-drop. When developing applications on a low-code platform, developers can drag and drop the required UI (User Interface) elements onto the development panel in a fully visual page to form the appearance of the application. Based on the pre-set business logic, drag-and-drop can form application logic, design workflows and business flows, and build relationships in the backend database, thus achieving visual building.

[0081] It should be noted that, unless it is explicitly stated that there is a sequential order of execution between different operations, or that there is a sequential order of execution between different operations in terms of technical implementation, the execution order between multiple operations may not be significant, and multiple operations may be executed simultaneously.

[0082] Figure 5 A block diagram of a permission management apparatus according to an embodiment of the present disclosure is shown schematically.

[0083] like Figure 5 As shown, the permission management device includes a first determination module 510, an acquisition module 520, an allocation module 530, and a configuration module 540.

[0084] The first determination module 510 is used to determine the target node of the target process dashboard in response to the permission configuration request, wherein the permission configuration request carries a target field.

[0085] Module 520 is used to retrieve business forms associated with the target process dashboard from the data warehouse.

[0086] The allocation module 530 is used to allocate tasks to the target process dashboard based on the business form and target fields to determine the target operation user, where the target operation user has user role attributes.

[0087] Configuration module 540 is used to configure the business flow permissions of the target operation user based on the business type and user role attributes of the target process dashboard.

[0088] According to embodiments of this disclosure, a permission management method, apparatus, electronic device, storage medium, and product determine the target node of a target process dashboard in response to a permission configuration request; retrieve related business forms from a data warehouse; determine the operating user based on the target fields carried in the business forms and the permission configuration request; and configure business flow permissions according to the business type of the target process dashboard and the role attributes of the operating user. Because the operating user is determined using the target fields and business forms, and the business flow permissions are determined using the attributes of the target process dashboard and the user's role, the information carried in the permission configuration request and the target process dashboard itself can be fully utilized to automatically redirect the target process dashboard to the user bound in the target fields and configure the permissions that the operating user can possess. This at least partially overcomes the problem of poor flexibility in configuring operating permissions for users of process dashboards in related technologies, thereby achieving the technical effect of improving the efficiency and granularity of permission configuration.

[0089] According to embodiments of this disclosure, the configuration module may further include an acquisition submodule, a first determination submodule, a second determination submodule, and a configuration submodule.

[0090] The Get submodule is used to retrieve process forms associated with the target process dashboard from the data warehouse.

[0091] The first determination submodule is used to determine at least one flow node associated with the target node based on the process form.

[0092] The second determination submodule is used to determine the target flow node from at least one flow node based on the business type and user role attributes to which the target flow dashboard belongs.

[0093] The configuration submodule is used to configure the business flow permissions of the target operation user based on the target flow node.

[0094] According to embodiments of this disclosure, the first determining submodule may further include a first determining unit and a second determining unit.

[0095] The first determining unit is used to determine multiple associated nodes that are associated with the target node from the process form.

[0096] The second determining unit is used to determine, based on business logic relationships, at least one flow node located after the process represented by the target node from multiple associated nodes.

[0097] According to embodiments of this disclosure, the second determining submodule may further include a correction unit, a matching unit, and a third determining unit.

[0098] The correction unit is used to correct the user role attributes based on the business type to which the target process dashboard belongs, so as to obtain the target operation user role attributes.

[0099] The matching unit is used to match the target user role attribute with the node role attribute of at least one flow node to obtain at least one matching result.

[0100] The third determining unit is used to determine the target flow node from at least one flow node based on at least one matching result.

[0101] According to embodiments of this disclosure, the correction unit may further include a first determining subunit, an acquiring subunit, an analyzing subunit, and a correction subunit.

[0102] The first determining subunit is used to determine the target operation user role attribute as the preset user role attribute when the business type to which the target process dashboard belongs is a preset business type.

[0103] The sub-unit is used to retrieve the historical operation records of the target user when the business type of the target process dashboard is not a preset business type.

[0104] The analysis subunit is used to perform statistical analysis on historical operation records and obtain analysis results.

[0105] The correction subunit is used to correct user role attributes based on the analysis results and the business type to which the target process dashboard belongs, so as to obtain the target operation user role attributes.

[0106] According to embodiments of this disclosure, the allocation module may further include an extraction submodule, a third determination submodule, and an allocation submodule.

[0107] The advance submodule is used to extract form data associated with a target field from a business form, where the form data includes at least one user identification information.

[0108] The third determination submodule is used to determine at least one operating user based on at least one user identification information.

[0109] The allocation submodule is used to allocate tasks generated based on the target process dashboard to at least one operator user, in order to determine the target operator user to whom the task is allocated.

[0110] According to embodiments of this disclosure, the access control device may further include a transfer module.

[0111] The flow module is used to transfer the target flow dashboard from the target node to the target flow node in response to the target user's drag and drop operation after the target user has completed the processing of the target flow dashboard.

[0112] Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure, or at least part of the functions of any one or more of them, can be implemented in one module. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be implemented by dividing them into multiple modules. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as hardware circuitry, such as a Field-Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a System-on-Chip, a System-on-a-Substrate, a System-on-Package, an Application-Specific Integrated Circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as computer program modules, which, when run, can perform corresponding functions.

[0113] For example, any plurality of the first determining module 510, obtaining module 520, allocating module 530, and configuring module 540 can be combined into one module / unit / subunit, or any one of these modules / units / subunits can be split into multiple modules / units / subunits. Alternatively, at least part of the functionality of one or more of these modules / units / subunits can be combined with at least part of the functionality of other modules / units / subunits and implemented in one module / unit / subunit. According to embodiments of this disclosure, at least one of the first determining module 510, obtaining module 520, allocating module 530, and configuring module 540 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any one of the three implementation methods or a suitable combination of any of them. Alternatively, at least one of the first determining module 510, obtaining module 520, allocating module 530, and configuring module 540 may be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0114] It should be noted that the permission management device part in the embodiments of this disclosure corresponds to the permission management method part in the embodiments of this disclosure. For a detailed description of the permission management device part, please refer to the permission management method part, which will not be repeated here.

[0115] Figure 6 A block diagram of an electronic device suitable for implementing a permission management method according to an embodiment of the present disclosure is shown schematically. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0116] like Figure 6 As shown, a computer electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0117] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0118] According to embodiments of this disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0119] According to embodiments of this disclosure, the method flow according to embodiments of this disclosure can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by processor 601, it performs the functions defined in the system of embodiments of this disclosure. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0120] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0121] According to embodiments of this disclosure, the computer-readable storage medium can be a non-volatile computer-readable storage medium. Examples include, but are not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0122] For example, according to embodiments of this disclosure, a computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0123] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods provided in the embodiments of this disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the permission management methods provided in the embodiments of this disclosure.

[0124] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0125] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0126] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0127] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions. Those skilled in the art will understand that the features recited in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not expressly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure may be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0128] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for managing access permissions, comprising: In response to the permission configuration request, the target node of the target process dashboard is determined. The permission configuration request carries a target field. The permission configuration request is a request to configure business flow permissions for personnel handling process business. The process business includes the business of verifying, testing, and putting the developed model or system into application. Retrieve the business forms associated with the target process dashboard from the data warehouse; Based on the business form and the target field, tasks are assigned to the target process dashboard to determine the target user, wherein the target user has a user role attribute, and the target user is automatically set by the process engine based on the user bound to the target field; and Configure the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attributes; The method is applied to low-code platforms; The method further includes: when the business type to which the target process dashboard belongs is a preset business type, determining the target user role attribute as a preset user role attribute; when the business type to which the target process dashboard belongs is not a preset business type, obtaining the historical operation records of the target user; performing statistical analysis on the historical operation records to obtain analysis results; and based on the analysis results and the business type to which the target process dashboard belongs, correcting the user role attribute to obtain the target user role attribute.

2. The method according to claim 1, wherein, The step of configuring the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attributes includes: Retrieve the process form associated with the target process dashboard from the data warehouse; Based on the process form, at least one flow node associated with the target node is determined; Based on the business type of the target process dashboard and the user role attributes, a target flow node is determined from at least one of the flow nodes; and Configure the business flow permissions of the target operation user based on the target flow node.

3. The method according to claim 2, wherein, The step of determining at least one flow node associated with the target node based on the process form includes: Determine multiple associated nodes related to the target node from the process form; and Based on business logic relationships, at least one flow node is determined from among the multiple associated nodes, which is located after the process represented by the target node.

4. The method according to claim 2, wherein, The transfer node has a node role attribute; The step of determining the target flow node from at least one of the flow nodes based on the business type to which the target flow dashboard belongs and the user role attribute includes: Based on the business type to which the target process dashboard belongs, the user role attributes are modified to obtain the target operation user role attributes; The target user role attribute is matched with the node role attribute of at least one of the flow nodes to obtain at least one matching result; and The target transfer node is determined from at least one of the transfer nodes based on at least one of the matching results.

5. The method according to claim 1, wherein, The step of assigning tasks to the target process dashboard based on the business form and the target field to determine the target user includes: Based on the target field, form data associated with the target field is extracted from the business form, wherein the form data includes at least one user identification information; Based on at least one of the aforementioned user identification information, at least one operating user is identified; and The tasks generated based on the target process dashboard are assigned to at least one of the operation users to determine the target operation user to whom the task is assigned.

6. The method according to claim 2, further comprising: When the target user completes processing the target process dashboard, in response to the target user's drag-and-drop operation, the target process dashboard is transferred from the target node to the target transfer node.

7. An access control device, comprising: The first determination module is used to determine the target node of the target process dashboard in response to the permission configuration request. The permission configuration request carries a target field. The permission configuration request is a request to configure business flow permissions for personnel handling process business. The process business includes the business of verifying, testing, and putting the developed model or system into application. The acquisition module is used to retrieve business forms associated with the target process dashboard from the data warehouse; The allocation module is used to allocate tasks to the target process dashboard based on the business form and the target field, in order to determine the target operation user, wherein the target operation user has a user role attribute, and the target operation user is obtained by the process engine automatically setting the user bound to the target field; and The configuration module is used to configure the business flow permissions of the target operation user based on the business type to which the target process dashboard belongs and the user role attributes; The device is applied to a low-code platform; The configuration module includes a correction unit, which includes: The first determining subunit is used to determine the target operation user role attribute as the preset user role attribute when the business type to which the target process dashboard belongs is a preset business type. The acquisition subunit is used to acquire the historical operation records of the target user when the business type to which the target process dashboard belongs is not a preset business type. The analysis subunit is used to perform statistical analysis on the historical operation records and obtain analysis results. The correction subunit is used to correct the user role attributes based on the analysis results and the business type to which the target process dashboard belongs, so as to obtain the target operation user role attributes.

8. An electronic device, comprising: One or more processors; Memory, used to store one or more instructions. When the one or more instructions are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method of any one of claims 1 to 6.

9. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 6.

10. A computer program product comprising computer-executable instructions, which, when executed, are used to implement the method of any one of claims 1 to 6.

Citation Information

Patent Citations

  • Workflow-based to-do list processor matching method and processing system

    CN113919757A