This page configuration is based on FastGPT v4.17.0
What the Data for This Category Looks Like
Business data for foundry (sand molding, precision casting, die casting) comes primarily from ERP material master data, melting furnaces, thermometers, spectrometers, MES heat records, mold management systems, and customer drawings. Daily produced documents include foundry process cards, batching lists, heat records, mold histories, first article inspection records, material test reports, and nonconforming product review forms.
Data updates occur per heat, per batch, or daily. Fields include alloy composition parameters, melting temperature, pouring duration, heat number, mold number, return charge ratio parameters, and others. There is no fixed unified format, and field formats must be matched to specific business scenarios.
What Constraints Do These Characteristics Impose on Workflow Orchestration
Multiple data sources and high update frequencies require the workflow to connect multiple heterogeneous data source nodes, and use variable mapping to match field formats across different systems. Business document fields are specialized and lack unified standards, so the workflow must include a dedicated field verification step to prevent document errors caused by parameter mismatches.
Workflow triggers must be bound to specific business events to adapt to the update rhythm of each heat. Error consequences are severe, so the workflow must add an exception verification branch. This branch conducts threshold checks on core fields such as batching ratios and melting parameters, and blocks unqualified data from entering the document generation stage.
Configuration Settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Global Variables | Map heat and material fields from ERP and MES systems, bind to the variables parameter passed via URL | Match core data sources for foundry business, support quick passing of business data for a specific heat |
| Node Invocation | Call pre-created foundry text processing nodes, associate nodeId to existing applications | Reuse existing document processing logic, avoid repeated configuration of specialized field mappings |
| Logging | Enable full-node logging, retain logs for 7 days | Track exceptions in batching verification and parameter judgment, meet quality traceability requirements |
| Workflow Trigger | Trigger on heat completion event, set timeout threshold of 300 seconds | Adapt to the update frequency of each heat, match average processing duration of melting and inspection stages |
| URL Parameter Passing | Enable parameter inclusion switch, specify variable name corresponding to heat ID | Support quick passing of specific business data via shared links, simplify manual input processes |
| Exception Handling | Configure verification rules for batching ratios and melting temperatures, set thresholds based on actual measurements | Block unqualified data, avoid generating incorrect process documents or exception reports |
Three Common Configuration Errors
- Phenomenon: Existing text processing nodes cannot be invoked after an upgrade, and workflow execution reports "node type does not exist". Cause: Legacy text processing node configurations were not migrated to the new workflow node library, and foundry-specific fields were not remapped.
- Phenomenon: After calling a pre-configured exception report generation plugin, no corresponding execution record appears in the conversation log. Cause: The logging switch for plugin calls was not enabled in the workflow, and the
variablesparameter for passing log context was not bound. - Phenomenon: After passing a heat ID via a shared URL, global variables do not take effect. Cause: The mapping key name corresponding to the global variable was not specified in the URL parameters, and the URL parameter inclusion configuration was not enabled.
How to Verify Successful Configuration
- Check variable mappings for workflow nodes, confirm that each foundry business field corresponds to the correct configuration item.
- Trigger a test workflow, pass simulated heat data, and verify that execution logs for all nodes are complete.
- Test the URL parameter inclusion function, pass a specified heat ID, and confirm that global variables load correctly.
- Call associated plugins or applications, and verify that process documents or exception report drafts conforming to foundry business formats are generated.
The values provided are common starting points and should be evaluated against the reader's own samples.