What This Category of Data Looks Like
Reference only; verify against the target FastGPT release and deployment documentation.
Constraints Imposed on Forms and Interactions by These Characteristics
Core refined oil sales data has strong timeliness, so form interactions must adapt to dynamic data sources. Retail fuel prices change daily, so the fuel price query field in formInput must bind to a real-time interface, and static cached values should not be used. Inventory levels fluctuate in real time, so inventory inquiry items in the form must pull the latest data immediately after the user submits a query. Service outlet addresses and coordinates are bound, so the input box must enable auto-complete to match regional gas station locations. Fuel grades are fixed enumeration values, so the options for the userSelect component must be preset to 92 octane gasoline, 95 octane gasoline, 98 octane gasoline, and 0 diesel, to prevent users from entering invalid grades. Additionally, price-related inputs must validate the numerical format with two decimal places, to prevent invalid characters from interfering with subsequent retrieval processes.
How to Set the Configuration
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
formInput | Enable dynamic data source binding, set input validation rule to "only allow numbers, letters, and specified punctuation", set character limit to 800–1200 characters | Refined oil inquiry content usually includes fuel type, price, inventory and other information; overly long content increases knowledge base retrieval load |
userSelect | Preset enumeration options as 92 octane gasoline, 95 octane gasoline, 98 octane gasoline, 0 diesel, enable dynamic refresh, set refresh interval to 24 hours | Fuel grades are fixed, but fuel prices update daily; associated event options must sync with price adjustments |
| Input box auto-complete threshold | Trigger after 3 characters are entered | Avoid frequent auto-complete triggering that affects operational fluency, while quickly matching gas station outlets or fuel grades |
| Form submission validation rules | Enable required field validation, configure non-empty prompt copy | Ensure users submit complete inquiry information, avoid invalid retrieval requests |
| Knowledge base association scope | Bind gas station service knowledge base and fuel price public notice knowledge base | Refined oil inquiries mainly revolve around fuel prices, outlets, and fuel types; limiting the scope improves retrieval accuracy |
Three Common Mistakes
- Phenomenon: When the content submitted in
formInputexceeds 1200 characters, the interface pops up an "input content too long" error, and the workflow returns status code 413. Cause: The character limit validation for form input was not configured, causing the load threshold of the knowledge base retrieval to be exceeded. - Phenomenon: When calling the workflow API to pass a custom knowledge base variable as a data source, the retrieval result is empty. Cause: The dynamic binding switch for workflow variables was not enabled, causing the variable to not be correctly passed to the knowledge base search node.
- Phenomenon: After configuring the
userSelectnode, the subsequent knowledge base retrieval node does not execute. Cause: The required submission rule for theuserSelectnode was not set, causing the workflow to terminate directly when the user has not completed the selection.
How to Verify That the Configuration Is Correct
- Manually enter inquiry content exceeding 1200 characters, verify whether the character limit validation prompt is triggered.
- Call the workflow API to pass a custom knowledge base variable, check whether the retrieval result is associated with documents from the corresponding knowledge base.
- Configure the required rule for the
userSelectnode, intentionally submit without completing the selection, verify whether the workflow triggers the required field validation. - Wait 24 hours, check whether the fuel price options in the
userSelectnode have updated to the latest daily prices.
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.