What the data for this category looks like
Survey and design business data primarily comes from pre-project site survey records, geotechnical investigation reports, professional design drawings, submission and approval documents, and site change orders. Data updates advance with project phases. Construction drawing data is updated after the preliminary design phase is completed. Corresponding node document content is updated synchronously during change processes. A single document includes fields such as project number, professional classification, submission and approval node, submission deadline, and approval status. Drawing files are measured in sheets. Submission and approval documents are measured in MB. Text documents are measured in characters.
What constraints do these characteristics impose on the "workflow orchestration" link
The multi-professional parallel execution business model of survey and design requires workflows to support parallel configuration of multi-branch nodes, and set variable judgment rules by professional classification. The volume of different file types varies widely, ranging from several KB submission forms to dozens of MB construction drawings. This requires document parsing nodes to be configured to adapt to processing thresholds for different files. Project data is updated frequently with project phases. This requires workflows to bind global parameters for real-time reading. Fixed approval deadlines exist in submission and approval links. This requires workflows to configure exception branches triggered by timeouts to avoid process blocking.
The following configurations apply to FastGPT v4.17.0.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Global variable binding | Bind the project number, approval status, and submission deadline in variables | Survey and design project data is updated frequently with phases, requiring real-time access to the latest business parameters |
| Judger node | Judge branches using the Boolean-type approval status in variables | Adapt to the approval switch logic of survey and design, matching the branch judgment requirements of business processes |
| Document parsing node | Set the single-file processing limit to 1000 MB, enable corresponding parsing rules by file type | Survey and design files include dozens of MB construction drawings, requiring adaptation to large-file processing |
| Multimodal node | Enable image recognition, set recognition timeout to 60 seconds | Survey and design drawings contain a large number of engineering symbols, requiring stable image recognition duration |
| Tool call node | Hide tool call output results, configure nodeId to associate with the end node | The business processing process does not need to display tool call details, only the final approval result needs to be pushed |
| Exception branch configuration | Set timeout threshold to 8 hours, trigger file upload exception branch | Submission and approval documents for survey and design are prone to failure due to network or permission issues during upload, requiring exception handling configuration |
Three common mistakes
- Symptom: The judger node cannot correctly recognize the Boolean approval status in
variables, and branch triggers do not match expected behavior. Cause: The Boolean variable is not set as a globally readable parameter, or the judgment condition does not align with the true and false value logic of the Boolean value. - Symptom: After enabling image recognition in the multimodal node, the prompt that image content cannot be provided is still returned. Cause: The node address of the uploaded file is not correctly bound, or the image parsing permission of the multimodal model is not enabled in the workflow.
- Symptom: After the tool call is completed, the call result is still displayed in the conversation interface, and the configured tool call end node does not take effect. Cause: The tool call end node does not correctly associate
nodeIdto subsequent nodes, or the automatic output switch for tool results is not turned off.
How to confirm the configuration is complete
- Trigger a simulated survey and design submission and approval process, and check whether the parameters bound to the global
variablesare updated in real time with process nodes. - Upload a test engineering drawing, and confirm that the multimodal node can normally recognize the image content and output corresponding parsing results.
- After configuring the tool call node, check the conversation output interface, and confirm that the detailed results of the tool call are not displayed.
- Simulate a file upload timeout scenario, and confirm that the exception branch can normally jump to the preset exception handling node.
The values provided here are common starting points, and should be evaluated 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.