User management method and device in business process, electronic equipment and readable medium

Abstract

The invention relates to a user management method and device in a business process, electronic equipment and a readable medium, and the method comprises the steps: creating a user group for each business node in the business process; performing association configuration on the service nodes and the user group which have the corresponding relationship, so that the users in the user group have the service authority of the service nodes; and when the business demand of any node in the business process changes, adjusting the user group of any node according to the change content of the business demand so as to manage the users in the business process. According to the technical scheme, the service nodes are associated with the user groups, so that adjustment of the service nodes or change of the users can be realized directly by adjusting the user groups, batch management is performed on the users through the user groups, and the problem that the users in the service process are difficult to simply and quickly manage is solved.

Description

Technical Field

[0001] The present application relates to the technical field of business scenario management, and in particular to a method, device, electronic device and readable medium for user management in a business process. Background Art

[0002] In a business process, each node may involve multiple users, who may play different roles, have different permissions and responsibilities. Users and user permissions are usually configured in advance for each node in the business process. However, due to personnel turnover and business changes, it is necessary to change the permissions of a certain user. In this case, not only the user permissions need to be modified, but also the business links bound to the user need to be found one by one, and then the user configuration of these business links needs to be modified. This processing method will result in a very large and inefficient workload for user management. Once the number of personnel to be changed increases, the entire change process will become extremely complicated, making it difficult to manage users in the business process simply and quickly.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The present application provides a method, device, electronic device and readable medium for user management in a business process to solve the above-mentioned technical problem of "difficulty in simply and quickly managing users in a business process".

[0005] According to one aspect of an embodiment of the present application, the present application provides a user management method in a business process, including: creating a user group for each business node in the business process; associating and configuring the business nodes with corresponding relationships with the user groups so that users in the user groups have business permissions of the business nodes; when the business requirements of any node in the business process change, the user group of any node is adjusted according to the changes in the business requirements to manage the users in the business process.

[0006] Optionally, a user group is created for each business node in the business process, including: displaying a new user group creation interface, and using information received through the new user group creation interface as user group information of the user group; displaying a user allocation interface, and adding the user selected by the target object in the user allocation interface to the user group; and displaying each created user group in the user group management interface to complete the creation of user groups for each business node.

[0007] Optionally, after creating the user group, the method also includes: when it is detected that the authorization control of any user group on the user group management interface is triggered, displaying the role allocation interface of any user group; obtaining the target role selected by the target object through the role allocation interface; authorizing the role permissions of the target role to any user group to perform batch authorization on each user in any user group.

[0008] Optionally, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to increase the number of approval personnel at any node, then determining the users to be added to any node; displaying the user allocation interface of the first user group associated with any node in the user group management interface; adding the users to be added to the first user group through the user allocation interface to complete the addition of approval personnel on any node.

[0009] Optionally, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to reduce the number of approvers at any node, determining the users to be deleted from any node; displaying the user allocation interface of the second user group associated with any node on the user group management interface; deleting the users to be deleted from the second user group through the user allocation interface to complete the reduction of approvers on any node.

[0010] Optionally, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to change the approval personnel of any node, then determining the users to be changed on any node corresponding to the changes, wherein the users to be changed include users to be removed and users to be added; displaying the user allocation interface of the third user group associated with any node on the user group management interface; deleting the users to be removed from the third user group through the user allocation interface, and adding the users to be added to the third user group, so as to complete the change of the approval personnel on any node.

[0011] Optionally, after associating and configuring the business nodes with corresponding relationships with the user groups, the method further includes: when the approval process flows to the target node, determining the target user group associated with the target node; sending the approval process to each user in the target user group so that each user in the target user group can process the approval process.

[0012] According to another aspect of an embodiment of the present application, the present application provides a user management device in a business process, including: a creation module, used to create a user group for each business node in the business process; an association module, used to associate and configure business nodes with corresponding relationships with user groups so that users in the user group have business permissions of the business nodes; a management module, used to adjust the user group of any node in the business process according to the changes in the business needs when the business needs of any node in the business process change, so as to manage the users in the business process.

