Multi-source task-oriented material flow synthesis method and device and storage medium

Abstract

The invention provides a multi-source task-oriented material flow synthesis method and device and a storage medium, and relates to the technical field of automatic material management. The method comprises the following steps: monitoring a towed form and verifying a drop point, correcting a node connection line, and receiving node attribute configuration information; a supplier blacklist is monitored based on a Rete algorithm, budget is monitored by means of a Boolean algebraic optimization algorithm, and an alarm is generated when abnormity occurs; based on the request import form, receiving configuration information, and updating and storing the configuration information; calling data connector configuration parameters, and synchronizing the form data and the parameters to a material platform. According to the method, a full-process automatic material management system is constructed, form node visual arrangement is realized, the operation threshold is reduced, the risk is accurately identified and early warning is performed, the data barrier is broken through, the construction efficiency is improved, the risk control capability and cross-platform collaboration are improved, and the problems of much manual intervention, slow response and data island in the traditional process are solved.

Description

Technical Field

[0001] This invention mainly relates to the field of automated material management technology, specifically to a material flow synthesis method, apparatus, and storage medium for multi-source tasks. Background Technology

[0002] In the field of automated material management technology, traditional material flow management models have several limitations and are difficult to adapt to the efficient collaboration needs of enterprises with multiple tasks. Firstly, process setup relies on manual coding or complex configuration by technical personnel, resulting in low participation from non-technical staff (such as purchasing and finance personnel). Furthermore, the association between forms and process nodes requires repeated manual debugging, leading to long setup cycles, slow response to business needs, and an inability to quickly adapt to changes in various scenarios such as material procurement and inventory management. Secondly, supplier management and budget control lack intelligent means: supplier blacklist identification relies on manual queries of Excel spreadsheets or ERP systems, which can easily lead to cooperation with untrustworthy suppliers due to information delays or human error, causing business risks. Budget monitoring is mostly based on post-event statistics, failing to verify the matching of purchase amounts with budget limits in real time. Problems are often discovered only after over-budget purchases, and there is a lack of automatic early warning mechanisms, resulting in passive financial risk control. Third, data silos exist between form data and the material platform: After the form is configured, data needs to be manually entered into the material management platform, which is not only time-consuming and labor-intensive, but also prone to data errors due to manual input (such as material code input deviations). Furthermore, the data connector parameter configuration is complex, cross-system data synchronization efficiency is low, and it is difficult to achieve data collaboration across the entire material flow. These problems collectively lead to the pain points of traditional material flow management: excessive manual intervention, low efficiency, high risk, and poor data collaboration. Therefore, a comprehensive end-to-end solution integrating visual orchestration, intelligent monitoring, efficient configuration, and cross-platform synchronization is urgently needed. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a material flow synthesis method, apparatus and storage medium for multi-source tasks, which addresses the shortcomings of the prior art.

[0004] The technical solution of this invention to solve the above-mentioned technical problems is as follows: A material flow synthesis method for multi-source tasks, comprising: When a form is detected being dragged to the visual orchestration interface, the landing point of the form is verified, and the logical relationship between nodes established by the user by dragging and connecting from the node component library is corrected. When the verification passes, the node attribute configuration information is received through the node attribute configuration window. The supplier blacklist is monitored based on the Rete algorithm, and the budget is monitored based on the Boolean algebra optimization algorithm. If a blacklist is detected or a budget overrun is detected, an alarm is generated. Based on the user's form configuration request, the form is imported into the form configuration interface. The form configuration information is received based on the form configuration attribute panel, and the form content is updated based on the form configuration information. After configuration, the updated form is saved based on the set save format. The data connector is invoked, its parameters are configured, and the updated data in the form is retrieved. The data in the form and the configured data connector parameters are then synchronized to the designated material platform.

[0005] Another technical solution of the present invention to solve the above-mentioned technical problems is as follows: A material flow synthesis device for multi-source tasks, comprising: The form drag-and-drop module is used to verify the landing point of the form when it is detected that a form is dragged to the visual arrangement interface, and to correct the logical relationship between nodes established by the user by dragging and connecting them from the node component library. When the verification is successful, node attribute configuration information is received through the node attribute configuration window. The monitoring module is used to monitor the supplier blacklist in the node attribute configuration information based on the Rete algorithm, and to monitor the budget in the node attribute configuration information based on the Boolean algebra optimization algorithm. If a blacklist is detected or a budget overrun is detected, an alarm message is generated. The form configuration module is used to import the form into the form configuration interface based on the user's form configuration request, receive form configuration information based on the form configuration attribute panel, update the form content based on the form configuration information, and save the updated form according to the set save format after configuration. The synchronization module is used to call the data connector, configure the parameters of the data connector, call the configured data connector to obtain the data in the updated form, and synchronize the data in the form and the configured data connector parameters to the specified material platform.

