What the documents look like
Central procurement and distribution data arrives from ERP purchasing, WMS, store POS, and supplier delivery records, with daily or weekly update frequency. The documents handled day to day include centralized procurement contracts, replenishment plans, distribution orders, and store requisition forms. Operating reports and exception reviews need these sources aligned on the same field and the same period, and the HTTP module carries requests and responses between systems. The supply chain center and distribution center focus on the quantity and status relationships among purchase orders, distribution waves, and store requisitions. Store display checks fall outside this page.
Constraints at the HTTP integrations step
The HTTP module sends a request to a specified address. Params carry path parameters and are common in GET requests. Body carries the request body and is common in POST and PUT requests. Headers carry special information. Custom variables can receive outputs from earlier nodes as variables, and all three data locations plus the URL can reference variables through double braces. Variable sources are global variables, system variables, and earlier node outputs. System variables include appId, chatId, responseChatItemId, variables, cTime, and histories; chatId and responseChatItemId do not exist in test mode. Return values are extracted through JSON path syntax or JS object access rules, and when the output type is set to string, the value at the corresponding key is converted to a JSON string.
The chat completions endpoint uses APIKey authentication. The appId priority order is body.appId, then apiKey-appId, then the appId associated with the apikey. When detail=true, the response includes responseData with fields such as moduleName, tokens, and similarity. A similarity value is a retrieval relevance number and does not perform permission or entity isolation. The same-vector-model requirement applies to a retrieval library itself and does not extend to external systems.
Hypothetical drill sample: a chain supply chain center plans to send one distribution order status query to the distribution system on 10 March 2025. The source text for comparison reads: "Centralized procurement contract HT-2025-0310 provides that supplier A delivers 200 units of product M to distribution center W1 by 12 March 2025; replenishment plan BH-2025-0310 lists store S1 requisitioning 80 units of product M; distribution order PS-2025-0310 states that distribution center W1 ships 80 units of product M to store S1, with status 'shipped'." The draft sentence to be judged reads: "Distribution order PS-2025-0310 has completed receipt confirmation at store S1." The source text records the status as shipped and contains no receipt record, so the draft sentence is unsupported. The authorization boundary is that this request only queries the distribution order status and does not trigger receipt confirmation, inventory writes, or supplier claims.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
| Request address | Distribution system status query endpoint | Determined by the external interface document, matching the distribution order number in the source text |
| Request method | GET | Queries distribution order status; checked against the external interface contract |
| Params | Distribution order number PS-2025-0310 | Compared character by character with the number in the source text |
| Headers | Authorization as Bearer plus credential | Credential injected through secure configuration, not written into public samples |
| Body | Not enabled | Body does not take effect under GET, consistent with the documented behavior |
| Return value extraction key | status | Extracts the status field by JS object access rules and compares it with the source text status |
These values are hypothetical starting points for this drill, used for item-by-item comparison with the source text, and do not represent official defaults. The configuration covers only the query request needed for this page's primary task and does not include database writes or external synchronization.
Three common errors
- Treating a retrieval relevance score as a permission filter. similarity is a relevance number for retrieval results and cannot exclude unauthorized records. The check supplies the same query, compares the authorization identifiers in the returned records, and observes whether unauthorized records appear.
- Treating a chatId that does not exist in test mode as a business failure. The documentation states that chatId and responseChatItemId do not exist in test mode. The check sends a request in test mode, compares whether these two fields are absent from the response, and observes whether this is misjudged as a distribution order exception.
- Treating a pending status as a completed operation. In the source text the distribution order status is shipped, while the draft sentence says receipt confirmation is complete, which is unsupported. The check compares the draft sentence with the status field in the source text character by character and observes whether the two agree.
How to verify the setup
- Enter the distribution order number PS-2025-0310 from the source text as Params, compare the returned status field with "shipped" in the source text, and if the two agree the query configuration is correct; if the return is empty or the status differs, record the difference and recheck the number and the endpoint address.
- Enter the draft sentence "Distribution order PS-2025-0310 has completed receipt confirmation at store S1," compare it with the distribution order status field in the source text, and note that the source text contains no receipt record, so the sentence is unsupported and cannot be judged as a completed receipt confirmation.
- Enter a query that carries no authorization identifier, compare the returned records with the authorization scope, and observe whether unauthorized records appear; if they do, record the observation and recheck the authentication configuration, since retrieval relevance does not perform permission filtering.