[0013] According to another aspect of an embodiment of the present application, the present application provides an electronic device, including a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, the memory and the processor communicate through the communication bus and the communication interface, and the steps of the above method are implemented when the processor executes the computer program.

[0014] According to another aspect of an embodiment of the present application, the present application also provides a computer-readable medium having a non-volatile program code executable by a processor, and the program code enables the processor to execute the above method.

[0015] The above technical solution provided by the embodiment of the present application has the following advantages compared with the related art:

[0016] The present application adopts a user management method in a business process, including: creating a user group for each business node in the business process; associating and configuring the business nodes with corresponding relationships with the user group so that the users in the user group have the business permissions of the business node; when the business requirements of any node in the business process change, the user group of any node is adjusted according to the changes in the business requirements to manage the users in the business process. By associating the business node with the user group, whether it is the adjustment of the business node or the change of the user, it can be achieved directly by adjusting the user group, so that users can be managed in batches through the user group, solving the problem of difficulty in simply and quickly managing users in the business process. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 A flowchart of a user management method in an optional business process provided according to an embodiment of the present application;

[0020] Figure 2 An optional user group creation interface provided according to an embodiment of the present application;

[0021] Figure 3 An optional user allocation interface provided according to an embodiment of the present application;

[0022] Figure 4 A schematic diagram of adding users to an optional user group provided according to an embodiment of the present application;

[0023] Figure 5 A schematic diagram of role authorization for an optional user group provided according to an embodiment of the present application;

[0024] Figure 6 A block diagram of a user management device in an optional business process provided according to an embodiment of the present application;

[0025] Figure 7 A schematic diagram of an optional electronic device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are 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 this application.

[0027] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application and have no specific meaning. Therefore, "module" and "component" can be used interchangeably.

[0028] In a business process, each node may involve multiple users, who may play different roles, have different permissions and responsibilities. Users and user permissions are usually configured in advance for each node in the business process. However, due to personnel turnover and business changes, it is necessary to change the permissions of a certain user. In this case, not only the user permissions need to be modified, but also the business links bound to the user need to be found one by one, and then the user configuration of these business links needs to be modified. This processing method will result in a very large and inefficient workload for user management. Once the number of personnel to be changed increases, the entire change process will become extremely complicated, making it difficult to manage users in the business process simply and quickly.

[0029] In order to solve the problems mentioned in the background technology, according to one aspect of the embodiments of the present application, an embodiment of a user management method in a business process is provided, such as Figure 1 As shown, including:

[0030] Step 101, creating a user group for each service node in the service process;

[0031] Step 103, associating and configuring the corresponding service nodes with the user groups so that the users in the user groups have the service rights of the service nodes;

[0032] Step 105 , when the business demand of any node in the business process changes, the user group of any node is adjusted according to the changed content of the business demand to manage the users in the business process.

[0033] This application can be applied to various business scenarios for user management.

[0034] First, establish a corresponding user group for each business node according to business needs (you can also establish multiple user groups in advance without considering business needs), and then associate the corresponding business nodes with the user groups. At this time, users in the user group can approve the approval process of the corresponding node, ensuring that users in the user group can operate the relevant business nodes.

[0035] When the business requirements of any node in the business process change, the users in the user group are adjusted according to the changes, rather than directly locating individual users to adjust various business permissions. This flexible user management method allows user permissions to be dynamically updated to adapt to changes in business processes and personnel changes.

[0036] As an optional embodiment, a user group is created for each business node in a business process, including: displaying a new user group creation interface, and using information received through the new user group creation interface as user group information of the user group; displaying a user allocation interface, and adding the user selected by the target object in the user allocation interface to the user group; and displaying each created user group in the user group management interface to complete the creation of user groups for each business node.

