Configurable processing method, system and equipment for multi-form process event linkage and medium

Abstract

The invention provides a configurable processing method, system and device for multi-form process event linkage and a medium, and belongs to the technical field of low-code development platforms. A basic database containing associated fields is constructed, a process database is constructed, and a data mapping relation is established between the process database and the basic database through the associated fields; according to the current node identifier of the process database and the service state of the basic database, determining a relationship between nodes; cross-form data query or editing is realized by binding the process model and the associated field; configuring an operable button according to the business rule and the operation authority; the method comprises the following steps: configuring a custom script, creating a process model, configuring a process event, defining a process approval node and a process rule, ensuring process jump after state change, and forming end-to-end state synchronization. According to the invention, the business logic realization process can be simplified, and all related business rules and verifications can be ensured to be executed at correct opportunities, so that the business processing efficiency is effectively improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of low-code development platforms, and specifically relates to a configurable processing method, system, device and medium for multi-form process event linkage. Background Art

[0002] Low-code development platforms store and manage application functionality, interface, logic, and other information as metadata. When users configure applications, the platform automatically generates corresponding code or execution logic based on the metadata, enabling rapid application construction. Visual modeling technology provides developers with an intuitive interface, enabling them to design application interfaces and orchestrate business processes by dragging, dropping, connecting, and configuring properties of graphical components.

[0003] In related technologies, business data and process data are often stored in different systems or databases, lacking an effective association mechanism. Each form's data is managed independently, and data updates are asynchronous, making it easy for problems like data redundancy and inconsistency to occur. Business rules are usually static configurations that cannot be dynamically adjusted based on the actual progress of the process and changes in business status. The relationships between process nodes are fixed, lacking effective permission management and conflict resolution mechanisms. Furthermore, the operation buttons are not displayed intelligently, making it difficult for users to quickly find currently executable operations and prone to misoperation. The approval progress display is not intuitive and cannot meet the personalized needs of users. There is a lack of linkage between multiple views, making it inconvenient to obtain and update information. Summary of the Invention

[0004] The present invention provides a configurable processing method for multi-form process event linkage, which realizes dynamic binding of process data across forms through visual configuration, thereby improving development efficiency and enhancing system flexibility and scalability.

[0005] Methods include: S101: Build a basic database containing associated fields, the basic database including: data fields, business status and business rules; S102: Build a process database, which includes data fields, node status, process node identifiers, and process processing stage information. The process database and the basic database establish a data mapping relationship through associated fields. S103: Constraining the operation rights of the process nodes based on the business rules of the basic database, and determining the relationship between the nodes according to the current node identifier of the process database and the business status of the basic database; S104: Displaying operation buttons based on the associated fields of the basic database and the node status of the process database, and implementing cross-form data query or editing by binding the process model and the associated fields; S105: Based on the business status of the basic database and the node status of the process database, the current approval progress is displayed, and the operable buttons are configured according to the business rules and operation permissions; S106: The configured custom script updates the business status of the basic database and the node status of the process database according to the data mapping relationship, creates a process model, configures process events, defines process approval nodes and process rules, ensures process jumps after status changes, and forms end-to-end status synchronization.

[0006] It should be further explained that step S101 also includes: Define at least one multi-level association field, which includes a primary association field for binding the process database node status and a secondary association field for associating with the business form data field; the secondary association field is configured with a cross-form cascade field for establishing a cascading update relationship between the basic database and other business forms, ensuring that the data status of the associated forms is synchronously updated when the business status changes; Business rules are configured as a dynamic rule engine, which dynamically adjusts business rule constraints based on real-time status changes of associated fields; The business status includes a status trigger condition. When the business status meets a preset threshold, the automatic execution of the associated process event in the process database is triggered.

[0007] It should be further explained that step S102 also includes: defining a process data model according to business requirements, the process data model including data fields, process node identifiers, and process processing stages; Establish a binding relationship with the basic database through the associated field mapping table; When the associated fields of the basic database change, the stage update event of the process database is triggered, the current stage tag of the process database is updated, and the stage change log is recorded; Stage update events include: field change events parsed by the business rule engine and events matching preset stage switching conditions; Define primary association fields for binding business entities in the underlying database and secondary association fields for identifying iterative versions of the process model to ensure compatibility between historical process data and current process rules; During the process execution, the node status verifier is used to verify whether the current node meets the jump conditions; when the node status of the process database is updated, the secondary associated field is used to trigger the cascade update of the basic database.

