What this category of data looks like
Survey and design data primarily originates from on-site survey and measurement reports, architectural structural design drawings, industry specification and standard documents, and project approval and filing documents. The data update rhythm is adjusted according to project progress, with on-demand updates during the schematic design and construction drawing design phases, and archived and locked after project completion. Most documents use a structure combining structured fields and unstructured text. Core fields include survey point coordinates (unit: meters), structural load parameters (unit: kPa), design numbers, and approval document numbers. Some documents include CAD or PDF format drawing attachments.
What constraints these characteristics impose on the forms and interactions link
Structured fields in survey and design data have dedicated units. This requires forms to be configured with unit validation rules to prevent input values from mismatching preset units. Data is updated dynamically with project phases. This requires forms to support filtering optional fields by project phase, hiding content that has not reached the reporting node to reduce redundant information. Some documents include large drawing attachments. This requires forms to support uploading design files such as CAD and PDF, and set a reasonable file size limit. Core associated fields such as approval document numbers need to connect to project ledgers. This requires forms to support automatic pulling from existing project data to reduce duplicate data entry operations.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput | Input box with unit validation, preset unit options | Most survey and design data has dedicated units, to avoid input errors caused by unit mismatches |
userSelect | Optional list filtered by project phase, maximum 5 selections per submission | Parameters vary significantly across survey and design phases, filtering by phase reduces reporting interference |
| File upload configuration | Supports CAD and PDF formats, maximum single file size 1000 MB | Adapts to mainstream design file formats, meets upload requirements for large drawings |
| Dynamic field trigger | Lazy load fields from unreached phases based on project status | Data updates with project phases, preloading causes redundant information |
| Context association configuration | Connect approval document number fields to project ledgers, automatically fill existing data | Reduces duplicate data entry and improves reporting accuracy |
| Request timeout configuration | 600 second timeout threshold | Adapts to processing durations for large drawing uploads and complex survey data |
Three common configuration errors
- Phenomenon: After creating a plugin and referencing it in a workflow during the code execution step, clicking the input field pops up an error message stating "duplicate input information". Cause: No deduplication validation rule configured for
formInput, leading to duplicate submission of reporting requests for the same survey and design project. - Phenomenon: Only a small number of optional models are visible in tool call configuration, and all available models cannot be selected. Cause: The permission filtering scope for
userSelectwas not configured correctly, and call permissions for corresponding models were not enabled. - Phenomenon: No expected tool call is triggered after form submission, only AI natural language responses are returned. Cause: No trigger conditions configured for dynamic fields, resulting in required parameters for the current project phase not being loaded, failing to meet the parameter requirements for tool calls.
How to confirm the configuration is correct
- Manually enter fields with units. Verify if a unit mismatch prompt appears, confirming that the validation rule for
formInputis active. - Switch between different project phases. Verify if form fields dynamically adjust, confirming that the dynamic field trigger configuration is active.
- Upload CAD or PDF format design files. Verify that the file upload function supports the corresponding formats, confirming that the file upload configuration is active.
- In the FastGPT v4.17.0 backend, cross-check configuration items against the recommended settings in the table above.
The values provided here are common starting points, and should be evaluated against the operator’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.