What the Data for This Category Looks Like
Data for this category primarily comes from the national petition information system, local petition systems, the 12345 citizen hotline, grassroots governance platforms, and historical petition archives. The update frequency is daily. Daily documents include petition registration forms, acceptance notices, transfer and assignment notices, handling opinions, review and recheck applications, and resolution plans. Core fields cover request content, handling entities, handling process steps, review opinions, and source system identifiers. The length of individual documents varies.
Constraints on the Source Citation and Traceability Link
Mixed calls of multi-source data require the traceability link to bind clear source system identifiers. This prevents mixing of petition data from different platforms. Document types are diverse, and core reference fields vary across documents. For example, handling opinions must link to document numbers. Review and recheck applications must mark applicant entities. Field extraction rules must be configured for specific use cases. The daily update feature requires the traceability system to support incremental matching of the latest handling data. It must also ensure cited content aligns with original document timelines, to prevent process node misalignment. Legal procedures for petition handling require traceability information to be accurate and traceable. Inaccurate traceability may lead to repeated petitions or review corrections.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the typical length of petition handling documents, ensures complete citation of core handling information |
| Source citation display toggle | Enabled | Binds the source system and document identifier for petition data, meets traceability requirements |
responseData | Includes source document number, handling unit, handling date | Matches core fields of petition documents, ensures cited information can be traced and verified |
detail | Enable full document traceability | Supports linking complete handling processes from historical petition archives, covers resolved case scenarios |
| Maximum number of citations per request | Top 3 entries | Avoids excessive cited content impacting reply readability, complies with standard petition reply requirements |
Three Common Errors
- When a workflow is exported and imported to a new environment, the petition data source configuration referenced in the workflow is lost. This occurs because associated data source configuration items were not selected during export, only basic settings for process nodes were exported.
- The end of a knowledge base reply displays "No permission to operate this conversation record", and citation display cannot be disabled. This occurs because the referenced petition archive data does not grant access permissions for the corresponding conversation role, and no permission exemption rule for cited information was configured.
- The \n symbol is output as-is in replies, without creating line breaks. This occurs because the FastGPT Markdown rendering switch was not enabled, or the response format configuration did not enable automatic escape processing.
How to Verify Successful Configuration
- Submit a simulated petition query request, check if source system, document number, and handling unit information for the corresponding document are attached at the end of the reply.
- Export the current workflow configuration, import it to a brand new test environment, check if the petition data source configuration items are fully loaded.
- Edit a test question that requires line breaks, submit it, confirm that the reply content has normal line breaks per the format, with no remaining \n symbols.
- Check the system logs, confirm that no permission error or data matching failure records appear in the citation traceability link.
The values provided are common starting points and should be evaluated against your own sample data.
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.