[0006] Another technical solution of the present invention to solve the above-mentioned technical problems is as follows: a material flow synthesis device for multi-source tasks, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the material flow synthesis method for multi-source tasks as described above.

[0007] Another technical solution of the present invention to solve the above-mentioned technical problems is as follows: a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the material flow synthesis method for multi-source tasks as described above.

[0008] The beneficial effects of this invention are as follows: Through four core steps—drag-and-drop form arrangement, Rete algorithm and Boolean algebra optimization algorithm data monitoring, form configuration update, and data connector synchronization—a fully automated material flow management system is constructed. This not only enables the visual and rapid arrangement of forms and nodes, reducing the operational threshold for non-technical personnel, but also accurately identifies supplier blacklists and budget overrun risks and provides timely warnings. At the same time, by using data connectors to break down data barriers between forms and material platforms, the overall efficiency of material flow construction, risk control capabilities, and cross-platform data collaboration capabilities are improved, solving the problems of excessive manual intervention, slow response, and data silos in traditional material flows. Attached Figure Description

[0009] Figure 1 A flowchart of a material flow synthesis method provided in an embodiment of the present invention; Figure 2 This is a block diagram of a material flow synthesis device provided in an embodiment of the present invention. Detailed Implementation

[0010] The principles and features of the present invention are described below with reference to the accompanying drawings. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0011] Example 1: As Figure 1 As shown, this embodiment of the invention provides a material flow synthesis method for multi-source tasks, including: When a form is detected being dragged to the visual orchestration interface, the landing point of the form is verified, and the logical relationship between nodes established by the user by dragging and connecting from the node component library is corrected. When the verification passes, the node attribute configuration information is received through the node attribute configuration window. The supplier blacklist is monitored based on the Rete algorithm, and the budget is monitored based on the Boolean algebra optimization algorithm. If a blacklist is detected or a budget overrun is detected, an alarm is generated. Based on the user's form configuration request, the form is imported into the form configuration interface. The form configuration information is received based on the form configuration attribute panel, and the form content is updated based on the form configuration information. After configuration, the updated form is saved based on the set save format. The data connector is invoked, its parameters are configured, and the updated data in the form is retrieved. The data in the form and the configured data connector parameters are then synchronized to the designated material platform.

[0012] In the above embodiments, a fully automated material flow management system is constructed through four core steps: drag-and-drop form arrangement, dual-algorithm monitoring (Rete algorithm + Boolean algebra optimization algorithm), form configuration update, and data connector synchronization. This system not only enables visual and rapid arrangement of forms and nodes, reducing the operational threshold for non-technical personnel, but also accurately identifies supplier blacklists and budget overrun risks and provides timely warnings. At the same time, by using data connectors to break down data barriers between forms and material platforms, the system comprehensively improves the efficiency of material flow construction, risk control capabilities, and cross-platform data collaboration capabilities, solving the problems of excessive manual intervention, slow response, and data silos in traditional material flows.

[0013] Preferably, when a form is detected being dragged into the visual orchestration interface, the form's landing point is validated, and the logical relationships between nodes established by the user through dragging and connecting from the node component library are corrected. When the validation passes, node attribute configuration information is received through the node attribute configuration window, including: The front-end drag-and-drop monitoring component identifies the user's drag-and-drop action from the form resource area to the canvas work area. When a drag-and-drop action is identified, the validity of the form landing point is verified. When the verification passes, the appropriate node component library is loaded based on the business scenario associated with the drag-and-drop form. Based on the loaded node component library, the user's operation of dragging and dropping the target node to the visual orchestration interface is monitored, and the connection between nodes is established by dragging from the outgoing port to the incoming port, and the metadata associated with the node and the connection is recorded. Based on the BPMN specification, the connection between nodes is corrected, including adjusting the direction of reverse connections, deleting duplicate connections, and deleting invalid connections. Once the connection correction is complete, the basic structure and data logic are verified sequentially based on the legality rule base of the invoked process logic. When the verification passes, the node attribute configuration information is received through the node attribute configuration window.

[0014] For example: Step 1, Wiring calibration triggered: By using front-end listening components (such as Vue / React-based event listener mechanisms), the system captures user connection operations in the visual orchestration interface in real time. When a user completes the action of "dragging from the upstream node's outgoing port to the downstream node's incoming port and releasing the mouse", and the system records the connection metadata (including connection ID, upstream node ID, downstream node ID, and connection type), the connection correction process is automatically triggered. It also supports manual triggering by the user, that is, the user clicks the "Connection Correction" button in the canvas toolbar to perform batch correction on all created connections in the current canvas.

