What data looks like for this category
Core data for this category comes from design history files, device and material lots, MES systems, cleanroom environment monitoring equipment, sterilization equipment, and inspection and calibration systems. Daily documents include production process specifications, batch production records, cleanroom zone records, sterilization batch records, inspection reports, software version records, adverse event and traceability materials. Data updates are synchronized with each batch or unit of product production. Cleanroom environment monitoring data is updated on a fixed scheduled basis. Document fields include unique device identifier, batch number, cleanroom environment parameters, sterilization parameters, inspection results, and other items. These fields must be strongly linked to production batches.
What constraints these characteristics impose on workflow orchestration
Dispersed data sources and the requirement for strong links to production batches mean workflow orchestration must support batch binding and association verification for multi-source data. Data updates change dynamically with production batches, so workflows must support triggering nodes per batch to avoid cross-batch data confusion. Strict document control and traceability requirements mean workflows must enforce association of core fields such as unique device identifiers. Workflows must also record inputs and outputs for each step to meet compliance traceability standards. Exception reports must link to all documents of the corresponding production batch, so workflows need to integrate upload and verification processes for multiple types of attachments.
Configuration settings
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
variables | Bind device lot, cleanroom monitoring data, and sterilization parameters as variables per production batch | Data sources for this category are dispersed. Core business fields must be linked per batch to ensure process data accurately matches production batches |
nodeId | Assign fixed nodeId to form submission, file upload, and exception reporting nodes | Ensure accurate positioning when invoking workflow nodes, avoid workflow trigger errors |
| Form submission pre-validation | Trigger subsequent nodes only after file upload and required field completion | Prevent incomplete exception reports or process documents from entering controlled processes |
| Timeout threshold | 600–900 seconds | Document processing for this category involves pulling sterilization and cleanroom data across systems, which takes longer. Sufficient processing time must be reserved |
| Single-batch file storage quota | 1000 MB per production batch | The volume of process documents and exception report attachments for each production batch is fixed. Limiting storage per batch prevents excessive resource usage |
| Full-node logging | Enable the logging switch | Meet traceability requirements for this category, facilitate subsequent verification of workflow execution status |
Three common mistakes
- When invoking the workflow API, uploaded files cannot be passed as variables. The symptom is an API error reporting missing parameters. The cause is that the uploaded file identifier was not bound to the
variablesparameter. - The workflow does not restrict triggering after form input is complete. The symptom is generating an exception report without uploading sterilization batch records. The cause is that the form submission pre-validation rule was not configured.
- The conversation log is empty after invoking the workflow. The symptom is retrieving an empty array when querying workflow logs from yesterday or today. The cause is that log recording parameters were not configured for the corresponding
nodeId.
How to confirm the configuration is correct
- Upload sterilization batch records and cleanroom monitoring files for a single batch, confirm that the file identifiers are automatically bound to the workflow's
variablesparameter. - Attempt to trigger the workflow by skipping required form fields, confirm that the workflow cannot proceed to subsequent nodes.
- After invoking the workflow API, retrieve the operation log for the corresponding
nodeId, confirm that complete workflow records are generated. - On the workflow management page of FastGPT v4.17.0, check the storage usage for a single batch, confirm that it does not exceed the preset quota limit.
The values provided are common starting points and should be measured against the reader's own samples.