What Data Looks Like for This Category
Data for this category primarily comes from registered process documents, raw material batch ledgers, DCS control systems, weighing systems, LIMS laboratory information management systems, chromatography data systems, and QMS quality management systems. Data updates trigger per production batch and each process step. Daily documents include batch production records, material balance ledgers, reaction and purification process records, cleaning validation records, impurity profile reports, and deviation and change documents. Core fields include batch identifier, reaction temperature, yield value, impurity content, and solvent residue amount, with corresponding units such as degrees Celsius, kilograms, ppm, and others.
Constraints Imposed on Workflow Orchestration
Multi-source heterogeneous data with updates per batch and process step requires workflow orchestration to adapt to data pull formats from different systems. This avoids data parsing errors. Full-process data volume for a single batch is large. Workflows must support aggregating data by batch to avoid single-processing overload. Core documents include multiple types of process and quality records. Workflows must pre-set validation rules for corresponding fields to ensure no key parameters are missing. Strict quality compliance requirements apply. Workflows must embed exception interception nodes to trigger additional audit processes for deviation and change-related data. This prevents non-compliant data from circulating.
Configuration Settings
This configuration is adapted for FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
| Trigger Method | Trigger by production batch events, or daily scheduled scanning of pending audit batches | Matches the rhythm of batch-by-batch and step-by-step data updates, ensuring audits cover all process nodes |
| Global Variable Configuration | Pre-set variables such as batch number, reaction temperature range, impurity threshold interval, etc. | Matches the fixed field format of core documents, simplifying cross-node parameter calls |
| Cross-Workflow Call Timeout | Set to 300 seconds | Adapts to the dependent execution duration of multi-step audits, avoiding interruptions to sub-workflow execution |
| External Data Pull Count | Top 10 entries | Matches the reasonable scale of single-batch process data, avoiding pull overload |
| External Data Pull Timeout | Set to 120 seconds | Adapts to data return speeds from multi-source systems, avoiding pull process blockages |
Three Common Configuration Mistakes
- Phenomenon: After a parent workflow calls a sub-workflow, subsequent nodes following the node with
nodeIdselected by the user in the sub-workflow do not execute. Logs show the node status as not triggered. Cause: When the parent workflow calls the sub-workflow, context parameters required for user interaction are not passed through. This causes the user selection node in the sub-workflow to fail to complete input, so subsequent nodes cannot be triggered. - Phenomenon: Attempting to update an AI model output to a null value via
variables, but the variable panel shows the original value was not cleared. Cause: The switch to overwrite existing values for variable updates is not enabled. This prevents null values from overwriting historically stored variable data. - Phenomenon: When passing custom parameters via an application link, workflow global variables are not assigned correctly. Logs show the parameters were not received. Cause: The receiving key name for the corresponding parameter is not pre-configured in the workflow global variable settings. This causes parameters passed via the link to fail to match the target variable.
How to Confirm Configuration Is Complete
- Trigger a simulated batch audit process, check that workflow nodes execute in the preset order with no missing nodes.
- Perform a variable update operation, verify that the specified
variablesfield can be correctly modified or cleared. - Generate a test application link and pass parameters, check that workflow global variables can correctly receive the corresponding parameters.
- Call the configured sub-workflow, view the sub-workflow execution logs, confirm that subsequent nodes following the node with
nodeIdselected by the user are triggered normally.
The values provided are common starting points and should be measured against the reader's own samples.