A collaborative management system and method for application business processes based on multi-tenant mode

Abstract

This invention provides an application business process collaborative management system based on a multi-tenant model, including an application module, an application business process stage module, an application business process stage status module, an application object module, an application object collaborative management module, an application permission module, an application business process reorganizer, and a shared database. This method, combined with actual application scenarios, can design business processes that meet requirements in multiple scenarios. Multiple scenario-based business processes within a single application can be collaboratively managed, reducing system switching between different tenant scenarios, improving collaborative management capabilities between tenants, and enhancing the multi-scenario management capabilities of tenant applications. Since applications from different tenants execute within the same system, applications from different tenants can authorize each other, and application object information between application scenarios can be shared, effectively improving the information interaction capabilities within tenant application scenarios.

Description

Technical Field

[0001] This invention relates to the field of business process collaboration management technology, and in particular to an application business process collaboration management system and method based on a multi-tenant model. Background Technology

[0002] Multi-scenario business application collaborative management is a management method that enables multiple people to simultaneously participate in multiple business scenarios while cooperating and dividing tasks to achieve beneficial objectives. The SaaS (Software-as-a-Service) model delivers software via the internet. Users no longer purchase software separately but instead rent web-based software from a provider to manage their internal operations without needing to maintain the software. Multi-tenancy technology is the core technology of SaaS. It enables multiple tenants to simultaneously provide services based on a single software system. Multiple tenants share system instances, allowing for multi-scenario business customization of system application instances while ensuring partial data sharing and isolation of customized components between system applications.

[0003] With the development of SaaS, multi-scenario business collaborative management has also become a software service offered to tenants. Providing multi-scenario business collaborative management in a SaaS model requires addressing the customization of business processes across multiple scenarios for tenant applications, as well as the reorganization of these processes. The method for customizing business processes across multiple scenarios requires classifying similar business types, and different business types should also have different business status types. Tenants can set business types according to their own application scenarios, naming, classifying, and setting business requirement steps, and then naming, classifying, and setting the various business step statuses under each step. The classification of business steps and the classification of business step statuses have certain constraints; additions, modifications, and deletions can be made reasonably within the defined constraints. After customization, users can obtain a complete, multi-scenario collaboratively manageable business process. The application business process reorganizer obtains multi-scenario business process information from shared data, identifies and judges the classification and setting information of business steps, recombines them, and then obtains the business step status information bound to the current business step. After reorganizing the above information, the reorganizer can output the information to the web service for tenant use. This model allows users to quickly develop multi-scenario business processes and continuously verify the correctness, rationality, feasibility, and effectiveness of the restructured processes. This significantly improves the user experience.

[0004] However, the inventors discovered that currently commonly used business process customization methods are generally based on single-scenario premises, providing users with modular business process forms for selection, or using variable point-based business customization methods to collaboratively advance the process step by step. Although these methods can solve collaborative management to some extent, they have obvious shortcomings for multi-scenario business collaborative management: there are many operation pages, the business operation process is complex, multi-scenario business also requires switching business systems, the overall collaborative effect is not ideal, and multi-scenario business processes require users to advance the business synchronously or asynchronously in multiple scenarios, and finally collaboratively complete the entire business process. Summary of the Invention

[0005] In view of this, the purpose of this invention is to propose an application business process collaborative management system and method based on multi-tenant mode, so as to solve the problems of complex business processes and inconvenient operation.

[0006] To achieve the above objectives, this invention provides an application business process collaborative management system based on a multi-tenant model, comprising an application module, an application business process stage module, an application business process stage status module, an application object module, an application object collaborative management module, an application permission module, an application business process reorganizer, and a shared database, wherein:

[0007] The application module is used to create a tenant application model and save the created tenant application model to the application data of the shared database with a form identifier WxappId.

[0008] The application business process module is used to design multi-scenario business process models, process business processes, create business processes and business process instances, and save the designed business process form identifier SchedulesetId to the application data in the shared database.