[0015] Once the calibration process is initiated, the core constraint rules related to "node connection logic" in the BPMN specification are loaded from the background rule base. These rules include "start node is only allowed to send out connections (cannot be a downstream node)", "end node is only allowed to send in connections (cannot be an upstream node)", "only one connection of the same type is allowed between the same pair of nodes", and "connections must be clearly associated with upstream and downstream nodes (cannot be broken)". These rules serve as the basis for subsequent calibration operations.

[0016] Step 2, adjust the direction of the reverse connection: Traverse all connections to be corrected within the current canvas, and based on the node role attributes (start node, end node, normal task node, gateway node) in the BPMN specification, determine whether the connection direction is reversed: Scenario 1: If the upstream node of the connection is an "end node" (only incoming connections are allowed according to the BPMN specification), and the downstream node is a normal task node / start node, then it is determined as an "outgoing connection from the end node and reverse connection". Scenario 2: If the upstream node of the connection is a normal task node / end node and the downstream node is a "start node" (only outgoing connections are allowed according to the BPMN specification), then it is determined as "start node incoming connection reverse connection". Scenario 3: If the upstream and downstream nodes of the connection are ordinary task nodes, but the node metadata is marked "only one-way flow is allowed" (e.g., "supplier verification node" is only allowed to flow to "budget monitoring node", and cannot flow in the opposite direction), then it is determined to be "business logic reverse connection".

[0017] For the identified reverse connections, perform automatic adjustments: Exchange the metadata of the "upstream node ID" and "downstream node ID" of the connection, and correct the reverse connection to "the forward connection that conforms to the node role / business logic" (e.g., "end node → ordinary node" is corrected to "ordinary node → end node"). Synchronously update the visual display of the connections within the canvas: automatically adjust the arrow direction of the connections (ensuring the arrow points to the downstream node) and the path (keeping the connections smooth and avoiding overlap with other nodes / connections), and at the same time pop up a temporary prompt box next to the connection (such as "Reverse connection has been corrected, current direction: Supplier verification node → Budget monitoring node") to inform the user of the adjustment result.

[0018] Step 3, delete duplicate connections: All connections are grouped and statistically analyzed based on the combined dimension of "upstream node ID - downstream node ID - connection type": If there are two or more connections within the same group (i.e., the same upstream node, the same downstream node, and the same connection type, such as all being "sequential connections" or all being "conditional branch connections"), then it is determined to be a "duplicate connection". For example, there are two "sequential connections" between "start node → supplier verification node", or two "conditional branch connections" between "budget monitoring node → financial approval node" (both with the condition 'budget sufficient'), which are both considered duplicate connections.

[0019] Duplicate connection deletion: For identified duplicate connections, the system performs deletion operations according to "creation time priority". The earliest created connection is retained (based on the creation timestamp in the connection metadata) to ensure that the core process logic is not affected; Automatically delete other duplicate connections, and pop up a prompt box at the bottom of the canvas (such as "2 duplicate connections have been deleted: Start node → Supplier verification node (sequential connection), keep the connection created on 2024-05-20 10:00:00"), and record the ID of the deleted connection and the creation time in the operation log for easy traceability later; If a user manually selects a duplicate line and marks it "Keep this line", the user-specified line will be kept first, and other duplicates will be deleted, improving operational flexibility.

[0020] Step 4, delete invalid connections: In accordance with the constraint in the BPMN specification that "connections must clearly link upstream and downstream nodes," the integrity of the connections is verified: Scenario 1: "Disconnected connection" - The connection is only associated with the upstream node (no downstream node, i.e. the downstream node ID is empty) or only associated with the downstream node (no upstream node, i.e. the upstream node ID is empty). For example, if the user drags the connection to a blank area of ​​the canvas without connecting to a node, or deletes a node associated with the connection without deleting the corresponding connection. Scenario 2: "Invalid Node Connection" - The upstream / downstream node associated with the connection has been marked as "deleted" (i.e., the "status" field in the node metadata is "deleted"), but the connection has not been deleted synchronously, resulting in the connection being associated with a non-existent node.

[0021] Invalid connection deletion: For identified invalid connections, the system performs the following operations: Automatically delete all invalid connections to prevent them from consuming canvas resources or interfering with process logic. Invalid connections that are about to be deleted are temporarily marked with a flashing red border within the canvas (for 3 seconds), prompting the user that "The following connections will be deleted because they are not associated with valid nodes: Connection IDs xxx and xxx", thus enhancing user awareness; After deletion, the canvas connection statistics are updated synchronously (e.g., "Current valid connections: 5, invalid connections deleted: 2"), and the metadata cache of invalid connections is cleared to ensure data consistency.

[0022] Step 5, Feedback on calibration results: The entire dataset from this correction is compiled and a "Connection Correction Result Report" is generated, displayed in a pop-up panel on the right side of the canvas. The report includes the following: "Adjust reverse connections: 2", "Delete duplicate connections: 3", "Delete invalid connections: 2"; Each correction operation includes the connection ID, original problem description (e.g., "reverse connection: end node → normal node"), correction method (e.g., "adjust to normal node → end node"), and correction time. If there are connection problems that cannot be automatically corrected (such as "the connection crosses multiple gateway nodes and the path needs to be manually adjusted"), the problem details and manual handling suggestions will be marked in red.

