What this category's data looks like
Laboratory hazardous chemical procurement and ledgers involve three types of materials: procurement applications, usage registrations, and inventory ledgers. A procurement application contains the item name, specification, quantity, application date, and approval signature; a usage registration contains the usage date, user, quantity, and receipt; an inventory ledger contains the balance quantity, date, and custodian signature. The materials are summarized weekly or monthly, sourced from paper or electronic forms submitted by each laboratory, and the update cadence is synchronized with the experiment progress. After entering the workflow, the procurement application, usage registration, and inventory ledger each enter the user selection node as independent materials, and the node records the interaction state and outputs the branch direction; subsequent nodes continue execution according to the branch, completing the progress table and the statistical scope description.
Configuration and implementation checks
This step is executed by the workflow nodes (user selection and branching), outputting the branch direction and interaction state records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | Whether the fields, date, and signature are complete, and whether the name, quantity, and date of the same record are consistent across the two materials | Check the options and branch connections one by one in the node, reference variables and run a trial once, and view the node status in the run records |
| Usage registration | Whether the usage date corresponds to the receipt signature, and whether the version is synchronized | Reference the selection result variable in a subsequent node and run a trial, and check the branch direction and interaction state records corresponding to nodeId |
| Inventory ledger | Whether the balance quantity, date, and custodian signature match the application and usage records | Trigger a user selection node once, view the node status in the run records, and check the options and branch connections |
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 entered separately, and the scope is not uniformly checked in the node branches.
- Symptom: The usage registration version is not synchronized, and the old and new versions coexist. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue execution according to the branch.
- Symptom: The procurement application lacks a signature or receipt. Cause: A certain option was selected but the default branch was still taken, and the interaction state was not recorded to the corresponding node.
How to verify the setup
Feature acceptance: Run a trial for each option, check the branch direction and interaction state in the run records, and confirm that variables has been passed to subsequent nodes and that nodeId corresponds to the correct branch.
Business test: Use one week of records to check the totals, and see whether the scope and exceptions are clearly written.
- Check the options and branch connections one by one in the node, trigger a 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, check the options and branch direction, and confirm that the same session does not enter the interaction repeatedly.