What the documents look like
In central chain procurement and distribution, store service and internal training work with four document families: centralized procurement contracts, replenishment plans, distribution orders, and store requisition orders. These materials pass through the chain supply center, purchasing managers, and the distribution center. Data sources include ERP procurement, WMS, store POS, and supplier delivery data, with daily or weekly update frequency. This page covers the forms and interaction step around these materials in store service and internal training. It does not cover price and display audits, and it does not inspect store displays.
In FastGPT v4.17.2, the Form Input node is a user interaction node. When triggered, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. The User Selection node is also a user interaction node with the same interaction-state behavior, and it evaluates the user's choice to execute a branch. Both nodes collect entered information or judge a selection. Neither node provides a business database function on its own.
Constraints at the interactive forms step
The status fields in centralized procurement contracts, replenishment plans, and distribution orders determine what a form needs to collect and what a user selection needs to judge. Approval status, signing status, and validity scope in the materials are the basis for interaction design. The nodes do not produce these statuses.
Hypothetical paper exercise sample: a chain supply center receives a draft distribution order whose text reads "Distribution order number PS-2026-0412, distribution center East China Distribution Center, store requisition order number YH-2026-0398, planned distribution date 12 April 2026, distribution quantity 300 boxes, status pending review." A separate centralized procurement contract summary reads "Contract number JC-2026-0117, supplier a food company, contract effective date 1 March 2026, contract status signed." The sentence to be assessed is: "This distribution order has been approved and can proceed with the planned distribution."
Form interaction needs to collect identifiers such as the store requisition order number and the distribution order number. User selection needs to judge whether the distribution order status meets an executable condition. Field values collected by the node pass to later nodes. Field validation, business approval, write-back, and batch operations need to be implemented in an external system or in later nodes. Retrieval or a form does not constitute authorized execution, and a pending-review status does not demonstrate that operating permission is absent.
Configuration and implementation checks
The following items center on this page's sample. They list documented settings or implementation checks. The values are starting points for this hypothetical exercise, used for comparison and observation, and are not official defaults.
| Configuration item | Hypothetical exercise starting point | Comparison and notes |
|---|---|---|
| Form Input node fields | Distribution order number, store requisition order number, distribution quantity | Compare item by item with identifiers in the sample materials; when an item is missing, observe whether the interaction state keeps waiting |
| User Selection node branches | Pending review, signed | Compare with status fields in the sample materials to judge the branch direction |
| Required information check | Distribution order number, store requisition order number, distribution quantity | Test missing and completed cases separately, and observe whether the node collects the full set |
| Interaction state recording | Workflow state recorded after triggering | Execution continues after the interaction completes; do not assert submission counts or snapshot guarantees |
| Downstream division of work | Field validation, business approval, write-back | Implemented in an external system or later nodes; the node itself does not perform these actions |
Three common errors
- Treating a pending-review status as approved. In the sample, the distribution order status is pending review, while the draft sentence states "has been approved." These are different values on the same field, so the sentence is unsupported. To check, input the sample text and the draft sentence, compare the distribution order status field, and observe whether the draft sentence goes beyond the status stated in the source.
- Treating the User Selection node as a personnel directory or a business data selector. In the sample, the user selection branches are pending review and signed, which correspond to status fields in the materials. To check, input the status values from the sample materials, compare the branch options with the status fields, and observe whether the branches reflect only the statuses stated in the materials.
- Treating field values collected by a form as completed business approval. In the sample, the form collects the distribution order number and the store requisition order number. These are identifier values and do not indicate that approval passed. To check, input the form fields and the sample materials, compare the field values with the approval status field, and observe whether any statement equates identifier information with an approval result.
How to verify the setup
- Input the sample text "Distribution order number PS-2026-0412, status pending review" and the draft sentence "This distribution order has been approved and can proceed with the planned distribution." Compare the distribution order status field with the draft sentence. If the draft sentence claims approval while the source status is pending review, judge the sentence unsupported and record the evidence gap.
- Input the sample text "Contract number JC-2026-0117, contract status signed" and the User Selection branch settings. Compare the contract status field with the branch options. If a branch option is signed and the material status matches, observe whether the branch direction follows the status stated in the material. If the material does not state a status, keep it as pending verification.
- Input the sample text "Store requisition order number YH-2026-0398, distribution quantity 300 boxes" and the required form field settings. Compare whether the identifiers and quantity collected by the form match the material. If a form item is missing, observe whether the interaction state keeps waiting. If the form is completed, observe whether the node collects the full set and passes it to later nodes. For empty-result handling, a clearly stated paper input [] can be used to check the downstream design; do not claim that a fictional rule retrieval necessarily returns [].