[0009] The application business process stage status module is used to design business process status models, process business process status, create business process status and business process status instances, and save the designed business process status form identifier as SchedulesetValueId to the status data of the shared database.

[0010] The application object module is used to create and manage business objects, and saves the business objects to the application object table of the shared database with the form identifier OrderId.

[0011] The application object collaborative management module is used to collaboratively manage the creation and modification of business object and business process status data information, and distribute and save it to different types of business data in the shared database in the form of datasets according to different business scenarios;

[0012] The application permission module is used to manage the relationship between tenants and applications, and save the permission data between tenants and applications to the application tenant relationship data in the shared database; it is also used to manage the relationship between applications, and save the permission data between applications to the application permission data in the shared database.

[0013] The application business process reconfigurator is used to retrieve business process and business process status data from a shared database under different scenarios, and output the reconfigured data to the Web client in the form of a data stream; it is also used to retrieve business data of business processes and business process status under different scenarios from shared data, and output the reconfigured data to the Web client in the form of a data stream.

[0014] The shared database is used to store application data, process data, process status data, application tenant relationship data, object data, application permission data, business data, and tenant data.

[0015] As an optional implementation, the business process refactoring device is also used to obtain business steps based on the current application identifier, classify them according to the type of business steps, and output the application business names in order in the form of business sorting.

[0016] As an optional implementation, the business process reorganizer is further configured to obtain business steps based on the current application identifier, classify them according to their type, and generate a business identifier order in the form of business sorting; then, based on the business object identifier, iteratively retrieves the business data of the business steps, matching the corresponding step status identifier to obtain the step status name. After the loop ends, the obtained data is reorganized to obtain the business object and the current step status information of each step.

[0017] As a second aspect of the present invention, an application business process collaborative management method based on a multi-tenant mode is provided. This method is applied to the application business process collaborative management system described above, and includes the following steps:

[0018] Analyze the requirements of the current application's business process steps, construct them in the order of the required business steps, and save them to the shared database in the form of natural language.

[0019] For the possible states of the business process in the current application, perform another state analysis and save the possible state results in the form of natural language to the shared data.

[0020] Configure application-tenant permissions, and then save the application-tenant operation permissions to the shared database.

[0021] Set application permissions to grant data permissions between applications, allowing tenants under an application to query other unrelated applications and view object data through collaborative management of application objects.

[0022] By using the business process refactorer and business data refactorer, business processes and data can be refactored, enabling customization of business processes and monitoring of business data in different scenarios.

[0023] As an optional implementation, the step of performing requirements analysis on the business process steps of the current application, constructing the process according to the order of the required business steps, and saving it to a shared database in natural language format includes:

[0024] When setting up business process steps, describe the step names using appropriate natural language according to the actual business, and then select the appropriate business step type according to the requirements to form the business steps.

[0025] As an optional implementation, the step-by-step analysis is performed again on the possible states of the business process in the current application, and the possible state results are saved in the shared data in the form of natural language, including:

[0026] When setting business process status, describe the status name of the process in appropriate natural language according to the actual status, and then select the appropriate status type according to the requirements to form the business status.

[0027] As an optional implementation, the step of setting application-tenant permissions and saving the application-tenant operation permissions to the shared database after setting them includes:

[0028] Assign operational permissions to other tenants as needed to enable them to collaborate.

[0029] The beneficial effects of this invention are as follows: This invention provides an application business process collaborative management system and method based on a multi-tenant model, including an application module, an application business process stage module, an application business process stage status module, an application object module, an application object collaborative management module, an application permission module, an application business process reorganizer, and a shared database. This method, combined with actual application scenarios, can design business processes that meet requirements in multiple scenarios. Multiple scenario businesses within a single application can achieve collaborative management, reducing system switching between different tenant scenarios, improving collaborative management capabilities between tenants, increasing the multi-scenario management capabilities of tenant applications, and enhancing the system's flexibility in setting up complex application scenarios. Since applications from different tenants execute within the same system, applications from different tenants can authorize each other, and application object information between application scenarios can be shared, effectively improving the information interaction capabilities within tenant application scenarios and significantly reducing operating costs between tenants. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only for this invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is a schematic diagram of an application business process collaborative management system based on a multi-tenant mode according to an embodiment of the present invention;