[0023] After the user views the calibration result report, they can click the "Confirm Calibration" button. The system will then save the connection metadata after this calibration (updating the front-end canvas data model and the back-end database). If the user clicks "Recalibrate," steps 2-4 will be executed again to ensure that the calibration result meets expectations. After calibration is complete, the system will unlock the node attribute configuration function, allowing the user to proceed to the next step of node attribute configuration and achieve seamless integration of workflow orchestration.

[0024] The above embodiments refine the entire process of form drag-and-drop and node configuration. Front-end drag-and-drop monitoring accurately identifies form drag-and-drop actions and verifies the landing point. Adaptive node component libraries are loaded based on business scenarios to ensure node-business compatibility. Connections are corrected according to BPMN specifications, and process logic is verified according to a rule base, ensuring a complete process structure, business compliance, and data matching. Its technical effect lies in optimizing process orchestration from three aspects: operational accuracy, business adaptability, and logical legality. It avoids process failures caused by incorrect form landing points, mismatched nodes, and chaotic connection logic, significantly improving the accuracy and standardization of material process orchestration and shortening the debugging cycle after process setup.

[0025] Preferably, monitoring the supplier content in the node attribute configuration information using the Rete algorithm to perform supplier blacklist monitoring includes: Based on the supplier configuration standard fields, the supplier content that matches the supplier configuration standard fields is parsed from the node attribute configuration information and marked as the supplier monitoring data source. The supplier blacklist rules are then loaded from the rule engine. For example: Supplier blacklist rules: Store the "set of conditions for determining a supplier to be blacklisted", such as "Rule 1: Supplier ID is in the blacklist table of the ERP system → determined to be blacklisted"; Rule 2: Supplier name contains the keywords 'dishonest' or 'abnormal' → determined to be blacklisted; Rule 3: Supplier belongs to a high-risk industry (such as illegal finance) and has no compliance qualification certificate → determined to be blacklisted. Each rule contains a unique rule ID, condition expression, and priority (such as rule 1 has higher priority than rule 2 because ID matching is more accurate).

[0026] Construct a Rete inference network, which includes a root node, a type node, an α node, and a β node. Using the supplier monitoring data source as input, a root node of the Rete inference network is created, and type nodes are created based on the field types of the supplier data. Each type node corresponds to a field used to filter data that matches the field type. Each condition in the supplier blacklist rule is broken down into atomic conditions, and an α node is created for each atomic condition. For rules that require a combination of multiple atomic conditions, a β node is created. For example, creating an α node: Rule 1, “Supplier ID is in the ERP system blacklist table”, is broken down into the atomic condition “Supplier ID ∈ blacklist ID set”. Node α1 is created, which contains the logic to “query the ERP blacklist table to obtain the ID set”. Rule 2, "Supplier name contains the keywords 'dishonest' or 'abnormal'", is broken down into the atomic condition "Supplier name LIKE '%dishonest%' OR Supplier name LIKE '%abnormal%'", creating an α2 node with built-in string fuzzy matching logic; Rule 3, “The supplier’s industry is a high-risk industry and has no compliance qualification certificate,” is broken down into two atomic conditions: “The supplier’s industry ∈ the list of high-risk industries” (node ​​α3) and “The supplier’s compliance qualification certificate = none” (node ​​α4). Create a beta node: For example, if Rule 3 requires an AND operation between node α3 (high-risk industry) and node α4 (no qualification certificate), create node β1, with the input being the output of nodes α3 and α4, and a built-in logic of "retaining data if both conditions are met simultaneously". All α nodes and β nodes are connected through "activation links" to form a complete Rete inference network. The network structure is stored in memory to avoid repeated construction.

[0027] When the supplier blacklist monitoring is triggered (e.g., when a user submits a form or a node begins execution), the supplier monitoring data first enters the root node. The root node distributes the data types in the supplier monitoring data to the corresponding type nodes according to the field type. The output results of each type node are pushed to the β node according to the rule association relationship. The β node judges according to the rule of multi-atomic condition combination. If at least one rule is activated, the current supplier is determined to be a blacklist supplier, and a supplier blacklist judgment result is generated. If all α nodes have no output, the current supplier is determined to be a non-blacklist supplier, and the judgment result is stored in the monitoring result cache.

