Workflow cross-tenant circulation method and system, terminal and storage medium

Abstract

The invention relates to the technical field of servers, and particularly provides a workflow cross-tenant circulation method and system, a terminal and a storage medium, and the method comprises the steps: creating a workflow handling role and a permission corresponding to the role, and mapping the permission of the role to users of a plurality of tenants; roles and circulation rules among the tasks are distributed to all levels of tasks of the workflow; and querying the user matched with the role of the target task by querying the role of the user of each tenant, and pushing the target task to the corresponding node. According to the invention, cross-tenant workflow circulation is realized.

Description

Technical Field

[0001] The present invention belongs to the field of server technology, and in particular relates to a workflow cross-tenant flow method, system, terminal and storage medium. Background Art

[0002] Workflow refers to the automation of part or all of a business process in a computer application environment. It is an abstract and general description of the workflow and the business rules between its various operation steps. In computers, workflow is part of computer-supported collaborative work (CSCW). The latter generally studies how a group can achieve collaborative work with the help of computers.

[0003] In current Web development, workflows have been widely used in the development field, and workflows are also widely used in many multi-tenant systems. However, the rule management and use of workflows are restricted by multi-tenant systems, resulting in the process being able to flow only under one tenant. In many systems, users who use a process may exist in different tenants, so many systems choose to let users create accounts in different tenants to use workflows, which results in a poor user experience. Summary of the invention

[0004] In view of the above-mentioned deficiencies in the prior art, the present invention provides a workflow cross-tenant flow method, system, terminal and storage medium to solve the above-mentioned technical problems.

[0005] In a first aspect, the present invention provides a workflow cross-tenant transfer method, comprising: Create workflow management roles and their corresponding permissions, and map the permissions of the roles to users in multiple tenants; Assign roles to tasks at each level of the workflow, as well as flow rules between tasks; By querying the roles of users of each tenant, users matching the roles of the target task are queried, and the target task is pushed to the corresponding node.

[0006] In an optional implementation, a workflow processing role and permissions corresponding to the role are created, and the permissions of the role are mapped to users of multiple tenants, including: According to workflow requirements, create corresponding roles in the authority management system, including role names and description information; Assign specific operation permissions to each role, including viewing, editing or approving; Maintain tenant information and user information under the tenant in the tenant management system. The tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; In the permission management system, map roles to tenant users; The mapping relationship between roles and users under the tenant is synchronized to the business system through the interface.

[0007] In an optional implementation, the roles are assigned to the tasks at each level of the workflow, and the flow rules between the tasks include: Parse the task sequence of the workflow and assign roles to each task in the task sequence; Analyze whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, no flow rules are added between the adjacent tasks. If the roles of adjacent tasks are different, flow rules are added between the adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

[0008] In an optional implementation, by querying the roles of users of each tenant, querying users matching the roles of the target task, and pushing the target task to the corresponding node, the method includes: Confirm that the current task execution completion status meets the flow triggering conditions, and obtain the role restriction information of the subordinate tasks; Extracting a target role from the role restriction information, and querying user information having a mapping relationship with the target role, wherein the user information includes a tenant to which the user belongs; The target node to which the corresponding tenant belongs is determined based on the user information, and the subordinate task is pushed to the target node.

[0009] In a second aspect, the present invention provides a workflow cross-tenant transfer system, comprising: The role management module is used to create workflow processing roles and the corresponding permissions of the roles, and map the permissions of the roles to users of multiple tenants; A flow configuration module, used to assign roles to tasks at all levels of the workflow, as well as flow rules between tasks; The flow execution module is used to query the roles of users of each tenant, query users matching the roles of the target tasks, and push the target tasks to the corresponding nodes.

[0010] In an optional implementation, the role management module includes: A role creation unit, used to create a corresponding role in the authority management system according to workflow requirements, wherein the role includes a role name and description information; A permission allocation unit, used to allocate specific operation permissions to each role, wherein the operation permissions include viewing, editing or approving; An information maintenance unit, used to maintain tenant information and user information under the tenant in the tenant management system, wherein the tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; The role mapping unit is used to map roles to users of tenants in the permission management system; The information synchronization unit is used to synchronize the mapping relationship between roles and users under the tenant to the business system through the interface.