[0032] Figure 2 This is an application business process diagram of an embodiment of the present invention;

[0033] Figure 3 This is a flowchart illustrating the collaborative management process for application objects in an embodiment of the present invention.

[0034] Figure 4 This is a flowchart illustrating the application service status and tenant permission management process according to an embodiment of the present invention.

[0035] Figure 5 This is a flowchart illustrating the application and inter-application authorization management process in an embodiment of the present invention.

[0036] Figure 6 Customized model diagram for application business processes in embodiments of the present invention;

[0037] Figure 7 This is a business process model diagram based on application business scenarios in an embodiment of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments.

[0039] It should be noted that, unless otherwise defined, the technical or scientific terms used in this invention should have the ordinary meaning understood by one of ordinary skill in the art to which this invention pertains. The terms "first," "second," and similar terms used in this invention do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0040] As one embodiment of the present invention, such as Figure 1 As shown, an application business process collaborative management system based on a multi-tenant model is provided, including an application module, an application business process stage module, an application business process stage status module, an application object module, an application object collaborative management module, an application permission module, an application business process reorganizer, and a shared database, wherein:

[0041] The application module is used to create a tenant application model and save the created tenant application model to the application data of the shared database with a form identifier WxappId.

[0042] The application business process module is used to design multi-scenario business process models, process business processes, create business processes and business process instances, and save the designed business process form identifier SchedulesetId to the application data in the shared database.

[0043] The application business process stage status module is used to design business process status models, process business process status, create business process status and business process status instances, and save the designed business process status form identifier as SchedulesetValueId to the status data of the shared database.

[0044] The application object module is used to create and manage business objects, and saves the business objects to the application object table of the shared database with the form identifier OrderId.

[0045] The application object collaborative management module is used to collaboratively manage the creation and modification of business object and business process status data information, and distribute and save it to different types of business data in the shared database in the form of datasets according to different business scenarios;

[0046] The application permission module is used to manage the relationship between tenants and applications, and save the permission data between tenants and applications to the application tenant relationship data in the shared database; it is also used to manage the relationship between applications, and save the permission data between applications to the application permission data in the shared database.

[0047] The application business process reconfigurator is used to retrieve business process and business process status data from a shared database under different scenarios, and output the reconfigured data to the Web client in the form of a data stream; it is also used to retrieve business data of business processes and business process status under different scenarios from shared data, and output the reconfigured data to the Web client in the form of a data stream.

[0048] The shared database is used to store application data, process data, process status data, application tenant relationship data, object data, application permission data, business data, and tenant data.

[0049] This invention provides an application business process collaborative management system based on a multi-tenant model, including an application module, an application business process stage module, an application business process stage status module, an application object module, an application object collaborative management module, an application permission module, an application business process reorganizer, and a shared database. This method, combined with actual application scenarios, can design business processes that meet requirements in multiple scenarios. Multiple scenario-based business processes within a single application can be collaboratively managed, reducing system switching between different tenant scenarios, improving collaborative management capabilities between tenants, increasing the multi-scenario management capabilities of tenant applications, and enhancing the system's flexibility in configuring complex application scenarios. Since applications from different tenants execute within the same system, applications from different tenants can authorize each other, and application object information between application scenarios can be shared, effectively improving information exchange capabilities within tenant application scenarios and significantly reducing operating costs between tenants.

[0050] Preferably, the description information of the application model designed in the application object module includes application identifier, application type, and tenant identifier.

[0051] Preferably, such as Figure 2 As shown, the descriptive information of the process model of the application business process module includes business process identifier, process name, process business type, process status, process order, and application identifier.

