What the data for this category looks like
This category of data originates from requirement specification documents, test environment configurations, customer business samples, and defect systems. Four core document types are routinely produced: UAT test cases, acceptance issue tickets, acceptance reports, and signed confirmation forms. Fields include test scenarios, problem reproduction steps, acceptance conclusions, customer signature items, and more. Data is updated once per project phase or version iteration, with adjustments focused on customer business scenario acceptance requirements. This data is not included in the general business data pool.
What constraints these characteristics impose on deployment and upgrade
This category of data relies on non-standard customer business samples and acceptance documents. During deployment, reserve field expansion space to adapt to the acceptance case structures of different customers. Updates per phase or version require the deployment process to support incremental synchronization, to avoid acceptance data loss caused by full overwrites. Because core data is linked to customer acceptance conclusions, ensure data consistency during the upgrade process to prevent abnormal fields in acceptance issue tickets from configuration changes. The usage scenarios of implementation consultants and test managers also require the post-deployment interface to adapt to the upload and retrieval logic of acceptance documents, and reserve interface configuration items for connecting to defect systems.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 connections | Adapt to concurrent read demands for multiple documents including UAT test cases and acceptance issue tickets, avoid exhausting database connections |
MONGODB_URI | Configured to the dedicated storage cluster address for customer acceptance data | Store acceptance issue tickets and defect system synchronization data, match customer-side database permissions and network policies |
PG_URL | Configured to the address of the test environment's PostgreSQL instance | Store structured fields of requirement specification documents and acceptance reports, ensure data query efficiency |
REDIS_URL | 127.0.0.1:6379 or a dedicated cache cluster address | Cache retrieval results and acceptance statuses of UAT test cases, reduce resource consumption from repeated queries |
FILE_TOKEN_KEY | Valid for 1800 seconds | Generate access tokens for customer business sample attachments, ensure security of temporary download links |
FE_DOMAIN | Access domain of the customer acceptance platform | Configure the front-end access address, ensure normal operation of the online preview and submission link for signed confirmation forms |
STORAGE_S3_ENDPOINT | Configured to the official endpoint of the customer's cloud storage service provider | Store attachments of customer business samples and acceptance reports, adapt to the customer's existing cloud storage environment |
Three common errors
- Symptom: The upgrade script returns a
POST /api/admin/initv4818 404error, with a duration of 76ms. Cause: The upgrade script from FastGPT v4.17.0 or later was not used, or the deployment environment's interface access permissions were not opened to the corresponding path. - Symptom: Customer-uploaded UAT test case documents cannot be queried after deployment. Cause:
STORAGE_S3_ENDPOINTor associated storage keys were not configured correctly, preventing documents from being properly synchronized to the system storage path. - Symptom: Complete fields of acceptance reports cannot be viewed after logging into the system. Cause: Database field mapping configurations were not adjusted based on the structure of acceptance documents, leading to abnormal structured data reads.
How to verify correct configuration
- Run the connection test script for
DB_MAX_LINK, verify that database connection counts do not exceed the configured limit during concurrent reads of UAT test cases. - Upload a test UAT test case document, confirm that it can be previewed normally via the front-end interface and stored to the specified path, verifying that the
STORAGE_S3_ENDPOINTconfiguration takes effect. - Trigger an acceptance issue ticket synchronization task, confirm that data can be normally pulled from the defect system and stored to the corresponding database instance, verifying that the
MONGODB_URIandPG_URLconfigurations are correct. - Log into the system using an administrator key, confirm that all acceptance-related configuration modules are accessible, verifying that the
FILE_TOKEN_KEYand role permission configurations take effect.
The values provided here are common starting points, and should be evaluated against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.