[0011] In an optional implementation, the flow configuration module includes: A task parsing unit, used to parse the task sequence of the workflow and assign a role to each task in the task sequence; A rule adding unit is used to analyze whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, no flow rules are added between the adjacent tasks. If the roles of adjacent tasks are different, flow rules are added between the adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

[0012] In an optional implementation, the flow execution module includes: A trigger judgment unit is used to confirm that the current task execution completion status meets the flow triggering condition and obtain the role restriction information of the subordinate task; A role query unit, configured to extract a target role from the role restriction information, and query user information having a mapping relationship with the target role, wherein the user information includes a tenant to which the user belongs; The task pushing unit is used to determine the target node to which the corresponding tenant belongs based on the user information, and push the subordinate task to the target node.

[0013] In a third aspect, a terminal is provided, including: processor, memory, wherein: The memory is used to store computer programs. The processor is used to call and run the computer program from the memory, so that the terminal executes the above-mentioned terminal method.

[0014] According to a fourth aspect, a computer storage medium is provided, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the methods described in the above aspects.

[0015] The beneficial effects of the present invention lie in that the workflow cross-tenant flow method, system, terminal and storage medium provided by the present invention use an independent workflow service to access the multi-tenant system, so that the workflow will not be affected by the multi-tenant system and can be circulated. At the same time, the workflow flow roles are synchronized to different tenants to ensure that users can normally receive the workflow processing tasks, thereby realizing cross-tenant workflow flow.

[0016] In addition, the invention has a reliable design principle, a simple structure and a very broad application prospect. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention.

[0019] Figure 2 is another schematic flow chart of a method according to an embodiment of the present invention.

[0020] Figure 3 is a schematic block diagram of a system according to an embodiment of the present invention.

[0021] Figure 4 A schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0024] The workflow cross-tenant transfer method provided in the embodiment of the present invention is executed by a computer device, and accordingly, the workflow cross-tenant transfer system runs in the computer device.

[0025] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention. Figure 1 The execution subject can be a workflow cross-tenant flow system. According to different requirements, the order of the steps in the flowchart can be changed, and some can be omitted.

[0026] like Figure 1 As shown, the method includes: Step 110: Create a workflow processing role and the permissions corresponding to the role, and map the permissions of the role to users of multiple tenants; Step 120, assigning roles to tasks at each level of the workflow, as well as flow rules between tasks; Step 130 , by querying the roles of users of each tenant, querying users matching the roles of the target task, and pushing the target task to the corresponding node.

[0027] To facilitate understanding of the present invention, the workflow cross-tenant flow method provided by the present invention is further described below based on the principle of the workflow cross-tenant flow method of the present invention and the process of transferring workflows across tenants in the embodiment.

[0028] For details, please refer to Figure 2 , the workflow cross-tenant flow methods include: S1. Create workflow management roles and the corresponding permissions for the roles, and map the permissions of the roles to users in multiple tenants.

[0029] According to workflow requirements, corresponding roles are created in the permission management system, and the roles include role names and description information; specific operation permissions are assigned to each role, and the operation permissions include viewing, editing or approving; tenant information and user information under the tenant are maintained in the tenant management system, and the tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; in the permission management system, roles are mapped to tenant users; the mapping relationship between roles and tenant users is synchronized to the business system through an interface.

[0030] Specifically, the process includes the following: 1. Demand analysis and planning Clarify workflow requirements: First, deeply understand business requirements, clarify which business processes require permission control, and the different types of operations involved in these processes (such as viewing, editing, approval, etc.).

[0031] Design permission model: Based on demand analysis, design a flexible permission management model to ensure that it covers all necessary permission control scenarios and reserve expansion space to cope with possible changes in future requirements.

[0032] 2. Role creation and management Define roles: In the permission management system, create corresponding roles according to business needs. Each role should have a unique role name and clear description information for easy understanding and maintenance.

[0033] Role hierarchy and inheritance: Consider implementing role hierarchy and permission inheritance mechanism, allowing high-level roles to inherit permissions from low-level roles, reducing duplication of permission configuration and improving management efficiency.