[0052] Preferably, the business type is set in advance according to actual needs, such as: type 1 (custom monitoring) and type 2 (monitoring personnel).

[0053] Preferably, the descriptive information of the process status model of the application business process process status module includes business process status identifier, business process identifier, process status name, business process status type, process status sorting, and application identifier.

[0054] Preferably, the status type of the business process is set in advance according to actual needs, such as: type a (monitoring - status), type b (personnel - personnel list), type c (monitoring - data);

[0055] Preferably: Set the status of the first valid step in the business process to the default business process status information.

[0056] Preferably, the descriptive information of the business object model of the application object module includes the business object identifier, business object name, business object creation time, and application identifier;

[0057] Preferably, such as Figure 3 As shown, the descriptive information of the business data model of the application object collaborative management module includes business data identifier, object identifier, process identifier, process status identifier, data content, application identifier, tenant identifier, creation time, and update time.

[0058] Preferably, the descriptive information of the data model between the application and the tenant in the application permission module includes permission ID, application identifier, tenant identifier, permission data, and creation date.

[0059] Preferably, the description information of the application-to-application data model in the application permission module includes permission ID, application identifier, authorized application identifier, permission data, and creation date.

[0060] Preferably, a business process refactoring tool is used: a business process refactoring tool and a business data refactoring tool.

[0061] The business process refactorer is used to obtain business steps based on the current application identifier, classify them according to the type of business steps, and output the application business names to the tenant in order in the form of business sorting.

[0062] As an optional implementation, the business process refactoring device is also used to obtain business steps based on the current application identifier, classify them according to the type of business steps, and output the application business names in order in the form of business sorting.

[0063] As an optional implementation, the business process reorganizer is further configured to obtain business steps based on the current application identifier, classify them according to their type, and generate a business identifier order in the form of business sorting; then, based on the business object identifier, iteratively retrieves the business data of the business steps, matching the corresponding step status identifier to obtain the step status name. After the loop ends, the obtained data is reorganized to obtain the business object and the current step status information of each step.

[0064] Corresponding to the aforementioned system, the present invention also provides an application business process collaborative management method based on a multi-tenant mode. This method is applied to the aforementioned application business process collaborative management system and includes the following steps:

[0065] S100. Analyze the requirements of the business process links of the current application, build them in the order of the required business links, and save them to the shared database in the form of natural language.

[0066] S200. For the possible state of the business process in the current application, perform another state analysis and save the possible state results in the form of natural language to the shared data.

[0067] S300: Set application-tenant permissions, and then save the application-tenant operation permissions to the shared database.

[0068] S400, Set Application - Application Permissions, open data permissions between applications, so that tenants under an application have the right to query other unrelated applications and view object data through collaborative management of application objects;

[0069] S500, using the business process refactorer and business data refactorer, can refactor business processes and data, thereby enabling business process customization and business data monitoring in different scenarios.

[0070] As an optional implementation, the step of performing requirements analysis on the business process steps of the current application, constructing the steps according to their order, and saving them in a shared database in natural language includes: when setting business process steps, describing the step names in appropriate natural language according to the actual business, selecting the appropriate business step type according to requirements, and constructing the business steps. The relationship between the application and business steps is one-to-many, and tenants can set up multiple business steps.

[0071] As an optional implementation, the process further analyzes the possible state states within the current application's business process, saving the resulting states in natural language to shared data. This includes: when setting business process states, describing the state names using appropriate natural language based on the actual state, selecting suitable state types as needed, and constructing the business states. The relationship between business processes and their states is one-to-many.

[0072] As an optional implementation, the setting of application-tenant permissions, such as... Figure 4 As shown, after setting, the application-tenant operation permissions will be saved to the shared database, including: assigning operation permissions to other tenants as needed, enabling tenants to collaborate.

[0073] Preferably, the setting of application permissions, such as Figure 5 As shown, data permissions are opened between applications, allowing tenants under an application to query other unrelated applications and view object data through collaborative management of application objects. This includes setting different application object authorization relationships between applications according to actual needs, which better solves the problems of data privacy and data collaboration between applications.

