What the documents look like
Cold-chain receiving at a store is recorded through four document types: cold-chain temperature records, arrival acceptance sheets, rejection notes, and supplier delivery notes. The data comes from vehicle temperature control, the WMS, the store receiving system, and quality inspection photos. The distinguishing feature of this category is that receiving work checks transport temperature and arrival batch, and does not handle origin price inquiry. The reference material gives a per-batch and daily update frequency; this page does not derive batch synchronization or real-time triggers from that frequency. These records connect directly to food spoilage, supplier disputes, and regulatory penalties, so any deployment or upgrade must first settle which accounts may submit acceptance data, which accounts may register rejection reasons, and which accounts may only view.
Constraints at the upgrades step
Before upgrading, compare the current version and the target version against the matching upgrade notes, and do not infer current behavior from an old configuration name. V4.17.2 contains two manually triggered upgrade scripts: the historical chunk training task migration and the knowledge base rebuild status migration, and the second depends on the first being complete. The scripts do not block service startup, but they should be executed only after confirming that all old-version FastGPT App and Pro instances have fully stopped and old task leases have expired. From V4.17.0, AI Proxy is a required dependency: both App and Admin must set AIPROXYAPIENDPOINT and a non-empty AIPROXYAPITOKEN, and a missing item causes startup validation to fail. From 4.15.0, the open-source edition no longer reads config.json, so an old mount must be removed and the related fields moved to environment variables per the migration table.
Hypothetical drill sample, clearly labelled as constructed for this page and not drawn from real records: a store receiving account "inspector A" at a fresh-produce warehouse-distribution entity submits a cold-chain arrival acceptance record on 10 March 2026; the temperature record shows a transport temperature of 4.2 degrees Celsius; the arrival acceptance sheet status field reads "pending quality inspection confirmation"; no rejection note has been generated. The draft handover sentence to be judged is: "Inspector A has completed acceptance of this batch and handed it to quality inspector B, and B may register the rejection reason on behalf of A." The source text supplied for comparison is: the arrival acceptance sheet status field "pending quality inspection confirmation"; the inspector A account permission note "may submit temperature records and acceptance sheets"; the quality inspector B account permission note "may view acceptance sheets, and registering a rejection reason requires team-lead authorization." The draft sentence writes a pending-inspection state as completed acceptance, and writes an operation that requires authorization as one that may be performed on behalf of another, so the handover request is unsupported.
Configuration and implementation checks
The table below lists only settings or implementation check items that the official material states and that relate to this page's primary task. The values are marked as hypothetical starting points for this exercise and are not official defaults.
| Configuration item | Hypothetical starting point for this exercise | Comparison method |
|---|---|---|
| AIPROXYAPIENDPOINT | Internal service root address, without a chat interface path | Compare with the documented root address form and confirm that no /v1 suffix is appended |
| AIPROXYAPITOKEN | Non-empty administrator token | Compare character by character with the server-side configuration and confirm it matches and is non-empty |
| Upgrade script execution order | Training task migration first, rebuild status migration second | Compare with the documented dependency and confirm the first is complete before running the second |
| Old config.json mount | The mount has been removed | Compare with the documented migration table and confirm the related fields are now environment variables |
| Account permission fields | Inspector A may submit; inspector B requires authorization | Compare with the account permission note text and confirm the operation and authorization boundary |
Three common errors
- Treating a pending quality inspection confirmation state as completed acceptance. The input is the arrival acceptance sheet status field "pending quality inspection confirmation"; the comparison object is the draft sentence "has completed acceptance of this batch"; the observable result is that the status field and the draft sentence do not agree, and the draft sentence is unsupported.
- Writing an operation that requires team-lead authorization as one that may be performed on behalf of another. The input is the quality inspector B permission note "registering a rejection reason requires team-lead authorization"; the comparison object is the draft sentence "B may register the rejection reason on behalf of A"; the observable result is that the permission note requires authorization while the draft sentence omits it, so the handover request exceeds the stated boundary.
- Treating a rejection note that has not been generated as an existing handover material. The input is the fact that no rejection note has been generated; the comparison object is the registration action implied by the draft sentence; the observable result is that no corresponding document exists to register against, so the action lacks its object.
How to verify the setup
- The input is the arrival acceptance sheet status field "pending quality inspection confirmation" and the draft sentence "has completed acceptance of this batch." Compare whether the two point to the same status value. The draft sentence is satisfied only when the status field clearly reads completed; at present it does not.
- The input is the quality inspector B permission note "registering a rejection reason requires team-lead authorization" and the draft sentence "B may register the rejection reason on behalf of A." Compare whether the authorization condition is met. It is met only when a team-lead authorization record exists; no authorization record is provided at present, so this remains to be verified.
- The input is the fact that no rejection note has been generated and the registration action implied by the draft sentence. Compare whether an operable document object exists. A registration object exists only when the rejection note has been generated; it is missing at present, so this is recorded as an evidence gap.