[0034] Dynamic adjustment: Provides interface or API support to allow administrators to dynamically adjust roles and their permissions based on changes in business needs.

[0035] 3. Permission allocation Fine-grained permission control: Assign specific operation permissions to each role to ensure that permission allocation is neither too broad nor too strict, and achieve precise permission control.

[0036] Permission combination: supports the combined allocation of permissions, that is, a role can have a combination of multiple operation permissions to meet the needs of complex business scenarios.

[0037] Permission review: Introduce an audit mechanism in the permission allocation process to ensure the rationality and security of permission allocation.

[0038] 4. Tenant and User Management Tenant information management: In the tenant management system, basic information of each tenant is maintained, including tenant name, unique ID, industry, etc. It supports the addition, deletion, modification and query of tenant information, and ensures the accuracy and consistency of data.

[0039] User information management: Assign a unique username and password to each tenant user, and record the user's tenant information. Supports batch import and export of user information, password reset and other functions.

[0040] User-tenant association: Ensure that the association between users and tenants is clear and unambiguous to facilitate subsequent role mapping and permission control.

[0041] 5. Role mapping and synchronization Role mapping: In the permission management system, the defined roles are mapped to specific users under the tenant. Both batch mapping and single mapping are supported to meet the needs of different scenarios.

[0042] Mapping relationship verification: Strict verification is performed during the mapping process to ensure the correctness and rationality of the mapping relationship. For example, check whether the user belongs to the specified tenant, whether the role already exists, etc.

[0043] Interface synchronization: The mapping relationship between roles and users under tenants is synchronized to the business system through a standardized interface. This ensures that the business system can obtain the latest permission information in real time and control user operations based on this information.

[0044] Synchronization monitoring and logging: Establish a synchronization monitoring mechanism to record key information during the synchronization process (such as synchronization time, synchronization results, etc.), and promptly issue an alarm when a problem occurs. At the same time, retain detailed synchronization logs for subsequent troubleshooting and auditing.

[0045] 6. Security and Compliance Data encryption: Sensitive information (such as user passwords, tenant IDs, etc.) is encrypted for storage and transmission to ensure data security.

[0046] Access control: Implement strict access control policies to ensure that only authorized users can access the permission management system and tenant management system.

[0047] Compliance check: Conduct compliance checks regularly to ensure that the rights management system complies with the requirements of relevant laws, regulations and industry standards.

[0048] S2. Assign roles to tasks at each level of the workflow, as well as flow rules between tasks.

[0049] Parse the task sequence of the workflow and assign roles to each task in the task sequence; parse whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, do not add flow rules between adjacent tasks. If the roles of adjacent tasks are different, add flow rules between adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

[0050] Specifically, the process includes the following: 1. Parse the task sequence of the workflow Task definition: First, define each task in the workflow, including the task name, description, execution logic, etc. These tasks constitute the basic framework of the workflow.

[0051] Task sequencing: According to the requirements of business logic and workflow, tasks are arranged into a task sequence in a certain order. This sequence defines the order in which tasks are executed.

[0052] 2. Assign roles to each task in the task sequence Role matching: According to the nature and responsibilities of each task, one or more appropriate roles are assigned to it. These roles should have the capabilities and permissions required to complete the task.

[0053] Role Description: Provide detailed description information for each assigned role, including the role's responsibilities, scope of authority, required skills, etc., to facilitate understanding and maintenance.

[0054] Role verification: Verify the rationality and completeness of role assignments, ensure that each task has a clear responsible entity, and that each role has sufficient authority and capabilities to complete its assigned tasks.

[0055] 3. Analyze whether the roles of adjacent tasks are the same Role comparison: Traverse the task sequence and compare the roles assigned to adjacent tasks one by one. Comparison is done by unique identifiers such as role name or role ID.

[0056] Role difference identification: For adjacent tasks, if their roles are different, this difference is identified. This difference may mean that the flow between tasks needs specific rules or conditions to control.

[0057] 4. Set circulation rules according to role differences Flow trigger conditions: For adjacent tasks with different roles, set flow trigger conditions. These conditions define when to flow from one task to the next. Trigger conditions can be based on a variety of factors, such as task completion status, time conditions, external events, etc.

