What the documents look like
Rebate calculation happens after sales close. The work centers on policy definitions and financial treatment rather than replenishment. The main data sources are ERP sales records, dealer remittances, contract ledgers and the finance system. The daily documents are rebate policies, sales achievement tables, reconciliation statements and red-letter invoices. Updates run monthly and quarterly.
For deployment and upgrades, these documents decide two things. First, a version change can alter how import, retrieval and invocation behave, so the same sample must be rechecked against the new version. Second, during an operations handover, materials, actions and requests each carry an authorization state. A retrieval result or a filled-in form does not replace an authorization action.
This page covers one task only: dealer rebate calculation, operations permission and handover management, at the deployment and upgrade step. It does not build business features without a documented basis.
Constraints at the upgrades step
Before upgrading, compare the current version and the target version against the corresponding upgrade notes. Do not infer current behavior from an old configuration name. Both App and Admin must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN. Missing either one causes a startup validation failure. An old single-model address does not substitute for these. Follow the official deployment and upgrade steps to check dependencies and backups. Restore capability must be verified in the operator's own environment. After upgrading, recheck import, retrieval and application invocation with the same sample. Completing the steps does not constitute a zero-interruption commitment.
Hypothetical drill sample: a brand finance team hands over rebate calculation operations after an upgrade. The source materials read: "The March 2026 East China rebate policy applies to first-tier dealers; the achievement basis is the ERP outbound quantity." "The March 2026 reconciliation statement shows dealer A's remittance status as written off; the rebate amount is pending finance review." "The red-letter invoice application form has been submitted with status pending review." Draft sentence to be judged: "Dealer A's March 2026 rebate has been approved, and the red-letter invoice has been issued."
The two migration scripts named for this release are manual-trigger tasks that do not block service startup. The historical chunk training migration must be run after confirming that all older FastGPT App and Pro instances have fully stopped and old task leases have expired. The knowledge base rebuild status migration depends on the first migration completing. These are documented conditions, not automatic actions.
Configuration and implementation checks
The table below lists implementation check items for this page. Numeric values are hypothetical trial starting points with stated reasons and comparison methods. They are not official defaults.
| Configuration item | Hypothetical trial starting point | Reason and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | Enter the AI Proxy root address without /v1 | The documented format is a root address; compare against the old single-model address to confirm no chat endpoint path was appended |
AIPROXY_API_TOKEN | Enter a non-empty admin token | The document requires it to match the server-side configuration and be non-empty; compare with the AI Proxy server setting |
AGENT_ENGINE | Keep fastAgent | The document allows fastAgent or piAgent; compare with the actual pre-upgrade value to confirm the intended change |
DEFAULT_TEAM_BASIC_PERMISSIONS_ENABLED | Keep App and Admin consistent | The document requires the two services to hold the same value; compare both sides |
CHECK_INTERNAL_IP | Keep false | The documented default is off; compare with whether the deployment needs to reduce SSRF risk |
SYSTEM_MIGRATION_BATCH_SIZE | Keep 100 | The documented range is 50 to 1000; compare with the record volume of this migration before adjusting |
The shared boolean variables for App and Admin use true, 1, yes or y for on; other values count as off. FILE_TOKEN_KEY, AES256_SECRET_KEY and INVOKE_TOKEN_SECRET are required at runtime and should be random strong keys, not example values. PRO_TOKEN must match between App and Admin and is at least 32 characters. These are documented conditions, not settings this page invents.
Three common errors
- Treating "pending finance review" as approved. The input is the reconciliation statement text "the rebate amount is pending finance review." The comparison object is the draft sentence "the rebate has been approved." The observable result is that the two status fields do not match, so the draft sentence is unsupported.
- Treating "pending review" as issued. The input is the red-letter invoice application status "pending review." The comparison object is the draft sentence "the red-letter invoice has been issued." The observable result is that an application status and an issuance fact do not match, so the claim is unsupported.
- Using a retrieval result in place of an authorization action. The input is a policy document fragment returned by retrieval. The comparison object is the authorization action in the handover request. The observable result is that retrieval only presents text and produces no authorization or execution record, so the permission state remains to be verified.
How to verify the setup
- Input the source text "The March 2026 East China rebate policy applies to first-tier dealers." Compare against the subject in the draft sentence, "dealer A." The observable result is that the subject tier needs separate verification. If the source does not state that A is a first-tier dealer, the subject scope of that sentence is unsupported.
- Input the reconciliation statement text "the rebate amount is pending finance review." Compare against the draft sentence "the rebate has been approved." The observable result is that the same field for the same period holds mutually exclusive values, so the draft sentence contradicts the source.
- Input the red-letter invoice application text "status pending review." Compare against the draft sentence "the red-letter invoice has been issued." The observable result is that pending review does not equal issued, so the draft sentence is unsupported.
All three checks use paper samples. No deployment, approval, refund or other business action was performed. Where a document field is not provided, it remains unknown. A pending request is not an approval, an offered option is not execution, and an unsigned termination is not a completed termination.