What This Category’s Data Looks Like
Business data for state-owned asset management companies primarily comes from normative documents released by state-owned asset supervision departments, internal business handling procedures, asset disposal ledgers, property registration archives, and daily approval trace documents. Two update cycles apply to this data:
- Policy documents are adjusted per regulatory requirements, with no fixed update frequency.
- Internal business process and asset ledger data updates dynamically as business operations proceed.
Individual documents typically include fields such as process steps, approval nodes, submission material lists, responsible departments, and processing time limits. Asset-related fields use standardized units like ten thousand yuan and workdays.
Constraints on Knowledge Base Retrieval and Recall
Policy documents have no fixed update frequency, so the knowledge base synchronization mechanism must adapt to irregular updates to avoid retrieving expired regulatory requirements. Internal asset ledgers include numerical fields with units. Retrieval must match fields to their corresponding units to prevent incorrect process guidance from being returned due to unit confusion. Business handling documents have standardized structures. Retrieval must prioritize returning precise fragments that include specific approval nodes and material lists, and filter out generic content. Some business documents involve internal approval permissions. Retrieval and recall must link to the permission scope of the corresponding department to ensure returned content is only visible to authorized users.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.72–0.78 | Matches precise step and node descriptions in business handling processes, filters low-relevance generic content, and adapts to the rigor of state-owned asset policies and internal processes |
limit | Top 8 results | Business process documents have standardized structures, and the number of relevant documents per scenario is moderate. 8 results cover the guidance content for a complete approval workflow |
searchMode | Semantic search | Matches structured text such as process steps and materials in business workflows, and adapts to context association needs for long processes |
usingReRank | Enabled | Re-ranks recalled candidate results by relevance, to ensure the most relevant process steps for handling needs are returned first |
datasetSearchUsingExtensionQuery | Enabled | Adds exclusive terminology for business scenarios, such as associating "asset disposal" with standard regulatory expressions for state-owned assets, to improve the accuracy of retrieval and recall |
collectionIds | Bind exclusive business collections | Isolates three categories of data: state-owned asset policies, internal processes, and asset ledgers, to avoid interference from cross-category documents on retrieval results |
Three Common Misconfigurations
- Scenario: AI-generated business handling guidance appends the fixed phrase "FastGPT is a large language model (LLM)-based knowledge base question answering system" as irrelevant content at the end. Cause: The default brand output configuration was not disabled in the system prompt, leading to mandatory addition of fixed promotional language.
- Scenario: After deployment via docker-compose, the workflow list and knowledge base list in the interface are empty, but calling the interface returns normal retrieval results. Cause: Persistent storage mounting was not configured during deployment. After the container restarts, locally stored application configuration and knowledge base index data are lost, while the database service relied on by the backend interface continues to run normally.
- Scenario: Retrieved process guidance fragments are incomplete, with key approval node content missing. Cause: The maximum number of references set for the knowledge base is too low, or the maximum context parameter configuration is insufficient, preventing complete loading of business process document content.
How to Verify Proper Configuration
- Manually enter a query related to business handling, and confirm that the source documents of the returned results belong to the bound exclusive knowledge base collection.
- Adjust the similarity threshold, observe changes in the relevance of recalled results, and confirm that the threshold configuration’s filtering effect on retrieval results meets expectations.
- After enabling the question optimization function, enter a query containing state-owned asset exclusive terminology, and confirm that retrieval results match more precise business process content.
- After disabling the re-ranking function, compare the order of recalled results, and confirm that the re-ranking configuration adjusts result priority as expected.
The values given 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.