What the documents look like
Cross-border product compliance and labelling work happens before listing and before import. The evidence base is product safety and label evidence, not payment risk control. The documents handled day to day are product test reports, English-language labels, MSDS files, and platform prohibited-item lists. Sources include platform policy centres, testing laboratory reports, destination-country regulation libraries, and supplier materials. Updates are irregular; each new product listing can trigger a fresh round of checking. In the store-service and internal-training setting, the form and interaction step collects information and routes the conversation, and whatever is collected is passed to later nodes.
The two interactive nodes documented for this version are Form Input and User Selection. Both are user-interaction nodes. When either node is triggered, the conversation enters an interaction state, the workflow state is recorded, and execution waits until the user completes the interaction. Form Input collects what the user fills in and passes it to later nodes after submission. User Selection evaluates the user's choice and executes the corresponding branch. Neither node carries business database functions. Field validation, business approval, write-back, and bulk operations need to be implemented in an external system or in later nodes.
Constraints at the interactive forms step
The interaction state is a wait state. When a node triggers, the dialogue box is hidden, the workflow records its state, and the flow continues only after the user acts. A submitted form is a set of collected values passed downstream. It is not an approval, not a database write, and not an authorisation to act. A selected branch is a routing decision based on the user's choice. It is not a personnel directory, not a business data selector, and not a permission filter.
Assumed paper exercise sample: the following fictional materials are used for this paper check and involve no real customer or legitimate identity number.
Material text one: "Product name: portable charger; destination country: Germany; test report number: TR-2024-0117; report status: issued, covering battery safety items; English label version: V2.1; MSDS status is pending supplier provision."
Material text two: "Platform prohibited-item list check result: this category is not currently within the prohibited scope; check date: 10 March 2024; checker: compliance specialist A."
Draft sentence to be assessed: "The product has completed all compliance material preparation and can be listed directly."
Assessment point: material text one shows MSDS status as pending supplier provision, which has not reached the provided state. Material text two states only that the category is not within the prohibited scope and does not address label review or test report completeness. The draft sentence's claim of "all compliance material preparation" lacks evidence that the MSDS has been provided, so the claim is unsupported.
Configuration and implementation checks
| Configuration item | Setting or check item relevant to this page | Explanation |
|---|---|---|
| Form Input node | Collect product name, destination country, test report number, label version, MSDS status | Passes values to later nodes after submission; does not write to a database |
| User Selection node | Set a branch on whether compliance materials are complete | The choice determines the subsequent flow direction |
| Required-field check | List the information this task cannot proceed without; test the missing case and the completed case separately | While a required value is missing, the node waits in the interaction state |
| Interaction state | Triggering records workflow state and waits for interaction | Execution continues downward after the interaction completes |
| Downstream division of work | Field validation, business approval, write-back, and bulk operations are implemented in an external system or later nodes | The form node does not perform approval or database writes |
Assumed starting value for this exercise: the test report number is set as a required field, because that value is a necessary input for later checking of test report validity. The comparison method is to submit an empty value and a filled valid number, and observe whether the node waits and then continues respectively.
Three common errors
- Treating form submission as completed business approval. The Form Input node collects values and passes them to later nodes, while approval must be implemented in an external system. If the submission action is read as approval, downstream processing can continue on the basis of unapproved information.
- Treating the User Selection branch result as a personnel directory or business data selector. This node executes a branch according to the user's choice and does not perform data queries or permission filtering.
- Treating retrieval or form collection as authorisation to execute. Retrieval results and form entries do not constitute operational authorisation; the authorisation boundary must be confirmed separately in an external system.
How to verify the setup
- Using material text one from the assumed sample, submit the MSDS status field empty and observe whether the Form Input node enters the interaction state and waits for completion; then fill it as "provided" and observe whether execution continues downward. The expected behaviour is waiting while the value is missing and continuing after it is supplied.
- Using the draft sentence from the assumed sample, configure the User Selection branch on whether compliance materials are complete, choose "not complete", and observe whether the corresponding branch executes. The expected behaviour is that the branch direction matches the choice.
- Using material text two from the assumed sample, check the platform prohibited-item list result field and confirm that this field records only the check conclusion and date and does not trigger automatic listing or approval actions. The expected behaviour is that the field records information, and any subsequent business action must be executed separately in an external system.