What Data for This Category Looks Like
The data sources for this category include procurement orders, drawing specifications, supplier quality certificates, test equipment outputs, historical quality records, and supplier portal information. Update frequency adjusts with each batch of incoming materials, monthly/quarterly supplier evaluations, and irregular audits. Daily documents cover inspection specifications, sampling plans, incoming material inspection reports, supplier audit reports, exception contact sheets, 8D corrective action reports, and concession acceptance approval forms. Data fields include batch number, inspection items, non-conforming item descriptions, supplier qualification numbers, and corrective action verification records. Inherent business field identifiers are used, with no additional custom units. Field naming follows general manufacturing quality control specifications.
Constraints Imposed by These Characteristics on the Citation Source and Traceability Link
Data sources for this category are scattered and have varying formats. It is necessary to accurately match batch and version information to avoid referencing expired inspection specifications or incoming material data from non-corresponding batches. The high update frequency requires the knowledge base to sync the latest supplier quality certificates, monthly evaluation records, and temporary exception corrective data in real time. Otherwise, traceability results will not match current business scenarios. Documents include multi-level approval and corrective verification links, so it is necessary to accurately associate exception reports with corresponding corrective closure records to ensure traceability covers the complete business process. It is also necessary to distinguish the association between historical quality data and current batches to avoid confusing different suppliers’ qualifications and test results.
How to Configure the Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum Context | First 1200–1500 characters | Adapts to the multi-field document length of this category, avoids truncating critical batch and corrective action information |
quoteMaxToken | 800–1000 token | Controls the output length of cited content, ensures complete display of inspection basis when drafting exception reports |
responseData | Includes citation source ID and document title | Meets business traceability requirements, facilitates associating exception reports with corresponding inspection specifications or incoming material reports |
detail | Enabled | Displays complete field information of cited documents, such as supplier number, batch number, etc., to meet traceability accuracy requirements |
| Single Search Limit | Top 6 entries | Covers multi-source inspection data, avoids missing critical supplier qualifications or historical quality records |
| Knowledge Base Sync Cycle | Calibrated based on actual testing | Adapts to the update rhythm of this category, ensures knowledge base data aligns with business system status |
Three Common Errors
- Phenomenon: Cited content returned in conversations only shows the document title, and does not include the corresponding batch number or supplier ID. Cause: The
detailparameter is not enabled, and the field display rules for cited data are not configured. - Phenomenon: Unable to obtain the knowledge base ID of the citation source after calling the conversation interface. Cause:
responseDatais not configured to a return format that includes the citation source ID, resulting in the interface not returning the corresponding fields. - Phenomenon: Cited content is too long and gets truncated, making it impossible to fully display the sampling plan in the inspection specification. Cause: The value of
quoteMaxTokenis too low, and does not cover the actual length of the corresponding document.
How to Confirm the Configuration Is Correct
- Enter the knowledge base configuration page of FastGPT v4.17.0, check whether the switches related to cited field display are enabled.
- Initiate a simulated incoming material exception conversation, and check whether the returned results include complete field information of the cited documents.
- Call the conversation interface, verify whether the returned data includes the citation source ID and document title corresponding to
responseData. - After adjusting the
quoteMaxTokenparameter, test whether the output length of the cited content meets the display requirements of business documents.
Note: The values provided here are common starting points and should be evaluated against the reader’s own samples.