[0008] It should be further explained that in step S103, the operation rights of the process node are constrained based on the business rules of the basic database. The constraint rules include: when the business status of the basic database meets the preset conditions, the operation rights of the process node are activated or disabled; Adjust the jump path of the relationship between nodes according to the current node identification of the process database; The constraint rules are configured to verify the logic of the business status of the basic database and the status of the process database node, and trigger the rollback of the process event when the verification fails; The determination of the relationship between the nodes includes: defining a permission conflict arbitration mechanism for each process node. When multiple business rules conflict with the operation permissions of the same node, the executable permissions are arbitrated based on preset priority rules, and the path dependency of the node jump is recorded to ensure that only reverse jumps along the historical path are allowed when the process rolls back.

[0009] It should be further explained that in step S104, an operable button is generated based on the business status of the basic database and the node status of the process database; Among them, button permissions are divided into primary permissions controlled by the business status of the basic database and secondary permissions controlled by the node status of the process database; The main permission is to allow the Submit button to be displayed when the customer status is valid; The secondary permission allows triggering the submission operation only when the process node is in the operational stage; When the primary permission conflicts with the secondary permission, the button is automatically hidden through the permission arbitration module; In step S104, the contract form data associated with the current process is also queried through the viewFormDataByCurrentPage function; Use the editFormDataByCurrentPage function to modify the associated fields of the external form and trigger cascading updates; Initiate a new process event through the reusable function module saveFormDataByCurrentPage.

[0010] It should be further explained that step S105 also includes: Generate the current approval progress view in real time based on the business status of the basic database and the node status of the process database, and receive instructions to adjust the view content to adjust the current approval progress view; Configure the display priority of actionable buttons based on the hierarchical relationship of associated fields; When multiple business rules conflict with the display of the same view element, the final display logic is selected based on the preset priority rules; Based on business rules and operation permissions, configuring an actionable button also includes: triggering the linkage update of multiple views simultaneously through associated fields; and verifying the logical compatibility of the associated fields of the target view with the current process model before executing the button operation.

[0011] It should be further explained that step S106 also includes: dynamically associating the data fields of the basic database with the node status of the process database, and triggering the update of the process database node status when the basic database customer status is modified; The status changes of process library nodes are synchronized to the business fields of the basic library; Each status update generates a version record containing complete field values, operation time, and operator; Record state changes through event tracing logs; When synchronization is abnormal, the compensation strategy is triggered; The compensation strategy is: if the error type is data verification failure, roll back the last operation.

[0012] This application also provides a configurable processing system for multi-form process event linkage, the system including: A basic database construction module is used to construct a basic database containing associated fields, the basic database including: data fields, business status and business rules; A process library construction module is used to construct a process database, which includes data fields, node status, process node identification, and process processing stage information. The process database and the basic database establish a data mapping relationship through associated fields; The node relationship definition module is used to constrain the operation permissions of process nodes using the business rules of the basic database and determine the relationship between nodes based on the current node identifier of the process database and the business status of the basic database; The query editing module is used to display operation buttons based on the associated fields of the basic database and the node status of the process database, and to implement cross-form data query or editing by binding the process model and the associated fields; The operation configuration module is used to use the business status of the basic database and the node status of the process database to display the current approval progress and configure the actionable buttons according to the business rules and operation permissions; The state processing module is used to configure custom scripts to update the business status of the basic database and the node status of the process database according to the data mapping relationship, create a process model, configure process events, define process approval nodes and process rules, ensure process jumps after status changes, and form end-to-end state synchronization.

[0013] According to another embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the configurable processing method for multi-form process event linkage are implemented.

[0014] According to another embodiment of the present application, a storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the configurable processing method for multi-form process event linkage are implemented.

[0015] It can be seen from the above technical solutions that the present invention has the following advantages: The configurable processing method for multi-form process event linkage provided by the present invention constructs a basic database and a process database, establishes a data mapping relationship through associated fields, and realizes data integration. Multi-level associated fields are defined, a one-to-one mapping is established for the primary associated fields, and cross-form cascading operations are realized by the secondary associated fields. At the same time, a state trigger mechanism is utilized to automatically update related data when the business state changes. The collaborative management of business data and process data is realized to ensure data consistency and integrity. The dynamic rule engine is utilized to enable real-time interaction between business rules and process database node status, and the business rules are dynamically adjusted according to the progress of the process. Flexible control and precise execution of the process are realized, improving business adaptability and process standardization.

[0016] Generate actionable buttons based on the status of the basic database and process database, divide button display and triggering into primary and secondary permissions, and configure button display priority based on the hierarchical relationship of associated fields. Generate an adjustable approval progress view in real time, support view linkage updates, and verify logical compatibility before clicking buttons. This makes user operations more convenient and efficient. A version record is generated for each status update, recording complete field values, operation time, and operator; the entire status change process is recorded through event tracing logs; and synchronization exception compensation strategies are set, such as rolling back the last operation when data verification fails. This enhances the maintainability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solution of the present invention, the following is a brief introduction to the drawings required for the description. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 A flow chart of configurable processing methods for multi-form process event linkage; Figure 2 A schematic diagram of a configurable processing system for multi-form process event linkage; Figure 3 Schematic diagram of an electronic device. DETAILED DESCRIPTION