[0028] In the above embodiments, a supplier blacklist monitoring system is implemented by constructing an inference network based on the Rete algorithm. Accurate supplier monitoring data sources are obtained by parsing node attribute configuration information. The blacklist rules are then broken down into atomic conditions, and corresponding α and β nodes are created, allowing data to flow and match efficiently according to field type. The technical effect lies in leveraging the Rete algorithm's characteristics of "reducing redundant calculations and rapid multi-condition matching" to achieve real-time (avoiding time-consuming manual queries and comparisons) and accuracy in supplier blacklist determination (multi-atomic condition combination judgment reduces the false judgment rate). This effectively blocks blacklisted suppliers from participating in the material flow, reducing the risk of enterprises cooperating with untrustworthy suppliers. Simultaneously, the determination results are stored in a cache for subsequent traceability, improving the intelligence level of supplier management.

[0029] Preferably, budget monitoring is performed on the budget content in the node attribute configuration information based on a Boolean algebra optimization algorithm, including: Based on the budget configuration standard field, the budget content that matches the budget configuration standard field is parsed from the node attribute configuration information and marked as the budget monitoring data source, and the budget monitoring condition expression is loaded from the rule engine; The budget monitoring condition expression is converted into a standard Boolean algebra format to obtain a Boolean expression, which is then marked as a budget monitoring execution rule. For example: Extracting variable symbols (such as C, T, D, S) from the "Budget Monitoring Execution Rule" (a simplified expression optimized by Boolean algebra, such as "C>T∨(C>D∧¬S)"): C → The "Current Purchase Amount" (the purchase amount entered by the user) parsed in the node attribute configuration; T → "Total Budget" (fixed threshold, such as total project budget) parsed in the node attribute configuration; D → Dynamic budget threshold (needs to be calculated synchronously from the financial system, such as "department monthly budget × 80%)); S → "Whether there is an over-budget approval form" (Boolean value, True if yes, False if no) is parsed in the node attribute configuration.

[0030] Based on the budget monitoring execution rules, the threshold rules are determined to be either dynamic threshold rules or fixed threshold rules. Based on the dynamic threshold rules or fixed threshold rules, the budget monitoring data source is monitored for budget overruns. If the Boolean expression output is true, it is determined that the current procurement has exceeded the budget, and a budget overrun determination result is generated. If the Boolean expression output is false, it is determined that the current procurement has not exceeded the budget.

[0031] For example: If the rule contains a dynamic threshold variable (such as D), call the "financial system connector" to pull the relevant data source in real time (such as the actual amount of the department's monthly budget, assuming it is 1 million yuan). Based on the "Dynamic Threshold Calculation Rules" (such as "Department Monthly Budget × 80%)" in the node attribute configuration, perform numerical calculation: 1 million × 80% = 800,000, to obtain the specific value of D (800,000). If it is a fixed threshold (such as T), the value of the "Total Budget" field in the "Budget Monitoring Data Source" (such as 500,000) can be read directly without additional calculation.

[0032] Substitute the field values ​​from the "Budget Monitoring Data Source" and the calculated dynamic threshold into the optimized Boolean expression: For example: Current purchase amount C=600,000, total budget T=500,000, dynamic threshold D=800,000, no over-budget approval form (S=False, therefore ¬S=True). Substitute the expression “C>T ∨ (C>D∧ ¬S)”: Calculate subexpression 1: C > T → 600,000 > 500,000 → the result is True; Calculate subexpression 2: C > D → 600,000 > 800,000 → the result is False; then perform an AND operation with ¬S(True) → False ∧ True = False; The final expression result is: True∨False = True (according to the Boolean algebra "OR operation" rule, the whole expression is judged as exceeding the budget).

[0033] Finally, the results are output in real time: The result of the expression calculation (True / False) is returned to the budget monitoring module in real time, serving as the direct basis for "over-budget determination": If the result is True, it is determined as "over budget", triggering the subsequent alarm process; If the result is False, it is determined as "not exceeding the budget" and the current monitoring period ends.

[0034] In the above embodiments, Boolean algebra optimization algorithms are used to optimize the budget monitoring process. First, the budget monitoring condition expressions are converted into standard Boolean format. Then, based on execution rules, dynamic / fixed thresholds are distinguished for budget overrun determination. The technical effect is that Boolean algebra simplifies budget rule expressions, reduces redundant calculation steps, and improves budget determination efficiency. Simultaneously, it accurately distinguishes threshold types, adapting to both rapid determination in fixed budget scenarios and flexible adaptation in dynamic budget scenarios (such as departmental monthly budget ratio thresholds). This ensures that budget monitoring covers multiple business scenarios, promptly identifies budget overrun risks, helps enterprises accurately control material procurement costs, and avoids financial risks caused by budget overruns.

[0035] Preferably, the form configuration information is received based on the form configuration attribute panel, and the form content is updated based on the form configuration information. After configuration, the updated form is saved according to the set save format, including: The form configuration information is received based on the form configuration attribute panel, the form configuration information is validated for legality, and the form content is updated based on the validated form configuration information. Upon receiving a user confirmation signal, the updated form is serialized according to the set saving format, synchronously stored in the preset form database, and a unique form identifier is generated.

[0036] Before the validity check, the process also includes the initialization of the visual orchestration interface (canvas) and the form. Specifically, it responds to the user's form configuration request, verifies the format validity of the form to be imported (such as whether it is a preset JSON / XML template or a blank form), parses the basic structure of the form (including field list, layout style, and related business scenarios) through the form parsing engine, loads the form into the visual configuration interface, and automatically generates the initial canvas (displaying the existing fields and layout of the form).

[0037] Next, users configure the form through the form configuration property panel (including tabs for field properties, layout styles, validation rules, etc.). The system receives input information in real time (such as modifying field names, adjusting the input type to "number", adding "required" validation, and setting the data source for the province, city, and district linkage component), and performs legality validation on the configuration information (such as no duplicate field names, correct validation rule syntax, and existence of linkage data source). Errors are marked and prompted in real time.

[0038] Based on the validated configuration information, the form content is dynamically updated: when field attributes change, the display name and input rules of the corresponding field in the canvas are updated synchronously; when the layout is adjusted (such as dragging fields to adjust their positions or merging form groups), the canvas layout is refreshed in real time; after the validation rules are configured, real-time validation feedback is added to the canvas (such as displaying a red prompt when an input error occurs).

[0039] After the user confirms the configuration, the save process is triggered. The system serializes the updated form according to the set save format (such as JSON format to store configuration metadata, and XML format to associate business rules), and synchronously stores it in the form database (recording form ID, configuration content, version number, and update time), and generates a unique form identifier (such as form code) to support subsequent process calls or secondary editing.

[0040] Finally, a success message (including the form preview entry) is displayed. If saving fails (e.g., due to a database connection error), the error reason is displayed, and the current configuration state is preserved. A snapshot of the form configuration (historical version) is automatically created, supporting configuration rollback (e.g., restoring to the last saved state) to ensure configuration security. The above embodiments clearly define the key steps in updating and saving form configurations. Configuration information is received and validated through the form configuration attribute panel to ensure compliance before updating the form. Finally, the form is serialized and stored according to a set format, generating a unique identifier. The technical advantages are: validation proactively avoids form configuration errors (such as missing fields or abnormal formats), reducing data problems in subsequent processes; serialization and unique identifiers ensure the traceability and uniqueness of form data, facilitating subsequent form calls, version management, and data queries, improving the accuracy and management efficiency of form configurations, and preventing material flow interruptions due to configuration errors or data storage chaos.

[0041] Preferably, the validity check includes field name check, input type check, required field check, and data source interface configuration information check. If the validity check fails, an error message is displayed.

[0042] The above embodiments refine the validity verification dimensions of form configurations, covering field names, input types, required fields, and data source interface configuration information verification, and annotate and prompt errors. Its technical effect lies in controlling the quality of form configurations from multiple dimensions: "basic field specifications" (name, type), "data integrity" (required fields), and "cross-system adaptability" (data source interface). Real-time error annotation allows users to quickly locate and correct errors, avoiding form unusability or data synchronization failures caused by duplicate fields, type mismatches, empty required fields, or incorrect interface configurations. This further improves the accuracy and efficiency of form configurations, laying a reliable data foundation for subsequent data flow and cross-platform synchronization in material processing.

[0043] Preferably, the process includes: invoking the data connector, configuring its parameters, retrieving updated data from the form, and synchronizing the form data and the configured data connector parameters to the designated material platform; The SAP connector call is triggered based on the user's model integration operation. First, the user's access permissions for connector calls and target form data are verified. If the permissions are granted, the SAP connector parameter configuration interface is loaded, guiding the user to configure basic connection parameters (SAP server address, system / client number, authentication information, timeout) and business interaction parameters (data synchronization scope, SAP interaction interface, form and SAP field mapping rules). The validity of parameter format, server connectivity, interface existence, and field mapping integrity is verified. After the verification is successful, the updated form data is extracted from the form database according to the synchronization scope. Null value fields are handled, data format is converted (adapting to SAP interface type / encoding), and special character filtering is preprocessed. Then, the configured SAP connector is called, and the preprocessed data is transmitted to the SAP system through the selected interaction interface to complete the data interaction. Finally, the form data and connector configuration parameters are encapsulated in the format required by the material platform, and the material platform data synchronization interface is called to achieve synchronization. After synchronization, the success / failure result is returned. If the failure occurs, the exception reason is recorded and retry is supported. At the same time, a synchronization log is generated and stored in the system.

[0044] Example 2: This embodiment of the invention also provides a material flow management device for multi-source tasks, including: The form drag-and-drop module is used to verify the landing point of the form when it is detected that a form is dragged to the visual arrangement interface, and to correct the logical relationship between nodes established by the user by dragging and connecting them from the node component library. When the verification is successful, node attribute configuration information is received through the node attribute configuration window. The monitoring module is used to monitor the supplier blacklist in the node attribute configuration information based on the Rete algorithm, and to monitor the budget in the node attribute configuration information based on the Boolean algebra optimization algorithm. If a blacklist is detected or a budget overrun is detected, an alarm message is generated. The form configuration module is used to import the form into the form configuration interface based on the user's form configuration request, receive form configuration information based on the form configuration attribute panel, update the form content based on the form configuration information, and save the updated form according to the set save format after configuration. The synchronization module is used to call the data connector, configure the parameters of the data connector, call the configured data connector to obtain the data in the updated form, and synchronize the data in the form and the configured data connector parameters to the specified material platform.

[0045] Preferably, when a form is detected being dragged into the visual orchestration interface, the form's landing point is validated, and the logical relationships between nodes established by the user through dragging and connecting from the node component library are corrected. When the validation passes, node attribute configuration information is received through the node attribute configuration window, including: The front-end drag-and-drop monitoring component identifies the user's drag-and-drop action from the form resource area to the canvas work area. When a drag-and-drop action is identified, the validity of the form landing point is verified. When the verification passes, the appropriate node component library is loaded based on the business scenario associated with the drag-and-drop form. Based on the loaded node component library, the user's operation of dragging and dropping the target node to the visual orchestration interface is monitored, and the connection between nodes is established by dragging from the outgoing port to the incoming port, and the metadata associated with the node and the connection is recorded. Based on the BPMN specification, the connection between nodes is corrected, including adjusting the direction of reverse connections, deleting duplicate connections, and deleting invalid connections. Once the connection correction is complete, the basic structure and data logic are verified sequentially based on the legality rule base of the invoked process logic. When the verification passes, the node attribute configuration information is received through the node attribute configuration window.

[0046] Example 3: This embodiment of the invention also provides a material flow synthesis device for multi-source tasks, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the material flow synthesis method for multi-source tasks as described above.

[0047] Example 4: This embodiment of the invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the material flow synthesis method for multi-source tasks as described above.

[0048] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0049] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described apparatus and unit can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0050] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0051] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0052] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0053] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for multi-source task-oriented material flow synthesis, characterized in that, Comprise: When monitoring the form dragged into the visual arrangement interface, verify the form drop point, correct the logical relationship between nodes established by the user dragging the connection line from the node component library, and when the verification is passed, receive node attribute configuration information through the node attribute configuration window; Based on the Rete algorithm, the supplier blacklist monitoring is performed on the supplier content in the node attribute configuration information, and based on the Boolean algebra optimization algorithm, the budget monitoring is performed on the budget content in the node attribute configuration information, and if the blacklist condition or the over-budget condition is monitored, an alarm information is generated; Based on the user's form configuration request, the form is imported into the form configuration interface, the form configuration information is received based on the form configuration attribute panel, and the form content is updated based on the form configuration information, and after the configuration is completed, the updated form is saved based on the set save format; Call the data connector, configure the parameters of the data connector, and call the data connector after the configuration is completed to obtain the data in the updated form, and synchronize the data in the form and the configured data connector parameters to the specified material platform.

