What Data for This Category Looks Like
This category's data typically originates from silicon wafer incoming materials, MES systems, diffusion furnaces, coating equipment, printing presses, EL and IV testing equipment, and laboratories. Update frequencies include per batch of materials, per wafer test results, and daily summaries. Daily documents include process cards, diffusion and coating parameter records, printing and sintering logs, EL test images, IV grading data, and yield analysis reports. Data fields include diffusion sheet resistance, coating thickness, printed grid line width, electrical performance test parameters, and other process indicators and test results corresponding to different processes.
What Constraints These Characteristics Impose on Forms and Interactions
The data for this category comes from multiple sources and covers multiple process nodes. Form interactions must split field groups by processes such as texturing, diffusion, coating, printing and sintering, to avoid input errors caused by cross-process information stacking. Data update frequencies cover single batches, single wafer tests, and daily summaries. Interactions must support batch import of single test data and association binding with batch numbers, to ensure that process parameters match corresponding quotation batches. There are various types of daily documents. Forms must support uploading attachments in different formats such as process cards and test images, and automatically associate metadata. Fields are linked to process logic. Interactions must restrict input of subsequent fields for which pre-processes are not completed, to prevent invalid data submissions. In tendering scenarios, form fields must also be bound to quotation accounting logic, to avoid quotation deviations caused by missing process parameters.
How to Configure
This configuration applies to FastGPT v4.17.0
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Form grouping | Split into 5-8 groups by process steps | Matches the document and data structure of multiple processes in this category, reduces the complexity of single-page data entry |
| Attachment upload limit | Maximum 200 MB per file, supports jpg, png, csv formats | Adapts to the size and type of common documents such as EL test images and process parameter csv records |
| Data association rules | Automatically bind corresponding process data by batch number | Meets the business requirement of batch-based traceability for this category, avoids data misalignment |
userSelect | Preset process node options and corresponding fields | Reduces user input errors, matches the fixed process flow of multiple processes |
| Batch import template | Export standard templates containing batch numbers and process parameters | Adapts to the daily summary batch data entry requirement, improves efficiency |
| Field validation | Validate required field completeness when formInput is triggered | Ensures that submitted form data includes core process parameters required for tendering |
Three Common Mistakes
- Phenomenon: Quotation data returned by API calls differs significantly from online chat results, and some process parameters are not correctly associated. Cause: The API call does not have context association logic configured by default, and cannot reuse the batch number association rule from historical interactions, leading to incorrect parameter matching.
- Phenomenon: Empty field errors occur when batch importing IV grading data. Cause: No field mapping rule is configured between the form and the import template, resulting in non-standard csv data being unable to match preset process parameter fields.
- Phenomenon: Server timeout error is returned after submitting a form. Cause: No limit is set on the total size of attachments uploaded in a single batch, causing oversized attachments to occupy excessive processing resources.
How to Confirm Proper Configuration
- Import the preset process parameter csv template, check whether the form automatically matches batch numbers and corresponding process fields.
- Call the API to submit a test request containing complete process data, compare the consistency between the returned result and online chat.
- Upload EL test image and process card attachments, check whether the form correctly identifies the attachment type and displays the upload status.
- Test input of subsequent fields for which pre-processes are not completed, check whether validation interception is triggered to prevent invalid submissions.
The values provided here are common starting points and should be evaluated against relevant samples.