Data Characteristics in this Category
CSO (Contract Sales Organization) product data originates from pharmaceutical companies, CRO (Contract Research Organization) firms, medical institutions, and third-party market research agencies. Data update frequency varies by source. Clinical trial data may update quarterly or annually. Market sales data may update monthly or weekly. Document structures are diverse, including standardized product specifications, clinical study reports (primarily PDF), sales data reports (Excel or CSV), market analysis reports (Word or PPT), and database records exported from internal management systems. Fields and units are industry-specific, such as drug names (INN, brand names), indications (ICD-10 codes), dosages (mg, µg), dosage forms, batch numbers, expiration dates, sales regions, sales amounts (RMB, USD), sales quantities (boxes, units), and market share percentages.
Constraints Imposed by These Characteristics on "Tool Calling and Plugins"
The fragmented and diverse nature of CSO product data requires tool calling and plugins to have robust multi-format file parsing capabilities, especially deep parsing of PDF documents to extract key information from unstructured text. Varying data update frequencies necessitate sophisticated data synchronization and caching strategies for plugins to ensure the timeliness of recalled information. Complex document structures, containing numerous specialized terms and industry codes, demand higher accuracy from RAG (Retrieval-Augmented Generation) recall. This requires enhanced recall through customized embedding models or glossaries. Additionally, when dealing with sensitive data like sales amounts and market share, plugins need strict data permission control and anonymization capabilities. The specificity of fields and units requires tools to correctly identify and convert units when processing numerical data, avoiding ambiguity.
Configuration Guidelines
| Configuration Item | Suggested Value | Rationale |
|---|---|---|
UPLOAD_FILE_MAX_SIZE | 500 MB | CSO product documents, especially clinical reports and large market analysis reports, are typically large. |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Parsing complex PDF documents is time-consuming and requires sufficient processing time. |
Chunk size | 800–1200 characters | Balances semantic completeness and snippet recall efficiency, avoiding overly long or short text segments. |
Recall count | Top 10 entries | Ensures coverage of enough relevant context for complex queries, improving recall accuracy. |
Similarity threshold | 0.75 | For documents with many specialized terms, increase the threshold to filter out irrelevant results. |
API_CONCURRENT_LIMIT | Calibrate by actual measurement | External API call concurrency requires stress testing based on actual backend service capabilities and response times. |
Three Common Pitfalls
- Plugins fail to parse specific PDF document formats, leading to incomplete information extraction. This occurs when the enhanced PDF parsing module is not enabled or incorrectly configured, failing to process scanned or specially encrypted PDF files effectively.
- Frequent timeout errors or connection failures occur when calling external data interfaces. This usually happens when the expected health concurrency of the API is not met, or network policies restrict communication between FastGPT and external services.
- Numerical field units are incorrect or missing in query results. This happens when the data preprocessing stage fails to effectively identify and standardize CSO product-specific units of measurement, or when plugins do not perform unit validation during data integration.
How to Verify Configuration
- Upload various types and sizes of CSO product documents (e.g., clinical report PDFs, Excel sales reports). Verify successful parsing and extraction of key information. Check the completeness of extracted fields.
- Simulate high concurrency scenarios. Test the response time and success rate of external tool calls. Ensure API concurrency is within the expected range.
- Execute queries involving numerical values. Check if units in the returned numerical fields are correctly identified and displayed, such as "100 mg" or "500 万美元".
- Regularly check plugin logs for error messages, especially those related to file parsing failures, API call failures, or data format errors.
The values provided are common starting points. Measure them against your 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-21.