What this category's data looks like
Laboratory hazardous chemical procurement and ledgers involve three types of materials: hazardous chemical procurement applications, usage registration, and inventory ledgers. Procurement applications record the product name, specification, quantity, application date, and approval signature; usage registration records the user, usage date, purpose, and receipt; inventory ledgers record the balance quantity, inbound date, and custodian signature. The three types of materials come from different sources and have different update rhythms: procurement applications are submitted as needs arise, usage registration is filled in per instance, and inventory ledgers are updated by batch or period. When entering the question-answering intake and missing-item follow-up stage, procurement applications serve as the basis for demand, usage registration as the basis for consumption, and inventory ledgers as the basis for balances. The three corroborate one another and are used to identify whether names, quantities, dates, and signatures are complete and consistent.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. "Intake records and items to be completed" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | Check whether the product name, specification, quantity, application date, and approval signature are complete, and whether the names and quantities are consistent with the usage registration and inventory ledger | Check the options and branch connections one by one in the node, reference variables and nodeId for a trial run, and view the node status in the run records |
| Usage registration | Check whether the user, usage date, purpose, and receipt are complete, and whether the dates and quantities match the procurement application and inventory ledger | Reference the selection result variable in a subsequent node and run a trial once to confirm it has been passed to the subsequent node |
| Inventory ledger | Check whether the balance quantity, inbound date, and custodian signature are complete, and whether the records are version-synchronized with the procurement application and usage registration | Trigger the user selection node once and view the node status and branch direction in the run records |
| Intake records and items to be completed | Missing items are identified and followed up on, answers have material basis, and the matter is transferred to the handler | Reference variables in a subsequent node and run a trial once to confirm the branch direction and interaction status records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the procurement application and the inventory ledger. Cause: The two materials are updated separately, without cross-checking and version synchronization.
- Symptom: The usage registration lacks a signature or receipt but still proceeds to subsequent processing. Cause: The intake stage does not list signatures and receipts as conditions for missing-item follow-up.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to the subsequent node.
How to verify the setup
This feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: submit a question that lacks key information and see whether it follows up first before answering.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once to confirm it has been passed to the subsequent node, and that the same session does not repeatedly enter the interaction.