What the data for this category looks like
This data typically includes documents such as request registration forms, dispatch records, handling responses, follow-up visit records, extension applications, return instructions, and knowledge base entries. Data sources include the 12345 citizen hotline platform, handling unit business systems, official knowledge bases, follow-up evaluation data, and local hotline management-related documents. Data updates occur daily. Some work orders transferred in real time are updated synchronously with processing progress. Most documents contain fields such as request number, handling unit, response content, processing progress, and follow-up result. Some documents use structured form formats, while others use semi-structured handling description text.
What constraints these characteristics impose on the citation sources and traceability link
Since data sources are scattered and updated daily, the traceability link must accurately match the identification rules of different data sources to avoid confusion between processing records of different work orders. Structured work order documents require extracting fixed fields as traceability bases. Semi-structured text must be associated with the corresponding request number to locate the original content. Real-time updated work order data requires traceability configuration to support dynamic pulling of the latest content. Otherwise, expired processing information may be returned. Document formats vary across different handling units. The traceability logic must adapt to multiple field structures, otherwise it will not be possible to accurately associate response content with the original work order. The accuracy of traceability results directly affects the compliance of work order processing. Incorrect traceability will cause responses to be returned for reprocessing.
How to set the configuration
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Adapts to the average length of 12345 work order documents, avoiding truncation of key traceability information |
responseData | Enable citation traceability switch | Enables generation of cite reference IDs to match work order request numbers with original documents |
detail | Enable detailed traceability | Displays complete fields of original documents, meeting the traceability requirements of party building learning Q&A |
| Maximum traceability per request | Top 3 entries | Controls the number of returned traceability items, avoiding content overload that affects response readability |
| Data source classification rules | Classify by work order ownership | Distinguishes data from the 12345 citizen hotline platform and handling unit business systems |
Three common mistakes
- Symptom: The conversation API call does not return the cite reference ID field. Cause: The citation traceability switch in the
responseDataconfiguration item is not enabled, so the API does not generate reference identifiers. - Symptom: An error occurs when viewing knowledge base citations in chat responses. Cause: No association mapping between work order data and knowledge base entries is configured, so the storage path of the original document cannot be located.
- Symptom: Traceability returned content is truncated and cannot display complete handling responses. Cause: The
quoteMaxTokensetting value is too small, and traceability content is automatically truncated after exceeding the configured token limit.
How to confirm the configuration is complete
- Initiate a test query related to work orders, check whether the API return result includes the cite reference ID field.
- Open the citation card in the chat interface, confirm that each traceability item is marked with the corresponding work order number or knowledge base entry name.
- Adjust the value of
quoteMaxToken, verify that the length of the returned traceability content meets expectations with no truncation. - Check the background logs, confirm that the traceability request successfully pulled the latest data from the corresponding data source, with no timeout or matching failure records.
The values provided are common starting points and should be measured 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-09-28.