What this category of data looks like
Data for work consultation and reply scenarios at power generation groups primarily comes from three sources: internal ticketing systems, power policy document libraries, and operation and maintenance consultation records from individual power plants. There are two data update schedules: daily work orders are updated in real time when consultations are submitted, while monthly updated policy documents include the latest power approval workflows and electricity price adjustment rules. Each document includes the following fields: consultation category, affiliated power plant, work order number, processing time limit, and feedback channel. The processing time limit is measured in working days. Work order numbers use a 16-character combination of letters and digits. Consultation categories fall into three types: installation application, maintenance request, and policy consultation.
Constraints for Forms and Interactions
Decentralized data sources require forms to support multi-data source association, to avoid repeated entry of cross-system information. Content with different update frequencies needs different caching strategies. Daily work orders should use a short caching cycle, while policy documents can use a longer cycle. Fields have specific unit and numbering rules, so forms must include unit prompts and format validation to block entries that do not follow the power generation group’s internal specifications. Fixed consultation category attributes require forms to pre-set category options, to reduce user input errors.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput | Configured in 3 groups, with required mark added for each group | Matches the business logic of basic information, consultation content, and attachment upload for power generation group work consultations |
userSelect | Preset 12 common internal department options, supports manual addition | The internal department structure of power generation groups is relatively fixed, and preset options can improve filling efficiency |
| Knowledge base variable reference | Bind ticketing system and power policy document datasets, enable real-time synchronization | Ensure that consultation replies match the latest internal ticketing and policy data |
| Push trigger rule | Push after work order status changes, with a delay of 10-30 seconds | Avoid excessive push frequency that causes load overload on the enterprise WeChat interface |
| Single search limit | Recall the top 8 results | Adapts to the common recall volume of power generation group consultation content, avoids excessive results interfering with user judgment |
| Attachment upload limit | Single file no larger than 500 MB, total size no larger than 2 GB | Adapts to the conventional upload needs of power generation group engineering drawings and test reports |
Three Common Configuration Errors
- An error
failed to create post pis prompted when uploading .txt format policy documents. The cause is that the upload validation rules of the knowledge base text dataset are not correctly configured, and the format requirements for long-text policy documents of the power generation group are not adapted. - Internal work order fields are empty in consultation results. The cause is that the ticketing system variable corresponding to
formInputis not correctly bound, and the data source association configuration is not completed. - The enterprise WeChat bot cannot actively push work progress notifications. The cause is that the interaction rules triggered by status changes are not set, and only passive question-and-answer interaction is configured.
How to Verify Successful Configuration
- A test form can be filled out, a preset department option selected, and the loading of options for the
userSelectcomponent confirmed. - An engineering drawing within 500 MB can be uploaded, and successful attachment upload confirmed with no error prompts.
- A work order status change can be triggered, and the enterprise WeChat checked for corresponding push messages.
- The knowledge base variable reference can be called, and the returned work order data confirmed to match the latest data from the internal system.
The values provided here are common starting points and should be measured 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.