What data for this category looks like
Data for this category is sourced from registered and filed formulas, raw material safety documents, production equipment including weighing and emulsifying units, ERP/MES systems, laboratory records, and packaging material version information. Daily associated documents include formula process sheets, weighing and feeding records, emulsification or filling records, site cleaning and disinfection records, semi-finished and finished product inspection reports, and label review materials. Data updates run with each production batch or line change. Core fields cover formula raw materials, restricted substance lists, production parameters, packaging material batch numbers, and product claim content. All fields must stay consistent with filed information.
Constraints on forms and interactions
Data for this category links to filing compliance requirements and batch production workflows. Form interactions must bind the filed formula and equipment ledger for the relevant batch. This stops entry of content that does not match filed records. Data updated per batch or line change requires forms to support dynamic loading of inspection items and production parameters for the target production link. This cuts down on repetitive manual input. Production errors directly carry compliance and recall risks. Forms must include required field validation and operation logging. Forms must also support linking to historical maintenance and inspection records for easy reference.
How to set up the configuration
This configuration is explained for FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
formInput | Bind batch-associated equipment ledgers and filed data | Ensure input content matches compliant filing and production equipment information |
userSelect | Pre-set inspection items and maintenance type options for production links | Reduce manual input errors, align with fixed cosmetics manufacturing processes |
| Form submission timeout | 600 seconds | Adapt to batch production process rhythms, avoid submission failures due to waiting in production links |
| Form validation threshold | 85% match rate | Ensure consistency between input content and filed data, calibrated via actual testing |
| Maximum single input character count | 1000 characters | Align with single-section document length in formula process sheets |
| Dialog trigger rule | Hide only within the current workflow | Adapt to interaction requirements for application nesting scenarios |
Three common configuration errors
- Phenomenon: When an application is nested within another workflow, the dialog triggered by
formInputremains visible. Cause: The trigger range forformInputwas not configured correctly, with only the hide rule for the current workflow set. - Phenomenon: After form submission, an error indicating an empty field appears, with a prompt that no filed data was matched. Cause: Batch-associated filed data was not bound, so the form did not automatically load the corresponding compliance fields.
- Phenomenon: Form submission times out after submission, returning status code 504. Cause: The configured submission timeout period is too short, not aligned with the process waiting rhythm of batch production.
How to confirm proper configuration
- Submit test batch form data, and verify that input content automatically associates with the filed formula and equipment ledger for the corresponding batch.
- Switch between nested workflow and independent workflow scenarios, and confirm that the dialog triggered by
formInputfollows expected display rules. - Simulate waiting scenarios in production links, and verify that form submission completes within a reasonable time frame.
- Enter suspected non-compliant raw material fields, and confirm that the form triggers corresponding validation prompts.
Note: The values listed here are common starting points, and should be validated against samples specific to the actual use case.