What this category's data looks like
The materials for laboratory hazardous chemical procurement and ledger come from procurement request forms, usage registration forms, inventory ledgers, handover receipts, and version records. The update cadence advances by batch and usage time points, and the field characteristics center on name, quantity, date, signature, version number, and responsible person. When a hazardous chemical procurement request enters the workflow, it serves as the object to be drafted; the usage registration serves as the source for verifying quantity and date; the inventory ledger serves as the baseline for comparing balances and versions; and the handover record serves as the credential for receipt and acknowledgment. The material drafting and responsibility handover stage needs to string the above sources into an issuable draft and keep fields consistent before the next stage's receipt.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The issuable material draft and handover record are completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters the interaction 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 request | Whether name, quantity, date, signature, version number, and responsible person are complete, and 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 record |
| Usage registration | Whether the usage quantity, usage date, user signature, and receipt match the procurement request and inventory ledger | Reference the selection result variable in a subsequent node and run a trial once, and check the name, quantity, and date of the same record in both materials |
| Inventory ledger | Whether the balance quantity, version, and date are synchronized, and whether missing signatures or receipts are blocked | Trigger a user selection node once, view the node status and branch direction in the run record, and confirm that it is blocked when the version is not synchronized |
| Handover record | Whether the responsible person is clear, receipt is complete, acknowledgment is complete, and version and date are consistent | Draft one according to the template and complete one handover, check whether missing items are blocked, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the procurement request and the usage registration. Cause: The two materials are maintained separately, and fields are not checked item by item in the node.
- Symptom: The inventory ledger version is not synchronized, and the draft is inconsistent with the ledger balance. Cause: The version record is not updated with the branch direction, and subsequent nodes reference old variables.
- Symptom: The handover record lacks a signature or receipt, and the process stops. Cause: After the interaction is completed, the branch corresponding to the selected option is not followed, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
Acceptance of this feature: Run trials option by option, check the branch direction and interaction status in the run record, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- 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 record.
- Reference the selection result variable in a subsequent node and run a trial once, and check the name, quantity, date, and signature of the same record in both materials.