Camuda-based multi-tenant service flow system and method

Abstract

The invention discloses a Camuda-based multi-tenant service flow system and method, and the method comprises the steps: S1, determining the demands of a multi-tenant service flow system, and configuring a Camuda environment; s2, configuring a user attribute database based on a Camuda environment, and optimizing a user organization model; s3, developing a configuration module according to the user organization model; s4, the configuration module integrates an Apaas form designer, and forms are customized and rendered in real time; s5, developing a business rule engine module according to the demand and the configuration module; s6, realizing a task-based authentication mechanism based on a business rule engine module; and S7, integrating the steps S1 to S6 to realize automatic execution of the business process. And S8, designing a user interface. According to the method, a user organization model of Camuda, electronic form design and a service rule configuration function are optimized, and a highly customizable, flexible and efficient multi-tenant service flow system is provided in combination with an Apaas form technology and a task-based authentication mechanism, so that the user experience is enhanced, and the safety and continuity of a service process are ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic digital data processing, in particular to the technical field of multiprogramming devices, and specifically to a multi-tenant business flow system and method based on Camunda. Background Art

[0002] Camunda is an open source workflow automation platform that supports standards such as BPMN, CMMN, and DMN. Camunda provides a powerful workflow engine that can be used to model, execute, and monitor business processes, allowing developers and business analysts to design processes and can be integrated into existing Java applications. A multi-tenant business flow system is a software architecture pattern that allows multiple tenants to share the same application instance while keeping data and business logic isolated. In a multi-tenant business flow system based on Camunda, different tenants can run their business processes on the same Camunda engine. Each tenant has its own independent data view and business process, but these processes all run on the same application platform. A multi-tenant architecture can improve resource utilization, reduce costs, and simplify maintenance and upgrade processes.

[0003] Although the Camunda native system can implement basic user tasks and copy tasks, its limitations gradually become apparent when dealing with the complex organizational structure and changing business needs of large enterprises.

[0004] Specifically, Camunda's default user organization model is unable to adapt to multi-level, multi-attribute enterprise organizational structures, especially in the recruitment process, which lacks a user screening mechanism based on business attributes. In addition, its built-in electronic form design tool lacks flexibility and scalability, and it is difficult to cope with the needs of advanced functions such as form layout adjustment and event extension in complex business scenarios. Although Camunda provides form builders and custom form options, there are still problems in achieving linkage between low-code generated forms.

[0005] Therefore, it is necessary to improve the Camunda multi-tenant business flow system in the prior art to solve the above problems. Summary of the invention

[0006] The present invention overcomes the shortcomings of the prior art and provides a multi-tenant business flow system and method based on Camunda, aiming to solve the problem of task-based authentication in the prior art, as well as the problem of proxy handler recommendation and authority allocation when the handler is empty.

[0007] To achieve the above object, the technical solution adopted by the present invention is: a multi-tenant business flow system and method based on Camunda, comprising:

[0008] S1. Determine the requirements of the multi-tenant business flow system and configure the Camunda environment;

[0009] S2. Configure the user attribute database based on the Camunda environment and optimize the user organization model;

[0010] S21. Introduce a business attribute screening mechanism: Allow users to screen users based on business attributes to ensure that the selection process can accurately match business needs;

[0011] S22. Support multi-level user organization structure: display the hierarchical relationship and attribute association between users in the form of tree structure or graphic structure;

[0012] S23. Calculate weight value and implement compensation mechanism: Calculate a weight value for each user based on the user's role, authority and business attributes; when the processor is empty, the user specifies that the initiator shall act as the agent or designate other personnel to act as the agent based on the business scenario;

[0013] S3. Develop configuration modules based on user organization model;

[0014] S4. The configuration module integrates the Apaas form designer to customize and render forms in real time;

[0015] S5. Develop business rule engine module according to requirements and configuration modules;

[0016] S6. Implementing a task-based authentication mechanism based on the business rule engine module;

[0017] S61. Design a task-based permission control model; the permission control model is classified into a direct permission model and an indirect permission model; the steps of the indirect permission model include: when the handler is empty, the system automatically recommends or designates a proxy handler according to the user weight value calculated in step S2, and the proxy handler temporarily obtains the permissions required to perform the task; when the handler is not empty, the permissions of the proxy handler are automatically revoked;

