What this category's data looks like
Data comes from official online service channels, product disclosure information from offline business outlets, and internal operational business ledgers. Data updates are completed at a fixed daily time, covering all product data from the previous workday. The document structure uses structured lists or tables. Each row corresponds to one financial product, and includes the product unique identifier, product category, tenor, return calculation benchmark item, and data update date. Tenor units are natural days or natural months. Return calculation benchmark items use annualized reference units.
Constraints Imposed by These Characteristics on Multi-turn Dialogue and Prompt Engineering
Scattered data sources require prompts to clearly define the data call scope, to prevent the model from referencing non-official or outdated information. The daily update rhythm requires context prompts to include timestamps for the latest data, to ensure every reply references content updated on the current day. The structured document structure requires prompts to clearly specify filter rules for fields such as product category and tenor dimension, to avoid generating results that do not match the required fields. Users may adjust filter conditions repeatedly during multi-turn interactions, so prompts must retain context filter parameters to reduce repeated input operations.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
maxContext | Previous 10 turns of dialogue context | Controls the retained length of conversation history, to fit multi-turn interaction scenarios for financial product filtering |
Recall count | Top 8 entries | When matching financial product data, covers common tenor categories to avoid missing core product information |
Similarity threshold | 0.75–0.85 | Balances recall precision and coverage, to fit the fine-grained classification characteristics of financial products |
PARSE_FILE_TIMEOUT_SECONDS | 300 seconds | Reserves sufficient time to parse structured documents of financial product disclosures, to avoid parsing timeouts |
UPLOAD_FILE_MAX_SIZE | 100 MB | Allows uploading complete financial product document packages, to meet bulk data import requirements |
SSE_RESPONSE_TIMEOUT | 60 seconds | Controls the maximum waiting duration for dialogue replies, to prevent client disconnections due to timeouts |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume and business rules. Each situation should be analyzed individually, and it is recommended to test on your own samples before finalizing.
Common Configuration Mistakes
- Issue: The dialogue interface cannot upload audio files, or no valid reply is generated after upload. Cause: The associated speech-to-text plugin is not configured, and the voice upload permission for the dialogue module is not enabled.
- Issue: The Markdown table in the AI reply is truncated, with
...[hide X char]displayed at the end. Cause: The output length limits formaxContextor knowledge base recall are not adjusted, causing long table content to exceed the default truncation threshold. - Issue: The
insufficient_quotaerror appears during dialogue, with a prompt that upstream load is saturated. Cause: Current limiting parameters for dialogue requests are not configured, or the resource quota for the current group is insufficient to support multi-turn concurrent interactions.
How to Verify Proper Configuration
- Initiate a dialogue that includes specific product categories and tenor dimensions, and verify that the reply content matches the preset product data fields.
- Complete two or more rounds of filter condition adjustment interactions, and verify that subsequent replies inherit the filter parameters from the previous round.
- Upload the structured document of financial product disclosures, and verify that the number of parsed entries matches the original document.
- Trigger a dialogue reply timeout scenario, and verify that the timeout prompt matches the configured error copy.
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-14.