What Data for This Category Looks Like
This category of data is sourced from design BOM, silicon steel sheet and insulating material data, vacuum and drying equipment, oil test reports, and test station test records. Daily documents include winding and core assembly records, vacuum drying records, insulating oil reports, partial discharge and withstand voltage test reports, and nameplate parameter tables. Data is updated once per device or per batch of materials, and must be bound to the unique nameplate number of a single device. Fields include insulating moisture content, partial discharge value, withstand voltage rating, and others, with corresponding units of %, pC, and kV. Full life cycle traceability for a single device must be implemented for all collected data.
What Constraints These Characteristics Impose on the Forms and Interactions Link
The requirement for single-device traceability means forms must be bound to a unique nameplate number to avoid mixing data from different devices. Multiple types of test documents require form fields to match exclusive fields for insulating oil, partial discharge tests, and other items, and adapt to the unit format unique to this category. The once-per-device or per-batch update frequency requires forms to support single-device data entry at a time, and to allow association with corresponding batch material data. The serious potential consequences of errors require forms to be configured with required field validation and format validation, to prevent invalid data entry that could lead to subsequent insulation breakdown or grid faults.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput | Enable required field validation, set input character limit to 1200, set timeout to 600 seconds | Adapt to the text length of test records, timeout matches the full entry duration for a single device |
userSelect | Preset options including insulating oil reports, partial discharge test reports, etc., default to select the latest 3 historical documents, lock the input box after triggering | Match the daily document types of this category, reduce manual selection costs, prevent incomplete interactions from being interrupted by new messages |
| Cross-branch link configuration | Enable cross-branch reuse permissions, support jumping to this form node from any branch | Adapt to the process reuse requirements of multi-process inspection, meet calls from different production links |
| Input guidance configuration | Enable input guidance, fill in field prompts exclusive to this category | Guide users to enter test data that meets the format, reduce entry error rates |
| Timeout handling configuration | Set timeout to 900 seconds, automatically restore the session after timeout | Adapt to long-duration entry scenarios for complex test reports, avoid accidental session interruptions |
This document is compatible with FastGPT v4.17.0
Three Common Misconfigurations
- Symptom: After triggering the
userSelectmodule, sending a new message before completing the selection causes the session interface to display a process interruption status, and subsequent inspection steps cannot be continued. Cause: The input lock rule after module triggering is not configured, and new messages will overwrite incomplete interaction requests, causing the link to fail to proceed normally. - Symptom: When attempting to jump to the form node from another production branch, the link cannot be activated after saving the configuration, and the form does not pop up normally. Cause: The cross-branch reuse permission of the form node is not enabled, and by default only supports calls from nodes within the current link.
- Symptom: After enabling input guidance and filling in a custom thesaurus address, a "parameter format error" pop-up appears during debug preview. Cause: The custom thesaurus does not include keywords for the category's exclusive test report fields, causing the thesaurus verification to fail.
How to Verify Proper Configuration
- Trigger the
formInputmodule, enter a device number that does not meet format requirements, and confirm that a format error prompt pops up on the interface. - Trigger the
userSelectmodule, send a new message without making any selection, and confirm that the session automatically restores after entering the timeout waiting state. - Configure cross-branch jump to the form node, start a session from another branch, and confirm that the form loads normally and data can be entered.
- Enable input guidance and fill in the category-specific thesaurus, and confirm that the input guidance content is displayed normally during debug preview with no error pop-ups.
The values provided here are common starting points and should be evaluated against appropriate samples.