[0037] The target objects can be system administrators, operation and maintenance personnel, and other business-related personnel.

[0038] User group information includes but is not limited to the user group name and user group description (eg, user group purpose, user group description, etc.).

[0039] When it is detected that the user add control on the user group management interface is triggered, the user group creation interface is displayed. The user group creation interface is as follows: Figure 2 As shown, the new user group creation interface includes two editing areas. The target object can fill in the user group information in the two editing areas. The two editing areas in the figure are used to fill in the user group name and description respectively. Among them, the "Description" editing area can receive the user-filled user group purpose or user group description.

[0040] After the target object enters the user group information and saves it, when it is detected that the user allocation control of the user group management interface is triggered, the user allocation interface is displayed. The user allocation interface is as follows Figure 3 As shown, the target object can click the "Add User" control on the user allocation interface, and the list of all users under the organizational structure will be displayed. The target object can select the intended user in the user list to add the user to the user group currently being created. The specific user group user addition diagram is shown in Figure 4 shown.

[0041] If the corresponding user group is only used for personnel approval management in the process configuration, no additional authorization is required. You only need to ensure that the roles to which the users added to the corresponding user group belong have the functional permissions for the corresponding links.

[0042] If the people in the user group need to have other business permissions besides approval, then the users in the user group need to be authorized. The following describes how to authorize users in the user group.

[0043] As an optional embodiment, after creating a user group, the method also includes: when it is detected that the authorization control of any user group on the user group management interface is triggered, displaying the role allocation interface of any user group; obtaining the target role selected by the target object through the role allocation interface; authorizing the role permissions of the target role to any user group to perform batch authorization on each user in any user group.

[0044] This application implements batch authorization for all users in a user group by granting roles to the user group.

[0045] Figure 5 A role authorization diagram for the user group provided for this application, when the authorization control of any user group on the user group management interface is triggered, the corresponding role assignment interface is displayed, and when the add control on the role assignment interface is triggered, the role selection interface is displayed. The target object can select the role that he wants to configure for the user group on the role selection interface, so that the users in the user group have the role permissions of the selected role.

[0046] After batch authorization, users in the user group will be automatically added to the corresponding roles and marked as being added from the corresponding user group; if users are removed through the user group, the users from this user will be removed from the corresponding roles.

[0047] Optionally, the target object can also manage the existing permissions of the current user group in the role assignment interface, and can delete the permissions corresponding to the role possessed by the user group by removing the role.

[0048] It should be noted that each user can also be authorized to a role individually when it is created. Authorizing the user group to which the user belongs will not affect the user's original permissions. The user's original permissions will not affect the user group. The permissions of the user group are redefined according to business needs through the user group function. After the user is in the user group, he only inherits the permissions of the user group. After the user is removed from the user group, the user will be released from the corresponding user group, but it will not affect the user group itself.

[0049] Adding a role to a user group means granting the permissions of the role to each user in the user group, which can achieve unified authorization for batches of users in the user group.

[0050] Specifically, any node of the present application is at least one node among multiple nodes in a business process. The present application can handle business demand changes of multiple nodes. When describing the embodiments below, processing business demand changes of a single node is used as a preferred embodiment. In actual application, the processing method of each node is similar.

[0051] As an optional embodiment, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to increase the number of approval personnel at any node, then determining the users to be added to any node; displaying the user allocation interface of the first user group associated with any node in the user group management interface; adding the users to be added to the first user group through the user allocation interface to complete the addition of approval personnel on any node.

[0052] If the change in business requirements is to add approvers to any node, it means that a new user wants to be added to any node of the business process. The specific user to be added needs to be determined based on the change content, and the identity information, role, and required permissions of the user to be added can be obtained at the same time.

[0053] In the user group management interface, the user allocation interface of the first user group associated with any node is displayed. Through the user allocation interface, the user to be added can be added to the first user group, ensuring that the new user can immediately obtain the corresponding permissions of the business node. The specific user addition steps are similar to the steps of adding users to the user group mentioned above, and will not be repeated here.