2. The process of claim 1, wherein, When monitoring the form dragged into the visual arrangement interface, verify the form drop point, correct the logical relationship between nodes established by the user dragging the connection line from the node component library, and when the verification is passed, receive node attribute configuration information, including: Based on the front-end drag-and-drop listening component, identify the form dragging action of the user from the form resource area to the canvas work area, and when identifying that there is a dragging action, verify the validity of the form drop point; When the verification is passed, load the adapted node component library based on the associated business scenario of the dragged form, listen to the user's operation of dragging the target node to the visual arrangement interface based on the loaded node component library, and establish the connection line between the nodes through the out-line port to the in-line port dragging, and record the metadata associated with the nodes and the connection line; Correct the connection line between nodes based on the BPMN specification, which includes adjusting the reverse connection direction, deleting duplicate connections, and deleting invalid connections; When the connection correction is completed, the basic structure and data logic are sequentially verified based on the called flow logic legality rule library; When the verification is passed, receive node attribute configuration information through the node attribute configuration window.

3. The process of claim 1, wherein, Based on the Rete algorithm, the supplier blacklist monitoring is performed on the supplier content in the node attribute configuration information, including: Based on the supplier configuration standard field, the supplier content matching the supplier configuration standard field is parsed from the node attribute configuration information, and is marked as a supplier monitoring data source, and the supplier blacklist rule is loaded from the rule engine; A Rete reasoning network is constructed, which includes a root node, a type node, an alpha node and a beta node, The root node of the Rete reasoning network is created with the supplier monitoring data source as the input, and the type node is created based on the field type of the supplier data, and each type node corresponds to a field for filtering data conforming to the field type, The conditions in the supplier blacklist rule are disassembled into atomic conditions, and an alpha node is created for each atomic condition, and a beta node is created for rules that require multi-atomic condition combination; When the supplier blacklist monitoring opportunity is triggered, the supplier monitoring data first enters the root node, the root node distributes the data types in the supplier monitoring data to the corresponding type nodes according to the field type, and the output results of each type node are pushed to the beta node according to the rule association relationship, the beta node judges according to the rule of multi-atomic condition combination, if there is at least one rule activated, it is judged that the current supplier is a blacklisted supplier, and a supplier blacklist judgment result is generated, if all alpha nodes have no output, it is judged that the current supplier is a non-blacklisted supplier, and the judgment result is stored in the monitoring result cache.

