What the data for this category looks like
Data related to urban commercial bank yield rates primarily comes from official wealth management sections, interbank regulatory reporting systems, and financial data aggregation APIs. The data updates on a T+1 schedule for each business day, and is delayed for holidays. This documentation presents data in structured table format, with each row corresponding to one wealth management product. Fields include product unique identifier, full product name, investment term range, minimum investment threshold, latest yield metric, and data update time. Field naming may vary slightly across issuing entities.
What constraints these characteristics impose on the "form and interaction" workflow
Dispersed data sources and inconsistent field naming require forms to support custom field mapping, to adapt to reporting formats from different urban commercial banks. The T+1 update schedule requires setting reasonable pull intervals in interactions, to avoid unnecessary high-frequency requests. Multi-dimensional product fields require forms to support configurable multi-condition filter components, to meet query needs across different scenarios. Some data must be pulled from internal private APIs of urban commercial banks, requiring configuration of API security verification rules in interactions to adapt to access permission requirements of financial institutions.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
schedule_fetch_interval | 86400 seconds | Matches the T+1 update schedule for urban commercial bank yield data, one daily pull covers the latest available data |
custom_field_mapping | Map by product identifier, full product name, term range, yield metric, and update time | Adapts to the standard field structure of urban commercial bank wealth management daily reports, supports custom extension of non-standard fields |
filter_condition_group | Support multi-dimensional combined filtering | Meets interaction requirements for querying urban commercial bank wealth management products by term, minimum investment threshold, and other dimensions |
api_whitelist_enabled | Enabled | Adapts to security verification requirements for financial institution data APIs, prevents blocked unauthorized access |
fetch_timeout | 300 seconds | Covers normal response delays for urban commercial bank data APIs, prevents pull tasks from being terminated due to timeout |
result_display_limit | Top 20 entries | Balances information display volume and interaction smoothness, aligns with common user expectations for single query results |
The parameter values provided on this page are common starting points for configuration setup. Actual values are affected by material format, data volume, and business rules. Specific scenarios require individual analysis, and it is recommended to test on samples specific to the deployment before finalizing settings.
Three common configuration mistakes
- Symptom: After associating a global variable from the knowledge base, the variable cannot be selected in the condition configuration panel of the conditional judge. Cause: The condition configuration permission for the global variable is not enabled. By default, only condition settings for basic variables are available.
- Symptom: After manually triggering a data pull, the returned result is empty with no error message. Cause: The urban commercial bank data API is not added to the system whitelist, and the interface directly blocks unauthorized requests.
- Symptom: The scheduled pull task triggers multiple times per day, exceeding the API call limit. Cause:
schedule_fetch_intervalis set to a value less than86400 seconds, which does not match the T+1 update schedule for urban commercial banks.
How to confirm successful configuration
- Manually trigger a data pull, check if the fields of the returned result match the configured
custom_field_mapping, to confirm that the field mapping rule takes effect. - View the scheduled task execution logs, verify that the time interval between two pulls matches the configured
schedule_fetch_interval. - Navigate to the conditional judge configuration page, attempt to associate a created knowledge base global variable, to confirm that condition judgment rules can be added.
- Test by calling the urban commercial bank data API, confirm that the request is not blocked and does not return error codes such as
403 Forbiddenor401 Unauthorized.
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.