[0054] For example, if a new employee is to be added, it is necessary to determine which business links the new user needs to participate in, and then use the user group function to find the user group of the corresponding link (the instructions when creating the user group are designed to facilitate this situation), and add the new user to the corresponding user group.

[0055] Directly add the users to be added to the user group corresponding to the node to ensure that the new users can be quickly added to the business process and have the corresponding operation permissions. This flexible management method helps to improve the efficiency and responsiveness of the business process.

[0056] As an optional embodiment, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to reduce the number of reviewers at any node, determining the users to be deleted from any node; displaying the user allocation interface of the second user group associated with any node in the user group management interface; deleting the users to be deleted from the second user group through the user allocation interface to complete the reduction of reviewers on any node.

[0057] If the change in business requirements is to reduce the number of approvers at any node, indicating that a user needs to be removed from a node in the business process, the specific user to be deleted needs to be determined from the change content.

[0058] In the user group management interface, the system will display the user allocation interface of the second user group associated with any node. The user to be deleted can be removed through the user allocation interface to ensure that the user to be deleted no longer has the permissions corresponding to the user group.

[0059] By executing the above steps to reduce the number of reviewers at any node, the user's permission changes are effectively managed, the security and rationality of the business process are ensured, the user group members are adjusted in time, and the flexibility and efficiency of the overall management are improved.

[0060] As an optional embodiment, the user group of any node is adjusted according to the changes in business needs, including: if the changes in business needs are to change the approval personnel of any node, then determining the users to be changed on any node corresponding to the changes, wherein the users to be changed include users to be removed and users to be added; displaying the user allocation interface of the third user group associated with any node in the user group management interface; deleting the users to be removed from the third user group through the user allocation interface, and adding the users to be added to the third user group, so as to complete the change of the approval personnel on any node.

[0061] If the change in business requirements is to change the approvers of any node, it means that some / single approvers on this node need to be deleted and new approvers need to be added.

[0062] It should be noted that the present application does not limit the order of removing the user to be removed from the third user group and adding the user to be added to the third user group.

[0063] In response to changes in business needs, this application adjusts the original selection and modification of a single user to make changes directly based on the user group. In the business process link, for the management of the processing personnel in each link, by associating the business process link with the user group, when the business flows to this link, it is only necessary to obtain the information of the processing user from the corresponding user group; for the business, what basically does not change is the circulation link and the permissions required for the corresponding link, and what changes is the processor of the circulation link. The processing mode in the prior art is that once the processor changes, it is necessary to find and update all the links bound to the processor, which is a huge workload because the complexity of the business process is higher than that of the user group. After associating with the user group, if there is a change in the processor, it is only necessary to find the user group where the processor is located, and remove or add the user through the function of the user group, which greatly simplifies the user change process.

[0064] As an optional embodiment, after the business nodes with corresponding relationships are associated with the user groups, the method also includes: when the approval process flows to the target node, determining the target user group associated with the target node; sending the approval process to each user in the target user group so that each user in the target user group can process the approval process.

[0065] In the technical solution provided by this application, during the flow of business processes, it is not necessary to consider whether the various reviewers belong to the same department.

[0066] After the target node is associated with the target user group, as long as the approval process flows to the target node, the approval process can be sent to each user in the target user group for approval. Each user in the target user group has the approval authority for the node.

[0067] The present application also provides an embodiment as another optional solution, which can configure the approval personnel of each node to be personnel from the same department as the node initiator.

[0068] Since the users in the user group on each approval node may come from different departments, cross-departmental approval will bring many inconveniences. Therefore, when adjacent approval nodes are transferred, node transfers within the same department are given priority.

[0069] For example, the initiator of the first node is Xiao A, who belongs to the first department. The user group on the next node of the first node involves the first department, the second department and the third department. In this case, the process proposed by Xiao A will be transferred to the approver system of the first department in the user group of the next node, and will not be transferred to the approver system of the second department or the third department.