[0018] S62, verifying the user's authority to access and operate tasks;

[0019] S7, integrate S1-S6 to realize the automated execution of business processes;

[0020] S8. Design the user interface.

[0021] In a preferred embodiment of the present invention, in step S23, corresponding weight factors Wn are assigned according to role factors, the sum of all factor weight factors Wn is 1, a quantitative scoring standard Sn is determined for each factor, and the weight value of each user is: W = ∑Wn*Sn; all users are sorted according to the calculated weight values, and the user with the highest weight value will be listed as the preferred agent.

[0022] In a preferred embodiment of the present invention, in step S61, the direct authority model includes a mechanism for task allocation and authority verification;

[0023] Task allocation includes: dynamic allocation and static allocation;

[0024] (1) Dynamic allocation: tasks are allocated to corresponding users or user groups in real time according to business needs or system policies;

[0025] (2) Static assignment: During the system initialization or configuration phase, specific tasks are fixedly assigned to specific users or roles;

[0026] Permission verification includes the following steps:

[0027] a. Each task is assigned a unique ID. When a user initiates a request, the system parses the task ID in the request to check whether the user has the right to perform the task.

[0028] b. Verify the association between the task and the corresponding form;

[0029] c. For forms with parent-child relationships, users can only access and operate forms within their authorized scope.

[0030] In a preferred embodiment of the present invention, in step S62, an authentication point is set in the access and operation link of the business process, and authentication is called at the authentication point to verify the user's task access and operation authority.

[0031] In a preferred embodiment of the present invention, in step S1, demand information about business processes, user roles, and authority requirements is collected.

[0032] In a preferred embodiment of the present invention, in step S5,

[0033] S51. Design the architecture of the business rule engine;

[0034] S52. Provide a rule editing interface to link business rules with form fields;

[0035] S53. Business rules are customized according to different terminals.

[0036] The present invention provides a multi-tenant business flow system based on Camunda, comprising:

[0037] Information collection module: responsible for collecting user information and business attributes;

[0038] Configuration module: allows administrators or users with corresponding permissions to configure business processes, form fields, business rules, etc.;

[0039] Execution module: responsible for the actual execution of the process, performing operations according to the processes, forms and business rules defined in the configuration module;

[0040] Authentication module: implements task-based permission control to ensure that users can only access and operate authorized tasks and data;

[0041] Form Designer module: Integrates Apaas technology to allow users to customize form fields, layouts, and events by dragging and dropping and configuring;

[0042] Business rule engine module: provides business rule configuration and management functions, and supports the linkage between business logic and form fields;

[0043] User interface module: provides customized interface display for different terminals.

[0044] The present invention provides a device for a multi-tenant business flow system based on Camunda, including an electronic device, characterized in that the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0045] The present invention solves the defects existing in the background technology and has the following beneficial effects:

[0046] (1) The present invention optimizes Camunda's user organization model, electronic form design, and business rule configuration functions, and combines Apaas's form technology and task-based authentication mechanism to provide a highly customizable, flexible, and efficient multi-tenant business flow system. Compared with the prior art, the present invention significantly improves the system's performance in processing the complex organizational structure and changing business requirements of large enterprises, enhances user experience, and ensures the security and continuity of business processes.

[0047] (2) The present invention realizes more sophisticated and flexible authority management by combining the authentication module with the task-based authority control model. The weight calculation and compensation mechanism of step S2 is combined with the indirect authority model in S6. A weight value W=∑Wn*Sn is calculated for each user according to the user's role, authority and business attributes. When the handler is empty, the user specifies that the initiator will act as the agent or designate other personnel to act as the agent according to the business scenario. The indirect authority model will then assign the corresponding authority based on the task to the agent handler. When the handler is not empty, the authority of the agent handler is automatically revoked. Compared with the prior art, this mechanism allows business flow without an agent and without the agent handler having direct data authority, thereby improving the flexibility and efficiency of the approval process.

[0048] (3) The configuration module of the present invention provides highly customized business process, form template and business rule configuration capabilities through integration with the Apaas form designer, allowing users to customize form fields and layouts by dragging and dropping and configuring. Compared with the existing technology, the system can quickly adapt to the specific business needs of different tenants without modifying the underlying code, thereby improving the flexibility and scalability of the system.

