This document is written based on FastGPT v4.17.0.
What Data for This Category Looks Like
Data sources for this category include customer-provided BOM, Gerber files, coordinate files, MES systems, solder paste and component batch ledgers, placement machines, SPI/AOI testing equipment, reflow oven temperature records, and more. Data updates in real time per work order and each line change.
Daily documents include BOM and coordinate files, line change sheets, stencil and furnace temperature records, first article confirmation reports, SPI/AOI test reports, repair records, traceability labels, and more. Fields cover part number, reference designator, alternative parts, component batch, furnace temperature parameters, and more. Units include millimeters, degrees Celsius, quantity, and more.
What Constraints Do These Characteristics Impose on the "Forms and Interactions" Link
Data for this category has strong real-time performance and updates per work order and line change. Form interactions must support dynamically pulling the latest component batch, furnace temperature parameters, and other data.
Multiple types of business documents correspond to different field sets. Interactions must allow splitting forms by business modules to avoid messy filling caused by too many fields.
Data sources involve multiple devices and systems. Interactions must support users to manually supplement or correct cross-system field values. They must also include basic part number and reference designator matching verification to prevent subsequent production problems caused by inconsistent data.
In addition, when a single bid involves multiple work orders, interactions must support quickly switching form data for different work orders.
How to Configure Settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
userSelect | Bind to the first 10 part number and reference designator options of the current work order, support single selection | Bidding needs to match fixed materials for the corresponding work order to avoid manual input errors |
formInput | Automatically synchronize component batch and furnace temperature data from MES and equipment, allow manual correction, synchronization interval is 30 seconds | Data is updated in real time, reduces manual entry costs, ensures data accuracy |
| Form block settings | Split by business modules, divided into material information, equipment parameters, test report modules, each module loads no more than 15 fields | Multiple types of business documents correspond to different fields, splitting improves filling efficiency |
| Verification trigger timing | Automatically trigger before form submission, delay 500 milliseconds based on actual measurement | Need to complete part number and reference designator matching verification before submission to prevent data inconsistency |
| Session process locking | Lock the current process after the work order is selected for the first time, do not allow switching options | Matches the requirement for fixed process in a single user session, avoids repeated changes to intended work orders during bidding |
Three Common Mistakes
- Phenomenon: The
userSelectcomponent displays empty options or options that do not match the current bid work order. Cause: The component is not bound to the BOM data of the corresponding work order, only uses global default options, resulting in incorrect material information being used in the bid document. - Phenomenon: After selecting the intended work order for the first time, reinitiating a conversation requires reselecting the work order, and the session process cannot be locked. Cause: The persistence attribute of
userSelectis not configured, the selection status is not retained after the session ends, which does not meet the requirement for fixed process in a single user session. - Phenomenon: Invalid array length error is triggered during form data loading. Cause: The field merging rule of
formInputis not configured correctly, resulting in abnormal length of the spliced field array, triggering a system error.
How to Confirm Configuration Is Complete
- Open the form page, check whether the options of the
userSelectcomponent match the part number and reference designator list of the current intended work order. - Try to modify the synchronized data of the
formInputcomponent, confirm that the modified data can be correctly synchronized to the bid document template. - Trigger form verification, check whether the matching relationship between part number and reference designator can be correctly identified, and there are no abnormal errors.
- After selecting the work order for the first time, reinitiate a conversation, confirm that the session process is still locked to the selected work order, and no re-selection is required.
The values given are common starting points and should be measured against the reader's own samples.