What this category's data looks like
Laboratory hazardous chemicals procurement and ledger materials include three types: hazardous chemicals procurement applications, usage registrations, and inventory ledgers. Procurement applications record the product name, specification, quantity, application date, and approval signature; usage registrations record the user, quantity used, date of use, and custodian signature; inventory ledgers record inbound, outbound, and balance quantities as well as the inventory count date. Materials are updated by batch, and the same record may appear in multiple materials, so field names, quantities, dates, signatures, and receipt status need to be compared item by item. When entering the workflow, the procurement application serves as the source basis material, the usage registration serves as the circulation verification material, and the inventory ledger serves as the balance verification material; together, the three support basis entries that can be traced back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The basis entries that can be traced back to the original text are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | The product name, quantity, application date, and approval signature in the procurement application must match the usage registration and inventory ledger item by item; a missing signature or receipt is regarded as incomplete basis | Check the options and branch connections one by one in the node, and confirm that the procurement application basis entry can be traced back to the original text |
| Usage registration | The quantity used, date of use, and custodian signature in the usage registration must be consistent with the procurement application and inventory ledger; if the name, quantity, or date of the same record does not match, the basis is unusable | Trigger a user selection node once, and check the node status and branch direction in the run record |
| Inventory ledger | The inbound, outbound, and balance quantities and inventory count date in the inventory ledger must match the procurement application and usage registration; if the version is not synchronized, the basis entry is invalidated | Reference the selection result variable in a subsequent node and run a trial once, and verify that the variable has been passed to the subsequent node |
| User selection node | Each option corresponds to one branch, and the selection result must be consistent with the branch direction; after the interaction is completed, the process continues execution | Check variables, nodeId, and branch connections, and confirm that the selection result variable has been passed to the subsequent node |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the procurement application and the usage registration. Cause: The two materials were entered separately, and the fields were not compared record by record.
- Symptom: The inventory ledger version is not synchronized, and the old balance quantity is still referenced. Cause: After the material was updated, the current version was not checked, and the basis entry points back to outdated original text.
- Symptom: The procurement application lacks an approval signature or the usage registration lacks a receipt. Cause: The signature and receipt fields were not included in the basis entry check, resulting in incomplete basis.
How to verify the setup
This function acceptance: run trials option by option, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and after the interaction is completed, continue execution according to the corresponding option.
Business test: ask a basis question that spans materials, see whether the answer gives a traceable source, and verify that the source comes from the institution’s materials, the version is current, and the entry matches the original text.
- In the user selection node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and check the reference relationship between
nodeIdandvariables. - Trigger a user selection node once, check the node status in the run record, confirm that the conversation enters the interaction state and records the workflow status, and continue downward execution after the user completes the selection.