What the documents look like
Wholesale stall trading runs on purchase notes, handwritten sales slips, stall lease contracts and payment receipts. These records sit alongside stall inventory, WeChat collection records and logistics consignment notes. Bargaining and writing the slip, arranging consignment, and chasing the final balance consume most of the working day. Slips are frequently handwritten, and one payment can be settled in several instalments. For deployment and upgrades, the consequence is concrete: after a version switch, the recorded permission ownership and handover state must be checked against each original document. Lists and search results inside the system reflect data rows only. They do not reflect the verbal authorisation given at the stall.
Constraints at the upgrades step
An upgrade begins by comparing the current version with the target version and the matching upgrade notes. Behaviour is not inferred from an old configuration name. V4.17.2 contains two manually triggered upgrade scripts: the historical chunk training task migration, and the knowledge base rebuild status migration that depends on the first. Neither blocks service startup. Both are executed after confirming that all old-version App and Pro instances have fully stopped and old task leases have expired.
At this step, member permissions, application read permission and log visibility belong to deployment configuration. Signing on a slip, the lease contract taking effect, and settlement of the payment belong to business facts. A search hit on a receipt shows that the data row exists. It does not show that the final balance has been collected or that the stall has been handed over.
Hypothetical exercise sample: a stall handover occurs on 10 March 2026. The source material reads: "Received today a deposit of 2,000 yuan from a buyer surnamed Wang; the remaining 8,000 yuan to be settled on the day of collection," and "Stall lease contract runs until 31 December 2026; the tenant field is Li." The draft sentence to be judged is: "The stall payment has been settled in full and the stall operating permission has been handed over." The comparison objects are the deposit receipt and the lease contract. The fields needed are settlement status and tenant. Neither document states that the remaining balance was paid, and neither states that handover was completed. The draft sentence is not supported.
Configuration and implementation checks
The table below lists only documented settings or implementation checks relevant to deployment, upgrades and permission reconciliation on this page. Where a value is a hypothetical starting point for this exercise, the reason for choosing it and the comparison object are given. It is not presented as an official default.
| Configuration item | Hypothetical starting point | Purpose and comparison method |
|---|---|---|
| AIPROXYAPIENDPOINT | Assume http://aiproxy:3000 | Required from V4.17.0; no /v1 suffix. Compare with the internal service address in the deployment template |
| AIPROXYAPITOKEN | Assume a non-empty administrator token | Required and must not be empty. Compare character by character with the AI Proxy server configuration |
| PRO_TOKEN | Assume a random string of at least 32 characters | Required when App sets PRO_URL. Compare with the value on the pro/admin side |
| DEFAULTTEAMBASICPERMISSIONSENABLED | Assume set to false | Controls default all-member group permissions for new teams. Compare the value on the FastGPT and Pro Admin sides |
| Manual upgrade script order | Assume the training task migration runs first | The second script depends on the first completing. Compare with the order listed on the administrator version upgrade page |
| Post-upgrade sample review | Assume the same purchase note and receipt are used | Compare observable results for import, retrieval and application invocation before and after the upgrade |
Three common errors
- Treating a search hit as authorisation. The input is the deposit receipt in the sample. Judging from it that the final balance has been settled treats the existence of a data row as a business fact. The receipt records only the deposit of 2,000 yuan and the agreed remaining 8,000 yuan.
- Treating a pending review as absence of permission. The member edit dialog fetches full member information before it opens. A dialog in the open state shows only that information is loading. It does not show that the member lacks operating permission.
- Merging signing, contract effectiveness and completed handover into one fact. In the sample lease contract, the tenant field is Li and the term runs to 31 December 2026. These facts are checked separately. A stated lease term does not indicate that handover is complete.
How to verify the setup
- Input the two source sentences and the draft sentence "The stall payment has been settled in full and the stall operating permission has been handed over." Compare whether the draft sentence has explicit records of settlement and handover. Neither document states them, so the sentence is judged unsupported and the evidence gap is recorded.
- Input the hypothetical configuration
AIPROXY_API_ENDPOINT=http://aiproxy:3000and a non-emptyAIPROXY_API_TOKEN. Compare whether startup validation passes. When either item is missing, startup validation fails, which is an observable event. - Input the sample receipt and lease contract. Compare whether search results and manual reconciliation conclusions agree. Search results are used only to locate data rows; permission and handover status follow the original documents. When they disagree, the original document record is retained.
This page covers only wholesale stall trading, operations permission and handover management, and deployment and upgrades. It does not treat retrieval or a form as authorisation or execution.