What Data for This Category Looks Like
Data sources for this category include design BOM, silicon steel sheet and insulating material ledgers, vacuum drying equipment logs, oil test reports, and partial discharge and withstand voltage test records from the test station. Data is updated per product and per batch of raw materials. Daily documents include winding and core assembly records, vacuum drying records, insulating oil test reports, partial discharge and withstand voltage test reports, and nameplate parameter tables. Core fields include insulating moisture content, partial discharge peak value, and withstand voltage test voltage, with corresponding units typically being ppm, pC, and kV.
Constraints Imposed by These Characteristics on the "Multi-turn Dialogue and Prompt Engineering" Link
The per-product updated data characteristics of this category require multi-turn dialogue to bind chatId to associate the unique identifier of the corresponding product, to avoid mixing data across devices. Specific units for core fields require prompt engineering to clearly define parameter formats, to prevent input errors. Demand for multiple document types requires dialogue to gradually guide users to supplement corresponding document types, to avoid requesting full data at one time. The high-value attributes of single-unit equipment require dialogue context to support filtering historical records by product, to ensure the accuracy of maintenance Q&A. Additionally, time-consuming links such as insulation structure verification and high-voltage test analysis require multi-turn dialogue to preset standardized inspection items, to lower user input thresholds.
Configuration Setup
The following configurations are based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
chatId | Bind to the nameplate number of a single transformer | Data for this category is updated per product, so full documents for the corresponding product must be associated to ensure dialogue context only points to the currently maintained equipment |
messages | Limit single-turn dialogue context to the first 10 historical messages | Core test data for this category has a large volume; overly long context reduces response speed and avoids interference from redundant information |
variables | Preset three required variables: insulating moisture content, partial discharge peak value, and withstand voltage test voltage, with units of ppm, pC, and kV respectively | The core verification fields for inspection and maintenance in this category are the above parameters, so users must be guided to supplement data in the corresponding format |
| Single search limit | Recall the first 8 documents | This category has a large number of associated documents for a single product; excessive recall increases context load, adjust based on actual measurements |
| Maximum context length | 8000–12000 characters | This category requires integrating multiple test reports and assembly records; this range covers full key document content for typical single-unit equipment |
| Dialogue timeout setting | 600 seconds | Document integration for single-unit equipment in this category takes a long time; this threshold covers typical data loading requirements |
Three Common Misconfigurations
- Symptom: After clicking the dialogue opening quick button, the preset inspection item guide menu does not pop up. Cause: The
variablespreset variable corresponding to the opening quick button is not bound in the prompt engineering configuration, so the button trigger logic is not associated with the corresponding dialogue process. - Symptom: Insulating oil report images fail to load when viewing dialogue history without a logged-in status. Cause: Public access permissions for uploaded documents in dialogue history are not configured, so non-logged-in users cannot obtain image storage links.
- Symptom: When calling an inspection Q&A application in a nested workflow, the dialogue logs of the called application are not recorded in the parent workflow. Cause: The
chatIdcontext synchronization configuration for the called application is not enabled, so dialogue history cannot be synchronized and stored across workflows.
How to Verify Correct Configuration
- Manually trigger the dialogue opening quick button, confirm whether the preset guide items for transformer inspection are displayed, and adjust the guide content per actual inspection requirements.
- Switch to a non-logged-in status, access the dialogue history page, confirm whether images from insulating oil reports and test reports load normally, and adjust access permissions per storage service configuration.
- Trigger form input nodes in both a single workflow and a nested workflow, confirm whether the dialogue box displays as expected, and adjust node display rules per scenario requirements.
- Call the inspection Q&A application in the nested workflow, confirm whether the parent workflow's logs include dialogue interaction records from the called application, and adjust context synchronization configuration per
chatIdbinding rules.
The values provided are common starting points and should be measured against the reader's own samples.