What the Data for This Category Looks Like
Data for this category comes from internal project management systems of Chinese state-owned and public sector enterprises, archived project approval documents, progress ledgers, and acceptance reports. Update frequency aligns with project progress nodes: weekly synchronization of progress information after project approval, and no further updates after acceptance and archiving. Each data entry is a structured item with 7 fields: project ID, project name, affiliated business department, project approval date, budget amount, current execution status, and responsible team. Budget amount is measured in ten thousand yuan. Execution status uses preset enumerated text values.
Constraints for Citation Sources and Traceability
The structured field structure requires precise matching of corresponding field content during citation traceability. Generalized descriptions will lead to traceability errors. The node-based update feature requires traceability information to include both the data update time and project phase. This ensures the timeliness of cited content. The multi-field entry structure requires clear listing of key identification fields such as project ID and responsible team when displaying citations. This allows quick location of the original data entry. The enumerated execution status field must strictly match preset values. No custom, undefined status descriptions are allowed.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Project data contains multiple fields, and the citation content of a single structured data entry must be fully accommodated |
responseData | Enabled | The original project data stored in the knowledge base must be returned as the citation source, to avoid generative rewriting |
detail | Full | All key field content must be displayed, to ensure complete verification of original data during traceability |
| Single search limit | Top 3 entries | The total number of internal project data entries is limited, and excessive redundant citations will interfere with traceability accuracy |
| Traceability details | Fixed as "Original Data Source: Project IDthe configured value, the configured value, the configured value: the configured value" | Output according to the preset field format, to ensure structured display of citation content |
Three Common Misconfigurations
- Phenomenon: The returned reply does not use the original project data text stored in the knowledge base, and generates generalized unmatched content. Cause: The
responseDataparameter is not enabled, so the system does not force use of the original knowledge base content. - Phenomenon: Structured knowledge base reference fields cannot be selected in workflow nodes, and the number of output results does not match expectations. Cause: The
detailparameter is not set to Full mode, so the system does not expose all fields for selection. - Phenomenon: Some key fields are missing from citation sources, preventing quick location of the original data entry for traceability. Cause: The
quoteMaxTokenvalue is too small, leading to truncation of some field content that cannot be fully displayed.
How to Confirm Successful Configuration
- Submit a query for a specific project. Check that the returned result includes a structured list of source fields at the end, with no generative rewritten content.
- Access the workflow variable selection panel. Confirm that options for structured fields such as project ID and project name are available.
- Run a query for a project with a large number of fields. Verify that all key fields are fully displayed, with no truncation.
- Compare the query result to the original data entry stored in the knowledge base. Confirm that the content is fully consistent, with no additional generated text.
The values provided here are common starting points, and should be evaluated against the user'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-09-28.