[0058] Role restriction information for subordinate tasks: In the flow rules, clearly specify the role restriction information for subordinate tasks. This includes which roles are eligible to receive and execute the task, as well as any restrictions or constraints that these roles may be subject to when executing the task.

[0059] Rule verification and adjustment: After setting the flow rules, verification is performed to ensure the correctness and effectiveness of the rules. Based on the verification results, the rules may need to be adjusted or optimized to meet business needs and the actual operation of the workflow.

[0060] 5. Integration and testing Rule integration: Integrate all task assignment information, role descriptions, flow trigger conditions, and subordinate task role restriction information into the workflow management system.

[0061] System testing: After the integration is complete, system testing is performed to verify the correctness and smoothness of the workflow. Testing should include multiple levels such as unit testing, integration testing, and end-to-end testing to ensure that all components and rules work as expected.

[0062] User training: Train system users to understand new workflow processes and role assignments, and how to use the system to perform and manage workflow tasks.

[0063] Through the above steps, the task sequence of the workflow can be effectively parsed and appropriate roles can be assigned to the tasks. At the same time, reasonable flow rules can be set according to the role differences to ensure that the workflow can run smoothly according to the predetermined business process.

[0064] S3. By querying the roles of users of each tenant, querying users who match the roles of the target task, and pushing the target task to the corresponding node.

[0065] Confirm that the current task execution completion status meets the flow trigger condition, and obtain the role restriction information of the subordinate task; extract the target role from the role restriction information, and query the user information that has a mapping relationship with the target role, wherein the user information includes the tenant to which the user belongs; determine the target node to which the corresponding tenant belongs based on the user information, and push the subordinate task to the target node.

[0066] Specifically, the process includes the following: 1. Confirm the completion status of the current task Status Check: First, the system needs to periodically check or receive notifications from the task executor to confirm the execution status of the current task. This includes checking whether the task has been completed, whether an error has been encountered, or whether additional input is required.

[0067] Condition matching: Match the current task status with the preset flow trigger conditions. These conditions may include task completion, arrival at a specific time point, triggering of external events, etc.

[0068] Exception handling: If the status of the current task does not meet the flow trigger conditions, the system should be able to identify and handle the exception, such as sending notifications to relevant personnel, recording error logs, or performing rollback operations.

[0069] 2. Get role restriction information for lower-level tasks Rule query: Once the current task is confirmed to be transferable, the system needs to query the role restriction information associated with the subordinate tasks. This information is usually stored in a database or configuration file and is associated with a specific task or workflow.

[0070] Information parsing: Parse the obtained role restriction information to clarify which roles are eligible to receive and perform subordinate tasks. This may include unique identifiers such as role name, role ID, role type, etc.

[0071] 3. Extract the target role and query user information Role screening: Extract target roles from role restriction information, that is, those roles that are qualified to receive and perform subordinate tasks.

[0072] User mapping: Use the mapping relationship between roles and users (this mapping is stored in the user management system) to query the user information that has a mapping relationship with the target role. This information usually includes user name, user ID, tenant, etc.

[0073] Tenant identification: Pay special attention to the tenant field in the user information, as this will determine to which target node the subordinate task should be pushed.

[0074] 4. Determine the target node and push the task Node location: Based on the tenant identified in the user information, the system needs to identify the target node to which the tenant belongs. This may require querying the tenant management system or node mapping table to obtain the specific information of the node (such as IP address, port number, etc.).

[0075] Task push: Encapsulate subordinate tasks and their related information (such as task description, execution parameters, etc.) into messages or task objects, and push them to the target node through appropriate communication protocols (such as HTTP, AMQP, etc.).

[0076] Confirmation and feedback: After receiving the task, the target node should be able to confirm receipt and possibly return the execution result or status update. The system should be able to process these feedbacks and perform subsequent operations as needed (such as updating task status, sending notifications, etc.).

[0077] 5. Monitoring and logging Task monitoring: During the entire task flow process, the system should be able to monitor the execution status and progress of the task in order to promptly discover and handle potential problems.

[0078] Log records: Record key information during the task flow in detail (such as task status changes, flow trigger conditions, user information, node information, etc.) to facilitate subsequent problem troubleshooting and auditing.