4. The process of claim 1, wherein, The budget content in the node attribute configuration information is monitored based on a Boolean algebra optimization algorithm, including: The budget content matching the budget configuration standard field is parsed from the node attribute configuration information based on the budget configuration standard field, and is marked as a budget monitoring data source, and the budget monitoring condition expression is loaded from the rule engine; The budget monitoring condition expression is converted into a Boolean algebra standard format to obtain a Boolean expression, and is marked as a budget monitoring execution rule; Based on the budget monitoring execution rule, the threshold rule is determined to be a dynamic threshold rule or a fixed threshold rule, and the budget monitoring data source is monitored based on the dynamic threshold rule or the fixed threshold rule, if the Boolean expression output result is true, it is judged that the current procurement exists over budget, and a budget overruns judgment result is generated, if the Boolean expression output result is false, it is judged that the current procurement is not over budget.

5. The process of claim 4, wherein, The form configuration information is received based on the form configuration attribute panel, and the form content is updated based on the form configuration information, and after configuration is completed, the updated form is saved based on the set saving format, including: The form configuration information is received based on the form configuration attribute panel, and the form configuration information is verified for legality, and the form content is updated based on the verified form configuration information; When a user confirmation configuration signal is received, the updated form is serialized according to the set saving format, and is stored synchronously in a preset form database, and a unique form identifier is generated.

