What the data for this category looks like
Data sources include the national public resource trading platform, natural resource trading systems, property right exchange systems, and state-owned assets supervision systems. The update frequency is daily. Commonly used documents include transfer announcements, trading notices, bid applications, margin payment vouchers, transaction confirmation letters, listing result announcements, and property right transfer specifications. Most fields focus on the ownership, location, amount, bidding rules, and other details of the traded subject. They include standard business units such as square meters and ten thousand yuan. The field formats of each document are relatively fixed, but there are minor differences across transaction types such as land use rights, mining rights, and state-owned property rights.
What constraints these characteristics impose on forms and interactions
Daily updated data sources require form interactions to support real-time pulling of the latest transaction data. This avoids using expired announcements or rule content. Multiple types of fixed-structure business documents require forms to support associated input of multiple documents. Users can reference multiple materials such as bid applications and transfer announcements at the same time. Ownership verification is the core time-consuming link. Forms must include an interactive entry for ownership verification to reduce manual verification costs. Transaction data sources are scattered across multiple systems. Forms must uniformly connect to data sources from each system to ensure consistency of field information.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput | Enable multi-document associated input | This category of business requires referencing multiple related documents such as transfer announcements and bid applications at the same time. Multi-document input simplifies the user's material integration process |
userSelect | Preset ownership verification options | Ownership verification is a core business link. Presetting verification entries for natural resource departments and state-owned assets supervision institutions allows quick triggering of corresponding verification |
| Form field length limit | 800–1200 characters | The standard filling length for documents such as bid applications and property right transfer specifications falls within this range. This avoids display abnormalities caused by overly long content |
| Single interaction limit | First 5 entries | The core transaction information of this category is concentrated in the first 5 announcements or application materials. This reduces interference from invalid information |
| Form verification timeout | 600 seconds | The time required to pull data such as ownership and margin across systems is usually long. This duration matches conventional data pulling requirements |
| Result display format | Classified by transaction type | This category is divided into three types: land use rights, mining rights, and state-owned property rights. Classified display improves the readability of guidance content |
Three common mistakes
- Symptom: After calling the interface with stream set to true, the returned segmented transaction data cannot be correctly concatenated. Cause: The streaming output splicing rule for
formInputis not configured. Segmented returned business content cannot be integrated into complete process guidance information. - Symptom: Ownership fields are empty or verification fails after the form is submitted. Cause: The data source of the corresponding public resource trading platform is not associated. The subject ownership information cannot be automatically filled in or verified.
- Symptom: Knowledge base search results include transaction content not belonging to this category. Cause: No category filtering conditions are set through
userSelect. Irrelevant data from procurement or other public resource transactions is mixed in.
How to confirm the configuration is complete
- Upload a bid application document. Check whether the
formInputmodule can automatically associate the core content of the corresponding transfer announcement. - Select the ownership verification option. Confirm whether the
userSelectmodule jumps to the verification entry of the corresponding public resource trading platform. - Submit a test form. Check whether the margin field triggers verification prompts that comply with business rules.
- Call the streaming interface to submit a test request. Confirm that the segmented returned data can be correctly integrated into complete process guidance text.
The values provided here 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.