[0049] (4) The present invention breaks through the traditional authority restrictions by designing and implementing a task-based authentication mechanism, allowing users to conduct business transactions without direct data authority. Compared with the existing technology, this innovation significantly improves the flexibility and efficiency of group and cross-departmental approval processes.

[0050] (5) The present invention calculates weight values ​​and implements a compensation mechanism to ensure that when the processing person is empty, the most suitable agent can be selected according to the weight value to avoid process interruption or delay. Compared with the existing technology, this mechanism improves the accuracy and efficiency of agent selection and ensures the continuity of the business process. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] 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 are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

[0052] Figure 1 is a flow chart of a preferred embodiment of the present invention;

[0053] Figure 2 This is a process flow chart of managing maintenance technicians according to a preferred embodiment of the present invention; DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 are within the scope of protection of the present invention.

[0055] In the following description, many specific details are set forth to facilitate a full understanding of the present invention, but the present invention may also be implemented in other ways different from those described herein. Therefore, the protection scope of the present invention is not limited to the specific embodiments disclosed below.

[0056] In the description of this application, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood by specific circumstances.

[0057] A Camunda-based multi-tenant business flow system includes the following modules:

[0058] Information collection module: responsible for collecting user information and business attributes, providing data support for the user organization model, and ensuring that subsequent modules can perform corresponding processing and decision-making based on these data.

[0059] Configuration module: allows administrators or users with corresponding permissions to configure business processes, form fields, business rules, etc.; provides high customizability so that the system can adapt to the business needs of different tenants without modifying the underlying code.

[0060] Execution module: responsible for the actual execution of the process, including task allocation, form filling, process monitoring, etc., performs operations according to the processes, forms and business rules defined in the configuration module; ensures that the business process can be executed according to the predetermined rules, and improves the efficiency and accuracy of business processing.

[0061] Authentication module: implements task-based permission control to ensure that users can only access and operate authorized tasks and data; involves role management, permission allocation and access control strategies, thereby enhancing the security of the system, preventing unauthorized data access and operation, and ensuring the confidentiality and integrity of business data.

[0062] Form Designer Module: Integrates Apaas technology, allowing users to customize form fields, layouts, and events by dragging and dropping and configuring; reduces dependence on professional developers, allowing non-technical personnel to quickly design and adjust forms to meet changing business needs.

[0063] Business rule engine module: provides business rule configuration and management functions, supports the linkage between business logic and form fields; involves rule definition, condition judgment, action execution, etc., so that the system can automatically make decisions and process control according to business rules, and improve the intelligent level of business processing.

[0064] User interface module: provides customized interface display for different terminals; involves responsive design, theme switching, layout adjustment, etc., so as to improve user experience and enable users to access and use the system more conveniently.

[0065] These modules work together to form a multi-tenant business flow system based on Camunda. The information collection module provides basic data for the system; the configuration module defines business processes and rules; the execution module performs operations according to the configuration; the authentication module ensures the security of operations; the form designer module provides flexible form customization capabilities; the business rule engine module implements intelligent decision-making; and the user interface module provides a friendly interactive experience. The entire system supports the efficient, secure, and flexible operation of multi-tenant business flows in a highly customizable and automated manner.

[0066] A method for a multi-tenant business flow system based on Camunda, comprising the following steps;

[0067] S1. Determine the requirements of the multi-tenant business flow system and configure the Camunda environment;

[0068] S2. Configure the user attribute database based on the Camunda environment and optimize the user organization model;

[0069] S3. Develop configuration modules based on user organization model;

[0070] S4. The configuration module integrates the Apaas form designer to customize and render forms in real time;

[0071] S5. Develop business rule engine module according to requirements and configuration modules;

[0072] S6. Implementing a task-based authentication mechanism based on the business rule engine module;

[0073] S7, integrate S1-S6 to realize the automated execution of business processes;

[0074] S8. Design the user interface;

[0075] Specifically, in step S1, key requirement information about business processes, user roles, and permission requirements is collected to provide guidance for subsequent steps; according to the requirement information, the Camunda server and database are configured to establish a development environment; Camunda environment construction is the basis for realizing the system architecture and technical requirements determined in the requirements.

[0076] Specifically, in step S2, the step of optimizing the user organization model includes:

[0077] S21. Introduce a business attribute screening mechanism: Allow users to screen users based on business attributes to ensure that the selection process can accurately match business needs; business attributes include: department, position, and project;

[0078] The implementation of the business attribute screening mechanism is based on the user attribute database, which stores various attribute information of users. When the user needs to select a specific user, the system will retrieve a list of users that meet the conditions from the user attribute database based on the screening conditions entered by the user, and present it to the user for selection.

[0079] S22. Support multi-level user organization structure: display the hierarchical relationship and attribute association between users in the form of tree structure or graphic structure;

[0080] In order to meet the multi-level and multi-attribute organizational structure requirements of large enterprises, it supports the customization and management of multi-level user organizational structures to ensure that the complexity of the organizational structure can be fully reflected. Users can freely add, modify or delete nodes and relationships in the organizational structure to adapt to changes in the enterprise organizational structure.

[0081] Through node configuration, the system uses advanced intelligent algorithms and query logic to automatically and accurately match the corresponding filler. This not only improves the intelligence of filler selection, but also ensures that each filling task can be correctly and efficiently assigned to the corresponding filler, thereby greatly improving the accuracy and efficiency of business processing.

[0082] S23. Calculate weight value and implement compensation mechanism: Calculate a weight value for each user based on the user's role, authority and business attributes. When the processor is empty, the user specifies that the initiator or other personnel shall act as the agent based on the actual business scenario to ensure that the process can be executed continuously and completely to avoid process interruption or delay.

[0083] This weight value is designed based on actual conditions, such as the level of the role, the importance of the authority, the relevance of the business attributes, etc. The users are then sorted according to their weight values, and users with higher weight values ​​are selected as recommendation results to improve the accuracy and efficiency of agent selection.

[0084] Furthermore, a weight factor Wn is assigned to each factor, the sum of all factor weight factors is 1, and the weight value of each user is calculated using the following formula: W = ∑Wn*Sn

[0085] All users are sorted according to the calculated weight values, and the user with the highest weight value will be listed as the preferred agent;

[0086] When the handler of a task is empty, it is sorted according to the weight value and the user with the highest weight value is selected as the proxy handler to ensure the continuity of the process.

[0087] Specifically, in step S3, the administrator configures the business process, form template, and business rules through a graphical interface, and persistently stores the configuration data to ensure that the configuration information can be restored after the system is restarted.

[0088] Specifically, in step S4,

[0089] S41. Introduce the Apaas form designer component and integrate it into the configuration module;

[0090] S42. Customize the form by dragging elements and configuring properties, and preview it in real time;

[0091] S43. Save and reuse form templates, and share or isolate form templates between multiple tenants;

[0092] The form design and management functions of Apaas are directly called through the backend, the form field change data sent by the frontend is received through code logic, and the corresponding business logic or database is updated. The frontend interface dynamically updates the form display based on the data returned by the backend.

[0093] Specifically, in step S5,

[0094] S51. Design the architecture of the business rule engine;

[0095] S52. Provide a rule editing interface to link business rules with form fields; define business rules in a graphical or scripted manner;

[0096] S53. Business rules are customized according to different terminals.

[0097] In step S51, the business rule engine module allows users to customize the business rules in the process according to business needs, including conditional judgment and data verification; business rules ensure the accuracy and compliance of business processes by defining a configuration model, storing the data structure of business rules, reading and parsing the data in the configuration model through a parser, and then executing the business rules through a customized rule engine.

[0098] In step S52, the linkage between business rules and form fields is supported. The business rules are bound to the form fields by referencing the rule ID in the rule engine in the form definition. When the value of the form field changes, the form triggers the corresponding business rules for verification or processing; the seamless connection between business logic and form interface is achieved, which improves the user experience and business processing efficiency.

[0099] In step S53, it supports separate configuration of the APP and PC terminals to ensure that the form display of the two terminals is consistent with business requirements and meet the differentiated needs of different terminals; the rule engine is used to load different configurations according to the terminal type, which is achieved by specifying the terminal type in the configuration file and reading these configurations when the rule engine is started.

[0100] Specifically, in step S6,

[0101] S61. Design a task-based permission control model;

[0102] S62, verifying the user's authority to access and operate tasks;