[0019] This application provides a configurable method for linking multiple form process events, enabling users to operate on the business processes of interest at the fundamental data level, including but not limited to process approval operations such as initiation, withdrawal, and termination. This approach simplifies the implementation of complex business logic and ensures that all relevant business rules and validations are executed at the correct time, effectively improving business processing efficiency.

[0020] The following describes in detail the specific steps of the configurable processing method for multi-form process event linkage involved in this application. For the purpose of illustration rather than limitation, specific details such as specific system structures and technologies are provided to facilitate a thorough understanding of the embodiments of this application. However, it should be clear to those skilled in the art that this application can also be implemented in other embodiments without these specific details.

[0021] It should be understood that when used in this specification, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their collections. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0022] To facilitate the clear description of the technical solutions of this application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or order of execution, and the words "first" and "second" do not necessarily mean different.

[0023] The phrases "one embodiment" or "some embodiments" described in this application mean that the specific features, structures, or characteristics described in the embodiment are included in one or more embodiments of the application. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. that appear in different places in this application do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized.

[0024] In embodiments of the present invention, computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (exemplarily, via the Internet using an Internet service provider).

[0025] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. 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 making creative efforts are within the scope of protection of the present invention.

[0026] See also Figure 1 The figure is a flowchart of a configurable processing method for multi-form process event linkage in a specific embodiment, the method comprising: Step S101: constructing a basic database containing associated fields, wherein the basic database includes: data fields, business status and business rules.

[0027] In some embodiments, when constructing a basic database, data fields encompass various data and information involved in the business process, such as the product name, quantity, and budget in a purchase requisition. Business status records the current stage of a business, such as whether a purchase requisition is pending, under review, approved, or rejected. Business rules define restrictions and regulations on business operations, such as requiring approval from a specific leader when the purchase amount exceeds a certain amount. Associated fields serve as a bridge connecting data from different forms and have the same or related meanings across multiple forms, such as the requisition number field found in both purchase requisitions and approval forms. This embodiment ensures accurate storage of business data through clear data field definitions; business status records business progress; and business rules constrain data operations to ensure compliance. Association fields enable data from different forms to be linked, allowing data to be referenced and transferred across multiple forms. In some specific embodiments, at least one multi-level association field is defined, and the multi-level association field includes a primary association field for binding the process database node status and a secondary association field for associating the business form data field; the secondary association field is configured with a cross-form cascade field, which is used to establish a cascading update relationship between the basic database and other business forms, ensuring that the data status of the associated form is synchronously updated when the business status changes.

[0028] Specifically, the dynamic rule engine is a logic processing module embedded in the underlying database. It monitors the node status of the process database in real time and adjusts the business rules in the underlying database. For example, when a process enters the final review phase, the engine automatically parses the rules corresponding to the current process stage and updates the business rule constraints in the underlying database. Simultaneously, the engine synchronizes rule changes to the process database using associated fields, such as the customer ID, to ensure consistency between process execution and business rules.

[0029] During execution of this embodiment, when the node status of the process database is updated, the engine matches the corresponding business rules from the rule base. This can update the business rule fields in the underlying database and trigger synchronization events for the associated fields. Upon receiving the rule changes, the process database of this embodiment restricts subsequent process operations. This allows rules to dynamically adjust with process status, avoiding the fixed nature of business operations caused by static rules.

[0030] This embodiment also establishes hierarchical mapping relationships between the basic database, process database, and external business forms by defining primary and secondary association fields. Primary fields are used for entity binding, while secondary fields are used for extended associations. A mapping relationship validation module verifies the validity of association fields (e.g., whether a contract number exists in the external contract table) when writing data, ensuring data integrity and consistency.

[0031] For example, a primary field might represent a one-to-one relationship between a customer and an approval process, while a secondary field might represent a one-to-many relationship between a customer and multiple contracts. The mapping validation module verifies the validity of the associated fields during data writing, such as whether the contract number exists in the external contract table, ensuring data integrity and consistency.

[0032] During execution, the customer number is bound to the approval process ID in the process database, ensuring that each customer is associated with only one primary process. The contract number is linked to the external contract table, allowing querying or updating multiple contract data via secondary fields. If the secondary field does not exist in the external table, data writes are blocked and an alarm is triggered. This multi-level mapping and validation prevents invalid or isolated data, and the hierarchical management of primary and secondary fields enhances the maintainability of data associations.

