What this category of data looks like
Teams source rail transit equipment data from three places: manufacturing execution systems (MES), equipment operation and maintenance logs, and complete vehicle factory inspection reports. Two update schedules apply to this data:
- Production batch and inspection data sync in real time with production line cycles.
- Maintenance and fault records update per work order closure cycles.
Each document includes fixed fields: equipment ID, model specification, rated power, operating hours, fault code, and disposal process. Most fields use industrial standard units, including millimeters, kilowatts, and operating hours. Document structure is fixed, and fields cannot be adjusted arbitrarily. Reference only; verify against the target FastGPT release and deployment documentation.
Constraints on Forms and Interactions
The formInput field must strictly match preset fields including equipment ID and fault code. No custom input items are allowed. Industrial standard units require mandatory unit format validation during interaction steps. This prevents invalid inputs with non-standard units. The form’s connected data source must support quick filtering by production line and batch for real-time synced production data. This meets on-site business instant query requirements. The form must support association with existing maintenance work order IDs for maintenance data updated per work order cycles. This prevents duplicate entry of business information.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput field validation | Match preset formats for equipment ID, fault code, etc.; enable unit validation | Aligns with fixed fields and industrial standard unit requirements for rail transit equipment data |
userSelect data source filtering | Classify by production line batch, maintenance work order ID | Adapts to real-time and periodic updated business data call needs |
| Form submission timeout | 300 seconds | Matches cross-system query time requirements in industrial scenarios |
| Single recall result count | Top 8 entries | Matches average content length of individual rail transit equipment documents |
| Input box maximum length | 2000 characters | Fits text length for fault descriptions and disposal processes |
Three Common Configuration Mistakes
- Symptom: The
userSelectvariable dropdown menu displays no selectable equipment ID list. Cause: No association mapping has been configured between the data source and the rail transit equipment MES system. No filter field has been specified as equipment ID. - Symptom: When passing maintenance JSON data across HTTP requests, a large number of backslash escape characters appear in field values. Cause: Automatic JSON formatting processing is not enabled. Raw unvalidated text is passed directly.
- Symptom: No knowledge base selection option appears during tool call steps. Cause: The knowledge base association switch has not been enabled in the form configuration. No rail transit equipment maintenance knowledge base has been bound.
How to Verify Successful Configuration
- Open the form configuration page. Check that the
formInputfield only retains preset items such as equipment ID and fault code. Confirm that the unit validation switch is enabled. - Call the test data source. Verify that the
userSelectdropdown menu displays selectable values for corresponding production lines and work orders. - Submit a test form. Confirm that the returned business process guidance matches the preset rail transit equipment disposal process.
- Check system logs. Confirm that no submission timeout errors are triggered, and that recall result counts match the configured requirements.
The values provided here are common starting points. They should be evaluated against local deployment 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.