[0074] Preferably, for different application scenarios, on-demand retrieval can be performed only according to the type of business process and the status type of the corresponding business process, which effectively reduces the pressure on the service, improves the data processing speed, and reduces the operating costs of the service provider.

[0075] Example

[0076] To illustrate the present invention more clearly, the specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0077] 1. Tenant creates / logs into application - Application name is Happy, application type is production management system.

[0078] 2. Configure application-tenant permissions.

[0079] 3. Set application permissions.

[0080] 4. Based on the business needs of the current application in multiple scenarios, the tenant analyzes the names of the steps involved in the business process, selects the appropriate business type according to the characteristics of the step, and determines the tenant's permissions - if no permission is granted, the process ends; if permission is granted, the step name is set as follows: Fabric Procurement, Accessory Procurement, Production Cutting Bed, Production Processing, Warehouse Clerk, Finished Goods Warehousing; among them, the custom monitoring type steps are: Fabric Procurement, Accessory Procurement, Production Cutting Bed, Production Processing, Finished Goods Warehousing, and the monitoring personnel type step is: Warehouse Clerk;

[0081] 4.1 Based on the business analysis in section 4, and combined with the actual business process status in the scenario, the fabric procurement options are: not procured, procured;

[0082] 4.2 Based on the business analysis in section 4, and combined with the actual business process status in the scenario, the auxiliary material procurement is set as: not procured, procured;

[0083] 4.3 Based on the business analysis in section 4, and combined with the actual business process status in the scenario, the production cutting bed is set to: cutting, number of cuts, and cut. The process status type for the number of cuts is: monitoring-data.

[0084] 4.4 Based on the business analysis in section 4, and combined with the actual business process status settings in the scenario, the production and processing are: Unprocessed, Quantity Delivered, and Completed. The process status type for Quantity Delivered is: Monitoring - Data.

[0085] 4.5 Based on the business analysis in section 4, and combined with the actual business process status in the scenario, the warehouse entry personnel are: Zhang San and Li Si. The process status type of this business process is: Monitoring - Personnel.

[0086] 4.6 Based on the business analysis in section 4, and combined with the actual business process status in the scenario, the finished product warehousing status is set as follows: not yet out of the warehouse, number of items in the warehouse, and warehouse warehousing completed. The status type of the delivery quantity is: monitoring-data.

[0087] 4.7 The status type of the process that is not specifically mentioned in steps 4.1-4.6 is: monitoring-status, where the order is in ascending order.

[0088] 5. When a user initiates collaborative management of application object business processes and sets up overall production monitoring, the system uses the business process reorganizer to retrieve business process step data, business step status data, business data, and application business object data from the database. The system then outputs the business process by monitoring data step name (sorted by data step status) and monitoring personnel / monitoring status name (sorted by business step status). Finally, based on the business object, the system obtains the scenario data by combining the business step ID, application ID, and step status ID, and outputs it to the user for review.

[0089] 5.1 The application object business process collaborative management in the example provides tenant progress summary viewing, cross-application data summary viewing, operation methods for multiple scenario stage types, and operation methods for multiple scenario stage status changes.

[0090] In summary, the technical solution of this invention implements business process customization services across multiple application scenarios through a multi-scenario business process customization method, and also provides a collaborative management system for application business process customization in a multi-tenant mode, such as... Figure 6 and 7 As shown, it realizes collaborative management in multiple scenarios, improves the flexibility of the system, and solves the problems of multi-tenant collaborative management and cross-application tenant collaborative management.

[0091] Obviously, the above embodiments of the present invention are merely examples to illustrate the present invention more clearly, and are not intended to limit the implementation of the present invention. Any modifications made based on the above description are still within the protection scope of the present invention.

[0092] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples; within the framework of the invention, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of the different aspects of the invention as described above, which are not provided in the details for the sake of brevity.

Claims