[0033] In this embodiment, the business rules are configured as a dynamic rule engine, which binds business rules to the node status of the process database. When the node status of the process database is updated, the dynamic rule engine analyzes the current node status and adjusts the business rule constraints of the underlying database. If the business rule verification fails, a rollback instruction is sent to the process database.

[0034] This embodiment can also perform cascading operations on multi-level association fields. When the business status of the basic database changes, the primary association field is used to locate the process in the process database and terminate its execution. The secondary association field is used to locate the external contract management table and update the associated contract status to inactive.

[0035] This embodiment can detect the business status in real time based on preset trigger conditions. When the trigger conditions are met, the associated operation is executed and the node status of the process database is updated synchronously.

[0036] S102: Build a process database, which includes data fields, node status, process node identifiers, and process processing stage information. The process database and the basic database establish a data mapping relationship through associated fields.

[0037] In some embodiments, the data fields in the process database are partially linked to the underlying database to store specific process-related data. The node status indicates the current state of a process node. The process node identifier is a unique number for each node, used to distinguish between different nodes. The process processing stage information records the stage of the process. The process database establishes a mapping relationship with the underlying database through linked fields, matching business data with process node data. In this embodiment, when building a process database, a process data model is defined based on actual business needs. Data fields are used to store specific process-related information. This information is closely related to the business process and records key data for each step of the process. Process node identifiers are unique numbers for each process node, allowing for clear distinction between different approval nodes. This embodiment establishes a binding relationship with the underlying database through an associative field mapping table. This mapping-based association allows the system to locate the corresponding associated data in the underlying database based on the mapping rules when operating on data in the process database, and vice versa. This enables data interoperability and sharing between the two databases, ensuring consistency between business data and process data. When the associated fields of the basic database change, the stage update event of the process database is triggered, and the current stage label of the process database is updated, and the stage change log is recorded. When a related field in the underlying database changes, such as a modification to the requisition amount in a purchase requisition, the system immediately detects this change and triggers a stage update event in the process database. During this stage update event, the business rules engine first parses the field change event and analyzes its potential impact on the process. It then matches the pre-set stage transition condition event to determine whether the current field change meets the conditions for a process stage transition. If the conditions are met, the system will update the current stage label of the process database, advance the process to the next stage, and record a detailed stage change log, including change time, change reason, involved related fields and other information. This embodiment also defines a primary association field for binding a business entity of a basic database and a secondary association field for identifying an iterative version of a process model to ensure compatibility of historical process data with current process rules.

[0038] In the process database, primary association fields are defined to bind to business entities in the underlying database, establishing a data association between the two databases. This accurately maps business data in the underlying database to process instances in the process database. Secondary association fields are used to identify iterative versions of the process model. When process rules are updated and changed, these secondary association fields help the system distinguish between different versions of the process model. This ensures that historical process data can still be queried and processed according to the current process rules. During the process execution, the node status verifier is used to verify whether the current node meets the jump conditions; when the node status of the process database is updated, the secondary associated field is used to trigger the cascade update of the basic database.

[0039] During process execution, the node status verifier monitors the status of each node in real time. It verifies the current node based on pre-set transition conditions. For example, in a procurement approval process, the transition conditions for a department approval node might be that the approval opinion is "Agree" and the approval time is within a specified range. The node status verifier checks whether these conditions are met. Only when all conditions are met will the process be allowed to transition to the next node. When the node status of the process database is updated, the system will find the business data associated with it in the basic database through the secondary associated fields and trigger a cascading update of the basic database.

[0040] S103: Constraining the operation authority of the process node based on the business rules of the basic database, and determining the relationship between the nodes according to the current node identifier of the process database and the business status of the basic database.

[0041] This embodiment allocates corresponding operation permissions to different process nodes according to the business rules in the basic database.

[0042] In some specific embodiments, when the business status of the basic database meets the preset conditions, the operation permissions of the process node are activated or disabled. During the operation of the business process, the basic database stores the core status information of the business, such as the status of the purchase application being submitted, under review, or approved.

[0043] This embodiment also adjusts the jump paths between nodes based on the current node identifier in the process database. The node identifier in the process database clearly identifies the current location of the process. Based on the current node identifier, combined with business rules and the business status of the underlying database, the system dynamically adjusts the jump paths between nodes. This allows the process to flexibly adjust its flow direction based on actual business needs and conditions, ensuring that the process proceeds in a reasonable order.

[0044] In this embodiment, the constraint rules are configured to logically verify the business state of the basic database and the node state of the process database, triggering the rollback of the process event if the verification fails. The system performs logical verification on the business state of the basic database and the node state of the process database to ensure consistency and rationality between the two.

