What this category's data looks like
Data for this category includes quarantine certificates, slaughter and cutting records, ingredient marinating records, thermal processing records, cold chain temperature records, microbial test reports, and more. Data sources cover animal quarantine information, supplier batch ledgers, production traceability systems, temperature collection devices, metal detection equipment, and laboratory test results. Updates are made per production batch and per shift output. Cold chain temperature data must be collected and updated continuously. Fields include batch number, quarantine qualification number, raw material traceability code, processing temperature value, test indicator value, and others. Some fields must match the associated relationships of corresponding quarantine and production links.
What constraints these characteristics impose on forms and interactions
This category has strong data association requirements: batch and quarantine information must correspond one-to-one. Forms must include field linkage logic to automatically match the corresponding quarantine number when a production batch is selected. Raw and cooked area control requirements mean forms must distinguish entry categories for raw meat and cooked products, to avoid confusion of cross-contamination related fields. Continuously collected cold chain temperature data has a large volume, so forms must support bulk import or segmented entry to reduce manual input workload. Data update frequency is high, so forms must connect to real-time production data interfaces to avoid using outdated manually entered information. Additionally, microbial test results must be bound to production process parameters, so forms must add associated verification rules to prevent submission of mismatched parameters.
Configuration Settings
These configurations apply to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Field Linkage Rules | Configure automatic matching of batch numbers and quarantine numbers, isolate raw and cooked product categories | Aligns with the category's batch association and raw/cooked product control requirements |
| Bulk Import Limit | No more than 300–500 temperature records per import | Matches the volume of temperature control data collected continuously per shift |
| Single Input Limit | No more than 1200 characters per field | Complies with single-field entry specifications for tendering documents |
formInput | Set as required, bind traceability code and test result fields | Ensures complete entry of core business data |
userSelect | Configure raw and cooked product category selection options | Distinguishes entry categories for raw meat and cooked products |
| Timeout Threshold | Set to 600 seconds | Adapts to typical response durations of production equipment data interfaces |
Three Common Misconfigurations
- Other workflow branches cannot jump to this form node, and the system displays the prompt "Node link does not support cross-branch reuse". Cause: The global reuse configuration of the form node is not enabled, so the node can only be called within the current branch.
- After enabling input guidance and configuring a custom thesaurus, the debug preview interface displays the error "quote type error". Cause: The reference format of the custom thesaurus does not match FastGPT's variable call rules, and the thesaurus content is not wrapped with the required identifiers.
- After submitting the form, the prompt "Batch and quarantine information do not match" appears, but manual verification of the data shows no errors. Cause: The form linkage rule is not bound to the correct production batch data source, causing the automatic matching logic to fail.
How to Verify Correct Configuration
- Call the debug function of the form node, enter a simulated production batch number, and confirm that the automatically matched quarantine number matches the preset data.
- Import bulk temperature control data, confirm that the number of imported records does not exceed the set limit, and that data fields have no format errors.
- Try to jump to this form node from other workflow branches, confirm that the jump is successful and no link errors occur.
- Enter test data that does not comply with the association rules, confirm that the system displays the corresponding verification prompt.
The values listed above are common starting points and should be measured against the reader's own samples.