1. A collaborative management system for application business processes based on a multi-tenant model, characterized in that, Applications from different tenants execute within the same application business process collaborative management system. Applications from different tenants can authorize each other, and application object information can be shared between application scenarios. This includes application modules, application business process stage modules, application business process stage status modules, application object modules, application object collaborative management modules, application permission modules, an application business process reconfigurator, and a shared database, among which: The application module is used to create a tenant application model and save the created tenant application model to the application data of the shared database with a form identifier WxappId. The application business process module is used to design multi-scenario business process models, process business processes, create business processes and business process instances, and save the designed business process form identifier Scheduleset Id to the application data in the shared database. The application business process stage status module is used to design business process status models, process business process status, create business process status and business process status instances, and save the designed business process status form identifier as Scheduleset Value ID to the status data of the shared database. The application object module is used to create and manage business objects, and saves the business objects to the application object table of the shared database with the form identifier Order Id. The application object collaborative management module is used to collaboratively manage the creation and modification of business object and business process status data information, and distribute and save it to different types of business data in the shared database in the form of datasets according to different business scenarios; The application permission module is used to manage the relationship between tenants and applications, and save the permission data between tenants and applications to the application tenant relationship data in the shared database; it is also used to manage the relationship between applications, and save the permission data between applications to the application permission data in the shared database. The application business process reconfigurator is used to retrieve business process and business process status data from a shared database under different scenarios, and output the reconfigured data to the Web client in the form of a data stream; it is also used to retrieve business data of business processes and business process status under different scenarios from shared data, and output the reconfigured data to the Web client in the form of a data stream. The shared database is used to store application data, process data, process status data, application tenant relationship data, object data, application permission data, business data, and tenant data.

2. The application business process collaborative management system according to claim 1, characterized in that, The business process reconfigurator is also used to obtain business steps based on the current application identifier, classify them according to the type of business steps, and output the application business names in order in the form of business sorting.

3. The application business process collaborative management system according to claim 2, characterized in that, The business process reorganizer is also used to obtain business steps based on the current application identifier, classify them according to the type of business steps, and generate a business identifier order in the form of business sorting; then, based on the business object identifier, it iteratively obtains the business data of the business step identifier, matches the step status identifier corresponding to the step identifier to obtain the step status name, and after the loop ends, it reorganizes the obtained data to obtain the business object and the step status information of each current step.

4. A method for collaborative management of application business processes based on a multi-tenant model, wherein the method is applied to the application business process collaborative management system as described in any one of claims 1-3, and the method comprises the following steps: Analyze the requirements of the current application's business process steps, construct them in the order of the required business steps, and save them to the shared database in the form of natural language. For the possible states of the business process in the current application, perform another state analysis and save the possible state results in the form of natural language to the shared data. Configure application-tenant permissions, and then save the application-tenant operation permissions to the shared database. Set application permissions to grant data permissions between applications, allowing tenants under an application to query other unrelated applications and view object data through collaborative management of application objects. By using the business process refactorer and business data refactorer, business processes and data can be refactored, enabling customization of business processes and monitoring of business data in different scenarios.

5. The application business process collaborative management method according to claim 4, characterized in that, The process of analyzing the requirements of the current application's business process steps, constructing the process according to the order of the required business steps, and saving it to the shared database in natural language format includes: When setting up business process steps, describe the step names using appropriate natural language according to the actual business, and then select the appropriate business step type according to the requirements to form the business steps.

6. The application business process collaborative management method according to claim 4, characterized in that, The process involves re-analyzing the potential states of each stage in the current application's business process, and saving the possible state results in natural language to the shared data, including: When setting business process status, describe the status name of the process in appropriate natural language according to the actual status, and then select the appropriate status type according to the requirements to form the business status.

7. The application business process collaborative management method according to claim 4, characterized in that, The setting of application-tenant permissions, after which the application-tenant operation permissions are saved to the shared database, includes: Assign operational permissions to other tenants as needed to enable them to collaborate.

Images