What data for this category looks like
Data sources for this category include ERP/WMS systems, barcode or RFID collection devices, procurement and production work orders, bin location information, AGV conveying systems, and weighing data. Daily generated documents cover receiving slips, putaway slips, material requisition and return slips, inventory transfer slips, inventory count sheets, lot ledgers, first-in first-out records, and expiration date records. Data update frequencies fall into three categories: real-time (such as barcode scanning for inbound storage and AGV scheduling), daily (such as inventory summaries), and monthly inventory updates. Common document fields include material code, lot number, bin location number, expiration date, inventory quantity, and inspection status. Units include pieces, kilograms, cubic meters, and others.
Constraints imposed by these characteristics on workflow orchestration
Data sources for this category are scattered, and their update frequencies vary widely. Workflow orchestration must support different trigger logic, including real-time pulling of barcode scanning data and scheduled synchronization of ERP inventory data. Lot number, expiration date, and inspection status are core validation fields. Workflows must set required field rules and format validation logic in advance to prevent invalid data from entering the quotation stage. Field mapping rules differ across document types. Workflows must configure unified field conversion nodes to ensure consistent access to information from documents such as receiving slips and material requisition slips. Additionally, the business requirement for consistent book and physical inventory requires embedding a data verification link in the workflow to mark and route inventory discrepancy data.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Trigger Timing | Triggered by document generation event, execute after a delay of 600 seconds | Matches the real-time update rhythm of warehousing data, avoids pulling incomplete document data |
variables Configuration | Preset material code, lot number, and expiration date as required variables | Covers the core validation fields of this category, reduces subsequent data cleaning costs |
| Node Dependency Rule | Start the quotation generation node only after the node with nodeId "WMS Data Pull" completes execution | Ensures quotation data comes from the latest warehousing inventory information |
| Retry Count | Maximum 3 times, with an interval of 120 seconds between each attempt | Addresses temporary exceptions in barcode scanning and AGV data transmission |
| Field Mapping Rule | Match the conversion relationship of corresponding fields by document type | Adapts to field differences across different documents such as receiving slips and material requisition slips |
| Timeout Threshold | 1800 seconds | Covers the batch pulling and processing duration of monthly inventory data |
Three common configuration errors
- An uncaught exception occurs when the workflow runs an AI conversation component, with no clear error log. Cause: Required fields in
variablesare not configured properly, leading to missing core parameters during invocation. - After adding a custom warehousing data pull plugin, no input or output parameters appear for workflow nodes. Cause: The plugin's parameter mapping rule is not enabled in the workflow configuration, or category-specific data fields are not associated.
- Lot or expiration date information is missing from quotation documents generated by the workflow. Cause: The trigger timing is set too early, and the WMS data pull node has not finished executing, so complete warehousing data is not obtained.
How to verify a correct configuration
- Manually trigger the workflow, and check if the WMS data pull node successfully pulls field data from receiving slips and lot ledgers.
- Simulate passing document data missing a lot number into the workflow, and confirm that the field validation interceptor activates.
- View workflow logs in FastGPT v4.17.0, and confirm that node execution follows the preset dependency rules.
- Test a temporary network exception scenario, and confirm that the workflow automatically enters the exception handling branch after reaching the maximum retry count.
The values provided are common starting points and should be evaluated against the reader's own samples.