[0045] When such a verification failure occurs, the system triggers the process event rollback mechanism. Specifically, the process will be rolled back to the last reasonable node state and the relevant data will be corrected to ensure data accuracy. This embodiment also defines a permission conflict arbitration mechanism for each process node. When multiple business rules conflict with the operating permissions for the same node, executable permissions are arbitrated based on preset priority rules. For example, if business rule B is given a higher priority than business rule A, then in the event of such a conflict, the system will use the priority rule. This effectively resolves the issue of permission conflicts in complex business rule scenarios and ensures the uniqueness and certainty of process node operating permissions.

[0046] This embodiment records the path dependencies of node jumps, ensuring that only reverse jumps along the historical path are allowed when the process is rolled back. As the process progresses, the path dependencies of each node jump are recorded. When the process needs to be rolled back, the recorded path dependencies are used to allow only reverse jumps along the historical path. This ensures the standardization and traceability of process rollback operations.

[0047] S104: Displaying operation buttons according to the associated fields of the basic database and the node status of the process database, and implementing cross-form data query or editing by binding the process model and the associated fields.

[0048] This embodiment determines which action buttons should be displayed to the user based on the associated fields in the underlying database and the node status in the process database. By binding the process model to the associated fields, data query and editing operations are enabled across different forms. For example, approvers can directly view and modify the detailed data of a purchase requisition within the approval form, and users can quickly perform corresponding operations based on the displayed buttons.

[0049] In some specific embodiments of the present application, the system obtains the business status of the basic database and the node status of the process database in real time, and uses this as a basis to generate operable buttons in the user interface. Button permissions are divided into primary permissions and secondary permissions. Primary permissions are controlled by the business status of the underlying database. For example, in customer management, the Submit button is displayed only when the customer's status in the underlying database is displayed as "valid." This is because a valid customer meets the basic requirements for conducting business. Displaying the Submit button only makes sense in this situation, preventing invalid customers from initiating business processes. Secondary permissions are controlled by the node status of the process database. Once an application has been submitted and entered the approval phase, the submit button should not be triggered again, otherwise it will lead to duplicate submissions or business logic errors. This ensures that operations are consistent with the actual progress of the process. When conflicts arise between primary and secondary permissions, the Permission Arbitration module comes into play. For example, if the underlying database indicates a customer's status is valid, but the process database indicates the current process node is in the completed approval phase, the Permission Arbitration module will automatically hide the Submit button. This prevents users from making incorrect operations at inappropriate times, preventing disruption to business processes and ensuring standardized business processes and data accuracy. The viewFormDataByCurrentPage function provided in this embodiment is used to query the contract form data associated with the current process. By calling this function, the system can accurately obtain the required contract form data from the underlying database or related forms based on the node and associated fields of the current process and display it on the user interface.

[0050] The editFormDataByCurrentPage function in this example is used to modify the associated fields of an external form and trigger a cascading update. When business personnel discover that certain information in a contract form is incorrect or needs to be changed, they can use this function to make the changes. This ensures the consistency of relevant data, avoids business disruptions caused by data desynchronization, and improves the accuracy and efficiency of data management. In this embodiment, a new process event is initiated through a reusable function module, such as the saveFormDataByCurrentPage function, which serves as a reusable function module for initiating a new process event. In a business process, when a user completes or modifies form data and needs to submit the data to trigger a new process link, this function is called. For example, in a purchase application process, after the applicant completes the purchase application form and clicks the Submit button, the system calls the saveFormDataByCurrentPage function. This function first saves the form data to the underlying database to ensure data storage integrity.

[0051] The benefit of reusable function modules is that they improve code reusability and development efficiency. In different business processes, as long as similar submission and triggering process events are involved, the function can be called without rewriting code.

[0052] S105: Based on the business status of the basic database and the node status of the process database, the current approval progress is displayed, and the operable buttons are configured according to the business rules and operation permissions.

[0053] This embodiment combines the business status of the basic database and the node status of the process database to visually display the approval progress of the current process, showing the nodes the process has passed and the nodes it is about to enter. At the same time, according to business rules and user operation permissions, the actionable buttons are dynamically configured. As an implementation method of this application, the system continuously monitors the business status of the basic database and the node status of the process database, integrates this information in real time, and converts it into an intuitive approval progress view to present to the user. At the same time, the system supports receiving user-issued instructions to adjust the view content. For example, the user hopes to add information about the person in charge of each approval node, the time required for approval, and other content to the approval progress view, or change the display style of the view from a progress bar to a Gantt chart. After receiving the instruction, the system will re-acquire the relevant data from the database according to the instruction requirements, adjust and update the view content, and ensure that users can obtain approval progress information according to their needs.

[0054] In a multi-form flow, different actionable buttons and associated fields have a hierarchical relationship. The system analyzes the hierarchical structure of these associated fields and configures the display priority of the buttons accordingly.

