What the documents look like
General trade export declaration produces, for every declaration, an export declaration form, a commercial invoice, a packing list and a contract. The working data comes from the China International Trade Single Window, the customs commodity code library, the forwarder bill of lading and the company ERP. Compared with general trade import declaration, export declaration also affects the matching of export tax rebate vouchers. That difference means handover judgements about material status depend more heavily on the correspondence between document fields and rebate vouchers. Commodity code classification, completing the declaration form, and checking freight and insurance are the three most time-consuming steps. A handover record needs to reflect the completion status and responsibility ownership of those steps.
The interactive forms step does not read those documents by itself. It collects what a person types or selects, and it holds the workflow until that interaction finishes.
Constraints at the interactive forms step
The form input node is a user interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. The node collects the information the user fills in and passes it to later nodes. It does not include a business database function of its own.
The user selection node is also a user interaction node. When it triggers, the workflow state is recorded and execution waits for the user to complete the interaction, then continues along the branch that matches the user's choice. Neither node acts as a personnel directory, a business data selector or a permission decision point. Field validation, business approval, write-back and batch operations need an external system or later nodes.
Retrieval and form collection do not constitute authorization. The authorization state of a material during operations handover must be confirmed by an external business system.
Hypothetical drill sample: a document clerk at a foreign trade company writes in a handover record, "Export declaration draft completed, commercial invoice and packing list attached, contract scan uploaded, freight and insurance pending check." The same handover request says, "Please take over and complete the remaining declaration and confirm the rebate voucher match." These two sentences state only draft and attachment status. They do not state whether the receiving person has been granted declaration operation permission, and they do not state who confirms the rebate voucher match.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form input node | Official node | Triggers the interaction state, records workflow state, collects filled information and passes it to later nodes |
| User selection node | Official node | Triggers the interaction state, records workflow state, executes the branch matching the user's choice |
| Required information check | Implementation check | List the information this task cannot omit, and check the missing case and the completed case separately |
| Interaction state carry-over | Implementation check | After the interaction finishes, execution continues downward; later nodes do not run while waiting |
| Downstream processing split | Implementation check | Field validation, business approval, write-back and batch operations are implemented in an external system or later nodes |
| Hypothetical trial starting point | This hypothesis | Treat "commercial invoice and packing list attached" as the starting point for the attached judgement, compared item by item with the attachments listed in the handover record |
The hypothetical trial starting point is chosen because the sample text names two attachments explicitly. It is compared against each attachment entry in the handover record, not against an official default.
Three common errors
- Treating a form input submission as completed authorization. In the sample, "Please take over and complete the remaining declaration" expresses a request only. Submitting the form does not create operation permission. Compare the materials listed in the handover record with the operation permission field, and observe whether a permission grant record appears.
- Treating a user selection branch as a personnel directory. The user selection node executes a branch according to the choice; it does not carry personnel or business data selector duties. Compare the node output with the personnel data in the external system, and observe whether the two are mixed.
- Treating retrieval output as a basis for permission or entity separation. A relevance score does not carry category, entity or permission filtering. Compare the retrieval output with the authorized scope, and observe whether unrelated records enter the handover list.
How to verify the setup
- Input the sample text and the handover request above. Compare the three states "attached", "uploaded" and "pending check" against the operation permission field, and observe whether the handover record marks the request as authorized. The expected result is that the request remains in a pending-confirmation state.
- Input "freight and insurance pending check" from the sample. Compare that field with the output of the later node, and observe whether the later node continues while the field is still incomplete. The expected result is that the interaction state waits and does not release automatically.
- Input an explicit paper empty result [] together with the downstream handover list design. Compare the empty-result carry-over logic, and observe whether the downstream treats the empty result as no pending items. The expected result is that the gap is recorded and not inferred as completed.