[0079] By expanding the above steps, we can have a more comprehensive understanding of each link in the task flow process and ensure that the task can flow smoothly to the next executor according to the predetermined rules and conditions.

[0080] In some embodiments, the workflow inter-tenant transfer system may include multiple functional modules composed of computer program segments. The computer programs of each program segment in the workflow inter-tenant transfer system may be stored in a memory of a computer device and executed by at least one processor to perform (see Figure 1 Description) Function that enables workflows to flow across tenants.

[0081] In this embodiment, the workflow inter-tenant transfer system can be divided into multiple functional modules according to the functions it performs, such as Figure 3As shown. The functional modules of the system 300 may include: a role management module 310, a flow configuration module 320 and a flow execution module 330. The module referred to in the present invention refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, which are stored in a memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.

[0082] The role management module is used to create workflow processing roles and the corresponding permissions of the roles, and map the permissions of the roles to users of multiple tenants; A flow configuration module, used to assign roles to tasks at all levels of the workflow, as well as flow rules between tasks; The flow execution module is used to query the roles of users of each tenant, query users matching the roles of the target tasks, and push the target tasks to the corresponding nodes.

[0083] Optionally, as an embodiment of the present invention, the role management module includes: A role creation unit, used to create a corresponding role in the authority management system according to workflow requirements, wherein the role includes a role name and description information; A permission allocation unit, used to allocate specific operation permissions to each role, wherein the operation permissions include viewing, editing or approving; An information maintenance unit, used to maintain tenant information and user information under the tenant in the tenant management system, wherein the tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; The role mapping unit is used to map roles to users of tenants in the permission management system; The information synchronization unit is used to synchronize the mapping relationship between roles and users under the tenant to the business system through the interface.

[0084] Optionally, as an embodiment of the present invention, the flow configuration module includes: A task parsing unit, used to parse the task sequence of the workflow and assign a role to each task in the task sequence; A rule adding unit is used to analyze whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, no flow rules are added between the adjacent tasks. If the roles of adjacent tasks are different, flow rules are added between the adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

[0085] Optionally, as an embodiment of the present invention, the flow execution module includes: A trigger judgment unit is used to confirm that the current task execution completion status meets the flow triggering condition and obtain the role restriction information of the subordinate task; A role query unit, configured to extract a target role from the role restriction information, and query user information having a mapping relationship with the target role, wherein the user information includes a tenant to which the user belongs; The task pushing unit is used to determine the target node to which the corresponding tenant belongs based on the user information, and push the subordinate task to the target node.

[0086] Figure 4 The present invention is a schematic diagram of the structure of a terminal 400 provided in an embodiment of the present invention. The terminal 400 can be used to execute the workflow cross-tenant transfer method provided in an embodiment of the present invention.

[0087] The terminal 400 may include: a processor 410, a memory 420 and a communication unit 430. These components communicate via one or more buses. Those skilled in the art will appreciate that the server structure shown in the figure does not limit the present invention, and it may be a bus structure or a star structure, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0088] The memory 420 can be used to store the execution instructions of the processor 410, and the memory 420 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. When the execution instructions in the memory 420 are executed by the processor 410, the terminal 400 can perform some or all of the steps in the following method embodiments.

[0089] The processor 410 is the control center of the storage terminal, and uses various interfaces and lines to connect various parts of the entire electronic terminal. It runs or executes software programs and / or modules stored in the memory 420, and calls data stored in the memory to perform various functions of the electronic terminal and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of multiple packaged ICs with the same or different functions. For example, the processor 410 can include only a central processing unit (CPU). In the embodiment of the present invention, the CPU can be a single computing core or multiple computing cores.

[0090] The communication unit 430 is used to establish a communication channel so that the storage terminal can communicate with other terminals, receive user data sent by other terminals or send user data to other terminals.

[0091] The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).

[0092] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention, in essence or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes, including several instructions for enabling a computer terminal (which can be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the methods described in each embodiment of the present invention.

[0093] In this specification, the same or similar parts between the various embodiments can be referred to each other. In particular, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description in the method embodiment.

[0094] In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system 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 through some interfaces, indirect coupling or communication connection of systems or modules, which can be electrical, mechanical or other forms.

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

[0096] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0097] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.