[0070] For example, in the business process of an actual project, the approvers of different links of the initiators of different departments may need to be screened according to the department where the initiators are located, and the approvers defined by different departments may be customized according to the actual situation, which may have nothing to do with the positions of the personnel themselves. However, this application defines a user group for each process link. After the user group is defined, users with approval authority from different departments are added to the user group. The business side can add the corresponding flow logic in the corresponding link after the process is initiated (that is, users obtained from the user group and the initiator who are in the same department can approve the matter).

[0071] The present application adopts a user management method in a business process, including: creating a user group for each business node in the business process; associating and configuring the business nodes with corresponding relationships with the user group so that the users in the user group have the business permissions of the business node; when the business requirements of any node in the business process change, the user group of any node is adjusted according to the changes in the business requirements to manage the users in the business process. By associating the business node with the user group, whether it is the adjustment of the business node or the change of the user, it can be achieved directly by adjusting the user group, so that users can be managed in batches through the user group, solving the problem of difficulty in simply and quickly managing users in the business process.

[0072] According to another aspect of the embodiment of the present application, the present application provides a user management device in a business process, such as Figure 6 As shown, including:

[0073] A creation module 602 is used to create a user group for each service node in the service process;

[0074] An association module 604 is used to associate and configure the corresponding service nodes with the user groups so that the users in the user groups have the service rights of the service nodes;

[0075] The management module 606 is used to adjust the user group of any node in the business process according to the changed content of the business demand when the business demand of any node in the business process changes, so as to manage the users in the business process.

[0076] It should be noted that the creation module 602 in this embodiment can be used to execute step 101 in the embodiment of the present application, the association module 604 in this embodiment can be used to execute step 103 in the embodiment of the present application, and the management module 606 in this embodiment can be used to execute step 105 in the embodiment of the present application.

[0077] Optionally, the creation module 602 is also used to create user groups for each business node in the business process, including: displaying a new user group creation interface, and using the information received through the new user group creation interface as the user group information of the user group; displaying a user allocation interface, and adding the user selected by the target object in the user allocation interface to the user group; and displaying each created user group in the user group management interface to complete the creation of user groups for each business node.

[0078] Optionally, the creation module 602 is also used to, after the user group is created, display the role assignment interface of any user group when it is detected that the authorization control of any user group on the user group management interface is triggered; obtain the target role selected by the target object through the role assignment interface; and authorize the role permissions of the target role to any user group to perform batch authorization on each user in any user group.

[0079] Optionally, the management module 606 is also used to determine the users to be added to any node if the change in business needs is to add approval personnel to any node; display the user allocation interface of the first user group associated with any node in the user group management interface; add the users to be added to the first user group through the user allocation interface to complete the addition of approval personnel on any node.

[0080] Optionally, the management module 606 is also used to determine the users to be deleted from any node if the change in business needs is to reduce the number of approval personnel at any node; display the user allocation interface of the second user group associated with any node in the user group management interface; and delete the users to be deleted from the second user group through the user allocation interface to complete the reduction of approval personnel on any node.

[0081] Optionally, the management module 606 is also used to determine the users to be changed on any node corresponding to the changed content if the changed business demand is to change the approval personnel of any node, wherein the users to be changed include users to be removed and users to be added; display the user allocation interface of the third user group associated with any node in the user group management interface; delete the users to be removed from the third user group through the user allocation interface, and add the users to be added to the third user group, so as to complete the change of the approval personnel on any node.

[0082] Optionally, the device also includes a processing module for determining a target user group associated with a target node when the approval process flows to a target node after the business nodes with corresponding relationships are associated with user groups; and sending the approval process to each user in the target user group so that each user in the target user group can process the approval process.

[0083] It should be noted here that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.