6. The process of claim 5, wherein, The legality verification includes field name verification, input type verification, mandatory item verification and data source interface configuration information verification, if the legality verification fails, an error item annotation prompt information is provided.

7. A method for multi-source task-oriented material flow synthesis, characterized in that, Including: The form drag module is used to verify the form drop point when the form is dragged into the visual arrangement interface, and the logical relationship between the nodes established by the user dragging the connection in the node component library is corrected, and when the verification is passed, the node attribute configuration information is received through the node attribute configuration window; The monitoring module is used to monitor the supplier content in the node attribute configuration information based on the Rete algorithm, and monitor the budget content in the node attribute configuration information based on the Boolean algebra optimization algorithm, if the blacklist condition or the over budget condition is monitored, an alarm information is generated; The form configuration module is configured to import the form into a form configuration interface based on a form configuration request of a user, receive form configuration information based on a form configuration attribute panel, update form content based on the form configuration information, and save the updated form based on a set saving format after the configuration is completed. The synchronization module is configured to call a data connector, configure parameters of the data connector, call the data connector after the configuration is completed, obtain data in the updated form, and synchronize the data in the form and the configured data connector parameters to a designated material platform.

8. The process of claim 7, wherein, When a form dragged to a visual arrangement interface is monitored, the landing point of the form is verified, the logical relationship between nodes established by the user through the connection line is corrected, and when the verification is passed, node attribute configuration information is received through a node attribute configuration window, including: A front-end drag listening component is used to identify a form drag action from a form resource area to a canvas work area, and when the drag action is identified, the effectiveness of the form landing point is verified. When the verification is passed, an adapted node component library is loaded based on the associated business scenario of the dragged form, the user's operation of dragging a target node to the visual arrangement interface is listened to based on the loaded node component library, and the connection line between the nodes is established through the out-line port to the in-line port, and the metadata associated with the nodes and the connection line is recorded. The connection line between the nodes is corrected based on the BPMN specification, and the correction of the connection line between the nodes includes adjusting the reverse connection direction, deleting duplicate connections, and deleting invalid connection lines. When the connection line correction is completed, the basic structure and data logic are sequentially verified based on a called flow logic legality rule library. When the verification is passed, node attribute configuration information is received through a node attribute configuration window.

9. A multi-source task oriented material flow process synthesis apparatus, characterized by, The computer program is stored in the memory and executable on the processor, and the processor executes the computer program to implement the material flow synthesis method for multi-source tasks according to any one of claims 1 to 6.

10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. When the computer program is executed by the processor, the material flow synthesis method for multi-source tasks according to any one of claims 1 to 6 is implemented.

Images