Claims

1. A workflow cross-tenant transfer method, characterized in that: include: Create workflow management roles and their corresponding permissions, and map the permissions of the roles to users in multiple tenants; Assign roles to tasks at each level of the workflow, as well as flow rules between tasks; By querying the roles of users of each tenant, users matching the roles of the target task are queried, and the target task is pushed to the corresponding node.

2. The method according to claim 1, characterized in that Create workflow management roles and their corresponding permissions, and map the permissions of the roles to users in multiple tenants, including: According to workflow requirements, create corresponding roles in the authority management system, including role names and description information; Assign specific operation permissions to each role, including viewing, editing or approving; Maintain tenant information and user information under the tenant in the tenant management system. The tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; In the permission management system, map roles to tenant users; The mapping relationship between roles and users under the tenant is synchronized to the business system through the interface.

3. The method according to claim 1, characterized in that Assign roles to tasks at each level of the workflow, as well as flow rules between tasks, including: Parse the task sequence of the workflow and assign roles to each task in the task sequence; Analyze whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, no flow rules are added between the adjacent tasks. If the roles of adjacent tasks are different, flow rules are added between the adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

4. The method according to claim 3, characterized in that By querying the roles of users of each tenant, querying users matching the roles of the target task, and pushing the target task to the corresponding node, including: Confirm that the current task execution completion status meets the flow triggering conditions, and obtain the role restriction information of the subordinate tasks; Extracting a target role from the role restriction information, and querying user information having a mapping relationship with the target role, wherein the user information includes a tenant to which the user belongs; The target node to which the corresponding tenant belongs is determined based on the user information, and the subordinate task is pushed to the target node.

5. A workflow cross-tenant transfer system, characterized in that: include: The role management module is used to create workflow processing roles and the corresponding permissions of the roles, and map the permissions of the roles to users of multiple tenants; A flow configuration module, used to assign roles to tasks at all levels of the workflow, as well as flow rules between tasks; The flow execution module is used to query the roles of users of each tenant, query users matching the roles of the target tasks, and push the target tasks to the corresponding nodes.

6. The system according to claim 5, characterized in that The role management module includes: A role creation unit, used to create a corresponding role in the authority management system according to workflow requirements, wherein the role includes a role name and description information; A permission allocation unit, used to allocate specific operation permissions to each role, wherein the operation permissions include viewing, editing or approving; An information maintenance unit, used to maintain tenant information and user information under the tenant in the tenant management system, wherein the tenant information includes tenant name, ID, and industry; the user information includes user name, password, and tenant; The role mapping unit is used to map roles to users of tenants in the permission management system; The information synchronization unit is used to synchronize the mapping relationship between roles and users under the tenant to the business system through the interface.

7. The system according to claim 5, characterized in that The flow configuration module includes: A task parsing unit, used to parse the task sequence of the workflow and assign a role to each task in the task sequence; A rule adding unit is used to analyze whether the roles of adjacent tasks are the same. If the roles of adjacent tasks are the same, no flow rules are added between the adjacent tasks. If the roles of adjacent tasks are different, flow rules are added between the adjacent tasks. The flow rules include flow trigger conditions and role restriction information of subordinate tasks.

8. The system according to claim 7, characterized in that The flow execution module includes: A trigger judgment unit is used to confirm that the current task execution completion status meets the flow triggering condition and obtain the role restriction information of the subordinate task; A role query unit, configured to extract a target role from the role restriction information, and query user information having a mapping relationship with the target role, wherein the user information includes a tenant to which the user belongs; The task pushing unit is used to determine the target node to which the corresponding tenant belongs based on the user information, and push the subordinate task to the target node.

9. A terminal, characterized in that: include: Storage, used to store workflow cross-tenant transfer programs; A processor is used to implement the steps of the workflow cross-tenant flow method as described in any one of claims 1 to 4 when executing the workflow cross-tenant flow program.

10. A computer-readable storage medium storing a computer program, characterized in that: The readable storage medium stores a workflow cross-tenant flow program, and when the workflow cross-tenant flow program is executed by the processor, the steps of the workflow cross-tenant flow method according to any one of claims 1 to 4 are implemented.

Images