[0055] In complex business scenarios, multiple business rules may conflict with each other, creating different display requirements for the same view element. To resolve these conflicts, the system pre-sets priority rules. For example, if business rule B is given a higher priority than business rule A, then in such a conflict, the system will select the logic of business rule B according to the priority rule. This ensures that the same view element has a unique and reasonable display logic under complex rules. This effectively avoids view display confusion caused by conflicting business rules and ensures that users receive accurate and consistent information.

[0056] The system configures the actionable buttons based on business rules and operation permissions so that they can trigger the linkage update of multiple views at the same time through associated fields.

[0057] Before executing a button action, the system verifies the logical compatibility of the target view's associated fields with the current process model. For example, in an approval process, when a user clicks the "Approved" button, the system checks whether the associated fields in the target view comply with the rules of the current process model. If the approver does not have the approval authority specified in the process, or if the approval time conflicts with the pre-set approval deadline, the system blocks the button action and prompts the user with an error message.

[0058] S106: The configured custom script updates the business status of the basic database and the node status of the process database according to the data mapping relationship, creates a process model, configures process events, defines process approval nodes and process rules, ensures process jumps after status changes, and forms end-to-end status synchronization.

[0059] This embodiment configures a custom script and, based on the data mapping relationship between the basic database and the process database, automatically updates the corresponding status in the two databases when the process status changes.

[0060] In this embodiment, a dynamic association is established between the data fields of the basic database and the node status of the process database. According to the pre-set association rules, the node status related to the customer in the process database is automatically updated, and the status of the ongoing business process node related to the customer is updated to suspended.

[0061] In this embodiment, a version record is generated each time the status of the basic database or process database is updated. This record contains complete field values, namely the specific values ​​of each relevant field before and after the update. Optionally, it can also include the operation time and operator, recording the user who performed the status update operation. This allows for rapid problem location and root cause identification.

[0062] In this embodiment, when an anomaly occurs in the state synchronization between the basic database and the process database, the system triggers a compensation strategy. If the error type is determined to be a data verification failure, meaning that the updated data does not conform to the pre-set verification rules, the system performs a rollback operation, undoing the last operation. For example, when updating a customer's status, if the newly entered customer status does not conform to the system's specified value range, the system will detect a data verification failure and restore the customer status to its pre-update state. When a synchronization anomaly occurs, timely measures can be taken to correct the error, preventing the further propagation and accumulation of erroneous data in the system and minimizing the impact on the business.

[0063] In summary, step S106 improves the data consistency, traceability, robustness and fault tolerance of the system by establishing dynamic associations between databases, generating version records, recording event tracing logs and setting compensation strategies.

[0064] On the basis of the above embodiment, in order to further improve the reliability of the configurable processing method for multi-form process event linkage provided by the above embodiment, as an implementable method, a specific embodiment is given below. In the specific embodiment, a process model is constructed through a visual interface, and process approval nodes, approval permissions (approval, rejection, return, withdrawal, etc.) and process rules are defined to achieve rapid construction of the process model; a process model is established, and process nodes, relationships between nodes and process rules are defined.

[0065] Set process events in process data to achieve data linkage with other processes; set process events to drive dynamic adjustment of related process data according to changes in the status of basic data. This embodiment uses an event-driven mechanism to achieve dynamic binding and linkage execution of process data across forms.

[0066] Take the implementation of the process event linkage configuration and execution method based on the low-code platform as an example: Construct fields that you want to associate with the process database in the basic database, such as approval status, customer status, etc. Define the process data model in the process database, including data fields and the current node of the process. Create a process model through a visual interface, configure process events, define process approval nodes, process rules, etc. Configure operation display rules according to the associated field customer status, and different customer status and approval status correspond to different operation buttons. The buttons configured in this embodiment support the configuration of custom JS scripts, and the encapsulated reusable function module viewFormDataByCurrentPage can be used in the custom script to view the approval information and approval progress of the current related process.

[0067] The viewed process information will present the corresponding process information, process approval progress, process approval opinions and the operational process approval permissions based on the node status of the current process, such as withdrawal, termination, rollback, transfer, etc. according to the configured process model and process events.

[0068] Approval authority execution process events utilize an event-driven mechanism to dynamically bind and coordinate process data across forms. This embodiment allows for editing, modifying, and initiating process events currently in draft state based on associated fields such as customer status and process status, using the reusable function module editFormDataByCurrentPage in custom scripts. Associated fields such as customer status and process status can also be used to initiate new process events in custom scripts using the reusable function module saveFormDataByCurrentPage.