[0103] The permission control model is classified into direct permission model and indirect permission model; direct permission refers to the permission that users directly have to access and operate certain resources in the system or perform certain tasks due to their role, position or specific authorization, and this permission is explicitly granted to the user; indirect permission refers to the access and operation permission that users obtain because the agent handler is empty and is recommended according to the weight degree.

[0104] Further, in step S61, the direct authority model includes a mechanism for task allocation and authority verification;

[0105] The direct permissions model includes:

[0106] Task allocation includes: dynamic allocation and static allocation;

[0107] (1) Dynamic allocation: tasks are allocated to corresponding users or user groups in real time according to business needs or system policies;

[0108] (2) Static allocation: During the system initialization or configuration phase, specific tasks are fixedly assigned to specific users or roles.

[0109] Permission verification includes the following steps:

[0110] a. Each task is assigned a unique ID. When a user initiates a request, the system parses the task ID in the request to check whether the user has the right to perform the task.

[0111] b. Verify the association between the task and the corresponding form;

[0112] c. For forms with parent-child relationships, users can only access and operate forms within their authorized scope;

[0113] The indirect permission model includes:

[0114] When the handler is empty, the system automatically recommends or designates a proxy handler based on the user weight value calculated in step S2, and the proxy handler temporarily obtains the authority required to perform the task; when the handler is not empty, the authority of the proxy handler is automatically revoked;

[0115] In a further step S62, an authentication point is set at a key link in the business process to ensure permission verification before performing sensitive operations. The authentication service is called at the authentication point to verify the user's task access and operation permissions. When authentication fails, corresponding exception handling is performed according to business needs. When authentication succeeds, the process is allowed to continue to execute subsequent operations.

[0116] In response to cross-departmental and cross-business line approval or process requirements, users can conduct business flows through specific tasks without direct data permissions. The implementation of this authentication mechanism is based on a given task ID. The algorithm accurately locates and retrieves the document ID associated with it, and then obtains other documents associated with this document. The obtained related information is compared with the current task for authentication.

[0117] Specific application scenario 1

[0118] like Figure 2 As shown, after the service work order is assigned, in order to ensure the accuracy and security of the maintenance log, a dedicated filling node is designed to manage the maintenance master's log filling process.

[0119] 1. Flexible configuration of filler

[0120] (1) Customized acquisition of filler: In the filling node settings, flexible configuration options are provided, allowing the administrator to dynamically obtain the maintenance technician of a specified document through an interface / script, ensuring that even if the maintenance technicians of different documents are different, the corresponding filler can be accurately found.

[0121] (2) Acquisition based on document fields: In addition to custom acquisition, it also supports direct acquisition and specifying the filler through specific fields on the document, including "maintenance technician ID" or "maintenance technician name", which simplifies the configuration process and improves efficiency.

[0122] 2. Optimize the filling experience

[0123] (1) Allow temporary saving: In the advanced configuration module, the temporary saving function is enabled. When filling in the maintenance log, if the maintenance technician needs to leave temporarily or needs more time to verify the information, he can choose to temporarily save the current content and continue editing later, which improves the flexibility and convenience of filling in the log.

[0124] (2) Business rule configuration: Detailed business rules are configured for the fields of the maintenance log. The editable rules for the corresponding fields of the maintenance log are turned on to ensure that only designated maintenance technicians can edit these fields. Corresponding display rules are also configured to ensure that other users cannot see or edit these sensitive information.

[0125] 3. Automated process management

[0126] (1) Process triggering: When a service work order is assigned, the document will be automatically submitted and enter the preset process to start the flow. Once it reaches the filling node, the system will automatically notify the corresponding maintenance technician to fill it out according to the previous configuration.

[0127] (2) Filling notification and reminder: The maintenance technician will receive a filling notification through the message center. Click the notification link or directly open the document, and the maintenance technician will enter the dedicated filling interface to edit the log.

[0128] (3) Submission and transfer: After the maintenance technician completes the form, he can choose to save or submit. If he chooses to save, the system will save the current content and allow subsequent editing; if he chooses to submit, the system will verify the integrity of the content and update the document status. Once the submission is successful, the process will automatically flow to the next node.

[0129] The above is based on the ideal embodiment of the present invention. Through the above description, relevant personnel can make various changes and modifications without departing from the technical concept of the present invention. The technical scope of the present invention is not limited to the content in the specification, and the technical scope must be determined according to the scope of the claims.

