Data Structure and Update Rules for This Category
The data for this category primarily comes from existing system inventories, domestic software and hardware directories, test environments, and publicly available manufacturer materials. Daily produced documents include adaptation inventories, compatibility test reports, migration plans, and issue ledgers. Fields cover system name, original software version, domestic replacement version, compatibility verification result, risk level, and more. The data update frequency follows individual project cycles or quarterly, and changes with adjustments to domestic innovation directories and updated test results. Adaptation data entries vary across different projects.
Constraints on Citation Sources and Traceability Workflows
Data sources are scattered and diverse in type. During traceability activities, reviewers must clearly specify the document type and update timestamp corresponding to each citation, to ensure that original adaptation or test records can be traced back. Document structures vary; field formats differ across document types. When displaying citations, teams must match the logic of corresponding fields to avoid information confusion. Update frequencies are not fixed. Traceability information must include the data acquisition time to prevent referencing outdated adaptation conclusions. Additionally, data links software and hardware replacement and compatibility verification. Traceability must specify specific operations corresponding to migration links, distinguishing this from general office process data.
How to Configure Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Covers the content length range of single documents such as adaptation inventories and compatibility test reports, avoiding truncation of core verification information |
responseData | Return source document ID, document type, and update time | Clearly identifies the source and timeliness of cited data, complying with FastGPT v4.17.0 trusted innovation replacement adaptation traceability management requirements |
detail | Enable full field display, with a single field display limit of 200 characters | Displays core fields such as original software version and domestic replacement version, supporting reviewers' compatibility verification judgments |
| Single search limit | Top 3 entries | Adaptation data entries for individual projects are relatively concentrated. Limiting to the top 3 entries reduces reviewer burden while covering core verification results |
| Citation template | Follow the format "Document Type + System Name + Verification Result" | The field structure of adaptation-related documents is relatively uniform. Using standardized templates improves readability during reviews |
Three Common Configuration Errors
- Symptom: The AI response does not include any citation sources. Cause: The
responseDataconfiguration item is not enabled, and queried adaptation data is not linked to source documents, resulting in inability to generate traceability information. - Symptom: Knowledge base citation variables cannot be selected in code run nodes. Cause: The recall scope of the adaptation-related knowledge base is not limited to trusted innovation replacement documents, or the correct citation trigger logic is not configured, resulting in no corresponding options in the variable pool.
- Symptom: Only citation links are returned without response content. Cause:
quoteMaxTokenis set too small, truncating the main response content and only retaining source document information, or the prompt does not correctly guide the association logic between response and citations.
How to Confirm Correct Configuration
- Initiate an adaptation plan review query, and check whether the response includes traceability information such as source document type, name, and update time.
- Attempt to call knowledge base citation variables in the code node, and confirm that fields corresponding to adaptation inventories, compatibility test reports, and other documents can be selected.
- Adjust the value of
quoteMaxToken, and verify that both response content and citation sources are fully displayed without truncation. - Import an outdated adaptation test data set for query, and confirm whether the traceability information includes the data acquisition time.
The values provided are common starting points and should be evaluated against the samples relevant to the specific deployment scenario.
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.