What the Data for This Category Looks Like
The data sources for this category include ERP orders and inventory, BOM lists, process routes, equipment capacity, staff shifts, work-in-progress inventory, and supplier delivery information. Data update frequencies are daily, weekly, or triggered when documents such as sales orders, delivery change notices, and material shortage lists are generated. Daily processed documents include sales orders, master production plans, material requirement plans, weekly production scheduling tables, work orders, material shortage lists, and delivery change notices. Core fields include order number, material code, capacity man-hours, work-in-progress quantity, and delivery date. Units include man-hours, pieces, days, and others.
What Constraints These Characteristics Impose on the "Workflow Orchestration" Link
Multi-source data with non-fixed update cycles typically requires workflows to support a combination of event-triggered and scheduled triggering modes, to avoid unnecessary execution. Large differences in field structures across multiple types of documents require workflows to be configured with flexibly adjustable document parsing rules, to adapt to field extraction requirements for different business documents. Scheduling calculations rely on real-time capacity and material constraint data, requiring real-time data transfer between workflow nodes to avoid using expired business information. Unpredictable trigger scenarios such as urgent order additions, material shortages, and equipment failures require workflows to have built-in configurable exception branch processing logic.
How to Set Configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
variables | Map to document fields as ["orderNo", "materialCode", "capacityHour", "deliveryDate"] | Match core fields of production planning documents, to facilitate subsequent verification and scheduling calculations |
nodeId | Configure unique IDs for the data verification node, scheduling calculation node, and exception handling node respectively | Facilitate locating workflow execution logs and error nodes, to quickly troubleshoot issues |
| Trigger Mode | Trigger based on data update events; fixed-cycle triggering is used for regular weekly scheduling tasks | Adapt to real-time trigger requirements for orders and exception changes, while balancing execution efficiency for regular scheduling |
| Global Variable Initialization | Set the initial value to the same-day inventory data synchronized from ERP | Cover basic material and capacity constraints, reduce real-time query times, and improve execution speed |
| Document Parsing Rules | Configure field extraction rules separately by document type | Adapt to different field structures of sales orders, work orders, and material shortage lists, to ensure accurate data extraction |
| Node Timeout Setting | 600 seconds | Match the typical time required for scheduling calculations, to avoid workflow interruptions caused by node blocking |
This page was written based on FastGPT v4.17.0.
Three Common Mistakes
- Phenomenon: After assigning a global variable string array, the array read by subsequent nodes contains duplicate historical content. Cause: The array was not explicitly initialized as empty in the
variablesconfiguration, causing content returned by AI replies each execution to be appended to the existing array. - Phenomenon: After clicking export workflow, the generated configuration file cannot load properly in other environments. Cause: The option to include associated data source configuration items was not checked during export, causing the target environment to fail to recognize the data source.
- Phenomenon: When accessing the workflow via API, the passed global variables are not correctly read by the nodes. Cause: Business data was not passed in the request body in the format required by
variables, causing nodes to fail to obtain core information such as orders and capacity.
How to Confirm Proper Configuration
- Manually trigger the workflow, check whether the fields corresponding to
variablesin the node logs match the current business data. - Simulate an exception order change, verify whether the workflow triggers the preset exception handling branch.
- Export the workflow configuration file, check whether all configured nodes and variable rules are included in the file.
- Call the API test, confirm that the parameters in the request body are correctly parsed by the workflow nodes.
The values provided here are common starting points and should be measured against the reader's own samples.