[0069] It can be seen that this embodiment improves reusability through multi-form process event linkage processing. The unified event configuration mechanism makes the process logic reusable and reduces the cost of repeated development; supports complex business rules: through the event-driven mechanism, data linkage between multiple forms and flexible configuration of business rules are achieved; improves maintainability: the visual configuration interface makes the process logic easy to manage and maintain.

[0070] The following is an embodiment of a configurable processing system for multi-form process event linkage provided by an embodiment of the present disclosure. This system and the configurable processing methods for multi-form process event linkage provided by the aforementioned embodiments belong to the same inventive concept. For details not fully described in the embodiments of the configurable processing system for multi-form process event linkage, please refer to the embodiments of the configurable processing methods for multi-form process event linkage provided by the aforementioned embodiments.

[0071] like Figure 2 As shown, the system includes: a basic database construction module, which is used to construct a basic database containing associated fields, and the basic database includes: data fields, business status and business rules.

[0072] The process library construction module is used to construct a process database. The process database contains data fields, node status, process node identification and process processing stage information. The process database and the basic database establish a data mapping relationship through the association field.

[0073] The node relationship definition module is used to use the business rules of the basic database to constrain the operation permissions of the process nodes, and determine the relationship between nodes based on the current node identifier of the process database and the business status of the basic database.

[0074] The query editing module is used to display operation buttons based on the associated fields of the basic database and the node status of the process database, and to implement cross-form data query or editing by binding the process model and the associated fields.

[0075] The operation configuration module is used to use the business status of the basic database and the node status of the process database to display the current approval progress and configure the operable buttons according to the business rules and operation permissions.

[0076] The state processing module is used to configure custom scripts to update the business status of the basic database and the node status of the process database according to the data mapping relationship, create a process model, configure process events, define process approval nodes and process rules, ensure process jumps after status changes, and form end-to-end state synchronization.

[0077] like Figure 3 As shown, the present application also provides an electronic device, including a display module 103, a memory 102, a processor 101, and a computer program stored in the memory and executable on the processor 101, wherein the processor 101 implements the steps of a configurable processing method for linking multi-form process events when executing the program.

[0078] In the embodiments of the present invention, electronic devices include, but are not limited to, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the embodiments of the present application described and / or claimed herein.

[0079] In the embodiment of the present application, the processor 101 can be implemented by using at least one of a special purpose integrated circuit, a programmable logic device, a field programmable gate array, a processor, a controller, a microcontroller, a microprocessor, and an electronic unit designed to perform the functions described herein. In some cases, such an embodiment can be implemented in a controller. For software implementation, an embodiment such as a process or function can be implemented with a separate software module that allows the execution of at least one function or operation. The software code can be implemented by a software application (or program) written in any appropriate programming language, and the software code can be stored in a memory and executed by a controller.

[0080] The display module 103 is used to display information input by the user or information provided to the user. The display module 103 may include a display panel, which may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.

[0081] The memory 102 can be used to store software programs and various data. The memory 102 can include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0082] The present application also provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the configurable processing method for multi-form process event linkage.

[0083] The storage medium can be any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0084] In the context of storage media, a readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0085] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A configurable processing method for multi-form process event linkage, characterized in that: Methods include: S101: Build a basic database containing associated fields, the basic database including: data fields, business status and business rules; S102: Build a process database, which includes data fields, node status, process node identifiers, and process processing stage information. The process database and the basic database establish a data mapping relationship through associated fields. S103: Constraining the operation rights of the process nodes based on the business rules of the basic database, and determining the relationship between the nodes according to the current node identifier of the process database and the business status of the basic database; S104: Displaying operation buttons based on the associated fields of the basic database and the node status of the process database, and implementing cross-form data query or editing by binding the process model and the associated fields; S105: Based on the business status of the basic database and the node status of the process database, the current approval progress is displayed, and the operable buttons are configured according to the business rules and operation permissions; S106: The configured custom script updates the business status of the basic database and the node status of the process database according to the data mapping relationship, creates a process model, configures process events, defines process approval nodes and process rules, ensures process jumps after status changes, and forms end-to-end status synchronization.

2. The configurable processing method for multi-form process event linkage according to claim 1 is characterized in that: Step S101 also includes: Define at least one multi-level association field, which includes a primary association field for binding the process database node status and a secondary association field for associating with the business form data field; the secondary association field is configured with a cross-form cascade field for establishing a cascading update relationship between the basic database and other business forms, ensuring that the data status of the associated forms is synchronously updated when the business status changes; Business rules are configured as a dynamic rule engine, which dynamically adjusts business rule constraints based on real-time status changes of associated fields; The business status includes a status trigger condition. When the business status meets a preset threshold, the automatic execution of the associated process event in the process database is triggered.