Claims

1. A method for a multi-tenant business flow system based on Camunda, characterized in that: The steps include: S1. Determine the requirements of the multi-tenant business flow system and configure the Camunda environment; S2. Configure the user attribute database based on the Camunda environment and optimize the user organization model; S21. Introduce a business attribute screening mechanism: Allow users to screen users based on business attributes to ensure that the selection process can accurately match business needs; S22. Support multi-level user organization structure: display the hierarchical relationship and attribute association between users in the form of tree structure or graphic structure; S23. Calculate weight value and implement compensation mechanism: Calculate a weight value for each user based on the user's role, authority and business attributes; when the processor is empty, the user specifies that the initiator shall act as the agent or designate other personnel to act as the agent based on the business scenario; S3. Develop configuration modules based on user organization model; S4. The configuration module integrates the Apaas form designer to customize and render forms in real time; S5. Develop business rule engine module according to requirements and configuration modules; S6. Implementing a task-based authentication mechanism based on the business rule engine module; S61. Design a task-based permission control model; The authority control model is classified into direct authority model and indirect authority model; the steps of the indirect authority model include: when the handler is empty, the system automatically recommends or designates a proxy handler according to the user weight value calculated in step S2, and the proxy handler temporarily obtains the authority required to perform the task; when the handler is not empty, the authority of the proxy handler is automatically revoked; S62, verifying the user's authority to access and operate tasks; S7, integrate S1-S6 to realize the automated execution of business processes; S8. Design the user interface.

2. According to the method of a Camunda-based multi-tenant business flow system according to claim 1, it is characterized by: In step S23, the corresponding weight factor Wn is assigned according to the role factor, the sum of all the factor weight factors Wn is 1, and a quantitative scoring standard Sn is determined for each factor, and the weight value of each user is: W ＝ ∑ W n *S n ; All users are sorted according to the calculated weight values, and the user with the highest weight value will be listed as the preferred agent.

3. According to the method of a Camunda-based multi-tenant business flow system according to claim 1, it is characterized by: In step S61, the direct authority model includes a mechanism for task allocation and authority verification; Task allocation includes: dynamic allocation and static allocation; (1) Dynamic allocation: tasks are allocated to corresponding users or user groups in real time according to business needs or system policies; (2) Static assignment: During the system initialization or configuration phase, specific tasks are fixedly assigned to specific users or roles; Permission verification includes the following steps: a. Each task is assigned a unique ID. When a user initiates a request, the system parses the task ID in the request to check whether the user has the right to perform the task. b. Verify the association between the task and the corresponding form; c. For forms with parent-child relationships, users can only access and operate forms within their authorized scope.

4. According to the method of a Camunda-based multi-tenant business flow system according to claim 1, it is characterized by: In step S62, an authentication point is set in the access and operation link of the business process, and authentication is called at the authentication point to verify the user's task access and operation authority.

5. The method of a multi-tenant business flow system based on Camunda according to claim 1, characterized in that: In step S1, demand information about business processes, user roles, and authority requirements is collected.

6. The method of a Camunda-based multi-tenant business flow system according to claim 1, characterized in that: In step S5, S51. Design the architecture of the business rule engine; S52. Provide a rule editing interface to link business rules with form fields; S53. Business rules are customized according to different terminals.

7. A multi-tenant service flow system based on Camunda, a method for a multi-tenant service flow system based on Camunda according to any one of claims 1 to 6, comprising: Information collection module, responsible for collecting user information and business attributes; Configuration module, which allows administrators or users with corresponding permissions to configure business processes, form fields, business rules, etc.; The execution module is responsible for the actual execution of the process and performs operations according to the processes, forms and business rules defined in the configuration module; The authentication module implements task-based permission control to ensure that users can only access and operate authorized tasks and data; The form designer module integrates Apaas technology, allowing users to customize form fields, layouts, and events through drag-and-drop and configuration; Business rule engine module, which provides business rule configuration and management functions and supports the linkage between business logic and form fields; The user interface module provides customized interface presentation for different terminals.

8. A device for a multi-tenant service flow system based on Camunda, comprising an electronic device, characterized in that: The electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a method for a multi-tenant business flow system based on Camunda is implemented as described in any one of claims 1 to 6.

Images