What the documents look like
Central chain procurement and distribution covers headquarters purchasing and outbound delivery, not store display checks. Order fulfilment and after-sales answering revolve around four document families: centralized procurement contracts, replenishment plans, delivery notes, and store requisition forms. Purchasing records come from ERP, warehouse and wave data from WMS, store sales from POS, and supplier delivery data is recorded separately. Daily and weekly updates coexist, and each store requisition form is generated per order. These materials determine what a shared access entry can reference and what it cannot. A share link solves the access entry point only; it does not change the authorization state of any purchasing, delivery, or claim party. A user who opens a share link has reached a conversation window, not an approved requisition, a dispatched delivery, or a settled supplier claim.
Constraints at the shared access step
The no-login window is created from the application detail page under publish channels, and the system-generated full link is copied for use. The link name is recorded for display only. Expiry time, QPM, point cap, and identity verification are configurable items, and some parameters are supported only in the commercial edition. Identity verification accepts a POST request root address; initialization, conversation start, and conversation finish each send a request to the corresponding interface. The unified response returns success, and a true value allows the user to continue. The uid value must be returned as a string that excludes specific characters and does not exceed 255 bytes in length; otherwise an Invalid UID error appears. The authToken is appended to the share link as an extra query parameter, and FastGPT carries token=[authToken] in the authentication interface body. Conversation records depend on localId, so the same device and same browser can pull records from the last 30 days, limited to 20 entries, while switching devices or clearing browser cache loses them. These are conditions stated in the official documentation. Retrieval and link access do not constitute business authorization.
Configuration and implementation checks
The following is a hypothetical drill sample used to explain the checking method. It does not represent any real record or any action that was carried out.
Hypothetical source text: a chain supply chain center produced a draft Store Requisition Form on the hypothetical date 10 March 2025, hypothetically numbered YH-2025-0310-01, with the requisition target being hypothetical Store A, the requisition category being hypothetical Product B, the quantity hypothetically 120 units, and the status column marked "awaiting distribution center confirmation." The same batch's draft Delivery Note is hypothetically numbered PS-2025-0310-07, the receiving party is hypothetical Store A, the delivery quantity is hypothetically 120 units, and the status column is marked "awaiting dispatch." The draft sentence under review reads: "This requisition has been confirmed by the distribution center and dispatched, so the store can arrange shelving on this basis."
| Configuration or check item | Value or state in this page's sample | Note |
|---|---|---|
| Share link name | Hypothetically named "store requisition Q&A entry" | Recorded for display only, carries no authorization meaning |
| Expiry time | Hypothetical trial start of 7 days after creation | A hypothetical starting point for this exercise, to be compared with the actual business use window |
| QPM | Hypothetical trial start of 10 requests per user per minute | A hypothetical starting point, to be compared with peak store inquiry volume |
| Point cap | Hypothetical trial start of a number of points | A hypothetical starting point, to be compared with estimated answering rounds |
| Identity verification root address | Hypothetically filled with an internal service root address | Only the root address is configured; the interface returns success and uid |
| authToken concatenation | Hypothetically concatenated with an internal user credential | Generated by the upstream system; FastGPT carries token in the body |
Three common errors
- Treating the creation of a share link as business authorization. A link can be copied and opened, which is a different fact from whether a requisition form is confirmed or a delivery note is dispatched. The input is the link and the material status; the comparison is between link availability and the document status fields; the observable result is that the two do not derive from each other.
- Writing a pending status as completed. In the sample, the requisition form is marked "awaiting distribution center confirmation" and the delivery note is marked "awaiting dispatch," while the draft sentence says "confirmed and dispatched." The input is the status fields of the two materials; the comparison is between the draft sentence and the source text; the observable result is that the draft sentence exceeds the status recorded in the materials.
- Treating retrieval relevance as a permission or entity filter. A similarity value reflects retrieval ranking only and does not distinguish stores, suppliers, or authorization scope. The input is the score returned by retrieval together with the record ownership identifier; the comparison is between the owning entity of the record and the identity of the visitor; the observable result is that a high or low score does not change whether the record may be used by that visitor.
How to verify the setup
- For the sample draft sentence, input the requisition form source text "awaiting distribution center confirmation," the delivery note source text "awaiting dispatch," and the draft sentence "confirmed and dispatched." Compare the status expressions of the three. The observable result is that the draft sentence is inconsistent with both source texts on the status field, and that sentence is not supported.
- For identity verification, input the hypothetical authToken and the identity verification root address, and compare the success value and the uid format returned by the interface. The observable result is that when success is true and uid is a compliant string, the user is allowed to continue; when success is not true, the message is shown; when uid is missing or contains a disallowed character, Invalid UID appears.
- For the conversation record boundary, input the two situations of the same device with the same browser and a switched device, and compare the record range that can be pulled. The observable result is that the first situation can pull records from the last 30 days, limited to 20 entries, while the second loses the records. This result does not change the authorization state of any document.