3. The configurable processing method for multi-form process event linkage according to claim 2 is characterized in that: Step S102 also includes: defining a process data model according to business requirements, the process data model including data fields, process node identifiers, and process processing stages; Establish a binding relationship with the basic database through the associated field mapping table; When the associated fields of the basic database change, the stage update event of the process database is triggered, the current stage tag of the process database is updated, and the stage change log is recorded; Stage update events include: field change events parsed by the business rule engine and events matching preset stage switching conditions; Define primary association fields for binding business entities in the underlying database and secondary association fields for identifying iterative versions of the process model to ensure compatibility between historical process data and current process rules; During the process execution, the node status verifier is used to verify whether the current node meets the jump conditions; when the node status of the process database is updated, the secondary associated field is used to trigger the cascade update of the basic database.

4. The configurable processing method for multi-form process event linkage according to claim 2 is characterized in that: In step S103, the operation authority of the process node is constrained based on the business rules of the basic database. The constraint rules include: when the business status of the basic database meets the preset conditions, the operation authority of the process node is activated or disabled; Adjust the jump path of the relationship between nodes according to the current node identification of the process database; The constraint rules are configured to verify the logic of the business status of the basic database and the status of the process database node, and trigger the rollback of the process event when the verification fails; The determination of the relationship between the nodes includes: defining a permission conflict arbitration mechanism for each process node. When multiple business rules conflict with the operation permissions of the same node, the executable permissions are arbitrated based on preset priority rules, and the path dependency of the node jump is recorded to ensure that only reverse jumps along the historical path are allowed when the process rolls back.

5. The configurable processing method for multi-form process event linkage according to claim 2, characterized in that: In step S104, an operable button is generated based on the business status of the basic database and the node status of the process database; Among them, button permissions are divided into primary permissions controlled by the business status of the basic database and secondary permissions controlled by the node status of the process database; The main permission is to allow the Submit button to be displayed when the customer status is valid; The secondary permission allows triggering the submission operation only when the process node is in the operational stage; When the primary permission conflicts with the secondary permission, the button is automatically hidden through the permission arbitration module; In step S104, the contract form data associated with the current process is also queried through the viewFormDataByCurrentPage function; Use the editFormDataByCurrentPage function to modify the associated fields of the external form and trigger cascading updates; Initiate a new process event through the reusable function module saveFormDataByCurrentPage.

6. The configurable processing method for multi-form process event linkage according to claim 2, characterized in that: Step S105 further includes: Generate the current approval progress view in real time based on the business status of the basic database and the node status of the process database, and receive instructions to adjust the view content to adjust the current approval progress view; Configure the display priority of actionable buttons based on the hierarchical relationship of associated fields; When multiple business rules conflict with the display of the same view element, the final display logic is selected based on the preset priority rules; Based on business rules and operation permissions, configuring an actionable button also includes: triggering the linkage update of multiple views simultaneously through associated fields; and verifying the logical compatibility of the associated fields of the target view with the current process model before executing the button operation.

7. The configurable processing method for multi-form process event linkage according to claim 1, characterized in that: Step S106 also includes: dynamically associating the data fields of the basic database with the node status of the process database, and triggering the update of the process database node status when the basic database customer status is modified; The status changes of process library nodes are synchronized to the business fields of the basic library; Each status update generates a version record containing complete field values, operation time, and operator; Record state changes through event tracing logs; When synchronization is abnormal, the compensation strategy is triggered; The compensation strategy is: if the error type is data verification failure, roll back the last operation.

8. A configurable processing system for multi-form process event linkage, characterized in that: The system is used to implement the configurable processing method for multi-form process event linkage as described in any one of claims 1 to 7; The system includes: A basic database construction module is used to construct a basic database containing associated fields, the basic database including: data fields, business status and business rules; A process library construction module is used to construct a process database, which includes data fields, node status, process node identifiers, and process processing stage information. The process database and the basic database establish a data mapping relationship through associated fields; The node relationship definition module is used to constrain the operation permissions of process nodes using the business rules of the basic database and determine the relationship between nodes based on the current node identifier of the process database and the business status of the basic database; The query editing module is used to display operation buttons based on the associated fields of the basic database and the node status of the process database, and to implement cross-form data query or editing by binding the process model and the associated fields; The operation configuration module is used to use the business status of the basic database and the node status of the process database to display the current approval progress and configure the actionable buttons according to the business rules and operation permissions; The state processing module is used to configure custom scripts to update the business status of the basic database and the node status of the process database according to the data mapping relationship, create a process model, configure process events, define process approval nodes and process rules, ensure process jumps after status changes, and form end-to-end state synchronization.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the configurable processing method for multi-form process event linkage as described in any one of claims 1 to 7 are implemented.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the configurable processing method for multi-form process event linkage as claimed in any one of claims 1 to 7 are implemented.

Images