[0084] According to another aspect of the embodiments of the present application, the present application provides an electronic device, such as Figure 7As shown, it includes a memory 701, a processor 703, a communication interface 705 and a communication bus 707. The memory 701 stores a computer program that can be run on the processor 703. The memory 701 and the processor 703 communicate through the communication interface 705 and the communication bus 707. When the processor 703 executes the computer program, the steps of the above method are implemented.

[0085] The memory and processor in the above electronic device communicate via a communication bus and a communication interface. The communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

[0086] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0087] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0088] According to another aspect of the embodiments of the present application, a computer-readable medium having a non-volatile program code executable by a processor is provided.

[0089] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0090] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.

[0091] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0092] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0093] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0094] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0095] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0096] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0097] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0098] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk. It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0099] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A user management method in a business process, characterized in that: include: Create user groups for each business node in the business process; Associating and configuring the service nodes having corresponding relationships with the user groups so that users in the user groups have service permissions of the service nodes; When the business demand of any node in the business process changes, the user group of the any node is adjusted according to the changed content of the business demand, so as to manage the users in the business process.

2. The method according to claim 1, characterized in that The step of creating a user group for each service node in the service process includes: Displaying a new user group creation interface, and using information received through the new user group creation interface as user group information of the user group; Displaying a user allocation interface, and adding the user selected by the target object in the user allocation interface to the user group; The created user groups are displayed on the user group management interface to complete the creation of the user groups for the service nodes.

3. The method according to claim 2, characterized in that After creating the user group, the method further includes: When it is detected that the authorization control of any user group on the user group management interface is triggered, displaying the role allocation interface of any user group; Acquire the target role selected by the target object through the role allocation interface; The role permissions of the target role are authorized to any one of the user groups, so as to perform batch authorization on each user in any one of the user groups.

4. The method according to claim 1, characterized in that: The adjusting the user group of the arbitrary node according to the change in the business demand includes: If the change in the business requirement is to add an approval officer to the arbitrary node, determine the user to be added to the arbitrary node; Displaying a user allocation interface of a first user group associated with the arbitrary node on a user group management interface; The user to be added is added to the first user group through the user allocation interface to complete the addition of the approval personnel on the arbitrary node.

5. The method according to claim 1, characterized in that The adjusting the user group of the arbitrary node according to the change in the business demand includes: If the change in the business requirement is to reduce the number of reviewers at the arbitrary node, determining the users to be deleted from the arbitrary node; Displaying a user allocation interface of a second user group associated with the arbitrary node on a user group management interface; The user to be deleted is deleted from the second user group through the user allocation interface to complete the reduction of the approval personnel on the arbitrary node.

6. The method according to claim 1, characterized in that The adjusting the user group of the arbitrary node according to the change in the business demand includes: If the changed content of the business requirement is to change the approval personnel of the arbitrary node, then determine the users to be changed on the arbitrary node corresponding to the changed content, wherein the users to be changed include users to be removed and users to be added; Displaying a user allocation interface of a third user group associated with the arbitrary node on a user group management interface; The user to be removed is deleted from the third user group through the user allocation interface, and the user to be added is added to the third user group, so as to complete the change of the approval personnel on the arbitrary node.

7. The method according to claim 1, characterized in that After associating and configuring the service nodes having a corresponding relationship with the user groups, the method further includes: When the approval process flows to a target node, determining a target user group associated with the target node; The approval process is sent to each user in the target user group, so that each user in the target user group can process the approval process.

8. A user management device in a business process, characterized in that: include: The creation module is used to create user groups for each business node in the business process; An association module, used for associating and configuring the service nodes with corresponding relationships with the user groups so that users in the user groups have service permissions of the service nodes; The management module is used to adjust the user group of any node in the business process according to the changed content of the business demand when the business demand of any node in the business process changes, so as to manage the users in the business process.

9. An electronic device, comprising a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer readable medium having a non-volatile program code executable by a processor, characterized in that: The program code enables the processor to execute the method according to any one of claims 1 to 7.

Images