What the data for this category looks like
Reference only; verify against the target FastGPT release and deployment documentation.
Constraints imposed on forms and interactions
Because data is sourced from multiple internal systems, field formats have strict specifications. Form interactions must include preset targeted validation rules to avoid invalid data entry. The real-time update feature requires that system status updates are triggered synchronously after form submission, with no delays. Multi-level approval business logic requires forms to dynamically display the current approval node and prevent users from skipping levels when submitting. The fixed attachment size range requires the interaction flow to limit uploaded file sizes to avoid exceeding system storage or transmission limits.
Configuration Settings
| Configuration Item | Suggested Value | Rationale |
|---|---|---|
| Form field validation rules | Match ^[1-2]#[A-Z0-9]{3}$ format | Adapts to the fixed naming rules for nuclear power operation unit numbers to ensure field validity |
| Upload attachment limits | Maximum 100 MB total, single file maximum 50 MB | Adapts to the common storage sizes of nuclear power business attachments such as maintenance reports and radiation detection reports |
formInput preset values | Automatically populate the current logged-in user's employee ID and affiliated work team | Reduces manual input steps and improves business handling efficiency |
userSelect optional scope | Only approvers from the current approval level | Complies with the level control requirements of nuclear power approval to avoid selecting incorrect approvers |
| Pre-submission confirmation popup | Display core document information (operation type, unit number) | Prevents accidental submission of important business documents and reduces the probability of operational errors |
Three Common Misconfigurations
- Phenomenon: A generic network error prompt is triggered when uploading nuclear power business attachments, and the prompt does not clearly state that the attachment size exceeds the limit. Cause: No dedicated attachment size validation error prompt text was configured, and generic error prompt logic was reused.
- Phenomenon: The form model selection dropdown only displays generic large models, and pre-configured reordering models cannot be selected. Cause: Visibility permissions for nuclear power operation-specific models were not enabled in segmented scenario configurations, causing pre-configured reordering models to not load.
- Phenomenon: No user confirmation popup appears during the tool call phase, and approval submission operations are executed directly. Cause: No pre-submission confirmation step was configured in the
formInputphase, skipping the user validation process.
How to Verify Successful Configuration
- Enter a unit number matching the
^[1-2]#[A-Z0-9]{3}$format and check if field validation passes. - Upload a test file with a size of 120 MB and check if a dedicated error prompt for exceeding attachment size is triggered.
- View the
userSelectdropdown and confirm that only the list of approvers from the current approval level is displayed. - Click the submit button and check if a confirmation popup displaying the operation type and unit number appears.
The values provided 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.